Should we define enum types
There are a number of cases where there are enum types which are transmitted as integers but have protocol defined meanings (e.g. open vs closed loop control, trigger selection, etc)
These are sometimes reused, sometimes specific to an individual message (sometimes used for multiple fields within a single message)
for now, I have been ignoring them to get things in quickly.
My proposal is to introduce another file for these enums as an optional, readable way of specifying these values (and leave the flexibility provided by just using int for the functions, the enums would have int mixed in)
Does anyone have any thoughts on this?