Touchstar Boston 8500 Handheld Scanner Disconnecting

[Anonymous]

Hi all,

We have quite 40 Touchstar Boston 8500 (http://www.touchstar.co.uk/product_mo...) Hand Held Barcode scanners that connect via ZoneFlex 7352 controlled by a Smart Standby Zondirector 1100 to our network.

We have just started testing and what we have found is that the hand held units seem to "disconnect" from the network at random intervals (5-60 minutes) all sleep and power setting are either off or on max. The hand held still has an IP address but the device can no longer access the LAN or can be pinged from any machine within our network. To reconnect we need to put the device in standby mode and then switch it back on, this effectively restarts the network card.

The WLAN card that the handheld has is a Summit, I have found a setting that I thing may be responsible for the drop off's as it may interfere with what the ZoneDirector is trying to do: http://www.summitdata.com/Documents/G...

Agressive Scan is a feature in Summit WLAN cards that actively looks for better Ap's and try's to connect to them, from my understanding the ZoneDirector will transfer the device between Ap's? Would this be culprit?

Any help appreciated.

Thanks,
Julius

[Anonymous]

Please copy and paste from the RF info of a few APs all lines under the below 2 subjects

------------ PHY Error Stats ------------

and

------------ Airtime Stats ------------

[Anonymous]

WASP005
------------ PHY Error Stats ------------
6896450 PHY errors since clearing all stats (rx_phyerr)
1 phy cck restart
5577245 phy ofdm group
1319204 phy cck group
0 PHY errors since clearing delta stats (1 sec)
Histogram of PHY errors per second (pcttime in each range)
0 1-500 ..1K ..2K ..5K ..10K ..20K ..50K .100K more
20 76 3 1 0 0 0 0 0 0

------------ Airtime Stats ------------
Airtime utilized (percent) since clearing delta stats (1 sec)
Busy: 0 RX: 11 TX: 3 Total: 14
Histograms of airtime (pcttime in each range) since clearing all stats
0 0-10 ..20 ..30 ..40 ..50 ..60 ..70 ..80 ..90 ..100
busy: 92 7 0 0 0 0 0 0 0 0 0
rx: 0 94 5 0 0 0 0 0 0 0 0
tx: 5 95 0 0 0 0 0 0 0 0 0
tot: 0 89 9 1 0 0 0 0 0 0 0

WASP009
------------ PHY Error Stats ------------
8089188 PHY errors since clearing all stats (rx_phyerr)
5445398 phy ofdm group
2643790 phy cck group
0 PHY errors since clearing delta stats (1 sec)
Histogram of PHY errors per second (pcttime in each range)
0 1-500 ..1K ..2K ..5K ..10K ..20K ..50K .100K more
15 81 2 2 1 0 0 0 0 0

------------ Airtime Stats ------------
Airtime utilized (percent) since clearing delta stats (1 sec)
Busy: 0 RX: 8 TX: 1 Total: 9
Histograms of airtime (pcttime in each range) since clearing all stats
0 0-10 ..20 ..30 ..40 ..50 ..60 ..70 ..80 ..90 ..100
busy: 91 8 1 0 0 0 0 0 0 0 0
rx: 0 90 9 1 0 0 0 0 0 0 0
tx: 5 94 1 0 0 0 0 0 0 0 0
tot: 0 78 17 3 1 0 0 0 0 0 0

WASP012
------------ PHY Error Stats ------------
83606678 PHY errors since clearing all stats (rx_phyerr)
6 phy cck restart
60633540 phy ofdm group
22973132 phy cck group
6 PHY errors since clearing delta stats (1 sec)
6 phy cck restart
Histogram of PHY errors per second (pcttime in each range)
0 1-500 ..1K ..2K ..5K ..10K ..20K ..50K .100K more
16 80 1 1 1 0 0 0 0 0

------------ Airtime Stats ------------
Airtime utilized (percent) since clearing delta stats (1 sec)
Busy: 0 RX: 7 TX: 2 Total: 9
Histograms of airtime (pcttime in each range) since clearing all stats
0 0-10 ..20 ..30 ..40 ..50 ..60 ..70 ..80 ..90 ..100
busy: 94 5 0 0 0 0 0 0 0 0 0
rx: 0 85 13 2 0 0 0 0 0 0 0
tx: 7 93 0 0 0 0 0 0 0 0 0
tot: 0 75 21 3 1 0 0 0 0 0 0

[Anonymous]

Well. It' probably not interference. It looks pretty clean.

Is tunneling helping?

[Anonymous]

Unfortunately not really, we are going to upgrade to 9.6 now. Thanks for looking at our logs.

[Anonymous]

Run an AP-ZD SpeedTest for every AP. Is there any packet loss?