About David08

David08 · ‎07-20-2023

The customer also wants to know if a CtrlX3 would have enough performance to put one per machine and manage 6 axes (6 devices) and 8 variables per Drive (total 48 tags).

David08 · ‎07-20-2023

Hello PraveenRams, The correct option is 6 machines with 8 axes each. The problem is that the connection is individual per axle. On the Device Bridge side you have to create a Devices per axis, because the connection is individual per axis. So as I understand it, that would be 48 devices. If this is the case, the problem would be that the cost of licences for 48 devices and few tags is very high.

David08 · ‎07-04-2023

Hello, A customer has a project where he has to read 5-6 parameters per axis, on 6 machines that have 8 axes each. In total there would be 300 tags and 48 devices. The customer did several tests of reading parameters by EAL and sending it to another device by MQTT. The tests were with 30-40 tags and 3 devices simultaneously. They obtained a sampling time of 190 ms. Now they have to consider which hardware to use and that the performance is good for a low sampling time. They have thought of two options: - One CtrlX X3 for 50 tags and 8 devices - One CtrlX X7 for 300 tags and 48 devices. On the X3 there may be a performance problem and on the X7 a licensing problem due to the number of devices. What would be the best recommendation for this application in terms of performance and cost? Thanks in advance.

David08 · ‎06-15-2023

Hello Michael_A, Thank you for your resply. Is there a plan to implement it in the future?

David08 · ‎05-22-2023

Thanks Drives_Uwe.

About David08

Re: Performance with Indradrive parameter reading

Re: Performance with Indradrive parameter reading

Performance with Indradrive parameter reading

Re: Torque Control with AxisInterface

Re: External encoder with measuring wheel