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.

bq78PL114S12 Errata: .dat File Load Error

Other Parts Discussed in Thread: BQWIZARD, BQ78PL116, BQ78PL114

A problem with the .dat file load process of the bq78PL114S12 has recently been discovered.  A description and resolution is shown below:

bq78PL114S12 errata: .DAT FILE LOAD ERROR

Product Effected:

bq78PL114S12, FW5000.

Symptom:

The chemistry Information contained in the .dat file may not load correctly for cell packs with more than three series cells.  In particular, all of the information contained in an .aux file for cells four to twelve are not always initialized properly after the .dat file load.

Remedy:

In either the bqWizard or a custom application created with the API library, always follow this procedure:

1.                  Load the .dat file. 

a.      If using the bqWizard, use the Load Configuration File and Relearn command to load the .dat file.

b.      If using a custom application created with the API, do a Commit command after the file is loaded.

2.                  Wait at least two seconds.

3.                  Load the .dat file (again). 

a.      If using the bqWizard, use the Load Configuration File and Relearn command to load the .dat file.

b.      If using a custom application created with the API, do a Commit command after the file is loaded.

Comments:

This problem is fixed in the bq78PL116.

  • Hello Jim!

     

    • how can this problem be fixed in the bq78PL116, if this only recently has been discovered?
    • Is there a list of discovered problems of bq78pl114(s12) available?
    • Why is this information stashed away in this forum where the people start to search, if  time has been wasted?

     

     

     

     

  • I would prefer a list instead of searching in the forums AFTER the problem causes problem.

    We did waste time with this bug .. we found the workaround before this post but would have been better if we knew right from the beginning ...