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.

IWR6843ISK: Questions about mmwave sensors performance

Part Number: IWR6843ISK
Other Parts Discussed in Thread: IWR6843

Hello !

I've performed some tests with my IWR6843 and some elements surprised me and I'd like to know what could cause those phenomena.

  1. The pointcloud "moves" a lot. I mean, it seems that, even with static object, the detection of the object is unreliable. Sometimes, some points will appear where there is no object or the pointcloud of a static object change a lot. Is this a characteristic of radar sensor, or is this issue coming from computing/algorithms.
  2. In my use case, I must detect the occupancy of specific areas. But quite often the radar does not detect the objects, here is an illustration of one of my tests (reality vs pointcloud):   
    What can be the reasons of these non detected objects ?
  3. Does the difference between the real area covered and the theoric FOV is due to the radiation curve of antennas or due to the low-level configuration (here is my configuration: 2D-profile40m.cfg)

Thanks in advance for your help,

Have a great day !

Quentin

  • Hi, Quentin:

    The tradeoff of miss detection and false detection can be tradeoff with different CFAR detection threshold.

    Are you using range FFT + Doppler FFT + CFAR detection + DOA algorithm in your post processing chain?

    With the CFAR detection,  a peak will be claimed if it is higher than the neighboring range bins.  But when the neighboring range bin are all quite strong, it may not declare as a peak.   In your case, traditional CFAR may not work very well.  

    In addition in your system, it seems that both sensor and target are static, the radar system can not take advantage of the separation of doppler domain,  you may want to go through the range-angle domain for detection instead of range-doppler domain for detection.  You can refer to people counting demo for this range-angle domain detection.   

    From your configuration, you have an angle of resolution of 15 degree.  You may want to consider using cascade radar system if you need to detect a lot of details that are close by.

    Best,

    Zigang

    Best,

    Zigang

  • Hi !

    Ok, I'll try more CFAR thresholds during my next tests.

    Yes I use all those algorithms.

    Ok I understand ! And are other algorithms used in some project ? Or do you know one algorithm that could solve this issue ?

    Thanks, I started with LRPC project recently but I don't undertstand very well how tracking are plotted from Target List and Target Index TLV. Could you explain me shortly please ?

    Yes it could be a solution thanks ! Is there currently any cascade radar system as an EVM ?

    Thanks for your help !

  • Hi Quentin,

    LRPC demo actually uses range-doppler detection.  The demo that uses range-azimuth detection is the "People Counting 68xx demo" - lab15.

    You can see the TLV format in the people counting user's guide.  It is identical between the different People Counting demos. 

    Unfortunately, cascade EVMs are not yet available. 

    Regards,

    Justin

  • Hi !

    Ok thank you, I didn't know ! So, if I switch to "People Counting 68xx demo" - lab15, I'll probably get better results than with LRPC, am I right ?

    Is Area Scanner using range azimuth or range-doppler detection, or where can I check which type of detection is used in a lab please ? (because I performed my tests with AS lab)

    I read the User guide but didn't get well what Target Index was used for.

    Thanks for those information !

    Regards,

    Quentin

  • Hi Quentin,

    It depends on the range you need to detect at. Lab0015 will perform much better under 20 meters.

    Area Scanner uses OOB demo, which is a range-doppler chain.

    Target index relates points to targets.

    Regards,

    Justin

  • In my use case, 30 m would be perfect but a better detection until 20m is already great !

    Will I be able to use low-level config for longer range with Lab15 project ?(as the one in my first post) 

    Ok thanks for those information, it helps me a lot !

    Regards,

    Quentin

  • Hi Justin !

    I tried the People Counting project with the config file of the Lab. Detection was good but as you told me the range was quite short.

    I tried to replace profileCfg and frameCfg from it with others from a long range config I used before:

    profileCfg 0 60 34 7 48.82 0 0 37.5 1 512 12499 0 0 30

    frameCfg 0 1 16 0 250 1 0

    But the result is quite unexpected :

    Currently, I don't know how I could solve this issue of detection.

    So, how can I modify the config from the Lab to increase its range please ?

    Thanks a lot,

    Quentin

  • Hi Quentin,

    Chirp slope determines the range. I recommend first lowering the chirp slope to get the desired range. Range calculation is described in this document.

    Profile config is described in the mmwave SDK user's guide.

  • Hi Justin,

    I already read those documents to create a set of config when I worked with the Area Scanner Lab.

    Unfortunately, as I said, those confgs don't work well with PC project.

    So I tried to create my own profileCfg and frameCfg using the documents you mentionned and some tools as mmWave Studio or mmWave Sensing Estimator while keeping all other config lines dentical to the config of the PC Lab config.

    Here is what I get with Sensing Estimator:

    Using the SDK User guide, I create my profileCfg and frameCfg lines with the values from Sensing estimator:

    profileCfg 0 60.00 2 5.30 72.67 0 0 11.35 1 251 3782 0 0 30

    frameCfg 0 1 31 0 100 1 0

    and so I get my config file :

    My_Config.cfg

    But when I send the config to the radar I get the following error in CCS:

    Error: MMWDemoMSS mmWave Configuration failed [Error: -203685734 mmWave: -3108 SubSys: 38]

    What is responsible of this error in my config ? (I did not managed to find the meaning of those differents error codes in the project)

    Thanks a lot for your patience and your help,

    Best regards

    Quentin

  • Hi Quentin,

    Please see this post on decoding errors

    Regards,

    Justin

  • Hi Justin,

    Thanks a lot !

    Regards,

    Quentin