[CODING] Missing CAFD Files

[shawnsheridan]

Originally Posted by ///Pip

Hey Shawn !

First time coding too ... I PM-ed you a few weeks ago and purchased the cable using the link you provided.

I followed the instructions and managed to connect the car to E-Sys ... but when I try to edit the CAFD ... I can't seem to find the directories ... all the directories has no name ... just "."

...[/IMG]

I'm using

ESysLauncherPremium 2.0.7_Build_54

and

v.55.4_PSdZData_Lite


Car is BMW M4 F82

Thanks in advance :-)

Is E-Sys Launcher Car Series set to F82?

[///Pip]

Originally Posted by shawnsheridan

Is E-Sys Launcher Car Series set to F82?

Yes ... I set it to F020

[shawnsheridan]

Originally Posted by ///Pip

Yes ... I set it to F020

I wrote F82, not F20.

E-Sys Launcher Car Series = F82
E-Sys Connection Target = F20

[///Pip]

Originally Posted by shawnsheridan

I wrote F82, not F20.

E-Sys Launcher Car Series = F82
E-Sys Connection Target = F20

Sorry misunderstood ... hahaha ...

E-Sys Launcher

Car series is F999 ... doesn't let me change to F82

it also says 2 Day(s) until next change

[shawnsheridan]

Originally Posted by ///Pip

Sorry misunderstood ... hahaha ...

E-Sys Launcher

Car series is F999 ... doesn't let me change to F82

it also says 2 Day(s) until next change

You received the following instruction:

* NOTE: E-Sys Launcher Car Series MUST be set to exactly match the car's chassis type you are coding (e.g. F01, F06, F07, F10, F12, F15, F25, F30, F82, F83, etc.). If after install it defaults to F999 and it cannot be changed, change PC Date ahead 4 days, then change E-Sys Launcher Car Series, then change PC Date back to current date. DO NOT create .EST Token and PIN with PC Date advanced 4 days as the Validity Start Date for the token will be 4 days in the future.

[///Pip]

Originally Posted by shawnsheridan

You received the following instruction:

* NOTE: E-Sys Launcher Car Series MUST be set to exactly match the car's chassis type you are coding (e.g. F01, F06, F07, F10, F12, F15, F25, F30, F82, F83, etc.). If after install it defaults to F999 and it cannot be changed, change PC Date ahead 4 days, then change E-Sys Launcher Car Series, then change PC Date back to current date. DO NOT create .EST Token and PIN with PC Date advanced 4 days as the Validity Start Date for the token will be 4 days in the future.

Awesome !

I managed to change it ... I'll try the codings now

[VinnyA320]

Originally Posted by shawnsheridan

You can flash Kombi to 56.2 and code it,

PM sent.

can I get some info on this as well shawn? I'd love to have the HUD coded correctly finally. thanks again!

[aboulfad]

Originally Posted by shawnsheridan

56.2 is latest.

Can I please have the latest? And the ista-p I-level overview. Thank you.

[shawnsheridan]

Originally Posted by VinnyA320

can I get some info on this as well shawn? I'd love to have the HUD coded correctly finally. thanks again!

Originally Posted by aboulfad

Can I please have the latest? And the ista-p I-level overview. Thank you.

PM's sent.

P3.56.2_ISTA-P VERSION AND I-LEVEL OVERVIEW.pdf:

https://mega.co.nz/#!MxQDwY4Y!FoVyv4...kNL92dwOjLhlDY

[aboulfad]

Originally Posted by shawnsheridan

PM's sent.

P3.56.2_ISTA-P VERSION AND I-LEVEL OVERVIEW.pdf:

https://mega.co.nz/#!MxQDwY4Y!FoVyv4...kNL92dwOjLhlDY

Thank you Sir. May I ask why isn't the I level overview included in your PM? Makes it easy to find the info in one place

[shawnsheridan]

Originally Posted by aboulfad

Thank you Sir. May I ask why isn't the I level overview included in your PM? Makes it easy to find the info in one place

Because if you are using the latest PSdZData, it really doesn't matter.

[aboulfad]

Originally Posted by shawnsheridan

Because if you are using the latest PSdZData, it really doesn't matter.

Ok gotcha btw, is there a way to stay up to to date on the new psd releases aside from reading this and other threads?

[shawnsheridan]

Originally Posted by aboulfad

Ok gotcha btw, is there a way to stay up to to date on the new psd releases aside from reading this and other threads?

Not really. There is no public announcement of such.

[///Pip]

Thank you so much Shawn !

E-Sys working great now :-)

[YMB-M3-J2]

Shawn - will 56.2 work on I-step 15-07-502?

[shawnsheridan]

Originally Posted by YMB_M4_j2

Shawn - will 56.2 work on I-step 15-07-502?

Yes.

[YMB-M3-J2]

Awesome. Can you send me those links please?

Thanks

[shawnsheridan]

Originally Posted by YMB_M4_j2

Awesome. Can you send me those links please?

Thanks

PM sent.

[RafaVargas]

Weirdest thing... I did all the installation and setup, Esys 3.24.3, the cadf files you sent me in PM, changed launcher to F082, connected to F020... Edited fembody fdl to disaable start stop as default.... Coded report was successfull no errors.

Then I tried the car to see if the code was working, it wasnt. Connected the esys back and the fdl was stock again... Seems it's not keeping the changes.

I thought it could be the JB4 using OBD2 cable... So I took the jb4 out... Tried a few times and now I cant detect vin with either of my two cables....

Any thoughts?

[shawnsheridan]

Originally Posted by RafaVargas

...Then I tried the car to see if the code was working, it wasnt. Connected the esys back and the fdl was stock again... Seems it's not keeping the changes.
...

Only Possible if you select Code and not Code FDL.

[RafaVargas]

Originally Posted by shawnsheridan

Only Possible if you select Code and not Code FDL.

Could you elaborate on that?

Any idea why neither my cables are getting a ip assigned to the laptop now?

Also my JB4 seems to not be able to keep halo lights full brighten... After turning the car off the halos come back to stock.

Dunno if I mentioned but I'm still on break in, not the this should matter I believe...

[shawnsheridan]

Originally Posted by RafaVargas

Could you elaborate on that?

Any idea why neither my cables are getting a ip assigned to the laptop now?
...

For Connection, turn car off for an hour, and try to connect again later. Make sure motor is running, and Windows Firewall is disabled.

For VO Coding you select the ECU itself, not the CAFD File.

VO = Vehicle Order

VO Code = Coding of all FDL's (100% of the ECU) to predetermined settings based on the Vehicle Order.

Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Right-Click on ECU (the ECU itself not the underlying CAFD) => Select CODE.

FDL = Function Data Line

FDL Code = Coding of individual FDL's in an ECU, overriding the VO Coding.

Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Right-Click on the ECU CAFD and select Read Coding Data => Expand the CAFD Folder by clicking + symbol => Right-Click on the CAFD file and select Edit => Edit CAFD as desired => Click the Blue Floppy Disc Icon to Save CAFD => Click the green back arrow icon => Right-Click on the CAFD file => Select FDL CODE.