1G Eprom Editing - Hardware, Software and Info

[Vlad Busta]

I've tried the WBO2 code modification and all looks to be working well.  The good thing is that you can log your regular O2 sensor which will now read/report thw actual WBO2 sensor voltage instead of the narrow band.

I've removed the stocker and screwed the AEM WBO2 sensor into the O2 housing and wired it's signal wire(from the gauge) directly into the ECU O2 sensor wire in the car.

This allows us to use the EGR sensor input for other purposes such as boost logging.

I've just started playing with the Ostrich and all I can say is that it's well worth the money  

[Wayne Wright]

That just rocks man, I order my ostrich last night, and I have a Burn1 as well.

I was reading into the code, glad to see it's working well, it's one of the first thing I wanted to do.

Any word on the Water/Meth injection through the BCS?

There's some talk about a GM maf with no Translator, they both output in hz, but the GM's output is much higher then our, and climbs exponentially.

[Vlad Busta]

There's a great disassembly of the E931 code done by Christian on the ECU yahoo group that could help you out with the BCS controlled WI.

What I was thinking in this regard would be to have the WI triggered at a specific boost level instead of trying to PWM the pump.  See msg 3527 in the DSM ECU archives for code on how to use the purge solenoid output to trigger a device, such as the WI solenoid.

As for a direct plug-N-play GM MAF, there needs to be a bunch of coding to accomplish it.  By looking at the Excel sheets that compare the GM MAF output frequency with the 1G stocker you'll see that the GM MAF is about 40X the frequency of the 1G MAS.  If you know electonics pretty well then I suppose you can hook up some sort of frequency divider circuit before the signal from the GM MAF to the ECU, then just fudge with the MAS compensation table to get it in line.

Something I'm looking into is a selectable studder box launch feature like the TMO chip had  

Later, Vlad.

[Wayne Wright]

Yeh, I was thinking that having it airflow dependant would be sweet.

I have lots of readin to catch up on in the group, been busy lately.

Very nice to see that there is a couple of us in on the editing bit though, very good stuff to be had out of it.

Would you mind Pm'ing me the code you used to the WB? (or post it up, this thread could become a good sticky one day)

Thanks,

Wayne

[Vlad Busta]

Miles posted the code on the first page of this post.  That's the same code I used and it seems to be working fine.  No CEL light and my low and high trims are updating.  I have to drive the car around some more to be sure.

[John Hartman]

I've been reading/subscribing to these threads too, and there are some great ideas being tossed around.

the native gm coding into our chips looks a bit ambitious tho, its not a linear 40x thing, its a bit odd, at least to me.

the thing that gets my blood boiling is the idea of a MAP sensor being used natively in our ECU code, no MAF, no worries about over running it, no worries about boost leaks causing drivability, no worries about venting, straigher less restrictive, simpler intake piping. In short that would be GREAT!!

My Keydiver chip has selectable stutterbox, so its out there and works well.

Another thing I'd like is if the "knock" gauge at 0 would be on the bottom instead of at the first notch.  I know the gauge can go down to the bottom because the lowest stutterbox setting is with the needle flat on the floor.