Connecting KVM-GO HDMI to low profile notebook

Hello,

I’d like to use KVM-GO HDMI to connect from my source Win11 notebook to target Win11 low profile notebook.
Questions:
Q1) If KVM-GO HDMI is too high, it will lift the edge of the low profile target notebook when inserted, which will cause mechanical and electrical stress.
For the low profile target notebook I need to connect to, the space between the bottom side of HDMI connector and surface of the desk where it sits is only 6.8mm.
How many millimeters are between bottom side of HDMI connector and bottom of KVM-GO HDMI - on the attached “KVM-GO HDMI dimension C.png” it is denoted as dimension C in millimeters?

Q2) What to do if dimension C > 6.8mm? Do you provide suitable short HDMI male - HDMI female cable to avoid plugging KVM-GO HDMI directly to the notebook? If not, what workaround do you suggest?

Q3) KVM-Mini due to indirect cable connection seams would solve it, however KVM-GO HDMI supports full HD 60Hz, which is much easier on eyes compared to max. full HD 30Hz offered by KVM-Mini. Despite that is there any reason why to prefer KVM-Mini over KVM-GO HDMI?

KVM-GO HDMI dimension C

Hi @Johnny_888

Thank you for your detailed questions. Please refer to the KVM-GO dimension drawings in this task’s attachment (KVM-GO-Dimension.pdf).

The specific dimensions for the HDMI version are labeled in the drawing (unit: mm).


Here is a short HDMI extender cable (shopify url) which may also work as a solution. Please check if this works for you.

Although the Mini-KVM only supports 1080p@30Hz, because it connects indirectly via cables, it can indeed avoid the mechanical stress issues at the HDMI port. If your use case is fixed desktop office work and you don’t have a strict requirement for 4K@60Hz, the KVM-Mini is a safer and more flexible choice.

If you have any other questions, feel free to continue the discussion.

Moreover, so sorry for the late reply. I just realized your post was in the line of approval before it got posted here… I will double check our forum backend setup.