Pausing at Nodes
Please Log in or Create an account to join the conversation.
From:
G64 P0.01 Q0.001 (tracking tolerances: 0.01")
To:
G64 P0.01 (tracking tolerances: 0.01")
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
if scale == metric then
post.Text (' G64 P0.254 Q0.025 (tracking tolerances: 0.254mm)\n')
else
post.Text (' G64 P0.01 Q0.001 (tracking tolerances: 0.01")\n')
end
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Sure, it is in the current postprocessor at line 72, it looks like:
just change it so it looks the same.if scale == metric then post.Text (' G64 P0.254 Q0.025 (tracking tolerances: 0.254mm)\n') else post.Text (' G64 P0.01 Q0.001 (tracking tolerances: 0.01")\n') end
I have revision F if that makes a difference
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
- snowgoer540
- Away
- Moderator
- Posts: 2381
- Thank you received: 775
It seems to have been a sheetcam issue with import tolerances being too small!
Happy we finally got this figured out!!
To anyone following along, we changed this import setting in sheetcam:
Max detail reduction error
Per sheetcam manual:
Max detail reduction error
Some drawings consist of a large number of very small line segments (especially polyline curves converted to DXF). This can slow down processing and produce very large g-code files. It can also slow down machining. SheetCam tries to reduce the number of lines when it loads the drawing. Removing lines introduces small errors and this value is the maximum allowable error. For Plasma cutting you can afford to have quite a large error (say .020"). The setup wizard adjusts this value to suit.
Please Log in or Create an account to join the conversation.