Ortur Laser Master 2 Pro Homing fail

Thank you for your answer.
I´ve run another test on a third pc with new installed Lightburn and the problem of no homing ist still there.
Here is the description of what it does after turning on the machine:
Case 1 (USB-Cable is unplugged):
No reaction of both axes → the red led is flashing.

Case 2 (USB cable is connected to PC and Lightburn is closed):
No reaction of both axes → the red led is flashing and the blue led is on.

Case 3 (USB cable is connected to PC and Lightburn is sarted):
If i go to “devices” in lightburn and i choose “COM3” for USB-Port the laser makes a step of 3mm in both axes (Y+ and X+) and then stops. The red and the blue led are now on constantly but laser laser is not homed. If i click on “HOME” it only makes the little steps (3mm) and then i get the message:
“ALARM:8
Homing fail. Cycle failed to clear limit switch when pulling off. Try increasing pull-off setting or check wiring.”
It´s really confusing me andI´m very frustraded. Could it maybe be a fault of the motherboard?
Thank you all for your help!
Markus

This actually makes me feel better about it as the symptoms otherwise didn’t make sense. It seems that the issue is somewhat inconsistent then, meaning that homing can work occasionally or under the right circumstances.

I think these tests are very telling. Somehow the laser isn’t attempting to home on startup. Have tried hitting the reset button on the laser? If not, perhaps try hitting reset, then power cycle. Does the behavior change?

Where is the laser head when you turn on the laser? If not already, can you move the laser head to the middle of the frame?

When you say there’s no reaction is there no sound or movement at all when you start the machine?

What was your procedure for testing this?

Can you try one thing? With no computer connected, power on laser. Then manually trigger both switches. Does anything happen? Trigger 2nd time. Any change?

Try the same thing with PC connected and LightBurn on.

How long does this process take? Does it take some time to timeout before you get the ALARM:8?

The error almost makes it seem like it’s in the middle of a homing cycle currently. Pull-off would only occur after the 2nd successful connection with limit switch.

This is why I’ve asked for your limit switch testing procedure. I’m wondering if the limit switches are sending a bad signal or indicating constant trigger state.

Another test: disconnect limit switches and power cycle. Be ready to pull power so you don’t crash the head. Any change in behavior?

Possible but the fact that it worked earlier and the fact that it worked once when you connected to other PC makes me think something else is going on.

First step in troubling is to read the error message and correct what the machine is complaining about.

IMHO, it thinks it’s on the switches when you initiate a home or power up. The attempt to back off fails. That’s it’s complaint and the correct place to start a diagnosis.

It is detecting no transition to ‘inactive’ when it attempts to back off.

The proper diagnosis is switches → wire → controller. If switches → wire is OK that leaves the controller.

@berainlb suggestion of power it on without the limits connected is great. However from pictures I’ve seen, it doesn’t appear that it’s an option since it’s single connector.?


If @Blaschi information is correct, that the switches and wiring is in good shape that pretty much would indicate a hardware problem at the controller end.

@Blaschi could elaborate on how you ‘know’ these are OK. Ohm’d them out, psychic? I’d have more confidence.


I’d at least pull the connector and visually ensure there is nothing ‘shorting’ the limits in some way.

Good luck

:smile_cat:

If it can’t be disconnected at the controller then could be disconnected at the switch.

I’m inclined to agree. If problems persist with limit switches disconnected then very likely hardware and mostly likely on the controller.

That leaves the wiring/connector as ‘questionable’. Low probability, but I’ve been burnt before with a shorted wiring harness or connector.


Maybe you know of a way to get grbl to display the state of the limit switches. It would be interesting to see if once it errors out, if it detects those as being active. I saw this somewhere, but don’t remember where or what command sequence displays these values.

:smile_cat:

Agreed. There’s still value in isolating issues with the switch vs cable.

Issuing ? for status report may show limit switch state status with certain compiles of GRBL. This may also depend on mask value provided in $10.

Pn:P followed by X and/or Y indicate switch activation.

Yes, I tried it very often. It makes no change. If I turn power on it really does nothing. Only the red LED is flashing.

Did you check the limit switch status with the commands @berainlb suggested?

If it says it’s ‘active’, you have to find out why.

:smile_cat:

Here I have some pictures and videos because I think it says more than words:

I also tested the signal of the limit switches on the plug from motherboard and it was there.
I really think that it’s a failure of my motherboard.

Watched the video. Looks like the same issue to me. It thinks it’s on the limit switches.

Everything looks good, including the limit switches. I’d have taken your word for an ohmmeter…

I think you’ve chased it down as far as you can without removing the controller and checking for some type of debris shorting things out.

How new is this machine?

:smile_cat:

Lots of good photos and videos there. Thanks for documenting so well.

Can you run ? in Console and check the status of “Pn”? Would like to confirm that they don’t show as being triggered.

