Table of Contents
RBC configuration data
The RBC configuration data will include all types of static data needed for the RBC (including the interlocking functionality) to do its job.
In order to simplify installation and maintenance of static train related data, most of these data will be stored as part of the RBC configuration data.
Refer to Signalling Layout / PT1 and engineering tools / DMT. RBC application data can be generated by hand, but by using the engineering tools consistant data can be generated in a shorter time.
Topology and Element data
Topology, Element data and HMI layout are commonly known as “PT2 data”.
Static topology data, element configuration and HMI data will be stored in a directional graph, covering both driving directions. Both real track side element like points, signals and balises and logical elements like triggers for level crossing activation will be represented in the graph. Real elements will be described by their physical extend (i.e. length), while logical elements may have an extend related to the logical function.
Each element will be designated by a name, an element type and various attributes. The name can be any text excluding whitespace. Element type and attributes are defined in the following sections.
All nodes holds information of each of their neighbor(s):
- Name of neighbor (text)
- Distance from element center to border to neighbor (cm)
Define/introduce direction up.
Distances
Each element is characterized by its track-related extend or “length”. The extend is, depending on the element type, defined as one or more distances from the center of the element to the border of the element. The location of this center depends on the element type and is listed in the next section.
The total distance between the centers of two neighbor elements can hence be calculated as the sum of:
- the distance from the center of the first element to the border between the two elements and
- the distance from this border to the center of the second element
Note, that all distances are relative - no absolute distance is specified. All distances are in centimeter and without sign. A distance of 0 is valid, indicating, that the border is coincident with the element center.
HMI data
HMI data provides screen coordinates and dimensions for the layout of the graphical user interface. These data are used only for layout of the HMI screen.
Node types
For this graph, following node types will be used. In order to identify which nominal direction e.g. a signal is applicable for, different node types will be used for each direction. All descriptions are for the track seen in direction up.
| Code | Node type | Node center | Remarks |
|---|---|---|---|
| BL | Balise | Balise | Balises are direction independent. This is due to the OBU reading the nominal direction by means of polarity of traction power, refer to Train positioning and direction of movement |
| PF | Point, facing in direction up | Tip | The distance from tip to border at the two branches would normally include the fouling point |
| PT | Point, trailing in direction up | Tip | The distance from tip to border at the two branches would normally include the fouling point |
| PHTU | Trigger | Trigger location | Trigger for activation of extended point holding for one point approached in direction up |
| PHTD | Trigger | Trigger location | Trigger for activation of extended point holding for one point approached in direction down |
| GT | Gate | Gate | |
| SU | Signal, applicable for direction up | Signal | |
| SD | Signal, applicable for direction down | Signal | |
| LX | Level Crossing | Road center | Level crossings are operated in the same way for both directions. |
| TG | Trigger | Trigger location | Trigger for activation and de-activation of one level crossing |
| BSE | Buffer stop at end of track | Buffer stop | |
| BSB | Buffer stop at begin of track | Buffer stop |
Common data
All nodes will include following data:
- Node type (see above)
- Node name (text)
Elements without a name (i.e. empty string) will be silently ignored by the system. This can be used for keeping templates in the data files.
Node specific data
In addition to the common data, each node holds data specific for the element, it is representing. Nodes representing elements, which are connected to an Element Controller, includes an interface specification providing one or more EC addresses, interface type and device numbers. Refer to EC configuration
Information about a neighbor includes:
- Name of neighbor
- Distance from element center to border of element in direction of this neighbor
Following specific data will be stored per node type:
Balise
- Balise ID (5 byte)
- Neighbor, direction up
- Neighbor, direction down
PF, Point, facing in direction up
- EC specification (address, interface type, major device, minor device)
- Supervision configuration
- Neighbor, direction up
- Right branch
- Left branch
- Neighbor (tip), direction down
- HMI orientation and coordinates
Supervision configuration is specified by:
| Code | Position supervision | Description | Physical point machine |
|---|---|---|---|
| U | Unsupervised | Point position is permanently detected as Unsupervised. Point can be thrown, but remains unsupervised. | Not controlled |
| S | Supervised in requested position | The point and its supervision is Simulated. Position is indicated as supervised in right or left as requested by latest throwing command. Point can be thrown. | Not controlled |
| P | Supervised in requested position | Position is indicated as supervised in right or left as reported by the connected Element Controller. Element Controller reports position supervision according to latest throwing command. Point can be thrown. | Controlled |
| F | Supervised by point machine | Point position is supervised by the connected point machine via position Feedback. Point can be thrown. | Controlled |
| CR | Supervised Right | Point is mechanically Clamped. Supervision is simulated in position Right. Point cannot be thrown. | Not controlled |
| CL | Supervised Left | Point is mechanically Clamped. Supervision is simulated in position Left. Point cannot be thrown. | Not controlled |
Orientation of HMI symbol is specified by:
| Code | Orientation of symbol |
|---|---|
| fr | Facing, diverting branch is right |
| fl | Facing, diverting branch is left |
| tr | Trailing, diverting branch is right |
| tl | Trailing, diverting branch is left |
PT, Point, trailing in direction up
- EC specification (address, interface type, major device, minor device)
- Supervision configuration
- Neighbor (tip), direction up
- Neighbor, direction down
- Right branch
- Left branch
- HMI orientation and coordinates
SU, SD, Signal (both directions)
- Signal type
- EP distance, if signal is EP of route, length of optional safety distance in rear of signal
- Optional Route indicator type
- Route information, if signal is EP
- EC specification of signal (address, interface type, major device)
- EC specification of optional route indicator (address, interface type, major device)
- Neighbor, direction up
- Neighbor, direction down
- HMI coordinates
Signal type is indicating the class of signal and the possible aspects:
| Code | Signal type | Possible signal aspects |
|---|---|---|
| MB | Marker Board | n/a (aspect provided at the DMI) |
| SE | Semaphore signal | Stop, Proceed |
| MS2 | Main Signal, 2 aspects | Stop, Proceed |
| MS3 | Main Signal, 3 aspects | Stop, Proceed, Proceed-Proceed |
Route indicator type is indicating the class of indicator:
| Code | Route indicator type |
|---|---|
| NRI | (no indicator) |
| RI2 | Route indicator, 2 segments |
| RI3 | Route indicator, 3 segments |
Route information is indicating which symbol to be shown for routes ending at this EP:
| Code | Route information | Remark |
|---|---|---|
| 0 | No Route information is defined for this signal when locked as EP | |
| <symbol> | Information <symbol> is shown when signal is EP | <symbol> is the direct order to the EC handling the route indicators |
BSE, Buffer stop, up
- Route information, if Buffer Stop is EP
- Neighbor, direction down
- HMI coordinates and size
| Code | Route information | Remark |
|---|---|---|
| 0 | No Route information is defined for this signal when locked as EP | |
| <symbol> | Information <symbol> is shown when signal is EP | <symbol> is the direct order to the EC handling the route indicators |
BSB, Buffer stop, down
- Route information, if Buffer Stop is EP
- Neighbor, direction up
- HMI coordinates and size
| Code | Route information | Remark |
|---|---|---|
| 0 | No Route information is defined for this signal when locked as EP | |
| <symbol> | Information <symbol> is shown when signal is EP | <symbol> is the direct order to the EC handling the route indicators |
LX, Level crossing
- EC configuration, road signal
- EC configuration, barrier drive
- Neighbor, direction up
- Neighbor, direction down
- HMI coordinates
Trigger for LX
- Name of LX to be activated
- Activation direction
- Neighbor, direction up
- Neighbor, direction down
PHTU, Trigger for extended point holding, up
- Name of point to be thrown to expected lie
- Neighbor, direction up
- Neighbor, direction down
PHTD, Trigger for extended point holding, down
- Name of point to be thrown to expected lie
- Neighbor, direction up
- Neighbor, direction down
Train data
Refer to Train configuration data
