Third Party Hardware

Hi, I am trying to develop my own 75V 100A vesc based on 75300 hardware.

My first prototype runs motor pretty well, but the phase current looks a bit noisy.

So I replaced shunt resistor 0.0005R →0.005R as I read on one article how to reduce the current noise.

and also I modified to source code to

#define CURRENT_SHUNT_RES 0.005 as well.

But the strange thing is that the measured motor current on VESC TOOL is about 10 times higher than before.

The input battery current is similar as before.

There’s a possible fault on mine, the ‘sw’ connection only works every 2nd toggle to switch and the voltages dont seem right. ie

h = on sw=3.25v
l = off sw=0v
h = on sw=3.0v <-----
l = on sw=0.125v <------
h = on sw=3.25v
l = off sw=0v

repeat…

SW line is connected to my bike alarm/ign. control is via pc123 opto-coupler as the output is 84v. vesc GND and SW are connected direct to opto-coupler.

Hey there,

like the tiltle states, i have successfully destroyed a Flispky FSESC 75350.

Problem is, i am not quite sure about what exactly happend and how to avoid it when the next controller arives.

So i was installing the FSESC on a stock sur ron with stock battery(90A BMS) and engine.

Because i was dumb and thirsty for power the battery current was set way too high(150A).

Hi guys, did anybody try to make his own driver which using STM32-F407VGT6? 

I'm researching now, every flipsky driver using F405, so i want to change it to F407, am I still can upload a code in it using Vesc Tool?

Thanks.
 

Hey gang,

I have a Flipsky 75200 that was working perfectly until a careless move on my part that damaged the USB communication on the Flipsky (and on my PC :( wahhh).

Any ways the controller still seems to function fine, but no USB. I checked the uart ports and there is no data. CAN does seem to be broadcasting correctly.

Are there any other ways to connect to Vesc tool? Can it be done over CAN? I suppose I could put a new microcontroller on but that is my last resort.

-z

Dear All,
I would like first to thank all the members on this forum who shared their knowledge.
So, I have decided to design a mid-range ESC 14s 50 Amps based on a downgrade of the  A200S_v2.1.
I have selected discrete FET drivers, motor phase current sensing but No CAN, No IMU, No servo input.
Just throttle and brake using ADCs.
Here is the first draft of the schematic and any feed back will be welcome.

Yafo_1450_v0.pdf

Dear all,

I have generated with success the binary firmware ver 6.05 for mini4, using the provided  hwconf/other/hw_mini4.c and   hwconf/other/hw_min4.h files.
Therefore, I do not understand why HW_HAS_DRV8301 is defined in hw_mini4.h,  knowing that there is absolutely no DRVxxx hardware on the MINI4 schematic.

#ifndef HW_MINI4_H_
#define HW_MINI4_H_

#define HW_NAME                    "MINI4"

HI All,

I'm working for a robot project planning to use ESP32 to control VESC via UART.
But the UART of my VESC 6 didn't give any response.
I've tried connect VESC-Tool through the UART but not working  (UART<>USB board to PC)
(Its work for my older VESC4 HW)

Details:
TX_SCL_MOSI
PA7(ADC12_IN7) / PB10

RX_SDA_NSS
PA4 / PB11

fw:6.02 (no hw limit)
hw:60
no NRF
App: No App / PPM / UART also not working for UART

Anyone knows the problem?
Thanks!
 

Hi, This is Ranjith, Im trying to develop a custom Driver based on VESC 75_300 schematics.

There is a major issue im facing right now, which i couldn't figure it out by myself, my hardware design has two boards,

- The Driver unit board has the mosfet, shunt, temp sensor and the signal connector that reaches the second board (Control Unit).

- The Control unit board has the rest of the components.

In this design we are using a different mosfet which is IPT029N08N5 instead of IRF7759L2PbF.

So the Issues are ; 

I keep seeing this error when connecting vesc to tool. "The connected VESC has newer firmware than this version of VESC Tool supports. It is recommended that you update VESC Tool to the latest version. Alternatively, the firmware on the connected VESC can be downgraded in the firmware page. Until then, limited communication mode will be used."

It updates but it says it fails to erase boot I believe.

When I try to run motor detection I Get same error message as the ESC has newer firmware please help anyone I am also running focbox TENKA if that helps.