UmproTech resource

CypCut & FSCUT Diagnostics | Version, I/O, EtherCAT & Parameters

CONFIGURATION CONTROL • BACKUP FIRST • SOFTWARE • I/O • MOTION • LASER ENABLE

Freeze the Machine State Before Changing the Controller

CypCut and FSCUT faults can come from software, Windows, configuration, I/O, EtherCAT, servos, height control, laser-source communication or a safety condition. The first step is preserving evidence and backups—not loading a parameter file from another machine.

Submit Controller Evidence
Do not bypass safety I/O, defeat interlocks, jog into an obstruction, energize a laser for testing without a controlled area, or load unknown machine parameters. Incorrect configuration can cause uncontrolled motion, collision, lost calibration or unsafe laser enable.
Backup discipline: Before approved changes, preserve the current machine configuration, software version, controller model, parameter screens, alarm history and any known-good backup. A backup from a similar-looking machine is not automatically compatible.

Classify the Fault Before Editing Anything

Software or file

Program will not open, DXF issue, nesting failure, license state, corrupted job or Windows problem.

Network or EtherCAT

Device offline, bus fault, servo communication or hardware-node mismatch.

I/O or safety chain

E-stop, door, gas, chiller, source-ready, contactor or interlock state prevents operation.

Motion and homing

Axis alarm, limit, encoder, servo, origin or collision-related condition.

Height control

Capacitive calibration, follow error, nozzle/ceramic, plate sensing or controller integration.

Laser enable

Source ready but no enable/emission command, wrong protocol or missing permission state.

Controller Identity Package

Item What to capture
Hardware FSCUT model, motion card, height controller, servo drives and major I/O hardware.
Software CypCut/HypCut or other software name, exact version/build, Windows version and license status.
Machine configuration Table size, axes, source, cutting head, chiller, exchange table and automation.
Failure evidence Exact alarm, status screens, I/O state, EtherCAT/device list and startup video.
Change history Update, PC replacement, parameter restore, power loss, relocation, drive replacement or wiring work.

Safe Diagnostic Sequence

  1. Record the exact error and machine state before resetting.
  2. Determine whether the fault is software/file, communication, I/O, motion, height control or laser enable.
  3. Compare current hardware and software identity to the assigned machine documentation.
  4. Preserve backups and screenshots before approved parameter changes.
  5. Check external conditions—E-stops, chiller, gas, source-ready, doors and obstruction—without bypassing them.
  6. Escalate electrical, drive, bus, cabinet or safety-circuit work to qualified personnel.

What to Submit

  • Full-screen screenshots, not cropped alarm text only.
  • Software version and controller/FSCUT model.
  • Video from startup to failure.
  • Device/EtherCAT status and relevant I/O screen when safely available.
  • Parameter backup availability and date of last known-good operation.
  • Machine, source, head, chiller and servo nameplates.
  • Exact change immediately before the fault.

Start Controller Support Intake

Scope Limitation

Evidence review does not authorize remote control, parameter changes, software licensing, electrical work or safety-circuit modification. Compatibility and recovery steps depend on the exact controller generation, machine configuration and valid backup. Written scope controls remote or onsite support.