User's Manual Part 6

  #*2') 
  
<   *   6% 3
Error Solicited response to
a transaction error.
This advises the DTE
that the RU has
detected an error
condition and cannot
proceed with the
current transaction.
Unsolicited
response to a system
error.
In some cases, an
exception condition
in the RU may cause
an ‘Error’ message to
be sent to the DTE
independently of
any control transac-
tions. A prompt or
‘Ready’ will be
issued after an
‘Error’ occurs, to
indicate the RU's
availability to accept
further commands.
e
[ETYPE] Error type. A single
character represent-
ing the error cate-
gory.
0 = transaction error.
This indicates some
problem with com-
munications. All
such errors result in
the transaction
being terminated,
without the current
command being
executed.
Transition error numbers
(
[ETYPE]
= 0):
1 0x01 = unsupported
command error
This may arise when
the DTE expects a later
version of RU than is
attached, and attempts
to use a command
which is not recognised
by the RU.
2 0x02 = checksum error
indicates that the check-
sum calculated by the
RU did not match the
one received in the com-
mand packet.
3 0x03 = parameter error
This encompasses val-
ues out of range, or
missing fields.
4 0x10 = communication
failure
This encompasses all
low level mechanisms,
i.e. framing error, over-
run error, parity error
etc.
5 0x20 = invalid channel
number
This may arise when
the DTE issues a ‘Go To
Channel’ command
with a
[CHANNEL
NUMBER]
exceeding
the maximum allowable
number.
[ENUM] Error number. A
character string rep-
resenting a decimal
number in the
range of 00 to 99,
which can identify
the specific error
condition.
For
[ETYPE]
= 0,
01 = unsupported
command
02 = checksum error
03 = parameter error
10 = communica-
tion failure
20 = invalid channel
number
Command Description
Message
Comments
[IDENT]
[PARAMETERS]