Re: Hidden xenocron write up.
 

So the shop we're doing this with has a pocket programmer 2 from an old hondata kit they bought, and we don't have the driver disk for it. One thing to the next.

Re: Hidden xenocron write up.
 

I have the software at home.

Re: Hidden xenocron write up.
 

Re: Hidden xenocron write up.
 

We have one at the shop. I can burn the drivers if those listed above wn't work.

Re: Hidden xenocron write up.
 

Ugh, so we were out until 130 last night trying to get this fucken car running. Everything is good, until 4-4.5k rpm. It sputters like it's misfiring. But if we put the stock ecu (P13) it revs all the way out.

JDM H22 in EG running P13 with t3/t4, 450cc, 7psi.

We ran both the stock USDM and H22 maps converted to the P30 rom? just like xenocron's write up says. We fucked with the timing and afr's until it would run really good until 4-4.5rpm. Even when it started stuttering, the air/fuel was good. I thought it would be an ignition problem, but why would the stock computer let him rev it out (with 450's too ???)

Anyone?

EDIT: Stealthmode had an experienced tuner and a dyno jet, so it's not my fault. :D

Re: WTF is going on? **update**
 

It's never anyone's fault, Steve, it's just work sorting the car. Like you said, you were out until 1:30 last night actually doing something instead of bitching about how you're too lazy to figure it out on message forums. You've got our help.

AFRs "looking good" while the car is breaking up doesn't make a lot of sense. If it's not burning the fuel then you get a false lean reading, since the O2 sensor picks up unburnt oxygen.

Crome is *very* stable compared to UD, but sometimes Crome's script engine compiles the code fucked up and it (usually) dead CELs or (rarely) just acts wierd like you are experiencing.

I'm going to up Stevo's 880cc H22 .bin to xenocron's site. You can recurve for 450 under fuel tools- keep in mind the recurve should be 240/450 not 450/880 FTW, that's a common mistake; fuel maps with FVFT are always in referrence to stock 240cc unless you're doing something wierd as ----.

If my .bin looks like gibberish, I'm more than happy to send you my .rar'd Crome directory which is already configured with all my favorite plugins. Let me know.

Re: WTF is going on? **update**
 

FTL? What did you set that at? and is it off for the tunning?

4.5K is too high for limp. Getting any CEL's?

Re: WTF is going on? **update**
 

sent it to me too ;) ill appreciate it!

Re: WTF is going on? **update**
 

Maybe some better insight will help.

H22A with P13 ecu runs fine. It does have a code 41 (heated 02), but we disabled it on crome and the one map we ran from uber.

We have a manual P06 chipped with added vtec. The car has a sold cel and can't be checked, but making map changes we get the car to run up to 4.5rpm, where it sounds like ignition breakup or a rev limiter.

Stock P13 ecu with afc we ran well to 200+ with only the heated 02 cel (it's not even hooked up).

Should I be looking at the ecu, or should I be looking at the files? Multiple crome maps ran. A basemap that we changed a couple times with no luck, some of the "tuned" maps out of the library, and finally a "TunedH22" map from the uber library that we didn't even open. Just download and burn.

Asian pusssy smells like catfish.

Re: WTF is going on? **update**
 

You have a solid CEL. You need to now figure out if its ECU, ROM or chip related. The best way to do this is open a p30 rom in Crome, scale the fuel map down for your larger injectors(add more fuel in the idle region), set it in debug mode, and burn the ROM. Key on, check if the CEL is still there. If it is still there(and assuming you arent a complete idiot), then you know the problem is not ROM(meaning the file) related. Now you can move on to checking if the chip is being burnt correctly. The easiest way to do this is put the chip in your chip burner, read the chip, and then open it in Crome. If it opens okay, then most likely it burnt okay. So if both of those work, then the ECUwas chipped badly.