The job stops early when run from lightburn, and even leaves the laser still on (!) It stops after 2-4 seconds (so just 4-10 gcode instructions), but not in the same place.
Saving the gcode and running from pronterface or octoprint works fine, the full laser cut is made.
On Linux I’m using lightburn 0.9.16, on Ubuntu.
I’ve tried:
Linux Ubuntu lightburn
Windows 10 lightburn
Without any USB extension cable - just short ‘blue’ cable the SKR 1.4 board came with
The RX buffer size number is a minimum. If yours was previously set to 1024, leaving it there isn’t hurting anything - it’s “how much data can LightBurn send the controller before it chokes”.
I’m adding support for the “ping-pong” method of communication, as this does not force-feed the controller until the RX buffer is full. Ping-pong mode sends a single command, and waits for the ok response before sending the next one. This method limits the throughput, so rastewr performance may not be as good, but it is likely what Pronterface is using and is less sensitive to poor comms handling on the controller side, electrical interference, etc.
Yes, that’s easy to do on our side. I’m not sure what our timing is going to be for the next release, but we may do a “cleanup” release with a few small new features before too long (IE weeks).
The 0.5W laser stopped working (very dim, wouldn’t etch). So I’ve ordered a whole “20W” Ortur Laser Master 2 instead of mounting a laser on to the marlin-based printer. When that arrives, I’ll ask for a trial reset if possible. Thank you!