Open darkclover92 opened 4 days ago
Can you remove the filament to not waste material while testing?
After that, please restart Octoprint and load any file or send through cura.
After it fishing please send me the Octoprint.log to see the output of the plugin while restarting and during the print time.
Here's the octoprint.log. I restarted OP and printed something I wanted to print. Let me know if you need anything else.
Thanks.
I can see that the plugin is able to parse all info:
2024-11-26 16:58:11,100 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - >>>>>> E3v3seprintjobdetailsPlugin Event detected: MetadataAnalysisFinished
2024-11-26 16:58:11,101 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - >>>+++ PrintedStarted and Metadata Finish, get print Info
2024-11-26 16:58:11,606 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - >>>>>> E3v3seprintjobdetailsPlugin Getting Print Details Info 1st time.
2024-11-26 16:58:12,507 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - File selected: /octoprint/octoprint/uploads/CE3V3SE_ExtrusionMultiplier.gcode
2024-11-26 16:58:12,507 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - Total layers found: 15
2024-11-26 16:58:12,507 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - File selected: CE3V3SE_ExtrusionMultiplier.gcode
2024-11-26 16:58:12,507 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - Print Time: 5719.0
2024-11-26 16:58:12,508 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - Print Time Left: 0
2024-11-26 16:58:12,508 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - current layer: 0
2024-11-26 16:58:12,508 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - progress: 0
2024-11-26 16:58:12,508 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - Print Time: 01:35:19
2024-11-26 16:58:12,508 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - Print Time Left: 00:00:00
2024-11-26 16:58:25,520 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - Ignoring M117 Command since this plugin has precedence to write to the LCD: M117 ETA is 06:33:40 PM
2024-11-26 16:58:25,602 - octoprint.plugins.action_command_notification - INFO - Got a notification: Bed Heating...
2024-11-26 16:58:25,619 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - >>>>>> E3v3seprintjobdetailsPlugin Event detected: ZChange
2024-11-26 16:58:25,619 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - >>>>>> E3v3seprintjobdetailsPlugin Update Print Details Info
2024-11-26 16:58:25,620 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - Print Time: 5719.0
2024-11-26 16:58:25,620 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - Print Time: 01:35:19
2024-11-26 16:58:25,620 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - Print Time Left: 5719
2024-11-26 16:58:25,620 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - Print Time Left: 01:35:19
2024-11-26 16:58:25,620 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - progress: 0.0
2024-11-26 17:00:27,480 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - ====++++====++++==== Layer Number: 1
2024-11-26 17:00:27,489 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - >>>>>> E3v3seprintjobdetailsPlugin Event detected: ZChange
2024-11-26 17:00:27,489 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - >>>>>> E3v3seprintjobdetailsPlugin Update Print Details Info
2024-11-26 17:00:29,470 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - >>>>>> E3v3seprintjobdetailsPlugin Event detected: ZChange
2024-11-26 17:00:29,471 - octoprint.plugins.E3V3SEPrintJobDetails - INFO - >>>>>> E3v3seprintjobdetailsPlugin Update Print Details Info
.......
So next step is to try disabing the DisplayLayerProgress plugin, i can see a lot of events from it. And if possible share with me the serial log. Need to see if the event are sent to the printer.
Alright. I restarted OctoPrint again and made a print. Here are the fresh logs: octoprint.log serial.log
Let me know if you need anything else.
Serial Log is not enabled:
2024-11-26 23:01:36,745 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
Here are the logs again. Sorry for not enabling serial.log. Let me know if you need anything else. I have disabled the DisplayLayerProgress plugin as well as restarted OP and printed something.
I can see in the Log of octoprint that the plugin gather all info to update the layer and progress but in the serial log I just see the commands when it Loads the screen and when it finish.
In your LCD did you see only first screen and completed screen? Not sure why the tty is not sending the commands, is it possible to share the gcode file so I can try in my setup?
Actually, the layer and its progress are shown, basically. Refer to this image below:
In terms of layer or time, I know it does not show time because I notice when printing a single layer test print, since it's only one layer, the progress basically went from 0% to 100% the moment the print started. The one I printed was this: ABS.txt
Is this related to I am unable to send M117 commands to the printer's LCD? Let me know if you need anything else.
Ah, well the plugin send updates to the screen every Z change, so if there is no layer change it will show from 0 to 100, but the image above should work as expected right, updating time and progress on z changes.
Issue - M117 Commands
I tried sending M117 command, it does not log in the terminal as well as prompt in the LCD screen. You may refer to this short video.
Plugins and Firmware
Firmware: _v1.0.9.73 OctoPrint: v1.10.3 (container via Portainer on TrueNAS Scale server) Plugins (for your info only):
Additional Observation
Print Job Details Update on LCD
Scenario 1 I used the cube-test-print you provided to _Bruce_VanEssen on the Creality forum. I printed with two methods, directly upload to OctoPrint and 'print withOctoPrint' in Cura. Both did not update the LCD when printing was initiated like how the stock one would if printed directly from SD card. Note also, SliceEstimator did give out 2 warnings;
No print time estimation from slicer available
andNo timecodes found
. My guess is that because it was a G-code meant for somebody else, with different slicer, material and printer. Maybe, just maybe.Scenario 2 I ran a test with my .stl file sliced in Cura and printed directly as well as upload on OctoPrint with the following plugin settings:
Side Note: This is NOT a serious, important nor urgent issue. I simply would like to share my findings. Your firmware as well as plugin work as they should and ~I am~ WE ARE grateful (on behalf of others). So, please do take your time to review it whenever you like. Thanks a bunch!