lube alarm broken on last update

Input is on this:

net low-lube-level iocontrol.0.lube_level lube_level.trigger <= hm2_5i25.0.7i77.0.0.input-13-not

Where is the message component (are you using the message component?) in the thread order?
Does it potentially run once before the first cycle of the 5i25 read thread?

I don't think I'm using any threads. I just have the messages listed in the beginning of the hal file.

loadrt message names=lube_level messages="LOW LUBE"

then below is:
addf hm2_5i25.0.read servo-thread


followed by:

addf lube_level servo-thread

# --- OIL-LEVEL ---
setp lube_level.edge 0
net low-lube-level iocontrol.0.lube_level lube_level.trigger <= hm2_5i25.0.7i77.0.0.input-13-not

"addf" adds the function to a realtime thread.

If it is added earlier in the HAL sequence than the 5i25 read function then it will run once before the 5i25 pins have done their first update.

I'll swap it around and see if it makes a difference. Thanks for the pointers.

you also can use a AND
so if Estop is off it calls the function or puts out the mesage
not only on Initalisation

If its some kind of start up glitch it might be a good idea to mask the input until LinuxCNC is in the "Machine-On" state

This does come on before machine is in the on state.
How do I mask the input? I don't really want to try adding to the estop logic. I'll just end up breaking it further lol...

If you chose the correct 7i77 pin for active high alarm (high meaning low-lube)
you would use an "and" component with one input connected to machine-on and
the other to the 7i77 input pin.

The output of the and component would connect to the (active high) trigger on
the message (you would need to set the message trigger to active high)

PCW wrote: If you chose the correct 7i77 pin for active high alarm (high meaning low-lube)
you would use an "and" component with one input connected to machine-on

To elaborate, there is a HAL pin called "halui.machine.is-on" and you can use this to mask the low-lube warning until the machine is turned on.