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:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
OpenPlotter 4 roadmap
#61
Is there a link for the PI5 version?
Thx
D
Reply
#62
(2024-02-09, 09:11 PM)addboy Wrote: Is there a link for the PI5 version?
Thx
D

Use the links from the First post for Pi4 and 5
Reply
#63
Since I was still having problems with SensESP devices connecting via OP4 wifi on a RP5, I decided to by pass the openplotter wifi and use a local wifi router with a wired connection to the OP4 RP5. Still no joy, but the serial terminal shows that the device defaults back to the old OP3 wifi route: " Websocket is connecting to Signal K server on address 10.10.10.1:3000".

Here is the code which sets the sensesp app:
sensesp_app = (&builder)
// Set a custom hostname for the app.
->set_hostname("FreshWater")
// Optionally, hard-code the WiFi and Signal K server
// settings. This is normally not needed.
->set_wifi("SV-JROSE", "XXXXXXX")
->set_sk_server("192.168.3.80", 3000)
->get_app();

And here are the serial logs after the upload:
(connect)(C0) WiFi is disconnected. SignalK client connection will connect when WiFi is connected.
(wifi_station_connected)(C1) Connected to wifi, SSID: SV-JROSE (signal: -44)
(wifi_station_connected)(C1) IP address of Device: 192.168.3.82
(wifi_station_connected)(C1) Default route: 192.168.3.65
(wifi_station_connected)(C1) DNS server: 8.8.8.8
(operator())(C1) HTTP server started
(connect)(C0) Initiating websocket connection with server...
(connect)(C0) Websocket is connecting to Signal K server on address 10.10.10.1:3000
(test_token)(C1) Testing token with url http://10.10.10.1:3000/signalk/v1/stream
(test_token)(C0) Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkZXZpY2UiOiJhMWIwOWE0Zi1iMGUzLWZhNmEtNzUwNi05YjVlNWJiN2M3ZTkiLCJpYXQiOjE3MDI2ODI3NTR9.s-6O0bYBHCWLGDnpQIMiVBrscXZNearrLJcE5BdshEs
(test_token)(C0) GET... failed, error: connection refused
(connect)(C0) Initiating websocket connection with server...
(connect)(C0) Websocket is connecting to Signal K server on address 10.10.10.1:3000
(test_token)(C0) Testing token with url http://10.10.10.1:3000/signalk/v1/stream
(test_token)(C0) Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkZXZpY2UiOiJhMWIwOWE0Zi1iMGUzLWZhNmEtNzUwNi05YjVlNWJiN2M3ZTkiLCJpYXQiOjE3MDI2ODI3NTR9.s-6O0bYBHCWLGDnpQIMiVBrscXZNearrLJcE5BdshEs
...

///////
I'm at a loss as I don't enter "10.10.10.1" anywhere but use set_sk_server("192.168.3.80", 3000). It looks like the SK server has a hardwired default. Any ideas?

Paul
Reply
#64
(2024-02-10, 05:56 PM)dreuge Wrote: Since I was still having problems with SensESP devices connecting via OP4 wifi on a RP5, I decided to by pass the openplotter wifi and use a local wifi router with a wired connection to the OP4 RP5.  Still no joy, but the serial terminal shows that the device defaults back to the old OP3 wifi route: " Websocket is connecting to Signal K server on address 10.10.10.1:3000".   

Here is the code which sets the sensesp app:
sensesp_app = (&builder)
                    // Set a custom hostname for the app.
                    ->set_hostname("FreshWater")
                    // Optionally, hard-code the WiFi and Signal K server
                    // settings. This is normally not needed.
                    ->set_wifi("SV-JROSE", "XXXXXXX")
                    ->set_sk_server("192.168.3.80", 3000)
                    ->get_app();

And here are the serial logs after the upload:
(connect)(C0) WiFi is disconnected. SignalK client connection will connect when WiFi is connected.
(wifi_station_connected)(C1) Connected to wifi, SSID: SV-JROSE (signal: -44)
(wifi_station_connected)(C1) IP address of Device: 192.168.3.82
(wifi_station_connected)(C1) Default route: 192.168.3.65
(wifi_station_connected)(C1) DNS server: 8.8.8.8
(operator())(C1) HTTP server started
(connect)(C0) Initiating websocket connection with server...
(connect)(C0) Websocket is connecting to Signal K server on address 10.10.10.1:3000
(test_token)(C1) Testing token with url http://10.10.10.1:3000/signalk/v1/stream
(test_token)(C0) Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkZXZpY2UiOiJhMWIwOWE0Zi1iMGUzLWZhNmEtNzUwNi05YjVlNWJiN2M3ZTkiLCJpYXQiOjE3MDI2ODI3NTR9.s-6O0bYBHCWLGDnpQIMiVBrscXZNearrLJcE5BdshEs
(test_token)(C0) GET... failed, error: connection refused
(connect)(C0) Initiating websocket connection with server...
(connect)(C0) Websocket is connecting to Signal K server on address 10.10.10.1:3000
(test_token)(C0) Testing token with url http://10.10.10.1:3000/signalk/v1/stream
(test_token)(C0) Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkZXZpY2UiOiJhMWIwOWE0Zi1iMGUzLWZhNmEtNzUwNi05YjVlNWJiN2M3ZTkiLCJpYXQiOjE3MDI2ODI3NTR9.s-6O0bYBHCWLGDnpQIMiVBrscXZNearrLJcE5BdshEs
...

