Significant bug in TS?

[AlexLTDLX]

I've gotten most things working at this point, but for the life of me I can't get SD card datalogging to log AFR. I'm using the AFR2 in on the MS3x expansion board. Is there a way to log AFR2 in SD card datalogging mode (i.e. am I doing something wrong)? Or is this this indeed an oversight?

[LT401Vette]

I take it you did add AFR2 to the Selected Data Log Fields under:
Data Logging --> SD Card Datalogging
?

Do you have an msq?

[AlexLTDLX]

I thought I'd be clever and try to find AFR2 as well - the thinking being maybe the AFR SD data doesn't follow the routing from tuner studio, though it's undocumented. To my surprise, there is no AFR 2 in the list. There is "AFR 2 Target" and "AFR 2 Error," but no AFR 2. I'm attaching my msq file here.

I should clarify - I'm only running 1 o2 sensor, hooked up as AFR 1, wired in through EGO 2.

[LT401Vette]

You have Number of Sensors set to 1 under:

Fuel Settings --> AFR/EGO Control.

[AlexLTDLX]

Yes, that is correct. I have 1 sensor, and it is connected to the EGO2 input. I can log AFR just fine via serial port, simply by looking at "AFR" in the log viewer. SD logging AFR doesn't work - there is no data there. Why would it work in serial logging but not in SD card logging?

[LT401Vette]

If it is logging as AFR with a normal data log, that is what it should log as with SD logging.

Try Going into the SD logging Dialog and remove a filed, the re add it, while connected to the MS3 of course.

Then try another log and see if it has data in the AFR channel.

[AlexLTDLX]

Ok; I just did that - but I couldn't remove "AFR" from SD card logging - in fact, there were a number of individual parameters that could not be removed (I don't know why - I can only guess). So I removed everything and re-populated the SD card datalogging. Then I ran both a serial and an SD card log simultaneously - lo and behold, it magically seemed to work! I'm attaching both datalogs here - the car wasn't running at the time, so it recorded AFR as 19.9. But that means it's reading something. The SD log is #12; the serial log is the other one. Any thoughts as to why you can't remove certain fields from the log?

I'll confirm at the track tonight - a laptop connected inside this car becomes a lethal projectile while racing. I had an entry ticket (i.e. a small piece of paper) on my dash I forgot to remove once. On launch, it shot straight to the back window and stayed there until I hit high gear (two speed powerglide).

[LT401Vette]

It wouldn't remove because there were other fields added that depend on it, probably AFR Error.
Just the attempt would have corrected the set fields on the MS3 though.

[AlexLTDLX]

So I got the track last night - everything seems to be working as expected - thanks! Now, how do I get rid of that lean spike and rich bit right after I floor it:



Here's a video (notice the AF gauge doesn't agree with the log):
https://youtu.be/M7p1_khAssI

[LT401Vette]

Most of the AFR Gauges have a great deal of lag built into them, so you will not see nearly as much as in a data log.

Minimizing the AFR swing there is a matter of AE tuning.

http://www.msextra.com/doc/pdf/html/Meg ... 3-175.html

[Supernova_6969]

hey.

I had a mean lean spike after I'd give it gas..

I tried a bunch of things and couldn't get it better (i'm FAR from an expert).

yesterday i tried setting up the X-tau, and read somewhere that it could help with this issue (Iamonst other; I also had a rich spike when i'd let the gas go). I set it up real basic, and I think it got better. I still get a small spike but nowhere near as bad (say, 15-16 instead of 16-17).

I think i'm on to something. only problem is I don't know how to refune the x-tau settings, and I'm running into other issues at the moment.

check it out. let me know if it helps

S.