Apparent bug in zigzag pocket

I am wondering how to report a bug in the zigzag routine. I am machining a acrylic window for a display and have found the zigzag routine cuts the bottom of some of the LED windows leaving a flat spot on some of them. I'd like to report that issue to the software developer.

I have a row of leds cut into an aluminum bud box and am cutting an acrylic window for it. Of the eight leds, four of them get clipped on the bottom creating a flat. I hand edited the g-code to get around the issue, but think it would be appropriate to report the problem.

Can anyone help me get in touch with the developer?

I guess it would help to know what CAM and machine software you are using.

The DXF file was created with Autocad Lt 2000. G-Code created with GrblGru V3.42.0. The router processes the cuts exactly as the G-code commands it to. The error shows up in GrblGru 3D plot tab regardless of the machine selection and examining the G-code confirms the bug. When the zigzag routine is creating the pocket, it appears it does not correctly compensate for the radius of the cutting tool, but only some of the time (50%).

FYI, my router is a modified Asymtek Automove 201 controller driving an Asymtek 12"x12" machine (don't know the model) driven by a custom, (written by me in National CVI) translator and sender, since the Automove has its own ACL language.

I have also acquired an Automove 303 XY table which I am currently building up which I will either drive with the 201 controller or perhaps Grbl on a Mega 1260 board or some other driver. I haven't decided as of yet.

This looks like a bug in my program. Thanks for the information.
Can you please provide me with the DXF file.

File is called Plexi.dxf in the Downloads:Post Files section. Mill bit is 1.5mm endmill.

The bugs on the Zigzag pocket is always available for the router. Once I was using this product and after some time my router shows me Wii Error Code 51330 and it's really a problem for me. Because these bugs really irritate me so much and not even know how to solve this problem. So I suggest to reinstall all the drivers of the router properly then you will solve it out.

@Asymtek

I found the bug and (hopefully) fixed it in the new beta version V3.42.6.
If you process the edges after the 'Pocket' job with a 'Cut' job you get the result on the 2nd picture.

Thanks again for your help to improve GrblGru. :)

Quote:

---

Originally Posted by GrblGru

@Asymtek

I found the bug and (hopefully) fixed it in the new beta version V3.42.6.
If you process the edges after the 'Pocket' job with a 'Cut' job you get the result on the 2nd picture.

Thanks again for your help to improve GrblGru. :)

---

And thank you for the amazing support. I've written a lot of automation software in my career and know just how hard it is to keep up with the bug reports. Thank you for the excellent work.

maxhowells7, the bug was in the code generation, not the router driver. GrblGru has fixed the problem in the current beta version. I applaud him for the excellent support and dedication.