[Almaretto]

Originally Posted by zhoudaniell

Great, excited to try this out tomorrow.

Couple of questions:

- How do I "backup" the default settings now in case I screw something up and need to restore it to the current version?
- I ran through the sofware setup for practicebut haven't done the actual coding since my cable doesn't get in until tomorrow - Is there a video or something to show what the process is like when the actual coding happens?
- I'm still a bit confused on the whole "ECU" specific vs chasis specific thing, anyway that you can expand?

Almaretto Would appreciate any input if you have it, definitely appreciate both of your recommendations so far!

VO coding restores ECU to factory settings.

Guides include pictoral step-by-step procedures.

Coding is hardware specific. This relates to available vehicle packages, headlamps, and individual ECU's. So, do not go looking for Fem_Body in an X3 as well as do not use codes meant for an F8x with Xenons on an F25 with Adaptive LED's.

[shawnsheridan]

Originally Posted by zhoudaniell

...- How do I "backup" the default settings now in case I screw something up and need to restore it to the current version?
- I ran through the sofware setup for practicebut haven't done the actual coding since my cable doesn't get in until tomorrow - Is there a video or something to show what the process is like when the actual coding happens?
- I'm still a bit confused on the whole "ECU" specific vs chasis specific thing, anyway that you can expand?..

Backups are worthless. You can restore any ECU to factory settings by activating original FA and VO Coding it.

I don't know what is confusing about ""ECU" specific vs Chassis specific". As an example, since NBT Head Unit ECU can be found installed in any Chassis (F30, F10, F15, etc.), you can use the Cheat Sheet for any chassis, and use it to code NBT ECU in any other chassis that has same ECU. Conversely, since FEM_BODY exists only in F2x/F3x chassis, you would not find it on F10 Cheat Sheet.

[zhoudaniell]

Originally Posted by Almaretto

VO coding restores ECU to factory settings.

Guides include pictoral step-by-step procedures.

Coding is hardware specific. This relates to available vehicle packages, headlamps, and individual ECU's. So, do not go looking for Fem_Body in an X3 as well as do not use codes meant for an F8x with Xenons on an F25 with Adaptive LED's.

What exactly does VO stand for? That's def a peace of mind knowing that I don't have to worry about backing up.

For the pictorial step by step, you're talking about the guides within the E-sys documents correct?

The hardware specific thing makes sense to me. Is there a way to know something like, "fem_body" doesn't exist in a x3 or etc..? Still trying to learn all the lingo. I guess the better question would be, if I code something that where the hardware doesn't exist, it just won't do anything right? Want to confirm that it wouldn't corrupt anythying else.

[zhoudaniell]

Originally Posted by shawnsheridan

Backups are worthless. You can restore any ECU to factory settings by activating original FA and VO Coding it.

I don't know what is confusing about ""ECU" specific vs Chassis specific". As an example, since NBT Head Unit ECU can be found installed in any Chassis (F30, F10, F15, etc.), you can use the Cheat Sheet for any chassis, and use it to code NBT ECU in any other chassis that has same ECU. Conversely, since FEM_BODY exists only in F2x/F3x chassis, you would not find it on F10 Cheat Sheet.

Ok that makes sense. As someone super new to all of this and the lingo, how do I know if a specific hardware is part of the car or not? For example, I wouldn't' know what "fem_body" is and wouldn't know if it was part of my x3 or not.

[shawnsheridan]

Originally Posted by zhoudaniell

Ok that makes sense. As someone super new to all of this and the lingo, how do I know if a specific hardware is part of the car or not? For example, I wouldn't' know what "fem_body" is and wouldn't know if it was part of my x3 or not.

Well, you can see from one Chassis Cheat Sheet to another what ECU's are common to both.

[zhoudaniell]

Originally Posted by shawnsheridan

Well, you can see from one Chassis Cheat Sheet to another what ECU's are common to both.

got it, thanks.

[Almaretto]

Originally Posted by zhoudaniell

What exactly does VO stand for? That's def a peace of mind knowing that I don't have to worry about backing up.

For the pictorial step by step, you're talking about the guides within the E-sys documents correct?

The hardware specific thing makes sense to me. Is there a way to know something like, "fem_body" doesn't exist in a x3 or etc..? Still trying to learn all the lingo. I guess the better question would be, if I code something that where the hardware doesn't exist, it just won't do anything right? Want to confirm that it wouldn't corrupt anythying else.

Fahrzeugauftrag (FA) = German for Vehicle Order (VO)

Yes, PDF's.

For additional guides, tips, & acronyms, see this thread:

Fxx, Ixx, & Gxx Series Coding: Latest Software, Guides, and Tips

One way to know ECU's by chassis:

E-sys_CAFD_ID's_P3.59_v8.1F.pdf

If you look at top of CAFD, you will see FP (Vehicle Profile section):

View post on imgur.com

[zhoudaniell]

Originally Posted by Almaretto

Fahrzeugauftrag (FA) = German for Vehicle Order (VO)

Yes, PDF's.

For additional guides, tips, & acronyms, see this thread:

Fxx, Ixx, & Gxx Series Coding: Latest Software, Guides, and Tips

One way to know ECU's by chassis:

E-sys_CAFD_ID's_P3.59_v8.1F.pdf

If you look at top of CAFD, you will see FP (Vehicle Profile section):

View post on imgur.com

really really stupid question, but where exactly is the port to plug the enet cable in on the car? Is it somewhere under the steering wheel?

[Almaretto]

Originally Posted by zhoudaniell

really really stupid question, but where exactly is the port to plug the enet cable in on the car? Is it somewhere under the steering wheel?

