KM Model #USW-N334 (note, not a KVM, just KM).
I have been a longtime user of KVMs from way back in the VGA days, and things have gotten so incredibly complex when it comes to Video options.
Whether it be DisplayPort, HDMI, etc, even the best full KVMs eventually have either issues, or degrade the native performance of a display.
For example, I now have a QHD (3440x1440) OLED display which supports a massive 240 Hz refresh rate on both HDMI and DisplayPort.
Even if I found a KVM that supported this single monitor and 4 computers, I would lose the awesome Picture-by-Picture capabilities of this monitor.
More so, in general, I have found that your KM device provides pretty much everything I need.
In particular, with two systems connected to the monitor, using PBP, I can use the mouse roaming to seamlessly switch from one system to the other. It’s almost magic!
So now that I got what I basically need, I want more!
Using DDC/CI there are mechanisms in all of the O.S.s (Windows, macOS, and Linux) to send a signal to the monitor and have it switch inputs.
With this, and a monitor with 3 inputs, I can effectively have a super high-quality KVM device that should work pretty much forever (for 3 systems, not 4, but I can live with that).
So, as I mentioned, each of the OS’s have different tools to manage DDC/CI commands, and each tool provides for some sort of a command-line interface.
- On Windows there is “ControlMyMonitor”,
- on macOS there is “BetterDisplay”
- on Linux their is " [
ddcutil] and and [i2c-tools]
So, what I am hoping to either grab from soneone else, or develop, is a way to integrate the KM hotkeys (or something equivalent) that causes the monitor input, and KM input, to change in tandem.
While I am on the topic of heavy-weight use of this KM, has anyone figure out how to plug a device into the serial port?
I have a variety of USB-to-RS232 cables, but none of them have the correct gender to plug into a standard USB port on a modern system.
If I had some ancient system with an actual make RS232 port, that would be good, but no luck there.
Most modern systems utilize a straight-through ethernet cable (Cisco-type) for RS232 signaling.