When trying to connect, either at the preset interval, or for an email alarm, the instrument will do it in two stages:

• The instrument first tries to connect to a WiFi™ router or access-point in its vicinity.

• Once connected to the network through the router or access-point, the instrument will then try to connect to a server (either the specified email server, or the server running the Instrument_Listener application, depending if that is an alarm or part of the regular reporting of recorded levels. The server connection can be done to a specified IP address, or to a domain name. Connecting using a domain name is preferable because IP addresses are often subject to change.

 

The instrument has a total time of 1 minute to go through the two stages. If the final stage is not established by the end of that minute, the instrument stops trying in order to preserve battery. It will then retry at the next preset interval, or if a new email alarm is triggered.

 

Note: In order to maximize data throughput and minimize power consumption, it is best to locate the router or access point close to the instrument so WiFi™ communications are reliable.

Note: If the Instrument_Listener application is not running on the server, the instrument will not be able to download any data.

Note: The panel shown in Figure 5 will display the progression of the connection when the instrument is connected through USB. It is designed to help debugging connection problems.

 

The Connection Status field indicates graphically the different stages of connection. Each icon (7, 8, 9 and 10 in Figure 5) indicates a different connection stage:

• Indicator 7 Active: The instrument is actively trying to connect to a Router or Access-Point

• Indicators 7 and 8 Active: The instrument is connected to a Router or Access Point. In this case the SSID of the Router or Access Point is written in indicator 5.

• Indicators 7, 8 and 9 Active: The instrument is on the network.

• Indicators 7, 8, 9 and 10 Active: The instrument has connected to the server and is talking to the Instrument_Listener application. In that case the server’s IP address is written in indicator 11.