Bambu Lab has change the debug network log from a plain text file to some kind of encoded file. That broke my print automation that was looking in the debug network log to find the file that had been sent to the printer in order to send a request to reprint it.
Does anyone know how to convert the file back to text, or what kind of encoding is being used?
I think the word you’re actually looking to use may actually be “encrypted” not “encoded”. I think they made the change specifically so that the logs could not be decoded anymore except by BBL.
Agree it would be nice be able to read the network logs.
Not 100% reliable, but the other log does seem to have a print start message in it with a plate number but not a file name.
It also has file load and other messages in it, so i’ve been using a combination of messages to track print starts,
I’ve then been using manual timelapse downloads to track successful print completes as these don’t seem to be logged.
Will look into mqtt stuff to at some point as I suspect there is some useful info avalable there too.
I was using MQTT to control the printer. My program would read the information for the previous print job and use it to send it again after the print had finished. My custom end g code would eject the previous print. With the actual command used to print the initial job in the debug network log it was easy to repeat it.
I actually meant encoded. I did not know if they were encrypted or just changed to a binary format. The file extension is mapped to wireshark on my computer.