0.9.20 still doesn’t work for me ,… back to 16 again
LightBurnLog.txt (18.0 KB)
This makes absolutely no sense at all. Your laser is found, it’s showing that it’s an Arduino Mega, and sending the G0 command, yet your machine is ignoring it:
09:18:50.971 D: Looking for port: “COM6”
09:18:50.971 D: – candidate port PID 66 VID 9025
09:18:50.971 D: mfr: “Arduino LLC (www.arduino.cc)”
09:18:50.971 D: prod: “Arduino Mega 2560”
09:18:50.971 D: name: “COM6”
09:18:50.971 D: - found matching port name
09:18:50.971 D: Found port: PID 66 VID 9025
09:18:50.971 D: Manufacturer: “Arduino LLC (www.arduino.cc)”
09:18:50.971 D: Product: “Arduino Mega 2560”
09:18:50.971 D: Name: “COM6”
09:18:50.971 D: Port open succeeded
09:18:51.033 D: “starting” busy: false state: 0
09:18:51.033 D: EV: 1001 took 9 uS
09:18:51.033 D: EV: 1001 took 5 uS
09:18:52.062 D: “Attempting to connect” busy: false state: 1
09:18:52.062 D: “Connecting…” busy: false state: 1
09:18:52.065 D: O: “\n”
09:18:52.320 D: “Connecting…” busy: false state: 1
09:18:52.324 D: O: “\n”
09:18:52.578 D: “Connecting…” busy: false state: 1
09:18:52.581 D: O: “\n”
09:18:52.836 D: “Connecting…” busy: false state: 1
09:18:52.839 D: O: “\n”
09:18:53.118 D: O: "G0\n"
@rsaylr1 - What exact board do you have, and where did you buy it? It looks like I’m going to have to get one of these so I can figure out the exact dance I need to do to make it wake up. The \n shown in the log is “newline”, aka “the enter key”. This works with every GRBL device I have yet yours and a few others don’t like it, and I have no idea why.
These are the board/s I have , I scrapped an old delta printer and made this Laser out of it. Would trying a different firmware help or is it a hardware issue? I can edit firmware or reconfigure/rewire if it will help. Cheers
Are you just using stock GRBL? The base of that board is just an Arduino Mega, and the top board looks like it’s just a generic stepper motor shield.
I used the one from here so I could use z axis later … as said earlier 0.9.16 works for me
Ok, you’re now the second person using this exact build that’s had this issue with it. I’ll have to see if I have an Arduino Mega around that I can flash this to.
I’ll try to see if the firmware maker has any ideas now… its probably not worth your time if others have issue with this same firmware … cheers mate
Well, if I can figure out why it’s happening, and make LightBurn handle it, that would be nice - I’d like to figure out what changed between 9.16 and now that’s making it not work.
If there is anything you want me to try let me know 
I have exactly the same Arduino mega 2560 r3 and ramps board running same grbl mega 5x
And I’m still able to connect to pronterface then lightburn… after I do that once I can close lightburn and reconnect no problem.
I just tried this and can confirm it also works for me after doing the same,
until I unplug the usb, then have to repeat procedure , cheers mate
pronterface does show “error 9” after connecting…
Any update on this?
Yes - I believe I’ve tracked this down as of last night. Can you try this version?
https://drive.google.com/file/d/1_AlkuYbz9s42xEIP1_dHiP3YInsKVJAZ/view?usp=sharing
Here are the results I got , still not working… but will work after connecting to pronterface first …
before…
after connecting with pronterface …
Can you check in Edit > Device Settings and see if you have “Enable DTR signal” turned on? If you do, try turning it off and see if that helps. The bug fix was to make the system properly respect that flag.
Anything based on an Arduino sees that signal as a sign to reset for programming, which was a poor choice on their part, because it’s supposed to be used to tell serial hardware that you’re ready to talk.
If that doesn’t work I’ll have to pull the Mega-V code and flash my test board with it and see if I can chase it down.
Hi, I checked and “Enable DTR signal” was already OFF , I am happy to use the current workaround if you have other things that deserve more attention and its only affecting a small batch of hardware/firmware , cheers mate
FWIW, I’m having the exact same issue. Used to work fine but now with latest version can’t connect.
I’m using a Genuine Arduino Mega with same firmware and driver card as Stano71
Cheers
OZ, you can cross one off the list. that last update you posted above worked for me out of the box. no pronterface trick, enable dtr off. i downloaded it and installed. connected right away. i rebooted and tried again and bingo… connected,
to recap, i have the exact setup stano posted above. i purchased mine as a kit from ebay.
only thing i noticed in the “console” pic of stano’s his has 5 axis enabled XYZAB and mine 4:
also my ver# is different. im also using purple “DRV8825” drivers
Waiting for connection…
ok
[VER:1.1n.20200424:]
[AXS:4:XYZX]
[OPT:VNMHL,35,255,26]
Target buffer size found
ok
I did some more testing today… when I turn it on and plug it in (usb) it connects
if I try to move I still get this
I found if I click the STOP button it will allow me to move as normal…
No need for pronterface…
Happy with that as its easy enough…
Cheers
