hy4145 tr en v肇慶市科通合易通訊

HY4145

TechnicalReference

TableofContents

1.INTRODUCTION 5

SCOPE 5

AUDIENCE 5

NOTATIONALCONVENTIONS 5

2.DETAILEDDESCRIPTION 6

SECURITY 6

AccessMode 6

TABLE1.DATAFLASHACCESSMODE 6

2.1.2.SealingandUnsealingDataFlashMemory 6

DATAFLASHACCESS 8

AccessingDataFlashMemory 8

AccessingManufacturerInformationBlocks 9

POWERMODES 11

NormalMode 11

SleepMode 12

FullSleepMode 12

HibernateMode 13

ResetMode 13

PROTECTION 15

JEITATemperatureRanges 15

1stLevelProtectionFeatures 16

CellOvervoltageandCellUndervoltage 16

ChargeandDischargeOvercurrent 18

OverTemperature 21

DischargeInhibit 23

ChargeInhibit 24

ChargeSuspend 25

BATTERYGAUGE 27

UpdateofStateOfCharge 27

UpdateofFullCapacity 27

UpdateofResistance 27

CHARGECONTROL 28

ChargeTermination 28

CALIBRATION 29

CalibrationProcess 29

2.7.1.VoltageGainCalibration(VoltageGain) 30

?2012HYCONTechnologyCorp

Confidential

April,2012

page2

HY4145

TechnicalReference

InternalTemperatureGainCalibration 31

ExternalTemperatureGainCalibration 32

CurrentGainCalibration(CCGain) 33

CurrentOffsetCalibration(CCOffset) 33

CoulombCountCalibration(CCCount) 34

CoulombCountCalibrationTime(CCTime) 35

3.REVISIONRECORD 37

.

?2012HYCONTechnologyCorp

Confidential

April,2012

page3

HY4145

TechnicalReference

?2012HYCONTechnologyCorp

Confidential

April,2012

page4

Attention：

HYCONTechnologyCorp.reservestherighttochangethecontentofthisdatasheetwithoutfurthernotice.Formostup-to-dateinformation,pleaseconstantlyvisitourwebsite:

.

HYCONTechnologyCorp.isnotresponsibleforproblemscausedbyfiguresorapplicationcircuitsnarratedhereinwhoserelatedindustrialpropertiesbelongtothirdparties.

SpecificationsofanyHYCONTechnologyCorp.productsdetailedorcontainedhereinstipulatetheperformance,characteristics,andfunctionsofthespecifiedproductsintheindependentstate.Wedoesnotguaranteeoftheperformance,characteristics,andfunctionsofthespecifiedproductsasplacedinthecustomer’sproductsorequipment.Constantandsufficientverificationandevaluationishighlyadvised.

Pleasenotetheoperatingconditionsofinputvoltage,outputvoltageandloadcurrentandensuretheICinternalpowerconsumptiondoesnotexceedthatofpackagetolerance.HYCONTechnologyCorp.assumesnoresponsibilityforequipmentfailuresthatresultedfromusingproductsatvaluesthatexceed,evenmomentarily,ratedvalueslistedinproductsspecificationsofHYCONproductsspecifiedherein.

Notwithstandingthisproducthasbuilt-inESDprotectioncircuit,pleasedonotexertexcessivestaticelectricitytoprotectioncircuit.

Productsspecifiedorcontainedhereincanno.tbeemployedinapplicationswhichrequireextremelyhighlevelsofreliability,suchasdeviceorequipmentaffectingthehumanbody,health/medical

equipments,securitysystems,oranyapparatusinstalledinaircraftsandothervehicles.

DespitethefactthatHYCONTechnologyCorp.endeavorstoenhanceproductqualityaswellasreliabilityineverypossibleway,failureormalfunctionofsemiconductorproductsmayhappen.Hence,usersarestronglyrecommendedtocomplywithsafetydesignincludingredundancyandfire-precautionequipmentstopreventanyaccidentsandfiresthatmayfollow.

