#Qidi X Smart 3 MCU Protocol Error

1 messages · Page 1 of 1 (latest)

tawdry pumice
#

Just set up my new XS3, updated the firmware using files from Qidi's site, & re-ran the input shaper per the update's instructions. Unfortunately something must have gone wrong during the update because the input shaper process would not finish & after 30-40 minutes of the printhead shaking I made the mistake of powering it off, thinking that a restart would do the trick.
Now the printer appears to be properly bricked, resulting in Klipper giving me the attached error. I don't know if it's even possible to update the MCU's on this machine myself or downgrade the system back to stock since Qidi has a disappointing lack of documentation. Any help getting this thing up and running would be appreciated.

MCU.png
woven fogBOT
#
AI Help

It sounds like there might have been an issue during the firmware update that caused the printer to malfunction. Unfortunately, if the printer is truly "bricked," the only solution may be to contact Qidi's technical support for assistance in repairing or replacing the printer.

Before doing so, however, you may want to try some basic troubleshooting steps. Unplug the printer from power for a few minutes and then plug it back in. If the printer still won't turn on properly or connect to Klipper, try resetting any relevant settings in Klipper or restoring the printer to its default settings.

If none of these steps work, contact Qidi's technical support team for assistance. They should be able to help you diagnose the issue and either repair or replace the printer if necessary.

WARNING: This response is AI generated and may contain errors.
simple canopy
#

Oh, sorry just checked their update instructions - I would assume that while it finished the system update to that board it didn't flash the new version to the printer's MCU

#

I would rerun the update and see if that prompts it to reflash if you're able to

tawdry pumice
#

I've tried to reflash, but the system thinks it's up-to-date. There's some variety of checks the printer runs between the files on the flash drive & the printers current firmware since you can only update after the machine is already fully booted.

The only thing I can think of is somehow spoofing the files so the printer thinks they are a newer version, but that is beyond me.
Aside from that I might be able to downgrade klipper to the earlier version using a git command, but I don't know how to find the version I would need.

I've sent an email to Qidi as well asking for some help, if they are able to sort me out I'll make sure to update this post.

woven fogBOT
#
This post has been closed due to inactivity.

This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.

tawdry pumice
#

Qidi has sent me a recovery firmware for the printer that caused it to run an update w/o having to reach the boot screen. While it did not fix my issue, it may help someone else who is experiencing a similar problem. I don't know if directly linking the file is allowed, but I've attached a redacted copy of the email they sent.

image.png
woven fogBOT
#
This post has been closed due to inactivity.

This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.

tawdry pumice
#

Qidi will be sending me a replacement board, if that doesn't solve my issue then I don't know what will. I'll keep this thread updated once it arrives.

woven fogBOT
#
This post has been closed due to inactivity.

This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.

tawdry pumice
#

Just installed the replacement EMMC from Qidi & all appears to be fixed. They have also sent a replacement toolhead & several cables as well. A+ support on their end.

#

?solved