[eugenR]

I have tested the function now in all cases:
If I use the SignalSubObj "NAME", the function produce a Warning in the Logfile, and the function has as Result "1" also if the HEAD is Missing!

If I use the Number of SignalSubObj ( x , the function is working correct.
I will ask Carlo, for modifying the manual.

Regards
EugenR

[ebnertra000]

Ohhh, so that's why it doesn't work. I've been trying to do this to SIGNAL_HEAD-type objects, but they have to be DECOR-type

[eugenR]

ebnertra000, on 18 May 2019 - 02:41 PM, said:

Ohhh, so that's why it doesn't work. I've been trying to do this to SIGNAL_HEAD-type objects, but they have to be DECOR-type

I think this is not correct,
The function is working with all kind of SignalSubObj, also with

SigSubType ( SIGNAL_HEAD ) 

given for this signal in the sigcfg.dat.
But you have to use the SignalSubObj Number

SignalSubObj ( 2

insted of Name, as written in the actual Manual

For having more then the four available SIGFEAT_USER flags, you have to use additional optional SignalsubObj with

SigSubType ( DECOR )

So this function can test if this optional SignalSubType is activated or not.


Regards
EugenR

[ebnertra000]

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

Attached File(s)

•  Sig_Test.zip (4.05MB)
  Number of downloads: 604

[eugenR]

ebnertra000, 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

You can throw a switch, so you can't use activity-mode. Which mode are you using? Manual or explore ?

regards
Eugen

[eugenR]

ebnertra000, 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

[ebnertra000]

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

[eugenR]

ebnertra000, 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

[ebnertra000]

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