-
Notifications
You must be signed in to change notification settings - Fork 71
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
Test with Windows Computer #18
Comments
I am working on Windows10 with this tool. Here are my observations till now
All in all, for the bare minimum task of obtaining/viewing the CSI output, no additional steps needed (existing documentations from you are enuf), whereas for logging the values using PuTTY will do the job. |
Thank you for sharing. Did you use the commands like Here are some other comments I have for you (which are unrelated to this issue):
|
I didnt use Actually i am personally concerned with only storing/saving CSI values which can be easily done with putty, and to filter/operate on them later using python, thats why i didn't try realtime filtering. |
ESP-IDF adds "winpty" command before of "python" for windows at this line. "idf_monitor.py" is run by a command like "winpty python" so that the error "stdout is not a tty" is throwed. To overcome this, the parameter for winpty "-Xallow-non-tty" could be used like that "winpty -Xallow-non-tty python" at that line. Because of this parameter, when I try to filter csi data by grep, I think the logs is broken. The new lines are broken. For example, I want to obtain this "CSI_DATA,STA,XX:XX:XX:XX:XX:XX,-56,11,1,6,1,1,1,1,0,0,0,-93,1,8,1,16715674,0,110,0,0,16.937968,384,[110 96 6 0 0 0 0 0 0 0 0 0 12 -8 12 -7 13 -7 13 -7 13 -6 13 -6 13 -6 13 -5 13 -5 13 -4 14 -4 13 -4 13 -3 13 -3 12 -3 13 -3 12 -3 12 -3 12 -4 12 -4 12 -3 11 -4 12 -4 11 -3 12 -3 11 -4 0 0 11 -4 11 -4 11 -4 10 -5 10 -5 10 -5 10 -5 9 -6 10 -6 10 -6 10 -6 10 -6 10 -6 9 -7 10 -7 10 -7 9 -7 9 -8 9 -8 9 -9 9 -8 9 -9 9 -9 9 -9 9 -9 9 -9 0 0 0 0 0 0 0 0 0 0 ],1625492304.85" , but I could just obtain just that "CSI_DATA,STAXX:XX:XX:XX:XX:XX,-56,11,1,6,1,1,1,1,0,0,0,-93,1,8,1,16719468,0,110,0,0,16.943324,384,[110 9". I don't know why but I think it is related with this. I also have thought removing the adding "winpty" for windows. I try the "python" code directly on msys32, and I see it works. So I remove the "winpty" command from that that. I see that it works clearly. For using grep command line, I take a error "Binary file (standard input) matches". I overcome with "-a" parameter. "make monitor | grep -a "CSI_DATA" > my-experiment-file.csv". It works clearly. For python script command, it works without any error. Those are my results. But I am not sure about the accuracy of my results. So I can't talk absolute. |
The windows equivalent to grep is findstr. I am able to store the CSI data in windows using the following command: |
This is a very late response, but I wonder if anyone has ideas of how to handle using Any suggestions for updating the documentation through a pull-request are greatly appreciated! |
It's a late and easy answer In a windows environment, you can use
same event
|
Thank you for taking a look at this @Loki-moon. I have updated the README docs to mention The consensus appears to be that |
We need to make sure that the project works well with Windows machines. However, I do not have access to a Windows computer to test.
It would be a huge help to this project if anyone in the community can confirm the following:
readme.md
?Here are some issues that seem to be Windows related
Thanks!
The text was updated successfully, but these errors were encountered: