English
Login

Puppy error

#31522 (CORE One) #35522 (CORE One L)

Relevant for

CORE One
CORE One L
CORE One+
Article is also available in following languages
English
Čeština
Polski
Deutsch
Français
Español
Italiano
日本語

What happened? 

On the Prusa CORE One/+ and Prusa CORE One L, communication with the xBuddy extension board is achieved using the MODBUS protocol. In MODBUS, there are two types of devices: the master and the slave, also known, respectively, as client and server. On Prusa CORE One firmware, the master is the xBuddy, and each slave is called puppy

If one of the puppies does not respond to a request from xBuddy within a specified time period, the printer will show the message: "Waiting for puppies to start timed out".

Error name: Puppy run timeout

Error code: #31522 (CORE One) #35522 (CORE One L)

The error indicates most likely a configuration problem that might have stemmed from the firmware, or a faulty connection of the xBuddy extension board. 

How to fix it? 

Ensure the printer is cold, switched off, and disconnected from the mains before accessing its electronics. 

CORE One/+

Access the xBuddy and xBuddy extension boards by loosening six M3x4bT bolts to remove the cover. Once visible, check the boards for visible damage on their surface, and check the connection between xBuddy and xBuddy extension for any irregularities. 

CORE One L

To access the CORE One L electronics, the first step is locating the Wi-Fi module on the rear panel of the printer. Using a 2.5 mm Allen key, remove the M3x14 screw. Gently pull the Wi-Fi module straight downward to remove it from the printer.

Note that the Wi-Fi module is connected to the electronics with eight spikes.

From the inside of the printer, locate on the rear side the highlighted M3x4bT bolts

Using a T10 Torx key, remove two M3x4rT bolts to release the rear xBuddy box cover. Lift the cover to expose the xBuddy and xBuddy extension boards. 

Once visible, check the boards for visible damage on their surface, and check the connection between xBuddy and xBuddy extension for any irregularities. 

Was this article helpful?
This action is available only to registered users. Please log-in.
 

7 comments

Log in  to post a comment
geo3d
Had this error after a blog of death. Power cycle did not help, but the error cleared with reset.
esamecar
I had the error directly after a reboot. Switched it off and turned it on again - everything back working.
EL RO'IY 3D
Same here: restart did the job. Sadly, this meant a day of printing thrown away just 20 minutes before finishing.

The error appeared after months of daily use. It appeared after installing the new 6.4.0. firmware. To me it could be a software bug.
Timmaey
Restart did the job for me, too!
Andy
My CoreOne L crashed like this too, only 10 days after first use, restart helped.
This is surely some memory leak or software bug.