Page 1 of 1

Gladiator Pro configuration problems

Posted: Thu Sep 29, 2016 12:49
by KPX
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
VKBGP-4.jpg

VKBP-2.jpg


VKB_JoyTester : OK

VKB_BtnTester : OK

Re: Gladiator Pro configuration problems

Posted: Fri Sep 30, 2016 15:07
by KPX
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 :
VKBP-13.jpg
VKBP-13.jpg (4.37 KiB) Viewed 7092 times

CH-Products :
VKBP-12.jpg

Device manager :
VKBP-11.jpg

Re: Gladiator Pro configuration problems

Posted: Fri Sep 30, 2016 15:28
by Ron61
Read this.

Re: Gladiator Pro configuration problems

Posted: Fri Sep 30, 2016 15:34
by Bourrinopathe
The Gladiator and Gladiator Pro share the same controller. That's why the name appears as "VKBsim Gladiator". Fortunately, no issue here at least :wink:

----

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… :roll:

Re: Gladiator Pro configuration problems

Posted: Sat Oct 01, 2016 11:28
by KPX
Ron61 wrote:Read this.


Hello, --- one step beyond...

As Ron61 suggested:
1. I put wizzo,vkbdevcfg,zbootloader and firmware file in same directory.

VKB2-1.jpg
VKB2-1.jpg (14.83 KiB) Viewed 4871 times



2. I run wizzo, select "advance setting", then select bootloader button.
This "unplugged" joystick and I got message saying joystick is not connected.

VKB2-2.jpg

VKB2-3.jpg


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

Posted: Sat Oct 01, 2016 11:36
by KPX
As I cannot attach more than 3 files,I will place other screenshots here

Zbootloader not detecting device ( point 3 in previous post).
VKB2-4.jpg


At this moment, I just unplugged and plug Joystick (Zbootloader still running) -> VKBDevCfg starts by itself and I could flash hardware.

VKB2-9.jpg


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 :

VKB2-6.jpg


What to do now ?

:shock: 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.