How do I configure stepper driver fault output?
20 Apr 2020 00:56 - 20 Apr 2020 06:00 #164703
by PhilCNC
How do I configure stepper driver fault output? was created by PhilCNC
I'm using a Mesa 7i76E and Gecko GR214V. If the stepper drive detects a fault, that drive stops, and all the other 2 drives keep going. This is problematic. I would like to make it so that the 5v fault output on the gecko drive is connected to an input pin on the Mesa 7i76E to trigger the machine to stop, and then I could reset the drives and continue on with the program. Any help is greatly appreciated. Edit: I looked through a lot of threads and the conclusion is to use the command (axis.N.amp-fault-in) I don't really know where exactly this goes in the HAL file, and how I will connect this command to a physical pin on my Mesa board. When I use that line of code, I get an error on startup saying "unknown command"
Final edit: I figured it out. What I wanted was a fault signal from my Gecko drive to stop the machine. To do this, connect a wire from the fault out pin on your gecko drive, to pin 9 on your Mesa board. Open your HAL file and enter the following
# --- Gecko drive fault ---
net faulty axis.1.amp-fault-in <= hm2_7i76e.0.7i76.0.0.input-09
Now when a fault is triggered, LinuxCNC will stop the machine and give you an error! much better. If anyone would like me to explain what is going on with the HAL,
Final edit: I figured it out. What I wanted was a fault signal from my Gecko drive to stop the machine. To do this, connect a wire from the fault out pin on your gecko drive, to pin 9 on your Mesa board. Open your HAL file and enter the following
# --- Gecko drive fault ---
net faulty axis.1.amp-fault-in <= hm2_7i76e.0.7i76.0.0.input-09
Now when a fault is triggered, LinuxCNC will stop the machine and give you an error! much better. If anyone would like me to explain what is going on with the HAL,
Last edit: 20 Apr 2020 06:00 by PhilCNC.
Please Log in or Create an account to join the conversation.
20 Apr 2020 07:00 #164788
by bbsr_5a
Replied by bbsr_5a on topic How do I configure stepper driver fault output?
hi
best is to use the pause Function
like
net drivefault halui.program.pause <= hm2_7i76e.0.7i76.0.0.input-09
if you got different inputs from the other drives use the OR chain to get all drives doing a pause
best is to use the pause Function
like
net drivefault halui.program.pause <= hm2_7i76e.0.7i76.0.0.input-09
if you got different inputs from the other drives use the OR chain to get all drives doing a pause
Please Log in or Create an account to join the conversation.
20 Apr 2020 07:36 #164797
by PhilCNC
Replied by PhilCNC on topic How do I configure stepper driver fault output?
Hi thanks for the help, so it turns out I need to change something else too.
The signal pins on the gecko are all 5v, and won't work with the field IO on the Mesa. how would I connect the 5V input pin? Maybe to my unused step and direction connectors on TB2?
The signal pins on the gecko are all 5v, and won't work with the field IO on the Mesa. how would I connect the 5V input pin? Maybe to my unused step and direction connectors on TB2?
Please Log in or Create an account to join the conversation.
20 Apr 2020 07:49 #164802
by bbsr_5a
Replied by bbsr_5a on topic How do I configure stepper driver fault output?
the mesa accepts 5V inputs
just hook it up and try to see it in HALmeter
just hook it up and try to see it in HALmeter
Please Log in or Create an account to join the conversation.
20 Apr 2020 08:47 #164807
by PhilCNC
Replied by PhilCNC on topic How do I configure stepper driver fault output?
Thanks again, I tried connecting the 5v signal from the Gecko to an input, but I'm not seeing anything. Do I first need to define a step or direction pin as a 5v input? Nothing is showing up in the halmeter.
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 17806
- Thank you received: 5923
20 Apr 2020 10:54 #164817
by tommylight
Replied by tommylight on topic How do I configure stepper driver fault output?
Setting Mesa 7i76E to mode 2 will give you 4 analogue inputs on the first 4 physical inputs, then in hal set the threshold to be 4 to 5V for it to trigger the fault.
Please Log in or Create an account to join the conversation.
20 Apr 2020 18:40 #164879
by PhilCNC
Replied by PhilCNC on topic How do I configure stepper driver fault output?
Thanks, I'm still new to this, could you walk me through this step?
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 17806
- Thank you received: 5923
20 Apr 2020 23:30 #164898
by tommylight
Replied by tommylight on topic How do I configure stepper driver fault output?
At the begnining of your hal file you will have something like this:
loadrt hm2_eth board_ip="10.10.10.10" config="num_encoders=1 num_pwmgens=0 num_stepgens=5 sserial_port_0=00xxxx"
change it to this, notice only one of the port numbers is changed
loadrt hm2_eth board_ip="10.10.10.10" config="num_encoders=1 num_pwmgens=0 num_stepgens=5 sserial_port_0=20xxxx"
Then in hal you will have to add also these
net analogin0 hm2_7i76e.0.7i76.0.0.analogin0
net analogin1 hm2_7i76e.0.7i76.0.0.analogin1
net analogin2 hm2_7i76e.0.7i76.0.0.analogin2
net analogin3 hm2_7i76e.0.7i76.0.0.analogin3
You can also change the signal names to better suit you
net fault-x hm2_7i76e.0.7i76.0.0.analogin0
net fault-y hm2_7i76e.0.7i76.0.0.analogin1
net fault-y1 hm2_7i76e.0.7i76.0.0.analogin2
net fault-z hm2_7i76e.0.7i76.0.0.analogin3
Some more logic will have to be added to trigger the fault at 4 to 5 volt, and maybe other changes, but i do not have a 7i76E to test with and it was 3 years ago since i used one.
-
Another issue with gecko is that you will need to pull that signal down if i am not mistaken to reset them,
here are some links about just that:
forum.linuxcnc.org/27-driver-boards/3668...ng-question?start=20
www.forum.linuxcnc.org/27-driver-boards/...rive-enable-question
Having them to just fault and stop motion is pretty easy, having to also reset them from Linuxcnc is a bit trickier, but doable for sure.
loadrt hm2_eth board_ip="10.10.10.10" config="num_encoders=1 num_pwmgens=0 num_stepgens=5 sserial_port_0=00xxxx"
change it to this, notice only one of the port numbers is changed
loadrt hm2_eth board_ip="10.10.10.10" config="num_encoders=1 num_pwmgens=0 num_stepgens=5 sserial_port_0=20xxxx"
Then in hal you will have to add also these
net analogin0 hm2_7i76e.0.7i76.0.0.analogin0
net analogin1 hm2_7i76e.0.7i76.0.0.analogin1
net analogin2 hm2_7i76e.0.7i76.0.0.analogin2
net analogin3 hm2_7i76e.0.7i76.0.0.analogin3
You can also change the signal names to better suit you
net fault-x hm2_7i76e.0.7i76.0.0.analogin0
net fault-y hm2_7i76e.0.7i76.0.0.analogin1
net fault-y1 hm2_7i76e.0.7i76.0.0.analogin2
net fault-z hm2_7i76e.0.7i76.0.0.analogin3
Some more logic will have to be added to trigger the fault at 4 to 5 volt, and maybe other changes, but i do not have a 7i76E to test with and it was 3 years ago since i used one.
-
Another issue with gecko is that you will need to pull that signal down if i am not mistaken to reset them,
here are some links about just that:
forum.linuxcnc.org/27-driver-boards/3668...ng-question?start=20
www.forum.linuxcnc.org/27-driver-boards/...rive-enable-question
Having them to just fault and stop motion is pretty easy, having to also reset them from Linuxcnc is a bit trickier, but doable for sure.
Please Log in or Create an account to join the conversation.
Time to create page: 0.085 seconds