Re: [Emc-developers] Homing from the Python interface in JA

> Except that for I thought that many users the attraction of JA + > neoTrivkins is that they can have a gantry that homes properly without > having to fuss with world and joint modes. Using KINEMATICS_BOTH, expected and common usage is to: 1) 'Home All' joints while obeying the HOME_SEQUENCE

Re: [Emc-developers] Homing from the Python interface in JA

On 5 October 2016 at 17:54, Dewey Garrett wrote: > > For an xyyz config, should probably be using: > > [KINS] > KINEMATICS = trivkins coordinates=xyyz kinstype=b Except that for I thought that many users the attraction of JA + neoTrivkins is that they can have a gantry that

Re: [Emc-developers] Homing from the Python interface in JA

For an xyyz config, should probably be using: [KINS] KINEMATICS = trivkins coordinates=xyyz kinstype=b ... [TRAJ] COORDINATES=XYYZ (kinstype=b means KINEMATICS_BOTH) to support both joints for the y coordinate not the default kinstype which is kinstype=1 (identity) not sure what is configured

[Emc-developers] Homing from the Python interface in JA

A user reports that his XYYZ gantry router misbehaves if he tries to home AxisY from the Axis interface using "home selected" https://forum.linuxcnc.org/forum/38-general-linuxcnc-questions/31598-random-motion-and-lost-steps-after-upgrade?start=10#81253 I see that Axis does a test for