ZigZag operation for HeeksCNC doesn't cut the same depth on surface of solid

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Created a 3.5" x 4" x .25" solid to run on .5" aluminum stock.
2. Selected cutting depth of .030 for each pass.
3. Tried both methods of cutting "one way" etc... and had same results.

What is the expected output? What do you see instead?
The green lines (tool path) appear to have been generated corrected but when 
you run the gcode on the mill the gcode alters the .030 cutting depth i.e. it 
doesn't cut .030 across the entire surface. Only the first couple of cuts are 
at .030 and the rest of them are just a couple of thousands. You can watch the 
end mill drop down to the proper depth but then it comes back up to only take 
off a couple of thou. On the second pass the same area's that got cut to .030 
the first time will again get another .030 removed and the area's that only had 
a couple of thousands revmoved will again only get a couple of thousands 
removed. I looked at the gcode to verify the inconsistancy with the cutting 
depth and it's it quite obvious that the depth was generated wrong in python. 
I'm using EMC2 and monitoring the toolpath graphic (green lines changing to 
red)while the gcode is running makes it appear that the cuts are going to the 
proper depth. 

What version of the product are you using? On what operating system?
I'm using the latest version of the download. 0.13.1 on a windows XP SP3 box 
with all the latest updates.

Please provide any additional information below.

Original issue reported on code.google.com by dunamis1...@yahoo.com on 10 Jun 2010 at 11:33

[GoogleCodeExporter]

I added the Gcode file to show the very odd Z depth variance in the gcode. The 
depth should remain the same until the first layer is cut before dropping down 
to the next cutting depth.

Original comment by dunamis1...@yahoo.com on 13 Jun 2010 at 4:21

Attachments:

• [Gcode file.txt](https://storage.googleapis.com/google-code-attachments/heekscnc/issue-219/comment-1/Gcode file.txt)

[GoogleCodeExporter]

I think this got fixed.

Original comment by danhe...@gmail.com on 24 Mar 2014 at 5:06

• Changed state: Fixed