search

openrails / test-launchpad-bugs

TEST repository for Launchpad bug migration exploration
0 stars 0 forks source link

[BUG 1598380] behaviour of ROUTE_SET() and BLOCK_STATE() #1747

Open twpol opened 8 years ago

twpol commented 8 years ago

Imported from https://bugs.launchpad.net/bugs/1598380

Property Value
Reported by Rippstein (ch-signale)
Date reported Sat, 02 Jul 2016 08:48:38 GMT

By testing a signal-script Type NORMAL which not use the Function ENABLED, I have found the following Problems in OpenRails:

For SignalType NORMAL, if the Train pass the Signal, there is a different behaviour of the functions: ROUTE_SET() BLOCK_STATE() between MSTS and OpenRails!

Function OpenRails MSTS ROUTE_SET() TRUE to FALSE stay TRUE BLOCK_STATE() CLEAR to JN_OBSTRUCTED CLEAR to OCCUPIED

For Signals not Type NORMAL the behaviour in MSTS and OpenRails is identical and similar to the behaviour of MSTS for signals Type NORMAL. Can you please have a look on the code for these two functions in OpenRails. I think this different behaviour has not make a problem until yet, because usually Signals Type NORMAL are closed by !ENABLED.

twpol commented 8 years ago

Imported from https://bugs.launchpad.net/or/+bug/1598380/comments/1

Property Value
Posted by Rippstein (ch-signale)
Date posted Sat, 02 Jul 2016 09:12:32 GMT

see also elvastower: http://www.elvastower.com/forums/index.php?/topic/28752-switch-protecting-signal-on-an-unsignalled-route/