Thanks for your suggestions.
I'm also seeing some strange differences in how the two types of Ant+
dongles I have (current models from Garmin and Cycplus.)
The Cycplus for example does not appear to support a get_interface control
request. That prevented the libant library from using it. They wer
On Sat, Feb 5, 2022 at 10:26 AM stuart lynne wrote:
>
> Most people are using a generic libusb-win32 driver for Ant+ dongles.
> I have two types, Garmin and Cycplus, and both show up as Dynastream
> as the manufacturer, but they do have minor differences, so even if the same
> chip from Dynastrea
Most people are using a generic libusb-win32 driver for Ant+ dongles. I
have two types, Garmin and Cycplus, and both show up as Dynastream as the
manufacturer, but they do have minor differences, so even if the same chip
from Dynastream, different configuration possibly.
In driver details, that sh
On Fri, Feb 4, 2022 at 4:40 PM stuart lynne wrote:
>
> Yes, I'm looking at claim_interface/release_interface. It seems to take
> a bit of a song and dance to get it to work.
>
> And I'm definitely seeing different results between Linux and Windows.
> I can live with that, platform.system() can be
Yes, I'm looking at claim_interface/release_interface. It seems to take a
bit of a song and dance to get it to work.
And I'm definitely seeing different results between Linux and Windows. I
can live with that, platform.system() can be used to differentiate with
different solutions.
A bigger issue
On Thu, Feb 3, 2022 at 7:25 PM stuart lynne wrote:
>
> I am working with libant and pyusb to support Ant+ devices.
>
> The issue I am trying to fix is preventing access to a device that is already
> open by another process. There may (usually will) be multiple Ant+ devices
> plugged in, and one
