Hi Lincoln,

?

sorry for being unprecise on the part number – it?s indeed about a DM-RMC-100.

So I guess the only route to run the new system in parallel to the old system is to use EISC.

However, I hoped to get it working without fiddling with the old code. The system consists of three processor all handling different aspects (KNX, TPs, AV, etc.) and are already communicating to each other via EISCs. I already integrated one of them into the new program via EISC and that went well, so let?s get fingers crossed that the others can be integrated as well. ?

?

Cheers, Thorsten

?

?

?

RMC100 isn’t a complete/valid part number… Do you mean a QM-RMC, a DM-RMC-100, a DM-RMC-100-C, RMC3, RMC4, or something else?

?

If it is a QM-RMC or RMC3 you can only have one master if it is in ESlave mode, but if it is running a program you can use multiple EISC to talk to multiple processors.

If it is one of the DM-RMC flavors only one master IP table entry is supported

?

So basically (without having a program running on the end point) they can be controlled from one device at a time. Likewise for a CP2/CSlave … Cresnet is a single master bus – there can only be one master on the bus at any time and that is whichever processor is running the program (not configured as a slave) so you can’t have two master processors trying to control any Cresnet devices at the same time including a CSlave CP2.

?

Of course they can be added to the new program and moved back and forth as necessary during testing; or something I’ve done in my own home through major hardware evolutions is to add a temporary EISC from old to new, dragged all of the IO across the EISC and physically connected it to the new processor while letting the old program run in the old processor. This keeps things working while allowing you to roll in new logic (and as necessary, isolate old logic controls either as they are retired or for testing)

?

Lincoln

?

?