Due to getting involved in Fiber Lasers my 4 diode laser have been in hibernation for about 3 months. Today with a temperature under 30c for a few hours decided to check the diodes! before shutdown, all were working without issues.
Today - I setup up a test burn - all set, hit frame the module moved fast to the material and stopped… but the progress bar in LB 1.5.0 2 still showed and a time rundown. Hit the stop -needed a few, but when stopped…Home and it did! frame showed that tarvel from to back OK and X from left front to around mid workspace so its not motors, belts . this start and stop routine went on for over an hour during which I had error 9 show and later error 1 - which a YT video indicated the bed size was usually the cause. I had used an HP win 10 laptop - no fiber or ezcad “litter” getting involved. I resized the work space - a few times each down by 5mm at 350 x 350 I give up. After the last Homing hit start and the laser fired uo and set about the image in the normal way.
I took opportunity while out out of its enclosure to check and adjust the Y belts which I do by having taped the X rail up against the front stops, after which I tried the framing again after trying 410 x 410 which I read on YT and 398 x 398 - in hope but to no avail! Summary. Apart from running around the outline framing - everything else seems OK and functional. Advice on a cure for that issue will be welcomed 
Error 9 is based on error 1
Could you power on your ortur and export the full console contents when you plug it in.
I am assuming of course ou checked the basics
Key, emergency switch and also checked that the main harness is still fully plugged on the motherboard?
Sent emails with the console text from three runs!
For readers…also fired up my olm2 pro …amazed to find it has the same issue!. Assuming LB at odds 1.5.01 and 02 versions. Uninstalled trashed the downloads…
This was from HP win 10 laptop.
downloaded 1.5.0 1 installed on my second win 11 laptop. Devices “ saw” the olm3 and its installed, The Olm2 was manually added…
Checked out both lasers….no change.
Opened an old GRBL app v5 ? It got a pop up to update…soI did! I know little about it but connected the Olm3 then blundered through adding an image…then hit the framing…Olm3 behaved itself and framed the image!
Ditto olm2. Which seemed to indicate an issue with LB After 5 hours I needed a lunch brake! Now over and going back to look through….GRBL .
Sorry Gil for the reams of console stuff.
Current before leaving out getting hotter garage was Alarm 11!
sent email to whom. Ortur support?
i no longer have access to those.
3rd after reinstalls and checking! Waiting for connection…
Port failed to open - already in use?
Waiting for connection…
Waiting for connection…
ok
[ORIGIN: China]
[PRODUCER: ORTUR]
[AUTHOR: ORTUR]
[MODEL: Ortur Laser Master 2 Pro]
[OLF: 170]
[DATE:19:08:08 - Jul 12 2021]
[VER:1.1f(ESP32).20210403:]
[OPT:VNMZHSL,15,1024,3]
Target buffer size found
ok
Homing
ok
ALARM:1
Hard limit triggered. Machine position is likely lost due to sudden and immediate halt. Re-homing is highly recommended.
[MSG:Reset to continue]
Ortur Laser Master 2 Pro Ready!
OLF 170.
[MSG: Flame detector active,Ambient infrared value:0]
Grbl 1.1f [‘$’ for help]
[MSG:‘$H’|‘$X’ to unlock]
[MSG:Emergency switch Engaged!]
error:18
[MSG: Emergency Switch Engaged.]
[MSG:Emergency switch Cleared.]
[MSG:Emergency switch Engaged!]
Ortur Laser Master 2 Pro Ready!
OLF 170.
[MSG: Flame detector active,Ambient infrared value:0]
Grbl 1.1f [‘$’ for help]
[MSG:‘$H’|‘$X’ to unlock]
error:18
[MSG: Emergency Switch Engaged.]
ok so few things
a) Your firmware is olddddd
https://ortur.tech/latest-firmware/
Suggets update to 1.78
Firstly though in console type
$RST=*
Press enter
And when machine responts with : MSG: retoring defaults
Tap reset to power it off
https://ortur.tech/firmware/OLM_Series/OLM2_PRO_S1_Firmware_Release_1.78.zip
b) hard limits shouldnt be enabled, so you been fiddling with the settings. BUt above steps will fix that
c) could you send a image of your Edit → device settings?
Machines in garage…no windows = no sum or brightblights.
Flame detector! Had tape on the olm2 sensor cover on the front , literally for over two years!
The Olm3 has never had a flame detection error shown.
Whatever the cause, Grbl Laser did not get problems and both lasers framed OK!
Sorry about email replies! Replied to your email!!
The x movement on framing still happens…moving right at …guessig o.5mm /1 second!! But if I hit start…it will start a full movement burn!
OLM3 has no flame sensors so that explains it
Again if you wrote to old ortur emails i no longer have access
To understand if i got it correctly.
You have a issue on X as it bounces back after homing?
Make sure there is no cable/Tubpe or similar thats tugging the X back, once homing stops the motors lose energy so anything can move them
Full movement burn, meaning all went ok?
Do update firmwares though as instructed
Latest update!
I have an Xtool Di Pro 10w. It, like my other diode lasers has not been used in 6 months!
This morning wired it up and setup to do a job.
Turned on….it homed as it would normally…this after Lighburn devices found the laser on my HP win 10 laptop.
Image in LB a simple 20mm circle centre of the work area. I hit frame. It does exactly the same as the two Ortor, ie travels to the burn start point and stops…no framing. Same on Win 11 laptop.
Todays plan!
Uninstall current 1.5.0 1 Lightburn, upload an older version….if the same result, drag my mini Mac and monitor to the garage to test if its basically a lightburn problem…other than that ….no idea!
Lot of fuss over a couple of lasers having hiccups!
Having speny best best part of a collective of 24 hours and the two Ortur .,: %@$=& ing lasers refusing to frame which change to framing at 0.5mm a minute…movement hardly see, but felt after placing fingers on the X belt!
I spent another…wasted 5 hours this morning trying more or less the same not working idea’s. Gave up fired up the Fiber and cleaned up some not used in years spanners! After a late lunch…back in the garage and reading ( but not understanding ) the console info saved for Gil a repeating “ issue” seen, indicating front stops not found where expected or words similar!
So opened devices manually set about a new OLM2 profile bed size 400 in the first time the Find my Laser has worked. But using idiot logic…if the front stops were not found on the firmware Radar were they farther away…or to near…I guessed lol,the were too near!!
So I made the work area 410 x410.
Turnd the laser on, hit Frame…lo and behold… off shot off the module and danced very smoothly around the 20mm line circle on the centre spot it stopped I hit start…it did and no expected crashing into the rails.
I have no idea on not supposed to have changed settings apperently curing the issue! Wife thinks we have fairies in the loft and came down in the night to help me! I will go with that tomorrow its the OLM 3 getting set up the same, ya’ll will no if I do not come back here!
Not the bounceback on homing Olm3 other than mine have mentied that since it came on the market.
My problem was wired up and connected to Iightburn 1.5.0 2 which had been working OK. Hit Frame…the module moved to the burn start point and stopping no actual frame indertaken.
However Inhave posted to day as that I Found the cure…not by brain power I add! Taking the console info and seeing…the front stops were not found…whatever that means…But I took it literally and tried to force the stops getting wacked…so I ……the answer and solution is in what I thought was my last comment on the issue
we might need to go into basics here
a) Latest lightburn 1.5.02
b) what OS, please open your windows menu > type run > type winver in the box and take screenshot
c) Right click windows menu > click device manager
Expand ports and disks section, and power on and plug in your OLM3
Take picture WITH OLM3 Plugged and with it unplugged
d) launch lightburn → go to EDIT → SEttings (Take screenshot) Edit > device settings (Take screenshot)
If possible, move head to cente,r pwoer on olm3 and record in video its homing, upload to youtube maybe
Also take images of both your belt tensioners and your main cable haness connectors
Thanks Gil, it seems a reply I made yesterday has been bypassed or maybe just lost in the list, it explained …how I got both lasers to Frame a test image!
I recalld the console notes pointed out the …Front Stops had found where expected…or similar wording.
It means nothing to this simpleton, however I decided to add more confusion re the front stops by extending the location, expecting the laser to stop when at the edge of the 400mm x 400 m, work area noted in the lightburn device settings. I changed the setting to both lasers as an edit to the device settings, from 400 to 410 x410mm.
Started the Frame function in LB using an image rather than a square in line mode.
Both lasers framed as per normal and no reaction to the extended work area.
Both are still working normal.
But nothing for me stays normal too long!!
Using xtool XCS i set about checking the firmware…response was advice to update. My reliable Xtool update managed to cripple the machine, guessing a glitch in the update corrupted what had loaded or stopped the update from completing…which ever the board is dead, ditto my spare when installed today!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.