Elvas Tower: New signalling functions - Elvas Tower

Jump to content

Posting Rules

All new threads will be started by members of the Open Rails team, Staff, and/or Admins. Existing threads started in other forums may get moved here when it makes sense to do so.

Once a thread is started any member may post replies to it.
  • 8 Pages +
  • « First
  • 2
  • 3
  • 4
  • 5
  • 6
  • Last »
  • You cannot start a new topic
  • You cannot reply to this topic

New signalling functions OR specific signalling functions added in version 2266 Rate Topic: -----

#31 User is offline   roeter 

  • Vice President
  • Group: Status: Elite Member
  • Posts: 2,424
  • Joined: 25-October 11
  • Gender:Male
  • Country:

Posted 01 June 2015 - 05:33 AM

View PostVicenteIR, on 25 April 2015 - 07:45 AM, said:

In OR it does not work due to the fact that the signals behave differently unlike MSTS (functions enabled() and opp_sig...()).


There is a slight difference in the use of 'enabled' between MSTS and OR.
In OR, if a signal has no 'fixed path' (that is, there is at least one switch or cross-over between this and the next NORMAL signal), it will not clear when not enabled by a train, even if the state of 'enabled' is not tested.
That is because as long as no path is cleared over that switch by a train, the position of the switch is 'unknown' and a signal can not be cleared over a switch in that state.

I do not think this affects your situation as in your case the signals will be cleared by a train. Perhaps the difference in SignalNumClearAhead is affecting your situation - you might want to have a look at that, and check that the value for SNCA for the preceding main signal is set at a high enough value to clear the path as far as required.

The function opp_sig has been tested and shown to be working correctly.

Regards,
Rob Roeterdink

#32 User is offline   raster 

  • Apprentice
  • Group: Status: Inactive
  • Posts: 9
  • Joined: 26-August 13
  • Simulator:MSTS
  • Country:

Posted 07 June 2015 - 08:27 AM

I meant something else, not always possible to use your method. I am writing a script, that for proper operation needs one variable which will be remembered, and its value will not be associated with a signal state. I think not only for me that such a thing was helpful.
These all my ideas for signaling, they are ideas that would allow the creation of a well-functioning signaling system on Polish railways, especially maneuvering signals that are handled manually, not automatically, so it's hard to automate. The best solution would be the use of special points in the patch, which would began or ended with a new type of patch, and his type could be read from a script signal-this would introduce some element of manual operation and would work best. I described it once already.
Are any of these possible?
Regards:)

#33 User is offline   VicenteIR 

  • Fireman
  • Group: Status: Active Member
  • Posts: 149
  • Joined: 24-April 15
  • Gender:Male
  • Location:Dimona, Israel
  • Simulator:Open Rails
  • Country:

Posted 28 January 2017 - 01:47 PM

ApproachControlSettings (PositionM ( 50 )) does not work in x3725. A signal is at danger, but when AI train passes previous signal, it opens regardless of what value of "position" is set

#34 User is offline   eugenR 

  • Conductor
  • Group: Status: Contributing Member
  • Posts: 472
  • Joined: 15-April 13
  • Gender:Male
  • Simulator:MSTS
  • Country:

Posted 28 January 2017 - 02:44 PM

View PostVicenteIR, on 28 January 2017 - 01:47 PM, said:

ApproachControlSettings (PositionM ( 50 )) does not work in x3725. A signal is at danger, but when AI train passes previous signal, it opens regardless of what value of "position" is set

I have tried this morning with X3757, it was o.k.
You need also in the sigscr.dat something like:
if (!enabled || block_state() !=# BLOCK_CLEAR || !APPROACH_CONTROL_POSITION(Approach_Control_Req_Position) )
{
state = SIGASP_STOP;
draw_state = 0;
}
else

#35 User is offline   VicenteIR 

  • Fireman
  • Group: Status: Active Member
  • Posts: 149
  • Joined: 24-April 15
  • Gender:Male
  • Location:Dimona, Israel
  • Simulator:Open Rails
  • Country:

Posted 28 January 2017 - 03:57 PM

It is work at another station. Thank you

#36 User is offline   eugenR 

  • Conductor
  • Group: Status: Contributing Member
  • Posts: 472
  • Joined: 15-April 13
  • Gender:Male
  • Simulator:MSTS
  • Country:

Posted 28 January 2017 - 11:57 PM

View PostVicenteIR, on 28 January 2017 - 03:57 PM, said:

It is work at another station. Thank you

The distance between both signals has to be greater the controlled-Distance (here 50m)!
If the first signal is standing in the controlled-Distance the second signal can switch only to clear after the train was closing the first signal.

Do you have a special track-situation between the two signals, if so please show a printscreen from the trackviewer for this situation.

regards
EugenR

#37 User is offline   VicenteIR 

  • Fireman
  • Group: Status: Active Member
  • Posts: 149
  • Joined: 24-April 15
  • Gender:Male
  • Location:Dimona, Israel
  • Simulator:Open Rails
  • Country:

Posted 29 January 2017 - 12:23 PM

View PosteugenR, on 28 January 2017 - 11:57 PM, said:

Do you have a special track-situation between the two signals, if so please show a printscreen from the trackviewer for this situation.

It is not a special track situation in this case. I think the problem was the starting point of the AI path (outside the station, and the signal has aт approach control is an output signal). The SNCA value is too large on the Entrance signal. Because of all this, at the next station it worked.
I tested already, and in my case, it did not help me. However, the function itself is working correctly, thank you

#38 User is offline   vitro 

  • Apprentice
  • Group: Status: New Hire
  • Posts: 10
  • Joined: 09-December 14
  • Simulator:Open Rails
  • Country:

Posted 28 May 2017 - 11:17 AM

Hello everyone. When I was trying to implement some Moscow Metro signaling features, it becomes a problem. I can't change draw states of signal with approach_control_* functions when signal is not enabled (have a waiting point before it). So I think it will be nice solution to implement this ability. Thanks.

#39 User is offline   roeter 

  • Vice President
  • Group: Status: Elite Member
  • Posts: 2,424
  • Joined: 25-October 11
  • Gender:Male
  • Country:

Posted 30 May 2017 - 12:12 PM

There is no interaction between waiting points and signals. There are various types of waiting points and do not know how exactly this affects the rest of the train's path. But if a signal is not enabled it means - to that signal - there is no train approaching that signal, and so it is not possible to clear the signal based on the approach control condition (the condition is checked by the signal, not by the train).
The signal should clear as soon as the waiting point condition is lifted.
But - why do you want a signal to clear if you're going to stop that train on a waiting point anyway? That makes no sense.

Regards,
Rob Roeterdink

#40 User is offline   vitro 

  • Apprentice
  • Group: Status: New Hire
  • Posts: 10
  • Joined: 09-December 14
  • Simulator:Open Rails
  • Country:

Posted 07 June 2017 - 11:36 AM

I don't want use an approach control for clearing disabled signal. I need to change draw_state of this signal with the same aspect.

In my case there is a signal which shows "Yellow and Red" until the train arrived to the station. Once the train stops, this signal becomes "Red" only. Then after 20 secs signal is cleared. Here's the real video: https://www.youtube....XmqTZ7-VI&t=41s


  • 8 Pages +
  • « First
  • 2
  • 3
  • 4
  • 5
  • 6
  • Last »
  • You cannot start a new topic
  • You cannot reply to this topic

2 User(s) are reading this topic
0 members, 2 guests, 0 anonymous users