Like i also stated, i am not familiar with the BMW Scanner proprietary interface or software. You're going to have to be a lot more specific than that. Chances are the app is looking for those instead of generic serial drivers. If you're trying to get BMW Scanner to work, try going through the corrupted USB drivers steps (google or the previous link I posted), then install the PA Soft / BMW Scanner specific drivers. If it looks like the proprietary PA Soft VID/PID, checkout the link in this post about tweaking the generic USB/RS232 drivers. Get the drivers sorted out, and maybe you'll see all those 'common problems', but the OP isn't even there yet.Īnyhow, for the OP: If you want to set up INPA, check the VID/PID of your cable. The OP described a problem not with the physical layer (OSI Layer 1), but higher up the stack (OSI Layer 2+ depending on how you'd categorize the drivers). Chances are you'll even find the same chips in ELM327 based USB devices. Maybe three different manufacturers (FTDI, Prolific, Silicon Labs) make the vast majority of the RS-232 to USB chips out there. if you plug it into your USB port, whatcha think happens? It's still gotta go from USB to RS-232. For stuff like PA Soft or BMW Scanner, same deal. The worst I've run into on my Mac was that vendor's driver was buggy - easily resolved by using the open source driver.įor people using INPA/DIS, I stand by my statement that generic USB to RS-232 cables work just fine. If your USB to RS-232 cable can't do this, it's defective and should be exchanged. 9600 bps, 8 data bits, even parity bit, 1 stop bit. BMW's DS2 protocol (as it's seen in the E39) is pretty simple. Pre-96/OBD2 cars will require dealing with separate transmit/recv lines, but that's something your ADS to RS-232 adapter would handle. With v1.4.0 they went with proprietary USB VID/PIDs, but it's still an FTDI RS-232 chip underneath.

However, the PA Soft / BMW Scanner cable uses a bog standard FTDI RS-232 chip. With an E90 you get to do the D-CAN to RS-232 step (07+). The BMW-specifc protocol that you'd find on an E39 (DS2) doesn't rely on any esoteric functions. If you're talking about ISO 9141-2 / KWP2000 style OBD2 init, that requires 5 baud handshake and that's why you use an OBD2 dongle (often ELM327 based). Unfortunately the functions the bulk of them do not emulate are required for diagnostic work.You're going to have to be a lot more specific than that. These often result in limited or no communication with some modules whilst performing perfectly with others - the reason is that they emulate most serial port functions (i.e. Read on - the vast majority of USB to RS232 adapters are not fine for diagnostic work.

Kwp2000 usb to serial driver