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
Pypilot for dummies
#21
Sorry should have mentioned: this is still work in progress. What's there are some notes. Haven't figured it out myself yet ?.
Reply
#22
I’ve worked through the steps until step 6, at which point there is an Arduino connected to a Raspberry Pi (3 or 4) via USB. This is shown in the first photo in this section.

Are there operational systems where a motor controller is connected directly to the raspberry Pi (3 or 4)?

This is where I end up by the end of step 9 before Tinypilot is introduced.

Tinypilot provides a simple standalone autohelm.
The Pypilot software is part of the Tinypilot software. Tinypilot will not run on a Pi (3 or 4).
Tinypilot software is intended to be used with a Pi zero W but does use the motor controller previously discussed.

Out of interest which was developed first? Tinypilot or Pypilot as part of OpenPlotter / OpenCPN (Im happy if someone would explain the difference between these packages)

Personally having Tinypilot at step 1 makes more sense as I'm familiar with a Tiller Pilot. This stands regardless of the historical order of development. That way you start simple and build up to the whole plotter package. Seems better given that this started as a Dummies guide. What do others think?

Although Ive read the following steps I would like to get these questions clear in my head first.
Reply
#23
pypilot was developed on tinypilot since the beginning and I continue to develop on the tinypilot platform, but since pypilot is very portable, it works on most linux systems, but laptops for example can't run rtimulib2, and without certain dependencies various parts of pypilot are disabled, but unlike many compiled programs certain missing libraries does not prevent it from working at all.
Reply
#24
(2021-04-19, 07:58 AM)ironman Wrote: I think this is my cue for building up a workbook page with all information that can be found on this forum on what all those parameters mean.


I just trawled through a number of settings and collated from the forum and the code what I could find about them; see https://github.com/pypilotWorkbook/workb...parameters. The selection of settings are those that are stored in pypilot.conf; some are blatantly obvious and I've already started to thin out the list. Feedback welcome, as always!
Reply
#25
I got some questions about the HAT and realized I left that section in the workbook still unfinished. So I updated that section to the best of my understanding. Feedback welcome!

https://github.com/pypilot/workbook/wiki...-interface
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)