Skip to content

Commit

Permalink
Added ieee754-f32 field to CANPoint spec in cangen/README
Browse files Browse the repository at this point in the history
  • Loading branch information
harrison-e committed Dec 6, 2024
1 parent 6427e59 commit 351019e
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions cangen/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,7 @@ Within the `points` member of a NetField object, there is a list of Point object
- `endianness` (optional), string representing the byte endianness of the bits being read, either `"big"` or `"little"` (`"big"` by default)
- `format` (optional, not recommended), string representing the final type of the data (`"f32"` by default)
- `default_value` (optional, only for Encodable Messages), float representing the default value to be sent before a command is received or when an empty command is received. This is ignored when decoding the Point (`0` by default)
- `ieee754_f32` (optional), boolean indicating if the bits in the Point should be interpreted as an IEEE754 32-bit float (`false` by default)

#### Sim
Within the `sim` member of a NetField object, there is a single sim object. This object is one of two types, either `sweep` or `enum`. However these types are implied, not written in the JSON, just use them correctly!
Expand Down

0 comments on commit 351019e

Please sign in to comment.