• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 272 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

IWR6843AOPEVM: packet length/parsing error while trying to replicate 3D People Counting Demo

Sebastien Chorney
Prodigy 20 points
Part Number: IWR6843AOPEVM
Other Parts Discussed in Thread: IWR6843AOP

Hi

We are trying to configure and test IWR6843AOP and see the board's performance in the 3D people counting demo.

The board configuration is selected from \ti\mmwave_industrial_toolbox_4_12_1\labs\People_Counting\3D_People_Counting\chirp_configs\AOP_6m_default

The prebuilt binary files are selected from:
C:\ti\mmwave_industrial_toolbox_4_12_1\labs\People_Counting\3D_People_Counting\prebuilt_binaries\3D_people_count_68xx_demo

The visualizer is from radar_toolbox_1_20_00_11\tools\visualizers\Industrial_Visualizer\mmWave_Industrial Visualize.exe

(please note the visualizer is selected from radar_toolbox_1_20_00_11 and not mmwave_industrial_toolbox_4_12_1)

When the device is connected, an error or warning raises:

"Warning: Frame packet length read is not equal to totalPacketLen in frame header. Subsequent frames may be dropped.
Parsing Error on frame: 187
Error Number: 3"

or sometimes this error is raised:
"Frame packet length read is not equal to totalPacketLen in frame header. Subsequent frames may be dropped.
Parsing Error on frame: 95"

Any thoughts on the cause(s) of this error or warning?

  • +1
    TI__Mastermind 34650 points

    Hi,

    If these errors don't stop execution, then I would not worry about them too much. Data streams off our device very fast and sometimes it is difficult for the computer to keep up. Try closing other tabs and putting the computer on high performance mode if the problems persist.

    Additionally, it is best to match visualizer version and software version (If you use RTB 1.20 for your visualizer, use the code in RTB 1.20 for the radar device too).

    Best,

    Nate