IC693DSM302 Limit Input at 24V but Axis Moves

IC693DSM302 Over-Travel Input at 24V but Axis Keeps Moving: Does Software Limit Really Mask Hardware Protection?

Brief Description: Field engineers on GE Fanuc Series 90-30 platforms report a confusing symptom. The IC693DSM302 over-travel input reads 24V, yet the servo axis continues to move in the limited direction. This article examines the real relationship between software limits and hardware protection, explains the module’s input logic, and offers practical diagnostic steps for industrial automation and factory automation engineers.

Understanding the IC693DSM302 Hardware Limit Architecture

How the Two-Axis Motion Controller Reads Limit Switches

The IC693DSM302 acts as a two-axis motion controller for the Series 90-30 PLC family. Each servo axis offers dedicated home and over-travel switch inputs. These circuits accept 24V DC signals through the IC693ACC335 or IC693ACC336 terminal boards. GE Fanuc recommends keeping the input voltage below 30 VDC on these 24V circuits.

Inverted Logic Creates the First Point of Confusion

The DSM302 does not always treat 24V presence as the safe condition. The firmware interprets the limit switch state based on the enabled or disabled setting in the configuration software. According to the DSM302 user manual, the over-travel limit switches must be ON, meaning 24V input is high, when the limit function is enabled. Conversely, the switch turns OFF when the OT Limit Switch is enabled via configuration. Therefore, this inverted logic represents the first potential source of confusion for control systems engineers.

The Interaction Between Software Limits and Hardware Protection

Two Independent Safety Layers, Not One Overriding the Other

Software limits and hardware limits run as parallel, yet independent, safety layers. Hardware over-travel stays active once wired and configured correctly. Software over-travel, by contrast, activates only after the axis has been homed and the feature is enabled by the system integrator.

How the Firmware Evaluates Both Limit Types

The DSM302 firmware evaluates both limit types during motion command execution. If a programmed move, either PMOVE or CMOVE, would cross a software end-of-travel boundary, the module restricts that move regardless of the hardware input state. This behavior does not constitute masking of the hardware limit. Instead, it reflects the module’s attempt to prevent the axis from reaching the physical switch in the first place. However, if the axis has not been homed, or if the software limit values are set outside the physical travel range, the hardware input becomes the sole protective barrier.

Diagnosing the 24V Input with No Stopping Response

Three Primary Failure Modes Behind the Symptom

Three primary failure modes explain why a 24V limit input fails to halt axis motion. First, the input signal may not reach the DSM302’s internal logic because of terminal board wiring faults or blown MOV protectors. The terminal blocks contain Metal Oxide Varistor circuits that absorb excessive energy. A failed MOV can open the circuit while the field voltage still reads 24V at the wire.

Disabled Configuration and AxisMode Errors

Second, the configuration parameter for the over-travel input may be set to disabled. The DSM302 allows each axis to ignore the limit switch input entirely. In this state, the input LED may illuminate, but the firmware never evaluates the signal for motion stopping. Third, an AxisMode configuration error can create a condition where the axis stops at the software EOT but cannot jog back off the switch. GE Fanuc documentation specifically warns that when AxisMode equals LINEAR, the PosEOT value must be set below the Hi Limit and the NegEOT above the LoLimit. For example, with a Hi Limit of +1000, set PosEOT to +990 rather than +1000.

Quantifying the Risk: Response Times and Position Ranges

Why Milliseconds Matter at High Axis Speed

The DSM302 position range extends from –8,388,608 to +8,388,607 user units. Speed settings reach 8,388,607 user units per second. At maximum velocity, an axis can traverse the entire positive software limit window in approximately one second. A hardware limit switch positioned only millimeters beyond the software boundary provides negligible additional stopping distance if the software limit fails to trigger.

Hardware Versus Software Stopping Delay

