[Sensible_]

Looks like progress!

What faults are being thrown now?

[9mmkungfu]

Originally Posted by Sensible_

Looks like progress!

What faults are being thrown now?

Finally!

I'm not sure; I talked to the shop briefly on the phone and they mentioned it but I can't remember now.

It does make sense though, because before all of the module business, the car was originally at the dealer for carbon build up and they also did an injector replacement.

They mentioned they were unable to do the IRAP session because of the module debacle.

Now that this is out of the way, I am hoping to have the session initiated and programming finalized this next week. I just wish I didn't have to go back to the dealer.

[Teq]

What is an IRAP session?

Great that it's almost solved! (I forgot to check this thread)

Before you go to the dealer check with inpa if all modules inside the car have your vin.

[Teq]

Originally Posted by Sensible_

To be honest from what you've said this is all software related. And nothing that can't be corrected with a cheap coding cable and factory tools - i.e BMW Standard Tools. Dealer software isn't cut out for what you need and although I've never used an autologic device I'd imagine they mimic dealer tools rather than give the flexibility of NCSEXPERT for coding.

It sounds like your VO needs to be corrected in both CAS and NFRM then the car must be coded back to default.

Hopefully Teq can confirm...

Exactly. I sounds like someone played with the vo and messed up the coding and didn't revert it back.

[9mmkungfu]

I just wanted to update this thread and say that the new FRM seemed to have fixed the issue. So, the dealer-installed FRM had an incorrect VO and a new FRM with proper VO etc resolved the communication glitch.