Another plasma component...

John,
I would like to confirm these statistic values:
Cut Time is actual cut time from beginning of x/y motion after move to cut height until torch off at the end
Cut Distance is the length of x/y motion during Cut Time
Probe Time is from pressing run until start of move to Pierce Height (includes unsuccessful probes)
Pierce Count is total number of pierce attempts including failures (basically a torch on count)
Rapid Time is time spent doing G0 moves

Would you like anything else?

Cheers, Phill.

Phill, thanks you'll be ruing the day that you decided to make this public but its one way to make a robust system!

I suspect the issue would be because of the probe height. My min soft limit is well below the slats. There is no guarantee I have a perfectly flat table height parallel with the gantry for the full length of the table.. I've always done a G92 Z0 to set the height. So I was working on probe height being above Z0. I think that means the probe height was below the material height.

Nothing goes into pause, it ends up in an endless yoyo loop and never stops.

So what has changed is the position on the table I am cutting at vs today and the other day. This leads me to another issue as I moved the material closer to the min limits to compensate for it.

I may not be doing it the right way so tell me how I should be doing it. Usually what I do is jog to the position where I want to start cutting from and issue a G92 X0 Y0. Sometimes I have added that to the beginning of my gcode. Previously the X0 Y0 position would be saved in the .var file and would persist between sessions.

With Plasmac, there is no .var file and the zero point (x0,y0) is not restored on the next startup as it used to be. I've found this an annoyance and it deviates from a standard config. If this had of worked, I could have left my ever diminishing test material at the back of the table and not had any problems.

I think the time has come to take my table off its casters and fit the leveling feet, and borrow a mate's engineers level and square the table properly.

phillc54 wrote: John,
I would like to confirm these statistic values:
Cut Time is actual cut time from beginning of x/y motion after move to cut height until torch off at the end
Cut Distance is the length of x/y motion during Cut Time
Probe Time is from pressing run until start of move to Pierce Height (includes unsuccessful probes)
Pierce Count is total number of pierce attempts including failures (basically a torch on count)
Rapid Time is time spent doing G0 moves

Would you like anything else?

Cheers, Phill.

One application might be to gather stats for quoting purposes. I would break the Pierce count up into successful, unsuccessful and total. That way you could average the probe time out for quoting. eg. if you had 1000 seconds of probe time 400 successful pierces and 100 unsuccessful pierces, you could calculate the percentage time to allow per pierce per failed pierce. So if you were using Sheetcam, you could run a job report with real production data per pierce that included an allowance for failures. This should generate a reasonably accurate production time for costing.

Also the percentage of failures might be a good indicator of remaining consumable life.

Just an aside. As a manufacturer, you really only have one KPI to measure and that is gross margin per hour. Assuming you set a target chargeout rate per hour you should be estimating your GM per job and comparing that with actual. Then you get feedback to send back into the quoting process so you are not working for nothing. This would be very powerful info if applied in a management sense. Get tit right, involve your staff and you will easily add 10% to 20% to the bottom line but that a bit out of scope on this forum... but it put a lot of money in the bank for me in a past life!

i personly as i got pre piezo pilot ACR egnithion
use only a probe once and start at 4mm the tourch then go down to 2mm and THC takes over after 1sec
as i like to cricle in to the contour it is enoph to get a sharp good cut

Rod,
I have always set X & Y at zero by using the touchoff button, I have never used G92.
I have Z zero permanently at around slat level, and home is about 5mm from max height. The intent was not to move Z, but let the component do all Z motion
I think we may have to revisit probing, something along the lines of:
Initial probe from Z top at a faster rate, find top of stock then move to probe height (which would be height above stock) then do normal probe. All subsequent probes until the end of the job would only be from probe height. This makes for a slower initial probe but I feel it would work out much better and cause less grief.
We would need to get some consensus on this before moving ahead though.

Cheers, Phill.

rodw wrote:
With Plasmac, there is no .var file

If you mean the [RS274NGC] PARAMETER_FILE in the ini file then it should be metric_parameters.txt (or imperial_parameters.txt) for all the sim configs.

Cheers, Phill.