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
LCD problem, v.2
#6
Quote:Short replies are of course laconic and great, but for people who don't know the stuff more explanation is needed.

First, you write:

"Program the wireless remote using

http://localhost:33333"

It seems to me that same thing, in more detail, should be:
  • Turn on the Raspberry Pi with Pypilot installed;
  • Connect to Openplotter on the computer, with ethernet cable stuck in the Raspberry;
  • Open VNC viewer on the computer and start the Openplotter;
  • Open web browser in the Openplotter;
  • Go to http://localhost:33333
Once there: what do "clear" and "default" buttons mean? These are the first to appear.
These clear all programming, and restore default settings respectively.
Quote: 
What is the difference between "auto" and "engage" buttons? Maybe "auto" engages the autopilot, but so does the "engage", it seems to me.
the auto button toggles the pilot on/off and also exits the menu.

the engage button will only turn the pilot on regardless of the menu.

The first is intended to be used if you can easily see the screen.
Quote:And there are many more buttons the meaning of which needs to be explained, such as "tack port" and "dodge port", etc. 

Probably, a separate chapter in a work
book should be devoted to explaining just this section: programming the remote to interact with the Pypilot. One needs to explain that "programming" means to associate certain buttons on the display with certain buttons on the remote, perhaps with video examples of the same. And of course the meaning of all buttons needs to be explained. I don't think this is asking for too much.
I intend to make a video about it...
Quote:So, mode #1 is controlling the Pypilot through the remote.

Mode #2 seems to be controlling it through smartphone, as you write: "run the web control enabling pypilot_web service".

Again, if that is true, you should explain that Open VNC viewer needs to be installed on the phone, and how that can be done. 
You dont need vnc.  Only a browser.

Quote:I did this experiment and uploaded here: https://youtu.be/NwfWfDJEu4Y 

Mode #3 seems to be controlling the Pypilot through a notebook, as I do at home, as you write: "use the pypilot opencpn plugin".
It is control through opencpn which runs on a variety of platforms.
Quote:Alternatively, one can add an LCD screen to the Raspberry Pi 4, and a keyboard, both controlled through Bluetooth. But a regular computer running Windows seems a better option, as one is more used to that system. And the LCD screen for Raspberry Pi that I have is certainly not waterproof.   

Mode #4 seems to be running Pypilot through a terminal on Raspberry Pi, as you write: "run "pypilot_control" script". Again, this boils to mode #3 above. Am I right?
The pypilot_control and/or pypilot_client scripts can generally run on most linux machines.   They probably can work on other platforms but I have no experience.   They dont have to run on the same raspberry pi but if this is the only linux machine then this is probably where they would be run from.    You could even use pypilot_client from a ssh client.
Quote:So, the options for controlling the autopilot seem to be:

1) Use infrared remote,
2) Use a smart phone, or
3) Use a computer, or 
4) Raspberry Pi connected to a screen and a keyboard, and a mouse. 
#1 can include the RF remote control if your hardware supports it, so work anywhere on the boat. It also includes optional wired buttons but most users use a remote.

#2  is not specifically a phone, but anything with a web browser

#3 is again really opencpn, which includes linux, windows, or macos.  the android support of the pypilot plugin is not maintained.

#4 is again,  scripts that typically run on linux systems so run fine on raspberry pi, but I can also use them remotely on a linux notebook, or a different raspberry pi.

I hope this clears it up.
Quote:Am I right? 

Another thing: if we're using the Raspberry Pi on board, one needs to power it from 12 volts. What is your advice on that? From my research, I am about to order this waterproof 12 to 5 volt power adapter:

https://www.amazon.com/gp/product/B09DGD...61PQ&psc=1  

Is this a good choice? Other alternatives? Nothing has been said about that in the workbook.
It looks like a good choice.
Reply


Messages In This Thread
LCD problem, v.2 - by Gennady - 2022-11-13, 10:53 PM
RE: LCD problem, v.2 - by seandepagnier - 2022-11-15, 03:52 PM
RE: LCD problem, v.2 - by Gennady - 2022-11-16, 02:43 AM
RE: LCD problem, v.2 - by seandepagnier - 2022-11-16, 08:56 AM
RE: LCD problem, v.2 - by Gennady - 2022-11-20, 06:34 PM
RE: LCD problem, v.2 - by seandepagnier - 2022-11-20, 06:59 PM
RE: LCD problem, v.2 - by Gennady - 2022-11-20, 08:41 PM
RE: LCD problem, v.2 - by stelian - 2022-11-20, 09:24 PM
RE: LCD problem, v.2 - by Gennady - 2022-11-20, 10:17 PM
RE: LCD problem, v.2 - by stelian - 2022-11-20, 10:31 PM
RE: LCD problem, v.2 - by Gennady - 2022-11-20, 11:22 PM
RE: LCD problem, v.2 - by seandepagnier - 2022-11-22, 05:06 AM
RE: LCD problem, v.2 - by Gennady - 2022-11-23, 12:52 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)