German850R Posted November 16, 2015 Report Share Posted November 16, 2015 Hi, I guess it's the same problem everytime when someone updates to a new OS. Bought a Windows 10 Laptop (well rather tablet such like MS Surface) and tried to use my VAG COM cable which works fine on my other Laptop with Win 7. Well, FTDI drivers installed as per instruction (version 2.12.6.0) and in the device manager it appears as COM 3, all looks fine. Tunerpro is configured as supposed and Brickdiag as well. Communication does not work with Brickdiag, nor Tunerpro. I installed an older driver without success. Any hints? Thanks a lot. Christoph Link to comment Share on other sites More sharing options...
Joe Volvo Posted November 16, 2015 Report Share Posted November 16, 2015 Most likely this has something to do with compatibility. I would suggest that you try to run this software in compatibility mode to see if it sorts you out. Most of the time though when moving from one OS to another it is wise to reach out to that vendor to specifically see if there is any W10 support for their product yet. This link is for W7 but will be similar for you on W10. http://www.sevenforums.com/tutorials/316-compatibility-mode.html Good Luck! Link to comment Share on other sites More sharing options...
German850R Posted November 16, 2015 Author Report Share Posted November 16, 2015 Thanks, didn't work. Especially in Brick Diag I get some error messages: - when I want to connect, it says Protocol Error - When I intentionally connect to the wrong ECU (Motronic 4.3) the car makes some noises. So some level of communication works. I checked all my port settings and compared them to Windows 7 on my other laptop and all is the same. Strange ;) Link to comment Share on other sites More sharing options...
NB-V70R Posted November 16, 2015 Report Share Posted November 16, 2015 I am running on Windows 10 with no issues. I am using the 2.12.04 driver don't know if that would make a big difference. Link to comment Share on other sites More sharing options...
German850R Posted November 16, 2015 Author Report Share Posted November 16, 2015 Ok thanks. That already helps narrowing it down. Link to comment Share on other sites More sharing options...
German850R Posted November 16, 2015 Author Report Share Posted November 16, 2015 OK, the tablet PC is based on an Atom X5 chip. For the Ostrich the same problem occurs which is logic as that also uses the FTDI interface. I am trying to find other drivers now for the Atom chipset, maybe that helps. Link to comment Share on other sites More sharing options...
German850R Posted November 16, 2015 Author Report Share Posted November 16, 2015 Maybe that won't work because the board the tablet is based on seems similar to a raspberry pi 2 (not the same though) which itself communicates to the PC via FTDI protocol. That might not help in getting it run for my purpose (tune and log in the car without having to carry around a laptop) Link to comment Share on other sites More sharing options...
SlapShot Posted November 17, 2015 Report Share Posted November 17, 2015 Pretty sure you want it to be COM1 These are my settings for Windows 10 Link to comment Share on other sites More sharing options...
NB-V70R Posted November 17, 2015 Report Share Posted November 17, 2015 5 minutes ago, SlapShot said: Pretty sure you want it to be COM1 These are my settings for Windows 10 Don't know if it makes a difference, but fwiw I'm also on COM1 so maybe there is something to that. Link to comment Share on other sites More sharing options...
German850R Posted November 17, 2015 Author Report Share Posted November 17, 2015 Managed to get Ostrich working on the one USB 3.0 port that the device has. Don't know why it is working now. I think the VAG-COM cable should be OK as well as it uses the same protocol and driver. Will report out later. Thanks for all the help and proposals so far! Link to comment Share on other sites More sharing options...
Tommy. Posted November 17, 2015 Report Share Posted November 17, 2015 COM1 or COM67 it shouldn't matter fwiw. As long as you have assigned the proper COM port to the Command line you should be all set. This is for Win7 though, I don't really see how it would make a difference on Win10, only difference I could see is the drivers available on the certain OS. Glad you got it worked out though, I have been contemplating on switching to Win10 but I only use my computer for web surfing, school stuff, and tuning so I don't really have any advantage to do so until one of the main things I use the computer for becomes compatible on a very optimal level. Link to comment Share on other sites More sharing options...
German850R Posted November 17, 2015 Author Report Share Posted November 17, 2015 So, cable still doesn't work. It worked fine on Sunday with my work laptop. Will try again tomorrow. Maybe the cable is shot, but I consider that unlikely. Ostrich still works just fine. It's time the k-line goes through that as well ;). Link to comment Share on other sites More sharing options...
volvoguy23 Posted November 17, 2015 Report Share Posted November 17, 2015 While on this subject, does anyone know of some good tablets that will work for data logging and flashing? Would love to be able to use just a tablet, not very familiar with any of them out there nowadays. Link to comment Share on other sites More sharing options...
German850R Posted November 17, 2015 Author Report Share Posted November 17, 2015 46 minutes ago, volvoguy23 said: While on this subject, does anyone know of some good tablets that will work for data logging and flashing? Would love to be able to use just a tablet, not very familiar with any of them out there nowadays. Probably best to open a separate thread about that. Let's keep this one about troubleshooting connection problems in case somebody searches this info in the future. Link to comment Share on other sites More sharing options...
PsychoBeano Posted November 18, 2015 Report Share Posted November 18, 2015 No issues here, Im using Asus T100TA w/FTDI cable mentioned on wiki. My Com port did change when I upgraded from 8.1 to 10 but other than updating com port in TP and Realterm it worked fine. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.