VKB-SIM

Firmware: 2.18.F(3)
Software: v0.93.19

Issue: All AUX Axes functions with a Target field (SWAP, REMAP, SWITCH, SWITCH 0) fail to remap source axis onto the logical axes controlled by target axis.

Steps:

• fw2.18.F(3) NXT with default config
• Logical axis 1 = AxID 1
• Logical axis 8 = AxID 8
• Assign any button to either of SWAP, REMAP, SWITCh or SWITHC 0 functions.
  
  • Source = physical axis 1
  • Target = physical axis 8
• Hold function button, observe that logical axis 8 does not move as physical axis 1 is moved.
  
  • In the case of SWAP, physical axis 1 does not even lose control over logical axis 1

https://youtu.be/0v4dgzmr0k4

This is a change from 2.18.F(2)

Check v2_18_F(5)

v2_18_F(5) fixed SWAP in the case where Logical axis index == AxID == Source, and Logical axis index == AxID == Target.

That is, If Source == 1 and Target == 2, SWAP will work if Logical axis 1 has AxID == 1 and Logical axis 2 has AxID == 2.

However this breaks in cases where AxID, Logical index and Source/Target don't line up.

At this point I would need clarification on what is exactly supposed to happen with these AUX axes functions, since the manual doesn't go into enough detail here. Are Source and Target fields meant to be references to Physical axes, or Logical axes?

I have assumed so far that both Source and Target are meant to be references to Physical Axes. That would be consistent with what I have observed in the past.
But with 2.18.F(5), they act as references to both Physical and Logical axes, at least for SWAP, and a Logical axis with AxID completely different from either Source or Target will still be affected. Since I cannot be certain my previous assumption is true it is making it hard to diagnose these issues. Can you clarify this?

Thanks for you work

AUX functions is manipulating of inputs LA - at the moment of activation AUX the LA ID is replaced

Thank you.

From this setup, where logical and AxID are reshuffled:

If Source/Target are logical axis indices, would I be correct to interpret SWAP 1 <> 2 to cause Logical 1 to be controlled by physical axis 3 (which controls Logical 2 before the button is pressed), and Logical 2 to be controlled by Physical 4 instead of 3?
This would produce a diagram like this in my interpretation:


As it stands with 2.18.F(5), this is the actual result of SWAP 1 <> 2:

Axes num in AUX have "absulute" numeration, bindings with Ax ID no matter