Location Deployment - MERAKI AP-EKAHAU-StanleyScout

[sudaryanto]

is there someone have experience of applying Location deployment for tracking assets in factory with MERAKI AP - Ekahau and StanleyScout Tags here. need to know how it work in real

[PhilipDAth · Accepted solution]

I don't know the answer, but here are some deployment guidelines.
https://documentation.meraki.com/MR/Monitoring_and_Reporting/Location_Deployment_Guidelines 

[alemabrahao]

There is a good article to read:

https://developer.cisco.com/meraki/build/rtls/

[rhbirkelund]

A wireless design is somewhat different when desigining for RTLS. Usually you'd design your wireless network such that you meet a certain SNR or coverage criteria.

When desigining RTLS, your goal is to be able to trangulate a devices position based on RSSI. SO your client needs to always be able to hear 3 or more APs at a time. When placing APs it helps if you remember to think about triangles.

Usually, you'd create a perimeter along the building inner contour, and within that contour you'd place APs evenly distributed, while still thinking about triangles, if this make sense.

I don't eactly remember how it is with AeroscoutStanley, nor how it interfaces with Meraki, but usually you'll have to be running a Location Engine from Stanley which collects all the location data, and more or less converts RSSI to an X,Y coordinate.

A lot has happened since it was called Aeroscout, so some of the integrations may have changed, but basically it's the same principles. Instead of designing for Wireless Coverage where you place APs where wireless is needed, you disperse APs evenly, across the area, and along the building perimeter, and make sure you have at least 20% channel overlap.