[Madhouse]

I have updated to version 69, but the leds rpm still do not work.

 

[Madhouse]

Start again by writing to the patch bin. my vin and isn, applying cluster patch 69, checksum ok, but file is identical to flashed.Something escapes me?

 

[sda2]

You need to apply the patch and then save the binary. In the parameter summary it should change to "patched".

Make sure you have directory permissions to save the file.

 

[Madhouse]

I just started from scratch vin, ecu, isn correct, corrected a tunerpro data pair, I just wrote it, but it still doesn't work.

 

[Madhouse]

Well, the patch I think was loaded on the map. Now if they no longer light LEDs, is it another problem?

 

[paw.garage]

can't wait the new patchlist

 

[Madhouse]

When I do indicator tests with bmw scanner, the rpm LEDs do not light up.

 

[Madhouse]

When checking test cluster indicators, do the rpm LEDs also light up?

If so, why don't they work for me?

 

[Madhouse]

I think my cluster does not have these holes for the LEDs.

 

[sda2]

Since this is not Facebook, please try not to spam this thread with multiple posts, but edit your last one.

For cluster questions open a new topic since this has nothing to do with it.

 

[Jeddreeves]

Hey everyone, i'm having some trouble get version 69 to run on my ms43.
I own a 2002 325i auto.
I have two dme's, one i got off eBay which is running "MS430056_M54B25_Logger_EWSsignature_CHK5off" and this have being working fine the past few months, i have even played around with some of the values in the 64kb portion to make the car pop/backfire. The other day i tried to install my completely stock untouched dme that came in my car, for some weird reason the car would crank be not start.

So i have decided to use the Ebay dme that is running ms430056 as my back up now and i am playing around trying to update my original dme to version 69 as i am going to be supercharging the car in the coming months and it seems like version 69 is much easier when it comes to tuning.

I flashed my original dme with the version 69 M54B25 RHD EU4 tune off the wiki after matching up the VIN and other numbers using the community patch list in tuner pro. I then read the full 512kb file from the dme, opened it with tuner pro and patched the immobilizer bypass, checksum bypass and the maf sensor hack. Once i was finish i used the "ms43 checksum" off the wiki. It corrected 3 errors. I then used "ms4x flasher" to write the full 512kb file to the dme. I disabled checksum correction in "ms4x flasher" when i uploaded that 512kb file.

The car just cranks and it will not start. i used INPA to read codes and i have attached screenshots of the codes found.
I tried resetting adaptation and that didn't seem to help. I have an engine light and ABS/traction light on the dash.

Any suggestions would be appreciated.

https://drive.google.com/open?id=10O-ThgqrskyZFEhFboo_6-W1-e5zPmec _sl_ _sl_ _sl_

 

[sda2]

We just found a bug with US based files and earlier versions of MS43.

This incompatibility is now solved and you may try again if you've had ECU self-test DTC and non starting engine in the past.

 

[sda2]

We just found a bug with US based files and earlier versions of MS43.

This incompatibility is now solved and you may try again if you've had ECU self-test DTC and non starting engine in the past.

 

[Raydijkstra]

hi guys. im having trouble getting my wideband o2 signal to log with tunerpro. i have an AEM wideband and using the 0-5v output of that into the post cat lambda bank 1. i can see the signal perfectly in INPA but the signal is not getting through to tunerpro. i am using Michael H. ADX file. it has provisions for a wideband input.

is there anyone that can shed some light on possible issues? i have changed the conversion in the ADX to match the gauge. this is definitely not a wiring problem as the voltage shows up in inpa and directly converts to the correct AFR when manually converting with the conversion factor.

any help would be greatly appreciated.

 

[d_cleverzz]

hi guys. im having trouble getting my wideband o2 signal to log with tunerpro. i have an AEM wideband and using the 0-5v output of that into the post cat lambda bank 1. i can see the signal perfectly in INPA but the signal is not getting through to tunerpro. i am using Michael H. ADX file. it has provisions for a wideband input.

is there anyone that can shed some light on possible issues? i have changed the conversion in the ADX to match the gauge. this is definitely not a wiring problem as the voltage shows up in inpa and directly converts to the correct AFR when manually converting with the conversion factor.

any help would be greatly appreciated.

The ADX for TunerProRT does not log post cat o2 sensors. I’m not sure why, to do this I still don’t know why. Just use RomRaider, which you can view the post cats and just use the proper correction factor for your AEM.


Sent from my iPhone using Tapatalk

 

[rbngr]

