• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 216 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.

LAUNCHXL-CC1310: CC1310 collector and sensor reset behavior

artur adamiak
Prodigy 250 points
Part Number: LAUNCHXL-CC1310

Hi,

Could someone explain to me what is doing after reset in sensor and collector examples?

Lets say I have power reset or software reset in sensor, is it still in network, should it rejoin or what?

In code of collector there are 3 cases:

if(addDeviceListItem(&dev, &newDevice) == false)
{
}
else if (true == newDevice) {
}
else {
}

Similar question about collector itself, has it got some default NV memory?

Is network still working after power reset?

Best regards

  • +1
    TI__Genius 14845 points

    Hi Artur, 

    As long as you don't reload the examples so one device remembers the connection but the other one does not, they should be able to reconnect after power reset. 

    Thanks, 
    Elin

  • 0
    Genius 5680 points

    It also depends if you use frequency hopping or not.

    Basically, when the sensor reboots it checks if network info is present in NV within the function sensor_process(). If there is info, it simply rejoins the network. If a software or factory reset occurs including an erase of the NV, there is no networ info present, thus it will search for a network and join it. This is basically the same behavior for the collector except that it does not search but open a new network if no info is found in its NV and if it founds info, it simply proceeds as if nothing has happened.

    However, if you perform a simple reset without NV erase on either the  sensor or collector, the FH timetable is not synced between sensor and collector, thus there will be no simple rejoin be possible. E.g. with 20 sensors and 1 collector, all sensors will go into the orphan state if the collector reboots. At least this is what I noticed.

  • 0 in reply to Slev1n
    Prodigy 250 points

    Thank you for this answer. So what are you doing after collector reset? Or should I just turn off FH?

    I want to be safe that sensors will still be working fine after some blackout. 

  • 0 in reply to artur adamiak
    Genius 5680 points

    Well it depends on in which country of the world you are planning to deploy your devices in the end if you choose non-beacon or FH. (I have no experience with beacon mode). If you have a simple blackout this means, that your devices always have their network info still present in their NV.

    I assume that the out of the box example covers this scenario for both, FH and non-beacon. I have added too many self-content to the code and I am using no the most recent SDK. Just try it out with two launchpads