Advanced Search

Hey Eduard,
Thanks for all the effort... do you mind sharing your configfiles? xml and hal?

this would be great!

Thank you

Cheers Einar

Awesome!

What are those magic display buttons? Link?

I’ve mainly worked on much smaller machines, so on a lathe this size, I’m not sure whether the long motor/encoder cables would become an issue. If it's okay to leave the drives in a central cabinet and just rely on good shielding and routing, I’m happy to do the same—this is more of a concern than a hard opinion.

EtherCAT still appeals because it lets me pull extra data from every drive (load torque, temperatures, alarms, second encoders), and keeps future expansions simple.

Suggestion / request:
Overrides
When starting a program running (cycle start): user is prompted that an override (rapid, feed, or spindle) and asked whether they want to continue with override, or want to reset to 100%

(I make the mistake of setting an override and then moving onto a new program and hitting start, forgetting about the override)

Vast majority of servo / servo drives have "normal" cabling between the servo and the servo drive.

Don't see any difference due to ethercat just because one axis is 7m long?

(I'm a fan of ethercat and think it is the way forward. So neat just plugging servo drive into linuxcnc with single ethernet cable and getting.servo drives status / encoder position etc)

Thanks for catching that: the machine is X + Z plus a spindle.

There’s no VFD at all—this is still a fully manual lathe with a star-delta spindle and gearbox.

I picked EtherCAT mainly because the bed is 7 m long and I don’t want voltage drop or noise on long analogue/encoder runs. One Cat-5e solves the length and loss issues.