SEM Module not showing up in VKB Device Config

[kneemoy]

I just got an SEM module for my dual evos, and after following VKB's video guide, I can't seem to find the SEM module in the device list in the config. Am I missing something?

[fallout9]

Post a picture with the 2 connected devices, showing the connections from underneath.

[kneemoy]

I have this exact setup. Right stick with SEM on the right. I can hold F1 and F2, and both devices show up in config, but as soon as I calibrate, both devices disappear. Connected from bus3 on SEM to Ext2 on the EVO. Unfortunate

[kneemoy]

Today, neither the EVO nor the SEM are showing up in config. This is how I have it connected.

[fallout9]

Could you try other computer ports (no extension/hub please)? Or even a different computer if available?

[kneemoy]

It looks like the issue is with the BUS3 and EXT2 connections on both the SEM and EVO. When specifically using those two connections, (Right handed stick with SEM on right side) it faults out the USB connection and makes it seem like there's an error with the USB device in Windows. The only fix I've seen is swapping the module to the left side of the right stick. I get no issues when its connected that way. perhaps a longer cable could be used to bypass this error with the ports?

[fallout9]

How about another computer port or a different computer - same situation?
Could you post your system information (Win+R, msinfo32)?

[kneemoy]

So no other ports on my pc seemed to fix the issue. and I don't have another computer I can try it on. Here is my System Summary:

[Sochin]

I'm having the same issue with the same connections. It is maddeningly inconsistent. 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.

I'm going to try switching the SEM to the left side to use the other connection, but that isn't a practical solution because the Omni throttle collides with the flaps axis when the SEM is installed on the left. Assuming it works, this whole issue could be avoided if the cable was long enough to reach the connection on the left side of the base.