• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 64 subscribers
  • Views 511 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

bqEVSW 0.9.88 bug

Dan-o
Intellectual 895 points
Other Parts Discussed in Thread: BQEVSW, BQ27510-G2

I'm using bqEVSW with bq27510-G2. It will not allow you to write a negative value for "CC Offset" in the Calibration part of Data RAM. It pops up an error message saying the value must be between 0 - 32767. There are other ways to do it I know, just pointing out a bug hopefully an employee reads this.

  • 0
    TI__Genius 14985 points

    If EVSW won't let you type in certain values, you can defeat it by exporting the gg file, editing it in Notepad, then importing it and clicking Write All.

  • 0 in reply to dMax
    Intellectual 895 points

    that doesn't seem to work either. it imports the negative value for CC offset but when I write all it reverts back to the default value (-0.756).

  • 0 in reply to Dan-o
    TI__Genius 14985 points

    CC Offset is actually autocalibrated by the IC periodically so you don't need to update this value and it doesn't matter what you try to put in it since it will get overwritten during autocal.

    Sorry I didn't notice which parameter you were talking about in the original post!

  • 0 in reply to dMax
    Intellectual 895 points

    ok i guess I'll leave it alone then! I have gone through another failed learning cycle now :( I think I need to try determining the chemistry ID. I can't install mathcad but I would like to use the shorter method from sluc1388aa. Can a TI employee look at the logs and calculate an ID for me? Would logged data from the failed learning cycle work? This data has higher discharge rate (C/5) and the sluc1388 calls for (C/10)

  • 0 in reply to Dan-o
    Intellectual 450 points

    There's another post related to this "invalid values for calibration data". It's a matter of changing the Regional Settings:

    http://e2e.ti.com/support/power_management/battery_management/f/180/t/87637.aspx