RomRaider

I am once again in a need of help from you knowledgable people, I'm having issues with my logger losing and reseting connection every few seconds and it makes logging and tuning a nightmare... Car reads everything fine, then pops a quick error for Invalid checksums and reconnects. From my understanding I instaled the ECU Logger definitions and everything properly since the car does get the info but resets here and there, I bought and use MS41 Quickflash like everyone recommends since it has automatic checksum correction. Thank you everyone in advance!

A little confusion here. Where are you seeing invalid checksum? In Romraider logger? If so that would indicate the logging packet checksum. Not the ecus flash checksums.


Sent from my iPhone using Tapatalk

Please provide the rr_system.log where this is happening.
https://www.romraider.com/index.php/Rom ... HowToDebug

Checksum failures are usually a sign of wrong protocol, a bad cable, bad USB port, cable connection problem, interference from a long cable and running engine, or ground loop between the logging computer and the DME.

Here is the rr_system.log that you requested, thank you very much for the quick reply dschultz!

Yeah busterhax, in bottom left corner of the logger, I just pointed it out since I've seen that there are programs that don't support automatic correction so I thought it might have something to do with that, really want to finish the conversion to MS41 on my M50 and start driving it, only thing left is to tune it, hope I can figure that out and finish it in next month and a half since that is when my MOT is

You have two problems:
1) You are using Java 64 bit, RomRaider does not work with that you need to use Java 32 bit. Uninstall it and load Java 8 for i586. No need to uninstall/reinstall RomRaider, just Java.
2) The protocol you are using is SSM for Subaru. I presume you want to use DS2 for BMW.

1) My mistake, thank you very much for pointing it out.
2)That is correct, I want to use DS2 for BMW.

I did what you pointed out was a mistake, atleast I think I did everything right but the error keeps popping up, I deleted the old rr_system file and posted a new one.

It finds your car okay.
17:36:45,011 INFO [Query Manager] - ECU ID = 1429861
17:36:45,027 INFO [AWT-EventQueue-0] - CAL ID: 41, Car: 1996-1998 Euro BMW E36/E39 MS41.0 MT

Are you using the official logger definition v370?
viewtopic.php?p=162644#p162644

Yes, and as DJ Khaled would say "anotha one".... still having the same problem.

Can you try logging only battery voltage to see if it is stable.
Then slowly add parameters until you see the error. Let me know the parameter that causes it to fail.
And provide the logger definition file with your reply.

I did as you ask and was logging only battery voltage it was 11.8~7 going up and down every second or two, the error appeared with only that on, didn't even add other parameters.
Here is the new rr_system and definition that you requested.

Looking at the log I suspect you have a "cable" problem. The data is being corrupt between the ECU and the Logger.

These are all valid replies:
15:25:23,177 DEBUG [Query Manager] - Mode:STATE_0 ECU Response <--- 1206A00073C7
15:25:23,257 DEBUG [Query Manager] - Mode:STATE_0 ECU Response <--- 1206A00074C0
15:25:23,337 DEBUG [Query Manager] - Mode:STATE_0 ECU Response <--- 1206A00074C0
15:25:23,417 DEBUG [Query Manager] - Mode:STATE_0 ECU Response <--- 1206A00074C0
15:25:23,496 DEBUG [Query Manager] - Mode:STATE_0 ECU Response <--- 1206A00074C0

This one, the third byte is A1, but A0 is the expected value for the acknowledgement byte.
15:25:23,576 DEBUG [Query Manager] - Mode:STATE_0 ECU Response <--- 1206A10073C7

These next two, the first byte should always be 12, we got 1A instead.
15:25:27,975 DEBUG [Query Manager] - Mode:STATE_0 ECU Response <--- 1A06A00072C6
15:25:34,014 DEBUG [Query Manager] - Mode:STATE_0 ECU Response <--- 1A06A00072C6

This reply has an invalid length (byte 2), it should be 06 but we got 16.
15:25:48,817 DEBUG [Query Manager] - Mode:STATE_0 ECU Response <--- 1216A00073C7

Can you try a different cable with a different driver set?
Do you have a ground loop between the computer and ECU? If using a laptop try running strictly on battery with no other electrical connections than your logging cable.
What about cable length from the ECU to the Logger, could there be interference? Does it log better if the engine if off?

I'll see if I can get my hands on another cable and try that, yes I put the switch on the cable for looping it, I've used this same equipent to flash multiple ECUs, and I've just tried what you said, when the car is ON position the logger doesn't disconnect at all, once I start the car the errors start to appear and it disconnect and reconnect again and again.

EDIT:
I looked up a bit about ground loop, and I realise that my ECU is grounded to the engine through the harness, do I just take the wire that is for the ECU ground, cut it and ground it to the chassis and hope that it will fix my RR logger issue, if it does, will I be able to just run and flash the car like that all the time or do I have to do some rewiring to wire it back to the engine ground?

I wouldn't change any factory harness grounding, that's sure to make your car not run right.
If your computer is only connected to the ECU through the logging cable and nothing else, there will be no ground loops. If you ground your computer to the chassis while connected to the logging cable, that will create a ground loop.
Start with a different/better reputable cable and driver software.

Yeah it was connected only through cable, nothing else, I'll see if I can get my hands on a different cable and try it, since my OBD2 cable seems like a decent one, the X20 adaptor to OBD2 looks cheap and iffy...