@Michael Daracz
Hi Michael, from your description it seems like the client is not roaming as quickly as it should. Some assumptions:
1. The scanner are set to operate on one band only, 2.4 or 5 GHz not auto
2. If using 2.4 the scanners are NOT 802.11b only
3. Your deployment has a good overlap (so an signal of no less than -65 dBm everywhere)
Base on those assumption and what you have indicated try the following:
1. Set the wlan to tunnel mode (this is recommended for handheld and phone)
2. Set the BSS min rate to something higher than the default so the scanner will get "out of range" while still able to communicate quite well and when looking for a new AP it should still get a good enough signal on the new AP and connect right away.
With a -65 dBm coverage it's safe to start with a BSS min rate of 12 Mbps. This wil make the AP send out management frames, such as beacon and probe response be sent out at 12 Mbps so the client can not get too far before it get out of range of a 12 Mbps radius of the current AP. Here are the command to set the BSS min rate for the wlan:
ruckus> enable
ruckus# config
ruckus(config)# wlan motoscanner
The WLAN service 'motoscanner' has been created. To save the WLAN service, type 'end' or 'exit'.
ruckus(config-wlan)# bss-minrate 12
The mgmt-tx-rate will be set to the same value as bss-minrate.
The command was executed successfully. To save the changes, type 'end' or 'exit'.
ruckus(config-wlan)# end
The WLAN service 'motoscanner' has been updated and saved.
Your changes have been saved.
ruckus(config)# end
Your changes have been saved.
ruckus#