Fundamental problems with 1.6.2 #709
-
My setup: Homebuilt standard CNC router, Arduino UNO, CNC Shield 3.0, all 3 motors are nicely and repeatably running with a test script that drives them directly. So hardware is fine. Then, sorry, I'd like to run with Arduino IDE. This is the simplest thing - one tool that also (very important for me) has an integrated Serial Monitor - so when uploading a script worked, I know that the IDE and Arduino speak to each other. This is the reason why I run with versions of µCNC of 1.7.2 and below - they compile small enough without any changes. Yet: 1.6.2, on the other hand, does (or rather, did some) work. I could run it, it answered to ? and $$ and even G00 (changed internal state, but no motor moved, even though I know they work - see above). 18:36:00.826 -> Grbl 1.6 [uCNC v1.6.2 '$' for help] I do have limit switches; but now I have them cut out and clamped the X, Y, and Z limit switch pins of the CNC Shield to ground with jumpers. Still, I get the message above. So, please, does anyone have an idea how I could continue? (As a side question: Is there some sort of hook where one can write a piece of debug code that sends something back over the serial wire? E.g. like this - my problem is writing to the serial thing ...
Thanks a lot!!! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi there. The problem with 1.6.2 is probably because you are using the board configuration that is similar to grbl1.1. That version is not compatible with shield v3 because z limit pin and one of the pwm spindle pin was switched. You can use the current version of uCNC. It should still fit on the uno with a normal configuration. Let me know if you run into problems. |
Beta Was this translation helpful? Give feedback.
-
Ok - I changed over to the master branch, and VSCode+PlatformIO. Works better, but not good enough ... separate discussion. I'll close this one. Thanks! |
Beta Was this translation helpful? Give feedback.
Hi there.
My guess with v1.7.2 not responding (or apparently being unresponsive) is that the alarm state is active because of the ESTOP pin state.
You can confirm this by sending a
?
char.The problem with 1.6.2 is probably because you are using the board configuration that is similar to grbl1.1. That version is not compatible with shield v3 because z limit pin and one of the pwm spindle pin was switched.
You need to use a mapping for shield v3.
You can use the current version of uCNC. It should still fit on the uno with a normal configuration.
Let me know if you run into problems.