RomRaider

I have seen screenshots of people getting 19 queries / sec but I am only getting 2.0-3.5 without ANY parameters selected. It makes me feel like less of a man

If you are getting more queries than me, what MY is your car, what are your pc specs, what cable are you using, and did you do anything special to get the queries / sec higher?

I get about 2.0-2.5 with my sl0w thinkpad with 512 mb of ram and 1.8 ghz single core. I get around 3.0-3.5 with my work laptop which is a dell latitude with 2 gigs of ram and over 2ghz dual core. I am using the tactrix 1.3 cable and I drive an 07 wrx.

I use a 1.4ghz laptop with 1gb RAM, but the hardware doesn't generally matter. Usually the limiting factor is the 4800 baud connection speed for SSM. That's like mid-1980s dialup modem speed.

I get 3-4 lines per second with my default logging profile, which has about a dozen parameters.
If you select only a couple of parameters, 10 lines per second sounds do-able.
If you select a ton of parameters a few seconds per line (not lines per second) is probably possible.

That said, if you're getting two different logging rates for the same log profile (same set of parameters) then maybe the 512mb needs to get upgraded to 1gb.

How much difference does it make selecting only parameters which can be read on the CAN-bus? Is it possible that it's logging parameters which have to be read on K-line that slows things down?

I don't have a CAN-bus car but it's my understanding that logging still goes over the k line even in those cars.

Interesting. I am playing with logging direct to microSD, and using the standalone application posted here to create the config files. That has radio buttons to choose either K-line or CAN protocol, and I understand from other users' posts than the data from RAM addresses can only be read via the K-line. IME, trying to log (for example) the FLKC values when set to CAN mode results in no logs at all, so it does seem to make some difference. I was expecting that live data from sensors could be read via CAN and would be faster.

Thanks for straightening that out!

If you have no parameters selected the ECU would not be queried at all and the rate would be a leftover value from the last logged parameter as you de-selected it.

The 4800 baud is the limiting factor. For each standard parameter you choose to log the Logger sends 3 bytes of info to get back 1 byte of info. What that means is 4 bytes of info has to traverse the signal line to/from the ECU. At 4800 that's about 8 milli-seconds per parameter (not including the query overhead).

The best I've seen is 65msec (about 15 samples/sec) with just RPM (and defrost switch) selected.
Adding four more parameters drops you to about 6.5 samples/sec.
The situation would be much better if we could increase the baud rate. Going to 9600 baud would allow you to record three more items, 7 total (with 1 byte return values) at 15 samples/sec.

There has been some discussion about how to log at a higher rate. The switch to the higher rate seems easy enough. But there is a problem with going higher as ECUflash is not currently compatible with a higher rate and that would lock you out of flashing without an elegant way to go back to the default 4800.

Don't think me yet, I have no idea how things work with the OP 2.0 and microSD logging... haven't tried it. Colby (Mr. Tactrix) knows a whole lot more about this stuff than I do, and he probably put that CAN option there for a reason... I just have no idea what it is.