VKB-SIM

Hi,
Just received a Kosmosima today to go on my Gunfighter Mk1 am have been trying for hours to flash to new firmware for it. I am have having a real problem with the bootloader not finding the device. Have tried as the instructions say, removing Razor, Logitec and Thrustmaster Software so it doesn't interfear but to no avail it just keeps iterating through read / write errors as shown in picture. Please Help!

Note: - With the MCG Pro Grip every thing is working fine.
- While the bootloader is running there are no lights on the Blackbox and I have to exit, run VKBDevCfg-C again, click on the VKB Boot Njoy32 platform v00.56 : HID-compliant vendor-defined device is and press Restart to get the Gunfighter to be connected again.
- Have tried with both the Blackbox's I have ( 1 extra came with T-Rudder ) and have looked at doing a hardboot via the Blackbox's PCB terminals, however the picture shown on Alex's site looks quite different to the one's I have and am not sure the of the correct terminals
- I have downloaded the latest firmware and VKBDevCfg-C v0.89.79 , also the ZBootloader 1.15
Thank you for your time.

If the hardware loader detects requests to the device that do not comply with the firmware protocol, it stops the process and reports unavailability.

These requests can send different programs:
VKB
1.VKBDevCfg-C.exe
2. T-Link.exe (not confirmed)
3. Z-Link(2).exe (not confirmed)
4. Wizzo

non VKB
1 Software / drivers for mice and keyboards
2 AORUS GRAPHICS ENGINE ( Gigabyte )
3. Razor Synapse


You need to temporarily deactivate this kind of program

Thank you very much Alex. It was the AORUS GRAPHICS ENGINE ( Gigabyte ) causing the problem. All booted up now.

Cheers

Awesome I had the same problem. I disabled my AORUS Graphics Engine and Razor Synapse programs and now the boot loader works great. Thanks

Thank you, add Razor Synapse to list.

I am having the same issues as listed above.

I have a Gladiator Pro MII and I just received the SCG grip and get a coms error with the stick. There is a coms error when flashing. The base buttons all work and it wants to see the stick but in the external tab the scg stick is red and shows a coms error.

K12 and MCG pro sticks no issues.

Any help would be appreciated.

I also did not see any software as described above.

The joystick is seated properly as well.


VKB Gladiator Pro Mk.II Firmware w/ Kosmosima Support (v1.96.7)
VKBdevCfg (v0.89.7.6)
ZBootloader (v1.15)

Have been think about this and why the AORUS GRAPHICS ENGINE would interrupt boot. Well I am guessing it is to do with LED's, but only the software developers would know for sure.
Still could be worth a try, what is there to lose? If you have any program that does anything with LED colour, pulses & etc. configuration try disabling it.

Thank you for the reply,
I did disable my Logitech software to no avail


I wonder if the joystick was DOA?

Targ> take it from the beginning:
Download the newst VKBdevCfg from here: https://vkbcontrollers.com/?product=vkb ... n-software
Download ZBootloader from here: https://vkbcontrollers.com/wp-content/u ... -v1_15.zip
Copy the ZBootloader in the same folder with VKBdevCfg
Download the firmware for Gladiator Pro+ Kosmie from here: https://vkbcontrollers.com/wp-content/u ... 1_96_7.zip
Open VKBdevCfg.
Open the Tools tab, press Bootloader. In Bootloader indicate the location of your firmware and load it up. The VKBdevCfg will restart.
Press the Default button to reset your device.
Try again and see if it works now.

I did all of that and still the same issue.

No coms with the stick. The base works fine, just not the stick. I have checked and rechecked that the grip is connected properly to the base but nada


Would pasting my DXDiag mean anything to and be helpful to post?

You could also get in here: http://alex-oz.strana.de/index.htm and take the latest Gladiator+Kosmo firmware (there are LH and RH versions) and VKBdevCfg v89.98. Zbootloader is the same so yours is still good.

I tried the those as well with no luck.

It's almost like the BOOT on the circuit board needs to be reset but I am not sure how to do that. I can see BOOT (very small txt) on the main board but there are no jumper pins on it.

Check the same website for hardware reset instructions.
What else I'd do - try to connect the controller to a different computer or at least to a different USB port, 2.0 preferably. On a fresh computer reboot try to run all the steps a few times over and over with all the funky apps like the ones mentioned above turned off.

I checked the website and although it says that you can reset the jumpers on the circuit board it does not indicate how that may be done. I see no jumper pins even though I can see where it says BOOT on the circuit board.


I have tried different USB ports and I am not sure what changed as I have swapped grips before with no issue. The only thing I have not tried is to short the BOOT jumper. If someone can answer how to do that it would be appreciated.

If that does not work than it is a defective stick.

- Close VKBdevCfg if it is currently running
- Disconnect your device from the USB port
- Gain access to the PCB (printed circuit board)
- Launch ZBootloader; you should see this message: "Boot device: turn out"
- Short the "Boot" pins (you can use the tip of a flat hat screwdriver) identified with 'boot' (keeping them shorted until after the next step)
- With the Boot pins still shorted, plug the joystick back into the USB port (Boot pins MUST remain shorted during this process)
- The ZBbootloader app will automatically recognize the joystick being connected to the PC again; you should see the following message: "Boot device: detected - OK"
- Clear the Boot pins to ensure they are no longer shorted
- From within ZBootloader, select the appropriate firmware for your device and click "Flash It!"
- After successfully flashing, ZBootloader will automatically close (and, if VKBdevCfg is stored in the same folder as ZBootloader, it will be launched automatically; if not, launch VKBdevCfg as Admin manually)
- From within VKBdevCfg, continue to calibrate all device axes