-
Notifications
You must be signed in to change notification settings - Fork 205
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
AWR1243 read results in socket timeout #47
Comments
Update So I wrote the following file (a la a suggestion from a different issue on this repo), which runs mmWaveStudio and reads adc_data as it repeatedly triggers captures; this results in a timeout however:
On the other hand, when I tried executing my original python script but with the timeout set to 10, and then triggering the capture on mmWaveStudio, it was successful, but only the first time. If I tried it again, it would give this error:
Looking over the adc code, it seems like the length the packet gives is longer than its actual length. I can only fix this problem by closing out mmWaveStudio and reopening it. But then the problem still occurs after the first successful trigger. |
Have u solved this issue yet? I'm currently facing the same one. |
I set up adc.py parameters to match my mmWaveStudio configuration as follows:
and I used the following code to read the data:
Firstly, dca.organize gives a list dimension error unless I multiply the number of samples by 2 as shown above. Why does it need to be multiplied?
Secondly, when I trigger a capture in the SensorConfig tab of mmWaveStudio (it triggers a read of 8 frames of data and then stops) and run the python, I get a timeout error. However, using a continuous stream (in the ContStream tab), I can successfully read data. Does openradar require a continuous read or is there a way to get it to detect or trigger a single capture with mmWaveStudio and the AWR1243?
The text was updated successfully, but these errors were encountered: