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.

"Testing Boris Fix" Error During AutoCycle

Other Parts Discussed in Thread: BQEVSW, BQ20Z65-R1

Hello,

I’m trying to AutoCycle my batteries.  I found an interesting error where during an autocycle, at the completion of every scan a “Testing Boris Fix” error pops up on the screen.  This locks up the program until the user clicks “OK” and stops the computer from performing any more scans, which effectively stops the autocycle from working since it seems to rely on the scan information.  This error only occurs during Charge / Discharge, not during rest.

I’m using the bqEVSW bq20z65-R1 v1.05, is there any chance of getting this cleared up and a new version of the program released? It would be very helpful if I could cycle these batteries.

Thanks,

Nick

  • This is fixed in EVSW v0.9.65. Please download the latest EVSW from the product webpage.

     

     

  • Hi Jackie,

    There seems to be two issues.  The first is that while v0.9.65 is the newest, the website still has v0.9.64 for download.  I went to http://focus.ti.com/docs/toolsw/folders/print/bq20z65-r1_bqevsw-sw.html and re-downloaded the software but it was v0.9.64.

    Second, I have already recieved v0.9.65 through someone else but the autocycle still has problems.

    As far as I can tell from my own testing and debugging, here are the issues:

    I’ve done some testing with the newest version of the bqEVSW (9.65) and there is one problem I can see with the AutoCycle, it won’t set the correct pin high to start the charger.

    According to the documentation,

    “The EV2300 I2C-SDA (or HDQ) terminal should be connected to a transistor/FET switch or relay which will connect your charger to the battery pack when the signal is HIGH (+5V). The charger must be disconnected when the I2C-SDA (or HDQ) terminal goes LOW (0V).”

    When going to AutoCycle -> 2 Pins -> Enable Charger (HDQ = 5V) the charger will begin to charge.  Similarly when I click again it will go low and stop charging.

    When going to AutoCycle -> 2 Pins -> Enable Load (I2C VOUT = 5V) the load will begin to discharge.  Similarly when I click again it will go low and stop discharging.

    However, during the Auto-AutoCycle, the charger will never start.  The AutoCycle will turn on the I2C Vout so that the load is enabled, the batteries will drain properly, the AutoCycle will turn them off and rest properly, but at that point it breaks.  Similarly, if you begin the AutoCycle with a Rest then Charge or just a Charge, the charge will never begin. 

    It appears to me that there is just a missing command at the beginning of the charge cycle to tell the HDQ line to go high.  I have tested it with a multimeter and have confirmed that in fact it is not going high.  Personally I’m using the HDQ line, however for reference the I2C SDA line also does not go high.

     

  • Hi Nicholas,

    Regarding the Charge cycle you are probably missing the pull-up for the SDA/HDQ line. AutoCycleHlp.txt says:

    The I2C-SDA (or HDQ) pin must be pulled up externally.   Max pullup voltage = 6V   Recommended sink current < 5mA   Max current: Current that will cause damage = 40mA (Linear regulator will begin to drop out)  

    Regards,

    Peter