We use cookies to personalize content, interact with our analytics companies, advertising networks and cooperatives, and demographic companies, provide social media features, and to analyze our traffic. Our social media, advertising and analytics partners may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services. Learn more.
I have an original x-carve, and the z-probe has worked fine for a long time. I think I was running grbl 0.9, but don’t know for sure. The arduino died, so I replaced it and flashed, of course I used the latest.
Now the z-probe doesn’t work at all, the machine inspector machine shows it always as “in contact” no matter what I do, I’ve checked for proper connection and shorts. Again, this worked on the old arduino with the older grbl.
I see a lot of references to grbl 1.0c having changed something, and that pin A5 (where my probe is connected) only being available in grbl 0.9, but the 1.1 grbl pinout still shows A5 for probing.
I suspect that I’ll have to change the grbl config and rebuild/flash it, but I have been looking for quite awhile now and can’t find any clear or definitive answers as to what has to change.
I see people that say they have it working with the arduino, but no answers.
I’d like to upgrade to an x-controller for the extra motor driver alone, and that would solve this issue too, but given that I haven’t used it in the last couple of years, it seems silly to throw $320 at it just to fix the z-probe.
Oh, and I should clarify something, when I say that z-probing worked, I don’t mean that it worked in easel, but it worked with other software, and the Machine Inspector in Easel properly indicated whether or not the z-probe were in contact or not.
Now Machine Inspector always things that the probes are in contact, and nothing I do changes that.
I’ve checked them many many times now
It literally went from working to not working in 30 minutes or less, the only thing that changed was that I had to replace the arduino, which I flashed with 1.1f.
The A4 was a typo, I’ve edited my original post.
I checked the continuity again, zero resistance when the clip and plate are touching. Interestingly, there is not-quite zero resistance, but still connectivity between pin A5 and ground with everything unplugged. That probably has something to do with it, but I don’t know if that is as a result of the change in grbl or something else.
I have another new, never used arduino, I’ll try that tomorrow, although I guess I’d be surprised if it made a difference.
I’m still trying to understand exactly what changed in grbl between 0.9.c and 1.1.f, it seems clear that something changed, but I haven’t found any specifics.
I have rerun the machine setup, and I’m checking the probe state in machine inspector, so not sure what another piece of software will do for me, but I’ll try a different g-code sender later tonight, in addition to trying a different arduino.
$6 is zero, although I’ve also tried 1.
$10 is 115.
I’d like to try flashing with older grbl versions, but so far I haven’t been able to find v0.9c or earlier. I did find a 0.9j hex file.
Anyone have an older version or a link?
Nothing changed from 0.9 to 1.1 that affects probing. If your arduino is not connected to the gshield, are you still seeing that A5 is grounded? How did you flash 1.1? Where did you get the file? @JustinBusby I don’t think anyone missed the point of your reply. I’ve always been curious about that $10=115
115 in v1.0c and earlier made the status be very verbose and that is how Easel was able to implement probing when the Xcontroller started being the default. It does appear that GRBL v1.1 changed how that setting works but it probably is not affecting Easel doing its thing anymore.
OK, well, it turns out that there was a reason that arduino board had been in my pile of x-carve parts for a few years
It has some sort of damage, I swapped the board for a brand new one, flashed it, and copied all my settings, and everything is working now.
