Support control center

Epilog Laser Support Built Around Evidence

Separate file, material, optics, airflow, motion, and connectivity symptoms before changing settings. A concise evidence packet shortens the path from an observed fault to a reproducible check.

Include with every request
  • Machine model and identifier
  • Software and file revision
  • Material grade and thickness
  • Photos, error text, and recent changes
Diagnostic dashboard

Five evidence lanes, one incident record

The values below define completeness targets for a support packet. They are not service-time promises or machine-performance claims.

100%

Identity

Model, serial or asset identifier, market, source type, lens, accessory, and electrical configuration.

4 files

Evidence

Source artwork, settings export or screenshot, result photo under neutral light, and full error text.

3 states

Machine condition

Optics cleanliness, focus method, and exhaust or air-assist condition at the moment of the issue.

2 runs

Reproduction

Known-good control file and affected production file tested without changing multiple variables at once.

1 change

Isolation

Change one parameter, component, cable, file, or material factor per step and record the observed difference.

Stop conditions

Stop operation when there is flame that is not immediately controlled, unexpected smoke chemistry, damaged interlocks, abnormal accessible emission, a compromised enclosure, electrical odor, coolant or fluid leakage where applicable, or motion that could strike a fixture. Do not bypass an interlock to continue a test. Unknown PVC or halogenated material remains outside the queue until its composition is confirmed.

Document library

Match guidance to the exact configuration

Use the current document supplied for the machine and market. Family-level guidance cannot replace model-specific electrical, exhaust, lens, accessory, or safety instructions.

Preflight evidence worksheet

Fields for system identity, file revision, material lot, optics state, focus, airflow, exhaust, and parameter history.

Request worksheet

Material test matrix

A bounded table for power, speed, frequency, resolution, focus offset, pass count, result code, and photo reference.

Request matrix

Maintenance observation log

Records cleaning, inspection, replacement, alignment checks, symptoms, operator, and before-and-after test result.

Request log
Escalation path

Change one variable at a time

This sequence protects the evidence trail. If a safety stop condition appears, stop before Step 1 and follow the model-specific safety and service instructions.

  1. Capture the baseline

    Save the current file, settings, material identity, machine state, photos, and error text before making changes.

  2. Run a known-good control

    Use an approved file and known material to distinguish a job-specific issue from a broader machine or environment issue.

  3. Inspect the process chain

    Check focus, optics, mirrors where applicable, air assist, exhaust, fixture clearance, bed flatness, cables, and recent maintenance.

  4. Isolate and document

    Change one factor, repeat the same observation, and add the outcome to the incident record. Avoid simultaneous settings changes.

  5. Escalate with the packet

    Send the complete record and state the last known-good run, first failed run, and every change between them.

Open a support brief with usable evidence

List the exact model, system identifier, material, software, source file revision, settings, observed result, recent change, and steps already completed. Attach unedited error text and clear photos when available.