TIME40 dtype doesn't take up the proper number of bytes #81
Assignees
Comments
MJJoyce
added a commit
that referenced
this issue
Jun 6, 2018
Update Time40 byte/bit counts to properly reflect the dtype's size. Because it's based off a MSB_U32 primitive type. This was causing issues with the expected length of packets that used Time40 given the 4 byte length of a MSB_U32.
MJJoyce
added a commit
that referenced
this issue
Jun 19, 2018
Update Time40 byte/bit counts to properly reflect the dtype's size. Because it's based off a MSB_U32 primitive type. This was causing issues with the expected length of packets that used Time40 given the 4 byte length of a MSB_U32.
MJJoyce
added a commit
that referenced
this issue
Sep 4, 2019
Update Time40 byte/bit counts to properly reflect the dtype's size. Because it's based off a MSB_U32 primitive type. This was causing issues with the expected length of packets that used Time40 given the 4 byte length of a MSB_U32.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The TIME40 type definition is based around a
MSB_U32primitive type. As such, the size of TIME40 is set as 4 bytes / 32 bits instead of proper size of 5 bytes / 40 bits.The text was updated successfully, but these errors were encountered: