Plasma Arc Timer?

[davek0974]

I don't think this is already featured in Mach but is it possible to add a cumulative Arc-On timer and a pierce counter??

I'm not sure if there is a way to add this feature to an existing Mach system or would it need to be written into the core code?

Is there a way to piggyback off the M03/M05 signals sent from Mach to say a little VB app running in the background that would track on signals and signal duration? The app would be easy but getting the signal to it seems difficult?

Any ideas?

It would make consumable tracking and costing easier.

[acourtjester]

If you are using SheetCam to generate your G-code you can run the report function after you run post processor and that will show all the info about your cutting operation. Pierce count is at the top of page 2

[davek0974]

Thanks for that,

I already use that feature but its not directly connected to the system - i can re-run one TAP file many times or equally run sheetcam many times and never actually cut a part.

I was looking for an automated solution

[vmax549]

There are several ways it can be done it depends on how comfortable you are working with mach3 and the screen designer and Cypress basic.

To count pierces you modify the M3 macro to do a count up to a Screen DRO. AND HAVE a reset button to rezero the count when needed. Each time the M3 (torch on) is run it adds 1 to the pierce count total.

You can also use a CB timer to track burn time. Add it to the M3 macro(STArt timer) then collect the time in the M5 (torch off) macro then add the time to a screen DRO same as the pierce count.


YOU can also use Sheetcam to ADD these items throught the post to add a total of pierces AND cut time thought the use of the #Parameters.

#500 = #500 + pierce count from Scam
#501 =#501 + total cut time from Scam

Each tiome the cut file is run it updates teh #varables in the gcode side. You can coolect the totals from the # vars and send them to a SCReen Dro.

Justa thought, (:-) TP

[davek0974]

Wow, that's interesting, slightly beyond me at present but definitely food for further research.


Thanks for that.

[vmax549]

IF yous guys need help with it I am more than willing to help out. I have been runnng a version of those things for years now.

(;-) TP

[davek0974]

IF yous guys need help with it I am more than willing to help out. I have been runnng a version of those things for years now.

(;-) TP

I would greatly appreciate any help possible

Feel free to dive in

[vmax549]

Hiya DAve do you KNOW what screen set you are running ?? Or better can you send me a copy of your screenset ?

(;-) TP

[davek0974]

Hiya DAve do you KNOW what screen set you are running ?? Or better can you send me a copy of your screenset ?

(;-) TP

I'm using a customised version of CandCNC's screen set I think it's called DTHC II - Hyt But I can get the full name tomorrow and let you have a copy.

Thanks

Dave

[davek0974]

Screenset attached in zip file.

Thanks

dave

[vmax549]

HIYA Dave, here is your new screenset with teh added stuff the stuf is on the main page lower left. You can play with the buttons just clivk on the DRO and inpout a number then press the reset button it resets back to zero

NOW if you can send me your M3 and M5 macro I can finish up the function.

(;-)

[davek0974]

Hi

That's brilliant, but I can't see the link or attachment?? I'll have time to play with it this weekend.

The M03/M05 macros are just the standard dospin() style so you could simply post up the code and I can paste it in when I get out in the shop.


Thanks again

[vmax549]

Lets try again (:-)

[vmax549]

Here are the Macros M3 M5 In the M3 macro the additional code MUST be at beginning, before your DoSpin() code.

IN the M5 macro the additional code MUST be after the DoSpinStop().

(;-) TP

[vmax549]

HIYA Dave, I noticed you were over at SheetCam asking about the pierce counts and cut time. IF you rather do the function with Scam I can show you how it is done.

You will have to mod the Scam post AND mod the mach3 M30 macro.

At the end of every cut file the M30 will update the Screen DROS with the info giving from Scam.

(;-) TP

[davek0974]

Brilliant, will be playing tomorrow

What do you reckon is best?

Sheetcam method or mach method??

I think that providing the mach method does not have any effect on the smooth running of mach then that method would be the most accurate? It's vital that it does not upset mach though, will have to test it.

On the other hand, would the Post method be safer?
I presume it triggers on the rewind command? But then if the code stops or is stopped mid way you would lose all the timings prior to that stop?

Maybe be better stick to the mach method

Are the accumulated figures retained on shutdown?

Thanks again, much appreciated.

[davek0974]

Ok, tested it and 99% success

Somehow, the accumulated time DRO gets updated with seemingly random values whenever the Stop button is pressed on the screen or at the end of a run, not sure why but issuing an M05 command in the MDI does the same thing.

Can that be fixed?

If not then maybe the sheet cam Post option is the only way?

Any thoughts?

Thanks again for looking at this BTW

[davek0974]

Thinking along, is it possible that the M03 macro could also set a variable/flag so that the M05 stop timer command only has effect if that flag is set first????

That would make it a sort of one-shot affair and any random pressing of the stop etc will have no effect.

Just a thought

Or is it better to go for the sheetcam option?.

[vmax549]

PK if the M30 is updating the dro THEN go to Config , General config and look on the center LH side and see IF the function"Program end, M30, or Rewind, "Spindle off"" is checked if so uncheck it.

Also I can also monitor the Torch ON LED from the M5 and only allow the update from the M5 IF the LED is on(torch on ).

(;-) TP

[vmax549]

Hiya Dave, Try this setup. With this you can recheck the gen config item . Here is a screenset AND the new macros.

(;-) TP

[davek0974]

Hi

well I would try it if the attachment was there

Monitoring the torch led would likely solve it.

Thanks

Dave

[vmax549]

OK try this

(;-) TP

[vmax549]

Monitoring the torch led cause a problem with a M5 delay when used.

THis solution fixed that problem.

(;-) TP

[davek0974]

Woohoo! 100% success

Works perfectly!

That function is exactly what was needed and should prove to be extremely useful.

Many thanks for working on it, much appreciated.

Is it possible you could document what you did in this thread?
I know a couple of other users who would like it too plus it would be helpful for future reference to this thread.

Thanks again

Dave

[vmax549]

Hiya Dave, I will write up a small description of how it works.

You can ALSO have it write all the data to a Text file along with dates and times that each consumable was replaced.

That way you can see a running total at each change out of the consumables.

Here at the shop it writes to a full screen setup for tracking consumables AND writes to a Text file that can be printed out OR just looked at when you want to.

IF you need more gizmos for plasma let me know (;-) I have helped develop MANY things for plasma USE over the years .

(;-) TP