GNX combo issue

[Sapejape]

I'm using VKB device config v0.93.43 (NJoy32 firmware v2.19.B), the program is running with administration priviledges. On windows 11, newest version.
I've got GNX module combo consisting 4 controllers: THQ(sub 4)->THQ(sub 3) -(USB-C bus cable)> SEM-V -> THQ-V (sub 1), I believe there has'nt been any other "versions" of these controllers. I'm using a powered USB hub.
The 3 THQ controllers have different subaddresses (1,3 and 4), i've modified the using the pins as described in the THQ software youtube video. The sub 4 THQ has WWII throttle grip and is connected to the computer with with the USB controller.

The combo has been working great until this friday. On the sub 1 THQ-V I wanted to combine C2 (physical 31) and C3 (physical 30) buttons to a single button press. I did this with a AND macro, so that physical 31 AND 30 -> virtual 30
Then the problems started. immediately button presses on THQ-V started to froze, and all the axes on THQ sub 4 went wonky.

First I tried to revert the changes by setting previous settings and set these on the controller. After this VKBConfig wouldn't anymore recognize the last 2 controllers. I tried to reset and configure without avail. I managed to save the problematic profile here https://www.dropbox.com/scl/fi/mq19olmy1bobfkls7corn/NXT-SEM-THQx3.cfg?rlkey=2y78k1vsrl0g4iclnv0o1tgal&st=6x6getzr&dl=0
I tried USB controller on each controller to rule out hardware problem and I verified the subaddresses. They all worked as a single unit with the GNX USB controller, therefore it shouldn't be a hardware problem.
I tried to flash the USB controller with newest firmware (_GNX_USB_Controller_v2_19_9.vkb). I did this with Zbootloader v.1.96 which is the newest version on the VKB website. After this the controllers woudn't work together at all.

The THQ sub 4 controller works as a single unit, reporting as VKBsim NXT XT2 v2.199 (attachment, screenshot)

When I try to plug in the other adjacent controllers there is a read data error / CPUID error / CRC error "profile not verified". After few seconds Windows tells me that the USB device malfunctioned and the controllers shut down. The device manager informs me that the device can't be started (code 10)
After this i've tried
-connect the controller directly into the computer bypassing the USB hub
-firmware _GNX_USB_Controller_Mod_Start_v2_19_9.vkb (managed to flash when only THQ is connected)
-starting the device with BOOT bins.
-turned off all other USB background programs, LED programs while configuring
-connecting only the adjacent THQ (sub 3). With the boot pins the controllers stay on, but USB device malfunction soon and VKBconfic gets stuck on repeating error messages "Access violation at adress...."
On a other thread i noticed that one could "save" a .opi file from ZBootloader, i'm guessing its from the GNX USB controller. so I did that. Its here https://www.dropbox.com/scl/fi/nat85v68ux2u9nlzqb2eu/56564135.op1?rlkey=f5g2jcd9iai8mgc73nwbbr9qi&st=ev2upc0n&dl=0

I'm guessing the issue is with the GNX USB controller? Any suggestions?

[Sapejape]

I also tired to swap all 4 pin JST wires connecting the GNX modules and USB BUS wires. It didn't resolve the issue.

[Sapejape]

I tried so set new subadresses to THQ units via pins: THQ (sub 4, with WWII grip) -(JST 4-pin)> THQ (sub 3) -(USB)> SEM-V -(JST 4-pin) -> THQ-V (sub 2)
I avoided using subadress 1 on THQ modules, since i believe this whole mess began with the THQ-V module with this subaddress: when the jumpers are in sub 1 mode the subadress can be modified via buttons.
What I believe happened is this: during controller reset I tried the new C1+C2 combo too soon which put the THQ-V into the subaddress choosing mode, and this somewhow messed the GNX USB controller
But the issue remains nontheless.
Edit: kept the subadress 4 with WWII since the grip only works in this subaddress

[Ron61]

Try the latest firmware and configurator from here. Pay attention to the file _GNX_USB_Controller readme.txt in the folder with firmware for GNX devices.

[Sapejape]

Should I use zBootloader v.1_97 with the newest date, or v.2_01 with the highest version number?

[Ron61]

Better is the latest v.2.01.

[Sapejape]

