[ThreeDots]

Originally Posted by shawnsheridan

Your Receive PM function is disabled. PM me when working.

Sorry, I'm new around here. Yes, I noticed that PM's not active yet. I'll be back. Thank you anyway.

[shawnsheridan]

Originally Posted by ThreeDots

Sorry, I'm new around here. Yes, I noticed that PM's not active yet. I'll be back. Thank you anyway.

PM sent.

[peterf15]

Hello Shawn,

can you sent me a PM with the latest E-SYS + Launcher + Tokengenerator ?

Thank you!

[shawnsheridan]

Originally Posted by peterf15

Hello Shawn,

can you sent me a PM with the latest E-SYS + Launcher + Tokengenerator ?

Thank you!

PM sent.

[fe7565]

A question: where can I find information about which ECU is affected by which VO code? For example VO 609 requires HU coding, but also KOMBI, and 205 to 2TB requires FEM ,EGS, ICM ECUs to be coded also. (I know this is dependent on the actual year, model, factory vs retrofit, etc). I saw a guide on ECU flashing (not coding) that lists some dependencies, but seemed complex.

A note to other newbie-coders like me: even if you only code the individual ECU vs he VCM (entire car = all ECUs at once), be careful with ACSM. I accidentally coded it, and on top of that I coded it with a different zeitkriterium (manufacture date) and there was no way to reset the error code via Esys transmitter, ISTA (haven't tried the Tool32 method). Changing back to the factory date fixed it right away, did not need to relock it.

Also, using too new zetkriterium for certain ECUs (example FEM) will throw error codes (for example related to keyless entry, antenna, door locks, rain sensor, etc.). You may be chasing your tail unnecessarily to find the physical source of the errors.

What is the "rule" for zeitkriterium? And how does the I-Level date come in the picture?

[shawnsheridan]

Originally Posted by fe7565

A question: where can I find information about which ECU is affected by which VO code? For example VO 609 requires HU coding, but also KOMBI, and 205 to 2TB requires FEM ,EGS, ICM ECUs to be coded also. (I know this is dependent on the actual year, model, factory vs retrofit, etc). I saw a guide on ECU flashing (not coding) that lists some dependencies, but seemed complex.
...
What is the "rule" for zeitkriterium? And how does the I-Level date come in the picture?[/B]

There is no easy way. In short, what VO Coding does is defined by Boolean Logic in each individual ECU Coding Application File for each FDL Code. First you would have to determine from the FAFP file the SALAPA Option code's corresponding criteriaVal. Then you would have to look in each one of your ECU CAFD Files one by one, and search for any FDL Code with that same criteriaVal, and for any ECU where it exists, it would be affected by VO Coding with that Option Code. Then the actual Value that VO Coding would produce for that FDL Code (e.g. aktiv) would be determined by it and any additional criterial such as zeitkriterium, although you would not need to know the FDL Code Value if simply VO Coding.

So besides being very tedious, you would also need to have Untrimmed FAFP and CAFD files, and be able to Decrypt them.

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.

[fe7565]

Thank you very much Shawn for your kind response.

Although I would be wrong to say I understood everything, I did dig around some based on your description. It certainly seems like a complex effort that may be best avoided with some no-nonsense coding. One thing that came up in my search spurred by your comment is the: NCD . CAFD Tool I downloaded and installed it, but not sure if it's worth the learning curve. I will first try the simpler general coding you outlined.


As far as DME CASF corruption. When I first coded I used Bimmercode and had the car running and not knowing any better coded my DME which promptly as you said stalled my car engine. Luckly, did not notice any issues afterwards. After that, I have been using a power supply that is capable 30 amps continuous at 13V, albeit I read that 50 amp-70 amps is desired. Which contradicts Bimmertech's notes calling for 15 Amps minimum. There are also cheap $15-20 HP server power supplies on Ebay and Amazon that can be fairly easily (one resistor) converted to 14V and 60-100 Amps constant supplies.

[shawnsheridan]

Originally Posted by fe7565

Thank you very much Shawn for your kind response.

Although I would be wrong to say I understood everything, I did dig around some based on your description. It certainly seems like a complex effort that may be best avoided with some no-nonsense coding. One thing that came up in my search spurred by your comment is the: NCD . CAFD Tool I downloaded and installed it, but not sure if it's worth the learning curve. I will first try the simpler general coding you outlined.

NCD / CAFD Tool was a great tool, although its very outdated (Aug 2017) and new CAFD are not supported, and "Results are Suggestions Only":

[paul6763]

Hi shawn could u pm me latest E sys + launcher and generator thanks

[shawnsheridan]

Originally Posted by paul6763

Hi shawn could u pm me latest E sys + launcher and generator thanks

PM sent.

[iDev326]

Hi Shawn,

Can you send me the link for Esys and Tokenmaster Request. Much appreciated, thank you.

[shawnsheridan]

Originally Posted by iDev326

Hi Shawn,

Can you send me the link for Esys and Tokenmaster Request. Much appreciated, thank you.

Your Receive PM function is disabled. PM me when working.

[paul6763]

Thanks for promt reply shawn

[fe7565]

Originally Posted by shawnsheridan

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.

Was so close to finishing, but four error codes popped up in ISTA related to (pretty certain) incorrect production date, as ISTA shows 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).

