-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Original State #7
Comments
I haven't tested it yet. But if you want to go back to the original state, you have to flash the original image from Qidi and then follow the steps to create the firmware. This should restore Klipper 0.10. Additionally I would copy the Moonraker and Klipper package from Qidi as I don't know how up to date the image is. |
I could give you an Guide on how to boot from an USB Drive and write the Image back to EMMC without actually having to buy an EMMC reader. |
I am very interested in this guide. If you could make it available, that would be great. |
Thanks. I don't think the mainboard/EMMC will be a problem, but how to restore print head might be?, unless Qidi's firmware flashes this also? |
You use my guide to flash the firmware. It describes how to flash the print head. This is the part with the two buttons. |
Yes, that is for Katapult, surely the way Qidi had the head setup is different?, otherwise, what would be the point in flashing it at all? |
Catapult is intended to flash the print head without pressing the two buttons during future updates. You can also go the way Qidi describes. Does not matter. |
Qidi describes nothing, as regards the print head. No matter, I have another board for it on the way. This should get it back to square one, hopefully. This 'update', while all good in intentions, does nothing but render the printer in a state of uncertainty. Camera refuses to work, period!, and believe me, I've tried everything to get it to do so. (Video0/1/2/3 etc., Crowsnest, configs, logs etc.) Mainsail or Fluidd, both the same. 'Z' offset and other settings do not save once printer is switched off, or sometimes they do?, but it's dammed irritating regardless. Connection to printer randomly lost, resulting in me having to input these details back into 'Orca' every so often, then having to do the above again. Failed prints galore, despite tweaking any settings. Weird movements of control system via KS, only at times, and several crashes into bed and surroundings with the print head. Listen, I'm not blaming you, as it was a great idea to do this, and I'm the one to blame for making the move in doing so. I will try and start to recover system on Monday. Got a few hints and files to try, so hopefully I can get it back to how it was, if not?, we move on ;), and I'll replace the head board when I receive, which should do it regardless. In any case, I'll post recovery procedure/files when done, once up and running :) P.S. If you decided to replace the EMMC with the 32G version anyway, like myself, and kept the original 8G variant (untouched), and think you can put that back, then flash latest firmware, forget it. System will be bricked. Just thought I'd mention, as nothing is never that easy lol ;) The print head is the problem, once flashed. Mainboard and EMMC are easy to fix. |
QIDITECH/QIDI_PLUS3#27 (comment)
I don't understand your problems there! The guide is exactly how I updated my printer.
Have you checked in the SSH console with
Z-Offset and all other settings made in Mainsail are definitely saved in printer.cfg. Changes made via Klipperscreen are also saved correctly.
I can't understand that either. Possibly call up the web interface directly in the browser. It is possible that your network is causing problems. Have you assigned a fixed IP to the printer?
Can you provide me with the complete config folder? And which printer is it exactly? MAX3-BL or probe etc.? With the printer.cfg etc. provided by me, there can be no bed crashes unless you have configured something completely different.
Even with the original EMMC, everything that was flashed to Klipper 0.12 MUST be flashed to the original Klipper from Qidi. The instructions on how to flash can be found in my guide or at the beginning of this post. Therefore again: First install the original system image. Then create and flash the firmware for the STM chip and the print head based on the Qidi clipper. |
Hey, thx for the extra info, more so regarding print head. Much appreciated :) Will get on to this tomorrow. Don't know why it's not working properly on my system?, but it is what it is. Camera is the one from Qidi, no drivers required, at least none were when I installed it with original setup/firmware. X-PLUS 3 is my printer. Many thanks again. |
All went poorly. To flash the print head, we need to put it into "DFU mode", but the other guide says to just hold 'BOOT' button? Which is it?? No matter, I've tried BOTH, and same result. Motherboard and EMMC fine, as expected, but print head, no way!! :( Be prepared to have another print head board if doing this mod, as that MCU ain't gonna return to stock when flashed, and will never flash back, no matter who says. Yeah it will work, just, and probably update fine?, but the print head is beyond repair after this, sorry. |
I have opened an issue in the Qidi Github. |
Only thing connected to mainboard is an Ethernet cable. Even the Wi-Fi/Bluetooth dongle is removed. Is there a detailed way to flash without Katapult?, as in the way Qidi flashed it originally. Tries recovery files, nothing happens. |
You can mark as fixed. |
Hello.
Can we have the steps to return machine to original state please?
The text was updated successfully, but these errors were encountered: