Launcher PRO 3.6.0

Launcher PRO 3.6.0 Build 288 is now available.

Change Log
====================

3.6.0 Build 288
- Added: Support for 3.34 64bit Only
- Improved PSdZ Handling and Translation
- Minor bug fixes

*Requires Google Authenticator mobile app. Download from Apple App Store or Google Play Store

Note: Please see https://www.fxxtokenmaster.com and blog before upgrading to 3.1+. Launcher PRO now uses Time-based One-time Password for authentication. 

Google Authenticator is required when using dynamic activation and when updating the Launcher.

V3.34 is really interesting, but appears to be an indication of how things are, going forward. The easier way to deal with it would have been to provide an alternate REST API for signing and encrypting NCD, but I don't believe in encrypting user's data.  It's my NCD, I'd like to not be locked out of it, so I chose the harder way. NCD files remain not encrypted. Properly signed, but not encrypted.

It appears to be well-coded and stable. I like this version a lot.


**Don't use the comment section to ask where to get it and stop posting your email addresses

Launcher PRO 3.4.2

Launcher PRO 3.4.2 Build 216 is now available.

Change Log
====================

- Improved CAFD processing and mapping, 200-300% gain typical

- Suppressed dialog G271

- Minor UI change - unified Launch and Abort button

- Fixed: Application launch failure on some system

- Minor bug fixes

-Fixed: Loading VO causes crash

I made a lot of changes for this build, I contemplated on labeling it 3.5. I made some major improvements on CAFD processing and mapping. On my 5th Gen Core i5, using 3.33.4 x64, fully processing HU NBT CAFD takes about 5 seconds, and BDC CAFD shows in under 8 seconds. This is a huge improvement over previous versions where it takes about 20+ seconds to process HU NBT.

I'd be doing further changes in the coming days.

I suppressed the G271 dialog as it's getting too annoying. I don't think anyone cares about what it says anyway.

I also made improvements on the web side. There was an incident where nobody can login, even myself. It was because the server time was  way off. I had to do an emergency deployment and query Internet time to rectify the issue, so the web application doesn't rely on server time anymore.

I recommend everyone to upgrade to this build.

Launcher PRO 3.4.0

Launcher PRO 3.4.0 Build 191 is now available.

Change Log
====================

3.4.0 Build 191

- Added: Support for 3.33.4 64bit Only

- Updated: CAFD Mapping compatibility level: 18-04 i-Step

- Removed: Required root certificate

- Minor bug fixes

NOTE: Authenticode RSA certificate is no longer required, but installing RSA Certificate with "EB06BA22 6FB31CD3 787A2ABB 84E71D61 F1CEA5B9" thumbprint to the Trusted Root Certification Authorities store on current user is still recommended. This certificate can only be used for Authenticode purposes and cannot be used to create intermediate or subordinate, or end entities certificates.

  To Install Certificate:

via Command prompt: LauncherPro3.exe installcert

via Windows: Right-click LauncherPro3.exe > Properties > Digital Signatures > Details > View Certificate > Install Certificate and install it under Trusted Root Certification Authorities store

  To Delete Certificate:

via Command prompt: LauncherPro3.exe removecert

or use mmc.exe and Certificate Snap-in. See https://tokenmaster.blogspot.com/2019/05/code-signing-certificate.html

*Requires Google Authenticator mobile app. Download from Apple App Store or Google Play Store

Note: Please see https://www.fxxtokenmaster.com and blog before upgrading to 3.1+. Launcher PRO now uses Time-based One-time Password for authentication. 

Google Authenticator is required when using dynamic activation and when updating the Launcher.

NOTE: For WIndows 7 users, if you're having problems with validation/activation, Windows is probably not using TLS 1.2 to communicate to my site. Check the following registry key, as shown in the image:

First thing to do is ensure all updates are installed. If you don't see TLS 1.2 key, create it, then create the Client key under it. The two DWORD values must exist and should contain data as shown in the image. Restart WIndows and try again

Launcher PRO 3.2.0

Launcher PRO 3.2.0 Build 144 is now available.

Change Log
====================
3.2.0 Build 144
- Added: Support for 3.33.0 32 and 64bit
- Added: Support for 3.32.2 32 and 64bit
- Updated: CAFD Mapping using 17-11 iStep as base for greatest compatibility with the newest PSdZdata
- Minor bug fixes

