When using workspace setting (G55, G56, etc.), following completion of a toolpath it resets to G54. When working with multiple tool paths at the same workspace this can be problematic. Is it not possible for the workspace setting to be remembered until I need to change to a different workspace.
Soft Limits still doesnāt allow for normal jogging within the safe work limits.
I get random āHard Limit Alarmā warnings when running toolpathās within safe limits which stops operation requiring a reset.
When a hard limit is reached, you have to Clear it and move twice to resume normal operation. I would think that once should be enough.
Slog through the following link, and youāll eventually find some information on your #2 statement. Iāve just taken to making macros and adding gcode to my programs to get back to the workspace setting Iām working with.
Even having been powered down, the X and Y relative to home seem to be remembered from the previous session. I like this, but donāt know if this is intentional.
Your post processor should output the WCS youāre working in in the header for the job. If it doesnāt, you might want to change it to do that.
Most likely caused by electrical noise causing a false trigger of the switches. Disable Hard Limits until you get your interference figured out. Set $21 = 0
Hi NeilFarreri, you replied to saskiaās post about the system remembering the previous sessionās x and y zero positions. In my case, once I finish a cut, the tool retracts and goes to a zero location from few jobs ago. This did not use to happen before the last software update, is this normal for grbl like you said in your reply? When I was done with a cut today, my CNC started moving to the previous location and crashed into something I had on the table. Do you know of a solution for this?
I am not very familiar with how gcode is generated so I am not able to answer that. But my process is: use Fusion 360 to setup cuts and then output it as a .nc file. I am cutting pieces of wood from a large stock material, so I manually jog to a spot where I have enough stock for the cut and then zero my x and y; I use a probe to zero my z direction. Once that is all set, I hit start to run the code. Everything cuts just fine, but the issue occurs after the tool is retracted, it jogs to a previous zero location. I tried uploading the gcode, but the system prevented me because I am a new user. I copied it below:
Your post processor is sending you to a G28 location. Is that your intent? Do you have a G28 location set?
That said, your Zeroes should still be the same.
I have a pretty good Fusion post that is used by many if youāre interested in returning to work zero at the end of a job. It also has some other useful features. Let me know and Iāll share it.
Thank you for your reply. I am not sure what G28 location is, Will going to the G28 explain why it goes to the previous zero location? What I will say is that I have not changed anything with how I setup jobs from Fusion, so I am suprised this has become a problem all of a sudden. Please share your post with me, although for what I am doing, I have not needed to return back to zero at the end of the job, but I am sure I will benefit from the post.
Itās one of two (the other is G30) user definable parking positions for a Grbl based CNC. Most people donāt use them, but itās pretty standard in industrial work.
Itās not. Unless you set your zero in that position. By default G28 is at machine zero.
Do you have homing switches?
What program are you using to control your CNC? gSender, IGS, CNCjs, etc? How are you setting your work origin?
@Bruces-CNC your reported issues should now all be dealt with as follows:
This was fixed with a LongMill Firmware update. You can use the āFirmwareā tool in gSender to reflash and this issue should go away
The workspace reset was a bug we finally tracked down and should now be fixed in 1.0.6
Should also be fixed now - especially after you update your firmware
Depending on the version of your machine you might need to look into using the resistors we recommend for the older machines to prevent false triggering of the switches: Custom Limit Switches - LongMill CNC
This is something that used to be even harder to deal with with how GRBL handles hard limits but we gave gSender a few smarts in these cases. I agree that making the pull-off a single move would be ideal though so itās something on our to-do list
Iām going to close this thread since itās pretty old at this point but if there are still any remaining issue or questions you can start a new one and ask away and then just link to this old one