IntelliBus Introduction.v4

合集下载

易灵思(深圳)科技有限公司RISCV-OPAL SOC演示说明说明书

易灵思(深圳)科技有限公司国产化中高端F P G A 领军厂商——加速您的创芯！RISCV-OPAL SOC 演示说明20221017准备工作➢T20F169DevKit或T20F256Devkit 开发板➢Efinity2019.3.272patch10.1以上➢Opal RISC-V SoC•SDK Windows:riscv_sdk_windows-v1.0.zip•IP Core:efx_opal_riscv_soc-v1.0.zip•Opal Risc-V SoC Hardware and Software User Guide ➢USB-UART串口电缆一根SDK Windows 软件开发环境搭建•安装Efinity•安装RISC-V SDK •安装Java JRE•安装SoC 开发工具安装（参照用户手册第一章）软件环境设置（参照用户手册第3章至第六章）•运行Eclipse •设置Eclipse 工作环境•建立和编译软件工程•用OpenOCD 进行Debug➢UART_RXD:GPIO_26➢UART_TXD :GPIO_28➢APB3LED:D9-D10➢GPIO:D3-D8➢演示说明：➢1程序运行串口打印信息➢2打印信息可通过C代码修改➢3程序运行D9D10交替闪烁➢4D3-D8同步闪烁➢5闪烁频率可通过C代码修改➢UART_RXD:GPIO_74➢UART_TXD:GPIO_73➢APB3LED:D5-D6➢演示说明：➢1程序运行串口打印信息➢2打印信息可通过C代码修改➢3程序运行D5D6交替闪烁➢4D5D6闪烁频率可通过C代码修改。

ease4.0

Ease4.01. IntroductionEase4.0 is the latest version of the Ease software, which is designed to provide users with a seamless and efficient user experience. This document serves as a guide to help users understand the new features and improvements brought by Ease4.0.2. Key Features2.1 Enhanced User InterfaceEase4.0 comes with a completely redesigned user interface that is more intuitive and user-friendly. The new interface makes it easier for users to navigate through the software and access various features and functionalities. The layout has been optimized to improve user productivity and reduce the learning curve for new users.2.2 Improved PerformanceOne of the major enhancements in Ease4.0 is improved performance. The software now runs faster and more efficiently, allowing users to perform tasks more quickly. The underlying code has been optimized to reduce resource usage and improve overall system stability. Users can expect a smoother and more responsive experience while using Ease4.0.2.3 Advanced Collaboration ToolsEase4.0 introduces advanced collaboration tools that make it easier for teams to work together. Users can now collaborate on projects in real-time, making it easier to share files, communicate, and track progress. The new collaboration tools allow for seamless teamwork, leading to increased productivity and better project outcomes.2.4 Enhanced SecurityIn Ease4.0, security has been given top priority. The software includes new security features and protocols to ensure that user data is protected and secure. Ease4.0 employs advanced encryption algorithms to safeguard sensitive information and prevent unauthorized access. Users can have peace of mind knowing that their data is safe and secure when using Ease4.0.3. System RequirementsTo use Ease4.0, your system needs to meet the following minimum requirements:•Operating System: Windows 10/ macOS 10.12 or later•Processor: Intel Core i5 or equivalent•RAM: 8GB or more•Storage: 500GB or more•Graphics Card: NVIDIA GeForce GTX 1050 or equivalent•Internet Connection: Required for collaboration featuresIt is recommended to use the latest available hardware and software for the best performance.4. Installation GuideTo install Ease4.0 on your system, follow the steps below:1.Download the Ease4.0 installation package from theofficial website.2.Double-click the downloaded file to start theinstallation process.3.Follow the on-screen instructions to proceed withthe installation.4.Once the installation is complete, launch the Ease4.0application.5. Getting StartedAfter installing Ease4.0, you can follow the steps below to get started:unch Ease4.0 by double-clicking the applicationicon.2.Familiarize yourself with the new user interface andexplore the available features.3.Refer to the user manual or the built-in help systemfor detailed instructions on how to use specific features.4.Start using Ease4.0 to streamline your workflow andenhance your productivity.6. ConclusionEase4.0 is an innovative software that brings a range of new features and improvements to enhance the user experience. With its enhanced user interface, improved performance, advanced collaboration tools, and enhanced security, Ease4.0 offers a seamless and efficient workflow for users. By following the installation guide and getting started steps, users can easily install and start using Ease4.0 to enjoy the benefits it offers.Give Ease4.0 a try and experience a new level of ease and productivity in your daily tasks!。

cef4手册

cef4手册引言概述：CEF（Chromium Embedded Framework）是一种开源的嵌入式Web浏览器控件，它能够将Chromium浏览器的功能嵌入到其他应用程序中。

CEF4是CEF的第四个版本，它提供了更多的功能和改进，为开发人员提供了更多的灵活性和便利性。

本文将详细介绍CEF4的手册内容，以帮助开发人员更好地了解和使用CEF4。

正文内容：1. CEF4的基本概念1.1 CEF4的定义和作用1.2 CEF4的架构和组成1.3 CEF4与Chromium的关系2. CEF4的安装和配置2.1 CEF4的下载和安装2.2 CEF4的配置和初始化2.3 CEF4的版本兼容性说明3. CEF4的常用功能3.1 CEF4的窗口管理3.2 CEF4的页面加载和渲染3.3 CEF4的JavaScript交互3.4 CEF4的资源管理3.5 CEF4的网络请求和响应4. CEF4的高级功能4.1 CEF4的多进程架构4.2 CEF4的插件支持4.3 CEF4的调试和性能优化4.4 CEF4的扩展和定制4.5 CEF4的跨平台支持5. CEF4的应用实例5.1 CEF4在桌面应用中的应用5.2 CEF4在游戏开发中的应用5.3 CEF4在嵌入式系统中的应用5.4 CEF4在移动应用中的应用5.5 CEF4在Web应用中的应用总结：通过本文的介绍，我们了解了CEF4的基本概念、安装和配置方法，以及常用和高级功能。

CEF4作为一种嵌入式Web浏览器控件，具有强大的功能和灵活的定制性，可以广泛应用于桌面应用、游戏开发、嵌入式系统和移动应用等领域。

同时，我们还了解了CEF4在不同应用场景下的应用实例，进一步展示了CEF4的多样性和适用性。

希望本文对开发人员在使用CEF4时能够提供一定的指导和帮助。

e4a中文编程模板 -回复

e4a中文编程模板-回复什么是e4a中文编程模板？e4a中文编程模板是一种以中文编写代码的编程工具。

它基于eclipse集成开发环境（IDE），提供了中文编程语言和中文的编程界面说明，旨在降低编程的学习门槛，使更多的人能够快速上手编写代码和进行软件开发。

为什么选择e4a中文编程模板？许多人想学习编程，但英语不是他们的母语或强项。

在传统的编程学习过程中，英文术语和代码注释往往会成为困扰学习者的障碍。

e4a中文编程模板的出现解决了这个问题，通过使用中文编程语言和中文的编程界面说明，帮助初学者更轻松地理解和使用编程工具。

如何使用e4a中文编程模板？首先，你需要下载并安装eclipse集成开发环境（IDE）。

然后，在eclipse 中安装e4a中文编程模板插件，这样你就可以开始使用中文编程模板了。

一旦安装完成，你可以在eclipse中创建一个新的项目。

选择模板菜单，你将看到一个以中文为主题的代码模板列表。

这些模板涵盖了常见的编程任务和算法，如条件判断、循环、数组、函数等。

选择一个你感兴趣或需要的模板，在编辑器中打开它，你将看到详细的中文注释和代码示例。

这些注释解释了代码的功能和使用方法，帮助你理解和修改它以满足你的需求。

当你完成了对代码的修改，你可以运行代码来测试它的功能。

eclipse提供了一个内置的调试器，让你能够逐步执行代码并观察变量的值和程序的执行路径。

这对于调试和排除错误非常有帮助。

另外，e4a中文编程模板还提供了常见问题的解答和编程指南。

如果你在使用模板的过程中遇到困难，你可以浏览这些资源来找到答案和帮助。

此外，e4a中文编程模板的用户社区也是一个寻求解答和交流的好地方。

最后，不要忘记参考e4a中文编程模板的文档和教程。

通过阅读文档和教程，你将更深入地了解中文编程模板的功能和用法，提升自己的编程技能。

总结：e4a中文编程模板是一种以中文编写代码的编程工具，它提供了中文编程语言和中文的编程界面说明，使初学者能够更轻松地学习和使用编程工具。

HP Server Automation Ultimate 版平台开发人员指南说明书

HP Server Automation Ultimate 版软件版本：10.10平台开发人员指南文档发布日期：2014 年 6 月 30 日软件发布日期：2014 年 6 月 30 日法律声明担保HP 产品和服务的唯一担保已在此类产品和服务随附的明示担保声明中提出。

此处的任何内容均不构成额外担保。

HP不会为此处出现的技术或编辑错误或遗漏承担任何责任。

此处所含信息如有更改，恕不另行通知。

受限权利声明机密计算机软件。

必须拥有 HP 授予的有效许可证，方可拥有、使用或复制本软件。

按照 FAR 12.211 和 12.212，并根据供应商的标准商业许可的规定，商业计算机软件、计算机软件文档与商品技术数据授权给美国政府使用。

Intel® 和 Itanium® 是 Intel Corporation 在美国和其他国家/地区的商标。

Microsoft®、Windows®、Windows® XP 是 Microsoft Corporation 在美国的注册商标。

Oracle 和 Java 是 Oracle 和/或其附属公司的注册商标。

UNIX® 是 The Open Group 的注册商标。

支持请访问 HP 软件联机支持网站：/go/hpsoftwaresupport此网站提供了联系信息，以及有关 HP 软件提供的产品、服务和支持的详细信息。

HP 软件联机支持提供客户自助解决功能。

通过该联机支持，可快速高效地访问用于管理业务的各种交互式技术支持工具。

作为尊贵的支持客户，您可以通过该支持网站获得下列支持：•搜索感兴趣的知识文档•提交并跟踪支持案例和改进请求•下载软件修补程序•管理支持合同•查找 HP 支持联系人•查看有关可用服务的信息•参与其他软件客户的讨论•研究和注册软件培训大多数提供支持的区域都要求您注册为 HP Passport 用户再登录，很多区域还要求用户提供支持合同。

Intellian i3 i4 i4P 产品说明书

