lube alarm broken on last update
- OT-CNC
- Offline
- Platinum Member
Less
More
- Posts: 622
- Thank you received: 75
24 Mar 2019 02:24 #129429
by OT-CNC
Replied by OT-CNC on topic 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
net low-lube-level iocontrol.0.lube_level lube_level.trigger <= hm2_5i25.0.7i77.0.0.input-13-not
Please Log in or Create an account to join the conversation.
- andypugh
- Offline
- Moderator
Less
More
- Posts: 23178
- Thank you received: 4864
24 Mar 2019 11:23 #129466
by andypugh
Replied by andypugh on topic lube alarm broken on last update
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?
Does it potentially run once before the first cycle of the 5i25 read thread?
Please Log in or Create an account to join the conversation.
- OT-CNC
- Offline
- Platinum Member
Less
More
- Posts: 622
- Thank you received: 75
24 Mar 2019 15:02 - 24 Mar 2019 15:11 #129476
by OT-CNC
Replied by OT-CNC on topic lube alarm broken on last update
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
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
Last edit: 24 Mar 2019 15:11 by OT-CNC. Reason: added the 5i25 read and order of listing
Please Log in or Create an account to join the conversation.
- andypugh
- Offline
- Moderator
Less
More
- Posts: 23178
- Thank you received: 4864
24 Mar 2019 15:20 #129479
by andypugh
Replied by andypugh on topic lube alarm broken on last update
"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.
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.
Please Log in or Create an account to join the conversation.
- OT-CNC
- Offline
- Platinum Member
Less
More
- Posts: 622
- Thank you received: 75
24 Mar 2019 15:30 #129480
by OT-CNC
Replied by OT-CNC on topic lube alarm broken on last update
I'll swap it around and see if it makes a difference. Thanks for the pointers.
Please Log in or Create an account to join the conversation.
- pl7i92
- Offline
- Platinum Member
Less
More
- Posts: 1875
- Thank you received: 355
24 Mar 2019 16:18 #129482
by pl7i92
Replied by pl7i92 on topic lube alarm broken on last update
you also can use a AND
so if Estop is off it calls the function or puts out the mesage
not only on Initalisation
so if Estop is off it calls the function or puts out the mesage
not only on Initalisation
Please Log in or Create an account to join the conversation.
- PCW
- Away
- Moderator
Less
More
- Posts: 17998
- Thank you received: 4842
24 Mar 2019 16:19 #129483
by PCW
Replied by PCW on topic lube alarm broken on last update
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
Please Log in or Create an account to join the conversation.
- OT-CNC
- Offline
- Platinum Member
Less
More
- Posts: 622
- Thank you received: 75
24 Mar 2019 16:31 - 24 Mar 2019 16:31 #129488
by OT-CNC
Replied by OT-CNC on topic lube alarm broken on last update
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...
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...
Last edit: 24 Mar 2019 16:31 by OT-CNC. Reason: sp.
Please Log in or Create an account to join the conversation.
- PCW
- Away
- Moderator
Less
More
- Posts: 17998
- Thank you received: 4842
24 Mar 2019 16:39 - 24 Mar 2019 16:40 #129490
by PCW
Replied by PCW on topic lube alarm broken on last update
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)
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)
Last edit: 24 Mar 2019 16:40 by PCW.
Please Log in or Create an account to join the conversation.
- andypugh
- Offline
- Moderator
Less
More
- Posts: 23178
- Thank you received: 4864
24 Mar 2019 17:29 #129494
by andypugh
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.
Replied by andypugh on topic lube alarm broken on last update
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.
Please Log in or Create an account to join the conversation.
Time to create page: 0.115 seconds