• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 64 subscribers
  • Views 528 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.

Original question:

BQ34110: Bq34110 Auto Sealed

BQ34110: Sealed, unable to unseal

Aditya Sehgal
Prodigy 50 points
Part Number: BQ34110
Other Parts Discussed in Thread: BQSTUDIO, EV2400

Hi, I am trying to calibrate the device using a micro controller over I2C, after reading back operationstatus(), SEC0 and SEC1 are both set which means the device is sealed, which I did not tell it to do ever. Now I am facing troubles unsealing it back... I am using an arduino as of now to work with the device and am using the following script:

Wire.beginTransmission(BQ34110);
    Wire.write(0x00);
    Wire.write(0x04);
    Wire.write(0x14);
    Wire.endTransmission();
    Wire.beginTransmission(BQ34110);
    Wire.write(0x00);
    Wire.write(0x36);
    Wire.write(0x72);
    Wire.endTransmission();
even after this, the device remains sealed. is there anything I am doing wrong? I got the instruction for this on this forum:
Thank you!!
  • 0
    TI__Guru** 105770 points

    Hello Aditya,

    I'm not sure of the function call you are using and how it communicates with the gauge. We usually recommend sending the commands on the EV2400 with bqStudio to see the communication protocol and make sure it is the same as what you are trying to implement.

    As the other post mentioned, the gauge should not be sealed from opening. Is it possible the gauge was sealed by accident?

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Prodigy 50 points

    Hi Wyatt,

    Thank you for getting back!

    I understand TI recommending EV2400, however, my workplace does not own one yet and does not seem to have any plans on purchasing one which is why I am using the MCU.

    As for the gauge, I have not made any active attempts to seal it just yet so I am not sure what happened here... I feel stumped right now and would appreciate any and all help :)

    Thank you!

  • 0 in reply to Aditya Sehgal
    TI__Guru** 105770 points

    Hello Aditya,

    Then I would check your I2C lines with a logic analyzer or scope to make sure the commands are being sent without a pause.

    Do you have any other gauges you can test to see if they are also sealed?

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Prodigy 50 points

    Hello Wyatt,

    it appears the commands are being sent without a pause...

    Would there be any way you would recommend to unseal the device using a microcontroller?

    Thanks!

  • 0 in reply to Aditya Sehgal
    TI__Guru 52115 points
    I guess the easiest way for you now is to replace the device with a new one so that you can move on with the calibration.
    In addition, we will check if we can share the sequence that you can use to unseal the device using your microcontroller.
    Andy
  • 0 in reply to Andy Liu (BMS)
    Prodigy 50 points

    Hi Andy,

    Thank you for getting back. While I wait for a new device, I have decided to move onto trying with a new microcontroller. Hopefully, that may help.

    Also Please let me know if you would be able to share the sequence with me to unseal the device.

    I also noticed that no matter what I requested the device to do (read voltage, device type, opertation status, or any other function), it would respond with "0xFEFF". Is this some sort of an error code? I was not able to find anything about this in the documentation.

    Thanks!

  • 0 in reply to Aditya Sehgal
    TI__Guru** 105770 points

    Hello Aditya,

    I believe once you try with a new device the issue will be resolved, it is possible the gauge was damaged somehow and become unresponsive.

    The device is probably damaged and that is why you are reading those values, are you getting an ACK when communicating with the gauge?

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Prodigy 50 points

    Hello Wyatt,

    Since I have decided to switch out my MCU for an STM32, Seems like I am able to communicate with the device, I do get an ACK back considering my I2C functions are returning "HAL_OK". One issue I am still facing is reading values off the registers.. I am just using a combination of HAL_I2C_Master_Transmit and HAL_I2C_Master_Receive... Would there be anything you could recommend that I may try to properly communicate with the chip?

    Cheers!

  • 0 in reply to Aditya Sehgal
    TI__Guru** 105770 points

    Hello Aditya,

    I am not familiar with the those functions or the library they are from. We always recommend using a scope or logic analyzer to compare your communication with the standard the EV2400 uses with bqStudio, if you cannot obtain a EV2400, can you capture the wave forms and share them here? You can also compare your results with other posts on E2E that show I2C communication wave forms.

    I would recommend making sure your pull-up resistors are the correct value. If you can share the scope or logic analyzer images I may be able to provide better feedback.

    Sincerely,

    Wyatt Keller