Disable and Enbale Device Functions in PLC program

[CQ2023]

Our customers add axes with different configuration in the slave, these axes can't be used at the same time , but share the same programs. Is there some function block to enable or disable these slave device in programs?

Just like the operation as below:

[CodeShepherd]

Are these simple IOs or even motion axes that should be controlled via ctrlX MOTION?

My main question is how are these IOs in the PLC program addressed and then programed?Could you tell us some more what you want to achieve how your programing looks like?

In our "Template for cartesian handling systems V1.0" we created methods accessing partially the same IO range and only one is called depending on the configuration. These IOs have always a fix address but do not necessarily be all available.

ctrlX PLC Engineering cartesian template IO addresses and method calls

ctrlX PLC Engineering cartesian template redundant addressing of IOs

[CQ2023]

Sorry, I didn't describe it clearly, and thank you for your answer.

these motion axes are controlled via softmotion.

I don't have customer's programs here, so I drew a diagram to show the actual situation.

In the picture, they configured a fixed number of slaves (four drives) in the PLC project to run the program. But in reality, there are two different configurations of slaves in the control network, and it is necessary to switch from one slave to another at different stages during the program running. (For example, from 4 to 3 drives). These two phases have the same control program, just using different number of drives. So in this case one drive must be automatically disabled by the program, otherwise the communication will be wrong.

Is there any way to solve this problem without having to disable the drive offline by hand?

[CodeShepherd · Accepted solution]

Moved topic to coresponding sub forum CODESYS - PLC Add-ons.

So you really are changing the configuration of ther EterCAT fieldbus? Or how do you switch between the topologies?

EtherCat can actually not perform any hot plug functionality and in the actual state will give addresses automatically depending on the topology. See online documentation.

You can switch up the EtherCat partially to OP and not all modules need to be attached. In standard all data is transmitted in one package and as soon as one datum is faulty all data will get invalid. But several data packages can be set up that are checked individually. This is handled via so called "sync units" (see docu). So if a missing slave is another sync unit then the rest, the bus can go up.