Third Party Hardware

I'm evaluating the Mboards BLDC ESC V6 and FlipSky FSESC6.6 for use as controllers in a machine where a motor controls a wheel that must maintain an accurate RPM between about 1000-6000RPM. When the motor parameters are detected properly, the Mboards VESC can repeatedly maintain the commanded RPM anywhere in that range. The FlipSky VESC is always off by a scaling factor dependent on the RPM. I tried tweaking every parameter allowable and cannot get the FlipSky VESC to be spot on accurate.

Sometimes with higher voltages cross-conduction occurs due to fast rise in drain source voltage driving gate voltage above threshold. 

I came with this solution. When 15V driver voltage  charges gate to 10V C1 charges to 5V. When driver voltage goes to 0V it should put negative voltage on gate and making it harder to cross-conduct and also make it faster to turn off. For example driver cap will be 1u, C1 100n, gate C 10n.

Hi,

I'am running my FSESC 4.2 with FW 5.2  and anti spark switch. Is there a way to deactivate the 'roll to start' function ?

best

Philo

Hello. I just got a single Flipsky FSESC 6.6 to control the motor of a traxxas car robot. I have a few questions given that its based on the VESC project.

1. Is it possible to retrieve the inbuilt IMU sensor data? if so how can I?

2. I need to upgrade my firmware. I want to control the servo of a car but on the vesc tool 3.0, I do not see the vesc_servoout.bin option. What are the works around to this? Thank you very much

Hi Vesc Folks, 

How can I change the PWM output polarity of the phase control outputs? Obviously I would like to change all six of them. I need them to be active low for my purposes.

I was not able to find a #define for it. It either does not exist or it simple did not catch my eye.

Can anybody point me to the correct direction in the code?

I have 2 Flipsky FSESCs like the one seen in this picture. Yesterday, one of them was disconnected during a ride, and after re-connecting it to power, it won't power on. No LED lights, nothing. I probed the 5V rail and I'm getting 5.1V, but when I probe the 3.3V rails, I'm getting 0V. This leads me to believe that the DRV8302 chip is working as it should be. The VREG (579-TC2117-3.3VDBTR) on the back of the PCB is heating up.

Hi guys,

I've been reading a bunch and have already successfully debugged a flipsky 4.2 I had. However, I'm having problems with a Seekerboard VESC 6 based ESC that I cannot seem to solve.

Long story short:

- Seekerboard/Boundmotor ESCs have no RST visible and CLK and IO have to be soldered directly to the hardware as diagram below (already did it and I'm trying flashing without RST).

As I mentioned in the title, I am designing a vesc75 / 300 based controller. There is a problem with my first prototypes that I cannot understand. PCB can successfully communicate with vesc tool. Real time data etc. I can reach parts. However, whenever I try to detect the motor, the connection is broken and the vesc resets itself when the power stage is supposed to work.

I think the problem is due to power stage. I suspect Mosfet drivers but not sure. If anyone has an idea, please share it with me

Thanks everyone!

Recently connected my Flipsky Dual FSESC4.20 Plus to with a NRF51 Bluetooth module connected to it to the VESC tool and now the Bluetooth module won't work. If I changed something on accident, any guess to what changed that broke this? I'm extremely unfamiliar with the VESC tool.