Limits override on start up.

ajsinfotech wrote: Hi guys, thank you all indeed!

Code:

[AXIS_X] MAX_VELOCITY = 15.0 MAX_ACCELERATION = 30.0 MIN_LIMIT = 0 MAX_LIMIT = 200.0 [JOINT_0] TYPE = LINEAR FERROR = 0.5 MIN_FERROR = 0.05 MAX_VELOCITY = 15.0 MAX_ACCELERATION = 30.0 MIN_LIMIT = 0 MAX_LIMIT = 200.0 HOME_IGNORE_LIMITS = NO HOME_USE_INDEX = NO HOME_OFFSET = -1.0 HOME = 3.0 HOME_SEARCH_VEL = 30.0 HOME_LATCH_VEL = -10.0 HOME_SEQUENCE = 0

I don't know what to ask. Sorry.

Thank you all!!!

HOME_IGNORE_LIMITS = NO (Try setting this to Yes)
HOME_USE_INDEX = NO
HOME_OFFSET = -1.0 Set this to 0 to start with
HOME = 3.0
HOME_SEARCH_VEL = 30.0
HOME_LATCH_VEL = -10.0 Are you aware that the sign changes the direction of travel
HOME_SEQUENCE = 0

Hi Aciera,

Thanks for your replay.

do you mean you try to home the axis in gmoccapy?

Yes, I mean home my x axis in gmoccapy

Hi Clive S

Thanks for reply.

HOME_IGNORE_LIMITS = NO (Try setting this to Yes)
HOME_OFFSET = -1.0 Set this to 0 to start with
HOME_LATCH_VEL = -10.0 Are you aware that the sign changes the direction of travel

Yes, I tried all of this in several combinations. Maybe not the right one I guess.

Do I understand you correctly that the machine does not move when you try to home the axis but instead comes up with the error that the home switch is already activated?

[edit]
Ok, one thing you need to fix is that you called the limit-switch signals of all three axis the same "all-limit-home".
Those need to be separate like "all-limit-home-x", "all-limit-home-y", "all-limit-home-z".

Thanks Clive, it seems you point me in the right direction

Trying to demux the signal into 3 new ones resulted to be a bit tricky:
- First get errors like signal was already asigned... etc
- Then, the signal does not exist... etc

Anyway I can figure out how to demux the signal all-limits-home into limit-home-x, limit-home-y and limit-home-z and started to run inconsistently.
Now I get:
- Home switch inactive before start of latch move j=0 (when I hit the switch)
or
- Hit limit in home state 14 (when I hold the switch pressed)

:sick:

Thanks

Do you home using linuxcnc, or just pressing the switches?
The latch error is caused due to inconsistency Motor Mobe and your finger

Please make a short video, press home_x button in gmoccapy and post exact error output from terminal
Please start LinuxCNC from console to see all errors

Norbert

Many thanks newbynobi!

I really really don't like this kind of erratic behaviors. And from the beginning is what I get. It is so diverse, you never know what comes next.

I think it is time to research a little more over another interface, I mean gscreen or another one. Does anyone have any suggestion?
Maybe doing a fresh start could solve all this problems.

Sorry but, I don't like to bother all of you with things when I am absolutely lost.
I will start from ground zero and track step by step. I don't like chasing phantoms.:woohoo:

Many thanks to all of you!!!

I'm sorry but you're all over the place.
We try to help. But you need to provide clear information.
If your setup in the hal and ini is incorrect you will not get the machine to behave the way you want, no matter which user interface you try.

The procedure to get efficient help includes answering the questions, reposting your ini and hal files after you made changes and describing the behavior you get when using linuxcnc with these ini and hal files.

If you can't post a video you need to make it clear which button you press where and how the machine moves.

Maybe you are right, but there is no clear information on how to setup the whole thing in a general and easy way. I think this is truly possible.

At the same time I've been doing a lot of customization (Spindle PID, RPi3, Mesa 7c81, etc) all of this with not clear or direct info. It is overwhelming.

I prefer to do a deepest analysis of the process background and setting up from ground zero in a manual way step by step. Setting up a CNC this way does not give me any confidence. Sorry.

I'll be in touch

Many thanks!

So if you decide to proceed logical. That is good.
1. Are your switches independend or dasy chained?
2. Can you confirm that each switch shows his value reliable in hal?
3. Do all of them react the same way, means signal gets f.x. true when triggered?
4. Is your hal written to accept the signals non inverted.?
5. Are your switches ate the end of your movement, or can your machine be outside?

Only then:
Have you read and looked and understood the drawings of
linuxcnc.org/docs/2.8/html/config/ini-homing.html

Mike