I am working on a friends car who is running an OBD1 PR4 chipped with crome on a stock b18b. I can't seem to get the car to run right on a stock USDM PR4 .bin that xencoron provided me a while ago. with j1 cut, the car runs perfectly fine, no CEL at all. but with the USDM PR4 bin and j1 jumped, I get a CEL that doesn't go away even just turning the car to aux to prime the fuel pump. I know its something i have missed, but i can't figure out what.

Basically, i am looking for something dumb that i am not doing, because this is my first foray into using crome. I have used Turboedit on my ef for several different applications, and i have never had this issue with just a stock map with launch control and some simple mods.

So a few things about the .bin i am using. I am using the addExtraFeatures plugin, so that I can have launch control. I also have the ELD and knock sensor disabled, which were default options on the bin provided by xenocron, and I am a little unclear if a b18b in a 91 crx si has an ELD or a knock sensor. my guess is that it doesn't? I don't have anything done with the checksum, AFAIK, it is still enabled, which i think might be the problem? I also am running the rtp+datalogging stuff, and i tried logging in EcuControl, and the data displayed but never changed.. which i think is a result of the duplex issue on the obd1 ecu, which i just discovered as well.

As part of my testing, I allowed the ELD as the only change, and that did not change anything. The ecu is still in limp mode with j1 jumped, so 4k rev limit and all that. The car idles great though, but if you go to 4k you hit fuel cut. I haven't had time to pull the code on the ECU yet, but that is on my list of things to add to this post once I gather that info.

My main hope is that someone will see something dumb like "hey you have to disable the checksum" or something.. which is on my list of things to do but i didn't think of last night at 2am. thanks for the help.

 

removing checksum is what i thought of prior to reading your last statement.

 

ok sweet. yeah that has to be it then.. I'll update once I do that.

 

Alright, so i have some updates. First of all, the ecu is a OBD1 PR4-A11.. i am starting to wonder if there is something up with this particular ECU model, if maybe its not compatible with the rest of its family or something, because i can't get it to run without a solid CEL on any of the pr4 or p75 binaries located here, or on the default OOTB crome p75 code or the pr4 code that xenocron sent me. All of these for sure had checksum removal routine run on them, so it can't be the checksum unless i am doing it wrong..

I have tried the #33 binary on that linked page above, the OzDM OBD0!! binary, actually by accident today, and it ran kinda shitty with the solid cel, but it started and idled.. Then i tried the p75 out of crome's default, and it started and idled on that too, but with a solid cel. Then i tried #235, which idled and revved up but broke up around 4k, and then wouldnt restart after i shut it off, all with a solid cel.

In all of these cases, i pulled the j1 jumper and the car started and ran like nothing ever happened. No cel, no nothing.

As part of the trouble shooting, i went and resoldered all 28 pins on the main socket, visually inspected the 74hc chip pins, and checked both capacitors and the resistor and the jumper for j1, and also removed j12 all together this time around. I am 99.99% certain that the solder job is fine, as i have done many many ecus before, and i have never burned a trace or shorted pins.. this ecu is pissing me off.

 

alright, i finally got the car running without a CEL on the chip. i used Xenocrons 274stock-usdm-LS.bin found here.

The next step is to build that up with the features i need.

for those who were following along at home, i think my POS chinese made willem with the pic id's sanded off is really the problem, not the car or the ecu chipping work. Burn1 FTMFBBQW


Modified by sanimalp at 10:47 PM 8/18/2008

 

The issue here was the "add extra features" plugin for crome. I noticed in the notes it didnt mention anything but a P30 or P72.. so i suspect that is the issue.

I built up the ecu one piece at a time. I have a burn2 now, so I just tried the stock rom linked above, and it worked fine. I then added quick datalogging + RTP from the enhancements menu, and that also worked. Then I added the "Add Extra Features" option to add launch control, full throttle shift, shift light control, and some other things, and that cause the issue.

My fuel pump just ran, it never turned off, and I got a CEL that I didn't check and the car won't start.

 

I believe the PR4-A11 is an automatic, you might want to modify it for manual before anything else. It sounds like your ROM is just bad, try importing the tables to a new .bin and ad all your plugins again. Otherwise, look for an updated (or alternate) version of the "Add Extra Features" plugin from sourceforge.com and see if that's your problem.

 

nah, its a manual.. all honda ECUs whose last 2 digits are >50 are auto ecus. This being 11 is a manual. I am nearly certain the add extra features plugin is the problem.. Ill have to check around and see if there is a newer one, as i know for certain that the add extra features plugin i was using was somewhat old.. more than 2 years i think.