LOGICAD 40_13_Application Structure (engl) v1.00

合集下载

响应AutoCAD消息

响应AutoCAD消息

AutoCAD 传递给ObjectARX应用程序的消息有四类:•传送给所有应用程序的消息.•仅当应用程序使用acedDefun()注册AutoLISP函数时传送的消息•传递给用ObjectARX已经注册服务的应用程序消息•只对使用ActiveX控件的应用程序需要作出响应的消息下面五个表分别介绍了AutoCAD传送给ObjectARX应用程序的消息.下表列举了传送给所有应用程序的消息.kInitAkInitAppMsg 当ObjectARX应用程序被加载并打开AutoCAD和应用程序之间通信时发送的消息.kUnloadAppMsg 当ObjectARX应用程序被卸载时(当卸载应用程序或退出AutoCAD时)发送该消息.关闭文件并清除操作kLoadDwgMsg 当打开图形时发送该消息.然后,如果应用程序使用AutoLISP注册函数时,AutoCAD向调入编辑器的每一个图形发送该消息.此时,AutoCAD编辑器已被完全初始化,所有全局函数都可用. 但是,在kLoadDwgMsg时不能使用acedCommand()函数kSaveMsg 当输入了SAVEAS、NEW或OPEN命令后,在AutoCAD保存图形时发送该消息kUnloadDwgMsg 当退出图形窗口时发送该消息kPreQuitMsg 当退出AutoCAD时,在开始卸载所有ObjectARX应用程序之前发送该消息.下表列出了应用程序使用acedDefun()注册AutoLISP函数时,AutoCAD发送给应用程序的消息kInvkSubrMsg 当使用acedDefun()调用函数注册时发送此消息kEndMsg 只有当图形被修改,输入END命令后,需要保存时(当dbmode不为0)发送此消息.对NEW或OPEN命令,不发送此消息,而发送kSaveMsg和kLoadDwgMsg.对END命令,如果dbmode为0,则发送kQuitMsg,而不是kEndMsg.(2000后END命令停止使用)kQuitMsg 当输入QUIT命令后AutoCAD退出(退出但不存盘)时发送该消息. 注释: kQuitMsg消息发送与KPreQuitMsg消息之前.kCfgMsg 只有当改变了显示驱动程序,AutoCAD从配置程序返回时发送该消息. 下表列出了如果使用ObjectARX已注册一个服务时应用程序收到的消息.kDependencyMsg 当ObjectARX应用程序已经注册了一个AcRxService对象,并且该服务的从属计数器从0变为1时发送该消息kNoDependencyMsg 当ObjectARX应用程序已经注册了一个AcRxService对象,并且该服务的从属计数器从1变为0时发送该消息.下表列出了如果应用程序使用ActiveX Automation时需要响应的消息.kOleUnloadAppMsg 确定应用程序是否可以被卸载时发送该消息(没有其他应用程序引用ActiveX对象或界面).在rxdefs.h文件中,AppMsgCode类说明定义了这些枚举常量.我们必须确定ObjectARX应用程序将对哪一个消息作出响应.下表介绍了收到每一个消息后的推荐操作内容kInitAppMsg 允许注册服务、类、AcEd命令及反应器和AcRxDymicLinker 反应器;初始化应用程序系统资源,如设备和窗口;执行所用初始化工作;AcRx、AcEd和AcGe都被激活;如果想解锁和锁定其应用程序时,保存pkt参数值.不允许初始化设备驱动程序、激活任意接口资源,以特殊的顺序加载应用程序、调用AutoLISP或者打开任意数据库.否则会引起错误甚至导致系统崩溃.虽然有关的Ac结Rx和其他结构被激活,但AcDb和AcGi库通常尚未被激活 .kUnloadAppMsg 允许执行最后系统资源清理工作,任何在kInitAppMsg中开始或创建对象,应当在此处停止或析构.不要除在kIniAppMsg中激活库外,当调用了该消息时,AutoCAD 通常被卸载 .kOleUnloadAppMsg 允许只有使用ActiveX的应用程序响应此消息.不允许:如果应用程序可以被卸载(没有其他应用程序引用该应用程序的ActiveX对象或界面).以AcRx::kRetOK回应.如果应用程序不能被卸载,则以AcRx::kRetError回应kLoadDwgMsg 执行有关当前图编辑会话的初始化。

ioLogik E1200系列产品(E1210)更新说明书

ioLogik E1200系列产品(E1210)更新说明书

Firmware for ioLogik E1200 Series (E1210) Release NotesSupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Fixed inaccurate counter value when using Modbus to start a pulse (E1210/E1212/E1213).• Fixed opposite on/off pulse width display on web console (E1211/E1212/E1214).• Fixed that the offset scaling value will reset after changing the Alias name (E1260).• Fixed self-rebooting when entering URL in the browser for the configuration file.• Fixed EDS file import connection error.• Fixed failure when using save counter on power failure and reset counter at the same time (E1210/E1212/E1213).• Fixed inaccurate counter value when using high frequency (E1210/E1212/E1213).• Fixed that the trap community name is not included in the export file.• Fixed that EtherNet/IP cannot use the “Set Attribute Single” service.• Added an enable RESTful API setting in the configuration file.EnhancementsN/AioLogik E1210, ioLogik E1210-T• EtherNet/IP registration on Moxa’s licensing website is no longer required.• Added case insensitive content-length for RESTful API.New FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs Fixed• Added SNMP Trap Community Setting to the web console.• Added a note on the password settings page that passwords are limited to 16 characters.• Fixed DHCP lease time did not ask for extension when half of the lease time elapsed.• Closed IP forwarding function (Port 0).• Closed UDP Port 161 when SNMP agent is disabled.• Fixed RESTful API header case-sensitive issue.• Fixed invalid token issue on login page when using Firefox.EnhancementsN/AioLogik E1210-T, ioLogik E1210• Added OPTIONS method for RESTful API.• Added quick access URI for RESTful API.New FeaturesN/A• This version of the firmware only works with ioSearch v2.0 or later versions.• To prevent system failure, only update the next or the previous released firmware version to prevent from system failure.Supported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Fixed file transfer problems when using the Chrome browser (e.g., firmware update, configuration import or export).EnhancementsN/AioLogik E1210, ioLogik E1210-T• Added the EtherNet/IP protocol.• Added RESTful API.• Added new registers for the Modbus/TCP protocol.• Added new OIDs for the SNMP protocol.• Modbus, EtherNet/IP, and RESTful services can be disabled (enabled by default).• Added sending heartbeat to port 9500 of MX-AOPC UA Server after the heartbeat function is enabled.• Increased password length from 8 to 16 characters.• Added a function to check special characters to prevent Cross-Site Scripting.• Passwords are now sent using the POST method instead of the GET method.New FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/AN/AEnhancementsN/AioLogik E1210, ioLogik E1210-T• Improved protocol efficiency for the ioLogik 2500 Series.New FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Unable to disable the P2P heartbeat interval.• When the P2P client heartbeat is larger than 256 the time interval is incorrect.EnhancementsN/AioLogik E1210, ioLogik E1210-T• Supports ioLogik 2500 expansion mode.• Supports setting an initial value for a counter.New FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• The counter storage is deleted when the power fails.EnhancementsN/AioLogik E1210-T, ioLogik E1210• Supports SNMP protocol.• Added P2P heartbeat function.New FeaturesN/A• This version of firmware only works with ioSearch v1.5 or later versions.• Use the web console when upgrading the firmware from v1.0 to v1.10.Supported Operating SystemsNotesChangesApplicable ProductsBugs Fixed• Ensured that the system works properly after unstable power conditions.N/AEnhancementsN/AioLogik E1210, ioLogik E1210-TN/ANew FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs Fixed• Improved firmware upgrading speed.• Removed Modbus/TCP ID checking mechanism.N/AEnhancementsN/AioLogik E1210, ioLogik E1210-T• Added "Locating I/O" function in General Settings.• Added Modbus address function code=0x08 for “ECHO” function.• Counter overflow status displayed in Channel Settings can be cleared manually.New FeaturesN/A• This version of the firmware only works with ioSearch v1.5 or later versions.• Use the web console when upgrading the firmware from v1.0 to v1.9.。

IKCS12F60F2A_C_Rev1_0_20100628(10)

IKCS12F60F2A_C_Rev1_0_20100628(10)

F o r P o w e r M a n a g e m e n t A p p l i c a t i o nControl Integrated POwer System (CIPOS™)I K C S 12F 60F 2A I K C S 12F 60F 2CD a t a S he e t ,J un. 2010CIPOS™ IKCS12F60F2AIKCS12F60F2CRevision History: 2010-06Rev.1.0Authors: Junho Song*, Junbae Lee* and Daewoong Chung*, W. Frank**, W. Brunnbauer**LS Power Semitech*, Infineon Technologies**Edition 2010-01Published byLS Power Semitech Co., Ltd. Seoul, Korea© LS Power Semitech Co., Ltd.All Rights Reserved.Attention please!The information given in this data sheet shall in no event be regarded as a guarantee of conditions or characteristics. With respect to any examples or hints given herein, any typical values stated herein and/or any information regarding the application of the device, LS Power Semitech Co., Ltd. hereby disclaims any and all warranties and liabilities of any kind, including without limitation warranties of non-infringement of intellectual property rights of any third party.InformationFor further information on technology, delivery terms and conditions and prices please contact your nearest LS Power Semitech Co., Ltd. office or representatives ().WarningsDue to technical requirements components may contain dangerous substances. For information on the types in question please contact your nearest LS Power Semitech Co., Ltd. office or representatives.LS Power Semitech Co., Ltd. components may only be used in life-support devices or systems with the express written approval LS Power Semitech Co., Ltd., if a failure of such components can reasonably be expected to cause the failure of that life-support device or system, or to affect the safetyor effectiveness of that device or system. Life support devices or systems are intended to be implantedin the human body, or to support and/or maintain and sustain and/or protect human life. If they fail, it is reasonable to assume that the health of the user or other persons may be endangered.TRENCHSTOP® is a registered trademark of Infineon Technologies AG.CIPOS™ IKCS12F60F2AIKCS12F60F2CTable of contents:CIPOS™ Control Integrated POwer System (4)Features (4)Target Applications (4)Description (4)System Configuration (4)Certification (4)Internal Electrical Schematic (5)Pin Assignment (6)Pin Description (6)HIN1,2,3 and /LIN1,2,3 (Low side and high side control pins, Pin 15 - 20) (6)FLT-TEMP (temperature NTC, Pin 24) (7)ITRIP (Over-current detection function, Pin 21) (7)VDD, VSS (control side supply and reference, Pin 22, 23) (7)VB1,2,3 and VS1,2,3 (High side supplies, Pin 1, 2, 4, 5, 7, 8) (7)VRU, VRV, VRW (low side emitter, Pin 12, 13, 14) (7)V+ (positive bus input voltage, Pin 10) (7)Absolute Maximum Ratings (8)Module Section (8)IGBT and Diode Section (8)Control Section (9)Recommended Operation Conditions (9)Static Characteristics (10)Dynamic Characteristics (11)Integrated Components (12)Typical Application (12)Characteristics (13)Package Outline IKCS12F60F2A (17)Package Outline IKCS12F60F2C (18)CIPOS™ IKCS12F60F2AIKCS12F60F2CCIPOS™C ontrol I ntegrated PO wer S ystem Single In-Line Intelligent Power Module3Φ-bridge 600V / 12A @ 25°CFeatures•DCB isolated Single In-Line molded module •FAULT signal•TrenchStop® IGBTs with lowest V CE(sat)•Optimal adapted antiparallel diode for low EMI •Integrated bootstrap diode and capacitor •Rugged SOI gate driver technology with stability against transient and negative voltage •Fully compliant to 3.3V and 5V microcontrollers •Temperature sense•Under voltage lockout at all channels •Matched propagation delay for all channels •Low side emitter pins accessible for all phase current monitoring (open emitter)•Cross-conduction prevention•Lead-free terminal plating; RoHS compliant •Qualified according to JEDEC1 (high temperature stress tests for 1000h) for target applicationsTarget Applications•Washing machines•Consumer Fans and Consumer Compressors DescriptionThe CIPOS™ module family offers the chance for integrating various power and control components to increase reliability, optimize PCB size and system costs.This SIL-IPM is designed to control AC motors in variable speed drives for applications like air conditioning, compressors and washing machines. The package concept is specially adapted to power applications, which need extremely good thermal conduction and electrical isolation, but also EMI-save control and overload protection. The features of TrenchStop®IGBTs and antiparallel diodes are combined with a new optimized Infineon SOI gate driver for excellent electrical performance. The product provides a FAULT signal, which is significantly simplifying the system.System Configuration• 3 half-bridges with TrenchStop®IGBT & FW-diodes•3Φ SOI gate driver•Bootstrap diodes for high side supply •Integrated 100nF bootstrap capacitance •Temperature sensor, passive components for adaptions•Isolated heatsink•Creepage distance typ 3.2mmCertificationUL 1577 (UL file E314539)CIPOS™ IKCS12F60F2A IKCS12F60F2CInternal Electrical SchematicFigure 1: Internal SchematicVSS (23)/LIN3 (20)/LIN2 (19)/LIN1 (18)/HIN3 (17)/HIN2 (16)/HIN1 (15)VDD (22)VB1 (7)VB2 (4)VB3 (1)VRW (14)VRV (13)VRU (12)W, VS3 (2)V, VS2 (5)U, VS1 (8)V+ (10)/FLT-TEMP (24)ITRIP (21)CIPOS™ IKCS12F60F2A IKCS12F60F2CPin AssignmentPin Description/HIN1,2,3 and /LIN1,2,3 (Low side and high side control pins, Pin 15 - 20)These pins are active low and they are responsible for the control of the integrated IGBTsuch to guarantee LSTTL and CMOS compatibility down to 3.3V controller outputs. The maximum voltage at these pins is 5.5V and therefore fully compliant to 3.3V-microcontrollers. Pull-up resistor of about 75k Ω is internally provided to pre-bias inputs during supply start-up and a zener clamp is provided for pin protection purposes. Input schmitt-trigger and noise filter provide beneficial noise rejection to short input pulses. It is recommended for proper work of CIPOS™ not to provide an input pulse-width and PWM deadtimes lower than 1us.The integrated gate drive provides additionally a shoot through prevention capability which avoids the simultaneous on-state of two gate drivers ofFigure 2: Input pin structureCIPOS™ IKCS12F60F2A IKCS12F60F2Cthe same leg (i.e. HO1 and LO1, HO2 and LO2, HO3 and LO3).A minimum deadtime insertion of typ 380ns is also provided, in order to reduce cross-conduction of the external power switches./FLT-TEMP (temperature NTC, Pin 24)The TEMP terminal provides direct access to the NTC, which is referenced to VSS. An external pull-up resistor connected to +5V ensures, that the resulting voltage can be directly connected to the microcontroller.The same pin indicates a module failure in case of under voltage at pin VDD or in case of triggered over current detection at ITRIP. A pull-up resistor is externally required to bias the NTC. No temperature information is available during fault. ITRIP (Over-current detection function, Pin 21) CIPOS™ provides an over-current detection function by connecting the ITRIP input with the motor current feedback. The ITRIP comparator threshold (typ 0.46V) is referenced to VSS ground. A input noise filter (typ: t ITRIPMIN = 225ns) prevents the driver to detect false over-current events. Over-current detection generates a hard shut down of all outputs of the gate driver after the shutdown propagation delay of typically 900ns. The fault-clear time is set to typically to 4.7ms. VDD, VSS (control side supply and reference, Pin 22, 23)VDD is the low side supply and it provides power both to input logic and to low side output power stage. Input logic is referenced to VSS ground as well as the under-voltage detection circuit. The under-voltage circuit enables the device to operate at power on when a supply voltage of at least a typical voltage of V DDUV+ = 12.1V is at least present.The IC shuts down all the gate drivers power outputs, when the VDD supply voltage is below V DDUV- = 10.4V. This prevents the external power switches from critically low gate voltage levels during on-state and therefore from excessive power dissipation.VB1,2,3 and VS1,2,3 (High side supplies, Pin 1, 2, 4, 5, 7, 8)VB to VS is the high side supply voltage. The high side circuit can float with respect to VSS following the external high side power device emitter/source voltage.Due to the low power consumption, the floating driver stage is supplied by an integrated bootstrap circuit connected to VDD. This includes also integrated bootstrap capacitors of 100nF at each floating supply, which are located very close to the gate drive circuit.The under-voltage detection operates with a rising supply threshold of typical V BSUV+ = 12.1V and a falling threshold of V DDUV- = 10.4V according to Figure 4.VS1,2,3 provide a high robustness against negative voltage in respect of VSS of -50V. This ensures very stable designs even under rough conditions.Figure 4: Operation modesVRU, VRV, VRW (low side emitter, Pin 12, 13, 14)The low side emitters are available for current measurements of each phase leg. It is recommended to keep the connection to pin VSS as short as possible in order to avoid unnecessary inductive voltage drops.V+ (positive bus input voltage, Pin 10)The high side IGBT are connected to the bus voltage. It is recommended, that the bus voltage does not exceed 500V.CIPOS™ IKCS12F60F2AIKCS12F60F2CAbsolute Maximum Ratings(T J = 25°C, V DD = 15V Unless Otherwise Specified): Module SectionIGBT and Diode Section1 Monitored by pin 24CIPOS™ IKCS12F60F2A IKCS12F60F2CControl SectionRecommended Operation ConditionsAll voltages are absolute voltages referenced to V SS -Potential unless otherwise specified.IKCS12F60F2CStatic Characteristics(T c = 25°C, V DD = 15V, if not stated otherwise)1 Allowed number of short circuits: <1000; time between short circuits: >1s.Dynamic Characteristics(T c = 25°C, V DD = 15V, if not stated otherwise)Integrated ComponentsTypical Application1Characteristics(T c = 25°C, V DD = 15V, if not stated otherwise)I C , C O L L E C T O R C U R R E N TI F , f o r w a r d C U R R E N TV CE , COLLECTOR EMITTER VOLTAGEV F FORWARD VOLTAGEFigure 4. Typical IGBT output characteristicFigure 5. Typical diode forward current as afunction of forward voltaget , S W I T C H I N G T I M E S0A 5A 10A 15At , S W I T C H I N G T I M E S25℃50℃75℃100℃125℃I C , COLLECTOR CURRENTT vJ , JUNCTION TEMPERATUREFigure 6. Typical switching times as afunction of collector current (inductive load,T vJ =150°C,V CE =300VDynamic test circuit in Figure A)Figure 7. Typical switching times as afunction of junction temperature (inductive load, V CE = 300V, I C = 6A Dynamic test circuit in Figure A)E , S W I T C H I N G E N E R G YE , S W I T C H I N G E N E R G YI C , COLLECTOR CURRENTT vJ , JUNCTION TEMPERATUREFigure 8. Typical switching energy losses asa function of collector current (inductive load, T vJ =150°C, V CE =300VDynamic test circuit in Figure A)Figure 9. Typical switching energy losses asa function of junction temperature (inductive load, V CE = 300V, I C = 6A Dynamic test circuit in Figure A)R T S , N T C r e s i s t a n c eZ t h J C , T R A N S I E N T T H E R M A L R E S I S T A N C E10-210-1100 T NTC , NTC TEMPERATUREt P , PULSE WIDTHFigure 10. Characteristic of NTC as afunction of NTC temperatureFigure 11. Transient thermal impedance as afunction of pulse width (D =t P /T )Test Circuits and Parameter DefinitionFigure A: Dynamic test circuit Leakage inductance L σ =180nH Stray capacitance C σ =39pFFigure B: Definition of diodes switching characteristicsFigure C: Definition of Enable propagation delayFigure D: Switching times definition and switching energy definitionI RRMI FLIN1,2,3HIN1,2,3i CU , i CV , i v CEU , v CEV ∫⋅=Cx CEx dti v Eoff 0∫⋅=Eont Cx CEx dti v Eon 0Figure E: Short Pulse suppressionPackage Outline IKCS12F60F2ANote: There may occur discolorations on the copper surface without any effect of the thermal properties.Package Outline IKCS12F60F2CPackage Data。

