Doc No. IM4772-7
Page 7 of 14
iSense
3.5
Adding iSense to Synergy
The iSense must be added to Synergy using the Family Type
iSense
; s
ee Synergy User Manual ‘Adding
Sensors’, for full details on adding sensors to Synergy.
Note:
Do NOT try to use the iSense with RadioLog, and do NOT attempt to configure the iSense with the
legacy iSenseConfig Utility or iSense USB Configurator.
3.6
Sensor operation
The devices will log data on-board at the pre-set log interval, and in due course send these to the IMC
Remote Data Service. This send process will occur under the following circumstances:
After the ‘SendInterval’
OR 300 logged points are available
OR 12hours has elapsed
OR the measurement is in alarm
In the event of communications failure the device will buffer up to 250k of data and gradually send this after
communications is restored, and in reverse time order. If and when this happens at each wake up the device
will send its current packet plus the most recent three packets whose sending was not successful
If the measurement goes into alarm then the unit will start to transmit every 15minutes for a period of up to 2
hours. At this time it will revert to its programmed behaviour. No alarm will be re-triggered until three logs have
been within the alarm limits.
The device sends its battery voltage with each message; this can be viewed via Synergy.
3.7
Alarm Handling
It is possible to set level alarms on each individual iSense channel. It is important to remember that as the
device only calls in, then these values can only be changed on a standard connect cycle. This cycle will
happen at some time later
– possibly many hours later – after the Synergy change.
Prior to an alarm the sensors are sampled at the nominal interval and sent periodically, but if an alarm
condition is detected it will transmit this within the following 4 minutes. Thus the maximum iSense response
time to an alarm is (nominal logging in4 min).
Assuming that the GSM network is up and running perfectly then there will be up to a further 8 minutes before
it appears on screens because of redirector and Synergy delays. Any provider network delays are outside of
our control and may be added to this time.
The device will continue to send data rapidly for 2 hours (every 15 minutes) after the initial transition and then
revert to normal mode. If the alarm condition persists then this will start the sequence again.
To cope with the system delays you should set the alarm reactivation time on the PC to a minimum of
30 minutes, and not manually reset it prior to this or you risk seeing the same alarm reported twice.
