Using VKB-Link/Z-Link to mimic the T-Link virtual brake behavior.

[Tuesday John]

This issue has been resolved with T-Link v0.78 and firmware v2.179 and later.

With T-Link not working with current firmware and T-Rudders MkV, here's a work-around using VKB-Link to mimic the T-Link virtual brakes.
In this work-around, we will be using a SHIFT state to activate virtual brakes.

1. Setup VKB-Link for T-Rudders and whatever VKB device you want to use to activate virtual brakes using the steps here - viewtopic.php?f=27&t=7391&p=59122#p59122
   Remember to set up T-Rudders in the "Source / Slave" box as it will be the device receiving the SHIFT state. The other device will send the SHIFT state to T-Rudders, which in turn will activate virtual toe brakes.
   
   
2. Lanuch VKBDevCfg.
   
   
3. Make changes in Profile/Axes/Physical Axes panel for T-Rudders as indicated in the red boxes.

   

   
   
4. Make changes in Profile/Buttons/Physical layer panel for T-Rudders as indicated the red boxes.

   

   

   
   
5. Create a Boolean as indicated below in T-Rudders. *This assumes you are using SHIFT 1 - if you are using different SHIFT or subSHIFT state, change the left side of the Boolean accordingly.

   

   
   
6. Press Set

Assuming everything was set up correctly, and with VKB-Link running and started, T-Rudders (in combination with your SHIFT state sending device) should now mimic how T-Link handled virtual brakes.
If the brake axes don't travel the whole range, recalibrate the rudders.

[wkwkwk]

As per a discussion with Alex Oz, in Step 4A you enter the number of the rudder axis in the button profile. In this example, button 123 is setup as a trimmer and in the Axis field you enter 4 which is the rudder axis: