BCD536HP: BCD536 dropping wifi connection

sacscorpio

Newbie
Premium Subscriber
Joined
Mar 1, 2008
Messages
20
Location
Northern California
I have a brand new BCD536HP and the wifi adapter is literally 4" from my wireless router. I set up it's own 2.4Ghz network so it's the only one on that network, and still I'm getting crap connection.

I have reset the BCD536HP and verified that it is current on firmware AND the database, not that it should make a difference for the DB, but I'm just lost. Any suggestions would be appreciated. Below is my ping from the computer connected to the BCD536HP with ProScan.


Microsoft Windows [Version 10.0.19041.388]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ping 10.0.0.149

Pinging 10.0.0.149 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.0.0.149:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\WINDOWS\system32>ping 10.0.0.149 -t

Pinging 10.0.0.149 with 32 bytes of data:
Reply from 10.0.0.149: bytes=32 time=903ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=895ms TTL=128
Reply from 10.0.0.149: bytes=32 time=789ms TTL=128
Reply from 10.0.0.149: bytes=32 time=454ms TTL=128
Reply from 10.0.0.149: bytes=32 time=167ms TTL=128
Reply from 10.0.0.149: bytes=32 time=384ms TTL=128
Reply from 10.0.0.149: bytes=32 time=639ms TTL=128
Reply from 10.0.0.149: bytes=32 time=347ms TTL=128
Reply from 10.0.0.149: bytes=32 time=511ms TTL=128
Reply from 10.0.0.149: bytes=32 time=418ms TTL=128
Reply from 10.0.0.149: bytes=32 time=94ms TTL=128
Reply from 10.0.0.149: bytes=32 time=428ms TTL=128
Reply from 10.0.0.149: bytes=32 time=34ms TTL=128
Reply from 10.0.0.149: bytes=32 time=85ms TTL=128
Reply from 10.0.0.149: bytes=32 time=144ms TTL=128
Reply from 10.0.0.149: bytes=32 time=304ms TTL=128
Reply from 10.0.0.149: bytes=32 time=490ms TTL=128
Reply from 10.0.0.149: bytes=32 time=50ms TTL=128
Reply from 10.0.0.149: bytes=32 time=402ms TTL=128
Reply from 10.0.0.149: bytes=32 time=374ms TTL=128
Reply from 10.0.0.149: bytes=32 time=322ms TTL=128
Reply from 10.0.0.149: bytes=32 time=260ms TTL=128
Reply from 10.0.0.149: bytes=32 time=185ms TTL=128
Reply from 10.0.0.149: bytes=32 time=342ms TTL=128
Reply from 10.0.0.149: bytes=32 time=112ms TTL=128
Reply from 10.0.0.149: bytes=32 time=543ms TTL=128
Reply from 10.0.0.149: bytes=32 time=105ms TTL=128
Reply from 10.0.0.149: bytes=32 time=87ms TTL=128
Reply from 10.0.0.149: bytes=32 time=96ms TTL=128
Reply from 10.0.0.149: bytes=32 time=207ms TTL=128
Reply from 10.0.0.149: bytes=32 time=184ms TTL=128
Reply from 10.0.0.149: bytes=32 time=236ms TTL=128
Reply from 10.0.0.149: bytes=32 time=93ms TTL=128
Reply from 10.0.0.149: bytes=32 time=171ms TTL=128
Reply from 10.0.0.149: bytes=32 time=179ms TTL=128
Reply from 10.0.0.149: bytes=32 time=93ms TTL=128
Reply from 10.0.0.149: bytes=32 time=504ms TTL=128
Reply from 10.0.0.149: bytes=32 time=154ms TTL=128
Reply from 10.0.0.149: bytes=32 time=459ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=782ms TTL=128
Reply from 10.0.0.149: bytes=32 time=715ms TTL=128
Reply from 10.0.0.149: bytes=32 time=255ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1000ms TTL=128
Reply from 10.0.0.149: bytes=32 time=965ms TTL=128
Reply from 10.0.0.149: bytes=32 time=345ms TTL=128
Reply from 10.0.0.149: bytes=32 time=530ms TTL=128
Reply from 10.0.0.149: bytes=32 time=146ms TTL=128
Reply from 10.0.0.149: bytes=32 time=71ms TTL=128
Reply from 10.0.0.149: bytes=32 time=902ms TTL=128
Reply from 10.0.0.149: bytes=32 time=300ms TTL=128
Reply from 10.0.0.149: bytes=32 time=288ms TTL=128
Reply from 10.0.0.149: bytes=32 time=479ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1739ms TTL=128
Reply from 10.0.0.149: bytes=32 time=640ms TTL=128
Reply from 10.0.0.149: bytes=32 time=246ms TTL=128
Reply from 10.0.0.149: bytes=32 time=233ms TTL=128
Reply from 10.0.0.149: bytes=32 time=10ms TTL=128
Reply from 10.0.0.149: bytes=32 time=62ms TTL=128
Reply from 10.0.0.149: bytes=32 time=259ms TTL=128
Reply from 10.0.0.149: bytes=32 time=194ms TTL=128
Reply from 10.0.0.149: bytes=32 time=509ms TTL=128
Reply from 10.0.0.149: bytes=32 time=25ms TTL=128
Reply from 10.0.0.149: bytes=32 time=30ms TTL=128
Reply from 10.0.0.149: bytes=32 time=48ms TTL=128
Reply from 10.0.0.149: bytes=32 time=316ms TTL=128
Reply from 10.0.0.149: bytes=32 time=428ms TTL=128
Reply from 10.0.0.149: bytes=32 time=260ms TTL=128
Reply from 10.0.0.149: bytes=32 time=355ms TTL=128
Reply from 10.0.0.149: bytes=32 time=49ms TTL=128
Reply from 10.0.0.149: bytes=32 time=118ms TTL=128
Reply from 10.0.0.149: bytes=32 time=371ms TTL=128
Reply from 10.0.0.149: bytes=32 time=224ms TTL=128
Reply from 10.0.0.149: bytes=32 time=289ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=425ms TTL=128
Reply from 10.0.0.149: bytes=32 time=153ms TTL=128
Reply from 10.0.0.149: bytes=32 time=405ms TTL=128
Reply from 10.0.0.149: bytes=32 time=879ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1167ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=2517ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1097ms TTL=128
Reply from 10.0.0.149: bytes=32 time=612ms TTL=128
Reply from 10.0.0.149: bytes=32 time=631ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1077ms TTL=128
Reply from 10.0.0.149: bytes=32 time=139ms TTL=128
Reply from 10.0.0.149: bytes=32 time=882ms TTL=128
Reply from 10.0.0.149: bytes=32 time=916ms TTL=128
Reply from 10.0.0.149: bytes=32 time=2180ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1382ms TTL=128
Reply from 10.0.0.149: bytes=32 time=513ms TTL=128
Reply from 10.0.0.149: bytes=32 time=2009ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=1993ms TTL=128
Reply from 10.0.0.149: bytes=32 time=924ms TTL=128
Reply from 10.0.0.149: bytes=32 time=736ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1438ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=770ms TTL=128
Reply from 10.0.0.149: bytes=32 time=397ms TTL=128
Reply from 10.0.0.149: bytes=32 time=2633ms TTL=128
Reply from 10.0.0.149: bytes=32 time=919ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=1641ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=1902ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1234ms TTL=128
Reply from 10.0.0.149: bytes=32 time=568ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1057ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=79ms TTL=128
Reply from 10.0.0.149: bytes=32 time=28ms TTL=128
Reply from 10.0.0.149: bytes=32 time=38ms TTL=128
Reply from 10.0.0.149: bytes=32 time=764ms TTL=128
Reply from 10.0.0.149: bytes=32 time=662ms TTL=128
Reply from 10.0.0.149: bytes=32 time=990ms TTL=128
Reply from 10.0.0.149: bytes=32 time=281ms TTL=128
Reply from 10.0.0.149: bytes=32 time=89ms TTL=128
Reply from 10.0.0.149: bytes=32 time=404ms TTL=128
Reply from 10.0.0.149: bytes=32 time=269ms TTL=128
Reply from 10.0.0.149: bytes=32 time=92ms TTL=128
Reply from 10.0.0.149: bytes=32 time=25ms TTL=128
Reply from 10.0.0.149: bytes=32 time=520ms TTL=128
Reply from 10.0.0.149: bytes=32 time=248ms TTL=128
Reply from 10.0.0.149: bytes=32 time=96ms TTL=128
Reply from 10.0.0.149: bytes=32 time=213ms TTL=128
Reply from 10.0.0.149: bytes=32 time=11ms TTL=128
Reply from 10.0.0.149: bytes=32 time=17ms TTL=128
Reply from 10.0.0.149: bytes=32 time=272ms TTL=128
Reply from 10.0.0.149: bytes=32 time=131ms TTL=128
Reply from 10.0.0.149: bytes=32 time=79ms TTL=128
Reply from 10.0.0.149: bytes=32 time=285ms TTL=128
Reply from 10.0.0.149: bytes=32 time=238ms TTL=128
Reply from 10.0.0.149: bytes=32 time=161ms TTL=128
Reply from 10.0.0.149: bytes=32 time=642ms TTL=128
Reply from 10.0.0.149: bytes=32 time=883ms TTL=128
Reply from 10.0.0.149: bytes=32 time=280ms TTL=128
Reply from 10.0.0.149: bytes=32 time=60ms TTL=128
Reply from 10.0.0.149: bytes=32 time=63ms TTL=128
Reply from 10.0.0.149: bytes=32 time=178ms TTL=128
Reply from 10.0.0.149: bytes=32 time=13ms TTL=128
Reply from 10.0.0.149: bytes=32 time=11ms TTL=128
Reply from 10.0.0.149: bytes=32 time=8ms TTL=128
Reply from 10.0.0.149: bytes=32 time=73ms TTL=128
Reply from 10.0.0.149: bytes=32 time=190ms TTL=128
Reply from 10.0.0.149: bytes=32 time=37ms TTL=128
Reply from 10.0.0.149: bytes=32 time=63ms TTL=128
Reply from 10.0.0.149: bytes=32 time=263ms TTL=128
Reply from 10.0.0.149: bytes=32 time=66ms TTL=128
Reply from 10.0.0.149: bytes=32 time=76ms TTL=128
Reply from 10.0.0.149: bytes=32 time=111ms TTL=128
Reply from 10.0.0.149: bytes=32 time=222ms TTL=128
Reply from 10.0.0.149: bytes=32 time=104ms TTL=128
Reply from 10.0.0.149: bytes=32 time=114ms TTL=128
Reply from 10.0.0.149: bytes=32 time=58ms TTL=128
Reply from 10.0.0.149: bytes=32 time=55ms TTL=128
Reply from 10.0.0.149: bytes=32 time=40ms TTL=128
Reply from 10.0.0.149: bytes=32 time=49ms TTL=128
Reply from 10.0.0.149: bytes=32 time=59ms TTL=128
Reply from 10.0.0.149: bytes=32 time=17ms TTL=128
Reply from 10.0.0.149: bytes=32 time=281ms TTL=128
Reply from 10.0.0.149: bytes=32 time=112ms TTL=128
Reply from 10.0.0.149: bytes=32 time=19ms TTL=128
Reply from 10.0.0.149: bytes=32 time=543ms TTL=128
Reply from 10.0.0.149: bytes=32 time=143ms TTL=128
Reply from 10.0.0.149: bytes=32 time=51ms TTL=128
Reply from 10.0.0.149: bytes=32 time=35ms TTL=128
Reply from 10.0.0.149: bytes=32 time=174ms TTL=128
Reply from 10.0.0.149: bytes=32 time=57ms TTL=128
Reply from 10.0.0.149: bytes=32 time=374ms TTL=128
Reply from 10.0.0.149: bytes=32 time=76ms TTL=128
Reply from 10.0.0.149: bytes=32 time=419ms TTL=128
Reply from 10.0.0.149: bytes=32 time=68ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1027ms TTL=128
Reply from 10.0.0.149: bytes=32 time=432ms TTL=128
Reply from 10.0.0.149: bytes=32 time=9ms TTL=128
Reply from 10.0.0.149: bytes=32 time=526ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1645ms TTL=128
Request timed out.
Request timed out.
Reply from 10.0.0.149: bytes=32 time=1102ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1212ms TTL=128
Reply from 10.0.0.149: bytes=32 time=948ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1759ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1166ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1417ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1019ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=1717ms TTL=128
Reply from 10.0.0.149: bytes=32 time=2244ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1249ms TTL=128
Reply from 10.0.0.149: bytes=32 time=614ms TTL=128
Reply from 10.0.0.149: bytes=32 time=965ms TTL=128
Reply from 10.0.0.149: bytes=32 time=2479ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=1544ms TTL=128
Reply from 10.0.0.149: bytes=32 time=637ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1659ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1025ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1821ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=2476ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1841ms TTL=128
Reply from 10.0.0.149: bytes=32 time=917ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1650ms TTL=128
Reply from 10.0.0.149: bytes=32 time=792ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1246ms TTL=128
Reply from 10.0.0.149: bytes=32 time=652ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=1428ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1208ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1431ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=1224ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1092ms TTL=128
Reply from 10.0.0.149: bytes=32 time=639ms TTL=128
Reply from 10.0.0.149: bytes=32 time=266ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=481ms TTL=128
Reply from 10.0.0.149: bytes=32 time=73ms TTL=128
Reply from 10.0.0.149: bytes=32 time=837ms TTL=128
Reply from 10.0.0.149: bytes=32 time=148ms TTL=128
Reply from 10.0.0.149: bytes=32 time=344ms TTL=128
Reply from 10.0.0.149: bytes=32 time=8ms TTL=128
Reply from 10.0.0.149: bytes=32 time=60ms TTL=128
Reply from 10.0.0.149: bytes=32 time=3ms TTL=128
Reply from 10.0.0.149: bytes=32 time=498ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=806ms TTL=128
Reply from 10.0.0.149: bytes=32 time=3227ms TTL=128
Reply from 10.0.0.149: bytes=32 time=3372ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=2300ms TTL=128
Reply from 10.0.0.149: bytes=32 time=1042ms TTL=128
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.0.149: bytes=32 time=3301ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=1596ms TTL=128
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.0.149: bytes=32 time=732ms TTL=128
Reply from 10.0.0.149: bytes=32 time=2586ms TTL=128
Reply from 10.0.0.149: bytes=32 time=3479ms TTL=128
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.0.149: bytes=32 time=3846ms TTL=128
Reply from 10.0.0.149: bytes=32 time=534ms TTL=128
Request timed out.
Request timed out.
Reply from 10.0.0.149: bytes=32 time=2556ms TTL=128
Reply from 10.0.0.149: bytes=32 time=2967ms TTL=128
Request timed out.
Reply from 10.0.0.149: bytes=32 time=3350ms TTL=128
Reply from 10.0.0.110: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.0.149: bytes=32 time=2535ms TTL=128
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 

hexagon_keyhole

Member
Premium Subscriber
Joined
Jul 7, 2020
Messages
74
Location
Sacramento, California
Even though you just got the scanner, have you checked to be sure the firmware in both the scanner AND the dongle are up to date?

.
Ditto. Also, when was the last time your router got a firmware upgrade, too?

I had some connectivity issues with a wireless device which I have since replaced, and in my case it turns out I had to turn off WiFi AX to get my device working. I have a newer WiFi router that broadcasts one network that’s both 2.4ghz and 5ghz; instead of two separate WiFi networks which caused some confusion and frustration.
 

ofd8001

Member
Premium Subscriber
Joined
Feb 6, 2004
Messages
6,873
Location
Louisville, KY
I would also try setting up the scanner in Access Point mode and use your smart phone to connect to the scanner. That gets the router out of the picture. If you do not experience issues with this setup, it suggests a router issue.
 

Ubbe

Member
Joined
Sep 8, 2006
Messages
4,928
Location
Stockholm, Sweden
WiFi channels are 3 channels wide, so if you are using ch3 and another WiFi system nearby are using ch4 they will not be aware of each other and will interfere hevealy with each other creating bad bandwidth and errors. If you have a seperate network name for your WiFi doesn't have anything to do with it, it is only the channel numbers that matter.

You have to use an app, or sometimes the routher have a scanning program, to first find out what channels are in use in your area. The nearest and strongest system to you must be on the same channel as you, or have to be 6 channels off from your frequency.

Normally you only use ch1-6-11 due to the overlapping of one channels frequency bandwidt into other channels. There are 52 timeslots with 1mb each on each channel so it should be lots of capacity left for many wifi systems to share one channel, and they will dynamicly assign the number of timeslots to handle the different peeks in bandwidt for each system.

/Ubbe
 

buddrousa

Member
Premium Subscriber
Joined
Jan 5, 2003
Messages
7,858
Location
NW Tenn
Also you do not need the scanner wifi and the router 4 inches apart.
I am running PROSCAN 16 times on the same PC 6 536's and 1 SDS200 wifi no problems.
 

belvdr

Member
Premium Subscriber
Joined
Aug 2, 2013
Messages
817
WiFi channels are 3 channels wide, so if you are using ch3 and another WiFi system nearby are using ch4 they will not be aware of each other and will interfere hevealy with each other creating bad bandwidth and errors. If you have a seperate network name for your WiFi doesn't have anything to do with it, it is only the channel numbers that matter.
The bandwidth also matters. Higher bandwidth means higher chance of interference. With 2.4, I'd go with 40 MHz first, and drop to 20 MHz if you have issues with that.

