The address is not an undocumented physical relay. B1202.0 is bit-of-word addressing for bit 0 of memory word V1202. Find what writes or updates V1202; every change to its bit 0 changes the state seen by the normally open contact.
Stop the quick fixes that hide the writer
Do not replace an output module, force the contact, or add another coil for B1202.0. The contact is only reading a memory bit. None of those actions identifies the instruction, communication transaction, or data operation changing the parent word.
| Quick fix | Why it fails | What to do instead |
|---|---|---|
Force B1202.0
|
The force masks the symptom and may override legitimate word updates. | Remove the force and monitor both addresses. |
Search only for B1202.0
|
A writer may reference the complete word V1202, so the bit address never appears as a destination. |
Cross-reference the bit and its parent word. |
| Replace field hardware | A memory contact does not prove that a physical input, output, or relay is defective. | Trace the word back to its actual data source. |
| Rewrite the contact under a new address | This disconnects the contact from its intended source without explaining the original cycling. | Identify ownership of V1202 before changing logic. |
Get it running only through a controlled, documented temporary action. Do not leave a force or bypass in place as the permanent repair. Before moving on, confirm that no active force is controlling B1202.0 or V1202.
Decode the address before tracing the program
Chapter 5 of the D0-05 User Manual describes bit-of-word addressing used by instruction types. In this notation, V1202 is the memory word and B1202.0 selects bit 0 within that word. The normally open symbol displays the state of that selected bit; it is not a separate stored relay with an independent trigger.
When bit 0 of V1202 is 1, B1202.0 is true and the normally open contact evaluates closed. When bit 0 is 0, the contact evaluates open. Other bits in V1202 can change without changing this contact, while any operation that changes bit 0 changes it immediately when the program evaluates the contact.
This relationship also explains why an unlabeled contact can cycle even when there is no matching bit coil. The program may be loading, copying, calculating, incrementing, masking, or receiving the complete word. Confirm the interpretation by displaying V1202 in a format that exposes individual bits and checking that its bit 0 indication matches B1202.0.
Watch the word and bit together
Connect with the programming software in monitor mode and observe V1202 beside B1202.0. Keep the machine in a condition where the cycling can be reproduced safely. Record the operating step, input condition, message activity, and program location active when bit 0 changes.
- Add
V1202andB1202.0to the same watch view. - Display
V1202in a bit-oriented format if the software provides one. A decimal-only display makes the relevant bit harder to follow. - Observe whether every transition of word bit 0 produces the same transition at
B1202.0. - Check whether the transition occurs once per machine event, continuously while a condition is true, or independently of the normal sequence.
- Save the observed state and timestamp through the software’s available monitoring or capture function, if provided.
A rapidly changing display can miss scan-to-scan events because the programming display refreshes more slowly than PLC logic execution. If necessary, add a temporary diagnostic latch or counter using an approved spare address, but do not write back to V1202. Before tracing writers, prove that the contact follows bit 0 of the word rather than a display artifact or active force.
Cross-reference every path into V1202
Search the project for both B1202.0 and V1202. Classify each result as a read or a write. A contact using the address is a read; the changing value must originate at a destination instruction, an indirect destination, retained data restoration, or an external communication path.
| Path to inspect | Diagnostic question | Proof |
|---|---|---|
| Direct word write | Which instruction has V1202 as its destination? |
The instruction executes when bit 0 changes. |
| Math or data conversion | Does a computed result overwrite the complete word? | The result value and execution condition reproduce the transition. |
| Copy, table, or block operation | Does the destination range include V1202? |
Calculate the range endpoints and show that the word lies inside them. |
| Indirect addressing | Can a pointer resolve to V1202? |
Capture the pointer value when the write executes. |
| External data write | Can an HMI, supervisory system, or another controller write this memory location? | The transition correlates with a logged write or stops when that write path is safely inhibited. |
| Initialization or retained data | Does the word change during startup or a mode transition? | The same transition occurs at the same initialization event. |
Search destination ranges, not just exact text matches. A block instruction can cover V1202 without printing that token as its destination. Complete this stage only when every possible writer has an owner or has been ruled out by its calculated destination range and enabling condition.
Prove which writer changes bit 0
Start with the candidate that executes at the same moment as the cycle. Monitor its enabling logic, source value, destination, and any pointer used to select the destination. For a whole-word operation, compare the value immediately before and after execution and inspect bit 0 specifically.
- Reproduce one transition under controlled conditions.
- Confirm the candidate instruction was enabled during that transition.
- Verify that its resolved destination is
V1202. - Verify that the written result changes bit 0 in the same direction as
B1202.0. - Repeat for the opposite transition; separate instructions may set and clear the bit.
Do not stop after finding the first writer. Multiple instructions or communication clients can write the same word, creating an apparent cycle as each source overwrites the other. If temporarily inhibiting a writer is allowed by the operating procedure, inhibit only its enabling condition and watch whether the transition disappears; never disconnect communications or alter live logic without checking what else depends on that path. Move to correction only after one writer, or a specific conflict between writers, reproduces both edges.
Correct ownership and verify the full sequence
Make the smallest change that restores clear ownership of V1202. Correct the source condition if the word write is intended but triggered at the wrong time. Correct the destination or range if a copy operation reaches V1202 accidentally. Correct the address mapping or write permissions if an external device owns a different data area. If multiple functions intentionally share the word, preserve unrelated bits with the project’s established bit-handling method rather than overwriting the complete word.
- Back up the running project and record the current value of
V1202. - Remove temporary forces, diagnostic bypasses, and test writes.
- Apply the approved logic, mapping, or configuration correction.
- Cycle every operating condition that should set and clear
B1202.0. - Watch the complete
V1202word to confirm unrelated bits retain their intended states. - Test startup, mode changes, and external operator commands that previously coincided with the cycling.
- Cross-reference the finished project again and document every remaining writer to
V1202.
The end-to-end check passes when the intended event changes bit 0 once, the contact follows it, the downstream sequence responds correctly, and no second writer reverses the value unexpectedly.
FAQ
Why does D0-05AR B1202.0 cycle without a coil?
B1202.0 reads bit 0 of V1202. A whole-word write, calculation, copy, indirect operation, initialization event, or external communication write can change that bit without a separate bit coil.
Why does searching for B1202.0 find no trigger?
The program may write V1202 as a complete word or include it inside a destination range. Search and cross-reference both addresses, then inspect block ranges and resolved indirect destinations.
Why should I stop troubleshooting and escalate this fault?
Stop here if you cannot account for every writer to V1202, cannot remove a force safely, or see changes that do not correlate with monitored logic or known communications. Preserve the running project, watch data, and change record, then contact official AutomationDirect support with the controller identification and project details.