tommylight wrote:

I have no power for the last 3 days so using the phone makes it dificult to quote stuff with this editor, but in short:
-i have PlasmaC in daily use in over 10 machines, users got used to occasional stops and are OK with it, luckily rareley happens, i think it is 2.8.4 version.

Tommy, the last commit to the PlasmaC component for 2.8 (that was not just a version rev) was December 15, 2020. I'm not sure why you expect anything from that branch that may be a bug to get fixed. I can tell you for sure that I have 0 interest in squishing bugs in 2.8.

Certainly many improvements have been made to PlasmaC in 2.9. That said, even from a Qt/PlasmaC perspective, we haven't pushed any changes to 2.9 since ~August 21, 2024. But it's worth noting that component hasn't seen a ton of changes in 2.10.

-PlasmaC has 4 or 5 ways of disabling the THC, most are useless, except VAD, and void lock sometimes. Right now i can not think of any other valid use case.

From the 2.10 component code:
Main GUI disable
Disable(and enable) via G-Code
Velocity Anti Dive (sometimes called Corner Lock)
Void Lock
Mesh Mode/Ignore Arc OK

Personally don't see any of those as useless, but you also aren't required to use any of it.

I will tell you that I am the reason for Mesh Mode/Ignore Arc OK, because it would be impossible to cut expanded metal otherwise, something my Hypertherm is very capable of, and I do use this feature from time to time.

BTW default should be at 60-70%, not at 95%.

For QtPlasmaC, Cornerlock/VAD is defaulted to 90%. It's on the PARAMETERS tab as "VAD Threshold", luckily you change it once, click "SAVE" and it stays as your new default . It's literally impossible to make a default that works for everyone. If I change it to 65%, there will be other users telling me it should be 90%. That's why it's tunable.

-what should i monitor for the issue where the torch keeps going down till float switch triggers during cut

If you are talking 2.9 or 2.10, then I would say without knowing what is causing it, I would just be guessing. But, I would want to know, is the voltage staying constant, and the plasmac component is commanding the THC down anyways? Is my voltage erratic? Etc.

As a start, I'd plot plasmac.arc-voltage-in with plasmac.move-down, plasmac.move-up, and plasmac.current-velocity. If you're telling the component what voltage you want it to shoot for, then I'd add plasmac.cut-volts. If you're using auto-volts then I'd want plasmac.target-volts.

happens often and ruins the nozzle. More often in QtPlasmaC but that might be just luck

Phill added plasmac.low-cut-volts as an attempt to prevent this. You could try setting that to prevent it form diving into the material.

-what should i monitor for the issue where the machine moves to a cut position and just stays there? This happens sometimes even when doing a manual cut where pressing F9 shows the machine running on screen but nothing moves. DRO does not change, machine state does. Again this happens a lot on QtPlasmaC, do not recall this happening on PlasmaC so might be a QT thing.

Again, I'd want to know if motion.eoffset-limited goes true when this occurs. I am also curious what state it's stuck in, so I would want you to turn on plasmac.debug-print before starting any cutting, etc. and copy and paste the terminal output from when it hung up.

-i think i have an old config for QtPlasmaC on a laptop for my machine, i can upload that if you think it might help.
-i absolutely have no issues with intelectual property, i do and will post everything i do personally, as can be seen from many posts here, i am strictly Open Source everything, and i did reject any job requiring me to sign an NDA
Ooops, not very short

If you have it, I'd look at it. Sure.