No sustained connection between LaserGrbl and Cosmos Maker controller #1140
Replies: 6 comments
-
|
LaserGRBL need to recognize valid grbl status report to accept valid connection. Can you record an "extended log" (menu ? - Activate extended log) of a connection session and upload here? |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, yes - all too easily. 00000 00155524 log Recording session started @ 10/11/2020 14:50:34 |
Beta Was this translation helpful? Give feedback.
-
|
Look like it does not reply at all with status message! |
Beta Was this translation helpful? Give feedback.
-
|
Usually comlog llok like this: 00000 00119782 log Recording session started @ 12/3/2019 12:14:20 AM |
Beta Was this translation helpful? Give feedback.
-
|
@jamesmknox do you have the offline controller mounted on it? |
Beta Was this translation helpful? Give feedback.
-
|
No, but I found the problem - thanks to your suggestion about the extended LOG. Traced the problem down to ANOTHER broken SMD resistor. [Second one I've found on this board, and also a previously found pulled lead on an IC.] So, looks like I've got it working. [At least, until I hit the next problem. ] My great thanks for the help. jmk |
Beta Was this translation helpful? Give feedback.
-
System: Windows 10 desktop. I have a CNC 3018 with a Cosmos Maker (aka Annoy Tools) controller. This controller has the admittedly notorious CH340G USB - Serial chip. It works okay under UGS, although it sometimes does take multiple tries. However, I downloaded LaserGrbl (ver 3.7.1) a couple of days ago, and am at a roadblock. It installed fine, and seems to run fine. However, it refuses to make a meaningful connection to the CNC controller.
Appropriate COM port and baud rate. Clicking "connect" produces an indication that it connected - specifically I get back a message "Grbl 1.1f ("$" for help)". The status changes to "Connecting". However, the jog and other buttons never enables, and it will take no commands. About 10 seconds later there is a "bing bong" and status changes back to "Disconnected".
Log shows:
10/11/2020 12:39:47 Program ------- LaserGRBL v3.7.1 [64bit] START -------
10/11/2020 12:40:04 SetStatus Machine status [Disconnected]
10/11/2020 12:40:20 SetStatus Machine status [Connecting]
10/11/2020 12:40:20 OpenCom Open COM4 @ 115200 baud
10/11/2020 12:40:20 SendImmediate Send Immediate Command [0x18]
10/11/2020 12:40:22 VersionInfo Detected Grbl v1.1f
10/11/2020 12:40:30 OpenCom Connection timeout!
10/11/2020 12:40:30 CloseCom Close COM4 [CORE]
10/11/2020 12:40:30 SetStatus Machine status [Disconnected]
I've tried reinstalling the device driver (which appears to be the exact same one I was using with UGS). I've rebooted,. I've tried running LaserGRBL with administrator privilege. It doesn't get worse, but it doesn't get better either. Still, I can cut and engrave with UGS... just not use the laser with LaserGRBL.
Any ideas/suggestions appreciated. jmk
Beta Was this translation helpful? Give feedback.
All reactions