Home » railML newsgroups » railml.interlocking » [railml3] Signal types and functions (See IS forum)
Re: [railml3] Signal types and functions [message #2135 is a reply to message #2132] Sat, 09 February 2019 09:32 Go to previous messageGo to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 87
Registered: March 2016
Member
Dear all,

we (IS/IL coordinators) have discussed the differences of <signalIS>@type and <signalIL>@signalFunction (may be renamed
to <signalIL>@function):

<signalIS>@type is about the physical types of objects one will call "signal"

<signalIL>@signalFunction is about the function of the signal as seen from the interlocking
"main" could be seen as a duplication but its meaning is more anything else but the specific uses - "The main signal is
a normal signal for train traffic protection which is neither used as block, entry, exit nor intermediate signal."

<signalIL>@isVirtual is especially considering ETCS systems were the interlocking in its data still has signals which
are switched to particular aspects. But on the outside there are only marker boards to identify the position of these
interlocking only signals. In that sense they are physical outside but virtual for the interlocking.
Whereas <signalIS>/<signalConstruction>@type="virtual" really means no physical object outside.

<signalIS>@switchable is a real addition to <signalConstruction>@type because there are signals of type "semaphore"
which may be switchable or not, e.g. electrification signals like "main switch off". Of course, with "light" signals one
can assume they are always switchable.


Regards,
Jörg von Lingen - Interlocking Coordinator
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Definition of Emergency Stop Area for railML 3.3
Next Topic: Reuse IL:SignalBox for Object controllers
Goto Forum:
  


Current Time: Wed Jun 19 16:31:35 CEST 2024