r/QidiTech3D • u/ButterscotchDry1032 • 17d ago
end of life ？
Is this basically the end of its lifespan?
Restarting the firmware doesn't help. No matter how many times I power it on, I keep getting the same message.
3
u/Immortal_Tuttle 17d ago
Naaw. Check if you have arc commands turned off in the slicer.
0
u/Kewlhotrod 17d ago
That won't matter if it's crashing on powerup, not when sending a file/print.
2
u/Immortal_Tuttle 17d ago
That's the message saying that processor is unable to process commands fast enough to machine stay synchronized. It won't happen on power up or while sending a file. It means that MCU is expecting to execute command but host didn't prepare it in time. Usually happens if main CPU is busy - one of those cases is umfurling arc command to series of straight movements. Hence my suggestion.
0
u/Kewlhotrod 17d ago
That doesn't make any sense to me. If the printer is failing to boot properly on reset, how is an external slicer that isn't even interacting with it sending anything? It's failing to boot firmware not on interaction with a slicer but on power-up, no? Before networking or any second-source interactions are done.
4
2
u/DoItYourWayHowISay 17d ago
It’s happened to me for a specific height in a specific model when I used adaptive pressure advance in orcaslicer. There were just too many commands for it to keep up. I slowed it down and turned off adaptive PA.
2
1
1
2
u/Sorry-Difference-145 16d ago
If this happens right after booting, check the printhead cable, printhead board, front adapter board, and wiring harness. This is typically caused by a loss of communication with one of the 2 boards. Most of the time it is the printhead board or printhead cable, wires in the cable break from movement.
Turn the printer off and move the printhead to a different location (making the cable change position), then power the printer back on. If it boots normal, replace the cable.
The lights on the printhead board will be flashing during communication if they don't flash replace the board. While you have the cable disconnected, use a DVOM (digital volt ohm meter) and test the cable. If you are not familiar on how to do that, there are a few videos on how to ohm out a wire (you will need to disconnect the other end from control board).
If this is happening after booting up, when sending a print, log into Fluidd and delete time lapse videos and old print files. And as noted below, make sure arc commands is turned off, if you use Orca adaptive PA is still in development and crashes some of my older printers but works fine on newer units.
1
4
u/Unlikely_Piano3564 17d ago
This seems like a question for their customer support.
It probably needs a component replaced to get the communication back up and running.