Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Xplus3 update issue #40

Open
baron011182 opened this issue Oct 17, 2024 · 22 comments
Open

New Xplus3 update issue #40

baron011182 opened this issue Oct 17, 2024 · 22 comments

Comments

@baron011182
Copy link

I have updated the printer today using the new release build for this device and I have encountered an issue.

When I updated it I got a bank screen mentioning Data Error. I managed to recover it but now I'm getting the following error on the screen and when http into the printer.

Include file '/home/mks/klipper_config/MKS_THR.cfg' does not exist

Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.
Printer is halted

This is on the new build that Qidi released 15hrs ago. How do I fix this issue.

@baron011182
Copy link
Author

9973D552-7E12-4DC3-A7B9-1408BED9710E

@TrollPlayer94
Copy link

How did you manage to recover from the DATA ERROR because nothing is working for me?

@svalsorim
Copy link

I just have white screen after the latest update, i think I just got message update failed check message. What message? Where? Also looking for a way to recover it but i have no working screen anymore

@baron011182
Copy link
Author

baron011182 commented Oct 19, 2024

I managed to get the screen working by using the QD_Plus3_UI5.0 and renaming it to mksscreen.recovery and putting that file onto a usb stick. Enter the usb stick in the printer usb port and switch on. It will do a re-flash on the screen to get that working.

@TrollPlayer94
Copy link

I got too this screen now to after trying this fix, but don't know how to proceed further.

@baron011182
Copy link
Author

I think this has corrupted the klipper and moon raker folder under /home/mks/

Once I ssh into it using mobxterm and copied the files over from qidi own version of Klipper and moon raker I was able to get working again.

@svalsorim
Copy link

Great! Thank you for the update ill try that!

@svalsorim
Copy link

Mine will not accept mksscreen.recovery no matter what i do. I could access it via network but now I lost that too

@QIDITECH
Copy link
Owner

According to your description, I think it is caused by your updating of klipper or moonraker. Restoring it to the default version of firmware should solve the problem.

@baron011182
Copy link
Author

baron011182 commented Oct 21, 2024 via email

@Plexix
Copy link

Plexix commented Oct 21, 2024

I don't understand how Qidi could release such a firmware version like 4.2.15. Not only does it cause the screen to freeze with a white screen of death, but if a user manages to recover using a micro SD card, there's a risk of damaging the printer. While the procedure with the micro SD card may resolve the white screen issue, it doesn't fix the underlying problems with the firmware itself. After switching to version 4.2.15 and performing the initial calibration, like input shaping and setting the Z offset, the printer completely ignores these settings during printing. If you start a print with mesh bed leveling, the printer immediately begins to dig the nozzle into the bed during the initial test line. First, I dealt with the frozen white screen, and now I've damaged my print bed. Qidi can't be serious about this.

@baron011182
Copy link
Author

baron011182 commented Oct 21, 2024 via email

@svalsorim
Copy link

I was going to comment that none of us updated klipper but used official update, but I left it to OP to address it. I’m still dealing with white screen and “data error! “ message.

@whb0514
Copy link
Collaborator

whb0514 commented Oct 22, 2024

9973D552-7E12-4DC3-A7B9-1408BED9710E

Just need the parameter page in the fluidd page, create a MKS_THR.cfg file, save it, and restart the machine to solve this problem. As for why the file is missing, we will look for the reason.

@baron011182
Copy link
Author

baron011182 commented Oct 22, 2024 via email

@herby99999
Copy link

9973D552-7E12-4DC3-A7B9-1408BED9710E

Um dieses Problem zu lösen, benötigen Sie lediglich die Parameterseite auf der Fluidd-Seite, erstellen eine MKS_THR.cfg-Datei, speichern sie und starten den Computer neu. Wir werden nach dem Grund suchen, warum die Datei fehlt.

kann den link nicht öffnen wäre dankbar damit der weiße screen weg geht

@gptech2444
Copy link

gptech2444 commented Oct 23, 2024

Wish I read this before doing the update. This is ridiculous. Now I have to try and unbrick my printer.
image

@mane81
Copy link

mane81 commented Oct 25, 2024

I am experiencing the same issue. Please remove this firmware release and correct it.

@baron011182
Copy link
Author

baron011182 commented Oct 25, 2024 via email

@logiclinux
Copy link

I have just updatet to .Ver 4.2.15 got a blank screen but acces to the Printer via SSH. Then i found the solution to download the file 800_480_PLUS.tft on an sdcard and put this card into the cardslot at the Qidi X-Plus 3 screen (very complicated to reach i had to unscem the screen to rech the slot) Swiching off wait 30 sec. swich on and it installs the frimware for the Screen.
But now i have no more access to the Network adjust,ments via this screen but you see the softkey gets pressed (at the moment no need caus its connected very well via ethernet and wifi). So i have SOC Ver 4.2.15 amd UI Ver 4.2.13 MMC is mot diplayed . When the srenn goes isn sctreensaver mode i cant wake him up by touching it.

@svalsorim
Copy link

For the record, I had not the same problem as the OP, I just had white screen( UI part failed) I got it resolved by repeated mksscreen.recovery updated in my case 5th consecutive time update passed. Maybe try forcing the update few times to see will it resolve your issue. There is a write up in wiki page for a Qidi q1 pro what to do if update failed.

@JozephSchmoe
Copy link

I was able to get past the white screen issues only to run into the Z offset problems. In my case, using the screen to set the Z offset results in a ridiculous -2.68 value. Adding 2mm to that value, for -.68 got me pretty close to what the value should be. This is far from ideal but I can at least print. You'll want to edit the config.mksini file, for anyone who didn't learn that from the last disastrous firmware update.
Do a reboot and Fluuid should see the correct value.
Screenshot 3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests