RomRaider

Hey,

RR 0.5.4 RC1 got fast-poll sampling and logging, with is realy great for full-pull-looging at WOT.

I´ve also to log long time terms, like a active regeration of the diesel engines, witch lasts about 12 Minutes.
Even in normal logging mode, SSM-II protocoll will give you a lot values and a big size of data-output.

So, is it possible to reduce the logging frequenz by request, for example just saving every 5th or 10th value, with is send on the bus ?
In this way you also be able to log and handle (!) longtime logs e.g. using RR as a datalogger on a race-track

Best regrads Jochen

To decrease the logging rate just switch back to slow poll mode in the Settings menu, or select about 20 parameters to log and ignore them when you are conducting your analysis.

mhh,
ok this is a work-around, witch produces a lot of unuseful data and is uncomfortable to work with..

If this function is not a big work, I am very glade, to have this kind of functions in one of the next RC...

BR

Are you looking for a feature to set the logging rate based on parameter and break the parameter list into two polling groups, one fast and one slow?

No, not this kind of complicated.

In my case it is enough to reduce the "global" storing rate as a divider of the sample rate ..

For long time logging starge rates of 1 or 2 samples a second is enough..

So basically have a data capture rate of once every 500ms?

Yes, for 12 minutes log, this is enough an provides 1440 value eatch parameter...

In best case, you can choose the divider from possible maximum sampling rate (witch is displayes by RR).
So you can have e.g. 200ms, 500ms, 1000ms...

Looking for a cooldown behaviour of a DPF, 2Hz is fast enough for logging

I'd like to back that request.

Logging rate definded as sampling rate ("sample every X msec").
Let's say 10000msec being the lower limit and 0msec (max. possible data rate, no extra delay) being the upper limit.

I also tend to log fairly long.
I've got to watch for drift, other trends or seldom anomalies which occur more and more often with my old 1999 WRX.

Cheers
matze

Hard drive space is at a premium these days...

Make a lot sense to log cooling temperatures with 15samples a sec.

Bigger problem will be the evaluation of this data-mess, if you log a few minutes..
Exspecially, if you work with Excel.
If there is no decrasing function for logging rate, my request will be chance to have FAMOS as data-output..

Uhh, switch back to the default logger speed and log EVERYTHING! Then you won't have to scroll down as far to gauge trends.

You wouldn't like the logging on my system! The lowest rate it currently does is more than 90Hz, with the highest at 1kHz for a single byte parameter (though I think it could go faster still). I personally really like the fine grain logging. You can watch things like instantaneous RPM during cranking and see each cylinder lift the engine up and then it fall back a bit before the next one comes on the power stroke. Consider using something to visualise the data, rather than reading each line one by one?

I think you guys are missing the point of the request for a diesel specific application that occurs over 10's of minutes.

A good log viewer can show you an hour of data as a trace on a screen, though. You shouldn't really have to sift through it line by line. Or am I missing something unique about the data he's trying to view?

http://subdiesel.wordpress.com/ecu-anal ... anagement/
You don't need 100 samples per second for this 12.5 minute process. As requested 1 or 2 samples per sec is sufficient.