Entering Closed loop faster with $A1

[tkoforpresident]

yeah thanks man, feels good to get the bird fixed up.

Of course as soon as I get the bird fixed my explorer starts acting up... brakes are grinding.. not good

[Schmieder]

Hey, so far so good. I installed the new chip, jumped the bird (battery was dead) and let it idle for a couple minutes. Then the moment of truth came and I popped it into drive and let it sit there for 5 minutes... Didn't stall out once. Reverse was fine too.

I don't want to declare it after one single test but it looks like the problem *might* be fixed.

How come we didn't change the map threshold sooner?

Ben has some explaining to do

Robert, thanks a million my friend. Let's hope we never get that code again.

That's great. Good job, I'm bringing my engine back to life after sitting 8-9 months. Winter to Summer temps too, outside. Crazy NE weather, does a number with time.

[Schmieder]

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

Ultimately, aside from the concept, I wouldn't do it to my engines PCM. I would find a much better solution. Resistors are more like road side quick last ditch effort to get home kinda thing, i guess. lol

[tkoforpresident]

Hey, so far so good. I installed the new chip, jumped the bird (battery was dead) and let it idle for a couple minutes. Then the moment of truth came and I popped it into drive and let it sit there for 5 minutes... Didn't stall out once. Reverse was fine too.

I don't want to declare it after one single test but it looks like the problem *might* be fixed.

How come we didn't change the map threshold sooner?

Ben has some explaining to do

Robert, thanks a million my friend. Let's hope we never get that code again.

[tkoforpresident]

and i've got a spare map sensor in case it is the actual sensor being goofy.

I'll burn this chip and then let you guys know the results.

thanks

[robertisaar]

well, since your cam doesn't generate a lot of vacuum at idle, we raised the threshold of where the ECM will start thinking there is a problem with the MAP sensor.

this SHOULD prevent a MAP high DTC from being set during it's test period, at least it will as long as everything is working properly. if the MAP itself goes completely nuts(reading above the 91kPa when in a near idle condition), it should still set the code. much better than simply disabling it.

[tkoforpresident]

got it.


Robert you are so kick ass.



Again though, what essentially have we just done and how will it help?

[tkoforpresident]

ok... one more minute.

[robertisaar]

and now i see why....

press ctrl + F2 to bring up the XDF header editor. change Bin Size to 8000.

then save XDF, close out of TP, reopen, change the value in the hex editor again, then save the BIN, should work this time.

[tkoforpresident]

I just emailed the .xdf to you that i'm using

[robertisaar]

sounds like problem... post/link to the XDF you're using(it may be mine, but i haven't seen it in a LONG time).

[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?

[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 hold on, this might take me a minute. I don't talk to computers in binary like you do

[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