16-Jun-2014MIPI® Alliance Specification forDisplay Command Set (DCS)Version 1.2 – 16 June 2014MIPI Board Adopted 18-Jun-2014* NOTE TO IMPLEMENTERS *This document is a MIPI Specification. MIPI member companies’ rights and obligations apply to this MIPI Specification as defined in the MIPI Membership Agreement and MIPI Bylaws.Specification forDisplay Command Set (DCS)Version 1.216 June 2014MIPI Board Adopted 18-Jun-2014Further technical changes to this document are expected as work continues in the Display WorkingGroup.NOTICE OF DISCLAIMERThe material contained herein is not a license, either expressly or impliedly, to any IPR owned or controlled by any of the authors or developers of this material or MIPI®. The material contained herein is provided on an “AS IS” basis and to the maximum extent permitted by applicable law, this material is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material and MIPI hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of negligence.All materials contained herein are protected by copyright laws, and may not be reproduced, republished, distributed, transmitted, displayed, broadcast or otherwise exploited in any manner without the express prior written permission of MIPI Alliance. MIPI, MIPI Alliance and the dotted rainbow arch and all related trademarks, tradenames, and other intellectual property are the exclusive property of MIPI Alliance and cannot be used without its express prior written permission.ALSO, THERE IS NO WARRANTY OF CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THIS MATERIAL OR THE CONTENTS OF THIS DOCUMENT. IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL OR THE CONTENTS OF THIS DOCUMENT OR MIPI BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT, SPECIFICATION OR DOCUMENT RELATING TO THIS MATERIAL, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.Without limiting the generality of this Disclaimer stated above, the user of the contents of this Document is further notified that MIPI: (a) does not evaluate, test or verify the accuracy, soundness or credibility of the contents of this Document; (b) does not monitor or enforce compliance with the contents of this Document; and (c) does not certify, test, or in any manner investigate products or services or any claims of compliance with the contents of this Document. The use or implementation of the contents of this Document may involve or require the use of intellectual property rights (“IPR”) including (but not limited to) patents, patent applications, or copyrights owned by one or more parties, whether or not Members of MIPI. MIPI does not make any search or investigation for IPR, nor does MIPI require or request the disclosure of any IPR or claims of IPR as respects the contents of this Document or otherwise.Questions pertaining to this document, or the terms or conditions of its provision, should be addressed to: MIPI Alliance, Inc.c/o IEEE-ISTO445 Hoes LanePiscataway, NJ 08854Attn: Board SecretaryContents12Contents (iii)3Figures ............................................................................................................................................................ v i Tables ............................................................................................................................................................. i x 45Release History (x)1Introduction (1)61.1Scope (1)71.2Purpose (1)892Terminology (2)2.1Glossary (2)10112.2Abbreviations (4)122.3Acronyms (4)133References (5)144Display Architectures (6)155Display Functional Description (9)165.1Power Level Definition (9)175.2Gamma Curves (12)185.2.1Gamma Curve 1 (GC0) (12)195.2.2Gamma Curve 2 (GC1) (12)205.2.3Gamma Curve 3 (GC2) (13)215.2.4Gamma Curve 4 (GC3) (13)225.3Self-diagnostic Functions (14)235.3.1Register Loading Detection (14)245.3.2Functionality Detection (15)255.3.3Chip Attachment Detection (optional) (16)265.3.4Display Glass Break Detection (optional) (17)275.4Display Command Set (18)285.5Command List (19)295.6Command Accessibility (22)305.7Default Modes and Values (24)315.8Image Data Compression (27)325.8.1Display Stream Compression Transport In Command Mode (28)336Command Description (29)346.1enter_idle_mode (30)356.2enter_invert_mode (32)6.3enter_normal_mode (33)366.5enter_sleep_mode (35)386.6exit_idle_mode (36)39406.7exit_invert_mode (37)416.8exit_sleep_mode (38)426.9get_3D_control (40)436.10get_address_mode (42)6.11get_blue_channel (44)446.12get_compression_mode (45)45466.13get_diagnostic_result (47)476.14get_display_mode (48)486.15get_green_channel (50)6.16get_pixel_format (51)496.17get_power_mode (53)506.18get_red_channel (55)51526.19get_scanline (56)536.20get_signal_mode (57)6.21nop (58)546.22read_DDB_continue (59)556.23read_DDB_start (60)56576.24read_memory_continue (62)586.25read_memory_start (64)596.26set_3D_control (66)606.27set_address_mode (69)6.28set_column_address (74)616.29set_display_off (76)62636.30set_display_on (77)646.31set_gamma_curve (78)656.32set_page_address (79)666.33set_partial_columns (81)676.34set_partial_rows (85)686.35set_pixel_format (87)696.36set_scroll_area (88)706.37set_scroll_start (91)716.38set_tear_off (93)726.39set_tear_on (94)736.40set_tear_scanline (96)6.42soft_reset (100)756.43write_LUT (101)76776.44write_memory_continue (103)786.45write_memory_start (105)79Annex A Pixel-to-Byte Mapping (108)80Annex B Color Depth Conversion Look-up Tables (informative) (112)Figures8182Figure 1 Type 1 Display Architecture Block Diagram (6)83Figure 2 Type 2 Display Architecture Block Diagram (7)Figure 3 Type 3 Display Architecture Block Diagram (8)8485Figure 4 Type 1 Display Architecture Power Change Sequences (10)Figure 5 Type 2 Display Architecture Power Change Sequence (11)86Figure 6 Type 3 Display Architecture Power Change Sequence (11)87Figure 7 Gamma curve 1 (GC0) (12)8889Figure 8 Gamma Curve 2 (GC1) (12)Figure 9 Gamma Curve 3 (GC2) (13)9091Figure 10 Gamma Curve 4 (GC3) (13)92Figure 11 Register Loading Detection Flow Chart (14)93Figure 12 Functionality Detection Flow Chart (15)94Figure 13 Chip Attachment Detection Reference (16)95Figure 14 Chip Attachment Detection Flow Chart (16)96Figure 15 Display Glass Break Detection Reference (17)97Figure 16 Display Glass Break Detection Flow Chart (17)98Figure 17 Compressed Data Flow (27)99Figure 18 Compressed Data Transportation in Command Mode (28)100Figure 19 Flowchart Legend (29)101Figure 20 enter_idle_mode Example (30)102Figure 21 enter_idle_mode Flow Chart (31)103Figure 22 enter_invert_mode Example (32)104Figure 23 enter_invert_mode Flow Chart (32)105Figure 24 enter_sleep_mode Flow Chart (35)106Figure 25 exit_idle_mode Flow Chart (36)107Figure 26 exit_invert_mode Example (37)108Figure 27 exit_invert_mode Flow Chart (37)109Figure 28 exit_sleep_mode Flow Chart (39)110Figure 29 get_3D_control Flow Chart (41)111Figure 30 get_address_mode Flow Chart (43)112Figure 31 get_blue_channel Flow Chart (44)113Figure 32 get_compression_mode Flow Chart (46)114Figure 33 get_diagnostic_result Flow Chart (47)115Figure 34 get_display_mode Flow Chart (49)Figure 35 get_green_channel Flow Chart (50)116117Figure 36 get_pixel_format Flow Chart (52)Figure 37 get_power_mode Flow Chart (54)118Figure 38 get_red_channel Flow Chart (55)119120Figure 39 get_scanline Flow Chart (56)121Figure 40 get_signal_mode Flow Chart (57)122Figure 41 read_DDB_continue Flow Chart (59)123Figure 42 read_DDB_start Flow Chart (61)Figure 43 read_memory_continue Flow Chart (63)124Figure 44 read_memory_start Flow Chart (65)125126Figure 45 set_3D_control Flow Chart (68)127Figure 46 B7 Page Address Order (70)128Figure 47 B6 Column Address Order (70)129Figure 48 B5 Page/Column Addressing Order (71)Figure 49 B3 RGB Order (71)130131Figure 50 B1 Flip Horizontal (72)132Figure 51 B0 Flip Vertical (72)133Figure 52 set_address_mode Flow Chart (73)134Figure 53 set_column_address Example (74)Figure 54 set_column_address Flow Chart (75)135136Figure 55 set_display_off Example (76)137Figure 56 set_display_off Flow Chart (76)138Figure 57 set_display_on Example (77)139Figure 58 set_display_on Flow Chart (77)140Figure 59 set_gamma_curve Flow Chart (78)Figure 60 set_page_address Example (79)141Figure 61 set_page_address Flow Chart (80)142143Figure 62 set_partial_columns with set_address_mode B2 = 0 (81)144Figure 63 set_partial_columns with set_address_mode B2=1 (82)145Figure 64 set_partial_columns with set_address_mode B2 = 0 (82)146Figure 65 set_partial_columns with set_address_mode B2 = 1 (82)147Figure 66 Entering Partial Display Mode Flow Chart (83)148Figure 67 Exiting Partial Display Mode Flow Chart (84)149Figure 68 set_partial_rows with set_address_mode B4 = 0 (85)150Figure 69 set_partial_rows with set_address_mode B4=1 (86)151Figure 70 set_partial_rows with set_address_mode B4 = 0 (86)152Figure 71 set_partial_rows with set_address_mode B4 = 1 (86)153Figure 72 set_pixel_format Flow Chart (87)154Figure 73 set_scroll_area set_address_mode B4 = 1 Example (89)Figure 74 set_scroll_area set_address_mode B4 = 1 Example (89)155Figure 75 set_scroll_area Flow Chart (90)156157Figure 76 set_scroll_start set_address_mode B4 = 0 (91)158Figure 77 set_scroll_start set_address_mode B4 = 1 (92)159Figure 78 set_tear_off Flow Chart (93)160Figure 79 set_tear_on M = 0 (94)Figure 80 set_tear_on M = 1 (94)161Figure 81 set_tear_on Flow Chart (95)162163Figure 82 set_tear_scanline (96)164Figure 83 set_tear_scanline Flow Chart (97)165Figure 84 set_vsync_timing Flow Chart (99)166Figure 85 soft_reset Flow Chart (100)Figure 86 write_LUT Flow Chart (102)167168Figure 87 write_memory_continue Flow Chart (104)169Figure 88 write_memory_start Flow Chart (107)170Figure 89 Three Bits per Pixel Format to Byte Mapping (108)171Figure 90 Eight Bits per Pixel Format to Byte Mapping (109)Figure 91 Twelve Bits per Pixel Format to Byte Mapping (109)172173Figure 92 Sixteen Bits per Pixel Format to Byte Mapping (110)Figure 93 Eighteen Bits per Pixel Format to Byte Mapping (110)174175Figure 94 Twenty-four Bits per Pixel Format to Byte Mapping (111)Tables176177Table 1 Command List (19)178Table 2 Command Accessibility (22)179Table 3 Default Display Mode, Power Mode and Register Values (24)180Table 4 enter_idle_mode Memory Content vs. Display Color (30)181Table 5 Gamma Curve Selection (48)Table 6 Interface Pixel Formats (51)182183Table 7 DCS 3D Commands (67)Table 8 Gamma Curves (78)184185Table 9 LUT Color Depth Conversions (102)186Table 10 Common Color Encoding (104)187Table 11 Common Color Encoding (106)188Table 12 12-bit to 16-bit LUT Red Component Values (112)189Table 13 12-bit to 16-bit LUT Green Component Values (113)190Table 14 12-bit to 16-bit LUT Blue Component Values (114)191Table 15 12-bit, 16-bit to 18-bit LUT Red Component Values (115)192Table 16 12-bit, 16-bit to 18-bit LUT Green Component Values (116)193Table 17 12-bit, 16-bit to 18-bit LUT Blue Component Values (118)194Table 18 12-bit, 16-bit and 18-bit Colors to 24-bit Color LUT Red Component Values (119)Table 19 12-bit, 16-bit and 18-bit Colors to 24-bit Color LUT Green Component Values (121)195196Table 20 12-bit, 16-bit and 18-bit Colors to 24-bit Color LUT Blue Component Values (123)197Release History198Date Release Description2005-02-15 v1.00a Initial MIPI Alliance Board-approved release.2006-06-22 v1.01.00 Minor update with editorial corrections, reference updates andseveral bit definitions added to commands for imagemanipulation.2010-10-20 v1.02.00 Minor updates containing technical clarifications and editorialupdates.2012-04-06 v1.1 Board-approved release. Added support for Stereoscopic DisplayFormats.2014-06-18 V1.2 Board-approved release. Added support for command modedisplay stream compression.1 Introduction199200This document defines display module behavior for devices that adhere to MIPI Specifications for mobile 201device host processor, and display interfaces in an abstract, device independent way. All commands in this 202Specification, except those indicated as optional, shall be supported by display modules that adhere to MIPI 203Alliance Standard for Display Pixel Interface [MIPI01], MIPI Alliance Standard for Display Bus Interface 204[MIPI02], and MIPI Alliance Specification for Display Serial Interface [MIPI03] except as provided for in 205the individual Specifications. Stereoscopic image support is defined in MIPI Alliance Specification for 206Stereoscopic Display Formats [MIPI05].1.1 Scope207208Display commands and logical flow are within the scope of this document. In addition, to support device abstraction, several display architectures are also specified.209210Electrical specifications and interface protocols are out of scope for this document.1.2 Purpose211212This document is used by manufacturers to design products that adhere to MIPI Specifications for mobile 213device host processor and display interfaces.214Implementing the DCS Specification reduces the time-to-market and design cost of mobile devices by 215simplifying the interconnection of products from different manufacturers. In addition, adding new features 216such as larger or additional displays to mobile devices is simplified due to the extensible nature of MIPI 217Specifications.2 Terminology218219The MIPI Alliance has adopted Section 13.1 of the IEEE Standards Style Manual, which dictates use of the220words “shall”, “should”, “may”, and “can” in the development of documentation, as follows:221The word shall is used to indicate mandatory requirements strictly to be followed in order222to conform to the standard and from which no deviation is permitted (shall equals is223required to).224The use of the word must is deprecated and shall not be used when stating mandatory225requirements; must is used only to describe unavoidable situations.226The use of the word will is deprecated and shall not be used when stating mandatory227requirements; will is only used in statements of fact.228The word should is used to indicate that among several possibilities one is recommended229as particularly suitable, without mentioning or excluding others; or that a certain course230of action is preferred but not necessarily required; or that (in the negative form) a certain231course of action is deprecated but not prohibited (should equals is recommended that).232The word may is used to indicate a course of action permissible within the limits of the233standard (may equals is permitted).234The word can is used for statements of possibility and capability, whether material,235physical, or causal (can equals is able to).236All sections are normative, unless they are explicitly indicated to be informative.2.1 Glossary2372382D Mode: An operating state in which a stereoscopic-capable display is rendering one image per frame to both eyes and does not create a stereoscopic effect.2392403D Mode: An operating state in which a stereoscopic-capable display renders a stereoscopic image with a241unique view for each eye.242Bitstream: The sequence of data bytes resulting from the coding of image data. The bit stream does not243contain a header or syntax markers.244Codestream: A sequence of data bytes composed of a bitstream and any header and syntax markers necessary for decoding. The codestream boundary usually coincides with a frame boundary, but does not 245246need to do so.247Compressed Data: A sequence of data bytes composed of a bitstream and any header and syntax markers248necessary for decoding.249Display Area: The portion of a display device used to show image data.250Display Controller: A separate silicon chip, or integrated functional block in a host device, used to control251a display module. May include full-frame or partial-frame memory.252Display Device: A functional device that shows images such as a Liquid Crystal Display.253Display Driver: An integrated circuit inside a display module used to control the display device. May or 254may not integrate full or partial frame-memory.255Display Glass: Same as Display Device. Derived from the display material’s name.256Display Module:A functional module used to show an image. Can consist of a display device, display driver, additional peripheral components or circuits and a display interface.257258Display Panel: Same as Display Device.259Frame Memory: Memory integrated in a display driver or display controller in order to provide storage for 260display device refreshment. Full-frame memory provides enough storage for the full display area of a 261display device. Partial-frame memory provides only enough storage for a portion of the display area.262Frame-based: The data transfer mode that sends an entire left or right view followed by the corresponding 263right or left view, respectively.264Frame-sequential: Same as Temporal Mode.265Landscape:The horizontal dimension exceeds the vertical dimension. If square,defined by the 266manufacturer.267Landscape Scanning:The pixel writing direction from the display driver to the display in which the 268number of pixels written per line exceeds the number of lines.269Landscape/Portrait Orientation: The orientation the display is viewed by a user.270Landscape/Portrait Switchable: A display where the stereoscopic effect can be switched between 271landscape and portrait orientation.272Left View: Part of the stereoscopic image intended to be viewed by the user’s left eye.273Left-Right Order:This value defines whether the first pixel,line,or frame of 3D Mode content sent 274across the physical link is intended for viewing by the left eye or the right eye. The order may apply with 275respect to pixel-based, line-based or frame-based modes of transmission276Line-based: The data transfer mode that sends an entire left or right line followed by the corresponding 277right or left line, respectively.278Portrait: The vertical dimension exceeds the horizontal dimension. If square, defined by the manufacturer.Portrait Scanning: The pixel writing direction from the display driver to the display in which the number 279280of lines written exceeds the number of pixels per line.281Right View: Part of the stereoscopic image intended to be viewed by the user’s right eye.282Spatial: The left and right views are shown simultaneously to the viewer.283Stereoscopic Image: A pair of offset images of a scene (views) that renders content to both the left eye and 284right eye to produce the perception of depth.285Temporal Mode: A time-sequential stereoscopic image in which the left view and right view are 286alternately presented to the user and directed to the appropriate eye.287Type 1 Display Architecture:A display module architecture in which the display module includes a288display device, display driver, full-frame memory, interface registers, timing controller, non-volatile289memory and a control interface.290Type 2 Display Architecture:A display module architecture in which the display module includes adisplay device, display driver, partial-frame memory, interface registers, timing controller, non-volatile 291292memory, a control interface and a video stream interface.293Type 3 Display Architecture:Similar to the Type 2 Display Architecture except no frame memory is294present.2.2 Abbreviations295296e.g. For example (Latin: exempli gratia)i.e. That is (Latin: id est)2972.3 Acronyms298299DBI Display Bus Interface300DCS Display Command Set301DPI Display Pixel Interface302DSI Display Serial Interface3 References303304[MIPI01] MIPI Alliance Standard for Display Pixel Interface (DPI-2), version 2.00, MIPI Alliance, 305Inc., 15 September 2005.306[MIPI02] MIPI Alliance Standard for Display Bus Interface (DBI-2), version 2.00, MIPI Alliance, Inc., 29 November 2005.307308[MIPI03] MIPI Alliance Specification for Display Serial Interface (DSI), version 1.2,309MIPI Alliance, Inc., In Press.[MIPI04] MIPI Alliance Specification for Device Descriptor Block (DDB), version 1.0,310311MIPI Alliance, Inc., 29 October 2008.312[MIPI05] MIPI Alliance Specification for Stereoscopic Display Formats (SDF), version 1.0,313MIPI Alliance, Inc., 14 March 2012.314[VESA01] Display Stream Compression Standard, v 1.1. Published by VESA ,315In Press, 2014.4 Display Architectures316 The display module shall be based on Type 1, Type 2 or Type 3 display architecture. 317 The Type 1 Display Architecture should consist of the following functional blocks:318 Display Device. The Display Device is used to show image data.319 Display Driver. The Display Driver may be one or more devices used to drive the display device. 320 Frame memory. Frame Memory holds compressed or uncompressed image data depending upon 321 whether compression is required for the display or not. Frame memory can be integrated in the 322 display driver.323 Registers. Registers are used to configure display behavior and identification information. 324 Registers can be integrated in the display driver.325 Timing Controller. The Timing Controller provides timing signals to control the display and326 display driver based on configuration information. The Timing Controller can be integrated in the 327 display driver.328 Non-volatile Memory. Non-volatile Memory is used to store default register and configuration 329 values. Non-volatile memory can be integrated in the display driver.330 Control Interface. The Control Interface is the interface between the host processor and the display 331 driver. The Control Interface can be integrated in the display driver.332 Display Driving Circuit. The Display Driving Circuit converts timing signals and voltages to 333 signals appropriate to drive the display device.334 Decoder (optional). The Decoder decodes compressed data from the host processor and generates 335 pixel data to pass to the display device. The decoder block is optional as compression is dependent 336 upon system requirements. The Decoder can be integrated in the display driver.337 Power Supply. The Power Supply converts system voltages to levels usable by the display device 338 and display driver. The Power Supply can be integrated in the display driver.339Display Interface340 Figure 1 Type 1 Display Architecture Block Diagram341The Type 2 Display Architecture should consist of the following functional blocks:342 Display Device. The Display Device is used to show image data.343 Display Driver. The Display Driver may be one or more devices used to drive the display device. 344 Partial-frame Memory. Partial-frame Memory holds compressed or uncompressed image data 345 depending upon whether compression is required for the display or not. Partial-frame memory can 346 be integrated in the display driver.347 Registers. Registers are used to configure display behavior and identification information. 348 Registers can be integrated in the display driver.349 Timing Controller. The Timing Controller provides timing signals to control the display and350 display driver based on configuration information. The Timing Controller can be integrated in the 351 display driver.352 Non-volatile memory. Non-volatile Memory is used to store default register and configuration 353 values. Can be integrated in the display driver.354 Control Interface. The Control Interface is the interface between the host processor and the display 355 driver. The Control Interface can be integrated in the display driver.356 Display Driving Circuit. The Display Driving Circuit converts timing signals and voltages to 357 signals appropriate to drive the display device.358 Decoder (optional). The Decoder decodes compressed data from the host processor and generates 359 pixel data to pass to the display device. The decoder block is optional as compression is dependent 360 upon system requirements. The Decoder can be integrated in the display driver.361 Power Supply. The Power Supply converts system voltages to levels usable by the display device 362 and display driver. The Power Supply can be integrated in the display driver.363 Video Stream Interface. The Video Stream Interface receives video image data and timing signals 364 from the host processor.365Display Interface366 Figure 2 Type 2 Display Architecture Block Diagram367 The Type 3 Display Architecture should consist of the following functional blocks:368Display Device. The Display Device is used to show image data.369 Display Driver. The Display Driver may be one or more devices used to drive the display device. 370 Registers. Registers are used to configure display behavior and identification information. 371 Registers can be integrated in the display driver.372 Timing Controller. The Timing Controller provides timing signals to control the display and373 display driver based on configuration information. The Timing Controller can be integrated in the 374 display driver.375 Non-volatile memory. Non-volatile Memory is used to store default register and configuration 376 values. Can be integrated in the display driver.377 Control Interface. The Control Interface is the interface between the host processor and the display 378 driver. The Control Interface can be integrated in the display driver.379 Display Driving Circuit. The Display Driving Circuit converts timing signals and voltages to 380 signals appropriate to drive the display device.381 Decoder (optional). The Decoder decodes compressed data from the host processor and generates 382 pixel data to pass to the display device. The decoder block is optional as compression is dependent 383 upon system requirements. The Decoder can be integrated in the display driver.384 Power Supply. The Power Supply converts system voltages to levels usable by the display device 385 and display driver. The Power Supply can be integrated in the display driver.386 Video Stream Interface. The Video Stream Interface receives video image data and timing signals 387 from the host processor.388Display Interface389 Figure 3 Type 3 Display Architecture Block Diagram390 In all architecture types, it is assumed the power supply is under the control of the display driver. 391 The Display Command Set is used through the mentioned control interface.392。
第一章1.获得天体信息的渠道：电磁辐射、宇宙线、中微子、引力波2.电磁辐射根据波长由长到短可分为：射电、红外、光、紫外、X射线和γ射线等波段3.电磁辐射由光子构成，光子能量与频率（或颜色）有关：频率越高（低），能量越高（低）4.黑体：能吸收所有外来辐射（无反射）并全部再辐射的理想天体5.黑体辐射波长与温度之间的关系;λT=0.29（cm K）6.高温黑体主要辐射短波，低温黑体主要辐射长波7.当电子从高能态跃迁到低能态时，原子释放光子，产生发射线，反之，产生吸收线8.谱线红移（蓝移）远离（接近）观测者辐射源发出的电磁辐射波长变长（短），称为谱线红移（蓝移）9.恒星距离的测量：三角视差、周年时差（要会计算）（三角测距法通常只适用于近距离的恒星）10.怎样测量周年是视差？通过测量天体在天球上（相对于遥远背景星）相隔半年位置的变化而测得11.怎样发现周围行星测量它们的距离？1.亮度2.恒星的自行较大rge separation in binary12.恒星大小的测定方法掩食法、间接测量法（通过测量恒星的光度和表面温度T就可以得到它的半径R）13.根据恒星的体积大小分类：超巨星R~100-1000个太阳半径巨星R~10-100个太阳半径矮星R~太阳半径14.恒星的光度和亮度：光度：天体在单位时间内辐射的总能量，是恒星的固有量亮度：在地球上单位时间单位面积接收的天体的辐射量15.视星等的种类（视星等的星等值越大，视亮度越低）根据测量波段的不同，分为：目视星等、照亮星等、光电星等按波段测量得到的行的称为热星等16.恒星的温度和颜色恒星的颜色反映了恒星的表面温度的高低，温度越高（低）颜色越蓝（红）（可根据波长和温度的关系推出此结论）17.赫罗图（自己看课件）18.双星：由在彼此引力作用下以椭圆互相绕转的两颗恒星组成的双星系统19.双星系统的质心以直线运动，但每一颗子星的运动轨迹是波浪形的，如天狼星20.不同质量的恒星在赫罗图上的分布高质量高温度的恒星明亮且高温，位于主序带的上部，低质量的恒星黯淡且低温位于主序带的下部第二章1.太阳的能源化学反应2H+O----HO+E 2引力收缩2.中微子中微子是一种不带电、质量极小的亚原子粒子，它几乎不与任何物质发生相互作用3.恒星的能量传输的三种形式辐射、传导、对流（对流不仅传递能量，还起着混合物质的作用太阳核心区产生的能量主要通过辐射与对流向外传递）第三章恒星主序星的演化（自己看课件）．第四章4.致密星：白矮星、中子星、黑洞5.白矮星位于赫罗图主序带的左下方结构：质量为0.2~1.1个太阳质量（平均为0.6个太阳质量）半径为5*10^8~10^9cm自转周期P大于等于10sec6.中子星的形成高质量恒星内部的和反应过程在恒星中心的Fe核；Fe核坍缩形成中子星，超新星爆发7.中子星的质量上限中子星的质量越大，半径越小；极限质量为2~3个太阳质量8.黑洞周围时空弯曲理论上黑洞并不一定必须是极高密度的天体，而只是必须致密到足以束缚住光在与而致密的天体附近，光线弯曲的程度度越大9.Kerr黑洞靠近黑洞处的时空不可抗拒的扭曲呈旋涡状黑洞并不是在固定的外部空间中转动的陀螺，而是拖曳着整个时空同它一起转动10.黑洞无毛发定理黑洞几乎不保持形成它的物质所具有的任何复杂性质，它保持的物理量只有质量、角动量和电荷第五章1.星际介质包括星际气体、星际尘埃、宇宙线与星际磁场2.星际气体主要由H构成，3.在不同环境下H的存在方式不一样（HI区、HII区、\分子云）4.电离H云的观测——发射星云被高温恒星的紫外辐射电离的星际物质，也称为HII区星际吸收线星际气体低温，产生窄吸收线；星际吸收线的位置反映了星云的运动中性H云的观测——H原子21厘米谱线是研究银河系大尺度结构的重要手段星际分子的观测：当星际介质的温度很低时，星际分子开始形成；星际分子分布在大的、冷的、致密的暗云中星际红化5.星际尘埃对星光的散射随波长的变化而不同，对蓝光散射较多而对红光散射较少，因而造成星光颜色偏红第六章1)银河系的结构银河系是一个包含2*10^11颗恒星的、具有的盘状星系主要成分：银盘、核球、银晕、银冕2)星族星族I恒星年轻的、富金属恒星，主要位于和银盘中，绕银心作圆轨道运动星族II恒星年老的、贫金属恒星，主要位于银晕和核球中，以银心作中心球对称分布绕银心作无规则的椭圆轨道运动3)不同星族恒星的轨道运动特征星系盘内的恒星绕银心做规则的圆轨道运动晕中的恒星绕银心作高偏心率的椭圆轨道运动，且轨道取向是随机的4)银河系的转动——较差转动在太阳附近，距离银心越远，转动速度越小测量方法：测量恒星和气体云谱线的多普勒位移（视向速度）随银经的变化；太阳附近恒星视向速度（或自行）的周期性变化（在太阳周围360度的范围内，恒星谱线唯一表现出周期性的蓝移和红移）5)旋臂的理论解释a.旋臂不是物质臂，表征旋臂的主要是年轻的天体b.密度波理论：旋臂是密度波的表现：旋臂——恒星形成c.自传播恒星形成理论：恒星形成——旋臂对银河系，两种效果可能同时起作用，密度波建立旋臂的基本结构，超新星爆发进一步改变旋臂的形态6)银心在人马座方向，核球呈椭球形；辐射主要来自年老的星族I天体红外和射电辐射收到星际消光的影响较小，是研究银心的主要途径7)银晕a.球状星云年老的星族II恒星，以银心为中心球状分布b.热气体c.暗物质（暗物质的特征：在所有波段都不产生辐射，仅有引力作用）第七章1.哈勃定律：由星系谱线红移得到的星系退行速度V与星系的距离D成正比，称为哈勃定律V=H*D 其中哈勃常数H=7.2+_7 kns^-1Mpc 002.哈勃定律的意义：反映了宇宙的膨胀3.星系的哈勃分类根据星系形态的不同，哈勃首先提出星系可以分为：椭圆星系、透镜状星系、旋涡星系、棒状星系和不规则星系星系的演化：4.第八章1.活动星系（指表现出强烈的活动性的星系）在观测上的分类：射电星系、塞弗特星系、蝎虎天体、类星体2.引力透视——引力场源对位于其后的背景天体发出的电磁辐射所产生的会聚火多重成像效应。
<< RS-W1616分析系统 >>帮助说明如何...RS-W1616低应变基桩动测分析系统，是武汉岩海公司最近推出的基于Windows的低应变动测分析软件的试用版本，主要对采集回来的数据进行室内分析、打印等工作，它完全兼容了K1616和K1616(P)的所有功能，同时它基于Windows操作系统，有着更优秀的特点：1、友好的Windows界面，全中文菜单，鼠标操作；2、波形编辑、分析、操作简单快捷；3、强大的打印功能；4、图形拷贝方便；5、外挂实用工具。
系统的基本框架构成：1、菜单：是进行波形编辑、分析、拷贝、打印等功能操作；2、工具条：是菜单的快捷操作方式，将鼠标光标置于工具条按钮片刻，便出现相应的功能说明，用鼠标左键点击按钮，便可对当前通道波形进行相应的功能操作；3、波形显示区：波形显示、编辑、分析；4、文件面板：位于波形区左边，主要用来快速选择文件类型和打开文件；5、标尺：位于波形区下面，显示水平刻度；6、状态栏：位于系统的最下面，用于显示选择菜单项的说明和键盘的按键盘状态,以及显示当前通道的输出信息，包括幅值、时间、桩长、波速等。
几个主要说明：1、CH1、CH2、CH3、CH4：分别表示第1、2、3、4道信号；2、选择：以下所说的“选择”表示在相应项上点击鼠标左键；3、快捷菜单：波形显示区里点击鼠标右键出现的菜单；4、通道选择：在波形显示区中，用鼠标左键点击相应的通道波形，当前通道即被置亮；5、定时线移动：即波形区中的黄色的竖虚线，将鼠标光标移到当前通道，按下鼠标左键并移动鼠标（或键盘左右箭头键、Ctrl+左右箭头键）；6、波形放大、移动的操作：包括线性放大、指数放大、左右移动和上下移动等，首先用鼠标选择相应的菜单项或工具栏按钮，使工具条上的相应按钮处于下压状态，再移动鼠标光标到当前通道，此时光标将变为上下箭头或左右箭头，按下鼠标左键，然后上下或左右移动鼠标，然后松开鼠标左键；7、选择“文件/打开”：表示从主菜单中选择“文件”菜单，然后在“文件”的子菜单中选择“打开”子菜单，其它也一样；8、热键：菜单项右边的按键标记，如“Ctrl+O”表示同时按下键盘的“Ctrl”和“O”键，这时将弹出文件打开对话框，相当于用鼠标选择“文件/打开”菜单项；9、某菜单项或工具按钮变灰表示该功能在当前状态下无效。
