All BMWs Psdzdata Technical questions

Hi,

I just learned about coding a few days ago, and i've been reading forums and instructions. I must have downloaded 30 PDFs. But there is nothing out that actually explains details...like what is the data exactly inside the psdzdata? How do you know which version of psdzdata you need? I have a 2013 328xi, which version works with it? Can I use older versions (47.5) instead of the latest (48.3)? What exactly is a PIN and Token?

Thanks for any help, apologies if this stuff has been covered, but I couldn't find answers to these questions anywhere.

Felix

if you are not an IT guy I will contact shawn or april1 it is very complicated set up for the average Joe.

Sent from my Nexus 7 using Bimmer App

I am in IT actually...I write code (software engineer). I would definitely like to hear the technical details, or read about them somewhere.

Originally Posted by Felixk

Hi,

I just learned about coding a few days ago, and i've been reading forums and instructions. I must have downloaded 30 PDFs. But there is nothing out that actually explains details...like what is the data exactly inside the psdzdata? How do you know which version of psdzdata you need? I have a 2013 328xi, which version works with it? Can I use older versions (47.5) instead of the latest (48.3)? What exactly is a PIN and Token?

Thanks for any help, apologies if this stuff has been covered, but I couldn't find answers to these questions anywhere.

Felix

Have you tried here: http://www.f30post.com/forums/showthread.php?t=696777
It's more specific to F30's.

psdzdata is a whole set of directories that contain files for every version of the firmware for every module of every applicable car. That's why it's about 16GB. You only need a small subset of that to code.

For coding, you need the CAFD files. They are encrypted on disk, but can be viewed in E-sys via the CAFD viewer. These define the parameter layout for each module.

You can't really tell what version is on your car until you connect it to E-Sys and read the I-step. That and Shawns table will tell you what version is currently on the car.

If you have an old version of psdzdata, then you won't be able to read the module when connected to the car as the corresponding CAFD file will be missing.

Once everything is setup and current, coding is simply changing parameter data, very similar to editing the registry in Windows. You are simply enabling, disabling, or changing a value of a previously defined variable that the firmware uses to control that specific function.

To code the car, the basic steps are to read the specific ECU field data (FDL). That reads in the current values for the module (Read Coding Data). Then you enable editing by selecting Edit FDL. You make you changes, and save them to the laptop disk. You then Code the updated FDL data into the ECU to store the changes on the car.

The step-by-step instructions show you how to do this in detail.

The token is a security feature; think of it as an encryption key. The PIN is what unlocks the key so that it can decrypt the CAFD files.

Thanks! That was a great explanation. Makes sense now.