move Esys files to their own folder, update readme
This commit is contained in:
parent
1dfbb69a2f
commit
2c40929817
BIN
ESYS/ESys Cheat Sheet.ods
Normal file
BIN
ESYS/ESys Cheat Sheet.ods
Normal file
Binary file not shown.
68
ESYS/cabooshy.xml
Executable file
68
ESYS/cabooshy.xml
Executable file
|
|
@ -0,0 +1,68 @@
|
|||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<FDL>
|
||||
<!--Cabooshy's FDL Codes for the F Series Mini's-->
|
||||
<cafd id="00001EF6" name="HU_NBT_EVO" author="cabooshy" series="F056">
|
||||
<code description="Enable ID6_Light on ID5 Headunits above 21-03">
|
||||
<group id="3000">
|
||||
<function start="29" end="29" comment="HMI_ID_VERSION" mask="00011100b">id6_light</function>
|
||||
</group>
|
||||
</code>
|
||||
<code description="Revert ID6_Light to ID5">
|
||||
<group id="3000">
|
||||
<function start="29" end="29" comment="HMI_ID_VERSION" mask="00011100b">id5_plus_plus</function>
|
||||
</group>
|
||||
</code>
|
||||
<code description="Enable JCW GP Force Meter Central Display Standard View">
|
||||
<group id="3000">
|
||||
<function start="21" end="21" comment="JOHN_COOPER_WORKS_HMI set to Active" mask="10000000b">aktiv</function>
|
||||
</group>
|
||||
</code>
|
||||
<code description="Disable JCW GP Force Meter Central Display Standard View">
|
||||
<group id="3000">
|
||||
<function start="21" end="21" comment="JOHN_COOPER_WORKS_HMI set to Not Active" mask="10000000b">nicht_aktiv</function>
|
||||
</group>
|
||||
</code>
|
||||
<code description="Enable the Acoustical Lock Confirmation Checkbox (requires Factory Alarm System)">
|
||||
<group id="3000">
|
||||
<function start="110" end="110" comment="ACOUSTICAL_LOCK_CONFIRMATION Set to Active" mask="00000001b">aktiv</function>
|
||||
</group>
|
||||
</code>
|
||||
<code description="Disable the Acoustical Lock Confirmation Checkbox">
|
||||
<group id="3000">
|
||||
<function start="110" end="110" comment="ACOUSTICAL_LOCK_CONFIRMATION set to Not Active" mask="00000001b">nicht_aktiv</function>
|
||||
</group>
|
||||
</code>
|
||||
</cafd>
|
||||
<cafd id="0000123C" name="EPS" author="cabooshy" series="F056">
|
||||
<code description="Set C_SEL_TUNING_BASE to HEAVY">
|
||||
<group id="3001">
|
||||
<function start="1" end="1" comment="C_SEL_TUNING_BASE set to Heavy (F56)" mask="11111111b">C_SEL_TUNING_BASE_F55_A_HEAVY</function>
|
||||
</group>
|
||||
</code>
|
||||
<code description="C_SEL_TUNING_SVT to HEAVY">
|
||||
<group id="3001">
|
||||
<function start="2" end="2" comment="C_SEL_TUNING_SVT set to Heavy (F56)" mask="11111111b">C_SEL_TUNING_BASE_F55_A_HEAVY</function>
|
||||
</group>
|
||||
</code>
|
||||
<code description="C_SEL_TUNING_SPORT to HEAVY">
|
||||
<group id="3001">
|
||||
<function start="3" end="3" comment="C_SEL_TUNING_SPORT set to Heavy (F56)" mask="11111111b">C_SEL_TUNING_BASE_F55_A_HEAVY</function>
|
||||
</group>
|
||||
</code>
|
||||
<code description="Set C_SEL_TUNING_BASE to LIGHT">
|
||||
<group id="3001">
|
||||
<function start="1" end="1" comment="C_SEL_TUNING_BASE set to Heavy (F56)" mask="11111111b">C_SEL_TUNING_BASE_F55_A_LIGHT</function>
|
||||
</group>
|
||||
</code>
|
||||
<code description="C_SEL_TUNING_SVT to LIGHT">
|
||||
<group id="3001">
|
||||
<function start="2" end="2" comment="C_SEL_TUNING_SVT set to Heavy (F56)" mask="11111111b">C_SEL_TUNING_BASE_F55_A_LIGHT</function>
|
||||
</group>
|
||||
</code>
|
||||
<code description="C_SEL_TUNING_SPORT to LIGHT">
|
||||
<group id="3001">
|
||||
<function start="3" end="3" comment="C_SEL_TUNING_SPORT set to Heavy (F56)" mask="11111111b">C_SEL_TUNING_BASE_F55_A_LIGHT</function>
|
||||
</group>
|
||||
</code>
|
||||
</cafd>
|
||||
</FDL>
|
||||
Binary file not shown.
15
README.org
15
README.org
|
|
@ -2,19 +2,20 @@
|
|||
#+description: This repo is here to store and document everything i've learnt from using these programs
|
||||
|
||||
* Why this exists
|
||||
There's not much out there regarding the F56 (Mini) with using these programs, and those that do know are the people that charge for their services (all the power to them).
|
||||
|
||||
This repo is essentially everything i have learned, documented, and put into practice on my own Mini for people who are more fully DIY inclined and want to work on their car themselves
|
||||
without having to pay someone to do it every single time they want small things changing.
|
||||
There's not much out there regarding the F56 (Mini) with using these programs, and those that do know are the people that charge for their services
|
||||
(all the power to them).
|
||||
|
||||
This repo is essentially everything i have learned, documented, and put into practice on my own Mini for people who are more fully DIY inclined and want
|
||||
to work on their car themselves without having to pay someone to do it every single time they want small things changing.
|
||||
|
||||
* E-Sys Cheat Sheet Spreadsheet
|
||||
This spreadsheet is currently a work in progress and i am updating it as often as i can, and is a culmination of everything i have found scattered across the many BMW Forums (as that's
|
||||
where all the Coding/Programming knowledge is) specific to this platform and some more general stuff that applies to the BMW's as well, i hope to have as much of it deciphered as i can
|
||||
to make working with E-Sys just that little bit easier for FDL Coding.\\
|
||||
This spreadsheet is currently a work in progress and i am updating it as often as i can, and is a culmination of everything i have found scattered across
|
||||
the many BMW Forums (as that's where all the Coding/Programming knowledge is) specific to this platform and some more general stuff that applies to the
|
||||
BMW's as well, i hope to have as much of it deciphered as i can to make working with E-Sys just that little bit easier for FDL Coding.
|
||||
|
||||
** E-Sys Launcher Pro 2.8.1 Cheatsheet
|
||||
this again is work in progress, and is specific to the F56 platform in E-Sys (which covers all F series Mini's and the 2 Series Active/Grand Tourer), i only have this older version of
|
||||
launcher pro right now, and it does the job i need it to. if you have another launcher that's more up to date, you might be able to use this with that launcher providing that the XML
|
||||
structure is the same as it is in launcher pro.
|
||||
|
||||
* ISTA+ Handbook
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user