WWII Grip Buttons and Invisible NXT

[Reim0s]

Greetings!

I've recently mounted a THQ to a left NXT, then attached the WWII grip onto it and the buttons wouldn't register (even after directed in the tutorial to set the THQ to subaddress 4, which caused the whole module to stop responding.) I reset the subaddress to 1 and everything functioned again aside from the grip buttons.

Next, I decided to update the firmware to the latest version to see if that would fix the issue. When I flashed the drive, I selected the 'OTA' version of the NXT on accident, and now the whole module is undetectable by the VKBDevCfg, even after resetting with the F1 and F2 buttons/plugging in the USB AND trying different USB ports.

Blue and red lights are lit solid on the stick, and the two lights on the base are alternating, the blue light being on longer.

[fallout9]

If you're on latest software and firmware versions. then set up your THQ on Sub4 (as it won't recognize the German throttle grip on other Sub), then select the device at the top of VKBDevCfg, press Default button, then Find&AutoConfig button and recalibrate. The whole process is here.

If your device doesn't show up in VKBDevCfg try one or a combination of the following: run it as Admin, plug in the back of computer instead of a hub, change USB ports, kill background running software like Aorus, Razer, Corsair, Logitec, any LEDs management, antivirus, reboot in Safe mode.

[KangaRooskie]

There is clearly an issue with the firmware. Spent 2-3 hours today trying to fix a similar issue, and was getting some help from VKB Operator on the HOTAS Discord.

Tried several firmware versions, no help. As soon as I installed the WW2 throttle grip, it prevented the computer from recognizing any of the modules. We eventually were able to get it to recognize a single THQ. As soon as a 2nd THQ was connected (even without the WW2 grip), nothing was being recognized. You can check out our extensive back and forth on the matter on Discord.

Here's the relevant exchange:

