YOU DA MAN TUFFY :huepfenicon111::yr1::clap:

 

I stopped by my Polaris dealer today and they gave me a copy of a bulletin from Polaris regarding blink code 26.

Some of the 2010 RZRs have been showing code 26 for no reason. Apparently this is a calibration glitch and the only RZR that the code is used on is the RZR-S international version with turf mode. So all the 2010 RZRs sold in the USA and Canada can ignore the code 26.

Here is a picture of the bulletin:

YOU DA MAN TUFFY :huepfenicon111::yr1::clap:

Good info Cliff...

 

bout time eh...thanks for the info:ride:

 

Awesome info Cliff...hopefully now that Polaris has clarified this guys with drivability issues can look past "code 26" and start to find their real issues. And for those who are still skeptical(and there will be some I bet)..look at the schematics..as I mentioned in a post in the code 26 thread,the VSS does NOT communicate with the ECU and therefore cannont cause performance issues, unless maybe it's harness was shorted to another harness(extremely unlikely) And in that case you WOULD get a check engine ICON.

 

I was under the impression that whenever Polaris was considering a bigger motor (WEBER)the light would blink.....

 

Good job Cliff :ride:

 

gee just like i have been saying...its a ghost code only codes that turn the check eng light on count....but hey nobody listens to me......

i just love it when what i have been saying for months is proven corect

 

It's hard to humble when you good :rofl3: Post awayopcorn:

 

So if speed sensor is not connected to the ecu what's it connected to?

 

the ecu....lol but its their for the speedo and for awd use mostly....not fuel mangmt

( i was going to be a punk and say its conected to the front wheel but you did ask in a real way so no joking with reply)

 

Good, that means I don't even have to check for a Code 26...:rofl3:

 

Great find shame Polaris owners have to learn about it here, 3 dealers know I have the code 26 problem that they could not resolve nobody has contacted me, Polaris knows I have the problem nobody has contacted me, Monday I will make some calls see if they even have been notified.

Look at the date on the bulletin took them since January to figure this out, impressive response time lol

At any rate I am glad they finally addressed the issue now owners like Highoctane can take has back to the dealer so they can figure out whats really wrong, guess mine can go back so they can try and figure out why it sometimes will idle real low to the point where the engine is about to die then backfire, Brad burditt needs to call his dealer see if they know about the code 26 bulletin they have had his RZR for 2 weeks now:scared2:

 

Great find shame Polaris owners have to learn about it here, 3 dealers know I have the code 26 problem that they could not resolve nobody has contacted me, Polaris knows I have the problem nobody has contacted me, Monday I will make some calls see if they even have been notified.

Look at the date on the bulletin took them since January to figure this out, impressive response time lol

At any rate I am glad they finally addressed the issue now owners like Highoctane can take has back to the dealer so they can figure out whats really wrong, guess mine can go back so they can try and figure out why it sometimes will idle real low to the point where the engine is about to die then backfire, Brad burditt needs to call his dealer see if they know about the code 26 bulletin they have had his RZR for 2 weeks now:scared2:

Just to clarify my machine has no issues at all...I only got involved in that thread to try to help others who ARE having issues figure out their problems..I have a bit of Polaris troubleshooting experience and was about 99.9% sure the VSS issue was having nothing to do with the drivability problems and could see that the code issue was throwing some people and dealers apparently. I felt that once the code was found they weren't looking any farther. As sad as it is I have learned to troubleshoot issues myself instead of relying on dealer techs(ie some high school kid working a part time job) Not saying all are bad,there are some great Polaris dealer techs...but IMO they are the minority. I can say highschool kid working a part time job part...because that is exactly what I did when I was in highschool, worked as a tech at a Polaris dealer :rofl3:
The EFI on these machines is not as advanced as a modern Auto..it lacks several sensors. Many things can cause drivability issues and NOT throw any codes...you have to get down to the basics...proper fuel mixture and ignition ...
Many of the sensors will only trip a check engine light or code if they completely fail, either shorted or open..an inaccurate sensor may cause intermitten poor drivability without ever tripping a check engine icon...also many things are not monitored at all...low fuel pressure..NO code..cyl missfire(plug fouled,bad plug wire ect)...NO code...intake leak...NO code..clogged injector....NO code..ect ect Some dealers rely way too much on Digital Wrench instead of good old fashion mechanical troubleshooting.

 

well after all this, 12 pages total, i checked mine and yes it was there, but since it has probably been there for a year i had already decided it was just the speedo's way of telling Polaris it was pissed for doing away its clock on the 2010.:rofl3:

 

Any way to clear the code now that it is determined it is a ghost code? Unplugging battery for days did not work for me.

 

The Polaris sheet for the 26 blink code has been out since July 2010. It does nothing/says nothing to solve the code itself and the check engine staying on for mine. When it 1st started I could flip my battery kill switch and then come back in a bit and turn the power back on and it would clear the code and the check engine. Now the code and check engine just stays on and no other codes come up.

No resolve from Polaris for this yet and it's been a few years. Anyone got an idea on how to kill this international turff code and get the check engine to go out?

 

ttt