I have an Octopi that connects through WiFi.
Frequently, it seems to drop off the network. The only thing that seems to cause it to reconnect... is to continuously ping it... even when the pings fail.
I do a continuous ping, and for several minutes.... I will get errors stating that it can't be reached.
But after a few minutes of pink, eventually I get ping responses.
If I let the pings continue, it almost seems to keep the connection "alive" for lack of a better term.
I wont see failed pings.
According to my Ubiquiti Unifi dashboard... the connection quality should be excellent.
Its almost as if Octopi has some sort of setting that causes the the Raspberry Pi to enter some sort of low-power idle mode that only comes "alive" if many many multiple attempts to communicate with it come through.
Any solutions to this issue?
If I run a print, the Octopi will actually become inaccessible... presumably unless I run a continuous ping in the background.
Frequently, it seems to drop off the network. The only thing that seems to cause it to reconnect... is to continuously ping it... even when the pings fail.
I do a continuous ping, and for several minutes.... I will get errors stating that it can't be reached.
But after a few minutes of pink, eventually I get ping responses.
If I let the pings continue, it almost seems to keep the connection "alive" for lack of a better term.
I wont see failed pings.
According to my Ubiquiti Unifi dashboard... the connection quality should be excellent.
Its almost as if Octopi has some sort of setting that causes the the Raspberry Pi to enter some sort of low-power idle mode that only comes "alive" if many many multiple attempts to communicate with it come through.
Any solutions to this issue?
If I run a print, the Octopi will actually become inaccessible... presumably unless I run a continuous ping in the background.
Statistics: Posted by JFox762 — Mon Mar 25, 2024 5:29 pm — Replies 0 — Views 13