I'm planing to make a shuttle train event,with 3 contacts.I want the train to stop on the midle contact,for 10 sec and then continue.Fore both ways.I know I can make it work with a contact track 24994 but is it possible to make it, with just a singel contact 24995 + logic from event tool?

Its a linear route and yes I have a CS3.My question is ,what funchion should I use (in event)on the midle contact on the return.The shuttle train starts in A,go to B ,wait 10 sec,than go to C.Wait 10 sec ,return to B wait 10 sec,go back to A......

I think we need to agree on a definition of the term "Event". It can be a series of functions or just one function. To me Marklin prefers to use the term to define a series of functions. Like a story. And Jean is correct, Marklin Events are mostly loco specific I have yet to figure out a way to get around that. It is possible to create stopping blocks using events that are not loco specific. We created an event that sends a panorama car out from a central station, climbs half way up a mountain, stops at a halfway house then continues up to stop near the top of the mountain. It then returns down to the starting station. We included announcements. door opening and closing, music, and conductor whistles and loco horns. All in one even and it repeats as long as you will allow it. Events is one of the major benefits Marklin provided us with the CS3 and it can be a never ending source 0f challenge for anyone who plays with it.

Clapcott, any chance you could give us an example of the second scenario? And in the first could you, after swapping a loco in a MU consist delete the remaining original loco?

Not exactly sure what you need, however the following shows a normal CS3 event macro "Shuttle 1" in this case designed with a Red Loco as a placeholder.

Below that is shown the Blue loco setup screen and the selection of an unused function button (F7) which is configured with "Shuttle 1" as its runtime option.

Thus , placing the blue train between the sensors and clicking F7 , will use the Shuttle1 Macro but with the Blue Loco as the inherited target

(Note: the signals and Loco labeling shown on the track board are extra to the actual shuttle macro, should you wish to get more into events and macros)

Please elaborate, " ... between the set boxes ..."


- which actions?
- is this perhaps referring to the (buggy) Web interface, where black boxes appear if you review the events from the main screen (as apposed to the specific event endpoint/view)?

Tomorrow, Oct. 8, there is a Marklin USA digital webinar on Youtube via Zoom live on a two train single line shuttle event rework. You can watch live and join or afterward later on.

I have the same problem. I block events a lot. I have reviewed every digital webinar on this, and still am stumped. I think Curtis and Rick said it is problematic for them too.

There are a number of ways to stop or terminate an event. By the way, I think the shuttle macro is terrible and making one from scratch provides a much better event. But first the easiest way to terminate an event is by clicking on the tab which has an icon of a loco on it inside the Event edit tab. That brings up other tabs such as Event Stop and Event Start(I don't remember exactly which right now) and experimenting around will usually terminate the event. Curtis in one webinar introduced a neat idea. He added an item to the layout screen which was not part of the layout but was switchable such as a light, signal, or even a turnout. He then included into the shuttle even an if then option so if the light or whatever was on then the event stopped. Interestingly, when I first discovered the shuttle macro I tried to add intermediate steps between the set boxes and thought, since I could not see them, that the Event had rejected them but though not visible they were actually in the Event.
I got off my butt and turned on my CS3 and the options are "Block events", "Terminate events" and "Stop events". There is actually another way to do it after a specific amount of time but it is so weird I don't really know how it works. If you want to experiment, click on "Edit" in the Event tab then on "add" and play around with the "Control" and "Modeltime" tabs.

On mine they were grey until I ran the event. Then they became white. "Stop event" stops the event at the operation when the button was clicked. "Terminate event" stops the event and resets it to start. The advantage of "Stop even" is you can restart the event from where it was stopped while with "Terminate event" you might have to operate the loco back to where it was before you started the event.

Hi Surge

In fact it is all very simple: one macro starts a loco which is simply stopped by the next macro to follow.
Each macro is a string of short commands to start a loco, set a speed, add a timer for the next command but the idea is that each event is normally very short.
Long duration needed lead to imprecision: It takes 30 sec for the loco to go from station A to station B

So you COULD make a macro to start the loco and stop it 30 seconds later but this will lead to imprecision. So better stop the loco when it reaches another sensor triggering another event. Very simple, very precise.

So in the HUGE majority of cases the event stops by itself (all elementary commands have been executed). It leaves the loco continue its run until the next event is triggered.



A misleading feature is the event recorder: you start a loco, do whatever you want, change turnouts, change signals, change the speed, start another loco, it may last for quite a while.
One very long event playing back all you activities (manual commands).
You may play it back but all these activities based on a given speed, given delay will NEVER repeat it excatly as the first time (speed may be slightly different, leading to the loco NOT stopping exactly as before.

The programming sequence MUST BE driven by multiple sensors for it to be precise hence the concept of short events finishing the ^previous event (stopping az loco) before starting it (or another one) in the same or the opposite direction.

The trick is KISS: Keep It Straitforward Stupid.

Cheers
Jean

In this case you need to associate the triggering contact to start an event with a condition (another entry sensor) ON or OFF) to eneable or disable its triggering

Jean

The problem with just terminating an even is that it only does that so any settings on the loco at the time of the termination of the event remain in operation. So if you terminate the event while the loco is running it continues running.