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

Tracking System with ZigBee

Imran7159
Prodigy 20 points


We propose to use your ZigBee technology for delivering a Wireless ECG
system for a following environment:

Hardware: eZ430-RF2480

Software Tool IAR Kickstart

1)    Upto 10 beds in an inpatient ward with ECG systems - communicating
their signals at 115,200 bits per second

2)    Each ECG system connected to a ZigBee end device - relaying the
information to a central Coordinator within 20 meters of distance from
any of the ECG systems

3)    The central coordinator connected to a PC over USB 2.0 - running
ECG monitoring software

4)    Routers as needed.

 

Can you please advice if we are likely to encounter any technical issues
- such as communication speed, discontinuity in communication etc

  • 0
    Intellectual 380 points

    Hello,

    does each ecg system transmit the signal with 115kbps over the air or is this just the used baud rate for the uart and the heart rate or any other evaluated information is transmitted only a few times per second ?

    Since IEEE802.15.4 only offers a datarate of 250kbps, 10 times 115kbps will break down the network...

    Regards,

    Tobias

  • 0 in reply to Tobias4760
    Prodigy 20 points

    Hi Tobias,

    The communication from ECG systems will NOT be continuous.  It is just the used baud rate – and information is transmitted intermittantly – the periodicity can be controlled.  We can do it in round robin method – polling for information from the 10 systems one at a time. 

    Even IEEE802.15.4 offers 250kbps, what is the effective data rate we will get with TI device?

     

    Thanks & Regards,

    Imran

  • 0 in reply to Imran7159
    Intellectual 380 points

    I guess the payload size for simple api packets is around 85 bytes. This leads to an overhead of 42 bytes + the phy overhead of 6 bytes. With a ratio from 85 bytes per 133 bytes packet this is a data rate of around 157kbps... ( All calculations without warranty ;-) )

    Tobias