• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 31 subscribers
  • Views 637 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.

Headset Eval Power Management

Mark Davis
Prodigy 205 points

I am using the CC85XX-Headset evaluation kit and have set the power management on the Master device to NONE.  I am powering the Master with a USB adapter.  As soon as power is applied, the unit begins to operate.  After an extended time, it powers down.  If I cycle the power, it returns to normal operation.  I don't have a good feel for time frame before the shutdown.  It only occurs if there are no clients but it is a long time and does not seem related to the missing network trigger.  Is there a default maximum time before shutdown?

  • 0
    TI__Expert 6825 points

    Hi Mark,

    No, it should not behave like that. What PPW project are you using? Please post it! Also, whar rev of the FW do you have?

    -Per

  • 0 in reply to Per H
    TI__Expert 6825 points

    One other thing came to mind, do have the battery connected while testing?

  • 0 in reply to Per H
    Prodigy 205 points

    I did not have a battery connected.  I did find another posting about the charge controller shutting down if it does not detect a battery.  I suspect that is my issue.

    Just for information, firmware 1.4.2.

    I am also getting random shutdowns from the slave units.  Time period is completely random and they are battery powered only, fully charged.  I can simply turn them back on and they operated for a random time period.  Power management is set for power toggle button with a network timeout of 120 seconds.

    Sometimes the slave shutdown is a reset and other times it just turns off.

  • 0 in reply to Mark Davis
    Prodigy 205 points

    Some preliminary testing results.  It seems related to the network timeout.  The only change in configuration was to disable the network timeout.  I have run the system for about 8 hours without a shutdown.  Way longer than I get with it enabled.  I'll keep and eye on it and update in a couple of days.

  • 0 in reply to Mark Davis
    Prodigy 205 points

    I now have over 60 hours of run time on the slave units without a random power down/reset.  The only change in power management was to NOT enable "power down if not connected to a network".  The downside is that if the user does not turn the slave off, it will run the battery down.  It was really nice to have an automatic shutdown at the loss of network.

    Any suggestions?

  • 0 in reply to Mark Davis
    TI__Mastermind 21125 points

    Hi Mark, 

    Have you verified that this is not actual NWK dropouts, did this happen while streaming audio?
    Assume the power down if audio outputs are silent was not enabled at the same time?

    I have not seen others reporting a faulty timeout for this parameter and that has this feature successfully implemented. 

    Kjetil

  • 0 in reply to Kjetil
    Prodigy 205 points

    Yes, I did my best to confirm it was not NWK dropouts.  It did happen while streaming audio at random time intervals.  I had to power the unit back on for audio streaming to resume.  I did not have the "power down if audio is silent" enabled.

    I have done something else and re-enabled the auto power down.  I covered the board with clear electrical tape. I am suspecting it could be a static issue.  The randomness has me believing that it is external to the firmware.

    I will update again when I know if this has any effect.