VKB-SIM

Hi,

Like a number of posts I have read through now, my right Gladiator premium space edition stick has stopped working for no reason. I have had both this and a left omni for about 1 and half years. When I first got them, followed the instructions for bootloader and VKBDevCfg and had no issues with them. I haven't used them in a little while and fancied playing a space sim only to find that the right stick was not being found. Blue base light was on but top one was off. Thought I would repeat everything from previous however the device name comes up as zBoot Njoy32 v02.31. When I try to install the firmware, I get multiple error messages. Through my testing over and over (probably about 5 hours of my time wasted now), I have seen predominantly error read data & CRC errors. There has been the odd occasion that the blue light on the base has gone off and only a red light flickered.

I had no issue updating the firmware on the Omni.

I have tried:

Different USBs
Different Cables
Checked internal cables and look correct
Resetting using the F keys on the base
Resetting using screwdriver to short device
Deactivating all other apps so they do not interfere with the process through run app - typing "msconfig"
Tried on an alternative device (laptop)
Cannot use VKBDevCfg to default the stick as I understand that zBoot Njoy32 v02.31 means it is in bootloader mode. Just wont accept the firmware.

I have read so many forums for ideas and clues of how to get past this issue, but none appear to work for my stick. It has become quite deflating frankly, especially as they haven't been used that much in the time I have had them.

Is there anything further that can assist me please? Or Is my device somehow just bricked? Appreciate any assistance here.

Are you using a specific mouse/keyboard software, such as Sinapse or AORUS?
Try USB-Hub just in case (unlikely to help)
I think you need to open a ticket with the dealer.

Hi Alex,

Sorry I am not the most tech savvy...

I have the Logitech Hub for mouse/keyboard if thats what you mean?
USB-Hub? You mean single entry into pc with x many USBs coming off it? If so, I dont have one and unsure why that would make much difference?

Sinapse or AORUS send packets to all USB devices, which is actually an attack. Early VKB F1 series devices perceived this as a hacking attempt, on modern G4 series controllers this should not affect - but you never know. Also, I have not yet explained the fact that firmware upload via USB hub occurs in 3-4 seconds, while firmware upload via motherboard ports can take 20-30 seconds. Neither the device nor the bootloader can know which ports they work through. These are the tricks of the operating system.
But at the same time, controller problems are not excluded.

In your case, I am inclined to think that the problem is with the controller itself, but it is necessary to exclude potential options.