› ›

Bed Overheats from SD Card, Works perfectly from Repetier Host

3didd3didd
in Extruder & Bed
hey,

Firstly thanks for the advice previously, using the configuration Tool i was able to fix the mirroring problem for the Y Axis.
But I was hoping to ask for some advice, hence the post here.

I am using the Repetier 0.92.8 Firmware.
Printing from Repetier Host every works perfectly.
Printing from SD Card the Bed overheats.

When Printing from the SD Card, the temp rises to about 95 deg, instead of the GCODE 60
The interesting thing is that the Display shows the temp as being 95deg, and how it should be 60 deg.

As this does not occur when i print using Repetier host, this makes me think that it is a Firmware setting, rather than a mechanical/electrical problem.

As i am using a relay to run the heatbed, so i have been using the setting;
#define HEATED_BED_HEAT_MANAGER 2 
#define HEATED_BED_SET_INTERVAL 5000

Sample below of the firmware settings, as far as i know this is all stock standard....
#define HAVE_HEATED_BED 1
#define HEATED_BED_MAX_TEMP 110
#define SKIP_M190_IF_WITHIN 3
#define HEATED_BED_SENSOR_TYPE 1
#define HEATED_BED_SENSOR_PIN TEMP_1_PIN
#define HEATED_BED_HEATER_PIN HEATER_1_PIN
#define HEATED_BED_HEAT_MANAGER 2 
#define HEATED_BED_SET_INTERVAL 5000   
#define HEATED_BED_PID_INTEGRAL_DRIVE_MAX 255
#define HEATED_BED_PID_INTEGRAL_DRIVE_MIN 80
#define HEATED_BED_PID_PGAIN_OR_DEAD_TIME   196
#define HEATED_BED_PID_IGAIN   33
#define HEATED_BED_PID_DGAIN 290
#define HEATED_BED_PID_MAX 255
#define HEATED_BED_DECOUPLE_TEST_PERIOD 300000
#define MIN_EXTRUDER_TEMP 150
#define MAXTEMP 275
#define MIN_DEFECT_TEMPERATURE -10
#define MAX_DEFECT_TEMPERATURE 290


thanks in advance.

Comments

  • RepetierRepetier

    I'd say #define HEATED_BED_MAX_TEMP 110 is the reason.

    From host you can set max. bed temperature as well and I guess that the slider caused a new command with 60°C instead revoking your old 95°C setting. Check the gcode and I think you told slicer to heat bed to 95°C.
  • 3didd3didd
    hi,

    so i checked the gcode file as suggested....

    header of file is as follows; 
    ; generated by Slic3r 1.2.9 on 2016-04-03 at 15:25:04

    ; external perimeters extrusion width = 0.40mm
    ; perimeters extrusion width = 0.67mm
    ; infill extrusion width = 0.67mm
    ; solid infill extrusion width = 0.67mm
    ; top infill extrusion width = 0.67mm

    M107
    M190 S65 ; set bed temperature
    M104 S210 ; set temperature
    G28 ; home all axes
    G1 Z5  ; move z axis down 5mm
    G1 X20 Y20 ; move to edge of bed
    G1 Z0 ; move z axis to home
    M109 S210 ; wait for temperature to be reached
    G21 ; set units to millimeters
    G90 ; use absolute coordinates
    M82 ; use absolute distances for extrusion

    i have checked the GCode for other examples of the M190 Gcode....
    Not found, using notepad++

    So i looked for the string "temp", nothing there.
    So i looked for the string M140, trying to find anything hotter than 65degrees, nothing found.

    didn't want to give you the full file....
    overheating only happens when using the SD card.....
    overheating not happen when using repetier host.....

    any suggestions ?

  • RepetierRepetier
    I agree that the code looks ok regarding bed temperature.

    Do you have a lcd display? If so what does target temperature for bed show when it overheats? Does it still show 65°C?
  • errolterrolt
    Is this is gcode file that is on the SD card? The exact same file that gives you problems?

    Repetier, in the first post he said:
    The interesting thing is that the Display shows the temp as being 95deg, and how it should be 60 deg.



    I think that means that the target is set to 95C?
  • 3didd3didd
    yes i have a 12864 screen on the printer.

    So the interesting this is that....
    As you know the screen has the Target Temp and the Current Temp(what bed is doing now)

    When the thing is over heating... and bear in mind is only over heats the BED, never the Extruder
    The LCD has the;
      Bed Target Temp = 60 deg
      Current Temp = 95 deg

    The fact that it shows both temps, is the bit that bugs me... and why i am asking your thoughts.

    The temp does not shoot up, but is a very gradual thing, over the life of the print.
    The Bed temp will stay normal on Prints using Repetier Host, yet other prints from the SD Card, the temp will increase very slowly through the course of the Print.
    When a print job can take hours, by about mid print, the temp is often way to hot.... have never let it continue the prints, the PLA am printing will have lifted at these temps, printers fall off the bed, leaving the print useless.


  • RepetierRepetier
    Please do the following.
    1. Connect with Repetier-Host and go to temp. screen so you can see bed output.
    2. Start sd print.
    3. Watch bed output. What happens if 60°C is reached. If the output shown goes to 0 and bed still heats up it is a different function setting bed output as well and you have to find out which. Maybe a fan or something else you defined. Also that would not explain why it only happens with sd as it would also do it from host.

    BTW: When did you get the firmware? There was a short time  a version with wrong bed handling when new outputs were added, so updating to latest 0.92.9 might also be a solution.
  • 3didd3didd
    Thanks for the update/feedback.

    I uploaded my existing 0.92.8 configuration file in the the 0.92.9 configuration tool.
    to see if the new firmware will resolve the bed overheating issue.

    Are there any changes i need to make....
    steps.
    1) upload existing 92.8 configuration.h file.
    2) download a full 92.9 firmware.
    3) upload 92.9 firmware in ardurino.

    Results.
    Firmware says it has uploaded.
    screen goes blank.
    re-start machine, screen still blank.
    nothing working.....

    Re-install original 92.8 firmware, machine all back to before.

    Is there a change i need to make in the 92.9 firmware ?
    Am sure is an idiot operator error ???
  • 3didd3didd
    Hi,

    So we replaced the motherboard, and all of the problems went away....
    Was not related to the firmware at all, thank goodness.


    For the Firmware not loading, blank screen.
    This was caused by not having a watchdog enabled and more than a single language in the firmware configuration tool.

    thanks again.
Sign In or Register to comment.