Anyone worked with the 16196397 yet?

[kur4o]

Patch reconfigures one of the SPI comm byte that is used in ac routine. This byte is compared with 819d and 819c. Stock settings are $24 and $80.
$24=36 and is really close to the MPH you reported. $80 might be considered 50kp. Still not clear how one byte value will be responsible to mph and map at the same time. There might be some bugs in the SPi side of the patch.

Change these two bytes to ff and report result. If it doesn`t work I wll look deeper in the code

[Xnke]

The patch changes the MAP value from 1 bar to 2 bar-so what originally would have been a 100kpA value, is now a 50kpA value. That could explain half of it-the other half, I do not know.

Basically, the T-side does the MAP analog conversion to digital, keeps the baro value, and sends the raw map ADC value across the SPI bus to the E-side. Then E-side then takes the MAP ADC value and does the math to generate a 2-bar MAP value, and also a 1-bar emulated value to send back to the T-side for transmission control stuff-because there isn't room in the T-side to do the 2-bar MAP rework over there. (also the T-side does the inital ADC, but then sends it to the E-side for the math.)

The wideband patch just slots in the wideband ADC value to the SPI bus, and sends it to the T-side so it can be put into the normal datastream sent out to the laptop. All the ADC values and conversion is done on the E-side.

I'll give this a try tonight, and we'll see if it works tomorrow morning when I drive to work. (40 miles of highway driving, the A/C almost never works on the highway.)

[Xnke]

OK, so byte 819C is already in the XDF as the "N/V (tach/speedometer vss) ratio to use WOT Disable", and the stock F-body bin it's 36, in the stock L-body bin it's 101. Byte 819D isn't defined in the XDF yet, so what I will be doing is adding it as a new scalar, naming it "Possibly the MAP value to disable the A/C", and I will play with it to confirm if that's it or not.

[kur4o]

Did you manage to test it out? I got some other ideas too, if it wont work.

[Xnke]

So far, it hasn't seemed to have worked. I am still doing some testing but setting bytes 819C and 891D to FF have not fixed it. It hasn't changed the issue at all, best I can tell.

[kur4o]

The code can run with 2 different AC system. On f-body with evap temperature control and TXV. On front wheel drive platforms it is with orfice tube.

There is separate settings and code for each system and a lot of undefined parameters. What system are you using?

I suggest copying all the settings with the hidden parameters. If still not working logging string of bytes with mode2 through eehack raw command window might help figuring what commands AC off.

Some DTC set also switch off the AC

[Xnke]

I am using the orifice tube, without temperature control. I have the flags set as per an L-body car, which also used the orifice tube. (at least I set them by putting the L-body bin in the compare bin slot, then went through the F-body manual bin (the only rear-wheel drive configuration) and changed all the things that come up in a ctl-F "A/C" search to match the L-body orifice tube settings.