Quote:
Originally Posted by ifr
yes for general pre-packaged options if there is no boolean then its not supported. Production features have boolean so that the car can be configured if it is 1) supported 2) paid for
there are some exceptions to this such as vim and other features (compass?) that are not production released but are supported in i-step. These may have no boolean or are set false, but we know they work when activated.
When you vo code your car it checks the fa for parameters - car build version, region, options (pre-req and new code options), blocking codes, etc. The target ecu is then coded based upon the boolean and fa. This is how dealers retrofit options such as 1cr - they don't fdl code.
1735 is 5at- driving assistant plus, so wherever this is set to true, if your fa has that option and all other conditions are met, then this will be coded aktiv. Still doesn't mean it will work as you may not have the hardware, so you generally see an error in ista.
You can use tm's ncdtool to quickly determine what the boolean codes correspond with and decrypt what is actually being set.
To add - in your remote start example, on cars where it is supported all of those codes that are set to false for the g30, have boolean. So you add 1cr to the fa of a g05 and you get:
1d92:
Dwa motor remote: Aktiv [01]
3d0e:
C_epbi_remote_start: Aktiv [01]
3e52:
Hvac_remote_engine_start: Aktiv [01]
4508:
Hmi_remote_start_enable: Aktiv [01]
51c9:
Min_tankinhalt_standheizen: 2l [02]
standklima_motorlauf: Aktiv_alle_aktivierungswege [01]
7083:
Alh_aktiv_in_pwf_zustand: Ab_standfunktionen [02]
rcm_enable_remote_enginestart: Aktiv [01]
tcm_remote_start: Aktiv [01]
voko_shz_alhz: Voko_aktive_alle_sitze [0f]
|
hi *ifr* if you to busy to answer i understand, just a quick question , how do i find trimmed settings, (your time is worth money, i dont mind to contribute to your coffee)