*Requires Google Authenticator mobile app. Download from Apple App Store or Google Play Store


Looks like 32bit is going away real soon. 3.33 gives you warning when using the 32-bit version.  This version still supports both 32 and 64bit.



NOTE: Please Do NOT use the comment section to request software. 

Update: TokenMaster's Launcher PRO 2.9.3

UPDATE: Launcher PRO V2.9.3 is now available

- Fixed minor certificate/EST issue

Thanks to botho for providing the environment for troubleshooting. It was a tremendous help.

UPDATE: Launcher PRO V2.9.2 is now available

- Fixed minor certificate/EST issue

TokenMaster's Launcher PRO V2.9.0 is now available.

Change log

Launcher PRO V2.9.0 Build 173
====================

- Increased allowed memory allocation for 64-bit JRE up to 8GB.

- Added another way of using 64-bit JRE by using "jre_x64" for folder name. This way, 32-bit JRE can remain untouched.

- Main window will become 65% transparent if a child window is open. This enhances the contrast and visibility of child windows. (See image below)

- Minor UI tweaks

- Minor security changes

- Removed support for 3.24 and 3.26. Minimum supported version is 3.27

Figure 1: Semi-Transparent main window

Majority of the work done on this version is not visible. Initial support (not available yet) for online activation has been laid out and will be enhanced further in future releases. These changes will trickle down to Premium as well.

I encourage anyone who's using PRO to upgrade to this version. This version is a little bit more stable and secure.

NOTE: Please do NOT request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

Update: TokenMaster's Launcher PRO 2.8.1 and NCD / CAFD Tool V0.5.2

TokenMaster's Launcher PRO V2.8.1 is now available.

Change log

Launcher PRO V2.8.1 Build 155
====================
- Added support for E-Sys 3.30.1

NOTE 1: While it support 3.29, I find 3.29 is too buggy for any useful purposes. I tried fixing some of the stuff, but I gave up and retracted my changes. There's just too many to fix. 3.30 appears to be stable but I just started using it a couple of days ago, I haven't had the chance to fully test it.

If you are not planning on using 3.30 or 3.30.1, there's no reason to update to this version. 

NOTE 2: I'm holding off on the Premium update for now as I'm contemplating a few changes. As much as I would like to release it, people just won't stop trying to exploit it for their own advantage.

I'm not always around to generate activation code, so I need to device something more autonomous. I just came back and I have zero idea at the moment.

NCD / CAFD Too V0.5.2 Build 203

====================

- Minor bug fixes

NOTE: Please do NOT request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

Update: TokenMaster's Launcher PRO 2.8.0 and NCD / CAFD Tool V0.5.1

TokenMaster's Launcher PRO V2.8.0 is now available.

Change log

Launcher PRO V2.8.0 Build 153
====================
- Added support for E-Sys 3.29
- Added support for E-Sys 3.30

NOTE 1: While it support 3.29, I find 3.29 is too buggy for any useful purposes. I tried fixing some of the stuff, but I gave up and retracted my changes. There's just too many to fix. 3.30 appears to be stable but I just started using it a couple of days ago, I haven't had the chance to fully test it.

If you are not planning on using 3.30, there's no reason to update to this version. 

NOTE 2: I'm holding off on the Premium update for now as I'm contemplating a few changes. As much as I would like to release it, people just won't stop trying to exploit it for their own advantage.

I'm not always around to generate activation code, so I need to device something more autonomous. I just came back and I have zero idea at the moment.

NCD / CAFD Too V0.5.1 Build 201

====================

- Minor bug fixes

NOTE: Please do NOT request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

Update: Launcher Premium 2.7.0 and NCD / CAFD Tool V0.5.0

Launcher 2.7.0 Premium and NCD / CAFD Tool 0.5.0 Alpha

Change Log:

Launcher Premium 2.7.0 Build 132
- Added configurable Cheat Codes selection
- "Code Default Values" button renamed to "DO NOT USE!!!" ("VERWENDEN SIE KEINE!!!")
- Windows XP is supported again
- Minor bug fix



Cheat Code selection on Startup.

This feature should have been included in the first release. I've discuss this a long time ago here: Code Default Values

NCD / CAFD Tool 0.5.0 Build 198 Alpha
- Minor bug fix


