Home » railML newsgroups » railML.infrastructure » railML 2.3 infrastructure extension proposal switch / crossing (railML 2.3 infrastructure extension proposal switch / crossing)
Re: railML 2.3 infrastructure extension proposal switch / crossing [message #1471 is a reply to message #1459] Mon, 02 January 2017 17:30 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Torben,

Am 20.12.2016 um 18:31 schrieb Torben Brand:
> [...]
> switch &crossing
> We need to define which controller controls a switch or
> crossing, and how. The elements <crossing> and <switch> are extended
> with the
> new attribute @NO:levelOfControll with the preset values:
> "controlled","supervised" or "unsupervised"

This attribute is misleading as in the end all switches and crossings
are somehow controlled (even if it is manually controlled). Can you
please clarify this requirement by providing some more information about
the use case behind?

> The elements <crossing> and <switch> are extended with the
> new attributes @controllerRef and @NO:typicalThrowTime
> [datatype: time in seconds]

These two suggested parameters make sense to me. In fact, all
infrastructure elements that can be incorporated in an interlocking
controlling, may have a reference to a controller. Alternatively (from
an interlocking point of view), the controller/interlocking shall
reference all the infrastructure elements that it controls. We should
decide for one direction of referencing, but not implement both.

> The last attribute is needed as we need to define the
> average time a switch uses from the command is given in the
> interlocking to turn the switch and its points are indicated
> locked in the interlocking in the new position.

Understood. However, instead of a "typical" throw time, which may vary a
lot, I prefer defining a "minimumThrowTime" and/or a "maximumThrowTime".

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
 
Read Message
Read Message
Read Message
Previous Topic: railml 2.3 Export only updated data from a data source
Next Topic: railML alpha version 3.0.5 available / railML 2.4 announced
Goto Forum:
  


Current Time: Mon Apr 29 06:27:11 CEST 2024