seandepagnier
pypilot automatically detects and connects to a signalk server on the network. So this uses zero conf, and no configuration is needed whether pypilot runs on openplotter, or pypilot is running on a separate computer like tinypilot connected to openplotter by network.
So to utilize signalk you only need to communicate with signalk-node-server which by default is running on openplotter. This is not really specific to pypilot anymore, but the default port is usually 3000 and it uses websockets or other transports, check the signalk documentation.
I moved this from the multi function display topic, since it seems like it is more appropriate here.
I start my computer before the tinypilot.
When the tinypilot starts there is no automatic connection from the SignalK server in the tinypilot
When I connect to port 3000 either TCP or websocket, I get connection refused
When I connect to port 20220 (NMEA0183) I get the tinypilot paths added to the SignalK data browser
Frankly I don't care about the autoconnect, but as I read above correctly the connection on port 3000 should not be refused.
Tinypilot configured to connect to an existing SSID and a fixed IP-address.
SignalK from the standard setup as mentioned on the github page on both ARM64 and X86_64
Tinypilot SK connected to the ARM64 and via the ARM64 to the X86_64.
OS Ubuntu 20.04 Focal / ARM64 (odroid N2), with github OpenCPN 5.2.x
OS Ubuntu 20.04 Focal / x86_64 (laptop i5) with stable OpenCPN 5.2.0
Also the missing keys on the pypilot plugin:
every start from OpenCPN I have to first select 127.0.0.1 and then the client IP address from the tinypilot. (This might be more appropriate in the pypilot_pi thread though).
Both on ARM64 and laptop.
I mention it here since it might be somehow related.
If I might roundup, I read there is supposed to be some automatic connection feature, which I I don't understand.
Therefore it is hard to trace the problems I face.
I will check tomorroe if the autoconnecting works as intended when the tinypilot provides the host AP.
One last thing:
tc@box:~$ netstat -a
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 (null):20220 (null):* LISTEN
tcp 0 0 (null):2947 (null):* LISTEN
tcp 0 0 (null):80 (null):* LISTEN
tcp 0 0 (null):33333 (null):* LISTEN
tcp 0 0 (null):22 (null):* LISTEN
tcp 0 0 (null):23322 (null):* LISTEN
tcp 0 0 (null):23322 (null):52482 ESTABLISHED
tcp 19 0 box:38404 box:23322 ESTABLISHED
tcp 0 152 (null):22 (null):58756 ESTABLISHED
tcp 0 0 (null):20220 (null):40060 ESTABLISHED
tcp 0 0 box:35268 box:2947 ESTABLISHED
tcp 0 0 box:23322 box:38402 ESTABLISHED
tcp 0 0 box:38402 box:23322 ESTABLISHED
tcp 0 0 box:2947 box:35268 ESTABLISHED
tcp 0 0 box:23322 box:38404 ESTABLISHED
udp 0 0 box:5353 (null):*
udp 0 0 (null):5353 (null):*
udp 0 0 (null):5353 (null):*
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 13101 /tmp/gpsd.sock
unix 2 [ ACC ] STREAM LISTENING 18092 /var/run/lirc/lircd
unix 2 [ ] DGRAM 18152 /var/run/wpa_supplicant/wlan0
unix 2 [ ACC ] SEQPACKET LISTENING 6644 /run/udev/control
unix 3 [ ] STREAM CONNECTED 21048
unix 3 [ ] STREAM CONNECTED 20894
unix 3 [ ] STREAM CONNECTED 21049 /var/run/lirc/lircd
unix 3 [ ] DGRAM 6652
unix 3 [ ] STREAM CONNECTED 20895
unix 3 [ ] DGRAM 6653
No port 3000...
pypilot automatically detects and connects to a signalk server on the network. So this uses zero conf, and no configuration is needed whether pypilot runs on openplotter, or pypilot is running on a separate computer like tinypilot connected to openplotter by network.
So to utilize signalk you only need to communicate with signalk-node-server which by default is running on openplotter. This is not really specific to pypilot anymore, but the default port is usually 3000 and it uses websockets or other transports, check the signalk documentation.
I moved this from the multi function display topic, since it seems like it is more appropriate here.
I start my computer before the tinypilot.
When the tinypilot starts there is no automatic connection from the SignalK server in the tinypilot
When I connect to port 3000 either TCP or websocket, I get connection refused
When I connect to port 20220 (NMEA0183) I get the tinypilot paths added to the SignalK data browser
Frankly I don't care about the autoconnect, but as I read above correctly the connection on port 3000 should not be refused.
Tinypilot configured to connect to an existing SSID and a fixed IP-address.
SignalK from the standard setup as mentioned on the github page on both ARM64 and X86_64
Tinypilot SK connected to the ARM64 and via the ARM64 to the X86_64.
OS Ubuntu 20.04 Focal / ARM64 (odroid N2), with github OpenCPN 5.2.x
OS Ubuntu 20.04 Focal / x86_64 (laptop i5) with stable OpenCPN 5.2.0
Also the missing keys on the pypilot plugin:
every start from OpenCPN I have to first select 127.0.0.1 and then the client IP address from the tinypilot. (This might be more appropriate in the pypilot_pi thread though).
Both on ARM64 and laptop.
I mention it here since it might be somehow related.
If I might roundup, I read there is supposed to be some automatic connection feature, which I I don't understand.
Therefore it is hard to trace the problems I face.
I will check tomorroe if the autoconnecting works as intended when the tinypilot provides the host AP.
One last thing:
tc@box:~$ netstat -a
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 (null):20220 (null):* LISTEN
tcp 0 0 (null):2947 (null):* LISTEN
tcp 0 0 (null):80 (null):* LISTEN
tcp 0 0 (null):33333 (null):* LISTEN
tcp 0 0 (null):22 (null):* LISTEN
tcp 0 0 (null):23322 (null):* LISTEN
tcp 0 0 (null):23322 (null):52482 ESTABLISHED
tcp 19 0 box:38404 box:23322 ESTABLISHED
tcp 0 152 (null):22 (null):58756 ESTABLISHED
tcp 0 0 (null):20220 (null):40060 ESTABLISHED
tcp 0 0 box:35268 box:2947 ESTABLISHED
tcp 0 0 box:23322 box:38402 ESTABLISHED
tcp 0 0 box:38402 box:23322 ESTABLISHED
tcp 0 0 box:2947 box:35268 ESTABLISHED
tcp 0 0 box:23322 box:38404 ESTABLISHED
udp 0 0 box:5353 (null):*
udp 0 0 (null):5353 (null):*
udp 0 0 (null):5353 (null):*
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 13101 /tmp/gpsd.sock
unix 2 [ ACC ] STREAM LISTENING 18092 /var/run/lirc/lircd
unix 2 [ ] DGRAM 18152 /var/run/wpa_supplicant/wlan0
unix 2 [ ACC ] SEQPACKET LISTENING 6644 /run/udev/control
unix 3 [ ] STREAM CONNECTED 21048
unix 3 [ ] STREAM CONNECTED 20894
unix 3 [ ] STREAM CONNECTED 21049 /var/run/lirc/lircd
unix 3 [ ] DGRAM 6652
unix 3 [ ] STREAM CONNECTED 20895
unix 3 [ ] DGRAM 6653
No port 3000...