DanGT86
100 kW
Free under 2 conditions:
Controller is a Flipsky 75100 Pro with Aluminum PCB
I bought this controller to learn about the VESC environment. That was a bad idea because I don't have the skills to know if its me or the hardware failing. Hard to learn anything like this.
Currently it will not connect to vesc tool. It tells me the com port is incorrect. It will not connect via bluetooth either.
It has run a few motors successfully. I had it running about 40battery amps at 72v. Seemed to function ok but every few rides it would do this same problem where it would lose connection and throw firmware warnings. I would reflash the firmware to fix it. But now that it wont connect to anything I am out of ideas. It also had a little trouble starting from a dead stop about 50% of the time.
I tried 2 different PCs and had the same result. I was trying to rule out com port driver and windows issues regarding this connection problem.
Anderson connector in the pic is through a resistor for anti-spark purposes.
- buyer pays shipping so I dont spend any more money on this dumb thing
- buyer tells me what they did to get it working. I would like to learn something from this other than not to buy any Flipsky products. I would really like to know what it takes to get it running again.
Controller is a Flipsky 75100 Pro with Aluminum PCB
I bought this controller to learn about the VESC environment. That was a bad idea because I don't have the skills to know if its me or the hardware failing. Hard to learn anything like this.
Currently it will not connect to vesc tool. It tells me the com port is incorrect. It will not connect via bluetooth either.
It has run a few motors successfully. I had it running about 40battery amps at 72v. Seemed to function ok but every few rides it would do this same problem where it would lose connection and throw firmware warnings. I would reflash the firmware to fix it. But now that it wont connect to anything I am out of ideas. It also had a little trouble starting from a dead stop about 50% of the time.
I tried 2 different PCs and had the same result. I was trying to rule out com port driver and windows issues regarding this connection problem.
Anderson connector in the pic is through a resistor for anti-spark purposes.
Last edited:
