VESC Tool

I'm working on developing custom VESC hardware, and when I try to connect the VESC Tool to it I get an error stating that it "could not deserialize motor configuration." I'm able to communicate with the custom hardware, but this error seems to be preventing me from writing the motor configuration to the VESC.

My understanding is that this is because the VESC tool does not recognize my custom firmware. Is there a way that I can create a custom build of VESC Tool that will recognize my custom firmware or is it possible to override this error somehow?

So here is the silliest question yet. I downloaded vesc_tool_free_linux.zip and unzipped the file. So now I have a binary file vesc_tool_6.02 how in the world do I run it in linux?

I have a VESC 6 EDU from here: https://trampaboards.com/vesc-six-education--with-imu-p-34332.html

I had some bad luck in a past

Im using vesc for my rover, and when im trying to move it with power off, my motor wheel works like generator creating micro impulses to my flight controller. My fc didn`t like it, and it restores to default. Is it any possible way to cut off regenerating capabilities using my vesc?

Hey guys. I am building a small wind turbine and want to run tests on my generator using a "back-to-back" configuration where a PMSM is driving my generator (stepper motor). I am using VESC 6 MKIII to drive the PMSM, but I have some issues with the setup wizard in VESC Tool. The most important part for me is to know how much power the output shaft of the PMSM is driven with (simulating wind power), and real-time data screen shows this. However, I am not sure whether it is correct.

I am using the VESC-Tool logging function to track the data after my experiments with a BLDC motor and I haven't found a thorough explanation of the over 50 values it tracks in the resulting csv. Some are self-explanatory, but some are just confusing to me. Especially the difference between the 'normal' and 'setup' variant of some values. e.g. 'ms_today' and 'ms_today_setup'. They are not the same and seem to be running on different clocks. Similarly the difference between 'current_motor' and 'current_motor_setup' is unclear to me.

I'm a bit new to electronics, forgive me if I say something stupid.
I currently have a servomotor running with a vesc and it has an incremental encoder. However, I have this desrm50-hfa0-k21 absolute encoder and I would like to test it on this motor. However, I don't know how to configure it or how to connect it to Vesc. If you can help me.

hi, 

I have seen online some people configuring their bms through the vesc tool.

I did not manage to do so.

I have a vesc and a ble dongle connected to the vesc. the bms is connected to vesc over can and I can see the realtime data of maxkgo bms.

I would like to know how to have the maxkgo appear in vesc tool side menu (like ennoid I saw online).

I can see a device on CAN being detected but it says motor 60. not sure why it does not say BMS.

how to change battery parameters, I can't do it! I used a 36v battery and replaced it with a 48v battery but the display is not showing the correct voltage on the RT

Hello,

I try to setup motors FOC without using the GUI. The aim is to configure the vesc and the motor automatically with a python script. I would like to know if there is a way to do this configuration without the GUI. I search into vesctool and pyvesc source (https://github.com/LiamBindle/PyVESC/tree/master), and that's what I got:

class DetectApplyFOC(metaclass=VESCMessage):

    id = VedderCmd.COMM_DETECT_APPLY_ALL_FOC

    fields = [