Useoftheinformationdescribedhereinforotherpurposesand/orreproductionorcopyingwithoutthepermissionofHYCONTechnologyCorp.isstrictlyprohibited.

HY4145

TechnicalReference

1.Introduction

ThisdocumentpresentsthemodulesandperipheralsofHY4145tobuildacompletebatterygauge

withprotectionsolution.

1.1.Scope

ThisdocumentdescribsthedetailsofoperationsinmodulesandaboutperipheralsofHY4145.Theelectricalandmechanicalspecificationsarecoveredbyotherdocuments(refertotheHY4145

datasheet).

1.2.Audience

Theaudienceforthisdocumentincludes:

BatterymanufacturersDesignersofdevicedrivers

DesignersofpowermanagementsystemsusingbatteryalongwithHY4145

1.3.NotationalConventions

Followingnotationisused,ifI2CcommandandDataFlashvaluesarementionedwithinatextblock:

I2CcommandsandDataFlashvaluesaresetinitalic,e.g.:Voltage()

I2CbitsandDataFlashbitsarecapitalized,setinitalicandenclosedwithsquarebrackets,

.

e.g.:[SS]

ThereferenceformatforI2Ccommandsis:

CMD:CommandName(),or

CMD:CommandName():AccessName().[BIT]

ThereferenceformatforDataFlashvaluesis:

DF:ClassName:SubclassName:ValueName(),or

DF:ClassName:SubclassName:ValueName().[BIT]

?2012HYCONTechnologyCorp

Confidential

April,2012

page5

HY4145

TechnicalReference

2.DetailedDescription

2.1.Security

2.1.1.AccessMode

TheHY4145providesthreesecuritymodes(FULLACCESS,UNSEALED,andSEALED)thatcontrolDataFlashaccesspermissionsasspecifiedinTable1.DataFlashlocations,specifiedinTable5,are

accessibletouser.Manufacturerinformationreferstothethreereserved32–byteblocks.

Table1.DataFlashAccessMode

OnlytheFULLACCESSmodeallowsthedevicetowritetheaccess–modetransitionkeys:Full

AccessKeyandUnsealKey.

2.1.2.SealingandUnsealingDataFlashM.emory

TheHY4145implementsakey–accessschemetotransitionbetweenSEALED,UNSEALED,andFULLACCESSmodes.EachtransitionrequiresthatauniquesetoftwokeysbesenttothedeviceviatheControl()subcommand.Thekeysmustbesentconsecutively,withnootherdatabeingwritten

totheControl()subcommandregisterinbetween.

WheninSEALEDmode,the[SS]bitissetinControlStatus(),butwhentheunsealkeysarecorrectly

receivedbythedevice,the[SS]bitiscleared.WhentheFULLACCESSkeysarecorrectlyreceivedbythedevice,the[FAS]bitisclearedinControlStatus().

TheUNSEALKEYisstoredatUnsealKey0()andUnsealKey1(),theFULLACCESSkeystoredatFullAccessKey0()andFullAccessKey1()ina2–word(4–byte)formatforeachinDataFlash,andthesekeyscanonlybeupdatedinFULLACCESSmode.TheorderofthebytesenteredthroughtheControl()subcommandisthereverseofwhatisreadfromthedevicethroughthecommunicationinterface.Forexample,iftheUnsealKeyis0x56781234,UnsealKey0()is0x1234andUnsealKey1()is0x5678.TheControl()subcommandshouldsupply0x3412and0x7856inseriestounsealthe

device.

RelatedVariables:

DF:Security:Codes:UnsealKey0()

DF:Security:Codes:UnsealKey1()

?2012HYCONTechnologyCorp

Confidential

April,2012

page6

FULLACCESS

R/W

R/W

R/W

UNSEALEDACCESS

R/W

R/W

R

SEALEDACCESS

NONE

R(A);R/W(B,C)

NONE

SECURITYMODE DATAFLASHACCESS MANUFACTURERINFORMATION KEYACCESS

HY4145

