Anyone worked with the 16196397 yet?

[Xnke]

So I've made another terrible video for Youtube, to try and explain better what's happening here. I still don't have a clue what's going on, maybe VATS is killing it, maybe it's super rich, I can't tell.

The wideband shows 13-14 AFR's when it starts, but when it would normally shift to the running table, I can't tell what happens because the engine either stalls out and dies, or I have to pedal the crap out of it to try to keep it running. The datastream is wigging out the whole time too, at least I have a datastream. Unfortunately, I haven't kept it running long enough to accurately measure the *running* PCM voltage. I still don't think it's an issue, though, because swapping to unpatched stock code and a 1 bar sensor lets the truck idle and free-rev OK, as long as I've changed the injector flow constant and the blower is bypassed.

Fixing the voltage issue did solve the super-rich chugging issue where it would fill the whole lab with fuel vapor, though! Gotta take a win where I can get one.

[RobertISaar]

i can't make any sense of the datastream issues..... I've seen vehicles have issues before with this PCM, but they were solved with a single tweak to the ADX. is it still freaking out if you use scan9495?

[Xnke]

https://www.youtube.com/watch?v=nrXr...ature=youtu.be

There's a video of last night's work-I am building a little VATS module to test and see if that's the issue. Who knows, it's ten minutes to get one going.

Possibly another update tonight.

[brian617]

I am building a little VATS module to test and see if that's the issue.

Vats typically disables the fuel pump, how about monitoring fuel pump voltage/amperage to diagnose?

[Xnke]

VATS on the 94/95 camaros had a starter interlock and disabled the fuel injectors-not the fuel pump. Really, it's Passkey-II, not VATS.

I don't have the starter interlock relay, as the S-10 doesn't have one-so VATS can't lock me out of the starter. It could be shutting off the injectors, though. I don't really think that's the problem but it's easy and free for me to build the module to check it, so I'm going to check.

Gotta run down one thing at a time, so far I've got the voltage issue fixed, still don't have good data on the datastream, possible VATS shutting me down, could just be the tune is that far off.

Like I said, with a 1 bar MAP sensor installed and the stock tune, if I set the VATS scalar to 0 and the fuel injector constant to the correct 36lbs, the truck will fire up and idle. I've copied that table into the 2-bar patched code, but no dice so far.

Even with the 1 bar map/tune in the ECU, I still get the terrible datastream. Of all the datalogging I've done, I have one single 2 minute datalog of clean data-and that was with partially-patched code!

EDIT: I wonder if the oil level/pressure stuff is cutting it off?? The PCM has monitors for oil level and oil pressure, but I don't have wiring diagrams for these two sensors-The oil pressure sending unit is the camaro unit and is wired properly for the camaro PCM-I didn't rewire it at all. The oil level sensor isn't present on the truck and I don't remember what I did with those wires...that might be it, but it wouldn't explain why it runs fine with the 1-bar sensor.

I'm pretty much logic'ing myself into a tune-related problem, instead of a wiring issue-but then that doesn't explain the datastream freaking out like it is. Like I said above-one thing at a time.

[RobertISaar]

PCM doesn't monitor oil pressure, but it can monitor oil level(if the option is selected), but it doesn't modify run characteristics at all, only lights up the dash indicator. the way it operates is odd too, it waits for the engine to shut off, then if the oil level switch doesn't go from "low" to "not low" in a certain amount of time, it decides the oil level is low and lights up the indicator for the next start-up. if you're parked on an incline, you'll almost always get the light unless you have a very non-stock oil pan or are very overfilled on oil level.

[Xnke]

OK, Progress!

I scrapped the whole BIN file we've been fighting with, and started with the 1994 F body Manual revision 3 bin, from your archive Robert.

Stock, unpatched, untouched. Just burned it to the PCM. And the truck started, but was very lean and didn't run. BUT, I had full communication in both Scan94/95 and Tunerpro, withPASSKEY-II error.

Next, I edited the fuel injector size and configured it for 36lb injectors. Flashed it, started the truck, and full communication-and it kinda-sorta ran. PASSKEY-II error.

Hooked up the PASSKEY-II emulation brick I built. Fired it up again, still had good comminucation, and the PASSKEY-II error was gone. Still kinda-sorta ran.

Next, the Revision 3.01 patch. Still had good communication, still only kinda sorta ran.

Next, I killed off PASSKEY-II. Still good communication, still only kinda sorta ran.

Next, the Boost Patch. Unconfigured, I did nothing but patch the code and flash it. Still good communication, still barely runs without help.

Next, I configured the patch scalars-but I did NOT configure the flag to set the patch active. Still good communication, still barely runs without help. I knew I would be fairly safe running as no boost could happen and I broke the engine in this way and it ran for 30 minutes with reasonable timing and fueling-a little retarted on the timing and a little rich on the fueling, but it ran fine with a bit of throttle help.

Next, I set the patch active. The truck still runs with a bit of throttle help to keep it going, and still communicates with Tunerpro-no big data error problems but only 3hz or so. And then I go back and look at the logs...Yeah, something is seriously wrong. A few examples...

Engine speed, 58.00 RPM. Actual somewhere around 1200.
Vehicle speed 130 ??? Sitting still, parking brake on, in neutral.
Spark advance? A cool 24201 degrees...plus or minus a thousand.

So, now that I have good data communication with no errors, albeit at a low data rate, I have completely bonkers data. I've attached the relevant information below-I am so hoping this is ADX related and I can start tuning soon!