A puzzling connection problem

I’m trying to connect Lightburn v1.4.05 running on Windows 10 to an Atomstack x7. This has worked in the past, but today the connection fails.
Windows Device Manager sees the laser, using driver USB-SERIAL CH340, and tells me this driver is up to date. In spite of what the device manager said, I swapped out the USB cable. I restarted Lightburn a few times. My original Lightburn device config worked in the past, but I created a new one - no luck. Windows USB selective suspend is disabled.

What can I try next?

Confirm that a COM port is being assigned to the machine when connected using Device Manager. Note the COM port. Then make sure that COM port is selected in Laser window in LightBurn.

The COM ports match. Should I be looking at the baud rate? This is a new problem since a Lightburn version update.

How did you create your new device?

Possibly but only if the device were created incorrectly.

This is likely a red herring.

Can you include screenshots of your troubleshooting efforts?

I may have been hasty in my earlier reply about COM ports. The only reference to a port I can see in the device manager is the title of the driver.
image
image

This should be sufficient. Do you have any other USB devices connected? Confirm that disconnecting the device removes COM3 and that reconnecting it recreates COM3.

Can you open the Console window? What do you see there? Please take a screenshot or copy/paste the content.

The connection failure happens with no other USB devices connected.
Console:
image
Laser connected:


Laser disconnected:

That’s interesting. Confirm that the device is indeed configured as “GRBL” by pushing Devices button, then click the name of your laser. The specific device type will be listed at the bottom of the window.

Additionally, can you take a screenshot of Edit->Device Settings?

Device type:
image
Device settings - I notice the baud rate doesn’t match the info in the driver:

Try toggling “Enable DTR signal” in Edit->Device Settings. From what I recall, your laser shouldn’t require that but worth a shot.

If that doesn’t work, can you try connecting with LaserGRBL?

“Enable DTR signal” doesn’t change anything. I DL’d LaserGRBL and hour or so ago and attempted a connection, but it failed also. I’m beginning to suspect the Atomstack. I’m completely ignorant about how connections are enabled on that end. Could this be a firmware issue?

That’s what I’m suspecting now. Either that or a hardware issue.

I’d suggest trying to reflash the firmware.

I am having the exact same issue. I had it working less than 24hours ago. Shut it off when I was done for the night and when I tried it again this morning it had the exact same issues as described above.

What OP is experiencing is fairly unique in terms of not working after remediation steps.

Have you worked through the same troubleshooting process as described in the posts?

Yup,
The drive says it is up to date, the COM port chosen matches what the device manager lists says, I have removed all other devices using a USB (only a mouse), every time I disconnect or power off the Atomstack it removes the COM option in Lightburn, device settings are the same as the screen shot, I have done the Enable DTR signal. And I cant seem to get it to connect to LaserGRBL (although I have not used the software much)
I have changed the COM port a few times and that gives the Port failed to open - already in use?
Not sure where to go from there. Is it possible the firmware on the Atomstack some how became corrupted?

It’s possible but this is almost always something else first.

Under what circumstances did it stop working? Are there other signs that could indicate root cause?

Does your laser have a reset switch? If so, may want to toggle that then do a full power cycle.

The emergency stop button was pushed down. Apparently that does not remove all power from the device (which I thought it did). Boy do I feel dumb

I got this working. I noticed the display on the laser was blank. I pressed the emergency stop button, released it and then pressed the reset button. All is good now.

salve, sto avendo gli stessi problemi con il mio eleksmaker, fino a qualche giorno fa funzionava poi una mattina non si connette più, ho fatto tutto quello che viene già spiegato in questo forum ma ancora non si connette, l’ho usato con un altro software e funziona bene, potrebbe essere effettivamente un problema di firmware, allora vi chiedo gentilmente, dove posso trovare l’aggiornamento per eleksmaker man se v3.2… grazie mille

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