斑马技术公司DS8108数字扫描仪产品参考指南说明书

斑马技术公司DS8108数字扫描仪产品参考指南说明书
Chapter 1: Getting Started Introduction .................................................................................................................................... 1-1 Interfaces ....................................................................................................................................... 1-2 Unpacking ...................................................................................................................................... 1-2 Setting Up the Digital Scanner ....................................................................................................... 1-3 Installing the Interface Cable .................................................................................................... 1-3 Removing the Interface Cable .................................................................................................. 1-4 Connecting Power (if required) ................................................................................................ 1-4 Configuring the Digital Scanner ............................................................................................... 1-4

3GPP TS 31.111 V8.4.0

3GPP TS 31.111 V8.4.0

3GPP TS 31.111 V8.4.0 (2009-01)Technical Specification3rd Generation Partnership Project;Technical Specification Group Core Network and Terminals;Universal Subscriber Identity Module (USIM)Application Toolkit (USAT)(Release 8)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM ) and may be further elaborated for the purposes of 3GPP.The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.KeywordsUMTS, SIM, Card, LTE3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16InternetCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© 2009, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).All rights reserved.UMTS™ is a Trade Mark of ETSI registered for the benefit of its members3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational PartnersContents Foreword (9)1Scope (10)2References (10)3Definitions, abbreviations and symbols (12)3.1Definitions (12)3.2Abbreviations (12)3.3Symbols (12)4Overview of USAT (12)4.1Profile Download (12)4.2Proactive UICC (13)4.3Data download to UICC (13)4.4Menu selection (13)4.5Call control by USIM (13)4.6MO Short Message control by USIM (13)4.7Event download (13)4.8Security (13)4.9Multiple card (13)4.10Timer Expiration (13)4.11Bearer Independent Protocol (13)4.12Description of the access technology indicator mechanism (14)4.13Description of the network search mode mechanism (14)4.14Geographical location discovery (14)5Profile download (14)5.1Procedure (14)5.2Structure and coding of TERMINAL PROFILE (14)5.3Definition of display parameters in Profile download (18)6Proactive UICC (18)6.1Introduction (18)6.2Identification of ME support (18)6.3General procedure (18)6.4Proactive UICC commands and procedures (18)6.4.1DISPLAY TEXT (18)6.4.2GET INKEY (18)6.4.3GET INPUT (19)6.4.4MORE TIME (19)6.4.5PLAY TONE (19)6.4.6POLL INTERVAL (19)6.4.7REFRESH (19)6.4.7.1EF IMSI changing procedure (19)6.4.7.2Generic Bootstrapping Procedure Request (19)6.4.8SET UP MENU (20)6.4.9SELECT ITEM (20)6.4.10SEND SHORT MESSAGE (20)6.4.11SEND SS (20)6.4.12SEND USSD (21)6.4.12.1MMI Mode (21)6.4.12.2Application Mode (22)6.4.13SET UP CALL (23)6.4.14POLLING OFF (23)6.4.15PROVIDE LOCAL INFORMATION (23)6.4.16SET UP EVENT LIST (25)6.4.17PERFORM CARD APDU (25)6.4.18POWER OFF CARD (25)6.4.23RUN AT COMMAND (25)6.4.24SEND DTMF (25)6.4.25LANGUAGE NOTIFICATION (25)6.4.26LAUNCH BROWSER (26)6.4.27OPEN CHANNEL (26)6.4.27.1OPEN CHANNEL related to CS bearer (26)6.4.27.2OPEN CHANNEL related to GPRS/3G packet service (26)6.4.27.3OPEN CHANNEL related to local bearer (26)6.4.27.4OPEN CHANNEL related to Default (network) Bearer (27)6.4.27.5OPEN CHANNEL related to I-WLAN bearer (27)6.4.27.6OPEN CHANNEL related to Terminal Server Mode (28)6.4.28CLOSE CHANNEL (28)6.4.29RECEIVE DATA (28)6.4.30SEND DATA (28)6.4.31GET CHANNEL STATUS (28)6.4.32SERVICE SEARCH (28)6.4.33GET SERVICE INFORMATION (28)6.4.34DECLARE SERVICE (28)6.4.35RETRIEVE MULTIMEDIA MESSAGE (28)6.4.36SUBMIT MULTIMEDIA MESSAGE (28)6.4.37DISPLAY MULTIMEDIA MESSAGE (28)6.4.38SET FRAMES (29)6.4.39GET FRAME STATUS (29)6.4.40Geographical Location Request (29)6.5Common elements in proactive UICC commands (30)6.6Structure of proactive UICC commands (30)6.6.1DISPLAY TEXT (30)6.6.2GET INKEY (30)6.6.3GET INPUT (30)6.6.4MORE TIME (30)6.6.5PLAY TONE (30)6.6.6POLL INTERVAL (30)6.6.7SET-UP MENU (30)6.6.8SELECT ITEM (30)6.6.9SEND SHORT MESSAGE (30)6.6.10SEND SS (31)6.6.11SEND USSD (31)6.6.12SET UP CALL (31)6.6.13REFRESH (31)6.6.14POLLING OFF (31)6.6.15PROVIDE LOCAL INFORMATION (32)6.6.16SET UP EVENT LIST (32)6.6.17PERFORM CARD APDU (32)6.6.18POWER OFF CARD (32)6.6.19POWER ON CARD (32)6.6.20GET READER STATUS (32)6.6.21TIMER MANAGEMENT (32)6.6.22SET UP IDLE MODE TEXT (32)6.6.23RUN AT COMMAND (32)6.6.24SEND DTMF COMMAND (32)6.6.25LANGUAGE NOTIFICATION (32)6.6.26LAUNCH BROWSER (32)6.6.27OPEN CHANNEL (33)6.6.27.1OPEN CHANNEL related to I-WLAN Bearer (33)6.6.28CLOSE CHANNEL (33)6.6.29RECEIVE DATA (33)6.6.30SEND DATA (33)6.6.31GET CHANNEL STATUS (33)6.6.36SUBMIT MULTIMEDIA MESSAGE (34)6.6.37DISPLAY MULTIMEDIA MESSAGE (34)6.6.38SET FRAMES (34)6.6.39GET FRAMES STATUS (34)6.6.40Geographical Location Request (34)6.7Command results (34)6.8Structure of TERMINAL RESPONSE (35)6.8.1Command details (36)6.8.2Device identities (36)6.8.3Result (36)6.8.4Duration (37)6.8.5Text string (37)6.8.6Item identifier (37)6.8.7Local information (37)6.8.8Call control requested action (37)6.8.9Result data object 2 (37)6.8.10Card reader status (37)6.8.11Card ATR (37)6.8.12R-APDU (37)6.8.13Timer identifier (37)6.8.14Timer value (37)6.8.15AT Response (38)6.8.16Text string 2 (38)6.8.17Channel data (38)6.8.18Channel status (38)6.8.19Channel data length (38)6.8.20Bearer description (38)6.8.21Buffer size (38)6.8.22Total Display Duration (38)6.8.23Service Availability (38)6.8.24Service Record (38)6.9Proactive UICC session and ME display interaction (38)6.10Handling of unknown, unforeseen and erroneous messages (38)6.11Proactive commands versus possible Terminal response (38)7ENVELOPE Commands (39)7.1Data download to UICC (39)7.1.1SMS-PP data download (39)7.1.1.1Procedure (39)7.1.1.2Structure of ENVELOPE (SMS-PP DOWNLOAD) (40)7.1.2Cell Broadcast data download (41)7.1.2.1Procedure (41)7.1.2.2Structure of ENVELOPE (CELL BROADCAST DOWNLOAD) (42)7.2Menu Selection (42)7.3Call Control and MO SMS control by USIM (42)7.3.1Call Control by USIM (42)7.3.1.1Procedure for mobile originated calls (42)7.3.1.2Procedure for Supplementary Services and USSD (43)7.3.1.3Indication to be given to the user (44)7.3.1.4Interaction with Fixed Dialling Number (45)7.3.1.5Support of Barred Dialling Number (BDN) service (45)7.3.1.6Structure of ENVELOPE (CALL CONTROL) (45)7.3.1.7Procedure for PDP Context Activation (47)7.3.2MO Short Message Control by USIM (48)7.3.2.1Description (48)7.3.2.2Structure of ENVELOPE (MO SHORT MESSAGE CONTROL) (48)7.3.2.3Indication to be given to the user (49)7.3.2.4Interaction with Fixed Dialling Number (49)7.4Timer Expiration (49)7.5.1.2Structure of ENVELOPE (EVENT DOWNLOAD – I-WLAN Access Status) (50)7.5.2Network Rejection event (51)7.5.2.1Procedure (51)7.5.2.2 Structure of ENVELOPE (EVENT DOWNLOAD – Network Rejection) (51)7.6USSD Data Download (52)7.6.1Procedure (52)7.6.2Structure of ENVELOPE (USSD Data Download) (52)7.7MMS Transfer Status (53)7.8MMS notification download (53)7.9Terminal Applications (53)7.10Geographical Location Reporting (53)7.10.1Procedure (53)7.10.2Structure of ENVELOPE (Geographical Location Reporting) (53)8COMPREHENSION-TLV data objects (54)8.1Address (54)8.2Alpha identifier (54)8.3Subaddress (54)8.4Capability configuration parameters (54)8.5Cell Broadcast Page (54)8.6Command details (54)8.7Device identities (55)8.8Duration (55)8.9Item (55)8.10Item identifier (55)8.11Response length (55)8.12Result (55)8.12.1Additional information for SEND SS (56)8.12.2Additional information for ME problem (56)8.12.3Additional information for network problem (56)8.12.4Additional information for SS problem (56)8.12.5Additional information for SMS problem (56)8.12.6Not used (57)8.12.7Additional information for USSD problem (57)8.12.8Additional information for interaction with call control or MO SM control (57)8.13SMS TPDU (57)8.14SS string (57)8.15Text string (58)8.16Tone (58)8.17USSD string (58)8.18File List (58)8.19Location Information (58)8.20IMEI (59)8.21Help Request (59)8.22Network Measurement Results (59)8.23Default Text (59)8.24Items Next Action Indicator (59)8.25Event list (59)8.26Cause (60)8.27Location status (60)8.28Transaction identifier (60)8.29BCCH channel list (60)8.30Call control requested action (61)8.31Icon Identifier (61)8.32Item Icon Identifier list (61)8.33Card reader status (61)8.34Card ATR (61)8.35C-APDU (61)8.36R-APDU (62)8.40AT Command (62)8.41AT Response (62)8.42BC Repeat indicator (62)8.43Immediate response (63)8.44DTMF string (63)8.45Language (63)8.46Timing Advance (63)8.47Browser Identity (63)8.48URL (63)8.49Bearer (63)8.50Provisioning File Reference (64)8.51Browser Termination Cause (64)8.52Bearer description (64)8.52.1Bearer parameters for CSD (64)8.52.2Bearer parameters for GPRS/3G Packet Service (64)8.52.3Bearer parameters for UTRAN Packet Service with extended parameters / HSDPA (65)8.52.4 Bearer parameters for I-WLAN (66)8.53Channel data (66)8.54Channel data length (66)8.55Buffer size (66)8.56Channel status (66)8.57Card reader identifier (66)8.58Other Address (66)8.59UICC/ME interface transport level (67)8.60AID (67)8.61Network Access Name (67)8.62Access Technology (67)8.63Display parameters (67)8.64Service Record (67)8.65Device Filter (67)8.66Service Search (67)8.67Attribute Information (67)8.68Service Availability (67)8.69Remote Entity Address (67)8.70Text Attribute (67)8.71Item Text Attribute List (68)8.72PDP context Activation parameters (68)8.73UTRAN Measurement Qualifier (68)8.74Multimedia Message Reference (68)8.75Multimedia Message Identifier (68)8.76Multimedia Message Transfer status (68)8.77MM Content Identifier (68)8.78Multimedia Message Notification (68)8.79Last Envelope (69)8.80Frames Layout (69)8.81Frames Information (69)8.82Frames identifier (69)8.83I-WLAN Identifier (69)8.84I-WLAN Access Status (69)8.85IMEISV (69)8.86Network search mode (69)8.87Battery State (69)8.88Browsing status (69)8.89Registry application data (70)8.90PLMNwAcT List (70)8.91Routing Area Identification (70)8.92Update/Attach Type (70)8.93Rejection Cause Code (71)8.96NMEA sentence (74)8.97PLMN List (74)9Tag values (74)9.1BER-TLV tags in ME to UICC direction (74)9.2BER-TLV tags in UICC TO ME direction (75)9.3COMPREHENSION-TLV tags in both directions (75)Type of Command and Next Action Indicator (75)I Allowed Type of command and Device identity combinations (75)11Security requirements (76)Annex A (normative): Support of USAT by Mobile Equipment (77)Annex B (informative): Example of DISPLAY TEXT Proactive UICC Command (78)Annex C (normative): Structure of USAT communications (79)Annex D (informative): ME display in proactive UICC session (80)Annex E (informative): Help information feature processing (81)Annex F (informative): Monitoring of events (82)Annex G (normative): Support of Multiple Card Operation (83)Annex H (informative): Multiple Card proactive command examples (84)Annex I (informative): Bearer independent protocol proactive command examples (85)Annex J (informative): WAP References (86)Annex K (informative): Use of USAT Bearer independent protocol for local links Bluetooth case (87)Annex L (informative): Bluetooth Service Discovery protocol (88)Annex M (informative): Use of USAT Bearer independent protocol for local links, server case (89)Annex N (informative): USSD information flow between the Network, the ME and the UICC (90)N.1MMI Mode (90)N.2Application Mode (92)N.3USSD Data Download (94)Annex O (informative): Geographical location information discovery information flow betweenthe ME and the UICC (94)Annex P (informative): Change History (96)ForewordThis Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:Version x.y.zwhere:x the first digit:1 presented to TSG for information;2 presented to TSG for approval;3 or greater indicates TSG approved document under change control.y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.z the third digit is incremented when editorial only changes have been incorporated in the document.1 ScopeThe present document defines the interface between the UICC and the Mobile Equipment (ME), and mandatory ME procedures, specifically for "USIM Application Toolkit".The present document refers in its majority to the ETSI TS 102 223 [32], which describes the generic aspects of application toolkits within the UICC.USAT is a set of commands and procedures for use during the network operation phase of 3G, in addition to those defined in TS 31.101 [13].Specifying the interface is to ensure interoperability between a UICC and an ME independently of the respective manufacturers and operators.The present document defines for 3G technology:- the commands;- the application protocol;- the mandatory requirements on the UICC and ME for each procedure.The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the UICC or the ME are only specified where these reflect over the interface. The present document does not specify any of the security algorithms which may be used.Within the context of the present document, the term "terminal" used in ETSI TS 102 223 [32] refers to the Mobile Equipment (ME).Within the context of the present document, the term "NAA" used in ETSI TS 102 223 [32] refers to the USIM.2 ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document.•References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.•For a specific reference, subsequent revisions do not apply.•For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (includinga GSM document), a non-specific reference implicitly refers to the latest version of that document in the sameRelease as the present document.[1] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network(PLMN)".[2] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the User Equipment (UE)".[3] 3GPP TS 22.042: "Network Identity and Time Zone (NITZ); Service description; Stage 1".[4] 3GPP TS 23.038: "Alphabets and language-specific information".[5] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".[6] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".[7] 3GPP TS 23.122: "Non-Access Stratum functions related to Mobile Station (MS) in idle mode".[8] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".[9] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3".[10] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radiointerface".[11] 3GPP TS 24.080: "Mobile radio layer 3 supplementary services specification; Formats andcoding".[12] 3GPP TS 27.007: "AT command set for 3G User Equipment (UE)".[13] 3GPP TS 31.101: "UICC-terminal interface; Physical and logical characteristics".[14] 3GPP TS 31.102: "Characteristics of the USIM application".[15] Void.[16] Void.[17] Void.[18] Void.[19] Void.[20] Void.[21] Void.[22] 3GPP TS 22.001: "Principles of circuit telecommunication services supported by a Public LandMobile Network (PLMN)".[23] 3GPP TS 23.048: "Security Mechanisms for the (U)SIM application toolkit; Stage 2".[24] Void.[25] Void.[26] Void.[27] 3GPP TS 44.018: "Mobile radio interface Layer 3 specification; Radio Resource ControlProtocol".[28] Void.[29] Void.[30] 3GPP TS 23.003: "Numbering, addressing and identification".[31] Void.[32] ETSI TS 102 223 Release 7: "Smart Cards; Card Application Toolkit".[33] 3GPP TR 21.905: "Vocabulary for 3GPP specifications".[34] 3GPP TS 22.101: "Service aspects; Service principles".[35] 3GPP TS 25.401: "UTRAN overall description".[36] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling".[37] 3GPP TS 24.090: "Unstructured Supplementary Service Data (USSD) - Stage 3".[38] 3GPP TS 25.331: "Radio Resource Control (RRC) Protocol Specification".[39] 3GPP TS 25.133: "Requirements for support of radio resource management".[40] Void.[41] 3GPP TS 31.115: "Secured packet structure for the (U)SIM Toolkit applications".[42] 3GPP TS 24.234: "3GPP System to WLAN Interworking; UE to Network protocols; Stage 3".[43] ETSI TS 101 220 Release 7: "Smart Cards; ETSI numbering system for telecommunicationapplication providers ".[44] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".[45] IEC 61162-1: "Maritime navigation and radio communication equipment and systems – Digitalinterfaces".3 Definitions, abbreviations and symbols3.1 DefinitionsFor the purposes of the present document, the terms and definitions given in ETSI TS 102 223 [32] and TR 21.905 [33] apply.3.2 AbbreviationsFor the purpose of the present document, the abbreviations given in ETSI TS 102 223 [32] and TR 21.905 [33] and the following apply:ADN Abbreviated Dialling NumberBroadcastCB CellCBMID Cell Broadcast Message IDentifierEGPRS EDGE General Packet Radio ServiceNumberFDN FixedDiallingGGSN Gateway GPRS Support NodeGPRS General Packet Radio ServiceGSM Global System for Mobile communicationsHSDPA High Speed Downlink Packet AccessMM MultimediaMessageServiceMMS MultimediaMessagingInterfaceMachineMMI ManPDP Packet Data Protocol, e.g., Ip or X25 or PPPRFU Reserved for Future UseServiceSS SupplementarySSC Supplementary Service Control stringUSAT USIM Application ToolkitUSIM Universal Subscriber Identity ModuleSupplementary Service DataUSSD UnstructuredWSID WLAN Specific IDentifier3.3 SymbolsFor the purposes of the present document, the following symbols apply:'0' to '9' and 'A' to 'F' The sixteen hexadecimal digits.4 Overview of USATThe USAT provides mechanisms which allow applications, existing in the UICC, to interact and operate with any ME which supports the specific mechanism(s) required by the application.The following mechanisms have been defined. These mechanisms are dependent upon the commands and protocols relevant to USAT in TS 31.101 [13].4.1 ProfileDownloadProfile downloading provides a mechanism for the ME to tell the UICC what it is capable of.4.2 ProactiveUICCProactive UICC gives a mechanism whereby the UICC can initiate actions to be taken by the ME. In addition to the actions listed in ETSI TS 102 223 [32], the USAT is extended with the following actions:- sending a SS control or USSD string.- requesting the ME to report current geographical location information.4.3 Data download to UICCData downloading to the UICC uses either dedicated commands (the transport mechanisms of SMS point-to-point and Cell Broadcast) or the Bearer independent protocol. Transferral of information over the UICC-ME interface uses the ENVELOPE command.4.4 MenuselectionSee ETSI TS 102 223 [32].4.5 Call control by USIMWhen this service is activated by the USIM, all dialled digit strings, supplementary service control strings and USSD strings or PDP context parameters are first passed to a USIM application before the ME sets up the call, the supplementary service operation or the USSD operation or establishes the PDP context. The ME shall also pass to the USIM application at the same time its current serving cell. The USIM application has the ability to allow, bar or modify the call, the supplementary service operation or, the USSD operation or PDP context activation by another context activation. The USIM application also has the ability to replace a call request, a supplementary service operation or a USSD operation by another call request or supplementary service operation or USSD operation.EXAMPLE: A call request can be replaced by a supplementary service operation or a USSD operation, and vice-versa.4.6 MO Short Message control by USIMWhen this service is activated by the USIM, all MO short messages are first passed to the USIM application before the ME sends the short message. The ME shall also pass to the USIM application at the same time its current serving cell. The USIM application shall have the ability to allow the sending, bar the sending or modify the destination address of the short message before sending it.download4.7 EventIn addition to the set of events defined in ETSI TS 102 223 [32], the following event may also be reported to the UICC: - Network Rejection4.8 SecuritySee ETSI TS 102 223 [32].card4.9 MultipleSee ETSI TS 102 223 [32].Expiration4.10 TimerSee ETSI TS 102 223 [32].4.11 Bearer Independent ProtocolSee ETSI TS 102 223 [32].4.12 Description of the access technology indicator mechanismSee ETSI TS 102 223 [32].4.13 Description of the network search mode mechanismSee ETSI TS 102 223 [32].4.14 Geographical location discoveryThe proactive command Geographical Location Request and the envelope command Geographical Location Reportingallows the UICC to request and receive the current geographical location information from the ME when the ME isequipped with a positioning feature and it is enabled (e.g. autonomous GPS, Assisted GPS or Assisted GNSS).download5 Profile5.1 ProcedureThe profile download instruction is sent by the ME to the UICC as part of the UICC initialization procedure. The UICCinitialization procedure is specified in TS 31.101 [13].If the UICC indicates the support of "Additional TERMINAL PROFILE after UICC activation" in its USIM ServiceTable, the ME shall handle the profile download procedure as specified in ETSI TS 102 223 [32].If the UICC does not indicate the support of "Additional TERMINAL PROFILE after UICC activation" in its USIMService Table, the profile download instruction shall only be sent by the ME to the UICC as part of the UICCinitialization procedure. However, if a USIM initialisation procedure is performed due to a refresh proactive command,the USIM initialisation procedure may also include a profile download.The profile(s) sent by the ME shall state the facilities relevant to USAT that are supported by the ME.5.2 Structure and coding of TERMINAL PROFILEDirection: ME to UICC.The command header is specified in TS 31.101 [13].Command parameters/data:LengthM/O/CDescription ClauseMlgth Profile -- Profile:Contents:- The list of USAT facilities that are supported by the ME.Coding:- 1 bit is used to code each facility:- bit = 1: facility supported by ME.- bit = 0: facility not supported by ME.NOTE: several bits may need to be set to 1 for the support of the same facility. This is because of backwardcompatibility with SAT: several options existed in SAT for a given facility, and they are mandatory inUSAT when this facility is supported.First byte (Download):b8 b7 b6 b5 b4 b3 b2b1[32]223TS102SeedownloadSMS-PPdatadownloaddataBroadcastCell[32]102223TSSeeBit = 1 if SMS-PP data download is supported223[32]TS102SeeBit = 1 if Call Control by USIM is supportedBit = 1 if Call Control by USIM is supportedSecond byte (Other):b8 b7 b6 b5 b4 b3 b2b1223[32]102TSSeeUSIMbyControlCallBit = 1 if Call Control by USIM is supportedbycontrolUSIMmessageMOshortBit = 1 if Call Control by USIM is supported223[32]TS102See[32]102223SeeTS223[32]TS102SeeThird byte (Proactive UICC):- See ETSI TS 102 223 [32].Fourth byte (Proactive UICC):b8 b7 b6 b5 b4 b3 b2b1223[32]102TSSeeSHORTSENDMESSAGEUICC:ProactiveSSSENDUICC:ProactiveUSSDSENDProactiveUICC:[32]223102SeeTS102[32]223TSSee[32]223102SeeTS(NMR)-inINFORMATIONPROVIDEProactiveUICC:LOCAL3GPP terms, this indicates support for GERANFifth byte (Event driven information):- See ETSI TS 102 223 [32].Sixth byte (Event driven information extensions):- See ETSI TS 102 223 [32].Seventh byte (Multiple card proactive commands) for class "a":- See ETSI TS 102 223 [32].Eighth byte (Proactive UICC):b8 b7 b6 b5 b4 b3 b2b1[32]223102SeeTS[32]223102SeeTS[32]223102SeeTS223[32]TS102See[32]223102SeeTS223[32]TS102See223[32]TS102SeeBit = 1 if Call Control by USIM is supportedNinth byte:b8 b7 b6 b5 b4 b3 b2b1223102[32]TSSee223[32]102TSSee[32]223See102TS223[32]102TSSeeINFORMATIONLOCAL(Timing ProactiveUICC:PROVIDEAdvance)[32]223TS102See223[32]TS102See223[32]TS102SeeTenth byte (Soft keys support) for class "d":- See ETSI TS 102 223 [32].Eleventh byte: (Soft keys information):- See ETSI TS 102 223 [32].Twelfth byte:- See ETSI TS 102 223 [32].Thirteenth byte:- See ETSI TS 102 223 [32].Fourteenth byte: (Screen height):- See ETSI TS 102 223 [32].Fifteenth byte: (Screen width):- See ETSI TS 102 223 [32].Sixteenth byte: (Screen effects):- See ETSI TS 102 223 [32].Seventeenth byte:b8 b7 b6 b5 b4 b3 b2b1223[32]TS102Seeissupported)"e"HSDPA(ifclassEighteenth byte:b8 b7 b6 b5 b4 b3 b2b1[32]223See102TSonGPRSCONTROLCALL[32]102223SeeTSNineteenth byte: (reserved for TIA/EIA-136 facilities):- See ETSI TS 102 223 [32].Twentieth byte: (reserved for TIA/EIA/IS-820 facilities):- See ETSI TS 102 223 [32].。

