Limits override on start up.

so I was working on my hal file setting up backlash comp and managed to get a following error when the backlash kicked in while homing. I closed gmoccapy and made an edit to the ini file and restarted and could not get the machine off the limit switch. When starting gmoccapy and on a limit switch the option for override limits was greyed out. I had to use axis to get the machine off the limit switch. Is there a way to enable override limits when starting?

@eman5oh,

When starting gmoccapy and getting out of estop state, the "ignore limits should be checkable!
You have to check the box, before switching on the machine!

Please try and report.

Norbert

Thats a point, but also a strange way to wire the limit switches.

Norbert

I have figured out how to replicate the issue, gmoccapy may work this way be design but it is different than axis. I power up the machine and then launch gmoccapy click the manual mode and jog the machine into a limit with my mpg, now I closed exit gmoccapy and restart. I can not click on override limits. What I found by tring a bunch of thinks is if I toggle my physical estop button the override limits then becomes available. Like I said this may be the way it is intended to be but it took me a while to figure out how to get off a limit when the machine is started in this state.

Hello
Does anybody know where are the the limit-switch configuration on gmoccapy?
I don't find any related to limit-switches. I mean hard limit-switches to do homing like axis.
It is possible to do homing with limit-switches in gmoccapy.

I didn't find any variable in halshow either.
I am absolutely lost about this.

Thanks

Thanks tommylight!

Does the limit-switches work in gmoccapy the same way as in axis? I tested long time ago in axis and it seems not to be the same.
Sorry but I haven't found any doc nor any video that are really clear to understand and configure.

When I click home x it runs to zero position immediately and stops not taking care of any limit-switch nor any input. I am sure there is something bad configured but it seems not to check any input at all. I think the axis has to run indefinitely until the switch is tripped so if I have something wrong with it will never stop right? Why it stops?

How do I instruct gmoccapy to see the limit-switches? Where is the limit switch signal come from? I think is internal. I mean, a kind of software homing.

Thanks

Thanks andypugh!

I haven't saw this link. I read the old one a lot of times. I will give it a read.

I am trying to setup a RPi3 with a Mesa 7c81, so you always have to patch something

Thanks!