Troubleshooting the Gweike M-Series¶
Good fault finding narrows the failing layer while preserving evidence. Record the exact state before restarting, reinstalling, clearing an alarm, or changing a parameter.
Stop instead of troubleshooting live
Isolate the equipment for smoke, arcing, burning odor, water near electrics, damaged optical fiber/connector, cracked optics, exposed conductors, uncontrolled motion/emission, fire, or a failed safety interlock. Do not publish/use service passwords, bridge an FTC/door/work-contact input, or open a laser source to chase an alarm.
First response: capture, make safe, classify¶
- Stop the active process normally if safe; use the emergency stop for an immediate hazard.
- Record the exact message/code, software screen, indicator lights, sounds, and what moved or emitted.
- Note the last known-good job and everything changed since: head/mode, file, parameter set, gas, material, Windows update, cable, maintenance, or power event.
- Classify the failure: power/safety, cooling/source, network/software, motion/height, gas/optics, or process/material.
- Test the least energetic layer first. A connection test does not need laser output; an FTC calibration does not need emission; a frame can prove path without cutting.
Symptom routes¶
- mLaser will not connect
- Remote pendant/handle does not work
- FTC signal wire alarm
- Read laser-source status and logs
- Dross, blowouts, incomplete cuts
- Maintenance schedule
What a useful support package contains¶
Send Gweike the exact model/serial, source brand/power/serial, head/mode, mLaser/Windows versions, timestamp, original error text/code, clear photos of relevant connections/indicators, a short video if motion is involved, source/chiller logs where accessible, the smallest safe reproduction sequence, and the checks already completed.
Do not send only “doesn’t work,” and do not change ten settings before collecting evidence. If a community thread has no verified resolution, this wiki says so rather than manufacturing one.