Rocklong,

The new clutches you're getting are probably more related to the recent belt slippage issues that your particular issue.

I've done that to a belt in my RZR 800. I always stuffed a clean micro fiber cloth in the CVT cooling air exhaust before I did a good washing of the engine compartment.

One time I forgot to pull the cloth out, and in about 30 minutes I failed a belt just as you have...the belt got too hot!!

I'd check your cooling air intakes and outlets and make sure there is no blockage.

And perhaps think about how you were driving when it happened, and see if that leads to a reason for excessive heat. I installed a Team Alba temperature gauge in the CVT of my RZR 800,
its incredible how fast the belt can get hot and how difficult it is to drive so that the belt doesn't get too hot.

Just thoughts,

Pirate

 

I’m to scared to even know how hot the belts get. Haha

 

You would be amazed. I was sorta depressed after I put the temp gauge in. I'll be danged if I could keep it out of the red...even with a blow hole fan!

So yes, its scary how hot the belt was for the 7 riding seasons prior....

Pirate

 

Got those same codes when I was running gates belts. Changed out to a oem and problem solved

 

I checked the belt. There is a small wear mark on it. I cleared the check engine light by driving in LOW at 4-5k rpm. Then rode it around for a bit, no issues. Drove it on the road wide open sounded fine, but it’s when I let off the throttle that it throws the code. And it sounds like it’s only firing on one cylinder? Any suggestions beside a belt? It’s on order.

 

Sorry I forgot to post the picture in the last post.

 

I’m still getting the codes at speeds over 60km/h. No issues at lower speeds. I’m going to give this a try. I figure I don’t have anything else to lose.

GILOMEN INNOVATIONS - Boat | Motor | Snowmobile | ATV | Polaris | Seadoo | Yamaha | Skidoo | Repair | Gilomen Innovations | Service | Shop | Northfield Minnesota 55057

https://youtu.be/lEWmjpfRAlA

 

Paul
Did you check to see the cost of it?
What happens if down the road your dealer needs to do some change again to the computer, will that screw up this flash?

 

I'm well out of warranty, so unless Polaris is coming out with a new flash to cure the misfire codes, my General won't be going back to the dealer anytime soon.

Here's the link to pricing.

1000 General - GILOMEN INNOVATIONS

With the US/CAD exchange and shipping, it's going to run me around $600. I'd like to see a cheaper fix, but as it stands, I can't get a good day of riding so it's better for me to pay this then have the General sitting in the garage.

 

Paul has yours been in for recall work? Do you know if they reflashed your ECU? I think there was a recall due to injectors staying open/possible fire hazard.

 

Yes, mine had the re-flash. It wasn't used much since the re-flash, approximately 100kms (60 miles), so I'm really leaning more towards the idea that this is the cause. I've removed my secondary and my primary. Nothing looks out of sorts there and the belt(s) seem fine.

 

Paul i can honestly say that just because the belt "seems fine" doesn't mean it actually is. It could be something as dumb as a slight deviation in the belt that's causing an abnormal vibration that the clutch sensors are picking up on. Polaris sensors for the belts on there machines i've learned are more picky and tempermental then a chick with PMS and a hunger craving...

EDIT : Nvm, just realized how long ago this post was... XD

 

There isn't any belt sensors on a Polaris.


The ECU just monitors rpm versus ground speed and a million other parameters and it is so sensitive on the general and when you have any belt slippage it sets off the code, other things cause it too.

 

And that's a good reason to look at Gilomen Innovations for a solution.

Here's a link:

1000 General - GILOMEN INNOVATIONS

Yes, I have one, I bought a new ECU with their programming on it. Soon to be installed!

Pirate

 

Well, I finally got the Cylinder Misfire Detection Codes 65590 and 65591 after 2,800 miles total (since June 2017) and 400 miles with the Duraclutch installed in early April 2018.
My 2017 Gen 4 was built in early April 2017 which was after the recall/flash fix for the fire problem (17-102) so my ECU probably either has that flash fix or is just a new ECU with the same fixes.

Managed to get out of limp mode and lose the Check Engine Light by driving for less than a mile after resting the machine for an hour or so.

It happened after a 45 minute/25 mile drive on tarmac roads in Turf Mode just as I was getting close to home after having the Door Panel fix work done at Ride Now Phoenix.
It was a hot day yesterday even early in the morning, probably around 85-90F while I was driving. Speeds would have been between 30 and 55 mph.
Gilomen cite constant high speed driving as a possible cause for these codes ( among many others) so I think that is a likely cause in my case.

