[ilhan1103]

Originally Posted by shawnsheridan

Yes, but what is standard in Belgium isn't always standard elsewhere, hence really the whole premise or coding ones car. So, behind your standard iDrive option lies an FDL code that must be set to enable that option on non-Belgium cars, that others outside of Belgium will have to code.

True, should have thought about that, my mistake.
Shawnsheridan, would you be so kind as to send me the esys links as well? I'm still not allowed to send or receive pm but I was hoping you could mail it to me?
laraake @ gmail.com

[rolandleth]

Originally Posted by shawnsheridan

Right-Click on the ECU, select Add or maybe it's New, and then navigate to your corresponding .NCD file to add it. Then select it, and FDL Code the ECU.

Awesome, thanks, yet again!

As for:

1. I modified V_SCHWELLE_1 and V_SCHWELLE_2 within REM_01 AND from within PMA, but the rear view camera and the top view camera still can't be activated at high speeds.
2. In the F10 cheat sheet there is FLA_AUTO_AKTIV under FRM module, it sets High Beam Assistant to Automatic On. Is there a way to do this on the F30? The F30 has no FRM module and I have no idea which one is its "counterpart".

Anyone? Any ideas, please?

[shawnsheridan]

Originally Posted by ilhan1103

True, should have thought about that, my mistake.
Shawnsheridan, would you be so kind as to send me the esys links as well? I'm still not allowed to send or receive pm but I was hoping you could mail it to me?
laraake @ gmail.com

You can Receive, just not Send yet. PM Sent.

[dport]

Hi,

Can I get a PM w/ a link to the software and data files? Thanks in advance!

[jjg]

Hello & greetings from Singapore. Can I get the link to the E-Sys program & datafiles as well? Thanks, Jeff.

[shawnsheridan]

Originally Posted by dport

Hi,

Can I get a PM w/ a link to the software and data files? Thanks in advance!

PM Sent.

[shawnsheridan]

Originally Posted by jjg

Hello & greetings from Singapore. Can I get the link to the E-Sys program & datafiles as well? Thanks, Jeff.

With only 1 Post, you can't receive PM's, so provide an email, or wait until you have more forum posts.

[jjg]

Originally Posted by shawnsheridan

With only 1 Post, you can't receive PM's, so provide an email, or wait until you have more forum posts.

hello shawnsheridan, my email is jefferyjoel@gmail.com Big txs in advance.

[shawnsheridan]

Originally Posted by jjg

hello shawnsheridan, my email is jefferyjoel@gmail.com Big txs in advance.

Email sent.

[dinnef30]

Originally Posted by rolandleth

Awesome, thanks, yet again!

As for:

1. I modified V_SCHWELLE_1 and V_SCHWELLE_2 within REM_01 AND from within PMA, but the rear view camera and the top view camera still can't be activated at high speeds.
2. In the F10 cheat sheet there is FLA_AUTO_AKTIV under FRM module, it sets High Beam Assistant to Automatic On. Is there a way to do this on the F30? The F30 has no FRM module and I have no idea which one is its "counterpart".

Anyone? Any ideas, please?

I did following coding with my 328i Jul-2012 Build and I can confirm that activation of the cameras using the Parking button works at high speeds.

REM-7A1 3203 PdcParkMasterVar V_OFF_PF_R UNKNOWN FF
REM-7A1 3203 PdcParkMasterVar V_SCHWELLE_1 UNKNOWN FF
REM-7A1 3203 PdcParkMasterVar V_SCHWELLE_2 UNKNOWN FF
REM-7A1 3203 PdcParkMasterVar D_SCHWELLE_1 UNKNOWN FF
REM-7A1 3203 PdcParkMasterVar D_SCHWELLE_2 UNKNOWN FF

PMA2-BCE 3003 PdcParkMasterVar V_OFF_PF_R UNKNOWN FF
PMA2-BCE 3003 PdcParkMasterVar V_SCHWELLE_1 UNKNOWN FF
PMA2-BCE 3003 PdcParkMasterVar V_SCHWELLE_2 UNKNOWN FF
PMA2-BCE 3003 PdcParkMasterVar D_SCHWELLE_1 UNKNOWN FF
PMA2-BCE 3003 PdcParkMasterVar D_SCHWELLE_2 UNKNOWN FF



