RomRaider

Hi guys. Just starting to use RomRaider & got the latest download off the net. This tool looks real nice & I would like to use it for data logging.

I've opened up the ECU logger, hooked up the green connectors under the dash and plugged in the USB cable to the laptop & OBD cable to the car.

If I start the car & press the start button, I get an error saying "COM1, with protocol: SSM, and connection timeout: 2000ms.

I have 2 USB ports out the back of the PC & using either seems to make no difference. Top dropdown box on the eculogger screen is set to COM1 & I get the same error if I pick COM12. If I choose the one remaining option (COM3), I get an error saying "Parameter queries must not be null or empty"

I have an ADM 02 WRX manual and have had some difficulties also getting ecuflash to talk to my ecu but got it working eventually. Just this logging bit to go and I could have a nice set up.

Anyone got any advice on this issue & how I might sort it out?

You only want the green flash connectors connected when you're using ECUFlash/ECU Explorer to flash or read your ECU.

I did look at that but you know, I just had no luck with getting the ecu to talk to ecuflash unless I had the white plug in. I guess that out of frustration, I was willing to try anything (within reason).

The good news is that since the last post, I have finally got some communication happening again (by setting up the com in ecuflash first) and then just firing up RomRaider, going to the logger and trying it on the 3 com ports available to me. COM12 works ok. YAHOO!

Now, I have just taken a couple of streams of data (just at idle in my garage while I learn about this cool bit of kit), but cannot find where the data that has been read is being stored. Must be sitting in a csv file somewhere I guess but I haven't found it yet. Any advice here?

Lastly, I clicked on a bunch of things that I want to log and was hoping I could save those things to a file that I could select from later. Is that what "save profile" is for?, it's just that when I did that, closed out of RomRaider and then restarted, although I could see the profile, and select it, the fields that I had preset did not return....

Gee I love this thing so far though........Can't wait 'till I become dangerous with this little bit of knowledge!

Hey qoncept, just re-read your note......Pulled out the white flashblock and you're right....RomRaider still does read fine. But I thought the white flashblock connector had to be connected if you wanted to flash your ecu....(not that I want to right now). What have I missed here?

No no, I didn't mean the green connectors are the ONLY thing you should have connected when flashing, I meant the only time you should have them connected is when you're flashing.

You need to select the rear defogger switch in the lower left parameter list for this. you can then start/stop file logging by turning on/off the rear defogger via the button on your car's dash. the resultant file will be in the RomRaider install directory.



yeah, the profile stuff is screwed in that release. try downloading and testing the latest logger-only test release in the logger thread in the development forum. hopefully should be fixed in there...

Hmmm.....I selected the Defogger switch in the lower left panel, and defogger does come up in the main logging panel, but cativating the switch with IGN on has no effect, either to turn on logging or to change the field value in the log. More experimentation maybe....

Still can't find the log files created. What is the file extention? Maybe that will help me find them. I did look in the RomRaider folder and the only files I see written with today's date are the settings and profiles.xml files

Getting closer.........

Finally got the logging and defog switch thing working. I also finally found the csv files! Stupid me was expecting the defog switch, once selected on the bottom left panel to start and stop the logging. I mistakenly believed that log start/stop was indicated by the log running indications at the very bottom left of the screen.

I didn't realise that that running bit just means the signals are being read (when you press start) and that the pressing of the defog switch actually passes those values thru to a file. DOH!

Anyway, I will go away and have a play now and I thank everyone that put pen to paper to help sort this out.

And I have looked over 10/14 pages on the logger so far and you guys putting this together are doing a mighty job.

Now if only we could find Bin Laden.........

glad to hear you got it sorted. download the latest test release at the end of the logger dev thread and let me know how it goes. no more start/stop buttons so hopefully should be less confusing!

OK. Will do so now.

You know, this is the other good thing about being on XMAS holidays & the wife is at work...

When she comes home from work, I gotta make sure I've got my story straight about what I've been doing. It's 40 deg C down here in Albury today so I can't use the old "I've been working in the garden".

I'll just have to tell her that the car needed some maintenance work (which it doesn't).

Now, where is that latest download.....................

Hi Paul, just letting you know how I went with trying the latest logger test version.

Downloaded, unzipped into a fresh folder sitting within the main RomRaider folder and fired off run-win.bat

On trying to communicate with the ecu, I had no luck.

I am looking at the cmd.exe log file. I want to copy & paste it to this post but don't know how. Can you advise?

Key points on the log are:
- Error loading user profile: profile.xml
- Once the query manager starts, I get "Error 0x5 at /home/bob/foo/rxtx-devel/build/..src/termios.c(860): Access is denied
- COM 1 currently in use (I later changed this to the correct COM 12 but did not fix anything).

Any clues here? Keen to help you if I can.

Not sure why but communication to the laptop fell over causing the last issue. I seem to have to establish communication first with ecuflash first, and once that is successful, I can successfully link RomRaider. Is that right?

I'll have more of a play with trying to get the logger to initiate the communication with the ecu on a fresh session.

So far, so good...

you shouldn't need to start ecuflash first. have you installed the tatrix cable drivers correctly?

I tried uninstalling the drivers using the uninstall utility, then tried reinstalling but no change. If it is the driver, then why does the device driver summary show OpenPort to always be connected? It is as though the computer says "Yes I can see that a cable is plugged in to this port", and yet RomRaider seems to be unable to access it once I have set the COM port to 12 (in my case),

Is there another driver I could try? I could uninstall the driver again, delete all the files in the driver directory (which sits under the ecuflash folder) and try again.....

Maybe I'm not uninstalling properly? Is there a better way you can suggest?

sounds like you've done the right thing. i'm not sure what the issue could be, as i've never experienced it first hand. can you post up what is printed out to the windows cmd console from the logger?