RomRaider

That might be a solution, thanks.


It already does that. You could press the record button and drive around for hours if you stay away from WOT, nothing will be recorded. As soon as you go WOT it starts recording and stops when you hit the max RPM you set. If you drop out of WOT before you get to the max RPM it will just ignore the non-WOT data. In this case you must press the record button again to stop it, then press the recalculate button. But you might want to reduce the max RPM a bit before you do or you'll get some weird stuff happening at the top of the curve when it tries to extrapolate past the known data.

Cheers for the clarification. I was not sure what data was being used in each run - just assumed it was using whatever data was being recorded as soon as you pressed the button :p

I'll give it more thorough testing this weekend and post a few screen grabs, and if I have time, I might even do a little vid with basic instructions for using it

Leslie

Not sure why, but it seems that it is recording all data and not just WOT data and this is causing some weird results in the dyno graph. Here is what mine ended up looking like after I had finished the WOT run:



Also, when I click record on the dyno rab, then switch over to the Dashboard tab to monitor knock and afr while doing my WOT run and then switch back to the dyno tab, the dyno tab has not started - it seems that for the dyno tab to function, it has to be the one being displayed when you start the WOT run, which is a problem for mist as they will want to monitor knock and afr at a minimum while doing a WOT run.

Leslie

Ignore the above, it seems that it is some type of issue with the zip version of RomRaider and not the patch. I reinstalled using the exe version of RomRaider and everything works correctly now.

Leslie

Hi:
Maybe attach the romraider.log file from your install dir.
I'd be interested to know what it was reading...
Dale

Hi Dale,

I have a habbit of only using the zip version of release candidates so I can have several on my laptop at a time for testing/using. However, since the latest zip version did not work with your modified jar file, I deleted the folder and reinstalled the latest release candidate from the exe.

So unfortunately I do not have the log any more - sorry mate. To reproduce, maybe download the latest release candidate in the zip version and then copy/paste your modified jar file to the extracted folder - then when you run the bat file to launch RomRaider editor and open the logger from their, you should get the same bug.

I've had no bugs/problems with the exe version though - all working as expected. Only real gripe (and it is little) is that it would be good to see if knock is occurring while Dyno window was open/focused (FLKC and FBKC indicators would be great).

Leslie

It's not in your recycle bin is it? Maybe next time then. I log all the samples gathered for the dyno there, prefixed with "DYNO Sample". You can even extract them for later analysis if needed.

That's exactly how I've been testing it before I post it here for review. I use WinXP.


Aren't you supposed to be watching the road
A better option would be to check those indicators on the Dashboard tab and set the "Warn Above" to something above the current value so you have an audible warning while you are doing the test.
At the moment I don't see an issue with doing this or switching away from the Dyno tab while in progress, but I'll double check it.

Thanks for all your help.
Dale

I did a check of v4 on my car. I set Knock Sum with a warning, then started the Dyno, while stopped and switched back to the Dashboard. I then proceeded from a stop to third gear and went WOT a bit after 2000RPM. It all worked as expected and plotted after it hit 6500RPM.
I do need to fix my text placement though... The dual axis is screwing that up on me.

I'll check tonight. If it isn't, I'll reinstall from the zip file and try and redo the bug for you (and post the log).

Same, win xp on my EEEPC - I was also logging FLKC, FBKC, ITT and load during the WOT log - maybe it has something to do with logging parameters on the "dashboard" tab, while performing a log on the "dyno" tab?


My passenger (wife) monitors things while I drive


I didn't even think of this - great solution - I'll check if it works tonight


After the weird bug I got (as posted earlier) I had to log in the background and keep the "dyno" tab opened for the "dyno" tab to work properly - so that is how I have been using so far. TBH, after I reinstalled using the exe I haven't tried to set the "dyno" tab to record and then monitor the "dashboard" tab while doing the WOT log. I'll test that tonight as well.


All good mate

Leslie

Ah sweet, I'll just do this then from now on. I'll be doing some logging tonight, so I'll try the things I mentioned above, and just generally test it out

One thing I have noticed is that the graphs plotted on the "dyno" tab are quite different to those plotted in Airboy's spreadsheet. Overall whp is different (even when using the same interpolation factor) and the graph shape is quite different too.

When I get home tonight I'll post a screenshot of the "dyno" tab and a screenshot of the same WOT log in Airboy's spreadsheet to show you what I mean.

Leslie

Yes it will look a bit different, less jagged.
In the spreadsheet the raw time and smoothed (using a linear trend) RPM are used to calculate vehicle speed. Then acceleration G's is calculated and also smoothed, linear trend again. Then power and torque are calculated.
The smoothing is required as the raw data is very noisy.
What I'm doing is capturing the raw time and RPM. I then calculate the coefficients of a polynomial where the degree is selected by the user, default 9, for each, time and RPM.
After is have the coefficients I then interpolate the time and RPM from the polynomials, this smooths out the raw data. With the smoothed data I proceed to calculate the vehicle speed, acceleration G's, power and torque. In the spreadsheet the higher the smoothing number selected the more sampled values are used to predict the linear trend of the data.
On the Dyno tab a higher number increases the degree of the polynomial and therefore becomes less smooth as the poly tries to match the noisy data more accurately. I think 9-11 should be good for you. If we had more samples, 300+, then you could increase that to 15 or so and still get a good curve.
Here's a shot of the data points un-smoothed and a poly line based on that noise. Not pretty

You can emulate what I'm doing on the Dyno tab in Excel with the linest function, that's were I started actually.

New test version attached to post topic39-34.html that fixes the results placement on the graph. It also reads the Atmospheric Pressure and IAT immediately after you complete your WOT run and uses those values in the calculations, so no need to set those fields anymore.

Dale, do you want commit access to the repository so you can contribute this work? Even if it's just a branch to begin with.

Let me know!

Thanks.

New test version rd-v7 attached to post topic39-34.html
Changed data collection to be strictly based on Throttle Angle. So once you press "Clear & Record Data" you can drive around and get setup for your run. Once the TA is over 98% the data will be recorded until TA is less than 98%. This works better for automatics. The RPM min and max will be updated to reflect the start and end reads of your WOT RPM.
This version also takes into account the Logger units of measure for ATM and IAT.
They are read and converted after you complete your WOT run and uses the values in the calculations.
NOTE: the ATM pressure is used in calculations, the elevation it reverse calculates is for information only and changing the field will not change the "recalculated" results.
IAT could be higher than ambient temperature by quite a few degrees, so you can set it and recalculate if it's way off.