Program, DXF, nesting, license
Separate file corruption, import settings, software build, license, storage, Windows, and job-specific behavior.
UmproTech industrial machinery
CypCut & FSCUT Diagnostics | Version, I/O, EtherCAT & Parameters
Review machines, applications, facility requirements, delivery, installation, training, warranty, service, parts, rental, and financing pathways.
Backup · software · I/O · EtherCAT · motion · laser enable
Freeze the machine state before changing the controller.
CypCut and FSCUT symptoms can originate in software, Windows, machine configuration, I/O, EtherCAT, servos, height control, the safety chain, source communication, or external readiness. Preserve evidence and a known machine identity before editing anything.
A parameter file is machine configuration—not a generic preset.Identity → evidence → backup → fault class → controlled change → acceptance.
Capture full screensAlarm, state, version, device list
Preserve backupsCurrent and known-good machine files
Classify the faultSoftware, bus, I/O, motion, height
Control every changeOne revision, one test, one record
!
Do not bypass safety I/O or interlocks, jog into an obstruction, energize the laser without a controlled area, defeat a door or E-stop state, load unknown machine parameters, or perform energized cabinet work without qualified authorization.Incorrect configuration can cause uncontrolled motion, collision, lost calibration, unexpected laser enable, or damage to the machine and work area.
Backup discipline: preserve the current configuration, CypCut or HypCut version, FSCUT model, parameter screens, alarm history, and any known-good backup before an approved change. A backup from a similar-looking machine is not automatically compatible.
Fault class
Classify the symptom before editing a parameter
A controller screen can display a problem that actually begins in a file, Windows, field device, safety state, drive, chiller, source, or optical system.
EtherCAT or device offline
Capture the complete device tree, first missing node, drive state, topology, startup sequence, and change history.
Interlock or readiness missing
Review E-stops, doors, chiller, gas, source ready, contactors, relays, and assigned safety conditions.
Axis, limit, home, servo
Record axis, command, actual position, limit or origin state, drive alarm, collision, and obstruction evidence.
Capacitive follow or calibration
Separate nozzle, ceramic, plate, cable, calibration, sensor, controller integration, and crash history.
Source ready, no emission
Preserve source status, power command, enable, safety permission, communication, head, and cooling evidence.
Diagnostic sequence
Six layers from evidence to controlled recovery
The sequence protects machine identity, the last known-good state, safety logic, and the ability to reverse an approved change.
Freeze state
Full alarm, screen, device state, machine position, job, startup step, and time of failure.
Identify system
Machine, CypCut or HypCut build, FSCUT, height controller, drives, source, head, and chiller.
Preserve backups
Current files, known-good version, parameter screens, license, Windows state, and storage location.
Classify layer
File, software, Windows, bus, I/O, safety, motion, height, source enable, or external readiness.
Approve one change
Defined objective, exact file or value, authority, backup, risk, rollback, and controlled test.
Accept or reverse
Verify homing, limits, motion, safety, height, source enable, cut result, documentation, and open issues.
Diagnostic matrix
Match the failure pattern to the evidence path
Do not use resets or parameter changes to erase the state before the complete evidence is captured.
| Symptom | Review first | Evidence to prepare |
|---|---|---|
| Software will not open or job fails | Exact software and build, Windows, license, storage, file type, one job versus all jobs, recent update or PC event. | Full error, version screens, original DXF or job, steps to reproduce, known-good file result, Windows and storage context. |
| EtherCAT or node offline | First missing device, topology, drive power and alarm, communication path, startup order, recent replacement or wiring work. | Complete device tree, all drive displays, controller and motion hardware labels, startup video, change history. |
| Machine will not become ready | E-stops, guarding, doors, gas, chiller, source ready, contactors, I/O, safety logic, assigned permissives. | Full I/O and status screens, external condition, exact missing state, alarms from all connected systems. |
| Axis will not home or move correctly | Axis identity, position, origin, limit, obstruction, drive alarm, encoder, mechanics, collision or relocation. | Command and actual screens, drive code, safe motion video, machine position, limit or reference state, recent work. |
| Height control fails | Nozzle, ceramic, plate sensing, calibration, cable, head model, controller integration, crash, grounding context. | Calibration screen, exact error, head and height-controller identity, external consumable photos, safe sequence. |
| Source ready but no laser command | Power command, enable, safety permission, source protocol, I/O, cooling protection, head state, process conditions. | Source and CNC status, relevant I/O, full alarms, chiller state, machine configuration, last normal operation. |
Change control
A safe recovery has a backup, owner, test, and rollback
Use this protocol only under the assigned machine documentation, site procedures, and qualified authorization.
Define the problem
Write the exact fault, state, production impact, and evidence that would prove the change worked.
Capture the baseline
Save full screens, machine identity, parameter values, configuration files, versions, and known-good history.
Approve one revision
Identify the exact file, parameter, device, software action, authority, risk, and rollback method.
Test in stages
Verify safety, I/O, homing, limits, motion, height, source readiness, then process performance in a controlled area.
Document the result
Record before and after states, accepted version, backups, unresolved issues, limits, and operator handoff.
Identity package
One screenshot is not a controller configuration
Submit full-screen evidence and the complete machine identity. Crop only a copy; preserve the original context and timestamp.
- Machine manufacturer, model, serial, table, axes, exchange table, and automation
- CypCut, HypCut, TubePro, or other application name and exact version or build
- FSCUT model, motion card, height controller, servo drives, and major I/O hardware
- Laser source, wattage, cutting head, chiller, gas, and support-equipment identity
- Complete alarm, device, EtherCAT, I/O, axis, height, and source-status screens
- Video from startup to the safe point where the failure appears
- Current backup, known-good backup, date, origin, software license, and storage location
- Last normal operation and exact update, PC change, restore, power loss, relocation, drive, or wiring event
- ZIP code, production impact, urgency, and requested outcome
Support boundary
Remote review, software recovery, and field service are different scopes
Evidence review does not authorize remote control, parameter edits, software licensing, energized cabinet work, or safety-circuit modification.
Evidence and configuration review
- Confirm machine and controller identity
- Classify software, file, bus, I/O, motion, height, or enable path
- Review available backups and change history
- Define information gaps and the next authorized check
Approved software or restore route
- Valid license and compatible machine files are available
- Current state and backups are preserved
- Exact action, risk, rollback, and acceptance test are written
- Safety, homing, limits, motion, height, and process are revalidated
Qualified field-service route
- Electrical, drive, bus, safety, cabinet, wiring, motion, or unresolved hardware work is required
- Site safety, access, utilities, personnel, and downtime are confirmed
- Travel, labor, parts, schedule, and uncertainty are approved
- Testing, documentation, open items, and handoff are completed
Related technical paths
Connect controller evidence to the full machine state
A controller symptom may belong to cooling, optical delivery, source readiness, installation, or the process.
01 · SYSTEM
Full laser diagnostics
Separate facility, process, control, motion, cooling, optical delivery, and source faults.
Open full diagnostics →02 · COOLINGChiller diagnostics
Review flow, temperature, coolant, condensation, communication, and source or head protection.
Open chiller path →03 · STARTUPInstallation & training
Review utilities, commissioning, configuration, backups, startup, acceptance, and operator handoff.
Open startup path →04 · INTAKESubmit the complete case
Send identity, full screens, backup status, failure state, change history, location, and impact.
Start service intake →CypCut and FSCUT FAQ
Protect the machine configuration from guesswork
Controller generation, machine configuration, valid backups, documentation, software rights, and qualified authority determine the recovery path.
Can a parameter file from a similar machine be loaded?
Not without verified compatibility and an approved recovery plan. Table, axes, motors, drives, limits, height control, source, head, I/O, safety logic, and options can differ.
Should alarms be reset before taking screenshots?
No. First preserve the full alarm, device, I/O, axis, and machine state. A reset can erase evidence or change the symptom sequence.
Does an EtherCAT alarm prove the motion card is bad?
No. Power, first missing node, drive state, topology, cable, connector, device replacement, configuration, and startup sequence must be separated.
Can remote support change safety I/O?
Evidence review does not authorize safety-circuit or interlock modification. Any change requires the correct documentation, authority, risk control, qualified personnel, and validation.
What should be submitted first?
Submit machine and component identity, exact software and FSCUT versions, full alarms and status screens, startup video, backup status, last known-good operation, exact preceding change, ZIP code, and production impact.
Preserve the machine state before attempting recovery.
Send the exact controller identity, full screens, device state, backup status, timeline, change history, location, and production impact.
Diagnostic review, recommendations, remote support, software access, licensing, backup compatibility, parts, field service, schedule, price, and outcome vary by machine and case. The final written quote, service authorization, manufacturer and software requirements, site safety rules, and applicable agreements control. Work must be performed by qualified personnel.
Planning pathway
Connect the requirement to the complete machine project
Application and capacity
Define material, geometry, thickness or capacity, production volume, quality, workflow, and future work.
Machine and facility
Compare configuration, controller, options, utilities, extraction, footprint, access, unloading, and placement.
Ownership and support
Confirm price path, delivery, startup, training, warranty, service, parts, financing, rental, used, or trade-in options.
Next step