pypilot on openplotter 3

[ironman]

Unable to access the X Display, is $DISPLAY set properly?

This typically happens when you run an application that requires X from an ssh session. Run openplotter-pypilot from a terminal that was started from the graphic environment. Or, if you choose, first type export DISPLAY=":0", but then still, the window pops up in the graphical environment.

---

Please try this and post any issues so the scripts can be updated and improved.

• Openplotter-pypilot provides a message when started without hardware-serial enabled. There might be users who run the motor.ino arduino off a USB connection. For them, the message might be unsuited.
  
• What's the usage of adding serial devices in the serial tab?
  
• Reinstall finishes without a message that it's finished. The only clue is the fact that the Update button is enabled again. A message 'pypilot has been updated from source and is running again; no reboot is required.' coud be useful.
  
• Reinstall provides some error messages E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) and 
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
  
  

---

Running pypilot at the prompt, there appear to be no error messages for signalk; it simply works for gps and wind. I do still have 'autopilot iteration running too slow' on the raspberry 3b+ which is really annoying.

Code:

autopilot iteration running too slow 0.09295263399985743
autopilot iteration running too slow 0.09343117699995673
autopilot iteration running too slow 0.09403497900007096
autopilot iteration running too slow 0.09281315699990955
autopilot iteration running too slow 0.09415445699983138
autopilot iteration running too slow 0.09295628099994246
autopilot iteration running too slow 0.0938497180000013