Swashbuckler

iTrader: (1)

I got the Creader and plugged it in today. ill give an update in a couple of weeks.

Gsxtremedsm

iTrader: (15)

I got mine in as well. I took it out last night on the interstate and made it throw the code. Shortly after it was cleared. So I tried to throw the code again.... and so far(please god let it stay this way) it wouldn't throw the code...

So I will give updates shortly(pray for me...)

_ceteuro

My friend got the Creader also and the car is awesome. I checked my car for leaks and found 5 major leaks. The code went away and the car is working great, I will update soon to let you know if the code came back. If it does I had the Creader abd the code can go F*** its self.

deadbeatrec

iTrader: (9)

pulled the P0300 yesterday while idleing. im thinking about getting a creader. i cant view it right now because im at work and i can only get on ebay at 11:30 -12:30 so will someone post a pic of it and host it in imageshack? thanks

deadbeatrec

iTrader: (9)

is this it?

http://www.harborfreight.com/cpi/cta...emnumber=46030

deadbeatrec

iTrader: (9)

well i got the creader and i need some help. how the **** do i use this thing? i realize u are all saying "leave it pluged in" but isnt it supposed to read the code first, tell u what it is and then clear it? all i am getting is

E Launching - - - -

please help

Ted B

iTrader: (6)

You plug it into the OBDII port and leave it there. That's all you do. If there is a CEL or any codes, it clears them and keeps them cleared.

deadbeatrec

iTrader: (9)

so it wont tell me what code it is? ok i will plug it in. how long until it clears the code?

Ted B

iTrader: (6)

If you watch the display when you plug it in, it will tell you what code. It will clear the codes within about 30-45 seconds after plugging it in.

deadbeatrec

iTrader: (9)

thats what im telling u, it never told me the code nor did it clear it. all it says when its pluged in is

E LAUNCHING - - - -

and it never says anything other than that. this is y im so confused.

1. should the car be on?

Ted B

iTrader: (6)

The engine can be running or not, so long as the key is in the 'on' position.

deadbeatrec

iTrader: (9)

nothing happens.

im going out to my car right now. i am going to see what happens. i will be back in 5 mins

nothere

iTrader: (23)

I just happened on this thread.

certainly good news for the p300 cel.

And I have learned that others have a "worser"(how come spell check didn't flag that, can't be a word) problem than mine.
I never get to the misfire stage, but I do get a p300 cel at or right after startup on my 03 VIII. I can clear it with evoscan but it comes back within minutes.

Ordered the creader cheater that Ted proscribes, hope it works, but somehow I need to kill the code so I can pass obd2 inspection this winter.

I wonder if temporarily gasketing the ks would help during the test?

deadbeatrec

iTrader: (9)

just went to my car. here is what i did

-turned the key to on
-pluged in the Creaded
-Creader read E LAUNCHING - - - -
-waited 2 mins

nothing happened. kept saying the same thing

-turned the car on
-pluged in Creader
-Creader read E LAUNCHING - - - -
-waited 2 mins while car was running

once again it never read any codes or cleared anything. i think this thing is a POS that is made in china.

mithrandir7533

iTrader: (1)

If your car is modified, all bets are off what it could be. If this issue was problematic on cars that are stock you can't necessarily correlate those findings to ones that are modified. I have had the P0300 code and it when away soon after dealer reflashed the ecu with the latest update. That was about 2-3 years ago. Installed a exedy hyper single clutch at 9k that has had and still has a lot of chatter.

You have to understand the logic and all the parameters (initial conditions, etc..) involved to produce this code. If you have a modified car those initial conditions/parameters can be altered and you may in fact be inducing the fault from your modifications.

You need to be able to evaluate all the data that's used in the logic to produce this error to really understand what's triggering the fault.

Anyone have a logic diagram for this fault???