irjudson - Question: anyone seen this error:Ap...
Question: anyone seen this error:
Apr 20 15:20:26 TypeError: Cannot read properties of null (reading 'latitude') at callback (/root/.signalk/node_modules/signalk-to-nmea2000/conversions/navigationdata.js:69:39) at /root/.signalk/node_modules/signalk-to-nmea2000/index.js:209:44 at Next.valueF
15 Replies
Something is wrong with your nav data. Position is null. Right?
navigation.position is correct, but other positions (anchor, etc are null)
It’s nextPoint
hm
I'm sitting in my yard debugging, that seems appropriate (that it would be null), right?
Yes. Bug in the code. It should be able to handle that.
ok, no worries, but I feel validated my understanding is improving
thx
But why is any of that data there if there is no nextPoint position?
that I cannot answer (yet)
you went beyond my understanding 🙂
Derived Data plugin creating it - hm
yes
Solved my probem, fwiw, getting GPS data from my Pi4 pican-m hat, to signalk, then out via NMEA0183 to my VHF
thank you for the help on understanding log messages
I do find at 38.4 baud I get more "not ready, not writing" messages than at 4800 baud - which I find fascinating. I suspect JS's innate event response style doesn't match well with timed/paced messaging like a serial port
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
I think Venus OS will have the serial port open. There’s a way to make it ignore that serial port, but I don’t recall how to do that off the top of my head…
I did, but not after I got the wiring sorted out correctly, then it was fine
Now I swapped my GPS for a AIS box that emits GPS and I have to sort out message translation all over 🙂
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
Dumb question, because I had to ask myself too: is it a spurious error - that is, is there an actual problem, or is it just throwing the error without actually impacting your experience? I suspect (haven't confirmed) there's a timing issue and errors are being thrown when there isn't a real problem, just a timing or sync issue...