Observations:
- Selecting sampled data brings up the window/tabs with time plots of Current and BEMF (as expected).
- Selecting "Sample Now" at the lower toolbar will <sometimes> display sampled curves.
- When display of curves fails, then the blue status bar (indicating data transfer?) stops at a random value less than 100%
- Setting a low number of samples (eg. Samp: 200) decreases the probability fail
- Selecting/enabling RT-APP from right toolbar does not seem to influence if sampled curves will be displayed.
- Triggered sampling rarely works (it will always transfer 2000 samples)
- Behavior is same with several USB cables (20cm long and 100cm),
- Behavior is same with several VESCs.
What is wrong? How to get sampled data to be more reliable?
My setup:
- VESC-tool 0.81 on Windows laptop computer, connected via USB Baud: 115200 bps.
- VESC 6, FW 3.28
- FOC
Have no problems with FOC, HW1.12, FW3.27, and win 7 Pro.
But I would like to have more flexibility for zoom and scaling (mostly for RT Data).
For example it would be interesting to stick the 0-100°C for temperature.
Have a Nice Day.
Thierry
ThierryGTLTS: You mean HW4.12, right?
Today I also tried HW4.12, but in Ubuntu/Virtual Box on a desktop computer with Windows 10. Realtime Data and Sampled Data works better with that setup, but still not reliable (same problem, but less frequent).
Realtime Data and Sampled Data works without any hickup at all on my Pi3.
Same cables and controller as before.
score: Windows/PC -2 vs. Linux/Pi3 +1
Now I have the same problem with version 3.29 and Windows 10.
The aquisition display bar stops between 50 or 80% and once it doesn't work, it becomes completely blocked.
Sometimes reducing the samples to 400 may help, but it's far from perfect.
Have you solved the problem?!
Have a Nice Day.
Thierry
Thierry,
I am having the same issues acquiring sampled data with the VESC6 and the VESC-tool. Sometimes it works fine (not often) but most of the time it quits before a full acquisition and does not display any new data. I have tried reseting the VESC, restarting the VESC-tool. Nothing seems to make a significant difference. I have a large ferrite bead on my USB to kill single ended transients, but it still does not aquire the data with any reliability. Let me know if you make any discoveries.
VESC-tool 0.82 on Windows 10 computer, connected via USB Baud: 115200 bps.
Tim
Hi Tim,
It's not related to your cable, but to Windows10, I have also tried compatibility too for Windows 8 and 7, but it doesn't work well.
At work I have a real Win7 Pro, and no problem at all!
Have a Nice Day.
Thierry
Have a Nice Day.
Thierry