Hi, New to Millmage I’m working with a 3018 pro my problem is as soon connect the machine to my computer the job control reads “Busy”. 100% never goes to ready. I have been able to design my work but cannot get the machine to go to the next step and perform “Frame” What am I doing wrong?
Hi Dennis!
Do you happen to have any other software open that could be maintaining the connection to your 3018 and not allowing MillMage to take control?
If you look to the Console window, is there anything reported there? Copy and paste it into your reply if so.
This is what it say’s on the console, Waiting for connection…
G0
G0
wt\x9A\xF0
Grbl 1.1h [‘$’ for help]
$I
check the comm port in windows “device manager’ under com ports, if you 3018 does not show up there; then did you install the usb driver? i assume you are running microsoft windows.
Hi, it does not say 3018 what it says is USB-Serial CH340 (com10). I have even tried using a different port reads the same. Also does the same in MillMage
should be able to communicate with the board if it s showing up in device manager, did you try the different GRBL selections? what board do you have?
I am actually working on that now I will get back to you
1 Like
This is showing Lightburn is actually talking to the controller. Otherwise, how would Lightburn know you are running GRBL 1.1h in the controller?
From the time you power up the laser and connect the USB cable, copy & paste everything in the Console window like @Colin asked.
Ok after two cups of coffee I approached this again, the board is a Nano, I tries to reflash it and I was able to make the Led’s flash. I then uploaded the latest sketch with success. closed the program and opened MillMage the job control reads Busy 100%, the console reads
Waiting for connection…
\x89\xE9BQ\xFF
Grbl 1.1h [‘$’ for help]
I’m stumped !
You have completely closed Lightburn with no other programs that could be connected?
What are your com port options?
Is this your first connection with Millmage?
It looks MillMage got a partially garbled response from G0 and is still waiting for a response from $I
Did you try toggling the ‘Enable DTR’ setting?:
The only programs open are device manager, this forum and MillMage and git hub.
I changed that setting. closed and reopened the program
I’ll do that and recheck,
Waiting for connection…
Grbl 1.1h [‘$’ for help]
Still no proper connection? looks like the DTS setting should be off.
Some other things to try:
Check the USB Cable:Troubleshooting: USB Cables - LightBurn Documentation
Try a different USB port: Troubleshooting: USB Cables - LightBurn Documentation
What happens if you try to connect using the factory supplied software that came with the machine?
Or, if you have a Chrome or Edge browser please try this tool:
Close MillMage.
Restart the machine.
Open this web page:
Click “Connect to device”, (at 115200 baud is fine):
Select a port and connect, for example:
Click ‘Copy log’, and then paste back here,
For example:
GRBL Diagnostic Log
Log name: grbl-diagnostic-manual-2026-03-30T14-12-22-896Z
Timestamp: 2026-03-30T14:12:22.896Z
Preset: manual
Description: Manual connect
Baud: 115200
DTR mode: default
Observe only: no
Port info: VID 0x303a · PID 0x4003
Source URL: GRBL Serial Diagnostic
[02:05:38] ● Selected port: VID 0x303a · PID 0x4003
[02:05:38] ● Connected at 115200 baud
[02:05:38] ● DTR control available
[02:05:38] ● Diagnostics mode: Manual connect
[02:05:38] ● Sending wake signal…
[02:05:39] → ↵
[02:05:39] ← ok
[02:05:40] → ?
[02:05:40] ← <Idle|MPos:0.000,0.000,0.000|Bf:35,7680|FS:0,0|Pn:P|CL:0,100|PS:2,1|ER:0,0|WCO:0.000,0.000,0.000|VA:24396,0|Ov:100,100,100|A:S>
[02:17:15] ● Disconnected
[02:17:24] ● Diagnostic test link copied to clipboard
GRBL Diagnostic Log
Log name: grbl-diagnostic-manual-2026-03-30T15-02-16-139Z
Timestamp: 2026-03-30T15:02:16.139Z
Preset: manual
Description: Manual connect
Baud: 115200
DTR mode: default
Observe only: no
Port info: VID 0x1a86 · PID 0x7523
Source URL: GRBL Serial Diagnostic
[10:59:32] ● GRBL Serial Diagnostic ready
[10:59:32] ● Open Chrome or Edge, connect your device via USB, then click Connect
[11:00:23] ● Selected port: VID 0x1a86 · PID 0x7523
[11:00:23] ✕ Connection failed during open: NetworkError - Failed to execute 'open' on 'SerialPort': Failed to open serial port.
[11:00:23] ✕ Disconnect cleanup warning: Failed to execute 'close' on 'SerialPort': The port is already closed.
[11:00:23] ● Connection attempt ended
[11:01:38] ● Selected port: VID 0x1a86 · PID 0x7523
[11:01:38] ● Connected at 115200 baud
[11:01:38] ● DTR control available
[11:01:38] ● Diagnostics mode: Manual connect
[11:01:38] ● Sending wake signal…
[11:01:39] → ↵
[11:01:39] → ?
[11:01:41] ← ��bR�
[11:01:41] ← Grbl 1.1h ['$' for help]
Hi Dennis,
Thanks, it does look like the serial connection is opening and GRBL is at least beginning to start up, but the controller may not be fully ready by the time the first status query is sent. I’m wondering if your Nano (or Nano clone?) board resets when the serial port is opened and then takes longer than usual to be ready? Where did you get the firmware you flashed to it from?
I have updated this web diagnostic tool so it will wait longer for a readable startup message from GRBL before it sends the first status request.
Please try this:
- Close MillMage completely.
- Turn the machine off, wait a few seconds, then turn it back on.
- Open this link in Chrome or Edge:
https://nicholas-a11y.github.io/grbl-diagnostic/?preset=startup-status&name=dennis-startup-status&baud=115200&wait=200&banner_timeout=5000&delay=600 - Click Connect and select the machine’s serial port.
- Wait about 5 to 10 seconds for the log to settle.
- Click Copy log and paste the full result here.
Hopefully, at the bottom of the log you will now see a response to the ‘?’ status query, something like; “<Idle|MPos:0.000,0.000,0.000”).
If not, ‘Disconnect’ , and then use this link to start a passive capture test which will reopen the port and just listen without trying to start a dialogue:
- Open this link:
https://nicholas-a11y.github.io/grbl-diagnostic/?preset=observe-only&name=dennis-observe-only&baud=115200&wait=0 - Click Connect.
- Wait for 5 seconds.
- Click Copy log.
- Paste that log here as well.
That looks the same as a Show All Console window. Am I close?
Hi Mike, I have a power outage here at the moment so I’m unable to check the results of this test on my other CNC machine. But if you are saying that for you the top link in post #16 produces a similar output as MillMage with show all enabled? - then that is good. Feel free to play around with this web app and post your results which is good for reference.
The idea I had for it was to have something outside of MillMage to check if the serial connection can be established and capture a nice diagnostic log. Beyond that, I thought it might be handy to later include some preset diagnostic checks (as I figure out what it needs to look for). Oh, and it can also be used to send a series of specific GRBL commands from the URL link which I think could be pretty handy and part of the app helps to build the URL for you with those commands embedded.
That makes perfect sense from a diagnostic point of view. My statement was just after a cursory view and test. I saved the link and will drill into it later to see what other magic I can find. You seem to have a knack for creating these “accessories”!
Hi Nicholas, First I want to thank you for all your help! I have been using “Github”, I don’t know if it is a clone it came with the mill when I bought it. How can I determine if it is? Anyway, this is what happened today.
GRBL Diagnostic Log
Log name: grbl-diagnostic-dennis-startup-status-2026-03-31T16-31-44-994Z
Timestamp: 2026-03-31T16:31:44.994Z
Preset: dennis-startup-status
Description: Wait for a device ready signal, then request a single real-time status report.
Baud: 115200
DTR mode: default
Observe only: no
Banner wait: 5000 ms
Startup resolved: banner
Ready line: Grbl 1.1h [‘$’ for help]
Port info: VID 0x1a86 · PID 0x7523
Source URL: GRBL Serial Diagnostic
[12:22:06] ● GRBL Serial Diagnostic ready
[12:22:06] ● Open Chrome or Edge, connect your device via USB, then click Connect
[12:22:06] ● Loaded diagnostic preset: dennis-startup-status
[12:22:53] ● Port selection cancelled
[12:23:47] ● Selected port: VID 0x1a86 · PID 0x7523
[12:23:47] ● Connected at 115200 baud
[12:23:47] ● DTR control available
[12:23:47] ● Diagnostics mode: Preset: dennis-startup-status | Commands: none | DTR: default | Observe only: no | Wait: 200 ms | Banner wait: 5000 ms | Step delay: 600 ms
[12:23:47] ● Waiting 200 ms before startup commands
[12:23:47] ● Waiting up to 5000 ms for a ready signal
[12:23:48] ← ��BQ�
[12:23:48] ← Grbl 1.1h ['$' for help]
[12:23:48] ● Ready signal detected: "Grbl 1.1h ['$' for help]"
[12:23:48] ● Startup resolved via: banner
[12:23:48] ● Sending wake signal…
[12:23:48] → ↵
[12:23:48] ← ok
[12:23:49] → ?
[12:23:49] ← <Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:Z|WCO:-464.000,-1.000,0.000>
Thanks again