uh-oh, now nothing works
get a blue light on the left THQ (the one connected to the computer), and that's it.
device config doesn't recognize it
ok, got it into boot mode
Tuesday — Today at 2:38 PM
Unplug. Plug it back in. Restart VKBDevCfg in admin.
KangaRooskie — Today at 2:38 PM
had to do the SEM boot thing
Tuesday — Today at 2:40 PM
Remember to do Find & AutoConfig
Blatherman — Today at 2:40 PM
Pretty sure I used GNX_USB
KangaRooskie — Today at 2:40 PM
hmm, still an issue
was able to get SEM lights blinking, but now nothing once I unplugged
nothing in VKBDevCfg, running admin.
blue light on THQ
otherwise nothing
Tuesday — Today at 2:42 PM
Restart machine. Close any and all peripheral related apps (Logitech, Corsair, etc). Run VKBDevCfg as admin
THQ with the grip also needs to be in sub address 4
I’d watch the video and go through the steps
KangaRooskie — Today at 2:45 PM
no dice so far
THQ with grip sub address 4, THQ to the left 3?
Blatherman — Today at 2:45 PM
Is VKBDevCfg recognizing your other controllers?
KangaRooskie — Today at 2:45 PM
THQ-v, 2?
KangaRooskie — Today at 2:46 PM
yes
Tuesday — Today at 2:46 PM
THQ with grip needs to be in sub 4. Other two THQ can be whatever, as long as it’s not 4 and they don’t use same sub
KangaRooskie — Today at 2:46 PM
first time i plugged in the modules they lit up, but the axes were wrong. i reflashed, now nothing
Blatherman — Today at 2:46 PM
As to the lights, I only get a light in my SEM, which is one that has the controller in it. My THQ has no blue light
Tuesday — Today at 2:47 PM
So is it in VKBDevCfg?
KangaRooskie — Today at 2:47 PM
no
not anymore
bootloader doesn't see anything
Blatherman — Today at 2:48 PM
Powered USB hub?
Tuesday — Today at 2:48 PM
See if it recognize it if you unplug the grip
KangaRooskie — Today at 2:53 PM
No, direct
KangaRooskie — Today at 2:53 PM
It recognized it before I flashed
Blatherman — Today at 2:54 PM
I'd highly recommend either using an powered hub (if you have one), or unplugging everything else and trying again
KangaRooskie — Today at 2:58 PM
have had 0 issues with the USB in the past
it's definitely not a power issue. something must have happened when i flashed it
KangaRooskie — Today at 3:16 PM
unplugged the grip
plugging only the THQs. moved the jumpers to force it to sub4
still nothing
@VKB Operator very strange. now going to check to make sure none of the other modules are set to sub4
set up grip as per instructions. plugged in first time, flashed firmware. when the modules restarted, they were no longer recognized by VKBDevCfg. Only the blue light showed up on the THQ with the USB controller.
Unplugged the other modules, plugging in only the two THQs. Unplugged the grip from the board. Still nothing.
Restarted, unplugged, re-installed VKBDevCfg.
KangaRooskie — Today at 3:31 PM
Single THQ not recognized either.
Tested with multiple USB ports. Other VKB devices work perfectly.
VKB Operator — Today at 3:48 PM
Plug only the module with the controller
KangaRooskie — Today at 3:48 PM
done
nothing shows up
VKB Operator — Today at 3:49 PM
is the LED lighting up?
KangaRooskie — Today at 3:49 PM
ok, it finally did
not sure why
the whole time only blue, now im getting blue with red blinking
only 1 module connected (THQ)
jumpers on 1
single module has been recognized
VKB Operator — Today at 3:50 PM
make sure all thqs are on different subaddresses; the one with the german grip has to be 4
KangaRooskie — Today at 3:50 PM
yes, i forced it with the jumpers
VKB Operator — Today at 3:50 PM
sem's subaddress doesn't matter
KangaRooskie — Today at 3:50 PM
right now only the single thq with controller is plugged in
should i reconnect the others?
VKB Operator — Today at 3:51 PM
if one of the thqs is on sub1, then the software setup takes priority
so even if the jumper is on 1, it still could be on other sub if set so through software
thqs on jumpers 2, 3, 4 can't get their subaddress set up through software
does it makes sense?
KangaRooskie — Today at 3:52 PM
ok, so if the other modules are plugged in it doesn't get recognized
now unplugged
single THQ not recognized anymore, solid blue light, no red
VKB Operator — Today at 3:53 PM
are you unplugging from usb before disconnecting the modules?
KangaRooskie — Today at 3:54 PM
yes. ok, now i got it recognized. C1+C2, then set to A1.
Restart
now single THQ with USB controller is showing up
but if I reconnect the others and restart, nothing shows up
VKB Operator — Today at 3:54 PM
try again
KangaRooskie — Today at 3:54 PM
is there a sub address conflict that is causing an error?
ok, should i connect the others while unplugged?
VKB Operator — Today at 3:55 PM
yeah
KangaRooskie — Today at 3:55 PM
ok, connecting THQ to the other THQ (with ww2 grip)
no longer recognized, solid blue
THQ with grip is on sub4 jumper
VKB Operator — Today at 3:57 PM
remove them one by one
KangaRooskie — Today at 3:57 PM
Them?
Image
VKB Operator — Today at 3:58 PM
leave only the master one and post a screenshot please in global/external
KangaRooskie — Today at 3:59 PM
Image
v2.115 firmware. is this wrong?
VKB Operator — Today at 4:00 PM
whole window please
KangaRooskie — Today at 4:00 PM
Image
VKB Operator — Today at 4:01 PM
press the default button
KangaRooskie — Today at 4:01 PM
done
blinking light
VKB Operator — Today at 4:01 PM
same screenshot please
KangaRooskie — Today at 4:01 PM
Image
VKB Operator — Today at 4:02 PM
select the device at the top, then post again
KangaRooskie — Today at 4:02 PM
Image
VKB Operator — Today at 4:03 PM
find&ac, then screenshot
KangaRooskie — Today at 4:03 PM
Image
VKB Operator — Today at 4:03 PM
try the other one
KangaRooskie — Today at 4:03 PM
connect the 2nd THQ?
VKB Operator — Today at 4:04 PM
yup
KangaRooskie — Today at 4:04 PM
doesn't show up
VKB Operator — Today at 4:05 PM
disconnect the second one, disconnect the german throttle grip
plug back the second module to first and try without the grip
KangaRooskie — Today at 4:07 PM
not showing up
(I had these 4 modules w/out the grip and it worked perfectly)
Image
VKB Operator — Today at 4:08 PM
unplug, short the 2 pins on the back of the gnx hid controller with something like a small screwdriver, plug back to usb, remove screwdriver after 2 sec
KangaRooskie — Today at 4:08 PM
two top pins?
VKB Operator — Today at 4:09 PM
yeah, you could see them on the gnx hid controller
labeled boot I think
KangaRooskie — Today at 4:10 PM
didn't do anything
i don't understand because even w/out the ww2 grip we can't get it to work
the jumpers on the ww2 grip's THQ are in the 4 position (brackets)
VKB Operator — Today at 4:12 PM
try again - disconnect usb, connect the 2 pins, plug back, release the pins on windows chime or after a few sec
KangaRooskie — Today at 4:12 PM
nothing.
the blue light comes on
but not recognized
VKB Operator — Today at 4:13 PM
try another usb port please
KangaRooskie — Today at 4:13 PM
sure, although i have done that already
nothing on another port.
it's the same port I've always used, and I just tried my other VKB stuff in that port and it's fine
and I've tried on a powered hub
_GNX_USB_Controller_v2_11_5
this is the proper firmware?
VKB Operator — Today at 4:16 PM
yup
KangaRooskie — Today at 4:17 PM
interesting. tried flashing it again and I got "division by zero"
VKB Operator — Today at 4:17 PM
just restart the software
so you tried other port, same results?
KangaRooskie — Today at 4:18 PM
yes. now I've reflashed
unplugging
no issues plugging/unplugging with one thq
now connecting 2nd thq w/out grip
nothing
now, when i had 4 modules i could still get the SEM into boot mode
but that's it
VKB Operator — Today at 4:20 PM
open the zconfig.ini file, it's in the same folder with vkbdevcfg
KangaRooskie — Today at 4:21 PM
done
VKB Operator — Today at 4:21 PM
just under [Device]
add this line:
GNX_R_MOD=1
save and close
KangaRooskie — Today at 4:21 PM
done
VKB Operator — Today at 4:22 PM
sorry, vkbdevcfg was supposed to be closed
if it wasn't, close it and check the file again
KangaRooskie — Today at 4:22 PM
yeah it's saved
restarted
nothing
Image
VKB Operator — Today at 4:23 PM
plug only 1st thq to usb
KangaRooskie — Today at 4:23 PM
done
VKB Operator — Today at 4:23 PM
on the global/common tab there's a RMOD box, check it, then press Set
KangaRooskie — Today at 4:25 PM
don't see it yet
Image
VKB Operator — Today at 4:27 PM
try this one, delete the previous
Attachment file type: archive
VKBDevCfg-C_v0.92.35_1.zip
8.00 MB
KangaRooskie — Today at 4:28 PM
oh i should have added the fact that i downloaded the latest one
before i did it, everything was fine
then downloaded new devCfg and flashed, and the issues began
ok, i have the new one
VKB Operator — Today at 4:29 PM
check for the rmod checkbox
KangaRooskie — Today at 4:29 PM
Image
VKB Operator — Today at 4:29 PM
close it and chck zconfig
KangaRooskie — Today at 4:30 PM
Image
VKB Operator — Today at 4:31 PM
flash this fm please
Attachment file type: unknown
GNX_USB_Controller_v2_11_8.vkb
75.36 KB
KangaRooskie — Today at 4:31 PM
done
v2.118
VKB Operator — Today at 4:32 PM
rmod?
KangaRooskie — Today at 4:33 PM
don't see anything like that
Image
VKB Operator — Today at 4:34 PM
press Default, run it as Admin
KangaRooskie — Today at 4:35 PM
i don't see rmod. what is it/how will it help?
VKB Operator — Today at 4:35 PM
Image
KangaRooskie — Today at 4:36 PM
right. not sure what I'm doing wrong, but i don't see it. i see it on your screen
I've got zconfig in the same folder as VKBDevCfg-C
VKB Operator — Today at 4:36 PM
any other computer, laptop around?
KangaRooskie — Today at 4:36 PM
I have other things in the same folder
no, not another windows
VKB Operator — Today at 4:38 PM
create a new folder, unzip again in there vkbdevcfg
run it once, close it
then open the zconfig file, add the line again, save, close, run vkbdevcfg
has to be there
KangaRooskie — Today at 4:40 PM
Image
Image
Image
VKB Operator — Today at 4:43 PM
are you running anything like aorus, razer, corsair, logitech, leds management?
what antivirus?
KangaRooskie — Today at 4:43 PM
just windows built-in stuff for antivirus
I do have razer stuff running
but it has never caused a problem until right now
VKB Operator — Today at 4:44 PM
try to turn off anything you don't need
KangaRooskie — Today at 4:44 PM
i haven't installed anything new
i'm not running anything
just discord and this
and everything was fine today before i added the grip
VKB Operator — Today at 4:46 PM
shut off the razer stuff, let's see
KangaRooskie — Today at 4:46 PM
done
no change
VKB Operator — Today at 4:46 PM
have to restart vkbdevcfg and run as admin
KangaRooskie — Today at 4:47 PM
right, done that
VKB Operator — Today at 4:50 PM
try this firmware too
Attachment file type: unknown
GNX_USB_Controller_v2_11_7.vkb
78.55 KB
are you flashing through vkbdevcfg?
KangaRooskie — Today at 4:50 PM
yes
VKB Operator — Today at 4:50 PM
or using the bootloader?
use the bootloader please
KangaRooskie — Today at 4:51 PM
i mean, it opens the bootloader
ok
VKB Operator — Today at 4:51 PM
I know, but it's safer to close vkbdevcfg and run just the bootloader
run it, select the device, press start boot
KangaRooskie — Today at 4:52 PM
done
VKB Operator — Today at 4:52 PM
select again the device after restart, click the ... button
then press flash it
KangaRooskie — Today at 4:52 PM
ok, now it flashed and turned off but not turning on
ok got it
VKB Operator — Today at 4:53 PM
run vkbdevcfg, select the device, press default
KangaRooskie — Today at 4:53 PM
keeps asking me to configure
VKB Operator — Today at 4:53 PM
yes
KangaRooskie — Today at 4:53 PM
done
still no rmod
VKB Operator — Today at 4:53 PM
try to attach the other module
KangaRooskie — Today at 4:54 PM
ok. unplug, reconnect, restart
really appreciate your help, almost out of time for tonight but I'll try this again
VKB Operator — Today at 4:55 PM
alright, buzz me tomorrow. we'll figure it out
KangaRooskie — Today at 4:55 PM
ok wait
now it sees it
with 2 modules
i think
ok, gave me a read data error
restarting
done
2 modules work
VKB Operator — Today at 4:56 PM
try them in tester
KangaRooskie — Today at 4:56 PM
should i connect the other 2?
ok so
VKB Operator — Today at 4:56 PM
yes, the throttle handle too
KangaRooskie — Today at 4:56 PM
find and show shows 2
but
only 1 THQ is set up
VKB Operator — Today at 4:57 PM
you'll have to press again the default, then either yes or press the f&a button
KangaRooskie — Today at 4:57 PM
f&a doesn't show up
also the LED doesn't light up anymore
but in find and show there are 2 THQs
VKB Operator — Today at 4:57 PM
because it's automatic with this software version, remember when you pressed Yes?
so plug them all in, press default, then yes to autoconfigure
KangaRooskie — Today at 4:58 PM
got a windows USB error
right now have 2 THQ connected w/out grip. both show up in Find and Show, but there's only one set up
Image
VKB Operator — Today at 4:59 PM
press default button
KangaRooskie — Today at 5:00 PM
read data error
VKB Operator — Today at 5:01 PM
change port
KangaRooskie — Today at 5:02 PM
done
no change
Image
VKB Operator — Today at 5:04 PM
man
what do you mean no change
select the thing at the top
KangaRooskie — Today at 5:04 PM
right. when i select default it doesn't give me the set up button. and now I'm getting more errors.
error read CPUID
Image
VKB Operator — Today at 5:05 PM
just restart the software
KangaRooskie — Today at 5:06 PM
Image
now an error loop
now whenever I open VKBDevCfg I get these errors
then windows disconnects the device
VKB Operator — Today at 5:09 PM
try a computer reboot
KangaRooskie — Today at 5:11 PM
still errors
plugged in, 5-6 red/blue blinking lights
then error
can't select devicxe
can't select it in bootloader
Image
VKB Operator — Today at 5:13 PM
let's leave it for tomorrow

