No I don't think there is currently any useful timing. Improve the realtime nature of the data is something I want to do in the future.
Something like a set of data per engine cycle.

FWIW I did some empirical testing of this a year ago or two (it was before the higher baud rate & BT) and as far as I could tell, I got a constant data rate from the ECU regardless of RPM. I don't quite remember now but I think it was something like 3 Hz - that is, three complete sets of data (each set consisting of three different kind of data strings IIRC) per second. I remember you (Cliff) said it wasn't really a constant rate - but in reality it was constant "enough" for me.

If I search a little (or maybe a lot) I can probably find some notes. It may even be mentioned on this forum. But it may be easier to just re-test it. Very easy, blocking read from serial port, print with hires timestamp. Ride it for five minutes like you stole it 

Today I could give the GSF Dyno a try. For me the easiest solution actually was borrowing an old ZEN V with Line In from my son and attach it with two wires to one of the spark plug cables (4cm parallel to the cabel and fixed with tape). Aim was to check if and how the whole thing works. I recorded 6 WOT runs in 3rd gear, varying only the spark advance by +- 10 % as I'm running the MyEcu closed loop actually. That means that the map was as lean again as it was before I started gambling with the BT module.
Here are the results:



It's not the actual max. values that count, nor is it really the form of the curves. The point is that GSFDyno seems to deliver constant values and so is an excellent supplement to MyECU and vice versa. Do 4 runs, change the map (quick and easy on the road), do another 4, change again and so on 'till you think it's enough. Then, at home or on the laptop in your buddy's car, you can see at once what change changed what.

Hubert

Please do I'd like to find someone I could talk to about my findings (or not-findings). You need a recorder with line-in. My HTC Magician unfortunatey lacks one.

The picture shows today's experiment:



The red curve is 20% more fuel in open loop (dark blue is my standard closed loop) plus 15% spark advance (up to 40deg - OEM still is 44!)

It seems that fueling is not that important once the map is smooth and around/below L=0,9. Also it looks as if these little Mivv Ghetto-Blasters are not the first choice power wise.

For those maybe interested in how it is done:

How the wires are connected

The other side

The recorder (get one now, they vanish)

Typical spark

Hubert

no, the lower 4 curves are the ones from the day before (sorry for mentioning the 6 runs). The green one sticking out is the result of these mentioned 6. The difference is the Mistral exhaust.

The original looks like that:

I have not, not the app and not an I-Phone.
But I have reinstalled the Quat-D over the weekend. Shouldn't have it removed before. Here is how the Mistral map works with the ExBox:

The nice thing is that exactly around the dip in the torque curve the map now is really lean. You can see the vertical blue bars. As the engine normally crosses the map from the lower left corner to the upper right one, I assume that the first lean column (positive compensation) leads to a rich one (negative comp.) and then to the next  really lean one. Looks a bit as if the compensation was oscillating.
For the next run I'll change only the lean areas a bit, tonight I then will see whether this will have a positive effect on the rich zones also.
Hubert