LAUNCHXL-CC2650: multiple ACTIVE_EP_REQ

There is no mac ack so it would do Mac layer retry.

so, is there anyway we can change the retry count?
why 8 times retry from MAC layer ? is it specification?

You can try to revise NWK_MAX_DATA_RETRIES. By the way, can you attach your sniffer log instead of screenshot?

may i know, which file i need to modify this variable. when i tried to search, i found "NWK_MAX_DATA_RETRIES" defined in command line

It should be in f8wconfig.cfg.

As I remember, APSC_MAX_FRAME_RETRIES in f8wconfig also affects retry count. Can you attach sniffer log so I can check what exactly happens?

the attached sniffer log file, you can see, 2 times i sent "ZDO_ACTIVE_EP_REQ (0x2505)" which was successful. then i power off my router. then i quiried again 2 times. 1st time i received 7 times "ACTIVE_EP_REQ" in packet sniffer, and in 2nd time query i received 8 times "ACTIVE_EP_REQ"

i found the variable "-DNWK_MAX_DATA_RETRIES" in "znp_f8wConfig.cfg" set as 2. if i change to 1 then when my router i switch off and request for "ACTIVE_EP_REQ", i get 4 times query instead of 8 times. but i want to make it 1. instead of 4

Hi Kaushik,

YK has already mentioned that DAPSC_MAX_FRAME_RETRIES also affects retry count, please reduce this value to 1 or 0 as well.

Regards,
Ryan

Hi,
i just verified, modifying DAPSC_MAX_FRAME_RETRIES does not have any effect in number of ACTIVE_EP_REQ in packet sniffer log.

Is there any other stuff need to do. i still getting 4 ACTIVE_EP_REQ (if my router is turn off and coordinator query for ACTIVE_EP_REQ).
I changed -DNWK_MAX_DATA_RETRIES from 2 to 1, this only make instead of sending 8 times, 4 times sending from MAC, all this i can see from packet sniffer.

please suggest.

best regards.

Try to set NWK_MAX_DATA_RETRIES to 0.

if i make NWK_MAX_DATA_RETRIES to 0 then i receive error in ztool.

<TX>10:24:12.36 COM70 ZDO_ACTIVE_EP_REQ (0x2505)
DstAddr: 0x59BF
NWKAddrOfInterest: 0x59BF

<RX>10:24:12.37 COM70 ZDO_ACTIVE_EP_REQ_SRSP (0x6505)
Status: afStatus_MEM_FAIL (0x10)

I don’t think it’s related to this change. If I remember correctly, if there is no MAC ack and retry time out of NWK_MAX_DATA_RETRIES *APSC_MAX_FRAME_RETRIES, device would stop retry. So, device should not do retry when you set the value to 0.

if i make NWK_MAX_DATA_RETRIES to 0 then i receive error in ztool, which i mentioned previous post. But if i set to 1 then 4 times retries i can see. if i set to 2 then 8 times retries.

Hi Kaushik,

Other suggestions include altering maxFrameRetries value of the macPibDefaults value in mac_pib.c and/or replacing the 4 value with (MAC PIB maxFrameRetries+1) inside the attrValue equation of zclDiagnostic_GetStatsAttr function of zcl_diagnostic.c

Regards,
Ryan

Hi Ryan / YiKai,

still same, i received 4 times, instead of 1 time

in mac_pib.c
1, //3, /* maxFrameRetries */

zclDiagnostic_GetStatsAttr function of zcl_diagnostic.c i made
*attrValue = ( macRetriesPerApsTx + ( apsTxUcastFailure * (maxFrameRetries+1) ) ) / ( apsTxUcastSuccess + apsTxUcastFailure );

Please confirm that settings of APSC_MAX_FRAME_RETRIES = 0 and MAX_DATA_RETRIES = 1 do not give the expected results. However, your system really needs retry attempts to allow proper time for a MAC ACK, why are you intentional on this non-recommended setup?

Hi Rayan,
APSC_MAX_FRAME_RETRIES = 0 and MAX_DATA_RETRIES = 1 does not give expected result. I don't want retries because in my application I want one time query without any retry.

Hi Yk Chen,

I tried your recommendation. But it also does not give no retry.

Always 4 times retry.

Best regards

Since you use ZNP project of CC2650, you should revise znp_f8wConfig.cfg instead of f8wConfig.cfg

I modified znp_f8wConfig.cfg, not f8wConfig.cfg. because, when you asked me to change in f8wConfig.cfg, i found ZNP project does not use it. XNP project use znp_f8wConfig.cfg. So, my ,odification was in znp_f8wConfig.cfg

But this does not work (4 times retries still there)

What if you use APSC_MAX_FRAME_RETRIES = 1 and MAX_DATA_RETRIES = 1?

zsniffer_debug_02.7zHi YiKai,

It's same response (4 times retries). please refer to attached sniffer output

best regards

In CC2650 ZNP source code, I couldn't find something like "{offsetof(macPib_t, maxFrameRetries), sizeof(uint8), 0, 7}" in CC253x ZNP source code. Need TI employee to suggest anything new...

C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP for the CC26xx uses znp_f8wConfig.cfg, C:\Texas Instruments\Z-Stack Home 1.2.2a.44539\Projects\zstack\ZNP for the CC253x uses f8wConfig.cfg, therefore the znp_f8wConfig.cfg is correct given use of the CC2650 device. I am still attempting to replicate this issue, what ZNP coordinator firmware is used on the LAUNCHXL-CC2650?

Regards,
Ryan

Hi Rayan,

I used ZNP fw located in C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP location

Best regards

Hey Kaushik,

What are your pre-processor options? I can't recognize the Coordinator - Pro Secure Link Key Join project firmware inside of Z-Tool. The pre-built image from the ZAP folder does work but this won't help me debug your issue.

Regards,
Ryan

Hi Rayan,

The project located in C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx

I use IAR 7.80.1.11873 to compile the code. I use option Coordinator -pro. This firmware get recognize by ztool 2.0.6.
I didn't use pre build image. as the outcome from pre build image and compiled image are same. And i need to modify certain parameters what you guys provided before.

Pre-processor options are as follows
ewarm
FLASH_ROM_BUILD
USE_ICALL
HEAPMGR_SIZE=6500
FEATURE_MAC_SECURITY
FEATURE_GREEN_POWER
FEATURE_ENHANCED_BEACON
ICALL_HOOK_ABORT_FUNC=halAssertHandler
CC26XX
xdc_runtime_Log_DISABLE_ALL
xdc_runtime_Assert_DISABLE_ALL
MODULE_CC26XX_7X7
xMODULE_CC26XX_5X5
xMODULE_CC26XX_4X4
ZDO_API_ADVANCED
HAL_ASSERT_SPIN
NEAR_FUNC=
DATA=
FEATURE_SYSTEM_STATS
ZDNWKMGR_MIN_TRANSMISSIONS=0
SECURE=0
xTC_LINKKEY_JOIN
DSECMGR_TC_DEVICE_MAX=16
xHOLD_AUTO_START
ROM_SBL
FEATURE_NVEXID
NPI
NPI_SREQRSP
NPI_USE_UART
NPI_UART_BR=115200
MT_SYS_FUNC

Thank you
Best Regards