RomRaider

Donations are welcome!

New release candidate with a few updates and new features (Please read the change list carefully!)

- Change Log -

0.5.6 RC6 (03/24/2013) Build # 483
-------------------------------------------

Editor

• fix for various Table Compare operations: by scotthew
• added a Java 64bit VM check and warning message: by lizzardo (*1)

Logger

• fix Logger Close issue #20 while on any of the MAF, Injector or Dyno tabs: by lizzardo
• added a Java 64bit VM check and error message then close: by lizzardo (*1)
• fix to allow logging of External sensors only (with no ECU connection) (*2)
• refactor to allow easier addition of other future Logging protocols
• added ISO15765 protocol support on Windows platform (*3)
• added a user Setting to Logger to force English US number format in log files
• fix for issue #4 (multiple Query Managers could be started)
• update 'Log to file' button to switch between 'Start/Stop' in the label
• add a rudimentary test app to read some OBD-II parameters (*4)
• reformat (shorten) display of Profile and log file names in Logger title bar

Application Installer

• added a Java 64bit VM check and warning message during installation: by lizzardo (*1)

Notes

1. Since RomRaider relies on various externally provided classes and vendor libraries, the 64bit Java VM is not supported. The RomRaider installer and Editor will issue warnings if a 64bit Java VM is detected and advise the user to uninstall it and install the 32bit Java VM. The Logger will warn and exit. It is unlikely that 64bit Java VM will even be supported as all external classes and vendor libraries must be compiled for native 64bit operation. See note 3 for an example.
2. To log External sensors only, un-select both the ECU and TCU checkbox on the Logger menu bar. Then switch to the Externals tab and check the items to be logged. The log Externals only setting is not retained between logging sessions.
3. The use of ISO15765 requires a J2534 compliant cable. Since the J2534 specification only defines Windows 32bit (not 64bit) systems as a valid platform, Linux and 64bit systems are not officially supported. When/if a Linux J2534 driver becomes available then support can be enabled for non-Windows 32bit platforms.
4. This rudimentary test app ONLY works with J2534 compliant cables and ONLY supports the ISO15765 protocol. It can currently read out the vehicle information and any active DTCs. The app can ONLY be started in the RomRaider directory from a command window using the following syntax:
   java -cp RomRaider.jar com.romraider.io.j2534.api.TestJ2534IsoTp [j2534dll]
   
   where [j2534dll] is a valid J2534 DLL library name, default is to use the Tactrix Openport 2.0 library

A note about External plugins: The Innovate MTS (LM-2) plugin checks each COM port on the computer to determine if any Innovate devices are connected. This action can slow the Logger's startup. If you do not need the support of the Innovate MTS (LM-2), I suggest moving that plugin item out of the RomRaider\plugins directory to stop it from loading. Actually this can be done for any External plugin that you don't use in your setup.


Please download it and give it a workout!

Downloads: Windows Installer | Windows ZIP | Linux Installer | Linux ZIP

really great stuff

Quick test on a EURO4 Diesel ECU and it works CAN-logging works fine.
I send the link with the software-update to some EURO5 Diesel drivers.
They will test on their "CAN-only" vehicles.

Thanks for this imported up-date

Jochen

I finally realized that there is a new menu item to select CAN bus as the logging connection (RR:Logger:Settings).

ECU logging through the CAN bus works fine (and is blazing fast!). Excellent! The command line app also works. I also verified that extended (RAM variable) parameters work; I have the "Subaru CAN Enhanced RAM Parameter Logging" patch in my ECU, so the logger must be making use of it.

The TCU throws lots of errors, as it does with K-line communications. It generates them much faster with the CAN bus enabled, though I have posted the log in the TCU debugging thread: http://www.romraider.com/forum/viewtopic.php?f=5&t=9398

Thanks for this update Dale, esp for that of Can! Hope you get reading of DTC and Fine learning table correction implemented soon.

Really like the ability to log external sensors without needing the ECU. This will make it easier for RR to be used with third-party datalogging hardware.

Also, it's simply amazing how far RR has come over the years. These sort of projects renew my faith in humanity.

Hi,

Just to confirm, to utilise the CAN bus logging, i need the ecuflash can bus patch on my rom?

Also do I uncheck the fast poll logging if using Can Bus logging or does it override and use can bus logging as a priority

Yes the patch applied by EcuFlash is needed if you want to log any of the Extended 2-byte or 4-byte parameters.
Standard SSM parameters can be logged with or without the patch.

When CAN is selected the Fast Poll option is ignored.

Thanks. Hopefully even more cool stuff can be added to help you keep your faith

Thanks, keep up the good work!

Any information as to why the CAN bus based 2008 USDM spec.b doesn't have the CAN bus option working or patch available in ECUFlash? A2TB001L. The only references I can find are from other users wondering when/if the patch will be released.

I know that fast k-line is working within Romraider but there hasn't been support added to Openport 2.0 for that so I am stuck with 4HZ logging to SDCARD which isn't as useful.

-- Patrick
-- Dallas, TX

You will have to ask Tactrix about this.
I suspect it's not supported because the ROM code does not match a known algorithm and therefore is not detected as valid CAN ROM.

I'm glad to see that you guys are still turning out revisions. RomRaider keeps getting better and better! Keep up the good work!

Not sure if we have a 'Feature Request' thread, so I'll just post here.

Can we get the ability to pause the datalogger with the defrost button? So one can do several pulls etc. and only have the data be appended to one file? There could be two logging modes and the user could select which one they want. Defrost as Start/Stop or Defrost as Pause.

Or, is there an alternate way to take a bunch of *.csv files and auto compile them together? I guess an external program that does this would work too. It could just ignore the first row for subsequent files.
Found this program but holy crap, why is it almost 30MB?!
http://www.tucows.com/preview/1588452/J ... e-Software

There's a cheaper way to concatenate files...
On Windows use the copy command.
Then just open the file and delete the extra header rows in Excel or a text editor.

This is actually a huge change to the ECU Editor. It has been a while since I wrote this code so I will try my best to explain in greater detail the changes.

New table compare options

• Compare to original/bin value.
  
  • The original value is the value loaded from disk or from a revert point.
  • The bin value is the displayed value.
• Compare to Table.

Realtime Compare
Comparing to the bin value should update the compare as that bin value changes.
Example:

• Open 2 Roms (Rom A and B).
• Open the Base Timing table for both Rom A and B.
• From Rom A Base Timing table menu. Select Table->Compare->Compare to Table->"Rom B.hex - Base Timing"
• From Rom A Base Timing table menu. Select Table->Compare->Compare to->Compare to Bin Value
• Then go to Rom B Base Timing and change some values. The compare should update as the "Bin" values of Rom B change.

More Changes

• The compare now compares table headers.
  
  • I am not completely sold on this feature. It makes it hard to line up columns when comparing the cells of a table.
  • I will probably add an option to toggle comparing table headers.
• The table base and derived class structures has been updated. These classes handle tasks like...
  
  • Colorize - colors the cells in a table.
  • Highlighting - selecting cells.
  • Copy/paste.
  • Undo All and Undo Selected.
  • Compare

Enjoy.

Scotthew