I downloaded newest (to date) firmare (v2_19_D(3)), VKBDevConfig (VKBDevCfg-C_v0.93.36) and zBootloader2 (v1_97)
With only THQ sub 4 (with GNX usb controller) connected, I flashed it with the firmware _GNX_USB_Controller_v2_19_D.vkb.
The controller is recognized correctly. Then I connected the other GNX units.
Result: When the other units are connected the USB device malfunctions, windows gives code 43 in the device manager
Then I flashed the THQ unit with firmare _GNX_USB_Controller_Mod_Start_v2_19_D
Result: the issue remains
I tried the BOOT pins
Result: the controller stays on, and VKBDevConfig recognizes the device as zBoot Njoy v02.31
I flashed it again with _GNX_USB_Controller_Mod_Start_v2_19_D
Several read error messages (pic attached)
Result: VKBDevConfig recognizes the device as zBoot Njoy v02.31
I flashed it with _GNX_USB_Controller_Mod_Start_v2_19_D
Result: USB device malfunctions again.
I tried the BOOT pins. The device stays on about 10 seconds, led shows blinking dark blue, red, purple lights meanwhile.

I switched to zBootloader2 v2_01, and flashed THQ sub 4 unit with firmware _GNX_USB_Controller_Mod_Start_v2_19_D
Again when the other units are connected, the device malfunciotns, and wont started even with BOOT pins

[Ron61]

Try to connect one THQ module to the module in which there is a HID controller and it is detected normally, reset the settings to default and do autoconfiguration.
Show a screenshot of the Global-External-External devices tab after this.
Then connect another module and repeat the procedure again - reset to default-autoconfiguration- show a screenshot. And so repeat until the faulty link is identified.
Photos of the module connections are only welcome.

[Sapejape]

Connected modules THQ sub 4 to THQ sub 3 with a 4-pin JST
With regular firmware the device malfunctions. I tried both JST slots on the right side on the sub 3 THQ, nothing changed. I also tried to connect via USB-C bus link (JST 4 -pin to USB-C cable), the same issue. Also when sub 4 THQ was connected to sub 2 THQ-V with this cable.
With firmware _GNX_USB_Controller_Mod_Start_v2_19_D and boot pins the controller units stayed on, but VKBDevCfg reports it as an zBoot Njoy 32 device (attachment 1). ZBootloader reports "Read error data 0"

I switched the GNX USB controller to the sub 3 THQ, in case the broken link is the sub 4 THQ. The unit was recognized normally (attachment 2). Autoconfigured. Then I connected THQ sub 4 with 4-pin JST. The device malfunctions.
Using JST 4 pin to USB-C cable, I connected THQ sub 3 (now with the GNX USB controller) to the THQ-V sub 2. The device malfunctions.

Therefore I can't connect and configure any extra unit to USB controller. It seems that the GNX USB controller can't handle now more than one unit, for some reason

edited.

[Sapejape]

Pics of connections as attachments
Edit. HTTP error, put them in dropbox here https://www.dropbox.com/scl/fo/nvz472mnsmolljacwzgxe/AO8zaq_WQiin8FPVQcMba5g?rlkey=2ldimh85penjxqsrkolf7rlwc&st=gtemb9o8&dl=0

[Ron61]

Move the HID controller to SEM, leave THQ-V connected to it. That is, we are configuring only two devices for now.
Reset to default and do autoconfiguration - show a screenshot of the Global-External tab.

[Sapejape]

Switched GNX USB controller to SEM-V module. Autoconfigured. Again as a single unit it works fine https://www.dropbox.com/scl/fi/v2eboplebmzpobni24tee/Screenshot-2025-07-20-172422.png?rlkey=ftngghl85317vklijm449nee1&st=2muvxihv&dl=0
I connected adjacent THQ-V with 4-pin JST. Again malfunctioned, code 43 in device manager
Then I tried to connect SEM-V via JST-USB cable to the desktop THQ units separately. Again, both combinations malfunctioned (THQ sub 4 and 3 were not connected inbetween during this)

[Ron61]

Move the controller to each module one by one and check the functionality.
Then connect any module (the bundle will be made up of only two) and flash the firmware _GNX_USB_Controller_Mod_Start_v2_19_C.vkb - screenshot after reboot.

[Sapejape]

