|
|
|
|
|
|
BMW Garage | BMW Meets | Register | Today's Posts | Search |
|
BMW 3-Series (E90 E92) Forum
>
NCS VIN error issue
|
|
08-03-2013, 04:46 PM | #1 |
Rainbow Racer
1008
Rep 2,539
Posts |
NCS VIN error issue
Hi guys,
Can anyone help me with this VIN error I received today while trying to initially connect to CAS? I was able to code my car earlier today, then ran into an error (I forgot which) and had to clear the .MAN files to make it work. Instead of hooking it into my car, we then coded my brothers car perfectly. We then connected to my car (forgot to have the car completely on), turned the car off and turn the car on again (engine not running mode). Here is the error code when trying to initially connect to CAS: [16:12:46.025] [2013-08-03] [SERIE] 2020 Error LFCDHDIA.CPP (A_E65CAS.IPS/IPO) CDHapiResultText 1 [16:12:46.025] [2013-08-03] [SERIE] SG antwortet nicht IFH-0009: SG nicht angeschlossen oder meldet sich nicht CAS [16:12:46.139] [2013-08-03] [SERIE] 2020 Error COAPI2.CPP coapiRunCabd 6 [16:12:46.139] [2013-08-03] [SERIE] SG antwortet nicht FGNR_LESEN [16:12:46.144] [2013-08-03] [SERIE] 2020 Error COAPI.CPP copiReadFgNr 12 [16:12:46.144] [2013-08-03] SG antwortet nicht FGNR_LESEN: A_E65CAS I've checked my SYSDATEN.TRC/MAN files, it does not contain my VIN #, plus it's telling me that it's an E92 (which is my brothers VIN# and chassis, I'm an E90) Any assistance would be appreciated. Edit: This was using NCS expert
__________________
-Loe P.-
Prior Car:'14 Audi S5 3.0t DSG [ APR ECU/TCU | Pullies + basic bolt-on mods | 10.861@127.90mph ] Current Car: F82 M4cs | TT-RS | On Order: i4 M50 |
08-03-2013, 08:00 PM | #2 |
Captain
33
Rep 648
Posts |
This could happen for a number of reasons but if no parameters on the car or computer changed (and I mean anything no matter how minor) the cable could've gone bad. I've had this happen before. Check com ports because they can change if you plug the cable into a different port. Also set any performance chips to stock map.
|
Appreciate
0
|
08-04-2013, 07:09 AM | #4 |
Rainbow Racer
1008
Rep 2,539
Posts |
Ok, did some german translation
Basically, it's a communication error, some is not connected, or does not respond, and it's pointing towards whatever FGNR_LESEN/FGNR_LESEN: A_E65CAS I'm pointing towards faulty cable too as nate2k mentioned. Before I order a new one, has anyone else experienced this?
__________________
-Loe P.-
Prior Car:'14 Audi S5 3.0t DSG [ APR ECU/TCU | Pullies + basic bolt-on mods | 10.861@127.90mph ] Current Car: F82 M4cs | TT-RS | On Order: i4 M50 |
Appreciate
0
|
08-05-2013, 05:03 AM | #8 |
Rainbow Racer
1008
Rep 2,539
Posts |
Sure PM me your info and I can contact you sometime this week. The cable still works on my brothers 335i, he tried it last night. I noticed the first time I connected to my car with nsc expert, it added an "x" at the end of my VIN number when it displayed it if that helps.
|
Appreciate
0
|
08-06-2013, 05:27 AM | #10 |
Rainbow Racer
1008
Rep 2,539
Posts |
Do you guys think its possibly a pin 7 & 8 issue? I looked at the pin, they don't look soldered. Do they need to be on a 2009 M3? thanks for the reply ******, i'm looking forward to thursday coding is addictive
__________________
-Loe P.-
Prior Car:'14 Audi S5 3.0t DSG [ APR ECU/TCU | Pullies + basic bolt-on mods | 10.861@127.90mph ] Current Car: F82 M4cs | TT-RS | On Order: i4 M50 |
Appreciate
0
|
08-06-2013, 11:48 AM | #11 | |
Captain
33
Rep 648
Posts |
Quote:
|
|
Appreciate
0
|
08-06-2013, 12:02 PM | #12 | |
Captain
33
Rep 648
Posts |
Quote:
|
|
Appreciate
0
|
Bookmarks |
|
|