Large system planning guidelines - AP10 - RFL100

Guidelines for large VaiNet systems Technical Note

Document code
M212596EN
Revision
C
Language
English
Product
AP10
RFL100
Document type
Technical note

Plan before you start

Before moving on to deploying a large VaiNet system, make sure you have a detailed device installation plan. From the point of view of network deployment, the plan should include the following information for VaiNet devices:

  • Model, serial number, firmware version, and installation location of each device
  • VaiNet segment and channel of each access point
  • VaiNet segment of each data logger

Place each segment in its own physical area

In situations where the VaiNet radio traffic is high, the data transfer performance will be better if each segment is placed its own physical area. A typical example of such a situation is the recovery from a network outage when measurement data from data loggers is being backfilled to the viewLinc system.

Concrete walls, floors, and other heavy structures are natural radio barriers that can be utilized between segments where possible. Note that due to the long range of VaiNet, such structures will typically not entirely block the signals.

Maximize access point connectivity for data loggers

VaiNet data loggers will automatically reconnect if they lose their access point connection. To minimize the impact of any access point outages, place access points so that each data logger is in the range of more than one access point. Centrally placed open locations within the segment area are good options.

It is not necessary to consider the access point placement or VaiNet channel assignments between segments. As long as an access point has its own VaiNet channel within the VaiNet segment and a suitable location in relation to the data loggers it is planned to connect, all is well.

Leave some free connection capacity in each segment

As data loggers will not connect to access points outside their home segment, free connection capacity is not shared between segments. It is therefore best to avoid filling any segment to the maximum. If possible, each segment should have sufficient free capacity to reconnect the data loggers in case a single access point becomes unavailable. Unallocated capacity will also help to prevent problems that could be caused by access points filling up, possibly leaving the remaining capacity in the segment unreachable by some data loggers.

Add segments as necessary and consider future expansion

Standard systems of up to 8 access points only need to use the default segment A. This maximizes communication performance and makes the best use of connection capacity. If desired, standard-sized systems can optionally implement more than one segment, for example to limit data logger roaming between areas.

Large systems of more than 8 access points must use at least 2 segments. The number of segments you should have depends on the size of the system and its physical layout. It is a good idea to leave some room for expansion in each segment in case more data loggers or access points are needed later.