T-Rudders Mk.IV - yet another modification to differential brakes

[apollon01]

Hello and thank you for the T-Rudders Mk.IV pedals. I am happy with them so far!

I was able to configure the "differential brakes" via T-Link and it works as it is supposed to. However, I would like to give it a little modification.

How it works now:
- When T-Link "brake" button is pressed, the aircraft starts braking on both wheels (that is done via TrimAuto+ with 64x speed I suppose)
- When rudder is deflected to the left, the right wheel stops braking and the aircraft starts turning to the left

How I would like it to work:
- When T-Link "brake" button is pressed, nothing happens (so no braking on both wheels - no TrimAuto+ function; instead the "brake" button only activates the left and right brakes axes)
- When rudder is deflected to the left, the left wheel starts braking and the aircraft starts turning to the left

I hope the example above is OK to understand. If not, please let me know.

I played with the VKBDevCfg, but to no avail.

Therefore, I would appreciate your help on how to achieve the above.

Thank you!

Milan

[apollon01]

Edit: obsolete post

[Ron61]

What is your configuration - base and grip?

[apollon01]

Hi Ron61,

and thank you for the reply.

I have the Gladiator Mk.II (non-Pro).

Milan

[Ron61]

There are two options - so far about the first. Assign 2 buttons to the pedal axis - 73 and 74, which will trigger when giving the corresponding foot.
The start of the trigger is set by Hysteresis. If this does not suit you, then assign the keyboard keys A and D to these buttons. Everything is in the video.
For a general brake, you have to assign your own button.

[Victorus]

How I would like it to work:
- When T-Link "brake" button is pressed, nothing happens (so no braking on both wheels - no TrimAuto+ function; instead the "brake" button only activates the left and right brakes axes)
- When rudder is deflected to the left, the left wheel starts braking and the aircraft starts turning to the left
Milan

Look here http://forum.vkb-sim.pro/viewtopic.php?f=25&t=4207&p=39695&hilit=split+axis#p39695. May be it will help

[apollon01]

Thanks guys for help.

Ron61 - I have already tried the A2B way but while the result works, I did not find it suitable for my needs.

Victorus - yes, this is the way I initially went - creating two virtual axes, one activating when the pedals are pushed to the left and the other one activating when pedals are pushed to the right.

Only now I would need to assign a button that would work as a SHIFT for the two new virtual axes. When this SHIFT button is not pressed, the two new virtual axes would not register movements to the sim and when the SHIFT is pressed, they would register.

I hope this explanation makes sense

[Victorus]

Only now I would need to assign a button that would work as a SHIFT for the two new virtual axes. When this SHIFT button is not pressed, the two new virtual axes would not register movements to the sim and when the SHIFT is pressed, they would register.

There is a tool that mirrors your idea. FA function. https://yadi.sk/i/emoZcmpw7Kyo9w.
"FA1
Fixes axis without center (throttle, for example) in zero position and axis with center (pitch, yaw etc.) in central position. Axis is fixed until button with FA1 unction will be released."
We will disable mirroring using Boolean functions.
I want to invert FA1. If unpressed axis blocked.
Disclamer. All used button numbers are for example only.
Certain LOGICAL button must be pressed when assigned Physical is not.
"XOR Button «pressed» if one of source buttons Operand 1 or Operand
2 IS pressed AND another IS NOT."
Pinky button number is 8. It will control brake axes.

Now boolean. Click unused line cell (9 in my example). Choose Boolean, XOR, check Invert. Operand 1 - Physical 8. Operand 2 - unused 120. It never will be pressed)). If pinky is not pressed, logical 9 is On.

Well, but logical buttons can not control axes. We need physical one.
Another boolean function, JMP, jumper.
"JMP Jumper. Maps logical button line to physical one."
Click some unused line and choose Boolean - JMP. Operand 1 - Logical #9 that is controlled by pinky. Operand 2 - physical 13. All will think so))) We know that it is fake physical. But who cares)))

Click line 13, choose Fix axes, FA1, select axes numbers. In my example I control single axis #8 - MCG brake lever. You must select your virtual brake axes.

Press SET. Some users forget to do this)))
Now if pinky button is not pressed controlled axes are zeroed. "Physical" button #13 (FA1) is "pressed".

If I press pinky, button #13 will be released, axes work!!!

Try. I hope I've understood you right.

[apollon01]

Wow, this looks like it will work.

Let me give it a shot tomorrow. I will report back.
Thanks for helping!

[apollon01]

OK, it seems that I am getting there.

First of all - I am trying to do this with my T-Rudders Mk.IV pedals (not a stick).

Here are my details:
- VKB Device Config v0.91.22 (yours is VKB Device Config v0.91.25)
- NJoy32 firmware v1.98.E (yours is NJoy32 firmware v1.99.3)
- T-Rudders Mk.IV pedals with firmware VKB-Sim T-Rudder v1.986 (your example is not using them)
- stick is Gladiator MK.II (non-Pro) with firmware VKBsim Gladiator v1.85B (newer firmware makes the axes unresponsive; yours is Gunfighter MCP v1.993)

What I have done:
- I was able to assign a "brake" button via T-Link that appears as physical button #121 in the config tool for the rudder pedals.
- I converted it from the Trim+ button to "normal" button with momentary action.
- I then followed your steps described above and successfully replicated them with the effect that if the "brake" button on my stick is NOT pressed, the new physical button #7 (on the pedals; in my case activating the FA1 function) IS pressed and vice versa (I am able to cross-check this also via the VKB joytester)

- using one tutorial here on the forum, I created two new virtual axes separately for left and right movements of the pedals - these are axes #1 and #2

- the new physical #7 button (with the FA1 function) is assigned to these two virtual axes #1 and #2... but it does not work as in your example

Can you see what is wrong here?
I wonder whether your suggestion can work also on the T-Rudders Mk.IV pedals?

Thank you. I appreciate your help!

Milan

[apollon01]

and for completeness I attach also settings of the other buttons I have created following your guidance

[Victorus]

Your pictures became dead. You use pedals with own controller? I try to make prifile for Gladiator with T-Rudder attached.

[apollon01]

Thank you. I appreciate it.

[Victorus]

Please, try attached profile for Gladiator+Trudder attached to Pedals port directly. Pinky button enables axis without center - for common brake. A1 button enables 2 virtual axes combined with pedals. If pressed red LED blinks ultrafast. Axes mapping changed significantly due to FA1 function restrictions.
Sorry, all descriptions later(

glad150520.zip

(1.13 KiB) Downloaded 135 times

[apollon01]

Hi Victorus,

I can see you put a lot of work into this.

I plugged my pedals directly to the Gladiator (non-Pro), ran the calibration and loaded the profile you sent me.
I can see the rudder axis appears on Gladiator as #7 (Slider 1) and when pinky is pressed, the #4 (Rot X) moves from 0 to max.

However, when the A1 is pressed, there is no blinking on my Gladiator and when moving the rudder no additional axes are moving on the Gladiator

Just in case, I attach the config Profile page for Buttons, Physical layer with the A1 pressed.

Please let me know if you want me to post some other screens if you feel like debugging still makes sense. However, I will understand if you will not. There was already a lot of time put into this.

Cheers,

Milan