it seems that either I have misread the manual or the cerbo has a problem with my GPS signaling.
I do have a Cerbo GX, Software Version 3.73. Attached to it is a USB GPS device. That one can be seen in the Cerbo’s device list and the coordinates are visible in VRM and my local MQTT browser.
The CerboGX is attached to a N2K network by the appropriate VE-Bus-2-NMEA cable.
The N2K network has a Yacht Device s WIFI Gateway onto which I connect with a signalk-server (RAW, TCP) . The signalk-server is not installed on the Cerbo.
I do see battery and tank status on the N2K network coming from the cerbo and the cerbo also does see some N2K data from another N2K tank sensor.
That means that the N2K connection works.
But I do not see the GPS data. When I read the manual correct, the Cerbo acts as a bridge for all attached devices towards the N2K network. So it should bridge the USB-GPS output to N2K, shouldn’t it?
What can I do to debug this or am I wrong with that assessment?
It is not yet supported. Only Cerbo getting GPS from NMEA2K, not sending from Cerbo to NMEA2K via NMEA2000OUT. I just asked this earlier this week in this topic: Does VenusOS support NMEA2000-out for GPS? - #2 by citolen . But it’s another good signal for a feature request to Victron to make it happen :).
Ah, thank you for that. I wonder why I did not find the refererred threat. But anyway, yes, it would be a good thing and would be consistent with the manual. No such restriction exists there.
Luckily this is not really important here since I do have two other completely independent GPS receivers with N2K. Was just curious to know why I do not see that data.
I was interested to read that you had gps data on your local mqtt browser and I have looked at my own (MQTT Explorer) and found that I have gps info there too. I’ve got lat., long., course, speed and some other info which I don’t need, what I do need, the time, is not there. Do you know of a way to get the gps time to display on the mqtt browser ?
As far as I know, getting the correct time isn’t that straightforward. The GPS outputs a timestamp (in UTC), which then has to be converted accordingly. However, because of the rollover mechanism (the developers didn’t allocate enough storage for the timestamp, so it’s more relative than absolute), the calculation isn’t quite so simple. The path for the “UTCTime” field in MQTT is
N/<gerät>/gps/0/UtcTime
The counter is currently at 80153000 and increments the fourth digit (the 3) every second…
An alternative (in my case) is a heartbeat. You can find it at N//heartbeat.
I’ve now solved the problem of feeding the position into my navigation system by running the main SignalK server on the Cerbo. It can collect the GPS signal from the USB port. The navigation software then accesses the SignalK data.
Edit: according to a source who shall remain nameless, it (my gps model) does send time (utctime) and date as it is an nmea–0183 standard protocol device. Still, it doesn’t help me as it is not on the remote console or mqtt.