TReX User Manual v2.14 Firmware
Custom Protocol
This protocol allows many existing protocols provided by other vendors to be supported by the
parsing of fields based on configuration (without new firmware being required).
The custom protocol takes as a starting point various default values that may or may not be
replaced depending on how the unit is configured:
- Preconfigured default cap code (*TX_CAP=1234567).
- Preconfigured default level or priority (*TX_LEVEL=0).
- Preconfigured default baud rate (*TX_BAUD=2400_25).
- Preconfigured default transport mode (*TX_MODE=POCSAG_A).
For each of these fields a command is set to specify the content (up to 9 fields)
*CUST_FIELD
*CUST_FIELD=F:S,L,“match”,I, T
Where:
F
is the field number (1-9 permitted)
:
is the colon character ‘:’
S
is the start index in message (from 0-255). This field rule will start looking at this
index in the incoming message (index is 0 based).
,
is the comma character ‘,’
L
is the length of the field to parse (0-255. If 0 is specified, then parsing will continue
until the first non printable character is found).
“match”
is any string that should be matched in the incoming message. This may or
may not be used as described below (not all field attribute types inspect this field)
I
is the case insensitive flag. ‘I’ means that the match string previously described is
case insensitive (“test” will match on incoming messages with “tESt” and “TEST”).
‘’ meaning that the match field is case sensitive.
T
is field attribute as described below (e.g. MATCH, CAP etc.).
Each field may have any of the following attributes (displayed in the command *LIST).
MATCH
- the field must exactly match the specified match string. Message is rejected
if not found.
© WTE Limited, 2018 – Christchurch New Zealand
Page 92 of 158
