pypilot on openplotter 3

[Sailoog]

I am not asking where did you download openplotter-settings from, I am asking what version is your Debian system.

I think you forced the installation of openplotter-settings v3 (for debian bullseye only) into a system running openplotter v2 (for debian buster only).

Downgrading after an update is really weird and that's the kind of paranormal effect of a broken debian. I can only advise you to start from scratch with the official image of openplotter v3: https://cloud.openmarine.net/s/mxrBi5K7zRj2gDq

[SVHM]

OK, I have reloaded OpenPlotter 3 with the Starter 32bit image. The load went fine but things are still not working. The Pypilot says its connected but the LCD screen is still blank and I can't get it to work. Given that it didn't give any info from the commands Sean had me enter (above), I am beginning to suspect that the SD card has been corrupted. What are the procedures in that case? I bought the TinyPilot preloaded. Do I need to pull the card and reformat, etc?

[SVHM]

Check if the serial port is setup correctly:
ls - l /dev/serial0

If this points to /dev/ttyAMA0 it should work.  In the newer openplotter I believe you can do this from the serial configuration.

Next, ensure the pypilot_hat service is running.  You must enable SPI in raspi-config for this to work, but normally the lcd should be autodetected.  You should be able to enable it from the interface from running openplotter-pypilot, or by
sudo service pypilot_hat start
sudo service pypilot_hat enable

Here are results from 1st

pi@openplotter:~ $ ls -l /dev/serial0
lrwxrwxrwx 1 root root 7 May 21 07:23 /dev/serial0 -> ttyAMA0
pi@openplotter:~ $ openplotter-pypilot
active
active
active
Settings file not found. Using defaults and creating settings file
Failed to open SPI bus 0, select 0
Using fusion algorithm RTQF
active

(openplotter-pypilot:1867): Gtk-CRITICAL **: 07:34:24.962: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar


Here are other commands

pi@openplotter:~ $ sudo service pypilot_hat start~
pypilot_hat: unrecognized service
pi@openplotter:~ $ sudo service pypilot_hat enable
pypilot_hat: unrecognized service
pi@openplotter:~ $

Her are the same commands after reinstalling OP3:

pi@openplotter:~ $ ls - l /dev/serial0
ls: cannot access '-': No such file or directory
ls: cannot access 'l': No such file or directory
/dev/serial0
pi@openplotter:~ $ sudo service pypilot_hat start
pi@openplotter:~ $ sudo service pypilot_hat enable~
pypilot_hat: unrecognized service
pi@openplotter:~ $

Here are the commands in the wiki:

pi@openplotter:~ $ pypilot boatimu
autopilot start 422.196537104
world magnetic model not available
ERROR loading wind.py cannot import name 'HeadingOffset' from partially initialized module 'pypilot.autopilot' (most likely due to a circular import) (/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py)  cannot import name 'HeadingOffset' from partially initialized module 'pypilot.autopilot' (most likely due to a circular import) (/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py)
imu process 2275
nmea process 2279
nmea server on port 20220: bind failed.
gps process 2281
loading servo calibration /home/pi/.pypilot/servocalibration
WARNING: using default servo calibration!!
Available Pilots: ['basic', 'absolute']
warning: failed to open special file /dev/watchdog0 for writing
        cannot stroke the watchdog
pypilotServer process 2284
pypilot_server: bind failed; already running a server?
made imu process realtime
Using settings file RTIMULib.ini
Settings file RTIMULib.ini loaded
Failed to open SPI bus 0, select 0
Using fusion algorithm Kalman STATE4
ERROR: No IMU Detected 422.487744334
autopilot init complete 422.533326817
serialprobe removing gps device /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0
autopilot iteration running too slow 0.07958608799998501
autopilot iteration running too slow 0.10437151899998298
autopilot iteration running too slow 0.0844185899999843
gps filter process 2282
autopilot iteration running too slow 0.09999870900003316
autopilot iteration running too slow 0.08603793099996437
autopilot iteration running too slow 0.09813967899998488
autopilot iteration running too slow 0.08866608499999984
nmea server on port 20220: bind failed.
autopilot iteration running too slow 0.09545324300000857
autopilot iteration running too slow 0.09107756999998173
autopilot iteration running too slow 0.09487047599998277
autopilot iteration running too slow 0.0907275659999982
autopilot iteration running too slow 0.09468375500000548
autopilot iteration running too slow 0.09223930100000644
autopilot iteration running too slow 0.0938905689999956
autopilot iteration running too slow 0.09200434999996787
autopilot iteration running too slow 0.09389963199998874
nmea server on port 20220: bind failed.
gpsd connected
GPSD devices ['/dev/ttyUSB1']
autopilot iteration running too slow 0.09359546199999613
autopilot iteration running too slow 0.09269482700000253
autopilot iteration running too slow 0.09330920900004003
autopilot iteration running too slow 0.09352931500001205
autopilot iteration running too slow 0.09331019899997273
autopilot iteration running too slow 0.09289212099997712
autopilot iteration running too slow 0.09358254500000385
^CTraceback (most recent call last):
  File "/usr/local/bin/pypilot", line 33, in <module>
    sys.exit(load_entry_point('pypilot==0.36', 'console_scripts', 'pypilot')())
  File "/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py", line 453, in main
    ap.iteration()
  File "/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py", line 321, in iteration
  File "/usr/local/lib/python3.9/dist-packages/pypilot/client.py", line 385, in receive
    self.poll(timeout)
  File "/usr/local/lib/python3.9/dist-packages/pypilot/client.py", line 277, in poll
    events = self.poller.poll(int(1000 * timeout))
  File "/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py", line 186, in cleanup
    raise KeyboardInterrupt # to get backtrace on all processes
