Type-X

Everytime I burn a map and put it in my car the check engine light comes on. I check to see what code it's throwing but it isn't showing any codes (no blinking). What's weird is that when I disconnect the jumper to the base map the check engine light goes away. So I thought it was the ecu but I put in my po5 vtec converted and chipped ecu and it does the same thing. I've burnt basemaps on cromepro and uberdata but the same thing happens. Another thing I found wierd was that there's a buzzing noise comming from the black thing behind the throttle body (near the butterfly) when I connect the basemap to the ecu. Then when I take the jumper to the basemap out it goes away. This is my second setup and I haven't run into this problem before. Please... anyone who's run into the same problem or knows what's going on help a fellow HMT member out thanks.

BlackCRX

need more info

what kinda motor and setup are you running ??
post your bin somewhere so we can look at it

Type-X

Setup:
-d16z6 (stock)
-t3/t4
-460cc injectors w/ 10 ohm resistors
-7psi
-2.5 charge pipes
-intercooled
-chipped ecu
Don't know how to post up bin so I'll e-mail it to anyone who's willing to help thanks.

Joseph Davis

Try burning a stock .bin to both of your chipped ECUs to try to isolagte the problem:

1) burner settings/defective?

2) chip defective?

3) socket/74HC373 install on the ECU defective? (bad solder joint in that area won't keep the ECU from running like stock with J1 cut)

Type-X

I tried burning a stock p28 map on uberdata 1.66 but the engine light still came on on both ecus. I have like 3 sst27SF512 chips and all three burnt with a map gave the same result: solid cel. I don't know why but my ecu fuse keeps going out when I start the engine. Could it be my stock harness?

Deucers

I'm new to the tuning with Uberdata, but I was throwing a few codes and had a solid CEL...I had these 2 codes (ELD, BARO) All I did was disable those codes and everything was fine after that.

Maybe try burning a new chip with everything disabled and seee if you get a CEL...If you don't start enabling different systems 1 at a time till your CEL comes on again.

Just an idea, and not sure if I am out to lunch on this one.

mrx

If you have a 512kbit rom, you must burn the rom content in the upper 256kbit

otherwise, use a 27c256 ... then it should run.

cobra2326

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Type-X &raquo;</TD></TR><TR><TD CLASS="quote">I tried burning a stock p28 map on uberdata 1.66 but the engine light still came on on both ecus. I have like 3 sst27SF512 chips and all three burnt with a map gave the same result: solid cel. I don't know why but my ecu fuse keeps going out when I start the engine. Could it be my stock harness?</TD></TR></TABLE>

Sounds like it wasnt chipped right. I was getting random solid CEL's when I first chipped my own ECU a few months ago and it was due to poor solder joints. Check those first.

Type-X

It might be my willem burner. Cause one of the components fell off when I was looking at it. I'm trying to solder that part back hopefully that's the problem.

.nate

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Type-X &raquo;</TD></TR><TR><TD CLASS="quote">I don't know why but my ecu fuse keeps going out when I start the engine. Could it be my stock harness?</TD></TR></TABLE>

You need to find the cause if this problem before you can procede any further. Does it pop the fuse with j1 open?

Type-X

it only pops when i try to start the engine with the basemap and j1 connected. When I try to burn on my willem i get alot of the same error and then once in a while it'll let me burn a map. The error I ussually get is:
Error at 0x000000 Chip = 0xFF buffer = 0xED. I have no clue what that means. I've foolowed every step on the pgmfi.org site too.

slodc2

did u choose the option to run a knock sensor?...if so turn it off and see what happens..that is the cause to alot of people's b/c p28's do not have knock sensors and if you choose to run it, it will throw a CEL

Type-X

Knock sensor was disabled. I have burnt stock maps on crome and uberdata for p28 but still a solid cel. Still don't know what's the problem.

BlackCRX

unlike atmel 29c256's the sst27sf512 chips require 8000hex offset
did you do that ??

grubere

willem burners hate SST cheaps. True story. Go buy some amtels. I know they cost double and all that crap but SST chips SUCK with Willem burners.

Type-X

Yeah I set the required 8000hex key offset and still I get a solid cel. When I burn a map onto the eprom and then try to upload it into crome or uberdata, a window pops up and tells me I "can't load the file". Cause to upload the bin from a chip i press the read button right. Once it read then i save it and open it in crom or uberdata. But when I do this it tells me I can't load it. So does this mean my burner is defective?

BlackCRX

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by grubere &raquo;</TD></TR><TR><TD CLASS="quote">willem burners hate SST cheaps. True story. Go buy some amtels. I know they cost double and all that crap but SST chips SUCK with Willem burners.</TD></TR></TABLE>

how so ?
i have been using sst's for the past year
btwn tuning and testing different things i have probably burnt over 100 chips and never had a problem
only problem was user error cuz i forgot to set the 8000offset a couple of times

BlackCRX

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Type-X &raquo;</TD></TR><TR><TD CLASS="quote">Yeah I set the required 8000hex key offset and still I get a solid cel. When I burn a map onto the eprom and then try to upload it into crome or uberdata, a window pops up and tells me I "can't load the file". Cause to upload the bin from a chip i press the read button right. Once it read then i save it and open it in crom or uberdata. But when I do this it tells me I can't load it. So does this mean my burner is defective?</TD></TR></TABLE>

check your dip switches??
http://uberdata.pgmfi.org/foru...26153


also when you write a bin, does it verify ok ??
one other thing, when you erase the chips you ahve to have the jumper on, but when you burn YOU MUST REMOVE THE JUMPER otherwise it wont burn correctly

grubere

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by BlackCRX &raquo;</TD></TR><TR><TD CLASS="quote">how so ?
i have been using sst's for the past year
btwn tuning and testing different things i have probably burnt over 100 chips and never had a problem
only problem was user error cuz i forgot to set the 8000offset a couple of times</TD></TR></TABLE>

Because you have to screw with the jumper every time you want to burn a chip. If you remove the wrong jumper you kill the chip and it never works right again. Ive had nothing but headaches with SST chips. Its not the chips fault, it just doesnt work well with the Willem's design. If you enjoy dicking around with a bunch of crap just erase a chip, SST is great. Personally I just like to put the chip in and press erase, and then burn. Hell I never even installed the jumper on my Willem and it works perfectly every time with amtels. Amtels cost a bit more, but its less aggravation. I'm all about limiting my aggravation when it comes to saving $2.

BlackCRX

true the jumper is a bitch sometimes
but the atmels also require a jumper btwn 2 of the pins. of course when i was using the atmels i just hardwired the jumper (soldered a jumper)

but on the plus side of the sst chips is that you can store 2 bins on one chip
so for the racers out there one chip will contain 2 tunes (ei one bin for street tune, second bin for race gas)

also out of curoiusity, what jumper would you have to remove to kill the chip ??
just so i know not to remove it
hahahah

Hybrid96EK

I would suspect either the chip or the chipping job on the ECU. I would first get a 29C256 and try burning the same map on that chip. This SHOULD work without any issues. I haven't personally heard of or used those chips you mentioned. That doesn't mean I am saying they won't work, I would just go back to a known working format. Try the 29C256 and see what you get. If that doesn't work, look for possible cold solder joints.

LoseRPunKx182

did u reset the ecu unhooking the jumper wire and resolder it

Joseph Davis

Type-X, it is pretty apparent that your burns are sucking poopdick.

Start troubleshooting that burner... try to read the info back off your chip and them open it in UD/Crome.

LSTEG96

buzzing is your injectors going nuts. ??? maybe?

my guess is u have the chip in backwards. aka, ur fucked.

Type-X

Thanks for the replies guys but finally got it to work.