Manual control but no prints

Been using Repetier server connected to my homemade I3 for a while.  Printed fine yesterday.  Today I can control my bed and nozzle temps manually from the server but it will no longer start to heat when I transfer a job or try to print directly from the server.

Said another way, repetier server controls the printer fine using the manual controls but I can no longer start a print from it.

Any ideas?

Comments

  • Check in printer tab if you have models in the queue. If there are models in waiting queue new prints get added to queue. So you need to start them from queue to start. Only if queue is empty print also starts print as it is then clear which file in queue to print.
  • Nope.  Nothing in the queue.  I restarted the system repetier is on and the printer several times and no luck.  I thought maybe heated bed got turned off but no, it is still set correctly.

    Manual control from repetier but no prints start.



  • Tested again from a fresh start of all systems this evening.  I can send a print job from Cura or I can select one from my drive using direct print.  The temps never turn red and they never seem to even try to heat.  But, the print job progresses through 100% over the amount of time it should have taken to actually print.

    I see the temps both toggle around 20.5 degrees plus or minus a couple of degrees.

    If I manually input a setpoint for the bed or the nozzle from repetier server, they turn red and go up to those temps and toggle around whatever setpoint I gave em plus or minus a degree or two.
  • Oh yeah forgot to say that I have full manual control of moving the nozzle but it never moves while the print job is fake running and the coordinates don't change on the screen.

    This all worked fine for probably 2 months until 2 days ago.

  • Logs look good up until a couple days ago.  now they are full of stuff like:  

    21:58:03.972:  T:20.23 /0.00 B:20.59 /0.00 @:0 B@:0
    > 21:58:03.972: ok
    > 21:58:03.975: echo:Unknown command: "endloop"
    > 21:58:03.976: ok
    > 21:58:03.976: echo:Unknown command: "endfacet"
    > 21:58:03.976: ok
    < 21:58:03.976: N11501 vertex -0.0031418369617313147 -0.0 5.150000095367432
    > 21:58:04.000: echo:Unknown command: "facet normal 0.0 0.0 0.0"
    > 21:58:04.001: ok
    > 21:58:04.021: echo:Unknown command: "outer loop"
    > 21:58:04.021: ok
    > 21:58:04.041: echo:Unknown command: "vertex -0.0031418369617313147 -0.0 5.150000095367432"
    > 21:58:04.042: ok
    < 21:58:04.042: N11502 vertex 0.9237578511238098 -1.1046360731124878 5.150000095367432
    > 21:58:04.065: echo:Unknown command: "vertex 0.9237578511238098 -1.1046360731124878 5.150000095367432"
    > 21:58:04.066: ok
    < 21:58:04.066: N11503 vertex 0.7178581357002258 -1.24880850315094 5.150000095367432
    < 21:58:04.066: N11504 endloop
    < 21:58:04.066: N11505 endfacet

    I get this on all files now including files i printed just days ago.
  • So I save gcode for one of the items I printed a few days ago.  I go to direct print, open that gcode and it refuses to heat again. 

    I copy the commands out of this file and enter them directly into the console and the heat numbers go red and it heats as it should.

    Something is really messed up.

    ;FLAVOR:Marlin
    ;TIME:7097
    ;Filament used: 4.92886m
    ;Layer height: 0.1
    ;Generated with Cura_SteamEngine 3.5.0
    M140 S60
    M105
    M104 S220
    M105
  • Reinstalled the .90 version and no luck.

    Reinstalled the .86 version and no luck.

    Uninstalled and decided to go back to octoprint but then changed my mind and decided to try one more time with the .86 version and now it is working again.

    I did no updates between the 2 months it worked and the day it quit.  I did a ton of updates and reinstalls and it still didn't work.

    I don't mind going round and round with something as long as I learn so I can fis it next time but I have no idea what happened.


  • 21:58:03.972:  T:20.23 /0.00 B:20.59 /0.00 @:0 B@:0
    > 21:58:03.972: ok
    > 21:58:03.975: echo:Unknown command: "endloop"
    > 21:58:03.976: ok
    > 21:58:03.976: echo:Unknown command: "endfacet"

    That is not a gcode file, taht is a stl file in ascii format! Sending this does nothing to the printer, that is correct.

    ;FLAVOR:Marlin
    ;TIME:7097
    ;Filament used: 4.92886m
    ;Layer height: 0.1
    ;Generated with Cura_SteamEngine 3.5.0
    M140 S60
    M105
    M104 S220
    M105

    That is a gcode which you can send.

    So as it looks you are uploading the wrong files which make it not work. Upload gcode and not stl and it should work again.
  • "So as it looks you are uploading the wrong files which make it not work. Upload gcode and not stl and it should work again."

    I got those errors when i sent a print from Cura.  Direct printing that exact gcode file failed, no heat and no motion.  Sending these commands from repetier host console worked.  

    After the reload it all works as it always did.

  • It printed 3 things perfectly and then stopped responding again.  I uninstalled and reinstalled and it started working again.  Reinstalling over one doesn't work.  You have to do a complete uninstall with sudo dpkg -r repetier-server and then install.  

    After the new install of .90 it is working again.

    Normally would not be screwing around with the printer on thanksgiving morning but my wife wants a couple of ornaments for the tree decorating later today.  She and the kids are cooking Thanksgiving lunch and all I have to do is "get those ornaments printed".  Good deal for me.
  • Waht do you mean with stop responding? Server not responding?

    Reinstalling or uninstalling and installing is effectly the same. You just refesh the files with the same copy. However it can make a difference if the sd card is bad. Lately I had the same problem. Suddenly some folders stopped working or content disappeared/files changed. If you do some stuff changing file system you might trick it into a working area but that can change any time. Try a different card (maybe even different type) with new image instead. Then you will see if it is more stable again. Did the same and now same pi is working stable for now.
Sign In or Register to comment.