Megasquirt Support Forum (MSEXTRA)

I understand that the composite logger is shown in pages because it's actually captured in a RAM page in the processor and only sent once the page is full, but why do we have to review the data in pages, and not as a continuous stream of teeth?

The reason I am asking is that there always seems to be a sync loss right at the end of a page or the beginning of a new page, making things a little difficult to diagnose.

Thoughts?

Displaying it as continuous data wouldn't work, because it isn't continuous data.

James

Yes, there is a discontinuity in the data / lost data between each page read, so something needs to indicate that discontinuity.

For the Engine Data logs, you can load those in MLV and it will display in a continuous fashion with a MARK to indicate each point of discontinuity.

LT401Vette wrote:Yes, there is a discontinuity in the data / lost data between each page read, so something needs to indicate that discontinuity.

For the Engine Data logs, you can load those in MLV and it will display in a continuous fashion with a MARK to indicate each point of discontinuity.

A red MARK line like in the datalogs would probably go a long way.

Isn't there a way to use two pages so that we can store the live data in page 2 while reading back pages, and vice versa? The composite logger is great and extremely useful, as long as it doesn't add to the confusion of an engine losing sync, either randomly or in a specific manner.

There isn't enough throughput to keep up with most of these functions with the current RS232 connection. If page swapping would fix it, we would be able to just run a steady stream. Now put in a bigger pipe, then we can stream it.

By my reckoning, the potential data is up to 3x the existing serial bandwidth.

James

It took me quite a while until suddenly oneday I figured out there was more data available 'hidden' out of sight on the other pages.

Ok, could a saved log be viewed as a single page when opened then?

Reverant wrote:Ok, could a saved log be viewed as a single page when opened then?

For the tooth and composite logger view that would require significant changes.