(2023-03-06, 10:57 PM)seandepagnier Wrote: [ -> ]you can ignore the warning about APT on tinycore... on tinycore the dependencies are fulfilled manually but normally in place already.
Thanks Sean,
We are now in Tonga down to NZ in few days, We have used Pypilot(0.32) since the Marquesas and it is doing very well. More recently we experienced lost of data : from time to time opencpn(5.6.2) was no longer receiving data from pypilot (who receives data from the actisense W2-1 as a client) and pypilot data (eg rudder angle) was also lost.
Pypilot continues to do its job but only on the compass mode (GWT modes disappear) few minutes later GWT were back (on opencpn ) but also on the pypilot screen.
I've check on various computers, this is not related to the raspberry running opencpn. I've got the same on my linux PC (opencpn 5.8.2)
This happen several times per hours but not regularly
I should add that pypilot was running for more than one week continously
Any idea ?
thanks for your help
Elea
It could be an issue with opencpn. For example if the wifi network is disrupted the opencpn connection logic could be bad.
If you restart opencpn does the connection come back? What steps do you take to restore it?
(2023-05-25, 07:13 AM)seandepagnier Wrote: [ -> ]It could be an issue with opencpn. For example if the wifi network is disrupted the opencpn connection logic could be bad.
If you restart opencpn does the connection come back? What steps do you take to restore it?
Nop, I tried to restart pypilot, and/or restart opencpn - same behavior, it looks like random. losing the "G" and opencpn connection on pypilot, pypilot fall back on the "C" to continue to steer the boat, then few minutes later connection comes back, opencpn got the boat data (gps, cog,soc etc... and pypilot screen is back "CGWT"
Any log I should look at ?
I'd appreciate your excellent suggestions on WK1..
My sailboat setup originally started with an Actisense Wk1 so I could send NMEA2000 to Navionics (NMEA 0183). I then added a Raspberry Pi5 Openplotter and logged into Actisense WK1 as a client to NMEA 0183 (send / receive) on 60003. And this was excellent. I can send all of my NMEA 2000 data like GPS, AIS, wind, depth, etc to Openplotter and receive openplotter course, xte, btw, etc data once a course is activated back to my NMEA backbone. So Openplotter data turns up on my small Raymarine i70s display.
So here's the question. I've recently bought and added Sean's TinyPilot setup. The compass steering is excellent. I now want to log Sean's TinyPilot setup into the Actisense WK1 to pickup the course and wind data. My approach with TinyPilot was to select AP+client so I could also access the TinyPilot on a smart phone but I quickly lost reliable wifi browser contact via 192.168.14.1. And I don't know best settings for Actisense WK1. How should I do this and settings you would recommend?
(2023-05-25, 07:53 AM)Elea Wrote: [ -> ] (2023-05-25, 07:13 AM)seandepagnier Wrote: [ -> ]It could be an issue with opencpn. For example if the wifi network is disrupted the opencpn connection logic could be bad.
If you restart opencpn does the connection come back? What steps do you take to restore it?
Nop, I tried to restart pypilot, and/or restart opencpn - same behavior, it looks like random. losing the "G" and opencpn connection on pypilot, pypilot fall back on the "C" to continue to steer the boat, then few minutes later connection comes back, opencpn got the boat data (gps, cog,soc etc... and pypilot screen is back "CGWT"
Any log I should look at ?
Sorry for the slow reply.. I would first see if you can ping the tinypilot when the data drops. Check the OpenCPN debug window and see if the data is being sent. You can also check the log files on the tinypilot, either via ssh, or the web interface. It should show if the source for gps and wind are found or lost.
(2024-07-01, 09:40 PM)Blue Horizon Wrote: [ -> ]I'd appreciate your excellent suggestions on WK1..
My sailboat setup originally started with an Actisense Wk1 so I could send NMEA2000 to Navionics (NMEA 0183). I then added a Raspberry Pi5 Openplotter and logged into Actisense WK1 as a client to NMEA 0183 (send / receive) on 60003. And this was excellent. I can send all of my NMEA 2000 data like GPS, AIS, wind, depth, etc to Openplotter and receive openplotter course, xte, btw, etc data once a course is activated back to my NMEA backbone. So Openplotter data turns up on my small Raymarine i70s display.
So here's the question. I've recently bought and added Sean's TinyPilot setup. The compass steering is excellent. I now want to log Sean's TinyPilot setup into the Actisense WK1 to pickup the course and wind data. My approach with TinyPilot was to select AP+client so I could also access the TinyPilot on a smart phone but I quickly lost reliable wifi browser contact via 192.168.14.1. And I don't know best settings for Actisense WK1. How should I do this and settings you would recommend?
By "lost reliable wifi" Do you mean it sort of works sometimes? It could have to do with the wifi channel of the access point being different.
I think you could be right to make the tinypilot a client to the actisense network. From there it can either be a nmea0183 client (configure from browser) or you can send nmea0183 to it on port 20220. I have not used the Actisense WK1 so I am not sure of the options it has.
(2024-07-03, 05:36 PM)seandepagnier Wrote: [ -> ] (2023-05-25, 07:53 AM)Elea Wrote: [ -> ] (2023-05-25, 07:13 AM)seandepagnier Wrote: [ -> ]It could be an issue with opencpn. For example if the wifi network is disrupted the opencpn connection logic could be bad.
If you restart opencpn does the connection come back? What steps do you take to restore it?
Nop, I tried to restart pypilot, and/or restart opencpn - same behavior, it looks like random. losing the "G" and opencpn connection on pypilot, pypilot fall back on the "C" to continue to steer the boat, then few minutes later connection comes back, opencpn got the boat data (gps, cog,soc etc... and pypilot screen is back "CGWT"
Any log I should look at ?
Sorry for the slow reply.. I would first see if you can ping the tinypilot when the data drops. Check the OpenCPN debug window and see if the data is being sent. You can also check the log files on the tinypilot, either via ssh, or the web interface. It should show if the source for gps and wind are found or lost.
(2024-07-01, 09:40 PM)Blue Horizon Wrote: [ -> ]I'd appreciate your excellent suggestions on WK1..
My sailboat setup originally started with an Actisense Wk1 so I could send NMEA2000 to Navionics (NMEA 0183). I then added a Raspberry Pi5 Openplotter and logged into Actisense WK1 as a client to NMEA 0183 (send / receive) on 60003. And this was excellent. I can send all of my NMEA 2000 data like GPS, AIS, wind, depth, etc to Openplotter and receive openplotter course, xte, btw, etc data once a course is activated back to my NMEA backbone. So Openplotter data turns up on my small Raymarine i70s display.
So here's the question. I've recently bought and added Sean's TinyPilot setup. The compass steering is excellent. I now want to log Sean's TinyPilot setup into the Actisense WK1 to pickup the course and wind data. My approach with TinyPilot was to select AP+client so I could also access the TinyPilot on a smart phone but I quickly lost reliable wifi browser contact via 192.168.14.1. And I don't know best settings for Actisense WK1. How should I do this and settings you would recommend?
By "lost reliable wifi" Do you mean it sort of works sometimes? It could have to do with the wifi channel of the access point being different.
I think you could be right to make the tinypilot a client to the actisense network. From there it can either be a nmea0183 client (configure from browser) or you can send nmea0183 to it on port 20220. I have not used the Actisense WK1 so I am not sure of the options it has.
Hi Sean - thanks for checking in on this one.
Very helpful to know that I'm pointing in the right direction using AP + client to reach Actisense WK1. Probably obvious to most people but I'm a newbie - how do I configure NMEA0183 client from browser... or send nmea0183 to port 20220. Thanks!
And yes exactly, by "lost reliable wifi" I do mean if it's in the default setting the iphone easy logs into tiny pilot and browser works well anywhere on the boat. If I switch to "AP + Client" even with the iphone right beside the Tinypilot it's intermittent to hold to Pypilot wifi or use the browser command if I do. I'm assuming the AP part of the selection is what is giving me access to the Tiny Pilot via 192.168.14.1 And the + client is letting me access the Actisense Wk1
The configuration of nmea0183 from a browser should be possible in the web control (
http://192.168.14.1) under configuration.
As for sending nmea0183 to port 20220, that would be for the actisense to do. If it can be configured to connect to a remote ip and port and send/receive data.
Is the wifi intermittent on both AP and Client or just the AP? It should still be reliable as a client right? It is not ideal, but if the phone connects as a client to your actisense, it should be able to access the tinypilot via whatever IP the actisense gave it.. Unfortunately it may be the case that AP+Client is not so reliable, especially if they are on different wifi channels.
(2024-07-05, 02:55 PM)seandepagnier Wrote: [ -> ]The configuration of nmea0183 from a browser should be possible in the web control (http://192.168.14.1) under configuration.
As for sending nmea0183 to port 20220, that would be for the actisense to do. If it can be configured to connect to a remote ip and port and send/receive data.
Is the wifi intermittent on both AP and Client or just the AP? It should still be reliable as a client right? It is not ideal, but if the phone connects as a client to your actisense, it should be able to access the tinypilot via whatever IP the actisense gave it.. Unfortunately it may be the case that AP+Client is not so reliable, especially if they are on different wifi channels.
Thanks for quick reply Sean. Haven't got client connection going yet as I wasn't sure what the strategy was (and settings) and this and the all the above is very helpful. The dropout issue so far for browser is AP+Client mode only but I'll head back to the boat try it again and confirm that again.
Actisense from what I've read defaults to AP mode (with three AP points to choose from) and default is channel 1. Or it can run in Client mode. I'm trying to get Tinypilot in Client mode to access Actisense in AP mode. I was thinking I need to change the port number on Actisense to 20220 to match the TinyPilot. I'm guessing the alternative I haven't tried is to switch one of the Actisense AP points to Client mode (send/receive) and access the Pypilot AP. Any thoughts on these ideas are much appreciated!
I found this link re: Actisense with Openplotter :
https://actisense.com/news/using-the-w2k...h-opencpn/
Also this manual:
https://actisense.com/wp-content/uploads...e-2.10.pdf
Here's a brief summary from the manual:
The W2K-1 can be used in either Access Point mode or Client Mode (also referred to as Station or STA
mode) Both modes can also be used simultaneously under certain circumstances.
Access Point Mode
This is the default mode for the W2K-1 used for initial configuration. This mode can also be used where
other Wi-Fi devices need to connect to / exchange data with the W2K-1 in the absence of an existing Wi-Fi
network. The W2K-1 will, by default, use channel 1 in this mode.
Client Mode
This is where the W2K-1 will become a “client” on an existing Wi-Fi enabled network, enabling the W2K-1 to
connect to / exchange data with other devices connected to that existing network. The W2K-1 will switch to
the Wi-Fi channel of the client network in this mode. See Wi-Fi Client settings.
The best setup in my opinion would be an ad-hoc wifi network. This is neither client or AP, but allows all devices to communicate without any access point or master required. In this sense you would not depend on the AP running for the network to work.
Unfortunately this network mode is not very common or widely used...