Hi David
You seem to be using slider-activated rails to trigger events. M track perhaps?

Using the full potential of a CS3 (occupation detection) you wouldn't have this problem unless M track.
With my first M-track train I liked these slider-activated rails but soon I discovered that with multiple sliders trains this was becoming a mess.

With a CS3 I don't know exactly how it is processed:
- start multiple execution of the same event after each detected slider
- start one event and interrupt it / restart it when the next slider triggers the event.

Not sure what the CS3 does here.

So - not sure here - but you may end with contradicting orders sent to your layout.

Conclusion:
- either you operate trains with one slider
- or you modify your layout to have occupation zones, the event being triggered EITHER when occupation starts OR when it stops. Your choice but alas not easy to do with M-track.
- an alternate solution is to inhibit the slider-operated rail when the first slider is detected (more wiring, more contact rails, additional relays). Of course in this case you need to add a contact rail elsewhere to stop the inhibition. Feasible, but a bit tricky.

Cheers
Jean

Jean. C track with circuit tracks. Three other events with locos and coaches with sliders work fine it is just this one event that causes the problem.
I have run events for years and this is first time I have found sliders on coaches to also control the loco.

David I don't know what this special event does.
Some examples:
If such a track (24994, 24194, 24294) triggers a signal S1 to green by a train TA with multiple sliders.
If train TA stops at another signal but only the loco has crossed the contact track and starts much later, then the other sliders will trigger S1 again to green much after initially intended. This may be unwanted and make collisions.
On the other hand, if such a track is not near a signal (the train does not stop), then the problems are less likely to happen (you order signal S1 3 times to green within 2 seconds so no big deal)

If instead, such a track orders a light to be on (using a relay) then the light being on again will have no concsequences.


What I am trying to say is depending on the content of the event and the location of the contact track (near/before a signal or far away) the adverse effect of multi sliders will have consequences or not

On the other hand, using occupation zones, you don't have this issue ever.

Jean

Hi. All you say in your two posts are correct and is how the event was set up. However I deleted the event replaced the circuit track and reset the loco. None of these alterations should have made any difference but when setting up the event again everything now works as it should. No idea what happened with this other than a Presierling came off the platform and made changes.
Many thanks for the comments.
All best
David

An event is sequential and if it is not sequencing as desired it is possible to observe it sequencing by activating it while seeing it on the CS3 screen. That allows you to see the actual "Event" in real time. That usually can indicate what the problem is. There is an adjustable time delay that the CS3 queries the S88 inputs. It is usually very small, fractions of a second, but can be increased.