I know, looks like a memory leak.
I read that and forgot. @parsec has a good suggestion too. Worst case, buy a $35 DLC-32 and load GRBL on it (some even come with GRBL installed, but make sure it is laser compatible).
We are on your side!
I know, looks like a memory leak.
I read that and forgot. @parsec has a good suggestion too. Worst case, buy a $35 DLC-32 and load GRBL on it (some even come with GRBL installed, but make sure it is laser compatible).
We are on your side!
Definitely! I’ll be following along, and I have the same machine if comparisons with a working machine are needed.
Just a thought: Could this be an issue with the cutter not knowing where the laser is, because some sensor has failed so the laser position is being reported incorrectly?
(I have one of these on order, it arrives today.)
I have flashed the current version twice and may try again although it seems to be correctly loading. I have not been able to find Version 1.0.0 anywhere online, including Creality’s site which claims to have archived firmware available.
Thanks for the recommendation. I have been thinking of doing this as a “nuclear option.” The issue I have read is the communication and pinout from the controller board to the laser module is proprietary. At least one user on GitHub has been trying to write code for it.
Thanks Jackie! I would love to see what your Console spits out on a boot up if you are able to paste it here.
Yours will likely work out of the box as a stranger hasn’t done mystery things to it before it arrived. I think the machine is correctly stepping and detecting home positioning. The Gcode Mikey sent yesterday seemed to run fine.
If you want, would you mind sending me a copy of the contents of the memory card that comes with your machine once you have it installed? Mine came blank and the documents on it are not available on Creality’s site. I’ve read that there are some user guides, test files etc. that are pretty useful.
There are no resolvers, so there is no position feedback. This is why you have to re-Home the machine if it hits the rails and keeps trying to move.
Here you go!
Waiting for connection...
Port failed to open - already in use?
Waiting for connection...
[OK]system start-up CV50-Pro-MASTER-Release V1.0.1 20240325-1042_info->power:40W ,CV50-LASER-40W-Release V3.0.5 20231129-1003
usb connect succeed
ok
[VER:1.1f.20220810:]
[OPT:VHL,127,65536]
Target buffer size found
[software versions: CV50-Pro-MASTER-Release V1.0.1 20240325-1042]
ok
[G54:-nan,2.871,0.000]
G54 Offset values not 0
[G55:-nan,2.871,0.000]
[G56:-nan,2.871,0.000]
[G57:-nan,2.871,0.000]
[G58:-nan,2.871,0.000]
[G59:-nan,2.871,0.000]
[G28:-nan,2.871,0.000]
[G30:-nan,2.871,0.000]
[G92:0.000,0.000,0.000]
[TLO:0.000]
[PRB:0.000,0.000,0.000:0]
ok
Homing
ok
Thank you!
This helps to rule out the “nan” G54 values as an issue since you have them as well. I am going to look into why my firmware listings appear in different sequence, but it may be the way you have your console set up. The major difference I see is that you have a single instance of each reply from the controller (ok, usb connected etc.) and I get multiples. Seems like my board is a bit ambitious.
The multiples are interesting, but I’m not sure what (if anything) they might signify. It’s interesting that it occurs whether or not it’s connected to a computer.
I can force mine into an infinite homing loop with what I believe is a grounding issue on the camera (need to do some troubleshooting I haven’t had time for), but mine doesn’t back off fully like it sounds like yours is doing.
I took the useful stuff from the memory card, compressed it, and left it here http://www.olimpia.com/subset.zip If you’re on Windows and this does not unpack, let me know.
This is awesome, thank you!
I will try unzipping later and let you know how it goes
Checking in to say a very grateful “thank you” to the community for all the ideas and troubleshooting ideas on my issue. Even though I am a new member here and my issue wasn’t directly related to Lightburn, the support has been amazing.
@MikeyH gets the prize for being closet to the actual root cause of my issue with suggestions to check grounding and cables.
After looking at every possible cause of the problem, I finally decided to remove the controller board and try running the printer with it, not mounted to the machine and it started right up and homed and acted normally. It looks like when the previous owner replaced the board they didn’t properly replace the strip of insulating rubber material on the backside of the board and something was shorting out. I actually used the test file that Mikey sent and increased laser power and use that as my first test print and burned paper successfully!
Again, thanks everybody for your help and I look forward to engaging with this community and forum to start actually engraving and cutting with my new machine.
This really good news! Now you know you got a bargain instead of a paperweight. ![]()
Thank you for the credit, but this was a tribe effort.
Don’t be a stranger. Post more questions, some of your finished crestions, and even jump in and offer to help someone else. That is how it works here. ![]()