This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Autopilot route plugin
#21
It's hard to say without more information. I can say the raspberry gives me strange problems that no one else sees.

For example, it won't boot with hdmi plugged in. I have, and the display is blurry unless I use the GL driver. Then, the mouse cursor often becomes invisible and doesn't reappear until the next boot.
Reply
#22
(2020-08-01, 01:05 AM)seandepagnier Wrote: It's hard to say without more information.   I can say the raspberry gives me strange problems that no one else sees.

For example, it won't boot with hdmi plugged in.  I have, and the display is blurry unless I use the GL driver.   Then, the mouse cursor often becomes invisible and doesn't reappear until the next boot.

So here is a log from today, I had to reboot a few times out there so its short, but you can see that pypilot is just exiting for what seems like no reason?
Any idea?

FYI I was able to plot and follow a route today without incident... except the above mentioned issue of the periodic exiting but that happens using compass mode or gps.
Reply
#23
You didn't post the file
Reply
#24
(2020-08-02, 07:12 PM)seandepagnier Wrote: You didn't post the file

Well that is unfortunate as it is gone now... I will post a new one next time I go out. 


Thanks!
Reply
#25
(2020-08-02, 07:12 PM)seandepagnier Wrote: You didn't post the file

The log. Basically Pypilot is going from a connected activated state... as in Autopilot is engaged, and then it crashes? the plugin window stays open, just Autopilot goes from engaged to disengaged. Sure would be nice to get some sort of warning when this happens...

Code:
pi@openplotter:~ $ journalctl -u  pypilot.service
-- Logs begin at Thu 2020-08-06 02:34:13 EDT, end at Fri 2020-08-07 17:56:58 EDT. --
Aug 06 12:25:01 openplotter systemd[1]: pypilot.service: Main process exited, code=killed, status=13/PIPE
Aug 06 12:25:01 openplotter systemd[1]: pypilot.service: Succeeded.
Aug 06 12:25:03 openplotter systemd[1]: pypilot.service: Service RestartSec=2s expired, scheduling restart.
Aug 06 12:25:03 openplotter systemd[1]: pypilot.service: Scheduled restart job, restart counter is at 2.
Aug 06 12:25:03 openplotter systemd[1]: Stopped pypilot.
Aug 06 12:25:03 openplotter systemd[1]: Started pypilot.
Aug 06 12:25:04 openplotter sudo[27310]:       pi : TTY=unknown ; PWD=/home/pi/.pypilot ; USER=root ; COMMAND=/usr/bin/chrt -p
Aug 06 12:25:04 openplotter sudo[27312]:       pi : TTY=unknown ; PWD=/home/pi/.pypilot ; USER=root ; COMMAND=/usr/bin/chrt -p
Aug 06 12:25:04 openplotter sudo[27310]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 06 12:25:04 openplotter sudo[27310]: pam_unix(sudo:session): session closed for user root
Aug 06 12:25:04 openplotter sudo[27312]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 06 12:25:04 openplotter sudo[27312]: pam_unix(sudo:session): session closed for user root
Aug 06 12:25:04 openplotter sudo[27324]:       pi : TTY=unknown ; PWD=/home/pi/.pypilot ; USER=root ; COMMAND=/usr/bin/chrt -p
Aug 06 12:25:04 openplotter sudo[27324]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 06 12:25:04 openplotter sudo[27324]: pam_unix(sudo:session): session closed for user root
Aug 06 12:55:03 openplotter systemd[1]: pypilot.service: Main process exited, code=killed, status=13/PIPE
Aug 06 12:55:03 openplotter systemd[1]: pypilot.service: Succeeded.
Aug 06 12:55:05 openplotter systemd[1]: pypilot.service: Service RestartSec=2s expired, scheduling restart.
Aug 06 12:55:05 openplotter systemd[1]: pypilot.service: Scheduled restart job, restart counter is at 3.
Aug 06 12:55:05 openplotter systemd[1]: Stopped pypilot.
Aug 06 12:55:05 openplotter systemd[1]: Started pypilot.
Aug 06 12:55:06 openplotter sudo[29234]:       pi : TTY=unknown ; PWD=/home/pi/.pypilot ; USER=root ; COMMAND=/usr/bin/chrt -p
Aug 06 12:55:06 openplotter sudo[29236]:       pi : TTY=unknown ; PWD=/home/pi/.pypilot ; USER=root ; COMMAND=/usr/bin/chrt -p
Aug 06 12:55:06 openplotter sudo[29234]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 06 12:55:06 openplotter sudo[29236]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 06 12:55:06 openplotter sudo[29234]: pam_unix(sudo:session): session closed for user root
Aug 06 12:55:06 openplotter sudo[29236]: pam_unix(sudo:session): session closed for user root
Aug 06 12:55:06 openplotter sudo[29247]:       pi : TTY=unknown ; PWD=/home/pi/.pypilot ; USER=root ; COMMAND=/usr/bin/chrt -p
Aug 06 12:55:06 openplotter sudo[29247]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 06 12:55:06 openplotter sudo[29247]: pam_unix(sudo:session): session closed for user root
Aug 07 07:56:21 openplotter systemd[1]: pypilot.service: Main process exited, code=killed, status=13/PIPE
Aug 07 07:56:21 openplotter systemd[1]: pypilot.service: Succeeded.
Aug 07 07:56:23 openplotter systemd[1]: pypilot.service: Service RestartSec=2s expired, scheduling restart.
Aug 07 07:56:23 openplotter systemd[1]: pypilot.service: Scheduled restart job, restart counter is at 4.
Aug 07 07:56:23 openplotter systemd[1]: Stopped pypilot.
Aug 07 07:56:23 openplotter systemd[1]: Started pypilot.
Aug 07 07:56:24 openplotter sudo[4463]:       pi : TTY=unknown ; PWD=/home/pi/.pypilot ; USER=root ; COMMAND=/usr/bin/chrt -pi
Aug 07 07:56:24 openplotter sudo[4463]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 07 07:56:24 openplotter sudo[4463]: pam_unix(sudo:session): session closed for user root
Aug 07 07:56:24 openplotter sudo[4468]:       pi : TTY=unknown ; PWD=/home/pi/.pypilot ; USER=root ; COMMAND=/usr/bin/chrt -pf
Aug 07 07:56:25 openplotter sudo[4468]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 07 07:56:25 openplotter sudo[4474]:       pi : TTY=unknown ; PWD=/home/pi/.pypilot ; USER=root ; COMMAND=/usr/bin/chrt -pf
Aug 07 07:56:25 openplotter sudo[4468]: pam_unix(sudo:session): session closed for user root
Aug 07 07:56:25 openplotter sudo[4474]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 07 07:56:25 openplotter sudo[4474]: pam_unix(sudo:session): session closed for user root
Aug 07 13:36:39 openplotter systemd[1]: pypilot.service: Main process exited, code=killed, status=13/PIPE
Aug 07 13:36:39 openplotter systemd[1]: pypilot.service: Succeeded.
Aug 07 13:36:41 openplotter systemd[1]: pypilot.service: Service RestartSec=2s expired, scheduling restart.
Aug 07 13:36:41 openplotter systemd[1]: pypilot.service: Scheduled restart job, restart counter is at 5.
Aug 07 13:36:41 openplotter systemd[1]: Stopped pypilot.
Aug 07 13:36:41 openplotter systemd[1]: Started pypilot.
Aug 07 13:36:43 openplotter sudo[26218]:       pi : TTY=unknown ; PWD=/home/pi/.pypilot ; USER=root ; COMMAND=/usr/bin/chrt -p
Aug 07 13:36:43 openplotter sudo[26220]:       pi : TTY=unknown ; PWD=/home/pi/.pypilot ; USER=root ; COMMAND=/usr/bin/chrt -p
Aug 07 13:36:43 openplotter sudo[26218]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 07 13:36:43 openplotter sudo[26220]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 07 13:36:43 openplotter sudo[26218]: pam_unix(sudo:session): session closed for user root
Aug 07 13:36:43 openplotter sudo[26220]: pam_unix(sudo:session): session closed for user root
Aug 07 13:36:43 openplotter sudo[26234]:       pi : TTY=unknown ; PWD=/home/pi/.pypilot ; USER=root ; COMMAND=/usr/bin/chrt -p
Aug 07 13:36:43 openplotter sudo[26234]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 07 13:36:43 openplotter sudo[26234]: pam_unix(sudo:session): session closed for user root


