moving problem

That is strange. Ages ago I had no trouble with adding an A axis and had a rotary table turning on my gantry machine under V2.8. There must be something missing.

Yes, I think equal, in fact one of the threads I have followed was yours, with a plasma Torch, I compared the Ini and Hal and I think I have it equal, saving the obvious differences.

I found this diving in the documentation:
"for trivial kinematics, X is always joint 0, A is always joint 3, and U is always joint 6"

What do you think about Rod, this could be the mistake?

Some interesting pics of a display with with the A in geometry in different places.

www.wallacecompany.com/machine_shop/LinuxCNC/fourth_axis/

RoberCNC wrote: Yes, I think equal, in fact one of the threads I have followed was yours, with a plasma Torch, I compared the Ini and Hal and I think I have it equal, saving the obvious differences.

I found this diving in the documentation:
"for trivial kinematics, X is always joint 0, A is always joint 3, and U is always joint 6"

What do you think about Rod, this could be the mistake?

That does not sound right in a joint axis world. I think its a typo.

I was running on joint 4 of a 7i76e (Version 2.

I found my A xis Config dated back to 2017. hal and Ini files are attached. There needs to be a change to the newer multispindle format for this to load.

I found this diving in the documentation:
"for trivial kinematics, X is always joint 0, A is
always joint 3, and U is always joint 6"

If you quote a document, please cite
a link or exactly how you found the document.

That quote is found at 2.10 [TRAJ]Section in the
"INI Configuration" Chapter of the 2.7 branch:
linuxcnc.org/docs/2.7/html/config/ini-config.html

But does not appear in the *unreleased* 2.8 branch:
linuxcnc.org/docs/2.8/html/config/ini-config.html

nor in the *unreleased* master branch:
linuxcnc.org/docs/master/html/config/ini-config.html

or its equivalent:
linuxcnc.org/docs/devel/html/config/ini-config.html

Numerous things change between branches.

dgarrett wrote:

I found this diving in the documentation:
"for trivial kinematics, X is always joint 0, A is
always joint 3, and U is always joint 6"

If you quote a document, please cite
a link or exactly how you found the document.

That quote is found at 2.10 [TRAJ]Section in the
"INI Configuration" Chapter of the 2.7 branch:
linuxcnc.org/docs/2.7/html/config/ini-config.html

But does not appear in the *unreleased* 2.8 branch:
linuxcnc.org/docs/2.8/html/config/ini-config.html

nor in the *unreleased* master branch:
linuxcnc.org/docs/master/html/config/ini-config.html

or its equivalent:
linuxcnc.org/docs/devel/html/config/ini-config.html

Numerous things change between branches.

My apologies dgarrett, you're absolutely right, I'm sorry.

Rod, thank you very much for attaching the files, I will compare them to see what I have different, thanks.

Hello Phill, thanks a lot for this info, I dont ser nothing similar ok my display .

Summary of situation:
The jamming of the linear axes in continuous jogging seems to be solved by reducing the speed, I will have to assume limitations of working with motors without pulleys.

Regarding the A axis (at the moment it is only a stepper for tests) I have observed several things:
1-If I work with linear speeds in the Preview window it is the tool that rotates.

2-If I work with angular speeds the tool remains static but in the coordinates if it acts as it should (rotations from 0 to 360 degrees and so on) from what I understand it would be correct.

Is an advance!! although in neither case do I get movement in the engine. On the other hand, I do not know if it will have something to do, but for giving the maximum possible data, when making a new configuration, arriving at the A axis, when I give test / tune axis an error window appears, attached copied text of the error.

Hello friends, I would need help to understand the problem I have and know what I am doing wrong, I comment:

Finally I was able to install the DQ860MA drivers but the blocking problems persist. Both continuously jogging and using MDI commands or running a program suddenly the motors are randomly blocked, with its catastrophic consequences .

From my ignorance and by elimination I think there can be two things:
1-some type of PC failure
2-section of insufficient cable (I am using 4-wire USB cable)

Since the rest of the components I understand that they are of a respectable quality, MESA cards and the mentioned drivers.
I would appreciate any help, I'm starting to despair.

What are you using USB cable for? If you are using it to connect the stepper motors then I would suspect that it is far too small.

Even high-power USB cable tends to have smaller wires for data (24AWG for power, 28AWG for data) and 28AWG is only really usable to 0.5A.

Precisely for that, from 7i76 onwards (from 7i76 to the drivers and from the drivers to the steppers) it is all USB cable, except power. What cable section would be recommended? They are 3A steppers, I guess it better be too much to fall short.

I have wired from the drivers to the stepper with section 1.5 and the problem persists.