RomRaider

I've written some software to display various SSM parameters in real time like a digital dashboard. It also aggregates data over time to produce scatter plots and tables of knock activity, volumetric efficiency, and so on. It was primarily intended for CarPC usage but it's also usable on laptops.

Pictures:
http://ssm.codeplex.com/Wiki/View.aspx?title=Pictures

Main page for the project:
http://ssm.codeplex.com/

To download it, click on the "Releases" tab on either page.

If you have a 16-bit ECU you'll have to edit the config file manually to choose the right extended parameters to make everything work. I think it will work as-is with most 32-bit cars, but it's only been tested on a few.

The to-do list, in no particular order:

OpenPort 2.0 support (long overdue)
PLX wideband support (using NSFW's code)
Configurable colors (requested by two users (that might be all of them?))
Write a couple seconds of logging data any time the knock counter increments (two seconds before, two seconds after)
Better support out-of-the-box for 16-bit ECUs
Ability to change which parameters to display via the UI (instead of tweaking the config file)

I welcome your feedback.

Hi there, I have a CarPC and do use your program. I like the fact that it's designed for CarPC touchscreen usage.
Am looking forward to your next version with user selectable parameters to log/view and maybe with a warning/threshold exceed feature.

Looking forward to openport 2.0 support.

Heya mate. I gave this a go last night and although it starts and works, I get a lot of errors saying XXX not supported.

I'm guesing it is a definition problem - any way of updating it support the RomRaider Logger definitions?


Edit: Also, none of the gauges display FLKC or FBKC - it would be more usefull to have them as default as part of the main gauges.

It already uses RR definitions, actually... The problem is that by default it tries to pull a list of parameters that I chose while running it in my own car. I'm guessing your car is not an '05 Legacy.

The SawMill.exe.config file is sort of like RomRaider's log profile, it contains the list of parameters to display. To get it to work on your car, you'll have to change the parameters to the equivalents for your car. It actually does show FBKC and FLKC on my car, but the parameter IDs aren't the same across all cars.

There's no UI for selecting parameters though, you just have to open the config file and open the logger.xml (in the Configuration subdirectory) and find the IDs for the parameters you want. I've been meaning to create UI for this for months to make this easier, but still haven't gotten around to it. I should have a bunch of free time in June, so maybe then. I can't promise though.

If you're willing to take the time to convert the exe.config file to work with your car, I'd be happy to include it with future versions, to save other people the trouble. I suspect (or, hope) that it would be sufficient to have one version for 16-bit cars and one version for 32-bit cars, but it might not be that simple.

Out of curiosity, is your car 16-bit?

Thanks!

Ah that would explain it then


Maybe a better way would be to offer an option somewhere in the UI for model selection - then once the model is selected it auto-loads the correct parameter IDs for that model. Is that possible?


Yeah, 16bit. I'll just manually edit the config for the moment, but if you can create a selection option as suggested above, that would be great

Cheers
Leslie

What logger definitions should be used on 16 bit ECU's?

Basically you need to go to the install directory (default it C:\Program Files\NateW\SSM Suite) and then go through the SawMill.exe.config file and change the parmater IDs to the correct ones to suit your vehicle. To get the correct parameter IDs, read through the RomRaider Logger definition file (logger.xml).

The easiest way to fix it to suit your car, is start sawmill, then write down the parameter ID that is listed with every error you get (ie. E90, E94, P36, etc) when changing to different screen views (ie. Gauges, Scatter Plots, Tables, etc) - make sure you go through EVERY possible screen and write down all the parameter IDs.

Then close sawmill, open the the RomRaider Logger definition file (logger.xml) and find the correct parameter ID to suit your vehicle for the same function listed for the parameter ID you got the error for.

EG. On a 16bit you get an error that lists E93. E93 is specific to 32bit models and is for "Throttle Plate Opening Angle (2-byte)**". So what you'd do is replace E93 in the "SawMill.exe.config" file with a parameter ID for a similar function - like P13, which is "Throttle Opening Angle" - or you can use whatever parameter you like instead.

If you want, go through sawmill and write the parameter IDs for the errors you get and post them here and I'll attach a modified SawMill.exe.config file for you to try

Leslie.

Well I just went back through my sawmill.exe.config file and double checked the addresses and found that I used incorrect capitalization on the functions I imagined would work. I fixored and will retest here in a little bit if it works then that explains my problem if not i'll attach my .config and let you see what i'm doing wrong.

Okie doke now it works right. Its amazing what telling it to read in the right units does!

I'm glad you guys were able to make it work. Would you mind posting your .exe.config files? Also, if I may have your permission, I'd like to include them in the official release - especially if one or both of you have a 16-bit car.

Thanks!

I hate to make predictions about stuff like this, but I'm going to anyway... With a little luck I will have some time next week to work on this project again. I'm going to be focusing on wideband support and OpenPort 2.0 support, but I don't know how far I'm going to get. Two months from now I should have a lot of free time, so I'm hoping to do a new release around the end of summer with both of those and UI for selecting parameters.

I'll post my config for you when I get home tonight.

And LC-1 support would be awesome - but rather then adding support how romraider has (ie. going through serial data and filtering the LC-1 info?), maybe follow the innovative SDK so that it supports all Innovative serial devices from the get go

Also, what would be awesome, would be having the ability to press "log" while you have sawmill running without having to close sawmill and open lumberjack (because you can only use one or the other via the openport cable). If you can integrate the logging functionality of lumberjack into sawmill that would be awesome - just add another button to the initial screen so it has:
Gauges
Scatter Plots
Tables
Logging

And under the logging screen have buttons for:
Log
Settings

Where Log will have buttons to stop and start log recording and show the logged data being recorded visually (like the gauges screen) and settings will have options to choose the parameters to log and where the log is to be saved.

Leslie.

Here's mine. I currently only have the main, FTrim and Boost tables configured. Do with it what you will as it is your project. It is a 16 bit ecu and works great on my brother in laws 03 usdm wrx wagon. I use COM3 running a cheap ebay VAG-COM knock off cable. Thanks alot for this tool!

Nate,

I'm glad I found you on this forum. I left a message over on codeplex but it seems like you haven't been checking there recently. I also really like your program and have been using it in my carpc for awhile. I am also having difficulties with the config file. I thought I could edit it to display different values on each gauge or to rename the gauge, but it doesn't seem to work. I am getting the errors saying the parameter is not compatible with my ecu, even though it seems like I pick a common one. How can I tell which parameters in the logger.xml are 32bit ones?

Thanks,
William