Prusa MK4

zekcode

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.

even though it does indeed use USB interface instead of SD card for printing.

Kind regards

zekcode

And even if the the printer supports direct printing on USB from repetier, are the dev team going to look into implanting wireless connection to printers, to remove the hassel of cables/wires and USB hubs? :)

Repetier

We are trying to get hands on a test device at the moment. Announcement says it uses Buddy Firmware which is same base as Pruse Mini which works with usb, so I assume for now that this is at least a way that works.

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.

zekcode

Repetier wrote
We are trying to get hands on a test device at the moment. Announcement says it uses Buddy Firmware which is same base as Pruse Mini which works with usb, so I assume for now that this is at least a way that works.

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.

Hello R,

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.

Repetier

> 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.
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.

zekcode

Repetier wrote
> 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.
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.

Hello R,

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? :)

Repetier

No unit so far. But will be glad for any feedback once you have it. Test first with usb until it works. Same settings should work with tcp if it is a put through telnet like port. Maybe use a portscanner to see all available ports on prusa for testing.

zekcode

Repetier said:

No unit so far. But will be glad for any feedback once you have it. Test first with usb until it works. Same settings should work with tcp if it is a put through telnet like port. Maybe use a portscanner to see all available ports on prusa for testing.

Hello R,

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. :) i will ofcorce fidle around with it my self also :)

Grizak

Hi - I received my MK4 and added it to my Repetier Servo Pro with a USB connection (The MK4 has a USB-C connector). Installation was simple - the same as the MK3S+.

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.

zekcode

