chip burning problem Burn 1 Uberdata
Thread Starter
1.0 BAR
Joined: Sep 2006
Posts: 221
chip burning problem Burn 1 Uberdata
Any way all my settings are right.When i burn a downloaded bin, or one i created, it won't rev pass 4500 rpms.When i burn a stock rom p30,p28,p72 it runs fine.This is a p06 converted to a p28.It has a solid cell o2 heater sensor.I have had that cell forever, so i know that's not my problem.I'm just need somebody to either tell me what i'm doing wrong, or point me to a page, and i'll just read it.I have the same set up as bbka 240cc setup.Yes i have manually searched for my problem, and cannot find it.I know its hitting limp mode just not with a stock rom.
Guest
Posts: n/a
Re: chip burning problem Burn 1 Uberdata
Originally Posted by d112crzy
full throttle launch? the bin could be corrupted. it happens a lot in uberdata.
You need to sort out that o2 code and see what happens.Those two wires are on the second largest plug D22 is green and white, D14 is solid white.
Pins d14 and d22 are for the o2 sensor on a p06. just trace them and make sure their actually going to the right place.
Thread Starter
1.0 BAR
Joined: Sep 2006
Posts: 221
Re: chip burning problem Burn 1 Uberdata
No when you try to floor it still hits 4000-4500 like a fuel cut.I'll check on them wires.Its a 94 delsol si d16z6 with the converted p06.No wiring has been touched.I can use my brothers ecu and the same stock p28 chip and it goes away.My ecu has had that code for 2 years.I had somebody on this board to convert it, but never had time for them too fix it.The car never ran bad with those 256 eproms.Every sense i had the 512's, they suck.
0.0 BAR
Joined: Jun 2005
Posts: 0
From: WA
Re: chip burning problem Burn 1 Uberdata
even if its floored out of 1st gear?
disable ftl to make sure its not ftl.
make sure you're erasing the chip as well as loading it correctly. before it burns, make sure uberdata is closed.
disable ftl to make sure its not ftl.
make sure you're erasing the chip as well as loading it correctly. before it burns, make sure uberdata is closed.
1.0 BAR
Joined: Jul 2005
Posts: 254
Re: chip burning problem Burn 1 Uberdata
You sure you reading your CEL correctly? You know O2 code is 41 and Vtec is 21 right? Might be your Vtec not engaging by the sounds of a fuel cutting at 4500. Might wanna check your Vtec solenoid and make sure its wired correctly. Happened to one of my friends car...he thought it was an O2 code and can't get the motor past 4500 but instead it was his Vtec not engaging.
Thread Starter
1.0 BAR
Joined: Sep 2006
Posts: 221
Re: chip burning problem Burn 1 Uberdata
Well so far every bin, most of them are corrupted.Weird fuel and timing values.I tried with 1.66 uberdata 1.7,1.7 repack,1.8,1.9. None of them work right except the stock rom.If somebody can burn me the 240cc setup (bbka), on a eprom and check it.I'll pay you for your time.I tried the samething with crome bin's, and no luck.Same problem.It's not the ecu or the solid cel.I have ran a uberdata turbo bin on that ecu before.It's just that somebody else burned it.
Guest
Posts: n/a
Re: chip burning problem Burn 1 Uberdata
Yeah uber is really finicky you have to follow the procedure exactly to get it to work right. To open I file in uber it has to be in the uberdata folder or you'll get some fail to assemble errors. then to burn the bin with burn one you have to close uber before you do it our it will cause problems with the burn. your doing som ething in a way uber doesn't like you just need to doing things in a differant order.
Basically make sure your bin is saved in uber if your going to mode it make sure you have the same version of uber it was made with. save the rom and close uber. Then open the bin in burn1 and burn the chip. if all thats done you should be fine.
Basically make sure your bin is saved in uber if your going to mode it make sure you have the same version of uber it was made with. save the rom and close uber. Then open the bin in burn1 and burn the chip. if all thats done you should be fine.
Thread
Thread Starter
Forum
Replies
Last Post
vang
Engine Management
9
Mar 11, 2005 09:05 PM
digitalhav0c
Engine Management
5
Aug 17, 2003 09:21 PM
