ZHCSDM9A December 2014 – March 2018 LDC1612 , LDC1614
PRODUCTION DATA.
- 1 特性
- 2 應(yīng)用
- 3 說明
- 4 修訂歷史記錄
- 5 Pin Configuration and Functions
- 6 Specifications
-
7 Detailed Description
- 7.1 Overview
- 7.2 Functional Block Diagram
- 7.3 Feature Description
- 7.4 Device Functional Modes
- 7.5 Programming
- 7.6
Register Maps
- 7.6.1 Register List
- 7.6.2 Address 0x00, DATA0_MSB
- 7.6.3 Address 0x01, DATA0_LSB
- 7.6.4 Address 0x02, DATA1_MSB
- 7.6.5 Address 0x03, DATA1_LSB
- 7.6.6 Address 0x04, DATA2_MSB (LDC1614 only)
- 7.6.7 Address 0x05, DATA2_LSB (LDC1614 only)
- 7.6.8 Address 0x06, DATA3_MSB (LDC1614 only)
- 7.6.9 Address 0x07, DATA3_LSB (LDC1614 only)
- 7.6.10 Address 0x08, RCOUNT0
- 7.6.11 Address 0x09, RCOUNT1
- 7.6.12 Address 0x0A, RCOUNT2 (LDC1614 only)
- 7.6.13 Address 0x0B, RCOUNT3 (LDC1614 only)
- 7.6.14 Address 0x0C, OFFSET0
- 7.6.15 Address 0x0D, OFFSET1
- 7.6.16 Address 0x0E, OFFSET2 (LDC1614 only)
- 7.6.17 Address 0x0F, OFFSET3 (LDC1614 only)
- 7.6.18 Address 0x10, SETTLECOUNT0
- 7.6.19 Address 0x11, SETTLECOUNT1
- 7.6.20 Address 0x12, SETTLECOUNT2 (LDC1614 only)
- 7.6.21 Address 0x13, SETTLECOUNT3 (LDC1614 only)
- 7.6.22 Address 0x14, CLOCK_DIVIDERS0
- 7.6.23 Address 0x15, CLOCK_DIVIDERS1
- 7.6.24 Address 0x16, CLOCK_DIVIDERS2 (LDC1614 only)
- 7.6.25 Address 0x17, CLOCK_DIVIDERS3 (LDC1614 only)
- 7.6.26 Address 0x18, STATUS
- 7.6.27 Address 0x19, ERROR_CONFIG
- 7.6.28 Address 0x1A, CONFIG
- 7.6.29 Address 0x1B, MUX_CONFIG
- 7.6.30 Address 0x1C, RESET_DEV
- 7.6.31 Address 0x1E, DRIVE_CURRENT0
- 7.6.32 Address 0x1F, DRIVE_CURRENT1
- 7.6.33 Address 0x20, DRIVE_CURRENT2 (LDC1614 only)
- 7.6.34 Address 0x21, DRIVE_CURRENT3 (LDC1614 only)
- 7.6.35 Address 0x7E, MANUFACTURER_ID
- 7.6.36 Address 0x7F, DEVICE_ID
-
8 Application and Implementation
- 8.1
Application Information
- 8.1.1 Conductive Objects in a Time-Varying EM Field
- 8.1.2 L-C Resonators
- 8.1.3 Multi-Channel and Single Channel Operation
- 8.1.4 Sensor Conversion Time
- 8.1.5 Sensor Current Drive Configuration
- 8.1.6 Clocking Architecture
- 8.1.7 Input Deglitch Filter
- 8.1.8 Device Status Registers
- 8.1.9 Multi-Channel Data Readback
- 8.2 Typical Application
- 8.1
Application Information
- 9 Power Supply Recommendations
- 10Layout
- 11器件和文檔支持
- 12機械、封裝和可訂購信息
封裝選項
機械數(shù)據(jù) (封裝 | 引腳)
- RGH|16
散熱焊盤機械數(shù)據(jù) (封裝 | 引腳)
- RGH|16
訂購信息
8.1.9 Multi-Channel Data Readback
When in multi-channel mode, the LDC1612/LDC1614 alternates conversions on all selected channels. After each channel conversion completes, the conversion results for that channel overwrites the previous conversion results with the new data. Note that the LDC1612/LDC1614 conversion data spans 2 registers. To avoid multi-conversion data corruption, the conversion results are stored in an internal buffer after every conversion, but the I2C DATAx field is only updated to reflect new data when the DATAx_MSB register is read.
When the device completes a conversion on the last channel in the selected group, the device will pull INTB low if DRDY2INT is set to 1. At this time, the conversion results should be retrieved via the I2C bus.
If the device is put into Sleep mode or Shutdown mode, all DATAx_MSB and DATAx_LSB registers are cleared of conversion data.
Figure 58. Data Readback Timing
The STATUS register (Address 0x18) flags UNREADCONVx monitor the accesses to the DATAx registers.
When the DATAx_MSB register is read, the DATAx_LSB register is updated with the corresponding LSB conversion data, and the UNREADCONVx flag is cleared. If the DATAx_LSB register alone is read, it will not update and will continuously return data corresponding to the last DATAx_MSB register read.
As shown in Figure 58 , if the I2C data readback is delayed, then it is possible to lose older, unread conversion results. Monitoring the UNREADCONVx flags are useful to assess whether data loss is occurring.
A delayed read of previous conversion results can produce the condition in which reading the STATUS register immediately after INTB asserts shows that Channel 0 has no unread data (where the UNREADCONV0 flag is 0), but other channels do have unread data indicated by the corresponding UNREADCONVx flags.