Advanced Search

Good evening gentleman,
I am almost done with my new setup (printnc "pro", mesa 7i76eu, probe basic, jianken ATC) and everything seems to be working now, except the tool length measurement.
When I start a measurement with G38.2.... and then press the toolsetter with a finger (just to test it), the system errors out with "probe tripped during non-probe movement".
So it recognizes that the toolsetter is triggered, but for some reason it thinks its the 3d probe...  

This is how my probe and tls signals are linked:

# --- PROBE-IN ---
net probe-in     <=  hm2_7i76e.0.7i76.0.0.input-08
# --- TLS-Normal-IN ---
net tls-in       <=  hm2_7i76e.0.7i76.0.0.input-09-not

addf or.probeortls servo-thread
net probe-in or.probeortls.in0
net tls-in or.probeortls.in1
net probe-tool or.probeortls.out
net probe-tool motion.probe-input

What am I doing wrong ?

Here is my full config...
github.com/SebastianMusser/LinuxCNC/tree/main

regards
Sebastian

Another remark.. not sure if that me misunderstanding anything or if its another bug, but witih MesaCT I generated a config to set my outputs 0-7 to sinking and 8-15 to sourcing.
This were the generated lines:
setp hm2_7i76e.0.7i76.0.0.output_sink 0xff00
setp hm2_7i76e.0.7i76.0.0.output_source 0xff

isnt this "the wrong order"? imho this sets 0-7 to source and 8-15 to sink.. right?

That's a bug with the 7i76eu I/O section. I'll fix that.

JT

good afternoon!
today I played around with MesaCT for the first time, and I saw that the generated configuration (for my 7i76eu) has a different naming / nomenclature for my outputs than pncconf...

pncconf outputs lines like this:
net dust-removal-out motion.digital-out-03 => hm2_7i76e.0.7i76.0.0.output-03

while mesact creates these lines:
net flood-output iocontrol.0.coolant-flood => hm2_7i76e.0.gpio.031.out

where does this "gpio" come from? is this redundant or did I do something wrong in the tool?

regards!