EasyProbe error

More
23 Sep 2025 00:24 #335312 by ckuecker
EasyProbe error was created by ckuecker
I'm trying to get EasyProbe running on my mill. I had an older version running, but am having problems with the probe signal.
The report file shows: Probe_postgui.hal:14: Pin 'hm2_7i96s.0.gpio.040.in_not' was already linked to signal 'probe-in'
Probe_postgui.hal has:
#
Probe signal and LED control (see readme.md)
# dbounce_probe.in must be linked to the probe tool input of the interface card
 
setp  dbounce_probe.delay      [PROBE]DEBOUNCE_TIME
setp  xor_probe.in0            [PROBE]PROBE_SWITCH
 
net   probe-raw                dbounce_probe.in             <=    hm2_7i96s.0.gpio.040.in_not
net   probe-switch             dbounce_probe.out            =>    xor_probe.in1
net   probe-signal             xor_probe.out                =>    motion.probe-input pyvcp.probe_led

I can't find any other instances of probe_in. Where might it be?

 

Please Log in or Create an account to join the conversation.

More
23 Sep 2025 14:03 #335325 by ckuecker
Replied by ckuecker on topic EasyProbe error
I found the probe signal problem and got the EasyProbe screen to come up.
Something is still wrong - clicking any probe button gives an error:
EOF in file: /usr/share/axis/images/axis.ngc seeking o-word: 0<probe_x_minus> from line: 0
I also do not have the Probe Signal LED working. So, my "fix" of the probe input error must have broken something that does not cause an error message on startup.

Please Log in or Create an account to join the conversation.

Time to create page: 0.610 seconds
Powered by Kunena Forum