tranceminister

A while back I had programmed my first chip with Uberdata, and I installed it in the ecu backwards and fried the chip (so I thought)... I bought some more eproms and today I programmed another chip, and installed it in my ecu (the right way) but I still have the same problem. I get a check engine light and it won't rev past 4000 rpm even when driving. The idle goes up and down pretty bad also.
I know I'm programming this thing correct, but now I'm wondering if maybe I fried the ecu the first time I tried to install the chip... Is this a possibility, or am I overlooking something? I'm honestly stuck and confused about what my next step should be to pinpoint my problem.
If anyone has any info that they wouldn't mind sharing with me that would be great. Hope fully I'll get this thing straightened out. Trance

TurboEF9

I doubt you fried the ECU.

Are you sure the checksum is being calculated correctly? If the ECU were "fried" it wouldn't run the car at all.

Use Keil Software's check8.exe utility (http://www.keil.com or some such) and check the checksum of the ROM. If it's saving incorrectly, then you'll get that checksum issue.

From what I have been told OBD1 ECUs calculate checksum based on the entire file, rather than just 0x0000 - 0x4FFF.

blundar

Uberdata disables the checksum.
Try burning a stock bin. You can find a ton linked out of the PGMFI wiki.
If a stock bin still gives you the same behavior, then you most definately have a hardware problem. I'd look to bad sodlering before I suspect toasted ECU.

tranceminister

Ok thanks you guy's, I'll look more into this problem tonight. i was getting frustrated last night and couldn't pinpoint it. I will burn a stock LS rom and see what happens. The ecu did work before i went and re-chipped it. There was already a chip and zif socket installed so really all I had to do was program and swap chips.
I'll report back in a while. Thanks again

ShadowRex

yea if ya burnt the ecu it would do nothing. Also I agree with all that was said what chips are you using? 29c's or 27'c? I have a nice rich LS bin i been sending out for dohc ZC's if ya want to try that one to let me know OM me a e mail addy and I will email ya it.

tranceminister

Well rex I appreciate your offer, but I just made a stock LS rom and tried it out. The car ran perfectly. No fluctuating idle or anything.
So now I know that my ecu, eprom programmer, and Uberdata is working fine. But, why when I make a custom chip (Launch control, different fuel settings etc.) does the ecu act horrible? It's almost like my computer isn't saving the settings I've made with the Uberdata.
Any ideas on that so I can figure out what's going on here? I appologize for the "New-B" questions, I'm new at this and this is how I learn. I make mistakes and then get them straight .

ShadowRex

I have never tried uber. Do you have turboedit? if so try using it to change it save it under a new name burn it and see if you have a problem that way. I will try to get uberdata and see if i can learn it tonight cause now you have me wondering lol

blundar

ok lets start with the basics:

-Car type, year
-Engine type
-OBD0/1/2 distributor?
-ECU type, year

Answer those and I bet we'll find the problem.

tranceminister

Well, it's a 2000 Integra
B18b engine
OBD2 distributor
OBD2-OBD1 conversion with a P75 ecu out of a 94 or 95 Integra (I don't remember exact year).
I've been using the 27c256 eproms to chip with. Kind of a pain in the *** because i don't have the eprom eraser.

Shadowrex I thought Turboedit was only for OBD-0.

ShadowRex

ah that it is i thought you were going old style. Um shoot i know blundar will, be alot more help cause I JUST got into obd1 lol