Forum Discussion
Wireless connect disables external Display Port
I'm having difficulty understanding your answer. Let me restate the question.
We have a Hub 55, connected to a 90" LCD display via the "Video Output" connector, as shown at https://technet.microsoft.com/en-us/itpro/surface-hub/connect-and-display-with-surface-hub#video-out
It is described as "The Surface Hub includes a Video Out port for mirroring visual content from the Surface Hub to another display."
This works if we connect the "visual content" to to the Hub by the Display Port, HDMI, or VGA input connectors, and the USB cable for Touchback/Inkback. The sutdents in the back of the classroom can see the instructors content on the 90" external display, but we have to run several cables acrosss the floor, creating a safety hazard.
To eliminate the cables and safety hazard, we obtained a Dell E5470, advertised in the Microsoft Store as https://www.microsoftstore.com/store/msusa/en_US/pdp/Dell-Latitude-14-E5470-Laptop-+-3-Year-ProSupport-Warranty/productID.5064602100 .As soon as the wireless connection to the Hub is established, the "Video Output" on the Hub 55 is disabled. The attached 90" display goes black with "NO SIGNAL". As soon as the wireless connection is stopped, the Video Output is enabled and we see the Hub again.
So actually, the hub almost always projects the connected source - but only when the connected source is attached by a cable running across the floor.
How do we get the Video Output to remain active when using wired (VGA, HDMI, or Display Port) and wireless (Miracast)?
MicrosoftHello Greg,
Sorry for the late reply, don't know if you still have the issue but the issue you are mentionning look like HDCP issue.
HDCP is designed to protect numerical content to prevent copy. If you send HDCP content to the hub it might block screen mirroring feature because it would be a breach of the security.
Do you know what kind of PC is projecting ? can you try with VGA which does not support HDCP.
We had some issue with MAC devices because they enforce HDCP by default.
HTH
Eric S.
I just assisted a client with a new Surface Hub installation and am experiencing the same problem. I thought it could be an HDCP issue as well. However the poster above who is just connecting to a standard display should be HDCP compliant from end to end. In both of our cases if it hasn't been made extraordinarily clear, HDMI and VGA guest connections work fine. However output is discontinued after successfully connecting to Surface's WiDi interface.
If this is a limitation of the system I can find no documentation supporting it or reporting the limitation.
- EricScherlingerHello,
Nice timing I was preparing my techsummit session yesterday and we faced the exact same issue.
Long story short it is an HDCP issue. We work around it with a samll box that we put between the HUB and the screen. It changed all the behavior.
Not sure I understand all but I can share the reference of the hardware if you wish.I would be interested in what you have between the HUB Display Port and the external display.
The tricky part is that I need to keep the digital audio intact from the laptop through the DP out on the HUB to connect to a Cisco SX80 codec. The codec drives the displays and feeds the audio amplifier. With the DP/HDMI operating, the digital audio is passed along and decoded in the codex. When the HUB Display Port out is disabled, that will require me to run to run 70' of audio cable back to the Cisco SX80, and doing the Digital-Analog-Digital dance as well.
Yes, this flaw is not documented anywhere - in fact the Surface HUB product is poorly documented. Had we been aware of this, we would have rejected the proposal and purchased a much less expensive "display only" screen without the crippled version of Win 10.
