[4cfd bmr]

I've searched the boards for hours lately and tried also installing different versions of INPA. I'm trying to merely code my one injector and it's taken about 6 hours of fruitless research to get INPA to code my injectors.

I've tried using vassillalov Injector Coding: N54 INJECTOR CODING DIY from this thread (http://www.e90post.com/forums/showth...njector+coding).

I am getting the black dots on Ignition and Battery when INPA is fired up. I then select e90 and then select Engine, MSD80 (N54), then System Diagnosis, then EOL Injector Rate Comparison and that's when I get the "ERROR #100 SYS-0010 INITIALIZATION ERROR API job error or no such result! Continue Script Processing? Yes? No?.

I'm a coding newby and Clem's lent me his INPA coding laptop to use which has coded previously so i'm trying to figure out what is up right now.

Other relevant info:

I have Procede 2.5 in map 0 (stock mode) right now. I'm not sure if there is anything else needed.

HELP?!?!?!?

[4cfd bmr]

Anyone???

[4cfd bmr]

Revival - I STILL NEED HELP WITH THIS...ANYONE???? I followed Vasillov's thread to a "T" and still get the "SYS-0010 INITIALIZATION ERROR" and I have both black dots at the initial screen.

[Douche]

Windows version? Tried running the software in compatibility mode with win XP?

[OregonDude]

Open up your INPA/EDIABAS cable and see if pins 7 & 8 are bridged (shorted) together. If so, remove the bridge and retry connecting.

[wildcatcrazy]

For starters, select Functional Jobs and see if you can read errors or UIF. That's a quick way to make sure the laptop is talking to your car.

If that's good, then there's something wrong with IPO/PRG files within your install.

[cryptomit]

Originally Posted by bora1point8t

Revival - I STILL NEED HELP WITH THIS...ANYONE???? I followed Vasillov's thread to a "T" and still get the "SYS-0010 INITIALIZATION ERROR" and I have both black dots at the initial screen.

What's your car production date?

[3000GT MR]

I had the same issue. After a bunch of beers and some messing around i got it to work. Then i had to remove and re-install all my coding programs because of an issue with NCS. Now my INPA doent work for the life of me and i get the same SYS-0010 fault. It will show values sometimes but its almost like the read/refresh rate isnt set correctly and i had tried everything i could to sync speeds. No luck at all. So i know my cable is good and my computer is good, and its something within the SW

[loknar]

bump!
I also get SYS-0010 error and the other script errors.

I can't make it work. Even paid to make sure I get the correct INPA files.
I changed to COM port #1.
I tried ignition off, accessory, on and start engine, keyfob in also
I am used to KKL interface on Fiat cars, when plugged in the car the OBD LED is turned on - when connecting it flashes.
With my K+DCAN the light is on for 20 seconds then turns off. Never saw it flash.

Made sure my driver was FTDI, and my cable had FTDI chip on it. It has FT232RL on the green board. and I tried a 2008 driver and 2016 driver from ftdi.

Both INPA circles are black even if OBD interface is not connected to the car. both become white if usb is unplugged though.

If I press F1 after starting INPA, the EDIABAS section only shows ??????? instead of paths. This is resolved by starting EDIABAS tool before INPA, but in this case, the interface does not produce black circles.

Please help. -Desperate

[wildcatcrazy]

Originally Posted by loknar

bump!
I also get SYS-0010 error and the other script errors.

I can't make it work. Even paid to make sure I get the correct INPA files.
I changed to COM port #1.
I tried ignition off, accessory, on and start engine, keyfob in also
I am used to KKL interface on Fiat cars, when plugged in the car the OBD LED is turned on - when connecting it flashes.
With my K+DCAN the light is on for 20 seconds then turns off. Never saw it flash.

Made sure my driver was FTDI, and my cable had FTDI chip on it. It has FT232RL on the green board. and I tried a 2008 driver and 2016 driver from ftdi.

Both INPA circles are black even if OBD interface is not connected to the car. both become white if usb is unplugged though.

If I press F1 after starting INPA, the EDIABAS section only shows ??????? instead of paths. This is resolved by starting EDIABAS tool before INPA, but in this case, the interface does not produce black circles.

Please help. -Desperate

Where did you buy the cable? If it's from a reputable source, I can help.

[loknar]

Originally Posted by wildcatcrazy

Where did you buy the cable? If it's from a reputable source, I can help.

Forgot to mention I'm on windows 7 and my car is 2007/07. I did previously try with windows 10. I also tried installing with ediabas setup and another bmw setup tool maybe it messed up my system. Now trying on a different PC and various virtual machines.

Thanks for your generosity. I don't think I qualify for a reputable source. There seems to be one 'bmw coding' site and others all recommend the same source at 80$. My cable looks the same though.

I told you the chip I have reads FT232RL and my driver is automatically loaded by windows as FTDI version 2.12.14 . pins 7 and 8 are NOT shorted.

If that's wrong please tell me what's the reliable, reasonably priced source.

[loknar]

update:

There is a person on ebay selling my exact cable with a modification switch on it. The switch has <2006 mode and 2007+ mode. 2007 mode seems to short pins 7 and 8 !!! I was reading in the forum that 2006 model needed shorting pins 7 and 8. Not the opposite. Anyone knows the truth?

[nate16]

You can download my coding image and use Rheingold to program the injectors

[nhatnguyen14]

The JB4 was causing the connection problem (error 100) for me. I removed the JB4 and I was able to code my injectors. I had a older K+DCAN cable (bought in 2012) and it still works for me. I thought it was the cable but it turned to be the JB4. My car is a 2011 E89, replacing the fuel injectors with index 12 because the older index 09 is failing. Hestitate to start, can't rev up past 3k, smells whole bunch of unburned fuel, and make sure to check your oil cap, it will also smells like fuel in there. That's when you know you have bad fuel injectors.

I used the INPA from beemergeeks, followed their instruction and it works perfectly without JB4 installed. Was installed on Windows 7 32 bit, make sure you run the command prompt with admin rights, that kinda got me stuck for a little bit.

[oilcrankinject]

I have this error as well. INPA worked just fine before I had to rebuild my motor.

I thought my DME was bad so I replaced it, same error. Fuse 37 is good. I am able to view the LIW to see a vin, the vin that this DME came from. I was not able to do this before with my old MSD but did I have to change the latency to 1 to get INPA to sort of work.

Car wont start.

ETA: My fault, motor works. I somehow forgot to plug in the small gray wiring harness into my DME. No faults now.