///////
I'm at a loss as I don't enter "10.10.10.1" anywhere but use set_sk_server("192.168.3.80", 3000).  It looks like the SK server has a hardwired default.  Any ideas?

Paul

I would reflash your ESP32 and try again. If you log onto the ESP32’s webpage, you may be able to release the previous settings, if you wanted to check that first?
Reply
#65
(2024-02-10, 06:41 PM)Techstyle Wrote: dreuge///////
I'm at a loss as I don't enter "10.10.10.1" anywhere but use set_sk_server("192.168.3.80", 3000).  It looks like the SK server has a hardwired default.  Any ideas?

Paul

I would reflash your ESP32 and try again. If you log onto the ESP32’s webpage, you may be able to release the previous settings, if you wanted to check that first?
YES YES YES!!!

I must have re-flashed a dozen times, BUT I did not know that the ESP32 had it own webpage interface.  I looked up the IPaddress on my router (and also noticed that "<hostname>.local" works too) and entered the address in my browser.  Bingo! It shows the setting for the Signal K server and also allowed me to change that address.  I entered my SK server's address (192.168.3.80), and all is now working as usual.


Thanks.
Reply
#66
Did some more testing and found that:

Autostart does not work for OpenCPN and neither did the Autostart of Chromium didn't work either.

The Chromium Autostart was per the following:
Code:
sudo nano /etc/xdg/lxsession/LXDE/autostart

Then add to this file:
@chromium-browser

as a work around for the time being I did the following:
Code:
1. Create the user’s session configuration directory:
    mkdir -p /home/pi/.config/lxsession/LXDE-pi
2. Copy the default autostart file into the directory created above:
    cp /etc/xdg/lxsession/LXDE-pi/autostart /home/pi/.config/lxsession/LXDE-pi/
3. Open /home/pi/.config/lxsession/LXDE-pi/autostart in your preferred text editor.
This does not require root or sudo.
4. Add the commands to the end of the file one program per line. Start a line with @ if you
want the windows manager to restart a program should it fail. For example:
    @chromium-browser
    @opencpn (until OP4 app works)
5. Save and close.
6. Logout and back in or reboot.

Hopefully this helps either as a temporary workaround or to helps the devs!
Reply
#67
autostart does work in OpenPlotter 4 because we use xxx.desktop files in /.config/autostart/ to do it. Try the autostart option in openplotter-opencpn-installer.

Do not use the lxsession approach to autostart because that will change when using Wayland or X11.
Reply
#68
(2024-02-12, 01:21 PM)Sailoog Wrote: autostart does work in OpenPlotter 4 because we use xxx.desktop files in /.config/autostart/ to do it. Try the autostart option in openplotter-opencpn-installer.

Do not use the lxsession approach to autostart because that will change when using Wayland or X11.

I will check again when I get home and send a screen shot, but the option to select autostart in the Openplotter OpenCPN installer was not available, I could not select it.
Reply
#69
(2024-02-12, 02:45 PM)Techstyle Wrote:
(2024-02-12, 01:21 PM)Sailoog Wrote: autostart does work in OpenPlotter 4 because we use xxx.desktop files in /.config/autostart/ to do it. Try the autostart option in openplotter-opencpn-installer.

Do not use the lxsession approach to autostart because that will change when using Wayland or X11.

I will check again when I get home and send a screen shot, but the option to select autostart in the Openplotter OpenCPN installer was not available, I could not select it.

I didn't realize, I had to "check version" first, after I did it is no longer greyed out and I selected autostart.  Additionally I removed the lxsession stuff I did yesterday and added a .desktop file to start up the Chromium browser. - thanks

additionally, with regard to my earlier initial findings on page 2, I added the following:
- heatsink case with twin fans: https://amzn.to/49vs1Xf
- a Pineberry Hatdrive Bottom: https://pineberrypi.com/products/hatdriv...0-for-rpi5
- a 256Gb M.2 PCI-e NVME SSD: https://amzn.to/3SzdtPL 

The top part of the case touches all the hot chips and the Pineberry hatdrive bottom is below the Pi on small standoffs, with the base of the case below it and acting as a heatsink to the SSD.

The earlier reported temperature was 85C, and now with similar things running, I see 50C and have never heard the fans come on - the active fan circuit comes on at 60C
Reply
#70
Hi,
Just installed OP4 on Rpi5
WOW it is absolutely cool. BUT....

Do you plan to add pypilot to OP4? any roadmap?
it is really deal breaker.

Viktor
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)