LCD problem, v.2

[Gennady]

Hi all!

I seem to have an LCD problem, as indicated by this video: 

https://youtu.be/sk2jdlqihI0

The screen lights up, but there is no information on it.

Does anybody have a clue why?

Thanks,

Gennady

[seandepagnier]

Did you enable spi in raspi-config?

Did you enable the pypilot_hat service? If the screen isnt working the remote control probably wont either.

[Gennady]

Did you enable spi in raspi-config?

Did you enable the pypilot_hat service?    If the screen isnt working the remote control probably wont either.

Thank you Sean, the screen is working now, for the first time! This video shows that.

https://youtu.be/hh2qBACQP0w

I think the trick was turning on the hat service, as you suggested. Also, spi was not enabled before. 

The question now becomes: how does one control the autopilot on a boat? I mean: how to set the course using the compass? How to turn the autopilot on and off? I mean there should be a stand-by mode...

Also: what are other alternatives to windshield motor to drive the boat? 

Thanks for your answers,

Gennady

[seandepagnier]

You can use one of several control interfaces.

Program the wireless remote using
http://localhost:33333

Also run the web control enabling pypilot_web service

You can also use the pypilot opencpn plugin.

Finally, run "pypilot_control" script.

[Gennady]

You can use one of several control interfaces.

Program the wireless remote using
http://localhost:33333

Also run the web control enabling pypilot_web service

You can also use the pypilot opencpn plugin.

Finally,  run "pypilot_control" script.

Hi Sean!

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.
 
What is the difference between "auto" and "engage" buttons? Maybe "auto" engages the autopilot, but so does the "engage", it seems to me.

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

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. 

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

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?

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. 

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.

Thanks for your replies,

Gennady

[seandepagnier]

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.

 
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.

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

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.

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.

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.

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.

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.

[Gennady]

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.

 
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.

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

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.

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.

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.

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.

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.

Hi Sean!

Thank you for reply.

It seems to me that we, the people who are trying to make a Pypilot, are at different levels of technical knowledge. Hence, different levels of explanation are appropriate for different audiences. 

Once I have made something workable, I think I will write up one explanation, aimed at people like me, who are not very knowledgeable in programming and different platforms. I can send it to you, or any other person, who is coordinating this project. And some coordinator is needed, as we see Linux OS was/is (?) coordinated by Linus Torvalds, etc. 

So far, I have created a playlist called "Autopilot", where I show my progress in making that tool, from connecting Arduino to a GPS, to the present, where I am able to control the Pypilot through the IR remote.

https://www.youtube.com/watch?v=obPLwdd9...gKdVIlM1bq

Now, to specific explanations:

You write that for controlling the Pypilot through a smart phone, "You dont need vnc.  Only a browser."

I attach two screens from my phone: first is contacting the localhost:8000 without VNC viewer, and second through it. As you can see, it works only through VNC viewer. Why is that in contradiction to your explanation?

[stelian]

On your phone, you should not connect to 'localhost' but to the IP address of the pypilot controller ! (same address as you are using to connect to VNC)

[Gennady]

On your phone, you should not connect to 'localhost' but to the IP address of the pypilot controller ! (same address as you are using to connect to VNC)

Hello Stelian!

Thank you for your answer.

However, I continue to experience difficulties, which I will illustrate with screens from my phone.

First screen: addresses of my VNC viewer.

I suppose it is 10.10.10.1:5900

(By the way, I also tried 10.10.10.1)

Second screen shows what happens when I enter the address.

And final screen shows what happens when I connect to the address through VNC. This time, I am able to connect to Pypilot.

So, maybe you can explain where I am going wrong?

Thanks,

Gennady

[stelian]

You should try 10.10.10.1:8000 , or maybe the full URL : http://10.10.10.1:8000