Follow

Max Temp Error

Overview

If the Viki displays the error message “Max Temp,” the hot end or bed is reading temperature above the upper limit set in firmware. (Bed - 150°C, Hot end - GB2-245°C, GB3-350°C on some and 400°C on others). If the hot end temperature is reading above 900C, it is a sign that the thermocouple wire or thermocouple extension wire has a break in the circuit.

Before proceeding, please collect and record the following data: 

  • Gigabot serial number
  • Photo of the Viki with the error message
  • Take a screenshot of the Simplify3D temperature graph when the error occurs
  • .factory file and .gcode of part you were printing
  • Did max temp error happen:
    • While heating the bed?
    • While heating the hot end?
    • During the print? 

Possible Causes: 

  1. Hot end temp set above maximum temperature in Simplify3D.
  2. Break/short circuit in hot end or bed thermocouple (GB3 and GB3+)
  3. Break/short circuit in hot end or bed thermocouple extension wire(GB3 and GB3+)
  4. Break/short circuit with thermistor (GB2)
  5. Break/short circuit in thermistor extension wire (GB2)
  6. Thermocouple daughter board malfunctioning (GB3 and GB3+) BED ONLY
  7. Thermocouple daughter board jumper wire is loose (GB3 and GB3+) BED ONLY

Possible Solutions:

  1. Reduce temperature in Simplify3D
  2. Replace thermocouple. You can purchase replacement thermocouples here: Link to shop
    1. Instructions to replace the hot end thermocouple 
    2. Instructions to replace the bed thermocouple
  3. Replace thermocouple extension wire
  4. Replace thermistor
  5. Replace daughterboard
  6. Replace jumper wires

Questions or concerns? Reach out to our support team at support@re:3D.org or open a support ticket

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

1 Comments

  • 0
    Avatar
    stan one

    I get the MAX TEMP error when I try to dual color print using both extruder.

    Extruder left does full prints test prints solo...  so does Extruder right.  Not sure why I am getting this error.  

Please sign in to leave a comment.