CLICK PLC Gate Control Works When Tags and Limits Align

The four C-more EA-9 speed choices can produce distinct 0–5 V commands only after the selected setting reaches the CLICK PLC word that drives the analog output. The project review identified a broken register path: the HMI writes settings to DS1 through DS4, while the output rungs use DS100 through DS103. Correct that mapping and normalize the numeric tag types before adjusting the analog scale. Commission the gate, temperature input, and current input as separate functions so a fault in one does not hide a fault in another.

Separate the preset mapping fault from analog scaling

Changing the EA-9 thumbwheel values or repeatedly rescaling the analog output will not fix a missing data path. If the ladder copies DS100 through DS103 to the output, but the HMI changes only DS1 through DS4, the output logic never consumes the operator’s settings. The reported 1.25 V and 2.5 V outputs, with the remaining choices following the same quarter-scale pattern, are a reason to inspect the selected-value path and output scaling separately.

Back up both the PLC and HMI projects before editing. In the PLC monitor, watch the four HMI selection bits, the four setpoint registers, the registers used by the analog-output rungs, and the channel’s live output value. Change one HMI value at a time and record which PLC value changes. Do not infer a connection merely because a tag name appears related or because the screen displays the intended number.

1. With the motor command safely isolated, select one EA-9 position and record the active discrete tag.
2. Change that position’s numeric setting and record the affected DS register.
3. Trace the register referenced by each analog-output rung and compare it with the changing HMI register.

Check: You can identify, online, the active selection bit, its associated setting register, and the exact value the output rung consumes. If the setting register changes but the rung’s source does not, repair the value path before touching the channel scale.

Correct the EA-9 tag types and numeric limits

The EA-9 screen uses four discrete tags for the radio-button positions and numeric thumbwheel tags for the adjustable values. Those are separate signals: a selection bit says which choice is active, while the associated numeric register supplies that choice’s value. The project review found a data-type mismatch among the numeric tags: DS1 was set to Unsigned Int 16, while DS2, DS3, and DS4 were set to BCD Int 16.

Standardize the HMI and PLC interpretation of each value; do not leave some presets encoded as BCD while another is treated as an unsigned integer. Then set a numeric-entry limit based on the defined process range. The project review flagged values greater than 100 as a possible problem, but the engineering unit and valid maximum were not specified. If the intended maximum is 100, enforce that limit in both the HMI entry and PLC logic. A two-digit thumbwheel was suggested only for a design whose true maximum is 99; it cannot represent 100.

Also confirm that the radio-button configuration clears the previously selected bit. If the HMI can leave multiple bits active, define a deterministic PLC response—preferably reject the conflicting command and indicate a fault rather than allowing rung order to choose the output silently.

Check: All four numeric tags use the same intended data format and range, each displayed value matches its PLC register, and a single selection produces one active discrete tag.

Route the selected value to the register used by the output

Choose one of two command patterns, based on whether operators may edit the four values while a position remains selected. For editable presets, use the active radio-button bit to select the corresponding current value from DS1 through DS4, then transfer it to the common command value consumed by the analog-output instruction. For fixed presets, a rising edge from each selection bit can load its predetermined value into that command register. The original project review described the latter pattern as loading a value on the leading edge of the selected bit.

The choice matters. An edge-triggered load captures the value only when the operator changes position; editing a thumbwheel while leaving that position selected will not update the output unless the logic also transfers the value continuously or detects the setting change. A continuously selected transfer follows an edited setpoint, but it must handle invalid or conflicting selection bits. In either pattern, do not copy an HMI value to a register that the output rung ignores.

1. Trace the PLC output rung to find the source value and configured output channel.
2. Connect each HMI preset to that source through a selection rule; use the actual CLICK transfer instruction supported by the project.
3. Monitor the destination word while changing each preset and selecting each position.

DF3 was identified in the project as the scaled 0–5 V output tag. Verify in the installed PLC project that it is the correct live output value for the physical channel; do not substitute an address from an example project. The four destinations DS100 through DS103 need a defined purpose if retained. If only one physical output channel drives the speed input, selecting one of four presets should ordinarily result in one unambiguous command value for that channel, not four unrelated source values with no connection to the HMI settings.

