Big thanks to shawnsheridan
Mar 20, 2017 BMW E-sys Coding Car List: BMW F series, the new 1 Series, 3 Series, 5 Series, 7 Series, GT, X3. BMW E-sys Coding Feature: Lock unlock sound confirmation ( to prevent radio interference, add sound to confirm car locked when turn light confirmation inconvenient. Sep 27, 2017 o nly E-SYS V3.2 3.4 is tested with bmw enet cable and bmw icom by professionals. Other versions are shared in the forums; just put it here for share and TRY AT YOUR OWN RISK. E-sys software 3.2 3.4 is the NEVER-EXPIRE version. Mar 28, 2014 Archive E-Sys Download Locations BMW Coding and Programming. Bimmerfest - BMW Forums The Best of Bimmerfest! BMW Coding. Is anyone else having this issue with the torrent downloads? I also downloaded about 10 from RapidShare. Same thing: half are corrupt.
E-Sys_Setup-3.32.1-52333_32bit.exe:
E-Sys_Setup-3.32.1-52333_64bit.exe:
BMW E-sys 3.32.1 Released Notes:
Current version:
PSdZ: 5.06.01
ProDiaS: 3.4.0
Jobs: 005_009_002
Template: PT01_template.003_000_228
EST_CM:1.5.0
KIS_AL:5.9.0
System requirement:
Processor: Intel Pentium 4 with minimum 1GHz clock rate
RAM: mindestens 512 MB
Hardware interface: (CAN/FD. Ethernet, …)
https://ghskyey.weebly.com/download-toyota-owner-manual.html. Java-Version (abgesichert mit): 1.8.0.121 64 bit
Operation system: Windows 7 (64 bit)
Driver for HW-Interface: for details please see information in ProDiaS Released notes
Info – Please note:
During the vehicle programming with E-sys, no further applications should be excuted in parallel on the flash processor. This includes, inparticular, background processes, such as the indexing service for desktop search or automatic deframentation services.
E-sys is currently not supported under Windows 10. workaround for display problems under Windows 10: E-sys.exe->Properties->Compatibility->”Override behavior at high DPI scaling”->Scaling performed by: “System”
Quality centre (processed items):
14269 – PDX-Charger – Removing of EE-Components from a Container
14271 – Coding Verification – Button ‘Verify All’ will not be activated when using FAs with a single entry
14293 – PDX-Charger – ‘Save As’ of a Container fails when using certain path names Https www.toyota.com 2011 prius owners manual.
14299 – PDX-Charger – missing SWEs after container import into PsdZ
14301 – Coding Verification – Function ‘Verify All’ can lead to an runtime error
Change requests and minor changes:
CR3304 – Certificate Management – Adaptations based on CR3135 AND 3178
KA3459 – Valid naming for RSU -specific ICs
CR3560 – E-sys – Conversion to 64 bit Java
Toyota crew cab 4x4 used. CR2359 – Certificate Management – unitary form for result files
CR3681 – E-sys – Adaptations resulting from modified TAL-Schema (IDR for ISTA)
BMW Esys Coding: Confirmed by obdii365.com
Note that functions are verified with TESTED E-SYS 3.23.4 with BMW ENET cable (Ethernet to OBD) Interface:
src: http://www.obdii365.com/wholesale/bmw-enet-interface-cable-e-sys-icom-coding-f-series.html
Who Viewed This Article Also Views:
(09/04/2017) Free download BMW E-sys software 3.30.0 (build 49694) for BMW ENET cable (Ethernet to OBD interface).
E-Sys Setup 3.30.0 (build 49694): not tested
https://mega.nz/#!l0JhHDQb!zwLgH90P0CxXdSN0DiX7sw6f3myexX5pv-_xXqkMpss ESys Launcher PRO 2.8.0 Build_153: not tested
NcdCafdTool v0.5.1: not tested
E-Sys Launcher Premium: not tested
E sys v3.23.4 + V50.3 data + TOKEN + PIN: tested OK!!
Credits to all sponsors esp. shawnsheridan
Observations: E sys 3.30.0 update info
1) Changed Settings => “EST” Tab to “Authentication” Tab and expanded the functionality:
2) Fixed KIS Database “Not available” problem (introduced in 61.5 PSdZData) when used with E-Sys 3.28.1 or 3.29.0:
E-sys 3.30.0 info you should know:
– E-Sys 3.29.0 and 3.30.0 have been released since after TokenMaster last disappeared, so don’t expect them, or any future version of E-Sys to work with E-Sys Launcher, until if and when TokenMaster returns and starts updating E-Sys Launcher again.
That said, E-Sys without E-Sys Launcher can be used for for Programming, VO Coding, and FDL Coding using Untrimmed CAFD. – Esys plus 2.8 show wrong coding lines with new pzdata , so be careful with it(but to avoid any confusion, this is an E-Sys Plus issue related to newer psdzdata and has nothing to do with subject of this thread, which is E-Sys 3.30.)
– Tokenmaster’s ESysLauncherPRO 2.8.0 Build_153 available now:
– Added support for E-Sys 3.29 – Added support for E-Sys 3.30
How to install E-sys 3.30.0 with Java 32 bit:
For flashing failure risks to minimize, you need as much JAVA memory as you can have.
E-sys 3.30.0 comes standard with Java 32 bit, maximizing usable memory to 2Gb (actually less, because runtime uses lots of Mb’s as well. Thx Tokenmaster). Default setting in E-sys 3.30.0 is 1024Mb. You can change it (in esys.bat; thx Shawn)to about 1500Mb. If you set too high, E-sys won’t start anymore. Just trial&error. If you want more usable memory to further reduce memory related flash failures, upgrade Java to 64bit:
1. Download/Install vcredist_x64.exe (see link)
2. Download/Install JRE 8 x64 (see link) 3. Delete JRE folder in c:EC-appsESGE-Sysjre 4. Rename just installed JRE 8 x64 folder(c:Program FilesJavajre1.8.0_144) to JRE and move to c:EC-appsESGE-sysjre. 5. Change memory setting in esys.bat: :startEsys :set OPTION_MEMORY=-Xmx3000m (or 2048 or 4000 or whatever) 6. Run E-sys and close E-sys 7. Open last LOG file in c:DataLogs 8. Search for : “Java (max)” Without quotes to check your present max usable memory 9. Use E-sys software with decreased flash failure risks Bmw E Sys Download
For me this was solution for NBT flash issues!
![]()
BMW ENET E-sys 3.30.0 review:
I tested it by psdzdata 3.62.1 for coding and programming ok.
But for FDL coding, because CAFD was trimmed,so refer to launcher+E-sys 2.8.1+psdzdata 3.61.4.002 for reference,for example “startup_emblem” countered the 32th from bottom of 3001,in the “Ausgelesen” of “Werte=00”,changed to “01”,so got the error:
“Failed to sign FDL[C158],EstCmCryptgraphicExcetion:SignHandler can not be initialized with data from EST.
For FDL Coding, E-Sys Launcher provides both an .EST Token Solution for signing Coding Changes, and CAFD Mapping to add back in and display the Trimmed Data.
You do not have .EST Token solution, so you have EST error. So, either a real BMW AG .EST Token file is needed or E-Sys must be patched to accept a non-OEM .EST Token file.
Beyond Token, you also need either Untrimmed PSdZData from BMW AG’s vault. Without Untrimmed PSdZData, you can resort to “counting” method as you did, or similarly using FDL Storage Info (Address and Bitmask), which spares you the counting, but both methods are tedious and make the assumption that Current CAFD versions FDL Code structure is same as previous version, an assumption that is not always true. Without Untrimmed PSdZData, FDL Coding is best left to older E-Sys 3.23.4 / 3.27.1 / 3.28.1 and E-Sys Launcher.
Bmw E SysWho Viewed This Article Also Views:Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |