https://e2e.ti.com/support/data-converters-group/data-converters/<p style="display:none;">blank</p>en-USTelligent Community 13https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1650665/ads1115-incorrect-readings-on-ads1115-connected-to-vdd-and-gnd/6367487Tue, 02 Jun 2026 14:19:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:61505b9d-c93c-4ffa-badc-f437efae8859Joachim WuerkerHello Giannina, thanks a lot for all those details. This looks all good. Are you converting the binary twos-complement numbers correctly to decimal numbers? Do you see the same issue on multiple boards? Or have you tried replacing one misbehaving unit with a known good unit just so we can exclude any device damage? Regards, Joachim Wuerkerhttps://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1650665/ads1115-incorrect-readings-on-ads1115-connected-to-vdd-and-gnd/6367404Tue, 02 Jun 2026 13:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:1904a82f-4432-4150-b6a1-7efeee5460eeGiannina MarreroThank you for your response. Regarding your questions, all four ADS1115 devices are configured with exactly the same register settings and firmware. The only difference between them is the I2C address defined by the ADDR pin, according to the datasheet: ADDR = GND → 0x48 ADDR = VDD → 0x49 ADDR = SDA → 0x4A ADDR = SCL → 0x4B The configuration written to the CONFIG register (0x01) is always the same for all four devices: Config = 0xC183 Bit breakdown according to the datasheet: Bit 15 (OS) = 1 → starts a single-shot conversion. Bits 14:12 (MUX = 100) → AIN0 referenced to GND. Bits 11:9 (PGA = 000) → input range &#177;6.144 V. Bit 8 (MODE = 1) → single-shot mode. Bits 7:5 (DR = 100) → 128 SPS. Bits 4:0 → comparator disabled. After writing this configuration, I wait 10 ms and then read the CONVERSION register (0x00). The ADC code is converted to voltage using the LSB value corresponding to the &#177;6.144 V full-scale range: voltage = raw * 0.0001875 where 0.1875 mV/LSB is the value specified in the datasheet for PGA = &#177;6.144 V. I simply wait 10 ms before reading the conversion result. Thank you for your help.https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1651484/ads1220-excel-calc-pspice-simulation-files-for-ads127l01Tue, 02 Jun 2026 13:13:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:1f6d1e6f-309b-4d8b-bb4f-da3c70887c45Camille FaivrePart Number: ADS1220-EXCEL-CALC Other Parts Discussed in Thread: ADS1158 , ADS127L11 Hello I am looking for TINA spice or PSpice .LIB files for the ADS127L11, or ADS1158 or any of the similar ADCs which use Delta Sigma modulation. Do these files exist ..? Best regards, CamilleADS127L11ADS1158ADS127L01ADS1220-EXCEL-CALChttps://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1648944/dac39rf10-sp-package-and-screening-inquiry/6367397Tue, 02 Jun 2026 13:11:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c858e6fe-f826-4841-9486-8d4d2a210637Kyle LewisDAC39RF10-SP is an organic flip-chip (plastic) as noted in the reliability report. Please locate the PCR report for QCI test conditions, samples sizes, etc: https://www.ti.com/ordering-resources/faqs/high-reliability-products/product-conformance-reports.htmlhttps://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1651463/adc12qj1600-enabling-sample-lanes-on-ti-jesd204c-ip-coreTue, 02 Jun 2026 12:03:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:56bd8020-cff5-4b42-a962-fbafbdae602dPanagiotis GkountoumisPart Number: ADC12QJ1600 Hi, are the lane samples (rx_lane_samples) outputs of the TI IP core available for the JMODE8 (64B66B, 12bit resolution, 4 lanes).? Is laso not clear form the User guide what are the TL_PARAM I set the IP core parameters like this: .RX_TL_ENABLED (&quot;YES&quot;), .TL_PARAM1 (3), .TL_PARAM2 (0), .TL_PARAM3 (2), .SAMPLES_PER_CYCLE_PER_LANE (4), .TL_TYPE (&quot;NORM&quot;) but I don&#39;t see the correct data at the output. The lane data are correct though. thank you in advance, PanosADC12QJ1600https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1642637/dac7614-required-thermal-information/6367228Tue, 02 Jun 2026 10:01:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c3d64fbd-9712-480b-9950-e8155e7e1286sharath BKHi Erin, Thanks for the mail. waiting for the confirmation. regards Sharath BKhttps://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1650235/ads1261-ads1261/6367207Tue, 02 Jun 2026 09:41:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:df9eb3cf-1c8e-4b06-bad3-deb0f65e2a18Sudharson BalrajThanks for your response Bryanhttps://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1640020/ads124s08-request-for-schematic-review-pt100-rtd-measurement-using-ads124s08/6367049Tue, 02 Jun 2026 08:03:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:95e7aeae-5638-4702-9430-4838dcdc7743Chetan Bidap1e2e.ti.com/.../PT100.pdfhttps://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1640020/ads124s08-request-for-schematic-review-pt100-rtd-measurement-using-ads124s08/6367047Tue, 02 Jun 2026 08:02:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3ee9042e-a79b-4068-96ca-2af855308243Chetan Bidap1Hello Bryan, Thank you for your help. I have implemented the changes you suggested, and the circuit is now working properly. I have now designed a new circuit for two 3-wire PT100 sensors . Could you please review it once and let me know if I have missed anything? I would also like to confirm whether it is possible to read data from both temperature sensors through the same SPI interface simultaneously. Thank you for your support.https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1651346/dac39rf10-output-fullscale-calc-full-schematics-for-trf1108-dac39rfevmTue, 02 Jun 2026 06:55:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c5b9bd2f-d8f5-46a7-9131-f6089ef806efAdrian GeigerPart Number: DAC39RF10-OUTPUT-FULLSCALE-CALC Other Parts Discussed in Thread: TRF1108-DAC39RFEVM , DAC39RF10 , DAC39RF12 Hi All Developing our own FPGA adapter for the TRF1108-DAC39RFEVM we need the full schematics or ideally even full design files of this EVM. We do have the schematics of &quot;DAC39RF10 EVM REVA&quot; which is almost the same (with differential / balun outputs), however, &quot;almost&quot; might not be good enough. Also the DAC39RF12 EVM RevC is not correct and has obvious differences to the RF10 EVM. Can you please help with this? thanks AdrianDAC39RF10-OUTPUT-FULLSCALE-CALCDAC39RF12DAC39RF10TRF1108-DAC39RFEVMhttps://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1648944/dac39rf10-sp-package-and-screening-inquiry/6366920Tue, 02 Jun 2026 06:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:dd9d1892-467f-4146-a758-057fd76ae32eishii-koHi Kyle, Could you give me the answer?https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1651083/ads114s08-ads114s08-thermocouple-error-in-lecture-readings/6366856Tue, 02 Jun 2026 05:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:19d9119e-d420-4fbb-926e-d650c4e6782djose gaaHi Dale, thanks for the answer. My configuration is exactly as you described, except for REFP_BUF = 0 (I have REFP_BUF = 1). Is it necessary to have REFP_BUF active if we&#39;re not using the external reference? These are the flag values ​​from your example code that I use to configure the register you mentioned. //Reference monitor configuration #define ADS_FLAG_REF_DISABLE 0x00 #define ADS_FLAG_REF_EN_L0 0x40 #define ADS_FLAG_REF_EN_BOTH 0x80 #define ADS_FLAG_REF_EN_10M 0xC0 //Positive reference buffer bypass #define ADS_REFP_BYP_DISABLE 0x20 #define ADS_REFP_BYP_ENABLE 0x00 //Negative reference buffer bypass #define ADS_REFN_BYP_DISABLE 0x10 #define ADS_REFN_BYP_ENABLE 0x00 //reference input selection #define ADS_REFSEL_P0 0x00 #define ADS_REFSEL_P1 0x04 #define ADS_REFSEL_INT 0x08 //internal ref #define ADS_REFINT_OFF 0x00 #define ADS_REFINT_ON_PDWN 0x01 #define ADS_REFINT_ON_ALWAYS 0x02 As an indication, the bias appears to be configured correctly because I measure 2.5V between the negative input and ground of the ADC. You mentioned removing R50; would that be necessary in the final design or just for testing? The idea is to be able to measure RTDs and thermocouples on the same PCB without different configurations. If AN3 isn&#39;t configured at all, how could that affect the bias? I&#39;ve performed tests applying voltage to the input instead of having the thermocouple connected, and I&#39;ve obtained correct readings, which is strange. Could it be a gain issue? In your example code, the gain was set to 2, which seemed odd to me since the thermocouple voltages are very small, and there&#39;s room to increase the gain. Thanks.https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1651312/ads8688-review-of-ads8688-and-mspm0g3507-q1-for-12v-lead-acid-battery-block-cmu-designTue, 02 Jun 2026 05:09:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:999a96d1-aaa3-4515-b017-24ca71f4b4f2Jihae EomPart Number: ADS8688 Other Parts Discussed in Thread: MSPM0G3507-Q1 Hello TI Team, My name is Deukkeun Jung, CEO of TwinRISLab Inc. We are currently developing a BMS for lead-acid battery-based UPS and rectifier systems. We are reviewing TI devices for a CMU design that monitors 12V lead-acid battery blocks. The battery configurations under review are as follows: • 12V lead-acid battery blocks: 4 / 9 / 16 / 20 / 30 / 32 / 40 blocks • For 32-block and 40-block systems, a neutral point exists in the battery string. The current CMU architecture we are considering for 12V block monitoring is as follows: • 4 &#215; 12V lead-acid battery blocks → voltage divider / input filter / protection circuit → ADS8688 → SPI → MSPM0G3507-Q1 → isolated CAN or isolated RS-485 → BMU MCU For a 40-block 12V battery system, we are considering using 10 CMU boards, where each CMU monitors 4 battery blocks. We would appreciate your review and recommendations on the following points. 1. Suitability of ADS8688 for 12V lead-acid battery block voltage measurement Is ADS8688 suitable as an ADC for measuring the voltage of 12V lead-acid battery blocks? The voltage of each 12V lead-acid battery block may vary depending on operating conditions, approximately from below 10V to around 15V. Therefore, we are considering using a voltage divider circuit to scale the battery voltage into the ADS8688 input range. 2. Recommended input circuit for 12V battery voltage measurement If ADS8688 is suitable, could you recommend a proper input circuit structure for this application? Specifically, we would like guidance on: • Recommended voltage divider configuration • Input RC filter design • Input protection circuit • Protection against transient voltage, reverse connection, or abnormal battery conditions • Any layout precautions for accurate battery voltage measurement 3. Temperature measurement using ADS8688 We are also considering measuring battery temperature using NTC thermistors or temperature sensor outputs. Is it appropriate to use some ADS8688 channels for battery temperature measurement together with voltage measurement? If so, are there any recommended circuit examples for NTC or analog temperature sensor input to ADS8688? 4. Alternative TI ADC or AFE recommendation For monitoring multiple 12V lead-acid battery blocks, is there any TI ADC or AFE device that would be more suitable than ADS8688? We are especially interested in devices suitable for: • 12V battery block voltage monitoring • UPS / rectifier battery systems • Isolated CMU-based architecture • Multi-board battery monitoring systems 5. Suitability of MSPM0G3507-Q1 as local CMU MCU We are considering MSPM0G3507-Q1 as the local MCU on each 12V CMU board. The MCU would handle: • SPI communication with ADS8688 • Measurement data processing • CMU board ID management • Local diagnostics • Communication control • Isolated CAN or isolated RS-485 communication with the BMU Would MSPM0G3507-Q1 be a suitable MCU for this CMU role? If there is a more recommended TI MCU for this type of CMU design, please let us know. 6. Isolation and neutral point considerations In 32-block and 40-block battery systems, a neutral point exists in the battery string. Are there any special design considerations for: • CMU isolation structure • Measurement reference point • Communication isolation • System grounding • Safety and diagnostic design when monitoring multiple 12V battery blocks through several CMU boards? If possible, please also provide or guide us to the following resources: • ADS8688 datasheet, application notes, and reference schematics • Recommended input circuit examples for 12V battery voltage measurement • ADS8688 EVM part number and purchase information • ADS8688 sample code or firmware examples • MSPM0G3507-Q1 development board and example code • TI recommended BMS architecture documents for lead-acid batteries, UPS, rectifiers, or ESS applications After reviewing the above system concept, we would appreciate your advice on the most suitable TI device configuration and development direction for 12V lead-acid battery block monitoring. Thank you. Best regards, Deukkeun Jung CEO, TwinRISLab Inc.Energy infrastructureMSPM0G3507-Q1ADS8688https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1649689/amc7908-amc7904-dac-output-current-mode-select/6366830Tue, 02 Jun 2026 05:01:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:61bad5ea-6d29-4c28-a632-0df4926799eeMuhammed MufeedHi Erin, Could you please clarify when the DAC1 pin is being shorted to ground—before powering up the device or after power is applied? Based on our observations, this condition appears during power-on, likely because the power amplifier is already in a faulty state. Additionally, Configuration Register 1 is not being programmed to 0x19. When the short condition is removed, the register value correctly reads back as 0x01. Regarding your comment on the VSS supply current limitation, could you help elaborate on your concern? Currently, the VSS supply is limited to a maximum of 200 mA and is shared across four negative DAC devices. As a test, could you try reducing the current limit to below 50 mA and repeat the experiment? This may help us better understand the impact of the VSS supply behaviour under these conditions. Regards, Mufeedhttps://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1651278/tsc2007-a-system-with-a-long-touch-cable-analog-line-overshoot/6366712Tue, 02 Jun 2026 02:49:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:eb9c8bcb-5c8f-4224-974d-171ac5663f14kz_skCurrently, touch input is working without any problems. The first sampled value after touch is often abnormal, so we discard the first two sampled data points and use the third and subsequent values. In this case, touch input works without any problems. Currently, the sampling period is approximately 10ms, and the sampling time per sample is about 2-2.5ms. I am concerned about whether this overshoot will cause problems in the long term. If TI sees it as a problem, we will consider countermeasures.https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1651278/tsc2007-a-system-with-a-long-touch-cable-analog-line-overshootTue, 02 Jun 2026 02:09:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d1939f51-b292-45a6-8311-18adf3b7d643kz_skPart Number: TSC2007 The system is as follows: The ESD diode package is U-DFN2510-10, and the pattern is designed to avoid stubs. The capacitor connected in parallel is also 0603 meter, and the pattern is designed to avoid stubs. Touch Panel Resistance: X:440~1100ohm , Y:100~420ohm At the end of the X and Y axis measurements, a 4V overshoot occurs at the Y+ and X+ pins. The maximum rating is 3.4V (Vcc + 0.1V). The magnitude of the overshoot varies depending on the touch point (resistance value), and since it occurs at the end of the measurement, it is thought to be caused by the induced electromotive force of the cable inductance when the current is cut off. We understand that lengthening the analog line is not recommended. However, we would like to minimize the overshoot as much as possible in this system. Please advise on effective countermeasures using currently unimplemented components. (e.g., 10pF on X+ and Y+) Thank you for your guidance. Correspondence between each pin and the touch panel ↓ X-...XR, X+...XL, Y+...YU, Y-...YD The overshoot of the X+ pin is larger on the right side of the screen and smaller on the left side. There is no change vertically. The overshoot of the Y+ pin is larger at the bottom of the screen and smaller at the top. There is no change horizontally. In both cases, the voltage trajectory follows a slow discharge pattern after the overshoot.Appliancestsc2007https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1651243/ads124s08-ads124s08-10x-slower-settling-than-expected/6366614Tue, 02 Jun 2026 01:22:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:41c94c90-2449-4155-8f65-df2d5c1d8b81JSRHi Dale, Thanks for the prompt response. You are correct, I was looking at the application report not the datasheet; sorry about that. Thanks for the FAQ link: in it I notice that my common mode filter caps should be at least 5x smaller. Regarding your questions: 1. Checking on that... 2. There is a dedicated 1k resistor on each channel. It is wired exactly like Figure 2-9 in the application report . Regarding your suggestions: we will give those a try...https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1651263/dac60501-spi-32mhz-clockTue, 02 Jun 2026 00:35:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:87da5c86-b70a-4617-9369-432b7f2f1a7bShuji IshiwataPart Number: DAC60501 Hi All, Customers are evaluating the DAC60501. Some devices output DCOUT correctly, while others only output 0V (likely the default value). The control is SPI and the clock is 32MHz.. Changing the clock from 32MHz to 16MHz allows control of devices that previously had a 0V output. The clock&#39;s upper limit is 40MHz, so 32MHz should be fine. 7.6 Timing Requirements: I checked the timing in SPI Mode and found no problems. Are there any other possible factors? Best Regards, IshiwataDatacom moduleDAC60501https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1651243/ads124s08-ads124s08-10x-slower-settling-than-expected/6366567Tue, 02 Jun 2026 00:29:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:97d8653a-17ce-4e9f-8069-2c9e68d09121Dale LiHi JSR, ADS124S08 datasheet does not have Figure 2-9 and Figure 2-11. I believe you were looking at application report . I have some questions: What&#39;s the normalized value in y axis of your graph? What is the difference between ch0 55us and ch0 16ms in terms of configurations and tests? Did you do the test on a specified channel or you switched the channels with a 1k resistor on each channel? How did you wire them? Suggestions: Ensure that the REFP0 buffer is on and the REFN0 buffer is off (these are the default settings). You should also remove capacitor CPR and CNR from your circuit, select a small capacitor value for CDR, and replace resistor RNR with a 0 ohm resistor. Follow up the guideline to select differential input capacitor and common-mode input capacitor, your 1uF capacitor value is high, see the details about input anti-aliasing filtering from the link [FAQ] Delta-sigma ADC anti-aliasing filter component selection . BR, Dalehttps://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1647919/vsp5621-vsp5620-datasheet/6366551Tue, 02 Jun 2026 00:02:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f36b0919-40eb-467d-aa9f-47d2b9e35bb6Shuji IshiwataHi All, I have been waiting for your reply, but have not heard from you. Could you give us a response? Best Regards, Ishiwata