The lower the bandwidth means lower throughput, but possibly a more stable signal. Without a site survey, it's down to trial and error, which is fine for most consumer uses.
Also you do not need the scanner wifi and the router 4 inches apart.
I am running PROSCAN 16 times on the same PC 6 536's and 1 SDS200 wifi no problems.
Good point. Having them too close together can also cause issues. It's better to have them a few feet apart than a few inches.
 

Ubbe

Member
Joined
Sep 8, 2006
Messages
4,928
Location
Stockholm, Sweden
The bandwidth also matters. Higher bandwidth means higher chance of interference. With 2.4, I'd go with 40 MHz first, and drop to 20 MHz if you have issues with that.
The 536's WiFi are a 20Mhz only device, so the router will automaticly fall back to a 20MHz mode for all connections to be able to support the 536. If a router runs in 40MHz mode it will interfere even more and take up half of the available channels in the 2,4GHz band. It would be unfortunate if a close by neighbour are running in 40MHz mode. Hopefully he instead choose to run at 5GHz to gain more bandwidt and keeps out from the 2,4GHz band.

/Ubbe
 

belvdr

Member
Premium Subscriber
Joined
Aug 2, 2013
Messages
817
The 536's WiFi are a 20Mhz only device, so the router will automaticly fall back to a 20MHz mode for all connections to be able to support the 536. If a router runs in 40MHz mode it will interfere even more and take up half of the available channels in the 2,4GHz band. It would be unfortunate if a close by neighbour are running in 40MHz mode. Hopefully he instead choose to run at 5GHz to gain more bandwidt and keeps out from the 2,4GHz band.

/Ubbe
I run 40MHz on 2.4 and 5GHz to keep throughput up, but I don't have close neighbors. Going to 5GHz is the best option, as you said. It really stinks the 536 WiFi adapter is only 20MHz.
 
Last edited:

sacscorpio

Newbie
Premium Subscriber
Joined
Mar 1, 2008
Messages
20
Location
Northern California
It's ok, I'm going to sell the BCD996P2 and the BCD536HP that are basically brand new. I got my delivery of two more SDS200s today. :)
 
Top