Page 67 of 101
DWG ID: 181-0101-00A
Date: 2003-09-26
DAYTIME yymmddhhmm[ss] (UTC time)
DAYTIME is used to manually enter a date and time (after which time and date are
formatted for display by the specifications given in DAYSTR).
When date and time are entered, using the input format specified in the command and
explained below, the values entered are used to set the software clock/calendar. The
software clock/calendar is then used for MHEARD logging, as well as for CSTAMP and
MSTAMP functions.
When entering the daytime digits, enter them in pure number sequence with no spaces,
dashes, or slashes. Notice that there are two digits each for entering a year, month, day,
hour, minute, and (optionally) second. Also, notice that you need to use the order given
here, which has nothing to do with the format (given in DATSTR) for displaying date and
time values. For example, to enter 2003, July 30, at 22:30:00 hours, the value of the
DAYTIME parameter would be 030730223000. In this case, seconds were entered, so the
string is 12 characters long (2 characters for each of six pieces of information entered).
If DAYTIME is entered with no parameter, the daytime is displayed using the format
defined by the DAYSTR command.
Note: If the TALON includes the GPS option, the DAYTIME will be set automatically
from the UTC time in the GPS data.
Hint: If the time appears to be stuck, check the current value of DAYSTR, to be sure that
the DAYSTR setting is being used to format the display of time and date, and not (in
error) to attempt to supply an actual date and time. If this is not the case, fix the problem
and see if time and date displays work correctly.
See also: cstamp, daytweak, daystr, mheard, and mstamp
DBLDISC {ON | OFF}
default OFF
When OFF, only one disconnect command (Disc) need be given to terminate an
unsuccessful connect attempt. If you are actually connected, the normal disconnect
sequence will occur.
When ON, a normal disconnect sequence will always occur (you will not be disconnected
until you receive an acknowledge of your disconnect or until the retry count is exceeded).
A second Disc command is required to force a local disconnect independent of the retry
counter.