Jimmy peBay cable, interfaced disturbed error, used to work 4-5 months ago prior to the computer being connected to the Internet.sounds like you have you a cheap cable with a counterfeit FTDI USB to Serial UART chip.
If thats impossible, then we just have to keep digging. We were connecting mine just to make sure that we had a working version because mine had never "not" worked and when we got to my garage, hooked it all up, mine would not connect either so thats when we started wondering about possible license expiration. The head scratcher was that mine which was previously working fine, just stopped working. I could certainly purchase another to try, but my friends just bought theirs two days ago and are having the exact same issues on the other cars and a bench test rig. When you say interface, you mean the actual UBS to OBD adapter cable right? I / we were wondering if that was a possibility. If your interface no longer works and you have checked settings on OBD.ini to ensure that they are identical to those in DCAN.exe/Device Manager, are showing black ignition and battery dots in INPA and have tried with a number of other working installations, chances are that your interface has packed it in.OK thanks for at least clearing that up. No, INPA/EDIABAS is internal software used by BMW in-house and was never intended for external use therefore it has no inbuilt software licensing. Thanks for any continued advice in this thread. The only other variable I can imagine may play into it, is in the interim of the months between my last use on my race car, my wife used the race car computer to download a windows program for her work, then deleted the program from my machine, but I fear some stealth Windoze update may have occurred behind the scenes that is now jamming my comm signal path to INPA.Īny advice is appreciated as it sounds like my issue is almost identical to espus. To further complicate matters I am almost Windows illiterate, I am a Mac guy and know just enough Windows to turn on the machine and talk to the car's Vipec ECU when needed and also the MK60 via INPA with what I need to do to maintain the race car.
The in car ABS warning / fault light lights then goes out as normal and the ABS is functioning perfectly.įor some reason the computer has stopped communicating with the MK60 unit. I do have the (2) black dots for battery and ignition, and the OBD end of cable lights up when I turn on the master power to the ABS unit.
I went to connect today and I keep getting the same 0003 warning as espus above. I have not connected the computer to the car for about the same time 4-5 months. I have been using INPA via a blue OBD2 to USB adapter cable purchased on Ebay since I did the install for ABS diagnostics and bleeding. I have a stand alone E46 MK60 ABS unit in my race car. Bumping this, as I came here looking for help with a very similar problem to espus.
0 kommentar(er)
