- Posts: 12160
- Thank you received: 0
Hypersensing questions
Please Log in to join the conversation.
net plasmac:ohmic-enable plasmac.ohmic-enable => ohmicsense.is-probing
Without it, the ohmicsense.is-probing never went true while probing
Please Log in to join the conversation.
So you should be good to go after checking the thresholds.
Please Log in to join the conversation.
- snowgoer540
- Topic Author
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
rodw wrote: What is happening to plasmac:ohmic-enable?
It should go true when you are probing and it needs to be connected to the ohmic component. via the debounce pin that we unlink.
Neither of them ever changed that I noticed.
Please Log in to join the conversation.
- snowgoer540
- Topic Author
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
rodw wrote: Sorry, In my config, that signal passes through a debounce component so that is what I unlinked. Maybe yours does not debounce it.
So you should be good to go after checking the thresholds.
I'm pretty confused. I attached my hal files and ini files in an earlier post, but they exactly match your space ship, and the primer you sent. The float and break away pins debounce on my setup, but I'm not sure I understand why you have to debounce this ohmic system?
At any rate, the thresholds are set correctly, and it defintely still doesnt work.
Please Log in to join the conversation.
- snowgoer540
- Topic Author
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
Uthayne wrote: I had to edit the line to add plasmac.ohmic-enable pin
net plasmac:ohmic-enable plasmac.ohmic-enable => ohmicsense.is-probing
Without it, the ohmicsense.is-probing never went true while probing
Ok, I can try that...
Please Log in to join the conversation.
- snowgoer540
- Topic Author
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
Uthayne wrote: I had to edit the line to add plasmac.ohmic-enable pin
net plasmac:ohmic-enable plasmac.ohmic-enable => ohmicsense.is-probing
Without it, the ohmicsense.is-probing never went true while probing
That fixed it!
I wish I knew what that was though LOL. How did you know to change that, and what exactly is it doing?
Why does Rod's config work without it?
Please Log in to join the conversation.
I figured it out by monitoring which plasmac pins went true when the ohmic test button was pressed which simulates a probing condition.
I could be wrong but as far as I understand it, net plasmac:ohmic-enable => ohmicsense.is-probing doesn't connect the ohmicsense.is-probing pin to anything. plasmac:ohmic-enable is the connection name, there needs to be a 3rd entry there. I could be wrong about this but I thought that was how basic connections work.
I'm curious to see how you fare from here. Rod mentions that with a water table you need to set the ohmic-low state pretty high (22-23v) due to water getting stuck in the torch and shorting it.
Whenever I get significant water intrusion into the torch like after a cutout (single line/internal cuts seem to be fine, just at the end when the air is blowing directly into the water and a lot of splashing occurs), ohmic-volts will read 23.5 or thereabouts, but with up to a volt of "noise". This causes it to fluctuate above 24.00V even. My ohmic cap to material short condition gives a pretty constant and stable 23.97-24.00v. It's the "non-contact" condition where I usually get up to 1v variation which makes it hard to set the low value, especially when it goes above 24v
Please Log in to join the conversation.
- snowgoer540
- Topic Author
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
rodw wrote: Sorry, In my config, that signal passes through a debounce component so that is what I unlinked. Maybe yours does not debounce it.
So you should be good to go after checking the thresholds.
Thanks for all the help!
Not sure why the edit makes it work, but I'm happy it does.
Please Log in to join the conversation.
- snowgoer540
- Topic Author
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
Uthayne wrote: Not sure why his works without it, unless he has more hal connections somewhere else.
I figured it out by monitoring which plasmac pins went true when the ohmic test button was pressed which simulates a probing condition.
I could be wrong but as far as I understand it, net plasmac:ohmic-enable => ohmicsense.is-probing doesn't connect the ohmicsense.is-probing pin to anything. plasmac:ohmic-enable is the connection name, there needs to be a 3rd entry there. I could be wrong about this but I thought that was how basic connections work.
I'm curious to see how you fare from here. Rod mentions that with a water table you need to set the ohmic-low state pretty high (22-23v) due to water getting stuck in the torch and shorting it.
Whenever I get significant water intrusion into the torch like after a cutout (single line/internal cuts seem to be fine, just at the end when the air is blowing directly into the water and a lot of splashing occurs), ohmic-volts will read 23.5 or thereabouts, but with up to a volt of "noise". This causes it to fluctuate above 24.00V even. My ohmic cap to material short condition gives a pretty constant and stable 23.97-24.00v. It's the "non-contact" condition where I usually get up to 1v variation which makes it hard to set the low value, especially when it goes above 24v
Interesting, how are you watching the voltage while a program is running? Just with the hal show?
Please Log in to join the conversation.
