Mesa 5i25+7i77 plug-n-go configuration

More
19 Mar 2014 15:52 #44973 by andypugh

-net spindle-on hm2_5i25.0.7i77.0.0.output-00
-net coolant-mist hm2_5i25.0.7i77.0.0.output-01
-net coolant-flood hm2_5i25.0.7i77.0.0.output-02

these statements identify output locations on 7i77 for machine functions?

Not directly. They link some HAL signals to specific output pins on the 7i77. However, despite their names, none of those signals do anything unless also linked to HAL pins exported by the LinuxCNC system. You should also see the same signals being connected to pins such as motion.coolant-flood elsewhere in the HAL file

With regards to setting up an input like "estop" how is this done?
I see "net estop-ext <=hm2_5i25.0.gpio.018.in"
but i was expecting to find a "hm2-5i25.0.7i77.0.0input-01" association


Well, the e-stop wiring is largely a choice that you get to make. I admit that I am slightly surprised to find it linked to a 5i25 direct GPIO rather than a 7i77 pin.
The following user(s) said Thank You: 33zy

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

More
20 Mar 2014 09:59 #45003 by 33zy
HAl pins exported by the linux system: is this them?
"net coolant-mist <= iocontrol.0.coolant-mist"
"net coolant-flood <= iocontrol.0.0cooland-flood"

On that coding theory?

net estop-ext <=hm2-5i25.0.7i77.0.0input-01
net estop-out <= iocontrol.0.user-enable-out
net estop-ext => iocontrol0.emc-enable in

should enable the linux cnc estop function if 7i77 input pin 01 is tripped?

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

More
20 Mar 2014 10:50 #45005 by 33zy
I see two types of "home code" not sure of the difference or if the intent is to use the table limit switches?

net home-switch<= hm2_[HOSTMOT2] (BOARD).0.7I77.0.0.input-00
net home-switch => axis.0.home-sw-in
net home-switch => axis.1.home-sw-in
net home-switch => axis.2.home-sw-in

"only the y servo has an index, x and z home without using index"
net y-index-enable hm2[HOSTMOT2] (BOARD).0.enocder.01.index-enable<=> axis.1.index-enable

It sounds like the intent of this is If i only have a single home input? not sure what this is? I have limit switches on the table?
But i also found the code below that sounds more like limit switch application on my 2EV3 bridgeport? I does seem odd, run the table to the limit switch for home, so maybe I am confused.... suggestions?

net min-x <= hm25i25.7i77.0.0.input-01
net min-y <= hm25i25.7i77.0.0.input-02
net min-z <= hm25i25.7i77.0.0.input-03

net max-home-x <= hm25i25.7i77.0.0.input-04
net max-home-y <= hm25i25.7i77.0.0.input-05
net max-home-z <= hm25i25.7i77.0.0.input-06

net max-home-x => axis0.0home-sw-in
net min-x => axis.0.neg-lim-sw-in
net max-home-x =>axis.0.pos-lim-sw-in

net max-home-y => axis0.0home-sw-in
net min-y => axis.0.neg-lim-sw-in
net max-home-y =>axis.0.pos-lim-sw-in

net max-home-z => axis0.0home-sw-in
net min-z => axis.0.neg-lim-sw-in
net max-home-z =>axis.0.pos-lim-sw-in

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

More
20 Mar 2014 18:50 - 20 Mar 2014 18:51 #45010 by andypugh

I see two types of "home code" not sure of the difference or if the intent is to use the table limit switches?
net home-switch<= hm2_[HOSTMOT2] (BOARD).0.7I77.0.0.input-00
net home-switch => axis.0.home-sw-in
net home-switch => axis.1.home-sw-in
net home-switch => axis.2.home-sw-in

This looks like a config where all the home switches are in series, and the system is configured to home one axis at a time. I can see that making sense on a parallel port system where inputs are scarce, but it seems strange on a 7i77 configuration.

But i also found the code below that sounds more like limit switch application on my 2EV3 bridgeport? I does seem odd, run the table to the limit switch for home, so maybe I am confused.... suggestions?


