IWR1843BOOST: Errors and frame issues occurred during using Play Back mode of Traffic Monitoring demo

Hello,

Can you please confirm:

1.  Gui  and Bin file belong to the same version of the donloaded Toolbox.

2. In the normal (run) mode Gui + binary works as expected

3. Error is seen only during playback.

Please provide the snapshot of error again as it seems to be illegible.

Thank you,

Vaibhav

Thanks for your reply.

1. Yes. Both files belong to the same version of the downloaded Toolbox.

2, 3. Yes. In order to find out the reason of these errors and frame issues I made multiple experiments with the same configurations/settings/GUI and etc. and every time when I am observing the results while process is going (run mode) it works normal - as expected, but in Playback mode it sometimes (not in every attempt) gives these frame issues and stops the whole process.

Therefore, I'd like to know if you can list or describe the possible reasons of facing these problems (errors related to some tracking parameters, skipped commands, and frame issues) so for the next attempts I will consider them during making measurements.

Errors:

Error: number of parameters is incorrect for stateParam commandError: number of parameters is incorrect for trackingCfg commandSkip parsing for: sensorPosition command
Skip parsing for: presenceBoundaryBox command
Skip parsing for: sensorStart command
Issue with Frame 1428. Skipping. Expected packet length: 928; Actual length: 191.
Issue with Frame 3780. Skipping. Expected packet length: 576; Actual length: 351.
Issue with Frame 5176. Skipping. Expected packet length: 736; Actual length: 479.

Hello

Thank you for confirming that Normal demo run works as in #2.

For replay (#3)  can you please confirm :

3.a  Error occurs and then it stops  replay

 Considering there are 3 errors in snapshot - did the replay not stop for  first two occurrences and then stopped on t3rd occurrence?

3.b What is the repeatability of the error:

3.b.a:  For a given saved file error occurs consistently at the same Frame # 

Potentially Issue: error in data file  Or Replay parser has errors

3.b.b:  For a given saved file error occurs different frame #

May be related to runtime stability and would need detailed debug.

Good part is that we provide the source code of the gui and explain the details of data format as given in Work with GUI source code

For additional debug please follow the steps below:

1. Try the matlab source code run for replay mode

2. Single step to identify  the data structs of the failing frame and check if integrity matches the expected data format

Hope this allows you to check the debug the issue.

Thank you,

Vaibhav

Yes. Replay stops when it reaches to 1428th frame (1427 is the last available/visible frame).

It happens in every attempt. I have tried to replay this data file many times, but always can see only first 1427 frames.

Thanks, I will check the source code for fixing it.

1. I have tried it as well, but nothing has changed.

2. Single step to identify  the data structs of the failing frame and check if integrity matches the expected data format - Can you please give an explanation on this? From where and how to find this particular frame? 

Hello

Thank you for checking the consistency of failure.   DOes the frame #1427 fail on all saved files  or just his one.

Is it possible that data file for same reason has an error.?

Would it be possible to recollect data and try the newly collected data file?

For Matlab source code debug, please see the Matlab tool help

https://www.google.com/search?client=firefox-b-1-d&q=matlab+code+single+step

Failures should help you identify the code,line#.

Thank you,

Vaibhav

For this particular data file it is the1427th frame which stops the playback process every time.

The main issue is that, I get this problem again in my new measurements. For each measurement the number of frame which stops the process is different. While taking measurements I can see radar data on GUI (during all measurement period - from beginning till end even after XXXth frame) but in Command Window of Matlab I get an error of "Issue with Frame XXX. Skipping.". So, after finishing the measurement, I can only see the radar data of XXX frames in Playback mode.

Thanks, I will check Matlab source code debug too.

It would be really helpful you can list possible reasons for this error, so for the next time I will consider it before setting up measurement environment. For example, I think possible reasons that lead to this problem can be usage of BIN and GUI files which are not belong to same version of toolbox and shaking the device during the measurement. Is there something else must be considered?

Okay.

Can you also give an explanation about another issue described in my question?

Error: number of parameters is incorrect for stateParam commandError: number of parameters is incorrect for trackingCfg commandSkip parsing for: sensorPosition command
Skip parsing for: presenceBoundaryBox command
Skip parsing for: sensorStart command

I'd like to know the reason why these errors appear in every measurement when I run the MATLAB code.

Hello

Do you see the error on the matlab  even on the live uart stream?

Thank you,

Vaibhav

Hi,

Yes.