Quote:
Originally Posted by bdbcat
Steve...
In the "error-max" image, I assume you are referring to the Hdg value of 374 degrees (true). Bogus, for sure.
In certain cases, OCPN calculates HDT from HDM and MagVariation. This could be happening here, with some logic error. Or it could be a legitimate N2K error-max detection problem.
Can you produce a candump -L record of this situation for analysis?
Thanks
Dave
|
I doubt these are OCPN calculation errors. they are values that should not be processed further after
reception. I have no idea how or where you are using the N2KIsNA functions.
A longitude of 214 44.901 E, a
depth of 42949705 (beyond the range of recreational
depth transducers), a speed of 1273 knots (which I have never attained in any form of transport !).
For a N2K developer, they're recognisable numbers.
For example, Speed. Convert SHRT_MAX (0xFFFF, 65535) from cm/s to knots (65535 * 1.94384 * 0.01) and you get 1273.
Similarly for longitude, INT_MAX (0x7FFFFFFF, 2,147,483,647) and multiple by 1e-7 to convert to longitude as a double.
You'll find the heading becomes even more confused because the heading value will also be affected by invalid variation and deviation values.
Nonetheless for you debugging pleasure here are max value (to be interpreted as data not available)
NMEA 2000 messages.
Code:
(1664117471.702665) can0 11FD02C8#03FFFFFFFFFFFFFF
(1664117471.703664) can0 11F50BC8#01FFFFFFFFFF7FFF
(1664117471.703664) can0 11F503C8#02FFFFFFFFFFFFFF
(1664117471.704666) can0 11F802C8#04FFFFFFFFFFFFFF
(1664117471.705665) can0 11F112C8#0501FFFF7FFF7FFF
(1664117471.704666) can0 11F801C8#FFFFFF7FFFFFFF7F
You could also "hand craft" values as max value -1 (to be interpreted as error)