SD card logging AFR's are all .3

[TheSilverBuick]

I finally wired the datalogging switch input in and was doing some datalogging of today's drive where it runs rich climbing hills and when I finally got to my destination to download the logs to do some corrections all the AFR's were simply .3. I had tuner studio open during the logging (my LCD cluster) and the O2 sensor was reading normally and cleanly during these logging sessions. Is there a setting I missed in the set up? I bug that was reported and I missed?

I'm running the 1.3 Alpha 5 code. I trimmed the log down to make the file size cap, but it's enough to see what's going on with the AFR. The VE table is a tad funky at the moment because I was trying to track down my pig rich climbing hills problem (plus I wouldn't exactly call myself a pro tuner )

[jsmcortina]

I've seen something similar to this a long while ago when I tried to add too many fields to the SDcard dataset. Moving to TS sub-section in case Phil has any ideas.

James

[LT401Vette]

We did have something similar some time back that was related to the max record size being set 1 byte too long and the last byte getting stomped by EOF marker.
But that is correct in the current ini's and looking at your msq it looks like you didn't have full field set, only 42 bytes getting logged.

Do you have the MS3 file that came from?

[TheSilverBuick]

MS3 file? The s19 file?

(Sorry for the delay, my car broke something in the clutch set shortly after this post and I ditched the car in Denver to spectate Drag Week. Picking the car back up in a week or two, but I have my laptop and files with me).

[LT401Vette]

The raw .MS3 file is on the SD card before TS transforms it into a msl.

[TheSilverBuick]

Ah, okay. My LOG0004.MS3 file was just over the 716kb limit, but this LOG0007.MS3 taken the same day has the same issue.

[LT401Vette]

It seems the raw data in that MS3 file is x03 the whole way through, that would translate to 0.3:1.

So it looks like the problem isn't on the TS side.
The AFR1 channel is getting logged to offset 40 of a 56 byte block, so it shouldn't be running out of space.

I take it AFR 1 is reading fine on the gauge and normal data log?

[TheSilverBuick]

Correct. I have the digital dash going and have done the laptop logging and both read normally for AFR1 (per the output channel setting of the gauge in Tuner Studio).

I guess that begs the question, is it possible since I have a computer linked up to the MegaSquirt and running Tuner Studio at the same time I'm SD Card logging that it's creating an issue?

[jsmcortina]

I guess that begs the question, is it possible since I have a computer linked up to the MegaSquirt and running Tuner Studio at the same time I'm SD Card logging that it's creating an issue?

That should be fine. I do that too.

James

[TheSilverBuick]

Okay.

When I get the car home (in a week or two) I can play with/test it some more. As of right now all my files are uploaded in this thread. I'll be open to suggestions. I might try a firmware change as a test then.

[contraption22]

Good morning.
Sorry to resurrect an old thread, but I am having this exact same issue. Was yours ever resolved?

Thank you,

Mike

[Turbo nut]

I know this is an old thread but I also am having this issue. What was the fix?

[jsmcortina]

I know this is an old thread but I also am having this issue. What was the fix?

An important part of the fix was:

[Turbo nut]

2020-04-06_14.41.49.msq

(273.31 KiB) Downloaded 34 times

Here is the msq. it is a rough tune just getting sorted out. Datalog is to large I will have to cut it down. Ill post it shortly.

[Turbo nut]

2020-04-05_19_modified.msl

(218.05 KiB) Downloaded 34 times

Short datalog.

[LT401Vette]

Generally the fix for this is to go into the SD Logging dialog, remove a Field, the re-add it.
That will fix your SD logs going forward.

[shiftin04]

Generally the fix for this is to go into the SD Logging dialog, remove a Field, the re-add it.
That will fix your SD logs going forward.

That explains why mine started working all of a sudden. I accidentally deleted the AFR1 and replaced it and after that the A/F started working correctly.

[Turbo nut]

Thank you that fixed it for me also.