Specifications

3U Traffic Outstation Handbook
667/HB/26568/000 Page 188 Issue 15
1. Bus Detect message entry, example:
25-APR-99 10:41:10 BID:6 B:6734256 R:560 PI:2 PO:2 O:1 M:90
BID: = Beacon ID (HEX, 1 - FF)
B: = Bus Radio ID (DECIMAL, 0 - 9999999)
R: = Bus Logical Route ID (DECIMAL, 0 - 999)
PI: = Priority Input Level in message (DECIMAL, 0 - 9)
PO: = Priority Output (DECIMAL, 0 - 7)
O: = Output Action (DECIMAL) :
0 = no output action defined
1 - 30 = Output Action List entry number
229 - 255 = rejection cause - beacon ID, route etc, see table overleaf
M: = Message count (DECIMAL, 0 - 99) - a separate count for each beacon
2. SIETAG Vehicle Detect message entry, example:
25-APR-99 10:51:10 R:6 W S:F C:2 A:0 T:3 I:4 OP:12 R:1 V:2C3 O:255 M:12
R: = Loop ID / Reader ID (HEX, 1-3F)
The first character (if present) identifies the number of the loop (0-3)
connected to a SIETAG reader on which the vehicle was detected.
If not present the loop number is assumed to be 0.
W: = Tag type / Tag data format (ASCII)
‘C’ = contact monitor or conditioning input.
When vehicle detection received from a V3.0 SIETAG reader :
‘W’ = read/write
‘S’ = Siemens encrypted
‘M’ = multi-page
‘R’ = read only
When vehicle detection received from a V4.0 (or later) SIETAG reader :
‘S’ = Siemens encrypted
‘O’ = SIEMENS open
‘T’ = TIRIS Unknown
S: = Supplier code (HEX, 1 - FF)
C: = Customer Number (HEX, 1 - FFF)
A: = Area (HEX, 1 - F)
T: = Vehicle Type (HEX, 1 - F)
I: = Activation ID (HEX, 1 - F)
OP: = Operator (HEX, 1 - FF)
R: = Route Number (HEX, 1 - FFF) - not used by standard Tag
V: = Vehicle Number (HEX, 1 - FFFFFF)
O: = Output Action (DECIMAL) :
0 = no output action defined
1 - 30 = Output Action List entry number
229 - 255 = rejection cause - customer, zone etc, see table overleaf
M: = Message Count (DECIMAL, 0 - 99) - a separate count for each reader