[fallout9]

If it'd be a firmware issue you'd see more reports about it. Also, I wouldn't recommend you a firmware with issues. Let's please stick to either the Discord or here, doesn't make any sense to spread all around.

[RogoRogo]

I do not want to necro an old thread but I am facing a variant of this problem.
I am using a WWII throttle module connected to a left NXT base (dualsticks plus throttle) and had issues from the start (entire left array of WWII+NXT+SEM-V not recognized, later not booting, aso aso aso).

VKB Support Europe was extremly forthcoming and helpful (fe sending me new PCBs with no questions asked and trying their best to not having me to send controllers in unnecessarily).
And while I was able to finally smash the issues via a powered USB Hub (where again VKB Support made a suitable recommendation, so again - KUDOS!!! in earnest) - the real culprit slowly unveils itself.

ATM I face the following bizarre issue:
Everything works but when I slide the WWII-throttle handle forward (which is aFR-190 throttle grip) the forward grey buttons (49, 50) and the Drezahlregler (buttons 51, 52) just stop working, completely.
This happens when the throttle is slid forward beyond halfway (50%+a increment)
The buttons only regain functionality when the handle is slid backwards below 25%.
The SIDE buttons (53, 54) KEEP WORKING at all times.
As I (just my luck) am using the forward buttons for zoom all the time, this is kind of a problem.
I would enquire if anyone has ever experienced something like this - I was not aware for the longest time since I was slowly isolating the issue, and when stuff worked I was either fakeflying a rotary (slider axis in reverse for collective), or thought of yet another DCS issue or in fakespace where I do not use a throttle.