TechnicalReference

DF:Security:Codes:FullAccessKey0()

DF:Security:Codes:FullAccessKey1()CMD:ControlStatus().[SS],[FAS]

.

?2012HYCONTechnologyCorp

Confidential

April,2012

page7

HY4145

TechnicalReference

2.2.DataFlashAccess

2.2.1.AccessingDataFlashMemory

InHY4145,DataFlashisanon–volatilememorythatcontainsinitializationdefaultvalues,batterystatus,calibrationinformation,configurationinformation,andapplicationinformation.TheDataFlashcanbeaccessinseveraldifferentways,dependingonwhatmodethedeviceisoperatinginandwhatdataisbeingaccessed.

MostDataFlashlocationsareonlyaccessibleinUNSEALEDmodeandFULLACCESSmodebyuseofthedeviceevaluationsoftwareorDataFlashblocktransfers.Theselocationsshouldbeoptimizedduringthedevelopmentandmanufactureprocesses.Onceestablished,theselocationsgenerallyremainunchangedduringend–equipmentoperationbyusers.Then,thesettingintheDataFlashcan

betreatedasagoldenimageandappliedonmultiplebatterypacks.

ToaccessDataFlashlocationsindividually,theblockcontainingthedesiredDataFlashlocation(s)mustbetransferredtothecommandspace,BlockData(),wheretheycanbereadtothesystemor

chargeddirectly.Thisisaccomplishedby:

Sendingtheset–upcommandBlockDataControl()(0x61)withthe0x00.

TheDataFlashClass()(0x3e)comma.ndshouldbeusedtosetDataFlashsubclass(CLASS).

TheDataFlashBlock()(0x3f)commandshouldbeusedtodesignatewhich32–byteDataFlashblockthelocationsresidein.

1.

2.

3.

4.

Upto32bytesofdatasetcanbereaddirectlyfromtheBlockData()(0x40…0x5f)command

space.

5.

Desireddatasetexternallyshouldbealtered,thenrewrittenbacktoBlockData()command

space.

6.

Finally,thedatasetintheBlockData()commandspaceistransferredtoDataFlash,oncethecorrectchecksumforthewholeBlockData()commandspaceiswrittenintoBlockDataCheckSum()(0x60).Onlywhenthechecksumisreceivedandverifiedbythe

device,thedatasetisactuallywrittenintoDataFlash.

7.

Afterthedatasettransferisfinished,themodifieddatasetinspecificDataFlashlocations

willbereturnedtoBlockData()commandspacefordoublecheckbyhost.

Specificmemorylocation(s)inDataFlashcanbeidentifiediftheircorrespondingOffsets,specifiedinTable5,areusedtoindexintothecommandspace,BlockData().Occasionally,aDataFlashCLASSislargerthan32byte.Inthiscase,aspecificmemorylocationisgivenby:0x40(32)+Offsetmodulo

32.

?2012HYCONTechnologyCorp

Confidential

April,2012

page8

HY4145

TechnicalReference

Readingandwritingdatasetsinasubclassareablockoperationupto32bytesinlengthintothe

BlockData()commandspace.If,duringawrite,thelengthexceedsthemaximumsizeofablock,thentheextradatasetisignored.

Noneofthedatasetwrittenintomemoryisbounded,andanydatasetisnotrejectedbythedevice.WritinganincorrectvaluetoDataFlashlocationmayresultinhardwarefailureduetofirmwareprograminterpretationoftheinvaliddata.Thewrittendatasetisstoredinvolatilememory,soa

Power–On–Resetdoesresolvethefault.

RelatedVariables:

CMD:ControlStatus().[SS],[FAS]CMD:BlockDataControl()

CMD:DataFlashClass()CMD:DataFlashBlock()CMD:BlockData()

CMD:BlockDataCheckSum()

2.2.2.AccessingManufacturerInformationBlocks

TheHY4145contains96bytesofuserprogrammableDataFlashstorage:ManufacturerInfoBlockA,ManufacturerInfoBlockB,ManufacturerInfo.BlockC.Themethodforaccessingthesememory

