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: Updating Firmware from 0.16 to 2.02

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

Hello,

I am updating my device (BQ34Z100-G1) FW from 0.16 to the new BQ34Z100-R2 FW (2.02) that is supposed to be compatible with all BQ34Z100 ICs. One issue I noticed is, that after updating, the voltage reading is drastically different.

Steps:

1. Default FW is 0.16, and I have the board calibrated

2. I program 2.02 to the IC and the memory in data flash is all reset

3. I use the same calibration data flash values (CC Gain, Voltage Divider, etc.) but now the voltage is drastically different than what is was

4. 2.02 has VoltScale, I check that even at '1' the voltage is drastically different than what it was on 0.16

5. I perform the calibration process (using the same CC Gain, CC Delta, CC Offset)

6. Voltage reading is now accurate, but Voltage Divider value in data flash updates itself from 9967 to ~33000

Is just updating VoltScale and Voltage Divider when moving to 2.02 the proper procedure for accurate voltage reading?

  • Updating the FW will overwrite the configuration. The best method to migrate the configuration from one FW to the other is to export the configuration as a gg file.

    After programming the new FW, program the ChemID and then import the gg file (hit Write All to make sure the data is written to the gauge).

  • In step 3 I reverted to the same configuration using the gg file. I can check again but my issue is that the same config/calibration, but different FW, gives me drastically different voltage readings from the gauge. I understand that the R2 accepts a larger range of voltages, so there is probably a different internal calculation happening when I update the FW. But I want to make sure this won't cause an issue and if I just need to recalibrate. 

  • Recalibration will fix this.