RomRaider

Looks like a lot of the issues people were having are finally solved in this release candidate so we should be getting close to the next official release.

I'm still of the opinion that the defs shouldn't be packaged with the application since they are likely to be updated again before the following app release rendering the next release out of sync. I also don't like idea of tying the app release to either standard or metric defs. I personally use a custom def (metric + psi) since the others don't suit me. Ideally RomRaider should support multiple scalings and have a single version of the ecu and logger defs with a unit preferences configuration option in RR.

Is anyone still having any issues with any aspect of the editor or logger?

Is that something you think you'll work on in the future? If so, I can certainly cater the defs to support this.

I guess the problem is that a lot of users don't bother to read anything - they will download RR and attempt to open their ROM and wonder what happened. Could you add a message if no ECU defs are added to the ECU def manager (i.e. default in the release), when a user attempts to open their ROM, they will get an error message "No ECU definitions are installed. Go to this link for the latest ECU definitions". Maybe the same for the logger defs too.

I'm of the opposite opinion: that it's better if the releases come with the most current definitions available at the time of release. This allows a user to download RomRaider and have something that works "out of the box." After that, it would be up to the user to get updates. Needing to get definition files separately from the kit isn't that big a deal, but it seems to me to be a little easier for the user if they have something included.

Either way is workable, and neither is perfect; ultimately, the one doing the work has the final say.

Forcing users to download definitions separately teaches them how to do the process in the future when definitions are updated and guarantees they will get the most-current definitions when they install RomRaider.

Tactrix cable 2.0
Windows Vista
02 WRX
Romraider 0.5.1b RC4

I noticed everyone else is having great success with this, but I still can't get my to log. I flashed a map with ecuflash, so I assume the drivers/cable are good, but I tried a few different version of RR for logging with no success. I dl'ed this version, got the new definitions, went through the step by step instuctions on how to log and still no dice. I just keep getting the "stopped" in the upper right hand corner, and "disconnected" in the lower left hand corner. For what it's worth I couldn't get ecuexplorer to connect either.

I'm new at this and have been studying for a few days on what to do but this thread was pretty much the end of the line when it was working for everyone but me.

Any advice?

Thanks

Did you install RR as administrator?

I'm pretty sure I installed it as an adminstrator. Would it have let me install it at all if I didn't? I think this is the third version I installed, so I'm not certain if the last one was as an adminstrator. I guess I assumed that if it installed at all I must have done that part right.

-sound right?

I tried re-installing it just to make sure I did it as administrator, re-extracted the definition files to the romraider main dir, and still no dice. Just says "stopped" and "disconnected" no matter what I do.

Whether the definitions are included is a moot point if the RomRaider application itself had a proper update feature.

It can't get much easier then if the user was to simply press "update" and have the RR application download the latest defs to the correct locations.

Try running the RomRaider.exe in the install directory as administrator.

Oh wow, of course it had to be too simple. Sorry for being a noob, I thought you only had to run the install file as administrator...turns out you have to run the program itself as admin too. Thanks for helping out.

great work. thanks.

It seems users constantly are confused by the parameter list in the logger that is shown before connecting to the ECU (which is just a list of all standard parameters). They look for extended parameters in the list and think they don't have any extended parameters because there's none in the list because they haven't actually connected to the ECU. Maybe the parameter list should not be shown until the logger connects to the ECU? I understand the list is there so that users can create profiles without being connected, but I think real-world, most profiles created are going to have at least one extended parameter anyway (plus the fact that not all standard parameters will apply to a particular ECU).

I am having trouble getting the LM-1 plugin to work with this release. I am running a direct Serial port on the laptop to COM1 and my OP2.0 resides on COM2. The LM-1 always shows 0 on the logger and never seems to "connect" to the Wbo2.