RomRaider

Oh sweet! That led to some google searching and I guess this will work too and take less typing.

Just downloaded and installed. I will give it a work out tonight. I had been having troubles with the logger freezing on the last build. Hopefully this will cure that!

Thanks again for all the hard work!

Josh

I made a handful of runs with this tonight and it worked flawlessly! It seemed to run much quicker than the previous edition and no freezes.

Thanks I will report back after further use

Josh

Bug report: The compare function does not correctly detect differences in DTC enablement between roms. It lists the tables, but the changes are not highlighted. I have enabled DTC that were disabled but it doesn't show the change.

Also, on my laptop I only get a list of changes, nothing more, and clicking on a change does nothing. What are the 'left' and 'right' meanings if there isn't a second window showing the changes?

Finally there is almost certainly some for of RAM leak in the app, probably objects that are not properly trashed during file parsing is my guess based on timing of the ram bloat. opening up multiple roms quickly bloats the javaw.exe, and closing roms does not recover much ram at all.

I have one instance where ram leak led to a fatal crash due to memory exhaustion, but I have quit the app before repeating, as i lost my rom and I had to delete all the config files to get Romraider to work again (acutally, reinstalled but the .Romraider dir was corrupted.) I have the logs and .Romraider confs that were bad if you care.





-- Patrick
-- Dallas, TX

Spectr you pretty much nailed it. you make me want to go grab my laptop and do some work.

The image compare is a small tool that I wrote because I quickly got tired of comparing every table. I use the getTableAsString() function to do do this compare. This attempts to compare tables with the same name. This is not the way to do an image compare but I didn't have to write any code and this function was already there. There is definitely room for improvement here.

Yes. It is there.

This application used to be single threaded. Basically you could only ever load one rom at a time. In previous version the UI would hang when performing long running tasks (opening, saving, compare, copy, etc.). I moved some of the long running tasks onto a worker thread. However, this does not mean that loading an image is any faster or takes less resources.

If I remember right this loads all of the images at once. This could be changed to load one at a time.

All,

I finally got my Tactrix cable fixed (Tactrix is amazing by the way. I Highly recommend this company) and found time to work on this.


No RAM Leak found. Opening a Rom does cause the Java heap to grow because loading a Rom is memory intensive. This is hard to answer without going into detail about how the JVM works but the heap space is allocated during the loading of the Rom. I have confirmed using VisualVM that the memory is released properly. However, the heap does not release the allocated memory once it has been allocated (see VirtualAlloc function, and virtual vs physical memory).


This is a case of just because you can doesn't mean you should. Opening up multiple Roms quickly is probably not a good idea. This will bloat the Heap size. If the first loaded Rom has not completed then this heap space will not be released. If you follow quickly with opening up a second Rom while the first is still loading the mem from the first load has not been released and more will need to be allocated to handle the new open. This means that opening multiple before it has finished will cause you to run out of heap space (among other possibilities like too many Roms open at once). There is command line arguments you can use to increase the heap size. I added a call to run GC after the open and close is completed to help release the mem from these operations.

When I find time I will update the "Image compare" and "Save as Repository" to be more useful and use something like the bin values to do a true compare and not the getTableAsString() function with a string compare.

Scotthew

Hey All

I came across a issue that's driving me up the wall and down the otherside...

I had RC5, it was working fine and well, I came across a 2011 STi, after changing a few things to get it to read from LV as well as the correct logger profile for the car (new logger)

Since then I am still able to connect to pre CANBUS ecu's and log, but for whatever reason the Innovate plugin will not connect anymore, I have reinstalled Romraider and now using RC6, I can confirm the cables etc all work as I can open the Innovate software and read the unit, log the unit and program the unit, it's a Innovate MTX, it works with the LC-1 plugin.

I've also tried reinstalling the Innovate drivers and software etc... no matter what I try it is not interested in reading...

Has anyone else had this issue??

Thanks!!

I was having tons of issues with the innovate plugin as well. Getting it working initially wasn't problematic aside from waiting eons for it to respond after selecting the port, but about half of the power cycles from reflashing required a full restart of RR, otherwise it would read flat. The usual tricks of reloading profile, changing ports, etc didn't always work.

If you are still having problems I suggest you submit your system log file so we can see what's happening.
http://www.romraider.com/RomRaider/HowToDebug

Hi There dshultz

