Multiple errors on ortur LM2 non pro after updating from legacy softwqre to newer 1.7.07 and 08

My ortur laser master 2 non pro 20 watt (5 watt output) laser has been working great until recently updating lightburn. On version 1.7.07 and the newest 1.7.08 i am now getting multiple halt codes. I am using the exact smae USB cable I have been using for the last 4 years with no issues(i am switching it out). I am getting the 2 following codes randomly.

I have even saved my file in the old legacy .LBRN format to see if it was the way its saves and still same issues. i have switched out the USB with a new one just in case and same issue

Thanks

error:9 Shock and Movement detected!]
Ortur Laser Master 2 Ready!

error:24

Two G-code commands that both require the use of the XYZ axis words were detected in the block.

On or near line 0:

Job halted

With a brand new shielded cable

Starting stream

Layer C00

error:24

Two G-code commands that both require the use of the XYZ axis words were detected in the block.

On or near line 0:

Job halted

Same exact errors

ok, tried a 3rd cable, no go. Firmware is fully up to date
 not sure whats going on. its random too

[AUTHOR: ORTUR]

[MODEL: Ortur Laser Master 2]

[OLF: 142]

[DATE:18:41:30 - Dec 15 2021]

[VER:1.1h.210324:]

[OPT:VNZHI,99,512]

Target buffer size found

ok

Homing

ok

$RST=*

[MSG:Restoring defaults]

ok

Ortur Laser Master 2 Ready!

OLF 142.

Grbl 1.1h [‘$’ for help]

Project loaded in 4 milliseconds

Starting stream

[MSG:Pgm End]

Stream completed in 0:06

<Idle|MPos:199.150,218.163,0.000|Bf:99,511|FS:0,0|Pn:P|WCO:0.000,0.000,0.000>

ok

Starting stream

Stream completed in 0:12

<Idle|MPos:199.150,218.163,0.000|Bf:99,512|FS:0,0|Pn:P|Ov:100,100,100|A:C>

ok

Starting stream

Stream completed in 0:12

Starting stream

[MSG:Pgm End]

Stream completed in 0:00

Starting stream

[MSG:Pgm End]

Stream completed in 0:03

Starting stream

[MSG:Pgm End]

Stream completed in 0:03

<Idle|MPos:199.150,218.163,0.000|Bf:99,512|FS:0,0|Pn:P|WCO:0.000,0.000,0.000>

ok

Starting stream

Stream completed in 0:12

<Idle|MPos:199.150,218.163,0.000|Bf:99,511|FS:0,0|Pn:P|Ov:100,100,100|A:C>

ok

Starting stream

Layer C00

error:24

Two G-code commands that both require the use of the XYZ axis words were detected in the block.

On or near line 0:

Job halted

Interesting, do these problems go away if you re-install the version you were previously running? Was that 1.7.06?

Even this issue?;

[Shock and Movement detected!]

I’m not sure how the software upgrades could cause this particular problem, but anyhow, here are some things to check:

-Make sure your laser machine is mechanically sound, clean any clumps of gunk off the roller wheels and guide tracks making sure you have smooth movement

-It might help to use brackets to fix the laser to the workbench.

-Reduce the speed does that help?

I didn’t even know that model had a shock sensor.

If the shock sensor is suddenly faulty or too sensitive you might be able to disable it or increase the triggering threshold which is in the $ code settings, on my machine (the LM2 Pro S2) I think it is $262 but I have different firmware - not sure what it is for your model ( I can’t find a firmware page for your controller model), so you might have to ask Ortur). @gilaraujo might know.

[error:24]

If this is related to the software upgrade then it should be predicable and not so random.

Run a test job at very low power only enough to lightly mark some test material.

For the test, enable ‘Synchronous’ mode (Edit > Device Settings);

And in the Console Window enable ‘Show All’;

When you start the job now it should now stream it to the laser one line at a time, so you can follow the job activity in the Console Window as it happens.

I’m hoping that by drip feeding the laser this will show us in a very consistent way the detail of any malformed GCode that the laser is choking on - or conversely show that the error is happening randomly in spite of receiving valid gcode.

So basically, if the job fails, look in the Console Window, and copy/paste here any errors you see and also observe where the job actually stopped, mark that position then run the same job again and see if the same error happens in exactly the same place.

1 Like

Can you confirm there is no “G-code cluster enabled” on Edit > Device settings?

This was one of the first 3 things i checked. It is off, as well as any z axis options.

Yes, these issues were not apparent in earlier versions. It was running great the other night doing 3 hour burns of anything. Last week it was great. I was on version 1.7.04 i think. Its been about 6 months since i updated, maybe a little longer.

Then i updated to .07 and got the error code for shock and movement. Used $33=750 and that seemed to help last night with that error but now i randomly get the error 24. I was able to run a 24 minute job multiple times, but if i switch yhe scan angle to 90, it SEEMS to fail more often. Updated to 08 and same thing

Sometimes it can run a job for more than 20 minutes, sometimes not.

It failed last night at the following time stamps

11 minutes into the burn
45 min
23 min
8 min
45 min

Always the same error.

Laptop issues with usb port? Lack of power? No idea.

Maybe the 3 shield cables i have suck but they worked for hours and hours before the updates

I am now currently testing the machine as per your recommendation. I am at 20% power and 3000mm/min using synchronous transfer. i really hope it fails because if it doesnt. im gonna be mad hahaha

ok, so with the lower power, and i turned off the cutting layer (turned off output switch) it worked. I wonder why? I am going to try again but with regular settings and cutting

Waiting for connection


ok

[AUTHOR: ORTUR]

[MODEL: Ortur Laser Master 2]

[OLF: 142]

[DATE:18:41:30 - Dec 15 2021]

[VER:1.1h.210324:]

[OPT:VNZHI,99,512]

Target buffer size found

ok

Homing

ok

Project loaded in 4 milliseconds

Starting stream

[MSG:Pgm End]

Stream completed in 0:06

<Idle|MPos:199.150,218.163,0.000|Bf:99,512|FS:0,0|Pn:P|WCO:0.000,0.000,0.000>

ok

Starting stream

Stream completed in 0:12

<Idle|MPos:199.150,218.163,0.000|Bf:99,511|FS:0,0|Pn:P|Ov:100,100,100|A:C>

ok

Starting stream

Stream completed in 0:12

<Idle|MPos:199.150,218.163,0.000|Bf:99,512|FS:0,0|Pn:P|Ov:100,100,100|A:C>

ok

Starting stream

[MSG:Pgm End]

Stream completed in 74:11

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