VKB-SIM

New MCG pro twist with black box
Running win 10 Pro
VKB first go appeared , saw joystick clicked on it and went and went into tools and pressed bootLader and it hung
Rebooted and VKB devConfig keeps hanging

viewtopic.php?f=25&t=2762
Save zbootloader.exe into the same folder with vkbdevcfg.exe.
When you press Bootloader button vkbdevcfg.exe will be automatically closed and zbootloader.exe starts. Vkbdevcfg.exe must NOT be launched simultaneously with zbootloader.exe.

I cannot get bootloader working to update firmware on my just delivered Gunfighter PRO MCG EN TWIST Mk2

Rebooted my PC and restarted VKBdevice config and recognised the joystick (GF MCG PRO EN TWIST Mk2) - it let me start the bootloader but it automatically went in to multiple messages Error write data and error read data and then finishes with a message: unable to write to zconfig.ini.
It is saying DEVICE NOT READY , green light on at the top of the window

The blackbox lights go out and it is not seen on Device Manager. I unplug the joystick and replug in and the lights go on and it appears in Device Manager but VKB DeviceConfig just hangs - blue light on and green light on
I reboot the PC and can restart VKBConfig and can do the calibration but I cannot get bootloader to work

I have the latest vkbconfig and bootloader Device config VKBDevCfg-C_v0_91_7_3, ZBootloader-C-v1_18

vkbconfig and zbootloader in same dir with subdir v2_00_7 firmware files

Win10Pro

Help please

ok I have put in a new post as teh bootloader hangs - all are in the same directory

What zbootloader version?
Please describe step by step.
Example.
Run vkbdevcfg.
Click controller.
Press Bootloader button (right?)
What does vkbdevcfg?
What does zbootloader?
What program hangs?
Please show screenshotsof these programs.

VKBDEVICECONFIG closes and bootloader starts but goes into error messages - see attached file.

Look for third party software running. For example Gigabyte Aorus, Raizer, Logitech mouse/keyboard software, MSI Afterburner etc. Try to disable it.

FWIW I've found the most recent versions of devconfig and firmware as of this past Friday did not work and play well with each other. I had some bizarre behavior while the black box was plugged in. It seemed some repeating keypress combo was happening. My folder became read only. Couldn't get to anything to reflash. I reset the black box using the pins and reflashed using older known working combos.

Note: I'm not sure as I'm not at the PC atm but the combo in my sig worked fine. Don't know if that's what I'm using now, I just dropped back a few versions of each to get myself back up and running.

Also as recommended I switched off all other apps eg Aorus, Logitech etc etc anddisconnected all other gear
Then started VKBConfig and it stopped on pressing Bootloader -then bootloader recognised device and flashed it successfully YAY
THANK YOU

Could you please mention for future reference which software you were running.

fallout9 wrote:Could you please mention for future reference which software you were running.

Was just experimenting with this and have replicated the problem. As I said, when it happened before I simply dropped back a couple of versions to what I knew would work not having had this happen. What I had working ok was a combo of config v91. 69 and FW v2. 02.1 which is what that version of config said it was compatible with.

No problems there.

Tried config v91. 73 with the same FW and had no apparent problems. It said it was compatible up to FW v2. 02.4. Thought I'd give it a try thinking I must have just messed something when I flashed it before. Bootloader worked but as soon as the device restarted it locked up. I have sys and pedals lights off (have no pedals), stick light steady green and bus light flashing red. Have to unplug the black box as it won't let me out of the program otherwise. Only way to get back is by shorting the pins in the black box and reflashing. FYI, as stated before when this happens it's also marking my VKB folder and sub folders as read only. I also have to reset those as well before I can even open config.

Will get myself back to the older known versions. Just letting you know what I'm finding.

Update:

Tried a few more combinations. The most updated I seem to be able to use without issue is Config v91.73 + FWv2.02.1. I never DL'd any other FW in between 1 and 4 so no idea about those. I'm guessing this issue isn't with Config but with v2.02.4 of the FW. Some incompatibility at least. Hope this helps.