We have recieved 83% of our goal ..


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Help me understand secure coding
#1
Hello everyone,

I come to you for help regarding coding on cars with Secure Coding/ NCD 2.0.
I understand that I will need to have a signed NCD from BMW backend to code that particular module and it is VO only.

What I do not understand is how do this integrate with coding other modules.

For example:
I am currently helping my friend with retrofitting fog lights in his MY22 G05 US modified for ECE.
Using BimmerUtility I can connect to the car and I see multiple coding options for different modules.
Some modules give me info that there is no cafds for that module - that means it need secure coding right?

So now I take full backup of everything.

If I change VO to have 5A1 it will code body3 module and all other modules needed (in case of 5A1 we only need body3).
So do i need secure coding for it or not since it's VO?
If I code sth that needs module that is ncd 2.0 and it fails on that module, can I use the backup to go back on other modules?

Edit:
I also would like to properly change the car from US to ECE as the previous coders did a mess in the FA, did not change the Language to german, left US radio etc, thus my question regarding the secure coding procedure.
iDrive was coded with sth custom as it has local language but not english...

Regards
Reply
#2
Yes, load the svt tree from backup and code the module. That will restore it
[-] The following 1 user says Thank You to Mehmetdogan2002 for this post:
  • scanman785
Reply




Users browsing this thread: 1 Guest(s)