NOTE: Please do not request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

Launcher V2.6.1 PRO and Premium, NCD / CAFD Tool V0.4.0 Update - Updated 11/08/2016

TokenMaster's Launcher 2.6.0 Premium and PRO are now Out.

[Updated: 11/08/2016]
Launcher V2.6.1 Pro and Premium Builds 130 and 122, respectively, are now out. These updates addresses the initial issues found with the previous releases.

Launcher PRO 2.6.0 Build 128
- Added support for E-Sys 3.28.x
- PsdZdata mapping compatibility upgraded to V3.59.4
- Added color indicator to FDL Cheat Codes (Blue = OK, Orange = partially applied, Red = failure)
- Added FDL Cheat Codes online update
- CAF Viewer is forced to use \Data\psdzdata\swe\cafd folder instead of \Data\CAF
- Changed .NET Framework requirement to V4.5.2
- Launcher is now completely hands-off in coding/flashing modules

- Updated Cheat codes

Launcher Premium 2.6.0 Build 119
- Added support for E-Sys 3.28.x
- Added CAFD Transalation for the following G-Series: G001, G002, G011, G012, G013, G030, G031, G032
- Fixed High DPI/Screen Resolution support for JRE7, JRE8 (E-Sys 3.26, 3.27, 3.28) - Enjoy crisp resolution without down scaling your display
- Fixed issue with HKFM_LS. Older PSdZ library and other ECUs do not need to expand CAF, but HKFM_LS does, and is sensitive to delay. Launcher is now modified to only perform translation when requested from the GUI
- Added color indicator to FDL Cheat Codes (Blue = OK, Orange = partially applied, Red = failure)
- CAF Viewer is forced to use \Data\psdzdata\swe\cafd folder instead of \Data\CAF
- Changed .NET Framework requirement to V4.5.2
- Launcher is now completely hands-off in coding/flashing modules

- Updated Cheat codes

A few notes on these features:

.NET Framework 4.5.2 is now required due to new features added. It can be downladed from this link: https://www.microsoft.com/en-us/download/details.aspx?id=42642

For Premium only. You will be asked to generate a token. I have changed the way token is generated for V2.6.

- CAF Viewer is forced to use \Data\psdzdata\swe\cafd folder instead of \Data\CAF - I find it annoying that the CAF Viewer defaults to \data\CAF. This is one of the more frequently asked questions I get. CAF viewer opens CAF files, FDL-Editor opens NCD files. They don't mix. CAF Viewer now defaults to \Data\psdzdata\swe\cafd, when Launchers are used.

- Added color indicator to FDL Cheat Codes (Blue = OK, Orange = partially applied, Red = failure) - The following picture is self-explanatory.

When previewing or applying changes, the selected item(s) will change color as a visual aide and indicates the status of the code. Blue means accepted, Orange means partially (for multiple code location), and Red means the value is outside the acceptable range.

- Added FDL Cheat Codes online update - FDL Cheat Codes can be updated if it's updated by the author and uploaded to Github repository.

NCD / CAFD Tool V0.4.0 is also now available. PsdZdata mapping compatibility upgraded to V3.59.4  

NOTE: Please do not request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

Update: Work-in-Progress - Launcher PRO and Premium 2.6

My first blog post after I came back was rather nasty, so I thought I'd post something more like the usual stuff.

I just finished setting up my coding PC after it crashed. I guess it didn't like being idle for so long. Anyway, here's what I'm working at:

Launcher PRO and Premium V2.6.0
- Supports E-Sys 3.28.x
- PSdZData Mapping compatibility: V3.59.4

Premium necessitates generating new token. You'll be asked to provide a PIN and old tokens will no longer work.

Also working on NCD/CAFD Tool with mapping compatibility updated to PSdZData V3.59.4

I hope to get it done in the next 7 days or so. Stay tuned.

E-Sys Launcher PRO 2.5.5

E-Sys Launcher PRO 2.5.5 Build 120


E-Sys Launcher PRO 2.5.5 is now out.

- Added CAFD Translation for the following G-Series: G001, G002, G011, G012, G013, G030, G031, G032
- Fixed High DPI/Screen Resolution support for JRE7 (E-Sys 3.26, 3.27) - Enjoy crisp resolution without down scaling your Ultra HD display
- Fixed issue with HKFM_LS. Older PSdZ library and other ECUs do not need to expand CAF, but HKFM_LS does, and is sensitive to delay. Launcher is now modified to only perform translation when requested from the GUI


