Navigation data to MFD
Hello! I am so close to having a fully connected system between my autopilot, MFD, and signalK server. I set the MFD to send and receive navigation destination, and I see that the data for that shows up in the data browser, but it's not showing up in Freeboard. I also don't think setting a destination in Freeboard sends anything to the mfd.
I'm using a ShipModul MiniPlex (ethernet) to handle the communication to the NMEA 2000 MFD. It shows up as NMEA 0183 over TCP for SignalK. The MFD is successfully recieving AIS targets from SignalK.
17 Replies
It looks like the data is there. Why is it not showing in Freeboard?
Freeboard-SK looks at the
navigation.course.nextPoint path to display the destination set by the Course API.
There is a server PR that addresses this issue and will populate that path from NMEA data received.
Hopefully that will be merged soon.Ok, so just something to wait for and anticipate?
Does it also handle the other direction, or should I expect that to take more effort to set up?
So currently setting the destination in Freeboard-SK will populate the necessary paths and these will be transmitted as NMEA which makes it available to other devices.
This PR addresses the situation where destination is set and received via NMEA to populate the signalk course paths
I guess I should try the other direction now then
I just wanted to be careful, because I'm actively navigating with the MFD right now, so I'll need to do that from the cockpit.
Hmm, no change
Which NMEA sentences? The closest I see in SignalK-nmea0183 is RMB, which I had enabled and have now disabled since I would prefer for the MFD to do the bearing calculation
Perhaps WPL? But it's not listed as an option to generate in that plugin.
BWC or BWR
I don't see those
Oh I think they must only be used by the nmea-to-signalk plugin.
Hmm
RMB also has the waypoint coords, but that didn't seem to do anything when it was on
Also, the UI for setting the waypoint from Freeboard is really imprecise! I'll tap a spot, set waypoint, and it picks some other random location.
Describe random, completely out of the immediate range or close but not the selectee location?
Also what type of device phone, tablet, device with a mouse?
Browser on phone
There's no crosshairs or other cursor to say what you're picking, and even if there were, it is not putting it where I touch, or in the center of the screen
It is on the screen, at least
Interesting, my pixel phone seems to place the destination in the correct place.
The guide re the selected location on touch devices is the location of the top left corner of the menu.
That's where I would have expected it to have been, yeah.
I use Firefox on Android