Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues when switching computers using a KVM #189

Open
1-lost-cause opened this issue Nov 18, 2024 · 9 comments
Open

Issues when switching computers using a KVM #189

1-lost-cause opened this issue Nov 18, 2024 · 9 comments

Comments

@1-lost-cause
Copy link

Hello, I found this repo and gave it a shot. Everything has worked great, but today as I tried to change inputs in my KVM (TESmart HKS402-P23-USBK) and I have the device (singe rasperry pi pico) connected to one of the standard USB connectors (vs the ones where the KVM intercepts the HID inputs for special hotkeys that it uses), and everything works fine until I try to switch from one PC to another. The device becomes unresponsive until I remove the mouse's dongle (Kensington Expert Mouse Wireless Trackball) from the rasperry pi and put it back in.

I'm still pretty new to using custom boards with these custom boards, but it seems like there could be some sort of setting or something that could "reset" the connection from the USB dongle?

@jfedor2
Copy link
Owner

jfedor2 commented Nov 18, 2024

We've had similar reports (#146) in the past, I didn't get around to investigating it properly yet. My guess was that the device plugged into HID Remapper goes into suspend while the switch is happening and we fail to wake it up afterwards.

@jfedor2
Copy link
Owner

jfedor2 commented Nov 18, 2024

#83 might also possibly have the same root cause.

@1-lost-cause
Copy link
Author

Not 100% sure what the difference is, but I tried out the two rasperry pi configuration, and that seems to be working to keep the connection while it switches

@jfedor2
Copy link
Owner

jfedor2 commented Nov 19, 2024

This would actually be consistent with my hypothesis. On the single Pico variant when we stop getting SOF packets from the host, we stop sending them to the device that's plugged in, which I think is causing it to go into suspend. On the dual Pico variant as long as the second Pico is powered, the device plugged into it doesn't see a difference, even if the first Pico is temporarily disconnected from its host. But I would have to look into it to confirm and come up with some solution.

@jfedor2
Copy link
Owner

jfedor2 commented Dec 8, 2024

You can try this test build and see if it makes a difference:

https://github.com/jfedor2/hid-remapper/actions/runs/12225991612

@jgermade
Copy link

It would be awesone to use hid remapper as kvm being able to use a hotkey for switch target device

@jfedor2
Copy link
Owner

jfedor2 commented Dec 10, 2024

It would be awesone to use hid remapper as kvm being able to use a hotkey for switch target device

I have a project derived from HID Remapper that does this, but I haven't been keeping it up to date:

https://github.com/jfedor2/screen-hopper

@jgermade
Copy link

It would be awesone to use hid remapper as kvm being able to use a hotkey for switch target device

I have a project derived from HID Remapper that does this, but I haven't been keeping it up to date:

https://github.com/jfedor2/screen-hopper

wow! this is great! sad not maintained...

in my case hotkey is more convenient because I work with 4 displays

I was thinking about any kind of daisy-chain with hid-remappers for reach this behavior

@braxlan
Copy link

braxlan commented Dec 14, 2024

It would be awesone to use hid remapper as kvm being able to use a hotkey for switch target device

I have a project derived from HID Remapper that does this, but I haven't been keeping it up to date:

https://github.com/jfedor2/screen-hopper

Any plans to update screen-hopper and merge the improvements of hid-remapper there?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants