• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 56 subscribers
  • Views 985 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.

CC2538: Sending data to coordinator as router function

Jackson Loh
Prodigy 80 points

Part Number: CC2538
Other Parts Discussed in Thread: TIMAC, Z-STACK,

Hi,

I encounter an issue when using TIMAC software. My devices is setup in a beacon enabled network where I have a PAN coordinator and routers.

For the router, I had the device setup as both Coordinator and Device. However, when the router device try to send data to the its parent router, the data is sending out during the its own beacon time instead of the parent beacon time. Since the data would not be ACK by the parent router when it sending out, the data will be sending again when the next parent beacon.

Even I have checked on MAC_MLME_BEACON_NOTIFY_IND to ensure that the beacon I have received is from its parent router before calling the function MAC_McpsDataReq, the data does not send out until its own beacon time.

Is there any way to solve this?

Thank you.

  • 0
    TI__Expert 8950 points

    Hi Jackson,

    Are you using TIMAC or Z-Stack? TIMAC does not have routers, only PAN coordinators and end devices.

  • 0 in reply to JasonB
    Prodigy 80 points

    I am using TIMAC. First I start the device as Device function. After associated with parent router/coordinator and successfully joining into the network, it will make a Coordinator startup and called MAC_MlmeStartReq.
    This work as what I need as it can associate with new device appear in the network.
    However, the issue occurs when it try to send data to its parent device.
    Any suggestion how to resolve this?

  • 0 in reply to Jackson Loh
    TI__Expert 8950 points
    Can you please .zip the .psd sniffer log and post it here?
  • 0 in reply to JasonB
    Prodigy 80 points

    You can see it happening on packet number RX268.

    The data is suppose to be sent from 0xE7C7 to 0xE7E4. However, the device 0xE7C7 is sending out the data during its own beacon time.

    And since the data did not get acknowledged, it resend again during the 0xE7E4 beacon time (packet number RX276).

    Please find the sniffer log attached.

    test_150317.zip

  • 0 in reply to Jackson Loh
    Prodigy 80 points

    Hi,

    We found another issue. When we heated up the pcb with CC2538 to roughly 70 degree celcius, the device does not send out any beacon anymore.

    However, the device is still able to sync with its parent router and sending out data when requested by the parent router.

    When the temperature is turn off and back to room temp, the device will once again resume to sending out beacon and the sequence number for the beacon is continue from where it stop sending out when get heated.

    Any idea what is happening and how to resolve it? 

  • 0 in reply to Jackson Loh
    TI__Genius 10650 points
    Hi Jackson, I have the following question to understand the issue better, when the device is heated up, the only functionality that is affected is that the device stops sending beacons, but all other application and network activity for example sending / receiving data from the PAN-coordinator still works? Or the device completely stops working at higher temperature?
  • 0 in reply to Suyash Jain
    Prodigy 80 points

    Hi Suyash,

    Yes, the other network activity still works except sending out its own beacon.

    The heated device still able to sync with its coordinator as well as transmit and receive data from coordinator.

    When the heat is removed, the beacon is sending out as the same timing as before.