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.

IWR6843LEVM: Problems about data processing in vital sign

Part Number: IWR6843LEVM

Hi

while we are doing the experiments about Vital_Signs_With_People_Tracking:

FW:  vital_signs_tracking_6843AOP_demo

CFG: vital_signs_AOP_2m

By far we undertand that these vital signs are calculated based on FW of people tracking, and most of parameters and algos are specifically explained.

However, about vital sign part, we have no idea about how our radar processed and output these information.

We have checked about some user guides and articles, but no clues in the end.

We will be gratful if you can give us some advice about this problem and where could we probably find answers.

Sincerely

  • P.S.
    In our experiments, Accuracy counld be very low when targets' heart rates are high(100 -120 BPM, error: 40 - 60 BPM). Maybe you used filters or something like?

    Our sensor is located in the upper left of the head, about 30cm away the head. Antennas are right towards to the chest


    Anyway, we really need the details of vital measurement algo, if it is possible to tell us.

    gratefully

  • Hi

    Thanks for your query. Please allow us a couple of days to respond

    Regards

  • Hi,

    You need to sign NDA with TI to get access to source code. Please get in touch with local FAE to sign the NDA.

    You can refer to radar_toolbox_2_00_00_06\source\ti\examples\Medical\Vital_Signs_With_People_Tracking\docs\vital_signs_with_people_tracking_user_guide.html

    to get information about the data sent out the device for Vital signs. It is expected that accuracy of vital signs will be +/-5 for Breath rate and +/-10 for heart rate. mmwave radar cannot provide the same level of accuracy as a smart watch or a pulse oximeter. Also, person needs to be stationary for alteast 30 seconds for the data to be accurate. As you are using a 2m configuration, can you try with AOP mounted on a tripod facing the chest area of the person and the person is sitting at a distance of 2m from the sensor

    Regards

  • Hi

    Thanks for replying

    In current stage, we don't need specific information like source code.

    Say, if we put our 6843isk at a certain position(OHC, or roof in a car), can we detect vital sign of an adult who sits in the driver's seat.

    From our data, the heart rate is always around 60 even our test target is over 120. We are thinking about that if you used LPF or something like that?

     In addition, what does "range bin" exactly represent? 0.84m(range resolution) * range bin = range, in user guide, but this is different from out data.

    Sincerely

  • Some functional questions are based on our speculation, so you don't have to answer if it is confidential
    But can you tell us what does range bin mean? Does range resolution equals to range unit.

    Thanks for following this problem. 

  • Hi

    Range bin is range/range resolution

    The demo will have a specific range resolution(in few cms) based on the configuration used by the demo. Range bin is representation of range in terms of range resolution

    Regards