I will add my experience using the "autopilot route plugin" 
anytime ARP (autopilot Route Plugin) is enabled and I attempt to activate a route, Pypilot sets a course almost exactyly 180 degs away from the first waypoint... even if that way-point is kilometres away....
I don't even know where to start with that one...
Reply
#26
I don't know where the log file is going but that isn't it. Could you stop pypilot with "sudo service pypilot stop" Then just run pypilot from the terminal "pypilot" and you should see the log I need. The 180 problem is something wrong with the route plugin.
Reply
#27
(7 hours ago)seandepagnier Wrote: I don't know where the log file is going but that isn't it.   Could you stop pypilot with "sudo service pypilot stop"  Then just run pypilot from the terminal "pypilot" and you should see the log I need.   The 180 problem is something wrong with the route plugin.

I will run the next time I'm out with pypilot running in a terminal window following your instructions next time I am out. 

I did have something that has not happened before happen today. 
AP was activated and we were trolling following a compass heading, when without any input from us the engine was turned hard to port... I looked at the pypilot plugin window in openCPN and it displayed a message about saturation limit error and then AP was deactivated? Not the exact words but that is what I remember... If that happened at speed... it would be very concerning. Any idea what might cause that?

Here is the start up log I just executed on land. Maybe there is something in that that will help

Code:
pi@openplotter:~/.pypilot $ sudo service pypilot stop
pi@openplotter:~/.pypilot $ pypilot
loading servo calibration /home/pi/.pypilot/servocalibration
WARNING: using default servo calibration!!
Loaded Pilots: ['wind', 'learning', 'simple', 'basic', 'absolute']
warning: failed to open special file /dev/watchdog0 for writing
        cannot stroke the watchdog
connected to gpsd
Settings file not found. Using defaults and creating settings file
Using settings file RTIMULib.ini
Detected MPU9250/MPU9255 at standard address
Using fusion algorithm Kalman STATE4
IMU Name: MPU-925x
min/max compass calibration not in use
Using ellipsoid compass calibration
Using accel calibration
autopilot failed to read imu at time: 1596920172.1508598
serial exception ('/dev/ttyS0', 38400) nmea0 Could not configure port: (5, 'Input/output error')
sensors is running too _slowly_ 0.07401466369628906
MPU-925x init complete
autopilot failed to read imu at time: 1596920172.3855631
arduino servo found on ['/dev/ttyAMA0', 38400]
serialprobe success: /home/pi/.pypilot/servodevice ['/dev/ttyAMA0', 38400]
connect failed to localhost:21311
nmea process failed to connect pypilot [Errno 111] Connection refused
nmea ready for connections
listening on port 20220 for nmea connections
EEPROM SIGNATURE ok
setup wiatches True
found gps on tcp socket1GP
servo calibration invalid False
Reply


Forum Jump:


Users browsing this thread: xfactor99, 1 Guest(s)