Print upload failing

[bull2525 0]

Printer: Flying Bear Ghost 6

Software: Ultimaker Cura 5.9.0

 

My prints have suddenly stopped uploading to my printer. I haven't changed any settings or anything physical on the printer. I am able to successfully connect to the printer via wifi, but whenever I try to upload any .stl file (including ones that have previously worked), it looks like it's trying to upload, but then I get an error message (see screenshots):

 

"Send file to printer failed. Check SD card"

 

I've never used the SD card option as I don't have any way of writing to it, so bypassing the wifi element isn't really an option for me. I have been able, up until the last couple of days, to print successfully.

 

I've tried: 

• Rebooting my computer (it's a Mac)
• Restarting the software
• Full reinstall of the software
• Attempted with multiple print files

 

Any help or suggestions would be greatly appreciated!

FBG6_screw and nut.3mf

[Slashee_the_Cow 519]

How are you connecting to the printer over WiFi, using OctoPrint? Cura can only connect to UltiMaker printers natively over WiFi.

 

Were I to take a stab in the dark, I would guess that the SD card in the printer might be full? If you're using OctoPrint, you can check that (and delete files) in the web interface. If you're using something else, then... I don't know something elses.

 

It's definitely worth having a card reader on hand, you never know when it's going to be useful... situations like this, for example. They're not expensive (unless you get one of the ludicrously expensive ones, but they only offer any benefit if you have ludicrously expensive cards, so not applicable) and it doesn't hurt to be prepared.

[bull2525 0]

Appreciate the response!

 

I connected directly from Cura to the printer. Cura is the recommended software from the manufacturer (as they don't have their own) for this reason. I have printed many things previously by this method. This error message has sort of popped up out of the blue. Whenever I turn the machine on the first message I receive is that the printer has successfully connected.

 

The error message is a bit misleading as I've never used the SD card and I get the same error when there's no SD card plugged in.

[Slashee_the_Cow 519]

28 minutes ago, bull2525 said:

The error message is a bit misleading as I've never used the SD card and I get the same error when there's no SD card plugged in.

It's highly likely it's just wirelessly uploading it to the SD card and then telling the printer to print from the card. My first bet would still be "card full" - is there a way you can browse and delete files on the printer itself?

(It's also possible the card is corrupted, but if it stays firmly entrenched in your printer that's less likely.)

 

If you have any other cards laying around you're not using (or can borrow for testing if you are using them) try that.

 

How are you getting it to communicate over WiFi? Do you have to download a plugin or something?

 

Just to be thorough anyway, put the card in the printer, then try printing something a couple of times (can be the same thing, the important part is that you're triggering the error). Then in Cura, go to Help > Show Configuration Folder. Inside that folder should be a file called cura.log - reply and attach that and we can see if there's anything to be seen from it.

[bull2525 0]

I've never used the SD card to print, nor have I uploaded anything to it. I've only ever done this via wifi. But I'm glad you asked because I made me look around the inside of the print chamber (I bought the printer 2nd hand) and I found an SD card in there. It has a few print files on it, so I tried printing a Benchy and it initiated and printed as expected.

 

I'm using an MKS plugin for the printer connection - screenshots of the settings are below. As you can see from the first one, the software has connected successfully to the printer. I've also attached the log file.

 

Thanks again.

 

cura.log

[Slashee_the_Cow 519]

It's definitely uploading it to either an SD card or (far less likely) internal storage and then just getting the printer to print it from that. It seems to be using some gocde commands (or at least values) which are completely different from regular Marlin, but that's neither here nor there for my purposes. But a line like this:

2025-01-11 15:35:34,690 - DEBUG - [MainThread] MKSWifiPlugin.MKSOutputDevice.on_read [1018]: mks recv: M994 /FBG6_3~1.GCO;4593164

is a dead giveaway that the printer has stored the gcode file and is accessing it using the classic DOS 8.3 filename limitations. Or possibly that's the message it sends while the file is being uploaded. Either way, it's definitely a file being either written to or accessed and if that message was coming from the computer's end it would probably have a full path and long filename, not a truncated filename.

There's also:

2025-01-11 15:35:34,701 - DEBUG - [MainThread] MKSWifiPlugin.MKSOutputDevice.on_read [1018]: mks recv: M27 0

M27 is "Report SD card print status". Normally the response is how many bytes through the file it has printed, I'm not sure if the 0 here is that it hasn't started printing or that's just how the printer responds to it.

 

It's hard to see too much in the log file because that plugin absolutely spams the Cura log, which gets recycled once it reaches a certain size. And if you're not trying to do something, every two seconds the plugin connects to the printer (presumably to see if there's anything going on) then disconnects... and each time it does that is four lines of text 😕

 

So I stand by my diagnosis: I fully believe you when you say you've never touched an SD card in the printing process. But the plugin is definitely getting the printer to save the gcode file to an SD card (or as I said, less likely, internal storage), then the printer prints it from that.

The only other way it could possibly print over WiFi would be like printing over USB, except doing it over WiFi. Which is a much worse idea than printing it over USB (which is a bad idea to begin with), but you'd need to keep your computer on and Cura running the whole time it was printing it if it was doing that.

 

So my reasoning is that if it's suddenly being a problem after you've been printing without a problem for quite some time, that it's reasonable that the card could be full if it never deletes the gcode files you print. Or (probably less likely) that the file system on the card got corrupted. Either way, it can't write the file to the card.

[bull2525 0]

Whelp, I got it working again. Just cleared out the SD card even though there was still over 7GB of space remaining. Then I reinstalled the firmware and it's uploading again. 

 

  🤷‍♂️  🤷‍♂️  🤷‍♂️

 

I saw that bloated beast of a log file for the first time when I uploaded it here. Certainly not the most efficient approach.

 

Really appreciate you helping me out with this. Have a good one!