Source never becomes ready
Capture the source alarm, chiller channel, safety state, communication, startup order, and component identity.
U.S. inventory • engineering • field support
UmproTech industrial machinery
Review machines, applications, facility requirements, delivery, installation, training, warranty, service, parts, rental, and financing pathways.
Ready state · cooling · I/O · enable · optical delivery
A program can run without cutting because the safety chain, chiller, controller, I/O, source readiness, enable command, cutting head, QBH, delivery fiber, optics, gas, focus, or process condition is incomplete. Isolate the first missing state before replacing parts.

Observed state
“No beam” is too broad. The machine state determines which evidence can separate control, cooling, source, head, and process paths.
Capture the source alarm, chiller channel, safety state, communication, startup order, and component identity.
Review CNC status, I/O, safety permission, process command, power request, and controller configuration.
Preserve source state, alarm, communication, cooling, command level, history, and assigned diagnostic interface.
Separate head state, shutter where applicable, QBH and fiber history, focus, optics, height, gas, and process.
Record time-to-fault, load, temperature, cooling, gas, alarm sequence, motion, source, and recent maintenance.
Treat the aiming light as alignment evidence only; it does not prove high-power enable, emission, or delivery.
Isolation sequence
Follow the signal and protection chain in order. A missing upstream permission can make a healthy source appear dead.
Power, E-stops, guarding, doors, gas, extraction, grounding context, and assigned permissives.
Chiller alarm, affected channel, flow, temperature, setpoint, coolant, communication, and source protection.
CypCut or other CNC, FSCUT, status, I/O, EtherCAT, program, power command, and safety permission.
Ready, enable, emission command, exact alarm, output state, communication, and service history.
Head alarm, shutter where applicable, QBH exterior, fiber and crash history, protective window, focus, and height.
Material, nozzle, gas, pressure, flow, focus, pierce, parameters, and controlled known-job evidence.
State matrix
Collect external evidence without opening guarded electrical or optical systems or disturbing the fiber connection.
| Observed condition | What it establishes | Evidence needed next |
|---|---|---|
| Source not ready | A readiness condition is missing; it does not identify whether cooling, communication, interlock, or internal source owns it. | Exact source, chiller, and CNC alarms; startup sequence; readiness screens; machine and component labels. |
| Source ready, no enable | The source may be available but has not received the required machine command or permission. | Controller status and I/O, power command, safety chain, process state, communication, configuration history. |
| Enable commanded, no emission state | The command path reaches the source interface, but the source response or protection state remains unresolved. | Exact source alarm and status, command level, cooling, communication, operating history, authorized diagnostic data. |
| Emission indicated, no workpiece energy | The source reports an emission-related state; optical delivery, head, focus, gas, and process remain open. | Head and controller state, QBH and fiber history, crash, window, focus, height, nozzle, gas, material, safe test result. |
| Intermittent emission or dropout | The failure depends on time, load, heat, cooling, power, reflection, motion, gas, or component state. | Time-to-fault, exact alarm order, job and power, chiller trend, gas behavior, ambient, maintenance, samples, video. |
| Guide light only | The low-power aiming path is visible. It does not establish high-power readiness, enable, emission, or delivery. | Complete source, controller, cooling, optical-chain, and process state—without relying on aiming light as proof. |
Evidence-first workflow
Use this workflow only when the machine is safe and the observations are within the assigned personnel’s authority.
Record the exact alarm, screen, source, chiller, controller, machine position, job state, and time.
Document machine, source, wattage, controller, FSCUT, head, chiller, software version, and recent configuration.
Review external safety, cooling, source-ready, controller I/O, enable, and communication without bypassing them.
Preserve head, crash, window, focus, height, QBH and fiber history, gas, material, and process evidence.
Escalate toward controller, chiller, head, source, process, parts, warranty, or field service with one complete case.

Evidence package
Preserve full screens and the original state. Never recreate a hazardous fault or disturb optical connections merely to obtain a photo.
Related technical paths
Keep the same identity, alarms, screens, sequence, and timeline attached throughout the diagnostic route.
Classify cooling, power, module, communication, enable, interlock, optical, and output alarm families.
Open alarm guide →02 · CONTROLReview software, backup, I/O, EtherCAT, safety, motion, height control, and laser enable.
Open controller path →03 · OPTICSReview nozzle, window, focus, height, gas, cooling, crash, QBH, fiber, and head concerns.
Open cutting-head path →04 · INTAKESend identity, state, alarms, cooling, I/O, optical history, process, location, and impact.
Start service intake →No-beam FAQ
Manufacturer documentation, site safety rules, valid controller configuration, optical procedures, and qualified personnel control the diagnostic boundary.
No. The aiming light does not prove high-power readiness, enable, emission, optical delivery, focus, or process energy at the material.
Not automatically. Safety, cooling, I/O, enable, source state, head, QBH, fiber, focus, gas, material, and parameters must be separated.
No. Preserve the missing permission and diagnose why it is absent. Bypassing protection can create unsafe laser, motion, electrical, cooling, or optical conditions.
Not as a general diagnostic step. Do not disturb the high-power optical connection without the correct qualified procedure, authorization, environment, and controls.
Submit component identity, full alarms and status screens, safe startup sequence, chiller state, I/O and enable evidence, head and crash history, process conditions, ZIP code, and production impact.
Send the exact machine identity, startup sequence, alarms, cooling, controller I/O, source state, optical history, location, and production impact.
Planning pathway
Define material, geometry, thickness or capacity, production volume, quality, workflow, and future work.
Compare configuration, controller, options, utilities, extraction, footprint, access, unloading, and placement.
Confirm price path, delivery, startup, training, warranty, service, parts, financing, rental, used, or trade-in options.
Next step