-
Notifications
You must be signed in to change notification settings - Fork 111
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
csi_data-read_parse error (AEGHB-722) #186
Comments
Thank you for reporting this issue. It seems like the CSI data is corrupted when transferring on the serial. To help us investigate:
Please provide a dump of your serial output if possible. Any additional details on how to reproduce the error would be helpful. |
1.I am using the ESP32 S3 development board |
You should monitor the receiver - that's where the csi_data_read_parse.py script grabs the CSI data from. I've added some print statements to show the packet content when it spots a corrupted packet. With those print statements you can check corrupted packets directly through console. Check out the updated csi_data_read_parse.py here: https://gist.github.com/suhipek/4f65fc797844b24ded20c8be0ab45162 BTW, have you changed any parameters in the sender, receiver, or parser programs? |
This is a strange phenomenon. If you look at the log you gave, there are many pieces of data that are broken. |
1.I cloned the esp-csi code again, but this error still occurs |
``
if len(csi_data) != len(DATA_COLUMNS_NAMES):
print("element number is not equal")
continue
try:
csi_raw_data = json.loads(csi_data[-1])
except json.JSONDecodeError:
print(f"data is incomplete")
continue
if len(csi_raw_data) != 128 and len(csi_raw_data) != 256 and len(csi_raw_data) != 384:
print(f"element number is not equal: {len(csi_raw_data)}")
continue
``
What is the reason for these errors when I use csi_data-read_parse for data collection?
The text was updated successfully, but these errors were encountered: