VCDS with Windows 10 under Bootcamp on new MacBook Pro (late 2016)

   #1  

JetTurbo

Verified VCDS User
Verified
Joined
Sep 4, 2016
Messages
2
Reaction score
0
Location
USA
VCDS Serial number
C?ID=18606
I have used VCDS for the last 7 years on a 2009 Intel i-7 MacBook Pro
under Bootcamp running Windows 7 Pro 32 bit. Always worked fine.
BTW I also replaced my 2006 vintage VCDS HEX+CAN with an up to date version in August 2016.
The new interface also works fine with the old MBP under bootcamp.

Finally replaced the old MBP with a new 15" MacBook Pro Retina / Touch Bar / Radeon 460 (late 2016).
Installed Bootcamp and Windows 10 on the new MBP
(the only Windows OS supported by the late 2016 MBP hardware under Bootcamp).

Of course, the new MBP only provides USB-C ports, so I connect the
HEX+CAN via a $9.00 Apple USB-C to USB Adaptor (MJ1M2AM/A - Model A1632).

While at my desk under AC power, installed VCDS 16.8.
Plugged in the HEX+CAN cable with Apple USB adaptor and it is recognized under VCDS,
noting Car not connected.
It shows up under Windows Device Manager (with hidden devices revealed) and indicates
the HEX-CAN is found and correctly installed.

I disconnect the HEX-CAN cable and Apple USB adaptor,
disconnect power to run on MBP internal battery,
move to the car, connect the interface to the OBD-II port,
ignition on, re-connect HEX+CAN & USB adaptor to the MBP
- the interface can no longer be found.

At first I thought this was going to force me to always have AC power connected
when running VCDS, which would be a bit of a hassle.

Then I discovered if I connect the HEX+CAN and Apple USB Adaptor to the MBP
while it is under AC Power (to properly recognize the interface) and then disconnect
AC power while maintaining the connection to the HEX+CAN cable & USB adaptor,
it continues to work on battery power. Still a bit of a hassle to keep the cable connected
while plugging it in to the car, but it beats the alternative.
I also suspect there may be some Windows power management function
that will eliminate this, will report back if I find it.

In the mean time, under battery power after the above procedure,
ran a full scan of my 2012 Golf R and all worked as expected.
:)
 
   #2  

rlarsen

Verified VCDS User
Verified
Joined
May 5, 2015
Messages
300
Reaction score
160
Location
Copenhagen, Denmark
VCDS Serial number
C?ID=78998
I'm also running VCDS on the new MacBook Pro 15" - but I'm running it under VMware Fusion and Windows 10 64-bit. - until now everything is working with and without power cable.

So maybe Bootcamp need a driver update ?? - you have installed the necessary Bootcamp drivers in windows ??
 
   #3  

JetTurbo

Verified VCDS User
Verified
Joined
Sep 4, 2016
Messages
2
Reaction score
0
Location
USA
VCDS Serial number
C?ID=18606
Yes, the Apple BootCamp USB controller drivers are installed,
I did check that in Windows Device Manager.
Pretty much can not avoid that the way bootcamp installation now works,
Apple hardware Windows driver installation is part of the automated process.
Basically you tell the bootcamp utility the size of the Windows partition you want,
where to find the Windows installation.iso file,
and the Windows serial number
and it is completely automated from there.
 
Top