| Electronic Components Datasheet Search |
|
LTM4675 Datasheet(PDF) 34 Page - Analog Devices |
|
|
|||||||||||||||||||||||||||||
LTM4675 Datasheet(HTML) 34 Page - Analog Devices |
|
34 / 132 page ![]() LTM4675 34 Rev. D For more information www.analog.com OPERATION n Output OV/UV Fault and Warn Protection n Output OC Fault and Warn Protection n Internal and External Overtemperature Fault and Warn Protection n External Undertemperature Fault Protection n CML Fault (Communication, Memory or Logic) n ExternalFaultDetectionviatheBidirectionalGPIOnPins. In addition, the LTM4675 can map any combination of fault indicators to their respective GPIOn pin using the propagate GPIOn response commands, MFR_GPIO_PROPAGATEn. Typical usage of a GPIO pin is as a driver for an external crowbar device, overtemperature alert, overvoltage alert or as an interrupt to cause a microcontroller to poll the fault commands. Alternatively, the GPIOn pins can be used as inputs to detect external faults downstream of the controller thatrequireanimmediateresponse.TheGPIO0and/orGPIO1 pins can also be configured as power good outputs. Power good indicates the controller output is within the OV/UV fault thresholds.Atpower-upthepinwillinitiallybethree-state.Ifit is necessary to have the desired polarity on the pin at power- up in this configuration, attach a Schottky diode between the RUN pin of the propagated power good signal and the GPIO pin. The Cathode must be attached to RUN and the Anode to the GPIO pin (see Figure 2). If the GPIO pin is set to a power good status, the MFR_GPIO_RESPONSE must be ignore otherwise a latched off condition exists. As described in the Soft-Start section, it is possible to control start-upthroughconcatenatedevents.IfGPIOnisusedtodrive the RUN pin of another controller, the unfiltered VOUT_UV fault limit should be mapped to the GPIO pin. AnyfaultorwarningeventwillcausetheALERTpintoassert low unless the ALERT is masked by the SMBALERT_MASK command. The pin will remain asserted low until the CLEAR_FAULTS command is issued, the fault bit is written to a 1, the PMBus master successfully reads the device ARA register, bias power is cycled or a MFR_RESET or RESTORE_USER_ALLcommandisissued.Channelspecific faults are cleared if the RUN pins are toggled OFF/ON or the part is commanded OFF/ON via PMBus. If bit 0 of MFR_ CONFIG_ALL is set to a 1, toggling the RUN pins OFF/ON or commanding the part OFF/ON via PMBus clears all faults. TheMFR_GPIO_PROPAGATEncommanddeterminesifthe GPIO pins are pulled low when a fault is detected; however, the ALERT pin is always pulled low if a fault or warning is detected and the status bits are updated unless the ALERT pin is masked using the SMBALERT_MASK command. Output and input fault event handling is controlled by the corresponding fault response byte as specified in Table 24 to Table 28. Shutdown recovery from these types of faults can either be autonomous or latched. For autonomous recovery, the faults are not latched, so if the fault condition is not present after the retry interval has elapsed, a new soft-start is attempted. If the fault persists, the controller will continue to retry.TheretryintervalisspecifiedbytheMFR_RETRY_DELAY commandandpreventsdamagetotheregulatorcomponents by repetitive power cycling. The MFR_RETRY_DELAY must be greater than 120ms. It can not exceed 83.88 seconds. Channel-to-channel fault dependencies can be created by connectingGPIOnpinstogether.Intheeventofaninternalfault, one or more of the channels is configured to pull the bussed GPIOnpinslow.Theotherchannelsarethenconfiguredtoshut down when the GPIOn pins are pulled low. For autonomous group retry, the faulted channel is configured to release the GPIOn pin(s) after a retry interval, assuming the original fault has cleared. All the channels in the group then begin a soft-start sequence. If the fault response is LATCH_OFF, the GPIO pin remains asserted low until either the RUN pin is toggled OFF/ON or the part is commanded OFF/ON. The toggling of the RUN either by the pin or OFF/ON command will clear faults associated with the channel. If it is desired to haveallfaultsclearedwheneitherRUNpinistoggled,setbit0 of MFR_CONFIG_ALL to a 1. The status of all faults and warnings is summarized in the STATUS_WORD and STATUS_BYTE commands. RESPONSES TO VOUT AND IOUT FAULTS VOUTOVandUVconditionsaremonitoredbycomparators. The OV and UV limits are set in three ways. n As a Percentage of the VOUT if Using the Resistor Con- figuration Pins n In EEPROM if Either Programmed at the Factory or Through the GUI n By PMBus Command |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |