Sutron Corporation 8310 & 7310 Users Manual 8800-1125Rev. 2.7 (BETA) 4/16/2014 pg. 105
type 8310.ssf
time
When "SetupPassword" and "DataPassword" are defined, each line of commands need to
include that code. When including an authentication code, put it before the command. For
example, if the authentication code is “mycode”, then the file above becomes:
Example file “commands_with_authentication.sbd”:
mycode type 8310.ssf
mycode time
PwrOnInterval + PwrOnTime + PwrOnDuration
Specifies when and for how long the system will power-on the Iridum modem to listen for
incoming messages. PwrOnInterval specifies how often to power on, PwrOnTime specifies an
offset to the interval, and PwrOnDuration specifies how long to stay powered.
For example, with PwrOnInterval = “01:00:00”, PwrOnTime = “00:30:00”, and PwrOnDuration =
“00:15:00”, the modem will be powered on every hour at half-past the hour, and will stay
powered for 15 minutes.
SetupPassword and DataPassword
These two properties specify authorization codes used to validate incoming command
messages. SetupPassword specifies the authorization code for “setup-level” access, while
DataPassword specifies the authorization code for “data-level” access.
Incoming command messages have setup-level access by default. When the SetupPassword
property contains an authorization string, any and all incoming messages that normally require
setup-level access to be processed must prefix the command with the authorization code. For
example, to command the station to reboot with an authorization code of “MyAuthCode”, the
incoming message content would be “MyAuthCode !reboot”.
SyncTime + LocalTimeOffset
When SyncTime is set to “YES”, the system synchronizes its system time to Iridium time once
daily. Iridium time is GMT (Greenwich Mean Time). To set the time to local time, enter the
difference in number of minutes between GMT and local time into LocalTimeOffset. For
example, Eastern Standard Time (EST) is 5 hours behind GMT. Hence, to sync the logger to EST
time using the Iridium clock, you would set LocalTimeOffset to 300.
The Iridium system provides GMT time using a counter relative to an “epoch” time defined by
the Iridium authority. The epoch time changes roughly every 7 or so years. In order for the
logger to compute system time properly through a change to the Iridium epoch, the logger must
store both the current epoch time, and the next expected epoch time. As of version 2.7, the
7310/8310 logger is programmed to handle an Iridium epoch change in May, 2014.
Iridium will announce new epoch changes in coming years. When a new epoch date is
announced, the logger must be told to store the new date. To change the value of the next
epoch date-time stored in the logger, send the following command to the logger via Iridium
short burst message:
irsenxt MM/DD/YYYY HH:MM:SS
For example, to set the next epoch date-time to 5PM June 3, 2020, you would send, “irsenxt
06/03/2020 17:00:00”.
It’s also possible to set the current Iridium epoch date-time in the logger, though this would only
be required if the logger failed to set the proper epoch date itself during an epoch transition. To
set the current epoch date, you would send the command, “irse MM/DD/YYYY HH:MM:SS”.
To Next Page
Loading...
