Ortur Laser Master 2: No X/Y Movement or Homing

Just got the Laser Master 2. Assembly and setup was easy. When trying to Home it and start things up, I’m having problems:

Waiting for connection...
Ortur Laser Ready!
Grbl 1.1f ['$' for help]
[MSG:Check Limits]
[MSG:'$H'|'$X' to unlock]
[MSG:Caution: Unlocked]

So I’m not sure what’s happening. I’ve looked up GRBL error:9 and ALARM:8.

“error:9”  : _(“G-code locked out during alarm or jog state”),

Ok, that make sense that it won’t do anything in an alarm state.

“ALARM:8” : _(“Homing fail. Cycle failed to clear limit switch when pulling off. Try increasing pull-off setting or check wiring.”),

Ok, so the laser is in the middle of the cutting field, so neither the x or y limit switches are being touched. I checked the wiring and everything appears to be hooked up just fine. (I mean, it wasn’t hard…)

The board is alive and responding:


Also, because I just got it, I am assuming the firmware update 1.34 is already installed, as $110 through $112 already at 9000.

I’ve read through the other posts and they seem to be focused on the firmware issue, but this shouldn’t be it: I just got it and it is already applied.

Any ideas on what I should check next?

Make sure you have the power cord plugged in - if it’s just connected by USB, it will talk to you but there will be no power to the motors. I know this seems like a dumb and obvious thing to start with, but I just connected mine and did this myself, so I figured we’d start here. :slight_smile:

1 Like

I must admit, when I first saw this, I was offended and angry.

Then I metered the power adapter. It was bad, putting out only about .01V as opposed to the 12V it was supposed to.

Note to self: make sure you’ve got good power as part of your troubleshooting!

It wouldn’t be the first thing we bring up if it wasn’t a frequent issue :slight_smile:

I try to start with the dirt simple stuff, just to get it out of the way, and honestly, most problems end up having simple solutions, and tossing your assumptions helps when solving them.

I’m repeating this mostly for me, because I couldn’t count the number of times I’ve been looking for a bug and passed over something in the code thinking, “well I know it’s not that”, and eventually, well, yes, actually, it ends up being that.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.