Nan - voltage

rodw wrote: Actually this might be better

unlinkp these plasmac.comp pins

Code:

pin in float arc_voltage_offset "offset to set arc voltage to 0 at 0 volts"; pin in float arc_voltage_scale "scale to convert arc_voltage input to actual volts";

setp them to the values used in your gui.
This would take NML out of the equation as values are not set by gui variables.
If it still happens, then its most likely a plasmac bug and you have isolated that to the lowpass code.

I don't see how NML is used in any of this, all we do is set and get HAL pins.

but you are setting hal pins via GUI variables so won't the GUI connect to HAL via NML?
I am trying to avoid that part of linuxcnc for now.

I'm a little late to the party. Was running a larger job and didnt take the time to post after Testremos mentioned he started a thread on it. Phillc54, this issue seems to be only in 2.9. Not sure if that helps or not. When my machine was done, we stepped back to 2.8 to get rid of the issues (which was just a trial that didn't work). The nan issue disappeared. I updated to 2.9 again for the FWD and REV buttons as they are very handy on larger runs. So it came right back. Also, dont remember if Tesremos had the nan issue in a virtual machine or not.

PurduePete wrote: This issue seems to be only in 2.9. Not sure if that helps or not. When my machine was done, we stepped back to 2.8 to get rid of the issues (which was just a trial that didn't work). The nan issue disappeared.

So it does not seem to be a Plasmac Issue but instead a Linuxcnc bug. It could have something to do with the move to Python 3.0 on master perhaps.

Very foggy on this, but i have seen this nan thing when i did an update of LinuxCNC but did not update the PlasmaC config, it was around .148 version i think, give or take a bit, and after updating the config everything was back to normal.
I use Master for everything.

We did not have issues when on v.144 or whatever. Just when we updated plasmac. But could be a problem with Linuxcnc.