• State
  • Locked Locked
  • Replies 11 replies
  • Subscribers 56 subscribers
  • Views 1106 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Problem Devices got removed by itself from TI Z-Stack Linux Gateway

Mohd Khairun Nasir Saadi
Intellectual 300 points

Other Parts Discussed in Thread: Z-STACK, CC2530

Hi,

We have a problem with TI Z-Stack Linux Gateway 1.0.1 together with Z-Stack Home 1.2.2.
The Gateway is running with coordinator CC2530+PA connected to Beaglebone though serial and it use ZNP firmware. And HAL_PA_LNA is enabled. Then we have around 20-30 router devices connected to the Gateway.

The problem is, sometimes occasionally the router devices got disconnected/removed from the gateway by itself.
This happen especially when there is a power breakout.

So we did a test to force power off the Gateway(Switch off beaglebone black) the turn it back on.
After several repeat on-off, then the problem did happen. The devices got removed by itself from the gateway.

Can anyone explain why this problem happen? How to prevent it happen?

Thank you.

Regards,
Khairun

  • 0
    Guru 735695 points
    Do you mean the router is removed from association list or it just cannot receive message from Z-Stack Linux GW? I suggest you to use Ubiqua Packet Analyzer to check this issue.
  • 0 in reply to YiKai Chen
    Intellectual 300 points
    The router is removed from association list from Z-Stack Linux Gateway. I'll share the sniffer log when we done setup the clean environment to grab the log properly.
  • 0 in reply to Mohd Khairun Nasir Saadi
    Guru 735695 points
    Yes, please attach sniffer log so I might be able to know what happens.
  • 0 in reply to YiKai Chen
    Intellectual 300 points

    This is the test result I've been doing and the sniffer logs:

    DEVICES and APPLICATION:

    SampleLight(Router):

    IEEE:     00124B00043C4F29

    Endpoint: 22 23 24

    Coordinator:

    IEEE:     00124B0004407DE6

    Endpoint: 2 3 4 5 6

    TI Linux Gateway running on Beaglebone Debian 7.8

    TEST STEP:

    Hard Reset TI Linux Gateway Server to clean all association

    Factory Reset SampleLight

    On Gateway

    ON SampleLight

    Permit join, Paired device

    Force Power ON/OFF Gateway repeated 20 times

    OFF SampleLight

    Force Power ON/OFF Gateway repeated 20 times

    OFF SampleLight and Gateway leave 30 minutes

    ON SampleLight and Gateway

    Power ON/OFF Gateway repeated, third attemped the Gateway ON, device now got disconnected

    Permit Join, device still cannot connect back to Gateway

    Recycle power SampleLight and start permit join, device still cannot connect back to Gateway

    Recyle power Gateway and start permit join, device still cannot connect back to Gateway

    OFF SampleLight and Gateway leave 5 minutes

    ON SampleLight and Gateway and start permit join, device still cannot connect back to Gateway

    Factory Reset SampleLight and start permit join, device connect back to Gateway

    Extra Test for TI Linux Gateway DB comparison:

    Hard Reset TI Linux Gateway

    Factory Reset SampleLight

    ON SampleLight

    ON Gateway

    Permit join, Paired device

    Remove device and reboot

    ANALYSIS:

    1) TI Linux Gateway DB Initial = TI Linux Gateway DB disconnect by itself = Table list is empty

    2) TI Linux Gateway DB after device remove then reboot = TI Linux Gateway DB Initial = TI Linux Gateway DB disconnect by itself = Table list is empty

    3) Extra Test for TI Linux Gateway DB comparison.

    Factory reset SW and permit join. Once paired then remove the device from Gateway.

    After device remove = TI Linux Gateway DB show SampleLight listed in table and commented by #.

    After device remove then reboot = Table list is empty

    CONCLUSION:

    TI Linux Gateway DB after device remove -> device listed in table commented by #

    TI Linux Gateway DB after device remove then reboot -> device that commented by # now deleted from table

    TI Linux Gateway DB after device remove then reboot = TI Linux Gateway DB Initial = TI Linux Gateway DB disconnect by itself

    ASSUMPTION:

    TI Linux Gateway unintended performed a Hard Reset triggered by Force ON/OFF power to beaglebone black.

    Please take a look at the attached file to have a better look at the Sniffer logs and TI Linux Gateway DB

    Device disconnect by itself issue.zip

    Thank you

    Regards,

    Khairun

  • 0 in reply to Mohd Khairun Nasir Saadi
    Guru 735695 points
    You described Device 00124B00043C4F29 disconnect by itself from GW in "05 Device 00124B00043C4F29 disconnect by itself from GW.psd" but I see Device 00124B00043C4F29 (short address 0x4320) still sending link status in the sniffer log, which means it is still connected within network.
  • 0 in reply to YiKai Chen
    Intellectual 300 points
    Yes, it is disconnected. If you see in the "03 TI Linux Gateway DB Device Disconnect by itself" which I grab from TI Z-Stack Linux Gateway server, the file .csv is empty. Which is strange even though like you said it is still connected to coordinator.
  • 0 in reply to Mohd Khairun Nasir Saadi
    Guru 735695 points
    This sounds like SW problem on Z-Stack Linux Home GW and you can only try to debug by yourself.
  • 0 in reply to YiKai Chen
    Intellectual 300 points
    The problem as you can see, is it the Gateway application problem or the Gateway server problem?
    For Gateway server, that is unlikely that I can do any changes since we only have the binary of the TI Z-Stack Linux Gateway.
    I wonder when do TI will release a new version based on Z-Stack 3.0. It is been a long time since the first release.
  • 0 in reply to Mohd Khairun Nasir Saadi
    Guru 735695 points
    This is more like application problem from my point of view.
  • 0 in reply to YiKai Chen
    Intellectual 300 points
    Based on TI Linux Gateway application given for free together with the source code. Can you point to where did the DB csv file being read and write. Any suggestion on how to prevent the problem of table list become empty? Is it because of improper shutdown of the beaglebone black/gateway?

    Because, we try to simulate the power breakdown situation when improper shutdown of the controller happen. Turn out we face this problem with device table list empty.
  • 0 in reply to Mohd Khairun Nasir Saadi
    Guru 735695 points
    After checking source code, I think you need to have full source code of Z-Stack Linux Home GW to trace this issue.