Torch On HAL Pin when using 7i76e

snowgoer540 wrote: You can use the pmx_test.py script to help you identify the correct port. Its usage is covered in the user guide.

I suspect it's going to take issue with your ohmic enable HAL pin next as you are feeding a bit output to an encoder.

Where might I find the pmx_test script?

Any suggestions regarding the HAL pin(s) I should be using?

txtrone wrote: This is what I have, anything look out of whack?

Where might I find the pmx_test script?

There is a hint in the user guide.
linuxcnc.org/docs/2.8/html/plasma/plasma...-guide.html#pm_comms

phillc54 wrote:

txtrone wrote: This is what I have, anything look out of whack?

Attachment not found

Where might I find the pmx_test script?

There is a hint in the user guide.
linuxcnc.org/docs/2.8/html/plasma/plasma...-guide.html#pm_comms

I ran the pmx_test script. Found the port, S1 in my case, I can change the drop down box on the test screen and verify it is changing modes on my plasma unit (Normal, CPA, Gouge) ... I changed the ini file to /dev/ttyS1 ... got the following errors.

Error report created by /usr/lib/tcltk/linuxcnc/show_errors.tcl:

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.8.0
Machine configuration directory is '/home/newpc/linuxcnc/configs/mark_i'
Machine configuration file is 'mark_i.ini'
INIFILE=/home/newpc/linuxcnc/configs/mark_i/mark_i.ini
VERSION=1.1
PARAMETER_FILE=imperial_parameters.txt
TASK=milltask
HALUI=halui
DISPLAY=axis
COORDINATES=XXYZ
KINEMATICS=trivkins coordinates=XXYZ kinstype=BOTH
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
twopass:invoked with <> options
twopass:found ./mark_i.hal
twopass:found ././plasmac/plasmac.tcl
twopass:found ./mark_i_connections.hal
twopass:pass0: loadusr -Wn pmx485 pmx485 /dev/ttyS1

Could not open /dev/ttyS1 for Powermax communications

twopass: Error in file ././plasmac/plasmac.tcl:
pmx485 exited without becoming ready
Shutting down and cleaning up LinuxCNC...
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
27117
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

snowgoer540 wrote:

tommylight wrote: Ohmic Probe Enable must be an output, not input.

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.

Would it be more straightforward to do away with "hypersensing" and use the relay method? I don't care either way... just want to get it running. thx

phillc54 wrote:

txtrone wrote: This is what I have, anything look out of whack?

Attachment not found

tommylight wrote: Ohmic Probe Enable must be an output, not input.

What does Type and Dir mean on HAL Show in my attached screen cap?

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

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

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

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.

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.