Help with Shunting Sensor

[Qwerty Bob]

I understand the Shunting Sensor is, essentially, an if-statement; It checks to see if the train has a locomotive on the correct end, then applies some shunting commands.

What I don't understand is how to handle the case where the train does not match the condition… my trains just stop in their tracks… the tutorial doesn't cover this…

Wanted behaviour based on train-layout (in tutorial):

  (-) (-) (-) (>)     Sent to a branch to flip the orientation
  (>) (-) (-) (-)     Should continue as-is...  (I can't get this to work!)

My trains which do not match simply stop at the signal.

If this cannot be done, then having a condition on sensor is pointless...

https://steamcommunity.com/sharedfiles/filedetails/?id=3169058099

[Arnstein86]

You have to have another sensor for that signal clearing the route if the shunting sensor trigger doesn't apply, I think.
I'm not 100% sure but I think the shunting sensor should take presedence over f.ex a routing sensor or relay sensor.
Or you could try putting the shunting sensor 1 spot before the other sensor as trains in shunting mode negates sensors.

[Randych]

As I understand, basic shanty sensors are agnostic and just blindly repeat what you told them to do.
If we look at "composition" part of shanty sensor setting, it says you need loco coupling which is whole another thing.
Here's example of stabling sensor I use (I don't need shanty sensors themselves it seems?) https://imgur.com/a/y8jINCl
so it has tracks in front of stations where I get 3-4 regionals, it parks them then stations back and reverses (since roundabout equals in proper position for reverse and then full speed).
Hope this helps.
(edit: not so much, it doesn't work at all lol)

[Qwerty Bob]

Originally posted by Arnstein86:

You have to have another sensor for that signal clearing the route if the shunting sensor trigger doesn't apply, I think.
I'm not 100% sure but I think the shunting sensor should take presedence over f.ex a routing sensor or relay sensor.
Or you could try putting the shunting sensor 1 spot before the other sensor as trains in shunting mode negates sensors.

After your comment, the only way I managed to make a Shunting Sensor "work" — i.e. only grab train with locomotives pushing — was to do the following:

https://steamcommunity.com/sharedfiles/filedetails/?id=3169194425

Sensors:

• Sensor one: If train has TWO locomotive -> go to the perpetual signal (to get out of SHUNT-MODE which locks you at 30 km/h
  
• Sensor two: If train has pulling locomotive -> go to the perpetual signal (to get out of SHUNT-MODE)
  
• Sensor three: If train has pushing locomotive -> Go to the side branch and turn around

With such space inefficiency, I don't see how anyone would ever use the Shunting Sensor. Unless I'm still not understanding something… but I'll need detailed instructions.

[Mišo]

You can have all this rules in one sensor. Each click on the track endpoint adds a new rule.

[Qwerty Bob]

Originally posted by Mišo:

You can have all this rules in one sensor. Each click on the track endpoint adds a new rule.

Seems obvious now… *facepalm*

Q: Do Shunting Sensors placed on platforms only trigger at the end of a "leg" or can it trigger when NORMALLY leaving towards the next station?

[Mišo]

Shunting sensors at platforms are triggered when a train logs arrival there. Stabling sensor gets triggered in the same moment but for only for trains that have their leg's schedule already finished and have a next leg.

[Randych]

Originally posted by Mišo:

Shunting sensors at platforms are triggered when a train logs arrival there. Stabling sensor gets triggered in the same moment but for only for trains that have their leg's schedule already finished and have a next leg.

So that's why stabling sensor does nothing and train just sits there? Instead need to use shanty sensor on platforms?

[Mišo]

Maybe. Stabling sensor is just for stabling - you finish one leg, you need to prepare the train for the next leg.

Also, note that we have a bug there that is already fixed but the hotfix version is neither built nor published yet.

FIX: Stabling Sensor worked only at station where next leg started despite UI allowing other stations
BUILD: 2.0.11

I wrote about it in https://steamcommunity.com/app/1124180/discussions/0/4339851902699403309/

[Randych]

Originally posted by Mišo:

Maybe. Stabling sensor is just for stabling - you finish one leg, you need to prepare the train for the next leg.

Also, note that we have a bug there that is already fixed but the hotfix version is neither built nor published yet.

FIX: Stabling Sensor worked only at station where next leg started despite UI allowing other stations
BUILD: 2.0.11

I wrote about it in https://steamcommunity.com/app/1124180/discussions/0/4339851902699403309/

I literally have same station set as leg 1 dest and leg 2 depart, still only manual commands work.

[Mišo]

Share your save, I will have a look.

[Randych]

Originally posted by Mišo:

Share your save, I will have a look.

https://drive.google.com/file/d/1XQPCdSqwfNa2-mkr-6tiTKPbaetJLW5t/view?usp=sharing

[Mišo]

Your setup almost almost worked

I did 4 minor adjustments:

• I turned off Auto Reverse for Masaryk Station. As you have sensors there, it is not needed & deceived you fatally
  
• I created a new rule attached to the dead-end (western) signal (was: the connected signal). The automation is triggered when the train records the visit, still being oriented towards the dead end. Auto Reverse kicks in only after this moment and the train then stops at the connected (eastern) signal. That deceived you to attach the rules there what did not work.
  
• I used the Go to platform command instead of the Go to signal command. Now the arrival and departure platforms may be different. I omitted the Reverse command - Departure Sensor reverses well.
  
• I clicked Paste the configuration to all neighbours to have the fixed version synced

Here is the updated save: https://drive.google.com/file/d/1Sm6BLCsfQWqMq1fi-G0JxpPndXF3gFxo/view?usp=sharing

[Randych]

Originally posted by Mišo:

Your setup almost almost worked

I did 4 minor adjustments:

• I turned off Auto Reverse for Masaryk Station. As you have sensors there, it is not needed & deceived you fatally
  
• I created a new rule attached to the dead-end (western) signal (was: the connected signal). The automation is triggered when the train records the visit, still being oriented towards the dead end. Auto Reverse kicks in only after this moment and the train then stops at the connected (eastern) signal. That deceived you to attach the rules there what did not work.
  
• I used the Go to platform command instead of the Go to signal command. Now the arrival and departure platforms may be different. I omitted the Reverse command - Departure Sensor reverses well.
  
• I clicked Paste the configuration to all neighbours to have the fixed version synced

Here is the updated save: https://drive.google.com/file/d/1Sm6BLCsfQWqMq1fi-G0JxpPndXF3gFxo/view?usp=sharing

I am very grateful for your time.
I still have way more questions than answers, but I hope it'll go away at some point.

[Mišo]

To address the confusion I implemented

UPDATE: Auto-reverse suppressed on platforms with Departure Sensor to prevent interference
BUILD: 2.0.11

[Randych]

Originally posted by Mišo:

To address the confusion I implemented

UPDATE: Auto-reverse suppressed on platforms with Departure Sensor to prevent interference
BUILD: 2.0.11

Wait, so it means I will have to remove departure sensors from almost all stations because almost all of them are dead end?
Now I have even more questions than before