So, if any of you have read my post about losing my old controller (Sevcon Dragon 8 ), you know Votol was a huge disappointment for me. However, my Fardriver ND84530 just arrived a few days ago and it's everything I hoped for and more. I got motor-spin as almost soon as I hooked up the battery, phase lines, hall sensors and throttle. I did have to disable the motor temp sensor in the app, since the controller expects 6 wires on the hall-sensors plug (V+, GND. temp sensor and 3 hall-sensor wires), and my motor doesn't have a temp sensor wire (from what I see, this is pretty common). Mind you, my motor is some unbranded 6kW, 17", 25kg mystery, so I was really impressed it spun without lots of configuring (the Votol EM30s failed to run it at all before it died).
I started playing around with the PC and Android apps at this point. All I can say is that it's OK. The Android app is solid enough to use (I heard reports of common disconnects, didn't experience nothing like that). The PC app is OK. Far from perfect (crashes every now any then, and sometimes it resets input values for no reason), but I was happy it worked out of the box.
The motor then started to beep two short beeps and then a long one, indicating it wants to run auto-learning. Took me a bit to get it to run the auto-learning process because I was terrified of letting my 25kg wheel run at unknown RPM on my janky test-stand. I kept setting the phase-current really low (~80A), or play with the throttle limits. That made the process fail to complete.
The way you run the self-learning is you hold the throttle open (not fully open, 50% seemed like enough), and let the motor spin up, spin down, stop (you need to release and re-pull the throttle here), reverse and so on. I was terrified it'll spin up to 3000RPM, fly off the stand and break something (or someone). After a while I grew a pair of Ukrainian balls and let it rip. It finished the self learning without breaking anything in under 1 minute (never passed 900RPM).
I've ran it since at 1500RPM (a little over 100km/h) to make sure it doesn't got ape-shit at high speeds. Next up, I'll assemble my bike back up, wire the controller into the brakes and other circuits and start testing it under load. Excited to get my bike running again.
I started playing around with the PC and Android apps at this point. All I can say is that it's OK. The Android app is solid enough to use (I heard reports of common disconnects, didn't experience nothing like that). The PC app is OK. Far from perfect (crashes every now any then, and sometimes it resets input values for no reason), but I was happy it worked out of the box.
The motor then started to beep two short beeps and then a long one, indicating it wants to run auto-learning. Took me a bit to get it to run the auto-learning process because I was terrified of letting my 25kg wheel run at unknown RPM on my janky test-stand. I kept setting the phase-current really low (~80A), or play with the throttle limits. That made the process fail to complete.
The way you run the self-learning is you hold the throttle open (not fully open, 50% seemed like enough), and let the motor spin up, spin down, stop (you need to release and re-pull the throttle here), reverse and so on. I was terrified it'll spin up to 3000RPM, fly off the stand and break something (or someone). After a while I grew a pair of Ukrainian balls and let it rip. It finished the self learning without breaking anything in under 1 minute (never passed 900RPM).
I've ran it since at 1500RPM (a little over 100km/h) to make sure it doesn't got ape-shit at high speeds. Next up, I'll assemble my bike back up, wire the controller into the brakes and other circuits and start testing it under load. Excited to get my bike running again.
