Can this be improved? Now rate is only 5 times per second which isn't really enough (I had 450rpm change between updates).
is there anything that can be done?
I've noticed that info is written every 1/10th of a second, but most records come in pairs with identical information - maybe this is a bug, fixing which we would get real 10times/sec rate?
Logging (update) rate
Moderator: Matt
Originally when this firmware was designed on the R31 the rate was much higher. But then it affected the operation of particular vehicles including the Z31
Every software interrupt that occurs we used to send all consult values in the table to the PC. It was very fast but affected operation
Now for every software interrupt only one consult value is sent over the USB line.
(More time spent inside the interrupt handler took time away from the ECU operation and affected injection)
I can raise an investigate item to increase the number of consult values reported and see what limits I can push without affecting vehicle operation. But this will require a firmware update and wont happen immediately until other problems have been resolved firstly
Every software interrupt that occurs we used to send all consult values in the table to the PC. It was very fast but affected operation
Now for every software interrupt only one consult value is sent over the USB line.
(More time spent inside the interrupt handler took time away from the ECU operation and affected injection)
I can raise an investigate item to increase the number of consult values reported and see what limits I can push without affecting vehicle operation. But this will require a firmware update and wont happen immediately until other problems have been resolved firstly
It is possible that the logger is oversampling the USB data.
- USB read loop is at 50ms (20 x per sec)
- Log playback/record loops are at 100ms (10 x per sec)
In theory with current data logging, you should be able to get 10 per sec. I can increase the resolution of the playback/record loops, if I can stop the data from being oversampled, by increasing rates
- USB read loop is at 50ms (20 x per sec)
- Log playback/record loops are at 100ms (10 x per sec)
In theory with current data logging, you should be able to get 10 per sec. I can increase the resolution of the playback/record loops, if I can stop the data from being oversampled, by increasing rates
We are now reading USB consult data and logging at 30ms. This is a good synchronisation time to also use with the wideband units
So we are sampling data at 33 times per second, but it depends on the rate that the ECU outputs also
Currently the firmware @ 3000rpm is spewing out the consult table data at 9 times per second on average. Higher revs might slightly increase the amount of data available to sample due to increased interrupts processed (consult firmware called more often)
I believe we have got close to achieving our target without modifying firmware further
So we are sampling data at 33 times per second, but it depends on the rate that the ECU outputs also
Currently the firmware @ 3000rpm is spewing out the consult table data at 9 times per second on average. Higher revs might slightly increase the amount of data available to sample due to increased interrupts processed (consult firmware called more often)
I believe we have got close to achieving our target without modifying firmware further
15:05:56.046 RX: CA 07 01 21 01 85 84 22 00 88 FF 61 80 44 02 A3 31 00 48 12 41 28
15:05:56.046 STREAM RX: 01 21 01 85 84 22 00 88 FF 61 80 44 02 A3 31 00 48 12 41 28
15:05:56.093 TX: CA 07
15:05:56.156 RX: CA 07 01 21 01 85 84 21 00 89 FF 61 80 44 02 A5 31 00 48 12 41 28
15:05:56.156 STREAM RX: 01 21 01 85 84 21 00 89 FF 61 80 44 02 A5 31 00 48 12 41 28
15:05:56.218 TX: CA 07
15:05:56.250 OnDisplayConsult: Refresh maptrace
15:05:56.281 RX: CA 07 01 21 01 85 84 22 00 89 FF 61 80 44 02 A2 31 00 48 12 41 28
15:05:56.281 STREAM RX: 01 21 01 85 84 22 00 89 FF 61 80 44 02 A2 31 00 48 12 41 28
15:05:56.328 TX: CA 07
15:05:56.390 RX: CA 07 01 22 01 85 84 21 00 89 FF 61 80 44 02 A5 31 00 48 12 40 EF
15:05:56.390 STREAM RX: 01 22 01 85 84 21 00 89 FF 61 80 44 02 A5 31 00 48 12 40 EF
15:05:56.437 TX: CA 07
15:05:56.500 RX: CA 07 01 22 01 85 84 22 00 88 FF 61 80 44 02 A4 31 00 48 12 40 EF
15:05:56.500 STREAM RX: 01 22 01 85 84 22 00 88 FF 61 80 44 02 A4 31 00 48 12 40 EF
15:05:56.546 TX: CA 07
15:05:56.609 RX: CA 07 01 21 01 85 84 22 00 89 FF 61 80 44 02 A2 31 00 48 12 41 28
15:05:56.609 STREAM RX: 01 21 01 85 84 22 00 89 FF 61 80 44 02 A2 31 00 48 12 41 28
15:05:56.656 TX: CA 07
15:05:56.734 RX: CA 07 01 22 01 85 84 22 00 89 FF 61 80 44 02 A4 31 00 48 12 40 EF
15:05:56.734 STREAM RX: 01 22 01 85 84 22 00 89 FF 61 80 44 02 A4 31 00 48 12 40 EF
15:05:56.796 TX: CA 07
15:05:56.843 RX: CA 07 01 21 01 85 84 22 00 88 FF 61 80 44 02 A4 31 00 48 12 41 28
15:05:56.843 STREAM RX: 01 21 01 85 84 22 00 88 FF 61 80 44 02 A4 31 00 48 12 41 28
15:05:56.906 TX: CA 07
15:05:56.984 RX: CA 07 01 21 01 85 84 22 00 89 FF 61 80 44 02 A2 31 00 48 12 41 28
15:05:56.984 STREAM RX: 01 21 01 85 84 22 00 89 FF 61 80 44 02 A2 31 00 48 12 41 28
Can't wait to check how it works - hopefully this week I will finish my car and checkMatt,
On the Type 3 ECU's the update rate is only 10 times a second in stream mode, is it possible to set this to around 30 times a second? Another consult program i use updates at 85 times a second and is great for logging but doesnt do wideband unfortantly.
Perhaps a user adjustable update rate would be good to accomodate for the various ecus?
On the Type 3 ECU's the update rate is only 10 times a second in stream mode, is it possible to set this to around 30 times a second? Another consult program i use updates at 85 times a second and is great for logging but doesnt do wideband unfortantly.
Perhaps a user adjustable update rate would be good to accomodate for the various ecus?