Hypersensing with THCAD - better way to do ohmic sensing

rodw wrote:
I will check my wiring is as I documented later today.

I'm pretty sure the issue is water entering the torch tip and creating a circuit when we don't expect one with a water table. I know I have sometimes cleared a stuck probe (with a low off threshold) by either a Plasmac torch pulse to get air flowing or flicking the airflow switch on my plasma cutter.

The behaviour on a dry table now is exactly how it was when we first put this together.

That sounds likely. I think I'm having ground issues as well. I'll have to take a look at my wiring again and clean it up. Depending upon where I placed my "table (V-)" wire, I would sometimes get 24v on contact, and then only 14v on contact when it was attached somewhere else. This was the first time ever seeing that.

So I filled the water tray and tested probing before cutting anything and its exactly the same as I reported before:
probe not touching: 0 volts
probe touching table 24.07 volts

I realised now that I did not have the plasma turned on So I'll try and remember to check tomorrow again.

I thinks we've proved its a wet torch (for me anyway). I would suggest pulsing the torch before starting your job so that there is air flowing through the torch to stop water egress.That was the intended function.

I think I may be getting somewhere. I see the light!

I stripped out all unecessary connections to my cabinet (sensors, steppers, etc) just to have a barebones setup. 7i76 connected to 5i25 in PC, 24v logic PSU on, THCAD-5 connected. Spindle connector disconnected.

I started everything up and THCAD-5 was working fine. Reading ~0v at idle. Touched the material and 24V. So far so good. Pulsed the torch (not over water) and re-checked everything. All is well, ohmic sensor still triggers and still at 0v when not touching. Then I pulsed over water and sure enough, ~16-18v was back after pulsing. It would remain somewhat constant when the air was not running, but if I pulsed the torch (again, not over the water), it would go down quite quickly, about 1v every 7 seconds or so. This confirms what you were suspecting about water shorting out the torch internally. It is quite easy to work around so that is fine.

However, I realized that by pressing the ohmic test button in axis, it would still light up the ohmic light even though the current voltage was below my ohmicsense.ohmic-low value (20v). I found out that 1v was the trigger point. If the ohmic-volts was above 1v, it would throw ohmic true. Now to investigate where this is coming from, because in my hal file I definitely have ohmic-low at 20v, but it just doesn't seem to be using it.

I would appreciate a second set of eyes looking over my hal files.

hypersensing.hal is where I configure the ohmicsense comp connections. Note I commented out ohmic_dev component which was my modified version, as well as some collision detection connections I was working on.




Rod, could you post your hal files pertaining to your setup?

I've attached my ohmic hal file. Note that the encoder is set up elsewhere so I added that to the example in the plasma primer. It does not have the threshold values I set the other day.

If the probe comes on when it shouldn't then the bug has to be the code in the component.
Do the pins show up correctly in Halshow when this happens?
Can you post your revised component again?
I'll revisit the logic. I know I made a quick change at my end too so I need to revisit that when I am next with my machine.

Anyway, at least we have both confirmed the issue is due to water splash.

In your testing, there is a rather cool component called sim_pin you can add to your ini file so you can change the thresholds on the fly. See: linuxcnc.org/docs/devel/html/man/man1/sim_pin.1.html

Rod, as of right now I'm back to using the stock component. (Attached)

I was able to brute force the component into working properly by changing the ohmic_low to a set value, i.e. 20


Then I did and it turned off at 20.0v

This will work until I investigate why it's not being pulled from the hal file to begin with.

Out of curiousity, why does there need to be a ohmic_low pin? Is it for hysterisis? Can the ohmic_threshold be enough

halshow confirms that ohmic-low is being set at what was in my hal file

Shows current ohmic-volts @ 12.6888V
ohmic-low @ 22
ohmic-threshold @ 23

ohmic-on true