I am hesistant to yet again open a ticket without trying to gain every little bit of knowledge first - and would be thankfull for any feedback.

[Delta]

That sounds like the cable connecting the throttle grip to the THQ base has gotten pinched somewhere and is getting torn apart - it might stop working entirely at some point, or at least some of the buttons may soon fail. You should look into getting a replacement cable and taking care to route the cable out of harm's way on future reassemblies.

[RogoRogo]

thank you - that is of course something I immediately feared.. but I checked quite often the cable is pristine and all of them are always guided to explicitly avoid chafing). I also checked the plug seating and everything long before doing the writeup.

[fallout9]

He's right though. See if you can replicate the issue without the cover plate, so you can see the cable moving underneath.

[RogoRogo]

well... encouraged by this I opened my left array up again.. And the cables looked pristine.

Then I checked all cables with a magnifying glass, no scorch marks, no rubbing marks, no chafing marks, no overcurrent marks.. nothing.
And then - suddenly - when pulling the strands around, the yellow one... just snapped.
broke in two, at the worst possible location along the strand.
And it looked like the ghost of bruce lee had cold-fusion sliced it... no rip... like a clean ghost-cut.

To say I was devastated was an understatement.
So I tried patch it (badly), it works for now... but I have no idea how this latest issue has come to pass.. none. zero.

