VESC 6.0 Data Logging?

Always worth tossing in the tried/true Eagletree datalogger v4. Simple inline, and can add sensors for temp/rpm/etc. etc.

FYI, I did the beta testing of Ackmaniac's update for VESC 6 compatibility.

After some corrections, it works great now (Android only, but no need of special BT module).

I noticed that the communication protocol changed (a little), has anyone a description / example on how to implement the latest version so I can update my Matlab code?

Check RollingGecko Arduino library, branch VESC 6 :

https://github.com/RollingGecko/VescUartControl/tree/VESC6

I finally re-worked my Eagle Tree v4 eLogger. Didn't like the unwieldy wires, so eliminated them. Now a simple XT90 in/out and much easier to drop inline to test a setup:
https://goo.gl/zVovUj

And some testing on my guest board, and GF's Vanguard i built for her:
https://goo.gl/Y6ou4z
https://goo.gl/bYowz1

Great info to know - a couple good hills around my house, one longer ride and one quick ride on her board. See consistently around 46-51A peak load. Both single setups and will test next with dual and VESC Six to compare.

Hi, 

Can anyone tell me how can I log data from VESC tool to my computer in excel file or something like that ? I would like to process and analyze the data like motor current, battery current, torque ,etc? Is there any script or software available online? I am using a Ubuntu 18.04 OS.

Thank You

Hi, I wrote a DLL for my company's Dyno software. I can post some info (if you have some knowledge on C programming)

I used this data struct to receive and process the data message:

Data in in Big Endian format, and scale is placed at the right as a comment (1 to 1e6)

typedef struct 
{
  char start_byte; //=2
  char msg_len;    //=65
//contents ------
  char buffer_id; // (cmd) = 4 = GET_VALUES
  char temp_fet_filtered[2];   //10
  char temp_motor_filtered[2]; //10
  char avg_motor_current[4];   //100
  char avg_input_current[4];   //100
  char avg_id[4];              //100
  char avg_iq[4];              //100
  char duty_cycle_now[2];      //1000
  char rpm[4];                 //1
  char input_voltage[2];       //10
  char amp_hours[4];           //1e4
  char amp_hours_charged[4];   //1e4
  char watt_hours[4];          //1e4
  char watt_hours_charged[4];  //1e4
  char tachometer_value[4];    //1
  char tachometer_abs_value[4];//1
  char fault;
  char pid_pos_now[4];         //1e6
  char controller_id;
  char NTC_TEMP_MOS1[2];       //10
  char NTC_TEMP_MOS2[2];       //10
  char NTC_TEMP_MOS3[2];       //10
//--------------
  char CRC16[2];
  char end_byte; //=3
} VESC_FRAME;

Did you get to log the data?