10 12.22.2016
GPS Operation
During a GPS fix attempt, the VHF transmitter will be silent. A GPS attempt may last as long as
the setting that was selected during programming but may also be shorter depending on the
collar’s view of the sky. Whether the fix attempt was successful or not will be indicated by the
VHF beep pattern that follows the attempt.
You will only hear these beep patterns if the
VHF
transmitter was scheduled to beep during this time.
Satellite Transmission Operation
During a satellite data transmission attempt, the VHF transmitter will be silent for up to 30
seconds. If the transmission was successful, data will be transmitted to the ATS server for
processing. If the transmission is not successful, the collar will attempt another transmission in
twelve minutes (provided that the transmission attempt does not conflict with a GPS fix attempt).
If the collar fails to transmit data for ten consecutive attempts, the collar will enter
Satellite
Transmission Suppression
(see Section 9 Satellite Transmission Suppression for more details).
Remote Commands
The GPS fix schedule of your G2110E2 can be adjusted remotely via satellite to a regular
interval. Available intervals are (in minutes): 10, 20, 30, 90, 120, 360, 480, 720, and 1440. The
schedule can also be adjusted from these intervals back to the original schedule. Note: Adjusting
the fix schedule may interfere with the programmed frequency of the email transmissions.
The GPS fix attempt duration can be adjusted remotely via satellite to one of three options: 60
seconds, 120 seconds, or 180 seconds.
The mortality setting of the G2110E2 can be adjusted remotely. Available settings are four
hours, six hours, eight hours, ten hours, twelve hours, and mortality disabled. The satellite email
schedule can be changed remotely. Available intervals are every 4, 6, 8, 12, 24, 48, 72, 96, 120,
144, or 168 hours.
Finally, the G2110E2 can be released remotely with a command as well.
NOTE: The G2110E2 is automatically configured to release when the main battery voltage
is low.
For all remote requests, the changes will take place after the next email transmission, not when
the remote command is issued. See Section 8 Remote Commands for more details regarding
remote programming.
