PyRow / Raspberry Pi 4

[georgeed]

Is anybody running a version of PyRow on a Pi 4B under Buster? I'm stumped trying to get it to work ...
Connecting to either a PM4 or a PM5 it drops out after the first read.
Using libusb v1.0.22.11312 and pyusb v1.0.0

I have a working instance on a Pi 3B+ (running Stretch) connecting to a PM4 with the libusb v1.0.21.? and pyusb v1.0.0 that's been working fine for 4 or more years - but it also craps out if I connect the PM5

I'm probably missing something obvious - but what!


Thanks, George

[Citroen]

You should ask on https://raspberrypi.org/forums there may be some quirks with libusb on a RPi4 (which gained USB3 and USB-C connectors and a different USB driver chip).

Or open an issue at: https://github.com/wemakewaves/PyRow/issues

I don't have a RPi4 in my fruit bowl.

Otherwise you need to tell us more about how it "craps out".

[georgeed]

Yeah, sorry. "craps out" = appears to just drop off the USB (bus) in the middle of the 2nd call. libusb "debug" messages show nothing strange. I can't find a way to get pyusb to show any diagnostics though. Same with a PM5 on Pi 3 or 4, or PM4 on the Pi 4 - hence I feel it's user error, rather than a RPi4 quirk.

Before state, on the Pi4 with PM4:
ls -l /dev/hid*
crw-rw-rw- 1 pi pi 243, 0 Aug 12 22:14 /dev/hidraw0
crw-rw-rw- 1 root root 243, 1 Aug 12 14:59 /dev/hidraw1
crw-rw-rw- 1 root root 243, 2 Aug 12 14:59 /dev/hidraw2
crw-rw-rw- 1 root root 243, 3 Aug 12 14:59 /dev/hidraw3

After - hidraw0 is just gone (but is still visible to lsusb)
ls -l /dev/hid*
crw-rw-rw- 1 root root 243, 1 Aug 12 14:59 /dev/hidraw1
crw-rw-rw- 1 root root 243, 2 Aug 12 14:59 /dev/hidraw2
crw-rw-rw- 1 root root 243, 3 Aug 12 14:59 /dev/hidraw3

Bus 001 Device 007: ID 17a4:0002 Concept2 Performance Monitor 4

[maidenelk]

Been having a hard time with Pi's Bluetooth as well on a 3B+. I'm working on a BLE Central that'll read workout data and upload it to Logbook. I initially based it on go-row (which uses https://github.com/go-ble/ble) and what I see is that the BLE client eventually hangs on a syscall to read from an HCI socket.

Also tried a USB dongle in case it was the onboard Bluetooth chipset, and got the same result. So, I'm also leaning towards it being a user error, especially since I'm also seeing near-immediate disconnects when I try manually pairing and connecting to another Pi via bluetoothctl.

BUT! I'm now using https://github.com/tinygo-org/bluetooth as the BLE client and am having slightly better luck. It's been successfully scanning for 26 minutes, which is significantly longer than go-row's client would before getting wedged.

Prob not super helpful to you, but figured I'd add another data point just in case!