Comgrow Z1 20w won't burn work LB

I cannot seem to get my Comgrow Congo z1 20w to work with Lightburn. The laser Homes properly, moves about the workspace properly (the up and down arrows are reversed but that’s easy to deal with) and it rames the image properly. When I start thee job, the laser moves the the start position, fires the laser for a half a second and then stops.

I’ve tried the $33=1, and that did not work. I’ve adjusted the baud rate with DTR signal toggled on and off for all baud rate options. My machine only responds at 230,400.

The Laser seems to function fine with laserGRBL.

Please help. I like your software and don’t want to have to learn am entirely different program.

Thank you so much

Why deal with this when it can be addressed? Most likely this is caused by a bad machine origin setting. in Edit->Device Settings make sure that origin is set to bottom-left dot.

What was this anticipated to change? What was the previous value?

Can you provide the following:

  1. Full screenshot of LightBurn with your design loaded and ready to burn.
  2. Screenshot of Edit->Device Settings
  3. Run the job, then capture any messages in Console and return here.
  4. Go to File->Save gcode, save the file with .txt extension, and upload here.

The up down arrows were fixed by your suggestion. Thank you!

As far as the rest

Waiting for connection…
ok
[VER:V2.4.20230625:$I]
[OPT:VZL,15,128]
Target buffer size found
ok
Homing
Project loaded in 192 milliseconds
ok
Starting stream
Layer C00
error:20
Unsupported or invalid g-code command found in block.
On or near line 0:
Job halted
Stream completed in 0:00
ok
ok
ok
ok
<Idle|MPos:202.438,171.550,0.000|FS:0,0>


Processing: 2.jpg…Processing: 1.jpg…

7Soul QR Code.txt (480.9 KB)

You say you’re using a Comgrow Congo Z1 but you’re using a device profile created for xTool D1 Pro.

The root issue is that there is custom user gcode enabled for the xTool that doesn’t work for the Comgo.

Is there a reason why you’re doing this?

When I select the Comgrow, it just sends these lines of code through the console window on an endless stream.

I can use both operate both machines by changing the com. The xTool D1 works fine. The Comgrow seems to do everything except the actual job. The “fire” button on the “move” window also works just fine, as well as the laser being on while framing the image.

Here is the console window, upon initial start up, with the xTool (com7) first, then swapping to the Comgrow (com8).

Waiting for connection…
ok
ok
ok
[XTool D1:ver 40.30.002.01 B1]
Homing
ok
start_home x
set_SGTHRS x (50)
enable x limit
x limit trigged
start_home y
set_SGTHRS y (50)
enable y limit
y limit trigged
MPos:0.000000,0.000000,0.000000
Waiting for connection…
ok
[VER:V2.4.20230625:$I]
[OPT:VZL,15,128]
Target buffer size found
ok
Homing
ok

If I select the Comgrow at all, it just cycles that code from the first picture, and is unrepsonsive.

I appreciate your help. Thank you so much.

The combination of com8 and Comgrow sends those lines of code.

The combo of com7 and Comgrow just waits for the connection. Anytime I select the xTool D1, it automatically changes to com7. If I select the Comgrow on com7, it shows this in the console window.

[XTool D1:ver 40.30.002.01 B1]
ok
start_home x
set_SGTHRS x (50)
enable x limit
x limit trigged
start_home y
set_SGTHRS y (50)
enable y limit
y limit trigged
MPos:0.000000,0.000000,0.000000
Waiting for connection…
�So�����1�����o�����o�E��
o���DSo�����o����Jo�����3����
o�}��So�����o����Jo����So����So�����o����o�}��o����So����

With the Comgrow device profile selected please provide the following:

  1. screenshot of Edit->Device Settings
  2. Go to File->Save gcode, save with .txt extension, and upload file here

I got it! The profile for the Comgrow had a bad baud rate. It didn’t occur to me that each device would have a different profile like this.

Both machines are working great! Thank you so much!!

If this $$ parameter is valid for your controller, it should be 1000, not “1”.

Can you confirm this is correct for your controller? Usually 115200 is used. Higher speeds see more communications errors.

What baud rate does it communicate with in LaserGRBL?

In the Device Settings window, do you have Enable Gcode Clustering enabled?

This is definately a communications protocol issue. I suggest you review all the settings for the RS-232 connection, including a cable.

LaserGRBL baud rate is 230,400

Gcode Cluster is off

I’m not gonna mess with anymore settings. Both machines are working brilliantly right now and I’m not gonna risk it.

1 Like

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