Correct and correct.jbraun wrote: The attempt to correct lost steps is done between the encoder and the drive. Linuxcnc is unaware of what happens there.
The shut-down alarm can be sent to Linuxcnc like an e-stop.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Craig E wrote: Thanks everyone,
This is very helpful. My stepper drivers have encoder inputs and alarm out if I understand correctly I should just wire the alarm out to Mesa board for LinuxCNC?
or am I misunderstanding and it would it be better to just wire the encoders to Masa directly and not the drivers?
Please Log in or Create an account to join the conversation.
Yes, namely wire it to the "joint.N.amp−fault−in" as Rod mentioned in the hal file, but the actual wire from the fault output can be connected to any of the Mesa field inputs. It literally needs a single line added for each of the drive/motors used in hal.Craig E wrote: My stepper drivers have encoder inputs and alarm out if I understand correctly I should just wire the alarm out to Mesa board for LinuxCNC?
Please Log in or Create an account to join the conversation.
This is something I have been looking into, my robot does this with its oem drives and has cables that go from the servodrives to the motion control card sending the encoder signals. So I have been looking for drives that do that aswell, and have found some of the lichuan drives do this servo.xlichuan.com/ProductsStd_212.htmltommylight wrote: The only issue is when using closed loop stepper/drives and using the same encoders for LinuxCNC feedback ( even this will work for sure ) but might need some signal shaping and/or splitting to have the same encoder wired to two inputs on the drive and Mesa board.
.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.