Can you try to apply the patch Johannes created for the iw tool and use it to try to use it instead of debugfs? Just to check whether it's a problem in the debugfs entries...

https://p.sipsolutions.net/bef149ad0c1b8c8f.txt

This patch needs to be completed by copying the driver’s “include/uapi/linux/nl80211.h” file over the “nl80211.h” file in iw, before it will even compile.  This is not part of the patch itself because it depends on which driver version you are using.  So please copy it from the Core30 release you took.

Thanks a lot, 

Any hints about where I should copy this file to? What is the directory of iw?

Also, how I use this patch?


Thanks,
Mohamed

Hello Luca,

I have download the latest version of iw:
https://git.kernel.org/pub/scm/linux/kernel/git/jberg/iw.git
Copied the nl80211.h file from the Core30 to the iw folder then built successfully

And patched the file you mentioned using:
patch -p1 < bef149ad0c1b8c8f.txt


Then I created config file with this entry:
bb:bb:bb:bb:bb:bb bw=20 cf=2412

And there is no error, got this result:
phy #1: FTM result! Status: 0
Target: 00:c2:c6:f2:76:eb, status: 4, rtt: 0 psec, distance: 0 cm


On the AP side, I get this message from hostapd:
IEEE 802.11: Failed to send Action frame

I checked the status, and it means 'Time event was scheduled but not called yet'

What that means? Do I need to do special configuration on the AP.


Thanks,
Mohamed

Created attachment 258801 [details]
patch adding tof to iw

For the record, I'm adding the patch here as an attachment.

What are you running on the AP side?

I am using Core30 (31 firmware) also on the AP side. I run hostapd (2.6 version) with this configuration:
driver=nl80211
interface=wlan0
hw_mode=g
channel=13
wmm_enabled=1
ssid=tof_test
ftm_responder=1
ftm_initiator=1

Also, tried to configure it as responder through debugfs, but also no response from AP.

While on the STA side, using the following configuration for iw:
bb:bb:bb:bb:bb:bb bw=20 cf=2472

Hello Luca,

I am still not able to get response from AP. The request is being sent successfully from the STA, and the AP receives it, but it doesn't reply.

Is there any missing configuration for the AP to configure it as a responder?
I have already showed to you, in my previous comments, the hostapd configuration.

I tried also to configure the responder through debugfs using tof_responder_params (with the AP BSSID, channel number and bandwidth) and tof_responder_config, after this step, I don't see this error: "EEE 802.11: Failed to send Action frame
", while running hostapd. However, still no response from the AP to the STA/requester. 


Thanks,
Mohamed

Thanks for the details.  I'll ask the FTM expert in our team and come back to you.

Thanks, I am waiting for your reply.

Hello, 

Have you asked the FTM expert?
Any hints to solve this problem?

It works for 8260 cards, however the error is ranging from 1.5 meter to 6 meters (while varying the distance between the two nodes from 1 meter to 14 meters) for line-of-sight measurements.

For the 8265 cards, they produce FW error. I get the FW error at the requester, if I used the 8265 as requester. On the other hand, if I used it as responder and used 8260 as requester, I get the FW error at the responder, when it receives the request.

Hello Luca,

I have something weird here. I have been using two NUC nodes with builtin 8260 cards. The ranging system was working reliably on these nodes, but I needed to test with external antennas. So, I purchased new 8260 cards with external antennas and adaptors to convert from M.2 to MPCIe.

I have installed the same version for Linux kernel, IWLWIFI backport, firmware, hostapd and iw. However, I am really getting different readings.
I am getting negative readings. For example, starting from -5 meters at almost zero actual distance, -4 meters at 1 meter actual distance, and it goes up when increase the distance.

As I mentioned everything is the same, same software and same cards, the only difference that I can see is the adapter. Please let me know what is the problem here?

I am afraid I'll disappoint here but after having contacted the FTM folks it appears that:

1) 8265 doesn't support FTM, only 8260 does.
2) we can't provide real product level support for FTM on 8260 since it requires special calibrations which aren't run on standard devices.


The bottom line is that we can return results on 8260, we can't commit on their accuracy.

I'll update our wiki page in order not to mislead users.

Sorry for the inconvenience.

Hi, Grumbach

How did you get the result of 1.5m, 6m with 8260 card?
I would like to know the settings and steps even if the measurement result has big error.

my setting is,
AP side: hostapd2.6, set conf file(ftm_responder=1,ftm_initiator=1), set tof_responder_params (channel_num, bssid,..)
STA side: iw with patch discusssed here

my step is,
just "iw dev wlp2s0 measurement ftm_request xxx.conf"

my result is,
phy #0: FTM result! Status: 0
Target: 44:85:00:32:70:8f, status: 4, rtt: 0 psec, distance: 0 cm


Best regards,


(In reply to mibrahim.ahmed from comment #12)
> It works for 8260 cards, however the error is ranging from 1.5 meter to 6
> meters (while varying the distance between the two nodes from 1 meter to 14
> meters) for line-of-sight measurements.
> 
> For the 8265 cards, they produce FW error. I get the FW error at the
> requester, if I used the 8265 as requester. On the other hand, if I used it
> as responder and used 8260 as requester, I get the FW error at the
> responder, when it receives the request.

Hi ahmed,

sorry for my mistake.
this is for your question.


(In reply to bdaddr.macaddr from comment #15)
> Hi, Grumbach
> 
> How did you get the result of 1.5m, 6m with 8260 card?
> I would like to know the settings and steps even if the measurement result
> has big error.
> 
> my setting is,
> AP side: hostapd2.6, set conf file(ftm_responder=1,ftm_initiator=1), set
> tof_responder_params (channel_num, bssid,..)
> STA side: iw with patch discusssed here
> 
> my step is,
> just "iw dev wlp2s0 measurement ftm_request xxx.conf"
> 
> my result is,
> phy #0: FTM result! Status: 0
> Target: 44:85:00:32:70:8f, status: 4, rtt: 0 psec, distance: 0 cm
> 
> 
> Best regards,
> 
> 
> (In reply to mibrahim.ahmed from comment #12)
> > It works for 8260 cards, however the error is ranging from 1.5 meter to 6
> > meters (while varying the distance between the two nodes from 1 meter to 14
> > meters) for line-of-sight measurements.
> > 
> > For the 8265 cards, they produce FW error. I get the FW error at the
> > requester, if I used the 8265 as requester. On the other hand, if I used it
> > as responder and used 8260 as requester, I get the FW error at the
> > responder, when it receives the request.