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 was watching some videos of the x-carve, and noticed that users are having their machine position displaying 0,0,0 for all three axis. When I look at my machines postion, it reads -789, -789. -1 when I have it homed.
Do I have some wires crossed somewhere that would be making this thing read backwards?
To be clear, by default, the top right corner (looking down) is the natural for the machine zero? And when it goes to my starting position (lower left), it is reading negative from that natural zero?
I would definitely like to change this. Is there a walkthrough on how to do the grbl rebuild?
A CNC machine is by nature a remover of material. Remove => subtract => working in the negative domain
As long as work zero and design is aligned all is good.
Uploaded with no problems. I now have 0 for my machine position instead of the negative.
In the midst of all of this, I did notice my left belt had just a bit more play than the right one. So, I decided to tighten it up a bit. Didn’t even get to the same play as the right one before it snapped… so… looks like I’ll be down for a few days…zzzzz
It’s not should or shouldn’t. I have tried to be careful in using the correct wording. If I have ever said that you should or should not use 1.1f/g that would be a mistake.
What I do say is that I do not recommend using 1.1f/g for laser work.
Modifications to make the laser work were extended to try and make laser work safer, but have instead created scenarios where serious injury could occur.
I’m not saying that my version is safe, by any means, but my version does not change the way G-code works and therefore is not as dangerous as 1.1f/g which causes the user to change the way they use G-code to get 1.1f/g to control a laser.
An easy example:
In my 1.0c version with $32=1, M3 S255 will turn the laser on.
In version 1.1f/g with $32-1, M3 S255 will not turn the laser on unless other operations have occurred prior to issuing the M3 command. And then at a later time you issue a movement command the laser will come full on. Like a G1 command.
With my version a G1 command will never turn the laser on.
The specifications that grbl is built on do not specify turning on the laser or spindle is a function of the G1 command.
And there are many other examples.
I have had one report that when running 1.1f/g the laser came on at full power when the operator was not expecting it.