KeyboardInterrupt
closing autopilot

pi@openplotter:~ $


pi@openplotter:~ $ pypilot servo
autopilot start 554.773446253
world magnetic model not available
ERROR loading wind.py cannot import name 'HeadingOffset' from partially initialized module 'pypilot.autopilot' (most likely due to a circular import) (/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py)  cannot import name 'HeadingOffset' from partially initialized module 'pypilot.autopilot' (most likely due to a circular import) (/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py)
imu process 2345
nmea process 2349
nmea server on port 20220: bind failed.
loading servo calibration /home/pi/.pypilot/servocalibration
WARNING: using default servo calibration!!
gps process 2351
Available Pilots: ['basic', 'absolute']
warning: failed to open special file /dev/watchdog0 for writing
        cannot stroke the watchdog
pypilotServer process 2354
pypilot_server: bind failed; already running a server?
made imu process realtime
Using settings file RTIMULib.ini
Settings file RTIMULib.ini loaded
Failed to open SPI bus 0, select 0
Using fusion algorithm Kalman STATE4
ERROR: No IMU Detected 555.08776801
autopilot init complete 555.106278855
serialprobe removing gps device /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0
autopilot iteration running too slow 0.0805108529999643
autopilot iteration running too slow 0.10352211599990824
autopilot iteration running too slow 0.08586914599993634
gps filter process 2352
autopilot iteration running too slow 0.09915112600003795
autopilot iteration running too slow 0.08726879799996823
autopilot iteration running too slow 0.0971526130000484
autopilot iteration running too slow 0.08985387999996419
nmea server on port 20220: bind failed.
autopilot iteration running too slow 0.09556806399996276
autopilot iteration running too slow 0.09084602699999778
autopilot iteration running too slow 0.09484836700005417
autopilot iteration running too slow 0.09227682599998843
autopilot iteration running too slow 0.09381116700001257
autopilot iteration running too slow 0.09254724600009467
autopilot iteration running too slow 0.09330954699998983
autopilot iteration running too slow 0.09274344699997528
autopilot iteration running too slow 0.09276313400005165
nmea server on port 20220: bind failed.
gpsd connected
GPSD devices ['/dev/ttyUSB1']
autopilot iteration running too slow 0.09451945699993303
autopilot iteration running too slow 0.09230010800001764
autopilot iteration running too slow 0.09376007299999856
autopilot iteration running too slow 0.09206406399994194
autopilot iteration running too slow 0.09352137200005473
autopilot iteration running too slow 0.09286152100003164
autopilot iteration running too slow 0.0933044420000897
autopilot iteration running too slow 0.0931725660000211
nmea server on port 20220: bind failed.
pypilot_server: bind failed; already running a server?
autopilot iteration running too slow 0.09370163500000217
autopilot iteration running too slow 0.09201119800002289
autopilot iteration running too slow 0.09371330099997977
autopilot iteration running too slow 0.09335579699995833
autopilot iteration running too slow 0.09206406400005562
autopilot iteration running too slow 0.09304621000001134
^CTraceback (most recent call last):
  File "/usr/local/bin/pypilot", line 33, in <module>
    sys.exit(load_entry_point('pypilot==0.36', 'console_scripts', 'pypilot')())
  File "/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py", line 453, in main
  File "/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py", line 349, in iteration
    time.sleep(pd10)
  File "/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py", line 186, in cleanup
    raise KeyboardInterrupt # to get backtrace on all processes
KeyboardInterrupt
closing autopilot

pi@openplotter:~ $ pypilot
autopilot start 716.320660638
world magnetic model not available
ERROR loading wind.py cannot import name 'HeadingOffset' from partially initialized module 'pypilot.autopilot' (most likely due to a circular import) (/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py)  cannot import name 'HeadingOffset' from partially initialized module 'pypilot.autopilot' (most likely due to a circular import) (/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py)
imu process 2386
nmea process 2390
nmea server on port 20220: bind failed.
gps process 2392
loading servo calibration /home/pi/.pypilot/servocalibration
WARNING: using default servo calibration!!
Available Pilots: ['basic', 'absolute']
warning: failed to open special file /dev/watchdog0 for writing
        cannot stroke the watchdog
