PSdZData Full vs Lite: Which One Do You Need?
Lite is Full without the flash files. What each one can do in E-Sys, which version your car needs, and why update packs can't just be copied over.
PSdZData is the data E-Sys works from. It holds the coding files for every module, the software for flashing them, and the rules for which software belongs in which car. It comes in two packages, Full and Lite, and the difference between them is simple.
Credits 
This comes from the F30post threads PSdZData Full vs. Lite, started by benoa in 2013, and Coding cable and ESYS, psdzdata. The answers are from steve@codemybimmer and shawnsheridan. Thanks to both.
The Difference
Lite is Full with the SWFL files taken out. Those are the module firmware files, and only flashing uses them. Everything coding needs is in both packages.
That makes Lite much smaller. When shawnsheridan explained it in 2013, Lite was about a quarter of the size of Full, 7 GB against 30 GB at the time.
| Job in E-Sys | Lite | Full |
|---|---|---|
| FDL coding (changing single values) | Yes | Yes |
| VO coding (adding or removing an option in the FA) | Yes | Yes |
| Injecting a CAFD with Detect CAF for SWE | Yes | Yes |
| Flashing a module or updating the iStep | No | Yes |
| Fitting a used module from another car | No | Yes |
The last row catches people out. A used module still carries the other car's VIN, and writing yours into it takes a flash.
So if you're only coding, Lite is all you need. As shawnsheridan put it, downloading the full package when you only need Lite just wastes bandwidth. If you plan to follow our E-Sys flashing guide or an NBT EVO iStep update, get Full.
Which Version?
At least as new as the car. shawnsheridan's rule is that your PSdZData has to be the same as or newer than the last software the car was programmed with. If the dealer has updated the car since your PSdZData came out, E-Sys can't find the module's coding files and you get CAFD not found. The latest version always works, so that's the easy choice.
A matching E-Sys. Newer PSdZData needs a newer E-Sys. shawnsheridan's note: injecting a CAFD or flashing with PSdZData 4.17.20 or newer needs E-Sys 3.30.0 or higher. If E-Sys refuses your data, update E-Sys first.
In the right place. It goes in C:\data\psdzdata. A copy on the desktop does nothing, because E-Sys keeps reading whatever its options point to.
Updating It
Smaller update packs come out between full releases. You can't always copy one over your existing folder. shawnsheridan's explanation:
- If the pack only has mapping, security, cafd or swe files, you can copy them in.
- If it has extLibs, kiswb or mainseries files, which is usually the case, the old versions have to be deleted first. Old and new can't sit side by side without conflicts.
The safe way is to replace the whole psdzdata folder with a complete newer set.
FAQ
Can I start with Lite and switch later?
Yes. Nothing you code with Lite has to be redone when you move to Full.
Why does my antivirus complain about it?
PSdZData runs to tens of thousands of files, and some tool files get flagged by mistake. Our coding laptop guide covers that.
The attached one-page PDF has the table and the update rules. Need help setting it up? I can do it remotely.
Files
- PSdZData-Full-vs-Lite.pdf