Inertial Data Register Naming: 16-bit vs 32-bit reads

[NevadaMark]

In the product datasheets, such as the ADIS16497, the *_LOW registers represent the lower 16bits of the inertial data, while in the software, they seem to represent the entire 32-bit number. Personally, I like the way that this works, but I am wondering if this could create confusion, in some customers. I really like the idea of representing the full 32-bit number, in the data log, but am wondering if we should consider including 16-bit or 32-bit naming in what the customers will selection.

Should we consider some form of notification, when customers select the _LOW, to let them know what they can expect? Or, should we consider listing 16-bit or 32-bit with these selections?

[ajn96]

It would not be too cumbersome to add a second column to the register display which shows the bit width of the register.