pypilotServer process 2395
pypilot_server: bind failed; already running a server?
made imu process realtime
Using settings file RTIMULib.ini
Settings file RTIMULib.ini loaded
Failed to open SPI bus 0, select 0
Using fusion algorithm Kalman STATE4
ERROR: No IMU Detected 716.642852074
autopilot init complete 716.660674944
serialprobe removing gps device /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0
autopilot iteration running too slow 0.08006781399990359
autopilot iteration running too slow 0.1032024309999997
autopilot iteration running too slow 0.08573585799990724
gps filter process 2393
autopilot iteration running too slow 0.09914056199988863
autopilot iteration running too slow 0.08736849000001712
autopilot iteration running too slow 0.09705017500004942
autopilot iteration running too slow 0.089471949999961
nmea server on port 20220: bind failed.
autopilot iteration running too slow 0.09527785600005245
autopilot iteration running too slow 0.09085661800008893
autopilot iteration running too slow 0.09497260099999494
autopilot iteration running too slow 0.09125963199994658
autopilot iteration running too slow 0.09369220200005657
autopilot iteration running too slow 0.0922198279999975
autopilot iteration running too slow 0.09387001200002487
autopilot iteration running too slow 0.0923515969999471
autopilot iteration running too slow 0.09364256699996076
nmea server on port 20220: bind failed.
gpsd connected
GPSD devices ['/dev/ttyUSB1']
autopilot iteration running too slow 0.09316038700001172
autopilot iteration running too slow 0.09290841199992883
autopilot iteration running too slow 0.09323194799992507
autopilot iteration running too slow 0.09320434500000374
autopilot iteration running too slow 0.09331278100000873
autopilot iteration running too slow 0.09299257700001817
autopilot iteration running too slow 0.09309752299998308
autopilot iteration running too slow 0.09314189700000952
nmea server on port 20220: bind failed.
autopilot iteration running too slow 0.0940421969999079
pypilot_server: bind failed; already running a server?
autopilot iteration running too slow 0.09169269900007748
autopilot iteration running too slow 0.09370376399999714
autopilot iteration running too slow 0.09200321599996641
autopilot iteration running too slow 0.09383647099991776
autopilot iteration running too slow 0.09199451899996802
autopilot iteration running too slow 0.0937508470000239
autopilot iteration running too slow 0.09185957300007885
nmea server on port 20220: bind failed.
autopilot iteration running too slow 0.09370397300006061
autopilot iteration running too slow 0.09211477700000614
autopilot iteration running too slow 0.0951521289999846
autopilot iteration running too slow 0.09123208100004376
autopilot iteration running too slow 0.0945514599999342
autopilot iteration running too slow 0.09246164699993642
autopilot iteration running too slow 0.09335126999997101
autopilot iteration running too slow 0.0929101819999687
autopilot iteration running too slow 0.09312471000009737
nmea server on port 20220: bind failed.
autopilot iteration running too slow 0.09407881200002066
servo probe ('/dev/AMA0', 38400) 721.782395683
failed to open servo on: ('/dev/AMA0', 38400) [Errno 2] could not open port /dev/AMA0: [Errno 2] No such file or directory: '/dev/AMA0'
server/client is running too _slowly_ 0.0771410319999859
autopilot iteration running too slow 0.14972650499998963
calibration loaded, starting 2384
autopilot iteration running too slow 0.09227946199996495
autopilot iteration running too slow 0.0933261659999971
autopilot iteration running too slow 0.0922527950000358
autopilot iteration running too slow 0.09355074600000535
autopilot iteration running too slow 0.09340220700005375
autopilot iteration running too slow 0.09396047999996426
signalk process 2391
nmea server on port 20220: bind failed.
pypilot_server: bind failed; already running a server?
autopilot iteration running too slow 0.09324179199995797
signalkread token eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkZXZpY2UiOiI3YjkyZTBlZC0xYmE5LTQ2MGQtOTg1ZS02YTRjOTk5MmM4MTkiLCJpYXQiOjE2ODQ4NjUyOTgsImV4cCI6MTcxNjQyMjg5OH0.58Ym64d085El7Yu_PbXW_yA5673l75fejlHeFeReRGA
autopilot iteration running too slow 0.0941139149999799
signalk server found 192.168.78.106:3000
signalk server found 127.0.0.1:3000
autopilot iteration running too slow 0.09141124600000694
autopilot iteration running too slow 0.09320372000001953
autopilot iteration running too slow 0.09218545300007008
autopilot iteration running too slow 0.09329429100000652
autopilot iteration running too slow 0.09248742800002674
autopilot iteration running too slow 0.09354027799997766
nmea server on port 20220: bind failed.
autopilot iteration running too slow 0.0941016760000366
autopilot iteration running too slow 0.09209566300000915
autopilot iteration running too slow 0.09494958000004772
autopilot iteration running too slow 0.0924971160000041
^CTraceback (most recent call last):
  File "/usr/local/bin/pypilot", line 33, in <module>
    sys.exit(load_entry_point('pypilot==0.36', 'console_scripts', 'pypilot')())
  File "/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py", line 453, in main
    ap.iteration()
  File "/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py", line 321, in iteration
  File "/usr/local/lib/python3.9/dist-packages/pypilot/client.py", line 385, in receive
    self.poll(timeout)
  File "/usr/local/lib/python3.9/dist-packages/pypilot/client.py", line 277, in poll
    events = self.poller.poll(int(1000 * timeout))
  File "/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py", line 186, in cleanup
    raise KeyboardInterrupt # to get backtrace on all processes
KeyboardInterrupt
closing autopilot



pi@openplotter:~ $ pypilot calibration 127.0.0.1
autopilot start 1051.309453682
world magnetic model not available
ERROR loading wind.py cannot import name 'HeadingOffset' from partially initialized module 'pypilot.autopilot' (most likely due to a circular import) (/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py)  cannot import name 'HeadingOffset' from partially initialized module 'pypilot.autopilot' (most likely due to a circular import) (/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py)
imu process 2474
nmea process 2478
gps process 2480
nmea server on port 20220: bind failed.
loading servo calibration /home/pi/.pypilot/servocalibration
WARNING: using default servo calibration!!
Available Pilots: ['basic', 'absolute']
warning: failed to open special file /dev/watchdog0 for writing
        cannot stroke the watchdog
