Hi
Since two Updates, the CS3 offers multiple MACROs namely ….
The BLOCK macro, like the other ones must be called by another event.
It contains 5 fields :
- The signal field Drag and drop the signal in this field
- The entry contact Drag and drop the entry contact
- The exit contact Drag and drop the exit contact
- The following BLOCK macro Drag and drop the following BLOCK macro
- The optional pause flag

When a BLOCK macro is invoked from another event, you get the following to fill



So I have filled 3 BLOCK macros (BLOCK 1, BLOCK 2 and BLOCK 3) the following way


BLOCK 2 follows BLOCK 1
BLOCK 3 follows BLOCK 2
BLOCK 1 follows BLOCK 3

Sensors are associated with each block
- 0E1 entry sensor for BLOCK 1, 0X1 exit sensor for BLOCK 1
- 0E2 entry sensor for BLOCK 2, 0X2 exit sensor for BLOCK 2
- 0E3 entry sensor for BLOCK 3, 0X1 exit sensor for BLOCK 3

- OP1 pause sensor for BLOCK 1,
- OP2 pause sensor for BLOCK 2,
- OP3 pause sensor for BLOCK 3.

So the 3 blocks are arranged for a simple loop circuit.

Now testing, here is what I observe
- the blocks will operate only when the event, containing the blocks is started
- The pause sensor must be de-activated for Blocks to operate
- The entry sensors seems to produce no reaction
- The exit sensor of BLOCK 1 will close the signal 1 and open the signal 2
- The exit sensor of BLOCK 2 will close the signal 2 and open the signal 3
- The exit sensor of BLOCK 3 will close the signal 3 and open the signal 1

Issues
- the Block macro, seems not to be working properly as I cannot simulate a 2 loco operation because, in this case, 2n signals must be red and only one green
- instead no matter what I simulate, always 2 signals are green and one is red
- strangely, no help is provided regarding the BLOCK macro as if the BLOCK macro was not finished and not operational yet

Question Is one of your, more successful than me in making this work?

Kind regards

Jean

Hi,
Thanks to you I found this document http://nagoya-maerklin.world.co...ol%2034%20-%20No%203.pdf and on page 6 it explains the BLOCK macro.

I must say I am very disappointed by this "gas factory" (In French we say "Usine à gaz" when a solution or tool is un-necessarily complicated.
The conventional arrangement of signals and speed control seems way easier w/o the BLOCK macro which must be combined with the BRAKE and IF macros.
Apparently, the modern use of occupation signals is not possible (only entry and exit contact rails).

I was just curious about Märklin latest developments (not so new as it was more than a year ago).
Sorry but I go back to Rocrail where there ar much much better possibilities (and easier to implement / test). Furthermore, editing events on such a small CS3 screen with, at least 3 superposing windows is really a pain in the neck.

Of course, if someone can prove me wrong, I will be happy to discover.
Cheers
Jean

Edited by user 09 July 2023 16:52:52(UTC)  | Reason: Not specified

Hi David
For a next generation CSx, I believe it must:
- be able to follow trains on the layout so that not insulated sections or brake sections are necessary
- the only way to a larger screen is to have none and rely on the existing flat screen market. I use a 17" screen for Rocrail and it could be better with a larger screen.
- allow the signals to "talk" to trains directly without having the need for a zillion insulated track sections.

I think Märklin is trying this since years (some bizarre fonctions briefly appeared on the CS2 approx 5 years ago).
The macros make only sense if you know which train to control thus simplifying the wiring and improving the possibilities (reduced speed in zones, etc)
So lets see what we will get.
Cheers
Jean

Powere being cut from, then restored to the block by the CS3.

I've never used it, but it sounds like the same as when you block events, but limited to a certain container action.