thu4n / ESP32-WiFi-Sensing

A WiFi Sensing project using the ESP32 CSI tool
6 stars 2 forks source link

COLLECTING DATA #21

Open Akai19 opened 2 weeks ago

Akai19 commented 2 weeks ago

I have problems in collecting the data

  1. Im using window and I use the command 'idf.py monitor | findstr "CSI_DATA" > my-experiment-file.csv' but there is no output so Itried
  2. idf.py monitor | tee >trial13.csv now the saved collected csi data is in one column

trial13.csv

thu4n commented 2 weeks ago

Hi, your issue is quite similar to https://github.com/StevenMHernandez/ESP32-CSI-Tool/issues/111 . Assuming you use the toolkit without any modification, I can't really help since I couldn't reproduce it on my side. I suggest you go the link and state your similar problem there.

Akai19 commented 2 weeks ago

yes we are in the same group. if ever, I think the problem is how the collected data is saved in my laptop, will there be a problem in collecting data if I directly collect it in esp32? I kinda have no idea, if ever the problem is in my laptop then we can just manually delimited and put it into machine learning or???

thu4n commented 2 weeks ago

There won't be a problem with directly collecting CSI data in the esp32, you only need to make sure it has enough storage space and a way to get the data later. Delimiting the data manually is fine too, just make sure the CSI data column isn't changed by the process.

Akai19 commented 2 weeks ago

An update:

The only problem is that the findstr doesn't work in Esp-IDF Powershell so we switch to CMD.

Mohammed-Baqir commented 4 days ago

ISSUE1_SAVEDATA any one got this kind of errors ?

PS E:\esp-v4.3\esp-idf\esp32-csi-tool\active_ap> idf.py -p \.\COM3 monitor | findstr "CSI_DATA" > my-experiment-file.c sv --- idf_monitor on \.\COM3 921600 --- --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H --- 0x400813f8: call_start_cpu1 at E:/esp-v4.3/esp-idf/components/esp_system/port/cpu_start.c:141