Running 2 instances of lightburn on M1 mac

I changed one of my lasers over to rotary and now the other one won’t run on absolute. Keeps crashing into the rails. I loaded the default machine settings, turned off enable rotary and it still crashes. Now I’m forced to run on user origin. Help. I swear it has something to do with the .ini file. I haven’t even had a chance to check the rotary setup on the other one that was working just fine. They were both running without a rotary. Do I have to have a separate Mac for each machine or what?

LightBurn shouldn’t crash.

If you’re willing, please post the crash report and the support data from each instance of LightBurn running.

To generate the Support data, Click help, then click Generate Support Data. The information will be in the copy/paste buffer. Return to the Forum and paste the support data in a reply here. Each instance should have unique support data.

Rotary or not, I have not seen any previous report or comment on separate instances of LightBurn interfering with each other.

Thank you. I will do further investigation and keep you informed.

1 Like

I just read your reply again. Lightburn isn’t crashing my laser is hitting the rails and crashing. When I try to frame it goes to the front end of the machine and hits the rails. My limit switches are right rear. Something got messed up in the Grbl I think. It just doesn’t seem like the 2 lasers are running independent from each other. I’m probably doing something wrong but that’s not unusual.

You can ask the engraver for the GRBL settings by entering the following request in the console Window:
$$
then press enter.
The symptoms you’re describing may be caused by a Workspace Coordinate Offset which can be seen by entering the following in the Console window:
$#
then press enter

You can also reset the controllers GRBL settings to the factory defaults with a command in the Console window:
$RST=*
then press enter.

If you request both reports, reset the GRBL controller and request the reports again you’ll see a difference if that’s what was messed up. If there is no difference in the reports the issue is likely elsewhere.

Any custom settings in the controller will be lost, so it’s a good idea to copy and paste the report somewhere safe before resetting.

If you copy and paste the reports into a reply here I’ll have a look.
This sounds like an interesting problem.

I found the problem. Rookie mistake. I was so preoccupied with working origin I missed the job origin. Thank you for your reply. MyBad.

1 Like

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