Elvas Tower: HASHEAD signal function - Elvas Tower

Jump to content

  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

HASHEAD signal function How, if at all, can it be used? Rate Topic: -----

#16 User is offline   eugenR 

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

Posted 20 May 2019 - 06:14 AM

View Postebnertra000, on 19 May 2019 - 10:05 AM, said:

Still I can't get what I'm trying to do to work. So I made a small test route so you can see what I'm trying to do. In the test route, the signal immediately after the start point should show Slow Clear (Red-Green) if you throw the switch, but instead it shows Stop. The two-headed signal on the siding track should show Restricting (Red-Yellow) if you approach it, but it too won't clear

I think the Problem is, that the signalheads GT_H1A_GYR_SL and GT_H2A_GYR_SL are in the sigcfg.dat not designed to link to the Switch-path, so both HEADS are working in the same common track.

See sigcfg.dat in usa2-Route (Marias-Pass) US2BSignal3.s
SigSubJnLinkIf ( 2 1 2 )
red : total number of optional signalSubObj's with optional JN_Link
green: SignalSubObj-Number

EugenR

#17 User is offline   ebnertra000 

  • Superintendant
  • Group: Posts: Elite Member
  • Posts: 1,259
  • Joined: 27-February 17
  • Gender:Male
  • Location:East-Central Minnesota
  • Simulator:OR/TSRE
  • Country:

Posted 20 May 2019 - 07:44 AM

I do my testing in Explore Mode for the most part. The heads themselves aren't junction-linked - just beyond all these signals is a second 'control' signal, which has junction-linked routes. All the references in the sigscr.dat to rt_state are the respective signal types checking the control signal. This system is considerably more flexible than the US2 system

#18 User is offline   eugenR 

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

Posted 21 May 2019 - 12:18 AM

View Postebnertra000, on 20 May 2019 - 07:44 AM, said:

I do my testing in Explore Mode for the most part. The heads themselves aren't junction-linked - just beyond all these signals is a second 'control' signal, which has junction-linked routes. All the references in the sigscr.dat to rt_state are the respective signal types checking the control signal. This system is considerably more flexible than the US2 system


Hi I understand very well what you would like to do whith this signalsystem, but
The Signal before the standing engine has activated 2 Signalheads, both of the Type NORMAL.
So the Signallogic of OR will calculate one after the other. It will overwrite the result of the first calculation and present the result the second calculation as the resulting state.
As example, if the switch is throw, OR calculate as second head the head (STOP) for strate, OR will present STOP for this direction.

There are two possibility, to avoid this:
linking this heads Type NORMAL, or
Use an other SignalType for this heads and define one single Signalhead Type NORMAL where the logic depend from all the other HEADs

I hope you can find a good solution for your Signalsystem.

regards
EugenR

#19 User is offline   ebnertra000 

  • Superintendant
  • Group: Posts: Elite Member
  • Posts: 1,259
  • Joined: 27-February 17
  • Gender:Male
  • Location:East-Central Minnesota
  • Simulator:OR/TSRE
  • Country:

Posted 21 May 2019 - 04:22 AM

I think I'll live with a couple minor inconsistencies, since only one or two aspects have this problem, and only two systems I have in the works have this problem

  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

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