FLIPSKY Electric Speed Controller for Skateboard Mini FSESC4.20 50A Base on VESC® 4.12 with Aluminum Anodized Heat Sink 12s esc

Seller claims ESC can handle up to 50A continous current. But battery cables are 12AWG which is rated up to 20 amps....

I have four of these in ex rental Ninebot max scooters. Ive used both the stock 10s battery pack as well as built my own battery packs of varying voltage. Even with the stock battery the performance is significantly better than the stock speed controller, much more torque and slightly better speed but where this controller really shines is when an option called field weakening is enabled. This will boost top speed on 10s to a little over an honest 30mph. There is a trade off with this and that is increased power consumption, the controller will also quick start getting hot and thermal throttling. I've tried unsuccessfully to resolve the heat problem by several methods. Even with the heatsink attached to a large fan cooled heatsink bonded with thermal epoxy I still run into thermal throttling after several minutes of full throttle. That said, Im pumping close to 3kw through this tiny controller at full throttle. This is a huge amount of energy and is very impressive. I've also been running this on 13s with no problem. Attached are logs of my scooter on 13s. I'm getting 37, 38mph, gobs of power. SI much motor is overheating to the point I drilled holes in the side covers to allow air circulation. It actually works. Lol.

I am using a pair of these for a full size metal R2D2 and they work pretty well. They aren't perfect, but they are a good build at a good price. THE VESC software (downloaded separately) has a bunch of options to tweak. They make me a little nervous, but so far, they have done a good job.

Mine bricked while I was configuring it. Now it won't even turn on. I'd like my money back please. Here are the logs : 2026-08-19 20:37:13: VESC® Tool 7.00 started 2026-08-19 20:37:13: Status: Not connected 2026-08-19 20:37:13: WARNING (:0 ): QSslSocket: cannot resolve EVP_PKEY_base_id 2026-08-19 20:37:13: WARNING (:0 ): Incompatible version of OpenSSL (built with OpenSSL 1.x, runtime version is >= 3.x) 2026-08-19 20:37:13: WARNING (:0 ): QSslSocket::connectToHostEncrypted: TLS initialization failed 2026-08-19 20:37:13: WARNING (:0 ): "" 2026-08-19 20:37:16: Status: Connected (serial) to ttyACM0 2026-08-19 20:37:16: DEBUG (:0 ): Reloading user interface due to configuration change. 2026-08-19 20:37:16: WARNING (:0 ): Param group "gpd" not found. 2026-08-19 20:37:16: Status: Connected (serial) to ttyACM0, limited mode 2026-08-19 20:37:17: Status: Motor config updated 2026-08-19 20:37:17: Status: App config updated 2026-08-19 20:37:23: DEBUG (:0 ): "No carrier" 2026-08-19 20:37:24: DEBUG (:0 ): Reloading user interface due to configuration change. 2026-08-19 20:37:24: WARNING (:0 ): Param group "gpd" not found. 2026-08-19 20:37:24: DEBUG (:0 ): Reloading user interface due to configuration change. 2026-08-19 20:37:24: WARNING (:0 ): Param group "gpd" not found. 2026-08-19 20:37:27: Status: Motor config updated 2026-08-19 20:37:27: Status: App config updated 2026-08-19 20:37:27: Status: Motor config updated 2026-08-19 20:37:27: Status: App config updated 2026-08-19 20:37:27: Status: Motor config updated 2026-08-19 20:37:27: Status: App config updated 2026-08-19 20:37:28: WARNING (:0 ): QXcbConnection: XCB error: 3 (BadWindow), sequence: 740, resource id: 11254390, major code: 40 (TranslateCoords), minor code: 0 2026-08-19 20:37:33: DEBUG (:0 ): "No carrier" 2026-08-19 20:37:43: DEBUG (:0 ): "No carrier" 2026-08-19 20:37:46: Status: Motor config updated 2026-08-19 20:37:49: Status: Serial port error: Resource temporarily unavailable 2026-08-19 20:37:49: DEBUG (:0 ): Reloading user interface due to configuration change. 2026-08-19 20:37:49: WARNING (:0 ): Param group "gpd" not found. 2026-08-19 20:37:51: Status: Not connected 2026-08-19 20:37:53: DEBUG (:0 ): "No carrier" 2026-08-19 20:38:01: WARNING (:0 ): Could not restore mc conf 2026-08-19 20:38:03: DEBUG (:0 ): "No carrier" 2026-08-19 20:38:05: WARNING (:0 ): Could not restore app conf 2026-08-19 20:38:13: DEBUG (:0 ): "No carrier" 2026-08-19 20:38:23: DEBUG (:0 ): "No carrier" 2026-08-19 20:38:33: DEBUG (:0 ): "No carrier" 2026-08-19 20:38:43: DEBUG (:0 ): "No carrier" 2026-08-19 20:38:49: WARNING (:0 ): QXcbConnection: XCB error: 3 (BadWindow), sequence: 948, resource id: 11293065, major code: 40 (TranslateCoords), minor code: 0 2026-08-19 20:38:51: Status: Invalid serial port: /dev/ttyACM0 2026-08-19 20:38:53: DEBUG (:0 ): "No carrier" 2026-08-19 20:38:53: Status: Invalid serial port: /dev/ttyACM0 2026-08-19 20:39:03: Status: Invalid serial port: /dev/ttyACM0 2026-08-19 20:39:03: DEBUG (:0 ): "No carrier"

This is a very nice implementation of a VESC based controller and is working very well in my custom ebike that has a 250W motor and a 10s battery. Having said that if one wants to get into the VESC ecosystm it is definitely a commitment in that you either have to have the electronics knowledge and/or be able to learn the specifics of these type of controllers in order to be successful with them. If you are not able to do this then these type of controllers may not be for you as it's easy to damage pretty much each and every component in your build if one is not careful and aware. I gave it a 5 star rating for easy to use because it was for me but this may not be the case for everyone.