Small wins

VETuner currently runs this sort of sequence

graph TD;
A[Write To ECU] --> B[Wait];
B --> C[Read Data From ECU];
C --> D[Process ECU Data];
D --> A;

The Wait and Read steps account for 93% of the cycle time during which VETuner is twiddling it’s metaphorical thumbs. However this means we can do the processing bit for ‘free’

graph TD;
A[Write To ECU] --> B[Process ECU Data from previous read];
B --> C[Wait];
C --> D[Read Data From ECU];
D --> A;

This strictly speaking means that the UI will lag one read behind reality, but as all the data is timestamped it will have no impact on logs or analysis and it has the benefit of about a 10% increase in the read rate because there is no pause between the read and the follow write.

Now to make this idea actually work…..