WirelessPrinting
WirelessPrinting copied to clipboard
Printer stop the print randomly
if i start printing with Cura (4.5) with Octoprint-Cura-Plugin (3.5.12) and Continuous build (bf50a18) the printer stop the print randomly. Im using Wemos d1 mini with SD-Card shield Any Ideas?
Can you see via telnet what is going on?
Do you have the same issue with this build? https://github.com/probonopd/WirelessPrinting/releases/tag/bad8e51
Can you see via telnet what is going on?
Nothing unusual.
Do you have the same issue with this build? https://github.com/probonopd/WirelessPrinting/releases/tag/bad8e51
Yes, same issue.
It is necessary to power on the PC? i think if my mac goes to sleepmode, the print is stoping.
Ok, strange. If i open an terminal with telnet and my macbook goes to sleep mode or i hit the button "go to sleep mode", the printer stops the print. If i start my mac again, the print go on.
It is necessary to power on the PC? i think if my mac goes to sleepmode, the print is stoping.
Not for normal operation. With telnet, maybe.
Which kind of printer with which kind of mainboard and firmware are you using?
Which kind of printer with which kind of mainboard and firmware are you using?
Ender2, SKR mini E3 v1.2 with Marlin 2.0.4.4
maybe its not an issue
Could you try e.g., on the Ender-2 with Marlin 1.x?
Sure. It will take some minutes :D
I think i cant install marlin 1.x on the skr mini e3
ah, you don't have the original Ender-2 board left?
i dont think so. There no rx + tx pins left
With telnet connection it took 10 secounds to write "sending"
With telnet connection and sleep mode by mac it took over one minute.
I have modify follow code:
inline void telnetSend(const String line) {
Serial.println("\n sending");
if (serverClient && serverClient.connected()) // send data to telnet client if connected
{
Serial.println("client available");
serverClient.println(line);
Serial.println("sending");
} else {
Serial.println("Client not available");
}
}
What is that line of ?=)(/&$§"§$%()=)&$§$%/)= there, do you have any clue where this might be coming from?
no, sorry. I will try to find out.
BTW. can u reproduce that?
When does this ?=)(/&$§"§$%()=)&$§$%/) occur: Immediately after you connect using telnet or when you send a print job?
i see this if i connect the d1 to Serial-Monitor without printer is connected
Please describe your test setup more completely. What have you connected to what, and what do you do when the ?=)(/&$§"§$%()=)&$§$%/) occurs? Currently I cannot reproduce your results.
if i connect the wemos d1 with an usb cable to my Mac (or Windows); open the Serial-Monitor with the Arduino IDE (Baudrate 115200) and the "?=)(/&$§"§$%()=)&$§$%/)" occurs.
You need to connect the wemos d1 mini to your 3D printer board using the pinout described. Then connect to the wemos d1 mini from your computer via telnet. Everything else won't work because the code will not run if no printer board is attached that responds to the commands...
Ich muss mal deutsch schreiben, weil mein englisch so lala ist, wie du vielleicht gemerkt hast. :)
Mir ist klar, dass ich den D1 mit meinem Drucker verbinden muss, um überhaupt drucken zu können.
Ich habe dieses Setup nur aufgebaut um zu prüfen, warum mein Drucker nicht weiter druckt wenn mein Macbook in den Ruhezustand geht und ich via Telnet dran bin.
Generell ist mir das (https://github.com/probonopd/WirelessPrinting/issues/150#issuecomment-600216686) aufgefallen.
Ich kann aber morgen mal versuchen das nachzustellen, wenn ich den Drucker dran hab
Das Telnet braucht man ja nur zum Debugging, und während der Zeit sollte das Macbook so eingestellt werden dass es nicht in den Ruhezustand geht.
Ja gut. Aber Strange ist es trotzdem. Lass uns hier schließen.
Please add a comment here if you are experience sudden print stops, too. Then we will reopen the ticket.
I experienced this now (WirelessPrinting bad8e51 on Prusa i3).
Argh. Need to see if it is an issue in master still.
We should come up with some large test gcode that we can run on printers without needing any filament... to find out what is going on.
Seesm to happen only with "larger" gcode files?
Does anyone have any ideas how to debug this?
it did it again today, 1mo gcode in spiff, print stoped at 85% saying complete and when I try to dl the gcode back, stop at 85% ..
I just received a wemos and the SD shield to try, could it be that it is link to upload speed / time ?, 1mo gcode seemed very long ..
It looks like the file may be corrupted in the flash ?