Actually, having traced the code, this message comes from a module that takes care of pypilot's internal communication mechanism:
This would mean that somewhere you have configured pypilot incorrectly, inadvertently having configured the address of your nmea server (192.168.14.5:20220) into a place where pypilot thinks there's a pypilot server sitting. I would not know where that could be. Could you grep in the .pypilot directory for 192.168.14.5 and look what comes up?
Code:
pypilot socket failed to send to 192.168.14.5:20220 1
pi@openplotter:~/pypilot/pypilot $ grep 'pypilot socket failed to send' *
bufferedsocket.py: print(_('pypilot socket failed to send to'), self.address, self.sendfail_cnt)This would mean that somewhere you have configured pypilot incorrectly, inadvertently having configured the address of your nmea server (192.168.14.5:20220) into a place where pypilot thinks there's a pypilot server sitting. I would not know where that could be. Could you grep in the .pypilot directory for 192.168.14.5 and look what comes up?
Code:
grep 192.168.14.5 ~/.pypilot/*