Another plasma component...

Yes I checked an old config and that is set in the ini file. So what does plasmac do to reset the G92 X0 Y0 Z0 data? I'e not come across that before.

rodw wrote: Yes I checked an old config and that is set in the ini file. So what does plasmac do to reset the G92 X0 Y0 Z0 data? I'e not come across that before.

OK, I see now your mertric_startup.ngc issues a G92.1. Why is that? Will it break something if removed?

Not sure, only one way to find out.

Cheers, Phill.

phillc54 wrote: Not sure, only one way to find out.

Cheers, Phill.

Just navel gazing at home.

I might have another go in the morning.

Let me know your thoughts on this idea. I think I need to probe each corner of my table and pick the highest point and see how far above the minimum soft limit the table is. Then add the thickest material I can cut (say 25mm) Then add a probing distance above that. How high above the material should the probe height be? Say 10mm , 20 mm or something else?

The default probing speed is 1000 mm/min. Does that work for you?

That sounds good to me, I think 10mm should be OK. That 1000mm/min was a mistaken leftover from testing, probably 300-400 would be safer.
That is a hangup from trying to support too many GUI's.

Cheers, Phill.

Edit: I meant to tell you that I normally use G10 L2 to set X & Y zero to the stock and I clear temporary offsets on machine startup.

Guys

I run my system like a mill. I jog the torch to X0,Y0 on the work piece and set the G54 X & Y offsets from the touchoff screen. I have a permanent G54 Z offset that puts the top of the work sheet within the probing range. I think that Gmoccapy likes to work this way. I tried using G92 before and it just shifted some machine zero if I recall. the G92.1 clears all previous G92 offsets, usually called at end of Gcode file to leave machine in known starting state. What you are doing is just shifting the machine zero to the work piece origin rather than setting a work piece origin in G54. This is an old legacy Mach trick for simple tables without homing that didn't use soft limits.

I had probing problems with Plasmac until I got my Z limits correct for my actual table condition instead of no errors when making Gcode Z moves when probing from Gcode. You will get better probing by moving slowly so set the probe distance for the anticipated thickness of the material so it can be as short as possible, I probe at 5ipm right now. If you set it for the thickest you can cut you will will waste time probing.

Phill

Cut time = arcok AND movement in X & Y
Cut Distance = arcok AND leading edge distance to go ( transition from 0 to some number) , I tried to use time and feedrate and it was way off. The TP should do a good job at calculating the actual cut distance so I think the key is getting it out. I think it is easy in plasmac because on cutting moves all Z movement is handled outside of the TP so DTG is only a 2D move.
Probing time = ohmic probe enable, of course this doesn't work for float switch probing so I guess time while at probe speed?
Pierce count = number of times torch on goes true.

At the end of the day the actual times are good for job costing and the pierce count and distance cut for estimating consumable life left. SheetCam is ok at estimating but doesn't account for machine acceleration which can have a huge effect when cutting art work ( non rectilinear pieces).

John

John