Here are the new test results. The missing tests with the S3 were not useful. It may not be clear to everyone looking at the attached pdf's but these are excellent results !
The red color coding of the text does not actually mean bad - see below. With #define CAM_REMOTE_HIGHSPEED_LIMIT 0
the results are exactly what they should be.
If you look a the value of "s" and the reported timing values, they are almost exactly correlated. At s=1000, the values reported are in mSec. When s=2000 the values are in mSec/2, when s=5000 the values are in msec/5, and when s=10000 the values are in mSec/10. Likewise the values when s=500 are mSec*2. And when s=250, the experiment fails because the interrupt rate was too high ( or s=500 for the older S3).
I suppose it would be possible to have the CHDK code scale the reported results prior to making them available to the script but that's extra processing that's really unnecessary if the script writer is aware of what changing the value of "s" does to the reported values.
If Werner_O was to redo his spread sheet and prescale the measured values relative to the value of "s", I don't think there would be any red text.
A big thank you for the tests goes to Werner_O from the German CHDK forum.
I'd like to say thank you as well. Excellent work !
I think its time to enable this feature in the 1.3.0 trunk unless anyone has an objection?