MMU Data Causes Random New Temps

[Cookietyrant]

Plotly keeps adding duplicate entries that cannot be deleted until rebooted.

[jneilliii]

You have a MMU? The issue stems from the garbage being reported in the temperature report. If you look at the terminal tab you'll see what I'm talking about. Basically with octoprint 1.8.0 all those are being parsed as temperature data, when they shouldn't be. We were discussing this on octoprint discord just the other day.

[Cookietyrant]

Indeed I am running a MMU... Lol it's a bit annoying being it makes the graph nearly unreadable after a time...

Sent from Proton Mail mobile

-------- Original Message -------- On Jun 6, 2022, 4:13 PM, jneilliii wrote:

You have a MMU? The issue stems from the garbage being reported in the temperature report. If you look at the terminal tab you'll see what I'm talking about. Basically with octoprint 1.8.0 all those are being parsed as temperature data, when they shouldn't be. We were discussing this on octoprint discord just the other day.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[jneilliii]

Yeah, discussion on discord seemed to indicate it might be possible to fix with single file plugin to filter out the BS that Prusa had added to the comm layer.

[jneilliii]

@Cookietyrant can you do me a favor and enable serial logging on your OctoPrint instance in settings > serial connection and let it run for a bit to gather those random lines from the printer, and then share your serial.log? This will help get a single file plugin fix implemented.

[Cookietyrant]

Most certainly I can do it when I get home tonight.

Sent from Proton Mail mobile

-------- Original Message -------- On Jun 7, 2022, 9:54 AM, jneilliii wrote:

@.***(https://github.com/Cookietyrant) can you do me a favor and enable serial logging on your OctoPrint instance in settings > serial connection and let it run for a bit to gather those random lines from the printer, and then share your serial.log? This will help get a single file plugin fix implemented.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[jneilliii]

Thanks. You'll have to upload the file via GitHub web interface as email attachments don't come through. You should be able to just drag the file into a comment to upload.

[Cookietyrant]

Here is the Serial Log

[Uploading serial.log…]()

[Cookietyrant]

serial.log

[jneilliii]

go into plugin manager, click get more, and copy/paste the url below into the from URL field and click install. once you restart I think the issue will be resolved.

https://gist.github.com/jneilliii/6a2cbf0056e8c9e5ed5a828fa1694aad/raw/0bfa67bbc2f7cd543e3d83fce3cd60cdcfad1b00/prusa_temp_fix.py

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in 14 days. It will be closed if no further activity occurs in 7 days