pypilotServer process 2483
made imu process realtime
Using settings file RTIMULib.ini
Settings file RTIMULib.ini loaded
Failed to open SPI bus 0, select 0
Using fusion algorithm Kalman STATE4
ERROR: No IMU Detected 1051.621062568
pypilot_server: bind failed; already running a server?
autopilot init complete 1051.664486838
serialprobe removing gps device /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0
autopilot iteration running too slow 0.07766433000006145
autopilot iteration running too slow 0.10497305399985635
autopilot iteration running too slow 0.08324268999990636
gps filter process 2482
autopilot iteration running too slow 0.10117616100001214
autopilot iteration running too slow 0.08516400099983912
autopilot iteration running too slow 0.09806187499998487
autopilot iteration running too slow 0.08851360000016939
nmea server on port 20220: bind failed.
autopilot iteration running too slow 0.09656598299989128
autopilot iteration running too slow 0.08961496000006264
autopilot iteration running too slow 0.0957184789999701
autopilot iteration running too slow 0.09123048899982678
autopilot iteration running too slow 0.0938310740000361
autopilot iteration running too slow 0.09193038699982026
autopilot iteration running too slow 0.09410018900007344
autopilot iteration running too slow 0.0919015329998274
autopilot iteration running too slow 0.09406201199999487
nmea server on port 20220: bind failed.
gpsd connected
GPSD devices ['/dev/ttyUSB1']
autopilot iteration running too slow 0.09355414499987091
autopilot iteration running too slow 0.09286961100019653
autopilot iteration running too slow 0.0931723730000158
autopilot iteration running too slow 0.09301164199996492
autopilot iteration running too slow 0.0929175280000436
autopilot iteration running too slow 0.09331596700008049
autopilot iteration running too slow 0.09323742500009757
autopilot iteration running too slow 0.09309502900009647
nmea server on port 20220: bind failed.
pypilot_server: bind failed; already running a server?
autopilot iteration running too slow 0.09352826000008463
autopilot iteration running too slow 0.09290612100016915
autopilot iteration running too slow 0.09308955899996363
autopilot iteration running too slow 0.09326148799982548
autopilot iteration running too slow 0.09319445599999199
autopilot iteration running too slow 0.09300721499994324
autopilot iteration running too slow 0.09310237199997573
autopilot iteration running too slow 0.09301909100008743
nmea server on port 20220: bind failed.
autopilot iteration running too slow 0.09340898799996467
autopilot iteration running too slow 0.0931879449999542
autopilot iteration running too slow 0.09362461400019129
autopilot iteration running too slow 0.09307237200005147
autopilot iteration running too slow 0.09325393499989332
autopilot iteration running too slow 0.09323304999998072
autopilot iteration running too slow 0.09359008199999153
autopilot iteration running too slow 0.09377263600003971
autopilot iteration running too slow 0.09286909000002197
nmea server on port 20220: bind failed.
autopilot iteration running too slow 0.09397737600011169
servo probe ('/dev/AMA0', 38400) 1056.782658963
failed to open servo on: ('/dev/AMA0', 38400) [Errno 2] could not open port /dev/AMA0: [Errno 2] No such file or directory: '/dev/AMA0'
server/client is running too _slowly_ 0.07448879300000044
calibration loaded, starting 2472
autopilot iteration running too slow 0.14654861700000765
autopilot iteration running too slow 0.09174762600014219
autopilot iteration running too slow 0.0933306019999236
autopilot iteration running too slow 0.09228846199994223
^CTraceback (most recent call last):
  File "/usr/local/bin/pypilot", line 33, in <module>
    sys.exit(load_entry_point('pypilot==0.36', 'console_scripts', 'pypilot')())
  File "/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py", line 453, in main
    ap.iteration()
  File "/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py", line 445, in iteration
  File "/usr/local/lib/python3.9/dist-packages/pypilot/autopilot.py", line 186, in cleanup
    raise KeyboardInterrupt # to get backtrace on all processes
KeyboardInterrupt
closing autopilot

[seandepagnier]

A few things.

There is something wrong with the install as pypilot_hat should be a recognized service.

You are running "pypilot boatimu" instead of pypilot_boatimu This just runs pypilot.

When it says "bind failed" it meas generally that another instance of pypilot is already running.

Can you try running pypilot_hat ?

[SVHM]

A few things.

There is something wrong with the install as pypilot_hat should be a recognized service.

You are running "pypilot boatimu" instead of pypilot_boatimu    This just runs pypilot.

When it says "bind failed" it meas generally that another instance of pypilot is already running.

Can you try running pypilot_hat  ?

Here is the output:

