When homing Ortur LM2Pro goes to bottom left corner but LB reports it is at -395 x -395

After removing rotary device and rewriting default setup to controller, Ortur LM2Pro homes normally (0,0) at bottom left corner but LB reports it is at -395, -395. When I try to center on grid (200,200) or click on origin it goes to top right corner and LB reports “out of workspace” error and 23,26 or other coordinates close to that. Seems inconsistent. Can’t do anything at center of grid. Can do a coaster at home if I change origin to user instead of absolute coordinates.

Try this, enter into the console this line:

$RST=#

That should zero out any work co-ordinate offsets that may be interfering.

Tried the code you gave me. Got the same results. Now however, when I try to move the laser to the workspace center it hits the hard stop at the top right corner and consistently reports 19,19 when I “Get Position”. Still reports -395,-395 when I home the laser at bottom left.

Can you run these commands in Console after a homing operation and return output:

$I
$$
$#
?
1 Like

[DATE:11:19:45 - Sep 1 2021]
[VER:1.1f(ESP32).20210403:]
[OPT:VNMSL,35,1024,3]
Target buffer size found
ok
$$
$0=5.0
$1=100
$2=0
$3=2
$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=0
$21=1
$22=1
$23=7
$24=600.000
$25=3000.000
$26=100
$27=5.000
$28=0.100
$29=0.0
$30=1000.
$31=0.
$32=1
$33=750.000
$34=0.000
$35=0.000
$36=100.000
$37=0
$39=1
$40=0
$41=0
$42=1
$43=1
$44=3
$45=4
$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
$259=0
$260=70
$261=0
$262=230
$263=30
$264=0
$265=100
$267=0
$100=80.000
$101=80.000
$102=400.000
$110=10200.000
$111=10200.000
$112=1200.000
$120=2200.000
$121=1800.000
$122=2200.000
$130=400.000
$131=400.000
$132=50.000
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]
error:7
EEPROM read failed. Reset and restored to default values.
ok
$
[HLP:$$ $# $G $I $N $x=val $Nx=line $J=line $SLP $C $X $H $B ~ ! ? ctrl-x]
ok

Can you try running the commands again, there’s some missing information and some of the commands may not have been run.

Can you make sure to cut and paste each command one at a time please?

$I

[ORIGIN: China]

[PRODUCER: ORTUR]

[AUTHOR: ORTUR]

[MODEL: Ortur Laser Master 2 Pro S2]

[OLF: 183]

[DATE:11:19:45 - Sep 1 2021]

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

[OPT:VNMSL,35,1024,3]

Target buffer size found

ok
$I

[ORIGIN: China]

[PRODUCER: ORTUR]

[AUTHOR: ORTUR]

[MODEL: Ortur Laser Master 2 Pro S2]

[OLF: 183]

[DATE:11:19:45 - Sep 1 2021]

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

[OPT:VNMSL,35,1024,3]

Target buffer size found

ok

$$

$0=5.0

$1=100

$2=0

$3=2

$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=0

$21=1

$22=1

$23=7

$24=600.000

$25=3000.000

$26=100

$27=5.000

$28=0.100

$29=0.0

$30=1000.

$31=0.

$32=1

$33=750.000

$34=0.000

$35=0.000

$36=100.000

$37=0

$39=1

$40=0

$41=0

$42=1

$43=1

$44=3

$45=4

$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

$259=0

$260=70

$261=0

$262=230

$263=30

$264=0

$265=100

$267=0

$100=80.000

$101=80.000

$102=400.000

$110=10200.000

$111=10200.000

$112=1200.000

$120=2200.000

$121=1800.000

$122=2200.000

$130=400.000

$131=400.000

$132=50.000

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:-395.000,-395.000,0.000:3]

[TLO:0.000]

[PRB:0.000,0.000,0.000:0]

ok
?

<Idle|MPos:-395.000,-395.000,0.000|Bf:35,1024|FS:0,0|Pn:PS|CL:0,100|PS:2,1|ER:0,0|VA:23726,0|Ov:100,100,100|A:S|H:0>

ok

You’re running a very old version of the firmware. This version allowed the negative coordinate situation that you’re seeing.

I suggest you update the firmware. That alone should fix the issue. If it does not, then issue $RST=* to reset all your settings to default.

Ortur – Firmware Repository – Ortur

Updating firmware to latest (1.90) fixed it. Took no further action.

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