-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does anyone know about the range or coverage of Wi-Fi wireless transmission? #338
Comments
Chapter 3.5 "802.11n and 802.11ac propagation model" of [1] might be a good starting point. [1] Eldad Perahia and Robert Stacey. 2013. Next Generation Wireless LANs: 802.11n and 802.11ac (2nd. ed.). Cambridge University Press, USA. |
@jlinktu Oh, thanks for replying. |
Don't know about it. But you could add debug flags " |
@jlinktu Hi, this is my dmesg output. I don't see any crashes, just went into promiscuous mode and didn't come out. device = raspberry pi 4B [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 |
Unfortunately, this doesn't help in identifying the issues. You can try to make sure not being in sleep mode with: When such a hang-up occurs again, please run the following and post the output:
|
@jlinktu Just like you said Note: I don't think it's a "sleep" issue. Instead of a script that sets this extraction cycle, I've had csi continuously extracted and observed it. This time, I was getting about 9300 packets, but stopped along the way. My sampling rates are 25Hz, and it's a beacon frame, not an artificial ICMP ping. Is the beacon signal an issue? pi@raspberrypi:~ $ sudo su |
Nothing in there that indicated a crash or misbehavior of the firmware. Maybe interference with a different program that tries to access the wifi chip, such as Can you rule out that your transmitter is misbehaving? |
@jlinktu Could you please check this out? This is the result of running Saved file number zz : 43 of 100 |
Seems not to be related to your problem. |
Hello @jlinktu I think I might have found something regarding this phenomenon. When extracting data at 80MHz, I can receive CSI continuously without interruptions, but when I set it to 20MHz or 40MHz, it stops partway through. I have insisted on using 20MHz because I thought that 256 subcarriers were too many. Could there be a software bug when extracting CSI at 20MHz or 40MHz? |
I don't think so. There is no obvious place where different bandwidths behave that differently. |
Hi, I'm a nexmon csi extractor user. I want to use csi to estimate whether each room is occupied in two adjacent rooms. If Tx is in the middle and there are people in Room 2 receiving csi from Rx1 and Rx2, the csi variation will be detected severely. On the contrary, however, if there are people in Room 1, there is some variation in Rx2, but it is not found very much. Why is that? Do you have any literature on the range form of radio waves? Is it not appropriate to put Tx between Rxs in a straight line? I would appreciate it if you could share your knowledge on the coverage of radio waves.
Note: Room1 is a private room and Room2 is a common area (ex. kitchen)
The text was updated successfully, but these errors were encountered: