![]() ![]() Still under ISTA it shows 0714 which throws error codes related to rear window regulator normalization, etc. Then last time I recoded all the ECUs individually to 0312, except my NBT_HU because it's a retrofit with emulator and I had it coded with the emulator's VIN and 0715 zeitkriterium. Previously, I coded NBT_HU, BKOMBI, ICM, and FEM_BODY with zeitkriterium 0714. ![]() Long question: My factory zeitkriterium is 0312 (F30). Short question: why is ISTA showing the wrong production date of 0714 (zeitkriterium) when I coded all ECUs with 0312 (except NBT_HU)? (never used VCM coding only ECUs individually). Should I lock the ACSM using the Tool32 method? Or lock it in ISTA? Using Esys 3.271 and Esys 30.x. After VO coding all ECUS with 0312 a second time, I also used ESYS external-application to lock/renew the ACSM ECU. Then when I went back to ISTA again, 0714 showed up even after I recoded VO in all the ECUs with 0312 (except NBT_HU 0715). These error codes started after I accidentally coded my ACSM ECU with 0714, which I recoded with 0312 later fixing the restraint system errors, but leaving the rear window errors still.įirst, immediately after VO recoding ACSM with 0312 (factory date) iSTA showed the correct 0312 date (does ISTA get its "production date" from the ACSM ECU?), but the error codes were still there. In another thread this was associated with wrong production date because there is different equipment from 0312 to 0714. (I tried to normalize in ISTA, but does not roll up/down the windows during the ISTA process, otherwise they all work manually or with remote). Previously, I VO coded NBT_HU, BKOMBI, ICM, and FEM_BODY with zeitkriterium 0714. Short question: why is ISTA showing the wrong production date of 0714 (zeitkriterium) when I VO coded all ECUs with 0312 (except NBT_HU)? (never used VCM coding only ECUs individually). Was so close to finishing, but four error codes popped up in ISTA related to (pretty certain) incorrect production date, as ISTA shows 0714. It is far easier if you have doubt to simply VO Code the entire ECU Tree (all ECU), just do NOT do so with motor running, as when it gets to VO Coding the DME / DDE module, it will stall out the motor and the CAFD will become corrupt. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |