Monitoring, Management & Location Tracking

Client timers in VisualRF 6.3

Prior to 6.2 all floor plans had a unique timer that was derived from VisaulRF > Setup :: Location Caching Timer. If this timer was configured to 5 minutes, each client on the floor plan had its location recalculated every five minutes regardless of samples received or device type.

In 6.2 each client has a minimum timer, sample trigger, and maximum timer based on device type and detailed in the table below. This ensures that VisualRF locates highly mobile devices more frequently based on new signal samples, and more sedentary devices less frequently. This new methodology increases the overall capacity of VisualRF while also increasing location accuracy for WiFi Tags and WiFi phones. 

Device Type Min 
Timer 
(secs) Max
Timer 
(secs) Sample
Trigger
Laptop 90 300 3
Phone 60 240 3
WiFi Tag 30 180 4
Rogue 900 3,600 3
Scale 900 3,600 3
Printer 900 2,700 3


The VisualRF -> Setup page has undergone some minor changes related to the new client location calculation methodology.

The Location Caching Timer setting has been renamed to Synchronization Timer and moved into Server Settings Section. This setting now controls how often the VisualRF engine polls AMP for state changes to access points.

The Allowed Deviation for Client Placement setting has moved into the Location Settings section.













To edit the timers create a rf.properties file in /usr/local/airwave/lib/java with the overrides.

Sample:
rf.floor.signal.tolerance=4

rf.device.schedule.default.min=900
rf.device.schedule.default.max=2700
rf.device.schedule.default.samples=4

rf.device.schedule.olap.min=30
rf.device.schedule.olap.max=300
rf.device.schedule.olap.samples=3

rf.device.schedule.nlap.min=30
rf.device.schedule.nlap.max=300
rf.device.schedule.nlap.samples=3

rf.device.schedule.phone.min=15
rf.device.schedule.phone.max=240
rf.device.schedule.phone.samples=1

rf.device.schedule.rfid.min=15
rf.device.schedule.rfid.max=180
rf.device.schedule.rfid.samples=1

rf.device.schedule.scale.min=900
rf.device.schedule.scale.max=3600
rf.device.schedule.scale.samples=4

rf.device.schedule.rogue.min=900
rf.device.schedule.rogue.max=2700
rf.device.schedule.rogue.samples=4

Version History
Revision #:
1 of 1
Last update:
‎06-09-2014 09:47 AM
Updated by:
 
Labels (1)
Contributors
Tags (1)
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.