Home » railML newsgroups » railML.infrastructure » Definition of Actuators (Point machines) for switches, crossings and derailers
Definition of Actuators (Point machines) for switches, crossings and derailers [message #3008] Thu, 02 June 2022 09:58 Go to next message
Georg Boasson is currently offline  Georg Boasson
Messages: 18
Registered: October 2020
Junior Member
The Interlocking elements <switchIL>, <derailerIL>, <movableCrossings> contains attributes to define the number of actuators:

• numberOfBladeSwitchActuators: number of switch actuators controlled from interlocking to throw the switch
• numberOfFrogSwitchActuators: number of switch actuators controlled from interlocking to throw the frog nose(s)

See railML3 Wiki for more details

We very much like the possibility to define position, name and maybe also other actuator-related data in the railML format. Since the actuator is both a physical and a functional element, implementation in both the Infrastructure- and Interlocking-schema must be considered.
Re: Definition of Actuators (Point machines) for switches, crossings and derailers [message #3017 is a reply to message #3008] Tue, 14 June 2022 11:01 Go to previous messageGo to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 447
Registered: January 2016
Senior Member
Dear Georg,

actuators for switches and switch frogs indeed have an infrastructure and interlocking dimension. The question is: how detailed shall the model of an actuator be? Apart from name and position, which information for an actuator do you want to have modelled?

As usual, any comment from the railML community is highly appreciated...

Best regards
Christian


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: Definition of Actuators (Point machines) for switches, crossings and derailers [message #3019 is a reply to message #3017] Tue, 14 June 2022 14:05 Go to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 88
Registered: March 2016
Member
Just as information:
In interlocking domain one can specify the number of actuators for
switch blades and for frog. This is just in relation to the power supply
of the signalBox which limits the number of concurrently activated
actuators (current limitation).

<rail3:switchIL numberOfBladeSwitchActuators="1"
numberOfFrogSwitchActuators="0" ..>

<rail3:powerSupplyIL numberOfSimultaneousSwitchingActuators="1" ..>

Any further details like model of actuator, mounting position etc. does
not matter in interlocking domain.

Dr.-Ing. Jörg von Lingen - Interlocking scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 351 87759 40; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
On 14.06.2022 11:01, Christian Rahmig wrote:
> Dear Georg,
>
> actuators for switches and switch frogs indeed have an
> infrastructure and interlocking dimension. The question is:
> how detailed shall the model of an actuator be? Apart from
> name and position, which information for an actuator do you
> want to have modelled?
>
> As usual, any comment from the railML community is highly
> appreciated...
>
> Best regards
> Christian
Previous Topic: [railML3] meaning and purpose of speedSection.isTemporary is unclear
Next Topic: Example of Level crossing with own TVD section
Goto Forum:
  


Current Time: Sat Jun 22 17:33:14 CEST 2024