sorry, i should have actually done that first.

I had already started getting verbose logs when i read your post.

Ok sooo.... after much installing, re-installing back and forth trying to see what i had updated, i also saw i had updated java version 7 25, so i removed that and reverted to version 21. I also went back to trying Romrider RC 5. Just to see if it gave me any joy, no joy :/

I got my hands on another laptop, clean laptop, i had re installed it a few days ago. this laptop is windows xp, versus my windows 7. I installed java update 9, 21 and 25, no difference, i tried RC5 and RC6.

I have discovered something very interesting, using Version 25 of Java and RC5 on Romraider, although i cannot see the figures in the Romraider screen when selecting innovate, i do see the figures filling up in the verbose log.... :/
I have the same issue in RC6. If i do anything ECU related, there is no issue at all, figures are there and working... i only use the innovate as a plug-in, so not sure if other plugins might have a similar issue.

I have attached 3 log files below.

Thanks for taking the tie to look at this. it defiantly has me confused.
I can confirm the cable work, the gauge works and it all works in logworks3 from innovate, this includes the tracing of AFR. i now know that romraider does see something according to the logs...

Thanks again!!

In all the logs you have no connection to the ECU that I can see, correct? If that's the case the only way to see the plug-in data values show up in the Logger display is to uncheck both the ECU and TCU checkboxes on the toolbar. See note #2
Or establish a usable connection to the ECU and then the plugin too.

If you have no plans to use any of the other plugins then just move all the unused plugin files out of the RomRaider\plugins directory and just leave in the ones you wish to use.

I have not seen any issues using the most recent version of Java 7 (32bit).

Hey

Yes correct, i was only using the Innovate to try get it to work, the previous night i have ecu connected, but it was giving me issues still.

I'll try with the machine i had the successful logs on and see if that works, ive never unticked the ECU block because i always generally have the ECU connected regardless.

Thanks again for your help on this. i will let you know how it goes.

Hey

I tested on the laptop that i had the successful logs, this time i had to install ECUFLash to get the tactrix drivers.

i get the following error in the logs.

103562 INFO [Thread-7761] - Connection closed.
103562 ERROR [Thread-7761] - Innovate Wideband AFR: connect error
com.romraider.logger.ecu.exception.NotConnectedException: com.romraider.logger.ecu.exception.SerialCommunicationException: Port is currently in use: COM7
at com.romraider.io.serial.connection.SerialConnectionImpl.<init>(Unknown Source)
at com.romraider.logger.external.innovate.generic.serial.io.InnovateRunner.serialConnection(Unknown Source)
at com.romraider.logger.external.innovate.generic.serial.io.InnovateRunner.<init>(Unknown Source)
at com.romraider.logger.external.innovate.generic.serial.plugin.InnovateDataSource.connect(Unknown Source)
at com.romraider.logger.external.core.GenericDataSourceConnector.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: com.romraider.logger.ecu.exception.SerialCommunicationException: Port is currently in use: COM7
at com.romraider.io.serial.connection.SerialConnectionImpl.openPort(Unknown Source)
at com.romraider.io.serial.connection.SerialConnectionImpl.connect(Unknown Source)
... 6 more

even if i reboot and then retry i get the same error :/

i have attached the full log as well

not sure what to try from here.

Do you have some other application open using COM7, do you have more than one plugin item set to use COM7?
The Innovate MTS Logworks3 driver will also check all your COM ports for sensors, so if you don't want to use the Innovate MTS plugin, remove it (lm2_mts.plugin) from the RomRaider\plugins directory.

Try unselecting the Innovate AFR from your logging profile and save it that way. Close the logger, delete the rr_system.log file to clean it out.
Restart the Logger and or computer.
Connect to the ECU. Once you have stable readings then set or reset Innovate AFR to COM7 in the Plugins menu. Then switch to the Externals tab and check the Innovate AFR item.

FINALLY!!!

After trying all sorts of different combinations, i had a friend with a LC-1 come over, tried connecting to his, it worked first time with no issues.

I pulled the battery off the car to hard-reset everything, thought pattern was to hard reset the gauge.

Connected everything back and it worked first time...!!!

I'm assuming it was to do with the gauge not being happy, but hard to say as it was working through logworks, i removed logworks and all other applications that might touch the gauge and it still wasnt working.

Thanks for the assistance