pi@openplotter:~ $ pypilot_hat
hat start 135.821031005
have gpio for raspberry pi
hat import done 135.899380705
loading config file: /home/pi/.pypilot/hat.conf
failed to load /proc/device-tree/hat/custom_0 : [Errno 2] No such file or directory: '/proc/device-tree/hat/custom_0'
host localhost
lcd process on 2074
lcd driver default False True
using glut
hat init complete 136.94498746
2075 (process ID) old priority 0, new priority 19
set language en
create font charater N 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016078
create font charater / 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016047
create font charater A 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016065
create font charater N 70 0 4
store grey /home/pi/.pypilot/ugfxfonts/070078
create font charater / 70 0 4
store grey /home/pi/.pypilot/ugfxfonts/070047
create font charater A 70 0 4
store grey /home/pi/.pypilot/ugfxfonts/070065
create font charater s 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016115
create font charater t 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016116
create font charater a 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016097
create font charater n 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016110
create font charater d 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016100
create font charater b 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016098
create font charater y 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016121
create font charater s 34 0 4
store grey /home/pi/.pypilot/ugfxfonts/034115
create font charater t 34 0 4
store grey /home/pi/.pypilot/ugfxfonts/034116
create font charater a 34 0 4
store grey /home/pi/.pypilot/ugfxfonts/034097
create font charater n 34 0 4
store grey /home/pi/.pypilot/ugfxfonts/034110
create font charater d 34 0 4
store grey /home/pi/.pypilot/ugfxfonts/034100
create font charater b 34 0 4
store grey /home/pi/.pypilot/ugfxfonts/034098
create font charater y 34 0 4
store grey /home/pi/.pypilot/ugfxfonts/034121
create font charater C 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016067
create font charater C 40 0 4
store grey /home/pi/.pypilot/ugfxfonts/040067
create font charater N 23 0 4
store grey /home/pi/.pypilot/ugfxfonts/023078
create font charater / 23 0 4
store grey /home/pi/.pypilot/ugfxfonts/023047
create font charater A 23 0 4
store grey /home/pi/.pypilot/ugfxfonts/023065
create font charater W 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016087
create font charater W 23 0 4
store grey /home/pi/.pypilot/ugfxfonts/023087
create font charater  16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016032
create font charater E 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016069
create font charater R 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016082
create font charater O 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016079
create font charater c 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016099
create font charater o 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016111
create font charater m 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016109
create font charater p 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016112
create font charater r 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016114
create font charater g 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016103
create font charater f 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016102
create font charater i 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016105
create font charater l 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016108
create font charater u 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016117
create font charater e 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016101
create font charater ! 16 0 4
store grey /home/pi/.pypilot/ugfxfonts/016033
create font charater E 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032069
create font charater R 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032082
create font charater O 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032079
create font charater c 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032099
create font charater o 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032111
create font charater m 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032109
create font charater p 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032112
create font charater a 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032097
create font charater s 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032115
create font charater r 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032114
create font charater  32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032032
create font charater g 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032103
create font charater y 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032121
create font charater f 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032102
create font charater i 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032105
create font charater l 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032108
create font charater u 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032117
create font charater e 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032101
create font charater ! 32 0 4
store grey /home/pi/.pypilot/ugfxfonts/032033
create font charater b 23 0 4
store grey /home/pi/.pypilot/ugfxfonts/023098
create font charater a 23 0 4
store grey /home/pi/.pypilot/ugfxfonts/023097
create font charater s 23 0 4
store grey /home/pi/.pypilot/ugfxfonts/023115
create font charater i 23 0 4
store grey /home/pi/.pypilot/ugfxfonts/023105
create font charater c 23 0 4
store grey /home/pi/.pypilot/ugfxfonts/023099
web process 2075
web failed to run process: [Errno 98] Address already in use: ('0.0.0.0', 33333)
2075 (process ID) old priority 19, new priority 19
web process 2075
web failed to run process: View function mapping is overwriting an existing endpoint function: index
2075 (process ID) old priority 19, new priority 19
web process 2075
web failed to run process: View function mapping is overwriting an existing endpoint function: index
2075 (process ID) old priority 19, new priority 19
web process 2075
web failed to run process: View function mapping is overwriting an existing endpoint function: index
2075 (process ID) old priority 19, new priority 19
web process 2075
web failed to run process: View function mapping is overwriting an existing endpoint function: index
2075 (process ID) old priority 19, new priority 19
web process 2075
web failed to run process: View function mapping is overwriting an existing endpoint function: index
2075 (process ID) old priority 19, new priority 19
web process 2075
web failed to run process: View function mapping is overwriting an existing endpoint function: index
2075 (process ID) old priority 19, new priority 19
^Cgot signal 2 cleaning up 2072
Traceback (most recent call last):
  File "/usr/local/bin/pypilot_hat", line 33, in <module>
    sys.exit(load_entry_point('pypilot==0.36', 'console_scripts', 'pypilot_hat')())
  File "/usr/local/lib/python3.9/dist-packages/pypilot/hat/hat.py", line 552, in main
got signal 17 cleaning up 2072
subprocess returned (2074, 15) []
    hat.poll()
  File "/usr/local/lib/python3.9/dist-packages/pypilot/hat/hat.py", line 544, in poll
    e=self.poller.poll(1000*period)
  File "/usr/local/lib/python3.9/dist-packages/pypilot/hat/hat.py", line 379, in cleanup
    raise KeyboardInterrupt # to get backtrace on all processes
KeyboardInterrupt

You are probably right.  II have the TinyPilot computer with zero w.  OP3 was installed on a RPi 3+.  I had pipilot working partially until I installed OP3.  I also installed Pypilot in op3.  One thing I did do is install the power for all three computers on one bus bar with a single switch so they all boot at the same time.  Probably not a good idea.  I will separate them.

[SVHM]

This is the type of post I hoped I would never have to write but frustration forces me to write.

