Writing a new multiplexer (MUX) setting to the ADS1115IDGSR does not immediately put a new-channel result in the Conversion register. In continuous mode, a conversion already in progress finishes with the previous configuration. For an unambiguous single-shot check, start the selected conversion from a known idle state, confirm completion, and then read the result. Also verify the register pointer and the channel label assigned by the driver.
1 Separate the configuration write from the result update
The ADS1115 returns the latest completed conversion; the word contains no channel identifier. A scan driver must retain the MUX and scale settings belonging to each request until it completes or is rejected. Updating a variable called current channel does not change the origin of the result already in the Conversion register.
TI data sheet SBAS444E, Revision E, describes the two operating modes in Section 7.4.2. MODE equal to zero selects continuous conversion. With MODE equal to one, the device supports single-shot operation and returns to power-down after a conversion. The MODE and operational status (OS) fields have different jobs. Keep their meaning separate when interpreting a register trace.
| Item to check | What it tells you | What it does not establish |
|---|---|---|
| MUX[2:0] readback | The selected input combination in Config | Which configuration produced the available result |
| OS reads zero | A conversion is in progress | That the Conversion register already contains its result |
| OS reads one | No conversion is currently in progress | That a new request was started and completed |
| OS written as one | Starts a single conversion from the idle power-down state | A restart when a conversion is already running |
In continuous mode, writing a new configuration leaves the current conversion to finish using the old configuration. Conversions using the new settings begin afterward. Reading back the new MUX field therefore confirms a configuration write, while the result may still belong to the previous input. Record the completed conversion against the settings that actually initiated it.
This distinction matters when a scan loop changes a software channel index, writes Config and immediately calls a read function. A successful I2C transaction confirms that the transfer worked. It does not confirm that the ADC has finished acquiring the input that the new index names.
2 Acquire each channel from a known idle single-shot state
For a controlled diagnostic, begin with the device in single-shot mode and with no conversion running. Build the complete configuration for the target input, including MUX, programmable gain amplifier (PGA), MODE and data rate (DR), with OS written as one to start the conversion. Check the write operation for errors before waiting for its result. Verify MODE and MUX readback, and serialize configuration access so another task cannot change the settings during this acquisition.
Writing OS as one during an ongoing conversion has no effect. Repeating the start write is therefore a poor substitute for tracking whether the previous request has finished. Keep one conversion request outstanding during this test. Store its input combination and scale settings in a request record that remains valid until completion or a reported failure.
Poll OS in the Config register, or use a correctly configured conversion-ready output, to confirm completion of the requested conversion. Account for the wake-up and start sequence when interpreting early status reads: an idle indication before the requested conversion starts is not its completion. Keep the accepted start request and its later completion evidence together. This does not require every polling host to observe OS equal to zero; a conversion may finish before a later poll.
If the write fails, a status read fails, or the wait expires, mark that request as having no valid sample. Preserve the error with its channel and sequence number. Passing the previous buffered result to the next channel can turn a communication or timing fault into a plausible but incorrectly labeled voltage.
Section 7.3.6 states that the ADC settles within one conversion cycle. Once a conversion using the new settings has completed, its first result does not require a universal extra discard. External source impedance, filters and changing input signals still need their own assessment. If the driver uses a fixed delay, check it against the selected data rate and applicable variation, rather than copying a delay from another application.
3 Trace the register pointer and compare known inputs
To poll Config, first select register address 01h. Before retrieving the conversion result, select address 00h for Conversion. Sections 7.5.3 and 8.1.1 describe the retained register pointer. A raw read after a Config poll can retrieve the configuration word if the driver has not selected the result register again.
Read the two result bytes most significant byte first, and retain them before applying voltage scaling. Compare the raw word with the selected PGA range and input combination. A value that tracks your configuration settings deserves a pointer check before you interpret it as an analog fault.
Coordinate each pointer selection and its following read for the same ADC. Another task can otherwise select a different register between those operations, even without changing MUX. This coordination need not reserve the entire I2C bus while conversion runs; the shared ADC configuration, pointer sequence and result ownership must remain consistent.
| Observed behavior | Record to inspect next |
|---|---|
| First value resembles the old input, later values look right | Operating mode, MUX write time and conversion-completion events |
| Two channels always report the same value | Actual MUX readback, input connections and software buffer ownership |
| The apparent voltage follows configuration changes | Register pointer before the read and the two raw bytes |
| The start or polling operation reports an error | Transaction result, timeout flag and sample-valid status |
Use a test board with two distinct, stable input levels that meet the device input conditions. First collect repeat readings from one fixed channel. Then alternate the two inputs using the same acquisition sequence. Keep a timestamped trace of the request, Config write, completion indication and data read so that each reported voltage can be followed back to its request.
Check the analog input limits separately if the test sources are in doubt. A timing correction cannot make an out-of-range input suitable for the ADC. Verify the actual wiring, ground connections and selected input pair before interpreting differences between channels.
4 Carry the acquisition conditions into the BOM and acceptance record
Save the full device code, board revision, firmware build, input combinations, PGA setting, data rate, operating mode and completion method. Include the raw words and the scaled values. Repeat the controlled channel test after a change so the acceptance record describes the firmware and hardware combination that was actually checked.
Separate the IC requirements from the behavior of the assembled acquisition board. A module can add filters, connections and scan software that the IC ordering code does not specify. When comparing boards, identify which input circuit and firmware behavior your application depends on.
Use the Texas Instruments parts listing to locate the catalog component, then verify the complete ordering code and package against manufacturer information. Define the expected channel sequence, valid-result criteria and covered board version in the acceptance record. A successful I2C transaction alone does not establish a correctly identified sample.
If the application requires simultaneous samples rather than sequential channel readings, evaluate a different acquisition architecture. The AD7606BSTZ is a separate simultaneous-sampling candidate, not a drop-in replacement for ADS1115IDGSR. Its input stage, interface, supply requirements and board design must be assessed for the project. Increasing the I2C clock or adjusting a delay does not turn a multiplexed scan into simultaneous sampling.
For an ADS1115IDGSR request, list the input combinations, scan mode, board revision and quantity you need. Keep the complete ordering code, package requirement and acquisition verification record together when reviewing candidate ICs. Send SUNTEC the full part number, quantity and target delivery date, with the channel-scanning conditions for the component inquiry.
Prepared by the SUNTEC Technical Team at Suzhou SUNTEC Electronics Co., Ltd.