-
TeamFDM.com is an UNOFFICIAL companion site for the DIY Voron 3D printer community. For official docs and final source of truth, visit the Official Voron Discord or the Voron Github
- 0
TeamFDM.com is an UNOFFICIAL companion site for the DIY Voron 3D printer community. For official docs and final source of truth, visit the Official Voron Discord or the Voron Github
Question
Anacardium
Hi!
My V0.2 is running fine. Printing is all good and now even better using the new improved Mini Stealthburner with Orbiter 2.0.
But: When ever I´m watching the camera feed of my Raspberry 2 cam, ping times increase and the video starts to freeze. Finally, the printer is not reachable any more.
Ping without watching camera stream:
64 bytes from 192.168.1.213: icmp_seq=10467 ttl=64 time=10.129 ms
64 bytes from 192.168.1.213: icmp_seq=10468 ttl=64 time=8.277 ms
64 bytes from 192.168.1.213: icmp_seq=10469 ttl=64 time=5.803 ms
64 bytes from 192.168.1.213: icmp_seq=10470 ttl=64 time=5.959 ms
64 bytes from 192.168.1.213: icmp_seq=10471 ttl=64 time=5.664 ms
64 bytes from 192.168.1.213: icmp_seq=10472 ttl=64 time=6.238 ms
64 bytes from 192.168.1.213: icmp_seq=10473 ttl=64 time=6.852 ms
64 bytes from 192.168.1.213: icmp_seq=10474 ttl=64 time=7.528 ms
64 bytes from 192.168.1.213: icmp_seq=10475 ttl=64 time=5.724 ms
Ping when watching the stream:
64 bytes from 192.168.1.213: icmp_seq=10566 ttl=64 time=35.601 ms
64 bytes from 192.168.1.213: icmp_seq=10567 ttl=64 time=110.564 ms
64 bytes from 192.168.1.213: icmp_seq=10568 ttl=64 time=25.575 ms
64 bytes from 192.168.1.213: icmp_seq=10569 ttl=64 time=304.525 ms
64 bytes from 192.168.1.213: icmp_seq=10570 ttl=64 time=730.814 ms
64 bytes from 192.168.1.213: icmp_seq=10571 ttl=64 time=375.876 ms
64 bytes from 192.168.1.213: icmp_seq=10572 ttl=64 time=409.942 ms
64 bytes from 192.168.1.213: icmp_seq=10573 ttl=64 time=529.365 ms
64 bytes from 192.168.1.213: icmp_seq=10574 ttl=64 time=427.653 ms
64 bytes from 192.168.1.213: icmp_seq=10575 ttl=64 time=1114.534 ms
Often it results in loosing the connection.
I already implemented a script as cron job which is checking ping time and resetting the connection if time goes over 50ms. But that´s only a bad work around, no real solution, of course.
My crownsnest config looks like:
----------------------------
----------------------------
Behavior is not as bad when using 640x480 and lower fps like 15. It takes longer to show the issue, but it is still there.
I´m running out of ideas.
Any suggestion what I could check or change is highly appreciated.
Link to comment
Share on other sites
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.