I put a Vortex ECU in my 2018 FE501 fresh out of the crate. The bike would start and die every cold start, bike would always fire up normally the second time. Other then the initial cold start issue the bike always ran strong and never missed a beat. I adjusted the throttle as mentioned in the above video as well, no change So, last spring when Slavens Racing released the GET ECU with their alleged proprietary tuning I bought one. Put the GET in the bike, set the TPS as instructed. The bike would fire and stay running every cold start. Initially I was pumped, that is until I got a few miles on the bike and noticed a lean pop on decel, a backfire at WOT around 8k RPM and the bike would also die under a WOT pull shifting from 5th to 6th gear. I called and spoke to Jeff at Slavens, first he had me change some settings myself which made no difference. He then had me send the ECU to him, I was told he didn't see anything wrong with it. Also was told that he spoke to GET andwas told the dying during during an upshift after an overrev is normal and that I shouldn't be revving my bike that high. The best part about him telling me not to rev the bike that high is, I had initially requested that the rev limiter be set at +200 RPM over stock, rather then the +400 RPM they were setting the GET ECU's at. He told me that +200 RPM is a waste of time and wouldn't be noticed, so he'd set it at +400RPM and if I didn't like it, he'd change it back. That all changed when my bike was dying during WOT pulls, then it was I shouldn't be revving the bike that high. Anyway, he updated updated the software. I had been riding the bike with the Vortex while the GET was gone and realized how much better my bike felt, it pulled harder and had absolutely no issues with backfiring or lean decel popping. When the GET arrived back to me, I immediately put it back on the bike went a mile down the county road I live on and guess what, it backfired at around 8k RPM just like it had been doing all along. I came back home, put the Vortex back in and that GET has been sitting in my toolbox since.
Fast forward to August, I'm getting ready to turn my bike into a snow bike. I called Jeff at PR2, I liked what he had to say, we discussed the cold start issue that I've had with the ECU. I decided to send him my Vortex, he did 5x5 mapping (5 dirtbike/5 snow bike maps) The weekend after christmas 2019 I took the bike to Wyoming for it's maiden snow bike trip. The bike starts and dies cold every time and is hard starting sometimes when warm. The bike runs flawless otherwise. I spoke to him about the issue when I returned home, he gave me a couple things to try, before sending the Vortex back to him. I haven't been back out west yet to try out what we discussed.
The other day PR2 posted about mapping Vortex and GET ECU's. I immediately called Jeff at PR2 and explained the issues I've had with my GET ECU that has Slaven's mapping in it. I ended up sending my GET to him as well. I'm confident that he will fix the issues with the GET ECU as well. I hope I get the GET back before our next trip next weekend, so I can try it out and compare it aginst the Vortex in the snow. The Vortex is superior on pavement and dirt in my opinion. Maybe it's just the poor Slaven's mapping, but i hope to find out.
Anyway, it's not just PR2 that has some issues. it's everybody! These issues are to be expected when purchasing ECU's that have the same mapping for (in my case) 3yrs of bikes 17-19. As everybody knows, there are no 2 bikes that will make the same power with the same map. I had a similar issue when having my diesel truck tuned, my truck didn't like the original tunes I received. I spent the better part of 4 weeks, doing data logs every night, emailing them off, downloading the new tunes the next day and repeating. It sucked and I was pissed, but in the end they nailed the tunes, my truck runs hard and the tunes are clean.
Hopefully PR2 will get the Vortex starting issues figured out. Sorry for the lengthy post, I just wanted to share my experience and make it known that it's not just PR2 having issues.
