• State TI Thinks Resolved
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 64 subscribers
  • Views 66 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

BQ40Z80: Unexplained shutdown, how to prevent and how to reset

Jeff Lenko
Prodigy 10 points
Part Number: BQ40Z80
Other Parts Discussed in Thread: BQSTUDIO

Tool/software:

Hello,

I am a electrical service technician that owns, operates, and maintains several tethered underwater drones known as ROV's that I use for remote inspection of irrigation pump station intake structures in fresh water ponds and lakes. 

Recently my larger ROV which has a removable Lithium Ion battery, failed suddenly, shortly after placing it in the water. After verifying the handheld controller and tether were ok and that the electronics housing was dry, I turned my attention to the battery. The battery level gauge on the controller had shown "full" as did the indicator light on the charger both before and after the failure. 

I currently have the battery connected to my laptop which is running BQSTUDIO to determine why the battery shutdown. The BAT pin voltage is 24569 mv, but the PACK pin voltage is only 8 mv. It appears that the discharge FET's are shut down but I don't see reason for that. Unfortunately I'm not familiar with the software yet, so I'm not sure what exactly what I need to do, since I don't see any alarms or faults causing the shutdown. 

Here are some screenshots that might help. Unfortunately since this is the first time using the software, I'm not sure what I should be looking for. I couldn't find any tutorial that explains the different screens and information displayed. I also videoed the screen as I tapped on each tab and scrolled though to show all of the information. 

  • 0
    TI__Mastermind 31526 points

    Hello Jeff,

    Based on your screenshot, as you can see from the "Safety Status A+B" register, the "ASCDL" protection tripped which is the short circuit in discharge protection. Seemed that when the drone was placed in the water it cause a short circuit to happen. You can read more about the protection here:

    Regards,

    Adrian

  • 0 in reply to Adrian
    Prodigy 10 points

    There was no water leak into the battery compartment, bulkhead connector or electronics housing. That was the first thing I checked, along with the tether and handheld controller. I was hoping the "Black Box Recorder" would show some reason for the fault, but it doesn't seem to show anything. Why isn't there any recorded data?

    I finally tried doing a "reset" and I got the short circuit fault to clear but the discharge FET's stay off unless I toggle them manually.

    I see in Operation Status A that the XCHG and XDSG bits are high. Is this why the FET's are staying off and if so, why didn't this clear with the reset? What do I need to do to get the battery to return to "normal?" I've attached a gg and log file to see if they help you. I was just getting ready to switch my connections around so I can connect the battery charger and see if it makes a difference.

    112.28.24.gg.csvM2 Pro 12.21.24_a.log

  • 0 in reply to Jeff Lenko
    TI__Mastermind 31526 points

    Hello Jeff,

    Yes, If you see XCHG and XDSG high then the FETs are turned off. To get the gauge back to a normal state you will need to clear any safety status or permanent fail registers (which you have done), then you will need to need to send the "FET_EN" command.

    Regards,

    Adrian

  • 0 in reply to Adrian
    Prodigy 10 points

    Adrian,

    Thanks for the information. I'll try that this weekend and let you know how it works out. Were you able to tell anything from the files I sent, as to the cause of the fault? Why isn't there any data in the black box? 

    Regards, 

    Jeff

  • 0 in reply to Jeff Lenko
    TI__Mastermind 31526 points

    Hello Jeff,

    Unfortunately I can not definitively say what caused this fault from the file, I would have to see a log file the instant that the protection was tripped. There is no data in the black box since a permanate failure was not set.

    Regards,

    Adrian