Panel Due Jog Axis In Message Not Displaying

[Phaedrux]

Is your A axis rotational?

I think the normal axis lettering would be XYZ UVW ABC

https://duet3d.dozuki.com/Wiki/M584

[that guy E]

@phaedrux

It is. But should that matter?

[Phaedrux]

For the PanelDue it may. @mfs12 may be able to say more.

[mfs12]

i think this is a mapping problem in RRF. Each axis corresponds to a bit in the m291 binary representation of the control field.

The mapping implemented in paneldue is "XYZUVWABCD".

Check the following PR for details of the implementation.

https://github.com/Duet3D/PanelDueFirmware/pull/226

mfs12 opened this pull request in Duet3D/PanelDueFirmware

closed Add more axis to movement popup #226

[mfs12]

does this also happen with DWC?

[dc42]

@mfs12 said in Panel Due Jog Axis In Message Not Displaying:

The mapping implemented in paneldue is "XYZUVWABCD".

That explains it. PanelDue should use the same mapping from axis numbers to letters as it does for the homing buttons, which I believe it picks up from move.axes[].letter.

[that guy E]

@mfs12

The correct axis are displayed in DWC a jog correctly.

While we're discussing axis jogging is there any ability to change the intervals that are displayed per axis? It would also be great if I could display a +/- instead of the baby step icons?

[dc42]

@that-guy-e I've logged this fault (incorrect axes displayed) at https://github.com/Duet3D/PanelDueFirmware/issues/242.

dc42 created this issue in Duet3D/PanelDueFirmware

closed Incorrect jogging axes shown in M291 message boxes #242

[that guy E]

@dc42 @mfs12

Thank you. I can reassign A to U and post process gcode for the interim. Do you guys have any timeline for the next panel due firmware update?

For future reference are thing like this best brought up here or github?

[dc42]

@that-guy-e said in Panel Due Jog Axis In Message Not Displaying:

@dc42 @mfs12

Thank you. I can reassign A to U and post process gcode for the interim. Do you guys have any timeline for the next panel due firmware update?

Note yet, but we may have news soon.

For future reference are thing like this best brought up here or github?

Here, because it's not always obvious whether an issue needs fixing in RRF, PanelDue, or both.