[fallout9]

Just fill up a service ticket, they'll send you a spare cable, just be careful when you close the lid.

[RogoRogo]

thank you, and already did - but again.. this is a bizarre mystery.. just a series of bad luck incidents

[denniskoc]

Hey RogoRogo, I have the exact same problem with my ww2 grip and just saw your post.

Same buttons are problematic in same manner. I also figured out that they are potentially stuck under throttle lever.
In my case the way they start or stop to function is more irregular
But didn't see any snap or damage in cables when I opened the case.

I will also try using powered USB hub but they way buttons behave make me think that there is sth physical like loose contact.
But I can't see any damage there.

Please inform us when replacement cables arrive if it solves your problem or not.

Thanks.

[RogoRogo]

Hello,
well, I can safely say that the powered USB Hub (with one button per USB port, so I can leave all my VKB devices connected but powered off when not needed, I also followed as VKB EU private recommendation for the model to use) solved most of my issues.
But I also had a physical cable snap LATER (and a bizarre one at that).
As I know how overwhelming such an outlier problem can be - I will try to update.
For now I have replaced the cable, and everything started working - so a loose contact, an internally broken wirestrand, a plug short, or a strand coming loose in one of the two plugs (in the grip or in the SEM-THQ PCB) could be an issue, even if not visible yet.
If my problem with the grip is finally solved forever, only time will tell (I also changed how I let the cable run to protect even more against any potential chafing by having it loose and in a circle under the connector-PCB in the SEM-THQ (before I had it running exactly like shown in the VKB video).
In my case having to open it so often (first taking my SEM-V out of the merged device, then changing PCBs, and in-between checking for plug and cable issues) might have caused the eventual break in the (yellow in my case) strand...

As the grip opens too rather easily (undo the 4 screws and gently lever the front out) you might want to check the upper, smaller plug and if one of the strands has come loose (i do not know how it is crimped origininally).

But again, I will try to update after a while how it goes.

[denniskoc]

Thank you! I just got a new powered USB hub and will try it right away.

I will also check inside of the upper grip part as you mentioned and see if there is anything broken over there.

[RogoRogo]

well.. I really really REALLY do not want to jinx it.. but so far everything is working reliably.. finally...

If I were a braver man I would now try to remerge my left array and reduce my cabling to the intended two but.. HELLO NO.
I do not want to jinx it.
I do not want to fiddle with it ever again (if possible).
I do not want to change keybinds around.
I just want to enjoy it working reliably (forever if possible).

also
I do not want to jinx it.
I do not want to jinx it.
I do not want to jinx it.
I do not want to jinx it.

Bad luck sometimes comes in way more than threes, or so my personal sampling might suggest.
Pfffffffff