I tried to create a support ticket but it was impossible because now the X1C printer, updated with the latest firmware v1.07.00.00, exports a log file to the microSD using “.tar.gz” format instead of “.tar” and the online ticket request form by Bambu Lab does not accept this format.
Please Bambu Lab, is it possible to fix this problem?
Thank you.
If you rename it to .tar (rename it by removing ‘.gz’ you can just upload it as normal but I have no idea if they can view it. I did this so I can upload an issue I’m having since the firmware update where by Z doesn’t move enough.
Just upload it in the other files section instead of the logs section.
that doesn’t help, because
you can’t open a ticket without logfile
Hi there,
I apologize for this. It’s a bug
We’re working on solving it shortly
Thanks
Files with extenstion “.tar.gz" are in fact ".tar” files, that have been compressed using a zip tool (gnu zip).
simply unzip the file, then you will get the file in “*.tar” format again.
“tar” stands for “tape archiver”, a tool, that was first invented long ago for the unix os to archive data to magnetic tapes. it is today still most popular in the linux world to store many files and / or folders and subfolders into one “*.tar” file.
I tried opening several tar.gz X1C log files with WinZip and WinRar but in both cases they were detected as corrupted.
hmm - sorry for this, but then something is wrong with these files.
files wih extension “.tar.gz" (or alternatively ".tgz”) usually are zipped tar files.
if you cannot unzip them using any unzip-tool like WinZip or WinRar, the files appear to be mis-created or corrupted in some way.
The files are not corrupted. They are ENCRYPTED.
You can’t decompress an encrypted file with the key.
wow - the zip files are encrypted?
why the heck would anybody do that with log file content?
and why can’t bambulab decrypt those files,
one would think, they should have the key?
ok, Ciprian already texted, that this was a bug,
encrypted log files would not make any sense anyway.
suppenhendl As I stated earlier,
The log files ARE encrypted.
The bug is the system not accepting the files correctly in the ticket, which is being (or has been) corrected.
Bambu Labs CAN decrypt those files, but WE cannot.
The log files ARE encrypted.
Bambu Labs CAN decrypt those files, but WE cannot.
Yeah, and I have no clue why this schould be that way.
Kinda striking, perplexing and annoying, that Bambu Lab is obviously trying to hide the log file content from the users.
Why would they do so? Are they just trying keep product errors and failures secret and invisible for the users?
No, I don’t think it’s anything nefarious or clandestine.
My thoughts are that the logs contain proprietary information related to their firmware and the inner workings of their printers, which would be a trade secret, since their firmware is closed source.
I believe they encrypt these logs to hinder those in the industry who would try to reverse engineer their products.
Hmm - maybe.
But I’ve never ever seen any piece of software revealing it’s inner workings or even part of the source code in a log file.
Software, which can be reverse-engineered by it’s logfile, is not worth anything and I really cannot believe, that this the case with the firmware of any 3d printer, regardless of the brand or maker.
Well, unfortunately, without being able to read through the logs ourselves, we shall never know.
Well, anybody still running a firmware prior to v1.07.00.00 should be able to read the logs, see the contents and thus also see, if they contain any “trade secrets” (really don’t think so)…
The log files have always been encrypted.
OK, did not know this (my x1c, which is my first bambulab printer, has just been shipped and is on it’s way to my place…).
So this means, that bambu has always encrypted the logfiles prior to creating the *.tar files (because tar cannot encrypt by itself), but is now creating password-protected zip files from the tarballs.
Hmm, strange enough, but they should know what they are doing and why…