MSefi.com read only forum (Jan.15,2018)

I have MS2 on a v3 board running the 2.89 code. I just switched from a NB O2 to the spartan wide band from 14point7. After installing the sensor and wiring I went into TS under Tools and Calibrate AFR. Per the Spartan data the liner output is 0v = 10afr and 5v = 20afr. Under Fuel Setup I switched EGO control to Wide Band. Under Other Fuel settings I have tried Combined VE/AFR and Seperate VE and AFR for WB.

When running the vehicle the AFR gauge in TS seems to be working fine. My trouble is when I go under Basic Tables and try to put in target AFR's it comes up as a Lambda table. When I use the tools to generate AFR's it seems to come up with reasonable starting numbers, 14.7 around idle, low load area around 15.1 and in the 12's for full power. When I click on Apply - AFR Table (Map) it loads all "2.000" everywhere in the Lambda table.

I was thinking I should end up with a table of target AFR's and my VE table could be adjusted (using VE analyze or Autotune) to hit those rations. Do I have something wrong with my settings in TS or is this working the way it is intended?

Thanks. Brian.

Post your msq. I am thinking this is a setting problem.

Ken

Thanks. Here is the msq file.

I tried reloading the 2.89 code and got the same thing. So next I tried loading the latest code, 2.92, and still got the same issue. I have always been curious about the MS Extra code so I loaded that and it seems to be working. So I am going to give the extra code a try for a while.

Brian.

Just got a chance to take a quick look at your msq and a couple things jumped out at me..........

In Project Properties, Lambda Display is set to Lambda which will make TS display in Lambda in stead of AFR......
Also in Project Properties, Ego Sensor is set to Narrow Band.....

Just a couple things I noticed.........

Ken

Thanks for looking Ken. I did switch to single wide band, I must not have saved it after one of my several reloads.

I did not know there was a setting in Project Properties that set it to show lambda. What I don't get is, after using the tool to build an AFR table and loading it, why did the lambda table come up with all the same number. I would have expected it to use the AFR vaules I put in when calibrating the AFR tables. I got all 2.00 or 2.89 in the whole table after trying to build the table several times.

Thanks again for looking at my msq file.

Brian.

Brian,

I cobbled up a test project using TS 2.4.02 beta (and 2.0.8 release) using both 2.89 and 2.920 B&G firmware along with your msq. In both cases I was able to create completely normal AFR tables, using the TS table generator. What I was not able to do, is duplicate the issue you describe. Perhaps one of the guru's will come along and lend a hand.

My only suggestion would be to maybe reload the most current code (2.920) and have a go with it....... Otherwise I'm not sure where to go next.

Sorry I could not be more help!

Ken

I couldn't edit my last post, so here is that edit.........

EDIT: Got it!!!
In Project Properties, with EGO O2 Sensor set to Narrow Band and Lambda Display set to Lambda---I ran the Table generator, clicked Apply and voila! All cells were set to 2.000! It seems to do the same thing when entering values manually also.
When I corrected the settings (ie. wb and afr) and re-ran the table generator, I got a normal AFR table.
My suggestion, is to set the wb & lambda settings in Project Properties properly and try again.
I have no idea if this is a TS issue. Maybe Phil will stop by and take a look.

In the mean time I have attached your original msq with the proper settings in Project Properties and an AFR table that I generated for my engine. It probably is not correct for your engine though! Don't use it! I only included it to prove my point!

Hope that helps a little!

Ken

Great work Ken.

Thanks.