Configuration Warnings, Etc

[R100RT]

Brief project background - BMW boxer motor bike 980 cc has been run for several seasons with an Edis ignition set up, which I wasn't confident was delivering proper ignition. I upgraded to MS2/ Extra at end of last riding season, changed over to a GM DIS type coil set up plus a Bosch ignition module to fire coils, etc.
I wanted to upgrade to extra code to gain ability to view composite logs in Tuner Studio and was able to confirm nice results during a couple of final tests (idling bike etc.)
Apart from those changes I wouldn't have expected much else to affect my best MSQ, but I believe I have offended the tuning gods again.
Regardless, after a careful reload upgrade to lates TS version MSV1.006, and subsequent reload of firmware MS2/Extra release 3.2.1 (20111211 14:40GMT) I find I may need to start over, also have the following warnings.
This first image is during log onto Tuner Studio (and I don't have flex fuel enabled)

DSC02118.JPG

The next image occurs during log viewing on MGlog viewer

DSC02119.JPG

I also upgraded to a new Inovate "MTX-L" air fuel ratio kit, but I believe that utilizes the same calibration settings that my older "LC1" utilized so I believe I can trust the AFR readings I am seeing.
If anyone has time to look at a starting log file/ MSQ I can post that too.
Thanks for any comments.
Lorne.

[LT401Vette]

That first one is interesting... That setting that is highlighed as changed is a bit that shares bits with other settings on the same byte. The other setting is different and causing it to come up as different.

So most likely flexportRemote "Remote sensor port" is set to something different.
Does it not go away if you select "Use Controller Settings"?

BTW, the handling of bit fields on difference reports was change a good time back in the beta, that will soon be released and will resolve this.

On the MLV prompt.

There is no O2 field in the log to calculate AFR from and you don't need it, AFR is already in the log.

To get rid of the prompt; on the main men select:
"Calculated Fields" --> "Wideband O2-AFR" --> "Off (Default)"

[R100RT]

Hi Phil,
With that TS warning, I chose "Use Controller Settings" a couple of times opening TS and confirming MSQ, and each time the same prompt came up.. It of course goes away with that choice, but then comes back next time. To load that firmware I actually cleaned my old Dell of every old saved files and early firmware files, loaded the MS2/extra serial 3.2.1 fresh, and upgraded TS to 1.006 @ same time. This was with MS ecu removed from the bike and plugged into a spare harness that has most wires terminated, with a 12v battery for power. I don't think that would be a factor.
The only remotely close alternate port I am using is the boost control tables, through the "FIDLE" green wire (actually controlling my water injection pump).

So the O2 prompt can be assumed as a non issue and just turn off as indicated? Just never seen that before in the 4 seasons I've been running logs.
Thanks for help.

[LT401Vette]

Can you post your msq?

I would like to see if I can reproduce that difference report here, then be sure it is handled in the beta.

[R100RT]

Hi Phil, here is an MSQ and data log during last starting attempts.
Perhaps I can also mention a couple of things to qualify these "woe fully inadequate" states of tune I seem to have fallen into.
Perhaps you (or anyone else) may care to comment on a seeming lean cold start (actually unable to warm up enough or smooth out to gain even an extended idle) As can be noted, both the VE lower bins, and various of the WUE and ASE charts have been pulled this way and that to offset what seems like a "die off" subsequent to taper off time out.
Keeping in mind I had developed a seemingly drivable tune back with B&G2.9 over the previous 3 years roughly. I've tried populating charts and files both by export/ import, and populating manually without much difference for about 4 tries now to climb out of a pretty rough and challenging (for me) outworking. Not sure it is just my move to MS2 Extra 3.2.1, or some hardware upgrades and associated changes to tune (cardinal sin to change more than one thing at a time without a doubt but felt it was manageable)
Any comments appreciated as always.

Lorne

2012-04-25_20.28.05.msq for EFI.msq

2012-04-24_19.08.56.msl 7th.msl

[LT401Vette]

Unfortunately I don't seem to be able to reproduce that error with that msq and 1.006...

It may just be something in the steps you took getting to these settings?

It would be nice to verify it is handled with the beta version.

[R100RT]

Well I believe I will try the Beta version then.
I may also have to back up and try my last good B&G2.9 firmware and msq to take some of the unknowns off the table. Nice that we can go back and forth at will.