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

Ultra low-power but mission-critical ZigBee sensor?

Ronak Shah
Prodigy 225 points
Other Parts Discussed in Thread: CC2530, TPS62730, CC2540, CC2541

Hi All,

    I am planning to design single chip solution for Zigbee base wireless sensor network in home automation with 4-5 sensors. Module must operated by CR2032 battery cell for 6-12 month.

Meanly, wireless SoC's task are to:

-> Fetch data from GPIO/ADC in every 250 msec.

-> Data acquisition and alarm generation in every 250 msec.

-> Zigbee stack execution and data transfer in mesh as per zigbee standards.

So my queries are:

How fast CC2530/1/3 is in 8051 execution and Zigbee/BLE stack?

Can a single zigbee SoC handle system easy?

And will my system low powered as much I expect?

anyone had face any of issues in those type of application previously?

Thanks and Regards,

Ronak

  • 0
    Guru 31280 points

    Ronak Shah said:

    -> Fetch data from GPIO/ADC in every 250 msec.

    -> Data acquisition and alarm generation in every 250 msec.

    -> Zigbee stack execution and data transfer in mesh as per zigbee standards.

    With these requirements it's kinda hard to get a 6 months of

    operation on CR2032 battery without replacing it with a fresh one.

    The BLE stack may be more suitable for your application since the combination

    of CC2540 along with TPS62730 + BLE can extend your CR2032 battery life.

    By the way CC2541 has better power conservation performance. 

  • 0
    TI__Mastermind 19350 points

    You should not design a very low power but mission-critical/time-critical device to poll its GPIO. Instead, you must design the system so the the GPIO can act as an interrupt source from deep, PM3, sleep. Try to de-couple the ADC input from the mission/time-critical problem to be solved. Hopefully, the ADC input does not need to be acted upon every 250 msec, but instead, only needs to be read, for example, when the GPIO causes a wake from PM3.

     

  • 0 in reply to Dirty Harry
    Prodigy 225 points

    Thanks Harry,

       I understand your point, good. So now if I thought system has 3-4 sensors are connected no GPIO/ADC interrupt pin.

    Will it help me to make my system so fast? and more low power?

    Will I get any problem while executing zigbee stack and mean while I get multiple interrupt from GPIO?

    Regards,

    Ronak

  • 0 in reply to Ronak Shah
    Guru 31280 points

    It is hard to tell.

    Are you still talking about 250ms between two interrupts (4 sensors generates 4

    asynchronous events)?

  • 0 in reply to Igor Sherer
    Prodigy 225 points

    Hi Igor,

       No. Interrupt can generated any time depending sensor. all events are synchronous events.

    Regards,

    Ronak Shah

  • 0 in reply to Ronak Shah
    Guru 31280 points

    My answer to you, it is possible, but use case dependable.

    You can purchase an evaluation board and get proof of concept,

    include timings, responsivity and power consumption.