Doesn't this essentially do what a signal stop section does? Why would you need an M84 in addition to a digital signal, when a CS3 can recieve feedback and an event can control it?
Does it replicate what a braking module does, and make the block longer?

…but in digital mode, you don’t need - and even shouldn’t have - powerless sections on your layout controlled by an m84 or any digital signal. When your engine arrives to the feedback section where you want the engine to stop, the CS3 simply tells the engine to stop (and/or to shut off motor sound or other engine functions).

Hi
I tend to agree with PeFu. The powerless part is not required. The locos does not accidentally start running unless the operator or cs3 tell them to go.
If in a shadowstation(unvisible) it it probably no big deal without sound and lights on. Only advantage with the powerless section is that you get a double safety against human error. You both need to set power on track section and tell the loco to start moving… will only work if you have told loco to stop before you shut off power to track. If you only shut of track power when loco is running it will resume with same speed as soon as track power is restored.

Finally to johnjeanb: I fully agree that rockrail etc can simplify and perform more complicated automation than we can do with cs3. Still the software does not track the locos, it assumes that the loco it sent towards a feedback contact is the one that triggers it. If a turnout fails or a train loose a wagon (triggering the said contact track) I assume the software will assume it was the train it sent there that has arrived. And automation will fail.
Regards
Thor who have lot of fun making automation with cs3.

As long as you have a cs3 no brake module is needed. You can both adjust the acceleration/deacceleration in the lok decoder with the cs3. You can also program a lover speed to be set as loco enters the feedback contact. To smooth it further set the event to wait a certain amount of time and then set even lower speed or stop. Repeat above if required. Alternative:
I have a feedback switch in both ends and in middle of each block. In event i program reduced speed on entering contact. Crawl speed on middle contact and stop on last contact. If you need a more abrupt stop after crawl Use the switch direction command. This will override the deacceleration programmed in the decoder. Make sure to switch twice so that correct direction of travel is set for next start…. Or make a habit of setting correct direction of travel at start of all events. And from crawl real trains also stops with a jerk as the brakes are applied.

Hi Jean.
I do not now RR. Dowloaded a copy once but never used it.
My point was that RR only computes where the Locos are based on given input at first startup. If you cut power and rearrange the locos i assume RR would not know.
Not to try to compete with RR but you can do some of the same with events in CS3. On my small layout with 5 locos the events take care partly the same way. There are never collisions. If one train looses power the others would wait in eternity since block is reserved for the halted loco. My layout are made with short sensor tracks so i cannot check for lost wagons🙄
And: to make events in cs3 you dont need to draw the trackplan at all in cs3. You can just as well have it on paper to help defining blockes routes etc.
That said I fully agree that RR is easier and better to keep high traffic density than you can obtain wih the events.
But then I loose the fun of trying😂
Regards
Thor
And we are now far off the question starting this tread. But as I have said earlier: what the heart is full off. The mouth spills over with. And to me these events are fun to make and evolve.

👍😇

No rytter, there isn't a way to slow down a loco. In an event with the CS3 without a brake module. The train will just stop. I'm not sure if Rocrail or other automation software can, but johnjeanb. Will know. You can only delay events in a CS3.

Ok! That's great! I guess if the Marklin digital guy's covered this, either I missed the webinar, or Marklin told then not to because this could help cease braking module sales?

The overall control is in yor brain… or on a sheet of paper. You make the event so that you know which loco is entering the various contacts. I hav choosen a solution where layot is split(again in your brain or a piece of paper) i blocks(i.e. Parts of the layout that can only hold one train at the time. Name the blocks and create controlling contacts in cs3 with same names. A controlling contact is a virtual thing/tag in cs3 that has a name and one of two conditions: on(meaning block occupied)or off(meaning block free). Then at startup all blocks not occupied by trains are defined as unoccupied. The ones with trains occupied. Then in all events for the trains you start with the event checking/waiting for relevant blocks to next station to be free an then set them occupied for its own train. Then the event set the turnouts correctly and set the train running. During the run the event is set to wait for the various contact tracks on end of each block. And when contact is triggered the events set the controlling contact for the previous block to un occupied(for other trains to use). One such event for each train and triggering all events simultanously. One event will capture and set required blocks to occupied. And travel planned routes. The other trains will wait til theire required blocks are free. Then do as for above and set off.
Works fine on my layout. Above a little simplified but the general principle is correct

Thor