New user - Pi Cam performance problems
Hello, I just started using Repetier SW for my 3D Printer (Sparkcube xl) a few days ago ... wonderful, all is is working great beside the performance of the Pi Cam stream:
The stream in the server window is very slow and seconds behind the reality ... but if I open an additional browser tap to view the stream directly it shows real time.
(Repetier shows the historie, the other tab shows the reality).
Any idea to optimize the performance in the repetier software?
Gruß Michael
Comments
For installation I used your detailed (well working!) instaruction on https://www.repetier-server.com/setting-webcam-repetier-server-linux/. No change of parameters.
Furthermore I tried the following:
- PC with WLAN connection, means Repetier Server connected via WLAN
- PI (here runs the Repetier Server and the PI CAM) connected via WLAN and additional ethernet cable connection => fluent stream
- PI connected via WLAN but without additional ethernet cable connection => delayed stream, but direct acces to stream is fluent
... hope that helps bringing some light in the problem.
Why all this effort: in the area were the 3d printer is located I have no ethernet cable connection, only WLAN
$ ping repetierserver.local
PING repetierserver.local (192.168.1.85): 56 data bytes
64 bytes from 192.168.1.85: icmp_seq=0 ttl=64 time=42.444 ms
64 bytes from 192.168.1.85: icmp_seq=1 ttl=64 time=12.707 ms
64 bytes from 192.168.1.85: icmp_seq=2 ttl=64 time=36.561 ms
64 bytes from 192.168.1.85: icmp_seq=3 ttl=64 time=12.779 ms
64 bytes from 192.168.1.85: icmp_seq=4 ttl=64 time=56.585 ms
64 bytes from 192.168.1.85: icmp_seq=5 ttl=64 time=5.579 ms
64 bytes from 192.168.1.85: icmp_seq=6 ttl=64 time=81.436 ms
64 bytes from 192.168.1.85: icmp_seq=7 ttl=64 time=3.577 ms
64 bytes from 192.168.1.85: icmp_seq=8 ttl=64 time=154.149 ms
64 bytes from 192.168.1.85: icmp_seq=9 ttl=64 time=35.681 ms
64 bytes from 192.168.1.85: icmp_seq=10 ttl=64 time=30.800 ms
64 bytes from 192.168.1.85: icmp_seq=11 ttl=64 time=34.932 ms
64 bytes from 192.168.1.85: icmp_seq=12 ttl=64 time=7.139 ms
64 bytes from 192.168.1.85: icmp_seq=13 ttl=64 time=12.971 ms
64 bytes from 192.168.1.85: icmp_seq=14 ttl=64 time=9.600 ms
64 bytes from 192.168.1.85: icmp_seq=15 ttl=64 time=46.083 ms
64 bytes from 192.168.1.85: icmp_seq=16 ttl=64 time=27.163 ms
64 bytes from 192.168.1.85: icmp_seq=17 ttl=64 time=4.185 ms
64 bytes from 192.168.1.85: icmp_seq=18 ttl=64 time=38.124 ms
64 bytes from 192.168.1.85: icmp_seq=19 ttl=64 time=4.663 ms
64 bytes from 192.168.1.85: icmp_seq=20 ttl=64 time=19.808 ms
64 bytes from 192.168.1.85: icmp_seq=21 ttl=64 time=3.914 ms
64 bytes from 192.168.1.85: icmp_seq=22 ttl=64 time=19.588 ms
^C
--- repetierserver.local ping statistics ---
23 packets transmitted, 23 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 3.577/30.455/154.149/32.750 ms
Btw. when next release coming? I am waiting for gcode sharing between printers
So the problem is inside the web interface not well developed, not in the streaming.