Do you have a WIFI network with AP roaming enabled?
This caused a bunch of problems with my RasPI based systems and I had to
turn it off.
StevenEllis's Profile: http://forums.slimdevices.com/member.php?userid=69979
View
Mellon wrote:
> It may be worth remembering that packet loss is not ALWAYS a result of a
> network malfunction.
>
> For example, if the device you are pinging is already working hard
> trying to do something else, that could be a reason for it to drop the
> ping request, rather than the ping
pascal! wrote:
> Hi,
> I have RPI ZERO W - with piCore
> piCorePlayer v7.0.0 | www v00011 | linux 5.4.83-pcpCore | piCore
> v12.0pCP | Squeezelite v1.9.9-1386-pCP
> And the WiFi goes down regurlarly and it is ok after the reboot for some
> minutes.
> My WiFi is quite good and I have another RPI
[WiFi Settings] > [Diagnostics] gives all (most) of the answers.
Code:
Wifi:on
SSID:GE2
Password:xx
Passphrase:
Security:WPA-PSK
Country:
Hidden SSID: 0
MAC address: 00:0f:13:28:20:85
Uptime: 0 days
...or neighbours on the same (or close) WiFi channel, of course.
Can you use something like InSSIDer (on Windows) to check the WiFi
channels in use in your vicinity: their strength and channel numbers?
Martin
mooblie's
Paul Webster wrote:
> Maybe if you move it even further away it will work even better!
Maybe! The quality and level did drop though.
Code:
Pos QualityLevel
1. 100 -11dBm
2. 75-57dBm
I think the problems start
Aren't the clever PCB-based antennae on Pis _orientation_sensitive_?
I got better WiFi reception with a Pi (Pi3 actually) VERTICAL, rather
than horizontal.
Martin
mooblie's Profile:
Maybe if you move it even further away it will work even better!
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc),
planetradio (bauer - kiss, absolute, scala, jazzfm etc), kcrw, supla
finland, abc australia, cbc/radio-canada and rte
Moved 7 meters away thru 1 interior wall.
Code:
PING 192.168.1.52 (192.168.1.52): 56 data bytes
64 bytes from 192.168.1.52: seq=0 ttl=64 time=6.003 ms
64 bytes from 192.168.1.52: seq=1 ttl=64 time=5.625 ms
64 bytes from 192.168.1.52: seq=2 ttl=64 time=7.219 ms
There is a [Diagnostics] button on the [Wifi Settings] page.
The diagnostics log is then available under [Main Page] > [Diagnostics]
> [Logs].
Here is part of the log from my Raspberry Pi ZeroW (located 100mm from
wifi router).
Code:
PING 192.168.1.52 (192.168.1.52):
Try swapping the two ZeroW locations to see if the problem is with the
specific ZeroW or with the location.
John
On 9/5/21 8:37 AM, pascal! wrote:
Hi,
I have RPI ZERO W - with piCore
piCorePlayer v7.0.0 | www v00011 | linux 5.4.83-pcpCore | piCore
v12.0pCP | Squeezelite v1.9.9-1386-pCP
And
11 matches
Mail list logo