PS: I'm as well interested in automatic-High-Beam-Assitant. No solution found yet.

[rolandleth]

I actually tried that, changing the values in BOTH modules and it worked. But only the TopView, the rear view camera still didn't work at high speeds. Oh well, I reverted them back to stock anyway, not interesting enough

Now ... I got another little problem.
I was stupid enough to try "Code Default Values" because "Code" gave me an error (no idea why, tried multiple times, some ECUs worked, some not) and I got lots of dumb errors like windows not working, collision detection not working, front camera not working, stuff like this (probably because values were set to "no options on the car"-state). I restored from the latest saved files, now everything is running with no problems.
BUT, I read somewhere about these so-called shadow errors ... Will the dealer see I had all those dumb, theoretically without logic, errors? How can I remove them, if so?

Thanks.

[shawnsheridan]

Originally Posted by rolandleth

I actually tried that, changing the values in BOTH modules and it worked. But only the TopView, the rear view camera still didn't work at high speeds. Oh well, I reverted them back to stock anyway, not interesting enough

Now ... I got another little problem.
I was stupid enough to try "Code Default Values" because "Code" gave me an error (no idea why, tried multiple times, some ECUs worked, some not) and I got lots of dumb errors like windows not working, collision detection not working, front camera not working, stuff like this (probably because values were set to "no options on the car"-state). I restored from the latest saved files, now everything is running with no problems.
BUT, I read somewhere about these so-called shadow errors ... Will the dealer see I had all those dumb, theoretically without logic, errors? How can I remove them, if so?

Thanks.

1) Which modules gave you an error with CODE? Some module have no codeable data like ZGW, RDC, etc., so maybe that is the reason. If the ECU has no CAFD, it has no codeable data, so you won't be able to FDL Code or VO Code it.

2) DON'T EVER HIT CODE DEFAULTS! This codes the ECU to a factory floor condition, and does not use your VO at all. If you mistakenly hit CODE Defaults, then the solution is to CODE afterwards to VO Code the ECU based on your specific vehicle order.

3) I have never heard of "shadow error codes", and I wouldn't worry about them. If the car isn't throwing and error code on the Instrument Cluster or an iDrive Control Message, you should be fine.

[mokwai]

Hi, can someone email me lawrencetoh@gmail.com the link for E-Sys program & datafiles as well? Thanks in advance. My cable is ready, waiting for the software to proceed.

[shawnsheridan]

Originally Posted by mokwai

Hi, can someone email me lawrencetoh@gmail.com the link for E-Sys program & datafiles as well? Thanks in advance. My cable is ready, waiting for the software to proceed.

Email sent.

[fgalanda]

Originally Posted by shawnsheridan

Yes, If during dealer programming, the ECU CAFD was updated to a new version, that should be read and backed up as "original", then FDL Coded and backed up "as coded". If the CAFD was not updated, then the last "as coded" backup .ncd could be restored.

Could I have the links for the files as well? Thank you.
I have a question regarding this ^^ because I am not completely sure if I understand your comment. Are you saying that if I code the car and dealer upgrade my ECU CAFD while service, I might not be able to restore it back to original? Does it mean if I want to go back I just have to do it all over again and"manually" code it back? Can you please explain it to me? Can the car be bricked when dealer does update? THANK YOU.

[shawnsheridan]

Originally Posted by fgalanda

Could I have the links for the files as well? Thank you.
I have a question regarding this ^^ because I am not completely sure if I understand your comment. Are you saying that if I code the car and dealer upgrade my ECU CAFD while service, I might not be able to restore it back to original? Does it mean if I want to go back I just have to do it all over again and"manually" code it back? Can you please explain it to me? Can the car be bricked when dealer does update? THANK YOU.

When the dealer programs your car, and the firmware of an ECU is updated, that is the "new original". There is no going back to the "previous original", nor would you want to. If prior to that you had FDL Coded that ECU, and backed it up, you would not want to restore that .ncd data because it is based on the older firmware. Instead, you would just FDL Code the ECU again, and back it up afterwards. You should only restore .ncd data if the ECU CAFD is currently the same version as the backed up version.

