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
The cfclient has a logblogs tab that can also save logging data on the go. This seem to fail on windows.
OS: Windows 11
Cfclient: latest master
How to recreate:
1- Connect to the crazyflie with the cfclient, start the logblock tab, and start logging of one of the logging variables:
2- The terminal says: INFO:cfclient.utils.logdatawriter:Started logging of block [sensors/magnetometer] to file [C:\Users...\AppData\Local\Bitcraze\cfclient\logdata\20220708T11-45-56\sensors-magnetometer-20220708T11-45-59.csv] or something similar.
3- If you go to that file, the folder doesn't exist.
Also the menu option 'go to config folder' does not seem to work either
The text was updated successfully, but these errors were encountered:
So we have done some research, and apparently, this happens when python is installed from the Windows Store, which is apparently in a different folder: C:\Users\USERNAME\AppData\Local\Packages\PYTHONVERSION\LocalCache\Local\Bitcraze\cfclient
This was very unclear as the Appdata module still opens the regular one: C:\Users\USERNAME\AppData\Local\Bitcraze\cfclient\ and it still does so for the config.
No clear solution for this but we should warn people with the installation instructions
The cfclient has a logblogs tab that can also save logging data on the go. This seem to fail on windows.
OS: Windows 11
Cfclient: latest master
How to recreate:
1- Connect to the crazyflie with the cfclient, start the logblock tab, and start logging of one of the logging variables:
2- The terminal says: INFO:cfclient.utils.logdatawriter:Started logging of block [sensors/magnetometer] to file [C:\Users...\AppData\Local\Bitcraze\cfclient\logdata\20220708T11-45-56\sensors-magnetometer-20220708T11-45-59.csv] or something similar.
3- If you go to that file, the folder doesn't exist.
Also the menu option 'go to config folder' does not seem to work either
The text was updated successfully, but these errors were encountered: