Dependence number of axes, cycle time and hardware

[RomyX]

Can more than 10 axes be supported by the Motion App (and is this possibly dependent on the set cycle time)?
And to what extent is this dependent on the selected hardware (currently CORE plus X3) and the CORE plus X7 available from next year?

[MichaelB · Accepted solution]

With RM22.07 (V1.16) up to 30 axes are supported with ctrlX MOTION. The possible EtherCAT cycle time is depending on the complexity of the application program and can be switched between 2 ms, 4 ms and 8 ms. For a higher number of drives I propose to use 4 ms or 8 ms cycle time. With ctrlX CORE X7 and RM22.11 (V1.18) the maximum number of drives will be increased. Detailed information will come in November. Please feel free to send me a PN for more details and to check your concrete application.

[RomyX]

Thanks for the helpful answer!
Would it be possible to document this topic accordingly in the Motion App?

[MichaelB]

Approvements concerning this topic are already in discussion and planned.

Thanks for your hint.