Same file name showing when printing from Bambu Studio or Orca; file not uploading; multiple repeat alerts from Obico/Octoslack when starting

jneilliii / OctoPrint-BambuPrinter

GNU Affero General Public License v3.0

84 stars 5 forks source link

Same file name showing when printing from Bambu Studio or Orca; file not uploading; multiple repeat alerts from Obico/Octoslack when starting #13

Open bdwilson opened 4 months ago

bdwilson commented 4 months ago

No matter what file I upload, it seems to be always picking the last file that shows in the file listing. It hasn't always done this, but seems to have started 2 days ago (that's when the last file name is showing in the Octoprint file list). Even though the old name is used, the print still prints the correct item and has the correct time/length in Octoprint.

Attached log shows finishing a print from Orca (name is not what is shown there).

Then shows me starting a new print from Bambu Studio (2024-03-08 16:26:01,969) which it appears to generate print resume -> starting print -> finishing -> operational a few times, then it prints the right file but still continues to show the old file from 2 days ago. All prints show this file name. All prints result in multiple notifications.

octoprint-debug.log

jneilliii commented 4 months ago

Please enable debug logging for all bambu items in OctoPrint logging section of settings and try again.

bdwilson commented 4 months ago

They were already enabled so the logs above should be able to correlate with this log. You can see the sizes/names are always the same even though I'm printing different files from different slicers.

plugin_bambu_printer_serial.log

jneilliii commented 4 months ago

2024-03-08 16:21:02,662 - octoprint.plugins.bambu_printer.BambuPrinter - DEBUG - SD File Print: cache/latch v3 - gen3 - 4x pulls.3mf

perfect, after reviewing the octoprint log it seems you are cloud connected and not running in local only mode? I think the issue here is that the cached folder gets involved with cloud prints, so it's not tying back to the flattened file list that includes the cache sub-folder. I'll take a stab at a fix tonight after dinner to see if I can work that out.

bdwilson commented 4 months ago

So it was installed before cloud connection came along. Use local is checked. I have not logged in via cloud and have all the local configs filled in.

jneilliii commented 4 months ago

But your slicer is cloud connected otherwise files sent with the print button wouldn't go into cache sub folder.

bdwilson commented 4 months ago

Ahh correct.

bdwilson commented 4 months ago

Here is another debug log. octoprint.log

I started the log after re-installing the version you sent me. I then printed the file: "BMW i3 strap - orca 06MAR24"