Long question: My factory zeitkriterium is 0312 (F30). Previously, I VO coded NBT_HU, BKOMBI, ICM, and FEM_BODY with zeitkriterium 0714. 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. Still under ISTA it shows 0714 which throws error codes related to rear window regulator normalization, etc. (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). In another thread this was associated with wrong production date because there is different equipment from 0312 to 0714. 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.

First, 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. 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). After VO coding all ECUS with 0312 a second time, I also used ESYS external-application to lock/renew the ACSM ECU. Should I lock the ACSM using the Tool32 method? Or lock it in ISTA? Using Esys 3.271 and Esys 30.x. and using ISTA 4.31.4

What am I screwing up?

[shawnsheridan]

Originally Posted by fe7565

Was so close to finishing, but four error codes popped up in ISTA related to (pretty certain) incorrect production date, as ISTA shows 0714.

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).

Long question: My factory zeitkriterium is 0312 (F30). Previously, I coded NBT_HU, BKOMBI, ICM, and FEM_BODY with zeitkriterium 0714. 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. Still under ISTA it shows 0714 which throws error codes related to rear window regulator normalization, etc. (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)). In another thread this was associated with wrong production date as the there is different equipment from 0312 to 0714. 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.

First, immediately after 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. Then when I went back to ISTA again, 0714 showed up even after I recoded all the ECUs with 0312 (except NBT_HU 0715). After recoding all ECUS with 0312 a second time, I also used ESYS external-application to lock/renew the ACSM ECU. Should I lock the ACSM using the Tool32 method? Or lock it in ISTA? Tried coding with Esys 3.27 and Esys 30.x. and using ISTA 4.31.4

What am I screwing up?

ISTA should be ready zeitkriterium from FA stored in car VCM.

Lock ACSM with ISTA or Tool32. Makes no difference.

[fe7565]

Originally Posted by shawnsheridan

ISTA should be ready zeitkriterium from FA stored in car VCM.

Lock ACSM with ISTA or Tool32. Makes no difference.

Thank you for the quick reply. How do I change the zeitkriterium in VCM without coding the entire VCM? I have been careful to only code individual ECUs (right click on ECU and "code") and never used to code with the "VCM master" tab.

[shawnsheridan]

Originally Posted by fe7565

Thank you for the quick reply. How do I change the zeitkriterium in VCM without coding the entire VCM? I have been careful to only code individual ECUs (right click on ECU and "code") and never used to code with the "VCM master" tab.

Edit FA, change zeitkriterium, and write FA to VCM. I would not leave it like this though.

[fe7565]

Originally Posted by shawnsheridan

Edit FA, change zeitkriterium, and write FA to VCM. I would not leave it like this though.

Shawn, thank you for the guidance! Managed to change the production date back to factory and used ISTA to normalize the rear window regulators. The four new errors are gone.

Note to self: close driver door ( all doors) or normalization will fail without saying why.

[shawnsheridan]

Originally Posted by fe7565

Shawn, thank you for the guidance! Managed to change the production date back to factory and used ISTA to normalize the rear window regulators. The four new errors are gone.

Note to self: close driver door ( all doors) or normalization will fail without saying why.

[hsjhitts]

Hi Shawn,

Can you kindly share Esys, Ista+ and psdz full latest versions please?

Cheers, Jhitta

[shawnsheridan]

Originally Posted by hsjhitts

Hi Shawn,

Can you kindly share Esys, Ista+ and psdz full latest versions please?

Cheers, Jhitta

Your Receive PM function is disabled. PM me when working.

[hsjhitts]

Cheers buddy, think it’s because I’m a new user.