Chapter 1 TL1 Overview
Responses
16 TimeProvider TL1 Reference Guide 097-58001-01 Revision E – September 2006
Position-Defined – In a position-defined payload block, the parameters that
make up the block are implied by their position within the block. The individual
parameters are separated by the comma character ( , ). If the value of a given
parameter is null, its position within the block still must be maintained by using
adjacent commas ( ,, ). Refer to Copy Memory (CPY-MEM), on page 36 for an
example of a command that uses a position-defined payload block.
Name-Defined – In a name-defined payload block, the parameters that make up
the block take on the form <keyword>=<value>. The <keyword> identifies the
parameter, and <value> is that parameter’s value. Keywords are not
case-sensitive. Refer to Edit Equipment (ED-EQPT), on page 45 for an example
of a command that uses a name-defined payload block.
Responses
When the TimeProvider receives and processes a command, it returns one of the
following types of responses:
Normal Response
Error Response
In-Process Response
The following paragraphs explain these response types.
Normal Response
The TimeProvider sends a Normal response when it receives and can properly
process a TL1 command. The format of a Normal response is as follows. Note that
M and COMPLD identify the response as a Normal response:
<cr><lf><lf>
sid date time<cr><lf>
M ctag COMPLD<cr><lf>
textblk<cr><lf>
textblk<cr><lf>
.
.
LG_textblk<cr><lf>
;
Table 1-1 explains each field that is contained in the Normal response.
Note: The textblk and LG_textblk fields are only returned with the
Normal response when the command requires such a message be
returned.
To Next Page
Loading...
Need help?
General
