Printable View
Derek,
I know it sounds redundant, but check in Device Manager to see if the BMW Scanner driver is installed (it'll be painfully obvious if it isn't). If it isn't, then update the software from the BMWScanner folder from the root of C:
Also, try another USB port. These two items usually resolve the issue for me.
Sent from my DROID RAZR HD using Tapatalk
I tried both USB ports, but no luck. The BMW Scanner was installed with drivers provided, and when that didn't work I tried it with the FTDI drivers online. Both didn't not work.Quote:
Originally Posted by az3579
PA Soft does see the scanner and drivers are installed with both green lights but no dice communicating to the car. It might be an issue related to the virtual machine and how USB interacts with OSX. I'm stumped. It works perfectly fine on the xp machine, perhaps I can install a virtual machine within a virtual machine and then run it. INCEPTION.
I ran the same setup as you have; I ran this on my OS X Macbook Pro Retina through a VM just fine and everything functioned.
I did find though that sometimes when I rebuild the VM and use Windows 7 it had a hit-or-miss functionality. If it didn't work, a reimage is what it took to fix it. With the XP image, it worked out of the box the first time, and is the only time I used an XP image when rebuilding.
Perhaps what you can try to do is run the FTDIUNIN.exe file from the C:\BMWScan140\Drivers directory to remove the drivers installed for it and then reinstall using the files in that same folder.
I had this issue before and it drove me crazy. PA Soft and the blue INPA cable use different OBD drivers, and they both want their own different specific version. I solved this by setting up a 2nd VM and haven't had issues since.
Thanks guys. I hope I didn't mess up my inpa drivers!
sent from Moto X Dev edition
This morning I went to drive the car to work but the battery was dead. I said F it, its been 5 years. I went to the dealership and got myself a new battery.
$197 after tax.
61-21-2-353-808
Not the cheapest but its okay, I rather have it in there right now and eliminate the battery as a cause. Everything else was checking out fine and I still had a bad battery so I think it was time to remove that as a variable.
I tried installing Windows XP SP3 on parallels and installing PA Soft and I still get an error for it saying hardware is not ready. I even got a BSOD when I tried plugging it in a few times. O_O. I am going to try VMware now and reinstall windows xp and see if it works. It bugs me that it doesn't work!
https://dl.dropboxusercontent.com/s/...iX2YcsBjQ3Qbyg
Low and behold what the driver is. -_-
I've given up on the damn BMW Scanner to work on anything outside my old 2004 XP laptop. It refuses to work on VMware with an SP3 clean install, or Parallels XP SP3 clean install. I suspect it might be some issue with the mac side?
I got an SES on the way home, and low and behold, its the lean fuel trim on bank 1 and 2 again. DAMMIT! I need to smoke test the damn thing to see where this leak is coming. I fear it comes from the DISA valve..
Sorry dude. Does that Bic lighter to the DISA hole work? If so, give it a shot.Quote:
Originally Posted by derbo
Always something :(
It is isn't it!
Figuring out what the Lean Codes for:
I put back on the stock intake in order to eliminate the AFE intake as a variable for the lean codes since it started after I put in the AFE Intake. I drove about 100 miles and the SES light did not return. I originally thought it was the intake boots as they were torn when I installed the AFE intake. Since the SES hasn't return yet, I'm wondering if it is the AFE intake itself.
I don't understand how the intake would cause the lean codes so I'll continue to monitor car whenever I drive it. The rubber ring that you remove from the stock intake MAF to put on the AFE was a bit loose. However, this is pre-MAF so it doesn't make sense to me that it would create a lean condition.
Is there a way to reset the MAF?