Problem setting up virtual brake behavior using VKB-Link

[wkwkwk]

I am trying to set up virtual braking behavior on my t-rudders using a button on my STECS (#12). The SHIFT is sent and received but the new axes are not activated.

I have followed the instructions at "VKB-Link/Z-Link guide: Sending SHIFT state from one VKB device to another" [http://forum.vkb-sim.pro/viewtopic.php?f=27&t=7391&p=59122#p59122] and at "Using VKB-Link/Z-Link to mimic the T-Link virtual brake behavior" [http://forum.vkb-sim.pro/viewtopic.php?f=27&t=7720].

I can tell that the devices are connected and the SHIFT is being sent through because of the S1 indicators on VKB-Link and in VKBDevCfg. The Boolean logic indicators light up when the STECS button is pushed and the buttons 123 and 124 (as suggested in the instructions) on the rudders light up. The normal rudder axis moves but the two new axes do not (#6 and #8 as suggested in the instructions).

I think my setups match the screenshots in the directions but there is obviously something I have missed. My firmware is newer than a post that mentioned a problem. The rudders are connected to their own black box. I tried t-link v0.7.5 and v0.7.8 as well with similar results - see the connection but no rudder response.

VKBDevCfg v0.93.43
Firmware: v2.19.B
VKB-Link v0.7.6
Profiles attached and screen shots follow.

Devices are connected and S1 indicated:


Boolean logic indicators light up when button is pushed:


No Y & Z axis movement (here nor DCS); note S1 indicator:


Axes profile:

[Alex Oz]

Please reload images

[wkwkwk]

[Alex Oz]

Thanks,
firstly check it

I haven't checked further, do that and we'll see what happens next.

[wkwkwk]

Thank you. Checking Virtual BUS over USB did not change anything. I checked it in the STECS first, and then in both STECS and rudders. S1 is still being indicated but the virtual axis do not activate.

[Alex Oz]

Sorry, also check global shifts in slave device:

[wkwkwk]

Yes, I had Global SHIFTs set already on (it's mentioned in the the instructions post). Now I have Virtual BUS and External Device checked for both STECS and rudder, with Global SHIFTs checked for rudder only.

[wkwkwk]

...and virtual axes not activated.

[Alex Oz]

there is no any register for output:

so the register-receiver doesn't receive anything:

[wkwkwk]

I set the Generic Virtual Reg N to 1.

The virtual axes do not respond. Should they?

[Alex Oz]

You must mark the register that will be transmitted.
The controller itself has no idea which register to transmit over the virtual bus.
Click Reg# (see sample - register #3 will be selected for bus transmission)

Изображение из буфера обмена (4).jpg (10.43 KiB) Viewed 5927 times

[wkwkwk]

Button 12 is assigned the SHIFT so I selected Reg#2.

Does the Reg N have to correspond? Still no virtual axis activation.

[Alex Oz]

Shift1 should be passed as a global status, it is no longer a button

BUT the receiver expects a button:

If you need to transmit the shift status, you need to create a Boolean shift-button converter in the receiver.

Please attach new profiles

[wkwkwk]

Thank you for all your help once again. This is getting way above my head. I've attached the new profiles.

I do have a Boolean shift function, as per the original instructions.

[Alex Oz]

So, I initially misunderstood the roles and relied solely on the button settings. But that's not the case.
The T-Rudder is the source, and it can't accept any buttons, only the SHIFT status.
But the pedals have a virtual device, which is what led to the confusion.
The received SHIFT status is converted to line 123, but it potentially conflicts, since this register is assigned to receive from the virtual device.
The virtual device needs to be removed—it's designed for use with T-Link, while the pedals are actually the master.
The purpose of the virtual device in STEX is also unclear.
So, we're left with:

But these trimmers are not used in any way and are useless: