Just downloaded the LB software to try. Installed it. Windows 10. During the step to scan for my laser, the software obviously finds the equipment because it lights up and activates for a moment – then the software freezes. I’ve tried everything. Restarting and such. Just gets to this scanning step and freezes forever. I have to manually end the task.
NOT a good first impression of this software!
Thank you for reporting this. I will attempt to reproduce the unanticipated behavior.
I’ve got a LaserPecker 4 here.
Please use the LP4.lbdev file to set up your device.
This may be worth review:
The LaserPecker 4 is an unusual device. Among other innovations, it defauts to 460,800 baud to connect.
I’m not certain that a momentary connection is different from a failed connection. In testing, I generated a noisy and erratic connection by attempting to connect at a more standard 230,400 baud and some garbled data appeared in the Console window in LightBurn.
When it connects, please let us know which firmware your device shipped with.
John, I’m sorry – how do I use LP4.lbdev file? I have no idea what that means?
I’m using v6.53 with my LP4. It’s brand new.
How do I change the baud rate? I can’t find any setting for the connection speed.
Download the file to your desktop
Then open lightburn → in laser pannel click Devices button
(you can delete other profiles if you only have 1 machine the Laserpecker
Import button → locale .lbdev file and click OK
this will import the profile
To confirm baud rate → Edit → device settings
Bottom right corner shows baud rate
No worries, we all start our journey somewhere.
Click on the link in the previous message (or below) to go to the manufacturers website.
Follow the instructions in Step 3.
Firmware 6.53 confirms that you are working with recent firmware that will work with LightBurn. The LP4 is still in testing here.
The connection speed setting will appear in the Device Settings window when a GRBL device profile is created. The Device Settings window is Dynamic and Baud rate won’t be available for all engravers; not all engravers communicate through the usb/serial port. The lbdev file is a file with all the Device Settings built in. After you import it, and select the LP4 Device, the Baud rate will be set correctly.
Thanks. Did all of that and it now connects. However, it keeps losing connection, giving EEPROM failure errors, etc. I can’t believe this is this difficult. The LP4 software might be a lot more basic, but it worked out of the box and I was burning images within about 5 minutes. I’m a couple hours into LB software and nothing but errors and problems. So frustrating.
The EEPROM is in the LaserPecker itself.
The test unit I received is running Firmware Version V6.5.5. Flashing newer firmware may help.
I have noticed others are struggling with Error 7 EEPROM Read Error.
Is this the error you’re seeing?
I’m attempting to confirm this but I’m fairly certain that this error can be generated by attempting to adjust Machine Settings that the Manufacturer has locked out.
If you’re willing, Screen captures from your computer and text copied from the Console window in LightBurn can aid troubleshooting considerably. I’ll fire up mine and see what I can discover.
Yes, error 7 eeprom failure is what I got. However, now that I’m trying to duplicate it for a screenshot, LB can’t even find my device. It’s on and usual. augh
If you have any other software running it can occupy the USB port and block other connections.
The other ‘feature’ of usb ports is that because they’re dynamically assigned, the laser can change COM ports when other connections are made.
In LightBurn, in the Laser window, confirm that you’ve selected the device profile for the LP4, then Click the Connection button in the middle. It will say Choose or COM3 or COM5 or something similar. You can have several options here but one will connect to the LaserPecker 4 if it’s plugged into your computer.
I’m looking for the technical reference for Error 7. I believe it’s emitted when a write operation is attempted on write-protected Machine Settings in GRBL. Any new settings that don’t match what is read from the EEPROM are interpreted as a Read-Error and the Settings are reset to what was built in (at build-time) when the firmware was compiled.
Occasionally, Microsoft OneDrive seems to cause project Files and Machine Settings to be misplaced or damaged. This also happens with removable storage and other cloud services. If things work well and suddenly go wrong, that’s my first go-to when troubleshooting.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