Hey everyone, i'm having some trouble get version 69 to run on my ms43.
I own a 2002 325i auto.
I have two dme's, one i got off eBay which is running "MS430056_M54B25_Logger_EWSsignature_CHK5off" and this have being working fine the past few months, i have even played around with some of the values in the 64kb portion to make the car pop/backfire. The other day i tried to install my completely stock untouched dme that came in my car, for some weird reason the car would crank be not start.

So i have decided to use the Ebay dme that is running ms430056 as my back up now and i am playing around trying to update my original dme to version 69 as i am going to be supercharging the car in the coming months and it seems like version 69 is much easier when it comes to tuning.

I flashed my original dme with the version 69 M54B25 RHD EU4 tune off the wiki after matching up the VIN and other numbers using the community patch list in tuner pro. I then read the full 512kb file from the dme, opened it with tuner pro and patched the immobilizer bypass, checksum bypass and the maf sensor hack. Once i was finish i used the "ms43 checksum" off the wiki. It corrected 3 errors. I then used "ms4x flasher" to write the full 512kb file to the dme. I disabled checksum correction in "ms4x flasher" when i uploaded that 512kb file.

The car just cranks and it will not start. i used INPA to read codes and i have attached screenshots of the codes found.
I tried resetting adaptation and that didn't seem to help. I have an engine light and ABS/traction light on the dash.

Any suggestions would be appreciated.

https://drive.google.com/open?id=10O-ThgqrskyZFEhFboo_6-W1-e5zPmec _sl_ _sl_ _sl_

Don't correct checksums with "ms43 checksum", let ms4x-flasher handle that.

 

[m54e30t]

The ADX for TunerProRT does not log post cat o2 sensors. I’m not sure why, to do this I still don’t know why. Just use RomRaider, which you can view the post cats and just use the proper correction factor for your AEM.


Sent from my iPhone using Tapatalk

It halves the logging speed because rear o2 sensors are in a different response.

 

[Jeddreeves]

Does anyone know what the “MS430056_M54B25_Logger_EWSsignature_CHK5off” file actually does to the EWS module.
I virginized an ecu with ms430069 by setting all of ISN to FF.
I then tried to resync the DME with the ews using both INPA and ms4x flasher but neither could contact the EWS module. When I try and sync I keep get the pop up “no code stored for this driving session.” If I try and reset it I get the pop up “no start value is stored in this DME.”
In INPA after I try to start the car I get the the error: EWS code.
I virginized the DME in boot mode using jmgarage flasher. I read the file back off the DME to make sure I had written to the ISN/VIN area of the DME. The Isn was still “FF” out so it should have being virginized but for some reason the car still won’t start it would only crank. I corrected all checksums.
I even tried using the patch to clear immobiliser data, and the immobiliser bypass patch but neither worked.

Also to double the MAF limit do you patch that in the community patch list file, and then double all values in both maf tables? Or is it more complicated then that.

Any suggestions?


Sent from my iPhone using E46Fanatics

 

[sda2]

Updated to v2.5!

added features:

• DS2 Logging Feature Enhancement updated
• DS2 Speed Increase
• Map Reduction
• Ignition Cut Limiter
• Alpha/N mode
• MIL Knock Indicator

Many of you waited for it, here is the first version of ignition cut (combinable with the launch control).

We will have to see how good this works, tests showed that ignition retard builds more boost than ignition cut, but that will be a feature of the next version

Exhaust sound videos welcome :clap:

MIL Knock Indicator is also handy and speed increase for logging speaks for itself.

Check it out here: https://www.ms4x.net/index.php?title=TunerPro_MS43_Community_Patchlist

WARNING: Some patches are overhauled, so we suggest starting with a fresh binary or undeploy the patches with the patchlist first.

 

[rbngr]

Updated to v2.5!

added features:

• DS2 Logging Feature Enhancement updated
• DS2 Speed Increase
• Map Reduction
• Ignition Cut Limiter
• Alpha/N mode
• MIL Knock Indicator

Many of you waited for it, here is the first version of ignition cut (combinable with the launch control).

We will have to see how good this works, tests showed that ignition retard builds more boost than ignition cut, but that will be a feature of the next version

Exhaust sound videos welcome :clap:

MIL Knock Indicator is also handy and speed increase for logging speaks for itself.

Check it out here: https://www.ms4x.net/index.php?title=TunerPro_MS43_Community_Patchlist

WARNING: Some patches are overhauled, so we suggest starting with a fresh binary or undeploy the patches with the patchlist first.

:thanks::excited: