What's needed for an entity to be shown in Freeboard
I'm working on the Meshtastic integration with Signal K (https://github.com/meri-imperiumi/signalk-meshtastic#readme), and I am populating the seen Meshtastic devices into Signal K entities of their own. If a node can be associated with a vessel, then that additional paths go there. If not, a separate
meshtastic.urn:meshtastic:node:NNNNNN will be populated.
It would be nice to see these in Freeboard, but I'm not sure what would be needed for that apart from having a navigation.position entry.
So, what are the requirements? Do I need to put them into vessels.? Do they need some particular paths populated?
17 Replies
https://www.npmjs.com/package/netais
It's work via Yggdrasil, not only via TOR. It can be done through the Meshtastic, I think.
Work with Freeboard, yes.
@Владимир Калачихин ok, thanks. That's a good example. I suppose not populating
mmsi on my end is one of the reasons at least to why they don't show up. I wonder if I should use the 98 MID for these
And I see you're using vessels.This is the same as other AIS targets. Therefore, the Freeboard shows them.
The thing is, these are of course not actual AIS targets. So question is how far should I try to make them resemble those
I definitely don't want them accidentally ending up on MarineTraffic or something 😛
In the SignalK is no concept " AIS targets". All vessels are equal.
Sure, and that's why I'm trying to figure out what exactly are the minimum parameters I need to fill in
There doesn't seem to be a plugin that sends all vessels from the SignalK to the MarineTraffic.
For MMSI, it seems this would mostly apply: https://www.itu.int/dms_pubrec/itu-r/rec/m/R-REC-M.585-8-201910-I!!PDF-E.pdf
Craft associated with a parent ship, need unique identification. These crafts which participate in the maritime mobile service should be assigned a nine-digit unique number in the format 98MIDXXXX where the digits 3, 4 and 5 represent the MID and X is any figure from 0 to 9.If I read it right, in some places you're putting a UUID to the MMSI path?
I don't remember. There, the mmsi is created from the name of the vessel, without regard to the rules. It's not very important.
I think there is way to show things other than AIS targets.
Wait for @AdrianP to reply
Freeboard-SK processes the following SIgnal K contexts:
- vessels
- atons
- sar
- aircraft
- meteo
(meteo context is populated from AIS messages. ping @Karl-Erik Gustafsson)
If you place them under vessels,
navigation.position should be enough to display them on the map.
If you use the meshstatic context then they will not be visible as FSK will not process those deltas.Thx. I wonder if atons would be a more accurate context. Though some of them are vessels, for example the Meshtastic tracker in our dinghy
we should have a place for things like "notes"?
I thought we did
or things like Active Captain
marinas, etc.
So ActiveCaptain plugin utilises Notes... these are generally "static" entries though.
I would go either with 98MIDxxxx or bend rules locally to use Main Ship MMSI + Dinghy digit. Both would work fine with FSK.
If you send Meshtastic data (carrier link), would it be freely receivable by others and then possibly proxied to 3rd party services like Marinetraffic?
If yes, then I see potential problem. If data is encrypted and only you can see it and you can control it, then there is no problems to use either.
Meshtastic traffic/telemetry is "stock" so there's just the Meshtastic node ID associated with each, no MMSI. So any MMSI or vessel creation happens on the receiving end with the plugin
But, verified that with a 98 MMSI and putting them into vessels context, the Meshtastic devices show up as targets
