[Bashidap]

Attachment 181019

If the cutting speed is to high, Mach takes a short-cut. The rounded edges are supposed to be straight. It probably has to do with the general configuration (constant velocity) or with the available computer memory. It doesn't happen always. That is why I think that it can be a memory problem as-well, cutting large files. Can anybody give me a good advice to avoid this. I annexed a screen-shot of the general config.

Thanks!Attachment 181020

[keebler303]

When is the rounding happening? When the cutter goes from one letter to the next? You can try turning off constant velocity and see if that helps. You could also put in a G4 dwell at a problem spot to see if that helps you out.

Matt

[Bashidap]

It's a "Lace" strategy. It happens going in the Z direction.
What does this G4 do and where in the G-code do I put this?

[keebler303]

It is a dwell as I said, you can google it for syntax.

CV mode normally affects the path in tight corners. If you ask it to dwell in the corner, it would go to the corner, dwell, then resume with the Z move. The location in the code should be the line after the line which commands the bit to the "corner" of the toolpath.

Matt

[Bashidap]

Thats not easy to do in a generated G-code, at leaste 5 Mb of lines. There must be a better solution in the adjustment of mach.

[keebler303]

I said you can try turning off CV mode. The G4 idea is for identifying the problem, not solving it!

[lancut]

Try "exact stop" setting.

[Bashidap]

Can you explain why it doesn't happen always. In general with big files.

[Bashidap]

Result at half the speed!

[jeffery926]

What version of Mach3 are you running? There are some issues with CV in older versions. If your not running R3.043.066, try loading it. Also looking at your config, you are not using any CV distance tolerance. Try enabling that and play with the settings. I'm running very large files (over a million lines of code) and I do not use stop CV on angles, but I do use CV distance tolerance.

[Bashidap]

Sounds interesting! Have you got a screenshot of you general config?

[Bashidap]

I'm still running version R3.042.020 Lest hope that this upgrade will be the solution!

[Bashidap]

I'm running very large files (over a million lines of code) and I do not use stop CV on angles, but I do use CV distance tolerance.

Hello Jeffery, What do you use as distance tolerance? I updated now to the last version and want to do some tests.

[jeffery926]

I'm laser engraving 8bit shades with my machine. I set the CV distance tolerance at the largest move any of the axis's will go at one time. My setting is .0255, but your setting may be different based on the G-codes your running. Disable your spindle and just do some air cutting and play with the setting and see what works best.

[Bashidap]

I made it 1. now, but I'm working in mm. Less looks very safe, but slow. First I'll be trying this. Thanks!

[jeffery926]

Well, I kinda figured you was using MM, so the settings will be based on your machine, units and g-code. If it runs to slow, keep increasing that number until it runs like you need it.

[Bashidap]

What happens with the G2 G3 codes if you change this?

[jeffery926]

I do not have a clue on that one. Try it. I'm only engraving with my Mach3 machines.

[Bashidap]

Thanks

[jeffery926]

I'm curious. Have you resolved your problem and did upgrading to the latest version of Mach3 and the CV settings make a difference?