I did some troubleshooting and discovered that the RPI Zero W that was in my TinyPilot computer was no good.  I can't get anything to work on it, even with a different SD card.  After spending considerable time setting up OpenPlotter 3, and after Sean's response above, I figured I would try to uninstall OpenPlotter's version of Pypilot and only communicate with TinyPilot directly in case I had two versions of Pypilot running at the same time.    As soon as I completed the uninstall, OP3 died.  It would boot to the Rasberry Pi logo then go blank.  At that point, I had had it with OpenPlotter.  While it seems that it is a good program for those who are power users and programmers, it just requires too much admin work and never seems to work right.  Nothing is plug and play, everything needs to be set up individually, which, seems to cause conflicts and the need to fix them.  There are so many pages that need to be filled and permissions that need to be set that I have found it to be completely unusable.  I have tried using OpenPlotter several times but always with the same result.  Yesterday I loaded Rasbian and OpenCPN.  I Setup GPSD, added maps, installed Pypilot plugin, and Pypilot fired up first time.  I was able to get my motor to move in both directions and I am now a very happy camper.

In the end, all I wanted was to use Pypilot to work with OpenCPN.  I am not likely going to have an IoT boat and sit and tinker all day with stuff like that.  A boat is already a full time job.  I think for people looking to quickly get a working navigation system and autopilot system built and go sailing, OpenPlotter is probably not going to satisfy you.  The documentation seems to be where it was two or three years ago but the architecture keeps changing.  Again, unless you are a fanatic about building computers and know Linux and programming inside and out, you will probably find it very challenging.  

I think that for OpenPlotter to be a success, it needs to get some basic parameters working easily for the average person without advanced computer skills.  OpenCPN has been around for a long time and Pypilot for a while too.  On their own, they work and have worked.  They need to work out of the box with OP before anything else if OP is to be a useful operting system.  The documentation needs to be at least to a point where people can get a basic system  working.  Adding additional functionality, such as engine sensors, AIS, cameras, propane sniffers, and especially interoperability with commercial products should all wait till the basics are working for everyone.  OP seems to be important on a certain level and I suppose it should go forward.  I am only trying to critique the implementation.  I would, however suggest that people think about what OpenPlotter and Pypylot should be in the future. 

Where is this all going?  Is the goal complete interoperability with commercial products even though the corporations that make the products have absolutely no desire for the same?  Or is the idea to build capabilities for people without the means or desire to purchase expensive products to have similar or superior capabilities of commercial alternatives?  I would argue that the latter is more important.  Building an operating system around Signal K seems to be a losing proposition over the long term.  Eventually someone will get sued by some company for copyright or patent infringement in order to crush out the competition and that will be it.  Or, striving for interoperability with commercial products may make people just give up entirely on open source because the corporations are implementing what open source develops for free.  I think it would be better to focus on building open source products that go their own direction independently and leave the companies in the dust.  That would create head to head competition rather than wannabe products.

[mgrouch]

This is the type of post I hoped I would never have to write but frustration forces me to write.

I did some troubleshooting and discovered that the RPI Zero W that was in my TinyPilot computer was no good.  I can't get anything to work on it, even with a different SD card.  After spending considerable time setting up OpenPlotter 3, and after Sean's response above, I figured I would try to uninstall OpenPlotter's version of Pypilot and only communicate with TinyPilot directly in case I had two versions of Pypilot running at the same time.    As soon as I completed the uninstall, OP3 died.  It would boot to the Rasberry Pi logo then go blank.  At that point, I had had it with OpenPlotter.  While it seems that it is a good program for those who are power users and programmers, it just requires too much admin work and never seems to work right.  Nothing is plug and play, everything needs to be set up individually, which, seems to cause conflicts and the need to fix them.  There are so many pages that need to be filled and permissions that need to be set that I have found it to be completely unusable.  I have tried using OpenPlotter several times but always with the same result.  Yesterday I loaded Rasbian and OpenCPN.  I Setup GPSD, added maps, installed Pypilot plugin, and Pypilot fired up first time.  I was able to get my motor to move in both directions and I am now a very happy camper.

In the end, all I wanted was to use Pypilot to work with OpenCPN.  I am not likely going to have an IoT boat and sit and tinker all day with stuff like that.  A boat is already a full time job.  I think for people looking to quickly get a working navigation system and autopilot system built and go sailing, OpenPlotter is probably not going to satisfy you.  The documentation seems to be where it was two or three years ago but the architecture keeps changing.  Again, unless you are a fanatic about building computers and know Linux and programming inside and out, you will probably find it very challenging.  

I think that for OpenPlotter to be a success, it needs to get some basic parameters working easily for the average person without advanced computer skills.  OpenCPN has been around for a long time and Pypilot for a while too.  On their own, they work and have worked.  They need to work out of the box with OP before anything else if OP is to be a useful operting system.  The documentation needs to be at least to a point where people can get a basic system  working.  Adding additional functionality, such as engine sensors, AIS, cameras, propane sniffers, and especially interoperability with commercial products should all wait till the basics are working for everyone.  OP seems to be important on a certain level and I suppose it should go forward.  I am only trying to critique the implementation.  I would, however suggest that people think about what OpenPlotter and Pypylot should be in the future. 

Where is this all going?  Is the goal complete interoperability with commercial products even though the corporations that make the products have absolutely no desire for the same?  Or is the idea to build capabilities for people without the means or desire to purchase expensive products to have similar or superior capabilities of commercial alternatives?  I would argue that the latter is more important.  Building an operating system around Signal K seems to be a losing proposition over the long term.  Eventually someone will get sued by some company for copyright or patent infringement in order to crush out the competition and that will be it.  Or, striving for interoperability with commercial products may make people just give up entirely on open source because the corporations are implementing what open source develops for free.  I think it would be better to focus on building open source products that go their own direction independently and leave the companies in the dust.  That would create head to head competition rather than wannabe products.