CONTENTSINTRODUCTION (1)I NTRODUCTION TO I NTELLIAN I3/I4/I4P (1)F EATURES OF I NTELLIAN I3/I4/I4P (2)B ASIC S YSTEM C ONFIGURATION OF I NTELLIAN I3/I4/I4P (3)INSTALLATION (4)S YSTEM C OMPONENTS (4)T OOLS R EQUIRED FOR I NSTALLATION (7)P LANNING THE INSTALLATION (8)S ELECTION OF I NSTALLATION S ITE (8)I NSTALLATION AND M OUNTING OF ANTENNA (10)I NSTALLING THE ACU (15)C ONNECTING THE S YSTEM C ABLES (17)C ONNECTING THE SYSTEM TO A GPS (20)T ARGET S ATELLITE S ETTING (21)A DJUSTING THE LNB S KEW A NGLE (L INEAR POLARIZATION ONLY) (22)OPERATION INSTRUCTION (24)I NTRODUCTION (24)OPERATION USING THE ACU (25)ACU S OFT K EYS (25)N ORMAL M ODE (25)S ET U P M ODE (30)OPERATION USING PC CONTROLLER PROGRAM (52)I NTRODUCTION (52)P ROGRAM I NITIALING AND S ERIAL P ORT S ETUP (53)M AIN M ENU –U SING D EFAULT D UAL-SAT M ODE (54)S ET S ATELLITE I NFORMATION (55)M AIN M ENU-U SING A DV ANCED T RI-SAT M ODE (56)S ET S ATELLITE I NFORMATION (57)C ONTROLLER MENU (60)TROUBLESHOOTING (65)PREPARATION FOR TRANSPORTATION (67)WARRANTY (68)APPENDIX : TECHNICAL SPECIFICATION (69)I NTELLIAN I4/I4P (69)I NTELLIAN I3 (70)INTRODUCTIONIntroduction to Intellian i3/i4/i4PIntellian i3/i4/i4P is a digital satellite antenna system designed specificallyfor all types of vessels (Anchored or transit) to automatically identify, trackand capture satellite signals from the Digital Video Broadcasting (DVB: the international standard for digital TV transmissions) compatible satellites.Specifically, Intellian i3/i4/i4P has Wide Range Search (WRS) algorithm, which minimizes the search time during initialization, and Dynamic Beam Tilting (DBT) technology, which dynamically shapes the antenna beam to utilize stabilization. Once the satellite is acquired, the antenna DBT continuously measures the heading, pitch, and roll of the vessel by obtaining the satellite signal level around the antenna point, and transmitscommands to the antenna motors to keep the antenna pointed at the satellite at all times. This active stabilization is enhanced by a conical scan tracking function to detect and lock onto the strongest signal, resulting in the clearest reception possible. The i3/i4/i4P has a built-in GPS system which enhances the speed of satellite signals acquisitions.In addition, the i4P provides the embedded auto skew angle control system to maintain the optimal signal strength and increase the quality of satellite receptions in weak satellite single coverage area.Features of Intellian i3/i4/i4PEnjoy satellite broadcasts at seaIntellian i3/i4/i4P is the most modern antenna system that enables you to receive a high quality broadcasting signal at sea, where the atmospheric and environmental condition are very harsh.Fully automatic control systemFully automatic control system allows you to simply turn the power switch on, and have crystal clear, high quality satellite television in motion or at anchor.High quality antennaHigh tech parabolic antenna technology has been adopted for this antenna system, which is optimal for marine conditions. This enables you to receive the optimal signal level even when it is raining or snowing. Fast and efficient search for the satelliteThe WRS (Wide Range Search) algorithm allows for the antenna system to search the satellite within the shortest amount of time and to detect the satellite signal under any position and with any directional movement of the ship.Easy installation and outstanding reliabilityIntellian i3/i4/i4P uses only one RF cable for installation. This makes installation easy. Power, RF and Data signals transfer from the antenna the ACU through this single cable. In addition, Intellian i3/i4/i4P provides highly reliable system through the implementation of a modularized design, and the usage of strictly proven components.Built-in GPSIntellian i3/i4/i4P has imbedded GPS, which allows for the system to upload the GPS data automatically into the system for an even faster and stable system.Built-in automatic skew angle control systemThe automatic skew control system allows Intellian i4P to maintain the optimal skew angle at all times and ensure maximum level of satellite signal level.NMEA GPSPC( Not Supplied)Satellite Receiver (Not Supplied)DC Power on Vessel Satellite Receiver (Not Supplied)Front Rear Hexagonal Bolt5EASpring Washer5EAFlat Washer5EATapping Screw(Φ4x16L)Machine Screw(Φ3x8L)Power Drill Cross-HeadΦ10mm Drill Φ80mm Pencil5mmAntenna Unit15°Obstacleobstacles within 15 degreesabove the antenna. Anyantenna from tracking thesatellite signal (Refer to theWARNINGØ10mm Drillø80mmHole sawRF Cable OptionalAntenna Unit 11mmSpannerWARNING Antenna Unit Support DeckM8 Flat WasherM8 Hex. Bolt13mm SpannerM8 Spring Washer5.38cm (2.1”)IRD 1 (Not Supplied)DC Power Cable NMEA GPSDC Power Cable NMEA GPSDC Power NMEA GPS IRD1IRD 2IRD 3IRD 4Multi switch (Not supplied)Ground (-)NMEA out (+)4-M4X6 Socket Set ScrewTRACKINGTRACKING B:TRACKING B:TRACKING C:DTV101###.# EL###.##E ##.##N1. Press BACK to enter sleep mode.2. Press Back again for exiting sleep mode.SET SAT PAIR ?SET TRIPLE SAT ? SAT A : DTV101 PREVSAT B : DTV119SAT C: DTV110#SAVE ?YES NOVER LOW NID 0x0003HOR LOW 12523 21096 x2HOR LOW NID 0x0003VER HIGH 12598 21096INPUT +VER HIGH NID 0x0003HOR HIGH 12523 21096SAVE ?VERIFY : DVB DECODE VOLTAGE: DISEQC: ONLY 22KHZ PARAM: SCAN OFFx3SET ANT PARAMETER?WRS LEVEL : 0500SATNAME : DTV101SAVE ? 5. Input thex4SAVE ?x4SET LOCAL FREQ? LNB TYPE : UNIVERSALNEXTSET SAT PAIR ?PREVLONGITUDE ###.## Ex1YES NEXTLONGITUDE ###.## EINPUT +SAVE ?4. Input the longitude data.SET SAT PAIR ?SAVE ?x5DO NOT USE DISEQCNEXT 4. Select the DiSEqC MethodSET SAT PAIR ?x6SF-301SSET SAT PAIR ?x7x9 ACU POWER : 27.1 Vx10SET SAT PAIR ?x8 SET REMOCON ? FUNC : CHANGE SATPRESS A REMOTE KEY FUNC :x11x12 LOAD REGION INFO? CONTINENT: EUROPE REGION : ITALYLOAD? LOADING :SET SAT PAIR ?x13Command Button• Baud Rate Setting – To display communication speed.•Connection Status Display – To display communication port Antenna Status Monitoring•Search – Antenna is searching for the selected satellite.•Tracking – Antenna is tracking the selected satellite.•Initialize – Antenna or the ACU is initializing.◆ ♦⌧•Satellite InformationThe name, longitude and confirmation method of the satellite isdisplayed when a satellite is selected in the list box. Push “EditSatellite Information” button to update the information onmodifying the value.•DiSEqCAntenna Status Monitoring•Search – Antenna is searching for the selected satellite.• Tracking – Antenna is tracking the selected satellite.• Initialize – Antenna or the ACU is initializing.◆ ♦•Satellite InformationThe name, longitude and confirmation method of the satellite is displayed when a satellite is selected in the list box. Push “Edit Satellite Information” button to update the information on modifying the value.•DiSEqCWhen the operation method of DiSEqC is selected to “Change3) Click “confirm / yes” button to complete the update.Command Buttons• Load GPS Files – Reads in the various city information from theGPS files.Command Button• Edit Satellite Information – Tothe antenna•Satellite Information – Satellite information consists of frequency,Command Button• Edit Satellite Information – To change frequency information ofthe antenna.• Angle of AntennaTwo kinds of antenna movement is available. One is to move to the target position and the other is to move by certain amount of angle. The current position (angle) of the antenna is displayed as “Current” and to move to the target position, push “Go to target Position” button after keying in desired angle into “Target”. To move to a certain amount of angle only, move antenna to directionbuttons after keying in the desired angle into the AZ and EL in the “Mover Command ButtonsSet Control Parameter–To register parameters values.Set Flags–To set flag setting for WRS Method or Offset Difference.Appendix 71Intellian Technologies, Inc.HQ Dongik Building 7th Flr.,98 Nonhyun-Dong, Gangnam-gu,Seoul 135-010, KoreaTel : +82-2-515-4923Fax: +82-2-545-4903Factory SK Ventium 104-501,522 Dangjeong-Dong, Gunpo-Si,Kyunggi-Do 435-776, KoreaPhone: +82-31-436-1488Fax: +82-31-436-1489R&D Center SK Ventium 104-601,522 Dangjeong-Dong, Gunpo-Si,Kyunggi-Do 435-776, KoreaPhone: +82-31-436-2280Fax: +82-31-436-2284Intellian Technologies USA, Inc.9261 Irvine Blvd.Irvine, CA 92618 USAPhone: +1-949-916-4411Fax: +1-949-271-4183E-Mail:*********************************Homepage : 。

Intellisync 4.0 iii 快速入门指南说明书

7
Quit, insert the Intellisync CD into your CD-ROM drive and click Get Acrobat Reader on the opening screen.
• Online Help. Intellisync includes complete online Help that is accessible through the Help icon in the Intellisync program group or by clicking Help in the program interface dialog boxes.
v
Intellisync 4.0
Introduction to Intellisync
Welcome to the Intellisync Quick Start Guide. This guide is designed to help you install Intellisync, as well as complete your first synchronization. It also includes information on accessing online Help and user guides.
The Intellisync Configure icon accesses the Intellisync Configuration dialog box—the main dialog box used to configure Intellisync operations. The Intellisync Help icon accesses the Intellisync online Help system.

微讯VSC8484数据手册：四通道WAN LAN 背板XAUI到SFP+ KR接收器说明书

VSC8484 Datasheet Quad Channel WAN/LAN/Backplane XAUI to SFP+/KRTransceiverMicrosemi HeadquartersOne Enterprise, Aliso Viejo,CA 92656 USAWithin the USA: +1 (800) 713-4113 Outside the USA: +1 (949) 380-6100 Sales: +1 (949) 380-6136Fax: +1 (949) 215-4996Email: *************************** ©2018 Microsemi, a wholly owned subsidiary of Microchip Technology Inc. All rights reserved. Microsemi and the Microsemi logo are registered trademarks of Microsemi Corporation. All other trademarks and service marks are the property of their respective owners. Microsemi makes no warranty, representation, or guarantee regarding the information contained herein or the suitability of its products and services for any particular purpose, nor does Microsemi assume any liability whatsoever arising out of the application or use of any product or circuit. The products sold hereunder and any other products sold by Microsemi have been subject to limited testing and should not be used in conjunction with mission-critical equipment or applications. Any performance specifications are believed to be reliable but are not verified, and Buyer must conduct and complete all performance and other testing of the products, alone and together with, or installed in, any end-products. Buyer shall not rely on any data and performance specifications or parameters provided by Microsemi. It is the Buyer’s responsibility to independently determine suitability of any products and to test and verify the same. The information provided by Microsemi hereunder is provided “as is, where is” and with all faults, and the entire risk associated with such information is entirely with the Buyer. Microsemi does not grant, explicitly or implicitly, to any party any patent rights, licenses, or any other IP rights, whether with regard to such information itself or anything described by such information. Information provided in this document is proprietary to Microsemi, and Microsemi reserves the right to make any changes to the information in this document or to any products and services at any time without notice.About MicrosemiMicrosemi, a wholly owned subsidiary of Microchip Technology Inc. (Nasdaq: MCHP), offers a comprehensive portfolio of semiconductor and system solutions for aerospace & defense, communications, data center and industrial markets. Products include high-performance and radiation-hardened analog mixed-signal integrated circuits, FPGAs, SoCs and ASICs; power management products; timing and synchronization devices and precise time solutions, setting the world's standard for time; voice processing devices; RF solutions; discrete components; enterprise storage and communication solutions, security technologies and scalable anti-tamper products; Ethernet solutions; Power-over-Ethernet ICs andmidspans; as well as custom design capabilities and services. Learn more at .Contents1Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11.1Revision4.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2Revision4.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3Revision4.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4Revision4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5Revision 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6Revision2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32.1Major Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Functional Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63.1Transmit Operation for XAUI to SFI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.2Receive Operation for SFI to XAUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.3PMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.3.1Supported Data Rates and Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.3.2Rate Auto-Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.3.3Receiver (Rx) Subsection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.3.4Variable Gain Amplifier Input Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.3.5Rx Equalizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.3.6Rx Clock and Data Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.3.7Rx Data Rate Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.3.8Rx Data Path Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.3.9External Capacitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.3.10VScope Input Signal Monitoring Integrated Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.3.11Unity Gain Amplifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.3.12Link Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.3.13Transmitter (Tx) Subsection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.3.14Tx Data Rate Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.3.15Tx Data Path Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3.1610BASE-KR Output Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3.17PMA Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.3.18PMA Linetime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.3.19External Capacitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.3.20Reference Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.3.21Reference Clock Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3.22Clock Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3.23Synchronous Ethernet Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3.24 1.25Gbps Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.3.25Power Down Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.3.26Clock Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.3.27Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.4WAN Interface Sublayer (WIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.4.1Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.4.2Section Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.4.3A1, A2 (Frame Alignment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.4.4Loss of Signal (LOS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.4.5Loss of Optical Carrier (LOPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.4.6Severely Errored Frame (SEF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.4.7Loss of Frame (LOF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.4.9Z0 (Reserved for Section Growth) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.10Scrambling/Descrambling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.11B1 (Section Error Monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.12E1 (Section Orderwire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.13F1 (Section User Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.14DCC-S (Section Data Communication Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.15Reserved, National, and Unused Octets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.16Line Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.4.17B2 (Line Error Monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.4.18K1, K2 (APS Channel and Line Remote Defect Identifier) . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.4.19D4 to D12 (Line Data Communications Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.4.20M0 and M1 (STS-1/N Line Remote Error Indication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.4.21S1 (Synchronization Messaging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.4.22Z1 and Z2 (Reserved for Line Growth) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.4.23E2 (Orderwire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.4.24SPE Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.4.25Bit Designations within Payload Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.4.26Pointer Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.4.27Pointer Adjustment Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.4.28Pointer Increment/Decrement Majority Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.4.29Pointer Interpretation States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.4.30Valid Pointer Definition for Interpreter State Diagram Transitions . . . . . . . . . . . . . . . . . . . . . . 403.4.31Path Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.4.32J1 (Overhead Octet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.4.33B3 (STS Path Error Monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.4.34C2 (STS Path Signal Label and Path Label Mismatch) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.4.35G1 (Remote Path Error Indication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.4.36G1 (Path Status) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.4.37F2 (Path User Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.4.38H4 (Multiframe Indicator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.4.39Z3-Z4 (Reserved for Path Growth) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.4.40N1 (Tandem Connection Maintenance/Path Data Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . 453.4.41Loss of Code Group Delineation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.4.42Reading Statistical Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.4.43Defects and Anomalies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.4.44Interrupt Pins and Interrupt Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.4.45Overhead Serial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493.4.46Transmit Overhead Serial Interface (TOSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493.4.47Receive Overhead Serial Interface (ROSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.4.48Pattern Generator and Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 3.5Physical Coding Sublayer (64B/66B PCS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533.5.1Control Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543.5.2Transmit Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543.5.3Receive Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553.5.4PCS Standard Test Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563.5.5PCS XGMII BIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 3.6Client/Host Interface (XAUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.6.1XGMII Extender Sublayer (PHY XS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.6.2XAUI Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.6.3XAUI Receiver Equalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.6.4XAUI Clock and Data Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.6.5XAUI Code Group Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.6.6XAUI Lane Deskew . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603.6.710B/8B Decoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613.6.88b/10b Encoder and Serializer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613.6.9XAUI Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613.6.10XAUI Transmitter Pre-Emphasis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613.6.12XAUI Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623.710GBASE-KR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623.7.1Auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623.7.2Technology Ability Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653.7.3Transmitted Nonce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.7.4Role of Firmware during Auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.7.5Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.7.6Advertised Ability Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.7.7Link Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.7.8Next Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.7.9Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.7.10Coefficient Update Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693.7.11Status Report Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.7.12Training Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.7.13Role of Hardware and Firmware during Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.7.14Training Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.7.15Coefficient Update and Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.7.16BER Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.7.17Forward Error Correction (FEC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.8Loopback and Bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.8.1Loopback Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.8.2Loopback A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.8.3Loopback B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.8.4Loopback F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.8.5Loopback G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773.8.6Loopback J . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773.8.7Loopback K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773.9Low-Speed Serial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.9.1MDIO Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.9.2Two-Wire Serial (Master) for Loading Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.9.3Two-Wire Serial Slave Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.9.4UART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.9.5JTAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.10Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.10.1Firmware Load Mode, EEPROM Address Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.10.2Default Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.11Loading Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.11.1EEPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.11.2MDIO and Two-Wire Serial Slave Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.12Microcontroller Activity Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.13Interrupt Pending Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.14Multipurpose GPIO Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.15PCS Activity Monitor LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913.16Temperature Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .944.1Global Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944.1.1GPIO Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974.2Channel Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1724.3EDC Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2864.3.1Hardware DC Offset Correction Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2935Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3035.1DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3035.1.1Low-Speed Inputs and Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3035.1.3MDIO Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3045.2AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3045.2.1Receiver Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3045.2.2Transmitter Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3085.2.3Timing and Reference Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3145.2.4Two-Wire Serial (Slave) Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3145.2.5MDIO Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3155.3Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3165.4Stress Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3186Pin Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3206.1Pin Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3206.2Pins by Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3206.2.1General Purpose Inputs and Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3216.2.2JTAG Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3216.2.3Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3226.2.4Ground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3236.2.5Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3236.2.6Receive Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3246.2.7Reference Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3246.2.8Clock Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3256.2.9Test and Mode Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3256.2.10Transmit Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3266.2.11XAUI Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3266.2.12Reserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3297Package Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3307.1Package Drawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3307.2Thermal Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3317.3Moisture Sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3328Design Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3338.1Sync-E in LAN Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3338.2Sync-E in WAN Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 9Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335。

Visual Components 4.4 Warehousing Components 用户指南说

VISUAL COMPONENTS WAREHOUSING COMPONENTSSupport****************************Visual Components Forum Warehousing components referenceVisual Components 4.4 | Version: February 08, 2022This living document introduces warehouse components in the eCatalog, their properties, and simple use cases. It will be updated as more warehouse-related components are added or updated in the eCatalog.NOTE! There are separate tutorials for resources commonly used with warehouse components, such as the ASRS manual introducing cranes. You will go through properties and use cases of the following: ▪ Warehouse Shelf / Floorspace Buffer ▪ Warehouse Process Shelf ▪ Dual Rail Transport Controller ▪ Overhead Cranes ▪ Stack Feeder ▪Pallet FeederContentsWarehouse Shelf / Floorspace Buffer (3)Warehouse Process Shelf (7)Properties (8)Transport Link properties (9)Stack Feeder (12)Pallet Feeder (14)Warehouse Shelf / Floorspace BufferA Warehouse shelf is a Process Modelling (PM) process for storing and buffering products.The warehouse includes multiple presets that can be used to set up the appearance and dimensions of the following:•Pallet Rack•Crane Rack•Light Pallet Rack•Manual Picking Shelf•PickToLightThe Visibility of different visual features can be manually changed from the Options tab. In addition to a component's basic properties, you can change the color of different shelf parts in the Materials tab.Single shelf bay dimensions, Tiers and Bays, and other structural properties can be changed from the component’s basic properties.You can use the ProductOrientation property to define the orientation of the product while on a shelf.It is possible to load and unload the shelf from opposite sides. If resources such as humans are used, they will go to the FlowIn or FlowOutResourceLocation. Cranes or robot arms will not use the location.A small arrow indicates the flow in or out of the location. The location will automatically transform to match the product location on the floor level, and the offset from the shelf will be maintained. Both locations can be modified with the corresponding properties on the shelf.Some statement properties need to be visited to change, for example, the following:•AcceptAllProductTypes•AcceptedProductTypes•AcceptedFlowGroups•BufferFeedMode•BufferNeedMode•ParallelInputLimit•ParallelOutputLimitThe ParallelInputLimit should be set to a value less or equal to the total capacity of the available resources. That way, if more than one shelf is used, the shelves will be filled roughly at the same rate. ParallelOutputLimit is set automatically to match the number of slots but can be manually changed after the shelf has been set up.Examples from the BufferNeedMode while the block component is selected as ZeroPositionNode:•Left is Chaotic•Middle is LinearOrder•Right is ClosestToZeroPositionThe Floorspace buffer component shares the functionality of the Warehouse Shelf component. Instead of the shelf structure, the Floorspace Buffer component utilizes floor space as a buffer. Single-slot dimensions, spacing, and the number of Rows and Columns can be changed from the Component Properties.Warehouse Process ShelfA Warehouse Process Shelf is a Process Modelling (PM) process for curing and processing multiple products simultaneously. Typical applications are curing shelves, test rack processes, and monitoring or limiting a products’ storing time.Components share the same properties with the Warehouse Shelf in the Component Properties tab.A Warehouse process shelf has some additional properties in Statement Properties.ProcessTime can set the processing time for each product placed on the shelf. After this time is consumed, the product is ready to leave the process.If MaximumStoringTime is defined (other than zero) and the product remains on the shelf longer than defined in this property (in addition to possible ProcessTime), the product will become Outdated, and its product type will be changed to OutdatedProductType.If FailedProductPercentage is defined, this value is used as a probability that a product will become defective after processing, and its product type is changed to FailedProductType. Dual Rail Transport ControllerThe Dual Rail Transport Controller is required to control the cranes and serve as thetrack/runway for the cranes. It can control up to two cranes simultaneously. The cranes are connected to the controller using the PnP tool. The cranes are referred to as crane A or B, determined by the interface the crane is connected to.Once a crane is connected, the interface matches the crane’s dimensions, preventing it from exceeding the track. The dimensions of the crane are taken from its bounding box.Dual Rail Transport Controller with two overhead cranes, Crane A on the left and Crane B on the right PropertiesRunwayLength, RunwaySpan, and RunwayHeight: The dimensions of the track SafetyClearance: Determines the minimum separation between the cranes if more than one crane is connected to the same trackCheckLimits: Pause the simulation and display output message if a crane runs out of track (exceeds the track length)Auto Configure Links: If more than one crane is connected to the track, auto-configure will associate each link with crane A or B using the crane closest to the link’s source and destination nodes.When the Dual Rail Transport Controller is assigned to a transport link, some default properties and their values in the LinkDefaults tab in its Component Properties panel are applied to transport link(s). If the values in the LinkDefaults tab are changed the matching values in the transport links will also change, if UseCustomParameters is not enabled in the transport link.Transport Link propertiesPriority: Sets the priority for the link against all available/active transportation tasks. The lower the number, the higher the priorityUse Crane: Define a specific crane for transportation or allow the controller to choose and crane. The controller will, by default, select the nearest available. WaitForNextTransport: If enabled, a crane will wait and remain reserved until the process executions reach the next WaitTransport statement in the process. This process is used in conjunction with the StartTransportIn statement.LoadAssist,UnloadAssist: Controller of a resource that will move into the loading/unloading position of the crane. The process is executed in this position (GraspTime/ReleaseTime). UseCustomParameters: Enable to override default values (defined in controller properties) GraspTime: A time that is taken to load the crane. Excluding handler extend and retract times.ReleaseTime: A time that is taken to unload the crane. Excluding handler extend and retract times.GraspFrom: Selection from which position a product is transported. PickApproach, PlaceApproach: Linear approach direction and distance of the crane when the product is grasped/released.Overhead CranesSeveral process modeling cranes are available in the eCatalog - PM Cranes. Cranes vary in construction and size, but their behaviours and properties are the same.Up to two overhead cranes can be connected to a Dual Rail Transport ControllerCranes have a set of default properties (like RailWidth) to define the size and robustness of different parts of the crane.SlingLength can be used to define additional distance from the crane hook to the product and visualize lifting slings.AutoHoming::Delay: Defines the time once the cranehas been without tasks to move to a home positiondefined by the following properties. Use zero todisable AutoHoming.AutoHoming::BridgePosition: Bridge (X) homepositionAutoHoming::TrolleyPosition: Trolley (Y) home positionAutoHoming::HoistPosition: Hoist (Z) home positionAutoHoming::Read Current Joint Values: Read the current position and set the above properties.The Speeds tab properties set the kinematic parameters for each joint. The deceleration will be equivalent to the acceleration.Stack FeederA Stack feeder is a component for creating stacks of product instances in Process Modelling. The bottom product in a stack may be different from the rest of the stack. The component uses a Process Modelling routine controlled by Component Properties.A Stack feeder is a process that can be connected to a conveyor. It shares default properties with all Process Modelling flow components.Properties in the Stack tab control the StackFeeder routine.In this routine, a Joint modeled to a component is moved up while Stack::Count monitors the number of products created. Created products are attached, creating a hierarchical stack. The distance between products in the stack is defined with the Stack::Step property. The Last product in the stack is created separately, and the distance to the stack is defined with separate Stack::PalletStep property. This allows you to select a different product type as the bottom part of the stack.After a stack is created, it is transported out from the process and is delayed the amount of time in Stack::Delay.The Stack feeder creates stacksusing a pallet as its default producttype. Stacks are created usingCreate statements and the producttype can then be modified manuallyonce a new product type is selectedin the product type editor.Pallet FeederA Pallet feeder is a component for creating stacks of product instances in Process Modelling. This component uses a Process Modelling routine controlled by Component Properties, and routine execution is partly controlled by Python Statements.StackFeeder is a process that can be connected to a conveyor. It shares default properties with all Process Modelling flow components.The feeder has a set of default properties (like ProductLength) to define the size and visibility of different parts of the feeder.Properties in the Stack tab control the StackFeeder routine.In the routine, a Joint modeled to a component is moved up while Stack::Count controls the number of products created. The Stack::Step property defines the distance between products in a stack.After a stack is created, products are transported out from the process one by one with Stack::Interval, and then the whole stack is transported out, Stack::Delay controls the amount of time the products are delayed.The Stack feeder creates stacks using a pallet as its default product type. Stacks are created using Create statements and the product type can then be modified manually once a new product type is selected in the product type editor.。

Intel 主动管理技术（主动式管理技术） v4.0 管理员指南说明书

Intel® Active Management Technology（主动式管理技术）v4.0管理员指南概览产品概览操作模式设置和配置概览预配置方法菜单及默认设置MEBx 设置概览ME 配置菜单AMT 配置菜单MEBx 默认设置设置和配置方法概览配置服务MEBx 界面（企业模式）MEBx 界面（中小企业模式）系统部署操作系统驱动程序管理Intel AMT Web GUIAMT 重定向 (SOL/IDE-R) AMT 重定向概览故障排除故障排除如果您购买的是 Dell™ n 系列计算机，则本文中关于 Microsoft® Windows®操作系统的任意参考内容均不适用。

本说明文件中的信息如有更改，恕不另行通知。

未经 Dell Inc. 书面许可，严禁以任何形式复制这些材料。

本文中使用的商标：Dell、Latitude和DELL徽标是 Dell Inc. 的商标；Intel 是 Intel Corporation 在美国及其他国家和地区的商标或注册商标；Microsoft和Windows是 Microsoft Corporation 在美国及/或其他国家和地区的商标或注册商标。

本说明文件中述及的其它商标和商品名称是指拥有相应标记和名称的公司或其制造的产品。

Dell Inc. 对其它公司的商标和产品名称不拥有任何所有权。

2008 年 8 月修订版 A00概览Intel® 主动管理技术 (Intel AMT) 使公司可通过以下方法轻松实现对其联网计算机的管理：搜索网络上的计算机资产（无论计算机处于打开或关闭状态）– Intel AMT 使用存储在非易失性系统内存中的信息来访问计算机。

即使计算机处于关闭状态，也能对其进行访问（也称为带外访问或 OOB 访问）。

假如操作系统发生故障，也可远程修复系统 — 在软件或操作系统发生故障的情况下，可使用 Intel AMT 远程访问计算机以完成修复。

Visual Components 4.0 用户手册说明书

© 2015 Visual Components Oy | PAGE 1 OF 15 |VISUAL COMPONENTS [ LAYOUT CONFIGURATION ]Works Library - Basics of Task Cre ationVisual Components 4.0 | Version: 9.2.2017The Works library can be used to simulate simple and complex processes during a simulation. A process contains tasks, which can be self-contained or require the use of resources, machines, inputs and outputs, and other processes.In this tutorial you will learn the basics of creating and simulating tasks with components in the Works library.This will involve:▪Creating products and forming stacks▪Teaching locations for storing products and filling containers▪Transporting products in and out of processes▪Using robot resources to pick and place parts Support ****************************CommunityGetting StartedA Works Process component is used to create and execute tasks during a simulation. A WorksTask Controller is used to manage the execution of those tasks. As a result, a layout with aWorks Process component requires at least one Works Task Controller. ArrayBy default, a Works Process component executes tasks in sequence. This process can includeconditional tasks, calls to global processes in the Works Task Controller, and be executedmultiple times during a simulation. The work order or tasks performed by a Works Processcomponent can be found in its Task properties group.| PAGE 2 OF 15 |GETTING STARTEdGETTING STARTEd | PAGE 3 OF 15 |You can add, edit, delete and replace tasks in a Works Process component by using its Default properties group.NOTE! For advanced users, you can access and edit the Task note of a Works Process component. We recommend learning and understanding the syntax of tasks before directlyediting a Task note.| PAGE 4 OF 15 |TASk - CREATETask - Create A Create task allows you to create a list of components found in the 3D world. A component needs to be referenced by name. At the time of creation, the new component can be assigned a specific ProdID. Otherwise, the default ProdID of a created component is its name.1. Press CTRL+N to clear the 3D world.2. Open the Task Creation - Start layout for this tutorial.3. In the Cell Graph panel, under the Works category, click WorksProcess to select that component in the 3D world.4. In the Component Properties panel, Default tab, set Task to Create and ListOfCompNames to Euro Pallet , and then click CreateTask .TIP! Use the Cell Graph panel to quickly reference the names of components in the current layout. The InsertNewAfterLine property can be used to quickly verify task creation was successful and the position of the new task in the process.5. Run the simulation to verify a pallet is created at the default frame location in the Works Process component, and then stop the simulation.6. Select the new pallet . Notice it is attached/contained in the Works Process component.7. In the Component Properties panel, verify the ProdID of the pallet is its name and notice it has a stamped TAT_property to indicate its turnaround time in the process.Task - Create PatternA Create Pattern task allows you to create a pattern of components by using a template. Thetemplate can be any component found in the 3D world. AmountX, Y and Z properties definethe size of the pattern along the XYZ axes. StepX,Y and Z properties define the spacing of thepattern along the XYZ axes. StartRange and EndRange properties define what elements in thepattern are generated by the task.1. Reset the simulation, and then select the WorksProcess component.2. In the Component Properties panel, Default tab, set Task to CreatePattern,SingleCompName to CarTyre, AmountX and Y to 1, AmountZ to 5 and StepZ to 160,and then click CreateTask. Notice that you are inserting a new task after you create apallet in the process.3. Run the simulation to verify a stack of tires are created, and then stop the simulation.Notice that the location of the first tire in the pattern is inside the pallet. You can fixthis by teaching the Works Process component a default location for the tire.TASk - CREATE PATTERN| PAGE 5 OF 15 || PAGE 6 OF 15 |TEACh LOCATIONSTeach Locations Locations allow you to define where you want components to be placed, stored and moved to in a Works Process component. For example, you can teach the location for the first item in a pattern.1. Reset the simulation, and then in the Component Properties panel, Default tab, set EndRange to 1, and then click ReplaceTask . This will replace the task listed in the InsertNewAfterLine property, which in this case is the CreatePattern task for the tires. Now, the pattern will only create one item, thereby making it easier to teach the location of the tire to the Works Process.2. Run the simulation, verify there is one tire inside the pallet, and then stop the simulation.3. Select the CarTyre inside the pallet, and then in the Component Properties panel, set the Z-axis coordinate to 844. This offsets the tire to be on top of the pallet.4. In the 3D world, select the WorksProcess , and then in the Component Properties panel, Default tab, click TeachLocation . The WorksProcess only checked the locations of components attached to it because the OnlyContainedComponents check box is enabled. This is why there are saved locations for a CarTyre and Euro Pallet.NOTE! A location is a key-value pair. The key is referring to either the name or ProdID of a component. The value is the location of a component based in the Works Process coordinatesystem. ProdID values can be used to teach different locations for the same type of component.REMOVE LOCATIONS | PAGE 7 OF 15 |Remove LocationsIn a Works Process component, you have the option of removing one or all saved locations.1. In the Component Properties panel, set Selection to Euro Pallet , and then click RemoveSelected .2. Set EndRange to 9999, and then click ReplaceTask . Now, all tires in the CreatePatterntask will be created during a simulation.3. Run the simulation, verify a stack of tires is on top of a pallet, and then reset thesimulation.Task - MergeA Merge task allows you to attach components contained by a Works Process component toone another. This is helpful if you need groups of components to move together, for examplea pallet with a stack of parts. The attachment of components is done by using ProdID values.1. In the Component Properties panel, Default tab, set Task to Merge, ParentProdID toEuro Pallet, and then click CreateTask. This will attach everything, for example thetires, contained in the Works Process component to the pallet. Array2. Run the simulation, select one of the tires in the stack, and then stop the simulation.With the PnP command enabled, verify the selected tire is attached to the pallet, andthen reset the simulation.| PAGE 8 OF 15 |TASk - MERGETASk - TRANSPORT OUT | PAGE 9 OF 15 |Task - Transport OutA Transport Out task allows you to move components out of a Works Process component via its path. You can transfer out all contained components or filter them by ProdID.1. In the 3D world, select the WorksProcess .2. In the Component Properties panel, Default tab, set Task to TransportOut ,ListOfProdID to Euro Pallet , clear the All check box, and then click CreateTask . Since the preceding task merges tires with the pallet, transporting out the pallet will also move its child components.3. Run the simulation, verify the pallet and tires move onto a conveyor, and then reset the simulation.NOTE! A new stack of tires and pallet are created in the Works Process component because its process will reset and run again after completing the last task. The number of times aprocess is executed is controlled by the Task::RunTaskTimes property.Task - Transport InA Transport In task allows you to move components into a Works Process component via itspath and stop them. You can transfer in any component or filter them by ProdID. Generally,you transport in components to process them. Otherwise, a Works Process component willact like a conveyor, transfer in and out components via its path without processing them.1. In the Cell Graph panel, under the Works category, click WorksProcess #2 to selectthat component in the 3D world.2. In the Component Properties panel, Default tab, set Task to TransportIn, and thenclick CreateTask.3. Run the simulation, verify a pallet of tires stops inside WorksProcess #2, and thenreset the simulation.| PAGE 10 OF 15 |TASk - TRANSPORT INTask - SplitA Split task allows you to detach components contained by a Works Process component fromone another. This is helpful if you need to ungroup stacks of components in order to pick andplace them separately. The detachment of components is done by using ProdID values.1. In the Component Properties panel, Default tab, set Task to Split, ListOfProdID toCarTyre, and then click CreateTask. This will detach the tires from the pallet, therebythe tires will be attached to Works Process #2.2. Run the simulation, wait until a pallet stops at WorksProcess #2, and then stop thesimulation.3. Select one of the tires in the stack at WorksProcess #2, and with the PnP commandenabled, verify the selected tire is not attached to the pallet, and then reset thesimulation.TASk - SPLIT| PAGE 11 OF 15 || PAGE 12 OF 15 |TASk - FEEdTask - FeedA Feed task allows you to signal resources that a list of components contained by a Works Process component are available and can be picked up and placed at other Works Process components. A TaskName is used to uniquely identify and assign a Feed task to a resource. ToolName and TCPName are used to identify a tool component and tool frame that a resource should use to the perform the task. You can feed all contained components or filter them by ProdID.The completion of a Feed task is when all of its fed components have been picked up by a resource. In order for a resource to pick up a component, there must be a need for the component at another Works Process component.1. In the 3D world, select WorksProcess #2.2. In the Component Properties panel, Default tab, set Task to Feed , TaskName to Pick1, clear the All check box, and then click CreateTask . This will feed the tires not the pallet.3. In the 3D world, plug the robot to the Works Robot Controller . The controller is used to assign tasks to a connected robot used as a resource. In addition, the controller automates the program of a connected robot to complete assigned tasks.4. Select the WorksRobotController , and then in the Component Properties panel, Default tab, set Tasklist to Pick1.5. Run the simulation, verify no more pallets are transported into WorksProcess #2because its Feed task is not completed, and then reset the simulation.Task - NeedA Need task allows you to request a list of components be placed in a Works Process component. The request is done by using ProdID values.The setup of a Need task is rather simple, but requires other Works Process components tofeed the needed products. That is, a resource must know from where the needed componentscan come from in order to deliver them.The completion of a Need task is when all of the listed components by ProdID have beenplaced by a resource.1. In the Cell Graph panel, under the Works category, click WorksProcess #3 to selectthat component in the 3D world.2. In the Component Properties panel, Default tab, set Task to Need, ListOfProdID toCarTyre, and then click CreateTask.3. Set Task to TransportOut, and then click CreateTask. This means a tire will betransferred out as soon as it is received at WorksProcess #3.NOTE! For a TransportOut task, the All property overrides the ListOfProdID property.4. Run the simulation, verify the robot picks and places tires from WorksProcess #2 toWorksProcess #3, and then reset the simulation.TASk - NEEd| PAGE 13 OF 15 |Task - Need PatternA Need Pattern task allows you to request a pattern of components be placed in a WorksProcess component. Similar to a Need task, the needed component is identified by its ProdIDand must come from other Works Process components.1. In the Component Properties panel, Default tab, set InsertNewAfterLine to the firsttask in the process, which requests the need of a tire.2. Set Task to NeedPattern, SingleProdID to CarTyre, AmountX and Y to 1, AmountZ to5, StepZ to 160, and then click ReplaceTask. Now, there is a need for a stack of 5tires.3. In the Component Properties panel, Default tab, set Task to Merge, ParentProdID toCarTyre, clear ListOfProdID, and then click CreateTask. This will attach the stack oftires to one another, thereby allowing the stack to move as a group.| PAGE 14 OF 15 |TASk - NEEd PATTERNREVIEw | PAGE 15 OF 15 | 4. In the 3D world, select WorksProcess #2, and then add a TransportOut task formoving out empty pallets.5. Run the simulation, verify the robot picks and places a stack of tires, and then reset the simulation.ReviewIn this tutorial you learned how to simulate simple processes using components in the Works library. For example, you created processes for depalletizing products using a robot. You understand the basics of creating and editing tasks in processes. This will help you in other Works library tutorials covering more complex processes and tasks. As a guide, we recommendyou now learn more about ProdID filtering and serial task lists for robots.。

Intel 64 和 IA-32 架构软件开发者手册（第二卷）说明书

Intel® 64 and IA-32 ArchitecturesSoftware Developer’s ManualVolume 2 (2A, 2B, 2C & 2D):Instruction Set Reference, A-ZNOTE:The Intel 64 and IA-32 Architectures Software Developer's Manual consists of four volumes: Basic Architecture, Order Number 253665; Instruction Set Reference A-Z, Order Number 325383; System Programming Guide, Order Number 325384; Model-Specific Registers, Order Number 335592. Refer to all four volumes when evaluating your design needs.Order Number: 325383-071USOctober 2019Intel technologies features and benefits depend on system configuration and may require enabled hardware, software, or service activation. Learn more at , or from the OEM or retailer.No computer system can be absolutely secure. Intel does not assume any liability for lost or stolen data or systems or any damages resulting from such losses.You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein.No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document.The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifica-tions. Current characterized errata are available on request.This document contains information on products, services and/or processes in development. All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest Intel product specifications and roadmapsCopies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or by visiting /design/literature.htm.Intel, the Intel logo, Intel Atom, Intel Core, Intel SpeedStep, MMX, Pentium, VTune, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries.*Other names and brands may be claimed as the property of others.Copyright © 1997-2019, Intel Corporation. All Rights Reserved.CONTENTSPAGECHAPTER 1ABOUT THIS MANUAL1.1INTEL® 64 AND IA-32 PROCESSORS COVERED IN THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.2OVERVIEW OF VOLUME 2A, 2B, 2C AND 2D: INSTRUCTION SET REFERENCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 1.3NOTATIONAL CONVENTIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 1.3.1Bit and Byte Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5 1.3.2Reserved Bits and Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5 1.3.3Instruction Operands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5 1.3.4Hexadecimal and Binary Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6 1.3.5Segmented Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6 1.3.6Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6 1.3.7 A New Syntax for CPUID, CR, and MSR Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7 1.4RELATED LITERATURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7CHAPTER 2INSTRUCTION FORMAT2.1INSTRUCTION FORMAT FOR PROTECTED MODE, REAL-ADDRESS MODE, AND VIRTUAL-8086 MODE. . . . . . . . . . . . . . . . . . . . 2-1 2.1.1Instruction Prefixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1 2.1.2Opcodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3 2.1.3ModR/M and SIB Bytes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3 2.1.4Displacement and Immediate Bytes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3 2.1.5Addressing-Mode Encoding of ModR/M and SIB Bytes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4 2.2IA-32E MODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 2.2.1REX Prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8 2.2.1.1Encoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8 2.2.1.2More on REX Prefix Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8 2.2.1.3Displacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 2.2.1.4Direct Memory-Offset MOVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 2.2.1.5Immediates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 2.2.1.6RIP-Relative Addressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 2.2.1.7Default 64-Bit Operand Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 2.2.2Additional Encodings for Control and Debug Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 2.3INTEL® ADVANCED VECTOR EXTENSIONS (INTEL® AVX). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 2.3.1Instruction Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 2.3.2VEX and the LOCK prefix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 2.3.3VEX and the 66H, F2H, and F3H prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 2.3.4VEX and the REX prefix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 2.3.5The VEX Prefix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 2.3.5.1VEX Byte 0, bits[7:0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 2.3.5.2VEX Byte 1, bit [7] - ‘R’. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 2.3.5.33-byte VEX byte 1, bit[6] - ‘X’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 2.3.5.43-byte VEX byte 1, bit[5] - ‘B’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 2.3.5.53-byte VEX byte 2, bit[7] - ‘W’. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 2.3.5.62-byte VEX Byte 1, bits[6:3] and 3-byte VEX Byte 2, bits [6:3]- ‘vvvv’ the Source or Dest Register Specifier. . . . . 2-16 2.3.6Instruction Operand Encoding and VEX.vvvv, ModR/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17 2.3.6.13-byte VEX byte 1, bits[4:0] - “m-mmmm”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 2.3.6.22-byte VEX byte 1, bit[2], and 3-byte VEX byte 2, bit [2]- “L” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 2.3.6.32-byte VEX byte 1, bits[1:0], and 3-byte VEX byte 2, bits [1:0]- “pp”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 2.3.7The Opcode Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2.3.8The MODRM, SIB, and Displacement Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2.3.9The Third Source Operand (Immediate Byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2.3.10AVX Instructions and the Upper 128-bits of YMM registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2.3.10.1Vector Length Transition and Programming Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Vol. 2A iiiCONTENTSiv Vol. 2A PAGE2.3.11AVX Instruction Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20 2.3.12Vector SIB (VSIB) Memory Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20 2.3.12.164-bit Mode VSIB Memory Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21 2.4AVX AND SSE INSTRUCTION EXCEPTION SPECIFICATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21 2.4.1Exceptions Type 1 (Aligned memory reference) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26 2.4.2Exceptions Type 2 (>=16 Byte Memory Reference, Unaligned). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27 2.4.3Exceptions Type 3 (<16 Byte memory argument) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28 2.4.4Exceptions Type 4 (>=16 Byte mem arg no alignment, no floating-point exceptions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29 2.4.5Exceptions Type 5 (<16 Byte mem arg and no FP exceptions). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30 2.4.6Exceptions Type 6 (VEX-Encoded Instructions Without Legacy SSE Analogues) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31 2.4.7Exceptions Type 7 (No FP exceptions, no memory arg) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32 2.4.8Exceptions Type 8 (AVX and no memory argument) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32 2.4.9Exceptions Type 11 (VEX-only, mem arg no AC, floating-point exceptions). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33 2.4.10Exceptions Type 12 (VEX-only, VSIB mem arg, no AC, no floating-point exceptions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34 2.5VEX ENCODING SUPPORT FOR GPR INSTRUCTIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34 2.5.1Exceptions Type 13 (VEX-Encoded GPR Instructions). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35 2.6INTEL® AVX-512 ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35 2.6.1Instruction Format and EVEX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36 2.6.2Register Specifier Encoding and EVEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38 2.6.3Opmask Register Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38 2.6.4Masking Support in EVEX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39 2.6.5Compressed Displacement (disp8*N) Support in EVEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39 2.6.6EVEX Encoding of Broadcast/Rounding/SAE Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41 2.6.7Embedded Broadcast Support in EVEX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41 2.6.8Static Rounding Support in EVEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41 2.6.9SAE Support in EVEX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41 2.6.10Vector Length Orthogonality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41 2.6.11#UD Equations for EVEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42 2.6.11.1State Dependent #UD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42 2.6.11.2Opcode Independent #UD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42 2.6.11.3Opcode Dependent #UD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43 2.6.12Device Not Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44 2.6.13Scalar Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44 2.7EXCEPTION CLASSIFICATIONS OF EVEX-ENCODED INSTRUCTIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44 2.7.1Exceptions Type E1 and E1NF of EVEX-Encoded Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47 2.7.2Exceptions Type E2 of EVEX-Encoded Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49 2.7.3Exceptions Type E3 and E3NF of EVEX-Encoded Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50 2.7.4Exceptions Type E4 and E4NF of EVEX-Encoded Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52 2.7.5Exceptions Type E5 and E5NF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54 2.7.6Exceptions Type E6 and E6NF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56 2.7.7Exceptions Type E7NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58 2.7.8Exceptions Type E9 and E9NF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59 2.7.9Exceptions Type E10 and E10NF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61 2.7.10Exception Type E11 (EVEX-only, mem arg no AC, floating-point exceptions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63 2.7.11Exception Type E12 and E12NP (VSIB mem arg, no AC, no floating-point exceptions). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64 2.8EXCEPTION CLASSIFICATIONS OF OPMASK INSTRUCTIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66CHAPTER 3INSTRUCTION SET REFERENCE, A-L3.1INTERPRETING THE INSTRUCTION REFERENCE PAGES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 3.1.1Instruction Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1 3.1.1.1Opcode Column in the Instruction Summary Table (Instructions without VEX Prefix). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2 3.1.1.2Opcode Column in the Instruction Summary Table (Instructions with VEX prefix). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3 3.1.1.3Instruction Column in the Opcode Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5 3.1.1.4Operand Encoding Column in the Instruction Summary Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8 3.1.1.564/32-bit Mode Column in the Instruction Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8 3.1.1.6CPUID Support Column in the Instruction Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9 3.1.1.7Description Column in the Instruction Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9 3.1.1.8Description Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9CONTENTSPAGE 3.1.1.9Operation Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-93.1.1.10Intel® C/C++ Compiler Intrinsics Equivalents Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12 3.1.1.11Flags Affected Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14 3.1.1.12FPU Flags Affected Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14 3.1.1.13Protected Mode Exceptions Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14 3.1.1.14Real-Address Mode Exceptions Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15 3.1.1.15Virtual-8086 Mode Exceptions Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15 3.1.1.16Floating-Point Exceptions Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16 3.1.1.17SIMD Floating-Point Exceptions Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16 3.1.1.18Compatibility Mode Exceptions Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16 3.1.1.1964-Bit Mode Exceptions Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16 3.2INSTRUCTIONS (A-L). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17AAA—ASCII Adjust After Addition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18AAD—ASCII Adjust AX Before Division . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20AAM—ASCII Adjust AX After Multiply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22AAS—ASCII Adjust AL After Subtraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24ADC—Add with Carry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26ADCX — Unsigned Integer Addition of Two Operands with Carry Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29ADD—Add. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31ADDPD—Add Packed Double-Precision Floating-Point Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33ADDPS—Add Packed Single-Precision Floating-Point Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36ADDSD—Add Scalar Double-Precision Floating-Point Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39ADDSS—Add Scalar Single-Precision Floating-Point Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41ADDSUBPD—Packed Double-FP Add/Subtract. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43ADDSUBPS—Packed Single-FP Add/Subtract. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45ADOX — Unsigned Integer Addition of Two Operands with Overflow Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48AESDEC—Perform One Round of an AES Decryption Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50AESDECLAST—Perform Last Round of an AES Decryption Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52AESENC—Perform One Round of an AES Encryption Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54AESENCLAST—Perform Last Round of an AES Encryption Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56AESIMC—Perform the AES InvMixColumn Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58AESKEYGENASSIST—AES Round Key Generation Assist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59AND—Logical AND. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61ANDN — Logical AND NOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63ANDPD—Bitwise Logical AND of Packed Double Precision Floating-Point Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64ANDPS—Bitwise Logical AND of Packed Single Precision Floating-Point Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67ANDNPD—Bitwise Logical AND NOT of Packed Double Precision Floating-Point Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70ANDNPS—Bitwise Logical AND NOT of Packed Single Precision Floating-Point Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73ARPL—Adjust RPL Field of Segment Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76BEXTR — Bit Field Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78BLENDPD — Blend Packed Double Precision Floating-Point Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79BLENDPS — Blend Packed Single Precision Floating-Point Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81BLENDVPD — Variable Blend Packed Double Precision Floating-Point Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83BLENDVPS — Variable Blend Packed Single Precision Floating-Point Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85BLSI — Extract Lowest Set Isolated Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88BLSMSK — Get Mask Up to Lowest Set Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-89BLSR — Reset Lowest Set Bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90BNDCL—Check Lower Bound. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91BNDCU/BNDCN—Check Upper Bound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93BNDLDX—Load Extended Bounds Using Address Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95BNDMK—Make Bounds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98BNDMOV—Move Bounds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-100BNDSTX—Store Extended Bounds Using Address Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-103BOUND—Check Array Index Against Bounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-106BSF—Bit Scan Forward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-108BSR—Bit Scan Reverse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-110BSWAP—Byte Swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-112BT—Bit Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-113BTC—Bit Test and Complement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-115Vol. 2A v。

idea中activiti bpmn visualizer -回复

idea中activiti bpmn visualizer -回复在编写Activiti中的BPMN可视化工具之前，让我们首先了解一下BPMN 是什么以及为什么可视化工具在业务流程管理中的重要性。

BPMN（Business Process Model and Notation）是一种用于描述业务流程的图形化标准。

它基于流程建模图（Process Flow Diagram，PFD）和流程编排图（Business Process Execution Language，BPEL），并提供了一种可读性强且易于理解的方式来定义业务流程。

BPMN图形化标准允许业务分析师和技术人员之间进行沟通，并帮助组织更好地理解和管理其业务流程。

在一个日益复杂的业务环境中，可视化工具在业务流程管理中具有重要的作用。

以下是一步一步回答您关于Activiti BPMN可视化工具的问题。

第一步：需求分析使用Activiti BPMN可视化工具的第一步是进行需求分析。

这涉及与业务用户、流程所有者和其他相关利益相关者进行深入访谈，以了解他们的需求和期望。

例如，他们可能希望以图形方式表示业务流程、查看流程的执行状态、跟踪流程实例等。

第二步：设计可视化界面在需求分析后，下一步是设计Activiti BPMN可视化工具的用户界面。

这可能包括主要的流程可视化面板、流程元素和连接的图形表示、状态跟踪面板、流程执行历史记录面板等。

在设计过程中，要确保工具的易用性和用户友好性，使用户能够轻松地导航和查看复杂的业务流程。

第三步：数据模型和接口设计设计用户界面后，接下来需要设计数据模型和接口。

这可能包括定义流程元素和连接的属性、流程实例数据、流程执行历史记录等。

此外，还需要定义与Activiti引擎进行交互的接口，以获取流程定义和实例的数据，并向引擎发送命令（如启动和暂停流程实例）。

第四步：开发可视化工具完成前面的分析和设计后，接下来是实际的开发工作。

intellisense 格式

intellisense 格式Intellisense: Enhancing Programming ProductivityIn the fast-paced world of software development, programmers face numerous challenges that can impede their productivity. One of these challenges is the time-consuming task of writing code without any assistance or guidance. However, with the advent of advanced programming tools, developers have been introduced to a revolutionary feature known as Intellisense. This article will explore the concept of Intellisense, its benefits, and its impact on programming productivity.Intellisense is an intelligent code completion feature found in many modern Integrated Development Environments (IDEs). It assists programmers by providing context-aware suggestions and auto-completion options as they write code. Through analyzing the codebase and the developer's input, Intellisense predicts and suggests the most likely code elements, variables, and syntax based on the context. It not only saves developers time but also reduces the chances of errors and enhances code quality.One of the key advantages of Intellisense is its ability to speed up the coding process. With its real-time suggestions, developers no longer need to memorize every function, method, or variable available in a programming language or framework. Instead, they can rely on Intellisense to provide accurate suggestions and complete their code faster. This feature is particularly useful for complex programming languages like C++ or frameworks like Angular, where manual code completion can be challenging and error-prone.Intellisense also acts as a powerful learning tool for developers. By providing suggestions for code fragments, it helps programmers understand programming language constructs and discover new functionalities. Beginners can benefit from Intellisense's guidance as it reduces the learning curve and enhances their understanding of syntax and libraries. Similarly, experienced developers can leverage Intellisense to explore available options within vast programming frameworks, enabling them to write efficient and optimized code.Another significant advantage of Intellisense is its error prevention capability. By suggesting valid code elements, Intellisense minimizes the chances of typographical errors and syntax mistakes. It warns developers about potential mistakes, such as using variables before they are declared, or invoking incorrect function parameters. As a result, developers can catch errors early in the development process, ultimately leading to fewer bugs and smoother code reviews.Intellisense also promotes better code consistency and adherence to coding standards. As it suggests commonly used code elements, developers are more likely to follow consistent naming conventions, use appropriate function calls, and apply best practices. This consistency improves code readability and maintainability, especially in large development teams or projects with multiple contributors. Furthermore, Intellisense can help enforce coding standards through customizable rules and guidelines, ensuring that the codebase remains clean and coherent.In addition to its benefits for individual developers, Intellisense can also enhance collaboration between team members. With the aid of this feature, developers can easily understand and utilize code modules created by their colleagues, even if they are unfamiliar with them. Intellisense suggests the available functions, their parameters, and the expected return values, enabling smooth integration and cooperation. This collaborative aspect saves time and effort by eliminating the need for extensive documentation or constant communication between team members.In conclusion, Intellisense is a powerful productivity tool that revolutionizes the coding experience for programmers. Its code completion and suggestion features significantly improve development speed, reduce errors, facilitate learning, and enhance collaboration. By leveraging Intellisense, developers can focus more on problem-solving and innovation, instead of getting tangled in syntax and manual code completion. As software development continues to evolve, Intellisense remains indispensable in empowering programmers and fostering efficient and high-quality code production.。

微软NGO eOpen软件安装指南说明书

1 ©2008 Microsoft Corporation. All rights reserved. /NGOeOpen Software Installation GuideWhat is eOpen?eOpen is an online tool that allows participants of the Microsoft Software Donation programme to manage theirsoftware licences, including:Accessing your Volume Licence Product Keys to install your softwareUpdating contact information Downloading software included in your software licence agreementInstallation InstructionsThese instructions are provided to grantees of the Microsoft Software Donation programme to help you to register, activate, and begin using your new software quickly and easily.When your software grant is approved, you will receive a notification letter from Microsoft via e-mail. After your software arrives, follow the steps outlined in the following section (this information is also in your notification letter). These instructions guide you through the registration process and enable you to access your Volume Licence product keys needed to activate your software (if required).1.Go to the eOpen Web site.In the upper right corner of the page, select your language from the Choose Language drop-down list (as needed).2.Click Sign In.3.Enter your Windows Live ID e-mail address and password in the designated spaces and click Sign In.Note: If you have a Hotmail account, MSN e-mail account, or Microsoft Passport, you have a Windows Live ID.You can sign in with your existing e-mail address and password.If you do not already have a Windows Live ID, click Sign Up Now to register.4.If this is your first time using the eOpen Web site, complete the My Profile section. Once you have completedyour profile, click OK, and you will return to the home page.5.Under Agreement Summary in the left-hand navigation, click Add Agreement.6.Enter your Authorisation Number and Licence Number from the notification letter you received fromMicrosoft, and then click Add to view.7.On the Agreement Summary page, select the appropriate Licence number in order to view the details of aspecific licence agreement. The Licence number is highlighted in yellow.8.Review the Microsoft Licence Agreement (use the scroll bar on the side to read the full text). Once you haveread, understood, and agreed to the terms, you can accept the agreement by entering your full name and clicking I Accept.9.To view the Volume Licence product keys, click View Volume Licence Keys in the left-hand navigation.10.If this is your first visit to the Licensing Service Centre (where the Volume Licence product keys are displayed)you will be prompted to complete a registration form like the one that is shown in the following image.11.Next, read and follow the instructions to verify the ownership of your e-mail address.12.When your e-mail address is verified, you will be redirected to the Licensing Service Centre. The VolumeLicence product keys that are required to activate your software are located under the Product Key heading in the main body of the page. Use the Volume Licence product key during software installation to activate and use your software.To install certain licensed products, you must use a specific Volume Licence product key. This product key is issued to your organisation for your exclusive use for each specific licence grant. Because yourorganisation is held accountable for unauthorised use of the Volume Licence product keys that areassigned to your software, you agree to use your best efforts to keep a secure record of product keys, which includes not disclosing them to any unauthorised third party.Volume Licence product keys are displayed for products that require activation only.Some products do not require activation, but still require a standard product key for installation. For these products, the standard product key is displayed on a yellow sticker on the back of the plastic sleeve that contains the software CD.The following image displays an example of the message you will see if a product that is included in your software grant does not require a Volume Licence key for activation. If you receive this message, look for the product key on a yellow sticker on the back of the plastic sleeve that contains the software CD. You will need this product key to install your software.。

4ms Company Tapographic Delay用户手册说明书

Tapographic D elayfrom4ms C ompany a nd M atthias P uechUser M anual1.0–N ovember3,2017for f irmware v1.0Table o f C ontentsIntroduction3 B ackground4 W hat’s a m ulti-tap d elay?4 W hat’s a t apography?6 Installation6 G etting s tarted:Y our f irst T D p atch7Create a n ew T apography7 Editing y our T apography8 Saving y our W ork8 Explore t he K nobs8 Explore t he S witches8 Explore t he B uttons9 Sequencer M ode9 Controls9 Signal p ath12 Editing t apographies13 Entering T aps13 ADD/OFF/INS S witch13 RES/AMP/LPF S witch14 Upper B utton R ow14 Settings M enu14 Navigating t apographies16 Loading a t apography16 Saving a t apography16 S equencer m ode17 Advanced f eatures17 Velocity n ormalization j umper17 F irmware u pdate18 C alibration19 F actory t apographies19Banks A-D19 R eset a b ank t o f actory d efault21 Acknowledgments21IntroductionThe T apographic D elay i s a c omplex m ulti-tap d elay i n t he E urorack f ormat w ith a u nique interface d esigned f or l ive p erformance.I t e xcels a t t ransforming t he s implest a udio(a drone,a p ercussive s ound)i nto c omplex r hythmic s tructures,m eshes o f o rganic t extures, lush h armonic m ille-feuilles,l iquid a nd r esonant e ffects…p lus e verything w e h ave n ot explored y et!Have y ou e ver g ot t ired o f t he m onotonous r epetitions t hat y our s tandard d elaypedal/module p roduced?H ave y ou e ver w ished f or a m ore c omplex r hythmic s tructure t han just d ecaying r epetition?I f y es,y ou h ave c ome t o t he r ight p lace:t he T apographic D elay i s an a dvanced e ffect t hat l ets y ou h andle r epetition i n a x c ompletely n ovel w ay.I t i s i n a w ay to a t raditional d elay w hat a f ull r hythmic s equencer(with p attern r ecall,v elocity c ontrol, tactile i nput)i s t o a s imple c lock.W ith t he T D,y ou i nteractively d efine t he r hythm t hat t he repetitions w ill f ollow:a v elocity-sensitive s ensor a llows y ou t o r ecord,e dit,m odify,a nd sequence y our o wn a rrangements o f d elays.I n a s ense,t he T D i s t he c onverse o f t he classic F rippertronics s ound-on-sound s etup p opularized b y R obert F ripp i n t he70’s:y ou don't p lay t he g uitar,y ou p lay t he t ape l oop!The T apographic D elay i s a n e xpressive e xperimental i nstrument m eant t o b e p layed i n real-time,r ather t han a s et-and-forget e nd-of-chain e ffect.I nteract w ith i t!E xperiment!P ush it t o i ts l imits!●Velocity-sensitive f orce s ensor t o t ap t he d elay c onfigurations(t apographies)●Up t o32t aps,e ach w ith i ts o wn d elay t ime,a mplitude/filter a nd p anning●Low-pass f ilter o r r esonant(pingable)b and-pass f ilter o n e ach t ap●Morphing b etween d elay c onfigurations,w ith a djustable m orph t ime●Two d ifferent f eedback p aths:a R epeat t oggle a nd a F eedback k nob●Save a nd r ecall u p t o24d elay c onfigurations(4b anks o f6s lots e ach)●Tapography s equencer w ith f orward,r andom w alk o r r andom d irections●Synchronization t o a n e xternal c lock,w ith c lock d ivider/multiplier●Gate o utput t hat p lays t he c urrent r hythm o f d elays●Maximum d elay t ime o f174s econds(almost3m inutes)●16b its/48kHz w ith32b its f loating-point i nternal p rocessing,1.3ms s oftware l atency●Mono-in,s tereo-out o peration●18HP E urorack m odule●Current c onsumption:125mA o f+12V;32mA o f-12V.(10-to-16pin c able i ncluded)●0.98"(25mm)m aximum d epth w ith p ower c able●Dry f requency r esponse:20Hz-5kHz:+/-0.1dB.@10kHz:-2.3dB.@20kHz:-7.8dB●Audio i nputs m ax22Vpp.A udio o utputs s oft-limit a t m ax17Vpp●Trigger/clock i nputs:+2V m inimum,+12V m aximum●Gate(trigger)o utput:+8V,4ms p ulse w idthB ackgroundW hat’s a m ulti-tap d elay?The b est w ay t o u nderstand t he c oncepts u nderlying t he T apographic D elay i s t o r emember the e xperimentations w ith r eel-to-reel t ape d ecks.I magine a s etup w ith t wo t ape r ecorders and a s trip o f t ape g oing f rom o ne t o t he o ther.T he f irst t ape r ecorder i s s et t o r ecord y our input a udio c ontinuously;t he s econd i s s et t o p lay w hat’s o n t he t ape t o y our s peakers.A s the t ape p asses t hrough t he w rite-head a nd t hen r ead-head o f t he t wo m achines,a d elay i s introduced b etween i nput a nd o utput:a p articular s ignal w ill a ppear a t t he o utput o f t he system s ome t ime a fter i t w ent i nto t he s ystem.T his d elay i s p roportional t o t he d istance between t he t wo m achines(and t he t ape s peed,w hich w e c onsider c onstant h ere).I f y ou use a m ixer t o s um t he“dry”i nput a nd t he“wet”o utput,y ou w ill h ear a r epetition:t he original s ignal,t hen i ts d elayed c opy s ome t ime a fter.Figure1:C lassic d elay s ystemIf n ow y ou r einject t he o utput o f t he s ystem b ack i nto i ts i nput,m aterial w ill b e p layed b ack, then r ewritten o n t ape,t hen p layed b ack a gain,a nd s o o n…I t w ill r epeat a t r egular i ntervals indefinitely,u ntil i t d ies o ut d ue t o s ignal a ttenuation a nd/or d istortion.T his i s f eedback.This s ituation a nd i ts t wo c ontrols,f eedback a mount a nd d ry/wet,d escribe t he w orkings o f typical d elays,w hether t hey u se a ctual a nalog t ape o r m emory c hips.Now,l et’s m ake t he t opology a b it m ore c omplicated b y i ntroducing m ore t han o ne r ead head o n t he p ath o f t he t ape.E ach o f t hese r ead h eads i s c alled a t ap:i t i s w here y ou t apinto t he t ape s ignal.O ur t raditional d elay c onfiguration a bove i s j ust t he p articular c ase o f a 1-tap d elay(one r ead h ead);b ut i f y ou p lace n t aps,a nd s um t hem a ll t ogether w ith t he input,y ou w ill n ow h ear n+1r epetitions(the d ry s ignal,t hen t he n r epetitions).Figure2:C lassic m ulti-tap d elayMore i nterestingly,t he i nterval b etween e ach r epetition w ill v ary w ith t he d istance b etween each r ead h ead(tap)o n t he t ape!E ven m ore i nterestingly,i f y ou n ow f eed t he s um o f a ll taps b ack i nto t he i nput,t he“rhythm”g ets m ore a nd m ore c omplex a s t ime p asses.F or instance,w ith t wo t aps p laced a t1a nd1.618s econds f rom t he w rite h ead,w e g et t his:A m ulti-tap d elay i s t herefore c onceptually a s mall s tep f rom t he u sual s ingle-tap d elay,b ut can g ive m ore c omplex s onic r esults,d epending o n t he r elative d elay t imes(distances)o f the t aps,t heir a mplitudes,t he a mount o f f eedback,t he m odulation o f t he d elay t imes…Since m ulti-tap d elays a re a bout t iming a nd r hythm,w hy n ot l et y ou e nter t hese p arameters yourself,b y t apping t he r hythmic p attern o n a s ensor.W elcome t o a w orld o f t apographies! W hat’s a t apography?It’s a w ord w e i nvented.A t apography i s t he p articular c onfiguration o f a m ulti-tap d elay including t he t iming a nd t he r elative i ntensity o f e ach t ap.A s ignals e ngineer w ould probably c all i t a n i mpulse r esponse(like o n a c onvolution r everb,o nly d iscrete),b ut a tapography c ontains a b it m ore i nformation.P recisely,a t apography i s a c ollection o f t aps, where e ach t ap h as t he f ollowing i nformation:●Time,i.e.t he d istance i n s econds s eparating i t f rom t he w rite h ead●Velocity(intensity)●A p arameter t he v elocity i s m apped t o(amplitude,l ow-pass c utoff,o r b and-passfrequency)●Panning i n t he s tereo f ieldThe T apographic D elay a llows y ou t o r ecord,e dit,s equence,s ave a nd r ecall t hese tapographies,a nd o f c ourse,h ear t hem i n a ction.Installation1.Remove t he T apographic D elay(TD)f rom t he b ox a nd a nti-static b ag.T he R AM c hipon t he T D m ay b e d amaged b y s tatic e lectricity;t ake c are n ot t o t ouch t he c ircuitboard.2.Connect t he f ree e nd o f t he p ower c able t o a E urorack p owerheader o n y our p ower s upply d istribution s ystem,w ith t he r edstripe t owards t o t he-12V.T he o ther e nd o f t he p ower c able i sa10-pin c onnector w hich s hould a lready b e c onnected t o t heTD.T he r ed s tripe o n t he p ower c able s hould b e o rientedtowards t he b ottom o f t he m odule(the b ottom i s m arked b y awhite s tripe a nd t he w ord“POWER”).N ote:T he T D i sreverse-polarity p rotected,b ut i f a m odule i s i ncorrectlyconnected,i t c ould d amage s omething e lse o n t he p ower b us.3.Securely s crew t he T D t o t he r ails o f y our c ase.4.Power t he s ystem o n.Y ou w ill s ee a c olored a nimation o n t heupper b uttons.G etting s tarted:Y our f irst T D p atchCreate a n ew T apography1.For y our f irst p atch w ith t he T apographic D elay,p repare a s imple s ound s ource.A s hortmelodic s equence o f p ercussive s ound(envelope w ith v ery s hort a ttack a nd~0.5sexponential d ecay)i s a g ood c hoice.M ake s ure t o c lock i t r elatively s low,p erhaps o ne note e very t wo o r t hree s econds.N ow,p atch t his s ound s ource t o t he A udio I n o f t he TD a nd m onitor b oth A udio O ut j acks i n s tereo.2.Put t he c ontrols i n t hese d efault p ositions:●Level a t70%(adjust d ownward i f y ou h ear c lipping)●Time a t50%●Feedback a t0%●Modulation a t0%●Dry/Wet a t50%●Morph a t50%●Bottom l eft s witch f lipped u p t o A DD●Bottom r ight s witch f lipped c enter t o A MP3.Take a l ook a t t he t op r ow o f b uttons:i f m ost o f t he b uttons a re r ed,y ou a re i n S EQ(sequencer)m ode.W e’ll d iscuss S EQ m ode l ater,b ut f or n ow l et’s g o i nto E DIT m ode: hold b utton4(M ODE)a nd t hen p ress b utton5(E DIT).W hen t he t op r ow o f b uttons a re no l onger r ed,y ou’re r eady f or t he n ext s tep.4.Hold t he R epeat/Clear b utton f or0.5s ec t o c lear a ny e xisting t apography.Y ou s houldnow o nly h ear y our d ry i nput.5.Tap s everal t imes(say,5t imes)o n t he s ensor,i n a r hythm o f y our c hoosing.W atch a ndlisten c arefully t o w hat h appens.●On t he f irst t ap,t he r ed T ap L ED l ocated a bove t he s ensor l ights u p,i ndicating t hatthe m odule i s n ow r ecording a t apography.●Each s ubsequent t ap m akes t he r ow o f b uttons f lash i n w hite,i ndicating t hat a n ewtap h as b een e ntered.T he m ore b uttons l ight u p,t he s tronger i ts v elocity i s.●Each i nput s ound i s n ow r epeated,a ccording t o t he r hythm y ou t apped o n t hesensor.F or i nstance,i f y ou d id“tap...t aptap…t ap”o n t he s ensor a nd t he i nputaudio g oes“pling”,y ou w ill h ear“pling…p lingpling...p ling”.T he v elocity o f t he t aps determines t he v olume o f t he“plings”.Congratulations,y ou r ecorded y our f irst t apography!Editing y our T apographyYou c an c lear i t b y h olding d own t he R epeat/Clear b utton f or h alf a s econd,t hen r ecord a new o ne b y t apping s ome m ore o n t he s ensor(or v ia C V).Careful:if you forget to clear and tap the sensor once more,you will add a new tapto the existing tapography,only far,far away from the rhythm you first entered!Since then,maybe70seconds have elapsed so your resulting tapography will sound l ike:“tap…t aptap…t ap…[70s econds o f s ilence]…t ap”.If y ou e nter m ore t han t he m aximum o f32t aps,t he u pper r ow o f b uttons w ill s tart p ulsing purple i nstead o f w hite,i ndicating t hat o lder t aps a re s tarting t o d isappear t o m ake r oom f or the n ew o nes.If y ou m ade a m istake,y ou c an d elete t he l ast t ap e ntered b y p ressing t he D elete b utton.Notice t hat t he D elete b utton f lashes t o r eflect t he p attern y ou t apped i n.E ach t ime t he button f lashes,t he G ate O ut e mits a s hort t rigger.U se t his o utput t o t rigger e vents somewhere e lse i n y our s ystem.Saving y our W orkWhen y ou a re s atisfied w ith y our t apography,y ou c an s ave i t t o a n e mpty s lot.B ank D i s empty w hen t he m odule l eaves t he f actory.G o t o t his b ank b y h olding t he s econd b utton (marked B ANK)a nd q uickly p ressing t he s ixth b utton(marked D).N ow,s ave y our tapography i nto s lot1:h old B utton1u ntil i t b links r ed,r elease i t a nd q uickly p ress i t a gain to c onfirm.Y ou h ave s aved t he t apography!T he b utton l ights u p g reen t o i ndicate t hat t his first s lot i s l oaded.T o l oad a nother s lot,j ust p ress i ts c orresponding b utton.Explore t he K nobsNow,e xplore t he e ffect o f t he k nobs:T urn L evel u p a nd d own t o h ear h ow t he l evel o f t he input c hanges.N ow t urn T ime.T his k nob s cales t he d elay t imes o f a ll t he t aps,m aking y our whole t apography s horter o r l onger,m aintaining t he t ime r atios b etween t aps.T he p itch w ill shift t emporarily w henever t his k nob m oves,l ike o n a t ape d elay.F eedback f eeds t he s um of a ll t aps b ack i nto t he i nput.T urn t his k nob w ith c are:i t c an v ery e asily b loom t o v ery h igh levels a nd d amage y our e ars,o r w orse,y our s peakers.M odulation s ets t he a mplitude a nd frequency o f t he L FOs w hich m odulate e ach t ap t ime,i ndependently.T urn i t a ll t he w ay down t o d isable i t;n ow t urn i t s lowly u p a nd l isten f or b endy,w ow-and-flutter s ounds t hat increase i n a mplitude a nd d ecrease i n s peed a s y ou t urn i t u p.A s u sual,D ry/Wet c ontrols the m ix o f y our i nput a nd o utput s ignal.Each c hange i n t he a ctive t apography c an b e i nstant o r g radual.T he M orph k nob s ets t he time i t t akes f or a t ap t o f ade i n o r o ut w hen y ou i nsert/delete i t,o r w hen y ou l oad a n ew tapography.T ry t urning M orph u p a nd t hen p ress a b utton o n t he t op r ow t o s elect a n ew tapography.S ee h ow t he n ew t apography’s b utton f lashes g reen f or a w hile?T hat i ndicates you a re“morphing”f rom t he c urrent t apography t o t he n ew o ne.Explore t he S witchesThe t wo s witches a t t he b ottom o f t he f aceplate d etermine w hat h appens w hen e ach n ew tap i s e ntered.F or a d etailed d escription o f t hese,s ee t he E ntering t aps s ection b elow. Briefly,t he l eftmost s witch(A DD/OFF/INS)d etermines w hat h appens w hen y ou t ap t he sensor(or f ire a t rigger i nto t he T ap j ack).W hen i t’s s et t o A DD,m ore t ime i s a dded t o t he tapography.I n t he t ape m achine a nalogy,t his i s a kin t o s plicing m ore t ape t o t he e nd o f t he existing t ape.A DD m ode i s g reat f or c reating y our i nitial t apography,b ut i f y ou l eave t he switch s et h ere f or a w hile a nd t hen a dd m ore t aps,y ou’ll g et s ome v ery l ong s ilences. Often,o nce y ou’ve c reated a t apography y ou w ill w ant t o a dd m ore t aps i nside t he“tape loop”w ithout e xtending t he t ime(or a dding“more t ape”).T o d o t hat,f lip t he s witch t o I NS. In t his m ode,n ew t aps a re I NS e rted I NS i de t he t apography,w ithout m aking t he t apography longer.T he c enter p osition,O FF,s imply d isables t he s ensor a nd t he T ap t rigger j ack:n o new t aps c an b e a dded.The r ightmost s witch(R ES/AMP/LPF)s elects w hat k ind o f t ap i s i nserted.R ES m eans t he tap i s r un t hrough a r esonant b and-pass f ilter w ith t he v elocity c ontrolling t he f requency. LPF m eans t he t ap i s r un t hrough a l ow-pass f ilter,w ith t he v elocity c ontrolling t he c ut-off. AMP m eans t he t ap i s a ttenuated b ased o n t he v elocity.T ry a dding d ifferent t ypes o f t apsto a t apography.K eep i n m ind,t he V EL s etting i n t he m enu c hanges h ow t he v elocity o f your t aps c hanges t he f ilters:t ry d ifferent v alues a s y ou e xperiment(see S ettings M enu). Explore t he B uttonsRepeat w ill m ake t he i nput r epeat i ndefinitely,a ccumulating o n t op o f o lder m aterial.T urn i t on a nd l isten h ow i nput m aterial b uilds u p q uickly!H old t he D elete/Sync b utton f or a second,i t w ill t urn r ed t o i ndicate S ync m ode.I n t his m ode,t he t otal l ength o f t he tapography(from t he f irst t o t he l ast t ap)i s s caled t o t he c lock i nput i n E xt C lock.T ry t his out:p atch y our m aster c lock t o t he E xt C lock j ack,a nd e nter a r hythmic t apography(one where t ap t imes a re a ll m ultiples o f a c ommon t empo).N ow e nable S ync a nd l isten h ow t he tapography s yncs;T ime t hen b ecomes a m ultiplier/divider f or t his c lock.Sequencer M odeRemember w hen w e c hecked t o m ake s ure w e w eren’t i n S EQ m ode a t t he b eginning o f this t utorial?L et’s e xplore w hat S EQ m ode i s.O n t he t op r ow o f b uttons,h old d own t he4th button(M ODE)a nd p ress t he6th b utton(S EQ)s hortly.R elease t he b uttons a nd y ou’ll e nter Sequencer m ode.Y ou k now y ou’re i n s equencer m ode b ecause t he t op l ights h ave a r ed “background”.I n t his m ode,t apping t he s ensor w ill n ot e nter n ew t aps;i nstead i t w ill s elect the n ext t apography s aved i n t he c urrent b ank.N otice t hat t he p osition o f M orph i s honored,a s w ell a s t he v elocity o f y our t aps:t he s tronger y ou t ap o n t he s ensor,t he f aster the m orphing w ill b e b etween s lots.T he l eftmost s witch a lso c hanges m eaning i n t his mode,a nd d etermines t he d irection o f t his s equencer:O FF m eans f orward,I NS m eans random w alk,a nd A DD m eans r andom.T o e xit S equencer m ore,h old t he4th b utton(M ODE)a nd p ress t he5th b utton(E DIT).ControlsTap B uttons1t o6:l oad a nd s ave t apographies(see N avigating t apographies);d isplay a nd m odifythe s ettings(see T he S ettings M enu).Level k nob:s ets t he l evel o f t he s ignal g oing i nto t he d elay(does n ot i ncludethe d ry p ath,o nly t he w et p ath).F rom0%(no s ignal g oing i nto t he d elay)t o300%a mplification.Time k nob:s cales a ll t he t ap t imes i n t he c urrent t apography b y a f actor f romabout0.1t o a bout4(middle p osition i s1).I t e ffectively c ompresses o rexpands t he c urrent t apography i n t ime.W hile t he k nob i s m oving,p itchshifting w ill o ccur.T his f actor a lso a ffects w here n ewly e ntered t aps w ill b eplaced,a nd i t a lso a ffects t he v isual a nd g ate o utput.W hen S ync i s e ngaged,Time s elects t he m ultiplication/division o f t he i ncoming c lock o n E xt C lock.The d ivisions/multiplications a vailable a re:1/8,1/7,1/6,1/5,1/4,1/3,1/2,1,2,3,4,5,6,7,8,16.T he m iddle p osition c orresponds t o1(nodivision/multiplication o f t he i nput c lock).Feedback k nob: A mount o f t he s um o f a ll t aps t hat i s i njected b ack i nto t heinput. F rom 0% t o 120%. C areful: i n s ome s ettings, t he e ffect o f t his k nob can b e w ild .Modulation k nob: A mount a nd f requency o f t he i nternal L FOs m odulatingeach t ap t ime. E ach t ap h as a n i ndependent r andom L FO w hose s hape i s close t o a s ine w ave. W ith e nough m odulations, t he d elayed m aterial w ill b e pitched u p/down, j ust l ike w ow a nd f lutter o n a t ape r ecorder. F ullycounter-clockwise, f requency i s h igh (around 50Hz) b ut t he a mount o f modulation i s s o s mall t hat t here i s n o e ffect. F ully c lockwise, a mount i smaximum (+/- 0.5 s ec) b ut f requency i s s o s mall t hat t he L FOs a re s talled o n a p articular p osition. P ositions i n b etween m inimum a nd m aximum g ive intermediate a mplitudes a nd f requencies f or t he L FOs. T ip: A dding a b it o f modulation c an h elp a void h arsh b uildups w hen u sing F eedback.Dry/Wet k nob: c rossfades b etween t he u naffected i nput s ignal a nd t he s um of a ll t aps.Morph k nob: a mount o f t ime i t t akes t o t ransition f rom o ne t apographyconfiguration t o t he n ext, f rom 0 s econds t o a bout 12 s econds. A ny t ime t he tapography c hanges, M orph d ictates t he t ransition t ime. T his i ncludes a dding a t ap, r emoving a t ap, c learing t he e ntire t apography, e n/disabling R epeat, and r ecalling a t apography f rom a m emory s lot.Time, F eedback, M odulation, D ry/Wet C VBipolar C V i nputs f or t he r espective p arameters (-5V t o 5V). S ending a positive v oltage a dds t o t he k nob’s v alue; s ending a n egative v oltagesubtracts f rom t he k nob’s v alue. Gate O ut : e mits a t rigger p attern i n a l oop, a ccording t o t he c urrenttapography a nd t he c urrent T ime s etting. C an b e u sed t o t urn t he T D i nto a recordable t rigger s equencer. T riggers a re +8V, w ith 4 m illisecond p ulse w idth.Audio O ut 1 & 2: s tereo a udio o utputs. B y d efault, t aps a re a ssignedalternatively t o e ach o utput. S ee P anning S etting f or m ore d etails. I n some p anning s ettings, A udio O ut 1 i s c onsidered t he m ain o utputfor m ono u se.Audio I n (audio i nput). A ccepts f ull r ange o f m odular l evel s ignals (+/-11V)Repeat j ack(trigger i nput):t oggles t he c urrent s etting o f t he R epeat b uttonwhen a t rigger i s r eceived o n t his j ack.Tap/Next(trigger i nput):w hen a t rigger i s r eceived,h as t he s ame e ffect a s tapping t he s ensor w ith a v elocity r ead f rom t he V elocity C V j ack.I n S EQ (sequencer)m ode,i t i nitiates a t ransition t o t he n ext t apography s lot.Tap L ED:l ights u p w hen a t apography i s b eing r ecorded(i.e.w hen t he i nternalstopwatch i s r olling,s ee E ntering t aps b elow);i t i s o ff w hen t he s topwatch h as stopped.T he L ED f lashes w hen t he s topwatch r esets/loops.Velocity/Morph(CV i nput):t he v oltage o n t his i nput i s s ampled e very t ime atrigger i s r eceived o n t he T ap j ack.V alid r ange i s0V t o+8V.W hen u sed t o s et cutoff f requency o f t aps(R ES o r L PF s etting),t his i nput t racks1V/Oct o n a f ew octaves.I n S EQ m ode,t his c ontrols t he M orph a mount w hen a t rigger appears o n t he T ap/Next j ack.H igher v oltage=s lower t ransition.Ext C lock(clock i nput):W hen S ync i s e ngaged,t he c urrent t apography’slength w ill b e s ynced t o t he c lock i nput,m ultiplied o r d ivided b y a f actor s et b y the T ime k nob.ADD/OFF/INS s witch:s elects w here n ewly e ntered t aps w ill b e i nserted i nthe c urrent t apography.A DD m eans a fter t he c urrent t apography,I NS m eans inside i ts b ounds,O FF m eans t hat i t w ill n ot b e i nserted(useful t o i nhibitrecording,e.g.d uring p erformance o r t o d isable t he T ap j ack).S ee t heEntering t aps s ection f or m ore d etails.Repeat/Clear b utton:s hort p ress t oggles R epeat.W hen e nabled,a n additional t ap a t t he v ery e nd o f t he t apography i s f ed b ack i nto t he i nput a t unity g ain,e ffectively r epeating t he a udio i ndefinitely.T he l oop s ize i s f ixed when R epeat i s a ctivated a nd w ill n ot b e s caled w ith t he T ime k nob.H olding this b utton d own f or h alf a s econd c lears t he c urrent t apography b y d eleting a ll taps a t o nce(W arning:t here i s n o u ndo!).B oth f unctions a re s ubject t o M orph: taps w ill f ade i n/out i n a t ime d etermined b y t he M orph k nob.Tap s ensor:t he f orce-sensing r esistor(FSR)t hat r ecords t he v elocity-sensitive tap i nformation.U sed f or e ntering t aps a nd a dvancing t he s equencer.Delete/Sync b utton:s hort p ress d eletes t he l ast e ntered t ap(subject t oMorph t ime);l ong p ress t oggles S ync.T he b utton f lashes w hite e ach t ime a trigger i s e mitted t o G ate O ut;l ights u p r ed w hen S ync i s e ngaged.RES/AMP/LPF s witch:s elects h ow n ewly e ntered t aps w ill b e a ffected b y t heirvelocity.R ES m eans t he t ap’s o utput w ill g o t hrough t he a r esonant b and-passfilter w ith t he v elocity m apped t o t he c enter f requency.A MP m eans t he t ap’svelocity i s m apped t o t he v olume.L PF m eans t he t ap’s o utput w ill g o t hrougha n on-resonant l ow p ass f ilter w ith t he v elocity m apped t o t he r oll-offfrequency.S ee E ntering t aps s ection f or m ore d etails.Signal p athThere a re t wo i ndependent f eedbackpaths:The R epeat f eedback p ath r e-injects t hetap w ith t he l ongest t ime b ack i nto t heinput o f t he d elay l ine.I t d oes t hiswithout a lteration,t hat i s,a t u nity g ainwith n o f iltering.I f t he t apography i s5seconds l ong a nd R epeat i s o n,t he i nputsignal5s econds a go i s c ontinually b eingre-injected i nto t he i nput.S incere-injection i s a t u nity g ain,t he s ignalnever w eakens.O ne u se f or t he R epeatfeature i s t o s end a o ne-shot s ound(perhaps a s ingle p ercussive s ound)i ntothe T D.W ith R epeat o n,t he o ne-shotsound w ill c ontinue t o l oop,a nd y ou c anplay w ith t he t apography w ithout h avingto f ire t he o ne-shot s ound a gain.The F eedback p ath r e-injects t he s um o fall t aps.T his m eans t heir d elay t imes a ndfiltering/amplitude e ffects w ill a ll b e f edback i nto t he s tart o f t he d elay l ine.I ftaps a re n ot“aligned”,i.e.i f t heir t ime a re not m ultiples o f a b ase t empo,t hen F eedback w ill g radually c reate m ore a nd m ore complex r epetitions,u ntil i t f ills t he s onic s pace w ith a s mooth“tail”.J ust l ike i n a r oom w ith a m icrophone a nd a P A,F eedback i s n ot s traightforward t o c ontrol:d epending o n t he number o f a ctive t aps,i t m ight b e t oo w eak t o b uild u p a nd q uickly d ilute i nto s ilence,o r too s trong a nd r apidly b uild u p h arsh t ones.W e d id o ur b est t o m ake t he r ange o f t he Feedback k nob a s u seful a s p ossible d epending o n t he n umber o f a ctive t aps.Note:A s oft s aturation i s a pplied t o t he o utput a nd t o t he f eedback p ath.T herefore,a s layers o f s ound a ccumulate,c lipping w ill b e a nalog-like a nd p leasant t o t he e ar.Editing t apographiesEntering T apsWhen y ou t ap o n t he s ensor(or i nput a t rigger),y ou a dd t aps o n t he d elay l ine s o t hat t he tap t imes m imic t he r hythm t hat y ou t ap.L et u s s ee h ow t his w orks i n a b it m ore d etail. Keep i n m ind t his s ection o nly a pplies t o E DIT m ode(see t he S ettings M enu s ection).When y ou f irst t ap t he s ensor a fter a C lear,t he r ed T ap L ED l ights u p t o i ndicate t hat t he TD i s r eady t o r ecord n ew t aps.T he v elocity o f t his f irst t ap i s n ot t aken i nto a ccount:i t j ust tells t he T D t o s tart r ecording.I magine t hat a s topwatch s tarts c ounting t ime w hen t he T ap LED l ights u p.E ach s ubsequent t ap o n t he s ensor w ill p lace a n ew t ap o n t he d elay l ine a t the t ime i ndicated b y t he i maginary s topwatch.ADD/OFF/INS S witchOnce t he T ap L ED i s o n,t he l eftmost s witch c ontrols w hat h appens w hen y ou a dd a t ap:●ADD m eans t hat n ew t aps a re a ppended t o t he e nd t he t apography.E ach t apyou a dd i n A DD m ode m akes t he t otal t ime o f t he t apography l onger.T heimaginary s topwatch s imply c ounts u pwards,i ndefinitely.Example:i f y ou t ap i n a f ew t aps i n A DD m ode,t hen w ait10s econds,t hen t aponce m ore,i t w ill a dd a n ew t ap10s econds a fter t he p revious o ne.A DD m odeis h ow y ou a dd t ime t o a t apography.T he m aximum t ime y our t apography c anbe i s a bout3m inutes.●INS m eans t hat n ew t aps a re i nserted i nside t he b oundaries o f t he c urrenttapography.T he t otal t ime l ength o f t he t apography w ill n ot c hange.W henyou’re i n I NS m ode,t he i maginary s topwatch c ounts f rom0t o t he l ast t ap,a ndthen l oops b ack t o0.N ew t aps w ill b e i nserted w herever t hey f all i n t his“loop”.The t op b uttons s hows t he t aps a nd c an h elp y ou v isualize w here t he n ew t apwill b e i nserted w hen y ou t ap t he s ensor.Example:l et’s s ay y ou a lready e ntered a f ew t aps f or a t otal o f3s econds i nADD m ode.I f y ou s witch t o I NS m ode a nd t ap a n ew t ap,i t w ill b e i nsertedsomewhere w ithin t hose3s econds.●OFF m eans t hat t apping t he s ensor a nd t he T ap j ack w ill h ave n o e ffect.T hiscan b e u sed t o p rotect a t apography f rom a ccidental t aps a nd u nwanted g ates.RES/AMP/LPF S witchWhen a dding a t ap,t he r ightmost s witch s ets w hat p arameter t he v elocity i s m apped t o. The V EL m enu s etting d etermines h ow m uch v elocity i s m apped(See S ettings M enu:V EL section).●AMP:T he t ap’s o utput i s a ttenuated b y a n a mount d etermined b y t he t ap’svelocity.●RES:T he t ap’s o utput p asses t hrough a r esonant b and-pass f ilter.T he v elocityof t he t ap i s m apped t o t he c enter f requency o f t he f ilter:t he s tronger y ou t ap,the h igher t he p itch.。

idea中intellivue用法

idea中intellivue用法
IntelliVue 是 SAP HANA Studio 提供的一种功能，用于可视化 HANA 数据库中的数据。

在 SAP HANA Studio 中，IntelliVue 可以帮助您轻松地探索和分析 HANA 数据库中的数据，并通过交互式图表和报告来呈现数据。

以下是在 SAP HANA Studio 中使用 IntelliVue 的基本步骤：
1. 打开 SAP HANA Studio 并连接到您的 HANA 数据库。

2. 在左侧导航栏中，展开“内容”节点，然后展开“分析”节点。

3. 单击“IntelliVue”节点，这将打开 IntelliVue 仪表板。

4. 在 IntelliVue 仪表板上，您可以看到一个可视化的数据浏览器，其中包含有关您的 HANA 数据库的摘要信息。

5. 在数据浏览器中，您可以单击不同的图表和报告来查看有关您的数据的更多详细信息。

6. 您可以使用 IntelliVue 中的各种工具和功能来筛选、排序和聚合数据，
以便更好地理解您的数据。

7. 您还可以使用 IntelliVue 中的各种图表类型来可视化您的数据。

例如，您可以使用条形图、饼图、线图和散点图等图表类型来呈现数据。

8. 在您完成对数据的分析和可视化后，您可以将结果导出为各种格式，例如 Excel、PDF 和 CSV 等。

总之，IntelliVue 是 SAP HANA Studio 中一个非常有用的工具，可以帮助您轻松地探索和分析 HANA 数据库中的数据，并通过交互式图表和报告来呈现数据。

Visual Studio IntelliSense 高级版说明书

Advanced IntelliSenseOur improved IntelliSense will help you type faster with our new prediction algorithm. New IntelliSense filtering and highlighting helps you find what you are looking for, especially in APIs and code you arenot familiar with.Powerful live code analysisInline visualizations identify errors in your code so you can get immediate feedback on the quality as you type. They also identify places in your code where you can follow best coding practices, adhereto team-defined style rules, or apply one of our many refactorings, code actions, and code fixes.Custom Code AnalysisDon’t see an analyzer or refactoring you want? Write your own Roslyn analyzer and code fix, or use one of the many analyzers/fixers written by our awesome OSS community.Download live analyzers for common FX Cop Rules at https:///dotnet/roslyn-analyzersFast code navigationNavigate your code to quickly find types, open files, and identify everywhere a type is referenced in your codebase.Live unit testingLive Unit Testing in Visual Studio Enterprise automatically runs the impacted unit tests in the background as you type. It also provides real-time feedback on which lines of code are hit by passing and failing unit tests, dramatically improving your productivity with writing and maintaining unit tests.Visual Studio 2017 is faster, leaner, and full of newproductivity features to help you write and publish code faster.Become a Power User. Master the shortcuts with Visual Studio 2017.Code Assistance & AnalysisVisual Studio 2015Visual Studio2017ReSharperShow available quick actions and refactorings Ctrl + . Alt+Enter or Ctrl + .Alt+Enter IntelliSense code completion Ctrl + Space Ctrl + Space Ctrl + SpaceFormat Document Ctrl+E, D Ctrl+E, D Ctrl+E, CFormat Selection Ctrl+E, F Ctrl+E, F Ctrl+E, C Parameter Info/Signature Help Ctrl+K, P Ctrl+K, P Ctrl+Shift+SpaceMove code up/down Alt+Up/Down Arrow Alt+Up/Down Arrow Ctrl+Shift+Alt+Up/DownArrowComment with line comment Ctrl+K, C Ctrl+K, C Ctrl+Alt+/ Uncomment line comment Ctrl+K, U Ctrl+K, U Ctrl+Shift+/Search and NavigationFinding References/UsagesFind All References Shift+F12Shift+F12Shift+F12Cycle through references F8F8Ctrl+Alt+PgUp/PgDown Quick Find Ctrl+F Ctrl+F Ctrl+FFind/Replace in Files Ctrl+Shift+F Ctrl+Shift+F N/AGo ToGo To Definition F12F12F12Peek Definition Alt+F12Alt+F12Ctrl+Shift+QGo To Implementation Ctrl+F12Ctrl+F12Ctrl+Alt, clickGo To All/Type/File/Member/Symbol Ctrl + ,Ctrl + , or Ctrl+T Ctrl + TOpen Error List Ctrl+W,E Ctrl+W,E N/AGo To Next Error F8F8Shift+Alt+PgUp/PgDown RefactoringsRename Ctrl+R, R Ctrl+R, R Ctrl+R, RMove Type to Matching File N/A Ctrl+. or Alt+Enter Ctrl+Shift+R Introduce temporary variable Ctrl + . Ctrl+. or Alt+Enter Ctrl+R, VInline temporary variable Ctrl + . Ctrl+. or Alt+Enter Ctrl+R, IEncapsulate field Ctrl + . Ctrl+. or Alt+Enter orCtrl+R,ECtrl+R, EChange signature Ctrl + . Ctrl+. or Alt+Enter Ctrl+R, SRemove Parameters Ctrl+. or Ctrl+R, V Ctrl+. or Alt+Enter orCtrl+R, VCtrl+R, SReorder Parameters Ctrl+. or Ctrl+R, O Ctrl+. or Alt+Enter orCtrl+R, OCtrl+R, SExtract Method Ctrl+. or Ctrl+R, M Ctrl+. or Alt+Enter orCtrl+R, MCtrl+R, MExtract Interface Ctrl+. or Ctrl+R, I Ctrl+. or Alt+Enter orCtrl+R, ICtrl+Shift+ROtherSync active file with Solution Explorer Ctrl+[, S Ctrl+[, S Shift+Alt+LSend code snippet to C# Interactive Window Ctrl+E, E Ctrl+E, E N/A Want to remap your shortcuts?T ry https://aka.ms/hotkeys。

vs intellisense 原理

vs intellisense 原理VS IntelliSense 原理1. 简介•VS IntelliSense是一种智能代码补全功能，为开发者提供实时的代码提示和文档支持。

•IntelliSense可以大大提高编码效率和准确性，减少错误。

•本文将从浅入深，解释VS IntelliSense的原理。

2. 语法分析•IntelliSense的基础是对代码进行语法分析。

•语法分析器会根据编程语言的语法规则，将代码解析成抽象语法树（AST）。

•AST是一种以树状结构表示代码的方式，可以更方便地进行后续的分析和处理。

3. 词法分析•词法分析是语法分析的前置步骤。

•词法分析器会对代码进行分词，将代码拆分成一个个的词法单元。

•词法单元可能是关键字、标识符、操作符、常量等。

•掌握词法单元信息有助于后续的代码补全和提示。

4. 语义分析•语义分析是IntelliSense的核心部分。

•语义分析器根据AST和词法单元的信息，进行上下文分析和类型推断。

•语义分析器能够理解变量的类型、函数的参数和返回值等信息。

•基于语义分析的结果，IntelliSense可以提供更准确的代码补全和文档支持。

5. 基于上下文的补全•IntelliSense根据当前的代码上下文，提供相应的补全选项。

•当输入一个对象实例时，IntelliSense会提示该对象的属性和方法。

•当输入一个函数名称时，IntelliSense会提示该函数的参数列表和返回值。

•IntelliSense还支持静态成员和继承关系的补全。

6. 文档支持•IntelliSense不仅提供代码补全，还可以显示相关的文档信息。

•当选择一个补全选项时，IntelliSense会显示该选项的描述和使用示例。

•这些文档信息能够帮助开发者更好地理解和使用相关的代码。

7. 异步更新•IntelliSense可以实时更新代码提示和文档支持。

•当开发者输入代码时，IntelliSense会对新输入的代码进行解析和分析。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

基于事件驱动机制
• 信息推送：自动将相关主题的更新消息发送给订阅者 • 双向沟通：客户端可同时是信息发布者和信息接收者
分布式服务器模式
• 分布式服务器模式，各服务器除了响应客户端的消息请求，同时可以与其他服务器交换消息
主要特点 - 2
数据安全
• 可采用国际标准或第三方算法加密，保证数据安全 • 提供用户数据存取日志和报告，满足内外部的监管要求
• 支持各主流数据库，最大程度配合客户当前使用，降低转换成本。
支持不同开发技术平台
• 开发方式灵活，采用开放性技术标准，支持主流开发技术平台，帮助用户节省中转处理成本。
系统架构
行业运用
可广泛运用于政府、电力、交通、金融、证券、保险、税务、电信、移动、教育等各行业
目标客户特点
内部多个独立应用系统或远程系统之间，存在业务数据整合与应用分析的需求各系统之间因不同操作系统或通信协议，需要通过异构环境访问现有系统功能，因而产生将分散的资源互连，并结合到新应用系统的需求需与外部系统（如各供应商系统）建立外部连接的需求
演示环境
一区 IP: 192.168.1.10 数据总线
信息发送 HTTP信息发送 SOAP信息发送 FTP 服务器
IntelliBus
IntelliBus
三区 IP: 10.1.1.20 数据总线
信息接收 FTP 文件发送
物理隔离文件 FTP 文件 FTP
演示内容
1区到3区流程
3区到1区流程
主要性能指标
eBrokersSys的数据处理单元均基于阵列服务器进行负载均衡。以一部HP DL380G5为例，测试结果如下：
• 订单申报：交易管理服务器 (Order Server)每秒可处理超1000笔市场交易 • 行情读取：数据分布服务器能够每秒1500次截获行情报价，每一次行情报价可多达1000字节
通道授权管理
• 可对每个数据通道进行单独的授权定义 • 可设置通道属性，包括私用与公用。
用户端使用授权
• 可为用户端系统授权，便于整体管理 • 权限包括发布者、接收者、发布者/接收者
主要特点 - 3
内存式数据存储
• 可用内存作数据存储 (In memory)，有效加快信息的传输效率。
主要数据库的兼容
数据属性
发布
接收
TCP
TCP
TCP
TCP
TCP
信息发布者
信息接收者
信息发布/接收者
TCP
P TC
发布 / 接收
主要特点 - 1
订阅与发布模式
• 实现透明的用户信息双向实时传送 • 信息发布者通过建立一个唯一主题来标识消息 • 信息订阅者通过订阅该主题来得到所需信息
按需派发
• 用户端可按需定制接收信息，同时支持动态定制信息，减少网络冲击 • 用户端也可以建立通道组，按需接收同一组别的消息
案例 – 基于IntelliBus的证券交易系统
所有数据均通过 IntelliBus进行传输，包括实时行情数据、历史数据
股市数据查看、前台下单服务、中台风险控制、后台结算服务等各类应用均通过 Intel有 20%-30%经由基于IntelliBus的交易平台完成
• 根据标签自动完成数据项的解释
数据的自演示
• 对多数据段的内容自动进行缺省的数据演示
系统架构
IntelliBus Admin
关系数据库 IntelliBus
数据通道数据加密数据格式
In Memory
Channel Channel 2 1 Obje a Obje 1 Obje b Obje 2 ... ...
测试实例
交易数量
8000 6000 4000 2000 0 3 0.1 1 0.2 378 0.3 0.4 2705 0.5 737 0.6 149 0.7 81 0.8 61 0.9 15 1 7382
响应时间 (s)
以下数据为系统某日实际运作之监控数据响应时间为从确定下单到风险监控计算到收到交易所系统回馈信息为终止。由图可知，其中90%的买卖盘在0.5s之内完成交易所使用机器：双CPU, dual core 2.8G, 2G 内存
Channel 3 Obje x Obje y ...
Channel 4 Obje A Obje B ...
Channel 5 Obje X Obje Y ...
Channel 6 Obje X1 Obje Y1 ...
Channel 7 Obje X Obje Y ...
Channel n
...
数据存储
数据管理及发布平台 IntelliBus
简介
什么是IntelliBus？
• 超低时延消息消息平台 • 通过数据通道进行可靠消息实时传送 • 可通过任何数据形式在不同的信息接收者和发布者间进行双向信息传递
主要优点
• • • • • • 超低延迟的快速信息处理高性能、高效率主题式的数据传送方式实时数据服务允许事件驱动模式低管理成本
数据通道 (Channel)
每一个数据通道均可进行多项自定义
• 数据来源 (数据库，Web Services) • 读取权限 • 数据传输方式 (广播，on demand)
通道设置使用灵活
• 对每个数据通道可动态加入用户 • 可设置通道属性，包括私用与公用 • 私用通道必须授权方能使用
数据的自解释
• IntelliBus数据总线 • HTTP • SOAP
• FTP发送文件