RomRaider

Hello everyone,

So I'd like to start tuning simple stuff (rev limiter, DISA as advised by some members due to loss of power past 6000rpm...) with Romraider, while I'm waiting for my WB sensor, to get used to it before moving on to the "more serious stuff".

While I have a reasonably good idea of what should be done as far as tuning goes, I'm kind of uncertain about the actual tools to be used for my specific DME (MS42)

I've put together a list of the steps that need to be taken, as far as I know, with their matching tools. I'd appreciate either confirmation or correction of the following:

1. logging - Romraider (already done and I do have the MS42 ECU def anf logger def)
2. reading (extracting current ROM from DME for analysis) - Chipster MSS5x Flasher - about that, I've seen on the wiki (https://www.ms4x.net/index.php?title=Flashing_Tools ) that it applies to either 512kb or 64kb (partial) reads/writes. My partial is only 32kb, how will it do with that?
3. Tuning - Romraider
4. Writing - Chipster MSS5x Flasher (same question as above regarding the file size)
5. Logging - Romraider
6. Repeat 1-5 until the logs are satisfactory.

As far as I understand, Chipster MSS5x Flasher will allow me to skip the bootmode part and checksum corrections will be done on the fly when flashing, which sounds great. Could you confirm please?

Any feedback appreciated, thanks!!

Yes simply just use mss5x flash tool. It also does 32k for ms42.

Thanks for your quick reply pazi88! Can mss5x flash tool be used with a regular OBDII-USB (K-line) adapter or do I need to use the "under the hood" 20pin one?

About the wideband sensor, I was thinking about that one:
https://www.amazon.com/AEM-30-0300-Wide ... lp_pl_dp_1

But any feedback from experienced users much appreciated! Being able to feed data to Romraider is obviously paramount...

You can read/write your full/partial tune through your OBD2 port.

As far as wideband, I dont know the answer. Am interested to know what brand you go with and how well/easily it works with RR Logger.

The x series is a good affordable choice, and it ha the fastest response time on the market at the moment.
I am not sure about its compatibility with RR but it should be

Thanks for your inputs. Fast is obviously good for accuracy... Romraider lists 3 different AEM WB's in the plugins section: UEGO AFR 9600 baud, UEGO lambda 19200 and X-wifi controller, but I don't know about the X series.

It'd be great to have confirmation from one of the devs or someone who tried one with RR, because logging to RR is the only thing that I'm interested in. I don't really care about the gauge but I do need proper data.

I will definitely report my experience here if I go ahead with this one!

I believe that the uego pluggin do the work with the X series. But I let people that tried confirm that.

But it seems it has already been done www.romraider.com/forum/viewtopic.php?f=14&t=13505

Thanks for that useful link! There is a difference in ref numbers (03-300 / 03-333) but I reckon it should work, since it shares two data logging protocols (rs232 / can bus). According to said link, the CAN protocol is superior to rs232, I guess because of transfer speed. If that is true I will have to get an esata to usb adapter, since my laptop only has one usb port, used by romraider...

About the necessity to hook up to a battery charger or another car when flashing, in practice what do you guys do when making partial (32kb) flashes? I did it twice while making full flashes, but let's say it's not very practical especially if one wants to edit a map and flash "on the fly" after making a log.

My battery shows (on torque pro, at the OBDII socket) about 14-14.1v while driving and around 12v with ignition on.

In practice, how safe is it for partial flashes?

You can get a booster pack for this.
Siemens MS ecus are really safe onces ... bosch ecus much more attentiveness (special CC460 processors).
So with good battery there shouldnt be problems with partial but would prefer booster pack.

Thanks, I will keep that in mind!

Ok so, first bump on the road (on the very first step haha) and I must be extremely ignorant because by the looks of my google research I'm apparently the only one with that question: where the heck can I find the 31 digits hardware ID asked for here: https://www.ms4x.net/licence/?

I looked for that 31 digit # using INPA, winkfp and RomRaider (RR) and all I could come up with is the following

- assembly id number (7 digits, used winkfp to get it)
- hardware # (7 digits, winkfp, same as "ECU ID" in RR)
- software # (7 digits, INPA)
- official # (7 digits, INPA)
- changing index: DA (INPA)
- exhaust variant: CAT (INPA)
- CAL ID (RR) : 0110CA

Is it a combination of some of the above? Or do I have to get the number on the DME? About that, I do have a pic I had taken after blowing the previous engine in my car. I had shared it with a member here so he could provide me with a ZB# for winkfp.

And as I"m now running a different configuration than before (M52TUB28 with a euro software instead of M52TUB25 with a US software) I can see on that pic that some # are different from the ones pulled with winkfp and the other softwares mentioned.

I've been thinking about possible numbers combinations, and the vin number (17 digits) + two of the abovementioned numbers (7+7) would equal 31 digits, but it's just a wild guess, and I don't which "7 digits numbers" to use from the list above.

Thanks.

Its a code that the mss5x flasher generates and displays when you plug in your usb obd cable for the first time but I dont think its even needed anymore. I just got a new cable yesterday and i didnt need to put in a license code. So as a quick test, open mss5x flasher and then plug in your usb obd cable. If a green light appeara on the bottom right hand side of mss5x, you are good to read / write.

Yes when mss5x flasher is started for first time it shows the code that you need to give for the license generator. It's that simple. Remember to plug in the usb obd cable before starting it for first time.

I thought that was needed to be able to download it in the first place because the licensing page is the one you're taken to by the first link on the Ms4x wiki and apparently I didn't pay attention to the second (download) link
So I'll try downloading it elsewhere and try it.

Thanks guys!