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.

BQ34Z100-G1: Calibration of Custom made Fuel gauge circuit

Part Number: BQ34Z100-G1
Other Parts Discussed in Thread: EV2400, BQSTUDIO,

I don't have evaluation module of Fuel gauge and EV2400 for communicating gauge to BQ studio. I have made following circuit for operation. I am connecting Gauge via Arduino. Can you tell me exact calibration process for gauge through Arduino or any other microcontroller. 

  • Hi Meet,

    bqStudio and the EV2400 are required to program the chemID into the gg.csv file.  The EV2400 and bqStudio also allow you to log and quickly modify device parameters in a GUI environment.  Please perform calibration with bqStudio and the EV2400.

    Once your gauge is configured, you can export the entire firmware as a BQFS or just the dataflash settings as a DFFS file.  These files consist of I2C commands that the arduino may use to program the gauge in production.

    With respect to the schematic above, please not that the datasheet lists REGIN as a max of 4.5 V and also requires a 0.1 uF cap tied to ground near the pin.  Power supply recommendations are listed in section 9 of the datasheet.

    Also, with respect to the current sense portion of the schematic, please refer to the schematic as shown below:

    Sincerely,

    Bryan Kahler

  • Hi Bryan...

    Sorry to interrupt this conversation......

    So if you plan to use this chip in a commercial product and want to support different (unknown) batteries, then its not possible to calibrate the chip to the customers battery, unless you get the actual battery, connect it to EV2400 and bqStudio, and then send it back to the customer?

    Kind regards

    Jens

  • Hi Jens,

    If you have a host MCU in the system, multiple configurations could be created and stored in the device. However, these configurations would need to list specific batteries to use with the system. If you wanted to support 3 models of battery, a DFFS may be required for each. In this case, the host MCU would need to be able to unseal the gauge and seal the gauge with the key.

    Alternatively, different SKUs could be made for the product you ship where it is matched to each battery. In this case the gauge could then be sealed in the factory.

    Sincerely,
    Bryan Kahler
  • Hi Bryan,

    But...I might not know what kind of battery is installed (AGM/Gel/normal lead/acid) or which capacity. Isn't it possible to do the same in my MCU as you do in the ev-kit/software?

    Regards, 

    Jens

  • Hi Jens,

    Yes, in the scope described above, with the MCU programming a known golden file from a series of known golden files to the gauge.

    A golden file is created per device per cell. The golden file is already programmed with the proper battery profile and is learned to the cells that will be used.

    Any other scenario with unknown batteries would result in the customer having to following the engineering steps in creating the golden file for the device.

    Sincerely,
    Bryan Kahler
  • Thanks again Bryan.

    I think I'll have to study this a lot more before implementing it on my next prototype PCB!

    Are you bringing a demo of this at Electronica/Munich next month?

    Regards,

    Jens

  • Hi Jens,

    No, there will not be a demo of the bq34z100-g1 at the TI Booth at Electronica next month, but a variety of other interesting demos will be there.

    Sincerely,
    Bryan Kahler