-
Notifications
You must be signed in to change notification settings - Fork 29
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
Parsing Nexmon .pcap files #36
Comments
|
Thank you for the prompt response. To follow up,
My concern with RSSI value is that 192 does not seem a reasonable value. But when I used CSIKit library to parse the same file, I get RSSI value -64 for the first packet. I noticed that 192-256=-64. Is there an issue for parsing the RSSI bytes? Thanks again! |
-64 is right, I'll fix it. You can also use |
|
Thank you for this amazing work! I have a question about parsing CSI and RSSI data using
csiread
. If I know that the CSI data was collected using RPi 4B using this precompiled binary of Nexmon, is there a way to tell if I should usecsiread.Nexmon
orcsiread.NexmonPull46
? Alternatively, given a .pcap file, how can I decide if we should usecsiread.Nexmon
orcsiread.NexmonPull46
? I would like to get RSSI in addition to CSI and the only way to get it throughcsiread.NexmonPull46
Also, there is no
csiread.NexmonPull46.read()
function. So, I created a similar one likecsiread.Nexmon.read()
, which basically callssuper().read()
.Here is the sample code that I am using:
Here is the output:
Looking at value 192, does it look like it is reading the correct RSSI?
Thank you!
The text was updated successfully, but these errors were encountered: