Password for log files

I’m getting lots of system errors (XS2060) and one Creality Wiki suggestion is to look at the printer’s log files and see what the error previous to the system errors was and attempt to fix that.

Have downloaded the logs onto a USB but they are PW protected ! anyone know the PW?

creality_2024 or creality2023.

You can find the password when you go to root when these dont work anymore.

Thanks for the reply but dont understand as there is no root directory on the USB drive i’m using. DO you mean root on the printer?

Yes the root on the printer, you can find it on the printer menu.

Have you checked the strain gauge kabel, its the one on top of te the extruder.

I had the error a couple of times it was most of the time when i deleted the bedmesh in fluid then start a new print. At the time i changed the workflow, delete the bedmesh, then in fluid i did a new bedmesh, then starting a print. Dont know this info wil help you in anyway with your problem. I dont need this anymore, i think the have fixed most of the petg problems i had in the firmware.

Thanks, When I try to go to the root it gives me this

“The authenticity of host ‘192.168.1.29 (192.168.1.29)’ can’t be established.

ED25519 key fingerprint is SHA256:hu6lRQVF8SHO+USFk/gI8GuivPm/tS0SyiU7mKUIM6w. This key is not known by any other names.”

Is this “Key Fingerprint”, or part of it the pass word?

OK I got the Password via the printer (creality_2024) but it won’t open the log file I downloaded on the USB
I’ve logged into the printer using ssh - cant see any logs. are they buried somewhere further in?

Thanks

OK I think I found the logs in /mnt/UDISK/creality/userdata/log
dozens of Mb size log files - now it turns into a “needle in hay stack” problems.

My chances of finding any printer error before the system errors in this lot are zilch. I’ll have to run the printer until it generates a printer error and then wait for the next system error - trouble is I haven’t had a printer error for many weeks - maybe months.

I think I have solved the system error 2060 problem, I back graded to 1.1.3.13 and so far so good :grinning_face:

It’s a bit silly that we have to jump through hoops to see our own logs! Try q! ew5rN7@U2s7;L—that’s the one that worked for me on the latest K1/K2 firmware. If that doesn’t work, try 0755cxsw$888.