You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using version 6.05 of VESC Tool with 6.05 firmware in a Trampa VESC 6 MK VI. I'm using a Dell XPS15, Windows 11, i9-12900HK, 64GB RAM with a 4k monitor and screen scaling of 125%. If I run VESC Tool in one-fourth of my screen, everything works fine. But if I go full screen while monitoring realtime data, the motor stops running as soon as I click the Realtime Data FOC tab or Rotor Position tab. The same thing happens when I click "Sampled Data". Even on the tabs where the motor does not stop spinning (Current), the redraw rate slows down noticeably. Sometimes, if I set a duty cycle and click the play button, it will run for a couple of seconds before stopping. There are no fault codes. I believe the high resolution just takes too long to redraw so the keepalive packets are not sent regularly enough. When running full screen like this, it looks like I'm probably maxing out my single-core CPU performance. This is a fast expensive laptop, so that shouldn't be the problem.
The text was updated successfully, but these errors were encountered:
I am using version 6.05 of VESC Tool with 6.05 firmware in a Trampa VESC 6 MK VI. I'm using a Dell XPS15, Windows 11, i9-12900HK, 64GB RAM with a 4k monitor and screen scaling of 125%. If I run VESC Tool in one-fourth of my screen, everything works fine. But if I go full screen while monitoring realtime data, the motor stops running as soon as I click the Realtime Data FOC tab or Rotor Position tab. The same thing happens when I click "Sampled Data". Even on the tabs where the motor does not stop spinning (Current), the redraw rate slows down noticeably. Sometimes, if I set a duty cycle and click the play button, it will run for a couple of seconds before stopping. There are no fault codes. I believe the high resolution just takes too long to redraw so the keepalive packets are not sent regularly enough. When running full screen like this, it looks like I'm probably maxing out my single-core CPU performance. This is a fast expensive laptop, so that shouldn't be the problem.
The text was updated successfully, but these errors were encountered: