Ghettodyne Support (OBD0) - Final Version: 2.3
0.5 BAR
Joined: Dec 2002
Posts: 164
Re:Ghettodyne 2.2.1 w/ boost officially working
Someone metioned that GHD does not work well on DOHC engines. I have a B20(no-tec) that I would like to use it on, but not if it is going to crash like what was mentioned a few posts back.
tia
Blze
tia
Blze
3.0 BAR
Joined: Apr 2003
Posts: 2,260
Re:Ghettodyne 2.2.1 w/ boost officially working
Originally Posted by snatch10psi
ok who is selling this chip and i would like to know how much you want for the chip launch at 3000rpm i have the zif sockets so please let me know
As for ECU chipping, and selling you an EEPROM, I'll chip your 90-91 PM6 for $30 shipped. Seems to be the going rate for the last few people I have done it for. PM me if you're interested.
0.5 BAR
Joined: Jul 2003
Posts: 82
Re:Ghettodyne 2.2.1 w/ boost officially working
Originally Posted by xtensive
What's even weirder than that is I've NEVER seen a PM7 that HAD an external prom! Weird. I've got two PM7's sitting here right now, no external prom(s). They are both USDM.
Mike
Mike
3.0 BAR
Joined: Apr 2003
Posts: 2,260
Re:Ghettodyne 2.2.1 w/ boost officially working
I thought we had gone over this already?
GhD 2.2 is only really suited for SOHC, or anything smaller. xtensive has never modified GhD to handle anything other than stock SOHC fuel multipliers. If you try to tune an LS with it, you end up with GhD giving you overflow errors and crashing.
I have bypassed this by using Carsten's OBD0Edit, then pasting the maps into GhD 2.2 boost bin and setting the checksum manually. It's a bit of a PITA the first time you try to do that, and does not make for easy tuning.
Basically, saying that you'll either have to A) Open a hex editor, change your multipliers for that of a DOHC and enter your pulse width durations manually in hex. or B) Wait until the new version comes out with "auto discovery" of multiplers.
Originally Posted by Joseph Davis
GhD 2.2 is only really suited for SOHC, or anything smaller. xtensive has never modified GhD to handle anything other than stock SOHC fuel multipliers. If you try to tune an LS with it, you end up with GhD giving you overflow errors and crashing.
I have bypassed this by using Carsten's OBD0Edit, then pasting the maps into GhD 2.2 boost bin and setting the checksum manually. It's a bit of a PITA the first time you try to do that, and does not make for easy tuning.
1.0 BAR
Joined: Jul 2003
Posts: 238
Re:Ghettodyne 2.2.1 w/ boost officially working
hey turboef i just need the chip burnede i already got a zif socket and everything soldered in i just need the actually chip burned ya know let me know how much i will get it thanx man and is there anyway that you can send me the specs on the chip (program)? bud
0.0 BAR
Joined: Feb 2003
Posts: 0
Re:Ghettodyne 2.2.1 w/ boost officially working
I was the one bitching about GhD and DOHC engines.
Using older versions of GhD I've inserted LS mappings and while the fuel tables look a bit odd due to GhD's incorrect interpretation of the table multipliers, they work great in NA form, and you can add fuel to them for most every conceivable NA setup.
Once you get into the GhD 2.2 boost .bins it gets funky quick. I ended up using OBD0Edit to make my fuel maps for a GhD 2.2 bin for LS wth T3/4. The bin works - Blundar's friend Joe'e runs it - but if you open it in GhD 2.2 then Ghd crashes due to an overflow error.
The problem I am talking about is with GhD tuner app, not GhD ECU code. Mike is endeavouring to fix it when he finds the time. Hope that clears things up.
Using older versions of GhD I've inserted LS mappings and while the fuel tables look a bit odd due to GhD's incorrect interpretation of the table multipliers, they work great in NA form, and you can add fuel to them for most every conceivable NA setup.
Once you get into the GhD 2.2 boost .bins it gets funky quick. I ended up using OBD0Edit to make my fuel maps for a GhD 2.2 bin for LS wth T3/4. The bin works - Blundar's friend Joe'e runs it - but if you open it in GhD 2.2 then Ghd crashes due to an overflow error.
The problem I am talking about is with GhD tuner app, not GhD ECU code. Mike is endeavouring to fix it when he finds the time. Hope that clears things up.
