Where is this copied from? Is there any reason that you didn't copy the text directly, so it could be searchable in the future? Not to mention, easier to read. Not a big deal; I was just curious.
1. No, you cannot communicate with ADIS16209, during any of these operations.
2. No, you do not need a factory reset, prior to using the auto-null function.
3. The settling time is equal to the total number of taps in the filter, divided by the sample rate. When AVG_CNT is equal to 0x0008, the total number of taps is equal to 2^8, or 256. When SMPL_PRD is equal to 0x0014 (factory-default),. the sample time is ~200SPS. 256, divided by 200, is ~1.28 seconds. I believe that we also included the turn-on time in the ~1.46 number.
I hope that helps!
Sorry about the screenshot - below contains the original text (hopefully this will make things searchable)
Regarding 1 - So there really is no indication that the long operation functions are complete. I should set up my code to wait the appropriate time (from the spec sheet) before trying to communicate with the part via spi. Agreed?
Regarding 3 - I didn't account for the turn on time - thank you!
Original Request / Question
1 - Can I talk to chip (16209) via SPI
during power on reset?
during software induced reset?
during save regs to flash?
during auto null?
what's the indication (from software / SPI perspective) that these functions are complete?
is it simply waiting the times in the data sheet?
can we continue to use the device while waiting for the functions that take a long time to complete ?
2 - does a factory calibration restore need to be performed before doing a auto null function
3 - What does this mean (from the 16209 data sheet)?
Note that for the default SENS_AVG and AVG_CNT settings, the typical settling time will be ~1.46 seconds.
is there a formula for this settling time?Thank You - Dale
The data-ready provides an indicator of "normal" operations. Use MSC_CTRL[2:0] to configure one of the two DIOx lines as a data-ready indicator. You can also set a delay to wait for the ADIS16209 to complete this function, using the functional times in the datasheet as well. They are listed as "typical" but in general, are pretty conservative.
Retrieving data ...