Closed gauteh closed 1 year ago
We are probably doing this correctly: https://community.st.com/s/question/0D73W000000bAS4SAM/detail?fromEmail=1&s1oid=00Db0000000YtG6&s1nid=0DB0X000000DYbd&s1uid=0053W000001snzQ&s1ext=0&emkind=chatterCommentNotification&emtm=1684313246967&emvtk=E54ccDtPqWVECsAa5CCiLUY.7M7t1PbWVtlIXpFI4Uk%3D
@akkermei
You are not making any errors in your application, consider that the spread can span the +-10% range so
having 48.57 Hz instead of 52Hz is acceptable.
Ouch, +-10% is a lot of uncertainty. But if they say so... Good to keep in mind for future use :) .
There was a bug in the dataset generation where I forgot to take the offset in the FIFO into account when generating the time vector. Fixed on main. This was a post-processing bug, so by re-running dataset-exports the error is gone and the frequency is much closer to 52 Hz (and no correction is usually necessary).
I spoke too soon (again...): the variation in frequency is real, but I do not think it is an error on our part. For the buoys tested at sintef the frequencies are:
Run4: GPS estimated frequency for 23: 48.59990507831039 Hz
Run4: GPS estimated frequency for 16: 48.57685009487666 Hz
Run4: GPS estimated frequency for 25: 49.06564446574029 Hz
Run4: GPS estimated frequency for 1: 55.89519650655022 Hz
Run4: GPS estimated frequency for 2: 55.80381471389645 Hz
So within the 10%. The last two buoys are the SINTEF-built ones, with ISM330DHCX. The others are LSM6DSOX. Also they might be from the same batch.
ODR specified in the datasheet refers to typical value, so the actual ODR may differ from typical value.
You can get actual ODR of the device following equation "ODRactual" stated in section 6.4 Timestamp of both AN for LSM6DSOX and ISM330DHCX: