Advanced Search

Adding a Visual.

 

Some success.

Z-Axis homes perfectly the way that it is set up now. I set that to SEQUENCE 0

Different story for Y.
First, it's not synchronizing the 2 joints.
On the Y-Axis it actually senses the switch and reverses like it should. 
The Y2-Axis simply continues past the switch and does not reverse.

Attaching files.

 

The LinuxCNC hal pins involved are from motion so

man motion

Will provide documentation on the joint pins for example.

The signal names (like max-home-z ) are arbitrary and created
by the first net command that uses them

Note that I suspect that you have the Z limit wrong as typically
you would use:

net max-home-z     =>  joint.3.home-sw-in
net max-home-z     =>  joint.3.pos-lim-sw-in

With a combined home/limit on Z because it's standard
to have the most positive Z position (furthest from the work = most positive)
as the home position. This also means that the Z home search velocity should
be positive. 

Copy-paste error, sorry, should be
net z-neg-limit => joint.3.pos-lim-sw-in

In my HAL file, couple of questions.

1. Where are the variables defined that are in use in the HAL file? In documentation? Or is this the actual definition being created?

2. Somehow this doesn't look correct what Tommy mentioned above:
net max-home-z     =>  joint.3.home-sw-in
net max-home-z     =>  joint.3.neg-lim-sw-in
net z-pos-limit     =>  joint.3.pos-lim-sw-in

Is this last line correct? 

 

The joint home and limit pins are active true which means
they should always be yellow when activated.

Depending on the external sensors you may need to select
the normal or inverted ( -not ) inputs to make this true.

I also suggest you always "watch" the joint pins
to verify the hal connections.

Ok, good news. What Tommy recommended worked for the Y-Axis.
It did not work on the Y2-Axis.

@PCW

Motions joint limit and home switch pins must change from
red  to yellow when activated which = true when activated.

Is that a correct statement when "-not" is in use?

The colors change from yellow to dark red.

Motions joint limit and home switch pins must change from
red  to yellow when activated which = true when activated.

What makes you think that I "edited stuff at random"  ??  

The only think that was edited by "hand" in the HAL file was the adding and removing of  "-not"

I've used PNCCONF as recommended.

It's perfectly ok to blame your glasses, pretty much a tactic that I use as well.

I'll make this change and reply.

Oh hell, do not edit stuff at random....
In your hal file:
# --- MIN-HOME-Y ---
net min-home-y <= hm2_7i76e.0.7i76.0.0.input-10

# --- MIN-HOME-Y2 ---
net min-home-y2 <= hm2_7i76e.0.7i76.0.0.input-14
Then a bit down
net both-min-home-y => joint.1.home-sw-in
net both-min-home-y => joint.1.neg-lim-sw-in
net y-pos-limit => joint.1.pos-lim-sw-in
and
net both-min-home-y2 => joint.2.home-sw-in
net both-min-home-y2 => joint.2.neg-lim-sw-in
net y2-pos-limit => joint.2.pos-lim-sw-in

WHY ??? And how do you expect it to work when the sensors are not in use waiting for a non existing signal?
those should be
net min-home-y => joint.1.home-sw-in
net min-home-y => joint.1.neg-lim-sw-in
net y-pos-limit => joint.1.pos-lim-sw-in
and
net min-home-y2 => joint.2.home-sw-in
net min-home-y2 => joint.2.neg-lim-sw-in
net y2-pos-limit => joint.2.pos-lim-sw-in

Also, the Z axis should home UP, not down, down is the table where the spindle will ram in.
Z should use in your case max-home-z.
Now, how did we miss that ....
I am blaming glasses!

The colors change from yellow to dark red.

I've checked all of them.

 

In the GUI open "show hal configuration", on the left expand pins then 6i76E and so on till you find input pins, on the right choose the "watch" tab, then on the left click on the input pins that the switches are attached to, use a screwdriver to activate the switches and watch the LED on screen, do they change color?
As for home final vel, i never read that, i just test things and learn from that, so i thought changing direction would work as with lath and search velocities! This means i never had to change it... oh well.

I've tried that as well.

The switches are the inductive proximity type purchased from Hamazon .

Wired to 24vdc, ground and signals to:

# --- MIN-HOME-X ---
net min-home-x     <=  hm2_7i76e.0.7i76.0.0.input-08
# --- MIN-HOME-A ---
net min-home-a     <=  hm2_7i76e.0.7i76.0.0.input-09
# --- MIN-HOME-Y ---
net min-home-y     <=  hm2_7i76e.0.7i76.0.0.input-10
# --- PROBE-IN ---
net probe-in     <=  hm2_7i76e.0.7i76.0.0.input
# --- MIN-HOME-Y2 ---
net min-home-y2     <=  hm2_7i76e.0.7i76.0.0.input-14
# --- MIN-HOME-Z ---
net min-home-z     <=  hm2_7i76e.0.7i76.0.0.input-15

Here, we have reached the switch, the lights on the switch turn off

Makes me think that maybe your home signal goes to False when your axis reaches the homing position. LinuxCNC is expecting a positive edge when the home switch activates if your switch is low active then you need to use the '...-not' pin of your input in your hal file.

When you look at the machine, Y axis moves towards you in negative direction and away from you in positive direction, that can be checked on the DRO in the GUI.
X moves left in negative and right in positive direction. Z moves down in negative and up in positive.
You have your sensors on the left on X and toward you on the Y.
Make sure when you jog the directions are correct.

We are all good to here and agree.

Then
-if the machine is moving correctly towards the switches during homing, do not change HOME_SEARCH_VELOCITY, that is correct.

And good here.

-if the reach the switches and do not stop at all for a short period, the switches are not set properly or not reacting at all, they have led's see if they change

Here, we have reached the switch, the lights on the switch turn off. The gantry continues moving in the positive(+) direction.

-if it does stop shortly then move again in the same direction, change HOME_FINAL_VELOCITY sign.

Based on the documentation, the HOME_FINAL_VEL (not HOME_FINAL_VELOCITY) indicates the following:

6.3. HOME_FINAL_VELThis variable has units of machine-units per second.It specifies the speed that LinuxCNC uses when it makes its move from HOME_OFFSET to the HOME position. If the HOME_FINAL_VEL is missing from the ini file, then the maximum joint speed is used to make this move. The value must be a positive number.