Studio 5000 Logix Designer 功能块图概念与操作说明书

Studio 5000 Logix Designer 功能块图概念与操作说明书

Course NumberCCP152Course PurposeThis course is a skill-building programming course that provides you with an understanding of Studio 5000 Logix Designer® function block diagrams and terminology. This COURSE AGENDADAY 1• Creating a Function Block Diagram• Programming Logical Function Block Instructions • Programming Timer and Counter FunctionBlock Instructions• Programming Analog Function Block InstructionsControlLogix/Studio 5000 Studio 5000 Logix Designer Level 4:Function Block ProgrammingWHO SHOULD ATTENDIndividuals who are responsible for developing,debugging, and programming Logix5000 controllers using the Logix Designer application with function block diagrams should attend this course.Also, individuals who use ActiveX controls in an operator interface, such as FactoryTalk® View ME software, should attend this course.PREREQUISITESTo successfully complete this course, the following prerequisites are required:• Ability to perform basic Microsoft Windows tasks • Understanding of basic measurement and control theory, including basic loop control• Completion of the Studio 5000 Logix Designer Level 3: Project Development course (Course No. CCP143)or equivalent experience STUDENT MATERIALSTo enhance and facilitate the students’ learningexperiences, the following materials are provided as part of the course package:• Student Manual– Contains the topical outlines and exercises–Used to follow presentations, take notes, and work through exercises • Studio 5000 Logix Designer and Logix5000 Procedures Guide–Provides the steps required to complete basicsoftware tasks common to all Logix5000 controllersHANDS-ON PRACTICETo gain real-world programming experience, you will be given a functional specification for a fictitious batch process mixer, where bulk ingredients are mixed to produce a product. You will be the programmer for this batch mixer and must follow the functional specification, which will be the basis for all hands-on exercises in this course.After completing all exercises, you will have developed a Logix5000 project for the fictitious batch process mixer. As you develop your project, you will be given opportunities to run it using an ABT-TDCLX3-B workstation. This programming and process-based application experience can then be transferred to your own job responsibilities.NEXT LEARNING LEVELOnce you have mastered the function block diagram skills covered in this course, you will be able to expand your Logix5000 programming knowledge by attending other Logix5000 programming courses, such as the Studio 5000 Logix Designer Level 4: Kinetix 6000 (SERCOS) Programming course (Course No. CCN145).COURSE LENGTH This is a two-day course.Allen-Bradley, FactoryTalk, Logix5000 and Studio 5000 Logix Designer are trademarks of Rockwell Automation, Inc.Trademarks not belonging to Rockwell Automation are property of their respective companies. Publication GMST10-PP190I-EN-E – January 2020 | Supersedes Publication GMST10-PP190H-EN-E – April 2018Copyright © 2020 Rockwell Automation, Inc. All Rights Reserved. Printed in USA.To be respectful of the environment, Rockwell Automation is transitioning some of its training courses to a paperless format. Students are asked tocomplete downloads and bring personal devices to these classes. A full list of digital/paperless courses is currently available through your local distributor.。

javawasstartedbutreturnedexitcode=13简便解决办法

javawasstartedbutreturnedexitcode=13简便解决办法

javawasstartedbutreturnedexitcode=13简便解决办法

当我通过电脑通知进⾏更新了Java后再打开我的Eclipse时就会报这个错误,原因在⽹上查了⼀下,说是第三⽅更新JRE时安装的是32位的JRE,与64位的Eclipse不匹配(报错信息的– launcher.library 中有x86_64说明这个Eclipse是64位的);

