Dell thunderbolt dock macbook pro pro#
If not (or honestly even if so, in certain cases), the CalDigit TS3+ or USB-C Pro Dock, the latter of which supports and will use TB3 if available on the attached system, would probably be better choices. I'm also not entirely sure why you're using Dell docks with MacBooks in the first place, unless you also have Dell systems. You wouldn't be able to use the WD19TB with an older Thunderbolt 1 or 2 system, and if the WD19TB itself were a TB1 or TB2 dock, then it wouldn't be able to provide power to charge your system, since that wasn't possible through the Mini-DisplayPort connector used by those older standards. You'll be able to plug the WD19TB directly into your MacBooks, no adapter needed. The WD19TB is a Thunderbolt 3 dock, and as such it uses a USB-C connector. That's why your MacBook Pros that support Thunderbolt 3 offer it through their USB-C ports. But unless it just happens to be possible to run 3840x1600 at 60 Hz through the half-bandwidth USB-C video link available through the WD15, you might really want to consider getting a Thunderbolt dock like the WD19TB, which when paired with those systems would be be able to tap into at least 4x more display bandwidth than the You're welcome, but.in addition to there being only one guy in here who's been helping, what are you planning to do with that TB2 to TB3 adapter? Thunderbolt 3 when it's available uses a USB-C port as its physical connector. That's a popular utility on Macs for people who want more control over their display setup. You could try using SwitchResX to see if you can force additional modes. In terms of why the two systems behave differently, I'm not sure since I don't spend much time on Macs. Carrying USB 3.0 requires two high speed lanes, which means your available video bandwidth is cut in half. With the WD15, the dock sets up the USB-C link to carry both video and USB 3.0 data simultaneously. But the reason the HDMI adapter works differently is that when you connect an HDMI adapter directly to the system, all 4 high speed lanes in the USB-C connector are allocated to video. 3840x1600 is between those two, so I'm not sure what's possible there. I can mouse the move within the screens but nothing more.Are you actually able to get 60 Hz when running that display through the WD15? The reason I ask is that the WD15's documentation indicates that it supports single displays only up to 1440p 60 Hz or 4K 30 Hz. Weird stuff is that it recognizes both displays with a black screen and nothing more. Unfortunately I need to use a bridged usb-c hub to connect to that. I also have a D3100 at home which is UBS3.0. Reply to this email directly, view it on GitHub, or mute the thread. You are receiving this because you are subscribed to this thread. It’s not thunderbolt, it’s usb, but at least it works and as of now I have zero complains on the dock.Įl 28-11-2018, a las 09:20, orappold escribió: Guys, do I understand correctly that the TB16 dock does not provide video passthrough for MBP's? That is the use case for having a dock to enable multiple displays? Does this affect other TB docks as well? It hard for me to understand the reasons behind. I surrendered on the TB16 because of all of its problems and went to the Dell WD15. The reason is the TB controller on TB16 isn’t certified by Apple, that’s why the tb3unblocker is needed, but as a third party solution, you can’t have the guarantee that it’ll work in all the devices available. Thunderbolt3Unblocker: Patched IOThunderboltFamily Xnu_override: Re-enabling kernel write protection Xnu_override: Disabling kernel write protection inCount: 2 data:0x143eSmartBattery: finished polling type 2 inCount: 2 data:0xe63Command 0x10 completed. inCount: 2 data:0xffffCommand 0xf completed. inCount: 2 data:0xaCommand 0x13 completed. inCount: 2 data:0xc2dCommand 0x17 completed. inCount: 2 data:0x2e77Command 0x8 completed. inCount: 2 data:0x160Command 0x9 completed. inCount: 2 data:0x0Command 0x12 completed. inCount: 2 data:0xf79Command 0x3c completed. inCount: 2 data:0xf83Command 0x3d completed. inCount: 2 data:0xf7cCommand 0x3e completed. inCount: 2 data:0x1e1Command 0x3f completed. inCount: 2 data:0x1Command 0x11 completed. inCount: 2 data:0xfd8cCommand 0xc completed. inCount: 2 data:0xfe50Command 0xb completed. inCount: 2 data:0xe443Command 0xa completed. inCount: 2 data:0x0Command 0x54 completed. inCount: 2 data:0xc0Command 0x53 completed. inCount: 2 data:0x1101Command 0x16 completed. inCount: 2 data:0x4Command 0x1 completed.