Skip to content

Fundamental problems with 1.6.2 #709

Closed Answered by Paciente8159
hmmueller asked this question in Q&A
Discussion options

You must be logged in to vote

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.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by Paciente8159
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants