As the saying goes… “From your lips to God’s ears”.
This request has been made countless times before and Bambu has steadfastly told the community Uck Fou by deed and by action. As you probably know, the logs are all on the SD card and they are encrypted. That should tell you that they don’t want you knowing why their printers fail. This is all part of their walled garden approach. If you need to know something about their printer which you mistakenly think you own, then you will have to send them the logs and they will tell you what they believe you should know about the product you thought you held title to.
For me, it is not even about proving bad things about their printers. They have been very reliable. I run a business and this would save me a lot of time as I need to keep track of this stuff anyways. It would help me automate the process so I can spend more time running my business. Just sayin,
Logs are saved plaintext to /userdata/ which is eMMC not SD. You’re thinking of the “log export” feature in which the printer compresses all of these logs and encrypts them so your information remains secure when the file is uploaded for support
None of the logs are saved with encryption. also it is really not full of secrets… it’s almost entirely debugging messages that are completely worthless to 99% of people.
Even if you use syslog to assist with development or reverse engineering, a vast majority of it is basically spam. If you don’t believe me, go root your printer and check for yourself. I’ve been using the x1’s syslog for various things for about a year and a half, and I have yet to see evidence of what you’re suggesting.
You’ll get unanimous agreement among the community of “tinkerers”. Think about the improvements the band of brothers at Orca Slicer have done to Bambu Studio and imagine what they could do if they were granted access to the logs and firmware. Sadly, Bambu has made it abundantly clear that this is not going to happen, period!!!
You may want to view this parallel thread on a similar topic posted some time ago.
I don’t remember if it can be done anywhere besides the touchscreen. To clarify though, I’m not saying you can use this log export feature to view your own logs. The file you get from exporting is an encrypted tarball intended for use by BL support. To view your logs, you need root access
Bambu officially supports Firmware R which solely exists to provide a method for rooting their firmware. If they had something to hide, would they really openly support rooting?
It seems only to capture prints sent from Babmu Studio or Babmu Handy, presumably because they go through the Bambu servers. Anything sent from the printer directly either through “Print Again” on the Print Finished screen or from the SD card is left off the list of prints in Bambu Handy.
What method do you use to log and retrieve printer history? I’m using Airtable to log printer health, I just WISH I could seamlessly tie with exported history by printer.