Before quitting open source DIY world,
have tried Bareboat Necessities OS?
It’s more plug and play than openplotter. 
It’s also open-source and free. In BBN OS you have less dialogs you need to fill out,
and almost nothing to download from internet after you installed 
from one image.

[seandepagnier]

Is the goal complete interoperability with commercial products even though the corporations that make the products have absolutely no desire for the same?  Or is the idea to build capabilities for people without the means or desire to purchase expensive products to have similar or superior capabilities of commercial alternatives?  I would argue that the latter is more important. 

I would too but it is obvious that there are a lot of people who believe in the first goal. I think it is because they already have such systems.

... I think it would be better to focus on building open source products that go their own direction independently and leave the companies in the dust.  That would create head to head competition rather than wannabe products.

I agree completely and it is my goal but my ability to achieve this is limited by the hours in the day. I have designed and build wind sensors, water speed sensors for myself as well as a lot of other things but I simply cannot produce them and sell in quantity. As it is I had to give up on selling autopilot parts for a bit to try to deal with my own problems.

[Sailoog]

This is the type of post I hoped I would never have to write but frustration forces me to write.

I did some troubleshooting and discovered that the RPI Zero W that was in my TinyPilot computer was no good.  I can't get anything to work on it, even with a different SD card.  After spending considerable time setting up OpenPlotter 3, and after Sean's response above, I figured I would try to uninstall OpenPlotter's version of Pypilot and only communicate with TinyPilot directly in case I had two versions of Pypilot running at the same time.    As soon as I completed the uninstall, OP3 died.  It would boot to the Rasberry Pi logo then go blank.  At that point, I had had it with OpenPlotter.  While it seems that it is a good program for those who are power users and programmers, it just requires too much admin work and never seems to work right.  Nothing is plug and play, everything needs to be set up individually, which, seems to cause conflicts and the need to fix them.  There are so many pages that need to be filled and permissions that need to be set that I have found it to be completely unusable.  I have tried using OpenPlotter several times but always with the same result.  Yesterday I loaded Rasbian and OpenCPN.  I Setup GPSD, added maps, installed Pypilot plugin, and Pypilot fired up first time.  I was able to get my motor to move in both directions and I am now a very happy camper.

In the end, all I wanted was to use Pypilot to work with OpenCPN.  I am not likely going to have an IoT boat and sit and tinker all day with stuff like that.  A boat is already a full time job.  I think for people looking to quickly get a working navigation system and autopilot system built and go sailing, OpenPlotter is probably not going to satisfy you.  The documentation seems to be where it was two or three years ago but the architecture keeps changing.  Again, unless you are a fanatic about building computers and know Linux and programming inside and out, you will probably find it very challenging.  

I think that for OpenPlotter to be a success, it needs to get some basic parameters working easily for the average person without advanced computer skills.  OpenCPN has been around for a long time and Pypilot for a while too.  On their own, they work and have worked.  They need to work out of the box with OP before anything else if OP is to be a useful operting system.  The documentation needs to be at least to a point where people can get a basic system  working.  Adding additional functionality, such as engine sensors, AIS, cameras, propane sniffers, and especially interoperability with commercial products should all wait till the basics are working for everyone.  OP seems to be important on a certain level and I suppose it should go forward.  I am only trying to critique the implementation.  I would, however suggest that people think about what OpenPlotter and Pypylot should be in the future. 

Where is this all going?  Is the goal complete interoperability with commercial products even though the corporations that make the products have absolutely no desire for the same?  Or is the idea to build capabilities for people without the means or desire to purchase expensive products to have similar or superior capabilities of commercial alternatives?  I would argue that the latter is more important.  Building an operating system around Signal K seems to be a losing proposition over the long term.  Eventually someone will get sued by some company for copyright or patent infringement in order to crush out the competition and that will be it.  Or, striving for interoperability with commercial products may make people just give up entirely on open source because the corporations are implementing what open source develops for free.  I think it would be better to focus on building open source products that go their own direction independently and leave the companies in the dust.  That would create head to head competition rather than wannabe products.

Thank you for your comments. Most of the messages we receive are congratulations but messages like yours are always more useful to improve.

These are my conclusions from your frustration and some proposals.

You haven't answered my questions yet but my conclusion is that your problems started when you tried to install openplotter 3 over an old openplotter 2 installation. This cannot be done without breaking the system and can only be done by following the "advanced" method. As a solution we will add a huge warning on the download page of the advanced method.

Pypilot in openplotter 3 does not need any command to be executed in the terminal and any task can be carried out from the graphical interface. In this thread it is recommended to carry out some manual tasks that come from the time when pypilot was not yet fully integrated into openplotter 3 and you had to force the installation. As a solution we should mark this confusing thread as obsolete. More background: https://forum.openmarine.net/showthread.php?tid=4221

You are right, DIY projects are not for everyone but there is little we can do there. The objective of openplotter is to bring development closer to non-advanced users and we believe that a lot is achieved but each one has its own limit.

You have been recommended to try other systems that claim to be more plug and play, I can only say that you try it and then tell us about your experience. Remember to read the Getting Started section and its 64 chapters before installing, paying special attention to the pypilot chapter

[SVHM]

This is the type of post I hoped I would never have to write but frustration forces me to write.