An ECU can be bricked any time it is flashed if something goes wrong, but that has nothing to do with whether or not the module was coded by you or not.

PM Sent.

[fgalanda]

Originally Posted by shawnsheridan

When the dealer programs your car, and the firmware of an ECU is updated, that is the "new original". There is no going back to the "previous original", nor would you want to. If prior to that you had FDL Coded that ECU, and backed it up, you would not want to restore that .ncd data because it is based on the older firmware. Instead, you would just FDL Code the ECU again, and back it up afterwards. You should only restore .ncd data if the ECU CAFD is currently the same version as the backed up version.

An ECU can be bricked any time it is flashed if something goes wrong, but that has nothing to do with whether or not the module was coded by you or not.

PM Sent.

Thank you So basically those back ups are just in case I want to try new things or if I do mistake somewhere so I can go back right away to last known configuration - but in the long run car firmware will get updated eventually anyway, so I might have to code everything again? Thank you.

[shawnsheridan]

Originally Posted by fgalanda

Thank you So basically those back ups are just in case I want to try new things or if I do mistake somewhere so I can go back right away to last known configuration - but in the long run car firmware will get updated eventually anyway, so I might have to code everything again? Thank you.

That's pretty much it.

[rolandleth]

1) Which modules gave you an error with CODE? Some module have no codeable data like ZGW, RDC, etc., so maybe that is the reason. If the ECU has no CAFD, it has no codeable data, so you won't be able to FDL Code or VO Code it.

2) DON'T EVER HIT CODE DEFAULTS! This codes the ECU to a factory floor condition, and does not use your VO at all. If you mistakenly hit CODE Defaults, then the solution is to CODE afterwards to VO Code the ECU based on your specific vehicle order.

3) I have never heard of "shadow error codes", and I wouldn't worry about them. If the car isn't throwing and error code on the Instrument Cluster or an iDrive Control Message, you should be fine.

Yes, I realized how dumb I was right after, good thing I just had backedup just in case i just restored from the backup, I suppose this was ok too, right?

The FEM_BODY and REM(this doesn't matter anymore, I've done them manually) gave me an error when trying to "Code". I mean it went through the whole process but after clicking "close", in the window that pops at the end where t tells you everything went ok and you can save the report, it told me there was an error, in red fonts. Should have saved it, I guess so I can paste it here

As for shadow codes, there are many talking about them even on these and e90post forums. It's an error that showed up then got fixed by itself so to say, but it remains stores somwhere for the dealer to see it (in the good way, so they can see there was a glitch and might need further investigating).

Also, about what you just explained, about the dealer updating the ECU, how will I know that? That long number of the saved ncd file going to be different than the ECU's, right?

Thanks!

[jmh]

I'd appreciate a link to the E-Sys files/data as well .
jmh at janixworld.com

Thx in advance,
Jan

[rolandleth]

Originally Posted by jmh

I'd appreciate a link to the E-Sys files/data as well .
jmh at janixworld.com

Thx in advance,
Jan

Sent.

[shawnsheridan]

Originally Posted by rolandleth

Yes, I realized how dumb I was right after, good thing I just had backedup just in case i just restored from the backup, I suppose this was ok too, right?

The FEM_BODY and REM(this doesn't matter anymore, I've done them manually) gave me an error when trying to "Code". I mean it went through the whole process but after clicking "close", in the window that pops at the end where t tells you everything went ok and you can save the report, it told me there was an error, in red fonts. Should have saved it, I guess so I can paste it here

As for shadow codes, there are many talking about them even on these and e90post forums. It's an error that showed up then got fixed by itself so to say, but it remains stores somwhere for the dealer to see it (in the good way, so they can see there was a glitch and might need further investigating).

Also, about what you just explained, about the dealer updating the ECU, how will I know that? That long number of the saved ncd file going to be different than the ECU's, right?

Thanks!

Yes, you will know because after the dealer update, the ECU CAFD file name will be newer.