VESC_TOOL 0.87 (and not 0.84) has support for something called "BLUEZ". I suspect it has something to do with bluetooth. I've never used bluetooth,
So when I start vesc_tool, I have to wait 30 seconds for the message: "Cannot find a running Bluez. Please check the Bluez installation.".
So... for the todolist: Either: Speed up the detection of the "running bluez". But I suspect that htis is just a library call. The library assumes that the calling app has no business running if the connection cannot be found, so waiting is reasonable.
The workaround would be to detect: bluez not found last time, require user interaction to retry the connection....