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.

CC2652R: Correlation received in ZMacLqiAdjust function is always 0

Part Number: CC2652R
Other Parts Discussed in Thread: CC2592,

Hi,

I have tried to use the ZMacLqiAdjust  as suggested by the TI user guide. However I always get the correlation value to be 0 irrespective of the RSSI.or how close the sending device is
Is there something that has to be configured to get the data correctly ? Any advise would be helpful.

SDK 6.10

Custom CC2652R + CC2592 amp for PA/LNA

Thanks
Akhilesh

  • Hi Akhilesh,

    lqiAdjMode is LQI_ADJ_OFF by default, thus no adjustment is performed.  Have you changed this inside zmac_cb.c and what mode is selected?  How are you calling ZMacLqiAdjust (provide code snippet) and have you stepped through the function inside the debugger to further understand its operation?

    Regards,
    Ryan

  • Hi Ryan

    I have modified zmac_cb.c to use te the LQI_ADJ_MODE1 as suggested in ZStack overview.. 
    The ZMacLqiAdjust is called in zmac_cb.c in the MAC_CbackEvent, this call was already present in zmac_cb.c and I haven't modified it.

    I have stepped in the code and the value of the correlation from the incoming max rx is always 0 and so the adjusted LQI also becomes 0 and this affects routing.

    Is it advised to used the LQI adjust ? 

    Also the default LQI_MIN_CORR=50 and LQ_MAX_CORR=110, however from the datasheet seems like correlation is 6 bits so it would range from 0-64, so do these limits have to be changed for cc2652r ? 

    Thanks
    Akhilesh

  • Hi Akhilesh,

    Thank you for providing this information.  After further investigation it appears that the equation/definitions used in LQI_ADJ_MODE1 are not currently valid for the SimpleLink CC13XX / CC26XX.  I cannot recommend that you further evaluate the use of ZMacLqiAdjust unless this is further investigated by the Software Development Team.

    Regards,
    Ryan