国产精品一区二区久久久久,精品人妻无码一区二区三区色欲,国产亚洲一区二区三区精品久久

SLVUAW9C September 2016 – February 2020 UCD90320

UCD90320 Sequencer and System Health Controller PMBus Command Reference

10.26 (ECh) LOGGED_FAULT_DETAIL (MFR_SPECIFIC_28)

This read-only block common command returns detail information about a given fault:

The time that it happened in milliseconds (0 to 86400000) and days (0 to 1048575)
Whether or not the fault is page specific
The page that the fault occurred on (when applicable)
The type of fault (see Section 10.24)

Table 49. LOGGED_FAULT_DETAIL Command Format

Byte Number (Read)	Payload Index	Description
		CMD = EC
0		BYTE_COUNT = 12
1	0	Page number + Milliseconds (high byte)⁽¹⁾
2	1	Milliseconds
3	2	Milliseconds
4	3	Milliseconds (low byte)
5	4	Fault ID + Days (high byte)
6	5	Fault ID + Days
7	6	Fault ID + Days
8	7	Fault ID + Days (low byte)
9	8	Fault Value (low byte)
10	9	Fault Value (middle byte)
11	10	Fault Value (middle high byte)⁽²⁾
12	11	Fault Value (high byte)⁽²⁾

(1) Page number is at bits 31:27 and Milliseconds is at bit 26:0.

(2) This byte is valid only if the current fault type is either Sequence On Timeout or Sequence Off Timeout.

New LOGGED_FAULT_DETAIL entries for a given fault are logged once and then not logged again until one of the following events occurs[2]:

Firmware is restarted
The rail stays in regulation for the amount of time determined by TON_MAX_FAULT_LIMIT. If TON_MAX_FAULT_LIMIT is set to 0, 4 seconds are used for the time.
The rail is turned off and then turned back on. (1)
The CLEAR_FAULTS command is written
The LOGGED_FAULTS command is written

(1) This applies to paged faults only.

(2) Everything GPI state is changed to de-asserted, a GPI fault is logged.

The maximum number of entries per device is show in Table 50. Once the maximum entries have been logged, no more detail is logged until the fault log is cleared (see Section 10.24). Unless, the “Enable Log FIFO” bit in the MISC_CONFIG command is set (see Table 68).

Table 50. Number of Log Entries in Each Device Type

Device	Entries
UCD90120	16
UCD90120A	16
UCD90124	10
UCD90124A	12
UCD9090	30
UCD90910	12
UCD90160	18
UCD90240	100
UCD90320	100

The Days field is a 32-bit value where the top bits are used to encode other information as shown in Table 51.

Table 51. Fault Identification + Days

Bits(s)	Description
31	Page Specific (1 – yes, 0 – no)
30–27	Fault Type
26–11	Days⁽¹⁾
10-0	Reserved

(1) The days is offset from 2000-01-01 00:00:00.00. It is responsible of application to add the that time base when retrieving the time stamp.

Information on the Fault Value (units and formatting) is shown in Table 52.

Table 52. Fault Value

Fault Type Number	Paged?	Description	Fault Value Units	Data Format
0	No	Reserved
1	No	System Watchdog Timeout	Not Valid	n/a
2	No	Resequence Error	Not Valid	n/a
3	No	Watchdog Timeout	Not Valid	n/a
4	No	Reserved
5	No	Reserved
6	No	Reserved
7	No	Reserved
8	No	Fan Fault⁽¹⁾	RPM	LINEAR11
9	No	GPI Fault⁽¹⁾	Not Valid	n/a
0	Yes	VOUT_OV Fault	Voltage	LINEAR16
1	Yes	VOUT_UV Fault	Voltage	LINEAR16
2	Yes	TON_MAX Fault	Voltage	LINEAR16
3	Yes	IOUT_OC Fault	Current	LINEAR11
4	Yes	IOUT_UC Fault	Current	LINEAR11
5	Yes	TEMPERATURE_OT Fault	Temperature	LINEAR11
6	Yes	Sequence On Timeout	N/A	Bit Mask⁽²⁾⁽³⁾
7	Yes	Sequence Off Timeout	N/A	Bit Mask⁽²⁾⁽³⁾

(1) The Page Number is used to encode which Fan or GPI that the fault information applies to.

(2) Any bit set to 1 corresponds to a page dependency that is not met. The GPI dependencies that are not met are OR’ed into the top 8 bits. So, for example, if page dependencies 2 and 5 are not met and GPI W (bit 4) dependency is not met, the fault value is 0x1024.

(3) Any bit set to 1 corresponds to a page dependency that is not met. The GPI dependencies that are not met are OR’ed into the all 24 bits. So, for example, if page dependencies 2 and 5 are not met and GPI W (bit 4) dependency is not met, the fault value is 0x000034