View post on imgur.com

Note: Orientation varies by chassis, but this should show you basic, superior lateral location in footwell space.

[zhoudaniell]

Originally Posted by Almaretto

View post on imgur.com

Note: Orientation varies by chassis, but this should show you basic, superior lateral location in footwell space.

Ok, what am I missing here? I connected to my car, did expert mode and coding and connected via vin. went into the right modules and changed certain ones to actif and werte = 01. saved, activated FA, coded and disconnected. No changes to the car.

Should I be doing something prior to going straight to coding in expert mode? Do I need to do a reset somehow for the car? So far I've coded the auto unlock via engine shut down and the fob close everything functions, but they haven't work.

shawnsheridan if you have any input.

[Almaretto]

Originally Posted by zhoudaniell

Ok, what am I missing here? I connected to my car, did expert mode and coding and connected via vin. went into the right modules and changed certain ones to actif and werte = 01. saved, activated FA, coded and disconnected. No changes to the car.

Should I be doing something prior to going straight to coding in expert mode? Do I need to do a reset somehow for the car? So far I've coded the auto unlock via engine shut down and the fob close everything functions, but they haven't work.

shawnsheridan if you have any input.

NOTE: "CODE" = VO Coding. "Code FDL" = FDL Coding

[zhoudaniell]

Originally Posted by Almaretto

NOTE: "CODE" = VO Coding. "Code FDL" = FDL Coding

Sorry, I believe I did do Code FDL, which is what I'm supposed to do right?

To test if my coding worked or not, should I be disconnecting completely/restarting the car at all? Or should it apply right away?

[Almaretto]

Originally Posted by zhoudaniell

Sorry, I believe I did do Code FDL, which is what I'm supposed to do right?

To test if my coding worked or not, should I be disconnecting completely/restarting the car at all? Or should it apply right away?

90+% work immediately. Older software sometimes take a little while to take effect.

"Reading Coding Data" and check values are changed.

[zhoudaniell]

Originally Posted by Almaretto

90+% work immediately. Older software sometimes take a little while to take effect.

"Reading Coding Data" and check values are changed.

Hm, I'll try it again. So to reiterate, once I connect via vin, I code in to change the actif and werte, save, code FDL and disconnect, it should work?

[Almaretto]

Originally Posted by zhoudaniell

Hm, I'll try it again. So to reiterate, once I connect via vin, I code in to change the actif and werte, save, code FDL and disconnect, it should work?

That or modify offline and then load NCD. You change Drop-down or werte, not both. Werte is what ultimately matters.

You do not have to disconnect for it to work. Trunk changes are one of the exceptions that take 1-15 minutes to take effect. Otherwise, associated functions of coded modules will power cycle and immediately work.

[Almaretto]

Originally Posted by zhoudaniell

Makes sense. Just got to the trunk stuff but glad I made a note about it. I'm trying to do some of the screen stuff, but I don't see a hu_cic module in e-sys. I only have hi_nbt, are those the same or no?

HU = Head Unit
NBT = Next Best Thing

HU_CIC does not equal NBT. The ladder is newer and supports more features, including boot animations.

[zhoudaniell]

Originally Posted by Almaretto

HU = Head Unit
NBT = Next Best Thing

HU_CIC does not equal NBT. The ladder is newer and supports more features, including boot animations.

yeah, I sorta figured that since nbt had a bunch of stuff required in CIC but not all. So just to confirm, the intro screen animation only comes on if your vehicle has been off for a while right? when I was quickly booting the system up in between tests and the system would go straight to the main menu

[Almaretto]

Originally Posted by zhoudaniell

yeah, I sorta figured that since nbt had a bunch of stuff required in CIC but not all. So just to confirm, the intro screen animation only comes on if your vehicle has been off for a while right? when I was quickly booting the system up in between tests and the system would go straight to the main menu

If you code electronics off with driver's door opening, then it will boot animate for each start.

[zhoudaniell]

Originally Posted by Almaretto

If you code electronics off with driver's door opening, then it will boot animate for each start.

Oh yeah, I was thinking about that. May do that in the future, 50/50 on it since sometimes I like to have the music continue to play when I'm packing up.

[Almaretto]

Originally Posted by zhoudaniell

Oh yeah, I was thinking about that. May do that in the future, 50/50 on it since sometimes I like to have the music continue to play when I'm packing up.

my exit process:

1. Pull into space
2. Press Start/Stop --> Vehicle automatically engages "P" & engine turns off.
3. Open drivers door --> electronics automatically turn off, steering wheel telescopes in, and seat moves back
4. Close door
5. Lock vehicle with CA --> doors lock, mirrors fold, & windows roll up

[zhoudaniell]

Originally Posted by Almaretto

my exit process:

1. Pull into space
2. Press Start/Stop --> Vehicle automatically engages "P" & engine turns off.
3. Open drivers door --> electronics automatically turn off, steering wheel telescopes in, and seat moves back
4. Close door
5. Lock vehicle with CA --> doors lock, mirrors fold, & windows roll up

Oh very interesting. How do you get it to automatically engage P, telescope and move back the seat?

Also it looks like the welcome screen is comepletely gone - just went straight to the normal menu. Any idea how to get it back without shutting off electronics with door open?

[titsataki]

I thought for safety purposes when you open the door or hit the start/stop button he car goes to P.

Now the rest of the stuff telescope/move the seat back I would interested.
Also how do you lock the car that puts windows up/folds the mirrors immediately?
I can do it but I have to hold the FOB button or hold comfort access.

Any pointers much appreciated.