Seems like no one really responds to these threads of people asking for help but I figured I'd give it a shot...
Serial#: 37820-PRB-A06 2068-601767
Vehicle: 02 Rsx Type S
Ecu: PRB K-Pro
Mods: AEM short ram intake, light flywheel about 12lbs, stock 6spd tranny
Swap: stock k24a4 accord longblock
Datalog: Included
Calibration: Included (stock tsx k24a2 calibration w/ a few changes) NOTE: the stock accord k24a4 calibration didn't work well it wouldn't rev above 2000rpm's
Problem: idle was very high but I improved it, still needs some work, motor will surge around 4000rpm's, running a little rich, mpg isn't very good. Overall need a tune for idle, part throttle/cruise, & WOT...
Any help is appreciated or if you could recommend me to a known reputable tuner that would be great, willing to pay for a good e-tune from a pro. I was notified that I don't need to dyno tune do to the fact that I have only a sri, so a street tune will be sufficient until I get more mods
Also I read that in order to tune you have to have a brand new set of spark plugs & a new primary o2 sensor, is this true?
All feedback is appreciated..
P.S. if you are a tuner that can seriously help me out & email is better for you please email me: jdmgreen24@yahoo.com
K24 Swap Type-S HELP
-
k24typesss
- Posts: 2
- Joined: Thu Sep 16, 2010 3:35 pm
K24 Swap Type-S HELP
You do not have the required permissions to view the files attached to this post.
-
k24typesss
- Posts: 2
- Joined: Thu Sep 16, 2010 3:35 pm
Really? The tuner who is suppose to e-tune my car said that I need to get a new o2 sensor, spark plugs & battery..
He said my o2 sensor flat lined (because it has high miles)
& he thought I needed a new tps (or check it for splicing) at 1st too but then I told him that those codes randomly came up after about 20-30 mins of data logging & that they never have came up before.. he said that a bad battery can cause false codes..
He said my o2 sensor flat lined (because it has high miles)
& he thought I needed a new tps (or check it for splicing) at 1st too but then I told him that those codes randomly came up after about 20-30 mins of data logging & that they never have came up before.. he said that a bad battery can cause false codes..