Abus Packet Specification

Following Abus packets will be used for communication between the RBC/IL and Element Controllers (including EC/LINK):

Packet Type

Code Description
0 (reserved)
1 Element status request (poll)
2 EC status request (up time etc.)
3 Mode and movement authorization. Train position request *)
10 Element order and element status request
20 Configuration data

*) Only valid for EC/LINK (not used for v4)

Packet Content

In the following “H” designates high order 4bit and “L” low order 4bit

See enummeration for coding of values.

Type 1, Element status request

Request status of all configured elements.

To slave: <empty>

From slave:

Index Type Content Values
3 byte Number of configured elements 0: no elements configured
n+4 H byte Status of element 2n See Status
n+4 L Status of element 2n+1

n: 0..15

The element status is provided in the same order as the elements were configured in, ref. packet type 20.

Type 2, Request for EC status

Request status of EC

To slave: <empty>

From slave:

Index Type Content Values
3,4,5,6 unsigned long EC Uptime Index 6 is MSB
7 byte Number of elements configured 0: no elements configured
8 byte Max number of elements N_ELEMENT
9 byte Number of U-devices installed N_UDEVICE
10 byte Number of L-devices installed N_LDEVICE
11 byte Number of P-devices installed N_PDEVICE

Type 3, Mode and movement authorization. Train position request

Provide mode and movement authorization to specific train. Request train status and position report from same train.

To slave:

Index Type Content Values
3 byte Train ID
4 byte Authorized mode
5..9 byte[5] Balise ID
10,11 int Distance from balise to EOA, with sign Valid in FS and ATO only
12 byte Allowed speed

From slave:

Index Type Content Values
3 byte Report status 0: void, 1: valid
4 byte Train ID
5..9 byte Balise ID
10,11 int Distance with sign
12 byte Speed
13 byte Status Ref. WT1
14 byte rtoMode FIXME, not implemented in EC-link

Type 10, Element order and element status request

Order for one specific element and request for status of all elements.

To slave:

Index Type Content Values
3 byte Element index Index is referring to the order in which the elements were configured starting with index 0, ref. packet type 20
4 byte Element order See Orders

From slave: (same as for packet type 1)

Type 20, Add configuration data

Add an element configuration or clear existing configuration.

To slave:

Index Type Content Values
3 byte Configuration command 0: delete existing configuration, 1: add configuration
4 byte <element type> See Device configuration
5 byte <major device number>
6 byte <minor device number>

From slave:

Index Type Content Values
3 byte Acknowledge of configuration 0: Configuration accepted, 1: invalid major device number, 2: invalid minor device number, 10: element capacity exceeded, 11: unknown configuration command, 12: unknown element type

it/wintertrainv4/implementation/abuspacket.txt · Last modified: 2019/10/28 17:09 by jabe