ZDP_MgmtLeaveReq for remove End Device

1. Why your dst short address is 0x0000, it should be the short address of the end device that you want to ask it to leave.

2. Yes, it is in hex format.

Earlier I have given the short address of end device only. But doesn't work. Then in one of the post u mentioned we need to give 0x0000 as dst Addr. Both doesn't work.

Earlier I have given the short address of end device only. But doesn't work. Then in one of the post u mentioned we need to give 0x0000 as dst Addr. Both doesn't work.

http://e2e.ti.com/support/low_power_rf/f/158/p/307290/1069461.aspx#1069461

If see the packet sniffer, Coordinator is successfully sends the request and end device also sends response. But still End device stays in the network. It is not leaving. Should I do any thing apart from this API.4784.packet.psd

Could Some one answer my question. it's really urgent for me.

Hi Reshmi,

I was not able to successfully open/parse the sniffer log you attached. I assume you used SmartRF Packet Sniffer to capture it. Can you please try to open the saved file, and if it succeeds, describe the steps to follow?

Regarding the issue itself - can you please check what is the status reported back in the leave response from the end device?

Regards,

OD

Hi Reshmi,

It's my fault to ask why your short address is 0x0000. You should use it in ZDP_MgmtLeaveReq. I just try this function in Z-Stack Home 1.2.0 and Z-Stack 2.5.0. They all work fine. Which Z-Stack version do you use?

Dear Yikai,

    I am using Zstack 2.5.1a.

Dear OD,

    Yes i have used smart RF packet sniffer. When i open saved file, It is asking for select RF Device type, with none select, i have given ok. Then i could able to open it successfully.

From your sniffer log, I don't see your coordinator sends out leave request. Please check return of ZDP_MgmtLeaveReq().

I am getting the return value as 0. which is success. In the packet sniffer, u can see the request after the End device is broad cast End node announcement. after that coordinator with Nwk src Address 0x0000 sending request.

    And what i need to give in dst address?short address of Coordinator or End device. 

The dst address should be 0x0000 and the IEEE address should be ZED's.

I have given dst addr 0x0000 only. But still End device is in network. I am given compile option ZDO_MGMT_LEAVE_REQUEST=1 in IAR also.

Earlier i have set ZDO_MGMT_LEAVE_REQUEST in ZDConfig.h. Then i tried to add ZDO_MGMT_LEAVE_REQUEST=1 in IAR compile option, now it's giving error  Error[Pe223]: function "MT_ZdoMgmtLeaveRequest" declared implicitly

Thanks to Yikai and OD for supporting me. I could able to solve it. Now ZC sends successful leave request. My problem is solved.

I have two more query,

1) After sending leave request, why the end device is not searching for other network to join. In the packet sniffer. I could able to see beacon request from end device. If End device is get a leave request, then it should search for other network to join. How it can be possible.

2)Can i increase the signal strength by changing any register in Zstack as we change in Bluetooth. 

Hi Reshmi,

Would you share how you solve the problem finally so it might help other has the same situation? As for your new question, here are my answer.

1.  You can set Rejoin parameter of ZDP_MgmtLeaveReq to 1.

2. You can use macRadioSetTxPower to set TX power.

Earlier I have set ZDO_MGMT_LEAVE_REQUEST in ZDConfig.h. Which is not working for me. Then I have defined in Compile option ZDO_MGMT_LEAVE_REQUEST=1 in IAR. Then it gives error as mentioned in previous post. That I fixed by adding the compile option. MT_ZDO_MGMT=1.

Where can I find the macRadioSetTxPower in ZStack 2.5.1a

Hi Reshmi,

You can change the Tx Power value by calling API ZMacSetTransmitPower() ( in zmac.c) and passing an argument of type ZMacTransmitPower_t. This lets you change tx power in -1db steps from -22db to 19db.

Saurabh

macRadioSetTxPower is in mac_radio.c

Thanks Yikai and saurabh. Should I call ZMacSetTransmitPower() in init?. what is the default tx power defined in sample light App, where it is defined. If I call ZMacSetTransmitPower() in init whether it will create a conflict.

In my application, I set it in zcl_XXX_Init.

Hi Reshmi,

I am also facing similar issue as ZDP_MgmtLeaveReq is not working.

I have set compile time option as ZDO_MGMT_LEAVE_REQUEST=1,

but I am also getting compile time error.

Can you please let me know what is the way to fix this issue.

Thanks  & Regards,

Nilima

Hi All,

Please can anybody help in sending leave request to end device.

Thanks & Regards,

Nilima

Hi Nilima,

How do you define ZDO_MGMT_LEAVE_REQUEST=1 and what compile error do you get?

Hi YiKai,

Sorry to I did not mentioned that.
So since ZDO_MGMT_LEAVE_REQUEST was giving error, I am setting COMPILATION flag as MT_ZDO_MGMT=1.

You don't have to define MT_ZDO_MGMT=1. Just define MT_ZDO_MGMT in compile option.

Hello YK Chen

Thanks for your reply. My implementation is as below:

When I receiving anything, I'll save the address information in

zAddrType_t lastMsgAddr

So when I want to remove such a device later on, I'll have process as below:

        APSME_LookupExtAddr(lastMsgAddr.addr.shortAddr
                             , lastMsgAddr.addr.extAddr);
        ZDP_MgmtLeaveReq(&lastMsgAddr, lastMsgAddr.addr.extAddr,0,1,1);

I have define 

ZDO_MGMT_LEAVE_RESPONSE
ZDO_MGMT_LEAVE_REQUEST

on both Coordinator and end device in iar. Unfortunately seems the code doesn't work... 

Tian

Hello YK Chen

Now I can remove the end device from the network. However another problem comes. 

I enable the end device rejoin network through 

ZDP_MgmtLeaveReq(&dstAddr, mac, true, true, false);

The end device can receive the message and re-join the same network. However, after few seconds, the end device will send couple of Data request in a short period of time, then the coordinator seems goes dead and end device send out an orphan notification. 

I tried many times and this always happen. Below is the sniffer file.

P1.psdP2.psd

Hope you can help! Thanks!

Regards,

Yiran

Indeed, its just like you said. Its the coordinator died first.

For some reason it goes into

HAL_ISR_FUNCTION( macMcuRfIsr, RF_VECTOR )

in mac_mcu.c and never goes out.

The coordinator get stuck in code:

  /* process RFIRQF0 next */
  if ((RFIRQF0 & IRQ_FIFOP) & rfim)
  {
    /* continue to execute interrup                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        t handler as long as FIFOP is active */
    do
    {
      macRxThresholdIsr();
      RFIRQF0 = (IRQ_FIFOP ^ 0xFF);
    } while (FSMSTAT1 & FIFOP);
  }

The do-while loop.

Regards.

Yiran

Mostly in application level. The only modification was in ZDOApp.c, ZDO_JoinIndicationCB().

Following code was embedded to implement a join whitelist.

  uint8     index;
  uint8*    goodtogo;

  // Look through the stored device list - used for approve devices
  for ( index = 0; index < HVAC_MAX_DRONE_NUM; index++ )
  {
    goodtogo = hvac_whiteList[index];

    if ( AddrMgrExtAddrEqual( goodtogo, ExtendedAddress )  == TRUE )
    {
      // break from loop
      index = HVAC_MAX_DRONE_NUM;
      
      // return as unknown device in regards to validation
      return ZSuccess;
    }
  }
  // Invalid join
  return ZFailure;