RomRaider

I have a USDM 2005 Subaru Forester X 2.5. I have been trying to get Rom Raider Logger to connect so I can log ecu data for diagnostic purposes. I have successfully connnected to the ECU and read data blocks with FreeSSM using a generic FTDI cable. I have no intentions of tuning or changing the factory rom so I do not think spending $200 on a cable is a smart idea. Down in the right hand corrner the logger show the following message "Error: Invalid Header...expected 80, actual 00", When I test the connection in RomRaider with the ECU INT test the send message looks different from the recieve message, picture attached.

I have folloowed the trouble shooting instructions and verified that I have 32 bit java.

When I open up the FreeSSM it lists my rom ID as being 3B12044106, on the list of supported ECUs https://www.romraider.com/forum/viewtopic.php?t=7591 the USDM 2005 Subaru Forester 2.5 MT/AT as being 3B12044206. There is one number that is different from what FreeSSM is reporting.

Given the ever so slight differernce in the IDs, the fact that the error message I am getting suggests it is not returning an expected value, and the ECU INT test seems to be returning a differnt value from what was sent: to me this suggest my specific ECU is not supported. Or I am still doing something worng. I am not going to give up that eaisly and would like to see if anyone out there can help me.

Thanks!

are you using the latest logger and ecu defs etc. ? Also have you generated a debug log from romraider logger as that will show a bit more on what's going on.

I am using version 370 of the logger definition and the ECU definition file is version 0.8.3.1b dated 10-07-09. Seems old but the download link takes you to this file.

I have attached the log and setting files. My FTDI cable is on com port 8.

RomRaider ECU INT test seems to receive succesful init message from ECU, so it is working as expected. And ECU ID is 3B12044106 as shown early in the received message. Possible is that it just not listed in the RomRaider logger file and could be added.

you could try creating a test logger XML, anywhere you see 3B12044206 add in 3B12044106 and see what that does for it - might be just your rom ID hasn't been added to the logger.

Thanks for the advise! I added my ECU id to the logger definitions and ECU definitions and voilà it started logging! Is ther anything I can do to help add my vehicle to the defintions for eveyone? If that is something the maintainers want, this is probably not a highly saught after vehicle.

So all of this is in service of trying to diagnosie excessive fuel consumption, it is worse than my truck. So I set up a logger file with 19 of the paramters that I think I would help me and when I looked at the log file there is no data stored. Is there a hard limit to the number paramters that can be logged at once? I had another test log with fewer paramters that successfully recorded data.

yes if your testing works then the main defs can be updated later to include your logging ID for the next person.

For your actual logging parameters, make sure you have fast polling turned on and keep an eye on the bottom corner of the screen in the logger - once you max out you'll see the requests per second dropping to 0 and maybe even an error message or two flashing here and there.