Limits override on start up.

Thanks tommylight!

Yes I finally figure that. Besides, I check the limits switches and work ok.

The problem is the "auto-home" mode. I don't know how to do it automatically in gmoccapy (maybe I can do some macro).
I really like the way axis handle that. Its auto-home mode fetching all the limit switches and setting up all the zeroes is simple and "visually" confident. You have a really feedback on how the machine is homing up.

Is there a way to do the same in gmoccapy? I mean, finding the limit switches and zeroing, not only nice simulations in the gremlin box.

Thanks

Havve you read this doc?
linuxcnc.org/docs/2.8/html/gui/gmoccapy.html
And watched the proposed youtubes?

For homing you have a buttons menue (lower menues bar) and there another for setting values.

Mike

Hi Mike!

Several times, forward and backward

Anyway gmoccapy does not behave like axis no matter how you set up your limit switches (at least my tests). I mean, finding the probe is ok going back and forth like the docs. But homing it's not the same like axis.
I insist with gmoccapy because of tool measurement.

It drives me nuts... maybe I have to leave it for a while...

Thanks

Do you mean like this:

Anyway gmoccapy does not behave like axis no matter how you set up your limit switches (at least my tests). I mean, finding the probe is ok going back and forth like the docs. But homing it's not the same like axis.

Can you make a short video of what axis is doing different?
I am not able to see your problem:( But I would like to help.

Norbert

Hi guys, thank you all indeed!

Sorry but, why a simple limit switch setting is so complicated? It is a simple switch you know?

I read this link lots of times:
linuxcnc.org/docs/devel/html/config/ini-homing.html

The drawings seem to be pretty clear but to my understanding, what says in point 4. Shared Limit/Home Switch Example Layout does not fit what says in point 5. Homing Sequence. Not even fit the numerical examples (I mean magnitude signs).

What I want: To home my machine using shared home/limit switches to automatically find my hardware limits.

But whatever configuration I tried I always get these 2 messages when I attempt to set the x axis limit:
- joint 2 on limit switch error
- joint 1 on limit switch error

It seems when the limit switch trips it drives the machine to a full stop (send the above messages) and not further actions can be done beyond this. What explains in point 5. Homing Sequence never ever happens.

I am not sure how gmoccapy works. Can I find my hardware limits automatically with my shared home/limit switches? I think this kind of limit switch homing can't be done with gmoccapy.

I remember long time ago I tested this with axis and it works fine. Now I am using gmoccapy with a RPi3 and a Mesa 7c81 so migrate to axis just to test this is a lot of work and I think I will mess all this up.

I show you one of my testings (just what I think is the important thing). I tested any kind of sign combinations, distances and speeds:


I don't know what to ask. Sorry.

Thank you all!!!

drive.google.com/file/d/1w97H8GVh5aNJJiw...SSN/view?usp=sharing