locationsisslightlydifferent,dependingonwhetherthedeviceisinFULLACCESS,UNSEALED,orSEALEDmode.

WheninUNSEALEDmodeandFULLACCESSmode,andwhen0x00hasbeenwrittentoBlockDataControl(),accessingtheManufacturerInfoBlocksisidenticaltoaccessinggeneralDataFlashlocations.First,aDataFlashClass()commandsetsthesubclass.TheDataFlashBlock()commanddesignatestheblocknumberoftheDataFlashSubclass.TheBlockData()commandspacecontainthereferenceddatasetintheDataFlashblock.AchecksumisexpectedtobereceivedbyBlockDataChecksum()beforeprogrammingthedatasetintotheDataFlashmemory.Ifthechecksumisreceivedandverified,thedatasetinBlockData()commandspaceisactuallywritten

intotheDataFlashmemory.

WheninSEALEDmode,DataFlashisnolongeravailableinthemannerusedinUNSEALEDmode.

AccessingtoManufacturerInfoBlocksisaccomplishedby:

1.

SendingtheDataFlashBlock()(0x3f)command.TheDataFlashBlock()(0x3f)commandshouldbeusedtodesignatewhich32–byteManufacturerInfoBlockthelocationsresidein.Issuinga0x01,0x02,or0x03withDataFlashBlock()causesthecorrespondingManufacturer

InfoBlockA,B,orCrespectively.

?2012HYCONTechnologyCorp

Confidential

April,2012

page9

HY4145

TechnicalReference

2.

Upto32bytesofdatasetcanbereaddirectlyfromtheBlockData()(0x40…0x5f)command

space.

3.

Desireddatasetexternallyshouldbealtered,thenrewrittenbacktoBlockData()command

space.

4.

Finally,thedatasetintheBlockData()commandspaceistransferredtothedesignedManufacturerInfoBlock,oncethecorrectchecksumforthewholeBlockData()commandspaceiswrittenintoBlockDataCheckSum()(0x60).Onlywhenthechecksumisreceivedandverifiedbythedevice,thedatasetisactuallywrittenintothedesignedManufacturerInfo

Block.

5.

Afterthedatasettransferisfinished,themodifieddatasetinthedesignedManufacturerInfo

BlockwillbereturnedtoBlockData()commandspacefordoublecheckbyhost.

WheninUNSEALEDmode,ManufacturerInfoBlockscanbeaccessedbythesamemethodinSEALEDmodeiftheBlockDataControl()issettobe0x01.NotethatManufacturerInfoBlockAis

read–onlywheninSEALEDmode.

RelatedVariables:

DF:ManufactureInfo:BlockA().[0–31]

DF:ManufactureInfo:BlockB().[0–3.1]DF:ManufactureInfo:BlockC().[0–31]CMD:ControlStatus().[SS],[FAS]CMD:BlockDataControl()

CMD:DataFlashClass()CMD:DataFlashBlock()CMD:BlockData()

CMD:BlockDataCheckSum()

?2012HYCONTechnologyCorp

Confidential

April,2012

page10

HY4145

TechnicalReference

2.3.PowerModes

TheHY4145hasfourpowermodes:NORMAL,SLEEP,FULLSLEEP,andHIBERNATE.InNORMALmode,thedeviceisfullypoweredandexecutesanyallowabletask.Otherwise,thedeviceoperatesinotherpowersavingmodes,ifthebatteryvoltageisabovethePower–On–Reset(POR)threshold

voltage.Thepowermodediagramispresentedasbelow.

EntrytoPORmode.

EntrytoNORMALmode.

Anycommunicationcommand,OR

EntrytoNORMALmode.Communicationcommandreceived,AND

Command

issued

Wak-upfromHIBERNA

Communicationactivity,

.

Nocommandreceived

EntrytoHIBERNATEmode.Cellrelaxed,AND

,if

[HIBERNATE]=1

OR

