Hi, I have been able to successfully calibrate, and make a first cut. But I’m having issues after the first cut is complete. Once the first cut is complete, no matter if I try to jog the machine, or click home, the machine wonders infinitely in a direction, until I have to hit the panic button to shut it off. And then I need to rehang Below is my console info after the first successful cut, and I clicked the home button after the successful cut. I guess my questions is, after a successful cut, what would I need to do to cut something again… do you always need to rehang? I’m running V.73, I cant get V.75 to work on the machine.
No, you should not have to unless something goes wrong as you describe. Once the gcode job finishes you should end up in “idle” state and able to load another job, jog, whatever.
What issues did you have getting the newer code on? There have been fixes both in the firmware and UI since .73 that you probably will want.
Actually, the issues might be UI related… And I have NEVER updated the index.html.gz file… So maybe I should do that. Maybe it does effect some functions with new firmware and stuff, but based on the description, I thought it was completely aesthetics.
“index.html.gz controls how the machine interface looks. If you wanted for example a dark mode, replacing this file would give the interface a new look. I expect that there will be a number of community created UI options created quite quickly.”
Yes, you should always update the index.html.gz at the same time as firmware.bin. These are often co-dependent. Also you should save off your maslow.yaml from the machine once you get a good calibration and keep it for reference, and update the maslow.yaml as well on new releases, then update the values for your machine that start with Maslow_ in the file or using the config or settings pages…
I updated to V.75 and updated the other 2 files. Re-calibrated, did a successful first cut. After the successful cut… I then hit right jog button 100mm and it was travelling infinitely to the right off my plywood atleast 4 ft… So I hit the emergency stop button. I’m not sure what to try. Any ideas anyone? @bar?
Many of us are experiencing similar issues where at some point the machine seems to stop processing (not sure of the cause) and the stepper motors will maintain their current speeds until commanded to change (which never comes). It is definitely a bug but it doesn’t seem anyone has found a repeatable pattern. It sounds like your gcode file may be a repeatable case (true?). If so, sharing your gcode file may help others reproduce it.
I have also had cases where the machine was told to jog the Z and picked another axis and jogged X, or told it to stop (not paused) and had it start moving again when released
The default jog settings are 100mm… when I hit play on my gcode file, it starts cutting, but the 100mm changes to 100 inches. SO when my file is done running, I hit the jog button but it goes what appears to be infinite movement, but its just trying to travel 100 inches in the direction I chose, not 100mm.
So your gcode is inch based and the jog selector is mm, so it gets confused about the units? Good find! I’ll take a look and see if I can see in the jog code what gcode its sending for jogging and make sure its setting the selected units on every every jog movement (I bet its not)
So your gcode is inch based and the jog selector is mm, so it gets confused about the units? Good find! I’ll take a look and see if I can see in the jog code what gcode its sending for jogging and make sure its setting the selected units on every every jog movement (I bet its not)
Is it possible to find out what mode the system is in and adjust the dialog
accordingly?
you don’t want to switch to start gcode in inches, pause, jog (and have it
switch to mm) then unpause and continue cutting in mm
possible, yes. Not as easy as I would hope as the normal grbl status messages that update the positions, etc in the UI does not include that information, but certainly can query the current state with a code, then wait for the async response prior to doing the jog and either send G20/21 or not based on whether it matches up then revert with the opposite after the jog.
I’ll enter a github issue as I don’t have quite the time today to address this and I don’t want to lose the request in the forums, which is not that easy (for me anyway) to search.
Below is my console info after the first successful cut, and I clicked the home button after the successful cut. I guess my questions is, after a successful cut, what would I need to do to cut something again… do you always need to rehang? I’m running V.73, I cant get V.75 to work on the machine.