1) Put GNX USB controller to THQ-V (subadress 2). As a single unit, worked fine. Defaulted and autoconfigured. Buttons and axes responded normally https://www.dropbox.com/scl/fi/jhdhwuoqopou8sr1tadjy/THQVsub2.png?rlkey=hea2inqcmsrox1icsgs680gdp&st=dsxby96w&dl=0.
-connected it to adjacent SEM-V via 4 pin JST. USB device malfunctioned (code 43 in device manager). Tried BOOT pins, again malfunctioned. Disconnected the unit from THQ-V.
-connected it to THQ (subaddress 3) via JST-USB cable. USB device malfunctioned (code 43 in device manager). Tried BOOT pins, again malfunctioned. Disconnected the unit from THQ-V.
-connected it to THQ (subaddress 4) via JST-USB cable. USB device malfunctioned (code 43 in device manager). Tried BOOT pins, again malfunctioned. Disconnected the unit from THQ-V.
2) Put GNX USB controller to THQ unit (subaddress 3). As a single unit, worked fine. Defaulted and autoconfigured. Buttons and axes responded normally https://www.dropbox.com/scl/fi/haovylhrhmb0amjlezna7/THQsub3.png?rlkey=2czjt9h1lmzgllogowee1cj2v&st=vjrtux3p&dl=0.
-connected it to adjacent THQ (subaddress 4) via 4 pin JST. USB device malfunctioned (code 43 in device manager). Tried BOOT pins, again malfunctioned. Disconnected the unit from THQ.
-connected it to THQ-V (subaddress 2) via JST-USB cable. USB device malfunctioned (code 43 in device manager). Tried BOOT pins, again malfunctioned. Disconnected the unit from THQ.
-connected it to SEM-V via JST-USB cable. USB device malfunctioned (code 43 in device manager). Tried BOOT pins, again malfunctioned. Disconnected the unit from THQ.
3) Put GNX USB controller to THQ unit with WW2 grip (subaddress 4). As a single unit, worked fine. Defaulted and autoconfigured. Buttons and axes responded normally https://www.dropbox.com/scl/fi/y2ujfaaubj7zlpvg8zghv/THQsub4.png?rlkey=oovgckixpuodcrnps3lfhhfxk&st=x4h0ir4g&dl=0.
-connected it to adjacent THQ (subaddress 3) via 4 pin JST. USB device malfunctioned (code 43 in device manager). Tried BOOT pins, again malfunctioned. Disconnected the unit from THQ.
-connected it to THQ-V (subaddress 2) via JST-USB cable. USB device malfunctioned (code 43 in device manager). Tried BOOT pins, again malfunctioned. Disconnected the unit from THQ.
-connected it to SEM-V via JST-USB cable. USB device malfunctioned (code 43 in device manager). Tried BOOT pins, again malfunctioned. Disconnected the unit from THQ.
4) I tried this with USB controller in SEM-V unit yesterday, the same result.

Hence I can't flashthe firmware to a 2-unit combo, since the the devices malfunction in any combination. When they malfunction, ZBootloader won't recognize them also.

[Ron61]

Managed to repeat your problem and found a solution.
Assigning subaddresses is possible in two ways - only by rearranging jumpers or by buttons (entering the configuration mode - hold down C1 + C2 on the THQ module before connecting the cable and buttons A1-A4 - subaddress number), but for this both jumpers must be set to the upper position, as for sub1.

As a result of erroneous actions, you can get the following situation.
For example, if the jumpers are set to 2 sub, but before connecting the USB cable, hold down C1 + C2 and assign a different address, for example, 3 sub (by pressing A3), then after rebooting the controller will not appear in the list of devices and there will be error 43.
And in this case, even the "hardware" transfer of the controller to bootloader mode by shorting the "Boot" pins may not work.
In USB3, it may not start. It seems that the LED is blinking, but there is no device in the configurator.
Only after connecting it to the USB2 port did it appear in the configurator.
You can try running it naked, removed from the module. The main thing is that it appears in the configurator.
So, we set the jumpers in all THQ modules to the upper position, and by moving the controller to each THQ module one by one, we assign the desired subaddress.
Keep in mind that when assigning an explicit address with the A3 (sub3) button when entering the configurator, another one may be shown that does not match the assigned one if you press the Find&Show button.

You should reset it to default and after rebooting, the addresses will already match.