| Re: SpeedChange : Protection system reference [message #402 is a reply to message #399] |
Wed, 24 October 2012 16:30   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Dear Christian, Dirk, Pierre and others,
Christian Rahmig <coord(at)infrastructurerailmlorg> writes:
>> This reference from a <speedChange> to a <trainProtectionElement> is a
>> useful innovation, which may be implemented with railML 2.2, because the
>> reference attribute will be optional. However, is it really the
>> <speedChange> that needs to refer to the <trainProtectionElement> or is
>> it the signal, which is connected to the magnet or the Belgian crocodile?
>
> I added the request for an (optional) reference from a <signal> to a
> <trainProtectionElement> as a comment to trac ticket [1].
>
> [1] https://trac.assembla.com/railML/ticket/173
That's only one part of the idea.
There are also speed changes that are ensured by train protection
elements, such as PZB-magnets. [1]
Sure, not all speed changes have such restrictions, it should be an
optional addition to the current <speedChange> element.
Moreover there should be more than one such a reference to different
<trainProtectionElement>s. The Germans use up to three magnets for one
speed aspect. [1]
[1] https://de.wikipedia.org/wiki/Geschwindigkeitspr%C3%BCfabsch nitt
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
