• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 392 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.

MSP430FR6047: AbsTOF interval and error reporting.

Thibault Helle
Expert 2090 points
Part Number: MSP430FR6047

Hi!

When having the USS_ALG_ABS_TOF_INTERVAL greater than 1, and removing ultrasonic sensors, I do not get the error 126 "USS_message_code_algorithm_error_no_signal_detected_ups_dns_channel" until the interval of absTOF calculation is done. Instead I get no error and the same flow rate/dTOF is returned as the last sample. The error appears when the interval is done.

I need to have a quick error reporting and a lower power consumption using bigger interval.

Why is this happening, the dTOF should still be calculated right? 

Thanks in advance

Best regards,
Thibault 

  • 0
    TI__Expert 7365 points
    Hi Thibault,
    That is the expected behavior according to the Ultrasonic SW Library implementation.
    The DToF does not get re-calculated if the internal state shows that there is no signal which is what error 126 "USS_message_code_algorithm_error_no_signal_detected_ups_dns_channel" indicates.
    If there is no signal, a new DToF calculation does not make sense as it trying to make an estimate from noise!
    Srinivas
  • 0 in reply to Srinivas Lingam
    Expert 2090 points

    Srinivas Lingam said:
    Hi Thibault,
    That is the expected behavior according to the Ultrasonic SW Library implementation.
    The DToF does not get re-calculated if the internal state shows that there is no signal which is what error 126 "USS_message_code_algorithm_error_no_signal_detected_ups_dns_channel" indicates.
    If there is no signal, a new DToF calculation does not make sense as it trying to make an estimate from noise!
    Srinivas

    Hi Srinivas,

    Okay but is there a way of knowing if we do not have a signal right away, because I do not get any error from the USS_startLowPowerUltrasonicCapture() or USS_runAlgorithmsFixedPoint() functions?

    Right know I have to wait x seconds for error 126 to appear due to the absTOF interval. 

    Thanks 

  • 0 in reply to Thibault Helle
    TI__Expert 7365 points
    Hi Thibault,
    In the current SW, the signal level check is done inside the Absolute ToF computation. If you reduce the rate of computation of AToF by setting USS_ALG_ABS_TOF_INTERVAL > 1, you will have this delay. One option for you now is to add a check for the signal level as part of the application SW.
    Srinivas

**Attention** This is a public forum