Hello,
I just installed the device and it is recognized by Windows (diview,joy and button tester OK).
I used wizzo to calibrate the joystick -> OK I could apply without problems.
Problems :
1. wizzo ; using bootloader, it tells me that the joystick is not connected,wizzo closes and the joystick is virtullay unplugged (no more signal in diview ). I have to physically unplug and plug again the usb connector to get back the device !
2. when I run VKBDevCfg : nothing happens. I only get a zconfig.ini file.
What can I do to be able to use those software. For the moment I have a Joystick that I cannot configure and cannot update firmware
I run on windows 10.
Best regards.
I DONE SAME TESTS ON SEVERAL COMPUTERS (WINDOWS 10 AND XP). SAME PROBLEMS. THESE OTHER COMPUTER DIDN'T HAVE OTHER JOYSTICKS.
Wizzo : V.0.73 (firmware v1.80.1)
Tried with no success :
VKBDevCfg-C_0_77_5_5
VKBDevCfg-C_v0.77.66
Those apps create only a zconfig.ini file with :[Common] Expert Mode = 0
no other error messages
ZBootloader-C.exe : window display : device disconnected though the joystick is seen in diview
VKB_JoyTester : OK
VKB_BtnTester : OK
Gladiator Pro configuration problems
Moderator: AdminGroup
Re: Gladiator Pro configuration problems
Could it be that the joystick is seen as a Gladiator and not a Gladiator Pro ?
In the device manager, the CH-Products joystick appear but not VKB Sim.
Here how the VKB Gladiator Pro is seen on my computer :
CH-Products :
Device manager :
In the device manager, the CH-Products joystick appear but not VKB Sim.
Here how the VKB Gladiator Pro is seen on my computer :
CH-Products :
Device manager :
- Bourrinopathe
- Posts: 126
- Joined: Wed Oct 07, 2015 9:35
- Has thanked: 88 times
- Been thanked: 60 times
- Contact:
Re: Gladiator Pro configuration problems
The Gladiator and Gladiator Pro share the same controller. That's why the name appears as "VKBsim Gladiator". Fortunately, no issue here at least
----
Just tested: trying to update the firmware following the aforementioned steps does not work. (wizzo 0.73 + Z-Bootloader 0.97 + firmware, from the FTP, in a dedicated folder (E:\WIZZO))
Same error message.
Windows 10 64bit
wizzo.exe ran with admin rights and I unplugged my other peripherals (only keyboard + mouse left).
The Gladiator axes are responsive in Wizzo and the current firmware version is displayed correctly.
The bootloader appears correctly when using the VKB Device Config.
Ah complexity…
----
Just tested: trying to update the firmware following the aforementioned steps does not work. (wizzo 0.73 + Z-Bootloader 0.97 + firmware, from the FTP, in a dedicated folder (E:\WIZZO))
Same error message.
Windows 10 64bit
wizzo.exe ran with admin rights and I unplugged my other peripherals (only keyboard + mouse left).
The Gladiator axes are responsive in Wizzo and the current firmware version is displayed correctly.
The bootloader appears correctly when using the VKB Device Config.
Ah complexity…
/// ВКБ Black Mamba MkIII / ВКБ T-Rudder MkII / ВКБ Gladiator / X-55 Rhino throttle / OpenTrack /// UTC +4 ///
Re: Gladiator Pro configuration problems
Ron61 wrote:Read this.
Hello, --- one step beyond...
As Ron61 suggested:
1. I put wizzo,vkbdevcfg,zbootloader and firmware file in same directory.
2. I run wizzo, select "advance setting", then select bootloader button.
This "unplugged" joystick and I got message saying joystick is not connected.
3. I run zbootloader and had the message : device not connected etc...
4. While zbootloader was running I just unplugged an plugged again my device.
5. Miracle ! VKBDevCfg ran automatically. I could update the firmware via bootloader (zbootloader -> flashit)
6 I can now update the firmware.
Other problem now : I still cannot configure the button. Each time I run "button wizzard", I get a message :
Access violation at address 004D4984 in module "VKBDevCfg-C.exe".
Write of address 000002D1
What can I do now to be able to configure Gladiator ?
Re: Gladiator Pro configuration problems
As I cannot attach more than 3 files,I will place other screenshots here
Zbootloader not detecting device ( point 3 in previous post).
At this moment, I just unplugged and plug Joystick (Zbootloader still running) -> VKBDevCfg starts by itself and I could flash hardware.
I can now run VKBDevCfg. I still have a problem : button wizzard does not work, each time I try to activate it, I got this message :
What to do now ?
The access violation problem was due to the fact that only the upper part of the interface of VKBDevConf. The part with "common" and "external" (I do not know why).
I replaced my zconfig.ini file by a zconfig.ini file given to me by Bourrinopathe. Now I have the full interface displayed and the button wizzard is working.
So, for the moment it seems that everything seems OK.
Thnaks for helping.
Zbootloader not detecting device ( point 3 in previous post).
At this moment, I just unplugged and plug Joystick (Zbootloader still running) -> VKBDevCfg starts by itself and I could flash hardware.
I can now run VKBDevCfg. I still have a problem : button wizzard does not work, each time I try to activate it, I got this message :
What to do now ?
The access violation problem was due to the fact that only the upper part of the interface of VKBDevConf. The part with "common" and "external" (I do not know why).
I replaced my zconfig.ini file by a zconfig.ini file given to me by Bourrinopathe. Now I have the full interface displayed and the button wizzard is working.
So, for the moment it seems that everything seems OK.
Thnaks for helping.
Who is online
Users browsing this forum: No registered users and 77 guests