Clearpath HLFB amp.joint.delay
- djdelorie
- Away
- Junior Member
-
Less
More
- Posts: 30
- Thank you received: 6
14 Dec 2025 21:11 #340100
by djdelorie
Replied by djdelorie on topic Clearpath HLFB amp.joint.delay
I spent some time working on my machine's fault handling, and in the end all I had to add to get it to do what I wanted (stop machine on fault) is to add these (in addition to the configs I posted earlier):
net x-fault => joint.0.amp-fault-in
for each joint. I also set VOLATILE_HOME for each joint in the *.ini but it didn't do exactly what I wanted.
Given that I use joint.N.amp-enable-out (aka x-enable, set in MACHINE.hal automatically) to enable the clearpaths, as soon as a fault comes in, it posts a warning and shuts the machine off, which disables the clearpaths, which clears the fault.
net x-fault => joint.0.amp-fault-in
for each joint. I also set VOLATILE_HOME for each joint in the *.ini but it didn't do exactly what I wanted.
Given that I use joint.N.amp-enable-out (aka x-enable, set in MACHINE.hal automatically) to enable the clearpaths, as soon as a fault comes in, it posts a warning and shuts the machine off, which disables the clearpaths, which clears the fault.
Please Log in or Create an account to join the conversation.
- Fastfred
- Offline
- Senior Member
-
Less
More
- Posts: 57
- Thank you received: 1
14 Dec 2025 21:47 #340102
by Fastfred
Replied by Fastfred on topic Clearpath HLFB amp.joint.delay
Would you mind sharing that part of the file ?
Please Log in or Create an account to join the conversation.
- djdelorie
- Away
- Junior Member
-
Less
More
- Posts: 30
- Thank you received: 6
14 Dec 2025 21:52 #340103
by djdelorie
Replied by djdelorie on topic Clearpath HLFB amp.joint.delay
Here are my full configs, since I didn't know which "part of the file" you meant.
Please Log in or Create an account to join the conversation.
- Fastfred
- Offline
- Senior Member
-
Less
More
- Posts: 57
- Thank you received: 1
14 Dec 2025 21:58 #340104
by Fastfred
Replied by Fastfred on topic Clearpath HLFB amp.joint.delay
Thanks will look at them soon and try.
Please Log in or Create an account to join the conversation.
- spumco
- Offline
- Platinum Member
-
Less
More
- Posts: 1965
- Thank you received: 799
15 Dec 2025 00:40 #340106
by spumco
I think you don't understand HAL naming and so forth.
The HAL section you posted earlier has some issues:net hlfb_x => and2.0.in0
net enable-faults => and2.0.in1
net x-fault <= and2.0.out
What the above does is connect signal 'hlfb_x' to pin 'and2.0.in0'
And if the signal doesn't already exist when LCNC gets to that line in the file, it creates a signal with that name.
Problem is, nowhere in the section you posted is another pin connected to either signal 'hlfb_x' or signal 'x-fault' So the 'and2.0.in0' and 'and2.0.out' pins are not connected to another pin. The AND2 function isn't doing anything.
You need to link two (or more) pins that already exist for the logical function to work. You create the signal names, but the pins must already exist in LCNC.
net SIGNAL PIN1 PIN2 is the format. You can put the connections on different lines, and the "=>" symbol is helpful when reading the file, but not necessary.
All of which means your attempt (I think) to add a time delay in the amp-fault / amp-ok sequence isn't going to work. Your physical inputs are connected directly to the amp-fault-in pins, and the time delay logic isn't in the equation.
Try this. I've put each part on a separate line - make the file longer but can be easier to read for some people:
net x-fault-in hm2_7i96s.0.inm.00.input-10-not
net x-fault-in and2.0.in1
net enable-faults and2.0.in2
net x-fault-delay and2.0.out
net x-fault-delay joint.0.amp-fault-in
Replied by spumco on topic Clearpath HLFB amp.joint.delay
Unless I still having a naming issue with the pins unfortunately I still don't understand this part yet.
I think you don't understand HAL naming and so forth.
The HAL section you posted earlier has some issues:net hlfb_x => and2.0.in0
net enable-faults => and2.0.in1
net x-fault <= and2.0.out
What the above does is connect signal 'hlfb_x' to pin 'and2.0.in0'
And if the signal doesn't already exist when LCNC gets to that line in the file, it creates a signal with that name.
Problem is, nowhere in the section you posted is another pin connected to either signal 'hlfb_x' or signal 'x-fault' So the 'and2.0.in0' and 'and2.0.out' pins are not connected to another pin. The AND2 function isn't doing anything.
You need to link two (or more) pins that already exist for the logical function to work. You create the signal names, but the pins must already exist in LCNC.
net SIGNAL PIN1 PIN2 is the format. You can put the connections on different lines, and the "=>" symbol is helpful when reading the file, but not necessary.
All of which means your attempt (I think) to add a time delay in the amp-fault / amp-ok sequence isn't going to work. Your physical inputs are connected directly to the amp-fault-in pins, and the time delay logic isn't in the equation.
Try this. I've put each part on a separate line - make the file longer but can be easier to read for some people:
net x-fault-in hm2_7i96s.0.inm.00.input-10-not
net x-fault-in and2.0.in1
net enable-faults and2.0.in2
net x-fault-delay and2.0.out
net x-fault-delay joint.0.amp-fault-in
Please Log in or Create an account to join the conversation.
- Fastfred
- Offline
- Senior Member
-
Less
More
- Posts: 57
- Thank you received: 1
15 Dec 2025 01:07 #340108
by Fastfred
Replied by Fastfred on topic Clearpath HLFB amp.joint.delay
I really do appreciate the help I am getting I did say I don't understand this part yet and I am sure I was told to copy the file that was posted
djdelorie
and just change the card pin naming to fit for my needs I will try to figure this out my apologies That I haven't picked up on this yet.
Please Log in or Create an account to join the conversation.
- djdelorie
- Away
- Junior Member
-
Less
More
- Posts: 30
- Thank you received: 6
15 Dec 2025 02:29 #340109
by djdelorie
Replied by djdelorie on topic Clearpath HLFB amp.joint.delay
You should not JUST copy the three files I posted; at best you could insert the snippets I posted first (there's a section in my custom.hal that matches it, you could cut-n-paste that). You *should* be able to use my HLFB logic as-is if you have wired each servo to its own enable/fault pins, and have a gantry-style (dual Y) system.
With a basic understanding of how HAL works, you should be able to figure out my hal setup. I'm not an expert at HAL so my logic is pretty basic. The bigcnc.* files are pretty much right out of pncconf (but tweaked) and the custom.hal file is all mine.
With a basic understanding of how HAL works, you should be able to figure out my hal setup. I'm not an expert at HAL so my logic is pretty basic. The bigcnc.* files are pretty much right out of pncconf (but tweaked) and the custom.hal file is all mine.
Please Log in or Create an account to join the conversation.
- Fastfred
- Offline
- Senior Member
-
Less
More
- Posts: 57
- Thank you received: 1
15 Dec 2025 02:42 #340111
by Fastfred
Replied by Fastfred on topic Clearpath HLFB amp.joint.delay
No I did not copy the whole thing just the hal part for HLFB thats it.
Thanks
Thanks
Please Log in or Create an account to join the conversation.
- spumco
- Offline
- Platinum Member
-
Less
More
- Posts: 1965
- Thank you received: 799
15 Dec 2025 05:01 #340113
by spumco
No worries, you'll get through this even if you feel like you're lost now.
Takes a while for HAL to sink in - it did for me.
Replied by spumco on topic Clearpath HLFB amp.joint.delay
I will try to figure this out my apologies That I haven't picked up on this yet.
No worries, you'll get through this even if you feel like you're lost now.
Takes a while for HAL to sink in - it did for me.
Please Log in or Create an account to join the conversation.
Time to create page: 0.083 seconds