This repository has been archived by the owner on Jan 14, 2024. It is now read-only.
Replies: 2 comments
-
Use the motor fault signal available in newer versions? It may require a small plugin or at least a modified board map file.
No. In the latest version unused pins can be repurposed and also made available for plugin code. Do you compile yourself? Again, please continue this discusson at the new repo. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks Terjeio. Moved to grblHAL/core#110 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Stepper motor control is open-loop and cheap. Servos are closed-loop and expensive. I am planning on partly closing the loop on my stepper driven system by feeding the step and directions outputs from the GrblHAL controller (Teensy based breakout board) to both the stepper drivers and to a separate position tracker based on a Raspberry Pi Pico. The three movement leadscrews will be linked via timing belts to 200PPR rotary encoders which will feed back to the Pico. After allowing a ratio for micro-stepping the Pico will then raise an error if the driver instructions and position feedback do not match within a given tolerance.
This has to be communicated to the GrblHAL controller somehow. What would be best? Triggering the door open switch? Does GrblHAL react to the limit switch inputs for the A or B axis even if compiled to handle only three axes?
Beta Was this translation helpful? Give feedback.
All reactions