![]() ![]() So now the Raymarine ST60 data is visible on his B&G Zeus 9″ Chart plotter. * proprietary PDU2 (non addressed) single-frame range 0xFF00 to 0xFFFF (65280 - 65535) */Ħ5340, /* NOTE 65341 in pgn.Here you see his SeaTalk bus is connected through the Quark-elec A034 to his N2K backbone (The A034 itself is powered by the N2B backbone, so no additional wiring needed here). ![]() I think that the best way to interpret “Data Valid” and avoid problems is to ignore GNSS integrity, and use the own indications of NMEA0183: GNS sentence on NMEA0183 has the same “GNSSMethod” information as PGN 129029, so there's no problem. But it is also possible that GNSS integrity is always at 0. My concern has been to find an equivalence for the field “Data Valid” of these 6 sentences that I mentioned, which is the only one existing for versions of NMEA0183 prior to specification 3.0, and I thought it logical to think that a 0 in the GNSS integrity field corresponded to that “Data Valid” because I detected it together with “Position Fix” in GNS Method. It seems that this field does not have a useful translation to the sentences: GLL, RMA, RMC and the derivatives for the calculations in navigation: APB, RMB, XTE. ![]() Looking in different sources I have observed the coincidence with the documentation of Maretron, and of course, it says the same in pgn.h “GNSS integrity” starts at message bit 256, this is byte 32. I apologize, I had an error in the byte count. This information has also been verified in the files of the CanBoat project: candumpSample1.txt and candumpSample2.txt The captures were made with a logical analyzer. 9: Integrity – This field always contains a value of 0 (no integrity checking).ĭata field (from 0, byte 30, bits 0 and 1) in PGN 129029 sent from a Raymarine A-series multifunction screen. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |