11-02-2023, 10:43 AM | #1 |
Junior Member
Join Date: Nov 2023
Posts: 3
|
Mac Mini with Television - no display detected
Hi,
I have a Mac mini (Intel) running Monterey 12.7.1. Just bought a Bose VB1. The Camera and the Microphone are identified and connected, but DisplayLink is claiming there is no display detected. Display is a 4K 50" television, connected via HDMI output on the Mac Mini. The Mac Mini is connected to the VB1 using the USB-C cable that came with the VB1. That link is clearly okay as I can see the video feed when remotely connecting to the Mac Mini. Followed instructions in the Knowledge Base, the VB1 is showing up in the System Report as expected and has a PID of 0xa213 (not one the KB states is problematic). Any thoughts? What am I doing wrong? |
11-10-2023, 01:23 PM | #2 |
Senior Member
Join Date: Sep 2015
Location: Cambridge, UK
Posts: 1,678
|
Hello Michael,
This PID 0xa213 isn't from the DisplayLink chip. The VID is 0x17e9 and the PID will start with 0x6. Are you sure the video output was doesn't need enabled by an app before being visible? The manual p29 mentions the output is disabled by default. It's possible Bose is controlling the video function by enabling/disabling the DisplayLink chip in the product. That'd explain why the DisplayLink Manager app doesn't see the chip. Regards, Alban
__________________
Alban Rampon Senior product manager, universal docking stations and accessories "DisplayLink is proud to be a Synaptics brand." Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution |
11-13-2023, 11:01 AM | #3 |
Junior Member
Join Date: Nov 2023
Posts: 3
|
Thank you AlbanRampon,
Understood about the PID. To be clear the System Report shows: USB2.0 Hub ProductID 0x2817 VendorID 0x2109 (VIA Labs, Inc) Then as subentries: Bose Videobar VB1 Product ID: 0xa213 Vendor ID 0x05a7 (Bose Corporation) and Bose Videobar VB1 Product ID: 0xa213 Vendor ID 0x05a7 (Bose Corporation) I'm guessing these are the speaker and camera connection. There is no indication that there is a video output recognised. the vendor ID 0x17e9 does not appear in the System Report at all. Further to the issue of video control chip being disabled by default in the Bose, I understand that - however I am unable to access the Bose device via Bose's 'Sidebar Configuration' app - it is unable to locate the device. Specifically, it gives the error 'Cannot find camera'. If I connect the television directly to the Mac Mini, there is video output and the speakers and camera function, however I cannot control zoom or any of the other features of the camera. I made sure I'm using the HMDI cable and the USB-C cable that came with the Videobar. |
11-22-2023, 07:44 PM | #4 |
Senior Member
Join Date: Sep 2015
Location: Cambridge, UK
Posts: 1,678
|
Hello Michael,
I'm afraid I don't have the tools or knowledge for that part of the Bose product. It would be best to reach out to them to solve the app connection issue. Then, if after enabling the function, the chip still doesn't appear on the USB bus, then there's a definite problem with the product. Regards, Alban
__________________
Alban Rampon Senior product manager, universal docking stations and accessories "DisplayLink is proud to be a Synaptics brand." Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution |
11-23-2023, 08:24 AM | #5 |
Junior Member
Join Date: Nov 2023
Posts: 3
|
After a great deal of messing around, I found out that the issue was that I had plugged in the USB-C cable too early....
These are the steps I took to get it to appear, in case anyone else ever has this issue: - Turned off everything - television, Mac Mini, VB1. - Unplugged USB from the back of the Mac Mini to VB1 - Powered on Mac Mini, logged into the admin account - Powered on the VB1, waited for green light to show on the front of it - Plugged USB-C into back of Mac Mini It appeared! All working now. I could not find anywhere in the documentation that you had to wait for the green light to show on the VB1.... Anyway, we're up and running - thanks for your help, all. |
|
|