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

New Release tonight. Here is a list of the changes:
VE Analyze Live:

• Added Heat Maps to show how well you have covered the table and how much the cells have changed.
  Changed Advanced settings layout a bit
  Added a button to get to your AFR target table even if they are disabled.
  Added support for Volt based AFR table (only occurs on MS1 extra & Hires)
  Added MS1 Base support
  Fixed MSII Base code bug
  Added TS based AFR Target table and AFR table Generator, However there is no way to activate it other than editing the ini file yet.
  Fixed Send going to controller but not to local Tune.
  Fixed AFR Interpolation for the recommended table tooltip.
  Added Dead Lambda Sensor Filter - Will filter any records that are at the min or max of the presented range.
  Added Warning if you are closing TS or restarting VE Analyze without sending previous recommended table values.

Gauge Clusters:

• All clusters display offline message
  The Basic Readout now honors Warning and Critical colors - Warning!!! This might cause a problem on your dash. If you are using a standard LED or Analog Bar Dash, I have already gone through and corrected them, so just load them again. Otherwise you may need to go into designer mode and set the warning and critical color to something more appropriate. Remember you can multi select by holding the CTRL key and change all of them at once.

MS3:

• CRC Checking to insure local data is always in sync with the Controller after all writes and burns.
  Also Use the CRC checking on initial interrogation to skip full page reads. This makes the initial interrogation a good bit quicker.

Other:

• Changes to Comms Timings - Mostly for improvements in MS3 and MS 2Extra 3.03, but please report if there is any negative side effects with any others.
  Comm Warning message and offer to stop polling the port when it doesn't exist (As in when a USB cable is unplugged from the computer)

I think that is about it, but I'm sure I forgot a few things

I updated to this version but had issues using VE analyze live. A copy from neons.org:

I used VE analyze live for a few days going back and forth to work and it made it horrible. It made it so lean that it was almost undrivable!

I recalibrated my WB controller then upgraded TS, but didn't recal my WB, TPS or MAP in TS. The MAP and TS are spot on and the WB looks close but it's hard to tell because it moves so fast.

My map was good befor with only a couple of lean spots I was trying to clean up with the analyzer, but it made them LEANER, along with more of the ve table around it. I was driving at a constant rpm for minutes at a time and watching the WB controller peg on full lean 16:00AFR and never move. I would glance at the ve map and the cells would never change. They would only change if I ran up through the rpm range and didn't stay on one cell. My AFR table was checked before running the analyzer and it's at 14.7AFR everywhere below 100kpa where I was tuning.

What gives?

MS2. I was asked about PID or simple O2 correction, but I don't know what that means. I have O2 correction "off" by setting to 0 for the alowable correction.

From what I see It will disregard when the AFR is at max scale and that may be the issue, but that really doesn't work for me(or anyone else with a NGK Powerdex possibly) because the max lean AFR read/output by the controller is 16.00AFR. It's too close to switchover for it to work well if you disregard it.

I was also wondering if you added the correction to the NGK Powerdex calibration code in this version or if that may be my issue?

I didn't recalibrate anything(TPS, MAP or WB) after updating TS, but wasn't sure if I needed to.

That is a good point on the 16:1, I would think it would be ok. But it would be throwing out a lot of data. Maybe that should be user selectable for those circu
stances. Or maybe I could put a range to where that wasn't active.
Btw you can disae that with an ini edit. The ini is in the in. Dir and which one depends on the firmware.

I'm wondering the correct shutdown procedure after a run with VE Analyzer Live. I see it writes to the ecu periodically. Do I need to stop corrections? Save the tune? Or is this already being done with the perceived writes to the ecu? Have you written instructions for the new features I'm not seeing somewhere?

Great work, by the way. It has made my car drivable very quickly.

Actually I still don't have instructions yet , I will soon.

If you have the "Update Controller" Checkbox Checked, it will periodically send the corrections to the controller.

However, it will not send a Burn Command until you click Burn or write to another page.

So that is really the main Shut down item to keep an eye on, You will want to click burn before you turn power off to the controller or exit TunerStudio.

I know this thread is a little on the older side, but...

What about Acceleration Enrichment? Should it be turned off for VE Analyzer Live to work properly?

What about Acceleration Enrichment? Should it be turned off for VE Analyzer Live to work properly?

No need, AE records are filtered and to some extend it is good to have your AE fuel factored in to some regions of the table.
That does mean you may need to run VE analyze again if you alter your AE settings, but that will get you to the best tune usually.

Great, that's good to hear. I'll re-enable AE tonight and try to figure out why I'm still getting pinging...(it appears that I may have wired my trailing coils backwards...but we'll see)