Single input for overtravel

Hello,
I am changing the CNC on a TRAUB milling machine and after looking at the documentation notised that overtravel is indicated by only three switches and they are fed to the coil of a relay . So the CNC only sees overtravel signal but no indication on which axis or max/min .
Is there a net in .hal which is overtravel only and does not specify anything else ? Rewiring will take far too much time .

Hi

It is quite normal to have all limit switches in series feeding one pin.

The usual hal file solution is to create a signal called all-limit which is connected to the signal pin

net all-limit <= parport.0.pin-13-in

Then link all the limit switch pins to it

net all-limit => axis.0.neg-lim-sw-in
net all-limit => axis.0.pos-lim-sw-in
net all-limit => axis.1.neg-lim-sw-in
net all-limit => axis.1.pos-lim-sw-in
net all-limit => axis.2.neg-lim-sw-in
net all-limit => axis.2.pos-lim-sw-in

Physically the switches are chained in series and there is a one wire signal that goes to (in this case) parport.0.pin-13-in

Any break in the signal and the error is activated.

If you have NO contacts instead of NC, you will have to reverse the logic, but I assume if "they feed the coil of a relay" they must be in series not parallel, or it would take all 3 erroring to produce a fault!

regards

Thank you !
Where can I find a list of signals ?

Take a look at show pin...
linuxcnc.org/docs/html/hal/tutorial.html

Rick G

Where can I find a list of signals ?

The signals can be called anything you like, as long as they are not reserved words or names already in use for pins

I just used the signal name all-limit just because that is the one that stepconf and pncconf use when generating configs with grouped limits, so you may have already seen it.

Think of a signal as a hub.

There is 1 feed only with data from an OUT pin ( like a drive shaft into the hub ), but you can attach many IN pins to it as you like, to share this data ( like spokes on a wheel driven by the hub )

regards

just because that is the one that stepconf and pncconf use when generating configs

all-limit was predefined and worked immediately .
net all-limit => axis.0.neg-lim-sw-in
net all-limit => axis.0.pos-lim-sw-in
these lines were not needed .
I am interested in a list of signals that pncconf creates automatically and to simply tap into it .

I am interested in a list of signals that pncconf creates automatically and to simply tap into it .

There is no list per se.

The easiest way is to create a dummy config with pncconf, that is something like your machine, but not bothering whether it is exact or not.

Look at the .hal file and you will see it contains a whole plethora of signal names, some of which are used and others may remain unused, depending upon on your config.
These signal names are standard throughout all configs produced with that version of pncconf

regards