Everything worked fine when I first set it up, then I started finding that the entire EVO+SEM would not appear in vkbconfig after the computer woke up from sleep. At first, changing usb would fix it. That not longer works. After shorting the boot jumpers I was able to flash the EVO to 2.10.3 which resulted in vkbdevconfig identifying the joystick, but not the SEM. After screwing around with unplugging the SEM and reflashing and other stuff, I got the SEM to detect. I ran the setup from the youtube video, and as soon as I hit C1 to commit the SEM vanished from vkbdevconfig and hasn't been detected since.
Since then I have found that committing the SEM setup by pressing C1 will consistently kill the entire gladiator EVO so it cannot be detected by vkbdevconfig, even when replugging into different USBs. Disconnecting the SEM will fix it, and reconnecting the SEM will let me boot it into setup mode to repeat the loop. I cannot progress past pressing C1 to commit the SEM setup. However, after rebooting a few times and leaving the computer asleep at night with the SEM disconnect, it appears that the EVO is no longer having issues with detection after sleep.
In summary, current situation step by step:
1. Plug in and calibrate Gladiator EVO without SEM connected.
2. Connect SEM on the right side (because the OTA interferes with the flaps axis on the left).
3. Connect the EVO + SEM to USB while holding B1/B2/B3. The SEM successfully boots into setup mode.
4. Press A1 to set up flaps, then press start because I removed the detent. ( have tried a variant where I press start before trying flaps setup to confirm the sub address, which changes nothing).
5. Press A2 to set up landing gear, then press B1 because I have the 2 notch detent installed.
6. Press C1 to commit. The SEM LEDs go dark.
7. Disconnect and replug the base into USB. There is no windows chime, and the EVO is not detected in vkbdevconfig at all.
8. Only way to regain use of the EVO itself is to disconnect the SEM and then replug USB, after which the EVO is detected by Windows and vkbdevconfig as usual.
In reiterate, this entire thing (EVO + SEM) was working fine originally, and I am trying to set it back up after flashing to most recent firmware while trying to fix the issue where vanishes after sleep, which in retrospect seems to be related to the SEM.
Attached is my config with the SEM disconnected.
