While locally at a sensor, you can initiate a manual check-in. During each check-in all logged reading(s) are transmitted to OneVue and any pending setting updates are downloaded to the sensor.
A Primex sensor checks-in to OneVue at regular intervals, per the frequency set in its Check-In Interval setting. The sensor's Logging Interval (how often a sensor stores a logged reading) and Check-In Interval settings are configured from a sensor's gateway profile. To view these settings, go to Monitoring > Monitored Assets > select the Monitored Asset assigned to the sensor > select the sensor type link > from the sensor profile, select its Gateway ID link.
How to initiate a manual check-in
From the front of the sensor, press and quickly release its Check-in button (up arrow).
The sensor emits a series of audio beeps indicating is connection sequence. During an active check-in connection, additional pressing of the check-in button is ignored.
Either of the below beep sequences, indicates a failed check-in:
If you only hear 1 beep: sensor could not connect to the facility's network.
If you hear 1 beep followed by 2 beeps: sensor could not connect to OneVue.
When a sensor failed to check-in to OneVue, its local LCD display also shows No Signal (lower right-corner). Signal OK indicates its last check-in was successful.
If a check-in fails, this is commonly due to the sensor could not establish a network connection. During this condition, all logged readings are stored in the sensor's non-volatile memory. If the number of failed check-ins exceeds the size of the non-volatile memory, the oldest readings are overwritten. A sensor can store up to 4096 readings in its non-volatile memory.
For troubleshooting, see topic Sensor and Monitored Asset in an Alarm state, Unresponsive status.