Cellrelaxed,AND

EntrytoSLEEP/FULLSLEEPmode.[HIBERNATE]=0,OR

EntrytoHIBERNATEmode.

[HIBERNATE]=1,OR

Figure1.PowerModeDiagram

2.3.1.NormalMode

TheHY4145isfullypowered,fullyfunctioned,andexecutesanyallowabletasksinthismode.It

performsmeasurements,calculationsanddatasetupdates.Datasetisaccessiblethroughthe

?2012HYCONTechnologyCorp

Confidential

April,2012

page11

TEmode.AND

Entryto[FULL

EntrytoNORMALmode.

Anycommunicationcommand,OR

,OR

EntrytoSLEEPmode.

FULLSLEEPmode. EntrytoFULLSLEEPmode.LEEP]=1 expired

LowpowerSLEEPmode.Batterygauginganddatasetupdatedevery20seconds

LowpowerSLEEPmode.Batterygauginganddatasetupdatedevery20seconds

counted

down

Batterygauginganddatasetupdatedevery20seconds

Allfunctionsdisabled,exceptSEpin

Batterygauginganddatasetupdatedevery1second

HY4145

TechnicalReference

2–Wire(I2C)communicationinterface.Thedevicestaysinthismodeuntilanotherpowermode

forcingitout.

2.3.2.SleepMode

TheHY4145isfullypowered,andperformsmeasurements,calculationsanddatasetupdatesina20

secondsextendedinterval.Thedeviceoperatesinareducedpowermode.

TheSLEEPmodeisenteredautomaticallyfromNORMALmode,if(1)thefeatureisenabledwith[SLEEP]=1,AND(2)theAverageCurrent()valueisbelowtheconfigurableSleepCurrent()

threshold.

TheHY4145exitsthismodeandentersNORMALmode,if(1)anycommunicationcommandisreceived,OR(2)theAverageCurrent()valuerisesabovetheconfigurableSleepCurrent()threshold,

OR(2)thecurrentabovetheconfigurableWakeCurrentThreshold()valueacrossRSENSEisdetected.

RelatedVariables:

DF:Power:CurrentThreshold:SleepCurrent()

DF:Power:CurrentThreshold:WakeCurrentThreshold()CMD:AverageCurrent()

.

CMD:ControlStatus().[SLEEP]

2.3.3.FullSleepMode

TheHY4145isfullypowered,andperformsmeasurements,calculationsanddatasetupdatesina20secondsextendedinterval,periodically.DuringFULLSLEEPmode,thedeviceisrunningunderslowertimebasetotallytofurtherreducethepowerconsumption.Thedevicecansuspendthe2–Wire

(I2C)communicationinterfaceasmuchas4msbypullingthecommunicationlineslow.

TheFULLSLEEPmodeisenteredautomaticallyfromSLEEPmode,if(1)thefeatureisenabledwith[FULLSLEEP]=1,OR(2)theconfigurableFullSleepWaitTime()isexpiredsincethedeviceisin

SLEEPmode.

TheHY4145exitsthismodeandentersNORMALmode,if(1)anycommunicationcommandisreceived,OR(2)theCurrent()valuerisesabovetheconfigurableSleepCurrent()threshold,OR(2)

thecurrentabovetheconfigurableWakeCurrentThreshold()valueacrossRSENSEisdetected.

RelatedVariables:

DF:Power:TimeThreshold:FullSleepWaitTime()DF:Power:CurrentThreshold:SleepCurrent()

DF:Power:CurrentThreshold:WakeCurrentThreshold()

?2012HYCONTechnologyCorp

Confidential

April,2012

page12

HY4145

TechnicalReference

CMD:Current()

CMD:ControlStatus().[SLEEP],[FULLSLEEP]

2.3.4.HibernateMode

TheHIBERNATEmodeisusedifthesystemorthebatteryneedstostayinaverylowpowerstate,andminimalpowerconsumptionfortheHY4145isrequired.Thismodecanbeappliedwithhost’sHIBERNATEmodetogether.Thedevicecanenterthismodeduetoeitherlowcellvoltage,orlow

