|
||||||||
| Xoutpost server transfer and maintenance is occurring.... |
| Xoutpost is currently undergoing a planned server migration.... stay tuned for new developments.... sincerely, the management |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
#11
|
|||
|
|||
|
__________________
Dave S. Northeast 2003 4.6is 2005 E53 4.4 2003 E39 Msport(a REAL ONE!) 1959 Fiat 600 |
| Sponsored Links | |
|
|
|
|
#12
|
|||
|
|||
|
Quote:
OK, I've followed this guide from FTDI and the thread below: https://www.ftdichip.com/Support/Doc...ndows%2010.pdf https://www.youtube.com/watch?v=bZLhlfDmmog https://xoutpost.com/bmw-sav-forums/...dows-10-a.html I've been beating my head against this for an hour and I can't get the drivers to be recognized by Windows. I've downloaded them but Device Manager won't recognize them as applicable to this device. Since this was so simple for you, do you have any ideas for me to try?
__________________
2003 3.0 5MT Topasblau Purchased in 2016 and sold in 2024 2012 35d Platingrau |
|
#13
|
|||
|
|||
|
Quote:
I don't know about those other links you cite, but the one I cited: https://forum.e46fanatics.com/showpo...72&postcount=1 Did it for me, when read carefully and followed exactly. Since it was posted in 2012 and worked for me in 2019, I expect it is still valid. Also, those instructions refer to Win7, and I did it on Win10-64-bit, further suggesting they are rock solid.
__________________
2001 X5 3.0i, 203k miles, AT, owned since 2014 |
|
#14
|
||||
|
||||
__________________
Digital Competition Systems The older I get... The faster I was... No Fear
|
|
#15
|
|||
|
|||
|
Quote:
Hey! That did it! Thank you!
__________________
2003 3.0 5MT Topasblau Purchased in 2016 and sold in 2024 2012 35d Platingrau |
|
#16
|
|||
|
|||
|
__________________
2001 X5 3.0i, 203k miles, AT, owned since 2014 |
|
#17
|
|||
|
|||
|
Alright you all, BMW scanner worked fine on my laptop the last time I tried it. But last night I fired it up again and it wouldn't connect. Every module it said "not found" and when I tried to ID the vehicle it just failed every time.
I tried the key in the "on" and the "run" positions, but neither one changed anything. I rebooted my PC and it didn't help. I tried connecting the cable before and after I booted up the BMW scanner program as well. Anybody want to guess what I am doing wrong?
__________________
2003 3.0 5MT Topasblau Purchased in 2016 and sold in 2024 2012 35d Platingrau Last edited by Bdc101; 05-05-2020 at 10:20 AM. |
|
#18
|
||||
|
||||
|
Windows Updates have probably messed up the drivers - check the software can communicate with the adapter.
__________________
Wayne 2005 BMW X5 3.0d (b 02/05) 2001 BMW F650GS Dakar (b 06/01) |
|
#19
|
|||
|
|||
|
Quote:
Nothing you did wrong. Just that the world changed while you were minding your own business. I would follow the installation instructions as if you are starting all over again - that 2012 link I reference a few posts up. That may force Windows to re-recognize things. If not, what Windows do you have? What exactly works and what is the failure?
__________________
2001 X5 3.0i, 203k miles, AT, owned since 2014 |
|
#20
|
|||
|
|||
|
I just walked through the steps in the post you mentioned again, with no success.
When I connect the cable and open BMW scanner, if I try to ID the car it says "Connection failure: cannot connect to IKE" and then "cannot connect to EWS" and then stops there. If I double click on any module, it just takes a minute and says "not found." It's different from when I open BMW scanner when the cable plugged into the laptop but not the car, or disconnected entirely from the laptop: when I do that, it just says "hardware not ready" when I try to ID the car. This tells me that the laptop is talking to the adapter, but cannot talk to the car. Am I interpreting that correctly?
__________________
2003 3.0 5MT Topasblau Purchased in 2016 and sold in 2024 2012 35d Platingrau |
![]() |
| Bookmarks |
|
|
|
|