Polaris Discussions about Polaris ATVs.

2007 Sportsman 500 EFI Code 22

Thread Tools
 
Search this Thread
 
  #1  
Old 06-01-2017, 06:23 PM
mecheng76's Avatar
Weekend Warrior
Thread Starter
Join Date: Jun 2017
Posts: 13
Likes: 0
Received 0 Likes on 0 Posts
Default 2007 Sportsman 500 EFI Code 22

Can't seem to get this code to clear.
replaced the TPS connector with a repair harness. Reference voltage 5v. Resistance of TPS checks good per the manual. Base setting of TPS measures 1.11v, also good per manual.
Engine bogs if you flick throttle at idle. No power over 40 mph. Overall does not run bad at all.
dealer cleared codes and checked sensors over the winter, ran for a while without codes returning. The will not clear no matter how long battery is disconnected.
not sure what to chase next... I see others mention maybe tbap harness?
 
  #2  
Old 06-01-2017, 06:45 PM
old polaris tech's Avatar
Polaris ATV Expert
Retired and loving it!
Join Date: Jun 2008
Location: North Texas
Posts: 24,352
Likes: 0
Received 34 Likes on 34 Posts
Default

Manuals say 85% of efi problems are wiring or connector related,not the sensors themselves which I believe is true.If you used a Polaris harness repair kit most wouldn't last very long.Same thin wiring and connectors as the original. Most common problem on the 500 was the tbap cheap connector or wiring.Sometimes even the grommet under the tbap can crack and suck air.Item#9 in the thumbnail pic. Look for obvious signs of bare wires or soft feeling wires.Some times you can wiggle the wiring at an idle and engine rpm will change.A lot has been posted on this over the years and I replaced a lot of harness kits only to have them fail again.Better harness repair kits are available here for the tps and tbap.https://otbpowersports.com/products/
 
Attached Thumbnails 2007 Sportsman 500 EFI Code 22-546568a710897d3854eb469f997074fe930cb65c.png  
  #3  
Old 06-01-2017, 08:17 PM
mecheng76's Avatar
Weekend Warrior
Thread Starter
Join Date: Jun 2017
Posts: 13
Likes: 0
Received 0 Likes on 0 Posts
Default

I used an aftermarket harness, but not OTB. Seems to be good quality but I will keep an eye on it.

will bad wires at the tbap cause a code 22? at other sensors?

I pulled the tbap and the grommet was definitely cracked and not in the best of shape. don't think that would cause a code 22 that won't clear though, do you?

Also, the dealer told me only they can reset blink codes - is that accurate?
 
  #4  
Old 06-01-2017, 08:36 PM
user493's Avatar
Moto Psycho
Join Date: May 2008
Location: Michigan
Posts: 8,747
Likes: 0
Received 3 Likes on 3 Posts
Default

Most of the time you can reset the blink codes by unhooking the battery. If that doesn't work I don't know how else to do it.
 
  #5  
Old 06-01-2017, 08:37 PM
old polaris tech's Avatar
Polaris ATV Expert
Retired and loving it!
Join Date: Jun 2008
Location: North Texas
Posts: 24,352
Likes: 0
Received 34 Likes on 34 Posts
Default

Codes thrown aren't always accurate,but code 22 does show low voltage to the tps. Possible the kit you installed is the problem area. I would at least get a new t-bap grommet and go from there unless you want to just go ahead and order both a new tps and tbap kit @39 bucks each and solve any future problems with the tbap acting up also.From my experience the t-bap harness and connectors gave us the most problems on the 500 efi.Only remember replacing a few tps harness kits.Once repaired right codes are usually easy to remove or just clear themselves.
 
  #6  
Old 06-01-2017, 09:02 PM
mecheng76's Avatar
Weekend Warrior
Thread Starter
Join Date: Jun 2017
Posts: 13
Likes: 0
Received 0 Likes on 0 Posts
Default

I just went out and poked around again... there is a harness under the TB that is clearly pinched by the exhaust pipe heat shield.. looks like I just found more wires to trace. My biggest question was if any other short could cause the 22 to show up, especially since I traced the TPS circuit and can't find a problem.

The 22 was before and after the TPS repair kit; I probed everything before and after and the old connector checks good - I went ahead and changed it just in case the wire was still in the process of failing.
 
  #7  
Old 06-01-2017, 09:17 PM
old polaris tech's Avatar
Polaris ATV Expert
Retired and loving it!
Join Date: Jun 2008
Location: North Texas
Posts: 24,352
Likes: 0
Received 34 Likes on 34 Posts
Default

Trace this harness down. Probably leading the crank position sensor at the stator cover...another area that I've found shorts in by wiring rubbing against the starter. Zip tie this harness up to where it's away from the engine after you repair any damaged wire.This may or may not solve the 22 code.
 
  #8  
Old 06-01-2017, 09:36 PM
mecheng76's Avatar
Weekend Warrior
Thread Starter
Join Date: Jun 2017
Posts: 13
Likes: 0
Received 0 Likes on 0 Posts
Default

will do, thanks for the advice!
 
  #9  
Old 06-25-2017, 05:14 PM
mecheng76's Avatar
Weekend Warrior
Thread Starter
Join Date: Jun 2017
Posts: 13
Likes: 0
Received 0 Likes on 0 Posts
Unhappy still no luck

finally had some time to get into it.
I traced every wire down on this thing and it all checks out. Even where the wires were rubbing on the heat shield - only damage to the loom, not to the wires.

I started it up again.. same code 22. if I flick the throttle, there is a serious bog and occasionally a backfire & die.

What's next?

I haven't tried making a TPS tester yet.

Beyond that???
 
  #10  
Old 06-25-2017, 05:53 PM
old polaris tech's Avatar
Polaris ATV Expert
Retired and loving it!
Join Date: Jun 2008
Location: North Texas
Posts: 24,352
Likes: 0
Received 34 Likes on 34 Posts
Default

Code 22 does refer to the tps. Either connection problem or short to ground. This code may not always be correct that I've found.Back firing and bogging,erratic idle was one of the more common symptoms of the t-bap wiring harness or connector. If you've replaced the tbap sensor split grommet you found I'd still think it's a t-bap problem just from all the ones I had to replace. But the best way is to probe the pins and wires on the t-bap and also the tps wiring harness and connector to see if you can narrow down which one might be the problem.
 



All times are GMT -5. The time now is 01:34 PM.