loadcurrentwith[HIBERNATE]=1.

A.

HIBERNATEduetolowcellvoltage.TheHIBERNATEmodeisenteredautomaticallyfromSLEEPorFULLSLEEPmode,if(1)theVoltage()valueisbelowtheconfigurableHibernateVoltage()valueAND(2)anOCVmeasurementtakenafterbatteryisrelaxed.ThisOCVvaluewillbehelduntilthebatteryvoltagedropstoPORthreshold.Inthiscase,ifthe[SHUTDOWN]is

alsoset,inControlStatus()register,theSEpinwillbeasserted.

B.

HIBERNATEduetolowloadcurrent.TheHIBERNATEmodeisenteredautomaticallyfromSLEEPorFULLSLEEPmode,if(1).[HIBERNATE]=1,inControlStatus()register,AND(2)theAverageCurrent()valueisbelowtheconfigurableHibernateCurrent()value(SystemSleepstate

only),AND(3)anOCVmeasurementtakenafterbatteryisrelaxed.

.

BeforetheentrytoHIBERNATEmode,theHY4145maystilltrytotaketheOCVmeasurementwithatleastoneconditionqualifiedfromabove.Duringthisperiod,if(1)thequalifieditemsinAdisqualified,OR(2)thequalifieditemsinBdisqualified,theHY4145stillcanbebacktoSLEEPorFULLSLEEPmode.ThehostcanidentifytheexitofthedevicefromHIBERNATEmodebychecking

ifthe[HIBERNATE]=0,thatwasclearedbythedeviceautomatically.

IfthebatteryvoltagedropstoPORthreshold,theHY4145willbepowereddown.Ifanycommunicationcommandisreceived,thedevicewillbeoutofHIBERNATEmode,andclearthe[HIBERNATE]bit,andenterNORMALmode.Aseriesofinitializationactivitiesstartstosetthedevicebeingreadyforbatterygauge.Thewholeprocesstakesabout350ms.Itisstronglyrecommendedfor

hosttoclearthe[HIBERNATE]bittopreventthedevicebacktotheHIBERNATEmodeagain.

RelatedVariables:

DF:Power:VoltageThreshold:HibernateVoltage()DF:Power:CurrentThreshold:HibernateCurrent()CMD:Voltage()

CMD:AverageCurrent()

CMD:ControlStatus().[SLEEP],[FULLSLEEP],[HIBERNATE],[SHUTDOWN]

2.3.5.ResetMode

?2012HYCONTechnologyCorp

Confidential

April,2012

page13

HY4145

TechnicalReference

TheHY4145detectsasoftwarereset(Reset()subcommandissuedthroughControl()access),it

determinesthesoftwaretypeofreset,andincrementsthecorrespondingcounter.

RelatedVariables:

CMD:Control():Reset()

.

?2012HYCONTechnologyCorp

Confidential

April,2012

page14

HY4145

TechnicalReference

2.4.Protection

2.4.1.JEITATemperatureRanges

TheHY4145appliestheJEITAsafetyguidelineswhichspecifythatchargingvoltageandchargingcurrentdependontheoperationtemperature.Thetemperaturerangesspecifywhatthecharging

voltageandchargingcurrentshouldbeapplied.

Therearethreetemperatureranges,configuredinDataFlash,inwhichchargingisallowedandthey

aredefinedas:

JT1–JT2:Lowtemperaturerange,T1–T2.

JT2–JT3:Standardtemperaturerange1,T2–T3.

JT3–JT4:Hightemperaturerange,T3–T4.

ChargeisinhibitedorsuspendedifthetemperatureisbelowT1oraboveT4untilthetemperatureriseaboveordropsbelowtherecoverythreshold.ChargeissuspendedinrangeT3–T4untilthe

temperatureriseaboveordropsbelowtherecoverythreshold.

Additionaltemperaturerangesareconfigured.inDataFlashforthedischargingvoltageanddischargingcurrent.

