![]() There are so many threads, different versions of all the programs and files, and a ton of what may be outdated information online that it is tough to really get a clear understanding of what to use and the steps to follow. (I was using 60.2 when I first attempted earlier this week) I swapped out my Psdz data file for 60.4. I did NOT change my E-Sys from version 3.28.1. I decided to start by making only a few minor updates to HU_NBT2 to make sure I was following the right process before I start making more extensive changes. I did this offline, opening the appropriate CAFD NCD file in E-Sys while not connected to the car. My F31 320d has the 2012 maps for Europe (I live in Western Europe ) and is equipped with the NBT Professional Navigation System.(Note that when offline, there doesn't seem to be a way to easily figure out which CAFD file is which, since they use cryptic CAFD ID numbers and do not have the logical names included). I take this opportunity to ask if you could send me the proper link for the 2016 road maps update. I have now customized my car thanks to you. I am sure that you, Shawn, know the reason for this.Īnyway thank you Shawn for pointing me in the right direction. Now I can access all modules and do all the coding. I uninstalled the LauncherPremiumSetup_2.5.3_Build_108, downgrade to the LauncherPremiumSetup_2.4.3_Build_85A version, and it worked perfectly. All the rest worked perfectly.Īs I had an older version of the E-Sys launcher on the CDs that came with the ENET cable, I decided to give it a try to see if this had to do with the launcher. ![]() The exact same thing happened on this two other computers: could not access the FEM_ BODY module as the same report showed up. "cafd_00000794_004_122_082" failed! ĬheckExpectedCodingDataLenght failed for coding data block 0x3085 :Īfter several reattempts I decided to install the software on two other computers (to try to conclude if it was a hardware problem or not): this time a Win 7 32 bits and a XP 32 bits. NCD read from ECU "ECUId:FEM_BODY_0x40" for CAF Transaktions-Report Aktion: Codierdaten lessen I would receive the following Report when I tried to read coding data over the CAFD file: I downloaded the linked software (ESysLauncherPremiumSetup_2.5.3_Build_108 + E-Sys_Setup-3.27.1_RC_b44813 + v.59.2_PSdZData_Lite), installed on my main laptop (Win 7 64 bit), and everything worked perfectly except that I could not access the FEM_BODY ecu. I would like to share the following in case it is useful for any other member: įound project F020_13_07_505 with incompatible psdz job version 4.8.2 ***8211 minimum required version is 5.0.5 please update PDX container to the latest template version and re-import! (Now me included ***8211 Houston I have a problem***8230. You must be one of the pillars of this forum as it seems that everybody addresses you. Will you please guide me into the right direction (hint and/or link)? Therefore I think I should try another installation with a different software source. ![]() ![]() So it seems it has nothing to do with the cable as the same warning shows up when I try to connect without the cable. It always recognizes the vehicle (VIN shows up). I have installed on another win 7 laptop (this time 32 bit) and the some problem occurs. I just bought the enet cable from China, via eBay, that came with the software disks (E-sys 3.27.1 + Launcher Premium V2.4.385 + PSdZDATA 50.3).Īfter the installation on a 64 bit win 7 laptop and connecting choosing TargetSelector F020 (not DIRECT) I always get this warning:įound project F020_13_07_505 with incompatible psdz job version 4.8.2 - minimum required version is 5.0.5 please update PDX container to the latest template version and re-import! (Now me included - Houston I have a problem…. Hi every BMW lucky owners around the globe. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |