Correcting the variable redline to 7k RPM in your M3 cluster

  • Login or Register, members don't see Ads!
  • Tip: You can toggle the Dark Theme at the bottom of the page

LMB335is

Sergeant
Apr 12, 2017
262
FOB FL
I want to post this up here first before anywhere else because I'm not sure how the values are derived and to throw the guys that have already done so much to move this retrofit along a small bone. Hell, with all the smart guys in here it may already be common knowledge but I found a utility, Perfekt Toolbox, which can do custom nettodat coding for the KOMBI. I don't think I can upload a zip here but I'll post a mega link to it. There's no tutorial for it, at least not one I can find so make sure you back up everything before you start playing with it. By changing the starting position offsets and motorsteps in the tach and warning zone menus you can adjust the redline to wherever you want it. You may be able to remove the error in the speedo as well with the right adjustments. This is just a pic of what the tach menu looks like. Props to @Hpaula for giving me access to his values so that I could correct mine.
https://mega.nz/#!ndxXEbKK!abfIqRbmdSbKPnOjE4BblGZHTg-s8zZX_AMMv1SjZNs
Perfekt_BILL.jpg
 
Last edited:

LMB335is

Sergeant
Apr 12, 2017
262
FOB FL
I'm not sure I understand the problem. My M3 KOMBI functions perfectly and shows a 7k RPM red line.
That's interesting. In mine and a couple other instances I know of, the cluster functions fine it's just that the redline parked itself at 7.5 k. There's a thread on the one of the other forums of a guy putting the M3 cluster in his diesel and having to use custom nettodat coding to bring it down to 5k rpm. If you have a chance sometime could you pull the KOMBI up in NCS Expert and save the nettodat pop up screen? I'd be interested in comparing your values to my pre and post coded values.

On a side note though, this utility can also be used to eliminate the error in the analog speedo and adjusting the swing if you switch from a mpg gauge to oil temp.
 

NoQuarter

Captain
Nov 24, 2017
1,163
Indiana, USA
Years ago I was working on the M-hud view in my 535. The rpm/temp display in the hud was always off for everyone that coded in the M view in their HUD

At the time, everyone was working on trying to get it to match via nettodat changes and I'm not sure but just a couple guys got it to work. However, I got mine working just via the "normal" NCSexpert type coding changes.

anyway.... this just reminded me of the same type of scenario and that in fact it may be you can fix this via NCSExpert especially since it is working for dyzak.
 

LMB335is

Sergeant
Apr 12, 2017
262
FOB FL
Years ago I was working on the M-hud view in my 535. The rpm/temp display in the hud was always off for everyone that coded in the M view in their HUD

At the time, everyone was working on trying to get it to match via nettodat changes and I'm not sure but just a couple guys got it to work. However, I got mine working just via the "normal" NCSexpert type coding changes.

anyway.... this just reminded me of the same type of scenario and that in fact it may be you can fix this via NCSExpert especially since it is working for dyzak.
If it's in FSW_PSW coding somewhere I'd love to know the parameter(s) in our KOMBI. I fooled around with everything I thought might have something to do with it including the four parameters that need to be coded to work with the M3 GWS. Maybe it has something to do with the VO changes for whatever reason, I don't know yet because I haven't gotten that far. All I know is that by changing a few motorstep and starting offset values in this utility it automatically applies the changes to the nettodat MAN and then writes it to the ECU with one click. @Hpaula has the M3 GWS and KOMBI coded in correctly and his was still off.
 

Stokes

Corporal
Jan 26, 2018
131
Houston, TX
I think I'll give it a go. Thanks.
Mine settles at 7200 rpm when warmed up. I'd like to move it down to 6500 just as a reminder that no power lives up there.
 

Seb335i

Specialist
Jun 14, 2019
55
Is there someone who know how to code the 330 km speedometer in perfekt toolbox ? I've a retrofited M3 DCT Cluster with custom gauges to match the 335i RPM and oil temp scale. Everything is ok but the speedometer need to be coded to show the right speed.
 

Attachments

island road

Corporal
Nov 21, 2016
102
Boston
Is there someone who know how to code the 330 km speedometer in perfekt toolbox ? I've a retrofited M3 DCT Cluster with custom gauges to match the 335i RPM and oil temp scale. Everything is ok but the speedometer need to be coded to show the right speed.
I would love to do the retro fit for my car so i have access to the oil temp but I cant stand the 9k RPM on the M5 cluster. Where did you happen to acquire the gauges?
 

LMB335is

Sergeant
Apr 12, 2017
262
FOB FL
If you're using the M3 cluster the speedo is already coded for 330 kph.

If you want to set the M3 tach and oil temp to match a non M tach and oil temp gauge face (stock 335i) read your stock cluster and use the stock motor steps and rpm/temp break points and write them to the cluster.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Top