Problems after latest uppdate

LightBurn Software Questions
1

First off , thank you so much for a fantastic software , bought my licenses after testing for 3 minutes :slight_smile:

I’m using the Lightburn on my china laser 3018 pro as im waiting for my co2 running Ruida.
since the last upgrade the laser isn’t so easy to use anymore , it seems lightburn send some 'gcode in the startup.

Waiting for connection…
Waiting for connection…
Port opened, waiting for response.

88<<88888888<<8888888<<88888888<<88888888<<8888888<<<8888888<<88888888<<88888888<<8888888<<<8888888<<88888888<<8888888<<<8888888<<88888888<<88888888<<8888888<<<8888888<<88888888

This in turn starts my Z axes down and starts the laser !! the maschine don’t respond to any commands in this state.
What i have found that helps sometimes is to start the lightburn software some minutes before i turn on the laser and attach the cables.

2

What firmware and what version of the firmware are you running? OS? Version of LightBurn?

3

Sorry should have included that , LB 9.0.2 ,GRBL 1.1, Windows 10

4

GRBL 1.1 with which letter afterwards?

See exactly what it says in Console when you connect, and or try sending $N in console to see the response.

5

Do you have a “Baud Rate” setting in the device settings? If so, check what it’s set to - the standard is 115,200, but it’s possible your machine either wants something else, or isn’t set to that.

6

The baud rate was set to 115,200 and it is the hz i use if i connect it to Laser Grbl .
Still stuck in the hospital so not able to read of the maschine settings , but it was flashed about 4 months ago with whatever was the newest at the time.

7

Grbl 1.1f [’$’ for help]

8

What device have you chosen in LightBurn? (I’m assuming just “GRBL” but I want to make sure)

9

yes you assume correct , but i have also tried the other ones

10

LightBurn doesn’t send anything on startup (aside from a couple of “enter” keypresses, to get the laser to respond). Check to make sure you don’t have anything like a loose electrical connection or cable, as that could cause this too.

This is a link to the 0.8.07 installer: https://drive.google.com/open?id=1itxn4DeCsb93gk8fDqPfm5TEy1Tvh3mL

If you can try it and verify that it still works properly, that will tell me that it’s definitely something that’s changed in the comms.

11

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