Open tophe75 opened 1 week ago
Was the print started from OctoPrint or by sending to printer from slicer? Would be great to get the full log as an attachment, you can just drag it into the comment here on GitHub.
Was the print started from OctoPrint or by sending to printer from slicer? Would be great to get the full log as an attachment, you can just drag it into the comment here on GitHub.
I sent the print from the slicer (Orca) Which log are we talking about? The plugin_bambu_printer_serial.log only has one line: 2024-10-25 10:30:19,912 Not a valid gcode command "MyPassword"
As for the octoprint log, it is not the hole file but everything from befor starting the print until it is done. octoprint_short.log
I found some weird stuff in my OctoPrint installation and custom GCODE Scripts that might be the reason for this behavior, I will try a print tomorrow and let you know if I found something.
For some reason the username and the password was typed in some of the fields: After tool change, After serial connection to printer is established, Before serial connection to printer is closed
But I will do a test and get back.
I was just about to say to make sure you don't have any gcode scripts configured in OctoPrint to start. Also, make sure in OctoPrint's logging section that the octoprint.plugins.bambu_printer
entry is configured for debug at the bottom.
So I just finished a print, still printing from the slicer (Orca), I get no Print Started nor Print Finished
What I am trying to achieve is for the plugin to get Print Started, Print Finished, Print Paused, Print Canceled, etc and then by using the WLED Connections plugin set status light.
New log file: plugin_bambu_printer_serial.log
Update Starting a print from the printers SD card (not using the slicer or OctoPrint) resulted in a 'Start' flag picked up by OctoPrint using the plugin and also the WLED plugin turned the lights on.
Still getting Cancel when the print finishes
Describe the Bug
P1S finish print successfully reported as candled in OctoPrint, Bambu printer reports print successfully finished.
Expected Behavior
Successful finished print should be reported as successful
Debug Logs
2024-10-25 11:31:15,885 - octoprint.server.heartbeat - INFO - Server heartbeat <3 2024-10-25 11:35:06,944 - octoprint.util.comm - INFO - Changing monitoring state from "Printing from SD" to "Cancelling" 2024-10-25 11:35:06,948 - octoprint.printer.standard.job - INFO - Print job cancelled - origin: sdcard, path: Paddle box .3mf, owner: None, user: None, fileposition: 1, position: {'y': None, 'f': None, 't': None, 'x': None, 'e': None, 'z': None} 2024-10-25 11:35:06,965 - octoprint.plugins.bambu_printer.BambuPrinter - INFO - command sent successfully 2024-10-25 11:35:07,022 - octoprint.access.users - INFO - Cleaning up user session 4BC3AF038A8E4B038B31B7A6DE089DBD for user
Screenshots
Printer and Plugin Setting Details Bambulab P1S with AMS, default plugin settings