drive enable wiring
11 Nov 2014 00:49 #52996
by andypugh
That will work if your field power is running at 24 V( being a 24V relay).
It seems rather over-specified for the job, you only need to switch a few mA so a tiny relay would be fine. However, there is something to be said for having all relays the same so that keeping spares is easier.
Replied by andypugh on topic drive enable wiring
I have a few of these ( attached file) relays around. Will these work ok? It's a t9ap5d52-24
That will work if your field power is running at 24 V( being a 24V relay).
It seems rather over-specified for the job, you only need to switch a few mA so a tiny relay would be fine. However, there is something to be said for having all relays the same so that keeping spares is easier.
Please Log in or Create an account to join the conversation.
20 Nov 2014 21:18 #53237
by andypugh
Not unless you make it so. By default those HAL pins don't leave the software layer.
One way of wiring things is:
iocontrol.0.user-enable-out -> GPIO output pin -> main contactor relay -> ESOP11 -> ESTPO2 -> ESTOPN -> GPIO input pin -> iocontrol.0.emc-enable-in
(I practice the GPIO output pin probably doesn't have enough current capacity to drive the main contactor but can drive a solid-state relay quite well)
No GPIO pins are connected to anything unless specifically connected in the HAL file. You would need lines like
Replied by andypugh on topic drive enable wiring
# create a signal for the estop loopback
net estop-loop iocontrol.0.user-enable-out => iocontrol.0.emc-enable-in
iocontrol.0.user-enable-out refers to TB8 - pin 17 (Output 0) ??
Not unless you make it so. By default those HAL pins don't leave the software layer.
One way of wiring things is:
iocontrol.0.user-enable-out -> GPIO output pin -> main contactor relay -> ESOP11 -> ESTPO2 -> ESTOPN -> GPIO input pin -> iocontrol.0.emc-enable-in
(I practice the GPIO output pin probably doesn't have enough current capacity to drive the main contactor but can drive a solid-state relay quite well)
So I'm guessing here but iocontrol.0.emc-enable-in TB8 - pin 1 (Input 0) is where we wire up the E-Stop circuit to signal that we have unlocked the E-Stop button?
No GPIO pins are connected to anything unless specifically connected in the HAL file. You would need lines like
net estop-out iocontrol.0.user-enable-out => hm2_7i80.0.7i77.0.0.output-000
net estop-in hm2_7i80.0.7i77.0.0.input-000 => iocontrol.0.emc-enable-in
The following user(s) said Thank You: accuartisans
Please Log in or Create an account to join the conversation.
29 Nov 2014 07:41 #53519
by cmtunnel
Replied by cmtunnel on topic drive enable wiring
Ok I've got it wired up now but i'm unsure what to choose for the i/o point in pncconf?
Please Log in or Create an account to join the conversation.
02 Dec 2014 09:10 #53590
by cmtunnel
Does this work automatically or do i need to make something in the config to make this work?
Replied by cmtunnel on topic drive enable wiring
No
Here's an example connection using field output 0
7I77 field output-0 TB8 pin 17 to relay coil-1
7I77 field common TB2 pin 8 to relay coil-2
relay NC contact to Drive 0,1,2 pin 11 (/INH)
relay COM contact to Drive 0,1,2 pin 2 (Drive GND)
Does this work automatically or do i need to make something in the config to make this work?
Please Log in or Create an account to join the conversation.
07 Dec 2014 07:29 #53776
by cmtunnel
Replied by cmtunnel on topic drive enable wiring
I've got the drive enables wired like we mentioned above. However, linuxcnc is not enabling. Should this happen on initial start up? I am trying to get a pncconf file that will work going and jt's sample file does not switch the relay. Is this something I can make work with pncconf?
Please Log in or Create an account to join the conversation.
07 Dec 2014 08:34 #53779
by PCW
Replied by PCW on topic drive enable wiring
Yes, you should be able to connect "X Amplifier Enable" to the desired smart serial0 output pin in pncconf
(you can do the same thing in JTs sample file by editing the hal file and using the net command)
(you can do the same thing in JTs sample file by editing the hal file and using the net command)
Please Log in or Create an account to join the conversation.
08 Dec 2014 02:32 #53796
by cmtunnel
Replied by cmtunnel on topic drive enable wiring
pncconf created this line in my config:
# --- X-ENABLE ---
net x-enable hm2_5i25.0.7i77.0.0.output-00
so i added it to jt's file and loaded it....didn't do anything. trying to figure out what the line means. I'm a little over my head with this.
# --- X-ENABLE ---
net x-enable hm2_5i25.0.7i77.0.0.output-00
so i added it to jt's file and loaded it....didn't do anything. trying to figure out what the line means. I'm a little over my head with this.
Please Log in or Create an account to join the conversation.
08 Dec 2014 03:18 #53797
by PCW
Thats only a part of the enable hal wiring because pncconf splits net statements onto multiple lines
there must be another line in the pncconf hal file like:
net x-enable axis.0.amp-enable-out
The complete hal net done in one line would be like:
net x-enable axis.0.amp-enable-out => hm2_5i25.0.7i77.0.0.output-00
If you edit JTs hal file I would search for axis.0.amp-enable-out to see how
its currently connected and just add hm2_5i25.0.7i77.0.0.output-00 to the net statement
Replied by PCW on topic drive enable wiring
pncconf created this line in my config:
# --- X-ENABLE ---
net x-enable hm2_5i25.0.7i77.0.0.output-00
Thats only a part of the enable hal wiring because pncconf splits net statements onto multiple lines
there must be another line in the pncconf hal file like:
net x-enable axis.0.amp-enable-out
The complete hal net done in one line would be like:
net x-enable axis.0.amp-enable-out => hm2_5i25.0.7i77.0.0.output-00
If you edit JTs hal file I would search for axis.0.amp-enable-out to see how
its currently connected and just add hm2_5i25.0.7i77.0.0.output-00 to the net statement
Please Log in or Create an account to join the conversation.
08 Dec 2014 08:03 #53801
by cmtunnel
Replied by cmtunnel on topic drive enable wiring
his line is:
net x-axis-enable pid.0.enable <= axis.0.amp-enable-out
I tried it with a space and with =>
no luck yet. I have a 24v power supply going into the 7i77 so i am assuming I'll be getting 24v from the output on tb8 when enabled??
net x-axis-enable pid.0.enable <= axis.0.amp-enable-out
I tried it with a space and with =>
no luck yet. I have a 24v power supply going into the 7i77 so i am assuming I'll be getting 24v from the output on tb8 when enabled??
Please Log in or Create an account to join the conversation.
08 Dec 2014 08:29 #53802
by andypugh
You probably ought to read the HAL manual rather than guessing
But the short-form is:
The net command is followed by a signal name (which you can choose freely) and one or more HAL pin names (which must already exist)
Any net commands with the same signal name connect together all the pins in all those net commands.
Only one of the pins connected to any signal name can be an output pin. (otherwise the net is logically inconsistent).
You can insert => , <= and <=> symbols in any way you choose, these are for you benefit and ignored by the computer.
To eliminate a potential confusion, from where HAL is placed, physical inputs from the real world are output HAL pins (they supply a value _to_ HAL) and physical output ons are input HAL pins ( they take a value from HAL)
Replied by andypugh on topic drive enable wiring
no luck yet.
You probably ought to read the HAL manual rather than guessing
But the short-form is:
The net command is followed by a signal name (which you can choose freely) and one or more HAL pin names (which must already exist)
Any net commands with the same signal name connect together all the pins in all those net commands.
Only one of the pins connected to any signal name can be an output pin. (otherwise the net is logically inconsistent).
You can insert => , <= and <=> symbols in any way you choose, these are for you benefit and ignored by the computer.
To eliminate a potential confusion, from where HAL is placed, physical inputs from the real world are output HAL pins (they supply a value _to_ HAL) and physical output ons are input HAL pins ( they take a value from HAL)
Please Log in or Create an account to join the conversation.
Time to create page: 0.164 seconds