I used my AlgoLaser Delta two days ago and had zero issues. I did the update to 1.7.08 yesterday, and now every job I run gives me “error:9 G-code locked out during alarm or jog state” I’ve gone over everything, so now I’m wondering if I can revert back to the previous version to see if the problem persists.
And by the way, after the past three updates, I’m still getting “Cut may be out of bounds” warning - even though nothing is out of bounds.Oddly, that warning only shows up one time: when I fire up LB and start the first layer/burn. After that, it disappears until I shut the machine off, or start a new job, without fail. That also began after an update, when using the machine the day before without any issues. thanks.
You can download any previous version from the site linked below, however, before you do that, try loading a preferences file from before the update and see if that solves the new issue. File Menu> Preferences> Load Prefs Backup.
Thanks, but nothing is out of bounds - even when previewing the ‘green box.’ I can open previously saved files that ran just fine prior to that update - when I import them into LB, I get that message. But as I stated: Only when I start a job for the first time, & I only get the message one time. I can click [proceed anyway] and the job runs just fine. Once it’s done, I can load another 12x12 and start the same job and I do not get that message.
This started after an update, I used the machine to cut a file the day before, and no problems at all. I ran the update, now it shows up when I start a job. I am using the exact same setup I have been using for 5 years with 4 different machines; I do not want to change the settings that I’ve used successfully for five years, because it works for me. It’s how I have my cutting area set up: I start the job from “current position” which is always at 200,200 - right in the center of the job like I’ve always done.
Thanks, I had seen others post a link to previous versions, but that didn’t have up to date info, this does. I tried as you suggested: I loaded preferences from about a month ago, ran the job, and I still get the ‘out of bounds’ warning, but I was able to run the entire job without error:9.
The interesting thing is that I have been using this machine for a couple of years and I like my settings - I don’t know enough to change them, so I leave everything alone because it works. So I’m not sure why after the last update errors began occurring. Seems to run the job fine now. who knows…
Something that “might” help figure out the out of bounds problem is a few screenshots since we’re not looking at your compute. Post a screenshot (not a cell phone pic) of your entire Lightburn screen with your project loaded and the Cuts/Layers Panel and Laser Panel visible. Also post a screenshot of the Settings Window (Gears icon) with the Units and Grids tab visible, the Settings Window with the Editor Settings tab visible and a screenshot of the Device Settings Window (Wrench and Screwdriver icon).
Sorry, I’ve already gone through all of that with LightBurn directly, and they couldn’t figure out why. I mentioned it in case others have discovered the same/similar issue, and can chime in. That’s why I didn’t post a screenshot, I actually sent a video to LightBurn showing exactly what happens.
Thanks, but I assure you, nothing is out of bounds unless it procreated by itself a mile from my home and won’t fit on the screen. lol But, as I mentioned, jobs that ran perfectly fine the day before now get that message when I try to run them the first time - and it doesn’t matter which of the 11 layers I select first.
Well, I guess I spoke too soon… the error: 9 is back. I’m just going to revert to the version I had last week and see if it goes back to normal. Maybe I should revert back to the version I had in December… none of these problems existed then. lol thanks
well, that didn’t work. I’m tired of this crap. maybe time to get something else. Ortur was horrible, now AlgoLaser is giving me fits and it’s the same people as Ortur, so maybe I’ll try a different brand, I’m getting tired of it working one day, then the next… errors.
A quick Google search shows alarm 9 on Ortur is usually shock or movement detected. It could be the sensor is going bad and acting too sensitive. I would try disabling the sensor and see what happens.
Changing Lightburn version will likely not solve the issue.
I guess I’ll try that, I thought it was fine. Weird how it can complete a 5400mm/m burn, then at 300mm/m it stops and gives me the error. Not sure how to disable the shock sensor, I tried $262=0 and got an error:53 setting not available. Any thoughts on that? thanks.
Well, who knows… I did all of these, updated again, checked the plugs… now it’s working like before, and I’m not getting the “out of bounds” message like before. But now that I’ve posted this, it will start playing games with me again. thanks
I have also been receiving the message that it is out of limits in this latest version (1.7.0.8), it happens in texts and there is nothing out and it records normally and in files that I used before and had no problems with being out of limits