Running the table to the limit switches to home is fairly common. (It is what my milling machine does).
The problem with a mid-position home switch is that the system has no idea which side of the switch it is on, and so has no idea which direction to search for the switch in.
The way round this is to use a very long flag for the homing sensor, so that half the table travel sets the switch on, and half sets it off. Homing then searches for the switching point.

I think that you are going at this backwards. You should start with how _you_ want to set up the home and limit switches on _your_ machine then configure the HAL to suit, not modify your hardware to suit someone else's HAL configuration.

Have you read the HAL tutorial?
www.linuxcnc.org/docs/html/hal/intro.html
Last edit: 20 Mar 2014 18:51 by andypugh.

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

More
31 Mar 2014 07:47 #45440 by 33zy
what is the difference bewtwwn these two code sets? I am not sure how "loop" operates


net estop-ext <= hm2_5i25.0.7i77.0.0input-01
net estop-loop iocontrol.0.user-enable-out => iocontrol.0.emc-enable in


vs

net estop-ext <= hm2_5i25.0.7i77.0.0input-01
net estop-out <= iocontrol.0.user-enable-out
net estop-ext =>iocontrol.0.emc-enable-in

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

More
31 Mar 2014 08:00 - 31 Mar 2014 08:00 #45441 by andypugh

what is the difference bewtwwn these two code sets? I am not sure how "loop" operates


There is no "loop"

The first term after a "newsig" command creates a signal. And it can use any name that has not been used.
The first term after "net" creates a signal, or if the signal exists, it uses it as the "wire colour" for the rest of the net.

Your first example short-circuits e-stop inside the software layer, with no external e-stop loop.
This isn't necessarily wrong, the actual e-stop chain should be hardware. But it's a nice feature to inform LinuxCNC that e-stop happened.
e-stop should never depend on software.

The second example in your post shows how to inform the system that there has been a hardware e-stop
Last edit: 31 Mar 2014 08:00 by andypugh.

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

More
04 May 2014 23:39 #46580 by 33zy
Hello, I am wiring the CNC machine inputs.
The limit switches and estop go from 24v to zero when activated, or from high to low.
How does one write the 7i77 logic with the HAL to accommodate a input going from high to low?



net min-x <= hm25i25.7i77.0.0.input-01
net min-y <= hm25i25.7i77.0.0.input-02
net min-z <= hm25i25.7i77.0.0.input-03

net max-home-x <= hm25i25.7i77.0.0.input-04
net max-home-y <= hm25i25.7i77.0.0.input-05
net max-home-z <= hm25i25.7i77.0.0.input-06

net max-home-x => axis0.0home-sw-in
net min-x => axis.0.neg-lim-sw-in
net max-home-x =>axis.0.pos-lim-sw-in

net max-home-y => axis0.0home-sw-in
net min-y => axis.0.neg-lim-sw-in
net max-home-y =>axis.0.pos-lim-sw-in

net max-home-z => axis0.0home-sw-in
net min-z => axis.0.neg-lim-sw-in
net max-home-z =>axis.0.pos-lim-sw-in

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

More
04 May 2014 23:49 #46581 by cncbasher
should you need to invert ( reverse ) the logic this is done by adding 'not' to the pin required

example
net min-y <= hm2_5i25.0.7i77.0.0.input-02-not

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

More
18 May 2014 06:14 #47018 by 33zy
How would I change the logic statement if I wanted it to sense ground!

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

More
18 May 2014 09:43 #47021 by PCW
The 7I77 field inputs sense positive input voltages
so:

hm2_5i25.0.7i77.0.0.input-02

will be true (1) when the input is positive (say connected to +24V)
and false (0) when unconnected or connected to ground

hm2_5i25.0.7i77.0.0.input-06-not

Will be true (1) when the input is unconnected or connected to ground and
false (0) when connected to a positive voltage

If you want to sense contact closure to ground it
requires an external pullup resistor on the input

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

Moderators: cmorley
Time to create page: 0.123 seconds
Powered by Kunena Forum