USB-monitor ASUS 169B+ not recognized on Intel NUC

[clkdiv]

Ooops! Double post. Sorry.

[AlbanRampon]

Hello,

It could come from a power brownout. The current rush to start the panel and backlight is making the voltage drops, which stops the panel, until it starts again.

Could you try to connect them through an externally powered USB hub to check if the behaviour changes?

Kind regards,
Alban

[clkdiv]

Hello Alban,

thanks a lot for your relply and your suggestion. I bought a USB 3.0 hub immediately and tried to run the ASUS monitors connected to the hub, without success, unfortunately.

I will try another hub, but I suppose power is not the problem.I can't imagine the Intel NUC can drive spinning hard drives but not the monitor, no?

While getting another hub, do you have another suggestion? Thanks a lot.

Martin.

[AlbanRampon]

Hi Martin,

Can you confirm you have used an external power supply?
If so, would you please use the third link in my signature to create the collection of the log files as follows:
1. Disconnect the ASUS USB monitors, leave the USB hub connected to the PC,
2. Start the Customer Support Tool and, in the options, please enable the Advanced Logging, leave it open,
3. Connect one ASUS USB monitor to the hub,
4. Wait one minute doing nothing. This is so I can see what takes place.
5. Click on the tool to collect the logs. It will take a while. Please do not do anything during that time, so the last point in the logs is clear to me.
6. Disable advanced logging not to fill your hard drive.
7. Close the tool.
8. Upload the ZIP the tool created here. Only employees can download them.

Kind regards,
Alban

[clkdiv]

Hello Alban, thanks again for another reply.

Yes, I used the USB-hub with its external power supply, 3.5A.

For now I tried the tool you suggested to create the logs. But unfortunately I ran the tool twice:

First run I used it the way it is described on the download page for the tool:

I uninstalled the Displaylink software from "Programs and features" in windows, put the tool to advanced logging, rebooted, installed the displaylink driver and then gathered the information.

Second run I did it as you wanted.

So you get two zips here. Hope it helps?

Best regards, Martin

[AlbanRampon]

Hello Martin,

There is something very wrong here I'm afraid, but I'm confident we'll get to the bottom of it.
Could you check if the logs were properly collected by looking in the following folder if you have a DisplayLinkManager*.log and/or Firmware*.log?
Folder = C:\ProgramData\DisplayLink\Debug (hidden by Windows by default)

In the logs, there is zero trace of any DisplayLink chip ever connected to the computer.
When you did the removal of the driver, it removed everything so the history so that's somewhat expect not to have old data.
With the second logs, I have nothing either, even in Device Manager or the Microsoft Installer logs. That second part (setuapi) lists what the OS has seen and done (very useful).

With what I have, I believe the displays don't enumerate on USB. So our driver is not even invoked by Windows.

Would you have a non-NUC machine on hand?
If so, would you please install 8.0M3 on that machine, disconnect it from the Internet, enabled advanced logging, and then connect one display on it, wait 2 minutes, and collect logs, then disable advanced logging? Did you get the display running? It may take up to 1-2 minute to reflash the firmware on these, provided the device is recognised (Windows USB connection sound and Device Manager will tell you if the device is recognised or not).
Then, on the NUC, remove the DisplayLink driver and connect the device. Do you have enumeration (sound and visible in Device Manager)? Because you're on Creators' Update, install from Windows Update is quick and painless.

Kind regards,
Alban

[clkdiv]

Hello!

Still no solution here. This is really sad, I bought two ASUS 169B+ monitors three months ago and I actually don't want to return them, if possible.

However I bought a USB 3.0 to HDMI converter today (j5create, 60$), and this one is running fine on a USB 3.0 port. I assume there is a DisplayLink driver running it too?

The problem is: I have to run three monitors at once from the NUC (two public displays and a control monitor). If this turns out to be impossible, I have to return the NUC itself. But since the USB 3.0-to-HDMI converter worked from scratch today, I think I will have to buy another USB 3.0-to-HDMI converter and two "real" monitors while returning the ASUS monitors. Don't like that at all, actually, because I really liked them.

So I am still hoping there is someone having an idea how to make the ASUS 169B+ monitors run on my NUC. Help is really appreciated!

Thanks a lot.

Martin....

[clkdiv]

Originally Posted by AlbanRampon

Hello Martin,

There is something very wrong here I'm afraid, but I'm confident we'll get to the bottom of it.

Alban

Hello Alban, did not see your reply when posting my desperate post just some seconds ago.

You are right, the monitors don't seem to be recognized at all. The device manager in Windows normally recognizes any USB device, before the drivers are installed. But connecting the ASUS monitors to my NUC does not do anything, there is literally no response at all. This is so strange, since both monitors run very fine and reliable on my much older ZOTAC ZBox.

Tomorrow I will do what you suggested: connect them to the old PC and send the logs. Thanks a lot so far...

Martin.