I found my bed is highly warped and have shimmed it with strips of paper, but I’d like to confirm the level and further optimize it beyond what I can do with my eye and a straight edge. I know that bambu will ask you for a log file if you submit a ticket about a warped bed to confirm how bad it is - how do they extract this info from the log?
I tried power cycling then running the bed level routine from the front panel, dumping the logs, and grabbing the TAR file from /export, but winrar doesn’t recognize it as a valid format. Was hoping to reverse engineer the results of of that. Anyone have more info?
While I’m at it, is there any way to get a gcode console against the x1c? Perhaps I could run G29 directly if that is possible.
Note: at this point I’m not interested in replacing the bed, even though the warping is bad enough to warrant it, I’d rather just shim it and continue printing.
It seems to be an encrypted .tar ball file, a common Linux compression format. Without the passphrase, we cannot extract the data from it, or would need to bruteforce through the encryption which might or might not be possible in a reasonable amount of time.
You could mount a depth probe instead of the nozzle on the printhead and do the heightmap of the heatbed yourself.
Technically tar files aren’t compressed, but they are commonly gzipped to a .tar.gz. This one has no second extension and I haven’t tried to look for any potential file format headers yet. The only thing I can tell from a quick peek in notepad++ is that it doesn’t contain any ASCII header or footer, and no ASCII text that “looks like” a log so yes, definitely either compressed or encrypted in some way. The “_enc” part of the filename also suggests some kind of encryption as you suggested. You wouldn’t happen to know any more about that would you? Probably not likely I could break it anyway, just idle curiosity as a software engineer.
Your suggestion of mounting a depth probe is interesting. Seems a waste when this functionality is already built in but I suppose I’m hitting one of the downsides of a closed system.
Is there no way to get a gcode console and just run G29 and observe the output? Perhaps someone has broken the log file encryption? Or there is some other way to get this data indirectly? I’m hoping someone somewhere has more info and will see this.
People have already found the FTP and MQTT functionality, and I have accessed these myself over the local network. Perhaps there is a telnet port or something that would allow watching log output as well? All I really need is to see the results of the G29 command.
That is true, but I haven’t seen a tar file that wasn’t compressed with gzip in the last decade or two.
I would maybe be possible, I would assume there is some disabled remote monitoring feature inside the firmware that is used internally for debugging and development, but finding it in a firmware we do not even have access to, enabling it might be as hard as decrypting the files.
Might be easier to become a billionaire and just buy Bambu Lab.
I found this, but apparently it’s only a specific (old) firmware version that will output the mesh data via MQTT: Bambulab Bed Mesh NodeRed Configurator
I had actually gone spleunking around the MQTT output myself, but didn’t see this since my firmware is newer. Why would they remove the ability to get this data out?!?!