0.5.1b RC4 Download!

Wideboy · **Joined:** Wed Feb 06, 2008 11:40 am **Posts:** 5

kascade wrote:

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.

+1 for this

ev8siv3 · **Joined:** Fri Mar 24, 2006 3:14 pm **Posts:** 671

LM-1 is working, just has a funky initialization sequence

Check LM-1
Activate LM-1 from dropdown and choose comport
Uncheck LM-1
Recheck LM-1

Turbo_Mike · **Posted:** Fri Oct 17, 2008 12:41 pm

merchgod wrote:

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).

True. I was thinking the same thing. If the list had all possible parameters and then turned off some of them based on the ECU it detects, or conversely if nothing shows up until the ECU is found, either way would be less confusing than the current list that just appears.

highrider · **Joined:** Fri Mar 07, 2008 11:17 pm **Posts:** 7

hi,

My setup is:

XP2
RC4
Latest defns updated
OP 2.0
MY07 EDM Forester

I can't get ECU Logger to work, ie. it doesn't connect to the ECU nor read data UNLESS I first start up under "SSM" 'launch Test Apps'. Once the 'Test Apps' window comes up I click to launch ECU Logger in the main RR window and it works!!

Does anyone have a workaround.......it's tedious having to execute 'Test Apps' and wait for a long time before that opens and I can activate the ECU Logger.

This is a carputer and I disable all the anti-virus etc programs.........

appreciate any suggestions/help.........cheers........ :wink:

And btw GREAT WORK Kascade, Merchgod, Colby and all you smart fellas!! THANK YOU!

hawke · **Joined:** Wed Feb 15, 2006 9:44 pm **Posts:** 16

Tried going from 5.0 to RC4 and keep getting "RomRaider is already running" on windows XP. Tried rebooting, logging on/off, reinstalling, disabling a few services and startup programs with msconfig, but still not having any luck. I went back and forth between RC4 and 5.0 and 5.0 continues to work fine, but RC4 still pops up with "RomRaider is already running". Looks like RC4 changed the port where is listens for romraider.

I used netstat and found PID 2860 is listening on port 50001. Does anyone know how to tell what PID 2860 is? or how to take care of this?

lizzardo · **Joined:** Sat Jan 06, 2007 1:18 pm **Posts:** 49

hawke wrote:

Tried going from 5.0 to RC4 and keep getting "RomRaider is already running" on windows XP. Tried rebooting, logging on/off, reinstalling, disabling a few services and startup programs with msconfig, but still not having any luck. I went back and forth between RC4 and 5.0 and 5.0 continues to work fine, but RC4 still pops up with "RomRaider is already running". Looks like RC4 changed the port where is listens for romraider.

I used netstat and found PID 2860 is listening on port 50001. Does anyone know how to tell what PID 2860 is? or how to take care of this?

Yes, the port changed. It's now 50001 instead of 54321. You don't mention what O/S you're running, but regardless, the PID is the Process Identifier, and is assigned by the O/S when the process begins. It is probably going to be different every time you start the application. If you are on Windows XP, hit Ctrl-Alt-Del and call up task manager. On the menu bar, select View-> Select Columns, and then check the box next to PID. Now you'll be able to tell which process is using that PID. RomRaider shows up as javaw.exe. On linux, from a command prompt type

Code:

ps -ef |grep 2860

and you'll information on that PID.

hawke · **Joined:** Wed Feb 15, 2006 9:44 pm **Posts:** 16

CommAgent.exe it's part of Webroot Spy Sweeper. Kill it and it starts just fine. Any way to make it use a different port or am I stuck killing the process if I want to use RC4?

lizzardo · **Joined:** Sat Jan 06, 2007 1:18 pm **Posts:** 49

There is not currently a way for the user to define the port. It's hard-coded and compiled in.

kascade · **Posted:** Sun Oct 19, 2008 5:23 pm

What port should it use?

lizzardo · **Joined:** Sat Jan 06, 2007 1:18 pm **Posts:** 49

The port is in the "dynamic port" range. Thoughts on having the instance of RomRaider start at 50001 and keep incrementing until it finds a port it can open?

This would allow multiple instances of RomRaider to be running, so there could be collisions. If that's undesirable, it would mean a more sophisticated mechanism than just checking a fixed port, but it might be worthwhile, since no ports above 49152 (inclusive) can be registered, i.e. they're up for grabs by dynamically.

bmw5002 · **Joined:** Sat Feb 03, 2007 3:58 pm **Posts:** 151

will the linux version ever actually be usable on os x? there are a few bugs that really kill the usability:

progress bar for opening roms flickers - must be some kind of redraw problem
opening roms takes WAY longer than when im running romraider via my windows emulator
tables dont have a close button - going to the menu to close each table window gets old fast
will not open a second rom at all when one is already open - appears to be processing then shows "ready" with no result

i havent even tried logging yet...
it might also be a nice touch to allow the open dialog to be like the standard os x open dialog with the sidebar showing the drives available and such.

and why do i want romraider for os x when i can use it via my windows emulator? simple. i have problems with the drivers and ecuflash - sometimes it works, sometimes not. there is an os x version of ecuflash available which works beautifully. having to switch between windows and os x chokes up the workflow while tuning. so if romraider could coexist peacefully with ecuflash and excel on os x, my life would be complete, and i wouldnt have to use my windows emulator.

Tgui · **Joined:** Tue Jul 11, 2006 9:25 pm **Posts:** 992

kascade wrote:

What port should it use?

Considering some of the strange issues going one here, how would you feel about breaking the logger into its own stand alone Jar? Could cut down on threading issues (if there are any). I love the work you've done and am torn between writing my own simple logging app to support my needs, or help/doing/waiting for a stand alone solution. I'd prefer to stick with your good work. With the realtime support *slowly* working forward I see a collection of applications comprising the RR arena.

I'm not entirely sure the extent of integration with RR, but it might be beneficial to more than just me to break this out and have some sort of programmatic interface to pull and listen to real time data.

Just a thought, I don't want to branch and or step on toes.

wrxsti-l · **Posted:** Tue Oct 21, 2008 6:07 am

Tgui wrote:

kascade wrote:

What port should it use?

Considering some of the strange issues going one here, how would you feel about breaking the logger into its own stand alone Jar?

Wouldn't doing this stop the MAF and inector tabs from working - as in, they will still log as expected, but won't be able to write changes back to the open ROM?

Tgui · **Joined:** Tue Jul 11, 2006 9:25 pm **Posts:** 992

wrxsti-l wrote:

Tgui wrote:

kascade wrote:

What port should it use?

Considering some of the strange issues going one here, how would you feel about breaking the logger into its own stand alone Jar?

Wouldn't doing this stop the MAF and inector tabs from working - as in, they will still log as expected, but won't be able to write changes back to the open ROM?

Not if there was still a programmatic interface.

tmarcel · **Posted:** Wed Oct 22, 2008 9:57 am

ev8siv3 wrote:

LM-1 is working, just has a funky initialization sequence

Check LM-1
Activate LM-1 from dropdown and choose comport
Uncheck LM-1
Recheck LM-1

I'll have to give this a shot. Aside from one of the stranger OP 2.0 issues that I've got right now (working with Colby on a fix) this LM-1 logging problem is just icing now

kascade,

Any chance this will be worked out in a future release? The LM-1 definitely connects to any available com port as the LM Programmer has no issues at all. Thanks for all your work.

RomRaider

0.5.1b RC4 Download!

Who is online