实例介绍
【实例简介】
PMBus1.2 specification for digital power supply.
Introductio∩ 9 1.1. Specification Scope 9 1.1.1. Specification Structure 9 1.1.2. What Is Included 1.1.3. What ls not Included In the pmbus specification 1.2. Specification Changes Since The Last Revision....... 999 1.3. Where To send Feedback and comments 2. Related documents 9 2. 1. Scope 2.2. Applicable documents 9 2.3. Reference documents 10 3. Reference Inform ation …10 3.1. Signal and Parameter Names 10 3.2. Numerical Formats 10 3.2.1. Decimal Numbers .10 3. 2.2. Binary Numbers 10 3.2.3. Hexadecimal Numbers 10 3.2. 4. Examples 10 3.3. Bit And Byte Order 3.4. Bit And Byte lllustrations .11 3.5. Abbreviations, Acronyms And Definitions 13 4. Addressing And Grouping .15 4.1. Device Addresses 4.2. General Call Address(Global broadcast 15 4.3. Sending Commands To A Group 16 5. Commands 16 5.1. Commands and command codes 16 5.2. Command extensions 16 5.3. Command execution 16 5. 4. Writing And Reading PMBus Devices 16 5,4.1. All Packets start With a write Address .16 5.4.2. Every Parameter That Can Be Written Must Be Readable 16 5.4.3. Commands May Be read Only 17 6. Memory Model, Startup Behavior And Defaults 17 6.1. Order Of Memory Loading And Precedence 18 6.2. The default and user stores 19 7. Data formats 20 7.1 Linear data format 2 7.2. DIRECT Data format 7.2.1. Interpreting Received values 2 7. 2.2. Sending A Value. 22 7.2.3. Obtaining The value Of The m, b, And R Coefficients 7.3. Accuracy 22 7. 4. Resolution 8. Data Formats For The Output Voltage And Output Voltage Related Parameters 23 8. 1. Two Step Process.... 23 8.2, VOUT MODE Command 23 8.3. Data Bytes For Output Voltage Related Commands 24 8.3.1 Linear mode 25 83.2 Vid Format 25 8.3.3. DIRECT Format 26 9. Setting And Monitoring The Output Voltage And Current 27 9.1. VOUT SCALE LOOP And VOUT SCALE MONITOR 27 9.2. Setting The Output Voltage.…,,,… .29 o 2009 System Management Interface Forum, Inc Page 3 of 105 All Rights reserved 9.3. Making And Calibrating Output Current Measurements 31 9. 4. Deleted 32 10. Fault Management And Reporting 32 10.1. Monitoring Operation 32 10.2. General Description Of PMBus Device Fault Management 33 10.2.1. Warning Conditions 33 10.2.2 Fault Conditions………… 10.2.3. Clearing Warning Or Fault Bits 33 34 10.2. 4. Clearing Individual Bits 34 10.2.5. Clearing bits In the statUs BYtE And StaTUS WORd ∴34 10.2.6. Immediate Reassertion After Clearing If Condition Is Still Present 35 10.3. Conceptual view of How Status Bits And smbalert# Work .36 10.4. Setting Fault And Warning Thresholds 37 10.5. Setting The Response To A Detected Fault Condition ..37 10.5. 1. Response To Voltage, Temperature And TON MAX Faults 38 10.5.2. Response To Current Faults 面面 画国面面面面 39 10.6. Reporting Faults And Warnings To The Host 翻国面国.国面 翻面画 41 10.6.1. SMBaLERT# Signal And Process 41 10.6.2. Direct PmBus device To host communication 41 10.7. Clearing A Shutdown Due To A Fault ∴42 10.8. Data transmission faults 42 10.8.1. Corrupted Data 42 10.8.2. Sending Too Few Bits 。 ,。 42 10.8.3. Reading Too Few Bits 国国 43 0.8.4. Host Sends Or Reads Too Few Bytes 43 10.8.5. Host Sends Too Many Bytes 43 10.8.6. Reading Too Many Bytes 国面国面面1 44 10.8.7. Device Busy 4 10.9. Data Content faults 44 10.9.1. Improperly Set Read Bit In The Address byte 44 10.9.2. Unsupported Command Code 45 10.9.3. Invalid Or Unsupported Data 45 10.9.4. Data Out Of Range Fault 45 10.95. Reserved bits… 46 11. Address, Memory, Communication And Capability related Commands 46 11.1. WRITE PROTECT 46 1.2. STORE DEFAULT ALL “· 11.3. RESTORE DEFAULT ALL 面E垂 47 11. 4. STORE DEFAULT CODE ..a..a....: 47 11.5. RESTORE DEFAULT CODE 47 11.6. STORE USER ALL .48 11.7 RESTORE USER ALL 48 11.8. STORE USER CODE 48 11. 9. RESTORE USER CODE …49 11.10.PAGE 1量面4面面面1面 面面面 EB面国国B面1 ,着潘 949 11.11. PHASE 51 11.12. CAPABILITY 51 11.13. QUERY 翻面1 :.“.a:.: 52 11.14 PAGE PLUS WRITE 53 11.15. PAGE PLUS READ 53 12. On, Off And Margin Testing Related Commands 1, 53 12.1 OPERATION 53 12.2 ON OFF CONFIG 54 13. Output Voltage Related Commands .56 13.1. VOUT MODE 56 13.2. VOUT COMMAND 56 o 2009 System Management Interface Forum, Inc Page 4 of 105 All Rights reserved 133. VOUT TRIM 56 13.4 VOUT CAL OFFSET 56 13.5. VOUT MAX 56 13.6. VOUT MARGIN HIGH 57 13.7 VOUT MARGIN LOW 57 13.8. VOUT TRANSITION RATE 57 13.9. VOUT DROOP 57 13.10. VOUT SCALE LOOP 58 13.11. VOUT SCALE MONITOR 58 14 Other commands 58 14.1 COEFFICIENTS 58 14.2. POUT MAX…… 59 143. MAX DUTY 59 14.4. FREQUENCY SWITCH 59 14.5 VN○N 60 14.6.V|N○FF .60 147. INTERLEAVE ,1c 60 14.8 IOUT CAL GAIN 61 149. OUT CAL OFFSET E面 61 14.10. FAN CONFIG 1 2 62 14.11. FAN CONFIG 3 4 ∴.63 14.12 FAN COMMAND n 64 15. Fault related commands 。 64 15 CLEAR FAULTS ∴.14 152. VOUT OV FAULT LIMIT 64 15.3. VOUT OV FAULT RESPONSE 64 15.4 VOUT OV WARN LIMIT 65 15.5. VOUT UV WARN LIMIT ..65 15.6. VOUT UV FAULT LIMIT 65 15.7 VOUT UV FAULT RESPONSE 1道 65 15.8. OUT OC FAULT LIMIT .66 159. OUT OC FAULT RESPONSE 66 15.10. JOUT OC LV FAULT LIMIT ..66 15.11 OUT OC LV FAULT RESPONSE .66 15.12. OUT OC WARN LIMIT 7 15.13. OUT UC FAULT LIMIT ∴.67 15.14. OUT UC FAULT RESPONSE 67 15.15. DELETED 68 1516. DELETED ∴68 15.17 OT FAULT LIMIT 68 15.18. OT FAULT RESPONSE 画E 68 15.19. OT WARN LIMIT 68 15.20. UT WARN LIMIT 69 15.21. UT FAULT LIMIT 69 15.22 UT FAULT RESPONSE 画面面 9 15.23. VIN OV FAULT LIMIT 70 15.24 VIN OV FAULT RESPONSE 70 15.25.VNO∨ WARN LIM|T 1B面 70 15.26. VIN UV WARN LIMIT 70 15.27. VIN UV FAULT LIMIT 71 15.28. VIN UV FAULT RESPONSE 1画1 7 15.29. N OC FAULT LIMIT 71 15.30. IIN OC FAULT RESPONSE ∴72 15.31.‖ N OC WaRN L|M|T 72 15.32. POWER GOOD Signal Limits ∴72 15.321. POWER GOOD ON 2 o 2009 System Management Interface Forum, Inc Page 5 of 105 All Rights reserved 15.32.2. POWER GOOD OFF 73 15.33. POUT OP FAULT LIMIT 73 15.34 POUT OP FAULT RESPONSE 73 15.35. POUT OP WARN LIMIT 73 1536. PIN OP WARN LIMIT .74 15.37. Other Fault And Warning Responses .74 15.38. SMBALERT MASK Command 74 16. Output Voltage Sequencing Commands 75 16.1 TON DELAY 16.2 TON RISE 75 16.3. TON MAX FAULT LIMIT 75 16.4 TON MAX FAULT RESPONSE 76 16.5. TOFF DELAY 76 16.6. TOFF FALL 76 16.7 TOFF MAX WARN LIMIT 76 17. Unit Status Commands 77 17.1 STATUS BYTE 78 17.2. STATUS WORD 78 173. STATUS VOUT 面国面 79 17. 4. STATUS OUT 80 175. STATUS INPUT .80 176. STATUS TEMPERATURE 81 17.7. STATUS CML (Communications, Logic, And Memory) 。 81 17.8. STATUS OTHER 82 17.9. STATUS MER SPECIFIC 82 17.10. STATUS FANS 12 82 17.11 STATUS FanS 3 4 83 18. Reading parametric Information 84 18.1. READ VIN 84 18.2.READⅢN 国国面 84 18.3.READ∨CAP 84 184 READ VOUT .85 18.5. READ JOUT 85 186. READ TEMPERATURE n 85 18.7 READ FAN SPEED n 85 18. 8. Deleted 86 18. 9. READ DUTY CYCLE .86 18.10. READ FREQUENCY 1量 86 18.11. READ POUT 1面 86 18.12. READ PIN 1813. READ EIN 86 18.14. READ EOUT 88 19. Reserved 88 22 Reserved 1 ∴88 1. Reserved L画量日1面国面1面面 1国量面日国国量面日面.面B面国 面面 89 22. Manufacturer's Information 89 22.1 PMBUS REVISION 89 22.2. Inventory Information .89 22.2.1. MER D.………… 89 22.2.2. MER MODEL 90 22.23. MER REVISION 90 22.2.4 MER LOCATION 90 22.25. MER DATE 22.2. 6. MER SERIAL 22.27. IC DEVICE ID 90 22.28. IC DEVICE REV o 2009 System Management Interface Forum, Inc Page 6 of 105 All Rights reserved 22.3 Manufacturer Ratings 90 223.1. MER VIN MIN 91 223.2. MER VIN MAX 91 22.3.3 MFR‖NMAX 91 22.3.4. MER PIN MAⅩ 91 223.5. MER VOUT MIN 91 223.6. MER VOUT MAX 9 223.7. MFR IOUT MAX 22.38. MER POUT MAX 91 22.3. 9. MER TAMBIENT MAX 91 22.3.10. MER TAMBIENT MIN 22.3.11. MER EFFICIENCY LL 91 22.3.12. MFR EFFICIENCY HL 92 223.13. MER PIN ACCURACY 93 223.14 APP PROFILE SUPPORT 93 223.15. MFR MAX TEMP 1. 2. 3 面 94 23. User Data and configuration 94 24. Manufacturer specific Commands 95 25. Command extensions 95 25.1. MER SPECIFIC COMMAND EXT 95 25.2. PMBUS COMMAND EXT 95 APPENDIX I Command Summary 96 APPENDIX IL. Summary of changes 105 Figure 1 Bit Order Within a Byte 11 Figure 2. Conceptual View Of Possible PMBus Device Memory And Communication 18 Figure 3 Flowchart Of Conceptual Loading Operating Memory At Start ..19 Figure 4. Linear Data Format Data Bytes 21 Figure 5. VOUT MODE Command Data Byte Structure 24 Figure 6. Linear Format Data bytes Figure 7. Vid Format Data Bytes Figure 8. DIRECT Format Mode Data Bytes 27 Figure 9. Output Voltage Sensing In A T ypical Power Converter 28 Figure 10. Conceptual View Of The Application Of The VOUT SCALE LOOP Command Figure 11. Conceptual View Of How Output Voltage related Commands Are Applied 30 Figure 12. Generating READ IOUT Concept 翻国面国.国面 31 Figure 13 Status Register Map 32 Figure14. Conceptual Schematic Of Status Bits And SMBALERT#…………,,… .37 Figure 15. Interaction Of SMBALERT# And Status Registers 41 Figure 16 Packet Structure For PMBus device To Notify Host 42 Figure 17. Conceptual View Of Paging Used For A Multiple Output PMBus Device. ...........................50 Figure 18. Conceptual view Of Using Paging With a PMBus To Non -PMBus Device Adapter 50 Figure19. PAGE PLUS Command Example With Written Data And PEc……… 53 Figure 20 PAGE_ PLUS Command Example With Data To Read And PEC 53 Figure 21. Retrieving Coefficients Using PEC 59 Figure 22. Illustration Of The INTERLEAVE Command Function 61 Figure 23. SMBALERT MASK Command packet format 74 Figure 24. Retrieving The SMBALERT MASK Setting For A Given Status Register .75 Figure 23. Summary of the status registers 77 Figure 26. READ EIN Command Packet Format 87 Figure 27. READ EOUT Command Packet Format 88 Figure 24. APP PROF ILE- SUPPORT Packet EXample 94 o 2009 System Management Interface Forum, Inc Page 7 of 105 All Rights Reserved Table 1 Bit And Byte Symbols Used In this specification Table 2. Summary of The VoUt MOdE Data Byte format 24 Table 3. VID Types Supported By PMBus 26 Table 4. Voltage, Temperature And Ton MAX Faults response data byte details 38 Table 5. Current Fault Response Data Byte Details 39 Table 6. WRITE PROTECT Command data byte .46 Table 7. CAPABILITY COMMAND Data Byte Format 51 Table 8 QUERY Command returned data byte format 52 Table 9. OPERATION Data Byte Contents ∴54 Table 10 ON OFF CONFIG Data Byte 5 Table 11. INTERLEAVE Data Bytes Format 60 Table 12. FAN CoNFiG 1 2 Data byte format 62 Table 13. FAN CONFIG__4 Data Byte Format 63 Table 14 STATUS BYTE Message Contents 78 Table 15 STATUS WORD Message Contents 78 Table 16 STATUS VOUT Data Byte 79 Table 17 STATUS IOUT Data byte ,.. .80 Table18. STATUS丨 NPUT Data Byte…… 80 Table 19 STATUS TEMPERATURE Data Byte Table 20 STATUS CML Data Byte 88 11面B画 Table 21. STATUS OTHER Data Byte 82 Table 22 STATUS MFR SPECIFIC Data Byte 82 Table23. STATUS_FANS_1_2 Data Byte∴………….………………….…… 82 Table 24 STATUs FANs 3 4 Data Byte 83 Table 25 PMBus Revision Data Byte Contents .89 Table 26. APP_PROFILE SUPPORT First Data Byte Contents 93 Table 27. Command Summary.. o 2009 System Management Interface Forum, Inc Page 8 of 105 All Rights Reserved The Power Management Bus("PMBus TM")is an open standard protocol that defines a means of communicating with power conversion and other devices For more information, please see the System Management Interface Forum Web site www.powersig.org The PMBus specification is in two parts. Part I includes the general requirements, defines the transport, and defines the electrical interface and timing requirements of hardwired signals Part I, this document, describes the operation of commands, data formats fault management and defines the command language used with the PmBus This specification defines a protocol to manage power converters and a power system via communication over a digital communication bus The PMBus specification is not a definition or specification of a particular power conversion device or family of power conversion devices A specification of any individual or family of integrated circuits This specification does not address direct unit to unit communication such as analog current sharing, real-time analog or digital voltage tracking, and switching frequency clock signals a summary of the changes between this revision and revision 1.0 are shown in APPENDIX II Please send all comments by email to: questions@power SIG. org If the requirements of this specification and any of the reference documents are in conflict, this specification shall have precedence unless otherwise stated Referenced documents apply only to the extent that they are referenced The latest version and all amendments of the referenced documents at the time the power system is released to manufacturing apply Applicable documents include information that is, by extension, part of this specification o 2009 System Management Interface Forum, Inc Page 9 of 105 All Rights Reserved [A01 PMBus Power System Management Protocol, Part I, General Requirements, Transport and electrical Interface [A02 SBS Implementers Forum Version 1.1 1 1 november 1998 A03 SBS Implementers Forum Version 2.0, 3 August 2000 [AO4] Version 2.1. Philips semiconductors January 2000 [A05]| SO/EC8859-1:1998 and all corrigenda amendments published through the date of release of this specification [ Ao6 PMBus Application Profile: Server AC-DC Power Supplies [A07] PMBus Application Profile: DC-DC Converters For Microprocessor Power And Other Computer Applications A08 PMBus Application Profile: DC-DC Converters For General Purpose Use Reference documents have background or supplementary information to this specification They do not include requirements or specifications that are considered part of this document None in this revision The names of signals and parameters are given in capital letters. Underscores are used to separate words rather than embedded spaces(example: SIGNAL NAME The names of signals that are active low and parameters that are true when the value is 0 are indicated with an octothorpe(#)suffix(example: WRITE# means that the device can be written when the signal is low) All numbers are decimal unless explicitly designated otherwise Numbers explicitly identified as decimal are identified with a suffix of"d Numbers in binary format are indicated by a suffix of b. Unless otherwise indicated, all binary numbers are unsigned All signed binary numbers are twos complement Numbers in hexadecimal format are indicated by a suffix ofh 255d4FFh分11111111b o 2009 System Management Interface Forum, Inc Page 10 of 105 All Rights Reserved 【实例截图】
【核心代码】
PMBus1.2 specification for digital power supply.
Introductio∩ 9 1.1. Specification Scope 9 1.1.1. Specification Structure 9 1.1.2. What Is Included 1.1.3. What ls not Included In the pmbus specification 1.2. Specification Changes Since The Last Revision....... 999 1.3. Where To send Feedback and comments 2. Related documents 9 2. 1. Scope 2.2. Applicable documents 9 2.3. Reference documents 10 3. Reference Inform ation …10 3.1. Signal and Parameter Names 10 3.2. Numerical Formats 10 3.2.1. Decimal Numbers .10 3. 2.2. Binary Numbers 10 3.2.3. Hexadecimal Numbers 10 3.2. 4. Examples 10 3.3. Bit And Byte Order 3.4. Bit And Byte lllustrations .11 3.5. Abbreviations, Acronyms And Definitions 13 4. Addressing And Grouping .15 4.1. Device Addresses 4.2. General Call Address(Global broadcast 15 4.3. Sending Commands To A Group 16 5. Commands 16 5.1. Commands and command codes 16 5.2. Command extensions 16 5.3. Command execution 16 5. 4. Writing And Reading PMBus Devices 16 5,4.1. All Packets start With a write Address .16 5.4.2. Every Parameter That Can Be Written Must Be Readable 16 5.4.3. Commands May Be read Only 17 6. Memory Model, Startup Behavior And Defaults 17 6.1. Order Of Memory Loading And Precedence 18 6.2. The default and user stores 19 7. Data formats 20 7.1 Linear data format 2 7.2. DIRECT Data format 7.2.1. Interpreting Received values 2 7. 2.2. Sending A Value. 22 7.2.3. Obtaining The value Of The m, b, And R Coefficients 7.3. Accuracy 22 7. 4. Resolution 8. Data Formats For The Output Voltage And Output Voltage Related Parameters 23 8. 1. Two Step Process.... 23 8.2, VOUT MODE Command 23 8.3. Data Bytes For Output Voltage Related Commands 24 8.3.1 Linear mode 25 83.2 Vid Format 25 8.3.3. DIRECT Format 26 9. Setting And Monitoring The Output Voltage And Current 27 9.1. VOUT SCALE LOOP And VOUT SCALE MONITOR 27 9.2. Setting The Output Voltage.…,,,… .29 o 2009 System Management Interface Forum, Inc Page 3 of 105 All Rights reserved 9.3. Making And Calibrating Output Current Measurements 31 9. 4. Deleted 32 10. Fault Management And Reporting 32 10.1. Monitoring Operation 32 10.2. General Description Of PMBus Device Fault Management 33 10.2.1. Warning Conditions 33 10.2.2 Fault Conditions………… 10.2.3. Clearing Warning Or Fault Bits 33 34 10.2. 4. Clearing Individual Bits 34 10.2.5. Clearing bits In the statUs BYtE And StaTUS WORd ∴34 10.2.6. Immediate Reassertion After Clearing If Condition Is Still Present 35 10.3. Conceptual view of How Status Bits And smbalert# Work .36 10.4. Setting Fault And Warning Thresholds 37 10.5. Setting The Response To A Detected Fault Condition ..37 10.5. 1. Response To Voltage, Temperature And TON MAX Faults 38 10.5.2. Response To Current Faults 面面 画国面面面面 39 10.6. Reporting Faults And Warnings To The Host 翻国面国.国面 翻面画 41 10.6.1. SMBaLERT# Signal And Process 41 10.6.2. Direct PmBus device To host communication 41 10.7. Clearing A Shutdown Due To A Fault ∴42 10.8. Data transmission faults 42 10.8.1. Corrupted Data 42 10.8.2. Sending Too Few Bits 。 ,。 42 10.8.3. Reading Too Few Bits 国国 43 0.8.4. Host Sends Or Reads Too Few Bytes 43 10.8.5. Host Sends Too Many Bytes 43 10.8.6. Reading Too Many Bytes 国面国面面1 44 10.8.7. Device Busy 4 10.9. Data Content faults 44 10.9.1. Improperly Set Read Bit In The Address byte 44 10.9.2. Unsupported Command Code 45 10.9.3. Invalid Or Unsupported Data 45 10.9.4. Data Out Of Range Fault 45 10.95. Reserved bits… 46 11. Address, Memory, Communication And Capability related Commands 46 11.1. WRITE PROTECT 46 1.2. STORE DEFAULT ALL “· 11.3. RESTORE DEFAULT ALL 面E垂 47 11. 4. STORE DEFAULT CODE ..a..a....: 47 11.5. RESTORE DEFAULT CODE 47 11.6. STORE USER ALL .48 11.7 RESTORE USER ALL 48 11.8. STORE USER CODE 48 11. 9. RESTORE USER CODE …49 11.10.PAGE 1量面4面面面1面 面面面 EB面国国B面1 ,着潘 949 11.11. PHASE 51 11.12. CAPABILITY 51 11.13. QUERY 翻面1 :.“.a:.: 52 11.14 PAGE PLUS WRITE 53 11.15. PAGE PLUS READ 53 12. On, Off And Margin Testing Related Commands 1, 53 12.1 OPERATION 53 12.2 ON OFF CONFIG 54 13. Output Voltage Related Commands .56 13.1. VOUT MODE 56 13.2. VOUT COMMAND 56 o 2009 System Management Interface Forum, Inc Page 4 of 105 All Rights reserved 133. VOUT TRIM 56 13.4 VOUT CAL OFFSET 56 13.5. VOUT MAX 56 13.6. VOUT MARGIN HIGH 57 13.7 VOUT MARGIN LOW 57 13.8. VOUT TRANSITION RATE 57 13.9. VOUT DROOP 57 13.10. VOUT SCALE LOOP 58 13.11. VOUT SCALE MONITOR 58 14 Other commands 58 14.1 COEFFICIENTS 58 14.2. POUT MAX…… 59 143. MAX DUTY 59 14.4. FREQUENCY SWITCH 59 14.5 VN○N 60 14.6.V|N○FF .60 147. INTERLEAVE ,1c 60 14.8 IOUT CAL GAIN 61 149. OUT CAL OFFSET E面 61 14.10. FAN CONFIG 1 2 62 14.11. FAN CONFIG 3 4 ∴.63 14.12 FAN COMMAND n 64 15. Fault related commands 。 64 15 CLEAR FAULTS ∴.14 152. VOUT OV FAULT LIMIT 64 15.3. VOUT OV FAULT RESPONSE 64 15.4 VOUT OV WARN LIMIT 65 15.5. VOUT UV WARN LIMIT ..65 15.6. VOUT UV FAULT LIMIT 65 15.7 VOUT UV FAULT RESPONSE 1道 65 15.8. OUT OC FAULT LIMIT .66 159. OUT OC FAULT RESPONSE 66 15.10. JOUT OC LV FAULT LIMIT ..66 15.11 OUT OC LV FAULT RESPONSE .66 15.12. OUT OC WARN LIMIT 7 15.13. OUT UC FAULT LIMIT ∴.67 15.14. OUT UC FAULT RESPONSE 67 15.15. DELETED 68 1516. DELETED ∴68 15.17 OT FAULT LIMIT 68 15.18. OT FAULT RESPONSE 画E 68 15.19. OT WARN LIMIT 68 15.20. UT WARN LIMIT 69 15.21. UT FAULT LIMIT 69 15.22 UT FAULT RESPONSE 画面面 9 15.23. VIN OV FAULT LIMIT 70 15.24 VIN OV FAULT RESPONSE 70 15.25.VNO∨ WARN LIM|T 1B面 70 15.26. VIN UV WARN LIMIT 70 15.27. VIN UV FAULT LIMIT 71 15.28. VIN UV FAULT RESPONSE 1画1 7 15.29. N OC FAULT LIMIT 71 15.30. IIN OC FAULT RESPONSE ∴72 15.31.‖ N OC WaRN L|M|T 72 15.32. POWER GOOD Signal Limits ∴72 15.321. POWER GOOD ON 2 o 2009 System Management Interface Forum, Inc Page 5 of 105 All Rights reserved 15.32.2. POWER GOOD OFF 73 15.33. POUT OP FAULT LIMIT 73 15.34 POUT OP FAULT RESPONSE 73 15.35. POUT OP WARN LIMIT 73 1536. PIN OP WARN LIMIT .74 15.37. Other Fault And Warning Responses .74 15.38. SMBALERT MASK Command 74 16. Output Voltage Sequencing Commands 75 16.1 TON DELAY 16.2 TON RISE 75 16.3. TON MAX FAULT LIMIT 75 16.4 TON MAX FAULT RESPONSE 76 16.5. TOFF DELAY 76 16.6. TOFF FALL 76 16.7 TOFF MAX WARN LIMIT 76 17. Unit Status Commands 77 17.1 STATUS BYTE 78 17.2. STATUS WORD 78 173. STATUS VOUT 面国面 79 17. 4. STATUS OUT 80 175. STATUS INPUT .80 176. STATUS TEMPERATURE 81 17.7. STATUS CML (Communications, Logic, And Memory) 。 81 17.8. STATUS OTHER 82 17.9. STATUS MER SPECIFIC 82 17.10. STATUS FANS 12 82 17.11 STATUS FanS 3 4 83 18. Reading parametric Information 84 18.1. READ VIN 84 18.2.READⅢN 国国面 84 18.3.READ∨CAP 84 184 READ VOUT .85 18.5. READ JOUT 85 186. READ TEMPERATURE n 85 18.7 READ FAN SPEED n 85 18. 8. Deleted 86 18. 9. READ DUTY CYCLE .86 18.10. READ FREQUENCY 1量 86 18.11. READ POUT 1面 86 18.12. READ PIN 1813. READ EIN 86 18.14. READ EOUT 88 19. Reserved 88 22 Reserved 1 ∴88 1. Reserved L画量日1面国面1面面 1国量面日国国量面日面.面B面国 面面 89 22. Manufacturer's Information 89 22.1 PMBUS REVISION 89 22.2. Inventory Information .89 22.2.1. MER D.………… 89 22.2.2. MER MODEL 90 22.23. MER REVISION 90 22.2.4 MER LOCATION 90 22.25. MER DATE 22.2. 6. MER SERIAL 22.27. IC DEVICE ID 90 22.28. IC DEVICE REV o 2009 System Management Interface Forum, Inc Page 6 of 105 All Rights reserved 22.3 Manufacturer Ratings 90 223.1. MER VIN MIN 91 223.2. MER VIN MAX 91 22.3.3 MFR‖NMAX 91 22.3.4. MER PIN MAⅩ 91 223.5. MER VOUT MIN 91 223.6. MER VOUT MAX 9 223.7. MFR IOUT MAX 22.38. MER POUT MAX 91 22.3. 9. MER TAMBIENT MAX 91 22.3.10. MER TAMBIENT MIN 22.3.11. MER EFFICIENCY LL 91 22.3.12. MFR EFFICIENCY HL 92 223.13. MER PIN ACCURACY 93 223.14 APP PROFILE SUPPORT 93 223.15. MFR MAX TEMP 1. 2. 3 面 94 23. User Data and configuration 94 24. Manufacturer specific Commands 95 25. Command extensions 95 25.1. MER SPECIFIC COMMAND EXT 95 25.2. PMBUS COMMAND EXT 95 APPENDIX I Command Summary 96 APPENDIX IL. Summary of changes 105 Figure 1 Bit Order Within a Byte 11 Figure 2. Conceptual View Of Possible PMBus Device Memory And Communication 18 Figure 3 Flowchart Of Conceptual Loading Operating Memory At Start ..19 Figure 4. Linear Data Format Data Bytes 21 Figure 5. VOUT MODE Command Data Byte Structure 24 Figure 6. Linear Format Data bytes Figure 7. Vid Format Data Bytes Figure 8. DIRECT Format Mode Data Bytes 27 Figure 9. Output Voltage Sensing In A T ypical Power Converter 28 Figure 10. Conceptual View Of The Application Of The VOUT SCALE LOOP Command Figure 11. Conceptual View Of How Output Voltage related Commands Are Applied 30 Figure 12. Generating READ IOUT Concept 翻国面国.国面 31 Figure 13 Status Register Map 32 Figure14. Conceptual Schematic Of Status Bits And SMBALERT#…………,,… .37 Figure 15. Interaction Of SMBALERT# And Status Registers 41 Figure 16 Packet Structure For PMBus device To Notify Host 42 Figure 17. Conceptual View Of Paging Used For A Multiple Output PMBus Device. ...........................50 Figure 18. Conceptual view Of Using Paging With a PMBus To Non -PMBus Device Adapter 50 Figure19. PAGE PLUS Command Example With Written Data And PEc……… 53 Figure 20 PAGE_ PLUS Command Example With Data To Read And PEC 53 Figure 21. Retrieving Coefficients Using PEC 59 Figure 22. Illustration Of The INTERLEAVE Command Function 61 Figure 23. SMBALERT MASK Command packet format 74 Figure 24. Retrieving The SMBALERT MASK Setting For A Given Status Register .75 Figure 23. Summary of the status registers 77 Figure 26. READ EIN Command Packet Format 87 Figure 27. READ EOUT Command Packet Format 88 Figure 24. APP PROF ILE- SUPPORT Packet EXample 94 o 2009 System Management Interface Forum, Inc Page 7 of 105 All Rights Reserved Table 1 Bit And Byte Symbols Used In this specification Table 2. Summary of The VoUt MOdE Data Byte format 24 Table 3. VID Types Supported By PMBus 26 Table 4. Voltage, Temperature And Ton MAX Faults response data byte details 38 Table 5. Current Fault Response Data Byte Details 39 Table 6. WRITE PROTECT Command data byte .46 Table 7. CAPABILITY COMMAND Data Byte Format 51 Table 8 QUERY Command returned data byte format 52 Table 9. OPERATION Data Byte Contents ∴54 Table 10 ON OFF CONFIG Data Byte 5 Table 11. INTERLEAVE Data Bytes Format 60 Table 12. FAN CoNFiG 1 2 Data byte format 62 Table 13. FAN CONFIG__4 Data Byte Format 63 Table 14 STATUS BYTE Message Contents 78 Table 15 STATUS WORD Message Contents 78 Table 16 STATUS VOUT Data Byte 79 Table 17 STATUS IOUT Data byte ,.. .80 Table18. STATUS丨 NPUT Data Byte…… 80 Table 19 STATUS TEMPERATURE Data Byte Table 20 STATUS CML Data Byte 88 11面B画 Table 21. STATUS OTHER Data Byte 82 Table 22 STATUS MFR SPECIFIC Data Byte 82 Table23. STATUS_FANS_1_2 Data Byte∴………….………………….…… 82 Table 24 STATUs FANs 3 4 Data Byte 83 Table 25 PMBus Revision Data Byte Contents .89 Table 26. APP_PROFILE SUPPORT First Data Byte Contents 93 Table 27. Command Summary.. o 2009 System Management Interface Forum, Inc Page 8 of 105 All Rights Reserved The Power Management Bus("PMBus TM")is an open standard protocol that defines a means of communicating with power conversion and other devices For more information, please see the System Management Interface Forum Web site www.powersig.org The PMBus specification is in two parts. Part I includes the general requirements, defines the transport, and defines the electrical interface and timing requirements of hardwired signals Part I, this document, describes the operation of commands, data formats fault management and defines the command language used with the PmBus This specification defines a protocol to manage power converters and a power system via communication over a digital communication bus The PMBus specification is not a definition or specification of a particular power conversion device or family of power conversion devices A specification of any individual or family of integrated circuits This specification does not address direct unit to unit communication such as analog current sharing, real-time analog or digital voltage tracking, and switching frequency clock signals a summary of the changes between this revision and revision 1.0 are shown in APPENDIX II Please send all comments by email to: questions@power SIG. org If the requirements of this specification and any of the reference documents are in conflict, this specification shall have precedence unless otherwise stated Referenced documents apply only to the extent that they are referenced The latest version and all amendments of the referenced documents at the time the power system is released to manufacturing apply Applicable documents include information that is, by extension, part of this specification o 2009 System Management Interface Forum, Inc Page 9 of 105 All Rights Reserved [A01 PMBus Power System Management Protocol, Part I, General Requirements, Transport and electrical Interface [A02 SBS Implementers Forum Version 1.1 1 1 november 1998 A03 SBS Implementers Forum Version 2.0, 3 August 2000 [AO4] Version 2.1. Philips semiconductors January 2000 [A05]| SO/EC8859-1:1998 and all corrigenda amendments published through the date of release of this specification [ Ao6 PMBus Application Profile: Server AC-DC Power Supplies [A07] PMBus Application Profile: DC-DC Converters For Microprocessor Power And Other Computer Applications A08 PMBus Application Profile: DC-DC Converters For General Purpose Use Reference documents have background or supplementary information to this specification They do not include requirements or specifications that are considered part of this document None in this revision The names of signals and parameters are given in capital letters. Underscores are used to separate words rather than embedded spaces(example: SIGNAL NAME The names of signals that are active low and parameters that are true when the value is 0 are indicated with an octothorpe(#)suffix(example: WRITE# means that the device can be written when the signal is low) All numbers are decimal unless explicitly designated otherwise Numbers explicitly identified as decimal are identified with a suffix of"d Numbers in binary format are indicated by a suffix of b. Unless otherwise indicated, all binary numbers are unsigned All signed binary numbers are twos complement Numbers in hexadecimal format are indicated by a suffix ofh 255d4FFh分11111111b o 2009 System Management Interface Forum, Inc Page 10 of 105 All Rights Reserved 【实例截图】
【核心代码】
标签：
好例子网口号：伸出你的我的手 — 分享！
小贴士
感谢您为本站写下的评论，您的评论对其它用户来说具有重要的参考价值，所以请认真填写。
- 类似“顶”、“沙发”之类没有营养的文字，对勤劳贡献的楼主来说是令人沮丧的反馈信息。
- 相信您也不想看到一排文字/表情墙，所以请不要反馈意义不大的重复字符，也请尽量不要纯表情的回复。
- 提问之前请再仔细看一遍楼主的说明，或许是您遗漏了。
- 请勿到处挖坑绊人、招贴广告。既占空间让人厌烦，又没人会搭理，于人于己都无利。
关于好例子网
本站旨在为广大IT学习爱好者提供一个非营利性互相学习交流分享平台。本站所有资源都可以被免费获取学习研究。本站资源来自网友分享，对搜索内容的合法性不具有预见性、识别性、控制性，仅供学习研究，请务必在下载后24小时内给予删除，不得用于其他任何用途，否则后果自负。基于互联网的特殊性，平台无法对用户传输的作品、信息、内容的权属或合法性、安全性、合规性、真实性、科学性、完整权、有效性等进行实质审查；无论平台是否已进行审查，用户均应自行承担因其传输的作品、信息、内容而可能或已经产生的侵权或权属纠纷等法律责任。本站所有资源不代表本站的观点或立场，基于网友分享，根据中国法律《信息网络传播权保护条例》第二十二与二十三条之规定，若资源存在侵权或相关问题请联系本站客服人员，点此联系我们。关于更多版权及免责申明参见 版权及免责申明
网友评论
我要评论