›

TEVO Tarantula Repetier Fail

JustinSchubertJustinSchubert
in Repetier-Firmware
when ever I print the Firmware prints about half the Print and then goes into "DRY Run Mode" No matter what I do I cannot get out of it I try a Reset and then try the print agai with the same results... I am Using slicer nor Skenforge or Curia because of my Lack of success with the programs.
I am De-baiting going back to Sprinter seven though I will have to have it connected to a serial connection to print AT LEAST IT WORKS.

Comments

  • JustinSchubertJustinSchubert
    One possible fix Yet to be confirmed replacing the stock SDHC card with one you buy locally Doing my first print Now to confirm if the fix works.

  • JustinSchubertJustinSchubert
    problem is still there and I saw no Error codes from the Log
    "14:34:10.902 : N6803 G1 X76.428 Y105.998 E30.68739*92
    14:34:11.061 : ok 6803
    14:34:11.062 : N6804 G1 X76.428 Y104.828 E30.74851*92
    14:34:11.157 : ok 6804
    14:34:11.255 : N6805 G1 X80.98 Y104.828 E30.98635*101
    14:34:11.269 : ok 6805
    14:34:11.271 : N6806 M104 T0 S0*25
    14:34:11.272 : N6807 M140 S0*92
    14:34:11.272 : N6808 M84*41
    14:34:11.309 : ok 6806
    14:34:11.309 : Other:: working marked decoupled
    14:34:11.309 : heated bed: working
    14:34:11.309 : Error:Printer set into dry run mode until restart!
    14:34:11.309 : ok 6807
    14:34:11.309 : Other:: working marked decoupled
    14:34:11.309 : heated bed: working
    14:34:11.309 : Error:Printer set into dry run mode until restart!
    14:34:11.309 : ok 6808
    14:34:11.683 : N6809 M105*16
    14:34:12.748 : T:132.38 /0 B:89.32 /0 B@:0 @:0
    14:34:12.748 : ok 6809
    14:34:12.761 : T:132.29 /0 B:89.28 /0 B@:0 @:0
    14:34:13.751 : wait
    14:34:14.744 : N6810 M105*24
    14:34:14.757 : ok 6810
    14:34:14.759 : T:130.50 /0 B:88.98 /0 B@:0 @:0
    Here is the code and Dry run mode I know is off.

  • RepetierRepetier
    From log one of the extruders triggered the decoupled test and firmware disabled them for safety. Find the original happening and you will see if it did not heat up fast emough or did not control control range. Then you can adjust that parameter in config so it does not trigger false. Or set decouple time 0 to disable, which is dangerous if it really happens.
Sign In or Register to comment.