Home » railML newsgroups » railml.interlocking » [railml3] Signal types and functions (See IS forum)
[railml3] Signal types and functions [message #2132] Fri, 08 February 2019 20:41 Go to next message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 54
Registered: February 2017
Member
This thread is also IL relevant

Best regards,
Thomas Nygreen
Railway capacity engineer
Jernbanedirektoratet
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 next message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 12
Registered: March 2016
Junior 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
Re: [railml3] Signal types and functions [message #2143 is a reply to message #2135] Mon, 11 February 2019 18:17 Go to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 54
Registered: February 2017
Member
Dear Jörg,

Jörg von Lingen wrote on Sat, 09 February 2019 09:32

<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."

Even with this kind of definition, "main" or "distant" still describes another type of property than "exit" or "entry". Hence, there should be two different attributes.

Quote:

<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.

OK. I assume that there may also be other cases where the signal model in the IL differs from the actual (or non-existing) signal outside, in which case it would also then be considered virtual?


Best regards,
Thomas Nygreen
Railway capacity engineer
Jernbanedirektoratet
Previous Topic: How to name a "non-fixed" balise?
Goto Forum:
  


Current Time: Sat Feb 16 15:16:52 CET 2019