RomRaider

This is the first release that includes support for the new OpenPort 2.0 cable using J2534 API.

Besides the new cable support, the rest remains the same as RC2. No additional features have been added or bugs have been fixed.

Things to note:

* The logger will automatically detect what sort of cable is attached (1.2/1.3 or 2.0).
* If you unplug the OP2.0 cable while it is communicating with the ecu, you may need to reboot in order to reconnect and continue logging. This seems to be an OP2.0 issue as it happens with the drewtech test app also. Moral of the story: DON'T UNPLUG THE CABLE IF IT IS CONNECTED TO THE ECU!
* If you are using an OP2.0, you can ignore the COM selection list. It is NOT used unless a 1.2/1.3 cable is connected. The OP2.0 is plug and play.
* OP2.0 will currently not work in any way shape or form on Linux. The download is only provided for testing of anything that may have been broken along the way.
* You will need to update the logger defs yourself this time, sorry I forgot!

Whether you have an OP2.0 or not, download it and test it out! I don't have time to test every scenario myself.

Download: See RC4

Enjoy!

I downloaded the new file and installed it after uninstalling my previous RR install and deleting the directory. I installed the latest ECU and logger defs as stated above.

I attached the cable to the laptop (running Vista) and plugged it into the OBD II port, started the logger then started the car. No dice. The logger said CAL ID: Unknown and ECU ID: Unknown.

I tried rebooting, cycling the ignotion, disabling the firewall, and all sorts of other things with no luck.

The car is an '04 JDM WRX.

EDIT: Initially I was getting an error about a corrupted .jar file. I just installed it again with new defs (converted to lambda) and it's working great. THANKS!

seems to be working, thanks for the great work....

I tried using a different laptop with the same result. The laptop see's the cable and identifies it as Tactrix 2.0 and assigns it to COM4. ECU Flash sees the cable. The logger shows COM4 in its list of ports but it doesn't work. Would the fact that the car was tuned with Ecutek have anything to do with it? Is there a specific sequence of actions that are required for it to work?

Logger still doesn't open for me. I uninstalled ALL java, rolled back video drivers, etc... It'll put the romraider logo on the screen for about 27 seconds then it shuts down javaw.exe with nothing. Same with both cables 1.3u and 2.0. Is there a way to debug why the Normal logger won't work? The SSM Tool works and the Utec logger works.

Shoot. I'm having problems with the logger too. I cannot connect. No matter what I do the circle in the upper right is orange and it reads "Stopped." On the lower left it reads "Disconnected".

Without turning off ignition or disconnecting the Tactrix cable, I shut down the new version and ran the older version of the logger. It connected nicely as usual. I shut that down and re-loaded the new logger and loaded a known good profile and I still can't connect. Ignition on/off/on, Tactrix in/out/in, tested many combinations and can't get the new logger to connect.

I am having that same issue with my setup. Whew, I thought it may have been something wrong with my cable.

For those having problems:

* Rename the log4j.properties in your base install dir so you don't lose it
* Copy the following file into your base install dir instead: log4j.properties
* Try and use the logger, replicating any errors, etc
* Post the resulting romraider.log up here along with car, cable type and operating system used.

Paul, Here is my .log file which is after downloading yours and deleting the .log file first. Ran the -logger first, then tried from inside RR. The second log is the same but with OP 1.3u.

*edit*

I do not have either cable connected to a car. I am simply trying to OPEN the logger on my computer first to verify functionality of the program.

I hate to sound stupid but I don't see a file called romraider.log in the directory. Is this file only created when there is a connection to the ECU?

The file is created when you start the logger.

Your logs don't reveal anything of interest. It looks like it is just being killed. Did you install as administrator? Have you tried it on an XP machine?

For those running Vista, where is the file op20pt32.dll located on your system? It is installed by the tactrix drivers. If it is in a different place to on XP machines (C:/windows/system32/op20pt32.dll) then the logger won't find it in this version. I am planning to improve this in the next release.

Works fine on my XP machines, it used to work great on my Vista laptop but a while back it stopped working. I rolled back as far as I could and still nothing. I checked the location of my DLL file and it was in C:\Windows\System32 as expected. Is the normal logger called differently than say the UTEC logger? The utec logger loads up just fine. I have tried Admin installs and normal installs. I have that Security stuff turned off and I am the only user on my computer with full priveledges.