Entering Closed loop faster with $A1

[Schmieder]

i was getting that map code, should I try replacing the map sensor?


It's such bull crap that after I put everything back to where it was I still have this issue.

Don't feel so bad. I just had to replace my Battery, Fuel Pump, PCM, brake lines AND fuel filter just because the car sat longer then it should have. Was doing a manual swap, I doubted it would be longer then 3-4 months. I was wrong....8 months so far.

I would welcome such an easier fix you got....lol.....but I know, it's all in perspective and it sucks over all. Good Luck man!

[robertisaar]

Assuming they can not reprogram the PCM, wouldn't a specific rated resistor (wanting to reduce 1v from the signal line) trick the PCM?

It would fix the MAP issue if it wasn't a physical vacuum causing the stalling. But then the WOT readings would be off as well. So then the resistor wired in would need to be switched out of the circuit during WOT. At that point, it becomes an interesting DIY circuit board project.

WHo doesn't like to hack?

HORRIBLE idea... especially since A1 is entirely hacked, every single byte of calibration being adjustable as if we were GM calibration engineers themselves

[tkoforpresident]

your MAP code can actually be causing the stalling, since when the code sets, the ECM assumes what the actual MAP values are, and i assume those haven't changed from the stock values.

either you have a significant vacuum leak causing the MAP error, or the threshold for setting the error needs to be modified to account for the significantly lower idle vacuum.

I sprayed parts cleaner around every part of the engine bay while my bro sat in the car and the rpms didn't change at all (until I sprayed some in the ram air of course)

so I don't think it's a vac leak.

[tkoforpresident]

exactly what was happening with my car a couple weeks ago.

In the tunerpro Constants section, insert a new xdf constant.

Title, MALF 33 MAP Hi LImit
Units, Kpa
Address 04E2
Size 8 bit
Significant digits, 2

On the conversion tab change the equasion to: X/2.324


Once that's in OK it and close it out.. then open the item and it should be set to 70kpa, change it to 90 and run that bin. If it works then drink a frosty beer.

I think I understand the concept of what you're talking about dave but when it comes to actually changing all of this around like you say it's pretty much wishful thinking.

Can one of you change this in the .bin/.xdf for me? Or is it something I have to do myself?

[robertisaar]

have my TP V5 XDF(either the factory style or nAst1)? it should be in there, just do a parameter search(Ctrl + F) for "MAP Threshold to Set Code (KKPM33)"

[tkoforpresident]

but i'm using v4

[tkoforpresident]

I'm using your "myA1" .xdf for v4

[tkoforpresident]

the only thing coming up is "DE map threshold" is that it?

It looks like it's set for 16 kpa

[tkoforpresident]

here's a dumb thought, can I just disable the code?

sorry for all da posts.

[robertisaar]

actually, here's a quick way in V4: open up the hex editor (Ctrl +H), jump down to the 04E2 Dave mentioned, change the value to DC, close out of the hex editor, save the BIN and now it's set to only cause the code when the MAP is at 91.534kPa when in it's test conditions.

[tkoforpresident]

the hex editor is HUGE. How do i find 04e2?

and where do i change it to DC?

[robertisaar]

addresses appear on the left, scroll down to where you see 4E0(may have a bunch of 0s in front of it), the click the value two to the right. at the bottom of the hex editor screen, you should see "Cursor: (bunch of 0s) 4E2", that confirms you're in the right spot, then just type DC

[tkoforpresident]

ok hold on, this might take me a minute. I don't talk to computers in binary like you do

[robertisaar]

the TP hex editor is how i impliment all of my patches, by the way....

and i rarely have to go binary, hex works pretty well.

[tkoforpresident]

ok i did it and saved the .bin


just fyi there was an error when saving "one or more checksums could not be updated, check checksum addressing etc, for validity"



should i be worried?




if that's not a problem then I should be able to just burn a new chip and go datalog right?

btw, what essentially did we just do? Disable the pcm setting off the map code reguardless of vacuum?