Hardware-based stopping in comparable motion controllers achieves response delays below 1 microsecond. Software-based stopping, by contrast, may incur a delay equal to the motion engine execution interval. The DSM302 block processing time remains under 5 milliseconds. For a servo axis moving at 500 mm/s, a 5 ms software response allows an additional 2.5 mm of travel before deceleration begins. Moreover, this figure grows proportionally with axis speed.

Recommended Verification Procedure for Field Engineers

Step-by-Step Checks for PLC and DCS Maintenance Teams

Begin by confirming the over-travel input configuration parameter in Logicmaster 90-30 or the relevant programming software. Verify that the axis-specific limit switch function is enabled, not bypassed. Next, measure continuity from the terminal board screw to the DSM302 connector pin while the 24V signal is present. This step isolates MOV failures from firmware issues.

Monitor Status Bits and Cross-Check Boundary Values

Then, command a low-speed jog toward the limit direction while monitoring the %I status bits for the over-travel input. If the bit transitions but motion persists, the fault lies in the configuration or firmware evaluation logic. Finally, cross-check the PosEOT and NegEOT values against the Hi Limit and LoLimit count boundaries. Maintain a minimum 10-unit separation between software and hardware boundaries to prevent the stuck at limit condition documented by GE Fanuc.

Conclusion: Software Limits Do Not Mask Hardware Protection

What the Evidence Actually Shows

The evidence does not support the hypothesis that software limits intentionally override hardware inputs. The DSM302 treats these as sequential protective layers with distinct activation conditions. A 24V input that fails to stop motion points to configuration errors, wiring faults, or terminal board component degradation. Engineers should verify the input’s enabled state and the AxisMode boundary values before assuming a firmware defect. Properly configured, the hardware limit remains the final and independent safety barrier.

Author Insight and Industry Commentary

Why This Symptom Keeps Appearing in Factory Automation

In my experience supporting industrial automation retrofits, this symptom often surfaces after a firmware update or a parameter restore. Engineers trust the 24V reading on the wire and assume the PLC sees the same state. However, the DSM302 evaluates the input only when the configuration enables it. As a result, teams should treat configuration review as part of every limit-switch troubleshooting routine. This habit reduces downtime and strengthens the safety layer that control systems depend on.

Application Case and Solution Scenario

Packaging Line Axis Over-Travel Recovery

A packaging line using a Series 90-30 PLC reported an axis that kept moving despite a 24V limit signal. The maintenance team first checked wiring and found a failed MOV on the terminal board. After replacing the board, the axis still jogged past the switch. A configuration review then revealed the over-travel input was disabled for that axis. The team enabled the input and adjusted PosEOT to 990 against a Hi Limit of 1000. The axis stopped correctly on the next test run, and the line returned to normal production within one shift.

Frequently Asked Questions

Can software limits override hardware over-travel on the IC693DSM302?

No. The DSM302 evaluates both layers independently. Software limits restrict programmed moves, but they do not disable the hardware input when the input is enabled and wired correctly.

Why does the limit input show 24V but the axis keeps moving?

Common causes include a disabled over-travel parameter, a blown MOV on the terminal board, or an AxisMode boundary error. Check configuration first, then measure continuity to the connector pin.

What is the correct PosEOT setting when Hi Limit is +1000?

GE Fanuc recommends setting PosEOT below the Hi Limit. For a Hi Limit of +1000, set PosEOT to +990. This 10-unit gap prevents the stuck at limit condition.

How fast does the DSM302 respond to a limit condition?

The block processing time stays under 5 milliseconds. At 500 mm/s, that delay allows about 2.5 mm of extra travel before deceleration begins. Hardware-based stopping in comparable controllers reacts below 1 microsecond.

Does the axis need to be homed for software limits to work?

Yes. Software over-travel activates only after the axis has been homed and the feature is enabled. Before homing, the hardware limit remains the sole protective barrier.

Leave a Reply

Your email address will not be published. Required fields are marked *

Comment

Name

Home Shop
Shopping Cart (0)

No products in the cart. No products in the cart.