RomRaider

bchslap,

when you used the MAF/Injector tab, did you try logging another set of values to file in the other tabs at the same time? I tried that and my MAF tab showed a weird scale. I had to click on "Reset Data" before the axis on both scales went back to normal.

No I never tried it like that. I'll do some more testing today, and see what happens.

Kascade
I used v.033, and just tried it on a 16bit ECU (2001/02 JDM STi V7 RA Type C - ag970 3391- A4RG0500 )

Using the LM-1

The MAF tabs works... i totally forgot to try the injector tab though ... sorry.

The only thing i noticed is if you press “record data” and then you press “record data” again to stop it, and if you press “reset data”, and want to start to “record data” again it would not log/record again. (no dots). I had to restart RomRaider, (not just the logger) to get it going again.

Great work man... thanks again.

Dweeb

That's weird. Anyone else experiencing this? I haven't had a problem yet with this.

Mine works fine.

I will try to replicate it again, later on during the week, when I have time. Will let you know...

02 usdm wrx
vista laptop

I tried to replicate this on my way to work this morning using rev033

I did NOT have any problems stopping data and restarting it on the MAF tab.
I recorded some data, stopped recording data, interpolated, reset the data and was able to restart recording data. (It would be nice for the recording data button to indicate off/on status)

On sunday though, I was able to have an issue with closing the command prompt box that runs in the background. I had done some maf tab recording, finished that went to exit the rev033 logger and then rev033 romraider, and the command prompt box didn't close on its own.

I had to end the task with the three fingered salute. Only time I've seen that so far, so take it with a grain of salt.

dm

I had this issue, quite a bit, when I used my Vista laptop.

I got tired of Vista issues, so I resurrected my old XP laptop and dedicated it for tuning.

I only have problems re-recording again after I click on the button "Update MAF".

I'll try it in a few minutes.

*knocks on wood*
I've only had this problem once with this latest test release.

dm

I tested this scenario 4 times this afternoon, and cannot duplicate it.

I do, however have some problems (probably me) with the MAF interpolation. I am thinking it's due to not enough data, but I logged the maf for about 10 mins idle time in my driveway, and tried interpolating. It would not. I had to drop the interpolation to 6 (from default 10) to get it to interpolate, or at least display the line..

p/s/ I also vote for some sort of "recording/logging" flag to be displayed when doing so. Reason is, it's hard to glance to the laptop and determine whether or not I've actually started/stopped/restarted the recording on the MAF/INJ tabs. I have to look to see if the status bar shows "querying..."

I'm not bitchin, by ANY means I'm just excited about the whole damned thing, actually!

Yep, you need more data over a larger maf range for the higher interpolation levels.



The record button itself is a toggle button so when it's "on" it should remain depressed. Clicking again to turn it off will raise it again. I can understand this could be a bit hard to discern from the driver's seat. A red/green indicator is a good idea.



no problem, all feedback is appreciated!

Sweet, thats what i figured..

It does remain depressed, but when I'm on my way home, and logging, the sun shines on the screen, making it that much harder to decipher.. A quick visual queue would absolutely ROCK!

Sweet. I'll do all I can.

Now, I'm off to osecu forums to try and find out why I get the BSOD every so often. Happened saturday, and again this afternoon..

Quick question:

Does the 'Overlay Log' function require a 'current' logging? I guess a better asked way, is: Can, say, a log that was don today, and saved, be overlayed on a table to see the touched cells?

(or do I need to delete this and move it to another thread? )