Pendant or remote handle not working¶
First identify whether the failure is wireless pairing, USB receiver stability, Windows device recognition, software focus/mapping, or the pendant itself. Keep laser output disabled and clear the machine because a recovered button can command motion.
Symptom A: no response and receiver stays connected¶
- Check battery orientation/charge and inspect contacts for damage or contamination.
- Confirm the USB receiver/dongle is the matching unit and fully seated.
- Use the documented pairing procedure for the supplied handle; do not hold random key combinations while the machine is able to move.
- Verify Windows recognizes the receiver without an error.
- Put focus on the intended mLaser window/mode and test only a low-risk documented key.
- Restart mLaser/control in a safe state after recording current behavior.
Symptom B: Windows disconnects/reconnects USB when a key is pressed¶
This points away from ordinary pairing. An owner reported exactly this behavior: keypress caused a USB disconnect/reconnect on two computers while the handle worked on a third (community report). That does not establish one universal cause, but it makes USB power, receiver hardware/firmware, driver/HID behavior, and host compatibility the useful layers.
Test one at a time:
- Move the receiver from a hub/front-panel extension to a direct known-good PC port.
- Use the same physical port that worked during commissioning.
- Observe Windows Device Manager while pressing a safe key; note the exact device that disappears.
- Compare with a second supported Windows PC if available, using the same receiver and safe machine state.
- Record Hardware IDs, Windows build, whether the device chime occurs, and which key triggers it.
Do not repeatedly reconnect it while an axis or laser command could be accepted. If the behavior follows the receiver across supported PCs, request a replacement/firmware path from Gweike. If it occurs on one PC only, focus on its USB power management, driver stack, port, or security software.
Symptom C: some buttons work or commands are wrong¶
Confirm the correct mLaser mode/window, handle mapping/profile, and software version. Photograph the intended button map from the supplied manual rather than guessing. A key that produces a different command is a stop condition until mapping is verified.
Support package¶
Include machine model, pendant/receiver labels, battery voltage/condition, mLaser and Windows versions, Device Manager evidence, pairing result, exact safe key tested, USB port type, and cross-PC result.