Did you clear the DTCs after the repair?, using a scantool (reset)
then drive and see if both codes return, are they the only codes
stored after 20miles driving? and fast 50mph and coasting to a stop fast and hot engine? (this act runs out most monitors)what car,?
not stated, just honda. there are lots of honda\'s.what year,
? must be 1996 or newer if USA my guess 2004+?what engine I4 or V6?
option?is car a USA car?
, USA cars are in fact quite different from all other cars , over the planet.
NO , my answer is no, do not GUESS!
why not read the FSM and do the tests there.?
buy a real FSM honda,. why own such a complex system with no books (bible)
or read it on line at alldata.com or mitchels.
the ECU/PCM does not know what is broken. NEVER
it only knows,what tests (monitors) failed, ONLY.
so it\'s the job of the technician (mech) to do other tests (simple)
to find the true cause. if you guess, it will be 10x more.$$
seems you are there already with a new TB. ouch.$$$
I4 answers. (4 banger?)
123 = bad TPS, or wires /conns to it.
223 = is vasty more complex
223 can be thrown for many reasons,
there are 5 major parts, to this system.
PCM. / TAC RELAY/ TAC MODULE, TB (with motor and TPS) and APP (leaving out, the whole engine, me bad..
ok, there are always 2 causes of 223.
1: the 223 monitor was fooled.
2: or there really is a real TAC FAILURE. (PARTS)
This is the number one thing go learn about OBD2 systems
fooled or not fooled.
To diagnose this system and not take wild expensive guesses.
what do we do.?
we learn how it works,
it is just a closed loop servo system that is fly by wire.
or better, its Throttlebywire. it is a royal PITA, no lie....
in a nut shell, you create demand via the foot (TPS)
note first there really is 2 TPS, TWO !
the one a the foot is DEMAND, (you) honda calls the pedal APP sensor.
you step on the gas, err, app, the PCM sees this.
and then sends a command to the TAC, THE TAC RUNS THE TV (throttle valve) motor, and tries to match your demand.
see, that word match>?
if it can not match your demand for any (most) reasons.
then its a failure, but the ECU is bricks stupid, it DONT KNOW WHY , but just takes a wild guess, and pukes out 2 codes.
lets examine what can cause the ECU to give out TAC codes.
not a full list by ANY means.
1: bad engine?
2: air leaks, or MAP/FAF weak readings (causing lean conditions)
any air leaks to the induction plenum (aka vacuum leaks)
3: sticking TAC parts (gummy) the motor, the TV or idle controls parts that are malfing,
4:engine lean for any reason (bogging)
5: gross misfiring not detected by P300 monitor, (it happens)
I ask you, are you going to replace $2000 in parts, just for a vacuum leak? why let the ECU do that to you,
it is , brick stupid, do not let any ECU dictate the snap (shot gun) buying of parts.
and buy an FSM and read the pages, the book is way less than
or the $15 access fee to alldata.
see discount here.http://www.scantool.net/software/alldata-diy-1-month-subscription.html
consider this simple thought.
the brain saw the drivers demand, but could not respond to the demand, ! that is it. (TBW, throttle by wire system)
The list of possibles are huge. i will not attempt to list them all
but will say this, we do all tests on the engine and EFI to see
if there are "other intanglements" ( lean, or other conditions)
or air leaks in the system .
and one more thing, all scan tools (real) have pending pages
got pendings ,while driving? y/n , yes, bingo. if not 123,223
and all scan tools have a freeze frame,
showing the last failure, and all PIDS, related to it
so looking at the freeze frame you can see when it happend
driving, how fast, and Baro readings, RPM, see list. examine all there. to get some idea of the conditions of failure, (it idle?)
This is my first big TAC post. i hope it helps others to understand
the reason the parts guy gets so rich, The ECU is stupid.
all this BS to replace a $5 throttle cable.... sigh. (i lied, its for traction controls,etc)