General discussion

I am currently designing a wireless controller that displays the VESC data (voltage, current, speed, etc.). I am using 2 arduinos that are connected to 2 NRF24L01 transceivers. The sending arduino is located on the skateboard and sends the telemetry data from the VESC to the receiving arduino. I am having trouble coding the transmitter side of the project as I do not know how to send the multiple variables to the receiving arduino. I am unfamiliar with this library for the NRF24L01 transceivers. Here is the code I have so far for the transmitting arduino.

I have a Flipsky 200a (vesc 6 based) esc and a turnigy CA80 160kv motor powering a go kart running on 12s.  I have a 1:7 gear reduction on 10in tires.  I have a few questions concerning the esc:

1. The esc says the motor is a 120a motor, but the manufacturer says it should be 200a.  Is this a problem with the motor or esc or what?

2. When I take a corner quickly, the esc will sometimes cut out. Is this some kind of g force cutoff?

Hi everyone,

I have a problem with my electric board, everything was fine with my motor in the bdlc mode, but today i tried to move for the FOC mode ( lower noise is enjoyable :) ) but here is my issue : when no one is on the board it runs quite well, but with a load on it, sometimes the motor lose his trust for a moment and just after spin at full speed. I don't understand why, it is a pretty serious problem as you can see because it can quickly unbalance the user.

Is it my configuration on vesc ? or another problem ?

I would like to use a vesc controller and a bldc motor in an application where a controllable torque is needed at low or zero velocity.

I am able to use the motor at high speeds with foc in sensorless mode. But it fails to run smoothly with foc in encoder mode. The both the motor and the encoder are detected and calibrated correctly with the VESC tool. 

I am using a VESC 6 and i am controlling the motor by setting a desired current (which I would like to result in a constant torque) over UART.

Hi all,

I'm setting up a CAN controller for a VESC 6.0 using an Atmega2560 , I'm able to control RPM, Duty, and Current ring and get back  all the info from Message 5 but is not clear form me ho to dynamically set the maximum motor current. Not intended as primary control, just the maximum current as in the FOC parameter.

Here is the portion of the code from comm_can.c

Hey Guys, 

I recently picked up a VESC 6+ and I can see that it has a built in IMU. I have managed to write my own code to access and use all the commands built into the VESC  i.e. SetDuty, GetVals... etc...

However I have not managed to find any info on extracting the IMU Data. I would assume this to be straightforward as the VESC tool can do this over USB, however documentation is slim. Does anyone have any pointers to get me started? I am writing in python due to its ease for rapid prototyping.

Hi everyone,

A bit of background, I'm running a fsesc6.6 on a razor scooter. I created a sketch using the solid geek libraries, my first screen displays volts,motor amps and watts and amps displayed in a progression type dial. I am trying to create another page for the fault codes (this is my first arduino/c++ project) like they way it comes up in ackmans bluetooth app. 

I have found the fault_data in datatypes but not sure how to use it 

I have been trying to find a way to accurately know what voltages will be seen by the high side fets with different motors. So I would set the resistance and inductance of the motor and can see the peak voltages.

Using the simulation that Benjamin made in LTSpice shows very small voltage peaks which I don't really believe.

If I just model one phase path with 2 IRF7769 mosfets, then it looks much more realistic. Plus you can model the motor phase much better. 

I'm building a project where I use an Arduino to control a single HAL-sensored outrunner motor through a VESC. The interface program I wrote sends a number of 'moves' to my device, which are then supposed to be executed one by one.

These 'moves' consist of a start-time, end-time, up-ramp-time, a down-ramp-time, a top speed in RPM, and a final tachometer position (the destination). Additionally, my program is aware of the minimum RPM I need to send to make the motor move. I also have access to current tachometer position and current RPM.

Hello, 

I'm interested into the compatibility of the vesc 6.0 firmware with standart ebike systems (display, pas, torque sensor). Before trying to reinvent everything myself, I'm investigation what already has been done in the field. Is there a list / compilation somewhere of vesc code optimization for ebike ? For an instance, maybe someone already worked on implementing 5s or bafang display protocols ?

Thank you for your time,

felix