As of firmware 0.85, the “Start Probe” button should no longer put out a 38.6 command. In firmwre 0.85, @bar changed the button to output a 38.2 command. Pre-v0.85, it was outputting a 38.6 command and then immediately throwing the Error 20. Did the latest firmware revert back to using a 38.6 command when the button is pressed?
1 Like
When you are able to test it again, please confirm what g-code command it is putting into the command box (a screenshot of the command box after pressing the button should work). After firmware v0.85, the g-code command after pressing the Start Probe button should be a 38.2 command. Before 0.85, it was outputting a 38.6 command and throwing the same error 20. If you have the latest firmware, then I believe it should still be outputting a 38.2 command.
Also, after trying the button and seeing what command is put into the command box, trying manually starting the probe by typing a 38.2 command into the command prompt box. E.g., “G38.2 Z-50 F60” (Z = max travel distance in mm before considering the probe action to have failed because no contact registered; F = speed in mm that machine will lower while probing). If that fails, also post the screenshot of that failed command.
2 Likes
Have you updated your index.html.gz file recently? The change in command is in the index.html.gz file (which controls the user interface and web portal) and not in the firmware itself. If you’ve been updating the firmware, but haven’t updated the index.html.gz file in a while, then that may be why you’re getting the old/bad command. I would probably try updating that file first (only takes like 30 seconds).
2 Likes
I thought I had? But I know that sometimes such changes don’t ‘stick.’ I’ll be taking the machine home next week to replace some worn parts, and will also work on this.
Mahalo nui loa!
1 Like
It’s worth checking either way. I often just update the firmware and don’t update the other files unless a big change has come (hate having to re-do a calibration changing to a new yaml file).
2 Likes
It is still a G38.2, but there was a reference to 38.6 (note no G) that was part of the handling for blocking multiple simultaneous probe requests.
Having said that there was no specific handling for ‘No probe pin defined’. I’ve now added that in a new PR. And along the way cleaned up some of the related start up / set up processes.
@bar Grbl tweaks for using probe by md8n · Pull Request #119 · BarbourSmith/ESP3D-WEBUI
2 Likes
Aloha,
Got the router home, verified that it was calling G38.6, deleted and uploaded fresh index.html.gz, and it stopped throwing that error. I suspect, however, that it has to be on the frame to probe?
When I tried it on the bench, it started the Z motors, then threw a position error on all arms.
Mahalo,
1 Like
I don’t recall if I ever tested it off the frame; probably not. Not super surprised though. Glad that resolved the error. Hopefully, it will all work as planned now.
3 Likes