The data sheet states that the capability exists (see 802.11mc Fine Timing Measurement (FTM) for precisiondistance ranging on p.4) but it does not appear to be enabled by default. How is this feature enabled?
as per instructions i received, you need to enable it as below.
But you have to manually calculate coordinates as we discussed in the CLI commands for setting static Location information in AP post. There is also Explanation by Jens how you can play around with it. Selflocating is not yet posible as per Jens Fluegel and it will be enabled in next Aruba Central. I don't know if they will also it possible for Instant cluster without central.
Calculation of location can be done like it is explained here: https://www.ietf.org/archive/id/draft-thomson-geopriv-3825bis-03.html
I will now try to enable it on the second AP as it obviously needs to be done separately on each AP right now, not just the master in IAP cluster. Result will be posted in the topic i mentioned
IAP615_LCI_chamb# configure t<o:p></o:p>
IAP615_LCI_chamb (config) # wlan ssid-profile 615_IAP<o:p></o:p>
IAP615_LCI_chamb (SSID Profile "615_IAP") # ftm-responder-enable<o:p></o:p>
IAP615_LCI_chamb (SSID Profile "615_IAP") # advertise-location<o:p></o:p>
IAP615_LCI_chamb (SSID Profile "615_IAP") # end<o:p></o:p>
IAP615_LCI_chamb# commit apply <o:p></o:p>
© Copyright 2023 Hewlett Packard Enterprise Development LPAll Rights Reserved.