Home » railML newsgroups » railML.infrastructure » Multiple train protection systems
Multiple train protection systems [message #237] Mon, 19 April 2010 15:43 Go to next message
Susanne Wunsch railML is currently offline  Susanne Wunsch railML
Messages: 0
Registered: January 2020
There are some lines equipped with PZB and additional systems like LZB
or even ETCS.

How do you define multiple active train protection systems on a track?

<!-- PZB -->
<rail:trainProtectionChange id="tpc0" pos="0"
monitoring="intermittent" medium="inductive"/>
<!-- LZB -->
<rail:trainProtectionChange id="tpc1" pos="500"
monitoring="continuous" medium="cable"/>

Normally, the new *Change entry stops the previous similar entry.
That means, from pos=500 upwards there is _only_ LZB, no PZB.

How do you define this issue?

Any comments would be appreciated.

Kind regards,
Susanne

--
Susanne Wunsch
Schema Coordinator: railML.common
Re: Multiple train protection systems [message #2096 is a reply to message #237] Mon, 14 January 2019 16:23 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear all,

more than eight years ago we took notice of the problem that we cannot
model overlapping / multiple train protection systems along a track:

Am 19.04.2010 um 15:43 schrieb Susanne Wunsch:
> [...]
> How do you define multiple active train protection systems on a track?
>
> <!-- PZB -->
> <rail:trainProtectionChange id="tpc0" pos="0"
> monitoring="intermittent" medium="inductive"/>
> <!-- LZB -->
> <rail:trainProtectionChange id="tpc1" pos="500"
> monitoring="continuous" medium="cable"/>
>
> Normally, the new *Change entry stops the previous similar entry.
> That means, from pos=500 upwards there is _only_ LZB, no PZB.
>
> How do you define this issue?

With upcoming railML 3.x, we finally can solve this problem: Each
<trainProtectionElement> instance has its own (linear) location and
these locations may overlap. So, if you want to define a track being
equipped with PZB and LZB (see example above), just define two
<trainProtectionElement> instances with overlapping locations.

Consequently, Trac ticket #80 [1] can finally be closed.

[1] https://trac.railml.org/ticket/80

Best regards
Christian

--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: Redefine the use of signal@ocpStationRef (railML2.4)
Next Topic: Use the concept of layer for splitting the data
Goto Forum:
  


Current Time: Thu Mar 28 22:32:35 CET 2024