I'm using VESC Tool v0.91 and custom VESC board with hall sensor inputs.
I spin the motor at constant RPM with my controller and all the real time data shows up in VESC Tool very well, no problems. RPM, Duty Cycle, Motor Current, etc.
When I go to the Sampled Data tab and try to click "Sample Now" the loading bar goes to about 30% then stops and never does anything. I've tried all the other buttons too, stopping and starting the motors, changing RPM. The BEMF tab is the same.
Am I doing something wrong in VESC Tool or is there something wrong in hardware?
Thanks
The sampled data currently only works over USB, so if you are using some other interface that might be the cause. I will probably have a look at that soon and make it work over all interfaces.
Hi!
I use an USB-cable to communicate with the VESC (Mini FSESC 4.20), and I have the exact same problem as OP. So this problem is certainly not only related to non-USB communication.
EDIT: Btw, I forgot to mention that I use VESC tool v. 1.28
I noticed the "Sampled Data" has a problem downloading to completion when you have the "Realtime Data" enabled. Turn off the "Realtime Data" whenever you want to "Sample Data" and it works every time.
I also think the x-axis is not getting updated properly. When you change the Dec (Decimation?) to something other than 1, the time axis doesn't change.
Hi, I have the same problem, where sampled data never loads to 100%, and real-time data (when selected separately) also halts once the motor is spun. For reference, I do not have a controller connected, I am just using the keyboard inputs in the VESC tool. (Update: I also tried this with UART commands from an Arduino, so that the USB connection to my PC was dedicated to streaming sensor data and got the same results). The "Experiments Tab" under motor settings works well, but I cannot figure out how to edit the outputs of the experiment for the plot (I am using FOC and would like to plot phase currents and rotor position, with no use for a wireless controller, I am just doing load tests with FOC for robotics). Any advice on getting the data saved reliably? I am using VESC Tool 6.02, have tried with Windows and Linux, and with firmware 6.0 and 6.02.
Elizabeth Mountz
FIXED - I switched to firmware 3.55, the oldest one in the VESC Tool archive and it does not seem to have this data logging glitch. Guess it was introduced down the road.Only worked a few times, now just randomly, about 1% of the time it will log the data and not get stuck.
Elizabeth Mountz
Just to update this thread, the only way I could fix the data logging issue was to switch to VESC 4 hardware instead of VESC 6. Perhaps just a bug on the newer hardware.
Elizabeth Mountz