Just for due diligence can you run these commands in Console and return results?

$I
$$
$#
?

Might want to post the syntax of the ‘Pn’. My grbl chokes on it and a bunch of variations. I don’t seem to see it when I search…

Thanks

:smile_cat:

It’s from November last year but I used it not often (maybe 20 hours total). Now i built an enclosure and could start and now I have this f…ing problem :frowning:

“Pn” is the output. You use standard ? to show status report which includes the Pn.

I’ll do these tests tomorrow because now it’s late and i have to work tomorrow.
Thank you all for your support!
Markus

Probably why I had difficulties… Thanks…


My grbl isn’t cooperating… $10 was 0

Grbl 1.1f [’$’ for help]
[MSG:’$H’|’$X’ to unlock]
[MSG:Caution: Unlocked]
ok
$10=16
ok
?
<Idle|WPos:0.000,0.000,-67.500|FS:0,0>
ok
$10=31
ok
?
<Idle|MPos:0.000,0.000,-67.500|Bf:15,127|FS:0,0>
ok


1.1f is that an issue?

It would be nice to be able to drive this… :frowning:

:smile_cat:

My understanding is that the dynamic status fields were introduced for 1.0 or 1.1 so you should be good in terms of version.

Try $10=3 or $10=255 to see if that makes a difference.

No difference…

$10=31
ok
?
<Idle|MPos:0.000,0.000,-67.500|Bf:15,127|FS:0,0>
ok
$10=255
ok
?
<Idle|MPos:0.000,0.000,-67.500|Bf:15,127|FS:0,0>
ok
$10=3
ok
?
<Idle|MPos:0.000,0.000,-67.500|Bf:15,127|FS:0,0>
ok

Bummer…

:smile_cat:

Hello to all.
Here are the results of the commands you wrote above:


$I

[ORIGIN: China]

[PRODUCER: ORTUR]

[AUTHOR: ORTUR]

[MODEL: Ortur Laser Master 2 Pro S2]

[OLF: 187]

[OLH: OLM_ESP_PRO_V1.2]

[SN: 8C58C60322A40FAC8E48A369AFXXXXXXXXXX]

[OLM:GENERAL]

[DATE:17:26:04 - Dec 15 2021]

[VER:1.1f(ESP32).20210403:]

[OPT:VNMZHSL,35,7680,3]

Target buffer size found

ok

$$

$0=5.0

$1=100

$2=0

$3=6

$4=7

$5=7

$6=1

$10=2047

$11=0.050

$12=0.002

$13=0

$14=6

$15=0

$16=1

$17=4

$18=0

$19=0

$20=1

$21=1

$22=1

$23=7

$24=600.000

$25=3000.000

$26=100

$27=3.000

$28=0.100

$29=0.0

$30=1000.

$31=0.

$32=1

$33=1000.000

$34=0.000

$35=0.000

$36=100.000

$37=0

$39=1

$40=1

$41=0

$42=1

$43=1

$44=3

$45=0

$46=0

$56=1.000

$57=1800.000

$58=395.000

$59=6000.000

$60=0

$61=0

$62=0

$63=3

$64=1

$65=0

$100=80.000

$101=80.000

$102=2124.000

$110=10200.000

$111=10200.000

$112=600.000

$120=2200.000

$121=1800.000

$122=200.000

$130=400.000

$131=400.000

$132=100.000

$259=0

$260=70

$261=0

$262=400

$263=30

$264=0

$265=50

$266=100

$267=0

$268=0

$269=0

$270=5120

ok

$#

[G54:0.000,0.000,0.000]

[G55:0.000,0.000,0.000]

[G56:0.000,0.000,0.000]

[G57:0.000,0.000,0.000]

[G58:0.000,0.000,0.000]

[G59:0.000,0.000,0.000]

[G59.1:0.000,0.000,0.000]

[G59.2:0.000,0.000,0.000]

[G59.3:0.000,0.000,0.000]

[G28:0.000,0.000,0.000]

[G30:0.000,0.000,0.000]

[G59.6:0.000,0.000,0.000]

[G92:0.000,0.000,0.000]

[HOME:0.000,0.000,0.000:0]

[TLO:0.000]

[PRB:0.000,0.000,0.000:0]

ok

?

<Idle|MPos:0.000,0.000,0.000|Bf:35,7679|FS:0,0|Pn:PXY|CL:0,100|PS:2,1|ER:0,0|WCO:0.000,0.000,0.000|VA:24064,0|Ov:100,100,100|A:S>

[GC:G1 G54 G17 G21 G90 G94 G49 G98 G50 M5 M9 T0 F6000 S0.]

ok

Any ideas?
Markus

This shows that both limit switches are triggered. Can you disconnect the limit switches and rerun ?? Hopefully that goes to “Pn:P” without the XY.