Check: Selecting each radio-button position moves the value monitored at the output rung’s source to the corresponding preset value, including after an operator changes a preset using the intended operating method.

Scale and measure the 0–5 V speed command

Only verify scaling after the source register changes correctly. Configure the PLC analog channel for the receiving device’s specified 0–5 V signal range, then use the installed module’s documented raw endpoints and the project’s scaling logic to translate the engineering command into that channel’s output value. The raw counts and module configuration are not identified here, so read them from the actual channel configuration and module documentation rather than guessing them.

Measure the output at the channel terminals relative to its specified analog common with a DC voltmeter. Confirm the receiving input uses the same signal reference and accepts a 0–5 V command. A correct PLC monitor value with an incorrect terminal voltage points toward channel configuration, wiring, common/reference, or output hardware—not the EA-9 tag mapping. A correct terminal voltage but incorrect receiver response points downstream to the receiving input’s wiring, configuration, or scaling.

The reported first two output points were 1.25 V and 2.5 V. If the intended design assigns four equally spaced quarter-span commands over 0–5 V, the corresponding points would be 1.25 V, 2.50 V, 3.75 V, and 5.00 V; use those as acceptance values only if they are the defined setpoints. The EA-9 values were described as adjustable, so measure and compare against the actual approved values instead of forcing an assumed quartile pattern.

1. Test one output command at a time with motor motion prevented by an approved isolation method.
2. Compare the selected HMI value, PLC command word, and measured terminal voltage.
3. Restore the receiving input connection and confirm the same command produces the expected receiver response under controlled conditions.

Check: Each selection produces the defined command at the PLC word and analog terminals, and the receiving device interprets it as intended. Stop if the commanded voltage and terminal measurement disagree or if the analog reference is uncertain.

Interlock the DPDT gate direction circuit

The gate actuator reverses motor polarity through a DPDT relay arrangement. Two PLC outputs were proposed for open and close control, but a PLC relay output must not carry motor current unless its rating explicitly supports that load. Use the PLC outputs to switch a suitably rated relay or the actuator’s designed control inputs, and verify the actual circuit against the wiring schematic before energizing it. A verbal description that one output fires once to open and another fires twice to close does not define a safe, deterministic PLC sequence.

Represent the two directions as distinct commands and prevent both direction outputs from being energized together. Check whether the external relay circuit has a suitable electrical interlock as well as the PLC logic interlock. During a direction change, confirm the old direction is off before the opposite direction is applied; use the relay and actuator documentation to determine any required transition behavior. Do not rely on an unverified ladder sequence to compensate for a polarity-reversing circuit whose contacts or coil wiring are unclear.

A sample project used a C0-02DR-D with Y001 and Y002 assigned to gate outputs and X001 and X002 to limit switches. Treat those as example addresses, not universal wiring instructions: confirm the installed PLC model, output type, input voltage rating, terminal assignment, and field wiring. The sample suggested using the outputs to control relays capable of handling the motor circuit rather than assuming the PLC outputs could power the motor directly.

Check: With the motor power path isolated, verify that open and close requests never turn on both direction outputs and that each PLC output actuates only the intended relay coil or control input. Resolve any disagreement between the schematic and actual wiring before moving on.

Sequence gate travel from command to limit

Use separate open and close sequences. An open request energizes the open-direction control, monitors the open limit input, and turns the output off when that limit is reached. A close request follows the same pattern with the close-direction control and close limit. The sequence must also reject an opposite-direction request while travel is active, or transition through a defined stopped state before reversing.

1. At rest, confirm both limit inputs show the real gate position and neither direction output is active.
2. Issue an open request; verify only the open output energizes and the gate moves toward the open limit.
3. Operate or reach the open limit; verify the input changes state and the open output turns off.
4. Repeat for closing, then test a request received during travel and confirm the configured interlock response.

