Prusa MK4
Hello Repetier
Are the Dev team going to look into implanting the new Prosa MK4 to the repetier server interface?, it does not look like these printers comes with the USB serial interface for printing but solely on wifi/ethernet connection.
Are the Dev team going to look into implanting the new Prosa MK4 to the repetier server interface?, it does not look like these printers comes with the USB serial interface for printing but solely on wifi/ethernet connection.
even though it does indeed use USB interface instead of SD card for printing.
Kind regards
Kind regards
Comments
With our current solution wireless is often bad even if it works. So many things can break wifi and then print would stop. Question is how we could send files and print from local memory so disconnects would not harm. But that is something I can not say how it would work and if we can do it. It talks encrypted with PrusaConnect but we are not Prusa so question is if it is accessible in some way to do the same. That needs to be tested and evaluated when I can test it my self.
I just got confirmation from Prusa, that the MK4, indeed supports Printing over USB, on a USB C connection, they told me that software like Octoprint etc. would need an update to work.
It might be possible to send the entire G-code to the printers memory, so that disconnection would not harm the print, looking forward to see how that would be resolved inside Repetier. I know that Octoprint have for the MK3, the possibility to write to the SD card for the printer, maybe the USB stick/SD card can be used in a way like this for the MK4, to temporary storage.
Ok that is already good news. Probably some commands working differently, but if it is same as pruse mini it should already work. Anyhow, guess in long run I make extra firmware Description for Buddy Firmware as the have named it.
We currently do not support remote printing. That goes against our logic preventing server commands from working. But at some time we will add that as long as gcode then has no server commands it would work. I think they can have usb stick as permanent memory storage or board has some. After all their software also uploads file first and then starts print, but we will see when I have a device at hand what I can do.
Any updates on here? we stand to recive some printers on friday. (6 units) im planing on hocking them up to Repetier with ethernet if possible.
You guys got a testunit yet?
Let's hope it will arive soon! i might can setup access to on printer and server for remote access for you guys to work on if you want. We arent really going to implant them into the setup before the repetier software can include them.
So far so good - it seems to work fine. I've printed a few things, no problems. The items I have printed are smaller, 4- 6 hour prints. I have QTY 2 - MK3S+ and QTY 1 - MK4 all running on the same Raspberry Pi Server.
I just re-slice the models in Prusa Slicer (2.5.2) with the MK4 profile - and upload the G-code into Repetier. Everything seems to work - I'm getting faster prints with the MK4, auto first layer, etc.
The only odd thing with the MK4 is the display - when sending prints via Repetier - the display doesn't update with the image of the print or the file name of the job from Repetier. The MK4 seems to get stuck on the last job that you printed directly from the MK4's USB memory stick. So the MK4 printer will show the name and image of the last job you printed directly on the MK4 with the proper % complete value - but Repetier will display the proper file name, image and the same % complete value. This doesn't impact printing - it's just a little confusing when you walk by the printer and see the image of one job, while the printer is printing something else.
Portscans shows only port 80/TCP open. nothing else.
No connection as of right now available for TCP uplink, so same limitations as the Prusa Mini unfortunately
https://github.com/prusa3d/Prusa-Link-Web/blob/bc157b2496874f1712165f71ac8521e5c0cb6e07/spec/openapi.yaml
also shows no query call to see what is going on. Hope it is just not in api description since knowing what is being printed and progress would be something I'd like to show at least.
2023-07-13 10:04:13: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:04:13: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-13 10:04:13: Leia: syslog: [669776.356808] usb 1-1.1: USB disconnect, device number 23
2023-07-13 10:04:13: Connection closed during print ... trying reconnect for 10 seconds to continue ...
You see that linux says usb device was disconnected and that is the reason the port stops working.
What might help is in communication settings enabling "Continue print after fast reconnect" which tries to reconnect without resetting printer so it can continue where it stopped.
Apart from this it would be good to know why linux does disconnect usb. So check /var/log/syslog at that timestamp and see if there are more hints. Typical reasons are undervoltage where linux disbles usb to reduce power usage and EMI on usb ports, where the hub disconnects the usb for protectopn for a short while. And of course broken cable where a contact breaks sometimes only, printer resetting and thus disabling usb.
Ansonsten bitte Drucklog aktivieren damit man sieht ob und warum ein Timeout entsteht, wenn es denn die Ursache ist.
Linux meldet nichts warum es trennt, wenn es das also nicht ist kommt es von der Verbindung zum Prusa.
sudo tail -f /var/log/syslog
eingeben und du siehst live was linux loggt. Kabel ziehen und wieder rein stecken. Mit cTrl+C kannst du das logging stoppen.