I just received my Cyborg 2 and after a lengthy session adjusting the device to my hand, I finally got to setting up my base profiles. The plan was:
After configuring this, the software became laggy/less responsive/delayed. At this point, I noticed the profile switching on the device itself did not work anymore, nor were any keys registering on my System. After unplugging the device, it wasn't recognized in the software anymore. Still no button presses were registering anywhere and profile LED did not change after triggering the button. After starting the device in bootloader mode by accident, I could reset the device inside the software on the next plug-in.
Profile switching worked again with the defaults, and changing single buttons had no ill effect. However, changing the Joystick to Xbox 360 mode again, froze it right back up, and I had to redo a reset as above.
Using current Azeron software (v1.5.4) and device already has the latest firmware (v99b) installed.
Tried reinstalling v99 firmware as well as the new performance firmware inside Azeron software but got an error. Attempted the manual firmware install as described on the site and video using STM32CubeProgrammer. In Boot-mode, the device is recognized as STM32 Bootloader in the device manager, but the Programmer software did not recognize any USB device. Reinstalling driver did not work.
Sort of at my wit's end here and suspecting a faulty board/firmware error that isn't fixable by me. Any other things I could try? Or do I need to start a replacement request?
UPDATE: Tried mapping 360 Joystick to the device from a different Windows machine with a fresh OS install, and it worked without a problem. I mainly game on Linux, however, so I only needed the software for the configuration of the base profiles. Everything seemed to work well in Linux EXCEPT the analog stick in the 360 profile. As soon as I switched to this profile and touched the stick, the device froze and sent no more button presses to my system. All other buttons in this profile worked until then. Figured out the reason for this: no drivers were being loaded by the Linux system, so keyboard input didn't pose a problem, but 360 Analog could not be interpreted. Fixed this by configuring xpad to load an xbox360 driver for the device and everything is now working fine.
To summarise, I seem to have had a bad driver interaction with my main Windows machine, which was fixed using a fresh install and a different system. Additionally, my Linux environment failed to load any driver for the Cyborg, which needs to be corrected manually. Device and firmware were working fine this whole time, just some bad luck with my system during initial configuration.
- Basic keyboard profile with Joystick as WASD
- Basic keyboard profile with 360 Joystick
- Basic Joystick profile
After configuring this, the software became laggy/less responsive/delayed. At this point, I noticed the profile switching on the device itself did not work anymore, nor were any keys registering on my System. After unplugging the device, it wasn't recognized in the software anymore. Still no button presses were registering anywhere and profile LED did not change after triggering the button. After starting the device in bootloader mode by accident, I could reset the device inside the software on the next plug-in.
Profile switching worked again with the defaults, and changing single buttons had no ill effect. However, changing the Joystick to Xbox 360 mode again, froze it right back up, and I had to redo a reset as above.
Using current Azeron software (v1.5.4) and device already has the latest firmware (v99b) installed.
Tried reinstalling v99 firmware as well as the new performance firmware inside Azeron software but got an error. Attempted the manual firmware install as described on the site and video using STM32CubeProgrammer. In Boot-mode, the device is recognized as STM32 Bootloader in the device manager, but the Programmer software did not recognize any USB device. Reinstalling driver did not work.
Sort of at my wit's end here and suspecting a faulty board/firmware error that isn't fixable by me. Any other things I could try? Or do I need to start a replacement request?
UPDATE: Tried mapping 360 Joystick to the device from a different Windows machine with a fresh OS install, and it worked without a problem. I mainly game on Linux, however, so I only needed the software for the configuration of the base profiles. Everything seemed to work well in Linux EXCEPT the analog stick in the 360 profile. As soon as I switched to this profile and touched the stick, the device froze and sent no more button presses to my system. All other buttons in this profile worked until then. Figured out the reason for this: no drivers were being loaded by the Linux system, so keyboard input didn't pose a problem, but 360 Analog could not be interpreted. Fixed this by configuring xpad to load an xbox360 driver for the device and everything is now working fine.
To summarise, I seem to have had a bad driver interaction with my main Windows machine, which was fixed using a fresh install and a different system. Additionally, my Linux environment failed to load any driver for the Cyborg, which needs to be corrected manually. Device and firmware were working fine this whole time, just some bad luck with my system during initial configuration.
Last edited:
