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.

BQ27531-G1: commands wait

Part Number: BQ27531-G1

Is it right that Read/Write and ReadOnly standard command will not issue more than two-command per sec?

Is it right that we need wait to 66us for control subcommand?

Do you have any wait rool for reading or writing DateFlash?

  • See my comments below.

    a) As we mentioned in the TRM, for read-write standard command, a minimum of 2 seconds is required to get the result updated. For read-only standard commands, there is no waiting time required, but the host must not issue any standard command more than two times per second.

    b) A 66μs bus-free waiting time must be inserted between all i2c packets.

    c) I think we already share all the information on the waiting time in the TRM.

    And6

  • Is the following correct?
    ---
    When a pulse is detected by SOC_INT, we need to check SOC1/Sysdown, Charge Fault and SOC.
    We can continuous read Flags() of Standard command  and Chrgr_Fault_Reg9() of Charger Date Commands by the a little wait time.
    But We need to issue StateOfCharege() of Standard command after 1 second.
    Therefore we take more than 1 second for checking SOC_INT pulse.
    ---

    If yes, in occasion SOC_INT pulse continuous occurs within 1 second,we cannot theses process.
    Is there any good way?

  • Unfortunately, I don't see there is any better implementation since the requirement that no-more than 2 standard commands per second must be followed.

    Andy