navaismo / Ender-3V3-SE

Modified firmware for the Creality 3D Printer Ender 3v3 SE
GNU General Public License v3.0
2 stars 0 forks source link

Ender 3 V3 SE Screen #2

Open countrykid123123 opened 4 hours ago

countrykid123123 commented 4 hours ago

Hey, I'm not sure if I missed an install step or something but I have also had some issues with the progress screen only updating a layer number in the middle of the screen while printing as shown in the attached photo. When the print finishes it seems to update the whole screen with the completed screen (attached photo). Otherwise the pressure advance and filament run out sensor and other changes seem to be working properly.

20241104_181729 20241104_183207

navaismo commented 4 hours ago

Hi @countrykid123123 This looks like an overlapping of the M117 messages and the O9000 cmd, you cant use both. If you want to see the progress using the M117 command with the Octoprint plugin DisplayLayerProgress then I suggest to use the main branch.

If you want to use the O9000 cmd from OctoPrintJobDetails then you must disabled the DisplayLayerProgress plugin and use the OctoPrintDetailsPageinLCD branch.

The OctoprintJobDetails plugin indeed update the screen on every Z change because is the effective way to tell the printer to update the values since the printer is only listenning for updates from OctoPrint server.

navaismo commented 4 hours ago

In this Link you can see how it works using Main Branch and DisplayLayerProgress Plugin.

In this Link you can see how it works the OctoPrintDetailsPageinLCD branch with the OctoPrintJobDetails plugin and the DisplayLayerProgress plugin disabled.

countrykid123123 commented 3 hours ago

Ok first I wanted to thankyou for the detailed response and all your work making the customized firmware and plugin. In my case I am not sure what is happening as I didn't actually have the displaylayerprogress plugin installed. I have the firmware from this branch (downloaded and installed from the firmware folder) and the companion Octoprintjobdetails for octoprint. I am running octo4a though so maybe that is causing some of the issues I am having. It is almost like it doesn't see the other events and only notices and send the command on the print completion.