KEMBAR78
E46 Cluster Coding Info | PDF | Computer Science | Computer Architecture
0% found this document useful (0 votes)
81 views3 pages

E46 Cluster Coding Info

BMW E46 cluster coding info

Uploaded by

Ranga Gamage
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
81 views3 pages

E46 Cluster Coding Info

BMW E46 cluster coding info

Uploaded by

Ranga Gamage
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

E46 Cluster coding info

This information is only confirmed on gasoline clusters as I'm from the US and diesels
aren't that popular here. This information is for M35080 and 080D0WQ EEPROMS. You
can reference here for modifications needed to make an R270 work perfectly.

Bosch M35080 when read with an R270 or PA SOFT breakdown:


0x316 HW
0x317 CI
0x318 DI
0x319-0x31B Date

Motometer M35080 when read with PA SOFT breakdown:


0xC8 CI
0xCB DI
0xBA - 0xBB Date
0xBC HW

Motometer M35080 when read with R270 breakdown:


0x288 CI
0x28B DI
0x27A-0x27B Date
0x27C HW

The information above is useful for programming M3 clusters to work in non-M cars, but
there are limitations. Bosch M3 clusters can be converted to non-M coding indexes and
you can code with NCSEXPERT just fine with the appropriate FA/ZCS loaded. The
same does not apply for Motometer M3 clusters. All Bosch clusters, whether M or
non-M, contain coding for DREHZAHL_KENNLINIE. On the other hand, only M3
Motometer clusters have that so when you code it with NCSEXPERT using a non-M CI,
the tachometer gets maxed out since its characteristics are no longer defined. In case
you do mess that up, the easiest way to restore the cluster is via an EEPROM backup
you made with PA SOFT.

I do not have mileage locations as I let the R270 handle that. You can change the VIN
with PA SOFT as long as the mileage is 0. You cannot set the mileage with PA SOFT on
EEPROMS that aren't 9S366. You can either use the R270 to set the mileage or set up
an LCM on your bench for the cluster to sync mileage off of. If you use an R270 to set
the mileage on a Motometer cluster, for some reason, the mileage on the cluster gets
doubled so only input half the mileage you actually want it to be in R270. Remember
that once the mileage is greater than 0, you cannot change the VIN so make sure
you've taken care of that first. You will use PA SOFT to change the VIN and mileage in
the LCM to be whatever you want to set the cluster to. You can reference below for the
bench setup pinout.

VIN is located at 7A-7E for Bosch clusters whether read with an R270 or PA SOFT. The
first two letters of the VIN are written as hex and need to converted from ASCII but the
numbers are left as hex. The last digit at 7E stays 0.
VIN is located at 200-203, skip 204 (should be 00), 205 for Motometer clusters when
read with an R270. The first two letters of the VIN are written as hex and need to
converted from ASCII but the numbers are left as hex. The last digit at 205 stays 0. If
read with PA SOFT, the VIN is located at 40-43, skip 44 (should be 00), 45.

To change the coding index from an M cluster to non-M, simply subtract 16. By doing
this, it lets NCSEXPERT write a non-M FA/ZCS to the cluster.

To clear the FA or ZCS from a cluster, use the ZCS_LOESCHEN job in NCSEXPERT.
From there, you'll have a cluster ready to accept either FA or ZCS. In my experience,
Bosch and Motometer clusters are able to accept either one once cleared. To write a
new FA or ZCS, simply read it from the ALSZ (if FA) or EWS (if ZCS) and use the
FA_WRITE or ZCS_SCHREIBEN job. Once done, you can then code a blank
FSW_PSW.MAN to have the cluster coded properly for your car. Keep in mind what was
noted earlier. You will mess up the cluster if you perform any coding on an M3
Motometer cluster that's had its CI changed to non-M.

Connecting the LCM and cluster on the bench

Cluster:
X11175 black plug
Pin 1 ground
Pin 4 constant +12v
Pin 5 switched ign +12v 2nd stage
Pin 25 k-line (goes to OBD cable)
Pin 14 k-bus (goes to the other modules)

LCM:
Pin 6 constant +12V
Pin 15 switched ign +12v 2nd stage
Pin 31 ground
Pin 21 k-bus
GM5:
X253 (middle connector)
Pin 27 constant +12V
Pin 47 switched ign +12v 2nd stage
Pin 10 ground
Pin 9 k-bus

==============================================================
I have been using an R270 with these modifications for over a year now with 100%
success rate.
I have done M35080, M350803, M350806, 080D0WQ, 160D0WT, and whatever CAS3
uses. 080D0WQ takes a minute or so to decode but it works. It does take quite a few
tries for the R270 to be able to detect it though. When doing a CAS module, you need to
use a hot air gun and keep it blowing on the processor. I have not had luck erasing
M35080V6. The replacement, upgraded board may be able to do it.

Replace AH08 with genuine TI SN74AHC08DR (AH08) on main board.


Remove yellow capacitor on C1 on the adapter board.
Use a high quality 12V power supply
Replace 74HC125 with genuine TI CD74HCT125M96E4 on the adapter board.
Replace the capacitor on the main board with a high quality 10V 1000uf capacitor
Replace R11 on adapter board with 10k resistor.

Finally, when using the software, always select "No" during the "check pin state" popup.

Hopefully you find this information useful. I have also attached a working version of the
software.
https://mega.nz/file/8tFmxYTa#4Tdtavf61T...aBQnLHY0aQ

You might also like