Want to add alarm input from motor drives

More
27 Aug 2020 23:44 #179756 by p27182
Running a 7i76 with some closed loop steppers and have everything going great so far including limit sensors, all thanks to the setup wizard.

I'm now at the point where I'm trying to edit the hal file to add items that dont exist in the wizard like alarms for each motor drive.

I can add digital inputs like below through the wizard (I added comments):

####### DRIVE ALARMS

# --- X drive ALM ---
net din-00 <= hm2_5i25.0.7i76.0.0.input-06

# --- Y drive ALM ---
net din-01 <= hm2_5i25.0.7i76.0.0.input-07

# --- Z drive ALM ---
net din-03 <= hm2_5i25.0.7i76.0.0.input-08

but I don't yet know how to connect the din-03 variable to the operation of linuxcnc. Where do I find the documentation specifying how I can link these HW inputs to an alarm function in linuxcnc that will tell me what alarm went off?

Thanks!

Please Log in or Create an account to join the conversation.

More
28 Aug 2020 10:53 #179803 by tommylight
You can have a look at
man motion
in a terminal as there should be something useful there and those inputs need to stop motion when triggered.
The following user(s) said Thank You: p27182

Please Log in or Create an account to join the conversation.

More
28 Aug 2020 16:56 - 28 Aug 2020 19:25 #179857 by p27182
thanks! I'll check that out.

edit:

linuxcnc.org/docs/html/man/man9/motion.9.html

axis.N.amp−fault−in IN BIT

Should be driven TRUE if an external fault is detected with the amplifier for this joint

looks like this is the one I need to add- something like :

# --- X drive ALM ---
net axis.0.amp−fault−in <= hm2_5i25.0.7i76.0.0.input-06

thanks again.... gonna see if this works this weekend...
Last edit: 28 Aug 2020 19:25 by p27182.
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
28 Aug 2020 20:37 #179880 by Mud
If looking to conserve inputs, would you simply accept combining the alarm signals into one and have an inaccurate warning message?

Please Log in or Create an account to join the conversation.

More
28 Aug 2020 22:16 #179885 by PCW
Sure, they are all combined by LinuxCNC anyway
The following user(s) said Thank You: Mud

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 02:53 - 29 Aug 2020 02:54 #179903 by Todd Zuercher
The only advantage for keeping them separate is that the error message that pops up on the screen will indicate which joint or axis had the fault.
Last edit: 29 Aug 2020 02:54 by Todd Zuercher.
The following user(s) said Thank You: Mud

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 06:38 #179918 by anfänger
I have error out for spindle and drives in a latching estop

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 13:23 #179932 by p27182
do you mean conserve hardware inputs or linuxcnc software inputs? I have a mesa 7i76 so I have more hardware inputs than I even have plans for. But if you meant linuxcnc inputs I was assuming that if I use axis.0.amp−fault−in (0-2, only 3 axis right now) linuxcnc is already monitoring these variables?

thanks

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 13:51 #179933 by anfänger
I met for Linuxcnc internally. I used the latching E-Stop. I don't know what linuxncn is doing when they are triggered but I wanted to make sure to cut power when this happens, so I use the Estop
But I also was using the Limt stithies with my Estop. I can bypass them withe a key switch. It's more or less the system was build before I retrofitted linuxcnc. If the Axis work for you everything is OK.
The following user(s) said Thank You: p27182

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 15:50 - 29 Aug 2020 17:20 #179939 by p27182
so I've got my drives behaving as expected regarding alarms and have added the following to the halfile but linuxcnc does not respond to me manually tripping the alarms... do I have to enable or edit something else?

# --- X drive ALM ---
net axis.0.amp−fault−in <= hm2_5i25.0.7i76.0.0.input-06

# --- Y drive ALM ---
net axis.1.amp−fault−in <= hm2_5i25.0.7i76.0.0.input-07

# --- Z drive ALM ---
net axis.2.amp−fault−in <= hm2_5i25.0.7i76.0.0.input-08

thanks again!

edit:

I've also verified with halmeter the signal is going high when expected

i.imgur.com/P0fRG9X.png

I also noticed that using halmeter the signal tracks the amp fault but the pin does not... do I need to net the signal to the pin somehow?

thanks
Last edit: 29 Aug 2020 17:20 by p27182.

Please Log in or Create an account to join the conversation.

Time to create page: 0.137 seconds
Powered by Kunena Forum