R1 Wurks brushless motors
#661
Motolyser is more accurate - it runs the test in sensorless mode to ensure a more accurate reading.
#662
Tech Adept
iTrader: (4)
I've heard this before but I get consistent readings like that on one of my motors with the same type of spread. At the same time I get very close readings.......consistently.....with other motors. If indeed I shouldn't trust numbers from the skyrc checkers then why are the numbers the same every time I test my motors?
#663
Tech Master
iTrader: (10)
I've heard this before but I get consistent readings like that on one of my motors with the same type of spread. At the same time I get very close readings.......consistently.....with other motors. If indeed I shouldn't trust numbers from the skyrc checkers then why are the numbers the same every time I test my motors?
#665
Anyone Try or using 114 mod software? I think there is a issue with it.
#666
#667
At low rpms both 113-114 the motor cogs for a mm or 2mm of throttle input
0-1/4 throttle fine just after cog then gone the rest of the way.
The other mod programs seem to be fine...
0-1/4 throttle fine just after cog then gone the rest of the way.
The other mod programs seem to be fine...
#668
Are you running it with a mod motor, or in 17.5? Whats your motor timing set at? What transmitter do you use? What neutral % is the speed control set at? Which mod program still worked for you? What make of motor?
#669
Thanks
#670
Tech Master
iTrader: (204)
I've heard this before but I get consistent readings like that on one of my motors with the same type of spread. At the same time I get very close readings.......consistently.....with other motors. If indeed I shouldn't trust numbers from the skyrc checkers then why are the numbers the same every time I test my motors?
#671
109,110
#672
Also 107 that it shipped with was fine as well.
#673
Contact the support at the above email with your info and they will work with you, you can even call them at 949 353 5566. They don't come on here often, so a direct contact is your best bet in getting the issue rectified.
#675