If the extruder is fine you must be able to easily push filament through the complete hotend until it leaves the nozzle.Ĭheck that the filament spool can move with ease on it's mounting platform (roller frame). Then we have to unscrew the assembly to remove old filament pieces and small flakes maybe. In this case it is not possible to push filament through the heated hotend - wether by hand nor by using extrude command. The Aero Extruder sometimes fails to extrude filament because it is clogged. Use some old cloth to the grab old filament when hotend is hot enough. Cleaning also gently helps to better calibrate the nozzle. Otherwise unneccesary fumes from old sticky PLA might get into air.
Clean the hotendīefore you print please check if the nozzle is clean. I have even tried putting in: G4 S60, in both Simplf圓d and the "run after job" section in Repetier Server to see if a delay would help but the printer still shuts a few seconds before the last layer is finished.Hardware pre-flight checks (filament guiding and extruder) When I take out the script from Repetier Server the print finished and the nozzle and bed finish their end movements. G1 X0 Y200 F2400 prepare for part removal When I add printerOff into the "run after job" section of the event dependent gcodes section, the printer shuts off before the last layer is completely finished, and the still hot remains on the part although my end script in Simplf圓d as follows: Additionally in the extcommands.xml I added a command and confirmed that it also works when I manually enter " printerOff" in the gcode console. py script (printerOff) as per the external commands instructions to toggle a relay attached to my Rasppi, works great to turn the printer off with button click in the Repetier Server menu. Thanks in advance & a big *thumbs up* for your work!
#Repetier server bed heat not turning off how to
RH on Win7 (or Linux as soon I can figure out how to transfer slicer-settings from here to there without getting a headache and/or spending more time faffing around with instead of actually printing something)
Now, I'm "beinahe fertig" with my new and somewhat bigger printer (X/Y ~400mm) and me thinks this is going to hurt somewhat because with long movements (think brim nearly maxing out the bed) with a buffer of 16 might run some time before the new speed actually is in action and this is quite "mühsam" 'cos one never knows whether the extruder starts losing steps at 140% (or are we at 160% already?) or there's something completely different going astray right now (warped bed, miscalibration and so on.)Īm I talking out of my posterior here or is this something that can (and possibly will, who knows -)) be addressed by RS / RH? With my current printer -xBot 150 from hence my username- this ain't so bad (BufSize 16, X/Y-MAX ~130) but it's still noticeable that shows the new speed way before the printer actually picks up "the new speed". So the impatient printer-admin decides to give a bump (possible reasons: too conservative settings in, "da geht noch mehr!") Deleting the empty file and restarting server helped (it stopped crashing and I could add and configure the printer again). So, it looks like if printer config file becomes empty (or damaged?) the server crashes and no longer shows web interface. I've checked the file size for OLP.xml and it was zero. Importing wifi connections from /var/lib/Repetier-Server/database/repetier-network-stored.xmlĪborterReading printer configurations. Importing wifi connections from /var/lib/Repetier-Server/database/repetier-network.xml Importing wifi connections from /boot/repetier-network.xml Starting printjob manager thread for unknown
Reading printer config /var/lib/Repetier-Server/configs/OLP.xmlĮrror: No element found in line 1 column 0 I tried starting in manually from the console and here is what I saw in output: I restarted the Pi again and after that it no longer works and shows 502 bad gateway error. I tried configuring this unknown printer but it froze on Automatic settings import from firmware. Then after the reboot it couldn't find the printer and said there is some unknown printer connected. There were some issues with the web interface, so I restarted the pi. I'm running Repetier server image on Raspberry Pi (version 0.85.2).