Due to the last item, I had to release PRO first. Premium will follow soon with the same features and fixes.

NOTE: Please do not request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

E-Sys Launcher 2.5.3 Premium and 2.5.4 PRO

E-Sys Launcher 2.5.3 Premium and 2.5.4 PRO are now Out.

Launcher PRO 2.5.4 Build 115
- Added support for extended characters in CAFD mapping
- Added support for extended characters in FDL Cheat Codes
- Added support for multiple FDL Cheat Code files
- Added configurable Cheat Codes selection
- Enhanced Search capability in FDL-Editor and CAFD Viewer: Option to search from the top

Launcher Premium 2.5.3 Build 108
- Added support for extended characters in CAFD mapping
- Added support for extended characters in FDL Cheat Codes
- Added support for multiple FDL Cheat Code files
- Enhanced Search capability in FDL-Editor and CAFD Viewer: Option to search from the top

PRO Only. FDL Cheat Codes are now selectable.

NOTE: Please do not request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

Running E-Sys and Java 64-bit

NOTE: The following section is experimental and not recommended for general use. Use at your own risks.

Update: E-Sys 3.24 has also been tested with JRE x64

E-Sys comes with its own 32bit Java Runtime Environment (JRE) and since it’s 32bit, maximum memory that can be allocated is 2GB. The runtime uses about 200MB, leaving about 1.8GB usable memory for the application. This free memory must be contiguous, however, before it can be use by JVM. So, just because you have 16GB of RAM, doesn’t mean you can allocate full 1.8GB to E-Sys. This is also the reason why sometimes, it works with 1GB+, other times, you can only allocate 512MB.

Enter JRE 64bit. JRE x64 appears to not have the limitation of JRE 32bit in that I can consistently allocate 4GB of RAM every single time. I only tested with E-Sys 3.27 since I can only find JRE 7 x64. E-Sys 3.24 needs JRE 6. Here are the steps:

1)  Download and install vcredist_x64.exe from this link: https://www.microsoft.com/en-us/download/details.aspx?id=40784
2)  For E-Sys 3.26 and newer Only: Download and install JRE 7 x64 from here: https://mega.nz/#!DN813aCD!B5bLE8yC2RuGRGUfI-yioO8FG5qZUIu5QHunyKEPjFw or from Oracle if you have an account
3) For E-Sys 3.24 Only: Download and install JRE 6 x64 from here: https://mega.nz/#!3YcjVShK!Zq3QH-2_WSCdpRRvNa7Ocikbyp44_bM0aWNtxZOatNs or from Oracle if you have an account 
4) Delete or relocate the content of  the JRE folder under E-Sys (C:\EC-Apps\ESG\E-Sys\jre)
5) Copy the contents of the JRE you installed into E-Sys JRE (from C:\Program Files\Java\jre6 or C:\Program Files\Java\jre7 to C:\EC-Apps\ESG\E-Sys\jre)
6)  Run E-Sys Launcher and configure memory as you see fit.

I can run E-Sys consistently using 3.5 and 4GB RAM allocated to it.

How to check how much memory is allocated to E-Sys.
1)  Open the current log file (usually in C:\Data\Logs)
2)  Search for "javamem".
You should see something like the following:
Java (used/javamem): 17,016,928 # Java (full): 127,795,200 # Java (max): 4,260,102,144 # Process (full/procmem): 486,379,520 # Process (virtual): 5,224,296,448 # Process (virtual max): 140,737,488,224,256


The number in bold (4,260,102,144) is the maximum memory JVM can use, in this case, just a tad bit lower than 4GB.

E-Sys Launcher 2.5.0 Premium and PRO

E-Sys Launcher 2.5.0 Premium and PRO

E-Sys Launcher V2.5.0 - PRO and Premium are now available


Change Log:

Launcher PRO 2.5.0 Build 103
- Fixed TAL-Editor error on E-Sys 3.24.x
- Enhanced Cheat codes

• Added Series option at the CAFD or code level
• Added Author attribute which can be used as a filter
• Added comment attribute at the function level.

