(2020-12-09, 09:28 PM)PaddyB Wrote:(2020-12-09, 09:01 PM)Pyxis Wrote: I'm slowly starting to understand! lol
So the Signal K server will try to decode nmea connections into Signal K format but even if it can not it will still push this data out to port 10110!
I scanned port 10110 in raw format and can see this;
!AIVDM,2,1,8,A,53P7AsD2<Iu=a4u7:21<B0tl4LR22222222222150pD2574g061PDk0C,0*3D
!AIVDM,1,1,,B,13MARih000wbAbJP0kr23aSV0<0g,0*73
!AIVDM,1,1,,B,13P>Hq0000wbF:RP0jR5dkOF0hHr,0*42
Which is AIS data so I'm guessing the Signal K can not decode this into a json format
Cheers
Paul
Yep, you've got it! Now annoyingly a few weeks ago I got into the ais data and with some node red saved the distance to the target into an influxdb database. But not a clue now how I did it! Think was to check if any antenna tweaks were helping to pick up more distant targets. No idea how I did it though. Must take a few notes in future......
Aha, knew it was there somewhere - have you used node-red yet? If you know what a json is then should be easy enough, there's an ais dedcode node - https://flows.nodered.org/node/node-red-...is-decoder
So if you input an AIS message you get this on the output =>
{"mmsi":227006760,"navigationStatus":"Under way using engine","rateOfTurn":128,"speedOverGround":0,"longitude":0.13138,"latitude":49.47557666666667,"courseOverGround":36.7,"trueHeading":511,"timeStampSeconds":14,"date":1607546243406,"isoDate":"2020-12-09 20:37:23","source":"!AIVDM,1,1,,A,13HOI:0P0000VOHLCnHQKwvL05Ip,0*23"}
Thanks for the pointers... I'm still not seeing any data in node-red. I'll probably need to work on it a bit more.
I copied the nmea data that I pulled from port 10110 and ran it through the data fiddler. The fiddler decoded it correctly into json and I was also able to push the send to server button... but unfortunately, I still can't see the data in the signalk data browser or node-red. Even though I have gauges and text boxes working ok for the GPS data and temperature sensors... All very strange! lol