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

• The instrument first tries to connect to a WiFi™ router or access-point in its vicinity. Up to three separate WiFi™ routers and access points can be configured for the connection, each with its own level of priority, and security. The instrument will try to connect to each one in order of priority, until it finds a connection.

• When connected to the network through the router or access-point, the instrument will then try to connect to a server by its IP-address. A list of up to four IP addresses can be configured for the connection. The instrument will try to connect to each one in sequence, until it finds a connection.

• After connecting to the server, the instrument will try to talk to the Instrument_Listener application. That application must be running on the server in order to allow the instrument to exchange data with the server. The Instrument_Listener application can listen to and manage a number of instruments.

 

The instrument has a total time of 1 minute to go through all three 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.

 

Note: If the Instrument_Listener application is not running on the server, the instrument will not be able to download any data or send any alarm emails. All those operations are performed by the Listener application running on the server.

 

Note: In order for the last connection stage to work, the server must be on the same local network as the instrument, or if on a global network, all firewalls in the data path (including the Windows firewall) must allow incoming connections to it.