Just got some printers delivered.
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 :(

Repetier

Sounds correct. Port 80 is for web gui with browsers and if there is no other port only usb would be possible.

zekcode

Repetier wrote
Sounds correct. Port 80 is for web gui with browsers and if there is no other port only usb would be possible.

There is indeed no other ports, just like the mini... i just talked to prusa, they said it was on the roadmap to connect to printers like USB, via ethernet. But inputshapeing was top priorities at the momemt. There is no way for the Repetiere software to add printers PrusaLink api?

Repetier

Connecting to storage and print type systems is planned for a later stage. The main problem here is we need to strip 90% of the functions for this as most of the things will not work when the printer controls print like server code, live preview, time prediction. But PrusaLink API
https://github.com/prusa3d/Prusa-Link-Web/blob/bc157b2496874f1712165f71ac8521e5c0cb6e07/spec/openapi.yaml<br/>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.

Martin81

Are there any new information concerning the mk4? I use RS with the mk4 IS alpha and it works except the % status. I did about 10 prints now. Today the mk4 suddenly stopped printing.

Repetier

If it happens frequently that a printer stop, you should start enabling logging so you can see and eventually post here what happens at that time. Since it uses same firmware as the mini zou might need to enable ping pong mode. The mini gets in trouble sometime without and then commands are executed with some offset meaning you send a command and you must send more commands before that one gets executed at all and that can cause blocking in the end.

Martin81

Thx! I compared the settings with my mk3s+ and yes the PingPong was disabled. I will enable it and try again.

<blockquote class="Quote">2023-07-13 08:55:40: Project Job:gcode#9a3e81e3-e58c-4bcc-bb6c-0514c8bf779c#/var/lib/Repetier-Server/projects/Schnellkupplung V6 Biturbo/files/Set_SK+HT110_V5_0.6n_0.2mm_PLA_MK3S_6h42m.gcode
2023-07-13 08:55:46: Time analysing /var/lib/Repetier-Server/projects/Schnellkupplung V6 Biturbo/files/Set_SK+HT110_V5_0.6n_0.2mm_PLA_MK3S_6h42m.gcode:5410297 us
2023-07-13 08:55:46: Executing: /usr/local/Repetier-Server/bin/RepetierRenderer -i "/var/lib/Repetier-Server/projects/Schnellkupplung V6 Biturbo/.gcodes/Set_SK+HT110_V5_0.6n_0.2mm_PLA_MK3S_6h42m.gcode/Set_SK+HT110_V5_0.6n_0.2mm_PLA_MK3S_6h42m.layer" -p "/var/lib/Repetier-Server/projects/Schnellkupplung V6 Biturbo/.gcodes/Set_SK+HT110_V5_0.6n_0.2mm_PLA_MK3S_6h42m.gcode" -c /var/lib/Repetier-Server/database/renderer.json
2023-07-13 08:56:05: Reading configuration file ...

Input file: /var/lib/Repetier-Server/projects/Schnellkupplung V6 Biturbo/.gcodes/Set_SK+HT110_V5_0.6n_0.2mm_PLA_MK3S_6h42m.gcode/Set_SK+HT110_V5_0.6n_0.2mm_PLA_MK3S_6h42m.layer

Rendering shadows ...3.64446 seconds.

Rendering gcode ...12.3131 seconds.

Number of end triangles: 951092

Number of normal triangles: 10629332

Rendering background ...

Time for raytracing: 2.71298 seconds.

images stored.

Computation time: 19.4308 seconds

2023-07-13 08:56:10: Too many push messages in short time. Message not send: Print Solo_HT100_V6_0.6n_0.2mm_PLA_MK3S_3h13m for printer Chewie continued from busy state.
2023-07-13 08:56:10: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-13 08:56:45: Too many push messages in short time. Message not send: Print Solo_HT100_V6_0.6n_0.2mm_PLA_MK3S_3h13m for printer Luke is busy for a long time.
2023-07-13 08:56:45: Too many push messages in short time. Message not send: Print Solo_HT100_V6_0.6n_0.2mm_PLA_MK3S_3h13m for printer Luke continued from busy state.
2023-07-13 08:57:35: Too many push messages in short time. Message not send: Print Solo_HT100_V6_0.6n_0.2mm_PLA_MK3S_3h13m for printer Chewie continued from busy state.
2023-07-13 08:57:35: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

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 ...
2023-07-13 10:04:13: Port closed for Leia
2023-07-13 10:04:13: Connection closed: Leia
2023-07-13 10:04:13: Connection continued: Leia
2023-07-13 10:04:14: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:04:14: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-13 10:04:14: Leia: syslog: [669776.356808] usb 1-1.1: USB disconnect, device number 23
2023-07-13 10:04:14: Leia: syslog: [669776.591316] usb 1-1.1: new full-speed USB device number 24 using xhci_hcd
2023-07-13 10:04:14: Leia: syslog: [669776.703346] usb 1-1.1: New USB device found, idVendor=2c99, idProduct=000d, bcdDevice= 1.00
2023-07-13 10:04:14: Leia: syslog: [669776.703366] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2023-07-13 10:04:14: Leia: syslog: [669776.703372] usb 1-1.1: Product: Original Prusa MK4
2023-07-13 10:04:14: Leia: syslog: [669776.703377] usb 1-1.1: Manufacturer: Prusa Research (prusa3d.com)
2023-07-13 10:04:14: Leia: syslog: [669776.703382] usb 1-1.1: SerialNumber: 4914-27145608112154302
2023-07-13 10:04:14: Leia: syslog: [669776.710795] cdc_acm 1-1.1:1.0: ttyACM3: USB ACM device
2023-07-13 10:04:14: Leia: syslog: checking bus 1, device 24: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
2023-07-13 10:04:14: Leia: syslog: checking bus 1, device 24: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
2023-07-13 10:04:14: Leia: syslog: [669778.149011] usb 1-1.1: USB disconnect, device number 24
2023-07-13 10:04:14: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:04:14: Port closed for Leia
2023-07-13 10:04:14: Connection closed: Leia
2023-07-13 10:04:15: Connection continued: Leia
2023-07-13 10:05:06: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:05:06: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-13 10:05:06: Leia: syslog: [669829.612136] usb 1-1.1: USB disconnect, device number 25
2023-07-13 10:05:06: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:05:06: Port closed for Leia
2023-07-13 10:05:06: Connection closed: Leia
2023-07-13 10:05:06: Connection continued: Leia
2023-07-13 10:05:08: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:05:08: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-13 10:05:08: Leia: syslog: [669829.612136] usb 1-1.1: USB disconnect, device number 25
2023-07-13 10:05:08: Leia: syslog: [669829.847865] usb 1-1.1: new full-speed USB device number 26 using xhci_hcd
2023-07-13 10:05:08: Leia: syslog: [669829.960748] usb 1-1.1: New USB device found, idVendor=2c99, idProduct=000d, bcdDevice= 1.00
2023-07-13 10:05:08: Leia: syslog: [669829.960780] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2023-07-13 10:05:08: Leia: syslog: [669829.960794] usb 1-1.1: Product: Original Prusa MK4
2023-07-13 10:05:08: Leia: syslog: [669829.960805] usb 1-1.1: Manufacturer: Prusa Research (prusa3d.com)
2023-07-13 10:05:08: Leia: syslog: [669829.960815] usb 1-1.1: SerialNumber: 4914-27145608112154302
2023-07-13 10:05:08: Leia: syslog: [669829.970575] cdc_acm 1-1.1:1.0: ttyACM3: USB ACM device
2023-07-13 10:05:08: Leia: syslog: checking bus 1, device 26: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
2023-07-13 10:05:08: Leia: syslog: checking bus 1, device 26: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
2023-07-13 10:05:08: Leia: syslog: [669832.172955] usb 1-1.1: USB disconnect, device number 26
2023-07-13 10:05:08: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:05:08: Port closed for Leia
2023-07-13 10:05:08: Connection closed: Leia
2023-07-13 10:05:09: Connection continued: Leia
2023-07-13 10:06:09: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:06:09: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:06:09: Port closed for Leia
2023-07-13 10:06:09: Connection closed: Leia
2023-07-13 10:06:09: Connection continued: Leia
2023-07-13 10:27:50: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:27:50: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-13 10:27:50: Leia: syslog: [671193.526499] usb 1-1.1: USB disconnect, device number 28
2023-07-13 10:27:50: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:27:50: Port closed for Leia
2023-07-13 10:27:50: Connection closed: Leia
2023-07-13 10:27:50: Connection continued: Leia
2023-07-13 10:32:47: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:32:47: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-13 10:32:47: Leia: syslog: [671490.786105] usb 1-1.1: USB disconnect, device number 29
2023-07-13 10:32:47: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:32:47: Port closed for Leia
2023-07-13 10:32:47: Connection closed: Leia
2023-07-13 10:32:47: Connection continued: Leia
2023-07-13 10:36:29: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:36:29: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-13 10:36:29: Leia: syslog: [671712.515415] usb 1-1.1: USB disconnect, device number 30
2023-07-13 10:36:29: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:36:29: Port closed for Leia
2023-07-13 10:36:29: Connection closed: Leia
2023-07-13 10:36:29: Connection continued: Leia
2023-07-13 10:46:12: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:46:12: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:46:12: Port closed for Leia
2023-07-13 10:46:12: Connection closed: Leia
2023-07-13 10:46:12: Connection continued: Leia
2023-07-13 10:46:19: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:46:19: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-13 10:46:19: Leia: syslog: [672295.769219] usb 1-1.1: USB disconnect, device number 31
2023-07-13 10:46:19: Leia: syslog: [672295.999354] usb 1-1.1: new full-speed USB device number 32 using xhci_hcd
2023-07-13 10:46:19: Leia: syslog: [672296.113181] usb 1-1.1: New USB device found, idVendor=2c99, idProduct=000d, bcdDevice= 1.00
2023-07-13 10:46:19: Leia: syslog: [672296.113200] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2023-07-13 10:46:19: Leia: syslog: [672296.113207] usb 1-1.1: Product: Original Prusa MK4
2023-07-13 10:46:19: Leia: syslog: [672296.113212] usb 1-1.1: Manufacturer: Prusa Research (prusa3d.com)
2023-07-13 10:46:19: Leia: syslog: [672296.113216] usb 1-1.1: SerialNumber: 4914-27145608112154302
2023-07-13 10:46:19: Leia: syslog: [672296.120133] cdc_acm 1-1.1:1.0: ttyACM3: USB ACM device
2023-07-13 10:46:19: Leia: syslog: checking bus 1, device 32: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
2023-07-13 10:46:19: Leia: syslog: checking bus 1, device 32: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
2023-07-13 10:46:19: Leia: syslog: [672302.426486] usb 1-1.1: USB disconnect, device number 32
2023-07-13 10:46:19: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:46:19: Port closed for Leia
2023-07-13 10:46:19: Connection closed: Leia
2023-07-13 10:46:19: Connection continued: Leia
2023-07-13 10:48:16: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:48:16: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-13 10:48:16: Leia: syslog: [672420.204145] usb 1-1.1: USB disconnect, device number 33
2023-07-13 10:48:16: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:48:16: Port closed for Leia
2023-07-13 10:48:16: Connection closed: Leia
2023-07-13 10:48:17: Connection continued: Leia
2023-07-13 10:48:26: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:48:26: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-13 10:48:26: Leia: syslog: [672420.204145] usb 1-1.1: USB disconnect, device number 33
2023-07-13 10:48:26: Leia: syslog: [672420.436565] usb 1-1.1: new full-speed USB device number 34 using xhci_hcd
2023-07-13 10:48:26: Leia: syslog: [672420.551005] usb 1-1.1: New USB device found, idVendor=2c99, idProduct=000d, bcdDevice= 1.00
2023-07-13 10:48:26: Leia: syslog: [672420.551037] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2023-07-13 10:48:26: Leia: syslog: [672420.551050] usb 1-1.1: Product: Original Prusa MK4
2023-07-13 10:48:26: Leia: syslog: [672420.551061] usb 1-1.1: Manufacturer: Prusa Research (prusa3d.com)
2023-07-13 10:48:26: Leia: syslog: [672420.551072] usb 1-1.1: SerialNumber: 4914-27145608112154302
2023-07-13 10:48:26: Leia: syslog: [672420.566284] cdc_acm 1-1.1:1.0: ttyACM3: USB ACM device
2023-07-13 10:48:26: Leia: syslog: checking bus 1, device 34: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
2023-07-13 10:48:26: Leia: syslog: checking bus 1, device 34: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
2023-07-13 10:48:26: Leia: syslog: [672430.189656] usb 1-1.1: USB disconnect, device number 34
2023-07-13 10:48:26: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:48:26: Port closed for Leia
2023-07-13 10:48:26: Connection closed: Leia
2023-07-13 10:48:27: Connection continued: Leia
2023-07-13 10:48:30: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:48:30: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-13 10:48:30: Leia: syslog: [672430.189656] usb 1-1.1: USB disconnect, device number 34
2023-07-13 10:48:30: Leia: syslog: [672430.424660] usb 1-1.1: new full-speed USB device number 35 using xhci_hcd
2023-07-13 10:48:30: Leia: syslog: [672430.537965] usb 1-1.1: New USB device found, idVendor=2c99, idProduct=000d, bcdDevice= 1.00
2023-07-13 10:48:30: Leia: syslog: [672430.537985] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2023-07-13 10:48:30: Leia: syslog: [672430.537991] usb 1-1.1: Product: Original Prusa MK4
2023-07-13 10:48:30: Leia: syslog: [672430.537996] usb 1-1.1: Manufacturer: Prusa Research (prusa3d.com)
2023-07-13 10:48:30: Leia: syslog: [672430.538001] usb 1-1.1: SerialNumber: 4914-27145608112154302
2023-07-13 10:48:30: Leia: syslog: [672430.551683] cdc_acm 1-1.1:1.0: ttyACM3: USB ACM device
2023-07-13 10:48:30: Leia: syslog: checking bus 1, device 35: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
2023-07-13 10:48:30: Leia: syslog: checking bus 1, device 35: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
2023-07-13 10:48:30: Leia: syslog: [672433.774243] usb 1-1.1: USB disconnect, device number 35
2023-07-13 10:48:30: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:48:30: Port closed for Leia
2023-07-13 10:48:30: Connection closed: Leia
2023-07-13 10:48:30: Connection continued: Leia
2023-07-13 10:48:52: error: Reading conection failed: End of file. Closing connection.
2023-07-13 10:48:52: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-13 10:48:52: Leia: syslog: [672456.049431] usb 1-1.1: USB disconnect, device number 36
2023-07-13 10:48:52: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-13 10:48:52: Port closed for Leia
2023-07-13 10:48:52: Connection closed: Leia
2023-07-13 10:49:03: Connection continued: Leia
2023-07-13 10:49:03: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-13 11:28:55: Connection config for Leia changed, reconnecting.
2023-07-13 11:28:55: error: Reading closed serial conection failed: Operation canceled
2023-07-13 11:28:55: Port closed for Leia
2023-07-13 11:28:55: Connection closed: Leia
2023-07-13 11:28:55: No valid response seen within 10 seconds from printer, restarting connection
2023-07-13 11:28:57: Connection started: Leia
2023-07-13 11:28:57: Internal reset printer Leia
2023-07-13 11:28:57: Reset printer Leia

Repetier

I fear it will not help when I see this in your log:
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.

Martin81

I have a new abort and here is the server log

<blockquote class="Quote">2023-07-14 16:26:13: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:26:24: error: Reading conection failed: End of file. Closing connection.
2023-07-14 16:26:24: Leia: Your OS syslog contains these messages close to this disconnect that might help to understand:
2023-07-14 16:26:24: Leia: syslog: [97068.190454] usb 1-1.1: USB disconnect, device number 14
2023-07-14 16:26:24: Connection closed during print ... trying reconnect for 10 seconds to continue ...
2023-07-14 16:26:24: Port closed for Leia
2023-07-14 16:26:24: Connection closed: Leia
2023-07-14 16:26:35: Connection continued: Leia
2023-07-14 16:26:35: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:26:49: Job created: /var/lib/Repetier-Server/printer/Han/jobs/00000024_FH_OSVAC_0.6n_0.2mm_PLA_MK3S_4h50m.u
2023-07-14 16:26:49: finish job creation /var/lib/Repetier-Server/printer/Han/jobs/00000024_FH_OSVAC_0.6n_0.2mm_PLA_MK3S_4h50m.u
2023-07-14 16:26:49: start printjob FH_OSVAC_0.6n_0.2mm_PLA_MK3S_4h50m on printer Han
2023-07-14 16:26:49: Imported FH_OSVAC_0.6n_0.2mm_PLA_MK3S_4h50m size:22449679
2023-07-14 16:26:49: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:26:49: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:26:49: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:26:50: Updating info for /var/lib/Repetier-Server/printer/Han/jobs/00000024_FH_OSVAC_0.6n_0.2mm_PLA_MK3S_4h50m.g printer Han
2023-07-14 16:26:55: Time analysing /var/lib/Repetier-Server/printer/Han/jobs/00000024_FH_OSVAC_0.6n_0.2mm_PLA_MK3S_4h50m.g:4525229 us
2023-07-14 16:26:55: LUA job rendering.render#{"id":24,"image":"/var/lib/Repetier-Server/printer/Han/jobs/00000024_FH_OSVAC_0.6n_0.2mm_PLA_MK3S_4h50m_l.png","layer":"/var/lib/Repetier-Server/printer/Han/jobs/00000024_FH_OSVAC_0.6n_0.2mm_PLA_MK3S_4h50m.layer","list":"jobs","slug":"Han"}
2023-07-14 16:26:55: Executing: /usr/local/Repetier-Server/bin/RepetierRenderer -i /var/lib/Repetier-Server/printer/Han/jobs/00000024_FH_OSVAC_0.6n_0.2mm_PLA_MK3S_4h50m.layer -c /var/lib/Repetier-Server/database/renderer.json
2023-07-14 16:27:04: Job created: /var/lib/Repetier-Server/printer/Chewie/jobs/00000019_GCM_DN32_0.6n_0.2mm_PLA_MK3S_6h16m.u
2023-07-14 16:27:05: finish job creation /var/lib/Repetier-Server/printer/Chewie/jobs/00000019_GCM_DN32_0.6n_0.2mm_PLA_MK3S_6h16m.u
2023-07-14 16:27:05: Updating info for /var/lib/Repetier-Server/printer/Chewie/jobs/00000019_GCM_DN32_0.6n_0.2mm_PLA_MK3S_6h16m.g printer Chewie
2023-07-14 16:27:05: start printjob GCM_DN32_0.6n_0.2mm_PLA_MK3S_6h16m on printer Chewie
2023-07-14 16:27:05: Imported GCM_DN32_0.6n_0.2mm_PLA_MK3S_6h16m size:24475836
2023-07-14 16:27:05: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:27:05: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:27:05: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:27:10: Time analysing /var/lib/Repetier-Server/printer/Chewie/jobs/00000019_GCM_DN32_0.6n_0.2mm_PLA_MK3S_6h16m.g:5484106 us
2023-07-14 16:27:16: Reading configuration file ...

Input file: /var/lib/Repetier-Server/printer/Han/jobs/00000024_FH_OSVAC_0.6n_0.2mm_PLA_MK3S_4h50m.layer

Rendering shadows ...3.23152 seconds.

Rendering gcode ...13.8306 seconds.

Number of end triangles: 2181036

Number of normal triangles: 10369292

Rendering background ...

Time for raytracing: 2.70883 seconds.

images stored.

Computation time: 20.477 seconds

2023-07-14 16:27:16: LUA job rendering.render#{"id":19,"image":"/var/lib/Repetier-Server/printer/Chewie/jobs/00000019_GCM_DN32_0.6n_0.2mm_PLA_MK3S_6h16m_l.png","layer":"/var/lib/Repetier-Server/printer/Chewie/jobs/00000019_GCM_DN32_0.6n_0.2mm_PLA_MK3S_6h16m.layer","list":"jobs","slug":"Chewie"}
2023-07-14 16:27:16: Executing: /usr/local/Repetier-Server/bin/RepetierRenderer -i /var/lib/Repetier-Server/printer/Chewie/jobs/00000019_GCM_DN32_0.6n_0.2mm_PLA_MK3S_6h16m.layer -c /var/lib/Repetier-Server/database/renderer.json
2023-07-14 16:27:37: Reading configuration file ...

Input file: /var/lib/Repetier-Server/printer/Chewie/jobs/00000019_GCM_DN32_0.6n_0.2mm_PLA_MK3S_6h16m.layer

Rendering shadows ...3.34848 seconds.

Rendering gcode ...14.4075 seconds.

Number of end triangles: 1607796

Number of normal triangles: 11819656

Rendering background ...

Time for raytracing: 2.82351 seconds.

images stored.

Computation time: 21.328 seconds

2023-07-14 16:28:46: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:28:46: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:29:00: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:29:00: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:29:48: Too many push messages in short time. Message not send: Print GCM_DN32_0.6n_0.2mm_PLA_MK3S_6h16m for printer Chewie continued from busy state.
2023-07-14 16:29:48: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2023-07-14 16:30:03: Too many push messages in short time. Message not send: Print FH_OSVAC_0.6n_0.2mm_PLA_MK3S_4h50m for printer Han is busy for a long time.
2023-07-14 16:30:03: Too many push messages in short time. Message not send: Print FH_OSVAC_0.6n_0.2mm_PLA_MK3S_4h50m for printer Han continued from busy state.
2023-07-14 16:31:06: Too many push messages in short time. Message not send: Print GCM_DN32_0.6n_0.2mm_PLA_MK3S_6h16m for printer Chewie continued from busy state.
2023-07-14 16:31:06: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

and also the syslog

<blockquote class="Quote">Jul 14 16:25:54 RepetierServer systemd[1]: Starting Time & Date Service...
Jul 14 16:25:54 RepetierServer dbus-daemon[367]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jul 14 16:25:54 RepetierServer systemd[1]: Started Time & Date Service.
Jul 14 16:26:24 RepetierServer kernel: [97068.190454] usb 1-1.1: USB disconnect, device number 14
Jul 14 16:26:24 RepetierServer systemd[1]: systemd-timedated.service: Succeeded.
Jul 14 16:26:35 RepetierServer kernel: [97078.658355] usb 1-1.1: new full-speed USB device number 15 using xhci_hcd
Jul 14 16:26:35 RepetierServer kernel: [97078.768146] usb 1-1.1: New USB device found, idVendor=2c99, idProduct=000d, bcdDevice= 1.00
Jul 14 16:26:35 RepetierServer kernel: [97078.768165] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 14 16:26:35 RepetierServer kernel: [97078.768171] usb 1-1.1: Product: Original Prusa MK4
Jul 14 16:26:35 RepetierServer kernel: [97078.768176] usb 1-1.1: Manufacturer: Prusa Research (prusa3d.com)
Jul 14 16:26:35 RepetierServer kernel: [97078.768181] usb 1-1.1: SerialNumber: 4914-27145608112154302
Jul 14 16:26:35 RepetierServer kernel: [97078.779126] cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device
Jul 14 16:26:35 RepetierServer mtp-probe: checking bus 1, device 15: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
Jul 14 16:26:35 RepetierServer mtp-probe: bus: 1, device: 15 was not an MTP device
Jul 14 16:26:35 RepetierServer mtp-probe: checking bus 1, device 15: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
Jul 14 16:26:35 RepetierServer mtp-probe: bus: 1, device: 15 was not an MTP device
Jul 14 16:26:55 RepetierServer dbus-daemon[367]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.3217' (uid=0 pid=9810 comm="timedatectl ")
Jul 14 16:26:56 RepetierServer systemd[1]: Starting Time & Date Service...
Jul 14 16:26:56 RepetierServer dbus-daemon[367]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jul 14 16:26:56 RepetierServer systemd[1]: Started Time & Date Service.
Jul 14 16:27:26 RepetierServer systemd[1]: systemd-timedated.service: Succeeded.
Jul 14 16:27:57 RepetierServer dbus-daemon[367]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.3219' (uid=0 pid=9907 comm="timedatectl ")
Jul 14 16:27:57 RepetierServer systemd[1]: Starting Time & Date Service...
Jul 14 16:27:57 RepetierServer dbus-daemon[367]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jul 14 16:27:57 RepetierServer systemd[1]: Started Time & Date Service.
Jul 14 16:28:27 RepetierServer systemd[1]: systemd-timedated.service: Succeeded.
Jul 14 16:28:45 RepetierServer rngd[473]: stats: bits received from HRNG source: 880064
Jul 14 16:28:45 RepetierServer rngd[473]: stats: bits sent to kernel pool: 809728
Jul 14 16:28:45 RepetierServer rngd[473]: stats: entropy added to kernel pool: 809728
Jul 14 16:28:45 RepetierServer rngd[473]: stats: FIPS 140-2 successes: 43
Jul 14 16:28:45 RepetierServer rngd[473]: stats: FIPS 140-2 failures: 1
Jul 14 16:28:45 RepetierServer rngd[473]: stats: FIPS 140-2(2001-10-10) Monobit: 0
Jul 14 16:28:45 RepetierServer rngd[473]: stats: FIPS 140-2(2001-10-10) Poker: 0
Jul 14 16:28:45 RepetierServer rngd[473]: stats: FIPS 140-2(2001-10-10) Runs: 1
Jul 14 16:28:45 RepetierServer rngd[473]: stats: FIPS 140-2(2001-10-10) Long run: 0
Jul 14 16:28:45 RepetierServer rngd[473]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
Jul 14 16:28:45 RepetierServer rngd[473]: stats: HRNG source speed: (min=236.341; avg=575.682; max=669.153)Kibits/s
Jul 14 16:28:45 RepetierServer rngd[473]: stats: FIPS tests speed: (min=23.548; avg=41.649; max=76.294)Mibits/s
Jul 14 16:28:45 RepetierServer rngd[473]: stats: Lowest ready-buffers level: 2
Jul 14 16:28:45 RepetierServer rngd[473]: stats: Entropy starvations: 0
Jul 14 16:28:45 RepetierServer rngd[473]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
Jul 14 16:28:58 RepetierServer dbus-daemon[367]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.3221' (uid=0 pid=10047 comm="timedatectl ")
Jul 14 16:28:58 RepetierServer systemd[1]: Starting Time & Date Service...
Jul 14 16:28:58 RepetierServer dbus-daemon[367]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jul 14 16:28:58 RepetierServer systemd[1]: Started Time & Date Service.
Jul 14 16:29:28 RepetierServer systemd[1]: systemd-timedated.service: Succeeded.
Jul 14 16:29:59 RepetierServer dbus-daemon[367]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.3223' (uid=0 pid=10142 comm="timedatectl ")
Jul 14 16:29:59 RepetierServer systemd[1]: Starting Time & Date Service...
Jul 14 16:30:00 RepetierServer dbus-daemon[367]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jul 14 16:30:00 RepetierServer systemd[1]: Started Time & Date Service.
Jul 14 16:30:30 RepetierServer systemd[1]: systemd-timedated.service: Succeeded.
Jul 14 16:31:01 RepetierServer dbus-daemon[367]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.3225' (uid=0 pid=10231 comm="timedatectl ")
Jul 14 16:31:01 RepetierServer systemd[1]: Starting Time & Date Service...
Jul 14 16:31:01 RepetierServer dbus-daemon[367]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jul 14 16:31:01 RepetierServer systemd[1]: Started Time & Date Service.
Jul 14 16:31:31 RepetierServer systemd[1]: systemd-timedated.service: Succeeded.
Jul 14 16:32:02 RepetierServer dbus-daemon[367]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.3227' (uid=0 pid=10321 comm="timedatectl ")

Martin81

Egal was da aktuell nun schief läuft nicht funktioniert oder ähnliches. Wann kann man denn damit rechnen, dass es ein Update von Repetier Server gibt, was den MK4 fehlerfrei untersützt? Ich verdiene mein Geld mit einer Druckerfarm und daher ist es interessant ob ich auf die Farm Lösung von Prusa setzt oder bei Repetier bleibe. Fehlt Euch noch ein Drucker zum testen oder was ist genau das Problem? Wie kann ich helfen? Ich komme aus Köln.

Repetier

Problem ist hier das die USB Verbindung getrennt wird. Check mal in den Server Verbundungseinstellungen ob "USB neu verbinden bei Timeout" aktiviert ist. Das ist der einzig mögliche Grund warum der server usb trennen würde. Stelle auch sicher das Ping-Pong an ist, falls er das gleiche Problem wie der Mini hat.

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.