Yes. As per your thought, That is right. But actually, We don't know the cause of co-ordinator turn off in that case how to cure that scenario. For that I am looking for solution.
Do we have any chance to get any information of connection break down in neighbour table (i.e: age parameter)? Look at the below code snippet:
/****************************************************************************
*
* NAME: vDisplayNT
*
* DESCRIPTION:
* Displays the neighbor table
*
* PARAMETERS: None
*
*
* RETURNS:
* None
*
****************************************************************************/
PUBLIC void vDisplayNT( void )
{
ZPS_tsNwkNib * thisNib = ZPS_psNwkNibGetHandle(ZPS_pvAplZdoGetNwkHandle());
uint8 i;
DBG_vPrintf(TRACE_ZBP_UTILS, "\r\nNT Size: %d\n", thisNib->sTblSize.u16NtActv);
for( i = 0 ; i < thisNib->sTblSize.u16NtActv ; i++ )
{
DBG_vPrintf(TRACE_ZBP_UTILS, "SAddr: 0x%04x - ExtAddr: 0x%016llx - LQI: %i - Failed TX's: %i - Auth: %i - %i %i %i %i %i %i - Active: %i - %i %i %i\n",
thisNib->sTbl.psNtActv[i].u16NwkAddr,
ZPS_u64NwkNibGetMappedIeeeAddr(ZPS_pvAplZdoGetNwkHandle(),thisNib->sTbl.psNtActv[i].u16Lookup),
thisNib->sTbl.psNtActv[i].u8LinkQuality,
thisNib->sTbl.psNtActv[i].u8TxFailed,
thisNib->sTbl.psNtActv[i].uAncAttrs.bfBitfields.u1Authenticated,
thisNib->sTbl.psNtActv[i].uAncAttrs.bfBitfields.u1DeviceType,
thisNib->sTbl.psNtActv[i].uAncAttrs.bfBitfields.u1ExpectAnnc,
thisNib->sTbl.psNtActv[i].uAncAttrs.bfBitfields.u1LinkStatusDone,
thisNib->sTbl.psNtActv[i].uAncAttrs.bfBitfields.u1PowerSource,
thisNib->sTbl.psNtActv[i].uAncAttrs.bfBitfields.u1RxOnWhenIdle,
thisNib->sTbl.psNtActv[i].uAncAttrs.bfBitfields.u1SecurityMode,
thisNib->sTbl.psNtActv[i].uAncAttrs.bfBitfields.u1Used,
thisNib->sTbl.psNtActv[i].uAncAttrs.bfBitfields.u2Relationship,
thisNib->sTbl.psNtActv[i].u8Age,
thisNib->sTbl.psNtActv[i].uAncAttrs.bfBitfields.u3OutgoingCost
);
}
}
Note*: Please look at bold fonts which indicate age field.
Please provide your appropirate input on above query.
Thank you.
Kanji Viroja.