Python errors when starting odrivetool, slow to connect

#1

Hi all

I am getting the following errors when i start odrivetool in Windows 10

ODrive control utility v0.4.11
c:\users\unknown\appdata\local\programs\python\python38-32\lib\site-packages\fibre\shell.py:104: RuntimeWarning: coroutine ‘InteractiveShell.run_code’ was never awaited
console.runcode(‘import sys’)
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
c:\users\unknown\appdata\local\programs\python\python38-32\lib\site-packages\fibre\shell.py:105: RuntimeWarning: coroutine ‘InteractiveShell.run_code’ was never awaited
console.runcode(‘superexcepthook = sys.excepthook’)
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
c:\users\unknown\appdata\local\programs\python\python38-32\lib\site-packages\fibre\shell.py:106: RuntimeWarning: coroutine ‘InteractiveShell.run_code’ was never awaited
console.runcode(‘def newexcepthook(ex_class,ex,trace):\n’
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
c:\users\unknown\appdata\local\programs\python\python38-32\lib\site-packages\fibre\shell.py:109: RuntimeWarning: coroutine ‘InteractiveShell.run_code’ was never awaited
console.runcode(‘sys.excepthook=newexcepthook’)
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
Please connect your ODrive.
You can also type help() or quit().

Odrive will connect but it takes close to 1 minute and i haven’t managed to make my motor running. So i am posting this as i don’t know if this effects its functionality.

Did anyone else had the same issues ? How do i fix the error messages?

#2

Same here.
Not sure, but at the end of the Python installation, there was a message asking if I want to allow Python to execute more than 260 lines (or something like this) of code - it is some type of win10 security feature. Could this have something to do with these warnings at odrivetool startup?
And also, as the Phyton is 32-bit installation, should it be manualy placed into Programs(x86) or it doesn’t matter, because the default installation path is in C:\Users…?

#3

OK, have reinstalled python with admin rights. Allowed it to execute more than 260 symbols at the end of the installation and I made the installation for “all users”, which automatically placed python in Programs(x86) ( now I get it :smiley: ). Reinstalled again the odrivetool with “pip install odrive” through an elevated prompt, but it seems the source package is still there, because the installation was very brief. Started the odrivetool again through an elevated cmd prompt and again it showed the same errors. Actually the Odrive connects to the PC, but while I’m trying to follow the calibration procedures it gives another errors and I’m not sure if they don’t mess with the whole procedure?
If someone knows, what is causing those errors at start-up, would be very helpful, as I think, that they might be related to the other errors I get after the Odrive is connected.