Posts: 6
Threads: 1
Joined: Aug 2020
Reputation:
0
Posts: 6
Threads: 1
Joined: Aug 2020
Reputation:
0
forgot to mention, the NMEA usb output was removed to add the keyboard. results are the same.
Posts: 6
Threads: 1
Joined: Aug 2020
Reputation:
0
SignalK is still outputting NMEA-0183 attitude data. Data is zeros as there is no MMU installed.
Posts: 6
Threads: 1
Joined: Aug 2020
Reputation:
0
Got a feeling I need to use Kplex to solve this problem. Going to learn more about it now.
Posts: 303
Threads: 5
Joined: Mar 2018
Reputation:
24
Device or resource busy in SK means you have something else that has already opened the gps device. Try
lsof | grep tty
To see what processes have open tty devices.
Posts: 6
Threads: 1
Joined: Aug 2020
Reputation:
0
Here is the result:
grep tty
bash 785 pi 0u CHR 4,1 0t0 7186 /dev/tty1
bash 785 pi 1u CHR 4,1 0t0 7186 /dev/tty1
bash 785 pi 2u CHR 4,1 0t0 7186 /dev/tty1
bash 785 pi 255u CHR 4,1 0t0 7186 /dev/tty1
chromium- 1609 pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1697 llvmpipe- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1698 llvmpipe- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1699 llvmpipe- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1700 llvmpipe- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1701 chromium- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1702 chromium- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1703 chromium- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1704 chromium- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1717 GpuWatchd pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1718 ThreadPoo pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1719 ThreadPoo pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1720 Chrome_Ch pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1609 1721 VizCompos pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
pi@openplotter:~ $
The two listed devices on the serial config are the GPS on 0 and the NMEA 0183 output to the tiller pilot "Tillie" I wonder if the SDR dongle is confusing the system? It is connected to USB, but was not given a tty address. I need to read up and understand the differences between tty0 and tty1
Posts: 6
Threads: 1
Joined: Aug 2020
Reputation:
0
Killed Pypilot, got this:pi@openplotter:~ $ lsof | grep tty
node 393 pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 618 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 619 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 620 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 621 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 622 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 705 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 962 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 963 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 964 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 965 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 1332 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 1333 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 1334 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 1335 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
node 393 1336 node pi 46uW CHR 188,0 0t0 11096 /dev/ttyUSB0
bash 754 pi 0u CHR 4,1 0t0 7186 /dev/tty1
bash 754 pi 1u CHR 4,1 0t0 7186 /dev/tty1
bash 754 pi 2u CHR 4,1 0t0 7186 /dev/tty1
bash 754 pi 255u CHR 4,1 0t0 7186 /dev/tty1
chromium- 1461 pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1547 llvmpipe- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1548 llvmpipe- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1549 llvmpipe- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1550 llvmpipe- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1551 chromium- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1552 chromium- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1553 chromium- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1554 chromium- pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1555 GpuWatchd pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1557 ThreadPoo pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1558 ThreadPoo pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1559 Chrome_Ch pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
chromium- 1461 1560 VizCompos pi 11r REG 0,17 4096 8096 /sys/devices/virtual/tty/tty0/active
pi@openplotter:~ $
Had a parameter wrong in SDR, was UDP, changed to client, it works now. GPS is also working now.