Torch On HAL Pin when using 7i76e

tommylight wrote:

txtrone wrote:
Does that mean the aforementioned 'encoder input-b' is actually a 'bit out' or am I misunderstanding?

It is for LinuxCNC, but not for us and not for the encoder, it is an input.

In Phillc54's response he marked up the image to call attention to 'bit out' and 'input-b'. I took that to mean there is a correlation between these two. Can you suggest an encoder output that might be suitable?

This went sideways rather quickly...
The "Ohmic Probe Enable" pin in the configurator must be a physical output that is wired to the relay that activates the power going to the sensing part of THCAD.
Any normal output can be used for that.

snowgoer540 wrote: True, but it looks like he's attempting "hypersensing", so he will need one of the ohmic components. There's a few threads around here that explain it better than I can off the top of my head.

As I said, you need to use the ohmic.comp (included with LinuxCNC). Or ohmic2.comp, or ohmic3.comp (in the link below, as well as how to install them).

Rod has posted examples of how to hook up the hal stuff. Including his own .hal files.

Here's at least one thread to read: forum.linuxcnc.org/plasmac/38848-hypersensing-questions?start=0

It details my (and a few others by the end) journey into "hypersensing", and as such has a lot of answers to questions with regard to getting it working, how it's evolved, and why it is the way it is.

It's 28 pages long, but it's worth the read.

In a nutshell, you need to pass the ohmic probe output from PlasmaC to the ohmic component. In addition, you need to pass the encoder velocity to the ohmic component. The output of the ohmic component will be passed to the PlasmaC ohmic input.

tommylight wrote: Type is the type of pin, be it bit, float, s32 etc.
Dir should be the direction of the signal looking from the LinuxCNC point of view. Might wana check this as i am a bit cloudy...
As for coms, might need to add the user to dialout, here is one of the many topics about that:
arduino.stackexchange.com/questions/7471...d-to-group-dialout-o

That solved the communication problem with my HyperTherm!

Now I am sifting through 28 pages of hypersensing evolution...

snowgoer540 wrote:

snowgoer540 wrote: True, but it looks like he's attempting "hypersensing", so he will need one of the ohmic components. There's a few threads around here that explain it better than I can off the top of my head.

As I said, you need to use the ohmic.comp (included with LinuxCNC). Or ohmic2.comp, or ohmic3.comp (in the link below, as well as how to install them).

Rod has posted examples of how to hook up the hal stuff. Including his own .hal files.

Here's at least one thread to read: forum.linuxcnc.org/plasmac/38848-hypersensing-questions?start=0

It details my (and a few others by the end) journey into "hypersensing", and as such has a lot of answers to questions with regard to getting it working, how it's evolved, and why it is the way it is.

It's 28 pages long, but it's worth the read.

In a nutshell, you need to pass the ohmic probe output from PlasmaC to the ohmic component. In addition, you need to pass the encoder velocity to the ohmic component. The output of the ohmic component will be passed to the PlasmaC ohmic input.

Just sorted through the 28 pages. I am a bit confused on ohmic comp versions and if I have one installed already or not. How can I check to see if ohmic comp is installed already?

Also, what is the verdict on using a relay to interrupt the power supply?

tommylight wrote: This went sideways rather quickly...
The "Ohmic Probe Enable" pin in the configurator must be a physical output that is wired to the relay that activates the power going to the sensing part of THCAD.
Any normal output can be used for that.

Is the relay that sends power to THCAD optional?