Press Interface

NC Feeder–Press Encoder Synchronization and Signal Interruption Checks

This guide explains the functional relationship between press position, feed permission and material release. It also shows how to preserve evidence when a signal becomes intermittent—without publishing a universal wiring diagram or timing angle.

Start with the architecture: some projects use an encoder, some use mechanical or electronic cam outputs, and others exchange PLC states. Identify the exact source, receiver, signal meaning and safe state before interpreting an interruption.
  • Position sourceEncoder, cam, press PLC or another released function.
  • Feed functionPermission or request while the die path is clear.
  • Release functionProject-defined handoff for pilot or die correction.
  • Safe responseStop and retain state when a required signal is lost.

Identify the actual synchronization architecture

Do not assume that the feeder receives a continuous shaft angle just because the press has an encoder. The press control may convert position into cam outputs or PLC conditions before the feeder sees any input. Record the released drawing, device identity, connection, controls owner and the exact feeder input or network variable being verified.

Architecture What the feeder may receive Evidence needed
Direct position integration Position data or a project-specific encoded reference Hardware, configuration, scaling and interface documents.
Cam-based Discrete feed and release windows Cam source, polarity, window definition and input mapping.
PLC handshake Request, permissive, ready, complete and fault states I/O or network list, sequence description and safe-state logic.
Processing-machine control Feeder output commanding a shear or another machine Project sequence and responsibility matrix for both systems.

Separate feed, release and interlock functions

A stable line may need more than one function. Feed permission tells the feeder when material motion is allowed. Release permits a project-defined material correction where fitted. Ready, complete, fault, guard, lubrication, air-pressure or die-protection states may prevent the next cycle. A symptom described only as “the signal stopped” is therefore incomplete.

NC feeder and press used for encoder synchronization checks
Identify the source and receiver on the actual feeder–press project.
servo feeder control hardware used for signal verification
Use released input definitions instead of a generic signal name.

Capture an interrupted-signal symptom before changing anything

Record the exact cycle point, operating mode, speed stage, job, recent change and displayed alarm or state. Determine whether the originating press function disappeared, the feeder input failed to recognize it, or the sequence intentionally removed permission because another interlock changed.

  1. Preserve the first-failure time and machine state.
  2. Compare the source indication with the receiving input using authorized diagnostics.
  3. Record related ready, complete, release, stop and fault states at the same moment.
  4. Inspect only the identified connector, cable route, terminal and device under the approved electrical safe-work method.
  5. Repeat a controlled observation only after the responsible controls owner approves the test.
Do not jumper an input or defeat an interlock. An intermittent signal may be the correct response to a lost prerequisite. Forcing it can start material or press motion outside the intended sequence.

Use the evidence pattern to narrow the fault boundary

Observed pattern Boundary to verify Useful retained evidence
Source and feeder input both drop Press logic, cam condition, upstream interlock or source device Press state, source trace and prerequisite states.
Source remains active; feeder input drops Wiring, connector, input device, reference, configuration or communications path Simultaneous source/receiver observation and released circuit reference.
Input remains active; feed does not start Feeder ready state, sequence, recipe, count, fault or motion permissive Feeder I/O, mode, counter, alarm and sequence step.
One feed completes, then no next request Handshake completion or press sequence Auto-mode sequence evidence.

Inspect physical and electrical conditions safely

With hazardous energy controlled, inspect for loose terminals, damaged cable sections, repeated flexing, contamination, connector strain and changes made during maintenance. Shield, grounding, reference voltage, input type and cable routing must follow the released electrical design; this article does not prescribe a generic termination.

NC servo feeder control interface for press operation
Press and feeder control responsibilities must be named in the project records.
NC feeder connected to a punch press for signal checks
Machine context alone does not define polarity, timing or safe state.

Verify timing as an acceptance function, not a copied angle

The approved feed and release windows depend on press motion, die clearance, material path, feeder response and the installed release method. A crank-angle range from another article or line is not an acceptance criterion. Verify the named functions in authorized jog, single-stroke and staged automatic conditions, then retain the observed source and receiver states.

Frequently asked questions

Does every NC feeder connect directly to a press encoder?

No. The project may use encoder data, cam outputs, PLC handshakes or another released architecture. Verify the actual design.

Why can a signal appear to be interrupted?

The source may drop, the transfer path may be unstable, the receiving input may not recognize the state, or another interlock may intentionally remove permission. Capture both sides simultaneously.

Can I use a common 240°-to-90° feed window?

Not as a universal setting. Use the named press, die, feeder and interface criteria and verify the result in controlled conditions.

Send HENLI a usable signal-interruption record

Include the feeder and press identity, released interface drawing, exact input/output names, operating mode, cycle point, alarms, recent changes and simultaneous source/receiver observations.

Request controls support