- Enhanced PSdZData mapping algorithm
- PSdZData mapping compatibility is now at V56.5. Some CAFDs are at V57.0
- JRE x64 support. It's now possible to use > 1.8GB RAM. I tested 3.27 and is stable at 4GB. See E-Sys Launcher.pdf for instructions on using 64bit JRE


Launcher Premium 2.5.0 Build 97
- Fixed "High Resolution Fix" option
- Fixed TAL-Editor error on E-Sys 3.24.x
- Enhanced Cheat codes

• Added Series option at the CAFD or code level
• Added Author attribute which can be used as a filter
• Added comment attribute at the function level.

- Enhanced PSdZData mapping algorithm
- PSdZData mapping compatibility is now at V56.5. Some CAFDs are at V57.0

NOTE: Please do not request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

E-Sys Launcher 2.4.3 PRO and Premium and E-Sys 3.27.1 Update

E-Sys Launcher V2.4.3 - PRO and Premium is now available


Change Log:


Launcher PRO 2.4.3 Build 98, Launcher Premium 2.4.3 Build 85
- Fixed issue with failure to load with some system when querying available memory due to corrupted .NET Performance Counter Registry
- "High Resolution Fix" is now always enabled
- Massive addition to Cheat codes, courtesy of dmnc02, Otakar and ruben_17non - Thanks fellas!
- Fixed minor UI issue - Review button tooltip (reported by myfxp)





E-Sys 3.27.1 Notes

I've been using E-Sys 3.27.1 a lot recently and I noticed that it crashes a lot due to a myriad of issues. Something as simple as having the MSM Updated turned on could crash E-Sys. The good news is that MSM update is the last process in coding, so the crash does not pose big problem when coding. It's just so annoying.

Memory, or the lack thereof, could also crash E-Sys. So, when running on default memory settings and trying to code complex ECUs, like NBT, could crash it.

I've never seen this happen to previous versions of E-Sys. It was pretty good at handling exceptions, but 3.27.1 seems different.

Bonus Tip
If you are forced to run E-Sys using default memory settings (512MB), you can help it by moving some PSdZData folders you never use. Some folders you can safely move, so long as you don't own a series which uses them are the series folders inside kiswb. I have F30 so I moved the following folder:
   C:\Data\psdzdata\kiswb\S15A (used by G-Series)
   C:\Data\psdzdata\kiswb\K001 and C:\Data\psdzdata\kiswb\KE01 (used by BMW motorcycle?)
   C:\Data\psdzdata\kiswb\RR01 (used by Rolls Royce)
   C:\Data\psdzdata\kiswb\I001 (used by i-3, i-8)
   C:\Data\psdzdata\kiswb\F056 (used by Mini)

Moving the above folders prevent E-Sys from reading database associated with these series. These databases are read on startup and kept in memory while E-Sys is running, using precious memory.

If you have plenty of RAM and can run at least using the medium settings, then moving the above folders are not required. Again, only do this if you are forced to run using default memory settings.  

E-Sys Launcher V2.4.2 - PRO and Premium

E-Sys Launcher V2.4.2 - PRO and Premium is now available

Launcher PRO
====================
2.4.2 Build 95
- Fixed multi-group parsing of FDLCodes.xml
- Added Cheat Codes Review


Launcher Premium
====================
2.4.2 Build 82
- Fixed multi-group parsing of FDLCodes.xml
- Added Cheat Codes Review


Parsing of FDLCodes.xml as intended is now working properly. I also added a Cheat Codes Review to preview the changes before codes are applied to FDL.

As usual, no request from this page, please.

E-Sys Launcher V2.4.0

UPDATE: V2.4.1 is now out.

2.4.1 Build 93
- Fixed E-Sys 3.26.x compatibility
- Minor Bug fixes

I highly recommend everyone to upgrade to this version.



E-Sys Launcher V2.4.0 is now out!

Launcher PRO
====================
2.4.0 Build 90
- Removed CAFD Remapping Option on the UI. As before, untrimmed CAFD will not undergo further processing.
- Added High Resolution fix for displays with width greater than 1600 pixels.
- Added "Storage Info" filter to CAF Viewer and FDL Editor (removed by ESG since E-Sys 3.26.x)
- Added Integrated Cheat Codes. Selectable, ready-to-use, cheat codes

