E-sys 3.27.1 download and e-sys installation guide…here you go…
- Esys Software Psdzdata 540
- Esys Software Psdzdata 547
- E-sys Software
- Esys Software Psdzdata 548
- E-sys Software Download
- Esys Software Psdzdata 545
Feb 14, 2019 CGDI BMW psdzdata database free download. After complete download, you’ll get this file: Extract the file. The folder contains these files shown as below. Right click the CGDI BMW icon on the desktop, choose the option “Open the location of the folder”. Copy or cut the folder ” psdzdata” and paste it into the category. BMW PSdZData Lite v.4.22.31 Win 1.99 GB The PSdZData are ECU Data Files, is basically a pack that contains all the data needed for E-Sys to be able to code a car, flash ecus and update firmware of B.
E-SYS download
E-Sys LAUNCHER 2.5.3.msiE-Sys 3.27.1.rar
Psdzdata lite download
PSdZData_Lite v3.59.5.rarBMWAiCoder 3.4
BMW e-sys cable
Spend some dollars with a working ENET cable
![Sys Sys](/uploads/1/2/6/5/126585293/725361470.jpg)
E-SYS installation guide
—————————————————————————————————-
EXTRACT E-SYS .rar ARCHIVE
—————————————————————————————————-
01) Extract E-Sys .rar archive to create the following 2 folders:
⦁ “E-Sys Program”
⦁ “E-Sys Documents”
—————————————————————————————————-
INSTALL bmw E-SYS
—————————————————————————————————-
02) From the extracted “E-Sys Program” folder, run “E-Sys_Setup_x_xx_x_xxxxxx.exe” to install program to default location (i.e. “C:EC-AppsESGE-Sys”)
03) When prompted, accept the default installation location Data Path (i.e. “C:Data”).
* NOTE: If upgrading from a previous E-Sys version, first uninstall current E-Sys version via Windows Control Panel.
—————————————————————————————————-
EXTRACT PSdZData_Lite – OR – PSdZData_Full .rar ARCHIVE
—————————————————————————————————-
04) Extract the PSdZData_Lite or PSdZData_Full .rar archive to produce the “psdzdata” folder.
05) Make sure that there is an empty “dist” folder in each of the psdzdata chassis folders, and if missing, create as needed, e.g.:
⦁ C:DatapsdzdatamainseriesF001F001_xx_xx_xxxodxdist
⦁ C:DatapsdzdatamainseriesF010F010_xx_xx_xxxodxdist
⦁ C:DatapsdzdatamainseriesF020F020_xx_xx_xxxodxdist
⦁ C:DatapsdzdatamainseriesF025F025_xx_xx_xxxodxdist
⦁ C:DatapsdzdatamainseriesF056F056_xx_xx_xxxodxdist
⦁ C:DatapsdzdatamainseriesI001I001_xx_xx_xxxodxdist
⦁ C:DatapsdzdatamainseriesK001K001_xx_xx_xxxodxdist
⦁ C:DatapsdzdatamainseriesKE01KE01_xx_xx_xxxodxdist
⦁ C:DatapsdzdatamainseriesRR01RR01_xx_xx_xxxodxdist
⦁ C:DatapsdzdatamainseriesS15AS15A_xx_xx_xxxodxdist
—————————————————————————————————-
Esys Software Psdzdata 540
INSTALL PSdZData (Lite or Full)
—————————————————————————————————-
06) If existing “psdzdata” folder exists in “C:Data” (i.e. “C:Datapsdzdata”) DELETE it.
07) From the PSdZData_Lite or PSdZData_Full extraction, copy the “psdzdata” folder to “C:Data” (i.e. “C:Datapsdzdata”)
* NOTE: If upgrading from a previous PSdZData version, DELETE old PSdZData folder and REPLACE with new PSdZData folder (DO NOT copy
(merge) new PSdZData folder on on top of old PSdZData folder).
* NOTE: PSdZData Lite Version has all ECU Firmware files removed, which are needed only for flashing new firmware onto ECU’s and which ARE
NOT needed at all for any Coding. PSdZData Full Version is needed ONLY for Programming (flashing) ECU’s with new Firmware.
* NOTE: BMW AG made changes to PSdZData beginning with 54.2 PSdZData where they removed (trimmed) all descriptive text from CAFD (and
FAFP) files, making FDL Coding of ECU’s difficult, as the FDL Codes can no longer be easily located. E-Sys Launcher Premium 2.x uses historical
CAFD data from older Untrimmed PSdZData releases to dynamically map the trimmed data back into E-Sys.
—————————————————————————————————-
INSTALL E-SYS LAUNCHER PREMIUM AND CREATE .EST TOKEN & PIN
—————————————————————————————————-
08) Run the “ESysLauncherPremiumSetup_2.0_Build_xx.msi” to install program to default location (“C:Program Files (x86)TokenMasterE-Sys
Launcher PremiumESysLauncher.exe”)
09) Run “E-Sys Launcher Premium” from Desktop Shortcut.
10) In “Path” field, press the “…” Button, and Select folder location to store Token file Path (i.e. “C:Data”).
11) In “PIN” field, enter any alphanumeric 4-12 character PIN to use with your Token file (e.g. “1234”).
12) In “Confirm” field, enter the same alphanumeric 4-12 character PIN previously entered (e.g. “1234”).
13) Press the “Generate Token” button, and wait for the “EST Software Token Successfully created at “C:DataFreeToken.est” message to appear,
and then press the “OK” button.
14) When the main E-Sys Launcher Premium window appears, press the “Abort” button at bottom of it.
15) Select the “Car Series” Dropdown box and choose your exact chassis type (e.g. F01, F06, F07, F10, F12, F15, F25, F30, F82, F83, etc.).
*NOTE: With E-Sys Launcher Premium version, once “Car Series” is set, it can only be changed every 3 days, so be sure to set it correctly during
initial installation and setup. If you do not want this restriction, you can obatain E-Sys Launcher Pro version from TokenMaster, which lacks this
* bmw esys token generator can be reached via:
http://www.eobdtool.co.uk/wholesale/bmw-enet-ethernet-to-obd-interface-cable-e-sys-icom-coding-f-series.html
16) After “Car Series” is properly set, press the “Launch Now!” button.
*NOTE: It will take E-Sys a while to open as it writes its the log file.
—————————————————————————————————-
CONFIGURE E-SYS software
—————————————————————————————————-
17) On E-Sys Menu Bar, select “Options” and then “Settings”:
- A) On the “PROGRAM” Tab, set the Directories => Data: path to “C:Data”
- B) On the “EST” Tab, set the Developer-Soft-Token => EST: path to match .est Token file created in Step 12) above (i.e. “C: Data
FreeToken.est” )
Esys Software Psdzdata 547
- C) On the “OPTIONS” Tab Uncheck the boxes for “Update VCM after TAL execution” and “Update MSM after TAL execution”.
18) Press “OK” to close the Settings Diaglog Window and then from the Menu Bar press “File” and then “Exit” to shut down E-Sys application.
—————————————————————————————————-
CONNECT TO CAR WITH E-SYS VIA ENET CABLE
—————————————————————————————————-
19) Make connection from car’s OBDII port to computer LAN port with OBDII-ENET interface cable.
20) Ensure Car has adequate power and is switched on.
*NOTE: A continuous power source of at least 12.6 Volts is needed. Failure to maintain proper voltage can lead to corruption of ECU Data. As
such, ideally the car is connected to an external charger. In lieu of using an external charger, the car can instead be coded with the engine running
in order to maintain proper voltage, which is acceptable for coding all ECU’s EXCEPT the DME (Digital Motor Electronics) ECU or DDE (Digital Diesel
Electronics) ECU. The DME/DDE are typically not coded anyway, so this ECU limitation is generally not an issue.
21) Wait a few minutes until the Laptop Windows wired network adapter icon shows a Connection with the yellow exclamation point over it.
*NOTE: The car does NOT have a DHCP server, so it does NOT assign an IP Address to the computer. Both the computer and the car will go into
DHCP fallback mode, each assigning themselves a random Class-B IP Address so that they can talk to each other. This can take up to 60 seconds,
so you have to wait until the PC has an IP address before you try to connect). Class-B IP Address range is from 128.0.0.0 to 191.255.255.255.
Automatic Private IP Addressing (APIPA) is a network client-side process used as a fall-back position when DHCP services are not available on the
network but the client devices are configured to use DHCP for their IP address configuration. APIPA allows the client device to randomly choose one
of the 65,534 addresses available in the Class B network address of 169.254.0.0/16.
*NOTE: If you are running E-Sys in a Virtual Machine (VM), make sure you set the VM NIC to bridging mode. Do NOT use NAT.
E-sys Software
22) Run “E-Sys Launcher Premium” from Desktop Shortcut to open E-Sys application.
23) On E-Sys Toolbar Press the “Connect” Button and in the “Open Connection” window under “Target”, select desired Target Vehicle based on
car’s Chassis.
(e.g. “TargetSelector:Project=F010-xx-xx-xxx, VehicleInfo=F010”)
*NOTE: Do NOT select the Target with the “_DIRECT” suffix (e.g. TargetSelector:Project=F010-xx-xx-xxx, VehicleInfo=F010_DIRECT).
*NOTE:
F001 psdzdata covers F001/F002/F003/F004/F007/RR04/RR05/RR06 (5-Series GT is an F07 NOT an F10)
F010 psdzdata covers F006/F010/F011/F012/F013/F018
F020 psdzdata covers F020/F021/F022/F023/F030/F031/F032/F033/F034/F035/F036/F080/F082/F083/F087
F025 psdzdata covers F015/F016/F025/F026/F085/F086
F056 psdzdata covers F039/F045/F046/F047/F048/F049/F052/F054/F055/F056/F057/F060
I001 psdzdata covers I001/I012
K001 psdzdata covers K010/K018/K019/K021/K022/K023/K032/K033/K045/K046/K047/K048/K049/K050/K051/K052/K053/K054
K080/K081
KE01 psdzdata covers K017
RR01 psdzdata covers RR01/RR02/RR03
S15A psdzdata covers F090/G001/G002/G011/G012/G030/G031/G032/RR11/RR12/RR31
*NOTE: If the “Open Connection” window under “Target” is empty (no targets), verify the following:
- A) That the psdzdata chassis folders each have an empty “dist” folder (See Step 05).
- B) That the “psdzdata” folder is installed properly (See Step 07).
- C) That the “Directories => Data: path is set properly (See Step 17A).
24) In the “Open Connection” window under “Interface” select “Connection via VIN”.
*NOTE: If “Connection via VIN” is grayed out and Vehicle VIN is not shown verify the following:
- A) ENET Cable connection to car is good.
- B) Car has proper voltage (Make sure Charger voltage is at least 12.6 Volts or motor is running if car is not on a Charger).
- C) Laptop Windows Firewall and any Antivirus software is disabled and not running.
- D) Laptop Lan Adapter has a 169.254.xxx.xxx IP address (Make sure it is using DHCP and does not have a Static IP address assigned to it).
If “Connection via VIN” remains grayed out, close E-Sys and shut car completely off for 30 minutes, and try connection again beginning with Step19.
Esys Software Psdzdata 548
25) In the “Open Connection” window under “vehicle-specific parameter (optional)” select “Series, I-Step Shipment”, and leave the two
Dropdown boxes blank.
*NOTE: Do NOT select “Read parameters from VCM”.
26) In the “Open Connection”, select “Connect” button.
*NOTE: Window should pop up confirming successful connection and car can now be accessed with E-Sys.
————————-
NOTES:
————————-
- A) Each time E-Sys is launched, the first time the FDL Editor or CAF-Viewer is invoked, either directly via “Editors & Viewers => FDL-Editor” or
“Editors & Viewers => CAF-Viewer” or indirectly via right-clicking on a module’s read CAFD and selecting “Edit FDL”, you will need to enter the EST
Token PIN.
- B) Coding KOMBI (Instrument Cluster) module will cause the car to chime and the dashboard to reset including the clock. Simply reset the vehicle
Date and Time via iDrive when done coding module.
E-sys Software Download
- C) Coding some ECU’s can result in a variety of initial Error Messages appearing on CID Screen. This is common. Just click on “Ok” to dismiss
them, and they should NOT reappear again. If errors persist, try and clear them with E-Sys as follows:
⦁ Click “External Applications” in the left menu.
⦁ Click “External Application”
⦁ Double-click “Transmitter”
⦁ Scroll to the bottom and click “… Clear all DTCs (clear DTC,clear Infospeicher,ZFS – DM_Lock,clear ZFS – DM_Clear,ZFS – DM_Unlock) to
highlight it.
⦁ Click “Connect” button.
⦁ Click the “Send” button.
- D) Some ECU’s take a long time before the changes begin working (e.g. trunk and mirror close). If still not working after a full hour of car being
shut off, try recoding the module again, even if it looks like the correct parameter (e.g.”nicht_aktiv”) is set.
- E) If you want to read an ECU CAFD’s last as-coded settings (i.e. net coding data), go to the “Editors & Viewers => FDL-Editor”, put your PIN in,
and then navigate to your CAF folder (C:DataCAF) and select the desired CAFD file’s corresponding read coding data .ncd file. You do NOT needto be connected to the car.
(e.g. Module CAFD Name cafd_000000f9.caf.007_003_167 = CAFD_000000F9_007_003_067.ncd)
- F) If you want to look at an unread CAFD file, go to the “Editors & Viewers => CAF-Viewer”, put your PIN in, and then navigate to your CAFD folder
(C:Datapsdzdataswecafd) and select the desired CAFD. You DO NOT need to be connected to the car.
(e.g. Module CAFD Name cafd_000000f9.caf.007_003_167)
G:) For known Coding Parameters, search for Coding Cheat Sheet for your chassis (e.g. F10, F30, F20, F15, etc.)
(BIG THANKS to hayk57 in the MH community)
Related Post:
102-06-2014, 10:30 PM (This post was last modified: 10-20-2014, 05:35 PM by zekan23.)
BMW E-Sys 3.25.3 + PSdZData v2.51.3 + Manuals
----------------------------------------------------------------------------------------------------
INSTALL E-SYS & EDIABAS
----------------------------------------------------------------------------------------------------
01) Run 'E-sysE-Sys_Setup_3_25_3_RC_b40861.exe' to install program to default location 'C:EC-AppsESG' (i.e. 'C:EC-AppsESGE-Sys')
02) During E-Sys installation, when prompted change the default Data Path from 'C:Data' to 'C:ESysData'.
03) Copy 'EDIABAS' folder to the root of 'C:' (i.e. 'C:EDIABAS')
04) Run 'C:EDIABASHardwareEdiabas-KonfiguratorEdiabas-Konfigurator.exe' and make sure 'Interface:' is set to 'INTERFACE=ENET'.
(It should already be set, but check anyway - if you need to change it, use the drop-down list and select 'INTERFACE=ENET' and then 'Andern' and then 'Ende'.)
----------------------------------------------------------------------------------------------------
INSTALL E-SYS EST TOKEN
----------------------------------------------------------------------------------------------------
05) Create subfolder 'E-Sys EST' under 'C:ESysData' (i.e. 'C:ESysDataE-Sys EST')
06) Copy EST Token File (e.g. 'esys_v1.4.EST') to 'E-Sys EST' folder (i.e. 'C:ESysDataE-Sys ESTesys_v1.4.EST')
----------------------------------------------------------------------------------------------------
INSTALL PSdZData
----------------------------------------------------------------------------------------------------
07) If existing 'psdzdata' folder exists in 'C:ESysData' (i.e. 'C:ESysDatapsdzdata') delete it.
08) Copy downloaded 'psdzdata' folder to 'C:ESysData' (i.e. 'C:ESysDatapsdzdata')
09) Make sure that there is a 'Dist' folder in each of the Chassis folders (F01/F10/F20/F25/K001/RR01) etc.
(e.g. 'C:ESysDatapsdzdatamainseriesF010F010_12_03_511odxdist')
(It should already be set, but check anyway - if not there - create empty 'Dist' folders for each chassis folder)
----------------------------------------------------------------------------------------------------
CONNECT AND CONFIGURE E-SYS
----------------------------------------------------------------------------------------------------
10) Turn Car's Auxiliary Power On (Engine Off) and make connection to car with OBDII-Enet Interface Cable
(Wait a few minutes until the network adapter icon shows a Connection with the yellow exclamation point over it)
(The car does not have a DHCP server, so it does not assign an IP Address to the computer. Both the computer and the car will go into DHCP fallback mode, each assigning themselves a random Class-B IP Address so that they can talk to each other. This can take up to 60 seconds, so you have to wait until the PC has an IP address before you try to connect).
(If you are running E-Sys in a Virtual Machine (VM), make sure you set the VM NIC to bridging mode, not NAT.)
11) Launch 'C:EDIABASHardwareENETZGW_SEARCH.exe' to verify cable and connection are working.
(Select Refresh Button until connection data appears (IP, ADR, MAC, & VIN) verifying actual communication to the car)
(ZGW_SEARCH.exe is non-functional (informational only) and not a requirement to run E-Sys. If you cannot get ZGW_SEARCH.exe working, instead verify the laptop's wired network adapter has an Class-B IP Address (128 to 191.xxx.xxx.xxx)).
12) Run 'C:EC-AppsESGE-SysE-Sys.exe' (It will take E-Sys a while to write the log file).
Under Options, Settings:
On the PROGRAM TAB, set the Directories - Data Path to 'C:ESysData'
On the EST Tab, set the Developer-Soft-Token EST Path to match EST Token installed in Step 06 above
(e.g. 'C:ESysDataE-Sys ESTCode Away.EST')
On the ODX Tab, set the ODX Rule Path to 'C:ESysDataRules'
13) Hit the Connect Button on E-Sys toolbar and select desired Target Vehicle (e.g. TargetSelectorroject=F010-12-03-511m VehicleInfo=F010)
(DO NOT use the Target with the _DIRECT suffix (e.g. TargetSelectorroject=F010-12-03-511m VehicleInfo=F010_DIRECT)
(F001 psdzdata covers the F01/F02/F04 7-series and the F07 5-series)
(F010 psdzdata covers the F10 5-series, the F12/F13 6-series, and the F06 6-series Gran Coupé)
(F020 psdzdata covers the F20 1-series and F30 3-series (There is no Z4 F-chassis yet))
(F025 psdzdata covers the F25 X3-series (There is no X5 F-chassis yet))
14) Select Connection via VIN, and click Connect
(Window should pop up confirming successful connection)
(The program will remember the 'connection via VIN' for future connections)
----------------------------------------------------------------------------------------------------
NOTES
----------------------------------------------------------------------------------------------------
A) Each time E-Sys is launched, the first time the FDL Editor or CAF-Viewer is invoked, either directly via 'Editors & Viewers => FDL-Editor' or 'Editors & Viewers => CAF-Viewer' or indirectly via right-clicking on a module's read CAFD and selecting 'Edit FDL', you will need to enter the EST Token PIN, which came separately with the EST Token).
B) Coding KOMBI (Instrument Cluster) module will cause the car to chime and the dashboard to reset including the clock. Simply reset the vehicle Date and Time via iDrive when done coding module.
C) Some modules take a long time before the changes begin working (e.g. trunk and mirror close). If still not working after an hour or so of being off (asleep), try recoding the module again, even if it looks like the correct parameter (e.g.'nicht_aktiv') is set.
D) If Coding for an extended period of time (>30 minutes or so) ensure car is on a charger to avoid killing the battery. You can safely code with the Engine Running to keep it charged with the exception of the DME module.
E) If you want to look at a read CAFD file's net coding data (.ncd files) go to the 'Editors & Viewers => FDL-Editor', put your PIN in, and then navigate to your CAF folder (C:ESysDataCAF) and select the desired CAFD file's corresponding read coding data .ncd file. You DO NOT need to be connected to the car.
(e.g. Module CAFD Name cafd_000000f9.caf.007_003_167 = CAFD_000000F9_007_003_067.ncd)
F) If you want to look at an unread CAFD file, go to the 'Editors & Viewers => CAF-Viewer', put your PIN in, and then navigate to your CAFD folder (C:ESysDatapsdzdataswecafd) and select the desired CAFD. You DO NOT need to be connected to the car.
(e.g. Module CAFD Name cafd_000000f9.caf.007_003_167)
----------------------------------------------------------------------------------------------------
Patch Installation Instructions
----------------------------------------------------------------------------------------------------
Replace the original JAR files with the ones supplied here:
[*] est-cm-01.05.01.jar --> C:EC-AppsESGE-Syslibestcmest-cm-01.05.01.jar
[*] psdz-core.jar --> C:EC-AppsESGE-SyslibPsdZpsdz-core.jar
[*] copy EST Token File (e.g. 'esys_v1.4.est') to 'E-Sys EST' folder (i.e. 'C:ESysDataE-Sys ESTesys_v1.4.est')
example of coding
NcdCafdTool v0.2.4 by MasterToken for coding comparing and changing FA etc
Author thread here <<< Link >>>
Do not forget say and press reputation button
----------------------------------------------------------------------------------------------------
INSTALL E-SYS & EDIABAS
----------------------------------------------------------------------------------------------------
01) Run 'E-sysE-Sys_Setup_3_25_3_RC_b40861.exe' to install program to default location 'C:EC-AppsESG' (i.e. 'C:EC-AppsESGE-Sys')
02) During E-Sys installation, when prompted change the default Data Path from 'C:Data' to 'C:ESysData'.
03) Copy 'EDIABAS' folder to the root of 'C:' (i.e. 'C:EDIABAS')
04) Run 'C:EDIABASHardwareEdiabas-KonfiguratorEdiabas-Konfigurator.exe' and make sure 'Interface:' is set to 'INTERFACE=ENET'.
(It should already be set, but check anyway - if you need to change it, use the drop-down list and select 'INTERFACE=ENET' and then 'Andern' and then 'Ende'.)
----------------------------------------------------------------------------------------------------
INSTALL E-SYS EST TOKEN
----------------------------------------------------------------------------------------------------
05) Create subfolder 'E-Sys EST' under 'C:ESysData' (i.e. 'C:ESysDataE-Sys EST')
06) Copy EST Token File (e.g. 'esys_v1.4.EST') to 'E-Sys EST' folder (i.e. 'C:ESysDataE-Sys ESTesys_v1.4.EST')
----------------------------------------------------------------------------------------------------
INSTALL PSdZData
----------------------------------------------------------------------------------------------------
07) If existing 'psdzdata' folder exists in 'C:ESysData' (i.e. 'C:ESysDatapsdzdata') delete it.
08) Copy downloaded 'psdzdata' folder to 'C:ESysData' (i.e. 'C:ESysDatapsdzdata')
09) Make sure that there is a 'Dist' folder in each of the Chassis folders (F01/F10/F20/F25/K001/RR01) etc.
(e.g. 'C:ESysDatapsdzdatamainseriesF010F010_12_03_511odxdist')
(It should already be set, but check anyway - if not there - create empty 'Dist' folders for each chassis folder)
----------------------------------------------------------------------------------------------------
CONNECT AND CONFIGURE E-SYS
----------------------------------------------------------------------------------------------------
10) Turn Car's Auxiliary Power On (Engine Off) and make connection to car with OBDII-Enet Interface Cable
(Wait a few minutes until the network adapter icon shows a Connection with the yellow exclamation point over it)
(The car does not have a DHCP server, so it does not assign an IP Address to the computer. Both the computer and the car will go into DHCP fallback mode, each assigning themselves a random Class-B IP Address so that they can talk to each other. This can take up to 60 seconds, so you have to wait until the PC has an IP address before you try to connect).
(If you are running E-Sys in a Virtual Machine (VM), make sure you set the VM NIC to bridging mode, not NAT.)
11) Launch 'C:EDIABASHardwareENETZGW_SEARCH.exe' to verify cable and connection are working.
(Select Refresh Button until connection data appears (IP, ADR, MAC, & VIN) verifying actual communication to the car)
(ZGW_SEARCH.exe is non-functional (informational only) and not a requirement to run E-Sys. If you cannot get ZGW_SEARCH.exe working, instead verify the laptop's wired network adapter has an Class-B IP Address (128 to 191.xxx.xxx.xxx)).
12) Run 'C:EC-AppsESGE-SysE-Sys.exe' (It will take E-Sys a while to write the log file).
Under Options, Settings:
On the PROGRAM TAB, set the Directories - Data Path to 'C:ESysData'
On the EST Tab, set the Developer-Soft-Token EST Path to match EST Token installed in Step 06 above
(e.g. 'C:ESysDataE-Sys ESTCode Away.EST')
On the ODX Tab, set the ODX Rule Path to 'C:ESysDataRules'
13) Hit the Connect Button on E-Sys toolbar and select desired Target Vehicle (e.g. TargetSelectorroject=F010-12-03-511m VehicleInfo=F010)
(DO NOT use the Target with the _DIRECT suffix (e.g. TargetSelectorroject=F010-12-03-511m VehicleInfo=F010_DIRECT)
(F001 psdzdata covers the F01/F02/F04 7-series and the F07 5-series)
(F010 psdzdata covers the F10 5-series, the F12/F13 6-series, and the F06 6-series Gran Coupé)
(F020 psdzdata covers the F20 1-series and F30 3-series (There is no Z4 F-chassis yet))
(F025 psdzdata covers the F25 X3-series (There is no X5 F-chassis yet))
14) Select Connection via VIN, and click Connect
(Window should pop up confirming successful connection)
(The program will remember the 'connection via VIN' for future connections)
----------------------------------------------------------------------------------------------------
NOTES
----------------------------------------------------------------------------------------------------
A) Each time E-Sys is launched, the first time the FDL Editor or CAF-Viewer is invoked, either directly via 'Editors & Viewers => FDL-Editor' or 'Editors & Viewers => CAF-Viewer' or indirectly via right-clicking on a module's read CAFD and selecting 'Edit FDL', you will need to enter the EST Token PIN, which came separately with the EST Token).
B) Coding KOMBI (Instrument Cluster) module will cause the car to chime and the dashboard to reset including the clock. Simply reset the vehicle Date and Time via iDrive when done coding module.
C) Some modules take a long time before the changes begin working (e.g. trunk and mirror close). If still not working after an hour or so of being off (asleep), try recoding the module again, even if it looks like the correct parameter (e.g.'nicht_aktiv') is set.
D) If Coding for an extended period of time (>30 minutes or so) ensure car is on a charger to avoid killing the battery. You can safely code with the Engine Running to keep it charged with the exception of the DME module.
E) If you want to look at a read CAFD file's net coding data (.ncd files) go to the 'Editors & Viewers => FDL-Editor', put your PIN in, and then navigate to your CAF folder (C:ESysDataCAF) and select the desired CAFD file's corresponding read coding data .ncd file. You DO NOT need to be connected to the car.
(e.g. Module CAFD Name cafd_000000f9.caf.007_003_167 = CAFD_000000F9_007_003_067.ncd)
F) If you want to look at an unread CAFD file, go to the 'Editors & Viewers => CAF-Viewer', put your PIN in, and then navigate to your CAFD folder (C:ESysDatapsdzdataswecafd) and select the desired CAFD. You DO NOT need to be connected to the car.
(e.g. Module CAFD Name cafd_000000f9.caf.007_003_167)
----------------------------------------------------------------------------------------------------
Patch Installation Instructions
----------------------------------------------------------------------------------------------------
Replace the original JAR files with the ones supplied here:
[*] est-cm-01.05.01.jar --> C:EC-AppsESGE-Syslibestcmest-cm-01.05.01.jar
[*] psdz-core.jar --> C:EC-AppsESGE-SyslibPsdZpsdz-core.jar
[*] copy EST Token File (e.g. 'esys_v1.4.est') to 'E-Sys EST' folder (i.e. 'C:ESysDataE-Sys ESTesys_v1.4.est')
example of coding
NcdCafdTool v0.2.4 by MasterToken for coding comparing and changing FA etc
Author thread here <<< Link >>>
Do not forget say and press reputation button
![Esys software psdzdata 547 Esys software psdzdata 547](/uploads/1/2/6/5/126585293/113274502.jpg)
E-Sys 3.25.3 and PSdZData Files v51.3.rar
72.97 KB
NcdCafdTool_V0.2.4.zip
Esys Software Psdzdata 545
316.29 KB
Thanks given by:iwoo , kiwi1hu , fabulous , wokounek , 017er , Fjurie , Smallville , smlee747 , propps , Autronic , pesona , mikakat , sarkisye , brunofraga , majo , Motasem , bossix , asdfgh , immarius , pancho , fadifadi , digitalbac , Mitroha , maximus1980 , OKCZ , CarlosF11 , Amused , wlemi , nader_h , ruben_17non , ime-actia , bydle52 , mangis , nama , hanz330 , taolian , ICEman-x , honzabmw , Chriz123 , turbodieselro , thchiang , ANDRIKSSON , bmwpeti , dragos , sec5klp , charles.soori , ktmjurca , bmwkastela , hubiheu , proautotechnology , shahbazart , EagleOne , onhus , Michael Drossos , abac , ristici , [email protected] , ashjab , hogjf , ro0lz , burko80 , dm19 , zuzuhe , BMWcare , alex_ng , utzeman , acercompaq , jimmy9980 , Lycos , RS4V8 , thcar685 , jasnicdusan , paskizo , wzw99 , tindan , natural7 , micromax , smahel , wojtekt , ssqxczc , automac , abdonete , imex , marius_d_2002 , mixx0108 , meesaeng , habe , pickeringroger , HarryH , steff , bmw_johnny , gnus , Kenny , kim sun sung , Crazyman , Slipah , buio service , -Kai- , FrancisNYC , iliandt , supra94tt , BMWandy , Rockiii , vwgolfvr61 , bedini , B3am3r , skipex , huzefa , Claudiu_dar , cm048 , xxxjecxxx , diman881 , deejayvlad , mark79 , altum , jammachado , colouny , michalkow , jimvou , tortu25 , coolman , tuareg , a66ict3d , misterlaan , mephala , bmw232700 , luc242 , vothanhtam19 , ducus , abdullllli , nerijusra , Juzas , acid , jaxone , BC Service , Jerry15 , janiki , flip49 , AutoLumen , Appie59 , profesor0127 , dhrvoj , pravin , petarmoon , Tee325 , daniel_milano_ro , StageX Motorsport , Tpauto , Rampauto , gtturbo2540 , knightrider64 , BimmerGT1 , njdiagnostics , nagyiii , mariuszna , dgrifon777 , ben visconti , xerxes , gerryc89