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

You seem to have HOME_SEQUENCE = 1 for all axis. I believe they should start at 0 usually for the Z so that it homes first, then the next say Y (for a gantry type with two motors) this needs to be a minus ie HOME_SEQUENCE = -1 for both joints and the last would be X with a 2.

I think that you cannot miss a number out and start with 1

This is assuming you are using 2.8

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.

You don't need gantry at all with version 2.8. Its essentially obsolete. Just follow the correct V 2.8 documents to set up homing.

Please confirm the version in use. Earlier you said you were using V2.8.

You still don't have HOME_SEQUENCE = -1 for joints 1 and 2 so homing will not square your gantry.

I noticed a couple of things in the ini file which are probably from John's configurator

Initially, I thought this should have been XYZ but I see it is now valid to be formatted like this in the docs:
I'm not seeing AXIS = n is valid in the joint section but it won't break anything. It probably should be commented out.

Ah, I see why negative is important. I had gotten it in my head that "-1" meant somehow excluding that joint/axis from homing altogether.

I'd argue that it would be a lot clearer to have a separate configuration parameter for specifying that two or more joints should be synchronized, and how they should be synchronized. This would allow joint-mode jogging, for example, if I could tell linuxcnc that two joints must always be synchronized.

I'm also worried that specifying -1 won't be enough, as it only synchronizes the final move, but (evidently) not the search for home or the latch move.

Lastly, to tommylight, I've been reluctant to "home all" precisely because I'm not sure everything is configured right. Having said that, it's working pretty well now, and I've been using Home All successfully even without the proper sequence configuration. I'll be making that change next.

Its perfectly fine. I've been using it for about 3 -4 years. What happens is the first side that hits the home sensor stops and waits for the other to catch up. Then they both go through the sequence together. Its quite amazing to watch if you rack the gantry, particularly at slow homing velocities. Final squaring can be done via the offsets in the .ini file

JetForMe wrote:

Ah, I see why negative is important. I had gotten it in my head that "-1" meant somehow excluding that joint/axis from homing altogether.

I'm also worried that specifying -1 won't be enough, as it only synchronizes the final move, but (evidently) not the search for home or the latch move.

To be clear the negative sign makes sure that when homing both gantry motors are driven together until one of them hits its own home switch then that motor stops and the other caries on until that hits its own home switch.

Then the magic happens and both motors go to their respective home offsets (as setup in the in file) So one could offset to say 2mm and the other to 2.3mm (or what ever it is the gantry is out of square by)