Other Parts Discussed in Thread: AWR1642, IWR1642
Greetings,
Upon working with the AWR1642 radar and trying to develop an algorithm with the information given in the documentation many difficulties have risen. In the following lines I’ll expose questions that would be of great help if answered:
1) How are the data structures effectively organized?
This question comes because after analyzing the document “mmw Demo Data Structure v0.1” we’ve seen the data structures defined for the first version of the SDK. Afterwards, we verified that although the structures are similar for the version 2_00_1 there are differences in the sizes of the structures and even in the structures utilized. As an example, we can see that in the index.html present on the SDK path for the version 2_00_1, that specifies the data structures used, there is a field called SubFrameNumber that wasn’t in the first version. What we would like to know is how the data is exactly structured for the newer versions to make it possible to develop algorithms based on these positions.
Being more objective, we would like to know the exact positions and length of the parameters given by the incoming frames.
2) How can we get meaning of the values taken from the fields?
This doubt appeared because, even if we acquire the data on each field and we know what the field is about, we don’t know the true meaning of the value we get. What I mean by this is, for example, when getting the x coordinate of a detected object, to which referential is the coordinate we are receiving related to?
3) Is the Matlab code for the demo visualizer available?
When developing the algorithm for our purposes, the configurations we are sending to the board are specified in the demo visualizer app and, as so, it would be very helpful if we could analyze the code to assert how the fields are organized and the information is processed
As a disclaimer, we students developing a project for educational projects. This question was important because the lack of documentation as proven to be a real difficulty for the development of our project.
Thank you!
