U2723QE, MacBook Pro M1 Max, daisy chain not working

Open the online U2723QE/QX User's Guide to page 12.

#3 HDMI
#4 DP 1.4
#5 USB Type-C (Video + data, up to 90W power delivery)
#6 DP out
#7 Audio line-out
#8 USB Type-C upstream (To enable USB 3.2 downstream if using #3 HDMI or #4 DP 1.4 for video)
#9/#10/#11/#12/#14 USB 3.2 downstream
#13 RJ45 Ethernet
#15 USB Type-C downstream (Data only, up to 15W of power charging)

Connecting the Macbook to U2723QE with USB-C and then connecting U2723QE to U2719DC through USB-C (downstream port) to USB-C

Won't work. The #15 USB Type-C downstream port is data only, not video.

Connecting the Macbook to U2723QE with USB-C and then connecting U2723QE to U2719DC through the display port.

That could work IF the 90W power delivery from the U2723QE #5 USB Type-C is enough for the MacBook Pro M1 Max to drive itself and two monitors. If not, connect the Apple power adapter to the MacBook Pro M1 Max and retest.

MacBook Pro M1 Max TB4 --> U2723QE USB Type-C to C cable --> U2723QE #5 USB Type-C/DP alt mode (DP MST On)
U2723QE #6 DP out --> U2723QE DP to DP cable --> U2719DC DP in port (DP MST Off)

Hello @DELL-Chris M 

Thanks for your response.

I didn't use USB-C Port #15 as I am aware it's only for data transmission from reading the user manual.

I did exactly what you have recommended:

1. I connected the Apple Power Adapter to the Macbook Pro M1 Max
2. I have used the provided USB-C Cable and connected the Apple TB4 to U2723QE USB-C #5
3. I have set the U2723QE MST to ON
4. I have connected the DP #6 of the U2723QE to the DP of the U2719DC
5. I have set the U2719DC MST to OFF
6. I have tried to turn on & off the monitors
7. I have tried to disconnect the USB-C cable between the Macbook Pro M1 Max and U2723QE

Unfortunately, it didn't work

Maybe MacOS doesn't seems to support MST. So the second screen U2719DC is mirroring the first one U2723QE, but they have different resolution. Maybe you have to connect the two screens separately to your Macbook.

Thanks for confirming. We knew this was an issue with older macOS but were hoping with the new MacBook Pro M1 Max and macOS 12 Monterey it might work.