Chinese INPA K+D CAN troubleshooting

1) Appearance
a. Scan or take high resolution photos of the main board
i. Front
ii. back
b. Some ft232 chips have some pins soldered together in pictures.
i. Are there any pins that look soldered together on your ft232?
c. Colors
i. Color of your main board?
ii. Color of connector? How many screws?
iii. Color of cable?
d. What are the names on the microchips on your board
i. FT232
 ii. ATMEGA162
iii. MCP2515 and MCP2551
iv. ATF16V8B
v. others
e. Extra Info if you feel like it:
i. Connector quality or how the leads attach to the main board.
ii. Does it use a thin wire? To pin 1?
iii. Do the chips look nice and square on board? Hows the soldering look?

2) FT232 eeprom Configuration

a. What are the IO settings for the CBUS pins.
b. Did your cable come with DSR and RI pins inverted?

Download FTprog from the official FTDI website in a zip file

http://www.ftdichip.com/Support/Utilities.htm#FT_PROG

When it comes up it should look like this.

Click the magnifying glass to scan and parse. This should locate your cable. In case you need it, this is
where youll find your serial number (to modify galletto.exe to work with your non-galletto cable). It is
important that you see what kind of chip you have and the product description. Send this info in.

Then expand the hardware specific tree. Open the IO controls.

Print screen, or write down the values for C0, C1, C2, C3, C4, and C5. Then expand Invert rs232
signals. If you followed a tutorial to fool the ignition and battery detect in INPA, these are the setting
that were changed. Report if anything came inverted on your cable or if you purposely did that.
3) Drivers and Operating System Open device manager by pressing start and typing device
manager
a. What driver is your computer currently is using with your device? Under Universal
Serial Bus controllers you should find USB serial converter. Go into its properties and
view the driver tab.
b. In the details tab, you can scroll the menu to hardware IDs and check if you find a
6001 in there or a 6000. If your chip is fake and the windows driver bricked it, it should
appear as PID_6000. Did the driver you used brick your device?
c. Did you install this driver yourself/manually?
d. Is this the driver that shipped with your cable? Or is it from FTDI? Or somewhere else?
e. What operating system are you using? 32bit or 64bit? Virtual machines?
f. Do you get an icon for the virtual com port? In the driver tab, what driver is it using?

g. What com port does your device install to by default? Example, com5.
 h. What latency works best for you? What works best for you to receive and transmit
bytes? Some claim that crappy cables cannot work at full speed and will work if your
transfer rate is set to 2048. What works for you?

4) INPA and BMW Standard Tools

a. With your cable plugged to usb (but not into the obd socket of the car) check your
battery dot and ignition dot. If in FTprog you saw your RI and DSR were not inverted and
you still have a solid dot for battery, then check INPAs OBD.ini to see if "uBat off" is
enabled.
b. With your cable plugged into both the usb and car, does the battery sense and ignition
sense function properly? Or is it permanently on. Or neither of them are on when the
car ignition is truly on?
5) Vendor Info was your cable marketed as VAGcom-KKL or INPA K+D CAN?
a. Was it advertised as 100kbits AND 500kbits?
b. Have you ever tried setting it to DCAN mode(500kbits)?
c. Use D-can Utility and attempt to set it to D-CAN mode or K-line mode. Results? This
needs to be done under 30-60 seconds after it has been plugged in. lots of tutorials for
this
6) MISC
a. What car have you tried this cable on?
b. Have you ever bench flashed a DME with this cable?
c. Have you ever had anything weird happen with this cable?
d. How long do your flashes take?
7) Galletto.exe to work with your cable, the galletto program needs to match the serial number
on your cable. You can change either or. Get it up and running and Attempt to identify your ECU.
 Do you get real info or only dots? Can you read your partial (32kb or 65kb) dump? Can you set
the DME into bootmode and successfully?
8) JMGarage Flasher Can you set the DME into bootmode and write/flash the full 512kb file to
the DME?
9) BMW logger has the ability to read codes and reset adaptations. It also auto-detects your cable
and com port. Download it from the official website or the MS43 Dev Crew thread and try it out.
Many claim the program is buggy, but it wouldn't hurt to have as much info on these cables as
possible. Also if you just need to code batteries then you really dont need BMW Standard tools,
as this will let you do it.
10) MSSFLASHER - The MSS54 guys use MSSflasher to mess with their DME's. The program has a
debug mode which verbally shows you when it searches for the com port, when it echoes to the
FTDI chip and what the chip echoes back. I had a bad cable that wouldn't echo properly on a
certain driver. MSSflasher allowed me to gain some more insight on what was going on in my
cable behind the scenes. Try it. Share results. I'm not sure it will properly identify a MS43 unit.
But it will confirm whether you have a working FTDI chip or not.