60 CCR TM8100/TM8200 Computer-Controlled Data Interface (CCDI) Protocol Manual
© Tait Electronics Limited April 2007
Effect
The implementation exits the validation as soon as an error has been struck
- it will not check the parameters if the command does not pass the
checksum test.
2.7.2 Validation Checksum Error
If the input string does not have the correct checksum, a checksum error is
immediately reported and no further checks are done.
2.7.3 Invalid Validation Command
If the input string passes the checksum test but the identity contained is not
a recognised CCR command, an invalid command is reported.
2.7.4 Validation Parameter Error
If the input string passes the general message format but not the command
specific tests, a parameter error is sent. For details on validation rules see the
specific commands.
■ data length check
■ range check on message data
■ correct sequence of commands
2.7.5 Radio Busy Message
If the input string passes both the general and command specific validation
criteria, it is processed only if the following conditions are true:
■ Radio is not in transmitting state
■ Radio is not busy processing the last sent command
The radio rejects the commands and returns the busy error code in these
instances.
2.7.6 Command Not Accepted Message
Some commands trigger sequence errors if they are sent when the radio
cannot process the command, for example:
■ Radio is attempting to use a selcall command when there is no selcall
configuration defined.
This error is, for instance, sent if a selcall command is received, but the CCR
channel is not activated with a network using selcall signalling.
To Next Page
Loading...
Need help?
General
