NCS error while trying to recode used GM5 Module

[thegenius46m]

Hey all... So this isn't my first rodeo with NCS Expert or coding/programming BMWs in general, but this one is throwing me for on a goose chase and I wanted some feedback on what you all think the issue may be.

Long story short, I have two spare 04+ GM5s on hand and am trying to swap one of them into my friend 02 (09/01 build) M3 who's gm5 is on the fritz. Process should be fairly straightforward where you just plug in the new module and recode the new module with a blank man file so NCS sets the module to defaults based on your car's VO. I did this exact process on my car a few years ago and it was effortless. Trying the exact process on my friend's car tonight yielded a failed effort. I kept getting the error message below where NCS reports that it can't write to the module. It can read no problem so we know the module is connected correctly. Also confirmed the uncoded module allows windows, wipers, central locking, etc to work prior to the recode.

Error: COAPI 2060

I looked up the code recommended disconnecting the battery for 15 min then retrying but nothing changed. Any ideas what could be happening here? Do I have a bad GM5 and just need to try another one, or is this potentially an issue with daten files?



[ATTACH]n21984[/ATTACH]

[Steve]

Did you get this code on each of your spare GM5s or did you only try one of them? Sounds like there might be something going on with this particular unit. I'd try the other spare before changing anything on your computer.

[thegenius46m]

Did you get this code on each of your spare GM5s or did you only try one of them? Sounds like there might be something going on with this particular unit. I'd try the other spare before changing anything on your computer.

Will be heading to my friend's in a few hours to give the spare a go as I only brought one of them last night. I'm thinking the same thing that the unit is faulty, as I've done this same process on my car with zero issues.

[terra]

I feel like I have run into this before, but I cannot for the life of me remember what the solution was if there was one.

Off the top of my head, it might be worth making sure the fuses are good to go. I could see the GM5 being diagnosable but not codable if it's getting power from some fuses but not all. Otherwise maybe double checking that it's not in transport mode or something like that.

[Steve]

I feel like I have run into this before, but I cannot for the life of me remember what the solution was if there was one.

Off the top of my head, it might be worth making sure the fuses are good to go. I could see the GM5 being diagnosable but not codable if it's getting power from some fuses but not all. Otherwise maybe double checking that it's not in transport mode or something like that.

I had an airbag module that I was unable to code because of some internal fault on my E36. I took a known good module and read the coding with pa soft, unplugged the good one, swapped them out and recoded the bad one and it has worked flawlessly since. I wonder if this would work on something like this or if I just got lucky?

[thegenius46m]

I feel like I have run into this before, but I cannot for the life of me remember what the solution was if there was one.

Off the top of my head, it might be worth making sure the fuses are good to go. I could see the GM5 being diagnosable but not codable if it's getting power from some fuses but not all. Otherwise maybe double checking that it's not in transport mode or something like that.

His car did have k bus issues years ago so it could be the car 😑... I did reprogram the old gm5 on his car though back at that time though without issues before we knew better.

[terra]

Yeah if there are K-bus issues that does throw a wrench in things. Do you have trouble coding any other modules?

[thegenius46m]

I had an airbag module that I was unable to code because of some internal fault on my E36. I took a known good module and read the coding with pa soft, unplugged the good one, swapped them out and recoded the bad one and it has worked flawlessly since. I wonder if this would work on something like this or if I just got lucky?

I see what you're saying but unfortunately that wont work, nor would recoding it on another car because the module needs to be reset to defaults based on the VO of the car in question. One thing I have never tried which "COULD" work... read the coding from the old unit then flash that to the replacement unit using my car as the donor. Never done this as it's definitely a hack and not sure how it would pan out later if I want to make coding changes. Plus it would be interesting if the correct vin carries over from the old coding data onto the new module. I feel it doesn't but this is all speculative. Going to try the spare unit later and report back. Thanks though

[terra]

You can just read the VO from the other car. Or even just enter the VO manually. The module itself doesn't actually care what the VO is. You can also just code it on the bench instead of sticking it in another car.

VIN will only be written if you specifically do the FGNR_SCHRIEBEN job or whatever it's called. Though the VIN on the GM5 doesn't actually impact anything.

[thegenius46m]

You can just read the VO from the other car. Or even just enter the VO manually. The module itself doesn't actually care what the VO is. You can also just code it on the bench instead of sticking it in another car.

VIN will only be written if you specifically do the FGNR_SCHRIEBEN job or whatever it's called. Though the VIN on the GM5 doesn't actually impact anything.

Ahh so "technically" you don't have to recode it from another car, it's just best practice? I did anyways, but good to know. And yes, I was talking to my friend last night and said that yes the VIN will be off but since gm5 is not tied to VO, the car does not care what the VIN is so I just left it.

With that said, I resolved the issue last night. Confirmed both my spare GM5s were actually good after finding something interesting... the issue was indeed with my friend's car. Either someone did this prior, or one of us loosened a pin the slightest bit on right most connector of the gm5 harness. Didn't take a before pic but it was one of the inner blue wires that was ever so slightly loosened. I just pushed it back in and we were back in business.

My theory (without digging into the WDS) is that either that specific pin controls the ability to flash the module, or that harness connector acts like an open circuit when loosened and prevents any communication to the module for flashing. Either way, if you get the code I got above, highly recommend starting at the GM5 harness connectors and verifying all pins are seated in the connectors securely.