INIFILE: ERR_CONVERSION for gantry configuration (2.8.0-pre1-4740-g60416609a)

Clive s wrote: Do you have Y1 and Y2 both with the same sequence number and both -ve in the ini file

HOME_SEQUENCE = -1

I do. Y1/Y2 are 0, X is 1, I turned off Z for now because I didn't want to deal with it for the moment (it also needs different values I haven't figured out yet).

I don't understand what you mean by “both -ve”?

As long as you have the negative home sequence, pretty sure Linuxcnc won't let you jog before homing. Just hit the home all button and it should work.... finger on red button.

Just check for Y and Y1 you have
HOME_SEQUENCE = -1

as Clive said!

WARNING:
Just going back to one of your posts and you linked to homing docs for V2.7 which are WRONG for master branch/2.8
go here linuxcnc.org/docs/devel/html/config/ini-homing.html

Read what it says about negative homing sequences as you might be on the wrong page to Clive and I.

dgarrett wrote: Errors like:

Code:

INIFILE: ERR_CONVERSION, section=JOINT_0, tag=HOME, num=1, lineNo=105

are due to the following bogus ini file entries:

Code:

... [JOINT_0] HOME = Xmin ... [JOINT_1] HOME = YLeftMax ... [JOINT_2] HOME = YRightMax ... [JOINT_3] HOME = ZMax ...

The values for HOME= must be numeric.
If these lines were created by a configuration tool,
it is broken.

linuxcnc.org/docs/devel/html/getting-sta...dating-linuxcnc.html

Those values don't come from my configuration tool, I suspect the LinuxCNC conversion tool is the culprit. I'll have to test later today after work. IIRC the LinuxCNC conversion tool wants version 1.2 and my tool is using 1.1.

Edit: I just did a git pull and checked out 2.8 branch and grepped for YLeftMax and did not find that, so now I have no clue where that came from.

Also, I never start a variable with a capitol letter if I had wrote that it would be "yLeftMax".

JT

I also grepped my entire github and LinuxCNC 2.7, 2.8 and master but those words are not there.

JT

rodw wrote: Just check for Y and Y1 you have
HOME_SEQUENCE = -1

as Clive said!

Well, I want these in the Home All sequence. I just want to be able to home my Y axis separately from X and Z, and there seems to be no way to do that. I don't want to ever home J1 or J2 independently (certainly not easily), because that could cause damage. I can Home All and it does the right thing for Y, but I fear it only does that because I have the same homing sequence set for them.

One question: I'm looking at the gantry docs. Do I need to include that in my config? Things seem to be working without it, but it seems like it offers some things I want.

JetForMe wrote: One question: I'm looking at the gantry docs. Do I need to include that in my config? Things seem to be working without it, but it seems like it offers some things I want.

What do you mean by : Do I need to include that in my config? What is it that you are trying to achieve?

It always helps to include the ini and hal files when asking any questions

I don't have an entry in my .hal right now for the gantry component. I'm asking if adding one will improve anything for me. It's working now, but I wonder what gantry would do for me.

Attached are slightly out-of-date files for what I have now.