![ATS G2110E2 User Manual Download Page 16](http://html1.mh-extra.com/html/ats/g2110e2/g2110e2_user-manual_3005213016.webp)
16 12.22.2016
other hand, if it is a scheduled transmission time and the collar has no successful fixes to send,
the collar will still transmit on schedule.
Note: If a collar transmits data containing GPS fix locations more than 9 days apart, the
Julian day and hour of the later data in the email may be incorrect. However, the data
stored on the collar will be correct and the next email should have correct data. This
situation may arise if you wish to test the collar and wait more than nine days after initial
testing before deploying the collar. If this is a concern, deploy the collar as soon as possible
after programming/ reprogramming the collar.
Data Access
The G2110E2 is assigned to a specific web account email address. When the collar transmits
data, that data is uploaded to the web account. An email will only be sent to the email address if
the collar has experienced an alarm-type event (mortality, VIT event, fawn event, low battery,
collar release). The email will provide more details on the status of the collar.
NOTE: The email will come from
. It is an automatically generated
email so it is possible that the email will be interpreted as spam. Please allow emails from
this address if you wish to view data via emails and check your spam folders when you are
not receiving data since security options are constantly updated.
The web account for the collar can be accessed at
www.atsidaq.com
. If you do not have a
username and password, please contact ATS to obtain one. There are multiple features of the
web account. You can download GPS data, Google Earth kml files, quickly determine if there
are collars that need immediate attention, and request schedule changes. For more information on
schedule changes, see Section 8, Remote Commands.
The web account was designed to be self-explanatory. Please contact ATS if you have any
questions regarding the web account.
NOTE: ATS does not generally store data older than 1.5 years old. Please make
arrangements to store data older than this as necessary.