Repetier Server Print Farm
I am having a difficult time finding a suitable connection setup with my current configuration. I love using the Repetier server software, it was super easy for me to set up and run when I had 4 printers. I have grown to 8 with plans to move on to more. I am having issues with connecting them all via USB to the server, it's a linux desktop machine, single core AMD64 bit processor. Currently using a powered USB Strip, however when I plug in the 5th printer the connection cycles on and off restarting the printer every 2-5 sec's. I have attempted to connect a octopi instance on a printer and connect to the Repetier server instance through the octopi via TCP/IP without success. When I attempt to set up the printer in RS, when I get to the connection method box and select TCP/IP connection, input the IP address it just spins with no connection being made....I tried port 80, 5000, 3344 and 23 with no luck. I see the Repetier host is available however it is not built for raspberry pi, so I haven't tried anything with that option. Is the best course to run multiple instances(I have 4 licenses left) with the Repetier Server multiple linux/windows computers and connect in groups of 4 or 5 via usb, or is there a way to leverage the TCP/IP connection using on ly one RS computer? I guess what I am asking is what is the preferred method from the companies viewpoint on how to handle this method of operations? Thank you for the assistance.
Comments
Running multiple printer on one machine is in general no problem and we have no real limit. But hardware might get problems with power. Quite some printers draw current from usb port and that can give problems. Linux will also disable usb ports if power goes down which might explain the on/off case. Try connecting printers without 5V see bottom of:
https://www.repetier-server.com/knowledgebase/undervoltage-and-throtteling-of-pi/
Then they get power from their main power.
Not sure what octopi has to do with our software. For pi we have own images that run server. We can not simply connect to octoprint. Over tcp/ip we can connect to printers that offer a tcp port similar to serial that just wants the communication data. These printers often also have a web interface on port 80 or 8080 whcih is the wrong port. We need more a telnet port. For reprapfirmware this for example exists but must be activated explicitly.
In theory the powered usb is a help if it has enough power. Regular usb 2 must allow 500mA so a 8 port active usb must deliver 4A. But then pi might also get some power from it (also as I understand that should not happen most hubs behave like that) or it might just have 2A extra power not expecting all devices to draw 500mA or even more (some do draw in deed more). So that is where theory and practice can differ causing problems.
I did purchase a usb power stripe with a 4A plug but, I am not sure what the max is at the USB plug individually. I did manage to install RepetierHost onto the Rpi and and connect to the printer just fine, but now for some reason when I use the connection from RepetierHost it connects the the RepetierServer, however when I attempt to set the Printer up in RepetierServer I can not get past the area where you plug in the IP address and port number of the printer.....It just says 'awaiting connection'. and doesn't connect....I did use the API key of the RS on the RH. Still working that....I am hesitant to just use RS on each Printer like many have suggested...I know I get 5 uses per license, but if I can set up 5 servers I can have 25 machines....however if buying a license for each machine needs to happen to get a stable print farm then so be it....just wanted to try several ways first before I buy.
> however when I attempt to set the Printer up in RepetierServer I can not get past the area where you plug in the IP address and port number of the printer
Why do you connect with usb when it is a printer with TCP/IP interface? When you connect with usb you use the serial connection in server configuration! Then you can use the pi ip to connect your browser but there is no direct ip for the printer directly. Maybe some misunderstanding here?