I see that the use of the Hat Moitessier in standalone mode is not very well known or at least no one claims to have used it. Therefore, after giving a couple of turns to the idea I have mounted a system similar to standalone assembly. I call it the Black Box.
As I had an old Rpi2 in disuse I have mounted the Hat Moitessier and I have installed OP2 the version with driver for the Moitessier. I have updated Signal K to accept Seatalk data and I have mounted it so that it is fed from the same Seatalk bus. I have to solder three wires to the Hat to be able to put the Seatalk data. It took a little time but it works fine.
This way I have a headless system that collects GPS, AIS, compass, accelerometer, barometer and temperature data from the same Moitesier and the rest of the data from the Seatalk bus. Everything is forwarded by wifi in NMEA0183 to port 10110 TCP, NMEA0183 to port 2000 UDP -for navionics App- and by Signal K to port 3000.
This system uses the Hat moitessier and the Seatalk input as a black box that collects and distributes all the Navigation data through wifi. It turns on along with the rest of the ST60 equipment and only increases the consumption by about 0.25 amps.
Then, apart I have the Rpi4 that is fed by the data from this black box, as well as the phones and tablets. This is where runs OpenCpn, Xygrib, Qtvlm Etc. That is to say the tools that require cpu power.
I think this separate assembly has many advantages. One of them is to better distribute the processing power. For the black box is not required too much. Only what is necessary to collect, add, filter and distribute the data. However by doing all this on the slow Rpi we leave all the power available from the powerful Rpi4 for the heavy applications. In addition, very often I don't need the Rpi4 to sail but I can use my phone or tablet outside drinking from the wifi data. So I keep the Rpi4 turned off because I don't need it. Another plus is that the redundancy of the equipment allows me to get out of trouble in case one of the rpi fails, which is otherwise unlikely.
To configure the black box I use any of the available systems. For example, to configure the Signal K server I can do it from any computer on the network, Rpi, tablet or phone simply by entering the IP of the black box. It's impossible to do it more simply. If what I want is to manipulate the desktop of the black box I use VNC but most of the times I simply use the ssh system from the Rpi4. With the -X parameter you can start in the rpi4 graphic applications from the black box like the ones that manage openplotter and its features directly.
I need to add a serial port to have a NMEA 0183 data output to send data to the autopilot and the Raymarine external data display. Once finished I think I have a fairly balanced assembly ... or so I hope.
As I had an old Rpi2 in disuse I have mounted the Hat Moitessier and I have installed OP2 the version with driver for the Moitessier. I have updated Signal K to accept Seatalk data and I have mounted it so that it is fed from the same Seatalk bus. I have to solder three wires to the Hat to be able to put the Seatalk data. It took a little time but it works fine.
This way I have a headless system that collects GPS, AIS, compass, accelerometer, barometer and temperature data from the same Moitesier and the rest of the data from the Seatalk bus. Everything is forwarded by wifi in NMEA0183 to port 10110 TCP, NMEA0183 to port 2000 UDP -for navionics App- and by Signal K to port 3000.
This system uses the Hat moitessier and the Seatalk input as a black box that collects and distributes all the Navigation data through wifi. It turns on along with the rest of the ST60 equipment and only increases the consumption by about 0.25 amps.
Then, apart I have the Rpi4 that is fed by the data from this black box, as well as the phones and tablets. This is where runs OpenCpn, Xygrib, Qtvlm Etc. That is to say the tools that require cpu power.
I think this separate assembly has many advantages. One of them is to better distribute the processing power. For the black box is not required too much. Only what is necessary to collect, add, filter and distribute the data. However by doing all this on the slow Rpi we leave all the power available from the powerful Rpi4 for the heavy applications. In addition, very often I don't need the Rpi4 to sail but I can use my phone or tablet outside drinking from the wifi data. So I keep the Rpi4 turned off because I don't need it. Another plus is that the redundancy of the equipment allows me to get out of trouble in case one of the rpi fails, which is otherwise unlikely.
To configure the black box I use any of the available systems. For example, to configure the Signal K server I can do it from any computer on the network, Rpi, tablet or phone simply by entering the IP of the black box. It's impossible to do it more simply. If what I want is to manipulate the desktop of the black box I use VNC but most of the times I simply use the ssh system from the Rpi4. With the -X parameter you can start in the rpi4 graphic applications from the black box like the ones that manage openplotter and its features directly.
I need to add a serial port to have a NMEA 0183 data output to send data to the autopilot and the Raymarine external data display. Once finished I think I have a fairly balanced assembly ... or so I hope.