Slo_crx1

One of my friends has a 2000 civic ex, and his g/f bought him a buddy club vtec controller for his birthday. I already told him it was useless to put on with a motor with only I/H/E, but he said he felt bad trying to tell her it was garbage and put it on anyway. Now here's the problem...
He hooked it up, it works the way it's supposed to, but after a while it pops a code (probably something dealing with either the vtec solenoid or the oil pressure sensor). Unfortunately the local auto parts store's code reader was down atm, so I couldn't find out exactly what it was. I rewriting some .xml definitions for an obd2 code reader I have using an openport obd2 Tactrix cable so maybe I can connect my laptop to his car and find out what it is. Either way, has anyone experienced anything like this on a stock obd2b ecu? Only thing I can think of is maybe the oil pressure isn't high enough at the rpm he's set at and it's tossing a code for that, otherwise I'm stumped. Even my Evo isn't that picky with it's obd2 MUTIII setup.

Guy-Fast

obd2=crap=obd1 conversion for the win



In reality take it off and break her heart

Slo_crx1

That's what I told him also. I'm slowly teaching this kid the ways of d-series and boost and he's sucking it up like a sponge. Eventually once he gets all his turbo pieces I told him he has to convert down to obd1 and can set it to whatever he wants through there, but his g/f can get pretty crabby at times if you know what I mean.