Wideband AFR in logfile?

[Talkiet]

Hi all... I have bought a car with a Megasquirt 2 MSextra 3.1 in it and am having a ball driving it and now looking into the ECU...

I have an Innovate MTX-L wideband AFR connected to the MS and through tunerstudio it's happily displaying matching values (after some mucking about with the output curve on the MTX-L) to the gauge.

I then fired up Shadow Logger on my phone and again, everything looked fine, values were being shown, even the AFR was again accurate. Started logging, went for a drive.

Used TS 1.19beta to convert from the binary .FRD file to an .MSL file and loaded that into MegaLogViewer.

Here's where I come unstuck. I couldn't find the AFR value to graph, and when I looked at the MSL file in Excel, I couldn't find it there either. Does Shadowlogger save this value and it was stripped by Tunerstudio in the conversion or has it been converted to another value that I am not recognising and has to be calculated by MLV for display?

Cheers - Neil G

[LT401Vette]

AFR should be in the log. A log from shadow logger should have the same fields as a log captured by tunerstudio with the open project

[Talkiet]

AFR should be in the log. A log from shadow logger should have the same fields as a log captured by tunerstudio with the open project

That's what I thought too, and what everything I read suggested... However I can't find it... This is going to be a slightly messy paste but it is the 2nd and 3rd row of an MSL file from shadowtuner.com... I see 'O2' there but it's static at 0.48. There's 'AFR Target 1' but I have to believe that's from the ECU as a target. The AFR is correctly displayed in realtime on the shadowlogger app and agrees with the MTX-L

Time SecL RPM MAP TP O2 MAT CLT Engine Gego Gair Gwarm Gbaro Gammae TPSacc Gve PW DutyCycle1 Gve2 PW2 DutyCycle2 SparkAdv knockRet ColdAdv Dwell tpsDOT mapDOT IACstep Batt V deltaT WallFuel1 WallFuel2 EAE1 % EAE2 % Load Secondary Load Ign load Secondary Ign Load EAE Load AFR Load EGT 6 temp EGT 7 temp gpioadc0 gpioadc1 gpioadc2 gpioadc3 gpioadc4 gpioadc5 gpioadc6 gpioadc7 status1 status2 status3 status4 status5 timing err% AFR Target 1 Boost Duty PWM Idle Duty Lost sync count Lost sync reason InjTiming1 InjTiming2 PW3 PW4 VE Trim 1 VE Trim 2 VE Trim 3 VE Trim 4 RPMdot XForce(g) YForce(g) ZForce(g) AccelForce(g)

0.048 112 1558 48.7 0 0.48 75.5 119 9 100 98 109 100 106 100 46 1.791 4.7 46 1.785 4.6 23 0 1 3 0 15 133 14.5 0 0 0 0 0 41.5 0 41.5 0 41.5 41.5 504 462 0 0 0 0 0 0 0 0 24 0 0 0 0 -6.1 14.2 0 52 1 0 0 0 0 0 100 100 100 100 0 0.004 0.77 0.649 0.007

Also interestingly, I cannot for the life of me get GPS co-ords in the file... Again the docs mention they should be in there along with the accelerometer data. GPS was turned on and locked. (Galaxy Nexus with ICS 4.0.3)

Regards
Neil G

[LT401Vette]

It looks like your TS priject is set to Narrowband in the Project Properties as it appears to be logging O2. So if you log directly with TS it would create the same log.

Press CTRL + P
then click on the Settings tab

The GPS data is not yet there.

[Talkiet]

It looks like your TS priject is set to Narrowband in the Project Properties as it appears to be logging O2. So if you log directly with TS it would create the same log.

Press CTRL + P
then click on the Settings tab

The GPS data is not yet there.

Oh cool - Thanks for this... I bought the car already setup and tuned so don't have an intimate knowledge of the setup yet... I'll look into the project settings... I presume that just flicking the project to Wideband won't actually affect the behaviour of the ECU (The tune ignores any O2 input and in fact when I got it the O2 sensor was disconnected (and had been tuned this way).

CHeers - Neil G

[Talkiet]

I tried this... With Tunerstudio open and connected to the ECU I edited the properties and changed it from a Narrowband O2 (Yes, it was set as that) to a WB and saved the tune then closed the project.

Reopened, started the car, logged from Tunerstudio and yes, the AFR field was being correctly logged in place of the O2 field previously.

Tried Shadow Logger again and same O2 field was still there.

Had an aha moment and uploaded the new MSQ tune file to shadowlogger.com and then exited the app on my phone, restarted it, waited for login and then took another log through shadowlogger.

But still it's logging the O2 value, not AFR.

Am I correct in thinking the app picks up the tune settings (and therefore the existence of a WB O2) from the MSQ file I uploaded to shadowtuner.com? Or is there some other magic being worked where it interrogates the ECU?

Regards
Neil Gardner

[LT401Vette]

Ah yes, if you let shadowtuner.com do the transformation from frd to msl, it is a different, but similar story..

You would need to do just what you did, update the msq on ShadowTuner.com

However, any logs already transformed on ShadowTuner.com would still carry the old fields. So you would need to upload the frd again from your phone.
You shouldn't need to capture a new log in Shadow Logger, just do a long press and select Upload Again.
It will run the transformation on it again when it get there.

ShadowTuner.com still has a very basic UI, It certainly doesn't walk your through it very well yet, but that will improve.

[Talkiet]

Only partial and confusing success here...

If I use TS 1.20beta to log then I get the correct AFR field logged.

If I use Shadow Logger 1.05 to log and TS 1.20beta to convert FRD to MSL, then the MSL file has the correct AFR field.

If I use Shadow Logger 1.05 to log and let shadowtuner.com to the conversion, THAT MSL file still has the O2 field instead of AFR (And the value is always 0.48v)

I believe I have uploaded the most recent MSQ file to shadowtuner with the WD O2 sensor specified. Is there anything else that I need to change in the setup for shadowtuner.com to pick up the AFR properly?

I do have a workaround (using TS to convert) but I do like the concept of shadowtuner.com so much - makes things so simple. I just walk in from the garage, hit F5, and open the file straight into MLV...

MS2 Extra 3.1.0 with Innovate MTX-L WB. Confirmed that Tunerstudio shows the correct AFR values in the dashboard, and so does shadow logger.

Cheers - Neil G

[LT401Vette]

Your ShadowTuner.com project does look in order now.

I think I have a theory on what is wrong though...
In order to convert the log file, ShadowTuner.com literally loads a TunerStudio project less the ui stuff.
Projects are cached so they do not have to be reloaded for every log file, the project cache is set quite large at the moment.

It looks like when you uploaded your new msq, the old loaded project was not flushed from cache so the new settings are not getting used..

Give it another shot, it should work now.

[Talkiet]

And that has fixed it!

Thanks for your help... Just bought MLV a couple of days ago and looking forward to having a good play...

One question before I take it to a new thread... Can I concatenate HEAPS of driving logs (being careful about headers etc) to help with the VE Analyse in MLV? Put another way - is more data always better?

Cheers - N

[LT401Vette]

Actually you can open multiple logs at once by opening the File Open dialog, then holding down the CTRL key and clicking on others or use the Shift key to select from 1 file to another.

More data is good, but isn't always better... At some point the data starts to have little added value, it is coverage of as much of the table as possible that is good and sometimes more data will get you that.

Just remember to make sure all the data was captured with the tune you have loaded.