DOT1:Dischargewillbesuspendedifthetemperatureisaboveuntilthetemperaturedropsbelowtherecoverythreshold(DOT1Recovery()).

DHT:Dischargeisinhibitedifthetemperatureisaboveuntilthetemperaturedropsbelowthe

recoverythreshold(DHTRecovery()).

AtemperatureHysteresis(TempHysteresis())isimplementedtospecifyadegreeofHysteresisthat

shouldbeusedbeforeswitchingthechargingvoltageandchargingcurrentbetweenthetemperatureranges.

Theactivetemperaturerange,whichdecodedbythepreviousstate,theactualtemperatureandthe

Hysteresis,isindictedbyflagsinTempRangeasbelow.

?2012HYCONTechnologyCorp

Confidential

April,2012

page15

HY4145

TechnicalReference

Table2.JEITATemperatureRange

2.4.2.1stLevelProtectionFeatures

TheHY4145supportsawiderangeofbatteryandsystemprotectionfeaturesthatareeasily

configuredorenabled.

2.4.3.CellOvervoltageandCellUndervoltage

TheHY4145detectscellinovervoltageandundervoltageconditionsandprotectthecellfrom

damage.

Iftheovervoltage/undervoltageconditionsaredetectedinaspecifictemperaturerangeaccordingtoJEITAsafetyguidelines,theHY4145sets[OV]/[UV]alertbitsinSafetyAlert()registertoindicatethe

faults.Iftheovervoltage/undervoltageconditionsremainsoveraconfigurableperiod(OVTime()/UVTime())oncell,theHY4145setsthe[OV]/[U.V]statusbitsinSafetyStatus()register.Thein-useALTC

pinissetif[OV]isset.Thein-useALTDpinissetif[UV]isset.Otherwise,thealertswillbeclears.

TheHY4145recoversfromtheovervoltageconditionifcellvoltagedropsbelowtheOVRecovery()threshold,andclearsthe[OV]statusbitinSafetyAlert()registerandSafetyStatus()register.TheHY4145recoversfromtheundervoltageconditionifcellvoltagerisesabovetheUVRecovery()threshold,andclearsthe[UV]statusbitinSafetyStatus()register.Thein-useALTCpinisclearedif

[OV]iscleared.Thein-useALTDpinisclearedif[UV]iscleared.

PerJEITAsafetyguidelines,theHTOVThreshold(),STOVThreshold(),andLTOVThreshold()are

configureddifferentlydependingonhigh,standardandlowtemperatureranges.

Thetransitionforovervoltageandundervoltageconditionsisshownbelow.

?2012HYCONTechnologyCorp

Confidential

April,2012

page16

HY4145

TechnicalReference

.

Figure2.OvervoltageandUndervoltageConditions

Note*:OVthreshold()/UVthreshold()valuesaredifferentunderhigh(HT),standard(ST)andlow(LT)temperatureranges.

Thestatesofrelatedflagsarelistedwithrespecttoovervoltageandundervoltageconditionsasin

Table3.

Table3.OvervoltageandUndervoltageConditions

RelatedVariables:

DF:1stLevelSafety:Voltage:LTOVThreshold()DF:1stLevelSafety:Voltage:STOVThreshold()DF:1stLevelSafety:Voltage:HTOVThreshold()

DF:1stLevelSafety:Voltage:OVRecovery()

?2012HYCONTechnologyCorp

Confidential

April,2012

page17

HY4145

TechnicalReference

DF:1stLevelSafety:Voltage:OVTime()

DF:1stLevelSafety:Voltage:UVThreshold()DF:1stLevelSafety:Voltage:UVRecovery()DF:1stLevelSafety:Voltage:UVTime()

DF:GeneralCfg:GeneralData:OperationCfgA().[ALT_EN]CMD:SafetyAlert().[OV],[UV]

CMD:SafetyStatus().[OV],[UV]CMD:Voltage()

CMD:Current()

