Help Needed: Cracking the Code on LinuxCNC Servo Homing Setup!

No I don't have. This is how the x-homing looks like:

#HOMING use EL8 drives internal homing. Uncomment the line below and in the ini as well. Home the machine, then comment out.
#net x-home-request joint.0.request-custom-homing => cia402.0.home
net x-home-request joint.0.custom-homing-is-requested => cia402.0.home
net x-homing joint.0.is-custom-homing <= cia402.0.stat-homing
net x-homed joint.0.custom-homing-finished <= cia402.0.stat-homed

Now is working like a charm! Thank you for supporting my work!

May I ask for a change? I have this line in hal, which is enabling the homed state after the machine is on. It is very useful, since I can not jog the machine out of softlimits.

net machine-on halui.machine.is-on => halui.home-all

How can implement thin into the default / custom homing?

I already try and in default state just gives me homing like before. Since the servos are absolute and the requested parameter is 2, the machine not moving just read the servo states and homing to absolute parameters.
In custom mode starts the homing when I turn on lcnc. Ideally in custom mode just dont need this feature. But I'm not familiar yet in hal to change it. It is possible to have this two states?

Nevermind. I will figure out a workaround to use custom/default homing with automatic homing enabled.
Like this:
Usually using auto home, and when needed just toggle on custom homing, do homing, toggle off, then using auto homing by default.

Thanks again for the very efficient help!

After speaking to Delta, the Gantry functionality only works with their motion controllers.

Donb9261 wrote:

After speaking to Delta, the Gantry functionality only works with their motion controllers.
 

Which Delta series? A2? A3? B3?

The A3 manual is 1373 pages long but only has brief mentions of the gantry function (I have 4x Delta A3 servos for a planned build with a gantry and was expecting to be able to use the gantry function)

All of them. The reason is that tandem axis control is the domain of the master. The master must issue commands for each motor. The same would be present if using a MESA card with S/D.

Tandem axis control using ECAT in LCNC isn't functional if I understand correctly. I am still digging.

Delta explained what I already knew to be true, that an ECAT servo must derive all commands via the master who is fed commands via the controller. They said, that with the setup they have the position loop is closed for both drives and the encoder output for D1 is fed into D2. The D1 drive uses the standard RS422 encoder output and D2 uses the external encoder interface IN as the position FB for D2. From there, D2 will be placed in follow me mode where it follows the pulse train from D1. While novel, much of the position calculations must be done by the master to ensure the following error of each drive remains as low as possible. Hence the reason it only works with their controllers.

I am just the messenger here. But what they said makes sense based on how their drives are designed. What they have provided as a solution is not ideal even by their standards. Tandem axis control should be the domain of the controller/master not the drive.

The engineer was going to reach out to his counterpart in Taiwan but DeltaTW is off next week so it would be W1 of July before a response is possible. He will forward any white papers if any are available.