Launcher Premium
====================
2.4.0 Build 78
- Added High Resolution fix for displays with width greater than 1600 pixels.
- Added "Storage Info" filter to CAF Viewer and FDL Editor (removed by ESG since E-Sys 3.26.x)
- Added Integrated Cheat Codes. Selectable, ready-to-use, cheat codes

Here's a small video I made using PRO.

 

NOTE: Please do not request download link by commenting. I will not reply to anyone asking me to send the software to them. Thanks for understanding.

E-Sys Launcher V2.3.0 PRO and Premium are out

E-Sys Launcher V2.3.0 PRO and Premium are out

Change Log

Launcher PRO 2.3.0 Build 85
- Added Dynamic Stack Memory Allocation from 512MB to maximum of 2048MB. This is separate from Heap Memory, which is more important to E-Sys
- Changed PSdZData handling. It is now offloaded to a native and managed code tandem providing faster data translation. Typically, 200% faster
- Changed processing of XML data to a more efficient library specifically designed for large XML
- Minimized memory used by smart cache by as much as 90%, giving E-Sys more usable memory


Launcher Premium 2.3.0 Build 75
- Added Smart, Safe caching - Subsequent reading of CAFD/FAFP will be significantly faster
- Added Dynamic Stack Memory Allocation from 512MB to maximum of 2048MB. This is separate from Heap Memory, which is more important to E-Sys
- Changed PSdZData handling. It is now offloaded to a native and managed code tandem providing faster data translation. Typically, 200% faster
- Changed processing of XML data to a more efficient library specifically designed for large XML
- Minimized memory used by smart cache by as much as 90%, giving E-Sys more usable memory


The dynamic Stack Memory allocation is based on available memory at the time of launching E-Sys. Free memory is queried and the maximum allowed value will be sent to E-Sys. This setting is separate from the ones configurable via the main Launcher UI. That handles the Heap memory which is more important to E-Sys (or any Java app, for that matter). How do you know it works? Look at your log files and find "javamem". You should see something like:

Java (used/javamem): 14,295,120 # Java (full): 24,379,392 # Java (max): 1,341,891,328 # Process (full/procmem): 205,340,672 # Process (virtual): 1,491,914,752 # Process (virtual max): 2,147,352,576

The first highlighted value is the Heap and achieved by setting it in the UI. The second highlighted value is determined dynamically and is assigned because I have about 2GB of RAM on this machine.

Note that Heap memory could fail and when it does, you'll see the following error:

The solution is either to restart your PC or select a lower memory settings. Stack memory is more forgiving as it is dynamically managed by the OS.


NOTE: Please do not request download link by commenting. I will not reply to anyone asking me to send the software to them. Thanks for understanding.

E-Sys Launcher V2.2.2 PRO and Premium are out

E-Sys Launcher V2.2.2 PRO and Premium are out.

Change Log:

E-Sys Launcher Premium 2.2.2 Build 72
- Added support for E-Sys 3.27.1





E-Sys Launcher PRO 2.2.2 Build 80
- Added support for E-Sys 3.27.1
- Added 2 missing functions in FEM found by valley_nomad

Tested on Windows 7, 8.1, and 10, both 32 and 64 bit versions


If you are interested in E-Sys Launcher PRO 2.x, email me at fxxtokenmaster_at_GMail

NOTE: Please do not request download link by commenting. I will not reply to anyone asking me to send the software to them. Thanks for understanding.

E-Sys Launcher Premium V2.2.0 Build 68

E-Sys Launcher Premium V2.2.0 Build 68 is out.

Chaange log:
- Added support for E-Sys 3.27
- Added support for FLE in PSdZData
- Added 2 missing functions in FEM found by valley_nomad

Last item is what I envisioned mapping is going to be, when I created CAFD Remapping. A community effort. Because let's face it, if we don't get untrimmed CAFD/FAFP, any new or moved functions, like the case of ASP_AUSKLAPPEN_NACH_KOMFORTSCHLIESSEN, will go unnoticed. But, if the community starts testing these new functions and determine what they do, then we'll have a fighting chance. I named these new/moved functions (PfExternalMirrorMaster_1_1_1, PfExternalMirrorMaster_8_8_1, ...etc.) as I know they mean something, I just don't know what they are. So, thank you, valley_nomad, for testing these (previously) unknown functions.

You can find the new build in the usual place. And lastly, please do not request for download link here. Enjoy!