Console commands not working

LightBurn Software Questions
1

Running a Genmitsu LC-60A on Win 10. Have had no problem burning projects until today,
Laser seems to be connected, all cables good. It will load the project but then no commands from the Laser tab will work.
Console code is

Waiting for connection…

Waiting for connection…

Grbl 1.1f [‘$’ for help]

[MSG:‘$H’|‘$X’ to unlock]

error:9

G-code locked out during alarm or jog state.

[MSG:Caution: Unlocked]

ok

Homing

[VER:1.1f.20170801:]

[OPT:V,15,128]

Target buffer size found

ok

ALARM:9

Homing fail. Could not find limit switch within search distance. Defined as 1.5 * max_travel on search and 5 * pulloff on locate phases.

ok

Grbl 1.1f [‘$’ for help]

[MSG:‘$H’|‘$X’ to unlock]

[MSG:Caution: Unlocked]

ok

Project loaded in 3 milliseconds

I have not changed any settings or setuo since it was working. What am i missing here?

Thanks
JT

2

Is the laser plugged in and getting power from the power supply?

3

Yes, it is plugged in. It will fire manually, and it will home manually. It just isn’t recognizing commands from the computer, from lightburn.

4

How are you doing this?

Not following you on this. The message you included shows communication.

Can you take a full screenshot of LightBurn with Laser window showing?

5

First, the LC-60A has a control panel. It has an on/off switch and a fire/home switch. All functions work from the physical control panel–the laser fires, and it will home to the front left corner.

Home, frame, and start from the Lightburn Laser panel have no effect. I have considered that maybe the Com port went wonky, but can’t find anyplace in Lightburn to address that.

Picture included as requested.

Thanks

20230811_141112
20230811_1411121920×1440 119 KB

6

If you click the Port field in Laser window (currently showing “Auto”), what shows there? Can you select the specific COM port for your laser?

If that doesn’t change anything, try right-clicking on Devices button. That should force a reconnect.

Copy and paste all text in Console from the time that you change the COM port.

7

Yes! That did it! I had forgotten where the Com Port selection was, but changing it from Auto to Com 4 did the trick! Thank you so much!

1 Like
8

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