2011 Pro Check engine..

[greasemonkey3406]

Went for a ride the other night and ended up having to turn around in a parking lot with no snow. Temps went up to 170 but went back down again when I got back in the snow. Then I noticed that the check engine light was on and stayed on til I shut it down. We stopped to have a bite to eat and when I was warming it back up before we left, the light came on again, went out and came on once more while on the way back and didnt come on again.
I fired it up in the garage again yesterday and the light came back on again after a few seconds and stayed on. It doesnt flash and it runs fine. Any ideas on what this could be or how to check to see what the code is?

 

[trestlecreek]

Its your EGT sensor. When starting the snowmobile, have the brake locked on, then while its idling, push the mode button. It will show a 173 code ( if my memory is correct) Its your egt sensor. After you get another one, or take one out of a buddies to check. You will need to start it and let it get to operating temps, ( 110-120) then the system will run its own check and the light will then go out.

 

[greasemonkey3406]

Ok, I tried starting it with the brake on and then I pushed the mode switch but it just cycled through the temp, max speed.... like normal. I pushed the select button a few times and the code came up. 524007 2 and the check engine light keeps flashing and doesnt stop. Is there somewhere I can go to look up the codes?

Edit - Just checked and it was a "signal out of range" code for the fuel resistor. Took it off, checked the resistance and it was exactly at 160 ohms. Plugged it back in and code was gone. Must have been a bad connection....

 

[ak49er]

Similar thing happened here, gained 1800' feet in a single pull, light came on, shut down, restarted, light came back on.
On a whim I cracked the fuel cap. And restarted, light did not come back. Nothing conclusive, but thought I'd share.

 

[Lococoin]

I had the same code about the resistor. Took it off a few times and it hasn't came back. I figured it was a bad connection as well.