Miguels244
Diamond
- Joined
- Mar 27, 2011
- Location
- Denver, CO USA
Ok,
I have worked with ethercat, modbus, can open, sercos 2 and3 , device eat, Ethernet ip.
I am being asked to decide which is "better" for a new controls department.
For my part they all suck in different ways.
Except that ethercat seems to be a little less obtuse, and servos works for motion control like it was designed for it (Dunn)
Our application is...for the moment not a motion control so high synch speed is not a ball buster.
What says the peanut gallery.
My recent experience with modbus tcp was a real downer.
Seems that this should be easier, and I recal ethercat and beckhof being damn near transparent.
What have you hated, loved, with what hardware, why?
I have worked with ethercat, modbus, can open, sercos 2 and3 , device eat, Ethernet ip.
I am being asked to decide which is "better" for a new controls department.
For my part they all suck in different ways.
Except that ethercat seems to be a little less obtuse, and servos works for motion control like it was designed for it (Dunn)
Our application is...for the moment not a motion control so high synch speed is not a ball buster.
What says the peanut gallery.
My recent experience with modbus tcp was a real downer.
Seems that this should be easier, and I recal ethercat and beckhof being damn near transparent.
What have you hated, loved, with what hardware, why?