Closed JaapvanEkris closed 3 years ago
Interesting. I'll see what I can find. What exact model of USB stick are you using?
Maybe you can check by issuing lsusb
on the command line.
Also what permissions does the device get on the system (probably ls -la /dev/bus/usb/001/
)?
Hi Lars,
When I look at the syslog, it is correctly initialised:
`Apr 24 00:33:12 Roeimachine kernel: [ 2.473505] usb 1-1.2: new full-speed USB device number 3 using xhci_hcd
Apr 24 00:33:12 Roeimachine kernel: [ 2.622678] usb 1-1.2: New USB device found, idVendor=0fcf, idProduct=1009, bcdDevice= 1.00
Apr 24 00:33:12 Roeimachine kernel: [ 2.624029] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 24 00:33:12 Roeimachine kernel: [ 2.625256] usb 1-1.2: Product: ANT USB-m Stick`
And the result of the ls /dev/bus/usb/001/
`pi@Roeimachine:~$ ls -la /dev/bus/usb/001/
total 0
drwxr-xr-x 2 root root 100 Feb 14 2019 . drwxr-xr-x 4 root root 80 Jan 1 1970 ..
crw-rw-r-- 1 root root 189, 0 Apr 24 00:33 001
crw-rw-r-- 1 root root 189, 1 Apr 24 00:33 002
crw-rw-rw- 1 root root 189, 2 Apr 24 00:33 003`
When I do a lsusb, It is found and identifies itself as a "Dynastream Innovations"
`pi@Roeimachine:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0fcf:1009 Dynastream Innovations, Inc. ANTUSB-m Stick
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub`
I also moved the USB stick to the other bus, to no avail.
I think I found the issue, will post a fix in a few minutes...
try now 😄
It works! I love it!
Awesome ❤️
I get a fatal error when I activate ANT+ (turned off BLE). When I disable ANT+, it works fine.
Apr 24 00:18:48 Roeimachine systemd[1]: Started Open Rowing Monitor. Apr 24 00:18:49 Roeimachine npm[2263]: > openrowingmonitor@0.7.1 start /opt/openrowingmonitor Apr 24 00:18:49 Roeimachine npm[2263]: > node app/server.js Apr 24 00:18:49 Roeimachine npm[2263]: ==== Open Rowing Monitor 0.7.1 ==== Apr 24 00:18:49 Roeimachine npm[2263]: bluetooth profile: Concept2 PM5 Apr 24 00:18:50 Roeimachine npm[2263]: classic ANT+ stick not found Apr 24 00:18:50 Roeimachine npm[2263]: webserver running on port 80 Apr 24 00:18:50 Roeimachine npm[2263]: mini ANT+ stick found Apr 24 00:18:50 Roeimachine npm[2263]: FATAL ERROR: Error::Error napi_create_reference Apr 24 00:18:50 Roeimachine npm[2263]: Aborted Apr 24 00:18:50 Roeimachine npm[2263]: npm ERR! code ELIFECYCLE Apr 24 00:18:50 Roeimachine npm[2263]: npm ERR! errno 134 Apr 24 00:18:50 Roeimachine npm[2263]: npm ERR! openrowingmonitor@0.7.1 start:
node app/server.js
Apr 24 00:18:50 Roeimachine npm[2263]: npm ERR! Exit status 134 Apr 24 00:18:50 Roeimachine npm[2263]: npm ERR! Apr 24 00:18:50 Roeimachine npm[2263]: npm ERR! Failed at the openrowingmonitor@0.7.1 start script. Apr 24 00:18:50 Roeimachine npm[2263]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. Apr 24 00:18:50 Roeimachine npm[2263]: npm ERR! A complete log of this run can be found in: Apr 24 00:18:50 Roeimachine npm[2263]: npm ERR! /root/.npm/_logs/2021-04-23T22_18_50_090Z-debug.log Apr 24 00:18:50 Roeimachine systemd[1]: openrowingmonitor.service: Main process exited, code=exited, status=134/n/a Apr 24 00:18:50 Roeimachine systemd[1]: openrowingmonitor.service: Failed with result 'exit-code'. Apr 24 00:18:50 Roeimachine systemd[1]: openrowingmonitor.service: Service RestartSec=100ms expired, scheduling restart. Apr 24 00:18:50 Roeimachine systemd[1]: openrowingmonitor.service: Scheduled restart job, restart counter is at 34. Apr 24 00:18:50 Roeimachine systemd[1]: Stopped Open Rowing Monitor. Apr 24 00:18:50 Roeimachine systemd[1]: openrowingmonitor.service: Start request repeated too quickly. Apr 24 00:18:50 Roeimachine systemd[1]: openrowingmonitor.service: Failed with result 'exit-code'. Apr 24 00:18:50 Roeimachine systemd[1]: Failed to start Open Rowing Monitor.