Skip to main content

2.1 BB Not Communicating

O
Written by Ollie Wells

Batteries will go into Hibernate if they are stuck in Bootloader for ~15 minutes. The BBs will need to be woken up before they can be recovered from Bootloader.

Symptoms:

  • Loss of communication with one or more Battery Blocks.

Troubleshooting Steps:

  1. Check that the Trunk Harness is connected properly.

  2. Follow any instructions provided within the Install App.

  3. Check Grafana to ascertain if the BBs have ever communicated.

    • If Never Communicated:

      • Attempt to wake from Hibernate with a power cycle (see article 99.3 Power Cycle Lunar Battery Block).

      • Attempt to wake from Hibernate through Gridshare: Go to the Gridshare devices page for the INV → Click Remote Actions tab → Select "Wake DCDCs from Hibernate" and click Submit.

      • Attempt to wake from Hibernate (Remote FW): TSE and T3 team can remotely wake the BB using SYSGUI. If communications are still not established, push a FW update. If communications remain absent, unplug Bridge low voltage comms, wait 30 seconds, then power cycle the BB.

      • If still no comms, escalation is required.

    • If Previously Communicated:

      • Check the DCDC Fault Matrix on Grafana to identify any raised faults.

      • If the BB disappeared after a FW upgrade, there is a high probability it is stuck in the Bootloader. This requires escalation; ping the FW team for support.

Did this answer your question?