• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 63 subscribers
  • Views 781 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.

BQSTUDIO: Possible Bug found in logging via GPC Cycle tab- Log file does not overwrite, data lost

Kyle Trenholm89
Intellectual 285 points
Part Number: BQSTUDIO
Other Parts Discussed in Thread: BQ34110

Hi there,

I couldn't find a place to submit a bug report, so I guess maybe one of the TI people here can pass this along.

I think I've found a bug in bqStudio when logging in the GPC Cycle tab.  What I'm seeing is that when I start a manual GPC Cycle and begin logging, data will log as normal.  Cancelling the cycle does not stop the logging process.  I'm not sure if that is intended.

What I'm pretty sure is not intended is if I go to start another GPC Cycle after cancelling a prior cycle, I will be prompted to overwrite the existing log file.  I choose yes, however the file does not overwrite.  The log file remains as-is, and the new log data is not written anywhere.  Step by step to reproduce:

1)  Open BQStudio and connect to gauge (in my case bq34110).

2)  Enter the GPC Cycle window.  Select Manual Mode.

3)  Output directory is left default (C:\ti\BatteryManagementStudio\OutputFiles)

4)  Base File Name is left blank.  EDV0 is set to 2900 in my case.

5)  Start the GPC Cycle process and begin logging.  File name defaults to roomtemp_highrate.log.

6)  Cancel the GPC Cycle.  Data continues to log to file roomtemp_highrate.log after cancelling the cycle.

7)  Start GPC Cycle again, prompt to overwrite appears.  Select 'Yes' to overwrite.

8)  Data stops logging to roomtemp_highrate.log, but the file is not replaced and no new data is written. 

A workaround I've found is to simply log to a new file rather than overwrite the previous one.

I am running Windows 7 x64, bqStudio v1.3.54.1.  Let me know if there's any other system information I can provide that might help.

I just lost a discharge cycle log to this, hope you can reproduce so nobody else ends up like me!

  • 0
    TI__Mastermind 34775 points
    Hi Kyle,

    Thanks for bringing this to our attention. we will follow your step to reproduce the issue and get back to you with our findings.

    Have you tried updating to the latest version in bqStudio test? can you try and let us know if the problem exists in that version 1.3.80?
  • 0 in reply to Damian Lewis
    Intellectual 285 points

    Damian,

    I have confirmed this behavior is present in the test version 1.3.80

  • 0 in reply to Damian Lewis
    Intellectual 285 points

    Damian,

    I have more to pass along for v1.3.80:
    - In the GPC Cycle window, starting any log, regardless of which temperature is selected, will always preface the file name with roomtemp.
    - When starting a "High Temp" log, the messagebox that appears tells the user to set to room temperature (30 C).  EDIT: I think this one is a misunderstanding on my end, it looks like it wants me to begin logging and perform the charge at room temperature and the discharge at the high or low temperature.