• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 62 subscribers
  • Views 864 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

BQ40Z60: Temp Range Data Item (address / command ID)

Rob Coker
Intellectual 390 points
Part Number: BQ40Z60
Other Parts Discussed in Thread: BQSTUDIO, BQ40Z50,

The Temp Range register shows up in bqStudio above the charging status.  However, I do not see how to access this data from the Technical Reference Manual (SLUUA04D).  The only place I saw it mentioned was in the flash memory for fault storage.  There is no place to get the current value.

What is the command ID for this data?  The mapping is shown in bqStudio.

  • 0
    TI__Guru* 76230 points
    There is no command for it. You can just read the actual registers in data flash to know what values they are
    thanks
    Onyx
  • 0 in reply to Onyx Ahiakwo
    Intellectual 390 points
    Onxy, thanks for the help.

    I think perhaps we are talking past each other.

    Section 3.25.3 of the TRM discusses the device status data that is saved in a permanent fault condition. There are a large number of parameters that are saved to flash when that happens. Those are historic/log values - the state of the system when the fault occurred. But every one of those items (Safety alert and status, PF alert and status, operation status, charging status ...) is available as current data (by ManufacturerAccess) during normal operation except for Temp Range. Further, on the bqStudio screen in the register bits section, it shows current value of Temp Range (NOT Temp Range when a permanent fault occurred). The Register Bits section is not flash data/configuration, but current data. There should be a listing in section 11 for the current value of Temp Range. bqStudio is obviously using it. That's what I'm trying to get - not the historic data when a permanent fault occurred as documented in 3.25.3.

    This is doubly confusing because section 2.4 (and a few others) treat the bits of the Temp Range field (like UT, STL, RT ...) as members of the ChargingStatus parameter. However, ChargingStatus as documented in 11.1.41 does not include the Temp Range fields. No place does (according to the TRM) except somehow a snapshot of the current data is saved when there is a fault.

    Is section 3.25.2.17 (flash address 0x4000 + 1110) the current Temp Range data? It seems according to the documentation that it is a snapshot of the Temp Range data when a permanent fault occurs. But maybe I'm misinterpreting it.
  • 0 in reply to Rob Coker
    Intellectual 390 points

    I did a little more investigation.  The BQ40Z50 (sluubc1c) does have the temperature flags (UT, LT, STL ...) as part of its charging status message (13.1.41, Mfg Acess 0x55).  It looks like certain aspects of the documentation were shared between the TRMs for the BQ40Z50 & 60.  That may explain why section 2.4 and others refer to temp range sub-fields being part of the ChargingStatus.  However, those fields are not part of the BQ40Z60 Charging Status message as defined in 11.1.41 of the BQ40Z60 TRM (sluua04d), so the documentation is in error for the BQ40Z60. 

    I just want to know where the BQ40Z60 has this data since it is not part of the Charging Status like it is in the BQ40Z50.

  • 0 in reply to Rob Coker
    Intellectual 390 points
    The documentation is in error for the BQ40Z60, section 11.1.41 Manufacturing Access() 0x0055 ChargingStatus of the TRM (sluua04d). It is not a 3 byte field, but a 4 byte field. This was discovered by looking at the bqStudio config file for the BQ40Z60. The low byte of the 4 byte field (the TRM only includes the high 3 bytes) is the Temp Range. This further explains why section 2.4 of the TRM refer to these bits as being part of the ChargingStatus() field. They are. But the ChargingStatus field documentation doesn't include them.

    So, to answer my original question, Temp Range is included in Manufacturing Access 0x0055 as the 4th byte.