I'm using an ADS interface cable, EDIABAS version 6.4.7 (though I have also tried 6.4.3 and had the same results). As we discussed, I've corrected the port settings as per the guide (FIFO buffers both on 8, no flow control, 9600 baud etc etc), but still no go. Does this help point to a potential cause for all my problems? I'm beginning to wonder if someone hasn't screwed around with this car in the past some time and done some damage here. After a minute it comes up fine and I can view all my coded ZKE options like alarm warnings, light check warnings etc etc. #Ncs expert tool says coding is faulty manual#If I fire up INPA and scan my 'Central Body Electronics ZKE', it gives me a warning saying "Version mismatch, malfunction possible" then proceeds to do some kind of manual check of 'PM modules' whatever that is. *edit* And here's something else that may or may not be of any relevance. All combinations give me the same errors posted above. As per an old thread I saw where Iceman mentioned that NCS 3.0.8 and 3.1.0 can be picky about what EDIABAS version you use, I have now also tried both versions of NCS on both versions of EDIABAS (6.4.3 and 6.4.7). I have also tried NCSexpert 3.0.8 and 3.1.0 and both do the same thing. If I set it to STD:OBD, I just get a transmission disturbed message, so it'll only work in ADS mode with NCS I assume. ADS cable by the way, set to ADS in EDIABAS.ini. Any ideas what's going on? I don't think it's even reading my VIN properly, as at the top of the page it shows 'FG WBA0000000DG94362Q' which is obviously completely wrong as it's put a bunch of 0's in place of letters and numbers, and added a Q to the end.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |