[blax123]

I changed my Speedometer Gauge Face from my 335i (max 280 kmh) to an M3 one with 330kmh

Read out an M3 with tool32 0x3100
That's the buffer:
E1 2C 03 00 00 4E 00 88 04 63 09 1C 0C 00 00 64 00 B0 04 C4 09 48 0D 00 00 B1 00 55 08 5A 0E 84 12

How can I adjust my 335i Kombi for the 330kmh Speedometer now?

[Sensible_]

Originally Posted by blax123

I changed my Speedometer Gauge Face from my 335i (max 280 kmh) to an M3 one with 330kmh

Read out an M3 with tool32 0x3100
That's the buffer:
E1 2C 03 00 00 4E 00 88 04 63 09 1C 0C 00 00 64 00 B0 04 C4 09 48 0D 00 00 B1 00 55 08 5A 0E 84 12

How can I adjust my 335i Kombi for the 330kmh Speedometer now?

Maybe it's late where I am but can you take a photo of the change you have made. Struggling to picture it to be honest :

[blax123]

The right one is my original 335i one 280kmh, left the new one "m3 Style" with 330kmh
I need to adjust my Speedometer but don't know how to. There are some people using Bimmer Tools but there must be a way to do it with Tool32

[Sensible_]

Originally Posted by blax123

The right one is my original 335i one 280kmh, left the new one "m3 Style" with 330kmh
I need to adjust my Speedometer but don't know how to. There are some people using Bimmer Tools but there must be a way to do it with Tool32

[img]https://abload.de/img/img-20170708-wa0029spsd7.jpg[/img]

Ah, you are simply changing the speedo calibrationZ You can do this with NETTODAT coding. It's pretty simple.

When I get some time I'll make you an example.

[blax123]

Originally Posted by Sensible_

Ah, you are simply changing the speedo calibrationZ You can do this with NETTODAT coding. It's pretty simple.

When I get some time I'll make you an example.

Would be very
Thanks a lot

[Sensible_]

Originally Posted by blax123

Would be very
Thanks a lot

Ok, can you readout the address 0x3100 with tool32 on your 280kmh cluster?

It's choose the komb87.prg file and job codierdaten_lesen

In arguments field just put 0x3100

[blax123]

Originally Posted by Sensible_

Ok, can you readout the address 0x3100 with tool32 on your 280kmh cluster?

It's choose the komb87.prg file and job codierdaten_lesen

In arguments field just put 0x3100

335i 280kmh:

CODIERDATENBLOCK                = 33 Bytes
    0000 : 52 2B 03 00 00 4E 00 D7   01 88 04 83 0A 00 00 64  R+...N.×  .?.?...d
    0010 : 00 F4 01 B0 04 F0 0A 00   00 A5 00 39 03 BC 07 0E  .ô.°.ð..  .¥.9.¼..
    0020 : 12                                                 .
  _TEL_ANTWORT                    = 40 Bytes
    0000 : A4 F1 60 62 31 00 52 2B   03 00 00 4E 00 D7 01 88  ¤ñ`b1.R+  ...N.×.?
    0010 : 04 83 0A 00 00 64 00 F4   01 B0 04 F0 0A 00 00 A5  .?...d.ô  .°.ð...¥
    0020 : 00 39 03 BC 07 0E 12 12                            .9.¼....

M3 330kmh:

  CODIERDATENBLOCK                = 33 Bytes
    0000 : E1 2C 03 00 00 4E 00 88   04 63 09 1C 0C 00 00 64  á,...N.?  .c.....d
    0010 : 00 B0 04 C4 09 48 0D 00   00 B1 00 55 08 5A 0E 84  .°.Ä.H..  .±.U.Z.?
    0020 : 12                                                 .
  _TEL_ANTWORT                    = 40 Bytes
    0000 : A4 F1 60 62 31 00 E1 2C   03 00 00 4E 00 88 04 63  ¤ñ`b1.á,  ...N.?.c
    0010 : 09 1C 0C 00 00 64 00 B0   04 C4 09 48 0D 00 00 B1  .....d.°  .Ä.H...±
    0020 : 00 55 08 5A 0E 84 12 4C                            .U.Z.?.L

[Sensible_]

Ok, so from the information you have provided...

330kmh
CODIERDATENBLOCK = 33 Bytes
0000 : E1 2C 03 00 00 4E ‪00 88 04 63 09‬ 1C 0C 00 00 64
0010 : 00 B0 04 C4 09 48 0D 00 00 B1 00 55 08 5A 0E 84
0020 : 12

280kmh
CODIERDATENBLOCK = 33 Bytes
0000 : 52 2B 03 00 00 4E 00 D7 ‪01 88 04 ‬
‪83‬ 0A 00 00 64
0010 : 00 F4 01 B0 04 F0 0A 00 00 A5 00
39 03 BC 07 0E
0020 : 12

0x00 = Checksum (FF this - NCSEXPERT will fix it for us!)
0x01 = Start position of needle - 2B in your case.
0x02 = Attenuation of needle 03

Next are the ranges and sectors:

X Range: (Used when BC_V_KORREKTUR is coded: aktiv)

(Hex)
0000, 4E00, D701, 8804, 830A

(Decimal Values)
0, 78, 471, 1160, 2691

Y Range:

(Hex)
0000, 6400, F401, B004, F00A

(Dec)
0, 100, 500, 1200, 2800

Sectors:

0000, A500, 3903, BC07, 0E12

So to code this we create a NETTODAT.MAN

B ‪00310000,0010‬,FF,2B,03,00,00,4E,00,D7,‪01,88,04,83‬,0A,00,00,64
B ‪00310010,0010‬,00,F4,01,B0,04,F0,0A,00,00,A5,00,39,03,BC,07,0E
B ‪00310020,00‬01,12

(Above is basically your current coding so is a backup)

So, in the same way as explained above, To convert to your M3 330kmh scale:

B ‪00310000,0010‬,FF,2B,03,00,00,4E,‪00,88,04,63,09‬,1C,0C,00,00,64
B ‪00310010,0010‬,00,F4,01,B0,04,F0,0A,00,00,A5,00,39,03,BC,07,0E
B ‪00310020,00‬01,12

Copy and paste everything from the first B to the 12 byte into notepad and save file as NETTODAT.MAN

Save or move this file to the NCSEXPERT/WORK/ folder.

Then nettodat code with NCSEXPERT.

Done!

[blax123]

Originally Posted by Sensible_

Ok, so from the information you have provided...

330kmh
CODIERDATENBLOCK = 33 Bytes
0000 : E1 2C 03 00 00 4E ‪00 88 04 63 09‬ 1C 0C 00 00 64
0010 : 00 B0 04 C4 09 48 0D 00 00 B1 00 55 08 5A 0E 84
0020 : 12

280kmh
CODIERDATENBLOCK = 33 Bytes
0000 : 52 2B 03 00 00 4E 00 D7 ‪01 88 04 ‬
‪83‬ 0A 00 00 64
0010 : 00 F4 01 B0 04 F0 0A 00 00 A5 00
39 03 BC 07 0E
0020 : 12

0x00 = Checksum (FF this - NCSEXPERT will fix it for us!)
0x01 = Start position of needle - 2B in your case.
0x02 = Attenuation of needle 03

Next are the ranges and sectors:

X Range: (Used when BC_V_KORREKTUR is coded: aktiv)

(Hex)
0000, 4E00, D701, 8804, 830A

(Decimal Values)
0, 78, 471, 1160, 2691

Y Range:

(Hex)
0000, 6400, F401, B004, F00A

(Dec)
0, 100, 500, 1200, 2800

Sectors:

0000, A500, 3903, BC07, 0E12

So to code this we create a NETTODAT.MAN

B ‪00310000,0010‬,FF,2B,03,00,00,4E,00,D7,‪01,88,04,83‬,0A,00,00,64
B ‪00310010,0010‬,00,F4,01,B0,04,F0,0A,00,00,A5,00,39,03,BC,07,0E
B ‪00310020,00‬01,12

(Above is basically your current coding so is a backup)

So, in the same way as explained above, To convert to your M3 330kmh scale:

B ‪00310000,0010‬,FF,2B,03,00,00,4E,‪00,88,04,63,09‬,1C,0C,00,00,64
B ‪00310010,0010‬,00,F4,01,B0,04,F0,0A,00,00,A5,00,39,03,BC,07,0E
B ‪00310020,00‬01,12

Copy and paste everything from the first B to the 12 byte into notepad and save file as NETTODAT.MAN

Save or move this file to the NCSEXPERT/WORK/ folder.

Then nettodat code with NCSEXPERT.

Done!

Thank you sooooooooooo much!!

Just a question. Could i theoretically use this Nettodat.MAN for my friends 335i too? Or does ist change from Car/Kombi to Car/Kombi even if its like the same 335i?

[Sensible_]

Theoretically yes, but it's best practise to read the cluster address first to check in case he is different.

I will just say that the scaling may need some minor adjustments. It's dependant on many things, wheel size, tyres etc etc.

Let me know how it goes and if any adjustment is needed. Speedo can be checked by tool32.

[blax123]

Originally Posted by Sensible_

Theoretically yes, but it's best practise to read the cluster address first to check in case he is different.

I will just say that the scaling may need some minor adjustments. It's dependant on many things, wheel size, tyres etc etc.

Let me know how it goes and if any adjustment is needed. Speedo can be checked by tool32.

Thank you very much, I'm gonna test it later and give you an feedback.

Thanks a thousand times 🙌

[Sensible_]

No problem. Don't thank me yet. Let's see if it's working

To test the speedo use the tool32 command: steuern_tacho with the desired speed in the argument field.

steuern_tacho_aus will reset the needle.

[blax123]

Originally Posted by Sensible_

No problem. Don't thank me yet. Let's see if it's working

To test the speedo use the tool32 command: steuern_tacho with the desired speed in the argument field.

steuern_tacho_aus will reset the needle.

hes not accepting the value 330. if im using 280, its working but ends @330kmh just like before. on the highway im driving like 100kmh and hes showing like 30kmh.
if i read the buffer with tool32 im seeing that he accepted the new nettodat values but something is wrong

[Sensible_]

Originally Posted by blax123

hes not accepting the value 330. if im using 280, its working but ends @330kmh just like before. did not had the time to test it on the highway.
if i read the buffer with tool32 im seeing that he accepted the new nettodat values.

Possible that just a technical issue with the command and the cars VO.

You'll have to test it on a highway.

The important thing to test is if the actual speed is accurately reflected on the tacho. As long as the Avalon is correct it should have worked...

[blax123]

Originally Posted by Sensible_

Possible that just a technical issue with the command and the cars VO.

You'll have to test it on a highway.

The important thing to test is if the actual speed is accurately reflected on the tacho. As long as the Avalon is correct it should have worked...

Tested it on the Highway, if im driving like 100kmh hes showing 30kmh
reverted to original

[Sensible_]

Originally Posted by blax123

Tested it on the Highway, if im driving like 100kmh hes showing 30kmh
reverted to original

Hmm, interesting. I'll do some testing on my own cluster and get back to you.

[blax123]

Originally Posted by Sensible_

Hmm, interesting. I'll do some testing on my own cluster and get back to you.

what if i use the full buffer of the m3 and code it via NETTODAT?

[Sensible_]

Originally Posted by blax123

what if i use the full buffer of the m3 and code it via NETTODAT?

It is the full buffer is it not? Only thing left out was the start position which I left as your 280kmh cluster?

[blax123]

Originally Posted by Sensible_

It is the full buffer is it not? Only thing left out was the start position which I left as your 280kmh cluster?

this one is the 335i 280kmh buffer (fully stock, without mods (even without the checksum mod)

B 00310000,0010,52,2B,03,00,00,4E,00,D7,01,88,04,83,0A,00,00,64
B 00310010,0010,00,F4,01,B0,04,F0,0A,00,00,A5,00,39,03,BC,07,0E
B 00310020,0001,12

this one is the 335i 280kmh buffer which youve modified

B 00310000,0010,FF,2B,03,00,00,4E,00,88,04,63,09,1C,0C,00,00,64
B 00310010,0010,00,F4,01,B0,04,F0,0A,00,00,A5,00,39,03,BC,07,0E
B 00310020,0001,12

this would be the m3 330kmh buffer without modifications(even without the checksum mod)

B 00310000,0010,E1,2C,03,00,00,4E,00,88,04,63,09,1C,0C,00,00,64
B 00310010,0010,00,B0,04,C4,09,48,0D,00,00,B1,00,55,08,5A,0E,84
B 00310020,0001,12

[Sensible_]

Originally Posted by blax123

this one is the 335i 280kmh buffer (fully stock, without mods (even without the checksum mod)

B 00310000,0010,52,2B,03,00,00,4E,00,D7,01,88,04,83,0A,00,00,64
B 00310010,0010,00,F4,01,B0,04,F0,0A,00,00,A5,00,39,03,BC,07,0E
B 00310020,0001,12

this one is the 335i 280kmh buffer which youve modified

B 00310000,0010,FF,2B,03,00,00,4E,00,88,04,63,09,1C,0C,00,00,64
B 00310010,0010,00,F4,01,B0,04,F0,0A,00,00,A5,00,39,03,BC,07,0E
B 00310020,0001,12

this would be the m3 330kmh buffer without modifications(even without the checksum mod)

B 00310000,0010,E1,2C,03,00,00,4E,00,88,04,63,09,1C,0C,00,00,64
B 00310010,0010,00,B0,04,C4,09,48,0D,00,00,B1,00,55,08,5A,0E,84
B 00310020,0001,12

Hmm ok. I see now. I think I rushed to much when I typed it out. Yes, try. It doesn't cause any harm...

[blax123]

Originally Posted by Sensible_

Hmm ok. I see now. I think I rushed to much when I typed it out. Yes, try. It doesn't cause any harm...

Should i FF the checksum from the m3 and code it then?
checksum is just the red marked yeh?

B 00310000,0010,E1,2C,03,00,00,4E,00,88,04,63,09,1C,0C,00,00,64
B 00310010,0010,00,B0,04,C4,09,48,0D,00,00,B1,00,55,08,5A,0E,84
B 00310020,0001,12

[Sensible_]

Originally Posted by blax123

Should i FF the checksum from the m3 and code it then?
checksum is just the red marked yeh?

B 00310000,0010,E1,2C,03,00,00,4E,00,88,04,63,09,1C,0C,00,00,64
B 00310010,0010,00,B0,04,C4,09,48,0D,00,00,B1,00,55,08,5A,0E,84
B 00310020,0001,12

You can leave the checksum. NCS does the checksum calculations on the fly. That byte will always be correct no matter what you write.