I don’t work for Flipsky in any capacity. I just know how the market works, and I know that they are a company that I want to support. They do take customers advise. They have literally ask me for it, and every time I’ve had a question or a comment about one of their products, they’ve responded within 24 hours. They also have a clone of the ODrive ESC, which just tickled me pink. They really won me over with that release- also selling closed loop hybrid stepper motors! I like where their engineers heads are. This is how all small companies start out.
Imo, this is a much more productive critique, but I’m not really understanding you. I get that you’re having a firmware update issue, but how do you know you aren’t having a com port error? I saw your post on the VESC website, this is what you get when you connect your board:
2020-06-27 12:57:07: VESC® Tool 2.06 started
2020-06-27 12:57:08: Status: Not connected
2020-06-27 12:59:04: Status: Invalid serial port: \.\COM3
2020-06-27 12:59:19: Status: Connected (serial) to COM3
2020-06-27 12:59:19: Status: Connected (serial) to COM3, limited mode
2020-06-27 12:59:58: DEBUG (:0 ): Reloading user interface due to configuration change.
2020-06-27 12:59:58: WARNING (:0 ): Param subgroup “hfi” not found.
2020-06-27 12:59:58: WARNING (:0 ): Param group “balance” not found.
2020-06-27 12:59:58: WARNING (:0 ): Param group “balance” not found.
2020-06-27 12:59:58: WARNING (:0 ): “can_mode” not found
2020-06-27 12:59:58: WARNING (:0 ): “can_mode” not found
Looks like a com port issue to me. Have you tried on another PC?