Troubleshooting F2-08AD-1 Analog Values That Stop Updating

When F2-08AD-1 raw values stay fixed—even after editing them in the data table—the first fault to check is whether the PLC recognizes the module, not whether the replacement card is defective. On the D2-250 installation described here, the I/O configuration showed slot 1 empty; powering down the rack, reseating the card, and powering back up restored operation.

Stop replacing cards when the raw values do not refresh

A live analog input normally causes the PLC’s analog data locations to be updated as the module and CPU exchange data. If an operator can write a test value into those locations and it remains unchanged, the expected update is not reaching that memory location. That points first toward the I/O configuration, card-to-rack connection, or ladder logic that transfers the data—not automatically toward a failed analog input circuit.

Clearing Scratch memory and switching from Run to Program and back to Run did not resolve this installation. Replacing the analog card also did not resolve it. These actions do not prove that the CPU has recognized the module or that the analog transfer logic is executing.

Check before continuing: Confirm that a test write to the raw data location is not being overwritten, and note whether the value remains fixed. Do not use repeated memory edits as a repair; they are only a clue that the normal update path is absent.

Confirm the D2-250 recognizes the F2-08AD-1

Use DirectSoft’s PLC I/O configuration view to inspect the slot containing the analog card. For the reported installation, the card was in slot 1. The expected description was “8 Channel A/D.” An empty slot is a recognition fault: the CPU is not seeing the module in the configured rack position, so changing a ladder special relay cannot restore analog updates.

1. Open the PLC I/O configuration in DirectSoft.
2. Inspect the slot occupied by the F2-08AD-1 and record whether it is identified as “8 Channel A/D” or shown as empty.
3. If the slot is empty, stop ladder edits and proceed to the rack connection check.

Do not infer recognition from the card’s physical presence or from the fact that it worked previously. A module can be installed yet absent from the CPU’s current I/O configuration. The configuration result determines whether to prioritize the physical connection or the program’s data-transfer path.

Check before continuing: The slot display identifies the analog module as “8 Channel A/D.” If it remains empty after a controlled reseat and restart, stop and escalate rather than repeatedly replacing cards.

Reseat the module only after a controlled rack shutdown

When the slot reads empty, a physical connection problem becomes the first corrective action. In this case, the operator powered down the rack, removed the card, plugged it back in, and powered the rack up; the system then ran without the analog-value problem.

1. Put the controlled process into its approved safe state and follow the site’s electrical isolation procedure.
2. Power down the rack before removing or inserting the module. Do not reseat a live module unless the equipment documentation explicitly permits it.
3. Remove the F2-08AD-1, inspect the module and slot for an obvious obstruction or damage, and reinstall it fully in the intended slot.
4. Restore rack power and re-open the I/O configuration in DirectSoft.

This is a temporary restore if the connection fault recurs; do not treat repeated reseating as a permanent repair. Check that the card is firmly installed and that the slot stays recognized through a normal operating cycle. If recognition drops again, investigate the rack, slot, module connection, and installation conditions with the equipment documentation and official support.

Check before continuing: The module remains identified in the correct slot after power-up. If the slot still reads empty, do not proceed by changing analog scaling or manually forcing data values.

Check the transfer method after the module appears

Recognition and data transfer are separate checks. The analog module must be visible to the CPU, and the PLC program must then retrieve or move its data into the intended V-memory locations. The installation used a pointer-method rung. A separate multiplexing method is another way to read analog values; follow the method actually implemented in the program rather than adding a second method blindly.

• Pointer method: Check that the program contains the pointer configuration rung and that the setup executes when required, such as at PLC power-up or when the PLC transitions from Program to Run.
• Multiplexing method: If the program does not use pointer configuration, inspect the ladder logic that selects and reads the analog data through the multiplexing method.

Use the existing program and the module/CPU documentation to determine which method applies, the configured data locations, and the channel mapping. Do not guess V-memory addresses or add a transfer rung based only on the symptom. A missing or nonexecuting rung can leave the expected data location stale even when I/O configuration recognizes the card.

Check before continuing: Online monitoring shows the applicable setup/read logic executing and the documented analog data locations changing as inputs change. If the rung never executes, resolve its conditions and startup behavior before evaluating signal scaling.

Treat SP0 and SP1 as a logic check, not the first fix

The existing pointer rung used SP1 rather than SP0. Changing it to SP0 did not correct the fault in this installation. The configuration suggestion was that SP0 can be used because the card setup only needs to occur once, unless other logic has written to the setup registers. That makes the special-relay choice relevant to setup behavior, but it was not the cause of this particular stale-value symptom.

Review the setup rung and any other logic that writes setup registers. Confirm the intended one-time initialization behavior from the program and applicable documentation. Avoid repeatedly changing SP0/SP1 as a substitute for checking whether the CPU recognizes the card. In the reported case, the empty slot indication explained why the SP0 change alone had no effect.

Check before continuing: After any setup-logic change, verify that the rung executes at the intended startup or mode transition and that the card remains recognized. If another rung can overwrite setup registers, resolve that interaction before concluding the configuration is stable.

Separate backplane communication faults from analog-circuit faults

Stale, manually editable V-memory values point toward a missing update path. One diagnostic distinction is whether the module communicates across the backplane at all. If the slot is empty in I/O configuration, resolve recognition and seating first. If the slot is recognized and the transfer logic executes, then move downstream to the input channel, field wiring, and signal source.

The installation troubleshooting noted that a failed analog circuit might be expected to write 0 or 8000 to the analog data locations, whereas unoverwritten data raised concern that the F2-08AD-1 had stopped communicating across the backplane. Treat those values as a diagnostic clue from this case, not as a universal pass/fail test for every channel or configuration. The key question is whether the module is recognized and whether updates arrive in the documented location.

1. Confirm the I/O slot identifies the module.
2. Confirm the program’s transfer logic is running.
3. Apply a known, safe input condition and compare the raw value with the expected channel response using the project’s documented mapping.
4. If data updates but is electrically implausible, measure the signal at the module input and inspect field wiring and channel assignment before changing scaling.

Check before continuing: With an input condition changed safely, the expected raw location updates. If it does not, return to recognition and transfer diagnostics; if it does, troubleshoot the analog signal path rather than replacing the CPU or repeatedly reseating the card.

Verify the complete recovery before returning the process

Close the job only after the module remains visible, the program reads its analog data, and the values respond to actual inputs. A mode change by itself is not proof of a repair. The correction in this installation followed the recognition check: slot 1 had appeared empty, and reseating the module during a rack power-down restored operation.

1. Confirm DirectSoft continues to show “8 Channel A/D” in the intended slot.
2. Monitor the documented raw data location and verify it changes from the manually entered test value.
3. Apply or observe a known safe input change and confirm the correct channel’s raw value responds in the expected direction.
4. Verify the value remains live through normal operation and an approved return to Run mode.
5. Record the slot recognition result, the connection work performed, and whether the fault recurs.

Stop if the slot remains empty after reseating, if recognition drops again, or if the raw value still does not update with the module recognized and the transfer rung executing. At that point, gather the CPU/module identification, slot configuration, program transfer method, and observed raw-value behavior, then contact official AutomationDirect support for equipment-specific diagnosis.

Frequently asked questions