The Z axis OVER/UNDER/NO FIT stuff is kicking my butt!!!
I understand a bug report has been opened on GitHub (#297 in May 2021) to address the simulator not recognizing G53 and G92.2 commands which causes an OVER/UNDER/or NO FIT reading on the DRO's on a certain axis (usually Z).
This has not been a problem on the machines I am running; I simply ignore the "warning" and the files work fine regardless. However, I am starting to build systems for other clients and this is proving to be a huge headache to work around or try to explain why the Z DRO is yellow or Red all the time.
MC
Any Update on GitHub issue #297?
Forum rules
No profanity, no gambling, no illegal activity, so sexual or pornographic material.
Posts not related to the Buildbotic CNC Controller are likely to be moved or deleted.
No profanity, no gambling, no illegal activity, so sexual or pornographic material.
Posts not related to the Buildbotic CNC Controller are likely to be moved or deleted.
-
- Posts: 15
- Joined: Mon Mar 29, 2021 6:46 pm
Re: Any Update on GitHub issue #297?
Hello.
I just ran into this issue also when doing some modifications to the vectric post processor by adding G53 G0 X24 Y18 Z7 to run at the end of each job.
I don't really use the 3D viewer, but this throws a "No Fit" error on the coordinate control page as the "Fit" checks are based on the zero offsets.
The G53 command does work but I don't like how the error is thrown as it is tough to realize if there is another "no fit" issue.
Mike
I just ran into this issue also when doing some modifications to the vectric post processor by adding G53 G0 X24 Y18 Z7 to run at the end of each job.
I don't really use the 3D viewer, but this throws a "No Fit" error on the coordinate control page as the "Fit" checks are based on the zero offsets.
The G53 command does work but I don't like how the error is thrown as it is tough to realize if there is another "no fit" issue.
Mike
Re: Any Update on GitHub issue #297?
100% agree. Should be on top of list of items to fix.
Re: Any Update on GitHub issue #297?
It is fixed in the next release. The release should be coming out soon.