BMW software versioning question

Pages: [1]

« previous next »

Author

Topic: BMW software versioning question (Read 876 times)

jtownson

Newbie

Karma: +7/-2
Offline

Offline

Posts: 13

	BMW software versioning question « on: June 21, 2024, 03:15:26 PM »

I wonder if anybody could help me understand a couple of things about BMW software versioning.

1. If you take an a2l version/epk (e.g. R1C2J8B3B), then there might be Bosch MG1CS003_B58_<VERSION>_x_DE_SWCalDoc.pdf but the BMW application export has a different, apparently unrelated name related to a program status (e.g. 209a_071_010_001). Is there a way to make the correspondence between a2ls and a matching BMW application export?

2. Calibration files have this additional id, e.g.
PRG (HEX): 3076501103
This looks like maybe a checksum of a specific calibration bin? Could anybody expand on or correct me please?

Thanks in advance.


	Logged

jtownson

Newbie

Karma: +7/-2
Offline

Offline

Posts: 13

	Re: BMW software versioning question « Reply #1 on: June 27, 2024, 08:40:57 AM »

To partially (and tentatively) answer my own question. The following scheme seems to apply:

VERSION=PREFIX + C2|C9 + VERSION1 + VERSION2 where

* Prefix denotes a specific engine as noted in the table below.
* C9 denotes a development build
* C2 denotes a release build
* VERSION 1 and 2 appear to be major/minor versions (although I was not able to confirm this).

Version prefix    Engine code    DME    App software
R0    Early BX8    MG1CS003    DME8.?
R1    B58    MG1CS003    DME8.6
R4    B58TU    MG1CS201    DME8.6T0
F4    S58    MG1CS049    DME8.6.S
H4    S63TU    MG1CS202    DME II

(See https://b58.wiki/wiki/Useful_resources_for_getting_started#BMW_software_versioning_side-note)


	Logged

Pages: [1]

« previous next »

Jump to:

Navigation

Personal Tools

September 28, 2024, 02:58:22 PM

Welcome, Guest. Please login or register.
Did you miss your activation email?

Navigation

Personal Tools

Search