Thanks for bringing this to our attention.

This is a mostly cosmetic issue with the Control Panel example, and the example should continue to work as intended, despite the reported error.

That said, we have fixed the issue, pending the next release.

We have replicated the issue and are working on a fix.

There is a Code Samples tab on the MOT2002 page that allows you to select a programming language and the Hub you are connecting to, which will give you code specific to your use-case to get started.

https://www.phidgets.com/products.php?p ... de_Samples

To clear up some confusion, 96Hz is not a multiple of 8ms.

Achievable data rates for this device would be:
8ms: 125Hz
16ms: 62.5Hz
24ms: 41.667Hz
32ms: 31.25Hz
40ms: 25Hz
48ms: 20.833Hz
56ms: 17.857Hz
64ms: 15.625Hz
72ms: 13.889Hz
80ms: 12.5Hz
etc.

The 1047, like many USB Phidgets based on older designs, is forced to have a DataInterval of multiples of 8ms.

A new version of the Phidget22 LabVIEW library has been released with this issue fixed.

A fix has been made to FrequencyCounterStart.vi to call the correct DataInterval function, pending release. Thanks for pointing it out!

In the meantime, you can use the FrequencyCounterSetDataInterval.vi from the FrequencyCounter palette.

Thanks for clarifying the question! Knowing what confuses people really helps in improving documentation. I'm seeing there could be confusion between the documentation saying the device assuming it's at rest, and what that means practically. The device never fully disregards the gyroscope. Exceeding...

Please disregard the comment about V104, after more intensive testing, it is completely functional. The problems mentioned above were present in an internal, unreleased build. We revert to recommending V104 at this time. To your earlier question 2: To check if AHRS/IMU parameters are doing anything ...

For clarity, are you using the MOT0110? 1: You can find explanations for what each parameter does on the linked page here: https://www.phidgets.com/docs/Spatial_Guide#AHRS_Parameters However, that wouldn't help you much at the moment because 2: Looking into it, setting the AHRS parameters was broken...