OpenMarine

Full Version: Pypilot zeroconf signalk causes crashing
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I converted my whole setup to the latest and greatest {openplotter, tinypilot} images, and I'm really glad I went through it for all the enhancements and as it all seems to work together smootly.

However, the pypilot (tinypilot) seems to arrive in a circle of crash-restart after it has connected with signalk through zeroconf (see attached). I can work around this by deleting the device authorization in signalk again, but then it generates a lot of verbosity in the log files. Once it would work, can I then drop the tcp/20220 connection from opencpn for good?

Thx, -
(2020-12-29, 07:50 PM)ironman Wrote: [ -> ]I converted my whole setup to the latest and greatest {openplotter, tinypilot} images, and I'm really glad I went through it for all the enhancements and as it all seems to work together smootly.

However, the pypilot (tinypilot) seems to arrive in a circle of crash-restart after it has connected with signalk through zeroconf (see attached). I can work around this by deleting the device authorization in signalk again, but then it generates a lot of verbosity in the log files. Once it would work, can I then drop the tcp/20220 connection from opencpn for good?

Thx, -
Hi Ironman
I had the same problem .... reported it here

https://forum.openmarine.net/showthread.php?tid=3086

First it happend after updating from SignalK 1.35 to 1.36 ... 

Now i.am at signalk 1.37 ad I dont use signalk to connect to the tinypilot

So my work arround: TCP/2020 NMEA conection in signal k and leave the SignalK access request unaprooved ...

Otherways I always loose the server connection and the tinypilots stops working and disengages. compleetly.

So now if there woul be an TcP data loss there would still be the compass mode working .


Hope there is a solution.
Save sailing
Andreas
Thanks for the cross-reference; I guess I didn't search first  Confused .