I did some troubleshooting and discovered that the RPI Zero W that was in my TinyPilot computer was no good.  I can't get anything to work on it, even with a different SD card.  After spending considerable time setting up OpenPlotter 3, and after Sean's response above, I figured I would try to uninstall OpenPlotter's version of Pypilot and only communicate with TinyPilot directly in case I had two versions of Pypilot running at the same time.    As soon as I completed the uninstall, OP3 died.  It would boot to the Rasberry Pi logo then go blank.  At that point, I had had it with OpenPlotter.  While it seems that it is a good program for those who are power users and programmers, it just requires too much admin work and never seems to work right.  Nothing is plug and play, everything needs to be set up individually, which, seems to cause conflicts and the need to fix them.  There are so many pages that need to be filled and permissions that need to be set that I have found it to be completely unusable.  I have tried using OpenPlotter several times but always with the same result.  Yesterday I loaded Rasbian and OpenCPN.  I Setup GPSD, added maps, installed Pypilot plugin, and Pypilot fired up first time.  I was able to get my motor to move in both directions and I am now a very happy camper.

In the end, all I wanted was to use Pypilot to work with OpenCPN.  I am not likely going to have an IoT boat and sit and tinker all day with stuff like that.  A boat is already a full time job.  I think for people looking to quickly get a working navigation system and autopilot system built and go sailing, OpenPlotter is probably not going to satisfy you.  The documentation seems to be where it was two or three years ago but the architecture keeps changing.  Again, unless you are a fanatic about building computers and know Linux and programming inside and out, you will probably find it very challenging.  

I think that for OpenPlotter to be a success, it needs to get some basic parameters working easily for the average person without advanced computer skills.  OpenCPN has been around for a long time and Pypilot for a while too.  On their own, they work and have worked.  They need to work out of the box with OP before anything else if OP is to be a useful operting system.  The documentation needs to be at least to a point where people can get a basic system  working.  Adding additional functionality, such as engine sensors, AIS, cameras, propane sniffers, and especially interoperability with commercial products should all wait till the basics are working for everyone.  OP seems to be important on a certain level and I suppose it should go forward.  I am only trying to critique the implementation.  I would, however suggest that people think about what OpenPlotter and Pypylot should be in the future. 

Where is this all going?  Is the goal complete interoperability with commercial products even though the corporations that make the products have absolutely no desire for the same?  Or is the idea to build capabilities for people without the means or desire to purchase expensive products to have similar or superior capabilities of commercial alternatives?  I would argue that the latter is more important.  Building an operating system around Signal K seems to be a losing proposition over the long term.  Eventually someone will get sued by some company for copyright or patent infringement in order to crush out the competition and that will be it.  Or, striving for interoperability with commercial products may make people just give up entirely on open source because the corporations are implementing what open source develops for free.  I think it would be better to focus on building open source products that go their own direction independently and leave the companies in the dust.  That would create head to head competition rather than wannabe products.

Thank you for your comments. Most of the messages we receive are congratulations but messages like yours are always more useful to improve.

These are my conclusions from your frustration and some proposals.

You haven't answered my questions yet but my conclusion is that your problems started when you tried to install openplotter 3 over an old openplotter 2 installation. This cannot be done without breaking the system and can only be done by following the "advanced" method. As a solution we will add a huge warning on the download page of the advanced method.

Pypilot in openplotter 3 does not need any command to be executed in the terminal and any task can be carried out from the graphical interface. In this thread it is recommended to carry out some manual tasks that come from the time when pypilot was not yet fully integrated into openplotter 3 and you had to force the installation. As a solution we should mark this confusing thread as obsolete. More background: https://forum.openmarine.net/showthread.php?tid=4221

You are right, DIY projects are not for everyone but there is little we can do there. The objective of openplotter is to bring development closer to non-advanced users and we believe that a lot is achieved but each one has its own limit.

You have been recommended to try other systems that claim to be more plug and play, I can only say that you try it and then tell us about your experience. Remember to read the Getting Started section and its 64 chapters before installing, paying special attention to the pypilot chapter

I had a version of OP  installed from over a year ago.  I have been unable to use my boat for a while and the version was outdated.  While using it recently, OP said I needed to upgrade and I merely upgraded using the upgrade that is part of OP.  After your message above, I wiped the system and started from a clean download with the link you provided.  The new version also had the same problems as the old and then it self-destructed.  I do think that hardware was one of the major contributors to the problem, and to my frustration, but my critique of OP and its user friendliness are valid in my view. 

I think you are failing to confront the realities of the user.  You must keep in mind that I have now installed OpenCPN and Pypilot on an operating system that has no software related to boats or anything related to signal k.  It has none of the tools you have in OP and it works.  That is something I have never been able to accomplish with OP.  I think that says a lot and it is something you should take to heart!

The documentation is a critical component for any user to get started.  OP's documentation has whole sections that are empty (coming soon).  There is nothing in there about Pypilot integration.  It would be better to have a solid documentation with physical installation scenarios rather than for people to constantly write to a forum to get things working. 

I argue that there should be a base functionality that gets you a working system with a chart plotter (OpenCPN), autopilot (Pypilot), and weather.  The dashboard should work with these three items. 

Let me finish by also offering congratulations.  If people like you did not work to build something like OP, we would not have it at all.  I thank you for this very much.  I want OP to work for me and I will try again but I need my OpenCPN and autopilot NOW.  Once I get my boat off before hurricane season gets into full swing, I will be able to play around with it more.  Thanks again.