VKB nxt EVO (KG-12 grip) and THQ -- throttles not working properly

[Rampage_ZA]

hello,

I am setting up a NXT EVO and I am having some trouble with the THQ module.

I've connected it according to the setup guide here: https://www.youtube.com/watch?v=hM6G_wvOCN4

however, it looks like the 3-pin connector on the EVO has changed to a 4-pin, so I used the 4-pin to 4-pin cable.

In the software, I can calibrate everything except the first two throttle levers on the THQ. I've attached screenshots.

I'm a noob, so I'm not too sure how all these settings work. That said, I have hit the default button, find&config button, then tried to calibrate according to the setup vids.

Help is appreciated.

[fallout9]

Please connect the 3 to 4 pins cable, like in the video. The EVO has only 2x4 pin sockets, fit the 3 pin end of the cable in it like this:

[Rampage_ZA]

hello, thanks for your reply.

I've connected the 3-pin cable as you demonstrated, but it's still showing up exactly the same as before -- everything detects fine except for the first two throttles. I've tried doing the default button / find and auto config again several times, but it's the same.

If you need any other pictures let me know.

[Rampage_ZA]

I noticed a problem with the third throttle too -- it's being picked up in the software as "rot x" and not an "axes" as shown in the setup video.

This is causing it to have a detent in the middle of the axes, and it also causes the throttle to not be detecting the full range of motion of the lever.

[fallout9]

1. Download software v0.92.31 and the attached firmware. Unzip them both in the same folder, same as the bootloader.
2. Launch VKBDevCfg as Admin and click the Bootloader button under Tools tab;
3. Navigate to the firmware file and load it up;
4. Unplug from USB, connect the THQ to the EVO, plug back to USB;
5. Launch VKBDevCfg and click the Default button under Tools tab;
6. Navigate to Global/Devices/External Devices and press the Find&AutoConfig button;
7. Go to Test/Axes1 tab and click on the Start Calibr button;
8. Move your pitch, roll and yaw axes all the way, slowly at the end;
9. Move the mini-throttle up and down;
10. Press the A1 ministick center button and when the LED turns red move the ministick all over;
11. Press the End Calibr button.

[Rampage_ZA]

Hello,

I followed all of the steps as you described, but the same issue persists with the throttle module. Only the 3rd throttle is bound, and incorrectly bound as a "Rotation" axes and not a throttle axes.

[fallout9]

Need the following screenshots:
- Global/External/ExternalDevices (like the last one you've posted, but instead of the Gladiator Stick I'll need the THQ selected - just mouse click on it);
- Profile/Axes/Logical and Physical Axes.

[Rampage_ZA]

Screenshots attached

[fallout9]

Go to Test/Axes and move the joystick along pitch, roll and twist it. Which axes are moving on screen?

[Rampage_ZA]

axis X, axis Y and Rot Z

[fallout9]

Operate these changes, then press the Set button under Action tab.

[Rampage_ZA]

thanks for that, the axis are definitely being picked up now and are responding. There is just one issue remaining, which is the axis are not displaying correctly, two of them are set as "Rot" axes, so they have a detent in the middle of their motion. The other throttle is being detected as a slider, which seems to operate fine.

[fallout9]

Axes' names have no relevance. Press the Start Calibr button, go through the whole range of all axes on your joystick (pitch, roll, twist, 3XTHQ), then press the End Calibr. button.

[Rampage_ZA]

I've done the calibration as you say, but I'm afraid there does seem to be a difference in operation.

Please observe the video here. Note that I am smoothly moving the throttle from end to end in this demonstration. Notice that there is a deadzone in the center of the motion. This doesn't occur with the other throttle that is mapped as a "Slider" instead of "Rot" axis.

https://drive.google.com/file/d/1AGhTAe ... sp=sharing

[fallout9]

Can you replicate the issue in VKBDevCfg?
Post again the axes screenshot please.