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

BQ34Z100-G1: Alert pin not asserting after initial

Jeffrey Wright
Expert 2875 points
Part Number: BQ34Z100-G1

Hello;

I've configured the Alert pin to assert on several events, including FC. But when the FC flag is raised, no interrupt occurs. However, if the capacity is low, I get an initial interrupt during device initialization, but thereafter, no ISR fires, despite the FC flag (as well as any others) being asserted. It seems as if the gauge requires the host to reset these flags, just as on the 34z110 and 78350 gauges.

Will you please confirm that the gauge does NOT require an Alert reset command, and if not, why is it not asserting the Alert pin when FC is asserted?

AlertCfg.docx

  • 0
    TI__Mastermind 19195 points

    Hi Jeffrey,

    Could you share a log of the test so we can see the registers along with the .gg

    Thanks,

  • 0 in reply to Nick Brylski
    Expert 2875 points

    I cannot run my application and studio concurrently, and so these files are exported when the application is paused. Note again that the FC bit is set, but it does not assert the Alert pin. That makes me suspicious that the 34z100  requires a reset of the ALert, just as its sister gauge the 34110.Studio.gg.csv

    Fullscreen Gauge.log Download 
    Wed Jan 06 09:17:48 EST 2021

Device Version Info = 0100_0_16
BQZ Device Name = bq34z100G1
BQZ Firmware Version = 0_16


Sample,DateTime,ElapsedTime,Control,CtrlStatus,StateofCharge,MaxError,RemCap,FullChgCap,Voltage,Current,AvgCurrent,Temperature,AverageTimeToEmpty,AverageTimeToFull,AvailableEnergy,AveragePower,InternalTemperature,CycleCnt,StateofHealth,ChargeVoltage,ChargeCurrent,PackConfig,Flags,Flags B,GridNumber,LearnedStatus,DoDatEOC,Qstart,TrueRC,TrueFCC,StateTime,DOD0PassedQ,DOD0Time,DOD0,QmaxDOD0,QmaxPassedQ,QmaxTime,LogRowTime(ms),LogStatus
1,2021-01-06 09:17:53,4.000,0x0016,0x0004,100,100,23,23,25096,-2318,-2314,35.2,1,65535,7,-727,7.0,0,1,28800,1709,0xF8E7,0x0217,0x0400,12,0,16081,23,277,23,107,-318,2,16384,0,-319,2,934,SUCCESS
2,2021-01-06 09:17:59,10.962,0x0016,0x0004,100,100,23,23,25096,-2317,-2315,35.2,1,65535,7,-727,7.0,0,1,28800,1709,0xF8E7,0x0217,0x0400,12,0,16081,23,272,23,114,-313,2,16384,0,-314,2,927,SUCCESS
3,2021-01-06 09:18:02,13.566,0x0016,0x0004,100,100,23,23,25096,-2317,-2315,35.2,1,65535,7,-727,7.0,0,1,28800,1709,0xF8E7,0x0217,0x0400,12,0,16081,23,271,23,116,-312,2,16384,0,-313,2,935,SUCCESS
4,2021-01-06 09:18:05,16.144,0x0016,0x0004,100,100,23,23,25096,-2318,-2316,35.2,1,65535,7,-727,7.0,0,1,28800,1709,0xF8E7,0x0217,0x0400,12,0,16081,23,269,23,119,-310,2,16384,0,-311,2,933,SUCCESS
5,2021-01-06 09:18:09,20.002,0x0016,0x0004,100,100,23,23,25096,-2317,-2316,35.2,1,65535,7,-726,7.0,0,1,28800,1709,0xF8E7,0x0217,0x0400,12,0,16081,23,266,23,123,-307,2,16384,0,-308,2,936,SUCCESS
6,2021-01-06 09:18:13,24.003,0x0016,0x0004,100,100,23,23,25096,-2315,-2316,35.2,1,65535,7,-727,7.0,0,1,28800,1709,0xF8E7,0x0217,0x0400,12,0,16081,23,264,23,127,-305,2,16384,0,-306,2,964,SUCCESS
7,2021-01-06 09:18:17,28.004,0x0016,0x0004,100,100,23,23,25096,-2317,-2316,35.2,1,65535,7,-726,7.0,0,1,28800,1709,0xF8E7,0x0217,0x0400,12,0,16081,23,261,23,131,-302,2,16384,0,-303,2,918,SUCCESS

  • 0 in reply to Jeffrey Wright
    TI__Mastermind 19195 points

    Hi Jeffrey,

    The .gg looks ok. There is no alert reset command, the alert pin is asserted by driving low. It will be asserted until the flags are cleared.

    Best regards,

  • 0 in reply to Nick Brylski
    Expert 2875 points

    Then why is the FC flag not triggering the Alert pint? THat's what the TRM says it should do.  Again - I've configured the Alert pin to assert on several events, including FC. But when the FC flag is raised, no interrupt occurs. What is the reason for this?

  • 0 in reply to Jeffrey Wright
    TI__Mastermind 19195 points

    Hi Jeffrey,

    I will let our FW team know about this issue, this issue was meant to be resolved with G1 version of device.

    Thanks,