You are here

Third Party Hardware

Single Flipsky FSESC 6.6 getting started and IMU data

Submitted by alexantosh on Wed, 2021-04-07 12:32

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

How to change the Phase PWM polarity

Submitted by Boben on Fri, 2021-04-02 20:51

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?

FSESC 4.12 Power Issues

Submitted by moneybags on Tue, 2021-03-30 08:01

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.

Target VESC has no space to be flashed with ST-Link

Submitted by Thi4g0tk on Sun, 2021-03-28 14:50

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).

DIY vesc 75/300 variant power stage problem

Submitted by motordriver111 on Sat, 2021-03-27 21:44

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!

 

 

Pages

Subscribe to RSS - Third Party Hardware