I am trying to display the current speed on a ST7735S SPI display using an arduino D1 Mini Pro as an intermediary and a VESC FSESC Mini V6.7 Pro. I am trying to follow this video VESC LCD Display - YouTube as a guide however he uses an I2C display what would i need to change if I'm using a I2C LCD display.
Currently building an electric surfboard, Im using a 100/250 VESC, 65161 Flipsky waterproof motor, 18S battery pack (75.6Vdc peak) . Currently redesigning my cooling system and want to use a passive heat sink located at the rear bottom of the board near the motor. The battery pack is in a waterproof case located at the top front of the board for weight balance reasons, this would result in the cables between the ESC and battery pack being about 1.5 meters apart.
I'm fairly new to firmware, however I am trying to display the current speed to a OLED display, using only the VESC and an OLED display. I found a tutorial online that uses an arduino nano as an intermediary however I was wondering how I might be able to achieve this without the arduino. Since the VESC has a microcontroller on it wouldn't it be possible to directly calculate the speed and read that data to the display?
Below is the tutorial im referencing: VESC LCD Display - YouTube
I have a 18s12p Lithium Ion battery pack with the VESC BMS, my issue is that when my charger is engaged the first cell in the pack reaches the preset cell voltage first eg. 4.2V, 3.9V, 3.6V and the charger will disengage rather than stay on charge and bleed the first cell and let the other cells catch up to the required preset voltage, this is resulting in only allowing me to charge my pack to around 80%-85%. Is there a setting in the VESC Tool that I am missing?
Any help would be greatly appreciated!
I'm using a flipsky dual 4.20 to drive 2 flipsky 6354 motors.
I'm new to brushless control, but I think I've got the settings mostly how I want them. One thing that intrigued me was the killswitch option.
When I activate the killswitch (whichever option I choose; I can manage with any of them) it only kills one motor (local to the killswitch).
Is there a way to communicate that killswitch to both sides via CAN? It seems like it should kill everything, but it does not.
Hey, everybody.
Hi, so I'm in search of replacement connectors/pigtail harness kits for the new style 75100 , 75200. I swap these controllers out on builds quite often and I have used up the connectors ( damaged, lost ect....) I contacted flipsky and they aren't interested in selling me any kits, said that I get an extra one if I buy another ESC. I already own three of them, with an answer like that I don't really want to buy another one. So does anyone know where I could purchase these wiring kits or what the connector is (eg. Jst-ph 1.5mm? ) Here is a pic of the connector/plug
Hello everyone,
I'm new to the VESC world and not an electronics specialist, but I have a small project in mind. I want to control a VESC using a Teensy 4.0 (Arduino framework). I've successfully communicated with it using UART, but I'm considering the ability to send commands while still being able to modify VESC parameters using a mobile app with a BLE adapter.
Hi guys,
I am new here, live in Austria and am looking for help in the forum because of a defective VESC from Flipsky.
I'm using the controller and an Outrunner 6474/170kv to drive a roller drive for a Mountenbike.
Unfortunately,
the circuit board got a little wet during the last ride and the VESC switched off.
After removal and 2 days drying, the controller can no longer recognize the motor and read out the values.
A red LED flashes every two seconds.
