So, I made some testing and here is what I managed to find out:
With the current configurations and setup, using your sliced gcode file, it still does not work.
After disabling all plugins (including DLP and PTG) except your plugin and dashboard, the M73 LCD progress update works even on my own sliced file via OrcaSlicer.
Then I slowly enabled few plugins at a time to see what was affecting this, and voila, the ‘OctoPrint-Display-ETA’ plugin was the culprit that prevented from displaying the print update on the LCD. I even tested again but this time with PTG and DLP (turned off the ‘Printer Display’) enabled and still works.
So, I took a step further and created a second instance of OctoPrint on Portainer and tested all the Time and Layer progress options, as you said, it does not work. But with Cura sliced Gcodes, it does work, both Time and Layer progress, with the % progress bar moving according to the actual progress.
Not sure if PTG has anything to do with actually updating the time but according to @TechieZebra, it should not work on Docker based OctoPrint but I think (but I might be wrong) that PTG actually works based on the icons next to the processed files and I am running OctoPrint on Portainer (not sure but iirc, it is within docker container, right?)
I further investigated my other issues with the OrcaSlicer sliced gcode files unable to show metadatas related to filament used and stuff and I found another thing, PTG cannot work with OctoPrint-SlicerEstimator plugin. If SlicerEstimator plugin is enabled, PTG will not run the analysis and all the other metadata analysis like CostEstimation, PrintJobHistory, etc. will also not work. I do not understand why but I can live without it.
Somehow with the fresh install of OctoPrint, it all works as it should which is mind-boggling. I guess it was some sort of a bug or clashed between plugins.
Anyway, that is all for the update. Thank you for your time!
I never have had the stars, so that is a good sign that it does work on your setup!
So reading your plugins, I reviewed to see what I have, and sure enough I do have Slicer Estimator installed!! Okay, now to remove it and try everything with PTG and see how things work out, just have to wait for the printer to finishing…
Yeah but I don’t recommend doing any changes or uploading files mid-print. Especially if it is a large file and the print is a long hour print. Many times have I wished I did not do that. Hahaha anything let me know, I will see what I can do to help.
Okay, did some bug swatting. It appears that PTG, when it does its thing, uses the 64-bit version of marlin-calc, which does not work in a container. I swapped it out for the 32-bit version and it now works!
Using Firefox Translate:
“Hey, everybody. I’m sorry to interrupt. Saw this firmware with input shaiping and some new mesh 5x5 (7x7)
And different versions 1.0.9.7_7 and 1.0.9.7_7v3 or v2. But I don’t understand, is it for all e3v3se printers or just for those who work on octoprint?? I use orcaslicer”.
And the reply:
"Hello, in version 1.0.9.7_7 size Input Shaping and Grid is 5x5. V2 or V3 is the same, but with a 7x7 grid.
The firmware will work without Octoprint, which displays the default screens, but you will have access to the Input Shaping menu and the new Tune features."
Спасибо за ответ. Сейчас читаю про imput shaping. Как понял есть разные SHAPER_TYPE и один скругляет углы больше, но гасит больше вибраций, а другой наоборот меньше скругляет, но и гасит меньше. У нас какой SHAPER стоит? А есть возможно подключить акселерометр?
Привет! Согласно коду поддерживаются следующие типы:
// T[map] Input Shaping type, 0:ZV, 1:EI, 2:2H.
Хотя и в очень простом смысле.
Что касается акселерометра, то у принтера нет доступных портов SPI, поэтому подключить его напрямую невозможно. Скоро я проведу несколько тестов для тех из нас, кто использует Octoprint с Raspberry Pi, поскольку можно подключить акселерометр напрямую.
I haven’t seen much of a difference between the two, and currently they both degrade the printing a bit (much less since I removed the sleep() function).
PTG does need extra processing of files, and so I think that is where using M73 has an advantage. Accuracy wise, I don’t need to watch the prints that closely for time, so if they are off with M73 in comparison to PTG, I don’t know.
Please use any language you feel comfortable in. It’s 2025 and we all have the ability to translate what we can’t immediately understand. If others are uncomfortable with Russian, Spanish, Hungarian or Chinese - that is their problem.
Пожалуйста, используйте любой язык, на котором вы чувствуете себя комфортно. Сейчас 2025 год, и у всех нас есть возможность перевести то, что мы не можем сразу понять. Если другим неудобно с русским, испанским, венгерским или китайским - это их проблема.