Another plasma component...

Rod,
The way it displays at the moment is once plasmac.thc-active turns on it stays on for the duration of the cut.
plasmac.kerfcross-is-locked will turn on when it sees an over voltage and turns off when the voltage has returned to 'normal'
While plasmac.kerfcross-is-locked is on then thc is disabled so that is the pin to watch.

Cheers, Phill.

Rod,
As long as you use F#<_hal[plasmac.cut-feed-rate]> for the feed rate cornerlock should work well as plasmac uses this feed rate for its cornerlock calculations.

Cheers, Phill.

Edit: Do you use a lowpass on your arc voltage?

Yes, I'm using the plasmac feedrate now I have a nice Sheetcam post processor!

I'll do some more plots when I get a chance. I found that opening halscope in Gmocappy actually saves the pins you connect.

phillc54 wrote: Edit: Do you use a lowpass on your arc voltage?

No I don't. I included it in my scale THCAD component very early in the piece because PCW often suggests it. Dewey Garrett on the other hand did not recommend any filtering as it would interfere with PID response and that was my experience when I played. I still have my component installed to decode the torch volts so I think I might see if I can do a plot of dV/dT over your data to see if it could sense the void any quicker. Let me go and lok to see if I have a plot done in the past.

Phill, this is the only one I have showing dV/dT



It looks like it idles along at around 1200 volts/second (variation of about 1.2 volts per servo cycle on a stable cut) under normal cutting conditions and then spikes almost immediately to about 10,000

With Plasmac holding the THC, then it will be much easier to get some data

Phil, On this plot it looks like your kerfcross-is-locked is true before we encounter the kerf and the voltage starts to rise. the dV/dT is idling along at about 3200 before the void. So holding the thc if it rises above 4-5000 would be a good threshold. The peak is up around 65000 v/sec

Anyway as usual, 1 cut will give a few days of thinking.... You really need to explore this in halscope as screen dumps only tell half the story as you can't rescale and explore as you can in halscope

oops wrong graph and I could not edit it so read this one