mLaser will not connect¶
Diagnose from cable to application. Reinstalling mLaser cannot fix a dead Ethernet link, and changing IP values cannot fix a controller that is not powered.
1. Preserve the known settings¶
Photograph the mLaser connection page and Windows IPv4 settings before editing. Record the controller address supplied for your machine, mLaser version, Windows version, adapter name, and whether the setup ever worked.
Keep laser output disabled and the motion area clear; a successful reconnect can restore control unexpectedly.
2. Prove the physical link¶
- Confirm the control system is powered normally with no safety/power fault blocking startup.
- Check the cable is in the intended machine Ethernet port, not another accessory port.
- Look for link/activity indication on the adapter/port where available.
- In Windows, confirm the dedicated Ethernet adapter appears and is enabled.
- Try a known-good cable and, for USB adapters, the same reliable USB port; avoid an unpowered hub.
If Windows repeatedly connects/disconnects the adapter, solve USB power/hardware first.
3. Verify the static IPv4 pair¶
Use the exact PC address, subnet mask, and controller address supplied for the machine. PC and controller must be distinct addresses in the same intended subnet. A direct machine link normally does not require a gateway or DNS entry.
Check that no second device uses either address. Do not copy an arbitrary IP pair from a forum screenshot: controller configurations can differ.
4. Remove routing ambiguity¶
Temporarily disconnect Wi-Fi and VPNs and disable unrelated virtual/network adapters for a controlled test, noting their original state. Windows should show the M-Series link on the dedicated adapter. Restore unrelated networking after the test.
If allowed on your Windows setup, test reachability of the supplied controller IP. A reply proves network reachability, not that mLaser is using the right controller protocol; no reply is not conclusive if the controller does not answer that test.
5. Check software and policy¶
- Launch the supported mLaser build and select the correct M-Series controller/configuration.
- Check Windows Firewall/security prompts for the private wired network. Prefer a narrow application/network rule over disabling protection globally.
- Run with the required user privileges for the installed driver/controller component.
- Verify the configuration/parameter package belongs to this machine/source.
6. Controlled substitutions¶
Change one thing per test: cable, adapter, then computer. If a second Windows PC connects with the same cable/settings, the first PC is the likely layer. If neither shows a physical link, focus on machine port/controller power and ask Gweike before opening control panels.
Escalate with evidence¶
Send the controller/PC addresses (mask private network details if publishing), adapter status, link-light behavior, mLaser version, exact error, and results of each substitution. Do not alter controller service settings or use a service password to force discovery.