Hello,
Recently, The Snapmaker 2.0 has been bringing an error "filament Recovery error " while Laser Engraving. Which is very odd to being with.
I am on Firmware Version 1.81
I am on Firmware Version 1.81
Do you have a photo of the start screen?
When the machine is booting up??
Plus the Firmware Update hangs up here.
Nothing really happens after here.
Tried to update the firmware via USB. The app crashes
No, the screen when it’s ready to be used after starting up.
Odd.
Check your cable connections.
For the update, try it with a different head connected, no need to to mount it.
It was printing well an hour ago.
Just after this project,
Then it started to misbehave.
So you think Changing the head Module and trying the update will help??
No idea, but you had a problem updating anyway.
I remember this update, it wasn’t working over the air for some people and me either.
We are now at V1.18.2 so, why not updating?
Attention, you need to update Luban too, there were significant firmware changes in 1.18 and Luban 4.9.1, this means your old gcode would not work anymore.
Edit: Sorry I thought you are on 1.8…
You should open a support ticket or email them, get your logs and share it.
https://snapmaker.formcrafts.com/support-ticket
Or support@snapmaker.com
I am on 1.81.
I can’t update to 1.82
Over WiFi and USB stick too.
I am checking my Luban Version.
Cause it just shift from Laser Engraving to Bringing Up an error that filament is out while Engraving.
Try a different usb thumb drive and wait for at least 30mins. Sometimes the update needs that long (mostly if there where touchscreen changes, I guess).
Did you print/engrave by transferring the file or from Luban?
By transferring the file.
I prefer that to sending from Luban.
Printing from Luban or uploading to the printer?
Does it also happen if you print from the touchscreen?
I mean I print from the touch screen.
Most files I put them in a USB stick.
Not true. I’m running latest firmware and old version of Luban (4.3.2), and everything works just fine. As long as you’re using modules compatible with that version of Luban (which OP is). Unless of course Luban 4.9.1 is generating bad gcode, or there’s a new module specific gcode (which isn’t the case). That’s the beauty of gcode, it’s mostly independent from the the hardware, I can use Luban, etc to generate gcode for my CNC plasma cutter.
I remember many cases where not both (machine firmware and Luban) were upgraded and this caused problems. Maybe you are correct but for most users it’s the information they need.