I will see if it happens again and if so I will check out the Duraclutch & Belt at that time. I am away from home for a while soon so another ride is not for several weeks.

 

Spggy,

If the machine does go into limp mode, stop, shut the engine off, restart and roll easy and in about 1/4 mile the Check Engine Light will go out. No need to let it sit for an hour.

Learned this in Arizona in January...did the hour wait...then next time...less wait...and by the 4th time...just shut it off, started and rolled and click out goes the light...

With the Gilomen ECU...should be a thing of the past. And will know for sure in about 48 hours as we'll be in Moab and rolling on the slickrock!!!

More to come...

Pirate

 

Good tips on not waiting much to restart and go.
Please do let us know if the Gilomen ECU flash solves your problem after MOAB.

 

I will do that, and probably while we are in Moab!!

Hoping for excellent results!!!

Pirate

 

I sent my ECU to Gilomen on Friday and will have it back the end of this week. Only did the troublesome code removals for $200 since I already have a custom tune of my own. We will also be riding in Moab the end of this month so making sure I do not experience these codes again and go into limp mode ... not what I need far back in the hills of Moab going up a slick rock. Will also update this thread with my results regarding the Gilomen ECU fix (after a few weeks of riding to ensure the codes are gone).

 

The reflashed ECU was waiting for me last night when I got home from Canada (for work). The turnaround time by Gilomen Innovations was very impressive. They reflashed the ECU removing the troublesome codes and shipped the ECU back the same day. Whole process took less than a week. I performed the reinstallation procedure this morning and had no issues when I took it for a “hard” ride. Before the reflash I was able to cause the codes to trigger by accelerating fast up to 50 mph then quickly letting off the throttle. So ... hopefully these codes are gone forever. Will update this thread if they come back.

 

I believe the issues Polaris dumped on us are gone with the Gilomen Innovations ECU program.

We've been out on the trails in Moab for six days, did all sorts of trails and all kinds of riding styles...not a single code...just works perfectly.

And the improvements to the ignition and fuel maps....just more power to use!!

Pirate

 

Good to hear. Thanks Pirate for the response. We are also headed to Moab the week after Memorial (when the crowds go home) ... and I am looking forward to enjoying quality riding time with my family ... without issues like this. The door skin replacements for our G4 came in on Friday ... so hopefully dealer can install them before Moab. Last Polaris design issue fix ... I hope ...

 

UTE are you familiar with the Moab trails?

Do you carry a GPS with you?

Pirate

 

I believe 65590 means your left cylinder injector is not working properly ie. not sucking fuel from the tank to the cylinder nozzle. Most likely a wiring issue. If you can, disconnect the wiring from the right cylinder and connect to the left and see if it works to test the injector condition.

 

Sooo...I responded to Jovi79's question on fault code 65590 and sent an e-mail to Terry Gilomen.

Here's what I got back, that I thought I should share:

Terry wrote:

I have performed the ECU false misfire fix to several 2018 Generals that the customer had been having issues with the 65590, 65591, 65592 codes coming up.
The 2016 Generals would of originally not had the misfire issue but if the ECU was ever updated at the dealership they would have the potential problem with the new flash update.
All 1000 Polaris models from 2017 + came with the misfire programming from the factory.
The 2019 models have it also.

So here is some additional information on the issue. I have not heard a word about Polaris fixing the issue. So Gilomen Innovations "fix" is the only one I know of.

Just thought I should share.

Pirate

 

I'm happy for Gilomen Innovations as they should be getting a lot of business from the Polaris community. It just sucks that Polaris won't correct the issue they know exists.


I'm still on the fence about getting my ECU reflashed. I'm not having the code issues unless it's driver induced. Still haven't heard if the Gilomen ECU increases fuel mileage. If it does


I would send mine off tomorrow.

 

I have 2017 rzr 1000 highlifter and been getting the error codes 65590 and 65592... changed my belt an plugs did oil change and all that an still getting error code... so I decided to pull my ECU and send it off to gilomen innovations to get it reflashed.... I’ll post my results next week

 

starky,

I have written to Terry asking your question. Hopefully I'll have an answer today.

Pirate

 

starky,

Here you go:

At cruising speed the millage stays about the same........thanks Stuart!


Pirate