We used ADS1242 in our thermocouple measuring device.
SETUP=0x03; MUX=0x01; ACR=0x16; other registers in default state.
f osc = 2.4576 MHz
As you see, we don't use ^DRDY pin. Therefore we couldn't syncronize data readings with ^DRDY falling edges.
How could we start an ADC conversion to predict the moment of conversion finishing?
We tryed to do this in the following way:
1. Send DSYNC command.
2. Send RDATA command, read incorrect data.
3. Wait 280 ms.
4. Send RDATA command, read valid data.
We faced the following problem: After items (1) and (2), first ^DRDY falling edge comes after 133.3 ms instead of expected 266.6 ms.
Have you been able to verify that the SETUP, MUX and ACR registers are set to the correct values using the RREG command? After your configuration sequence, if you simply let the ADS1242 free run, what rate do you see the DRDY signal coming out at?
Sending RDATA after DSYNC should not upset the modulator timing - did you have the 4*tosc period delay between 1 and 2 above (see page 6 of the datasheet)?
Yes, i have. SETUP, MUX and ACR is correct.
I did the following:
1. RESET command
2. write SETUP=0x03, MUX=0x10, ACR=0x16, all other regs are in default.
3. DSYNC command
4. RDATA command, they read previous result and don't use it.
5. 720ms delay
6. RDATA command to read real result
7. Then go to point 3.
And they see next picture on oscilloscope
A - /DRDY signal
B - SCLK signal
t_1 = 133.3 ms ( 7.5Hz)
t_2 = 266.6 ms ( 3.75Hz)
(1) - exchange with ADC (see p.4 & 5 (DSYNC É RDATA)
(2) - exchange with ADC (see p.6 (RDATA) to get valid data.
The question is: If DSYNC starts new conversion, why t_1 is 133ms, not 266?
Are you working with Alexander on this? One of my associates is working this very same issue at the moment and we hope to have resolution shortly.
Yes, i working with Alexander from Saint-Petersburg departament. He suggested to take the second DRDY after first data. It is not solution for us.
I've mentioned this to Alexander already, and I think you have the information already, but I'm posting this here to be complete.
I've assembled this circuit using an EVM and tested out the results and it looks like the early /DRDY pulse is occurring in this case.
In the default case, the part runs at 15Hz, with a data period of 66.6ms. After the DSYNC command, the next falling edge of the /DRDY line occurs correctly at 66.6ms.
In the other data rates however, the /DRDY comes in exactly half the time as expected. In the 7.5Hz mode (or 133.3ms data period) and 3.75Hz mode (266.6ms data period), the first falling edge of /DRDY comes in exaclty hald the time (in 66.6ms and 133.3ms respectively).
However, once past this first data read, the data rate resumes at the programmed value.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.