[ramspeed]

I have a semi-emergency going on. My car is at a friends shop right now, and will not start. Upon taking the car to the dealer, they ran diagnostics and said that it is for sure the starter. I had my friends shop replace the starter, and the car still will not even turn over.

I'm concerned though because the day before all this started, I was coding my car for the first time. I am using the 2.1 distribution (with edibas 7.2 and INPA 5.0). I am using the E89v 50.2 datens on a 2008 e92 335i. I coded the idrive start screen to be disabled, the mirrors to fold in with keyfob (not comfort access). And I tried to code the foglights to stay on with the high-beams.
I was having issues connecting my DCan cable to the car, (NCS expert was saying there was an interface issue).
But That was all finished Sunday night. I started it up sunday, and drove around a little. Monday, I took the car to the car-wash, washed it, and then moved it from the wash bay to dry it. Once I was finished drying though, the car did not start. It didnt even try to turn over.
My question is, could this be related to the coding that I did? Did I somehow mess up the ECU?
After scanning for codes with cobb, I got a bit serial data interface error (which freaked me out).

Also, the car runs fine once bump-started. It just won't start on it's own.

I'm going to try resetting the modules that I coded, but I was having issues with edibas connecting as of this past friday. (maybe that's an indication of something being messed up)
Thanks in advance.

EDIT:

Turns out the issue was un-related to coding. Issue was caused by a faulty ground that was not immediately exposed.

[wildcatcrazy]

Does not sound like a coding issue. If it were, you would have known as soon as you coded it. Does your lights or anything work? Id be leaning towards a battery problem.

[Sensible_]

+1 for battery problem.

How long were you coding for?

There car isn't cranking?

[ramspeed]

Originally Posted by wildcatcrazy

Does not sound like a coding issue. If it were, you would have known as soon as you coded it. Does your lights or anything work? Id be leaning towards a battery problem.

That's kinda what I thought as well. I had the battery charged (1024 ccas out of 900) and the car still does nothing. The dash lights and cluster all turn on when the key is in, but once you hit the start button, you can hear the fuel pump prime, but nothing happens with the engine whatsoever

[cryptomit]

Did you code CAS?
Try to recode CAS to default settings.

[ramspeed]

Originally Posted by cryptomit

Did you code CAS?
Try to recode CAS to default settings.

I just updated the datens 53.3 so maybe that was causing a connection issue with edibas. But if I can connect to the car, is my next step to have the dealer re-flash?

[Sensible_]

You need to diagnose what's wrong first.

What modules did you code?

I'd connect up INPA or ISTA /d to see what faults you have and if all modules are accessible.

Do you have any warnings on the dash?

Edit:

If its module problem i think the following are the only ones which prevent vehicle starting:

CAS
DDE / DME
EKP

[ramspeed]

Originally Posted by Sensible_

You need to diagnose what's wrong first.

What modules did you code?

I'd connect up INPA or ISTA /d to see what faults you have and if all modules are accessible.

Do you have any warnings on the dash?

Edit:

If its module problem i think the following are the only ones which prevent vehicle starting:

CAS
DDE / DME
EKP

Yeah I coded the CAS module for the windows/mirrors. So that is a possibility. I'm going to try to reset that module today for sure. If I can't reset it for some reason, can the dealer?

There are no codes thrown on the dash, but like I said, when I scanned for codes with my COBB ap, it threw something related to "binary bitstream invalid" or something thereabouts.

[cryptomit]

you will be able to reset CAS using EXPERT profile.

[terminator2k2]

I'm no expert but I don't think this is a coding problem as the car was fine till it was washed and dried.

One thing I would check, is there some kind of switch which might of got dislodged or gone faulty. When you start your car you have to put your foot on the clutch or it will not turn over. Is this related? Same for automatic I think I think you have to engage the break pedal?

Might be talking crap but hey just my 2ps worth

[cryptomit]

you may be right, but to the author - check this parameter in CAS ANLASSSPERRE_BLSRE_BLS

[ramspeed]

Originally Posted by cryptomit

you may be right, but to the author - check this parameter in CAS ANLASSSPERRE_BLSRE_BLS

I'm running into an error:

Vin is faulty

COAPI-2000: EDIABAS or SGBD error

IFH-0018: initializing failure of the interface handler

EDIT: copied the obd.ini file to C:\Winows, no dice. Then changed the configuration (and com) to Com1. Still no dice.

[Sensible_]

Is your MAN file empty?

[ramspeed]

Originally Posted by Sensible_

Is your MAN file empty?

Yes

[Deebag]

Originally Posted by terminator2k2

I'm no expert but I don't think this is a coding problem as the car was fine till it was washed and dried.

One thing I would check, is there some kind of switch which might of got dislodged or gone faulty. When you start your car you have to put your foot on the clutch or it will not turn over. Is this related? Same for automatic I think I think you have to engage the break pedal?

Might be talking crap but hey just my 2ps worth

If its the clutch switch it should show a picture on the dash indicating to depress the clutch.

[melloww22]

It sounds like your battery dropped below sustainment level while coding and is unable to hold a normal charge. This is why it is recommended to use a battery charger while coding. If you reset your your modules and your still experiencing this problem, you will know that it's not a coding problem

[cryptomit]

Originally Posted by ramspeed

I'm running into an error:

Vin is faulty

COAPI-2000: EDIABAS or SGBD error

IFH-0018: initializing failure of the interface handler

EDIT: copied the obd.ini file to C:\Winows, no dice. Then changed the configuration (and com) to Com1. Still no dice.

are you able to code other modules?

[ramspeed]

Thank you all for your help. Turns out the issue was not even coding related, but it was due to a severed ground on the top of the engine. Nice and simple fix

[wildcatcrazy]

Originally Posted by ramspeed

Thank you all for your help. Turns out the issue was not even coding related, but it was due to a severed ground on the top of the engine. Nice and simple fix

Glad you were able to get it resolved.

[albotronic]

Originally Posted by ramspeed

Thank you all for your help. Turns out the issue was not even coding related, but it was due to a severed ground on the top of the engine. Nice and simple fix

OP glad you got this figured out...just curious how you traced faulty ground?

[ramspeed]

Originally Posted by albotronic

OP glad you got this figured out...just curious how you traced faulty ground?

Yeah, as am I. We used a multi-meter at various points along the starter circuitry to find out if we were losing power at some point. We went all the way from the fuse to the clutch-switch, to the starter button, to the starter (not necessarily in that order). Everything seemed to be fine, but we were getting weird readings when we grounded the starter to the block. So from that point we knew what it was, it was just a witch hunt to find the wire. Ended up being one of the grounds connected by the coil-packs.

[albotronic]

sounds like a lot of work but