PIXEL 2511 DI Logic: Polarity Mismatch, Not Random Inputs

PIXEL 2511 input faults that appear random can come from three separate layers: missing SMLogix variable bindings, opposite filter polarity between local PIXEL inputs and MR120 inputs, or an electrical/hardware fault. Diagnose those layers separately. Do not rewrite the level logic or return the controller for repair until the raw input indications pass a controlled test.

1. Initial symptom classification

Before anything else, confirm whether the failure exists in the project editor, in the controller's raw input status, or only in the application logic. Each observation sends the diagnosis down a different branch.

Keep these branches separate. A project can contain detached variables while the input hardware is healthy, and a correct variable binding can still feed an inverted MR120 signal into the level logic.

2. SMLogix binding inspection

Detached variables were observed unpredictably when leaving a macro and returning to the main project screen. One object, several objects, or all related variables could disappear. Downloading that state transfers a project whose buttons or I/O references no longer point to the intended device-tree objects.

1. Open the project that will actually be downloaded. Do not validate an older diagnostic copy while the controller runs a modified copy.
2. Expand every branch of the device tree containing buttons, local DI, MR120 DI, and DO objects.
3. Compare the objects placed in macros and screens with the corresponding tree entries. A missing or visibly detached reference must be treated as invalid.
4. Replace each detached variable by selecting the correct object again from the device tree. Do not merely rename the broken object; rebuilding the reference is the corrective action.
5. Leave the macro, return to the main screen, and repeat the tree inspection because that navigation was associated with the detachment.
6. Save, reopen, and inspect the final project immediately before download. Do not move on until all required inputs, outputs, and keyboard objects remain present.

Use the newest available SMLogix release approved for the installation. Newer releases showed better stability, but version choice does not remove the pre-download inspection requirement. No affected or corrected version number is identified, so acceptance must be based on a repeatable project check rather than a version assumption.

3. Raw-input isolation

The decisive reading is the raw channel state, not the tank-level code produced after filtering and decoding. A displayed value such as 0100 or 1000 can result from polarity, ordering, or decoder errors even when the electrical channel works.

1. Record the exact project revision running in the controller.
2. Disconnect all field-input connectors from PIXEL 2511 and MR120. Leave only the controller supply and the interconnection cable between the controller and module required for the test.
3. Open the controller system menu, enter SMLogix project management, and observe the numeric indications for the corresponding raw inputs.
4. Record every idle value before applying a test jumper. All disconnected channels should show their defined inactive state after the project conventions are accounted for.
5. Operate one physical input only and record three observations: the raw system-menu channel, the application display position, and the calculated level code.

If the raw channel changes but the wrong display position changes, trace the software mapping from that channel through the filter macro and into the display variable. If the raw channel itself does not change, continue with the electrical checks. If DI4 remains at 1 with all field connectors removed, do not mask it in the decoder; inspect and test that input as a possible terminal or hardware fault.

4. PIXEL and MR120 polarity decision

The installation's working correction was an opposite filter convention for the two input locations. This difference must be implemented deliberately wherever the same contact type can be connected to either device.

Apply these values in the input-filter macro, not by reversing unrelated display bits or altering the failure code. The opposite convention is a compatibility characteristic retained to avoid changing the behavior of commissioned projects.

1. Identify whether each signal enters the local PIXEL terminals or the MR120.
2. Identify the field contact as normally open or normally closed.
3. Set the filter value from the table for that device and contact type.
4. Watch the raw state while opening and closing the contact. Confirm that the filtered logical state follows the process meaning, not merely the electrical level.
5. Repeat for every channel; do not copy one filter setting across local and expansion inputs without changing the convention.

For the recorded level decoder, expected codes included 0, 1, 2, 4, and failure code 5. A proposed code of 8 was corrected: with the cited PRCD arrangement, the relevant decoded result was 4. Verify the input count and bit order at the block before assigning a decimal code.

5. Energized voltage test

Use voltage measurements for an energized controller. A continuity beeper injects its own test current and can conduct through input protection or semiconductor paths, so a reading of zero with an audible signal on powered electronics does not establish that the DI terminals contain a metallic short.

1. Remove the field wiring and inspect the removable terminal block for wire strands or conductive debris bridging adjacent positions.
2. Power the isolated controller and measure from INT to N. The expected potential is greater than 18 V.
3. Install a jumper between EXT and N.
4. In the system menu, watch the raw SMLogix input values while momentarily connecting each local DI terminal to INT.
5. Confirm that only the addressed channel changes and that it returns to its idle value when the jumper is removed.
6. At MR120, measure U+ relative to the module's ground terminal. The expected potential is greater than 18 V.
7. Momentarily connect each module input to U+. Confirm both the corresponding module LED and the raw input indication.

A missing supply potential directs the diagnosis toward supply, common, or terminal wiring. Correct voltage with no raw-state response directs it toward channel configuration, interconnection, or input hardware. A channel LED that operates while the controller value does not points away from the field contact and toward the module-to-controller data path or project association.

6. De-energized continuity test

Continuity and resistance measurements require a de-energized, isolated circuit. Measuring resistance while the controller is powered produces an invalid test condition and can make protection networks look like a short.

1. Switch off and verify removal of controller and module power.
2. Remove the input terminal block from the controller.
3. Disconnect the sensors at the far end so the cable is isolated at both ends.
4. Measure conductor-to-conductor resistance in the cable. This separates cable damage from controller behavior.
5. Inspect the removed connector and measure it separately. Look specifically for a clipped wire strand bridging positions.
6. Measure the controller inputs only after verifying zero applied voltage. Reverse the meter leads and record both readings because semiconductor protection paths can be polarity-sensitive.

A cable that tests isolated while adjacent controller inputs remain at near-zero resistance in both directions requires hardware evaluation. Input protection is intended to limit wider damage; a protection event can still leave the affected controller damaged. Do not infer that protection operation should make several inputs read as a permanent short, and do not infer healthy hardware solely because the rest of the controller runs.

7. Resolving-branch commissioning procedure

1. Convert incompatible screen assets from PNG to JPEG, reload them, and confirm correct rendering independently of the DI work.
2. Open the exact SMLogix project intended for service, rebuild every detached button and I/O reference from the device tree, navigate out of each macro, and inspect the tree again.
3. Disconnect the field inputs and verify the raw idle states. Investigate any channel such as DI4 that remains active before modifying the level decoder.
4. Verify more than 18 V from INT to N, install the EXT-to-N jumper, and stimulate each local DI from INT.
5. Verify more than 18 V from MR120 U+ to module ground, then stimulate each MR120 input from U+ while checking its LED and raw value.
6. Set the input-filter values by location: local PIXEL NC 0, local PIXEL NO 1, MR120 NC 1, and MR120 NO 0.
7. Reconnect one field signal at a time. Confirm the physical channel, raw value, filtered value, display position, and decoded result before connecting the next signal.
8. Exercise every valid tank-level combination and every invalid combination. Confirm expected codes 0, 1, 2, and 4, with invalid combinations producing 5.
9. Perform the final device-tree inspection, download the unchanged verified project, cycle through the macros and main screen, and repeat the one-input-at-a-time test without any variable disappearing or moving to another displayed position.

FAQ