I recently bought (what i thought was a decent deal) on a 2016 CFMoto CForce 500 HO. I bought it from a person i have known for years, he had only put about 5 miles on it and parked it due to issues with his knees. Anyway long story short, i bought the unit in mint condition with 5 miles. I got it home and drove it around for a while and everything ran fine. After about an hour or so of riding it, it cut off on me. I started it back up, and went on with my business.
Now anytime i ride it, its not dependable because after about an hour or so of riding, it just cuts off and it's a pain in the rear to get it back started. Even if i get it started as soon as you give it gas it cuts off again. For it to work normally again, i have to let is sit for a few hours or overnight. After it's sat a while it will fire right back up and you can ride it for a hour or so again.
I had read on the forum here that some of the 2016 models have weird issues with the harness going to the fuel pump relay, so i made a pigtail like they have described here, and hooked up and was hoping that was going to fix it, but it didn't. I'm sure someone is going to ask about temperature of the unit when these issues occur the temperature isn't always the same. It goes up to 4 bars, then the fan kicks on and bring it down to 2-3, so the fan seems to be working. I am using the recommended 89 octane fuel in the system, and have even tried 93 octane but didn't help. We've checked the plug and it looks just fine, so it doesn't seem to be rich/lean at all.
I figured i'd post here and see if anyone else has had this issue, or knows someone they can ask how to fix it or what test to do next.
I need to get it into the dealership for the Cylinder Head bracket recall, but they are backed up right now and can't look at it for a few weeks. So i'm trying to resolve this other issue since i have nothing but time now.
Oh the other issue i've had with it sometimes starting it just runs up to 4k RPMS and stays there, and quick on/off of the key, and the idle is reset, so it's not a cable issue mechanically, but maybe a sensor? It hasn't done that in a few weeks though, so maybe it worked itself out.