• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 16 subscribers
  • Views 443 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.

RemoTI/RF4CE Standby mode - transmission reliability

Oscar Mezyk
Prodigy 130 points
Other Parts Discussed in Thread: REMOTI

Dear all,

could anyone let me know which parameters in RemoTI  specify what happens when the Target is in STANBY (duty cycling) and the Remote tries to send a packet?  Is the tranmission replied untill success or target sends a beacon on wake-up or?  Where is it described?

Thanks

OscarM.

  • 0
    TI__Genius 16570 points

    Hi Oscar,

    the behavior of the target node in standby is described in the RF4CE specification.

    There's no beacon signal being transmitted by the target. Target open its receiver window for a certain amount of time with respect to the duty cycle.

    These values are specified as NIB elements in the RF4CE specification: nwkDutyCycle, nwkActivePeriod. Please note also controlling the node in power saving mode is specified by RF4CE spec to be a NIB element: nwkInPowerSave.

    RF4CE specification details also the behavior of the controller node for data service: as there's no beacon signal for better power performance on a controller node, remotes acquire the target channel by sending data in multi-channel acknowledged mode (the timeout for sending node is 1 sec).

    Hence, as controller and target are asynchronous in this protocol, to guarantee at least that RC hits one receiver window during the duty cycle of target, nwkDutyCycle shall be < 1sec and nwkActivePeriod > (time needed to send on 3 channels). More receiver windows can be hit (hence more robust the system can be designed with respect to OTA collisions) if the duty cycle is reduced, with the obvious downside of bigger power consumption on the receiver side. 

    The RemoTI stack allows user to control these parameters through RTI_WriteItem API. The items are the following

    RTI_SA_ITEM_STANDBY_ACTIVE_PERIOD --> default 16 msecs

    RTI_SA_ITEM_DUTY_CYCLE --> default 330 msecs

    RTI_SA_ITEM_IN_POWER_SAVE --> default TRUE

    These are NWK config parameters so they they need to be written after stack has completed its initialization if you want to change them. If that is the case, please modify after stack has finished its init routine (RTI_InitCnf callback).

    I hope this helps.

    Thanks and have a nice day,

    TheDarkSide

     

     

     

     

     

  • 0 in reply to TheDarkSide
    Prodigy 130 points

    Thanks TheDarkSide, but still I got some uncertainity:

    what will happen if I hit the button just after ActivePeriod finishes? Will the RC continue sending the packet until the Target recieve window opens again? Meaning that it will try to send the packet for at least ~330-16ms=314ms?

     

    thx

    Oscar

     

  • 0 in reply to Oscar Mezyk
    TI__Genius 16570 points

    Hey Oscar,

    yes the controller keeps sending data for 1 sec from the moment you hit the button.

    It will hit with a probablity = 1 the receiver open window 3 times in 1 sec and of course stops sending data when the first ACK is received.

    I hope this clarifies your doubts.

     Thanks,

    TheDarkSide