The displayed time seams wrong.
If I enable keyboard control and RT data and run the motor for 5 seconds the x-axis shows around 16 seconds.
FW modified 3.27, tool 0.80, custom HW, Windows 7 64 bit.
Is it the same for everbody?
/Eric
The displayed time seams wrong.
If I enable keyboard control and RT data and run the motor for 5 seconds the x-axis shows around 16 seconds.
FW modified 3.27, tool 0.80, custom HW, Windows 7 64 bit.
Is it the same for everbody?
/Eric
You are right, the time scale is not correct. Added to TODO list:
http://vesc-project.com/node/110
Fixed in VESC Tool 0.81
That was quick but not 100% good yet.
Now I get 3.3 seconds is displayed for 5 seconds of running. To measure acceleration, tune PID loops etc the time has to be correct.
Maybe you could send a timestamp (chVTGetSystemTimeX()) with each COMM_GET_VALUES reply?
In the tool changelog it wrongly says FW 3.27 is supported.
I put a toggle of a pin in COMM_GET_VALUES, the average frequency is 33 Hz (30 ms between edges). If you zoom in on realtime data in Vesc-tool the display shows the samples at 20 ms apart.
There is a lot of jitter in the requests, but this will probably differ from PC to PC and different OS.
I added a pull request which fixes that issue and shows the real time data with the correct timing.
Thanks, I was also annoyed with RT problem.
Have a Nice Day.
Thierry
Havent tested a lot in VESC Tool 0.82, but looks like Ackmaniacs pull request results in a bricked temperature graph. When choose the temperature tab instead of the current tab the graph freezes. Maybe I can look into that later. Great that the sources are available now.
Update. It is not just the temperature graph that gets destroyed. In my opinion the whole realtime data graphs are useless in the new VESC Tool. I uploaded a short video here: https://www.dropbox.com/s/oeythjs7g3yjwyj/FW3_29_RealtimeData.MOV?dl=0
You can see that the motor response to keyboard commands instantly when the realtime data is disabled. After enabling the realtime data the update interval of the incoming data stream gets slower over time. Not just the displayed values are delayed, the whole system acts delayed as you can see in the video.
I had a look at this. Do you happen to use a UI scale factor that is not 1 in VESC Tool Settings?
Yes. I did not changed it manually, but with the "auto" enabled I get a UI Scale Factor of 1,18.
That is probably the reason. The new version of qcustomplot supports float scaling, but it becomes extremely slow if that is used. I have disabled ui scaling for the plots in vesc tool 0.83, so this should be solved. The disadvantage of disabling it is that the plots will have a bit lower quality when the scale factor is not 1. Can you give it a try?
Thanks for the fix. Now it is working also with a scale of 1,18 without problems.