PIN:ALTC,ALTD

2.4.4.ChargeandDischargeOvercurrent

TheHY4145detectsovercurrentfaultsinchargeanddischargeoperationsandprotectthecelland

systemfromdamage.The1sttierofovercurrentprotectionisimplemented.

1stTier–IftheCurrent()isabovetheconfigurableCOCThreshold()/DOCThreshold()valuesincharge/dischargerespectively,theHY4145sets[COC]/[DOC]alertbitinSafetyAlert()registertoindicatethefault.Iftheovercurrentconditionremainsoveraconfigurableperiod(COC

Time()/DOCTime())onanycellinthestack,theHY4145setsthe[COC]/[DOC]statusbitsin

SafetyStatus()register.Thein-useALTC.pinissetif[COC]isset.Thein-useALTDpinissetif[DOC]isset.

IftheAverageCurrent()valuedropsbelowtheCOCRecovery()/DOCRecovery()thresholdsandtheCurrentRecoveryTimer()expires,the[COC]/[DOC]statusbitswillbeclearedinSafetyStatus()register.Thein-useALTCpinisclearedif[COC]iscleared.Thein-useALTDpin

isclearedif[DOC]iscleared.

NotethattheCOC/DOCovercurrentprotectionfeaturesaredisablediftheCOCTime()/DOC

Time()valuesaresettozero.

Thetransitionfor1sttierchargeanddischargeovercurrentconditionsisshownbelow.

?2012HYCONTechnologyCorp

Confidential

April,2012

page18

HY4145

TechnicalReference

ExitfromCOCCondition.

ExitfromDOCCondition.

ANDCurrentRecoveryTimerexpired

ANDCurrentRecoveryTimerexpired

ExitfromCOCAlert.

beforeCOCTimerexpired

EntrytoCOCAlert.

StayinDO

ANDDOC

StayinCOCAlert.

ANDCOCTimercounts

EntrytoCOCCondition.[NR]=1,

AND

ANDCOCTimerexpired

StayinDOCCondition.

ANDCurrentRecoveryTim

StayinCOCCondition.

ANDCurrentRecoveryTimerclears

.

Figure3.1stTierChargeandDischargeOvercurrentConditions

ThestatesofrelatedflagsarelistedwithrespecttoovercurrentconditionsasinTable4.

Table4.ChargeOvercurrentandDischargeOvercurrentConditions

Therecommendedsettingfordischargeovercurrentprotectionlevelsarepresentedasbelow.

?2012HYCONTechnologyCorp

Confidential

April,2012

page19

CAlert.Timercounts

EntrytoDOCCondition.

ANDDOCTimerexpired

erclears

Set[DOC]statusbit.Clear[DOC]alertbit.StopDOCTimer.

StartCurrentRecoveryTimer.

Set[COC]statusbit.Clear[COC]alertbit.StopCOCTimer.

StartCurrentRecoveryTimer.

Set[COC]alertbit.StartCOCTimer.

ExitfromDOCAlert.beforeDOCTimerexpired

EntrytoDOCAlert.

Set[DOC]alertbit.StartDOCTimer.

Clear[COC]or[DOC]statusbit.ResetCurrentRecoveryTimer,COCTimerorDOCTimer.

HY4145

TechnicalReference

DischargeCurrent

Time

.

Figure4.DischargeOvercurrentProtectionLevels

RelatedVariables:

DF:1stLevelSafety:Current:COC(1stTier)Threshold()DF:1stLevelSafety:Current:COC(1stTier)Recovery()DF:1stLevelSafety:Current:COC(1stTier)Timer()DF:1stLevelSafety:Current:DOC(1stTier)Threshold()DF:1stLevelSafety:Current:DOC(1stTier)Recovery()DF:1stLevelSafety:Current:DOC(1stTier)Timer()DF:1stLevelSafety:Current:CurrentRecoveryTimer()

DF:GeneralCfg:GeneralData:OperationCfgA().[ALT_EN]

DF:Configuration:Registers:OperationCon