Closed xela144 closed 10 years ago
Some of the N2K messages have body size that does not end on a byte boundary. Should we just assume that it does end on the next largest byte? Example with a 3-bit lookup table that makes message length 43 bits. Should we assume this message size is 48/8 = 6 bytes.
PGN: 130306 - Wind Data
Field #1: SID Bits: 8 Field #2: Wind Speed Bits: 16 Field #3: Wind Angle Bits: 16 Field #4: Reference Bits: 3 Type: Lookup table Signed: false Lookup: 0=True (referenced to North) Lookup: 1=Magnetic Lookup: 2=Apparent Lookup: 3=True (boat referenced)
For parsing messages, it does not matter if the all the bits are accounted for in the body string.
On the other hand, for encoding messages, offsets should be accounted for and all blank spots on the body array string be filled in with "don't cares", or 1's.
This was done a few weeks back. 8a57b91
For example PGN127245 for commanding the rudder angle.