Overview
If your Gigabot stops during a print and no longer responds to commands, this guide will help you identify the cause and restore normal operation. Follow the checklist below to document what happened, then proceed through the recommended troubleshooting steps.
Information to Collect Before Troubleshooting:
When a print halts unexpectedly, gather the following details. This information is essential for diagnosing the cause:
Is the hot end still heated?
Was the print started over USB or from an SD card?
If using USB, is the computer still connected?
Is the Viki display showing an error message?
Are you using a UPS (Uninterruptible Power Supply)?
Does the Viki display show “Gigabot Ready”?
Was the model sliced recently, and do you still have the project (e.g.,
.factory) file?
Documenting these observations will help determine whether the failure was caused by the G-code, the SD card, power stability, or a hardware-level issue.
Possible Causes:
Several issues can cause Gigabot to stop mid-print and become unresponsive. Common causes include:
-
USB Communication Interruption:
If the print was run over USB, the connection may have dropped or the computer may have entered sleep mode. This can halt the print and lock up the printer.
-
Corrupted or Incomplete G-Code:
If the print head stops at a specific point every time, the G-code file may be incomplete or corrupted.
-
Faulty or Failing SD Card:
SD cards can develop bad sectors or fail over time. This can prevent the printer from reading the next line of G-code.
-
Power Interruption or Power Drop:
Momentary power loss can cause the printer to shut down or freeze. In these cases, the hot end is typically cold and the motors unpowered at the point of failure.
-
Loose or Faulty Electrical Connections:
A loose connector, wiring short, or intermittent electrical fault can cause the control board to reset or hang during a print.
Recommended Troubleshooting Steps:
Follow these steps in order:
-
Print From an SD Card:
If you were printing over USB, switch to printing from an SD card. USB printing is not recommended for long prints due to communication instability.
-
Re-Slice and Re-Export the File:
Re-slice the model using your slicer and export a fresh G-code file. Confirm that the file fully finishes writing to the SD card before removing it.
-
Reformat or Replace the SD Card:
Use a known-good SD card formatted to FAT32. If the current card has corrupted sectors, reformatting or replacing it may resolve the issue.
-
Use a UPS for Long Prints:
A UPS helps prevent resets caused by power dips, brownouts, or short outages.
-
Inspect Wiring and Connectors:
Check for:
Loose screw terminals
Partially seated connectors
Worn or damaged cables
Any exposed wiring that may be shorting
Pay particular attention to power wires and connectors inside the electronics enclosure.
-
Isolate or Replace Suspected Components:
If the issue repeats after completing the above steps, the cause may be a failing control board, power supply, or wiring harness. Components should be tested individually and replaced if faulty.
When to Contact Support:
If you continue to experience mid-print stoppages after completing all troubleshooting steps, please contact re:3D Customer Support at support@re3d.org.
Include the following information:
Photos of the printer, display, and wiring
The G-code file used
Whether the failure occurs at the same point in the print
The model of Gigabot and firmware version
Whether the hot end remained heated during the failure
Whether you were printing from USB or SD
A detailed description will help our team troubleshoot and resolve the issue more quickly.
Comments
0 comments
Please sign in to leave a comment.