IMM User Guide
Windows输入法编程接口
Windows输入法编程接口Windows9x系统下汉字输入法的基本原理Windows系统下汉字输入法实际上是将输入的标准ascii字符串按照一定的编码规则转换为汉字或汉字串，进入到目的地。
由于应用程序各不相同，用户不可能自己去设计转换程序，因此，汉字输入自然而然落到WINDOWS系统管理中。
一、输入法与系统的关系键盘事件应用程序｜｜Windows的USER.EXE｜输入法管理器｜输入法系统的键盘事件有windows的user.exe软件接收后，user.exe在将键盘事件传导输入法管理器(Input Method Manager,简称IMM)中，管理器再将键盘事件传到输入法中，输入法根据用户编码字典，翻译键盘事件为对应的汉字(或汉字串)，然后再反传到user.exe中，user.exe再将翻译后的键盘事件传给当前正运行的应用程序，从而完成汉字的输入。
二、汉字输入法的组成微软Windows9x系统中汉字输入法的名称是"Input Method Editor" ,简称IME,输入法的程序名称为:*.ime,数据文件名称为*.MB,即通常说的输入法编码表(字典).实际上IME文件是一个动态连接库程序（DLL），它与dll文件没有区别，只是名称不同而已。
一般汉字输入法都由三个窗口组成:状态窗口（Status Windows)-显示当前的输入法状态（中文还是英文等站环信息）；编码输入窗口(Composition Windows)-显示当前击键情况；汉字选择窗口(Candidates Windows)-列出当前编码的全部汉字(串),供用户选择或查询。
上述三个窗口由基本的用户接口（User Interface ）函数管理着。
现在我们用Dumpbin.exe打开微软提供的拼音输入法（WINDOWS\SYSTEM\WINPY.IME）看看它有什么组成（这里一WINDOWS98为例，并假定windows系统安装在c:盘下）：C:\Dumpbin c:\windows\system\winpy.imeMicrosoft (R) COFF Binary File Dumper Version 6.00.8168Copyright (C) Microsoft Corp 1992-1998. A ll rights reserved.Dump of file WINPY.IMEFile T ype: DLL ／／IME 实际为dll程序Section contains the following exports for WINPY.ime0 characteristics34A37323 time date stamp Fri Dec 26 17:04:35 19970.00 version1 ordinal base19 number of functions //共有１９个函数19 number of names // 对应１９个名称ordinal hint RVA name1 0 0000A010 CandWndProc //"选择汉字窗口"注册函数2 1 0000E750 CompWndProc //"输入编码窗口"注册函数3 2 0000FB50 ImeConfigure //配置当前ime参数函数4 3 0000FEC0 ImeConversionList//将字符或字符串转换成目标字符5 4 0000FFA0 ImeDestroy //退出当前使用的IME6 5 000030D0 ImeEnumRegisterWord7 6 0000FFB0 ImeEscape //应用软件访问输入法的接口函数.8 7 00003080 ImeGetRegisterWordStyle9 8 0000E9A0 ImeInquire //启动并初始化当前IME输入法10 9 0000A800 ImeProcessKey //IME输入键盘事件管理函数11 A 00002C20 ImeRegisterWord //向输入法字典注册字符串12 B 000109A0 ImeSelect //启动当前IME输入法13 C 000109E0 ImeSetActiveContext //设置当前的输入处于活动状态.14 D 0000C850 ImeSetCompositionString 由应用程序设置输入法编码15 E 0000AEE0 ImeT oAsciiEx //将输入的键盘事件转换为汉字编码事件16 F 00002F40 ImeUnregisterWord //删除被注册的字符串.17 10 0000CA90 NotifyIME //IME事件管理函数18 11 00005160 StatusWndProc //状态窗口注册函数19 12 00002350 UIWndProc //用户界面接口函数Summary5000 .ShareDa7000 .data2000 .idata1000 .rdata3000 .reloc5000 .rsrc2000 .sgroup18000 .text从上述可以看出，IME程序共有１９个出口函数组成，每一个函数都有特定的格式，它们担负着与windows 系统传递信息的作用，这些函数是供Windows系统调用的。
联想服务器IMM运维管理指南
联想服务器IMM运维管理指南Integrated Management Module II (IMM2) 基本操作（远程管理端口）目录一、登陆IMM远程管理界面 (3)1. 设置固定的IMM远程管理口IP地址登陆 (4)2. 临时登陆 (7)3. 在Windows操作系统中，通过带内接口登陆 (9)二、IMM管理界面简介 (11)三、IMM常用操作说明 (37)1. 查看、导出日志及熄灭日志检查指示灯 (37)2. 微码刷新 (43)3. 远程终端 (65)一、登陆IMM远程管理界面找到服务器背面的IMM远程管理口，一般会标记为”IMM”或者有一个扳手型的标志，参考《认识您的System X服务器》（知识库编号：154325）。
在System x3650 M5等主流型服务器上有单独的IMM远程管理口。
在System x3250 M5等低端型服务器上IMM远程管理口与普通网口复用。
IMM远程管理的默认登陆用户名及密码为：用户名：USERID密码：PASSW0RD（数字0）1. 设置固定的IMM远程管理口IP地址登陆开机看到Lenovo System x Logo时按F1键进入BIOS界面，进入System Settings。
再进入Integrated Management Module。
进入Network Configuration设置IMM远程管理口的IP地址。
注：如果IMM无法登陆或者发生问题需要恢复，可以选择”Reset IMM to Defaults”恢复IMM默认设置（包括IP地址及用户），或者选择”Reset IMM”重启IMM功能。
在BIOS中恢复或重启IMM可能会出现数分钟操作无响应的情况，风扇也会全速转动。
对于有独立IMM远程管理口的System x机型，X3650M5的第一项”Network Interface Port”为"Dedicated"；对于共享网口的机型，该项为"Shared"，一般不需要做改动。
膝关节支撑器使用说明书
Knee CrutchInstructions for UseProduct No. F-KCP80028231Version BENGLISH (3)中文简体 (18)DANSK (34)NEDERLANDS (49)SUOMI (65)FRANÇAIS (80)DEUTSCH (96)ΕΛΛΗΝΙΚΑ (113)ITALIANO (131)日本語版 (147)한국어 (162)NORSK (177)POLSKI (192)PORTUGUÊS (209)ROMÂNESC (225)РУССКИЙ (241)SRPSKI (259)SLOVENSKY (275)SLOVENŠČINA (291)ESPAÑOL (306)SVENSKA (322)TURK (338)IMPORTANT NOTICESPrior to using this or any other type of medical apparatus with apatient, it is recommended that you read the Instructions for Use andfamiliarize yourself with the product.•Read and understand all warnings in this manual and on the device itself prior to use with a patient.•The symbol is intended to alert the user to important procedures or safety instructions regarding the use of this device.The symbol on the labels is intended to show when the IFU should be referenced for use.•The techniques detailed in this manual are onl y manufacturer’s suggestions. The final responsibility for patient care with respect to thisdevice remains with the attending physician.•Device function should be checked prior to each usage.•This device should only be operated by trained personnel.•All modifications, upgrades, or repairs must be performed by an authorized specialist.•Keep this manual available for future reference.•Any serious incident that has occurred in relation to the device should be reported to the manufacturer and the competent authority listed in this document.Knee Crutch (F-KCP)1General Information (6)1.1Copyright Notice: (6)1.2Trademarks: (6)1.3Contact Details: (7)1.4Safety Considerations: (7)1.4.1Safety hazard symbol notice: (7)1.4.2Equipment misuse notice: (7)1.4.3Notice to users and/or patients: (7)1.4.4Safe disposal: (7)1.5Operating the system: (8)1.5.1Applicable Symbols: (8)1.5.2Intended User and Patient Population: (9)1.5.3Compliance with medical device regulations: (9)1.6EMC considerations: (9)1.7EC authorized representative: (9)1.8Manufacturing Information: (10)2System (10)2.1System components Identification: (10)2.2Product Code and Description: (10)2.3List of Accessories and Consumable Components Table: (11)2.4Indication for use: (11)2.5Intended use: (11)2.6Residual risk: (11)3Equipment Setup and Use: (12)3.1Prior to use: (12)3.2Setup: (12)3.3Device controls and indicators: (13)3.4Storage, Handling and Removal Instructions: (13)3.4.1Storage and Handling: (13)3.4.2Removal Instruction: (13)3.5Troubleshooting Guide: (13)3.6Device Maintenance: (13)4Safety Precautions and General Information: (14)4.1General Safety Warnings and Cautions: (14)4.2Product Specifications: (15)4.3Sterilization Instruction: (15)4.4Cleaning and Disinfection Instruction: (16)5List of Applicable Standards: (16)1General InformationAMATECH Corporation is a subsidiary of Allen Medical Systems, Inc. which is asubsidiary of Hill-Rom, Inc. (NYSE: HRC), a leading worldwide manufacturer and provider of medical technologies and related services for the health care industry.As an industry leader in patient positioning, our passion is improving patientoutcomes and caregiver safety, while enhancing our customers' efficiency. Our inspiration comes from providing innovative solutions to address our customers' most pressing needs. We immerse ourselves in our customers' world, to better address these needs and the daily challenges of their environment. Whether developing a solution to address patient positioning challenges or creating a system to offer safe and effective surgical site access for the surgical team, we are committed toproviding products of exceptional value and quality.1.1Copyright Notice:Revision© 2019 Allen Medical Systems Inc. ALL RIGHTS RESERVED.No part of this text shall be reproduced or transmitted in any form or by anymeans, electronic or mechanical, including photocopying, recording, or by any information or retrieval system without written permission from Allen MedicalSystems, Inc. (Allen Medical).The information in this manual is confidential and may not be disclosed to thirdparties without the prior written consent of Allen Medical.1.2Trademarks:Trademark information can be found in /pages/terms-conditions.Product may be covered by one or more patents. Please consult listing at/patents for any patent(s).1.3Contact Details:For complains or ordering information, please contact your supplier and refer to the catalog. All modifications, upgrades, or repairs must be performed by an authorized specialist.1.4Safety Considerations:1.4.1Safety hazard symbol notice:DO NOT USE IF PRODUCT SHOWS VISIBLE DAMAGE AND MATERIALDEGRADATION.1.4.2Equipment misuse notice:Do not use product if package is damaged or unintentionally opened before use.All modifications, upgrades, or repairs must be performed by an authorized specialist.1.4.3Notice to users and/or patients:Any serious incident that has occurred in relation to the device should be reported using the contact details provided in section 1.3 of this Instruction for Use and to the competent authority of the Member State in which the user and/or patient is established.Note: Refer to the surgical table manufacturer's user guide for instructions on use.Always refer to the surgical table manufacturer’s weight limits.NEVER EXCEED THE WEIGHT CAPACITY OF THE OPERATING ROOM TABLE1.4.4Safe disposal:Customers should adhere to all federal, state, regional, and/or local laws and regulations as it pertains to the safe disposal of medical devices and accessories.If in doubt, the users of the device shall first contact their supplier for guidance on safe disposal protocols.1.5Operating the system:1.5.1Applicable Symbols:Symbol used Description ReferenceIndicates the device is a medical device MDR 2017/745Indicates the medical device manufacturer EN ISO 15223-1Indicates the manufacturer’s serial number.The device serial number is encoded as1YYWWSSSSSSS.∙YY indicates the year of manufacture. i.e.118WWSSSSSSS where 18 represents theyear 2018.∙WW indicates the number of themanufacturing week per a standard shopcalendar. (Leading zeros included.)∙SSSSSSS is a sequential unique number.EN ISO 15223-1Indicates the medical device Global Trade Item Number 21 CFR 830 MDR 2017/745Indicates the date when the medical devicewas manufacturedEN ISO 15223-1Indicates the manufacturer’s lot code usingthe Julian Date yyddd, where yy indicates thelast two digits of the year and ddd indicatesthe day of the year. i.e. April 4th, 2019 would berepresented as 19094.EN ISO 15223-1Indicates the manufacturer’s cataloguenumberEN ISO 15223-1Indicates the need for the user to consult theinstructions for use for important cautionaryinformation such as warnings and precautionsEN ISO 15223-1Indicates the device do not contain naturalrubber or dry natural rubber latexEN ISO 15223-1Indicates the authorized representative in theEN ISO 15223-1European CommunityIndicates the Medical Device complies toMDR 2017/745REGULATION (EU) 2017/745Indicates a Warning IEC 60601-1Intended to show when the IFU should bereferenced for use EN ISO 15223-11.5.2Intended User and Patient Population:Intended User: Surgeons, Nurses, Doctors, Physicians and OR healthcareprofessionals involved in the device intended procedure. Not intended for Laypersons.Intended Populations:This device is intended to be used with patients that do not exceed the weight in the safe working load field specified in the product specification section 4.21.5.3Compliance with medical device regulations:This product is a non-invasive, Class I Medical Device. This system is CE-marked according to Annex VIII, Rule 1, of the Medical DeviceRegulations (REGULATION (EU) 2017/745)1.6EMC considerations:This is not an electromechanical device. Therefore, EMC Declarations are not applicable.1.7EC authorized representative:HILL-ROM SASB.P. 14 - Z.I. DU TALHOUET56330 PLUVIGNERFRANCETEL: +33 (0)2 97 50 92 121.8 Manufacturing Information:ALLEN MEDICAL SYSTEMS, INC. 100 DISCOVERY WAY ACTON, MA 01720 USA800-433-5774 (NORTH AMERICA) 978-266-4200 (INTERNATIONAL)2 System2.1 System components Identification:2.2 Product Code and Description:F-KCP - Knee Crutch, PairBootPadHandleClamp2.3List of Accessories and Consumable Components Table:The following list are accessories and components that may be used with thisdevice.Note: Consult the corresponding IFU for the products mentioned in the above table.2.4Indication for use:The Knee Crutch is used in a variety of short surgical procedures including, but not limited to cystoscopy surgery. These devices are capable of being used with a broad patient population as determined appropriate by the caregiver or institution.2.5Intended use:The Knee Crutch is designed to position and support the patient’s lower leg and upper leg in a variety of short surgical procedures including, but not limited to cystoscopy surgery. These devices are intended to be used by healthcare professionals within the Operating Room setting.2.6Residual risk:This product complies with relevant performance, safety standards. However, user or patient harm from misuse, device damage, function or mechanical hazards cannot be completely excluded.3Equipment Setup and Use:3.1Prior to use:a.Inspect the product looking for any visible damage or sharp edges that couldbe caused by a drop or impact during storage.b.Make sure product has been properly cleaned and disinfected and wiped dryprior to each use.3.2Setup:a.Place patient on table in a comfortable position.b.Mount the Knee Crutch into an adjustable clamp located adjacent to thepatient’s hip joint.c.Place Knee Crutch into the desired amount of abduction, then lock clampssecurely.d.Once the Knee Crutches are located to the desired position of the patient’scalves and height is set approximately, tighten Lock Handle on the KneeCrutch.e.Ensure that the Knee Crutch pads are in place and arranged properly. TheKnee Crutch straps should be out of the way.f.If the patient is anesthetized, obtain adequate help to place both legs intothe Knee Crutches simultaneously; this significantly reduces risk of patientinjury.g.Adjust the Knee Crutch position by placing a supporting hand near the mountunderneath the Knee Crutch. Loosen the Knee Crutch Lock Handle, and railclamp. Adjust crutch height, rotation, lithotomy angle, andabduction/adduction. Align the knee, hip and opposing shoulder. Retightenthe Knee Crutch Lock Handle, and rail clamp.h.Ensure that all clamps are securely locked.i.Secure the Knee Crutch straps. Avoid tightening these straps against the leg.You should be able to slip your finger between the leg and strap at thetightest point. If it is necessary to restrain the leg more securely, adequatepadding should be applied between the straps and the leg.j.Check to ensure that no undue pressure is being applied to the leg. Do not permi t anyone or anything to lean on the patient’s leg at any time.3.3Device controls and indicators:The indicators below are placed on the sole of each boot.This Symbol represent the patient‘s right foot.This Symbol Represent the Patient’s left foot.3.4Storage, Handling and Removal Instructions:3.4.1Storage and Handling:The product should be stored in a clean and safe environment to prevent product damage. See storage Specifications under Product Specification section.3.4.2Removal Instruction:a.Remove the Clamp handle from the O.R. table rail.b.Remove the Knee crutches from the Tri Clamp.c.Remove the Tri Clamp from the side rail.3.5Troubleshooting Guide:This device does not have a troubleshooting guide. For technical support user of the device shall first contact his or her supplier.3.6Device Maintenance:Make sure that all labels are installed and can be read. Replace labels asnecessary by using a plastic scraper to remove the label. Use an alcohol wipe to remove any adhesive residue.Contact us if you need to repair or replace the device by using the information from the contact details section (1.3).4Safety Precautions and General Information:4.1General Safety Warnings and Cautions:WARNING:a.Do not use if product shows visible damage.b.Prior to using this device, please read the instructions for equipment set up anduse. Familiarize yourself with the product before application on a patient.c.To prevent patient and/or user injury and/or equipment damage, examine thedevice and surgical-table side rails for potential damage or wear prior to use. Do not use the device if damage is visible, if parts are missing or if it does not function as expected.d.To prevent patient and/or user injury and/or equipment damage, verify thedevice attaching clamps completely touch the table-side rails and are firmly in place. Test the locking mechanism to ensure no movement when elevated or pushed.e.The patient's toes may extend beyond the end of the stirrup boot.f.The product must be used with compatible clamps.g.Check for patient contact pressure points and consult the physician before use.h.Only use approved pad.i.Ensure the patient's legs are secure in the boot prior to adjusting.CAUTION:a.Do not raise thigh closer to torso than 90º as patient may experience nervedamage.b.To prevent patient and/or user injury and/or equipment damage: allmodifications, upgrades, or repairs must be performed by an Allen authorizedspecialist. Failure to comply may void warranty.c.Do not exceed safe working load shown in the product specification table.4.2Product Specifications:Note: Consult the corresponding IFU for the products mentioned in the above table.4.3Sterilization Instruction:This device is not intended to be sterilized. Equipment damage may occur.4.4Cleaning and Disinfection Instruction:WARNING:∙Do not use bleach or products that contain bleach to clean the device. Injury or equipment damage can occur.∙After each use, clean the device with alcohol-based wipes.∙Do not put the device into water. Equipment damage can occur.∙Use a cloth and a quaternary ammonium disinfecting/cleaning solution to clean and disinfect the device.∙Read and follow the manufacturer’s recommendation for low-level disinfection.∙Read and follow the cleaning product’s instructions. Use caution in areas where liquid can get into the mechanism.∙Wipe the device with a clean, dry cloth.∙Make sure that the device is dry before you store it or use it again.CAUTION: DO NOT IMMERSE PADS IN ANY LIQUIDCAUTION: DO NOT USE BLEACH OR PHENOLICS ON PADS5List of Applicable Standards:Sl. no Standards Description1.EN 62366-1Medical devices - Part 1: Application of usability engineering to medical devices2.EN ISO 14971 Medical devices- Application of risk management to medical devices.3.EN 1041 Information supplied by the manufacturer of medical devices4.EN ISO 15223-1 Medical devices - Symbols to be used with medical device labels, labelling and information to be supplied - Part 1: General requirements5.EN ISO 10993-1 Biological evaluation of medical devices - Part 1: Evaluation and testing within a risk management process6.IEC 60601-2-46 Medical electrical equipment - Part 2-46: Particular requirements for the basic safety and essential performance of operating tables7.ISTA International Safe Transit Association standards for package testingKnee Crutch使用说明产品编号 F-KCP80028231Version B重要声明将本设备或其他类型的医疗仪器用于患者之前，建议您先阅读本《使用说明》并熟悉该产品。
Windows输入法编程接口
Windows输入法编程接口Windows9x系统下汉字输入法的基本原理Windows系统下汉字输入法实际上是将输入的标准ascii字符串按照一定的编码规则转换为汉字或汉字串，进入到目的地。
由于应用程序各不相同，用户不可能自己去设计转换程序，因此，汉字输入自然而然落到WINDOWS系统管理中。
一、输入法与系统的关系键盘事件应用程序｜｜Windows的USER.EXE｜输入法管理器｜输入法系统的键盘事件有windows的user.exe软件接收后，user.exe在将键盘事件传导输入法管理器(Input Method Manager,简称IMM)中，管理器再将键盘事件传到输入法中，输入法根据用户编码字典，翻译键盘事件为对应的汉字(或汉字串)，然后再反传到user.exe中，user.exe再将翻译后的键盘事件传给当前正运行的应用程序，从而完成汉字的输入。
二、汉字输入法的组成微软Windows9x系统中汉字输入法的名称是"Input Method Editor" ,简称IME,输入法的程序名称为:*.ime,数据文件名称为*.MB,即通常说的输入法编码表(字典).实际上IME文件是一个动态连接库程序（DLL），它与dll文件没有区别，只是名称不同而已。
一般汉字输入法都由三个窗口组成:状态窗口（Status Windows)-显示当前的输入法状态（中文还是英文等站环信息）；编码输入窗口(Composition Windows)-显示当前击键情况；汉字选择窗口(Candidates Windows)-列出当前编码的全部汉字(串),供用户选择或查询。
上述三个窗口由基本的用户接口（User Interface ）函数管理着。
现在我们用Dumpbin.exe打开微软提供的拼音输入法（WINDOWS\SYSTEM\WINPY.IME）看看它有什么组成（这里一WINDOWS98为例，并假定windows系统安装在c:盘下）：C:\Dumpbin c:\windows\system\winpy.imeMicrosoft (R) COFF Binary File Dumper Version 6.00.8168Copyright (C) Microsoft Corp 1992-1998. All rights reserved.Dump of file WINPY.IMEFile Type: DLL ／／IME 实际为dll程序Section contains the following exports for WINPY.ime0 characteristics34A37323 time date stamp Fri Dec 26 17:04:35 19970.00 version1 ordinal base19 number of functions //共有１９个函数19 number of names // 对应１９个名称ordinal hint RVA name1 0 0000A010 CandWndProc //"选择汉字窗口"注册函数2 1 0000E750 CompWndProc //"输入编码窗口"注册函数3 2 0000FB50 ImeConfigure //配置当前ime参数函数4 3 0000FEC0 ImeConversionList//将字符或字符串转换成目标字符5 4 0000FFA0 ImeDestroy //退出当前使用的IME6 5 000030D0 ImeEnumRegisterWord7 6 0000FFB0 ImeEscape //应用软件访问输入法的接口函数.8 7 00003080 ImeGetRegisterWordStyle9 8 0000E9A0 ImeInquire //启动并初始化当前IME输入法10 9 0000A800 ImeProcessKey //IME输入键盘事件管理函数11 A 00002C20 ImeRegisterWord //向输入法字典注册字符串12 B 000109A0 ImeSelect //启动当前IME输入法13 C 000109E0 ImeSetActiveContext //设置当前的输入处于活动状态.14 D 0000C850 ImeSetCompositionString 由应用程序设置输入法编码15 E 0000AEE0 ImeT oAsciiEx //将输入的键盘事件转换为汉字编码事件16 F 00002F40 ImeUnregisterWord //删除被注册的字符串.17 10 0000CA90 NotifyIME //IME事件管理函数18 11 00005160 StatusWndProc //状态窗口注册函数19 12 00002350 UIWndProc //用户界面接口函数Summary5000 .ShareDa7000 .data2000 .idata1000 .rdata3000 .reloc5000 .rsrc2000 .sgroup18000 .text从上述可以看出，IME程序共有１９个出口函数组成，每一个函数都有特定的格式，它们担负着与windows 系统传递信息的作用，这些函数是供Windows系统调用的。
IBM IMM用户手册-远程管理卡
IMM使用指南一．如何访问IMM (1)二．IMM主要功能介绍 (4)三．几个常用功能 (5)1．远程开关机 (5)2．通过IMM刷新服务器的UEFI/IMM微码 (6)3．远程终端功能 (7)一．如何访问IMM通常主机后部有一个专用的管理端口，例如下图以3650M3为例，可以通过此端口访问IMM。
IMM管理端口默认IP：192.168.70.125用户名：USERID密码：PASSW0RD注意字母为大写，密码中的“0”是数字0在UEFI中修改IMM的IP地址在开机自检的过程中根据提示按F1进入UEFI设置，在UEFI中进入System Setting->Integrated Management Module->Network configuration。
在输入需要修改的IP地址后，选择Save Network Settings在IE中输入IP地址即可访问IMM管理界面二．IMM主要功能介绍System status查看服务器的健康状况，包括温度、电压和风扇状态等。
Virtual Light Path查看服务器光通路诊断板上是否有告警。
Event Log可以查看服务器的日志信息，可以用Save Log as Text File另存日志信息为文本文件。
Vital Product Data查看服务器的型号序列号及各种微码版本。
Power/Restart通过IMM控制开关服务器，包括定时开关机功能Remote Control远程控制服务器终端，需要添加IBM Virtual Media Key选件来实现此功能，大部分机型标配没有此选件。
PXE Network Boot设置服务器的PXE启动。
Firmware Update刷新服务器的UEFI和IMM的微码。
System Settings设置IMM的时间日期，名字等基本信息。
Login Profiles为IMM添加除默认之外的其他用户。
Alerts设置snmp告警等信息。
Immersive Display PRO User Guide
Immersive Display PRO是一个对DirectX, OpenGL 和Windows 7 桌面进行终极几何矫正与软边缘融合的软件包。
它基于成熟的Fly Elise-ng图像几何矫正和软边缘融合技术，支持多投影仪投影到规则和非规则的投影屏幕（包括圆柱屏幕，全部或部分圆顶屏幕以及其他形状的屏幕）。
Immersive Display PRO利用Fly Elise-ng核心组件进行图像几何矫正和软边缘融合配置、演示。
在一个简单的用户界面上，使用鼠标和键盘操作就可以将输出图像映射到任何一种投影屏幕。
调整细粒度和伽玛值对投影图像间重叠边缘进行融合。
一台投影仪的彩色矫正可以应用到其他投影仪的配置文件上。
Immersive Display PRO支持每台电脑最多连接10台投影仪，投影仪可以进行不同的水平和垂直位置叠加摆放。
其典型的应用是将飞行模拟器、赛车模拟器、投影仪模式的家庭影院等其他第一人称的软件，用多投影仪全方位的融合到投影屏幕上。
Immersive Display PRO是为家庭和特定环境设计的。
其应用领域有：●家庭娱乐系统●飞行、船舶和汽车模拟器●业务数据可视化●互动触摸显示器●会议室●视频播放●实时数字移动图形以下是所需的最低配置：2.1 2.0GHz或更高处理器（32位或64位）2.22G或以上内存2.3一个合适的显卡（NVIDIA 或AMD/ATI）2.4为能够在Windows7下进行广泛的多投影仪显示，需做以下要求：2.4.1NVIDIA显卡需要支持NVIDIA环绕2D2.4.2ATI 显卡需要支持ATI Eyefinity(宽域多屏显卡)2.4.3Matrox DialHead2GO或者TrippleHead2GO(多屏宝)，外部硬件盒2.5需要Administrator权限安装Immersive Display PRO2.6不需要Administrator权限运行Immersive Display PRO3安装和卸载3.1安装注意：Immersive Display PRO使用DirectX运行时集约。
RME ADI-8 DS Mk III 用户手册说明书
用户手册ADI-8 DS Mk III真正的工业标准高精度24 Bit / 192 kHz参考级别低延迟转换8通道模拟<> AES / ADAT 接口24 Bit / 192 kHz 数字音频ADAT <> AES 格式转换器24 Bit 接口重要的安全说明 (4)概述 (5)1. 介绍 (6)2. 包装清单 (6)3. 简介及主要特点 (6)4. 首次使用——快速上手 (7)4.1 控制、接口与显示 (7)4.2 快速上手 (8)5. 附件 (9)6. 产品保证 (10)7. 附录 (10)CE / FCC符合性声明 (11)使用和操作 (12)8. 前面板操作 (13)8.1 Select（选择）键 (13)8.2 A/D State（A/D状态）- Meters（电平表） (13)8.3 A/D Output（A/D输出） (13)8.4 Patch Mode（批处理模式） (13)8.5 Clock（时钟） (14)8.6 D/A Input（D/A输入） (15)8.7 D/A State（D/A状态）- Meters（电平表） (15)8.8 D/A Reference（D/A参考） (15)输入和输出 (16)9. 模拟输入/输出 (17)9.1 Line In（线路输入） (17)9.2 Line Out（线路输出） (18)10. 数字输入/输出 (19)10.1 AES/EBU (19)10.2 ADAT光纤 (20)11.字时钟 (21)11.1字时钟输入和输出 (21)11.2 技术描述和使用 (22)11.3 布线和终止 (23)技术参考资料 (24)12. 技术指标 (25)12.1 模拟 (25)12.2 数字输入 (26)12.3 数字输出 (27)12.4 数字 (27)12.5 D-Sub AES/EBU接口针脚 (28)13. 技术背景 (30)13.1 技术 (30)13.2 锁定（Lock）与SyncCheck（同步检查） (31)13.3 延时（Latency）与监听（Monitoring） (32)13.4 DS –双倍速 (33)13.5 QS –四倍速 (33)13.6 AES/EBU - SPDIF (34)13.7 DS/QS模式下的噪声电平 (35)13.8 SteadyClock（稳定时钟） (36)14. 框图 (37)重要的安全说明注意! 不要打开底盘，以防触电。
COMSOL Nonlinear Structural Materials Module User’
Nonlinear Structural Materials ModuleUser’s GuideC o n t a c t I n f o r m a t i o nVisit the Contact COMSOL page at /contact to submit general inquiries or search for an address and phone number. You can also visit the Worldwide Sales Offices page at /contact/offices for address and contact information.If you need to contact Support, an online request form is located on the COMSOL Access page at /support/case . Other useful links include:•Support Center: /support•Product Download: /product-download•Product Updates: /support/updates•COMSOL Blog: /blogs•Discussion Forum: /forum•Events: /events•COMSOL Video Gallery: /videos•Support Knowledge Base: /support/knowledgebase Part number: CM022901N o n l i n e a r S t r u c t u r a l M a t e r i a l s M o d u l e U s e r ’s G u i d e © 1998–2022 COMSOLProtected by patents listed on /patents , or see Help>About COMSOL Multiphysics on the File menu in the COMSOL Desktop for a less detailed lists of U.S. Patents that may apply. Patents pending.This Documentation and the Programs described herein are furnished under the COMSOL Software License Agreement (/sla ) and may be used or copied only under the terms of the license agreement.COMSOL, the COMSOL logo, COMSOL Multiphysics, COMSOL Desktop, COMSOL Compiler, COMSOL Server, and LiveLink are either registered trademarks or trademarks of COMSOL AB. All other trademarks are the property of their respective owners, and COMSOL AB and its subsidiaries and products are not affiliated with, endorsed by, sponsored by, or supported by those trademark owners. For a list of such trademark owners, see /trademarks .Version: COMSOL 6.1The Nonlinear Structural Materials ModuleThe Nonlinear Structural Materials Module is an optional add-on package forCOMSOL Multiphysics® designed to assist you to model structural behavior thatincludes nonlinear materials. The module is an add-on to the Structural MechanicsModule or the MEMS Module and extends it with support for modeling nonlinearmaterials, including hyperelasticity, creep, plasticity, and viscoplasticity. The module isdesigned for researchers, engineers, developers, teachers, and students who want tosimulate nonlinear structural materials, including a full range of possible multiphysicscouplings.The module provides an extensive set of nonlinear structural material models,including:•Predefined and user-defined hyperelastic materials: neo-Hookean, Mooney–Rivlin,St.Venant–Kirchhoff, Arruda–Boyce, Ogden, and others.•Small-strain and large-strain plasticity models using different types of hardening.•User-defined plasticity, flow rule, and hardening models.•Porous plasticity models, used for example for powder compaction simulation.•Predefined and user-defined nonlinear elastic materials: Ramberg–Osgood, Powerlaw, and others.•Shape memory alloys.•Predefined and user-defined creep material models: Norton, Garofalo, Anand,potential, volumetric, deviatoric, and others.•Viscoplastic models: Anand, Chaboche, and Perzyna.•Models for damage in brittle materials.A C C E S S I N G T H E N O N L I N E A R S T R U C T U R A L M A T E R I A L S D O C U M E N T A T I O NThis is an add-on module requiring either the Structural Mechanics Module or theMEMS Module. The feature information, including theory and modeling details, isincluded in the Structural Mechanics Module User’s Guide.When you install COMSOL Multiphysics, the documentation sets are installed inseveral locations, both on your computer and most easily accessible while you areworking in COMSOL Multiphysics. The next section details where to access it.T H E N O N L I N E A R S T R U C T U R A L M A T E R I A L S M O D U L E|34 | T H E N O N L I N E A R S T R U C T U R A L M A T E R I A L S M O D U L EA C C E S S I N G C O M S O L D O C U M E N T A T I O N A N D A P P L I C A T I O N L IB R A R I E SA number of online resources have more information about COMSOL, including licensing and technical information. The electronic documentation, topic-based (or context-based) help, and the Application Libraries are all accessed through the COMSOL Desktop.T H E D O C U M E N T A T I O N A N D O N L I N E H E L PThe COMSOL Multiphysics Reference Manual describes the core physics interfaces and functionality included with the COMSOL Multiphysics license. This book also has instructions on how to use COMSOL Multiphysics and how to access the electronic Documentation and Help content.Opening Topic-Based HelpThe Help window is useful as it is connected to the features in the COMSOL Desktop. To learn more about a node in the Model Builder, or a window on the Desktop, click to highlight a node or window, then press F1 to open the Help window, which thendisplays information about that feature (or click a node in the Model Builder followedby the Help button (). This is called topic-based (or context) help .If you are reading the documentation as a PDF file on your computer,the blue links do not work to open an application or contentreferenced in a different guide. However, if you are using the Helpsystem in COMSOL Multiphysics, these links work to open othermodules, application examples, and documentation sets.().In the upper-right corner of the COMSOL Desktop, click the ()T H E N O N L I N E A R S T R U C T U R A L M A T E R I A L S M O D U L E | 5Opening the Documentation WindowT H E A P P L I C A T I O N L I B R A R I E S W I N D O W Each model or application includes documentation with the theoretical background and step-by-step instructions to create a model or application. The models andapplications are available in COMSOL Multiphysics as MPH-files that you can open for further investigation. You can use the step-by-step instructions and the actual models as templates for your own modeling. In most models, SI units are used to describe the relevant properties, parameters, and dimensions, but other unit systems are available.Once the Application Libraries window is opened, you can search by name or browse under a module folder name. Click to view a summary of the model or application and its properties, including options to open it or its associated PDF document. () button.Help>Help .(). () button.Help>Documentation.The Application Libraries Window in the COMSOL MultiphysicsReference Manual .6 | T H E N O N L I N E A R S T R U C T U R A L M A T E R I A L S M O D U L E Opening the Application Libraries WindowTo open the Application Libraries window ():C O N T A C T I N G C O M S O L B Y E M A I LForgeneralproductinformation,******************************.C O M S O L A C C E S S A ND TE C H N I C A L S U P P O R TTo receive technical support from COMSOL for the COMSOL products, please contact your local COMSOL representative or send your questions to******************.Anautomaticnotificationandacasenumberwillbesenttoyou by email. You can also access technical support, software updates, license information, and other resources by registering for a COMSOL Access account.menu, select () select ()C O M S O L O N L I N E R E S O U R C E SCOMSOL website Contact COMSOL /contactCOMSOL Access /accessSupport Center /supportProduct Download /product-downloadProduct Updates /support/updatesCOMSOL Blog /blogsDiscussion Forum /forumEvents /eventsCOMSOL Application Gallery /modelsCOMSOL Video Gallery /videoSupport Knowledge Base /support/knowledgebaseT H E N O N L I N E A R S T R U C T U R A L M A T E R I A L S M O D U L E|78|T H E N O N L I N E A R S T R U C T U R A L M A T E R I A L S M O D U L E。
IMM5709E表格填写指南说明书
From (YYYY-MM-DD) To (YYYY-MM-DD)
4. The cost of my studies will be: Tuition Room and board Other
5. a) Funds available for my stay (CAD) b) My expenses in Canada will be paid by:
Contact Information 1. Current mailing address
ANSWERS Client ID (8 or 10-digit number listed in top right corner of your study or work permit); or look for “UCI” number. Do not include the hyphen Apply for a study permit for the first time or extend my study permit.
ON / Sudbury / 935 Ramsey Lake Road P3E 2C6 O19304259382 (this number starts with the capital letter O not zero)
Exte 42280 温度与湿度数据记录仪用户指南说明书
User GuideTemperature and Humidity Datalogger Model 42280IntroductionCongratulations on your purchase of the Extech 42280 Thermometer and Relative Humidity Datalogger. The 42280 is a wall-mount, tripod mount, or desktop indoor air quality monitor with an internal memory capable of storing 16,000 readings (8000 temperature readings and 8000 relative humidity readings) that can later be transferred to PC using the USB interface. Real-time meter-to-PC logging is also supported. This meter is shipped fully tested and calibrated and, with proper use, will provide years of reliable service.Material listSupplied MaterialsMeterUser GuideUSB cableProgram CDFour (4) batteries; 1.5V ‘AA’9V adaptorOptional accessoriesCalibration bottles (33% and 75%) for Relative Humidity CalibrationFeaturesLarge LCD display shows temperature, humidity, and date/time clock simultaneously16,000 internal memory capacity (8000 temperature; 8000 RH%)Visual and Audible (with 117V AC adaptor only) AlarmsEasily configure datalogger through the keypad or via PC interfaceUSB PC interface with Windows TM softwareWall mount, tripod mount, or for desktop useMeter Description1. Humidity Sensor (internal Temperature sensor)2. Audible alarm (with AC adaptor power only)3. Visual Alarm LED4. Relative Humidity display5.Date and Time display6. Temperature display7. RECORD status LED8. USB port9.AC Adaptor jack10. Datalogger START-STOP button 11. MODE button 12. SET button 13. Up Arrow button 14. Down Arrow button 15. Tripod mount jackNotes: The battery compartment is located on rear of instrument. Desktop stand footers are notshown in diagram.LCD Display Description 1. Temperature Display 2.Dew Point icon3. Datalogger icon4. Date and Time5. Humidity Display6. Low battery icon245Important Note before startingThis meter relies on firm button presses to operate correctly. Be sure to press firmly and hold the button for as long as directed in the instructions.Meter Power1. The meter is powered by four (4) ‘AA’ 1.5V batteries or the 117V AC adaptor.2. When the batteries are installed or the adaptor is connected to an AC power source,momentarily press the START-STOP button to turn the meter ON.3. Press the START-STOP button again to turn the meter OFF.Viewing the displayed readings1. Normally, the top line indicates temperature in degrees C or F. Use the MODE button to switchbetween degrees C and degrees F.2. Press and hold the MODE for at least 2 seconds. This will change the top display to Dew Pointtemperature. The ‘DP’ icon will appear on the LCD when in Dew Point mode. Press and hold the MODE button for at least 2 seconds to return the top display to the normal temperature display mode.3. The middle line displays Relative Humidity in %.4. The bottom line automatically alternates between Time and Date displays.5. If the ALM status LED illuminates and the display flashes, one of the Alarm limits has beenreached. Program the High and Low Temperature/Humidity limits in Programming parameter P5 (detailed later in this user guide).Datalogger BasicsThe Model 42280 has a built-in Datalogger that can store up to 8000 temperature and 8000humidity readings. Readings can be stored in the meter and transferred at a later time to a PC. The meter can also display real-time readings on a connected PC; in other words, the PC can display readings at the instant the readings are taken.The meter must be configured before datalogging can be attempted. Parameters such as Real Time Clock and Datalogger Sample Rate must be programmed before datalogging can begin. It isstrongly recommended that the user take advantage of the supplied software to configure the meter.Instructions for manually configuring the meter are provided below; however configuring the meter via software is very convenient.Basic instructions for connecting the meter to a PC and getting started with the supplied software are provided later in this guide. Detailed instructions regarding the supplied software are provided ina separate manual included on the supplied CD-ROM and the HELP utility in the software program.Manual ProgrammingThe Model 42280 has several programming modes (P1, P2, P3, P4, P5, and P6). Theseparameters must be programmed before the Datalogger or the Alarm can be used.List of Programming ModesP1 - Number of samples to record (1, 2, 4, 8, 12, or 16 x 1000; 1=1000, 2=2000, etc.)P2 - Datalogging Start Methods (Immediate, Keypad, Scheduled, and Repeat modes)P3 – Start Time (set the time and date when Datalogging will automatically begin); Note that P3 will not appear in the menu if ‘SCh’ is not selected in P2.P4 - Sample Rate (set the datalogging interval from 1 second up to 12 hours)P5 - Alarm Mode (set High and Low Temperature/Humidity limits)P6 - Real Time Clock (set the meter’s internal date and time clock)Programming Mode P1; Number of readings (sample points) to record1. Press the SET button to access the setup mode2. Use the arrow buttons to select parameter P1 (see sample display below)3. Press the SET button again4. Use the up/down arrow buttons to select thedesired number of samples (in thousands) to recordfor a datalogging session (1, 2, 4, 8, 12, or 16;where 1=1000, 2=2000, 4=4000, and so on)5. Press the SET button to save setting6. Use the arrow buttons to select another programming mode or press MODE to exit theprogramming mode.Programming Mode P2; Datalogger Start Modes1. Press the SET button to access the setup mode2. Use the arrow buttons to select parameter P23. Press the SET button again4. Select one of the four Start modes using the up/down arrow buttons (see list and diagrambelow)a. rEp (Repeat Start mode): Logger startsonce readings are downloaded to PCb. hEy (Keypad Start): Datalogging beginsafter the START/STOP button is held for2 secondsc. imm (Immediate Start): Recording startsimmediately after exiting the setup moded. SCh (Scheduled Start): Logging beginsat a preset date and time5. Press the SET button to save the setting6. Use the arrow buttons to select anotherprogramming mode or press MODE to exit theprogramming mode.Programming Mode P3; Datalog Start Timeset to ‘SCh’).1. Press the SET button to access the setupmode2. Use the arrow buttons to select parameter P33. Press the SET button again4. Use the up/down arrow buttons to set the year5. Press the SET button again6. Use the up/down arrow buttons to set month7. Press the SET button again8. Use the up/down arrow buttons to set the day9. Press the SET button again10. Use up/down buttons to set the hours11. Press the SET button again12. Use up/down buttons to set the minutes13. Press the SET button again14. Use the up/down arrow buttons to set theseconds15. Press the SET button again to store the settings16. Press the MODE button to back out to the top level of this menu.17. Use the arrow buttons to select another programming mode or press MODE to exit theprogramming mode.Programming Mode P4; Datalogger Sample Rate1. Press the SET button to access the setup mode2. Use the arrow buttons to select parameter P43. Press the SET button again4. Use the up/down arrow buttons to set hours5. Press the SET button again6. Use the up/down arrow buttons to set the minutes7. Press the SET button again8. Use the up/down arrow buttons to set the seconds 9. Press SET again to store the settings10. Press the MODE button to back out to the top level of this menu.11. Use the arrow buttons to select another programming mode or press MODE to exit theprogramming mode. Programming Mode P5; High and Low Alarms1. Press the SET button to access thesetup mode 2. Use the arrow buttons to selectparameter P5 3. Press the SET button again4. Use the up/down arrow buttons to set theHigh Temperature Alarm limit 5. Press the SET button again6. Use the up/down arrow buttons to set theLow Temperature Alarm limit 7. Press the SET button again8. Use the up/down arrow buttons to set the High Humidity Limit 9. Press the SET button again10. Use the up/down arrow buttons to set the Low Humidity Limit 11. Press the SET button again to store the settings12. Press the MODE button to back out to the top level of this menu.13. Use the arrow buttons to select another programming mode or press MODE to exit theprogramming mode. Note:The AC Adaptor must be used for the audible alarm to soundProgramming Mode P6; Real Time Clock1. Press the SET button to access the setup mode2. Use the arrow buttons to select parameter P63. Press the SET button again4. Use the up/down arrow buttons to set the year5. Press the SET button again6. Use the up/down arrow buttons to set month7. Press the SET button again8. Use the up/down arrow buttons to set the day9. Press the SET button again10. Use the up/down arrow buttons to set the hours11. Press the SET button again12. Use the up/down arrow buttons to set the minutes13. Press the SET button again14. Use the up/down arrow buttons to set the seconds15. Press SET again to stores the settings16. Press the MODE button to back out to the top level of this menu.17. Use the arrow buttons to select another programming mode or press MODE to exit theprogramming mode.DataloggingStarting a Datalogging sessionThe 42280 can automatically store up to 16,000 readings (8000 temperature and 8000 humidity) for later transfer to PC. Program the controller, as discussed earlier, before Datalogging. If theDatalogger has not been configured at this point, configure as necessary. If programming iscomplete, continue with the next section.Starting the Datalogger by push-button (Key Mode)1. Programming mode P2 (Datalogging Start Modes) must be set to KEY (hEy) mode for thismethod.2. When P2 is set to ‘hEy’, press and hold the START-STOP button for 2 seconds.3. The REC front-panel status light will blink indicating that readings are currently recording atthe rate programmed in parameter P4 (sample rate)4. To stop recording, press and hold the START-STOP button for at least 2 seconds. The RECstatus light will stop blinking.Starting the Datalogger in Immediate Mode1. Programming mode P2 (Datalogging Start Modes) must be set to ‘Imm’ mode for this method.2. When the programming mode is exited, Datalogger automatically begins.3. The REC front-panel status light will blink indicating that readings are currently recording.4. To stop recording, press and hold the START-STOP button for at least 2 seconds. The RECstatus light will stop blinking.Starting the Datalogger in Schedule Mode1. In Schedule Mode the meter begins recording at a specific date and time, as programmed bythe user.2. Programming mode P2 (Datalogging Start Modes) must be set to ‘SCh’ mode for this method.3. After setting P2 to ‘SCh’, set the desired time and date in Programming Mode P3 (P3 onlyappears in the menu when ‘SCh’ is selected in P2.4. Datalogging will start at the programmed date and time. Note that the Real Time Clock(Programming Mode P6) must first be set to the current date and time.5. When datalogging begins, the REC front-panel status light will blink indicating that readingsare currently recording at the rate programmed in parameter P4 (sample rate)6. To stop recording, press and hold the START-STOP button for at least 2 seconds. The RECstatus light will stop blinking.Starting the Datalogger in Repeat ModeIn Repeat Mode the meter simply begins datalogging again after readings are downloaded to a PC. This allows the user to maintain the same programming selections time after time.Datalogging is indicated by the flashing REC light as described in the other Start Modes above.To stop recording, press and hold the START-STOP button for at least 2 seconds. The RECstatus light will stop blinking.Connecting the Meter to a PCA USB cable is provided with the meter. One end of the cable connects to the meter’s USB jackand the other end connects to a USB port on the PC.Running the supplied PC softwareThe supplied PC software is included on the supplied CD-ROM. Insert the CD into the computer’s CD-ROM drive and follow the on-screen prompts and instructions. In the software COM PORT SETTING field, select the COM port to where the meter is connected.Software Datalogging ParametersFrom the main software screen, select LOGGER SET and set the sample rate, sample points, and start mode. These are described in some detail in the separate software manual and the software HELP utility on the supplied CD-ROM. Remember to press ‘OK’ after changing a setting to ensure that the software processes the changes. The meter is now ready to record.Transferring readings to PC1. Connect and run the supplied software as previously described.2. Press the DOWNOAD START button on the main software screen to transfer the readings.3. The separate software instructions supplied in the software’s HELP utility explain how toview, graph, save, export and print the downloaded data.NOTE: The Software’s HELP utility provides in-depth software and downloading instructions, which is beyond the scope of this user guide; please refer to the HELP utility in the supplied software program for detailed guidelines and instructions.Humidity Calibration1.With the meter OFF, plug the humidity sensor probe into the 33% Calibration Reference bottle. 2.Simultaneously press and hold the START-STOP and the SET buttons for at least 2 seconds to enter the 33% Calibration mode. The display ’32.8%’ will begin to flash on the display. 3.Approximately 30 minutes later, the ’32.8%’ display will stop flashing, indicating that the 33% calibration is complete 4.Plug the humidity sensor probe into the 75% Calibration Reference bottle. 5.Press and hold the START-STOP button for at least 2 seconds to enter the 75% Calibration mode. The display ’75.3%’ will begin to flash on the display. 6.Approximately 30 minutes later, the display will stop flashing, indicating that the entire calibration is complete. The meter will automatically return to the normal operating modeCalibration Notes:•The user can exit the calibration without finishing by pressing the START-STOP button for 2 seconds (before reaching step 6 above). •For best accuracy, perform the calibration at room temperature. •Calibration Reference bottles are available optionally through Extech Instruments distributorsSpecificationsGeneral SpecificationsLCDwith status LED indicators Display Multi-functionMeasurement ranges Temperature: -20 to 70o C (-4 to 144o F)Humidity: 0 to 100%Dew Point temperature: -20 to 70o C( -4 to 144o F)o C / o F / %Resolution 0.1Accuracy Temp: 1.0°F (+/- 0.6°C) from 0 to 50’C (32 to 122°F)2.0°F (+/-1.2°C) outside of this rangeHumidity: +/-3% from 10 to 90% (+/-5% outside of this range) Datalogger memory 16,000 total (8000 temperature and 8000 humidity readings) Over range indication Error code appears on the LCDLow battery indication Battery symbol appears on the LCDPower supply Four (4) 1.5v ‘AA’ batteries or 9V adaptorTroubleshootingPower is ON but there’s no displayCheck that the batteries or the AC adaptor is installed and connected properlyEnsure that the START-STOP button is pressed firmly and for at least 100msCalibration FailureCheck that the batteries or the AC adaptor is installed and connected properlyEnsure that the calibration bottles are tightly sealed around the meter sensorEnsure that calibration takes place at room temperatureFlashing LED IndicatorsREC flashes when datalogging takes placeALM light flashes when alarm limit has been exceededError CodesE02 - Under flow errorE03 - Over flow errorE04 - E02 and E03 combined errorE11 - CAL error (recalibration required)E32 - IC read/write error. Return unit for repairE33 - Circuit Error. Return unit for repairBattery ReplacementYou, as the end user, are legally bound (Battery ordinance) to return all used batteriesand accumulators; disposal in the household garbage is prohibited!You can hand over your used batteries / accumulators at collection points in yourcommunity or wherever batteries / accumulators are sold!Disposal: Follow the valid legal stipulations in respect of the disposal of thedevice at the end of its lifecycleCopyright © 2011 Extech Instruments Corporation (a FLIR company)All rights reserved including the right of reproduction in whole or in part in any form.。
通过IMM手动安装Windows2003操作指导
使用IMM安装操作系统指南IBM 服务器集成管理模块的远程控制能能可以通过ISO文件远程安装系统，具体操作步骤如下：1，X3650M3 IMM管理口位于机器后面最左边的位置，如下面图片所示：X3850X5 IMM管理口在电源下方板载网口右边，如下图所示system management ethernet2，IMM的默认IP地址为192.168.70.125 默认用户名:USERID 默认密码：PASSW0RD (the sixth character is the numeral zero)，包括用户名在内的所有字符大小写敏感)如果网络里面有开启DHCP，IMM会优先从DHCP获取地址在BIOS里面修改IMM地址：机器自检时按F1进入setup-->System settings-->>Integrated Memory Module-->Network3,将IMM和一台装有windows系统的客户机连接到同一个网络，并将客户机的IP地址和IMM 的地址设置为同一个网段4，在客户机的IE地址栏中直接输入IMM的IP后根据提示输入用户名和密码即可登陆【默认用户名:USERID 默认密码：PASSW0RD (the sixth character is the numeral zero)】，登陆后的界面如下：(建议使用火狐浏览器)5，更改IMM的IP地址：点击左边导航栏里面的network interface，在DHCP选项中选择使用静态地址，static IP configuration中配置IP,点击save保存6，更改IP后需要重新启动IMM才可生效，点击左侧导航栏中的restart IMM选项，在弹出的窗口中点击restart重新启动IMM，IMM重启过程大概需要1-2分钟，重启后即可使用设置的IP登陆。
7，开启远程控制：点击tasks中的remote control选项，选择start remote control in single user mode即可开启远程控制桌面（远程控制功能需要jre6.21或以上版本的支持，可以点击get jave start and latest jave runtime here或登陆下面地址下载安装）/en/download/ie_manual.jsp?locale=en&host=:808，远程控制桌面分两部分：虚拟媒体窗口和桌面显示窗口可以通过add image添加RAID卡驱动文件和可引导的windows安装源9,将img格式的RAID卡驱动mount到IMM上。
urg user guide
Unified Coverage Reporting User GuideVersion X-2005.12December 2005Comments?E-mail your comments about this manual to vera_support@Copyright Notice and Proprietary InformationCopyright 2005 Synopsys, Inc. All rights reserved. This software and documentation are owned by Synopsys, Inc., and furnished under a license agreement. The software and documentation may be used or copied only in accordance with the terms of the license agreement. No part of the software and documentation may be reproduced, transmitted, or translated, in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without prior written permission of Synopsys, Inc., or as expressly provided by the license agreement.Right to Copy DocumentationThe license agreement with Synopsys permits licensee to make copies of the documentation for its internal use only. Each copy shall include all copyrights, trademarks, service marks, and proprietary rights notices, if any. Licensee must assign sequential numbers to all copies. These copies shall contain the following leg-end on the cover page:“This document is duplicated with the permission of Synopsys, Inc. for the exclusiveuse of __________________________________________ and its employees. Thisis copy number __________.”Destination Control StatementAll technical data contained in this publication is subject to the export control laws of the United States of America. Disclosure to nationals of other countries contrary to United States law is prohibited. It is the reader’s responsibility to determine the applicable regulations and to comply with them.DisclaimerSYNOPSYS, INC., AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IM-PLIED, WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WAR-RANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.TrademarksSynopsys, the Synopsys logo, Arcadia, BiNMOS-CBA, CMOS-CBA, COSSAP, DESIGN (ARROWS), DesignPower, DesignWare, dont_use, EPIC, ExpressModel, in-Sync, LM-1000, LM-1200, Logic Modeling, Logic Modeling (logo), Memory Architect, ModelAccess, ModelTools, PathMill, PL debug, RailMill, SmartLicense, SmartLogic, SmartModel, SmartModels, SNUG, SOLV-IT!, SourceModel Library, Stream Driven Simulator, Synopsys, Synopsys (logo), Synopsys VHDL Compiler, Synthetic Designs, Synthetic Libraries, TestBench Manager, and TimeMill are registered trademarks of Synopsys, Inc3-D Debugging, AMPS, Behavioral Compiler, CBA Design System, CBA-Frame, characterize, Chip Architect, Compiled Designs, Core Network, Core Store, Cyclone, Data Path Express, DataPath Architect, DC Expert, DC Expert Plus, DC Professional, DelayMill, Design Advisor, Design Analyzer, Design Compiler, DesignSource, DesignTime, DesignWare Developer, Direct RTL, Direct Silicon Access, dont_touch, dont_touch_network, ECL Compiler, ECO Compiler, Embedded System Prototype, Floorplan Manager, Formality, FoundryModel, FPGA Compiler, FPGA Express, Frame Compiler, General Purpose Post-Processor, GPP, HDL Advisor, HDL Compiler, Integrator, Interactive Waveform Viewer, Library Compiler, LM-1400, LM-700, LM-family, Logic Model, ModelSource, ModelWare, Module Compiler, MS-3200, MS-3400, Power Compiler, PowerArc, PowerGate, PowerMill, PrimeTime, RTL Analyzer, Shadow Debugger, Silicon Architects, SimuBus, SmartCircuit, SmartModel Windows, Source-Level Design, SourceModel, SWIFT, SWIFT Interface, Synopsys Graphical Environment, Test Compiler, Test Compiler Plus, Test Manager, TestSim, Timing Annotator, Trace-On-Demand, VCS, VCSi, VHDL System Simulator, VirSim, Visualyze, Vivace, VSS Expert, and VSS Professional are trademarks of Synopsys, Inc.Linux is a registered trademark of Linus Torvalds used by permission.All other product or company names may be trademarks of their respective owners.Unified Coverage Reporting User Guide, Version X-2005.06 2Contents1.Unified Coverage ReportingFeatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3 Generated Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5 Common Elements for all pages . . . . . . . . . . . . . . . . . . . . . . .1-5 Dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7 "hierarchy" File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8 "modlist" File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10 "groups" File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11 "tests" File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12 "modN" File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-13 "grpN" File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15 Assertions and Property Coverage Reports . . . . . . . . . . . . . .1-17 Coverage Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-18 Common Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-18 Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-20 T oggle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-20 Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-221FSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-22 Assertions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-24 T estbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-25 Coverage Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-26 Grading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-26 Grading and the -scorefile Option . . . . . . . . . . . . . . . . . . . . . .1-27 Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-28 Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-28 Coverage T ypes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-29 Controlling the Report Format. . . . . . . . . . . . . . . . . . . . . . . . . . . .1-29 Grading and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-30 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-31 Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3221Unified Coverage ReportingThe Unified Report Generator (URG) generates combined reports forall types of coverage information. The reports may be viewed throughthe design hierarchy, module lists, coverage groups, or through anoverall summary "dashboard" for the entire design/testbench. Thereports consist of a set of HTML or text files.The HTML version of the reports take the form of multiple interlinkedHTML files. For example, a "hierarchy.html" page shows the design'shierarchy and contains links to individual pages for each module andits instances.The HTML file that the URG writes can be read by any web browserthat supports CSS (Cascading Style Sheets) level 1, which includesInternet Explorer (IE) 5.0 and later versions, any version of Opera,and the later versions of Netscape.Unified Coverage Reporting1-1Note:For the Vera X-2005.12 release, only testbench and assertion coverage are supported. Assertion and Code coverage is notsupported by Vera alone, but requires that you also use eitherovasim or VCS.To invoke URG, enter the urg command and specify the directoriescontaining coverage data files.•Testbench and assertion coverage data are written to the *.vdb directory•Code coverage data is written to a *.cm directoryFor all three types of coverage, you invoke URG as follows:% urg -dir simv.cm simv.vdbData files are grouped into tests based on the names of the files. Soif you have:./simv.vdb/snps/coverage/db/testdata/test1./simv.cm/coverage/verilog/test1.db./simv.cm/coverage/vhdl/test1.db./simv.vdb/fcov/test1.dbAll of these files will be considered data for 'test1'.The reports generated by URG are placed in a directory (by defaultthis is "urgReport" in the working directory). The reports consist of aset of HTML or text files. Each time URG is run, the report directoryand all of its contents are removed and replaced by the new reportfiles.Unified Coveage Reporting1-2FeaturesURG includes reporting for the following metrics:•Code coverage-line-condition-toggle-FSM•Assertions•TestbenchNote: You can only report on code or assertion coverage if you use VCS code or assertion coverage to collect data.Path, assigntgl, and branch coverage are not supported. Nosub-options for these features are supported in this version.The following report pages are generated as .html or .txt files:•dashboard•hierarchy•modlist•groups•modN.html or modinfo.txt•grpN.html or grpinfo.txtUnified Coverage Reporting1-31-4Unified Coveage Reporting•asserts •assertcategories •assertseverities •assertcomplexities •assertdensities •testsThe following options are supported:Table 1-1. URG Options OptionDescription Comments -dir directory_name Specifies coverage data directories-metric line+cond+fsm+tgl+assert+tb Limit report to specified metric(s)-show textGenerate text report (not HTML) -cond exclude filenameSpecify excluded conditions condition coverage only -cond idsShow condition ids in generated report -cond nocasedefExclude case default from condition reports -fsm disable_sequenceDo not show fsm sequences fsm coverage only -fsm disable_loopDo not show fsm sequences containing loops -line nocasedefExclude case default from line coverage reports line coverage only -show testsShow the tests that covered each line and condition line & condition coverage -show maxtests NSpecify the maximum number of tests with "-show tests"-grade goal timelimitGrade tests (see page 26) -scorefile filename Allows user to specify different weight to each metric1-5Unified Coverage Reporting Generated FilesCommon Elements for all pagesCoverage data boxes are used throughout the URG report pages. These are tables containing one box for each type of coverage. An example of a text version of the report is as follows:Score Line Cond Toggle FSM Assert Testbench 46.15 87.08 40.11 20.24 -- 50.00 33.33-report mydirGenerates report in mydir instead of default directory -help and -hShows command line and options supported by URG -log filenameSends diagnostics to filename instead of stdout/stderr -split N Controls how large files are allowed to become before being split.The argumentis an integer specifying the maximumsize in bytes for any generated file. Thisnumber is used as a guideline, not anabsolute limit. The default is 200kb.-dbname argumentGenerate merged data files using argument Table 1-1. URG OptionsOptionDescription CommentsThe HTML version includes color-coded boxes, or cells left empty ifno coverage data for the coverage type represented by the box wascollected. For example:The first box shown is the overall score for all metrics. By default, thisis the simple average of all the metric percentages. You can controlthe way the score is computed with the -scorefile option (see“Grading and the -scorefile Option” on page 1-27).In this example we collected Line, Condition, Toggle, Assertion andTestbench coverage. FSM coverage was turned on, but no FSMswere found in this region.The Line box is green because it falls into the upper range of targetvalues. Values display in a range of 11 colors from red (low) to green(high) as shown below. These colors are graduated every 10percentage points (with 100 being the 11th class).All generated pages contain a common navigation menu at the top.This menu allows you to go directly to any of the main pages, includingthe hierarchy, modlist, groups, dashboard, or tests files. It is a simplelist of the top-level pages, plus a legend showing the cutoffpercentages for each color:Unified Coveage Reporting1-6Unified Coverage ReportingDashboardThe dashboard page is the top-level view of all coverage data. It includes the coverage data boxes for the database as a whole. Note that you can weight the coverage score in various ways. For example, 60% assertions coverage may be much worse than 25% condition coverage.The following is an example of a dashboard report. Note: The underlined words: "dashboard," "group," "tests" and"asserts" are hyperlinks in this example"hierarchy" FileThis file contains an indented list of all module, interface, andcomponent instances in the design. The indentation corresponds tothe design tree - children are indented underneath their parents.Note: The following examples are shown in HTML. The text versions of these pages contain the same content, but are missing thehyperlinks and color.The coverage data boxes for each instance in hierarchy.html showsthe total coverage information for the subtree rooted at the instance.The name of the instance is linked to its part of its module's modN.htmlpage. Each metric in the coverage data box is linked to thecorresponding section of the module instance's data in the modN.htmlpage.A section from an example hierarchy.html page is shown below. Thedata shown in the hierarchy pages is the cumulative coverage for theentire sub-tree rooted at each instance. So, the coverage shown forMMRK0 is the coverage for that instance, plus the coverage for Unified Coveage ReportingDELAY_MOD and ovac_CHKR. To see the coverage for the instance MMRK0 alone, click on it to go to the instance report.A hierarchy may be broken into multiple pages. When this happens, you can click on 'subtree' to see the elided part of the design.If an entire subtree in the design has no coverage data, the instances in that subtree will not have links to modN.html pages. They will still be shown in hierarchy.html but there will be empty coverage data boxes.Unified Coverage ReportingIf a particular instance itself has no coverage data, but one of itschildren or other descendents does, it will have a link to a modN.htmlpage. This way, you can still traverse through the coverage datathrough the modN.html page to the children or parents.If there is no design coverage information, no hierarchy will be shown.The hierarchy page will not be generated and the "hierarchy" link willnot be underlined."modlist" FileThe modlist.html file contains a flat list of all modules, entity/architectures, and interfaces in the design. The module (or entity, orinterface) names link to the corresponding modN.html page. Theentries in the list are similar to those in hierarchy.html, but there is noindentation, and the labels are module names rather than instancenames. The coverage data boxes show the accumulated coverageinformation for all instances of the module (or entity/architecture, orinterface).List entries in modlist.html are sorted in "worst-first" order. That is,the first module (or entity, or interface) shown will be the one with theworst overall coverage score. The next are ones with better coverage,ultimately followed by the one with the best coverage. Following allthese are the module (or entity, or interface) entries for which thereis no coverage information.Unified Coveage ReportingIn the example below, the module TR has no line, condition or assertion coverage information. Note that the modules are listed in worst-first order based on total coverage score.If there is no design coverage information, no module list will be shown. The hierarchy page will not be generated and the "modlist" link will not be connected."groups" FileThe file groups.html contains a flat list of coverage group definitions with coverage data boxes. The data boxes show the coverage information for the coverage group.As in the modlist.html page, all groups in the groups.html page will be shown in "worst-first" order.Unified Coverage ReportingThe link from each group leads to a grpN.html page.The following example shows three coverage groups as they wouldbe displayed in the groups.html page.If there is no testbench coverage information, no groups will beshown. The groups page will not be generated and the "groups" linkwill not be underlined."tests" FileThis page lists, in score order, all tests whose coverage data wasloaded to generate the report. Tests are listed in overall coveragescore in best-first order, unless the report was produced with grading,in which case they are listed in graded order (see “Grading andAnalysis” on page 1-30). There will always be at least one test in thetests.html page.Unified Coveage ReportingWhen testbench coverage is enabled, the simulation and random seed information is shown in the tests.html page:"modN" FileEach modN.html file contains the summary coverage information for a module, entity/architecture, or interface. Unless the file has been split for size, it also contains coverage information for each of the instances of the module (if it is very large, or has a large number of instances, the data for each instance and for the module itself is put in a separate modN_M.html file).Each modN.html file has a header section and a coverage data section. The header section contains the name of the module and a list of the self-instances of the module. The self-instances are listed in "worst-first" order by overall coverage score.Coverage data boxes are shown for the module summary information and for each of its instances so users can see the status of each. TheUnified Coverage Reportingcoverage data boxes for the self instances are smaller than that forthe module.The self-instance links go to the module instance information for eachinstance. These are the same links as from the hierarchy.html pagefor each of the instances.The module instance sections also have header and coverage datasections. The header is similar to the module header, but instead ofsource file and self instance lists, links to the parent instance and tochild instances are shown.Smaller coverage data boxes are shown for the module summaryinformation, the parent, and each child of the module instance. The Unified Coveage Reportingnames of each of these relatives is a link to the respective module or module instance report.As for all report pages, the coverage data boxes are linked to the corresponding coverage reports. For example, clicking on "Line" in the above example would display the line coverage information for the module instance "DUT.KPU0.MA.arbfGRLNK2". These links are convenient for movement within a modN.html page, and are also the only way to view the coverage data reports if the modN.html page has been split for size."grpN" FileEach grpN.html page will have a similar outline to the modN.html pages. There will be a header for each coverage group, giving its name, and list of instances. Both sections will have the appropriate data boxes linking to coverage data reports.Unified Coverage ReportingThe header for a group shows the group's name, coverage, goal, andweight, along with smaller data boxes for each of its children. Eachcoverage group then contains a statistics table for variables andanother for crosses showing the overall coverage for each variableand cross, as shown in the figure below.The names of the variables and crosses in these tables are linked totheir details.Group instances have similar headers, with a link to the groupsummary information rather in place of the list of instances. Groupinstances have statistics tables and detailed reports in the same Unified Coveage Reportingformat as the group summary information shown in the examples above.Assertions and Property Coverage ReportsThree special files are generated for assertion and property coverage, asserts.html, assertcategories.html and assertseverities.html.The asserts.html page below shows the score for each category and severity of assertions, properties and sequences.Unified Coverage ReportingThe following assertcategories.html report shows a detailed listorganized by category.The assertseverities.html report, not pictured here, provides adetailed list organized by severity.Coverage DataThis section discusses how each type of coverage will be formattedfor the reports.Common ElementsThere are two basic types of display that will be used for showingcoverage results. One is the statistics table, and the other is the tableof coverable objects.Unified Coveage ReportingStatistics tables are summaries of types of coverage elements. Each line in a statistics table reports the coverage for a class or category of object. For example, a statistics table for line coverage will look something like this:As shown in the example, statistics tables are colored using the same percentages used for coverage data boxes.The table of coverable objects shows the coverage results for individual coverable objects. Coverable objects do not have percentages - they are covered or uncovered. Coverable object tables show covered (and observed) objects in green and uncovered in red. The example in the Condition section shows a coverage data table for condition coverage.For all types of coverage, the data section will begin with a statistics table showing the basic categories (for example, lines, statements, and blocks, or logical and non-logical conditions). This will be followed by a table of coverable objects.Note that several metrics have options that change exactly what is covered or how it is output. For example, condition coverage has -cm_cond allops+anywidth, which affects which vectors and conditions are monitored for coverage. Unless otherwise specified below, these options will not affect the basic structure of the coverage data output.Unified Coverage ReportingLineThe line coverage section will begin with a table showing the overallcoverage for lines, statements, and blocks. It will then show asummary of the coverage data for all types of blocks (always,caseitem, for, forever, etc.).The other type of coverage data currently in the line reports is a tableshowing the line number of each statement, 0 or 1 for not covered/covered, and then the block type if that statement begins a block.An example statistics table for line coverage is shown below.ToggleThe toggle coverage report starts with a table containing the numberof Nets, Regs, and VHDL signals, the bits in each, and the summarycoverage statistics for each type of signal. It then shows a table foreach type of signal, listing each signal and indicating whether it wasfully covered or not.Unified Coveage ReportingThe figure below is an example toggle summary table:This figure shows a section of a toggle coverage detailed table:Unified Coverage ReportingUnified Coveage ReportingConditionCondition coverage information will be shown as a table with each type of condition, then an enumeration of each condition showing the source code. For example:FSMThe FSM coverage section will begin with a summary table for states,transitions, and sequences for all FSMs in the module/instance/entity.It will then show individual state, transition and sequence tables for each FSM.Unified Coverage ReportingAssertionsThe assertion coverage section displays a table showing the statisticsfor assertions.Unified Coveage ReportingTestbenchEach coverage group section lists all points and crosses and their coverage scores at the top.Unified Coverage ReportingIn the table above, "hole analysis" has compressed forty nine binsinto a single row of the "uncovered bins" table.There will then be a section for each point or cross, showing theindividual coverage percentage, information about the point or cross,and other information essentially in the same format as the currenttestbench coverage reports.Coverage AnalysisIn previous sections, we have discussed how reports are generatedand how collected coverage data is displayed. This section discussesmore sophisticated reported methods used in the generated reports.GradingWhen the -grade option is given to URG, it will grade all of the teststhat are provided as input to URG.When grading is specified, the tests.html page will list the tests inthree sections. The first section will list the tests in graded order,showing the incremental coverage scores for each test with respectto the tests above it in the list. The second section consists of a simplelist of tests that were not used to reach the grading goal (or were notuseful). In the third section, all tests will be listed in descending orderof overall coverage score.Note that if the time limit is specified, only those tests that are gradedbefore the time limit is hit will be included in the graded list. Only thedata for those tests will be used to generate the report files, even ifthe grading goal is not reached.Unified Coveage ReportingIf more than one metric is specified on the URG command line along with the -grade option, all specified metrics will be used together in the grading algorithm. For example, if you specify:% urg -grade -metric line+assertThen each line and assertion will be considered with the same weight when grading tests. This will be as if the coverage percentage of a given test is the number of covered lines plus the number of covered assertions, divided by the total number of lines plus the total number of assertions. We will use the same basic grading algorithm (test loading/unloading of all data from that test) as in the single metric case, but compute the percentages in this unified way.Grading and the -scorefile OptionWhen specifying the -scorefile option, you designate how coverage percentages should be computed in a separate file. This file allows you to give a different weight to each metric.The following is an example score file. It shows that line coverage is weighted normally, but that each testbench coverable object should be weighted double:line 1tb 2The names of the metrics in the score file are the same name used as arguments to the -metric flag. As for the unified grading example in the last section, we use the same grading algorithm. The only difference is how we compute the coverage percentages. In this example, the total coverage percentage would be computed as the mean of the scores for line and twice the testbench coverage.Unified Coverage ReportingCommand LineThis section describes the command line for URG.Directories-dir directoryThis option will accept any coverage directory (.cm, .vdb, and anyfuture unified directory form) and take data from that directory for itsreport. Multiple -dir options can be specified. You must specify atleast one directory- there is no default coverage directory name.Since urg is a Unix command, the arguments may include shellvariables, absolute, or relative paths, such as:% urg -dir $MYDIR/foo.cm% urg -dir $MYDIR% urg -dir ~username/covd ~username/covd/simv1.cmurg is invoked from the command line, and writes coverage data intodesignated directories.•Testbench coverage data is written to the current directory•Code coverage data is written to a *.cm directory•Assertions coverage data is written to a *.vdb directorySo for all three types of coverage, you invoke URG as follows:% urg -dir . simv.cm simv.vdbUnified Coveage Reporting。
IBM服务器远程管理模块IMM初步使用
IBM服务器远程管理模块IMM初步使用买了台IBM x3650服务器, 折腾了一下IMM, 小记之....IBM服务器都有一个远程管理端口, 同时支持静态和动态IP地址. 管理端口默认IP地址统一为192.168.70.125, 更改IP地址有两种方式, 一是开机按"F1"进入BIOS设置, 二是先通过WEB登陆http://192.168.70.125进入IMM管理界面进行修改.1) 第一种方式: 在BIOS中修改管理端口IP启动服务器后, 可以使用BIOS设置工具管理IMM 网络连接.开启服务器, 通电大约两分钟后, 电源控制按钮将会激活, 按下开机按钮, 就会显示IBM System x Server Firmware 欢迎界面.按下F1键. 在Setup utility主窗口中, 选择System Settings - Integrated Management Module - Network Configuration. 在DHCP Control中有三个IMM 网络连接选项(Static IP,DHCP Enabled,DHCP with Failover (default). 选择其中一种网络连接方式.如果选择static IP, 须指定IP地址,子网掩码,网关.(IP address,subnet mask and default gateway).设置完后选择Save Network Settings保存, 退出 Setup utility.2) 第二种方式: 在IMM管理界面中修改IP用网线将笔记本与服务器管理端口相连, 修改笔记本的IP地址为192.168.70.xxx, PING通服务器管理端口后, 在网页地址栏中输入http://192.168.70.125, 回车后就可以进入IMM管理界面.Note: IMM 默认用户名是USERID, 密码是PASSW0RD(0是数字零而不是字母O).在欢迎界面中, 选择timeout值(此值为IMM自动退出登陆的时间), 点击Continue 开始进入, 浏览器将出现System Status页面, 在IMM Control - Network Interfaces中修改IP地址.3) IMM各项功能简介修改IP之后, 将管理端口连至交换机, 即可远程管理服务器, 包括开机,关机,查看系统日志,升级BIOS和Firmware以及远程控制等. 如图:在IMM Control - LoginProfiles修改IMM默认用户USERID的密码, 或新建新用户;在Monitor - Event Log中可以查看机器的日志;在Task - Remote Control中可以进行远程控制, 远程控制须在本机安装好Java插件;关于IMM详细配置, 可至IBM官网下载和查看imm_users_guide.pdf文档. --End--。
TiWi-uB2 EM BOARD User Guide
T I W I-U B2EM B OARDUser GuideLast updatedMay 28th, 2013Table of Contents1Introduction (3)1.1Purpose & Scope (3)1.2Applicable Documents (3)1.3Revision History (3)2TiWi-uB2 Module Description (4)3TiWi-uB2 EM Board Hardware (5)3.1Antenna (5)3.2Connectors (5)3.3Required Signals between EM Board and Host Device (6)3.4Connecting EM Board to Host Platform (7)3.5Power Supply (7)3.6Serial Interfaces (7)3.7HCI UART (8)3.8PCM Interface (8)3.9Option 1: Using EM Connectors (8)3.10Option 2: Using Single Row Headers (11)3.11Using J7 with USB to Serial Converter (12)4Schematic (13)4.1Bill Of Material (BOM) (14)5Application Development (15)5.1Overview (15)5.2Development Tools (15)6Contacting LS Research (20)1Introduction1.1 Purpose & ScopeThe purpose of this document is to provide details regarding the setup and use of theTiWi-uB2 module on an EM board. This document covers a description of the EM board and its features and a brief tutorial on how to operate the module EM board.1.2 Applicable Documents∙TiWi-uB2 Datasheet (330-0100)∙TiWi-uB2 Antenna Design Guide (330-0106)1.3 Revision HistoryTable 1 Revision History2TiWi-uB2 Module DescriptionThe TiWi-uB2 EM “Evaluation Module” Board is an evaluation platform for the LSResearch TiWi-uB2 Bluetooth and Bluetooth Low Energy (BLE) module.Communication between the TiWi-uB2 module, which is a slave, and the host device is through a UART interface.The TiWi-uB2 EM Board contains an on board chip antenna and U.FL connector. The EM board is intended for evaluation purposes when used in conjunction with variousTexas Instruments MSP430 and Stellaris development boards.Figure 1 TiWi-uB2 EM Board TopFigure 2 TiWi-uB2 EM Board Bottom3 TiWi-uB2 EM Board Hardware 3.1 AntennaThe TiWi-uB2 EM Board contains an on board chip antenna which is modular certified for FCC 15.247 and IC RSS-210, as well as compliant to the RF requirements for ETSI EN 300 328 and ETSI EN 301 489. The antenna layout and circuitry on the EM Board can be replicated on a custom designed PCB assembly. Assuming the design/layout is followed exactly as that which is on the EM Board, the custom PCB will retain the modular certification. Below are details on the certifications.FCC ID: TFB-BT1, 15.247 IC ID: 5969A-BT1, RSS 2103.2 ConnectorsThere are two primary connectors on the TiWi-uB2 EM Board (J1 & J2). These provide a standard interface to Texas Instruments development platforms (See Section 3.9). Two additional non populated connectors (J4 & J5) provide access to all of the significant signals on the module on a standard, single row 2mm pitch header.165423789Figure 3 TiWi-uB2 EM Board Top Side ConnectorsTable 2 TiWi-uB2 EM Board Top Side Connectors3.3 Required Signals between EM Board and Host DeviceIn addition to power and ground, there are three signals required for connecting a TiWi-uB2 module to a host device. See Table 3 below for details on these connections.Table 3 TiWi-uB2 Required Connections3.4 Connecting EM Board to Host PlatformThe TiWi-uB2 EM Board is intended to allow for evaluation of and early developmentwith a TiWi-uB2 module. The EM Board has two “EM” connectors on the bottom of the board that allows for easy connection to various Texas Instruments microcontrollerdevelopment platforms. The primary development platform is the MSP430F5438Experimenter Board.It is also possible to adapt the TiWi-uB2 EM Board to work with microcontroller platforms that do not have support for the EM connectors. Sections 3.9 and 3.10 describe the two options for adapting an EM Board to work with other microcontroller platforms.3.5 Power Supply3.5.1 VBATVBAT requires a 3.0V to 4.8V DC power supply.3.5.2 VDD_IOVDD_IO requires a 1.8V DC power supply.Figure 4 Power Supply3.6 Serial InterfacesThere are two serial interfaces to the module, HCI UART and PCM. Each interface isdescribed below.Figure 5 Serial Interfaces3.7 HCI UARTThis is the main interface between the host microcontroller and the module. TheBluetooth UART may also be used to download external patches from the host to theTiWi-uB2. The UART interface supports baud rates from 9600bps to 4Mbps.BT debug pin: The debug interface (TX_DBG) helps customers to debug the HW/SWissues for their application (not pictured).3.8 PCM InterfaceThe PCM Interface can connect to linear PCM Codec devices in master or slave mode.In master mode, the TiWi-uB2 generates the PCM_CLK and PCM_SYNC signals, and in slave mode, these signals are provided by another master on the PCM interface and are inputs to the TiWi-uB2.Figure 6 PCM Interface3.9 Option 1: Using EM ConnectorsEither build a PCB which has the EM Board mating connectors which will allow forplugging the TiWi-uB2 EM Board into, or solder wires to EM Board mating connectorsthat can then be wired into whatever development platform is being used.Below are two suggestions for the mating EM connectors.Through hole connector: Samtec TFM-110-01-S-D-WTSurface Mount connector: Samtec SFM-110-02-L-D-AIf building a PCB that has the mating EM Board connectors, the connectors need to be lined up and spaced 1.2” apart as shown in Figure 7.Figure 7 Host PCB EM Mating Connector Arrangement (Top View)Refer to Table 4 and Table 5 below for details on the signals brought out to the EM connectors J1 and J2.Table 4 EM Connector J1Table 5 EM Connector J2DI = Digital Input; DO = Digital Output; DIO = Digital Input/Output; PI = Power Input3.10 Option 2: Using Single Row HeadersSolder single row 12 pin 2mm headers into locations J4 and J5 on the EM Board, and then build a wiring harness between the headers on the EM Board and themicrocontroller development platform of interest.Below is a suggestion for the 12 pin 2mm headers.Sullins NRPN121PAEN-RCRefer to Table 6 and Table 7 below for details on the signals brought out to the single row headers J4 and J5.Table 6 Single Row Header J4DI = Digital Input; DO = Digital Output; PI = Power InputTable 7 Single Row Header J5DI = Digital Input; DO = Digital Output; DIO = Digital Input/Output; PI = Power Input3.11 Using J7 with USB to Serial ConverterJ7 is provided for interfacing the TiWi-uB2 Module to a USB-to-Serial converter, or similar serial device capable of providing 1.8V logic level data.Table 8 Single Row Header J7DI = Digital Input; DO = Digital Output; DIO = Digital Input/Output; PI = Power Input;4.1 Bill Of Material (BOM)Table 9 TiWi-uB2 EM Board BOM5Application Development5.1 OverviewThe TiWi-uB2 EM Board used in conjunction with a Bluetooth stack running on TI’sMSP430BT5438 or Stellaris LM3S9B96microcontroller (MCU) will reduce designbarriers and provides a highly flexible platform to enable customer’s early prototyping capabilities of embedded Bluetooth applications. The ready-to-go wireless platforms simplify the development process of pre-integrated and pre-validated Bluetooth serial link on an MSP430BT5438 or LM3S9B96system.For an overview of development platforms and software examples see CC256xBluetooth.5.2 Development Tools5.2.1 MSP430 HardwareHardware required for initial evaluation and development include:∙ 2 - TiWi-uB2 EM Boards∙ 1 - TI MSP430 USB Debugging Interface∙ 2 - TI MSP430F5438 Experimenter Boards5.2.2 Stellaris Hardware∙ 1 - TiWi-uB2 EM Board∙ 1 - TI MSP430 USB Debugging Interface∙ 1 - TI Stellaris LM3S9B96 EM2 Expansion Board∙ 1 - TI DK-LM3S9D965.2.3 SoftwareSoftware required for initial evaluation and development include:Stellaris∙Bluetopia®+LE SDK∙CC256x_Bluetopia_Stack∙Stellaris DK-LM3S9B96 SDKIntegrated BT Profiles∙Classic Bluetooth∙SPP∙A2DPFigure 9 TiWi-uB2 EM Board with Stellaris DK-LM3S9B96MSP430Bluetopia∙Bluetopia®+LE SDK∙CC256x_Bluetopia_Stack∙CC256x MSP430 Bluetopia Basic Demo APPSIntegrated BT Profiles∙Classic Bluetooth∙SPP∙Bluetooth Low Energy∙GATT∙ANP∙HRP∙HTP∙PASPThis Bluetooth software solution is licensed from Stonestreet One. The Bluetopia®+LE SDK is comprised of Single Mode and Dual Mode offering implementing the Bluetooth 4.0 specification. Bluetopia®+LE stack is built upon the solid foundation of the Bluetopia protocol stack that is currently being used in millions of consumer and industrial devices and that was first qualified in 2000 `TiWi-uB2 + MSP430 Bluetopia Basic Demo APPS allows users to evaluate TI's CC256x Bluetooth device by using the TiWi-uB2 EM board and the MSP-EXP430F5438 board. The CC256x+MSP430 Bluetooth sample applications code are provided to enable a rich out-of-box experience to the user. The application allows the user to use a console to send Bluetooth commands, setup a Bluetooth Device to accept connections, connect to a remote Bluetooth device and communicate over Bluetooth.Figure 10 TiWi-uB2 EM Board with MSP430F5438 Experimenter Board6Contacting LS ResearchHeadquarters LS Research, LLCW66 N220 Commerce CourtCedarburg, WI 53012-2636USATel: 1(262) 375-4400Fax: 1(262) 375-4248Website Wiki /products-wikiTechnical Support /products-forumSales Contact*************The information in this document is provided in connection with LS Research (hereafter referred to as “LSR”) products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of LSR products. EXCEPT AS SET FORTH IN LSR’S TERMS AND CONDITIONS OF SALE LOCATED ON LSR’S WEB SITE, LSR ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL LSR BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF LSR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. LSR makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. LSR does not make any commitment to update the information contained herein. Unless specifically provided otherwise, LSR products are not suitable for, and shall not be used in, automotive applications. LSR’s products are not intended, authorized, or warranted for use as components in applications intended to support or sustain life.Mouser ElectronicsAuthorized DistributorClick to View Pricing, Inventory, Delivery & Lifecycle Information:L S Research:450-0105。
IBMx3650M4微码升级immv2uefiimmupdate
实用标准文档第一步，要按照如下方法把IMM2的IP 改成下图中的规格。
启动服务器后，可以使用BIOS 设置工具管理IMM 网络连接.开启服务器，通电大约两 分钟后,电源控制按钮将会激活,按下开机按钮,就会显示IBM System x Server Firmware 欢迎界面.按下F1 键.在 Setup utility 主窗口中，选择 System Settings - Integrated Management Module - Network Configuration.在 DHCP Control中有三个 IMM 网络连接选项(Static IP,DHCP Enabled,DHCPwith Failover(default). 选择其中一种网络连接方式.如果选择static IP ,须指定IP 地址,子网掩码，网关.(IP address,subnet mask and default gateway).设置完后选择 Save NetworkSett in gs 保存,退出 Setup utility.第二步，要在IBM 官网上下载以下两个文件(分别是 UEFI 和IMM2的升级文件)----------------------- 1Mtnrk CowfifuratliHi6Netuork Interface PortFaiPDver hile EuiiHfd In fkldrcssH DS I IUK<Ded kdted> <Mone> 40-r2-E9-?4^D-&E---This option wl)I illou youto select ijour Systen 能畑胆帕就 Network Inter 巾u Pn 「t ・DHCP CcHitrol IP Address Subtil Hdsk Derault Gdietuy (Static IP> 1324G6.70.125 25S.JS5,255.e 9.6.0.0inLomE Link Address<Endbled> FE8O ：：42F2：E1FF ：也4：9D 6E/S4114-floue Highlight <Enter>=Select E^itry Eac-Exlt(1.506M] DIMH Pbpu lat Inn Change Detected实用标准文档IEiM D EF-I l-las^i Update以下文件将彌该补「dn I bmjw_uefi_vv&15Qc-Z22_anyos_32-64,Ghg (13.2 KB) i d i ibir fv/ uc J i /7^153c-2.22 j" /U5 32-0-. 'Eitli 197 &j ibnn uefi we150c-Z22_anyos_32-64<txt (16-02 KB)以下■文件将丈為该补丁。
ImmuNet - 快速参考指南 - 基本指南说明书
Basic GuideWelcome to ImmuNet!By referring to the Basic Quick Reference Guide you will be able to:●Log in to ImmuNet●Manage Patients●Enter a New Patient●Add an Ordering Authority or Clinician●Add an Immunization to a Patient Record●View the Immunization Record●Print the Immunization Certificate●Save the Immunization Certificate●Change your ImmuNet PasswordTo go to the ImmuNet application, type into the address bar of your browser session and press Enter.Enter your User Nam e and Password and click Login.If you have forgotten your password, click Forgot Password. Enter your User Name and E-mail Address (that was used to register you with ImmuNet). You will be e-mailed a link that will enable you to reset your password or see your organization’s Admin User, who can reset your password.Log in to ImmuNetOn the left navigator click Patients , then click Patient Search or click the blue button Patient Search .Type in the First Name , Last Name , and Birth Date and click Search .Manage PatientsIf you find more than one patient, click on the appropriate blue last name link to access the record.If there are no records for the patient, you will see this message:Enter a New PatientTo create a new patient record, click Enter as New Patient.Enter in as much patient information as possible into the sections:●Patient Information●Address Information●Responsible PersonsClick Save.To perform this operation, you must have an ImmuNet access role of Admin User . To add a clinician, on the left navigator, click Manage Org Selections , Manage Clinicians .Add an Ordering Authority or ClinicianOn the right, click Add ClinicianClick the radio button Clinician.Type in the First Name, Last Name of the clinician.Under Complete Site Listing, click directly on the name of the organization and click Add (to add it under Selected Sites). Click Save.The message Record Updated will be displayed in red at the top, if successful.To add an Ordering Authority/Clinician, on the left navigator, click Manage Org Selections, Manage Clinicians.On the right, click Add ClinicianClick the radio button Ordering Authority/ClinicianEnter the Individual NPI (of the responsible provider of the organization) and click Validate.The First Name, Last Name and Address (not shown) information should automatically populate in the fields. Under Complete Site Listing, click directly on the name of your organization and click Add (to add it under Selected Sites).Click Save.The message (not shown) Record Updated will be displayed in red at the top, if successful. To remove a clinician,on the left navigator, click Manage Org Selections, Manage Clinicians.Click on the appropriate blue link of the clinician name.Click DeleteClick OK to the question that will be displayed at the top of the screen.Within the patient record, click Add Immunization.Go to the appropriate immunization name (row) under the appropriate vaccine type (column).Basic GuideFor VFC (Vaccines for Children) vaccines administered - Enter the Date Provided, Ordering Authority or Ordering Authority/Clinician, Trade Name-Lot, Administered By/Dose, Body Site/Route, VFC Eligibility.Click Save.Click Cancel or click the back arrow to enter additional vaccine administration for the same patient.For private vaccines administered - Enter the Date Provided, Ordering Authority, Trade Name, Dose, Lot Number, VFC Eligibility (select Not VFC Eligible), Administered By, and Funding Type (select Private).Click Save.Click Cancel or click the back arrow to enter additional vaccine administration for the same patient.For historical vaccines administered (vaccines administered by another provider) - Enter the Date Provided, Trade Name, Lot Number (if available), Historical Org Name (if available), and Source of Imm (if available).Click Save.Click Cancel or click the back arrow to enter additional vaccine administration for the same patient.Note: To enter multiple doses administered of the same vaccine for the same patient, enter a number greater than 1. Multiple rows will be displayed for the information to be entered.To view the immunization record on the screen, click History/Recommend.View the Immunization RecordView the patient’s immunization history in the section titled History. You can also view vaccines the patient is due based on the ACIP schedule in the section titled Vaccines Recommended by Selected Tracking Schedule.To view the 896 School Certificate, click Patient Reports. On the right, select your organization from the drop-down menu under Site. On the left click Maryland 896 School Certificate.To print, right-click directly on the certificate and click Printor click the printer icon in top-right corner of the screen.Basic GuideTo save, right-click directly on the certificate and click Save asor click the down-arrow icon in the top-right corner of the screen.To change your ImmuNet password, click My Account.On the left navigator click Manage My Account, Change My Password.Type in a new password in the New Password field and again in the Confirm New Password field, keeping in mind the guidelines for creating a new password.Click Save.If your password is accepted, you will see the following message in red at the top of the screen (if not, you will have to type a different password into the fields New Password and Confirm New Password and click Save).To access ImmuNet, Click Applications, ImmuNet.Click on the blue organization name link orclick on the appropriate organization link for which you are trying to access, if you have access to more than one organization.To learn how to navigate ImmuNet, click on ‘Resources’ then click ImmuNet Quick Reference Guide and ImmuNet Training Videos.Contact ImmuNet Support (here)with any questions.。
Immersive Display PRO User Guide
Immersive Display PRO是一个对DirectX, OpenGL 和Windows 7 桌面进行终极几何矫正与软边缘融合的软件包。
它基于成熟的Fly Elise-ng图像几何矫正和软边缘融合技术，支持多投影仪投影到规则和非规则的投影屏幕（包括圆柱屏幕，全部或部分圆顶屏幕以及其他形状的屏幕）。
Immersive Display PRO利用Fly Elise-ng核心组件进行图像几何矫正和软边缘融合配置、演示。
在一个简单的用户界面上，使用鼠标和键盘操作就可以将输出图像映射到任何一种投影屏幕。
调整细粒度和伽玛值对投影图像间重叠边缘进行融合。
一台投影仪的彩色矫正可以应用到其他投影仪的配置文件上。
Immersive Display PRO支持每台电脑最多连接10台投影仪，投影仪可以进行不同的水平和垂直位置叠加摆放。
其典型的应用是将飞行模拟器、赛车模拟器、投影仪模式的家庭影院等其他第一人称的软件，用多投影仪全方位的融合到投影屏幕上。
Immersive Display PRO是为家庭和特定环境设计的。
其应用领域有：●家庭娱乐系统●飞行、船舶和汽车模拟器●业务数据可视化●互动触摸显示器●会议室●视频播放●实时数字移动图形以下是所需的最低配置：2.1 2.0GHz或更高处理器（32位或64位）2.22G或以上内存2.3一个合适的显卡（NVIDIA 或AMD/ATI）2.4为能够在Windows7下进行广泛的多投影仪显示，需做以下要求：2.4.1NVIDIA显卡需要支持NVIDIA环绕2D2.4.2ATI 显卡需要支持ATI Eyefinity(宽域多屏显卡)2.4.3Matrox DialHead2GO或者TrippleHead2GO(多屏宝)，外部硬件盒2.5需要Administrator权限安装Immersive Display PRO2.6不需要Administrator权限运行Immersive Display PRO3安装和卸载3.1安装注意：Immersive Display PRO使用DirectX运行时集约。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
IMM使用指南
一．如何访问IMM (1)
二．IMM主要功能介绍 (4)
三．几个常用功能 (5)
1．远程开关机 (5)
2．通过IMM刷新服务器的UEFI/IMM微码 (6)
3．远程终端功能 (7)
一．如何访问IMM
通常主机后部有一个专用的管理端口，例如下图以3650M3为例，可以通过此端口访问IMM。
IMM管理端口默认IP：192.168.70.125
用户名：USERID
密码：PASSW0RD
注意字母为大写，密码中的“0”是数字0
在UEFI中修改IMM的IP地址
在开机自检的过程中根据提示按F1进入UEFI设置，
输入需要修改的IP地址后，选择Save Network Settings
在IE中输入IP地址即可访问IMM管理界面
二．IMM主要功能介绍
System status
查看服务器的健康状况，包括温度、电压和风扇状态等。
Virtual Light Path
查看服务器光通路诊断板上是否有告警。
Event Log
可以查看服务器的日志信息，可以用Save Log as Text File另存日志信息为文本文件。
Vital Product Data
查看服务器的型号序列号及各种微码版本。
Power/Restart
通过IMM控制开关服务器，包括定时开关机功能
Remote Control
远程控制服务器终端，需要添加IBM Virtual Media Key选件来实现此功能，大部分机型标配没有此选件。
PXE Network Boot
设置服务器的PXE启动。
Firmware Update
刷新服务器的UEFI和IMM的微码。
System Settings
设置IMM的时间日期，名字等基本信息。
Login Profiles
为IMM添加除默认之外的其他用户。
Alerts
设置snmp告警等信息。
Serial Port
设置串口信息
Port assignments
定义IMM所使用的端口。
Network Interfaces
设置IMM的网络地址
Network Protocols
配置SNMP，DNS等网络协议
Security
配置SSL、SSH等安全协议
Configuration File
备份和恢复IMM的配置文件
Restore Default Settings
将IMM恢复默认设置
Restrat IMM
重启IMM
Log off
退出登录
三．几个常用功能
1．远程开关机
选择Power/Restart选项可以实现远程开机、关机和重启
在Schedule Daily/Weekly Power and Restart Actions中可以实现每天定时的开关服务器。
2．通过IMM刷新服务器的UEFI/IMM微码
选择Firmware Update，然后在浏览中选中微码刷新文件，此处以3650M3的UEFI刷新为例，文件名为ibm_fw_uefi_d6e149a_windows_32-64.exe，注意刷新微码前服务器需要开机。
选择文件后点选update，会出现上传微码的界面，完成后会有现有旧微码和新微码的信息，例如“The current build id is D6E148B.You will be installing D6E149A build id”
点击continue会开始刷新进程
3．远程终端功能
此功能需要添加IBM Virtual Media Key选件来实现此功能，大部分机型标配没有此选件。
同时要求打开远程控制的客户机（登录IMM界面的台式机或者笔记本，不是指控制的目标服务器）需要安装JRE（Java Runtime Environment）软件，可以到java网站下载
/zh_CN/
打开菜单中的Remote Console页面，如果只允许一个用户连接到服务器终端选择Start Remote Control in Single User Mode；如允许多用户同时连接选择Start Remote Control in Multi-user Mode。
选择后可以打开终端窗口，可以对服务器的终端进行控制。
虚拟媒体功能
利用IMM的虚拟媒体功能可以将本地PC机、笔记本上的光驱/软驱、或者iso/img镜像文件远程的挂载给服务器使用。
在虚拟媒体窗口中选中要挂载到远程服务器的光驱前面的Map选项，然后选择右边的Mount Selected按钮，就可以实现把本地的光驱挂载到服务器上，比如例子中将本地插有windows2003光盘的光驱F挂载到服务器上，服务器启动后就可以从挂载的光驱启动安装
windows操作系统了。
选择Add Image可以将本地的iso/img镜像挂载到远程服务器上。