DRO not counting for JOINT_4

I am tinkering with the very nice Qtdragon QtVCP interface and added a 5th axis as C-axis.
That worked in principle, all good.

Then I ran into the following issue with the DRO for the C-axis only.
The C-axis is configured as JOINT_4.
If I home all axes by pressing HOME ALL, all axes are counting and homing and I can see the C-axis counting as well.
The counting is in red, as the C-axis is not homed yet.
As soon as it is homed, the C-axis DRO stops counting.
Jogging the C-axis after it is homed, does move the cone on the graphics and using LinuxCNC Status shows an actual C-axis position that changes every time the C-axis is jogged.
However, C-axis DRO stays at 0.
If I de-select ALL HOMED, so the DRO goes to red showing axes are not homed, and I jog the C-axis, the DRO is counting.

Is this a limitation in QtVCP? Looking through the code, it appears as if QtVCP is setup for 10 joints.

Added screenshot showing all axes homed and A jogged to 38.490 and C to 77.070 degrees. The cone is tilted and rotated accordingly.
DRO for C-axis shows 0 but LinuxCNC Status shows actual position.

Can you post your config files please.

Chris

Hi Chris,

Thanks for your quick reply.
Attached the ini file and the hal file.
As you can see, I'm not using a real machine but just a simulator for now.
Do you need anything else?

Thanks

Tommie

if you could share your modifications to qtdragon then I could test everything together.
Thanks

Chris

Chris, I have a battery meltdown on my Macbook that has my VM on it and it won't boot. I hope to get a new battery within a few days and I'll send you the qtdragon files then. Thanks

Tommie

Hi Chris,
I'm back and running again. Attached the config files. The tar.gz file should create directory sim.qtdragon5A

Thanks

Tommie

This is indeed an error in qtvcp. The mapping of joints vrs axes is wrong when non consecutive axes are used.
I'll work on a fix

It's actually quite a difficult problem to solve satisfactory

One half work around (that works with no updates) is on the DRO widget for the C axis set Qjoint_number in designer to 5.

Then the display won't respond to unhomed jogging but will display after-homed position.

Chris

I pushed some work on this for 2.8. (available on next update)
You still must use the axis index number for Qjoint_number in designer.
but now it converts it to a joint number for displaying when unhomed.

This isn't a perfect solution as an axis that has two joints will only have one displayed, but it works in most situations and is as about as good as I can do for a released 2.8.

If it's not adequate for a particular screen then the author would have to do a little python programming work in the handler file.

I'll have to think hard how to fix this better in master.

Chris

Thank you Chris. I changed the Qjoint_number to 5 and it works as suggested.
That it doesn't respond to unhomed joggging and doesn't display the counting whilst homing is ok for now.

Thanks for your help.