null.

i recently street tuned my new setup, but strange thing is; when i burned the chip and put it into my P28 and bring it up past 7000+ rpms, it throws code 16 (which is fuel injectors) and goes into limp mode. I shut the car off and turn it back on and CEL resets; everything is fine. I can repeat the cycle over and over.

my final assumption is that the problem is the p28 ecu. reason being is because we hooked up uberdata ostrich up to the p28 and it still threw the code past 7000 rpms. we hooked up the uberdata ostrich with the p72 and everything is fine, no code.

the chipping of the p28 looks perfectly fine, i used it on my N/A setup and no problems at all, same chip, same program. It definitely can't be the fuel injectors wiring because it doesn't throw it on the p72.

what could it be?

if it matters my setup is:
ls/vtec
11.5:1 compression
580cc saturated injectors
t3 .42 .48 (yes i know it's small)
boosting at 8lbs

Dunc

you've got some ***** too....11.5:1 CR, thats definitely living on the edge haha. Sounds like it could be the ecu.

SOHCmaster

Man dont tell me that... I just got a P28 chipped for uberdata and got peps here w/Ostrich as well. Havent used it yet, but hope I dont have no issues.

null.

i'm pretty sure my problem is rare. i've searched and found no answer.

Enz0Speed

Definitely the first time I've heard of the problem. You're kind of screwed when it comes to testing the ECU because you can't cut J12 and rev that high without hitting fuel cut.

But it still sounds to me like a software issue. You said it wasn't the software because you burned the ROM into ostrich and used it in a P72. But how? You'd have to import a P72 bin right?

It just sounds like one of those things that will go away if you keep dicking around with the MISC tab and different uberdata versions. The uberdata bugs are weird - some will affect only specific ECUs, i.e. your P28.

Here is the only setup that I've found to work with my P28 and ostrich - create a ROM in uberdata version 1.70. Save the ROM and then close 1.70. Now you can open uberdata version uberdata.ost2 and open up the ROM you saved in 1.70 and upload it to your ostrich. This is the only method I could come up with that didn't have CEL issues.

Version 1.70 seems to be the best. You just have to use ost2 to program your ostrich. And don't use version 1.8 - still too many bugs - you'll give yourself a headache trying to figure out how to work it.

null.

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Quagmire &raquo;</TD></TR><TR><TD CLASS="quote">

Here is the only setup that I've found to work with my P28 and ostrich - create a ROM in uberdata version 1.70. Save the ROM and then close 1.70. Now you can open uberdata version uberdata.ost2 and open up the ROM you saved in 1.70 and upload it to your ostrich. This is the only method I could come up with that didn't have CEL issues.

Version 1.70 seems to be the best. You just have to use ost2 to program your ostrich. And don't use version 1.8 - still too many bugs - you'll give yourself a headache trying to figure out how to work it.</TD></TR></TABLE>

yeah i did the exact samething you just said before, mainly because uberdata ostrich has the bug where if you save the bin file it is too big.

what i'm going to try to do is see if i can get ahold of another p28, if that has the same problem as mine, that it will be a software problem, if it doesn't than it's my ecu.

0mtber

iTrader: (2)

I doubt it is the ecu. Anything is possible.

Enz0Speed

Yeah, I seriously doubt that it's the ECU. Just think about it - you could either be the first person to ever have that kind of problem with your ECU, or you could be one of thousands of people to encounter weird uberdata bugs.

null.

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Quagmire &raquo;</TD></TR><TR><TD CLASS="quote">Yeah, I seriously doubt that it's the ECU. Just think about it - you could either be the first person to ever have that kind of problem with your ECU, or you could be one of thousands of people to encounter weird uberdata bugs.</TD></TR></TABLE>

yeah that is true, alright i'll just play with uberdata more

Jaker

Is your P72 JDM? If not, do you have the "disable injector test" box checked at all?

reaction360

we had this problem on uberdata once, and i think we just used a different version of uberdata and it was fine. we got tired of all the bugs, so now we just run Crome.

Enz0Speed

Yup, uberdata is a bitch to get going. I went through like five versions before settling on one that worked.

Plus, as if that's not bad enough, sometimes the downloads inexlicably go bad and you will have to re-download the zip file. Then it suddenly works.

But that's why the software is free. In my opinion, the money saved when I switched from hondata to uberdata was well worth the three weeks of headaches to get everything working.


The only advice I can offer to people who read this:

- If you have a P28, don't burn chips with version 1.8 unless you want a solid CEL
- Don't try to datalog with version ost2

nfn15037

Or you could just run Crome and not have any headaches......*shrug*

reaction360

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by nfn15037 &raquo;</TD></TR><TR><TD CLASS="quote">Or you could just run Crome and not have any headaches......*shrug* </TD></TR></TABLE>

Enz0Speed

Bah! It's not as rewarding then

It's like, you could pay someone to install a turbo kit, but when you do things yourself with your own blood sweat and tears you appreciate it more in the end.

SPL Dan

I've had this issue a few times ...


When I convert the binary from p28 code base to p72 it corrupts the Higher RPM fuel values ...

Check the code base in a hex editor and make sure its correct ... I belive the adress is 4DCC , It should read 06CA yours will probally read 18CA

Enz0Speed

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by SPL Dan &raquo;</TD></TR><TR><TD CLASS="quote">I've had this issue a few times ...


When I convert the binary from p28 code base to p72 it corrupts the Higher RPM fuel values ...

Check the code base in a hex editor and make sure its correct ... I belive the adress is 4DCC , It should read 06CA yours will probally read 18CA</TD></TR></TABLE>





I wish I knew how to talk like that

nfn15037

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by SPL Dan &raquo;</TD></TR><TR><TD CLASS="quote">I've had this issue a few times ...


When I convert the binary from p28 code base to p72 it corrupts the Higher RPM fuel values ...

Check the code base in a hex editor and make sure its correct ... I belive the adress is 4DCC , It should read 06CA yours will probally read 18CA</TD></TR></TABLE>

Why are you doing this??

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Quagmire &raquo;</TD></TR><TR><TD CLASS="quote">Bah! It's not as rewarding then

It's like, you could pay someone to install a turbo kit, but when you do things yourself with your own blood sweat and tears you appreciate it more in the end.</TD></TR></TABLE>

Thats not how I see it. I figure if you have a program that actually works, it is much easier to focus on the theories and applications of that tool rather than figuring out why that tool doesn't work. *shrug* to each his own.