What I have noticed is with Firmware 1.06 I have always had a issue with O2 correction and decel related issues which has forced me to stay with version 1.00. (software 1.07.4)

I decided to give 1.06 a go again for some troubleshooting and found something interesting. The O2 correction seems to reference the external MAP sensor when it is set to use the internal MAP sensor in the unit.

My setup is like the image below. You will notice that my MAX MAP is set to 0.0 kg/cm. If I leave it like this then I have no O2 correction. ie: at idle I see the O2 Correction 1 and O2 Correction 2 sitting at 0 constantly when it should be adjusting in relation to the target AF table.

If I set MAX MAP to what the static non connected external map sensor value in "Calibration MAP Sensor" is which in my case 0.65 kg/cm then I will see O2 correction on both banks. This tells me that the O2 correction is referencing the wrong MAP Sensor values because what is happening is that the ECU is seeing 0.65 kg/cm for MAP and saying that it is greater than 0 kg/cm.

On face value it appears the correct MAP values are used when tracing on the Fuel/ignition maps etc

Has anyone else noticed this or I have over looked something. Keep in mind that on v1.00 with the same values my O2 correction works correctly. Also the engine is warm and exceeds the values in the startup time and minimum water temp.

Any ideas?

 

would really like to know this too i have these values

i

 

I do remember an issue with early firmware with the O2 control not working if the max map was not a positive #. Not sure what's going on with v1.06 for you - it seems your issue is reversed. Weird.

 

There was a problem with this at one point, though not anymore. It is possible/likely your map was built from that bugged map. If I remember correctly, your o2 input(s) are coming from something custom wired as well (not through the o2 inputs), so you may have problems there as well. You should talk to whoever setup this up for you and/or tuned the vehicle.

 

HAL/Raj not sure if your comments were directed at me or the other poster. Anyway in my case O2 feedback works fine if I use a external MAP sensor. i'm not sure about the buggy map as I'm pretty sure I built my 1.06 from the base map in the 1.06 software. ie: typed in my values manually for all cells, not imported.

I have the newer harness where the O2 sensors are using the AMP breakout connector and that is why i built the map from scratch

 

MR RIZK-
We recently ran into the same issue on a customers car using the Haltech. Car is an 06 5AT 350Z, running ECU Manager 1.07 and 1.06 firmware. It would not go into closed loop fueling no matter what we tried. We double checked all of the settings, and everything was set up properly. We are using the internal MAP sensor and the 0v-5v output of an LC-1 as wideband input. We tried various 'Max MAP' settings in the wideband control menu, and nothing worked, even with it set at 14psi boost.

Tonight, I decided to try setting the 'Max MAP' setting up to the maximum allowed value of 58psi and FINALLY, it went into closed loop.

 

Chris, When u monitor channel "Calibrations - MAP Sensor" what is the value returned. In my case it was 0.65kg so if I set my MAX MAP to anything over this close loop worked.

Easy test to see if it is the same issue as mine just buy a GM Delco 3 Bar external map sensor and wire it in. The Haltech has a CAL file for this already. Set the unit to use the external sensor and disconnect the internal senser vacuum line.

In my case when I did this I could set the MAX MAP to what ever I wanted and closed loop works as expected.

I hope this helps you as it puzzled me for months.

 

Chris@FSP, check your email.

 

Now I understand what you're saying. I have used closed loop successfully with the internal MAP sensor though. I do have an external now because it responds faster to throttle changes that the internal (perhaps because of the shorter tubing) - datalogged both in action.

 

From what I know the shorter the line the better as you have indicated. I have seen some go as far as plumbing the sensor directly in.

 

Out of curiosity, what decel related issues did you have with 1.06?