JDK8/JRE8 在安装完成之后,会添加⼀个环境变量C:\ProgramData\Oracle\Java\javapath,⾥⾯存在三个快捷键⼀样的⽂件,直接删掉,甚⾄把javapath ⽂件夹删掉都可以,然后再重启Eclipse就可以了,不⽤像其他⼈说的什么修改eclipse.ini ⽂件、重新安装什么的这么⿇烦,我是直接删掉后就能启动eclipse,甚⾄不⽤重启电脑(删除完后还是不能启动eclipse的查看⼀下⾃⼰配置的jdk和jre的环境变量有没有变动什么的)。

AJA FS2 Installation and Operation Guide

AJA FS2 Installation and Operation Guide

AJA FS2 Installation and Operation Installation and Operation GuideB e c a u s e i t m a t t e r s .7/31/2012 Version: 1.1.0.0TrademarksAJA®, KONA®, Ki Pro®, KUMO®, and XENA® are registered trademarks of AJA Video, Inc. Io Express™,Io HD™ and Io™ are trademarks of AJA Video, Inc. Apple, the Apple logo, AppleShare, AppleTalk,FireWire, iPod, iPod Touch, Mac, and Macintosh are registered trademarks of Apple Computer, Inc.Final Cut Pro, QuickTime and the QuickTime Logo are trademarks of Apple Computer, Inc. All othertrademarks are the property of their respective holders.NoticeCopyright © 2012 AJA Video, Inc. All rights reserved. All information in this manual is subject tochange without notice. No part of the document may be reproduced or transmitted in any form,or by any means, electronic or mechanical, including photocopying or recording, without theexpress written permission of AJA Inc.FCC Emission InformationThis equipment has been tested and found to comply with the limits for a Class A digital device,pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protectionagainst harmful interference when the equipment is operated in a commercial environment. Thisequipment generates, uses and can radiate radio frequency energy and, if not installed and usedin accordance with the instruction manual, may cause harmful interference to radiocommunications. Operation of this equipment in a residential area is likely to cause harmfulinterference in which case the user will be required to correct the interference at his own expense.Changes or modifications not expressly approved by AJA Video can effect emission complianceand could void the user’s authority to operate this equipment.Contacting SupportTo contact AJA Video for sales or support, use any of the following methods:180 Litton Drive, Grass Valley, CA. 95945 USATelephone: +1.800.251.4224 or +1.530.274.2048Fax: +1.530.274.9442Web: SupportEmail:***************SalesEmail:*************1FS2 Installation and Operation Manual — Limited Warranty Limited WarrantyAJA Video warrants that this product will be free from defects in materials and workmanship for aperiod of five years from the date of purchase. If a product proves to be defective during thiswarranty period, AJA Video, at its option, will either repair the defective product without charge forparts and labor, or will provide a replacement in exchange for the defective product.In order to obtain service under this warranty, you the Customer, must notify AJA Video of the defectbefore the expiration of the warranty period and make suitable arrangements for the performanceof service. The Customer shall be responsible for packaging and shipping the defective product to adesignated service center nominated by AJA Video, with shipping charges prepaid. AJA Video shallpay for the return of the product to the Customer if the shipment is to a location within the countryin which the AJA Video service center is located. Customer shall be responsible for paying allshipping charges, insurance, duties, taxes, and any other charges for products returned to any otherlocations.This warranty shall not apply to any defect, failure or damage caused by improper use or improper orinadequate maintenance and care. AJA Video shall not be obligated to furnish service under thiswarranty a) to repair damage resulting from attempts by personnel other than AJA Videorepresentatives to install, repair or service the product, b) to repair damage resulting from improperuse or connection to incompatible equipment, c) to repair any damage or malfunction caused bythe use of non-AJA Video parts or supplies, or d) to service a product that has been modified orintegrated with other products when the effect of such a modification or integration increases thetime or difficulty of servicing the product.THIS WARRANTY IS GIVEN BY AJA VIDEO IN LIEU OF ANY OTHER WARRANTIES, EXPRESS OR IMPLIED.AJA VIDEO AND ITS VENDORS DISCLAIM ANY IMPLIED WARRANTIES OF MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE. AJA VIDEO’S RESPONSIBILITY TO REPAIR OR REPLACEDEFECTIVE PRODUCTS IS THE WHOLE AND EXCLUSIVE REMEDY PROVIDED TO THE CUSTOMER FORANY INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES IRRESPECTIVE OF WHETHERAJA VIDEO OR THE VENDOR HAS ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES. Important Safety InformationHazard!This symbol, when used in the manual, indicates a serious health hazard with risk of injury ordeath.Warning!This symbol, when used in the manual, indicates a serious risk or threat to personal safety.Caution!This symbol, when used in the manual, indicates important safety and complianceinformation.Table of Contents ContentsAJA FS2 Installation and Operation Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiFCC Emission Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii Contacting Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii Limited Warranty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Important Safety Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vChapter 1:Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Video Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Available Video Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Audio Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Control and Other Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Typical Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3FS2 Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Front Panel Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Remote Web Browser Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 SNMP Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4GPI Inputs and Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Optional Remote Control Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Optional Fiber I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Optional Dolby E Decoder and Encoder Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Video Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73G Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Audio Processors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 What’s In The Box? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9In This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Chapter 2:Controls, Indicators, and Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Control and Indicator Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Front Panel Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Alphanumeric Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Operational Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Pushbuttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Control Knobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Incompatibility Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Incompatible Video Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Example Reference and Video Incompatibility Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Rear Panel Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Connector Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 AC Power Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 AES/EBU Digital Audio In and Out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Balanced Analog Audio In and Out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 RS-422 Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 GPI Inputs and Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 SDI In and Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Optical Fiber In and Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Component/Composite Analog Video In and Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 HDMI In and Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Composite NTSC/PAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Reference Video (looping) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 About Inputs and Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Chapter 3:Installation & Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Installation Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Unpacking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Shipping Box Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Installing Optional Fiber Optic I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Installing Optional Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Dolby Decoder Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 FS2 Chassis Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Physical Requirements for Mounting the Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Chassis Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Cabling and Cooling Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Power Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Network Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291FS2 Installation and Operation Manual — ContentsNetwork Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Networking Using DHCP or Default Static IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Networking the FS2 Using Your Own Static IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Using Ping to Test the Network Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Mac Ping Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Windows PC Ping Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Web Browser Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Software Update Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Download the Latest FS2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Unpack the Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Uploading and Installing the Software to the FS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33System Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34System Video/Audio Cable Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34GPI Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34FS2 Audio Level Choices—Pro or Consumer, US or EBU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Chapter 4:Display Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Controlling the FS2 via Front Panel Display Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Parameter Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Menu Group Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39SELECT and ADJUST Knobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Menu Operation Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Status Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Simple Menus: Config Format Alarm Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Multiple Parameter Menus: Video 1 ProcAmp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Multiple Field Parameters: IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43STATUS Menu Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44S.1 I/O Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44S.2 Vid1 Format Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44S.3 Vid1 Format Alarm Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44S.4 Vid2 Format Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45S.5 Vid 2 Format Alarm Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45S.6 Output Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45S.7 Power/Temp Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45S.8 Caption Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46S.9 Dolby Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46S.10 System Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46REMOTE Menu Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 Remote Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471.1 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472.1–4 GPI IN 1–4 Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.1–4 GPI 1–4 OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Interaction of Presets and GPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Example of a Serial Recall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Example of an Unintended Recall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49CONFIG Menu Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 System Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.1 IP Config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.2 IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512.3 Subnet Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512.4 Default Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 MAC Address (view only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.0 SNMP Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.1 SNMP Trap Destination 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.2 SNMP Trap Port 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.3 SNMP Trap Destination 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.4 SNMP Trap Port 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545 Power Supply Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546.1 Vid1 Format Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546.2 Vid2 Format Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557 Reference Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558 Hidden Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 Display Intensity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5510 Serial Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5611 Software Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5612 Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 PRESET Menu Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 Recall Preset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 Store Preset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Interaction of Presets and GPIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 SYSTEM Menu Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581 Component In Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582 Component Out Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583 Analog Audio Std . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 SDI1 3G Detect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595 SDI2 Input Protect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596 Fiber1 3G Detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607 Fiber2 Input Protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618 Genlock Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619 Frame Rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6110 NTSC Standard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6211 Composite Downconv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6212 HDMI RGB Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6214.0 AES/EBU SRC Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6314.1–14.8 AES/EBU SRC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6315 Dolby Decoder Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6416 Dolby Decoder Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6417 Dolby Decoder Aux Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6518 Dolby Decoder Aux Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65。

Flex System Fabric SI4093系统互连模块产品指南(撤回产品)说明书

Flex System Fabric SI4093系统互连模块产品指南(撤回产品)说明书

Flex System Fabric SI4093 System Interconnect ModuleProduct Guide (withdrawn product)The Flex System™ Fabric SI4093 System Interconnect Module enables simplified integration of Flex System into your existing networking infrastructure and provides the capability of building simple connectivity for points of delivery (PODs) or clusters up to 252 nodes. The SI4093 requires no management for most data center environments, eliminating the need to configure each networking device or individual ports, thus reducing the number of management points. It provides a low latency, loop-free interface that does not rely upon spanning tree protocols, thus removing one of the greatest deployment and management complexities of a traditional switch. The SI4093 offers administrators a simplified deployment experience while maintaining the performance of intra-chassis connectivity. The SI4093 System Interconnect Module is shown in Figure 1.Figure 1. Flex System Fabric SI4093 System Interconnect ModuleDid you know?The base switch configuration comes standard with 24x 10 GbE port licenses that can be assigned to internal connections or external SFP+ or QSFP+ ports with flexible port mapping. For example, this feature allows you to trade off four 10 GbE ports for one 40 GbE port (or vice versa) or trade off one external 10 GbE SFP+ port for one internal 10 GbE port (or vice versa). You then have the flexibility of turning on more ports when you need them using Features on Demand upgrade licensing capabilities that provide “pay as you grow”scalability without the need to buy additional hardware.The SI4093 can be used in the Flex System Interconnect Fabric solution that reduces networking management complexity without compromising performance by lowering the number of devices that need to be managed by 95% (managing one device instead of 20). Interconnect Fabric simplifies POD integration into an upstream network by transparently interconnecting hosts to a data center network and representing the POD as a large compute element isolating the POD's internal connectivity topology and protocols from the rest of the network.Click here to check for updatesTable 3. Supported transceivers and direct-attach cablesDescription Partnumber FeaturecodeMaximumquantitysupportedSerial console cablesFlex System Management Serial Access Cable Kit90Y9338A2RR1 SFP transceivers - 1 GbELenovo 1000BASE-T SFP Transceiver (does not support 10/100 Mbps)00FE333A5DL14 Lenovo 1000BASE-SX SFP Transceiver81Y1622326914 Lenovo 1000BASE-LX SFP Transceiver90Y9424A1PN14 SFP+ transceivers - 10 GbELenovo 10GBASE-SR SFP+ Transceiver46C3447505314 Lenovo 10GBASE-LR SFP+ Transceiver90Y9412A1PM14 Optical cables for 1 GbE SX SFP and 10 GbE SR SFP+ transceiversLenovo 1m LC-LC OM3 MMF Cable00MN502ASR614 Lenovo 3m LC-LC OM3 MMF Cable00MN505ASR714 Lenovo 5m LC-LC OM3 MMF Cable00MN508ASR814 Lenovo 10m LC-LC OM3 MMF Cable00MN511ASR914 Lenovo 15m LC-LC OM3 MMF Cable00MN514ASRA14 Lenovo 25m LC-LC OM3 MMF Cable00MN517ASRB14 Lenovo 30m LC-LC OM3 MMF Cable00MN520ASRC14 SFP+ direct-attach cables - 10 GbELenovo 1m Passive SFP+ DAC Cable90Y9427A1PH14 Lenovo 1.5m Passive SFP+ DAC Cable00AY764A51N14 Lenovo 2m Passive SFP+ DAC Cable00AY765A51P14 Lenovo 3m Passive SFP+ DAC Cable90Y9430A1PJ14 Lenovo 5m Passive SFP+ DAC Cable90Y9433A1PK14 Lenovo 7m Passive SFP+ DAC Cable00D6151A3RH14 QSFP+ transceiver and cables - 40 GbELenovo 40GBASE-SR4 QSFP+ Transceiver49Y7884A1DR2 Lenovo 40GBASE-iSR4 QSFP+ Transceiver00D9865ASTM2 Lenovo 40GBASE–eSR4 QSFP+ Transceiver00FE325A5U92 Lenovo 40GBASE-LR4 QSFP+ Transceiver00D6222A3NY2 Optical cables for 40 GbE QSFP+ SR4/iSR4/eSR4 transceiversLenovo 10m QSFP+ MTP-MTP OM3 MMF Cable90Y3519A1MM2 Lenovo 30m QSFP+ MTP-MTP OM3 MMF Cable90Y3521A1MN2 Lenovo 10m QSFP+ MTP-MTP OM3 MMF Cable (replaces 90Y3519)00VX003AT2U2 Lenovo 30m QSFP+ MTP-MTP OM3 MMF Cable (replaces 90Y3521)00VX005AT2V2 Optical breakout cables for 40 GbE QSFP+ iSR4/eSR4 transceiversLenovo 1m MTP-4xLC OM3 MMF Breakout Cable00FM412A5UA2 Lenovo 3m MTP-4xLC OM3 MMF Breakout Cable00FM413A5UB2 Lenovo 5m MTP-4xLC OM3 MMF Breakout Cable00FM414A5UC2 QSFP+ breakout cables - 40 GbE to 4x10 GbEFigure 2. Location of the I/O bays in the Flex System chassisThe SI4093 module can be installed in bays 1, 2, 3, and 4 of the Flex System chassis. A supported adapter card must be installed in the corresponding slot of the compute node. Each adapter can use up to four lanes to connect to the respective I/O module bay. The SI4093 is able to use up to three of the four lanes.Prior to Networking OS 7.8, with four-port adapters, an optional Upgrade 1 (95Y3318) was required for the SI4093s to allow communications on all four ports. With eight-port adapters, both optional Upgrade 1(95Y3318) and Upgrade 2 (95Y3320) were required for the module to allow communications on six adapter ports, and two remaining ports are not used. With Networking OS 7.8 or later, there is no need to buy additional module upgrades for 4-port and 8-port adapters if the total number of port licenses on the SI4093 does not exceed the number of external (upstream network ports) and internal (compute node network ports) connections used.In compute nodes that have an integrated dual-port 10 GbE network interface controller (NIC), NIC ports are routed to bays 1 and 2 with a specialized periscope connector, and the adapter card is not required. However, when needed, the periscope connector can be replaced with the adapter card. In this case, integrated NIC will be disabled.Table 4 shows compatibility information for the SI4093 and Flex System chassis.Table 4. Flex System chassis compatibilityDescription Partnumber EnterpriseChassis withCMMEnterpriseChassis withCMM2Carrier-gradeChassis withCMM2Flex System Fabric SI4093 System InterconnectModule95Y3313Yes Yes NoThe midplane connections between the adapters installed in the compute nodes to the switch bays in the chassis are shown diagrammatically in the following figure. The figure shows both half-wide compute nodes, such as the x240 with two adapters, and full-wide compute nodes, such as the x440 with four adapters.Figure 3. Logical layout of the interconnects between I/O adapters and I/O modulesTable 5 shows the connections between adapters installed in the compute nodes to the I/O bays in the chassis.Table 5. Adapter to I/O bay correspondenceI/O adapter slotin the compute node Port on the adapter Corresponding I/O module bay in the chassisBay 1Bay 2Bay 3Bay 4Slot 1Port 1YesPort 2YesPort 3YesPort 4YesPort 5YesPort 6YesPort 7*Port 8*Slot 2Port 1YesPort 2YesPort 3YesPort 4YesPort 5YesPort 6YesPort 7*Port 8*Slot 3(full-wide compute nodes only)Port 1YesPort 2Yes Port 3YesPort 4Yes Port 5YesPort 6Yes Port 7*Port 8*Slot 4(full-wide compute nodes only)Port 1YesPort 2Yes Port 3YesPort 4Yes Port 5YesPort 6Yes Port 7*Port 8** Ports 7 and 8 are routed to I/O bays 1 and 2 (Slot 1 and Slot 3) or 3 and 4 (Slot 2 and Slot 4), but these ports cannot be used with the SI4093.The following table lists the adapters that are supported by the I/O module.Table 6. Network adaptersDescription Part number Feature code50 Gb EthernetThinkSystem QLogic QL45212 Flex 50Gb 2-Port Ethernet Adapter7XC7A05843B2VT7XC7A05845B2VVThinkSystem QLogic QL45262 Flex 50Gb 2-Port Ethernet Adapter withiSCSI/FCoE25 Gb EthernetThinkSystem QLogic QL45214 Flex 25Gb 4-Port Ethernet Adapter7XC7A05844B2VU10 Gb EthernetEmbedded 10Gb Virtual Fabric Adapter (2-port)†None NoneFlex System CN4022 2-port 10Gb Converged Adapter88Y5920A4K3Flex System CN4052 2-port 10Gb Virtual Fabric Adapter00JY800*A5RPFlex System CN4052S 2-port 10Gb Virtual Fabric Adapter00AG540ATBTFlex System CN4052S 2-port 10Gb Virtual Fabric Adapter Advanced01CV780AU7XFlex System CN4054 10Gb Virtual Fabric Adapter (4-port)90Y3554*A1R1Flex System CN4054R 10Gb Virtual Fabric Adapter (4-port)00Y3306*A4K2Flex System CN4054S 4-port 10Gb Virtual Fabric Adapter00AG590ATBSFlex System CN4054S 4-port 10Gb Virtual Fabric Adapter Advanced01CV790AU7YFlex System CN4058S 8-port 10Gb Virtual Fabric Adapter94Y5160A4R6Flex System EN4172 2-port 10Gb Ethernet Adapter00AG530A5RN1 Gb EthernetEmbedded 1 Gb Ethernet controller (2-port)**None NoneFlex System EN2024 4-port 1Gb Ethernet Adapter49Y7900A10Y* Withdrawn from marketing† The Embedded 10Gb Virtual Fabric Adapter is built into selected compute nodes.** The Embedded 1 Gb Ethernet controller is built into selected compute nodes.The adapters are installed in slots in each compute node. Figure 4 shows the locations of the slots in the x240 Compute Node. The positions of the adapters in the other supported compute nodes are similar.Figure 4. Location of the I/O adapter slots in the Flex System x240 Compute NodeConnectors and LEDsFigure 5. Front panel of the Flex System Fabric SI4093 System Interconnect ModuleNetwork cabling requirementsThe network cables that can be used with the SI4093 module are shown in Table 7.Table 7. SI4093 network cabling requirementsTransceiver Standard Cable Connector 40 Gb Ethernet40GBASE-SR4 QSFP+ Transceiver (49Y7884)40GBASE-SR410 m or 30 m MTP fiber optics cables supplied by Lenovo(see Table 3); support for up to 100 m with OM3 multimodefiber or up to 150 m with OM4 multimode fiberMTP40GBASE-iSR4 QSFP+ Transceiver (00D9865)40GBASE-SR410 m or 30 m MTP fiber optics cables or MTP-4xLCbreakout cables up to 5 m supplied by Lenovo (see Table3); support for up to 100 m with OM3 multimode fiber or upto 150 m with OM4 multimode fiberMTP40GBASE-eSR4 QSFP+ Transceiver (00FE325)40GBASE-SR410 m or 30 m MTP fiber optics cables or MTP-4xLCbreakout cables up to 5 m supplied by Lenovo (see Table3); support for up to 300 m with OM3 multimode fiber or upto 400 m with OM4 multimode fiberMTP40GBASE-LR4 QSFP+Transceiver (00D6222)40GBASE-LR41310 nm single-mode fiber cable up to 10 km LCDirect attach cable40GBASE-CR4QSFP+ to QSFP+ DAC cables up to 7 m; QSFP+ to 4xSFP+ DAC break-out cables up to 5 m for 4x 10 GbESFP+ connections out of a 40 GbE port (see Table 3)QSFP+ 10 Gb Ethernet10GBASE-SR SFP+ Transceiver (46C3447)10GBASE-SR Up to 30 m with fiber optic cables supplied by Lenovo (seeTable 3); 850 nm OM3 multimode fiber cable up to 300 mor up to 400 m with OM4 multimode fiberLC10GBASE-LR SFP+Transceiver (90Y9412)10GBASE-LR1310 nm single-mode fiber cable up to 10 km LC Direct attach cable10GSFP+Cu SFP+ DAC cables up to 7 m (see Table 3)SFP+ 1 Gb Ethernet1000BASE-T SFPTransceiver (00FE333)1000BASE-T UTP Category 5, 5E, and 6 up to 100 meters RJ-451000BASE-SX SFP Transceiver (81Y1622)1000BASE-SX Up to 30 m with fiber optic cables supplied by Lenovo (seeTable 3); 850 nm multimode fiber cable up to 550 m (50 µ)or up to 220 m (62.5 µ)LC1000BASE-LX SFPTransceiver (90Y9424)1000BASE-LX1310 nm single-mode fiber cable up to 10 km LC Management ports1 GbE management port1000BASE-T UTP Category 5, 5E, and 6 up to 100 meters RJ-45External RS-232 management port RS-232DB-9-to-mini-USB or RJ-45-to-mini-USB console cable(comes with optional Management Serial Access Cable,90Y9338)Mini-USBWarrantyThe SI4093 carries a 1-year, customer-replaceable unit (CRU) limited warranty. When installed in a chassis, these I/O modules assume your system’s base warranty and any warranty service upgrade.Physical specificationsFigure 6. SI4093 connectivity topology - Link Aggregation Figure 7. SI4093 connectivity topology - Virtual Link AggregationFigure 8. SI4093 in the 10 GbE networkTable 8. Components that are used in 10 GbE solution with the SI4093 (Figure 8)Diagram reference Description PartnumberQuantityFlex System Virtual Fabric solutionFlex System CN4054 10Gb Virtual Fabric Adapter90Y3554 1 per compute nodeFlex System Fabric SI4093 System Interconnect Module95Y3313 2 per chassisFlex System Fabric SI4093 System Interconnect Module (Upgrade 1)*95Y3318 1 per SI4093RackSwitch G8264, G8316, or G8332* The Upgrade 1 might not be needed with flexible port mapping if the total number of the internal and external ports used on the SI4093 is less or equal to 24.Note: You also need SFP+/QSFP+ modules and optical cables or SFP+/QSFP+ DAC cables (not shown in Table 8; see Table 3 for details) for the external 10 Gb Ethernet connectivity.SI4093 in the converged FCoE networkSI4093 supports Data Center Bridging (DCB), and it can transport FCoE frames. These interconnect modules provide an inexpensive solution for transporting encapsulated FCoE packets to the Fibre Channel Forwarder (FCF), which is functioning as both an aggregation switch and an FCoE gateway. Vendor-specific examples of this scenario are shown in Figure 9, Figure 10, and Figure 11. The solution components that are used in the scenarios that are shown in Figure 9, Figure 10, and Figure 11 are listed in Table 9, Table 10, and Table 11, respectively.Figure 9. SI4093 in the FCoE network with the RackSwitch G8264CS as an FCFFigure 10. SI4093 in the FCoE network with the Brocade VDX 6730 as an FCFFigure 11. SI4093 in the FCoE network with the Cisco Nexus 5548/5596 as an FCF Table 9. SI4093 with the G8264CS as an FCF (Figure 9)Diagram reference Description PartnumberQuantityFlex System FCoE solutionFlex System CN4054 10Gb Virtual Fabric Adapter90Y3554 1 per compute node Flex System CN4054 Virtual Fabric Adapter Upgrade90Y3558 1 per VFAFlex System Fabric SI4093 System Interconnect Module95Y3313 2 per chassisFlex System Fabric SI4093 System Interconnect Module (Upgrade 1)*95Y3318 1 per SI4093RackSwitch G8264CSBrocade or Cisco MDS SAN fabricStorage systemsIBM DS3000 / DS5000IBM DS8000IBM Storwize V3700 / V5000 / V7000 / SAN Volume ControllerIBM XIV* The Upgrade 1 might not be needed with flexible port mapping if the total number of the internal and external ports used on the SI4093 is less or equal to 24.Table 10. SI4093 with the Brocade VDX 6730 as an FCF (Figure 10)Diagram reference Description PartnumberQuantityFlex System FCoE solutionFlex System CN4054 10Gb Virtual Fabric Adapter90Y3554 1 per compute nodeFlex System CN4054 Virtual Fabric Adapter Upgrade90Y3558 1 per VFAFlex System Fabric SI4093 System Interconnect Module95Y3313 2 per chassisFlex System Fabric SI4093 System Interconnect Module (Upgrade 1)*95Y3318 1 per SI4093Brocade VDX 6730 Converged SwitchBrocade SAN fabricStorage systemsDS3000 / DS5000DS8000®Storwize V3700 / V5000 / V7000 / SAN Volume ControllerXIV* The Upgrade 1 might not be needed with flexible port mapping if the total number of the internal and external ports used on the SI4093 is less or equal to 24.Table 11. SI4093 with the Cisco Nexus 5548/5596 as an FCF (Figure 11)Diagram reference Description PartnumberQuantityFlex System FCoE solutionFlex System CN4054 10Gb Virtual Fabric Adapter90Y3554 1 per compute nodeFlex System CN4054 Virtual Fabric Adapter Upgrade90Y3558 1 per VFAFlex System Fabric SI4093 System Interconnect Module95Y3313 2 per chassisFlex System Fabric SI4093 System Interconnect Module (Upgrade 1)*95Y3318 1 per SI4093Cisco Nexus 5548/5596 SwitchCisco MDS SAN fabricStorage systemsDS3500 / DS5000DS8000®Storwize V3700 / V5000 / V7000 / SAN Volume ControllerXIV* The Upgrade 1 might not be needed with flexible port mapping if the total number of the internal and external ports used on the SI4093 is less or equal to 24.Note: You also need SFP+ modules and optical cables or SFP+ DAC cables (not shown in Table 9, Table 10, and Table 11; see Table 3 for details) for the external 10 Gb Ethernet connectivity.Lenovo provides extensive FCoE testing to deliver network interoperability. For a full listing of supported FCoE and iSCSI configurations, see the System Storage Interoperation Center (SSIC) website at:/systems/support/storage/ssicFigure 12. SI4093 in the Flex System Interconnect Fabric solutionThe solution components that are used in the scenario that is shown in Figure 12 is listed in Table 12. Table 12. SI4093 in the Flex System Interconnect Fabric solution (Figure 12)Diagram reference Description PartnumberQuantityRack and PDU infrastructure42U 1200mm Deep Dynamic Rack93604PX10U 12 C19/12 C13 32A 3 Phase PDU46M414321U Quick Install Filler Panel Kit25R55592Top of Rack switchesRackSwitch G8264CS (Rear-to-Front)7309DRX23m Passive DAC SFP+ Cable90Y9430161m Passive DAC SFP+ Cable90Y942710Flex System Enterprise Chassis with SI4093 modulesFlex System Enterprise Chassis with 2x2500W PSU8721A1G3Flex System Enterprise Chassis 2500W Power Module43W904912Flex System Fabric SI4093 System Interconnect Module95Y33136Flex System Fabric SI4093 System Interconnect Module (Upgrade 1)*95Y33186Flex System Chassis Management Module68Y70303Flex System Enterprise Chassis 80mm Fan Module Pair43W90786Management application (optional)Switch Center, per install with 1 year software subscription and support for 20switches00AE2261* Upgrade 1 is required for x222 compute nodes or compute nodes with 4-port network adapters installed. Upgrade 1 is not required if 2-port LOM on the compute node other than x222 is used for network connectivity.Note: Cables or SFP+ modules for the upstream network connectivity are not included.Related publications and linksTrademarksLenovo and the Lenovo logo are trademarks or registered trademarks of Lenovo in the United States, other countries, or both. A current list of Lenovo trademarks is available on the Web athttps:///us/en/legal/copytrade/.The following terms are trademarks of Lenovo in the United States, other countries, or both:Lenovo®Flex SystemRackSwitchThinkSystem®VMready®The following terms are trademarks of other companies:Intel® is a trademark of Intel Corporation or its subsidiaries.Other company, product, or service names may be trademarks or service marks of others.。

Scia Engineer 2013安装手册说明书

Scia Engineer 2013安装手册说明书

All information in this document is subject to modification without prior notice. No part or this manual may be reproduced, stored in a database or retrieval system or published, in any form or in any way, electronically, mechanically, by print, photo print, microfilm or any other means without prior written permission from the publisher. Scia is not responsible for any direct or indirect damage because of imperfections in the documentation and/or the software.© Copyright 2013 Nemetschek Scia nv. All rights reserved.Release: Scia Engineer 2013Manual: Installation GuideRevision: 05/2013Nemetschek Scia OfficesLatest version is available on: /en/contact/officesBelgium Headquarters Nemetschek Scia nv Industrieweg 1007B-3540 Herk-de-StadTel.: +32 13 55 17 75Fax: +32 13 55 41 75E-mail:******************** Support PhoneCAE (Scia Engineer)Tel: +32 13 55 09 90CAD (Allplan)Tel: +32 13 55 09 80CIM (Scia Steel, Scia Steel Manager)Tel: +32 13 55 09 70Concrete (Precast Manager) Tel: +32 13 35 03 15Support Email:*********************** AustriaScia Datenservice Ges.m.b.H Dresdnerstrasse 68/2/6/9A-1200 WienTel.: +43 1 7433232-11Fax: +43 1 7433232-20************SupportTel: +43 1 7433232-12E-mail:*********************** BrazilNemetschek do BrasilRua Dr. Luiz Migliano, 1896 – sala 702, CEPSP -05711-001 São Paulo BrasilTel: +55 11 4314-5880E-mail:**********************Czech RepublicNemetschek Scia s.r.o.Evropská 2591/33E160 00 Praha 6Tel.: +420 226 205 600Fax: +420 226 201 673E-mail:******************Nemetschek Scia s.r.o.Slavickova 1a638 00 BrnoTel.: +420 530 501 570Fax: +420 226 201 673E-mail:*****************FinlandNemetschek Scia FinlandLinnoitustie 5FI-02600 ESPOOTel.: +358 207 698 600Fax: +358 207 - 698 699Email:***********************FranceNemetschek Scia sarlCentre d’Affaires10, Rue du ChâteauFR-59100 RoubaixFranceTel.: +33 3.28.33.28.67Fax: +33 3.28.33.28.69**********************GermanyScia Software GmbHEmil-Figge-Strasse 76-80D-44227 DortmundTel.: +49 231/9742586Fax: +49 231/9742587************NetherlandsNemetschek Scia bvWassenaarweg 40NL- 6843 NW ArnhemTel.: +31 26 320 12 30Fax: +31 26 320 12 39************SlovakiaNemetschek Scia s.r.o.Topol’ová 8SK - 010 03 ŽilinaTel.: +421 415 003 070-1Fax: +421 415 003 072************SwitzerlandNemetschek Scia SwitzerlandDürenbergstr. 24CH-3212 GurmelsTel.: +41 26 341 74 11Fax: +41 26 341 74 13************UAENemetschek Scia Middle EastDubai Silicon Oasis HQ BuildingP.O. Box 341041, Dubai, U.A.E.Tel.: +971 4 5015744Fax: +971 4 5015777*******************USANemetschek Scia North America7150 Riverwood DriveColumbia, MD (USA)Tel.: +1 443-542-0638Fax: +1 410-290-8050*******************Table of contents (4)1.Introduction (5)1.1Welcome (5)1.2System Requirements (5)2.Installation of Scia Engineer (7)2.1Installation of Scia Engineer (7)2.2Activation of the FlexNET Network Student protection (10)3.Uninstalling Scia Engineer (12)3.1Uninstalling with Add/Remove Programs in Windows (12)3.2Uninstalling without Add/Remove Programs (14)4.Troubleshoot (15)4.1Scia Engineer does not start (15)4.2User Access Control (16)4.3Scia Engineer 2013 on Windows 8 (17)1.1.1 WelcomeWelcome to the Scia Engineer Installation Guide. Scia Engineer is a calculation program running under Windows XP/Vista/Windows 7 with a large range of application: from the check of simple frames to the advanced design of complex projects in steel, concrete, wood…The program treats the calculation of 2D/3D frames, including the profile check and the connection check for steel constructions. Apart from frames, it is also possible to dimension plate structures, including advanced concrete calculations.This manual describes the procedures for a correct installation of the application.1.2 System RequirementsTo install Scia Engineer it is recommended that your system qualifies the following requirements:HardwareProcessor Pentium IV - 3Ghz(Advised: CoreDuo2 3 Ghz and higher) RAM 2 GB (Advised: > 4 GB)Graphics Controller 256 MB, supporting OpenGLDisk space for installation,5GB projects and temporary filesMinimum resolution 1280 x 800SoftwareScia Engineer on Macintosh To run the Scia Engineer software on Mac OS Xvirtualization software has to be used. ParallelsDesktop 7 is recommended for this. WhenParallels Desktop 7 is used, a Windows operatingsystem may be installed as a virtual machine andWindows applications are used alongside Mac OSX applications. In this way, the user has 2operating systems at the same time.Standalone protectionWindows XP 32 bitWindows Vista 32/64 bit Windows 2003 server 64 bit Windows 2008 server 64 bit Windows 2012 server 64 bit Windows 7 32/64 bit Windows 8 32/64 bit It is advised to install the latest Service Pack for these Operating Systems.Floating protection Windows XP 32 bitWindows Vista 32/64 bit Windows 2003 server 64 bit Windows 2008 server 64 bit Windows 2012 server 64 bit Windows 7 32/64 bit Windows 8 32/64 bit It is advised to install the latest Service Pack for these Operating Systems.Allplan Scia Engineer 2013 is compatible only with:Allplan 2009.0Allplan 2011.1Allplan 2012.0Allplan 2013.0Allplan Precast 2010.0However one should first install Allplan and thenScia Engineer, otherwise the proper installation forthe Allplan patch won't be recognised. Revit Scia Engineer 2013 is compatible only withRevit 2013The Revit link is available on/revit Etabs Scia Engineer 2013 is compatible withEtabs 9.2 IFC Scia Engineer 2013 is compatible only withIFC version 2x3 SDNF Scia Engineer 2013 is compatible only withVersion 2.0 and Version 3.0 Tekla Scia Engineer 2013 is compatible only with:Tekla version 15, 16, 17, 18 and 19.0 – 32bitOn 32bit OS as well as on a 64bit OS.2.This chapter describes the procedure to install a Student version of Scia Engineer.The installation procedure consists of the following steps:•Installation of Scia Engineer•Activation of the FlexNET Network Student protection2.1 Installation of Scia Engineer1. You can start the installation using the web setup from our site:Go to our download page:/And run the web setup.2. In the dialog box which appears, select the language for installation:The language chosen for installation is also the default language that will beused for the help files of Scia Engineer.3. The Welcome screen for installation appears. Press [Next] to continue.4. In the dialog Customer Information the User Name and Company Name canbe inputted. The Company Name will appear automatically in the document ofScia Engineer. Press [Next] to continue.5. In the dialog Choose Destination Location the folder where the files will beinstalled can be specified. By default the destination folder is created in ProgramFiles. It is advised to use this default location.Press [Next] to continue.6. In the dialog Setup Type the preferred setup can be chosen. Press [Next] tocontinue.NoteWhen choosing a “Typical installation”, NOT all language modules will be installed, only the English language and the language chosen for installation. If you wish to install other languages, it is needed to choose a Custom install where multiple languages can be selected.To be able to choose another language for the environment of Scia Engineer two requirements need to be met:The preferred language needs to be installedThe necessary language module needs to be active in the dongle or on the server If you want to install one of the Scia Engineer Plug-ins, then you need to select the plug-in in the Custom installation.The following plug-ins are available: Tekla Structures plug-in, Revit Structure plug-in, CADS RC Link Designer, BS2000, Pipeline Wizard, Composite Beam, Composite Column, Arcelor Mittal-Cellular beams.7. In the dialog Protection Defaults the default values for the protection settingscan be set.Activate Student version.If you activate the option run activation manager when setup is finishedthe next chapter for the activation of the licence will be started automatically.Otherwise you have to start the Activation manager manually after theinstallation of Scia Engineer.Press [Next] to continue.8. In the dialog Application Defaults the default values for the national code canbe set.Choose the default setting for your national code and measuring system. Press[Next] to continue.9. The last window shows an overview of the selected settings. Press [Install] tostart the installation process.10. After installation, the message appears that Scia Engineer has been installedsuccessfully. Press [Finish] to end the installation procedure.2.2 Activation of the FlexNET Network Student protection1. Execute the file C:\ProgramFiles\SCIA\FlexNET\ActivationUtility\ActivationUtility.exeA shortcut to this application can be found on your desktop as Activation managerPress [Read Licence ID]The Lock ID is stored in a SCIAx.lid-file, where x represents the number of your file.The file will be send to you by email.Select your lid-file and press [Open]2. The number of your license file will appear in the FlexNET activation utility window.Select this number and press [Activate licence]3. The circle in front of the license number will become green and the license file hasbeen activated.Press [Close]NoteWhen using the license file on another computer, it is necessary to deactivate thelicense file on the previous server.Using Windows Explorer, go to the folder C:\ProgramFiles\SCIA\FlexNET\ActivationUtilityExecute the file ActivationUtility.exeSelect the License file number and press [Return License]Press [Close]From now on it will be possible to use Scia Engineer 2013 in student mode on your computer.3.3.1 Uninstalling with Add/Remove Programs in WindowsScia Engineer can be uninstalled like any other windows based software application:1. Go to Add or Remove Programs through Start > Settings > Control Panel >Add or Remove Programs.2. A list with installed software applications will appear. Select Scia Engineer andpress [Change/Remove]3. In the dialog box that appears choose the option Remove4. Press [Next] to start the uninstall procedure.After completing the uninstalling, some settings remain in the Registry of windows.These traces can be deleted manually. Deleting these entries can be necessarywhen problems occur with a new installation.1. Open the Run dialog box through Start > Run2. Type regedit and press [OK]Take note, for this step it is required to have at least Power-User rights!3. The Registry Editor appears.4. Go to the following key’s and delete them using the Delete button.HKEY_CURRENT_USER\Software\SCIA\ESA\*HKEY_LOCAL_MACHINE\Software\SCIA\ESA\*Where * represents the version number.5. Close the Registry Editor through File > ExitAfter completing the uninstalling, some folders remain on your hard disk and can be deleted manually:32 bits computer: C:\Program Files\SCIA\ESA**64 bits computer: C:\Program Files (x86)\SCIA\Engineer**Also the following folders remain on your hard disk and can be deleted:Windows XP: C:\Documents and Settings\#USER#\ESA**C:\Documents and Settings\#USER#\My Documents\ESA**Windows Vista and Windows 7: C:\Users\#User#\Esa**C:\Users\#User#\Documents\Esa**Where ** represents the version numberAttentionThese folders can be deleted using Windows Explorer. Please note that the firstfolder can contain projects so the user must be absolutely sure if he/she wishes todelete these folders.3.2 Uninstalling without Add/Remove ProgramsSometimes Scia Engineer cannot be uninstalled using “Add/Remove programs” of Windows. Sometimes this give an error message or Scia Engineer is not added to Add/Remove Programs. This way, it is not possible to uninstall the software.This problem can occur with every Windows based program.To easily uninstall Scia Engineer, use the following procedure:Go to ‘Start’ -> ‘Run’In the dialog that appears, type the following command:msiexec /x {8BF90233-A9C2-41D1-BEEA-A391BE0F15FD}This will execute the same procedures as uninstalling through Add/Remove Programs.A complete list of Frequent Asked Questions can be found on our website:/en/support/faq4.1 Scia Engineer does not startGo to "Start -> all programs -> Scia Engineer 2013 -> Protection setup"And change here the option "Type" to "Only floating" and the address to: @127.0.0.1 as shown below:And click on OK.If Scia Engineer doesn’t work still after this change, please go to the services ofWindows. You can do this by typing "Services" at the Start menu in Windows:A list of Services will appear. Search for the service "lmadmin" here. Stop this serviceand restart it.Afterwards Scia Engineer 2013 should start up.4.2 User Access ControlIf UAC (User Access Control) is enabled the following message will appear at the end of the installation:Choose “Install this driver software anyway” to end the installation.NoteFor using Scia Engineer, standard user rights suffice. Here, no Administrator rightsare needed.However, the user must have read/write permission for the user folder of SciaEngineer:Windows XP: C:\Documents and Settings\#USER#\ESA**Windows Vista, Windows 7: C:\USERS\#USER#\ESA**Where ** represents the version number and #USER# represents the user login name4.3 Scia Engineer 2013 on Windows 8If Scia Engineer 2013 does not start correctly on Windows 8, you can try to run it in compatibility mode on Windows 7 as follows:1. Right click on the Scia Engineer 2013 icon and choose for Properties2. Go here to the tab “Compatibility”3. And activate the option “Run this program in compatibility mode for:” and choose for“Windows 7” just below it:。

RSLogic5000安装和使用手册

RSLogic5000安装和使用手册

Publication 9399-RLD300GR 技術支援電話:1-440-646-780技術支援傳真:1-440-646-7801 世界網站 :1999,2000 Rockwell 軟體公司,Rockwell 自動化公司,在美國版權所有,翻印必究。

部份版權由Allen-Brandley 公司‧ LLC ,Rockwell 自動化公司所有。

此手冊和相關Rockwell 軟體屬於Rockwell 軟體公司所有。

若非經Rockwell 軟體公司同意,嚴禁翻印。

請遵照執照合約細則。

Rockwell 軟體公司商標, RSAlarm, RSAnimator, RSAssistant, RSBatch, RSBreakerBox,RSButton, RSChart, RSCompare, RSControlRoom, RSData, RSDataPlayer, RSEventMaster,RSGuage, RSJunctionBox, RSLogix Emulate 5, RSLogix Emulate 500, RSGuardian,RSHarmony, RSKeys, RSLadder, RSLadder 5, RSLadder 500, RSLibrary Builder, RSLinx,RSLogix 5, RSLogix 500, RSLogix Frameworks, RSLogix SL5, RSMailman, RSNetworx forControlNet, RSNetworx for DeviceNet, RSPortal, RSPower, RSPowerCFG , RSPowerRUN,RSPowerTools, RSRules, RSServer32, RSServer, RSServer OPC Toolkit, RSSidewinderX,RSSlider, RSSnapshot, RSSql, RSToolbox, RSToolPak I, RSToolPak II, RSTools, RSTrainer,RSTrend, RSTune, RSVessel, RSView32, RSView, RSVisualLogix, RSWheel, RSWire,RSWorkbench, RSWorkshop, SoftLogix 5, A.I. Series, Advanced Interface (A.I.) Series,AdvanceDDE, AutomationPak, ControlGuardian, ControlPak, ControlView, INTERCHANGE,Library Manager, Logic Wizard, Packed DDE, ProcessPak, View Wizard, WINtelligent,WINtelligent LINX, WINtelligent LOGIC 5, WINtelligent VIEW, WINtelligent RECIPE,WINtelligent VISION, and WINtelligent VISION2 是Rockwell 軟體公司/自動化公司註冊商標。

Oracle Essbase Integration Services 11.1.1.3 发行版说明

Oracle Essbase Integration Services 11.1.1.3 发行版说明

Oracle® Essbase Integration ServicesRelease 11.1.1.3Readme[Skip Navigation Links]About This Service Fix (1)New Features (1)Defects Fixed (1)Known Issues in Release 11.1.1.3 (3)Documentation Updates (6)About This Service FixThis Readme file describes the defects fixed in Oracle® Essbase Integration Services Service Pack11.1.1.3 as well as the known issues in this release.Top of Document New FeaturesCertification MatrixInformation about system requirements for EPM System products is now available in a spreadsheet format in the Oracle Hyperion Enterprise Performance Management System Certification Matrix, posted at /technology/products/bi/hyperion-supported-platforms.html. Systemrequirements are no longer part of the Oracle Hyperion Enterprise Performance Management System Installation Start Here.Supported LanguagesThis release supports non-English languages. The list of supported languages for all EPM System products is included in the Oracle Hyperion Enterprise Performance Management System Certification Matrix, posted at /technology/products/bi/hyperion-supported-platforms.html.Top of Document Defects FixedDefects Fixed in Release 11.1.1.3•Member load. In the batch file created for EIS scheduling for member loads, the path was not updated to include the start command.(8439772)•Console. Creating the fact table by selecting the Menu > Tools option failed.(8403636)•Data load. Batch file executed during data loads falsely reported that load was terminated with errors despite data load being successful.(8412247, 8304235, 8269211)•Console. Integration Services Console was not granting re-access to users after they exited the application because user ID information was not being cached.(8412193, 7714801)•Data and member loads. Data and member loads failed when run from a .cbs script, but Integration Services status indicated the load was successful.(8412254, 8304252, 7721750)Defects Fixed in Release 11.1.1.2These defects are fixed in Integration Services release 11.1.1.2. The defect number follows thedescription of the defect.Drill-Through Template SQL. Incorrect table alias names were generated in the SQL query created by Integration Server.(6584510, 8-631137724)Drill-Through Template SQL. Integration Server terminated abnormally when verifying Drill-Through Template SQL.(6851055)Data Load. When the Default Miscellaneous Member option was enabled for the aggregate storage option, the default members were not added and the data load failed. The data load failure has been addressed; however, you may need to reload any rejected records.(7607685, 7268275)Defects Fixed in Release 11.1.1.1These defects are fixed in Integration Services release 11.1.1.1. The defect number follows thedescription of the defect.Console. When building a cube in Integration Services Release 9.3.1., using a metaoutline that been generated in Release 7.x, a false error condition sometimes prevented users from building the cube.(7138407)Console. When several batch jobs for data loads were run consecutively, and one or more scripts had empty parameters, Integration Services would sometimes shut down, forcing a manual restart.(7212289)Load. In data loads, the displayed total of records loaded and records rejected exceeded the number of records in the outline.(7310328, 7158311)Drill-Through. If users changed passwords, sometimes drill-through report operations would fail because of encryption errors.(7360009, 7393959)Top of DocumentKnown Issues in Release 11.1.1.3The following issues are the noteworthy known issues of this release.ODBC Notes•“Localhost” is not a valid server name. In the Login dialog box, you must specify a computer name or IP address in both the Integration Server frame and the Essbase Server frame.•For UNIX systems, Integration Services installation creates a template odbc.ini. To store information about how to connect to a relational data source, edit the file using your preferrededitor.•To configure a Teradata data source, the TDODBC environment variable must be set manually. Configuration File Entry for DB2 OS/390DB2 OS/390 is supported only as a data source and should not be used as an OLAP Metadata Catalog.If you use IBM DB2 OS/390 as a data source, you must add an entry to the ais.cfg file for each data source name you configured in your DataDirect Wire Protocol driver for DB2. Add an entry to the ais.cfg file in the following format: [DS:dsn:390]. For example, using the sample database, TBC, the following is the entry to the ais.cfg file:[DS:TBC:390]JISX0213 Japanese Character Set Not SupportedThe JISX0213 Japanese character set, which replaces the JISX0208 and JISX0212 Japanese character sets, is supported on Windows Vista.The Oracle Essbase family of products, including Integration Services, does not support the JISX0213 Japanese character set. (6576813, 8-563756229)Windows Server 2003 SP1 May Experience Abnormal ShutdownIf you are using Windows Server 2003 Service Pack 1 with Integration Services, your system may experience an abnormal shutdown. To prevent this, install the update from Microsoft by going to: /kb/923996/Column Names with 0x5C Double-byte Characters May Not DisplayIf column names contain 0x5C double-byte characters, the columns may not display in a table.(6551802, 2-HYPER00071286)MBCS Characters Should Not Be Used in Names of Some Entities Multibyte-character-set characters should not be used in the names of these entities:•OLAP models•Metaoutlines•Data sources•Owners(6550123; 2-HYPER00073848, 73905, 73906, 73910, and 74122)Oracle Database as Unicode Data SourceIf you run Integration Services on Windows and access an Oracle database as an MBCS or Unicode data source using the DataDirect Wire Protocol Driver, characters corresponding to 0x4E88 in UTF-8 encoding may not be processed properly.Time-based Incremental Load LimitationDue to database restrictions in some databases such as Oracle, if the IN clause has more than 1,000 outline members that require updating during time-based incremental loads, SQL statements may not execute. In such cases, we recommend full loads rather than time-based incremental loads.Unable to Validate @ISUDA FunctionsAlthough Oracle Essbase Administration Services validates recently added functions in formulas for the block storage option (BSO), Integration Services may not. We strongly recommend you use Oracle Essbase Administration Services to validate these functions.Japanese EncodingIf you use Japanese encoding, Oracle recommends you use MS932 encoding instead of Shift-JIS.Specifying Ancestors in Template SQL for Drill-Through Operations on Duplicate MembersIn general, Oracle does not recommend using Drill-Template SQL for OLAP metaoutlines that support duplicate member names.If you still choose to use Drill-Through Template SQL for OLAP metaoutlines that support duplicate member names, Oracle suggests you take the following actions in order for Drill-Through Template SQL to function correctly:•Associate database keys for the drill-through-enabled members.To do this, in the General tab of the Member Properties dialog box for each drill-through-enabled member, in the Member Key Column drop-down list, select the appropriate database key columns for the drill-through-enabled members.These actions are valid for drill-through reports defined on any member level, including level zero members.•For drill-through defined on level zero members (leaf nodes), you can also fully identify a duplicate member by specifying all the ancestors for that member in Template SQL.In the following example of Template SQL using the TBC sample, for a drill-through intersectiondefined on Product.SKU, a WHERE clause was added (see bolded text) for the ancestor of SKU in order to fully define the member:SELECT DISTINCT ac."SKU", ac."SKU_ALIAS", ac."CAFFEINATED", ac."OUNCES",ac."PKGTYPE", ac."INTRODATE", aa."SUPPLIERID", ad."SUPPLIER_ALIAS", ad."ADDRESS", ad."CITY", ad."STATE", ad."ZIP", ad."COUNTRY"FROM TBC.SALES aa, TBC.PRODUCTDIM ab, TBC.PRODUCT ac, TBC.SUPPLIER adWHERE aa."PRODUCTID" = ac."PRODUCTID"AND aa."SUPPLIERID" = ad."SUPPLIERID"AND ac."SKU" = ab."SKU"AND ((($$Year-COLUMN$$ IN ( $$Year-VALUE$$))))AND (ab."FAMILY" in ('100'))AND (((ab."FAMILY" in ('100','200','300','400','Diet')) AND ($$Product-COLUMN$$ IN ( $$Product-VALUE$$))))The caveat to the solution given in the above example is that the member is fully defined only for children of Product 100; it is not practical to define Template SQL for every possible ancestor value.(6807790, 1-156SS6)Runtime Filter Condition Limitation for Customized Drill-Through OperationsIf you customize drill-through reports at run time and add a user-defined filter, keep the length of the filter under 8KB; otherwise, some members may not be included in the drill-through report query.(1-147T5F)Users Without Create Access to Essbase Server Cannot Verify Member FormulasTo verify member formulas, users must have Create access to the Essbase Server.(1-82215061)Updating Drill-Through Reports Not Supported for Outlines Containing Duplicate Member NamesRelease 11.1.1 does not support updating drill-through information in an outline containing duplicate member names. For such outlines, you should perform a full member load.Drill-Through Operations Are Not Supported on Unicode Data in Release 11.1.1 Records Rejected During Data Load when Alternate Fact Table SelectedIf the Time dimension is built directly from the fact table, and you select an alternate fact table, the data load may reject those records for which time members are not found in Oracle Essbase. In such cases, be sure that the time dimension is built to span time periods of all fact tables.(1-194924642)SQL Server 2005 Requires Name of New Executable in Sample Creation Scripts to Create TBC Sample Tables and to Load Sample DataThe current batch files and scripts used to create the TBC sample tables and to load the sample data do not function with SQL Server 2005. These files require the executable named SQLCMD.EXE.WORKAROUND: Edit the batch file install_sqlsrv.bat located in the AIS\samples directory, and replace the name of the executable ISQL.EXE with the new executable name SQLCMD.EXE.(8-532792001)Application Naming RestrictionsWhen managing Oracle’s Hyperion Shared Services models and naming applications, you cannot use the forward slash (/), backslash (\), or double quotation (“) characters.(8-514151218)Read-only Permission to External Data Sources for Drill-Through ReportsOracle recommends that your users be granted read-only permission to external data sources for drill-through reports and custom data load SQL.Adding Alternate Hierarchy a Second Time Duplicates ValuesWhen building a shared hierarchy for a block storage database, adding a shared hierarchy a second time may duplicate the values stored on a single element, resulting in incorrect data. This problem occurs when shared members are from the same hierarchy, such as these two hierarchies from theTBC sample database: Diet > 100-20 and 100 > 100-20.WORKAROUND: Use user-defined SQL to edit data load commands.(6584211)Start and Stop Controls for Windows Service on Windows 2003 SP1On Windows 2003 SP1, after installing Integration Services, the EPM System Installer uses Windows services to start and stop the services for Integration Services. Sometimes after stopping the service using Windows Services console, the Integration Server process, olapisvr.exe, continues to run.WORKAROUND: Manually stop the “olapisvr.exe” and “olapisvc.exe” processes by using the Windows Task Manager.(7253757)Long Table and Column Names Truncated in the Drill-Through WizardWhen using the Drill-Through Wizard in Essbase Spreadsheet Add-in, users will only see the first 80 characters of the table or column name.(6536313)System Limitations•Integration Services supports full Unicode functionality only on Oracle relational database servers.•Oracle recommends you use the same language for your Data source names as you use for your applications. (English will work in all cases.)•When creating a drill-through report with an OLAP intersection level based on a user-defined dimension or column, neither of the variables of the form $$dimension-COLUMN$$ or $$dimension-VALUE$$ will be created.•To retain and upgrade Dynamic Time Series settings made in Integration Services prior to release6.5.4, open and save the metaoutline using release 11.1.1. For recursive and alternate hierarchies,we recommend that you verify your settings.•Integration Services does not support user-defined tables created in Sybase or Informix.Top of Document Documentation UpdatesAccessing Hyperion Product DocumentationThe most recent version of each Hyperion product guide is available for download from theDocumentation area of the Oracle Technology Network (OTN) Web site(/technology/index.html). Deployment-related documentation is also availablefrom the Oracle E-Delivery Web site (/EPD/WelcomePage/get_form).Individual product guides are available for download on the Oracle Technology Network (OTN) Web site only.Note: Not all of the documentation for this product has been updated from Release 11.1.1.1 or11.1.1.2. Similarly, the product UI may not have been updated from Release 11.1.1.1 or 11.1.1.2. Oracle Call Interface No Longer SupportedOracle® Essbase Integration Services no longer supports Oracle Call Interface (OCI). References in the documentation to OCI should be disregarded.Top of DocumentCopyright © 2009, Oracle and/or its affiliates. All rights reserved.。

Studio 5000 Application Code Manager中的机器构建库文档说明书

Studio 5000 Application Code Manager中的机器构建库文档说明书

OverviewMachine Builder Libraries help design machines faster, delivering specific functionality and best-in-class performance in a modular approach.Machine Builder Libraries are available in Studio 5000® Application Code Manager as a Rockwell Automation Library.Studio 5000 Application Code Manager allows the creation and management of your own library objects for reuse on other projects.The use of Machine Builder Libraries as components of your own libraries facilitates the management of the lifecycle of your application code.Application Content – Machine Builder LibrariesReduce Time to Design, Develop and Deliver Machine Builder Libraries GranularityMachine Builder Libraries are designed in a modular way to maximize granularity andflexibility. Machine Builder Libraries utilize standardized interfaces to assure interoperability with each other. They are also made to be embedded into your existing Logix Application and work with your existing code where possible.Machine Builder Libraries are:• Life-cycle managed • Tested and documented• Best-in-class for performance • Application-centric• Flexible, granular and modular •Easy to integrateStudio 5000Application Code Manager:• Easily create and configure objects using re-usable libraries of code • Helps improve design consistency, reduce engineering costs and achieve faster commissioningBenefit from Machine Builder Libraries Architecture ExampleUser selects applicable blocks from the library to assist the creation of a specific application module. For example, user needs to build a “Cross-seal and cut” application module.The composition of a function using smaller and relevant blocks allows the creation of greater variability of functions.Device Handler• Kinetix® and Powerflex axes handler– Enhanced diagnostics (multiple languages)– Manual axis operation – Path recovery– Axis virtualization = test your code as a virtual machine – Standard interface for application code – Several methods availableNo Product No Bag• Cam management– Connect when product available– Disconnect when product not available – Adjust phase– Switch from cyclic 1 to cyclic 2Machine Builder Libraries ArchitectureReduce Time to Design, Develop and DeliverDevice Operation Rotary Knife Cam Calculation• Calculate cam profile – Connect (accel)– Disconnect (decel)– Cyclic (continuous)• Configure profile– Maximum smoothness – Minimum peak velocity • Sync compensation – Linear – ArcsineTechnologySelect library objects from Machine Builder Libraries that helps build the desired application module.As an example, use Machine Builder Libraries to accelerate the development of a “Cross-seal and cut section” application module.Publication 9324-PP003B-EN-P – September 2017 Copyright © 2017 Rockwell Automation, Inc. All Rights Reserved. Printed in USA.Allen-Bradley, Connected Components Workbench, Guardmaster, Kinetix, LISTEN. THINK. SOLVE., Micro800, PanelView, PowerFlex, Rockwell Software and Studio 5000 are trademarks of Rockwell Automation, Inc. Trademarks not belonging to Rockwell Automation are property of their respective companies.Connect with us.For More InformationContact the Machine Builder Libraries team at ************************.com.Now available for download on the Compatibility & Downloads web page at . Click here to download.Registration Instruction• Arm/re-arm in one instruction• Hardware registration – drive and 1732 SOE modules • Software registration – capture position of another axis • Look for the sensor in a specific position window • Support for CIP , virtual and consumed axes•Calculate correction distance, length and averagesPosition Tracking• Produce an event into a position tracking queue • Consume an event from a position tracking queue• Tracking queue consists of ID, position, product presence and user-defined dataMachine Performance Tracking• RAPID equipment interface Add-On Instructions (AOI) data structure• View current machine mode and state • Track cumulative mode/state times• Track Overall Equipment Effectiveness (OEE) and production data over 1-, 5- and 12-hour timeBenefits of Machine Builder Libraries:• Faster design cycles–U se the Device Handler in Virtual Mode and virtualize your complete machine application code– No need to wait for hardware availability to test the code • Reduced engineering cost– U se Device Handler queue of events to troubleshoot your application code • Reduced execution risk– C reate and manage your reusable modular code based on application specific, tested and documented libraries • Increased machine value–B uild a machine event list aggregating events from different devices• Managed machine life cycle– E asier hardware upgrade due to device handler standard interface – S eparation of application code and hardware management – B enefit from futures updates of Machine Builder Libraries – E asier machine functionalities upgrade by updating Machine Builder LibrariesMachine Builder Libraries Portfolio Examples。

Rockwell Automation FactoryTalk Logix Echo 产品说明书

Rockwell Automation FactoryTalk Logix Echo 产品说明书
警告:标识可能导致暴露于危险环境从而造成人员伤亡、财物损害或经济损失的做法或环境的相关信息。
注意:标识可能导致人员伤亡、财物损害或经济损失的做法或环境的相关信息。注意事项可帮助您识别危险,避开 危险,以及意识到后果。
重要 标识对成功应用和了解产品至关重要的信息。 还会在设备上或内部使用标签来提供具体预防措施。
FactoryTalk Logix Echo SDKFra bibliotek附录 A
SDK 文档套件和 NuGet 软件包 .......................................................... 35 API 功能 .................................................................................................... 35
FactoryTalk Logix Echo 获 取结果指南
获取结果指南
Rockwell Automation 出版号 9310-GR001B-ZH-P - 2022 年 11 月 取代出版号 9310-GR001A-ZH-P - 2021 年 8 月
原始说明
FactoryTalk Logix Echo 获取结果指南
章节 3
使用控制器快照 ........................................................................................ 25 添加快照............................................................................................... 25 编辑快照.............................................................................................. 26 恢复快照.............................................................................................. 26 导出快照.............................................................................................. 27 导入快照.............................................................................................. 27

Process Control Annunciator Alarm Modules说明书

Process Control Annunciator Alarm Modules说明书

Power Supply 85 to 265 VDC/VAC 85 to 265 VDC/VAC 85 to 265 VDC/VAC 12 to 24 VDC/VAC 12 to 24 VDC/VAC 12 to 24 VDC/VAC
ACCESSORY A-360, Aluminum DIN Rail 1 m
PROCESS CONTROL
Series SC1
Process/Temperature
Alarm
Switch
Module
Two Form C (SPDT) Switches, Small Size, Mounts Easily on 35 mm DIN Rail
3.88˝ [98.5]
0.886˝ [22.5]
Model SC1090
SC1290
Input 4 to 20 mA, 10 to 50 mA, 0 to 20 mA, 0 to 10 V, -10 to 10 mV Thermocouple Type J, K, R, S, T, E
SC1490 RTD Pt1000 Ni100, Ni120, Cu10, Ni-Fe1000, N-Fe2000
SCL1090 4 to 20 mA, 10 to 50 mA, 0 to 20 mA, 0 to 10 V, -10 to 10 mV
SCL1290 Thermocouple Type J, K, R, S, T, E
SCL1490 RTD Pt1000 Ni100, Ni120, Cu10, Ni-Fe1000, N-Fe2000
Lead Compensation Error: (SC1490) ≈ 0.02%/Ω. Open Lead Protection: (SC1490) upscale only. Input Impedance:

IBM Cognos 软件开发工具包版本 11.0.0 混搭服务开发人员指南说明书

IBM Cognos 软件开发工具包版本 11.0.0 混搭服务开发人员指南说明书
Chapter 3. Cognos Mashup Service samples......................................................... 11
Java samples..............................................................................................................................................11 Java sample file locations.................................................................................................................... 11 Running the Java samples................................................................................................................... 12
Chapter 2. Overview of the Mashup Service............................................................ 7
Programming interfaces...............................................................................................................................7 Identifying reports....................................................................................................................................... 8 Output formats.............................................................................................................................................9 Sample programs.......................................................................................................................................10

WAS全套错误代码

WAS全套错误代码

ADMA5ADMA5104I=ADMA5104I: 已成功更新 {0} 的服务器索引条目。

此参考消息表明程序状态。

用户无需执行任何操作。

ADMA0014E=ADMA0014E: 验证失败。

{0}准备应用程序时发生验证错误。

此消息后跟详细错误消息。

请参阅此详细消息,以获取如何更正问题的指示信息。

ADMA6001I=ADMA6001I: 将开始应用程序准备工作-此参考消息表明程序状态。

用户无需执行任何操作。

ADMA0158I=ADMA0158I: [EJBDeploy] {0}当运行 DeployEJBTask 时,此消息将写入日志文件。

请检查参考消息和 DeployEJBTask 以前的消息,以确定是否需要执行任何更正操作。

ADMA5103E=ADMA5103E: 从配置库删除 {0} 的配置数据失败。

卸载过程无法成功删除应用程序配置数据。

应用程序卸载仍将继续。

If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: WebSphere Application Server for z/OS Support page: .ADMA0122E=ADMA0122E: 在获取应用程序 {0} 时发生意外的异常。

异常:{1}。

在获取指定的应用程序作用域时发生意外错误。

请查看并调查最初的异常。

ADMA0013E=ADMA0013E: 找不到任务 {0} 的依赖性辅助控件。

为应用程序设置任务时发生错误。

如果任务提供程序提供了安装任务对象,那么请验证是否正确设置了这些对象。

ADMA0049E=ADMA0049E: 获取部署描述符 {0} 的模块时发生异常传递给 AppManagement MBean 的 getApplicationInfo API 或getModuleInfo API 的模块唯一 URI 与企业归档(EAR)文件中的模块不匹配时发生异常。

Atlas错误代码

Atlas错误代码

E001-E009 0 拧紧操作失败E100-E199 1 事件相关错误E200-E299 2 用户输入事件E300-E399 3 统计事件E400-E499 4 通信事件E500-E599 5 硬件事件(工具)E600-E699 6 硬件事件(DC3000/MC3000)E700-E799 7 硬件事件E800-E899 8 软件事件E900-E999 9 事件MMI3000事件代码E003 扭矩测量值可能无效编程错误。

请检查程序并保证在第二操作阶段套筒转动过。

E102 由于参数lock on reject,拧紧操作被禁止当参数lock on reject[C130]设置为禁止拧紧操作,则欲进行一个拧紧操作时会显示此事件代码.E103 通过数字输入锁定工具工具通过数字输入被锁定。

——实际紧固位置与设定位置不同E107 由于采用线体控制而未打开批处理功能,拧紧操作被禁止若选择使用生产线控制一个工作,则当收到一个行控制起动信号时,工作才启动。

E112 重复拧紧重复拧紧一个已经拧紧过的螺拴E113 电流达到极限,退出拧紧操作当电流超过极限时,驱动器被禁止使用。

E117 工具锁定-不能访问RBU Power Focus不能与RBB之间进行通信,且必须重启保护数据。

E120 电机调整失败电机调整失败。

可能是在电机调整完成以前释放了扳机或工具产生故障。

E121 开口调整失败此事件表明开口调整命令未能成功地执行。

E125 超时警报或扭矩丢失警报当在Pset中启动超时报警功能,此事件代码表明由于超时拧紧操作退出。

此警报启动表明引起拧紧操作退出的基本原因是超时。

E126 多步拧紧操作退出此事件表明当前运行的多步拧紧未完全执行(在拧紧操作完成前驱动器被关闭或工具扳机被释放)。

E127 PVT关闭此事件表明在自攻中或拧紧操作的现行阶段驱动被关闭E128 扳机过早释放当在Pset中启动扳机释放功能时,此事件表明工具扳机在拧紧操作达到最终目标以前被释放E129 扭矩低于目标值当在Pset中启动“扭矩低于目标值”功能时,此事件表明扭矩结果值低于最终目标值,即使扭矩结果值大于最终扭矩最小值,扭矩状态也是NOK。

ReadSoft AB PROCESS DIRECTOR 7.3 故障排除指南 September

ReadSoft AB PROCESS DIRECTOR 7.3 故障排除指南 September

PROCESS DIRECTOR 7.3Troubleshooting GuideSeptember 2016 – ReadSoft ABThe contents of this document are subject to change without notice.Questions or comments about this document may be emailed to **************************.02092016.1253ReadSoft AB (Head office) | Södra Kyrkogatan 4 | SE-252 23 Helsingborg | Sweden | Phone: +46 42 490 21 00 | Fax: +46 42 490 21 20 ReadSoft AG | Falkstrasse 5 | 60487 Frankfurt | Germany | Phone: +49 69 1539402-0 | Fax: +49 69 1539402-13ContentsIntroduction (4)About this guide (4)Typographical conventions (4)Troubleshooting (5)Collecting debugging information (5)Dealing with short dumps (9)Troubleshooting performance issues (9)Testing the ArchiveLink connection (9)Repairing the Worklist (10)Troubleshooting the Web Application connection (10)Troubleshooting missing action buttons (11)Troubleshooting the Services for Object button (13)User exit / BAdI problems (14)Creating the /EBY/ namespace (15)Establishing number ranges (15)Regenerating menus and toolbar (16)IntroductionAbout this guideThis guide is intended for implementation consultants who are installing and configuring the SAP/ABAP component of PROCESS DIRECTOR.The guide offers useful tips and tricks on what to do if something is going wrong with PROCESS DIRECTOR.For information on installing and configuring PROCESS DIRECTOR, refer to the following guides:▪Importing PROCESS DIRECTOR into SAP▪PROCESS DIRECTOR SAP Configuration Guide▪PROCESS DIRECTOR Advanced Configuration Guide▪PROCESS DIRECTOR Reference GuideTypographical conventionsThe following typographical conventions are used:▪Menu names, commands, and dialog names appear in bold.▪Names of keys on your keyboard appear in S MALL C APITAL L ETTERS.▪Names of files, folders, and settings appear in Courier font.▪SAP transaction codes and program names appear in ARIAL MONOSPACE.▪Variables that have to be replaced by an actual value are italicized or appear in <>.Troubleshooting▪Collecting debugging information▪Displaying message call stacks▪Dealing with short dumps▪Performance issues▪Testing the ArchiveLink connection▪Repairing the Worklist▪Troubleshooting the Web Application connection▪Troubleshooting missing action buttons▪User exit / BAdI problems▪Creating the /EBY/ namespace▪Establishing number ranges▪Regenerating menus and toolbarCollecting debugging informationIf you are not sure where something is going wrong, it can be helpful to collect more debugging information.Try to zero in on the problem by successively increasing the logging granularity:1.Start by checking the document message logs for warnings and errors.2.If a given logging detail level does not provide enough information, increase the loggingdetail level and recheck the message logs.Logging detail level How to setProduction This detail level refers to the logging behavior as currentlyconfigured—that is, the default level of message logging in theproduction configuration.Logging detail level How to setDebug messages As above, but in addition:▪Successively enable display of debug messages.Message call stacks As above, but additionally:▪Successively enable display of message call stacks.Displaying debug messages1.Select the SAP GUI menu item System > User Profile > Own Data and then click theParameters tab.2.Add the parameter ID /EBY/PDBO_DEBUG_MSG to the table and set the appropriateparameter value:Value When to useEE If you want to display Debug Error messages onlyWW If you want to display debug Debug Error and Debug Warning messages.II If you want to display all Debug messages3.Save your changes.Displaying message call stacksEnable message call stacksFor SAP GUI1.Select the SAP GUI menu item System > User Profile > Own Data and then click theParameters tab.2.Add the parameter ID /EBY/PDBO_CALLSTACK to the table and set the appropriateparameter value, then save your changes.Value When to useE To enable call stacks for errors only.W To enable call stacks for errors and warnings.S To enable call stacks for all messages.For the Web Application1.In SAP transaction SU01, enter the name of the Web Application RFC user and click .2.Add the parameter ID /EBY/PDBO_CALLSTACK to the table and set the appropriateparameter value.3.Save your changes.View message call stacksFor SAP GUITo display the call stack for a message:1.Enable message call stacks.2.Click to open the message viewer3.Click the message's call stack icon .For the Web ApplicationIn the ABAP debugger, set a breakpoint at the end of the function module/EBY/PDWA_RFC_MAIN.When the breakpoint is hit:1.Add this field to the field names: lr_support->mr_controller->mt_messages.2.View the message call stack by clicking on the CALLSTACK field:Dealing with short dumpsIf dumps occur during document posting, you can try to narrow down the possible cause by elimination:▪If short dumps are occurring during control framework flushes (METHOD FLUSH), the underlying problem is usually being hidden by asynchronous processing. To track the problem down, you need to switch on automatic synchronous queue processing byselecting the SAP GUI menu item System > Utilities > Autom. Queue: Synchronous Processing.▪Post the same document from a standard SAP transaction to see whether PROCESS DIRECTOR is at fault. For example, if posting fails in PROCESS DIRECTORRequisitions, try posting with the same data in SAP transaction ME21N.▪Deactivate your dynamic presets to see whether they are causing the problem.▪Deactivate your user exit / BAdI implementations.Short dump LOAD_PROGRAM_LOSSIf this short dump occurs during document transfer, check, post, or other actions, increase the abap/buffersize parameter in transaction RZ11. Recommended value: 400000 or higher.Troubleshooting performance issuesIf you are experiencing poor performance in PROCESS DIRECTOR, check the Tune Summary in transaction ST02 with the SAP System Administrator.Testing the ArchiveLink connectionTo test the ArchiveLink connection:1.Directly enter SAP transaction OAC0.2.Select the PROCESS DIRECTOR content repository in the overview list.3.Click the toolbar button to go to the detail view.4.Click the button .Repairing the WorklistWorklistIf you are having a Worklist related issue, you should:1.Be aware that Worklist behavior may not match the currently saved configuration, as theconfiguration may have changed since the Worklist was last generated.2.Check any Worklist node authorization objects to make sure they are not causing theproblem.3.Make sure the problem is not being caused by an active implementation of the user exit /BAdI Modify Worklist.4.Regenerate the Worklist. Choose Yes in the popup that asks if you want to regeneratestatic nodes.If these steps do not resolve the issue, directly enter SAP transaction SE38 and execute the standard Worklist repair reports that ship with PROCESS DIRECTOR:1./EBY/PDBO_GEN_FAILED_NSTDSETS2./EBY/PDBO_CHECK_NESTEDSET_NEW3./EBY/PDBO_CHECK_WL_DOC_COUNTSelection screenTo debug selection screen related issues, try setting a breakpoint on the/EBY/CL_PDBO_WORKLIST_NODE method GET_GUIDS and examine the content of thelt_query field.Troubleshooting the Web Application connectionHow to display the PROCESS DIRECTOR Web Application versionLog on to the PROCESS DIRECTOR Web Application, change the URL in the browser address bar to .../pdweb-app/copyright.jsp and reload the page.This will display a page containing version information.Troubleshooting missing action buttons There are a number of configuration settings that can influence whether or not an action button is available in a given context.Configuration settings that can influence action availabilityFor SAP GUIApplicable configuration settings for the SAP GUI (in the ascending order of precedence)Setting type Configuration activity Layer SAP transaction Base actionpoolMenu structure and user commands System /EBY/PDVI_VMENCustomer /EBY/PDVI_VMENC Assign function codes to actions System /EBY/PDVI_VUCOCustomer /EBY/PDVI_VUCOCDocumentauthorizationsAction authorization activities System /EBY/PDBO_VACAPer document status Change system settings > Model> Excluded actions perdocument statusSystem /EBY/PDBO_VSTECustomer /EBY/PDBO_VSTECFor documents in workflow Default excluded actions System /EBY/PDWC_VEAC Generally excluded actions Customer /EBY/PDWC_VEACCPer workflow step Initial settings > Workflow >Define steps > Action restrictionCustomer /EBY/PDWC_VSTPCUser exit / BAdI User exits / BAdIs > Platform >Basic > Screen PBO/PAI >EXCLUDE_FUNCTION_CODESCustomerFor Web ApplicationApplicable configuration settings for the Web Application (in the ascending order of precedence)Setting typeConfiguration activity Layer SAP transactionBase action pool Available actions for WebApplicationSystem /EBY/PDWA_CACTCustomer /EBY/PDWA_CACTCDocumentauthorizationsAction authorization activities System /EBY/PDBO_VACACustomer /EBY/PDBO_VACACPer document status Change system settings >Model > Excluded actionsper document statusSystem /EBY/PDBO_VSTECustomer /EBY/PDBO_VSTECFor documents in workflow Default excluded actions System /EBY/PDWC_VEAC Generally excluded actions Customer /EBY/PDWC_VEACCPer workflow step Initial settings > Workflow >Define steps > ActionrestrictionCustomer /EBY/PDWC_VSTPCUser exit / BAdI User exits / BAdIs > Platform> Web Application > SetactionsCustomerSetting typesBase action poolImportant: For the SAP GUI, an action must be in the base action pool in order for any of the other configuration settings in the table to take effect with regard to it.However, for the Web Application, the user exit / BAdI Platform > Web Application > Set actions can enable actions that are not in the base action pool.Document authorizationsIf document authorizations are in use for a given process type, all actions in the base pool are disabled unless the user has the appropriate authorization for their associated activity.In the customer configuration for action authorization activities, you can create new customer action-authorization mappings, redefine existing system mappings, or disable system mappings (by redefining with an empty activity).Per document statusHere, you can disable actions, depending on the current document status of the document.In the customer configuration for action exclusion per document status, you can re-enable actions that were disabled in the system configuration for action exclusion per document status—but not re-enable actions that were disabled elsewhere.For documents in workflowHere, you can generally disable actions for documents in workflow.In the customer configuration for action exclusion during workflows, you can re-enable actions that were disabled in the system configuration for action exclusion during workflows—but not re-enable actions that were disabled elsewhere.Per workflow stepHere, you can disable actions and/or re-enable actions that have been generally disabled for documents in workflow—but not re-enable actions that were disabled elsewhere.User exit / BAdIHere, you can disable actions and/or re-enable actions that were disabled elsewhere. For the Web Application, you can also enable actions that are not part of the base action pool. Troubleshooting the Services for ObjectbuttonIf the Services for Object button is not displayed for a process type in the SAP GUI, make sure that the following settings are entered in transaction SGOSM:Setting Required entryName of service /EBY/ARCHIVESetting Required entryDescription Store business documentQuick info Store business documentClass f.Gen.Service /EBY/CL_PDBO_ARL_SRV_LINKService type Single ServiceIcon ICON_VIEWER_OPTICAL_ARCHIVENext service CREATE_ATTASubservice BlankControl Not checkedCommit required CheckedMake sure that the same content repository ID is assigned to the PROCESS DIRECTOR object type and its corresponding SAP business object type in OAC3.You can configure which SAP business objects a PROCESS DIRECTOR document type connects to so that the documents attachments can be viewed in the SAP document. User exit / BAdI problemsYour user exit / BAdI method implementation does not appear to be working:▪Is the BAdI activated? Is the BAdI filter-dependent? Are the results being overridden by some other BAdI implementation?▪Set a breakpoint at the beginning of the method implementation to see whether it is being called.▪Make sure you are following the general best practice guidelines for user exits / BAdIs.If your user exit / BAdI method implementation is dumping, see Dealing with short dumps. Creating the /EBY/ namespaceIn PROCESS DIRECTOR, the namespace /EBY/ comes with the code transport and normally does not need to be created manually. These instructions are only for reference.If for some reason it is necessary to manually create the namespace, simply perform these steps:1.Directly enter SAP transaction SE03.2.Select Administration > Display/Change Namespaces and create the namespace /EBY/with the values from this table:Field EntryNamespace /EBY/Namespace role CRepair license 05790374410114137903Short text PROCESS DIRECTOR - ReadSoft Ebydos AG - Germany, Frankfurt/M Owner ReadSoft Ebydos AG3.After creating the namespace /EBY/, the system changeability must be set to changeable.Do this in SAP transaction SE03 under Administration > Set System Change Option. Establishing number rangesEach PROCESS DIRECTOR document obtains a specific number that is taken from a number range for that business object.The number range objects for the PROCESS DIRECTOR business document types currently come with the code transport and normally do not need to be created manually. These instructions are only for reference.To maintain number range objects, directly enter SAP transaction SNRO.The number range definition and interval for each business document type must exist and the current number should be 0. If it is not 0, reset it manually. Regenerating menus and toolbarNormally, the GUI status is automatically generated by /EBY/PD. These instructions are only for reference, in case you need to manually regenerate the application's toolbar and menus: 1.In SAP transaction S E80, create a new GUI status program (naming proposal:Z XY_PDVI_GENERATED_CUA) as an empty module pool.2.In SAP transaction SE38, run program /EBY/PDVI_CUA_MAPPER on this empty GUI statusprogram to populate it with generated menus.3.In SAP transaction /EBY/PDVI_VMAI, configure PROCESS DIRECTOR to use this GUIstatus program.。

logiCAD_TrainingWithRTSNTX86_ENG

logiCAD_TrainingWithRTSNTX86_ENG
logi.CAD / logi.RTS
Using and Individually Adjusting
Learning Curve – Complexity
• logi.CAD and logi.DOC are easy to use - the „Windows Style Guide“ is supported • Supported block sets must not be explained - defined standards, such as IEC 61131-3, have been implemented and are well known
per 4096 digital in- and outputs per 256 analog in- and outputs MFLOP : mill. floating point operations per second MIPS : mill. operations per second, medium modification MIPS : mill. operations per second, medium modification time
data structure
structure
Functions according to IEC 61131-3
type converstion numeric
ANY_TO*, TRUNC, BCD_TO_INT, INT_TO_BCD ADD, MOVE, ABS, MUL, SUB, DIV, MOD, EXPT, SQRT, LN, LOG, EXP, SIN, COS, TAN, ASIN, ACOS, ATAN
enumeration
相关主题
  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

Date: November 2002
Slide number: 2
VANTAGE Training
Process Data & Interface Structures
A separate set of Process Data is used for each task :
In: Out: AuxOut: AuxIn:
For External input signals Output of main data or technological relevant external data Output of interim results, diagnostic or internally relevant data Input of configuration values and parameters
This task is used to control sequences within a package. (Cyclically- and Event Triggered)
This task is used for safety checks and initiating of safety actions caused by abnormal conditions. (Cyclically Triggered)
XxxTsk:
In this module the code for this tasks functioBiblioteka ality is situated.
XxxTskOut (Output Interface):
Write external data like signals to the field, or signals to other packages (Fast RDS, RFM, SHM, Messages). Do not pass values to another tasks in this package through the Output Interface module.
This task is used for fast control loops. (Cyclically Triggered)
This task is used for evaluation of the reference values within a package. (Cyclically Triggered)
VANTAGE Training
AppEv AppLp AppRef AppLgc AppSaf AppAnc
Standard Application Program & Task Structure
The task AppEvent is used to read configuration parameters for a package. The data are written independent of the communication mechanism like RDS or Config-Server. (Event Triggered)
The implementation of further substructures is recommended if the data overview will be improved, or the software implementation will be simplified.
Note: The configuration parameters for a task are accessed directly via the Process Data of the AppEv, e.g. PdEv.In.AuxRef.Xyz
Date: November 2002
Slide number: 1
VANTAGE Training
Program & Task Design of Application „XXX“
XxxTskIn
XxxTsk
XxxTskOut
XxxTskIn (Input Interface):
Read external data like signals from the field, or signals from other packages (Fast RDS, RFM, SHM, Messages). Do not pass values from another task in this package through the Input Interface module.
Remarks: In the uppermost level of the above mentioned modules (In, AppXxx and Out), direct access of Process Data Images of another task is allowed. Tsk specifies the function of the task within the application according to standard task structure
Date: November 2002
Slide number: 3
VANTAGE Training
XxxEvIn
x => PdEv.In.AuxRef.x y => PdEv.In.AuxSaf.y
This task is used to do low prior calculations and to write data which are required for the Engineer HMI. Depending on the communication mechanism the values are written to different variables (RDS or resource global variables). (Cyclically Triggered)
相关文档
最新文档