-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BFW-5832] [BUG] M73 G-Code status report not correct #4089
Comments
Hi @samdurnxn thanks for the report. I confirm the issue is present, we will work on fixing it. |
just for my information, any news on the fix ? |
@samdurnxn the fix was merged into 6.1.0, which was just released for mk4s; release for other printers will follow "in near future" - probably in several weeks. |
My bad, I check the release summary not the comparaison with previous release. |
Nah, it is OK to ask. Nobody expects you to read 1000 commit messages. I would personally prefer smaller releases more often, but that's the way it is 🙂 |
I fully understand as I'm an developer too ;) |
@samdurnxn new version of the firmware 6.1.2 should contain the fix, can you test that? |
Hello,
And on the printer screen, the next change value is "N/A". Strange because I add little box in PrusaSlicer with many colors changes with the MMU3. |
Update from my previous test with the 6.1.2 firmware. @danopernis can you confirm that for the moment the remaing time is handle only with M6xx gcode ? If I'm right, can you add the Tx gcode support for the remaining time for a future version ? |
I just update the firmware to 6.2 alpha1. Have you plan to handle this value for both M6xx and Tx gcode or not ? I don't know if it's relevant to many people but for me I need this information to add it on a detached monitoring screen. |
@samdurnxn I was looking into this, but then got distracted by something more important. I am still hoping to fix this at least by final v6.2.0 Thanks for the suggestion about MMU and Tx gcodes, that helped a lot and seems like you are on the right track. |
No problem, I understand. |
@samdurnxn I looked into it some more and the only G-code that sets up time to pause is Technical detour, we need to have those M73 in the instruction stream because it is not possible to put entire G-code to MCU memory and compute actual time. For serial printing that is also impossible, because actual lines of G-code arrive some time in the future. The solution to this problem is for slicer to essentially simulate the printer and insert those M73 G-codes to instruct the printer what to display on the screen. |
@danopernis ah I understand. An issue have been already opened on this bug -> prusa3d/PrusaSlicer#13031 (comment) I had a comment on it. |
Printer model
Mini+
Firmware version
6.0.0, 6.0.3
Upgrades and modifications
None
Printing from...
Prusa Link
Describe the bug
In PrusaSlicer, the option to send progress("Printers -> general -> Supports remaining time") is correctly tick.
For my purpose, I create a python script which read serial data from the printer, every 60s I'd like to know the progress, the remain time and the time until the next change (break or color change). As it's explain in this article, you can get the progress by sending the M73 G-Code without any parameters.
The printer answer this code with :
M73 Progress: 5%
Time left: 0m
Change: 10m
But the values for time left and change are not updated.
How to reproduce
You can reproduce this issue like this :
Expected behavior
Normally, the time left value and the time of next change have to be update like the progress value.
Files
No response
The text was updated successfully, but these errors were encountered: