[Hunterworks]

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.

 

[Pirate]

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

 

[Spggy]

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.

 

[Pirate]

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

 

[Spggy]

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.

 

[Pirate]

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

Hoping for excellent results!!!

Pirate

 

[UTEngineer]

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).

 

[UTEngineer]

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.

 

[Pirate]

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

 

[UTEngineer]

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 ...

 

[Pirate]

UTE are you familiar with the Moab trails?

Do you carry a GPS with you?

Pirate

 

[Bat]

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.

 

[Pirate]

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

 

[starky]

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.

 

[Pirate]

starky,

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

Pirate

 

[Pirate]

starky,

Here you go:

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


Pirate

 

[Phuksakes]

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

 

[Pirate]

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

Looking at the codes you're getting, its Misfire Detection and Terry Gilomen will fix that! Did you get the performance upgrade as well?

Pirate

 

[Keever01]

Just got my general (2017) a few weeks back and after a creek ride, my check engine light came on. It kind of put the machine in "limp mode" (I couldn't get it to go over 30 mph.) Took it back to the dealer and they said it was some sort of a drive shaft sensor (I could be wrong about exactly what it was but, the light didn't come back on after the repair) which they replaced. Today, the light came back on with the two codes listed in the title (65590 and 65592) which, after a bit of research, I found to be something with the spark plugs. Pulled them out and they look brand new. Blew out the chambers, plugs and boots and will ride it again tomorrow to test it before we head to Brimstone on Thursday. Any other ideas as to what these codes mean? Any tips would be appreciated. Also, if the check engine light comes on, if I turn the machine off then back on, the performance returns to normal. I will be calling the dealership Tuesday for help but wanted to ask here for a quicker response (my local dealer is closed Sundays and Mondays). One more bit of info, the creek ride referred to earlier was basically some splashing of water....no deep holes and nothing over the wheels.

the exact thing happened on my brand new machine with only 50 miles on it! They says needs new belt had burn spots! unbelievable!

 

[Pirate]

The Misfire Detection issue is one that is totally random when it shows up, and when it goes away...until the next time.

The intent of the ECU Misfire Detection programming was to detect a cylinder misfiring, shut the fuel off to that cylinder...to prevent buildup of raw fuel in the muffler and potential of fire.

But it's too sensitive. If the ECU responds to what it sees as a misfiring cylinder, it puts the fuel injection in "Limp Mode" and the Check Engine light comes on.
Stop, shut the engine off, and restart...the Limp Mode is gone and in a quarter mile or so the Check Engine light goes out.

Polaris did a recall in mid-2017 for 2016 and early 2017 Generals. The recall was to replace a steering column fastener and reprogram the ECU. Well the fastener was BS just to get you to bring your machine to a dealer. The ECU reprogramming gave us the Misfire Detection issue.

I got mine done in September 2017. No problems at all. Went from Southern Colorado to Arizona in January 2018. First ride, 8 miles in...right under the highway...boom...limp mode and check engine light. Installed my DuraClutch kit in October 2017. So I called them. They had heard people talking about belt slip. So they sent me a new belt...no issue. Another Primary clutch with the other weight set in it. Nope that wasn't it. reviewing things, the belt slip would be the ECU and Crank Position Sensor losing sync for an instant. That doesn't happen unless you're under water. So kept digging for info and communicating with DuraClutch...back to Colorado. Not sure how, but I stumbled over Gilomen Innovations. Talked with Terry.

Just bought a new ECU with his full program...a fix for the Misfire Detection, 8-9 more hp, cooler running. Talked with Terry a number of times...I'm a good rep for them...
and I've never had the problem since and neither has anyone, that I know of, that got their ECU programmed by Gilomen Innovations.

My 2016 diagnostic codes list doesn't have these two codes. But looking them up...I'm certain they are referring to the same issue.

My experience and engineering background.

Pirate