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
Setup Tinypilot to SignalK/AVNav
#1
Hello,

I have a tinypilot by Navitop.fr and a RaspberryPi 4 with AVNav navigation software and SignalK. I would expect that, if the WIFI-connections of pypilot are set to:

mTinypilot WLAN-Konfiguration
AP and client
Zugangspunkt SSID pypilot
Zugangspunkt Schlüssel (leer lassen für keine Verschlüsselung) 
Client SSID (of my Raspi4AP)
Client Schlüssel (mypassword)
Client-Modus-Adresse (leer lassen für DHCP) 

would simply bring up the connection to my boatnetwork and pypilot could receive data from signalk. But it doesn't work this way. 

Please let me know, how to setup this connection step by step.

Thank you
Michael
Reply
#2
The explanation and a temporary solution can be found in this link.

https://forum.openmarine.net/showthread.php?tid=6532

Personally, this no longer bothers me because I prefer to have Pypilot as the master of the Wi-Fi network. The autopilot is always powered and ready to use, while the other instruments and the tablet are only switched on intermittently. This way, I'm certain that my autopilot will always be functional and accessible from any device with a web browser or OpenCPN, even if the rest of the onboard electronics fail.

This is especially problematic if you want to install another Raspberry Pi with Pypilot in "remote mode" as a repeater with buttons and LCD display. You then need to follow the steps described in the link to configure Pypilot's "remote mode" as a client.
Reply
#3
(2026-04-13, 06:02 PM)Arbalete Wrote: Hello,

I have a tinypilot by Navitop.fr and a RaspberryPi 4 with AVNav navigation software and SignalK. I would expect that, if the WIFI-connections of pypilot are set to:

mTinypilot WLAN-Konfiguration
AP and client
Zugangspunkt SSID pypilot
Zugangspunkt Schlüssel (leer lassen für keine Verschlüsselung) 
Client SSID (of my Raspi4AP)
Client Schlüssel (mypassword)
Client-Modus-Adresse (leer lassen für DHCP) 

would simply bring up the connection to my boatnetwork and pypilot could receive data from signalk. But it doesn't work this way. 

Please let me know, how to setup this connection step by step.

Thank you
Michael

all answers regarding pypilot you may find at this link
https://www.facebook.com/groups/1677078816603405/
Reply
#4
My setup is
  • Signalk : raspberry PI 4 (ip 192.168.3.2)
  • Avnav : raspberry PI 3 (ip 192.168.3.4)
  • Pypilot : raspberry PI zero (ip 192.168.3.3)
  • Wifi router (ip 192.168.3.1)

Signalk, Avnav and Pypilot are wire connected to the wifi router
To wire connect the pypilot 
  • usb to ethernet adaptator 
  • load module net-usb-4.9.22-piCore.tcz
  • add to bootlocal.sh
    Code:
    chpst -utc tce-load -i net-usb >> $DEBUG
    ifconfig eth0 192.168.3.3

Everything is working well since 2 years
I use pypilot in
  • compas (from pypilot sensor)
  • gps (from sensor connected to signalk server)
  • wind / true wind (from wind sensor connected in NMEA183 to signalk server)
  • Nav (from route make in Avnav)
Reply
#5
But why does it work with Openplotter, but not with SingnalK and AVNnav?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)