• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 55 subscribers
  • Views 1403 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Indirect messaging in Zstack Linux Gateway

Jef Shams
Prodigy 150 points
Other Parts Discussed in Thread: CC2531, Z-STACK

Hi,

Description : 

An end device gets its packet from its parent through polling (POLL_RATE defines time duration of polling located in  f8wConfig.cfg)

A parent holds a packet for its child.( NWK_INDIRECT_MSG_TIMEOUT defines holding time located in f8wConfig.cfg)

I have a coordinator implemented in Zstack Linux Gateway (Beaglebone black(BBB)) and there is an end device too.

end device has been joint to network  and binded to the coordinator(gateway). 

Configuration  : 

POLL_RATE of end device is 50 second.

NWK_INDIRECT_MSG_TIMEOUT of ZNP (implemented in cc2531_dongle_usb and connected to BBB) is 60 second.

Problem  : 

When i send a command for example (attribute read command) to end device, the gateway does not hold the command for 60 second and it responds FAILED after about several second. I expect that the coordinator(gateway) hold the command for 60 second until end device poll the command. where is the problem? 

note : when I set POLL_RATE = 5 for end device,everything works properly. 

  • 0
    Guru 735625 points
    Do you send lots of indirect messages in 60 seconds?
  • 0 in reply to YiKai Chen
    Prodigy 150 points
    No, I only send one command and after about 5-10 sec, response is "STATUS_FAILURE".
    Is there a specific command for indirect messaging or each command such as "attr_send_read_attribute_request()" which is sent to end device is indirect messaging?
  • 0 in reply to Jef Shams
    Guru 735625 points
    I suspect NWK_INDIRECT_MSG_TIMEOUT Isn't set correctly. When I test this in SOC mode, it works without problem.
  • 0 in reply to YiKai Chen
    Prodigy 150 points

    I checked it using debug; the NWK_INDIRECT_MSG_TIMEOUT is configured correctly.

    In previous reply, I had said "the response is "STATUS_FAILURE"" .Sorry, I revise it : "the response is "STATUS_TIMEOUT".

    In the document of "Z-Stack Linux Gateway API", it is written :

    "it is possible that an outgoing request will never get its incoming responses (e.g. when the device being contacted is turned off before being able to respond). For that reason, it is recommended that the application implement a timeout when waiting for responses."


    So I think, the timeout response is not from the ZNP, it maybe is from the Z-stack-linux-gateway. But during 50 sec, there is no response from ZNP too!

  • 0 in reply to Jef Shams
    Guru 735625 points
    I would suggest you to use Ubiqua Packet Analyzer to check over the air messages.
  • 0 in reply to YiKai Chen
    Prodigy 150 points

    Thank you for your suggestion.

    Using "Ubiqua Packet Analyzer ", I found that, everything is correct. Gateway as a parent hold command and send it to end device when end device send data_request packet, then end device responds  to the command, BUT the response is not received in z-stack-linux-gateway.

  • 0 in reply to Jef Shams
    Guru 735625 points
    Then, you can only debug into Z-Stack Linux Home gateway application.
  • 0 in reply to YiKai Chen
    Prodigy 150 points

    By debugging "Z-stack Linux Gateway" on BBB and "ZNP" on CC2531_dongle_USB  and end-device simultaneously, I found that :

    (1.)Z-stack Linux Gateway transfer a command to ZNP,

    (2.) Z-stack Linux Gateway gets a confirmation.

    (3,4.)Then  Z-stack Linux Gateway writes TIMEOUT on screen and  it also send  something to ZNP  again!

    (5,6,7) after a while, end-device sends packet-request and receive the command from ZNP and it responds to ZNP.

    (8.) ZNP receives  the packet and transfer it to Z-stack Linux Gateway. BUT any function is called in Z-stack_Linux_Gateway!

    note: I also could not find TIMEOUT parameter to set it for longer time.

    Graphical representation :