Platform: Artemis
Measurement period is extreme: 10Hz with nav rate of 5Hz (update rate of 2Hz). Problem also shows itself with Example6_OutputRate (nav freq set to 10Hz).
Module will say bytes are available but will present 0xFFs towards the end of the frame.
In this example, 0x64 bytes are 'available':
But part of the way through the byte harvesting, we start getting 0xFFs:
And then our CRC is corrupt. This error occurs ~3 times per 10 seconds.
Often the frame will include 0xFFs in between what looks to be valid data:
It seems as though the module is busy updating other ports (serial, SPI, etc) and is not serving up bytes to I2C buffer.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4
