My Newb Plasma Table Attempted Build

Cr@p, does that mean i have to do all the drawings for you ?
Post the gcode for that circle, lets have a look at what is there that can cause that.

tommylight wrote: Cr@p, does that mean i have to do all the drawings for you ?
Post the gcode for that circle, lets have a look at what is there that can cause that.

Haha that was pretty funny! I think that until we can figure this all out and resolve the underlying issue, I may be able to use my dxf files in inkscape and generate the gcode to cut them from inside it. I don't have a bunch of parts that need to be nested at the moment, at least nothing that has a customer waiting for it.

Sheetcam 2" circle file attached. BTW, I did cut another square using the wizard without the lead-in/out and that made no difference...same issue.

Sorry to long time:
What kind of motors? Anything "intelligent" with a deadband?
Any kind of backslash compensation?
This locks like there is somehow added a small offset to the first move. By either lcnc or by a contoller that had stopped with a deadband before.
Strange

Your gcode, no issues.
You can remove the
M52 P1
line and test again, and remove the lead in and test without it.
One of those will do the trick, hopefully.

Mike_Eitel wrote: Sorry to long time:
What kind of motors? Anything "intelligent" with a deadband?
Any kind of backslash compensation?
This locks like there is somehow added a small offset to the first move. By either lcnc or by a contoller that had stopped with a deadband before.
Strange

I'm absolutely new to all of this, so I'm not completely understanding what you mean by deadband. I agree that there is something programmed in the software that is not quite right and being triggered by one of the preamble M codes (like an offset of some kind). That's just my beginner's observation.

tommylight wrote: Your gcode, no issues.
You can remove the
M52 P1
line and test again, and remove the lead in and test without it.
One of those will do the trick, hopefully.

Attachment not found

Tried #1 in pic with M52 P1 removed. Then removed lead-in and had the same result.

I'm not plasma. When i loock on your "punch" into the metal i had a silly idea.
If i understand correct you start by switching on air. In my eyes this must give some force on z axis witch will bend and move the torch. Probably 90 degrees away from the beam.
Maybe you can test something like that by just switching air on.
Mike

Its not really surprising that using adaptive feed and slowing down travel on holes (or circles) results in different dimensions., By slowing the feedrate down, the kerf will become wider (as there is more time to burn material away)

Also even without M52, on short segments, the planned velocity is likely constrained so your commanded feedrate is never achieved so you end up with a triangular acceleration profile.

What is the feedrate and what is your max acceleration setting?

So what you should do from here is to use halscope and plot motion.current.vel and compare the commanded velocity against the actual feedrate.

Please remember that plasma is a blunt axe, not a precision machining instrument.

rodw wrote: Its not really surprising that using adaptive feed and slowing down travel on holes (or circles) results in different dimensions., By slowing the feedrate down, the kerf will become wider (as there is more time to burn material away)

Also even without M52, on short segments, the planned velocity is likely constrained so your commanded feedrate is never achieved so you end up with a triangular acceleration profile.

What is the feedrate and what is your max acceleration setting?

So what you should do from here is to use halscope and plot motion.current.vel and compare the commanded velocity against the actual feedrate.

Please remember that plasma is a blunt axe, not a precision machining instrument.

Yes, I do know about how plasma is in the real world. Although I have never had or built a plasma table before, I did have a fabrication company where we outsourced to a vendor all of our parts cut work. Some we sourced for flame cutting, some plasma, some hi-def plasma, and some laser.

All that said, the bottom line is this: the machine was absolutely not doing this before, and abruptly began doing this afterward. When I try to cut a part out it actually begins to 'stack' the errors up (the more direction changes, the more off the mark it progressively gets). I just chose to use these simple shapes for diagnostic purposes, I had not been cutting them prior to the issue arising.

The problem is not the inherent properties and tendencies of the plasma process, it is something in the software. Removal of all of the M codes from the preamble have shown the error disappears, all other things being equal (same dimension piece to be cut, same air and amperage settings, same THC, etc). At this point honestly if I didn't have the time invested in the THCAD-10 for torch height, I would be buying a different controller strictly so I can get these orders out of my queue and then take my time working this issue. But, there is no other option that I am aware of with that card. To that end, it appears working the code via Inkscape will get those pending paying jobs taken care of. But that won't help when I need to nest parts and things such as that later.

I really wish I understood the software and gcode much better, but it's just gonna take time. Thanks for the help anyway Rod...

Mike_Eitel wrote: I'm not plasma. When i loock on your "punch" into the metal i had a silly idea.
If i understand correct you start by switching on air. In my eyes this must give some force on z axis witch will bend and move the torch. Probably 90 degrees away from the beam.
Maybe you can test something like that by just switching air on.
Mike

The torch holder is very solidly attached to the Z axis. There is no play, I can actually lift up on the torch while it's attached and shift the table. It had some slop in it before which I took care of.