pypilot on openplotter 3

[seandepagnier]

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.

---

You can use ssh -X as well.

• 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.

Perhaps.. but I really dont recommend this setup, and they can ignore the message for now

What's the usage of adding serial devices in the serial tab?

To inform pypilot that it can probe these ports. This prevents pypilot from taking over serial ports not intended to be used with it.

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.

Good idea.

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?

I saw this but dont think it matters... It is a confusing warning though.

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.

Is there an imu connected? I only get this without a working IMU. Its because it is trying very hard to probe the IMU which slows the loop down. I should fix it so it does not produce this error while probing the imu.

---

I reran the install with regard to the serial interface:

• On a clean 32-bit Openplotter 3.0 image on a raspberry 3b+, there is only a ttyAMA0 interface; serial1 points to it. 
  
• When serial port is enabled in raspi-config, and serial console disabled, ttyS0 is added and serial0 points to it.
  
• When openplotter-pypilot has done its 'enable hardware serial' thing, serial0 and serial1 are swapped, and hciuart is disabled.
  

That means it does not matter, and it is not necessary, to enable the serial port in raspi-config manually; you have to do it through openplotter-pypilot anyway. I believe this was different in the previous version of openplotter/raspbian, when the raspi-config actions were enough to make pypilot access the serial. Still, this is no problem for the rollout to openplotter, but it needs to be part of the release notes / install instructions, otherwise it might confuse those who are new to this arena.

You can enable the hardware serial by editing /boot/config.txt instead which is all openplotter-pypilot helper script does anyway... I dont think it was ever possible through raspi-config.

When openplotter does its thing, serial0 and serial1 are swapped, and hciuart is disabled.

correct