Check the physical switch’s normally open/normally closed arrangement and the PLC input polarity instead of assuming that an energized input means the gate is at its limit. The example mapped X001 and X002 to the two limits, but the actual address and input voltage must match the installed hardware and wiring. Confirm the sensor changes state at the intended endpoint, not merely when the input terminal is jumpered.

Check: Each physical end switch stops travel in its matching direction, the opposite end switch does not falsely stop that motion, and neither command can drive the gate past its limit.

Add a travel timeout and report a failed limit

A limit-switch sequence can leave a motor energized indefinitely if a switch, wire, relay, or mechanical travel path fails. Add a timeout to each travel operation. Set the value from measured normal travel time under the actual operating conditions, then apply an engineering margin appropriate to the machine; no timeout duration is specified for this installation. When time expires before the expected limit arrives, turn off the direction output, latch a fault indication for the HMI, and block another movement command until the cause is inspected and the fault is deliberately reset.

Also diagnose impossible input combinations, such as both end limits indicating active when the machine cannot physically occupy both positions. Do not bypass a limit or suppress the fault to recover production. Verify switch alignment, wiring continuity, input state, relay operation, and mechanical obstruction before clearing the fault. The example project recommended a timer and a C-more fault indication as error checking beyond the basic sequence.

Check: With the limit input safely prevented from changing during a controlled test, the timeout de-energizes the motor command, displays a fault, and prevents automatic restart. Restore the switch and prove a deliberate reset is required.

Scale temperature and current as separate inputs

The temperature transmitter was described as a 4–20 mA signal spanning −40 to 160 degrees, with the thermal output intended to turn on at 40 and off at 38. Those endpoints give a 200-degree span over 16 mA, or 12.5 degrees per mA. If scaling directly from measured loop current, use T = -40 + ((I - 4) / 16) × 200, where I is current in mA and the temperature unit remains the one used by the transmitter. If the PLC uses raw channel counts, use the input module’s configured raw endpoints to implement the same linear relationship.

Verify the live input at a known temperature or with an approved loop simulator before enabling the thermal output. Then test the 40-on and 38-off thresholds in the project’s stated temperature unit. The 2-degree separation is the intended hysteresis band; confirm the output does not chatter as the measured value moves through the range. The direction of the thermal action—heating or cooling—must match the actual output wiring and equipment, rather than being inferred from a threshold alone.

The current transducer also uses a 4–20 mA loop, but its current measurement span is not stated. Read the transducer nameplate or datasheet and configure the PLC input using that span; do not derive amperes from the loop signal without it. The described behavior, “on at 0 amps, off at 50 amps,” does not identify which condition is an alarm, permissive, or control demand. Define the intended state transition first, then verify the scaled reading at known current points before enabling dependent logic.

Check: The temperature value matches the transmitter range and switches at the defined 40/38 thresholds; the current value matches the sensor’s documented span and the intended 0 A/50 A logic is unambiguous.

Run the complete commissioning test before service

Once each subsystem passes independently, test the combined machine in a controlled state. Preserve a known-good copy of the PLC and EA-9 projects and record the final tag map, analog channel configuration, and gate I/O assignments. Change one input condition at a time so a fault can be localized to the HMI, PLC logic, field wiring, or receiving device.

1. For all four speed choices, compare the active EA-9 bit, preset register, selected PLC command word, measured 0–5 V output, and receiving-device response.
2. For the gate, test open, close, each limit switch, both-direction conflict prevention, and timeout/fault reset.
3. For temperature and current, compare the PLC-scaled values with known input values, then test thresholds and output polarity.
4. Remove test simulators and temporary isolation only after the actual sensors, relays, and receiving inputs are restored and retested.

Do not release the machine with a forced output, bypassed limit, unexplained analog offset, or unresolved mismatch between the schematic and actual wiring. Keep the final live monitor values and fault behavior available during handoff so the next operator can identify a real failure instead of masking it with a setpoint change.

Check: Every HMI choice drives only its approved speed command, gate motion stops at both intended limits, failed travel drops the output and reports a fault, and scaled sensor values produce the specified thermal and current behavior.

Frequently asked questions