![]() I was following the most people suggestion on the install page and assumed this would protect qbike from getting way behind changes in PyQtGraph. The first time I did this, I pulled a local copy of PyQtGraph into the qbike folder and added it to the. It is build on PyQt4 which it will install as part of its dependencies. I use PyQtGraph, by Luke Campagnola, for the graph displays in qbike. I need to try the Suunto stick again but that’s for another day. Could be the PyUSB b1 package is now broken, could be the Garmin stick uses a different ANT+ key. It doesn’t work with the Garmin stick, hanging after printing antnode created from stick. Nevertheless, the package seems to build and install each time (even if edited).Ĭurrent status (date of post): qbike worked with the Suunto stick and without Johannes’ is_kernel_drive_active patch. Python setuptools does a lot of work here and there are one or two warnings. To get the is_kernel_driver_active function, you need to downgrade PyUSB to the b1 version of the package. Could the pi kernel hold onto TTY interfaces when it runs headless but let them go when input devices are detected? Back inside and running headless, I first got device not found errors (see the hardcoded product id issue noted above) and then the device busy errors. So I tried his fork and found the pre-installed raspian PyUSB library didn’t include the is_kernel_driver_active function.Ĭommenting out Johannes’ change in python-ant /src /core /driver.py, got everything working out in the shed with the Suunto stick, keyboard, mouse and screen attached. Johannes Bader said he had trouble with AlternateSetting and Resource busy errors and made a fork to fix them. ![]() It must be possible, but there are some quick and dirty workarounds. qbike.py while logged in to a VNC session (with tightvncserver). Sor far I’ve not worked out how to combine starting sudo. It is annoying because I’d like to test and develop via VNC with the pi running headless. the dialout group) and other obscure settings - but haven’t got the python program using the device as a normal user. I’ve looked through various permissons, group memberships (i.e. The remaining problem here is that /dev/ttyUSB0 is only usable by root. Plug the stick back in and check for a /dev/ttyUSB0 node that represents the ANT+ device. The prefix numbers control the order in which the rules are setup by the daemon. Is this what they call programmed obsolescence? If so, my next device will not be a Garmin for sure.Pi$ sudo nano /etc/udev/rules.d/les At this point i cannot pair my 610 with the computer. Tried intalling Training Center + Ant Agent. Tried intalling Ant Agent plus communication plugins. The more i use Garmin the more i like it.Įdit 3: Still trying. Now that i am reinstalling the process bar is stuck at some 70%, sounds familiar to me. let's see if i can make it work again.Įdit 2: I love it. Tired! I wish one day Garmin decides to make devices with a simple micro usb for charging and connecting and stops annoying us with such "special" specs.Įdit 1: I finally uninstall it with "total uninstall". Then i have uninstalled plugin but I'M UNABLE to unistall ANT Agent. No activities can be transferred from device to computer. All of a sudden either plugin communicator or Ant agent (or both) stopped "seeing" my garmin 610.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |