Orion Status Update-April2012
moxa 的e1212用法 -回复

moxa 的e1212用法-回复ReentrantLock(可重入锁)是Java中的一种同步工具,它提供了比synchronized关键字更为灵活的线程同步机制。
ReentrantLock内部维护了一个同步队列(AQS,AbstractQueuedSynchronizer),使用该队列中的节点(Node)来管理等待获取锁的线程。
在ReentrantLock的内部,还有一种重要的概念,即Condition(条件)。
Condition对象是由ReentrantLock创建的,它提供了一种线程间的协议,用于控制线程的等待(await)和唤醒(signal)操作。
本文将详细探讨ReentrantLock的Condition原理,并解释如何使用它来实现多线程之间的协作。
一、Condition的基本概念Condition接口提供了一种线程阻塞和唤醒的机制,以及一些与锁绑定的条件(condition),它与ReentrantLock紧密关联。
每个Condition对象都与一个ReentrantLock关联,并通过ReentrantLock进行创建。
与Object类中的wait和notify方法类似,Condition提供了await和signal 方法来实现线程的等待和唤醒操作。
Condition的主要方法包括:1. await():使当前线程进入等待状态,同时释放当前线程对应的锁,直到被其他线程调用signal或signalAll方法唤醒。
2. awaitUninterruptibly():与await方法相比,该方法不会响应中断,不会抛出InterruptedException异常。
3. signal():唤醒一个等待在该Condition上的线程,如果有多个线程在等待,则只唤醒其中一个。
4. signalAll():唤醒所有等待在该Condition上的线程。
二、Condition的底层实现在深入探究Condition的原理之前,我们先来了解ReentrantLock的底层实现。
nVent ERICO PlusCU 2L 6V 电源控制器操作指南说明书

C o u n t -u p I g n i t i o n I n d i c a t o rT r i g g e r G u a r dT r i g g e rB a t t e r y D o o rB a t t e r y I n d i c a t o rC a d w e l d P l u s C u p C o n n e c t o rP L U S C U 2L 6P L U S C U 2L 15P L U S C U 2L 6N B P B P L U S C U 2L 6P B P L U S C U 2L 15P L U S C U 2R L D 6P L U S C U 2R L D 15L e a d C o n n e c t o rIndicator lights are flashing:The PlusCU uses an internal charging mechanism that sends an electric current to the Cadweld Plus cup. If the trigger on the control unit is pulled before the internal charging mechanism resets, the lights will flash. Wait 5 seconds and try again.If the error message persists, contact your nVent ERICO representative.PlusCU does not respond when trigger is pulled:If the unit does not respond, check battery status to determine if new batteries are needed.Cadweld Plus cup does not ignite:Disconnect the PlusCU lead from the PlusCU then re-examine your mold, weldmetal cup, ignition strip, and other Cadweld equipment to verify proper setup.If this issue persists, contact your nVent ERICO representative.PlusCU does not function properly at temperatures below 0° F [-18°C]:Alkaline batteries are not intended for extreme cold temperatures. nVent ERICOrecommends the use of lithium-ion batteries at temperatures below 0° F [-18°C].WARNING:nVent products shall be installed and used only as indicated in nVent product instruction sheets and training materials. Instruction sheets are available at and from your nVent customer service representative. nVent products must never be used for a purpose other than the purpose for which they were designed or in a manner that exceeds specified load ratings.2.All instructions must be completely followed to ensure proper and safe installation and performance.3.Improper installation, misuse, misapplication or other failure to completely follow nVent's instructions and warnings may cause product malfunction, property4.damage, serious bodily injury and/or death, and void your warranty.SAFETY INSTRUCTIONS:All governing codes and regulations and those required by the job site must be observed.Always use appropriate safety equipment such as eye protection, hard hat, and gloves as appropriate to the application.nVent, nVent CADDY, nVent ERICO Cadweld, nVent ERICO Critec, nVent ERICO, nVent ERIFLEX, and nVent LENTON are owned byHigh voltage electrical shock hazard. Keep hands and body clear of the cord(leads) while operating. Failure to do so can result in death or serious injury.Safety First!Personal SafetyWhen working with nVent ERICO Cadweld Plus, always use appropriate safety equipment suchas eye protection, heat-resistant gloves, and other PPE as appropriate to the application and required by local safety codes.Avoid contact with hot materials. Maintain safe working distance and secure footing whilewelding or working with hot materials.Welding material is a mixture of oxides and metal which react to produce hot molten materialwith temperatures in excess of 1400° C [2500° F] and a localized release of smoke. Thesereactions are not explosive and not known to be toxic. Ignition temperatures of weldingmaterial are in excess of 900° C [1650° F] and will not ignite under ambient conditions.For reduced or eliminated smoke options, contact nVent ERICO.。
ORA-00603ORA-27504ORA-27300ORA-27301ORA-27302参考学习

ORA-00603ORA-27504ORA-27300ORA-27301ORA-27302参考学习--节点1 告警⽇志Thu Jun 20 03:02:18 2019Thread 1 advanced to log sequence 2092 (LGWR switch)Current log# 11 seq# 2092 mem# 0: +DATA/test/onlinelog/redo11_1.logCurrent log# 11 seq# 2092 mem# 1: +DATA/test/onlinelog/redo11_2.logThu Jun 20 03:02:18 2019LNS: Standby redo logfile selected for thread 1 sequence 2092 for destination LOG_ARCHIVE_DEST_2Thu Jun 20 03:02:20 2019Archived Log entry 5703 added for thread 1 sequence 2091 ID 0x9b8db1ed dest 1:Thu Jun 20 03:03:53 2019skgxpvfynet: mtype: 61 process 316751 failed because of a resource problem in the OS. The OS has most likely run out of buffers (rval: 4) Errors in file /u01/app/oracle/diag/rdbms/test/test1/trace/test1_ora_316751.trc (incident=560025):ORA-00603: ORACLE server session terminated by fatal errorORA-27504: IPC error creating OSD contextORA-27300: OS system dependent operation:sendmsg failed with status: 105ORA-27301: OS failure message: No buffer space availableORA-27302: failure occurred at: sskgxpsnd2Incident details in: /u01/app/oracle/diag/rdbms/test/test1/incident/incdir_560025/test1_ora_316751_i560025.trcThu Jun 20 03:03:54 2019Dumping diagnostic data in directory=[cdmp_20190620030354], requested by (instance=1, osid=316751), summary=[incident=560025]. opiodr aborting process unknown ospid (316751) as a result of ORA-603Thu Jun 20 03:04:03 2019Sweep [inc][560025]: completedSweep [inc2][560025]: completedThu Jun 20 03:06:15 2019Thread 1 advanced to log sequence 2093 (LGWR switch)Current log# 5 seq# 2093 mem# 0: +DATA/test/onlinelog/redo05_1.logCurrent log# 5 seq# 2093 mem# 1: +DATA/test/onlinelog/redo05_2.logThu Jun 20 03:06:16 2019---trc ⽂件--trc⽂件,初步看应该是服务器⽹卡mtu值相关问题*** 2019-06-20 03:03:53.395*** CLIENT ID:() 2019-06-20 03:03:53.395*** SERVICE NAME:() 2019-06-20 03:03:53.395*** MODULE NAME:() 2019-06-20 03:03:53.395*** ACTION NAME:() 2019-06-20 03:03:53.395SKGXP:[7f5ab0ef57c0.0]{0}: SKGXPVFYNET: Socket self-test could not verify successful transmission of 32768 bytes (mtype 61). SKGXP:[7f5ab0ef57c0.1]{0}: The network is required to support UDP protocol sends of this size. Socket is bound to 169.254.16.188. SKGXP:[7f5ab0ef57c0.2]{0}: phase 'send', 0 tries, 100 loops, 32354 ms (last)struct ksxpp * ksxppg_ [0xc11fde0, 0x7f5aadaf5588) = 0x7f5aadaf5580Dump of memory from 0x00007F5AADAF5580 to 0x00007F5AADAF6AB0---数据库状态select INST_ID,INSTANCE_NAME,STARTUP_TIME from gv$instance;--添加到CRTset lines 1000\r alter session set nls_date_format='yyyymmdd hh24:mi:ss';\r set time on \r selectINST_ID,INSTANCE_NAME,STARTUP_TIME from gv$instance;09:42:29 SYS@test1(test1)> set lines 100009:43:30 SYS@test1(test1)> alter session set nls_date_format='yyyymmdd hh24:mi:ss';Session altered.09:43:31 SYS@test1(test1)> set time on09:43:31 SYS@test1(test1)> select INST_ID,INSTANCE_NAME,STARTUP_TIME from gv$instance;INST_ID INSTANCE_NAME STARTUP_TIME---------- ---------------- -----------------1 test1 20190509 15:30:082 test2 20190507 21:37:04---节点2 ⽇志Thu Jun 20 03:03:54 2019Dumping diagnostic data in directory=[cdmp_20190620030354], requested by (instance=1, osid=316751), summary=[incident=560025]. Thu Jun 20 03:10:10 2019Thread 2 advanced to log sequence 912 (LGWR switch)Current log# 6 seq# 912 mem# 0: +DATA/test/onlinelog/redo06_1.logCurrent log# 6 seq# 912 mem# 1: +DATA/test/onlinelog/redo06_2.log---参考官⽅⽂档2041723.1CAUSEThis happens due to less space available for network buffer reservation.SOLUTION1. On servers with High Physical Memory, the parameter vm.min_free_kbytes should be set in the order of 0.4% of total Physical Memory. This helps in keeping a larger range of defragmented memory pages available for network buffers reducing the probability of a low-buffer-space conditions.*** For example, on a server which is having 256GB RAM, the parameter vm.min_free_kbytes should be set to 1073742 ***On NUMA Enabled Systems, the value of vm.min_free_kbytes should be multiplied by the number of NUMA nodes since the value is to be split across all the nodes.On NUMA Enabled Systems, the value of vm.min_free_kbytes = n * 0.4% of total Physical Memory. Here 'n' is the number of NUMA nodes.2. Additionally, the MTU value should be modified as below#ifconfig lo mtu 16436To make the change persistent over reboot add the following line in the file /etc/sysconfig/network-scripts/ifcfg-lo :MTU=16436Save the file and restart the network service to load the changes#service network restartNote : While making the changes in CRS nodes, if network is restarted while CRS is up, it can hung CRS. So cluster services should be stopped prior to the network restart.---实际操作,两个节点执⾏[root@test1 bin]# ifconfig lo mtu 16436[root@test1 bin]#[root@test1 bin]# vi /etc/sysconfig/network-scripts/ifcfg-loDEVICE=loIPADDR=127.0.0.1NETMASK=255.0.0.0NETWORK=127.0.0.0# If you're having problems with gated making 127.0.0.0/8 a martian,# you can change this to something else (255.255.255.255, for example)BROADCAST=127.255.255.255ONBOOT=yesNAME=loopbackMTU=16436---重启⽹络服务# systemctl stop network# systemctl start network⼆、设定 vm.min_free_kbytes 参数为物理内存的0.4%For example, on a server which is having 256GB RAM, the parameter vm.min_free_kbytes should be set to 1073742 *** ---此次修改主机内存 512G ,所以这个值是 1073742*2=2147484vm.min_free_kbytes=2147484[oracle@test1 ~]$ cat /proc/sys/vm/min_free_kbytes65536[oracle@test1 ~]$调整MIN_FREE_KBYTES的⽬的是保持物理内存有⾜够的空闲空间,防⽌突发性的换页。
飞泛(Futaba)Futaba14SG R7 firmware更新说明书

February 2020—Firmware and FAA RID NPRMAs February greets us many have chosen to set theirhobby interests aside, or at least limit their participa-tion to inside for the past couple months. The winterbuild is a time-honored tradition in the northern cli-mates. In addition to getting new aircraft ready forwhen the weather warms and the winds calm it’s theperfect time to give our existing airframes a thoroughexamination for signs of wear, or potential failure. It’salso a good time to check to see if our transmitters, re-ceivers, or ESC’s may have pending firmware updates.The advantage of firmware updates is they often givenew capabilities for your existing hardware, or fix pre-viously unknown defects. However, sometimes as newfeatures are introduced or patched another featuremay be inadvertently broken by the update. The avail-ability of an update does not mean it’s necessary foryour use. As an example, when Futaba released up-date 7 for the Futaba14SG they inadvertently intro-duced a range check failure on startup. Futaba recent-ly introduced update 9 to fix the range check failure onstartup issue. Firmware updates tend to be an iterativeprocess with customers being the final test of function-Futaba Software DownloadFrSky Important Update for ACCST D16 FrSky Firmware Downloads Spektrum Firmware Updates Jeti Firmware Updates Graupner Updates Castlelink UpdatePersonal safety is not the only topic to discuss this month. The survival of our hobby is very much threatened by the recent FAA RID Notice of Pro-posed Rulemaking (NPRM). The FAA published their plan requiring broadcast from all aircraft weighing over 250 grams (0.55 pounds) on Dec 31. ality. FrSky recently released a new firmware for ALL of their D16 ACCST transmitters and receivers back to 2013 (OpenTX as well as FrOS). The firm-ware addresses a serious issue –if you’re in the Eu-ropean Union. The FCC (American) version of transmitters/receivers are not significantly affect-ed, especially if operated where the airwaves are not crowded with many 2.4ghz signals. One take-away from this is noting that when applying radio firmware updates be sure to note that you have downloaded FCC version and not EU. I recom-mend waiting on the FrSky ACCST updates for a couple months as this is a major update and there will inevitably be bugs. I’d rather do the updates one time since this transmitter update also requires that all receivers are updated.In summary; when checking over all the clevises, horns, pushrods, screws, motor mounts etc, don’t forget to check where you stand regarding what you can’t see –the firmware. Additionally, be judi-cious about applying a recently introduced firm-ware especially if it’s a major update. Finally, be sure you’re using the FCC radio firmware and not the EU version.Don’t be misled by the term “drone” in the NPRM. The FAA uses the term “drone” to apply to all Un-manned Aircraft Systems(UAS), this includes every-thing we fly at TCRCM field and may even include free flight and control line. This NPRM is open for public comment until March 2. The AMA, and EAA (Experimental Aircraft Association) as well as others petitioned in vain for an extension to the comment period. In response to the request for an extention FAA replied on January 28:“…the need for remote identification of UAS increas-ingly has become important as new public safety and national security concerns arise regarding the use of UAS. Accordingly, the FAA has determined that any extension of the comment period, and the subse-quent delays in promulgation of a final rule imple-menting remote identification of UAS, would not be consistent with the safety and security objectives of the proposed rule.Therefore, your request to extend the comment pe-riod for the Remote Identification of Unmaimed Air-craft Systems NPRM is denied. The comment period for the NPRM closes on Monday, March 2, 2020.”Once one dives into the 319 page NPRM in depth it details how the FAA is proposing to progressively annihilate the hobby. This NPRM proposes to make it illegal for a land owner to fly over their own land in the short term, and eventually eliminate model flying fields for home-built aircraft like we now fly. There are many many levels of concern. Grouping Line of Sight (LOS) modeling in with the regulations of Beyond Visual Line of sight BVLOS operations is a one size fits all solution that is inappropriate. Making it impossible to establish new flying fields, or even move an existing club flying field to a new location is well beyond what Congress mandated in the FAA reauthorization act of 2018. To assist with digesting the information about the NRPM, Jim Andersan has posted a page of infor-mation on the Club Website. There are also links to two summaries of the NPRM in the sources below.It’s seriously imperative that all interested reach out to the FAA and to all elected representatives. Even if your position is that you have no intention of follow-ing these rules then politely tell the FAA that they can expect noncompliance from otherwise law abid-ing citizens.Some would say that contacting FAA or representa-tive will make no difference. If that’s the case we’re no worse off and you did what you could. Your com-ments MAY make a difference in which case it’s time and energy well spent.Links to Contacts:• Dan Newhouse• Patty Murray• Maria Cantwell• White House• FAA RID NPRM Comment pageLinks to Information and resources.• Layman’s Guide to the NPRM for Remote ID• AMA summary of the RID NPRM• AMA Templates to use to assist in drafting your own response.• Our club website。
os-e401_2012-04

OFFSHORE STANDARDDNV-OS-E401Helicopter DecksAPRIL 2012The electronic pdf version of this document found through is the officially binding versionD ET N ORSKE V ERITAS AS© Det Norske Veritas AS April 2012Any comments may be sent by e-mail to rules@This service document has been prepared based on available knowledge, technology and/or information at the time of issuance of this document, and is believed to reflect the best of contemporary technology. The use of this document by others than DNV is at the user's sole risk. DNV does not accept any liability or responsibility for loss or damages resulting from any use of this document.FOREWORDDET NORSKE VERITAS (DNV) is an autonomous and independent foundation with the objectives of safeguarding life,property and the environment, at sea and onshore. DNV undertakes classification, certification, and other verification and consultancy services relating to quality of ships, offshore units and installations, and onshore industries worldwide, and carries out research in relation to these functions.DNV service documents consist of among others the following types of documents:—Service Specifications. Procedural requirements.—Standards. Technical requirements.—Recommended Practices. Guidance.The Standards and Recommended Practices are offered within the following areas:A)Qualification, Quality and Safety Methodology B)Materials Technology C)Structures D)SystemsE)Special Facilities F)Pipelines and Risers G)Asset Operation H)Marine Operations J)Cleaner Energy O)Subsea SystemsCHANGESGeneralThis document supersedes DNV-OS-E401, April 2011.Text affected by the main changes in this edition is highlighted in red colour. However, if the changes involve a whole chapter, section or sub-section, normally only the title will be in red colour.Main changes—Ch.1 Sec.1 new text A202 regarding scope of this standard.—Ch.1 Sec.1 Table B1 new reference.—Ch.2 Sec.8 “Norwegian Civil Aviation Authorities Requirements” in previous edition of document deleted.—Ch.3 update section A in line with OSS-101 and subsequent changes of OSS-201.CONTENTSCH. 1INTRODUCTION (6)Sec. 1Introduction (7)A.General (7)A100General (7)A200Objectives and Scope (7)A300Organisation of this standard (7)B.Normative References (7)B100General (7)B200Offshore service specifications and rules (7)B300Offshore standards (8)B400Other references (8)rmative References (8)C100General (8)D.Definitions (8)D100Verbal forms (8)E.Abbreviations and Symbols (8)E100Abbreviations (8)E200Symbols (9)CH. 2TECHNICAL PROVISIONS (10)Sec. 1Structural Categorisation and Selection of Materials (11)A.Structural Categorisation (11)A100General (11)A200Structural category (11)B.Material Selection (11)B100General (11)B200Design temperatures (11)C.Material Connections (11)C100Steel and aluminium connections (11)Sec. 2Design Loads and Load Combinations (12)A.General (12)A100General (12)A200Wind loads (12)Sec. 3Structural Strength (13)A.Strength Requirements (13)A100Deck plating and stiffeners (13)A200Girders and supporting structure (13)A300Buckling (13)Sec. 4Miscellaneous (14)A.General (14)A100General (14)Sec. 5Requirements to Vessel Safety (HELDK-S) (15)A.Safety Requirements (15)A100General (15)Sec. 6Requirements for Helicopter (HELDK-SH) (16)A.Safety (HELDK-SH) (16)A100General (16)Sec. 7Requirements for Helicopter Refuelling and Hangar Facilities (HELDK-SHF) (17)A.HELDK-SHF (17)A100General (17)Sec. 8Testing and Certified Products (18)A.General (18)A100General (18)CH. 3CERTIFICATION AND CLASSIFICATION (19)Sec. 1General (20)A.Introduction (20)A100Application (20)A200Class designation (20)A300Technical requirements (20)A400Assumptions (21)A500Documentation (21)OFFSHORE STANDARDDNV-OS-E401HELICOPTER DECKSCHAPTER 1INTRODUCTIONCONTENTS PAGE Sec.1Introduction (7)D ET N ORSKE V ERITAS ASSECTION 1INTRODUCTIONA. GeneralA 100General101 This standard is intended to provide requirements and guidance to the design of helicopter decks constructed in steel or aluminium, for mobile offshore units (MOUs), or offshore installations designed and built for installation at a particular offshore installation.102 The requirements in this standard apply to units or installations with erected landing platform for helicopters or a landing area arranged directly on weather deck or supported by substructure anywhere on the unit or installation.103 The standard is applicable to the design of complete helicopter deck structures including sub-structure and hull connections and reinforcements.104 The standard has been written for general worldwide application. Governmental regulations may include requirements in excess of the provisions of this standard depending on the size, type, location and intended service of the offshore unit or installation.Guidance note:For Classed mobile offshore units (MOUs) relevant parts of statutory requirements, e.g. MODU Code and/or SOLAS will be applicable.---e-n-d---of---G-u-i-d-a-n-c-e---n-o-t-e---A 200Objectives and Scope201 The objectives of this standard are to:—provide an internationally acceptable standard of safety for helicopter decks by defining minimum requirements for the design, materials, construction, arrangement for safe helicopter operations and commissioning—serve as a contractual reference document—serve as a guideline for designers, suppliers, purchasers, contractors and regulators—specify procedures and requirements for helicopter decks subject to DNV certification and classification. 202 The scope of this standard covers requirements for the helicopter deck structure, vessel safety, helicopter and refuelling and hangar facilities.The scope excludes the NMD Helicopter deck regulations as applicable on Norwegian shelf. These are provided in DNV-OSS-201.A 300Organisation of this standard301 This standard is divided into three main chapters:Chapter 1: General information, scope, definitions and references.Chapter 2: Technical provisions for helicopter decks for general application.Chapter 3: Specific procedures and requirements applicable for certification and classification in accordance with this standard.B. Normative ReferencesB 100General101 The standards given in Table B1, Table B2 and Table B3 include provisions, which through reference in this text constitute provisions for this standard.B 200Offshore service specifications and rules201 The offshore service specifications and rules given in Table B1 are referred to in this standard.Table B1 DNV Offshore service specifications and rulesReference TitleDNV-OSS-101Rules for Classification of Offshore Drilling and Support UnitsDNV-OSS-201Verification for compliance with norwegian shelf regulationsDNV-OSS-102Rules for Classification of Floating Production, Storage and Loading UnitsPt.6 Ch.1 Sec.2Rules for Classification of Ships, - Helicopter InstallationsB 300Offshore standards301 The offshore standards given in Table B2 are referred to in this standard.B 400Other references401 The references given in Table B3 are referred to in this standard.C. Informative ReferencesC 100General101 The documents in Table C1 include acceptable methods for fulfilling the requirements in the standards.Other recognised documents may be used provided it is shown that they meet or exceed the level of safety of the actual standards.D. DefinitionsD 100Verbal forms101 Shall: Indicates requirements strictly to be followed in order to conform to this standard and from which no deviation is permitted.102 Should: Indicates that among several possibilities, one is recommended as particularly suitable, without mentioning or excluding others, or that a certain course of action is preferred but not necessarily required. Other possibilities may be applied subject to agreement.103 May: Verbal form used to indicate a course of action permissible within the limits of the standard.104 Can: Can-requirements are conditional and indicate a possibility to the user of the standard.E. Abbreviations and SymbolsE 100Abbreviations101 The abbreviations given in Table E1 are used in this standard.Table B2 DNV Offshore standardsReference TitleDNV-OS-C101Design of Offshore Steel Structures, General (LRFD method)DNV-OS-C201Structural Design of Offshore Units (WSD method)DNV-OS-D101Marine and Machinery Systems and EquipmentTable B3 Other referencesReferenceSOLAS requirements in forceCode for the Construction and Equipment of Mobile Offshore Drilling Units (MODU Code) in forceTable C1 DNV Recommended Practices and Classification NotesReferenceTitleDNV-RP-A201Plan Approval Documentation Types – Definitions DNV-RP-C203Fatigue Strength Analysis of Offshore Steel Structures DNV-RP-C205Environmental Conditions and Environmental Loads Classification Note 30.1Buckling Strength AnalysisTable E1 AbbreviationsAbbreviation In fullCAA Civil Aviation Authority DNV Det Norske VeritasICAO International Civil Aviation Organisation IMO International Maritime Organization LRFD Load and resistance factor design MODUMobile offshore drilling unitE 200Symbols201 The following units are used:202 The following Latin characters are used:203 The following Greek characters are used:OS Offshore standardOSS Offshore service specification RP Recommended practiceSOLAS International Convention for the Safety of Life at Sea ULS Ultimate Limit State WSDWorking stress designg =gram k =kilo m =meter cm =centimetre mm =millimetre t =tonne N =Newton s=second.g =acceleration due to gravity p =pressure A =areaL =length between perpendiculars M =mass P =force V=velocity.σ=stressη=usage factor.Table E1 Abbreviations (Continued)Abbreviation In fullOFFSHORE STANDARDDNV-OS-E401HELICOPTER DECKSCHAPTER 2TECHNICAL PROVISIONSCONTENTS PAGE Sec.1Structural Categorisation and Selection of Materials (11)Sec.2Design Loads and Load Combinations (12)Sec.3Structural Strength (13)Sec.4Miscellaneous (14)Sec.5Requirements to Vessel Safety (HELDK-S) (15)Sec.6Requirements for Helicopter (HELDK-SH) (16)Sec.7Requirements for Helicopter Refuelling and Hangar Facilities (HELDK-SHF) (17)Sec.8Testing and Certified Products (18)D ET N ORSKE V ERITAS ASSECTION 1STRUCTURAL CATEGORISATION AND SELECTION OF MATERIALSA. Structural CategorisationA 100General101 Selection of structural categories, material quality, and requirements for inspection of welds are following the principles and requirements given in DNV-OS-C101 Sec.4 or DNV-OS-C201 Sec.4.A 200Structural category201 The main bearing parts of the helicopter deck with substructure shall in general be categorised as primary structure.B. Material SelectionB 100General101 Material specifications shall be established for all structural materials. Such materials shall be suitable for their intended purpose and have adequate properties in all relevant design conditions. Material selection shall be undertaken in accordance with the principles given in DNV-OS-C101 Sec.4 or DNV-OS-C201 Sec.4. 102 When considering criteria appropriate to material grade selection, adequate consideration shall be given to all relevant phases in the life cycle of the unit.B 200Design temperatures201 The helicopter deck including support structure shall be designed for service temperatures equal to the lowest daily mean temperature for the area(s) where the unit shall operate. Definition of mean temperature is given in DNV-OS-C101 Sec.4 or DNV-OS-C201 Sec.4.C. Material ConnectionsC 100Steel and aluminium connections101 In areas exposed to green sea/ sea spray, a non-hygroscopic material shall be applied between steel and aluminium in order to prevent galvanic corrosion. Bolts with nuts and washers shall be of stainless steel, quality A4-316 or equivalent.102 Horizontal inertia forces in bolted connections may be required to be taken up by metal to metal stoppers with insulation tape in the gap.103 Aluminium superstructures that are provided with insulating material between aluminium and steel shall be earthed to the hull. See Rules for Classification of Ships Pt.4 Ch.8.104 For welded connections, any bimetallic connection flats shall be delivered from approved manufacturer with DNV certificates.SECTION 2DESIGN LOADS AND LOAD COMBINATIONSA. GeneralA 100General101 The design loads and load combinations shall comply with the requirements listed in DNV Rules for Classification of Ships Pt.6 Ch.1 Sec.2 B combined with wind loads as specified in A200. It is to be noted that inertia forces with a 100 year return period shall be applied.Guidance note:For non-ship shaped units sea pressure on the helicopter deck can normally be excluded.---e-n-d---of---G-u-i-d-a-n-c-e---n-o-t-e---A 200Wind loads201 The wind loads shall be calculated using ‘gust’ (3 s averaging time interval) wind velocities.Guidance note:When evaluating wind pressures the following listed one minute sustained wind velocities at 10 m above base is normally to be used as a basis for calculating the gust wind velocities:For additional information regarding wind conditions, please see DNV-RP-C205.---e-n-d---of---G-u-i-d-a-n-c-e---n-o-t-e---202 The wind pressure acting on the surface of helicopter decks shall be calculated using a pressure coefficient C p = 2.0 at the leading edge of the helicopter deck, linearly reducing to C p = 0 at the trailing edge,taken in the direction of the wind. The pressure may act both upward and downward.203 For structures where vortex shedding may be of importance, vibration induced loads shall be taken into account.V 1min.10 =30 m/s for the landing condition V 1min.10=55 m/s for the stowed condition.SECTION 3STRUCTURAL STRENGTHA. Strength RequirementsA 100Deck plating and stiffeners101 DNV Rules for Classification of Ships Pt.6 Ch.1 Sec.2 C200 shall be complied with for requirements to helicopter deck scantlings for deck plating and stiffeners.A 200Girders and supporting structure201 The scantlings shall normally be based on direct stress analysis.The basic allowable usage factor, η0, is as follows (see DNV-OS-C201 for details):Guidance note:When dimensioning the support structure part of the hull (e.g. integrated platform beams part of weather deck or deck beams below the supporting structure of separate platforms), the stresses from the loading of the helicopter deck should be combined with relevant global stresses. In operational landing conditions the still water hull bending stress should be applied, while for stowed conditions both still water and dynamic wave bending stress should be applied.---e-n-d---of---G-u-i-d-a-n-c-e---n-o-t-e---A 300Buckling301 Buckling evaluations shall be carried out according to Classification Note 30.1 or equivalent internationally recognised codes and standards.—Operational conditions:Landing condition: η0 = 0.67Stowed condition:η0= 0.80SECTION 4MISCELLANEOUSA. GeneralA 100General101 DNV Rules for Classification of Ships Pt.6 Ch.1 Sec.2 D shall be complied for requirements to safety nets, tie-down points and surface friction of helicopter decks.102 In case of landing on a hatch cover section which is underlying in the packing joint, the strength or spacing of cleats shall be sufficient to keep the connection intact and tight.SECTION 5REQUIREMENTS TO VESSEL SAFETY (HELDK-S)A. Safety RequirementsA 100General101 DNV Rules for Classification of Ships Pt.6 Ch.1 Sec.2 E shall be complied with for requirements to vessel safety.Guidance note:For operation onboard vessels with large storage tanks for hydrocarbons, e.g. FPSOs & FSOs, practical guidance for safe operations can be found in Guide to Helicopter/Ship Operations issued by the International Chamber of Shipping.---e-n-d---of---G-u-i-d-a-n-c-e---n-o-t-e---SECTION 6REQUIREMENTS FOR HELICOPTER (HELDK-SH)A. Safety (HELDK-SH)A 100General101 DNV Rules for Classification of Ships Pt.6 Ch.1 Sec.2 F shall be complied with for helicopter safety.SECTION 7REQUIREMENTS FOR HELICOPTER REFUELLING AND HANGARFACILITIES (HELDK-SHF)A. HELDK-SHFA 100General101 Units equipped to support helicopter operations may be given the notation HELDK-SHF provided the requirements listed in DNV Rules for Classification of Ships Pt.6 Ch.1 Sec.2 G300 and DNV-OS-D101 Ch.2 Sec.3 G are complied with.SECTION 8TESTING AND CERTIFIED PRODUCTSA. GeneralA 100General101 Requirements to testing and certified products shall comply with the following references in DNV Rules for Classification of Ships:a)Pt.6 Ch.1 Sec.2 A301 g)b)Pt.6 Ch.1 Sec.2 A505c)Pt.6 Ch.1 Sec.2 I.OFFSHORE STANDARDDNV-OS-E401HELICOPTER DECKSCHAPTER 3CERTIFICATION AND CLASSIFICATIONCONTENTS PAGE Sec.1General (21)D ET N ORSKE V ERITAS ASOffshore Standard DNV-OS-E401, April 2012Ch.3 Sec.1 – Page 20SECTION 1GENERALA. IntroductionA 100Application101 As well as representing DNV’s recommendations on safe engineering practice for general use by the offshore industry, the offshore standards also provide the technical basis for DNV classification, certification and verification services.102 A complete description of principles, procedures, applicable class notations and technical basis for offshore classification is given by the offshore service specifications for classification, see Table A1.Guidance note:It will be necessary to also comply with statutory unit/ installation safety regulations of the state in which the unit/installation is registered, e.g. MODU Code and SOLAS, and helicopter safety operation demands by the operators or guidance in this respect by the helicopter registry authorities. This applies to e.g.:-size, location and marking of helicopter deck -obstacle free approach and take-off -rescue and fire fighting equipment -helicopter facility operation manuals.---e-n-d---of---G-u-i-d-a-n-c-e---n-o-t-e---A 200Class designation201 Offshore units and installations fitted with helicopter decks that have been designed, constructed and installed in accordance with the requirements of this standard under supervision of DNV may be given the class notation HELDK together with qualifiers as defined in Table A1.202 The application of the different qualifiers is restricted as follows:—The qualifier H can only be applied together with the qualifier S. —The qualifier F can only be applied together with the qualifiers SH.—The qualifier (N) can only be applied together with qualifiers SH or SHF.A 300Technical requirements301 Technical requirements for HELDK shall comply with Ch.2, as applicable: — Sec.1 to Sec.4 for notation HELDK— Sec.5 Additional requirements for qualifier S — Sec.6 Additional requirements for qualifier H —Sec.7 Additional requirements for qualifier F .For addition additional requirements for qualifier (N) see OSS-201, Ch.2, Sec.9.Table A1 DNV Offshore Service SpecificationsNo.TitleDNV-OSS-101Rules for Classification of Offshore Drilling and Support UnitsDNV-OSS-102Rules for Classification of Floating Production, Storage and Loading UnitsDNV-OSS-103Rules for Classification of LNG/LPG Floating Production and Storage Units or InstallationsTable A1 HELDK class notationClass notationDescriptionQualifier Description HELDK Helicopter deck<none>StructureS Additional requirements to ship safety.H Additional requirements to helicopter safety F Additional requirements to helicopter facilities(N)Evaluated with respect to requirements specified by the Norwegian Civil AviationAuthorities (CAA-N).Offshore Standard DNV-OS-E401, April 2012Ch.3 Sec.1 – Page 21 A 400Assumptions401 Any deviations, exceptions and modifications to the designed codes and standards given as recognised reference codes shall be documented and approved by DNV.402 Where codes and standards call for the extent of critical inspections and tests to be agreed between contractor or manufacturer and client, the resulting extent is to be agreed with DNV.A 500Documentation501 Documentation for classification shall be in accordance with the NPS DocReq (DNV Nauticus Production System for documentation requirements) and DNV-RP-A201.D ET N ORSKE V ERITAS AS。
SECS-GEM PROTOCOL SPECIFICATION

SECS-GEM PROTOCOL PURCHASE SPECIFICATION PUR-STA(PURCHASING RULES SITE AGRATE)DOCUMENT HISTORYDOCUMENT APPROVALREFERENCED DOCUMENTSCUSTOM ATTRIBUTES Alternate NumberDispatcher VERGANIL Working Vault AGRStatus ACTIVECycle type ACTIVE Change designator REVALIDATION Customer N/A Department BACK_END Originator FARRUGIAMA Owner FARRUGIAMA Replication sites C29O8Wait for ChildrenRevalidation Date02-JUL-2012AppendixA SECS-GEM PROTOCOL SPECIFICATIONA.1 Applicable documentsA.2 IntroductionA.3 Physical communication requirementsA.4 SEMI Equipment communication standard 2 message content (SECS-II)A.5 GEM requirementsA.6 Exception HandlingA.7 Documentation structureA.8 SECS interface acceptance test1. APPLICABLE DOCUMENTSApplicable documents are the reference books created by SEMI Communication Committee for SECS. The purpose of these documents is to provide both the structure of the protocol anda common approach for its description.SECS is divided in two main layers: physical connection and logical connection.E4 SEMI Equipment Communication Standard 1 Message Transfer (SECS I)E37 High Speed SECS Message Services (HSMS) Generic ServicesE5 SEMI Equipment Communication Standard 2 Message Content (SECS II)E30 Generic Model for Communication and Control of SEMI Equipment (GEM)E90 Specification for Substrate TrackingE32 Material Movement Management (MMM)G84 Specification for Strip Map ProtocolE142 Specification for Substrate MappingThe physical connection can be addressed using or SECS-I either HSMS.SECS-I defines the physical link, block transfer protocol and message protocol, using a RS232 serial line. HSMS accomplishes the physical connection using a TCP/IP network protocol.SECS-I is described in the BOOK OF SEMI STANDARDS (EQUIPMENT AUTOMATION SOFTWARE 1 and 2) section E4-0699 "SEMI EQUIPMENT COMMUNICATIONS STANDARD 1 - MESSAGE TRANSFER (SECS-I)" (hereafter E4).HSMS is intended to cover the same functionality as SECS-I but it allows a much higher communication performances and it is described in the same BOOK OF SEMI STANDARDS in section E37-0303 "HIGH-SPEED SECS MESSAGE SERVICES (HSMS) GENERIC SERVICES" (hereafter E37).SECS-II defines the method of conveying information between equipment and host in the form of messages.It is described in the BOOK OF SEMI STANDARDS section E5-0703 "SEMI EQUIPMENT COMMUNICATION STANDARD 2 - MESSAGE CONTENT (SECS-II)" (hereafter E5).The GEM standard is an extension of SECS-II and defines which SECS-II messages should be used, in what situations, and what the resulting activity should be. Indeed SECS-II defines several standard functions and the related messages, but it does not specify the modeling of the equipment, that is what it is expected by the SECS protocol from a behavioral standpoint.The GEM standard is described in the section E30-0302 "GENERIC MODEL FOR COMMUNICATIONS AND CONTROL OF SEMI EQUIPMENT (GEM)" (hereafter E30).Substrate Tracking is described in the BOOK OF SEMI STANDARDS in the section E90-0703 “SPECIFICATION FOR SUBSTRATE TRACKING” (hereafter E90).The MMM standard is described in the BOOK OF SEMI STANDARDS (EQUIPMENT AUTOMATION SOFTWARE 1 and 2) section E32-0997 "MATERIAL MOVEMENT MANAGEMENT (MMM)” (hereafter E32).Strip Map Handling is described in the BOOK OF SEMI STANDARDS in the section G84-0303 “SPECIFICATION FOR STRIP MAP PROTOCOL” (hereafter G84).Substrate / Wafer Map Handling are described in the BOOK OF SEMI STANDARDS in the section E142-0305 “SPECIFICATION FOR SUBSTRATE MAPPING” (hereafter E142). SECSIM and SECSIM-PRO (by Asyst Technologies inc.) are software tools that are able to simulate (although not entirely) both the host (in order to develop the interfaces without direct connection to the equipment) and the equipment (in order to test the equipment itself). It is described in the "SECSIM User Manual".2. INTRODUCTIONThis document describes the requirements for the SECS communication protocol to be implemented in the assembly, testing and finishing equipment purchased by All STMicroelectronics Ltd. Back End Plants. It also specifies the structure of the documentation and the tests that will be performed to verify the equipment's SECS/GEM interface. Not all the listed communication protocol features may apply to specific equipment. However the equipment supplier should find that when making the compliance review of the present specification. In the scenario were a cell is made up of multiple equipment, any equipment in the cell is required to be capable for being integrated with the Host.2.1 General RequirementsThe SECS communication protocol software installed on the equipment, along with any other related software, must be Y2K compliant.2.2 Communication ProtocolThe required communication protocol is the S emiconductor E quipment C ommunication S tandard (hereafter SECS) defined by the SEMI (S emiconductor E quipment and M aterialsI nternational) Communication Committee (hereafter SEMI).2.3 Communication ModelIn order to use the equipment efficiently in an automated environment the SECS interface must satisfy a generic model of communication. The model that STMicroelectronics have chosen is GEM. By the physical point of view, HSMS is preferred to SECS-I especially when communication performances can become a critical issue (long recipes, recipes containing images, images, long tables or maps). For example, Die Bonder, Wire Bonder, Laser Marker and Testers equipment are required to be provided with HSMS.The SECS-GEM interface must allow different levels of equipment integration: it must be usable in a fully automated line but also in a traditional production environment. Indeed both the approaches may be used in STMicroelectronics in designing automation lines and control applications.In a fully automated environment the operator intervention must be limited to the resolution of equipment assist requests, while in a traditional line, without material movement management, the operator will be in charge to load the equipment and start them, therefore the SECS protocol will be used just to integrate the MES to the physical equipment, that is to take actions on the equipment and collect data from it as soon as specific transactions are performed by an MES client.2.4 Material Movement ManagementIn the automated lines the product is loaded on the equipment using dedicated Material Handling Systems (MHS). These systems are basically of two types:•In-line. The equipment is mechanically integrated with each other. There is not an external system to transport the product from equipment to equipment. In most casesthe single strip moves from equipment to equipment.•External. The equipment is standalone and the MHS is an independent system that transport product from one equipment to the other. Most often the product istransported in carriers. This also applies when a line is made up of several in-linesystems connected together using an independent MHS.The MMM protocol is required whenever an external MHS is used either to transfer product between standalone equipment or in-line systems. The usage of different protocols, like SMEMA (S urface M ount E quipment M anufacturers A ssociation described in SMEMA 1.2), is allowed only within the boundaries of an in-line system.3. PHYSICAL COMMUNICATION REQUIREMENTS3.1 SECS-ISECS-I defines the physical link, block transfer protocol and message protocol, using a RS232 serial line. It must exactly follow E4 SECS-I standards. Protocol parameters described in SEMI standards as being adjustable must comply exactly with the E4 standard. The system bytes in a reply message sent by the equipment must be equal to the system bytes of the host primary message the equipment is replying to. The system bytes of all blocks in a multi-block message must be the same.It is required that the equipment can handle concurrent open transactions.The equipment's communication parameters (SECS protocol parameters, equipment constants, etc.) must be saved in non-volatile memory in case of reset or power supply failure. Loss of the non-volatile memory must generate an alarm or event report. During equipment start-up (after boot or power supply failure) parameters concerning the SECS interface set previously must be re-activated. This includes equipment constants and SECS communication parameters. The method for changing the SECS-I parameters must be included in the SECS interface documentation and the SECS-I parameter configuration must be password protected.Whenever a piece of equipment is composed of more modules, the equipment control must be able to manage all the different modules. From the SECS standpoint, the equipment must be seen a single unit with only one SECS connection. However if equipment is integrated with another equipment example Laser Marker onto a Handler any of this equipment should be capable of being integrated with the Host Independently.3.2Documentation (SECS-I)For equipment or Host to comply with SECS-I, a document is required containing the following information. (See also SEMI E6-0303, GUIDE FOR SEMICONDUCTOR EQUIPMENT INSTALLATION DOCUMENTATION)1. Method for setting all the parameters in Table 1 (below).2. Range allowed and resolution for each parameter in Table 1 (below).3. Compatibility with duplicate block detection and the method for enabling and disablingthe same if present (See E4-0699 Section 7.4.2).4. Maximum Expected inter-character, protocol, reply, and inter-block delays generatedunder normal operating conditions.5. Whether multi-block message are supported as a receiver.6. Whether multi-block message are used as a sender.7. Whether there is a limit to the size of a message received and, if so, what the limit is.8. Maximum expected size of a message being sent.9. Whether message interleaving is supported as a receiver.10. Whether message interleaving is used as a sender.11. Number of Device ID’s supported on the port.12. Maximum number of supported concurrent open transactions.Reference E4-0699 Section 8 Parameter settings3.3 HSMSHSMS accomplishes the physical connection using a TCP/IP network protocol. It must exactly follow E37 HSMS standards. The equipment must be able to support periodic Linktest.req messages. Despite it is not required; the equipment may initiate periodic Linktest.req messages. The equipment must provide a password protected way to configure HSMS parameters. Those settings must be kept by the equipment on a non-volatile storage device and must be reloaded at each power failure or system software reloads. Multiple open transactions must be supported by the equipment entity.It is preferred that the equipment establish the TCP/IP connection using Passive Connect Mode.The documentation must include:•The method for setting protocol parameters (Including if the IP address is static or dynamic).•The ranges and units allowed for each parameter.•The option used for refusing incoming connection requests if the implementation uses Passive Connect Mode.•The maximum message size that can be received.•The maximum message size that can be sent.•The maximum number of supported concurrent open transaction that the HSMS implementation can handle (greater than 1).In case of Passive Connect Mode, multiple connection requests on a single published port are allowed anytime even if equipment is a cluster of independent modules provided with independent control system software. The reply matching criteria defined in E37 (9.4.1) must be strictly observed.3.4HSMS Reply Matching CriteriaWhen a Sender sends a Primary Message with W-Bit 1 (Reply Expected), the Sender should expect a Reply message whose header meets the following requirements.•The Session ID of the Reply must match the Session ID of the Primary Message.•The Stream of the Reply must match the Stream of the Primary Message.•The Function of the Reply must be one greater than the Function of the Primary Message, or else the Function of the Reply must be 0 (Function Zero Reply).•The System Bytes of the Reply must match the System Bytes of the Primary Message.4. SEMI EQUIPMENT COMMUNICATION STANDARD 2 MESSAGE CONTENT(SECS-II).The SEMI Equipment Communication Standard Part 2 (SECS-II) defines the details of the interpretation of messages exchanged between intelligent equipment and a host.The SECS-II is intended to be fully compatible with SEMI Equipment Communication Standard E4 SECS-I. It is also the intent to allow for compatibility with alternative message transfer protocols which adhere with protocol requirements contained in E5-0703 Section 3.SECS-II gives form and meaning to messages exchanged between equipment and host usinga message transfer protocol, such as SECS-I.SECS-II defines the method of conveying information between equipment and host in the form of messages. These messages are organized into categories of activities, called functions.SECS-II defines the structure of messages into entities called items and lists of items. This structure allows for a self-describing data format to guarantee proper interpretation of the message.The interchange of messages is governed by a set of rules for handling messages called the transaction protocol. The transaction protocol places some minimum requirements on any SECS-II implementation (See E5-0703 Section 5.3).STMicroelectronics requires that all messages exchange between equipment and host comply with SEMI Standards E5-0703.For any received message that cannot be processed, the equipment must send the appropriate error message on stream 9.Upon detection of a transaction timeout, the equipment should send S9F9 to the host.Upon receipt of function 0 as a reply to a primary message, the equipment must terminate successfully the related transaction, without any error sent to the host.SECS-II must support block interleaving for multi-block messages when based on SECS-I layer.5. GEM REQUIREMENTSSTMicroelectronics requires GEM as the standard implementation of SECS-II.The equipment must be a GEM Compliant machine in the terms specified in E30 standard.This means that:• The fundamentals GEM requirements are satisfied.• Each capability is implemented to conform to all applicable definitions, descriptions, and requirements defined for the capability in E30.Regarding some GEM capabilities we want to stress the following points.1. The level of the equipment on board automation must allow for running the equipment usingSECS commands without requiring the operator intervention. However While the equipment is in production mode, the operator should still be able to intervene in case of emergency and to perform minor process related adjustments on the equipment, stop the equipment and clear the alarms.2. While running in automatic mode, regardless of the control state, any change in productionparameters and machine configuration must generate dedicated event reports that allow identification of changed parameters together with corresponding new value.3. The host system will not replace the equipment functionality via SECS, that is, it will notimplement functions that during offline or local equipment operation are performed by the equipment control software itself. SECS conversations will send requests to the equipment controller software to perform macro actions such as 'prepare to process a lot'. Micro actions, such as opening a relay or step a lifter, are not performed through the SECS interface but by the equipment control software once it has received a macro action. Moreover the host system is not expected to take on any type of equipment diagnostic or maintenance functions using the SECS interface.4. Host interface and operator interface must have the same functionality during production inremote control state: the host must be able to access the same functions an operator can access from the equipment terminal during error free operations and vice versa. Moreover, while in remote control, any command initiated by the operator must trigger the sending of a related event report.5. The equipment may supply additional functionality not specified in the GEM standard aslong as it does not conflict with compliance to GEM capabilities.For a definition of the terms fundamental requirements and capability see E30. Table 2 summarizes the GEM fundamental requirements and additional capability required for equipment types. According to the Production needs, an equipment may not be equipped with the full below defined capabilities.Table 2 GEM fundamental requirements and additional capabilityImportant: The Die Picked Event is not required if E142 is implemented. The information will be available in the Transfer Map.Important:The Enabling / disabling concept of the start button is to have the Start Button disabled as soon as the lot have done Track out or Track in cancel and to enable the Start Button only when a successful lot Track in occurs.Equipment Integration controller to enable the START button on the equipment via the SECS-II message S2F15 with the following data items:8ECID = <ECID>8ECV = <ECV>5.1 STMicroelectronics specific GEM RequirementsThis section explains some outlines, limitations and further requirements to the GEM and to the specifications of SECS-II not explicitly mentioned in the GEM standard.The supplier may define new streams and functions for custom tasks as long as he respects the standard structure and allowed stream and function codes if so all the custom Stream and Functions must be fully and clearly documented in the equipment SECS-GEM manual. However, it is strongly desirable that the supplier use the basic standard streams and functions pre-defined in E5.5.1.1 Process Program ManagementAll process programs residing on the equipment and all associated tables or data that are used while the machine is in production must be supported (downloaded/uploaded) by the "Process Program Management" capability. Moreover, the equipment of the same model must be able to share process programs and all the related tables that are required in production. (See E30-0703 Section 4.6.4)The recipe downloaded by the host while the equipment is in remote control state must be suitable to execute also if the equipment was switched to local control state and it must be shown on the equipment display i.e. the recipe must be stored and executed on the local non-volatile storage.5.1.2 Event Report NotificationNo hardcode or “canned” reports are allowed. Dynamic report configuration is required.The following collection events (CEID) are required:•Product process start.•Product process stops.•Save of a recipe on the equipment hard disk.•Change of a configuration parameter (ECID) by the machine console.•Process step start and completion (when process programs are composed of more process steps).•Process completion of a strip.•Process start of a strip.•Process completion of the product contained in an input carrier (for any type of carrier or cassette or tube or tray).•Carrier (or cassette or tube or tray) load in the input process position.•Empty carrier (or cassette or tube or tray) load in the output process position.•Carrier (or cassette or tube or tray) unloads from the output process position. •Operator command executed.•Loss of configuration.•An input buffer becomes empty (for any type of carrier, cassette, tube or tray both full and empty).•An output buffer becomes full (for any type of carrier, cassette, tube or tray both full and empty).• A material required to the process has been exhausted, for any type of material.•Unique CEIDs for each event.•CEID for maintenance and down state•CEID for production state•CEID for process state change•CEID for equipment OFF-LINEThe equipment supplier must provide documentation of all collection events defined on the equipment and the conditions for each event to occur (see E30-0703 Section 4.2.1.1.4) 5.1.3 Variable Data CollectionIt is required that any input and output parameter relevant for the process monitoring and control is available as a SECS communication Variable ID.The following VIDs are required depending on the type of process:•PPID of the last recipe saved on the equipment hard disk.•PPID of the recipe currently in process.•ECID of the last configuration parameter changed by equipment console.•StripID of the strip in process at a machine module (for each module).•ID of the carrier or cassette or tube or tray in the input process position(s).•ID of the carrier or cassette or tube or tray in the output process position(s).•Last command executed by the operator.•Device scraps (uncompleted) count in the last strip completed.•Device scraps (uncompleted) count in the strip currently in process.•Device or position skipped count in the last strip completed.•Device or position skipped count in the strip currently in process.•Device processed count in the last strip completed.•Device processed count in the strip currently in process.•Device scraps (uncompleted) count in the last carrier completed.•Device scraps (uncompleted) count in the carrier currently in process.•Device or position skipped count in the last carrier completed.•Device or position skipped count in the carrier currently in process.•Device processed count in the last carrier completed.•Device processed count in the carrier currently in process.•Strip processed count in the last carrier completed.•Strip processed count in the carrier currently in process.•Total count of good devices.•Total productive uptime.•Total standby time.•Total downtime.•Start button status enabled or disabled.If the equipment is required to handle strip / substrate mapping all Data variables stated in the SEMI standard E90, G84 or E142 must be provided.5.1.4 Establish CommunicationThe equipment may poll the host to determine if the line is still active while in the GEM communicating state. The SECS interface must include a method to disable polling and to adjust the polling interval.The Equipment must provide the Establish Communications Timeout Equipment constant as described in the Gem document E30.5.1.5 Remote ControlManual intervention must never be required to initiate any given host action. Therefore any remote command or any other host message must be accepted by the equipment regardless the status of the operator interface.As an extension of E30 chapter 4.4.4, the following remote commands must be implemented (refer to SEMI Standard document E30 to obtain detailed supporting information)1) PROCESS PROGRAM SELECTDescription: the process program is retrieved from the disk and loaded intoworking memory.2) STOPDescription: stops the equipment at the end of a safe cycle for product that is atthe end of a cycle where product is not damaged or scrapped. (Stop after currentDevice, Block or Strip depending on the product cycle).3) STOP AND CLEARDescription: stops unloading product from the input carrier, completes the processof the entire product on the equipment, loads this product in the output carrier andstops.4) STOP AND UNLOADDescription: like “STOP AND CLEAR” and unloads the input and output carriers.5) STOP NEXTDescription: completes the process of the product in the input carrier loading it intothe output carrier and stops.6) RUN ONE CARRIERDescription: starts and completes the process of the product into the input carrier,loads it into the output carrier and stops. The identification of the carriers in theinput and output process locations must NOT be a result of this command.7) IMMEDIATE STOPInstantly Equipment stops.Description:8) START BUTTON ENABLING / DISABLINGDescription: This feature is required so that the EIC is able to prevent the userfrom starting the equipment without having the necessary validations completed.5.1.6 Control State ModelAll capabilities that are available to the operator when the "local control" state is active should be available to the host when the "remote control" state is active. For each of the operator commands a specific Collection Event ID will be generated by the equipment, allowing the cell controller to track operator actions. This is a minimum requirement, while it is advisable that the operator capability level in "remote control" is configurable using equipment configuration parameters. Please, refer to E30 chapter 3.3 for details. These configuration parameters must be available also as SECS constants (ECID).5.1.7 Process state modelThe equipment supplier is required to use the GEM Processing State Model as a reference and to adopt it to the specific characteristics of the equipment.5.1.8 Alarm ManagementThe capability of clearing the pending alarms must be always available by the equipment to the operator, regardless of the communication state. As an extension of E30 chapter4.3.4, the following functionality must be implemented:•List currently set alarms.•Alarms concerning Strip Mapping.•Alarms concerning Wafer Mapping.•Alarms concerning Recipe Management.•Process Specification Alarms.•Equipment Related Alarms.The equipment manufacturer must define for the equipment a set of alarms relating to the physical safety limits of operator, equipment, or material being processed.The equipment must maintain all enable/disable states and report definitions for alarms and collection events in non-volatile memory.Each alarm defined on the equipment must have a brief description of its meaning, an associated unique alarm identifier (ALID), alarm text (ALTX), an alarm status (ALCD) and two unique collection event identifiers (CEIDs), one for set and one for cleared.Enabled alarm reports must be sent prior to corresponding enabled event reports.For each enable alarm the S5F1 message must be transmitted within 2seconds from the time at which the alarm occurred on the equipment.The equipment must continue to transmit alarm messages (S5F1) even if the control state is LOCAL.All reports states and enable/disable status of alarm must be stored in none volatile storage.All Alarms must comply with the Alarm Management GEM Standard E30 Section 4.35.1.9 Product ManagementThe equipment must always maintain the carrier integrity: strips coming from one carrier must not be loaded in a carrier containing strips coming from a different carrier. This is a mandatory capability and must not affect equipment capacity and throughput.The product can be loaded in carriers, strips, tubes or trays. It is assumed that these containers are codified using bar codes, matrix codes or other ID systems. The code to be read will be defined in a separate document which will be supplied with this specification. It may be either of CarrierID or, a StripID or, a TubeID and a TrayID.The equipment must be able to identify the product at specific equipment locations using bar code readers or other lot identification systems. It is mandatory that the equipment can identify the carriers in the input and output process locations.The equipment control software must contain a definition of machine locations where material can be stored on board. When the equipment receives product in carriers, the location should define the place where a carrier can be stored. If the equipment receives the product as single strips, the location should define the place where a strip is stored.Similar requirement applies to tubes and trays.The equipment SECS interface should be able to report the status of all the material (product) on board using the S3,F1 / S3,F2 messages. Moreover the equipment should be able to detect and report when an unexpected material is found on the equipment or an expected material has been lost. The messages to be used for this purpose are: S3,F5 / S3,F6 / S3,F7 / S3,F8.5.1.10 Data CollectionFor measurement equipment, the host must be able to change the sampling sequence (strip and die co-ordinates) regardless of the measurement recipe. In the case of re-measure the host can re-specify the sampling sequence without sending a new recipe.Different recipes must be available for selection for different carrier slots/devices.Moreover, the equipment must keep on measuring when a slot where a strip was expected is found empty. In this later case a specific Collection Event ID must be initiated by the equipment.5.1.11 SpoolingSpooling is a capability whereby the equipment can queue messages intended for the host during periods of communication failure and subsequently deliver these messages when communication is restored. Spooling is limited to primary messages of user-selected streams. Spooling on the equipment must comply with the requirements in the GEM (E30) Standard section 4.11.4.Equipment must provide a spooling capability, it must also provide the host with the ability to enable and disable Spooling for any message (except Stream 1 messages, i.e. S1,F1, S1,F13) via the S2,F43/F44 transaction. Spooling may be enabled for an entire Stream, for individual messages within a stream, or for any combination of the two. Streams and Functions not referenced in this message are not spooled. Spooling can be totally disabled by sending an S2,F43 with a zero length list for the first item.。
lx2160a-serdes-reconfiguration-user-说明书

1IntroductionThe device reference manual provides a list of all supported SerDes protocols.Only SerDes options that have been validated on silicon are documented in the reference manual. Custom SerDes configuration may be supported by reconfiguring the lanes for the desired settings if validated and approved by NXP. Any changes to configuration of default SerDes options require software reconfiguration.This document describes the sequence to reconfigure SerDes lanes from SGMII to USXGMII/XFI and two PCIe x2 lanes at Gen 1 or Gen 2 speeds for the LX2160A device. Subsequent reconfiguration from SFI/XFI to 10GBase-KR or USXGMII shall follow the sequence described in the LX2160A Reference Manual.2SerDes configuration requirementsThis document describes a use case requirement of four lanes of USXGMII/XFI and two PCIe x2 lanes at Gen 1 or Gen 2 speeds,shown as SerDes 1 protocol number 31 in Table 1. Protocol 31 is not one of the default SerDes options for the LX2160A, therefore,it is not documented in the LX2160A Reference Manual. However, standard MC firmware versions 10.24.1 and later add support for protocol 31.This document describes the sequence that results in the target configuration which can be summarized as:1.Start with SerDes protocol 11, which supports four lanes of SGMII on lanes F, E, B, and A, and two PCIe x2 lanes at Gen 3 speed on lanes H, G, D, and C.2.Reconfigure the SGMII lanes to USXGMII/XFI and limit the PCIe lanes to Gen 2 speed.3.Change the PLL assignment for USXGMII/XFI to PLLS since 10G Ethernet only runs on PLLS.4.Change the PLL assignment for PCIe to PLLF since it runs on 5 GHz VCO frequency so it cannot run on the same PLL as USXGMII/XFI.Table 1.SerDes 1 reconfigurationThe reconfiguration sequence assumes the following starting RCW settings:•SRDS_PRTCL_S1 = 5'b01011 to select protocol 11.Contents 1Introduction......................................12SerDes configuration requirements ........................................................13Software sequence.........................24RCWSR29 override. (65)Revision history (7)AN13022LX2160A SerDes 1 Lane Reconfiguration from 11 to 31Rev. 0 — 10/2020Application Note•SRDS_DIV_PEX_S1 = 2'b10 to configure PCIe to train up to a max rate of 5G (Gen 2).•SRDS_PLL_REF_CLK_SEL_S1 = 2'b mn, where m selects the reference clock for the PCIe lanes on PLLS and n selects the reference clock for USXGMII/XFI lanes on PLLF. Example:—m = 0 for 100 MHz PCIe reference clock—n = 1 for 161.1328125 MHz USXGMII/XFI reference clock•SRDS_PLL_PD_PLL1 = 0 and SRDS_PLL_PD_PLL2 = 0 so both PLLF and PLLS are powered up.•SRDS_REFCLKF_DIS_S1 = 0 to keep SD1_PLLF_REF_CLK enabled.•SRDS_INTRA_REF_CLK_S1 = 0 intra reference clock is not used.3Software sequenceThe reconfiguration sequence must be implemented in PBI and is shown below.1.Disable SGMII for lanes A, B, E, and F.•SD1: PCC8 (offset 0x10A0) = 0x0000_0000—SGMIIA_CFG = 0 disable SGMIIa—SGMIIB_CFG = 0 disable SGMIIb—SGMIIE_CFG = 0 disable SGMIIe—SGMIIF_CFG = 0 disable SGMIIf2.Enable XFI mode for lanes A, B, E, and F•SD1: PCCC (offset 0x10B0) = 0x9900_9900—SXGMIIA_XFI = 1 PCS operates in XFI/SFI mode—SXGMIIA_CFG = 001b enable SXGMIIa—SXGMIIB_XFI = 1 PCS operates in XFI/SFI mode—SXGMIIB_CFG = 001b enable SXGMIIb—SXGMIIE_XFI = 1 PCS operates in XFI/SFI mode—SXGMIIE_CFG = 001b enable SXGMIIe—SXGMIIF_XFI = 1 PCS operates in XFI/SFI mode—SXGMIIF_CFG = 001b enable SXGMIIf3.Assume 100 MHz reference clock for PLLF for the PCIe lanes•SD1: PLLFCR0 (offset 0x0404) = 0x0000_0000—REFCLK_SEL = 00000b for 100 MHz4.Configure 5G clock net frequency for PLLF•SD1: PLLFCR1 (offset 0x0408) = 0x9030_0008—SLOW_VCO_EN = 1 to enable the slower VCO—FRATE_SEL = 10000b for PCIe on PLLF—HI_BW_SEL = 1 to select higher PLL bandwidth—CLKD_RCAL_SLW_EN = 1 to enable resistor calibration for clock driver—RTMR_BYP = 1 to bypass retimer to clock driver and SSC phase interpolator—EX_DLY_SEL = 00b5.Set the recommended PLLF settings for PCIe 5G•SD1: PLLFCR3 (offset 0x0410) = 0x0000_3000—SSC_SEL = 00b no PLL modulation—SSC_SLP_OFF = 0000000000b for no slope offset—Bit 13 = 1—Bit 12 = 16.Set the recommended PLLF settings for PCIe 5G•SD1: PLLFCR4 (offset 0x0414) = 0x0000_0000—SSC_BIAS_BST = 000b SSC bias boost—SSC_SAW_MIN = 0000000000b SSC minimum sawtooth frequency offset—SSC_PI_BST = 00000b SSC phase interpolator Iqdiv2 boost—SSC_SAW_MAX = 0000000000b SSC maximum sawtooth frequency offset7.Assume 161.1328125 MHz reference clock for PLLS for 10GE operation•SD1: PLLSCR0 (offset 0x0504) = 0x0004_0000—REFCLK_SEL = 00100b for 161.1328125 MHz8.Configure 10.3125G clock net frequency for PLLS•SD1: PLLSCR1 (offset 0x0508) = 0x8610_0008—SLOW_VCO_EN = 1 to enable the slower VCO—FRATE_SEL = 00110b for XFI/SFI on PLLS—HI_BW_SEL = 0 to do not select higher PLL bandwidth—CLKD_RCAL_SLW_EN = 1 to enable resistor calibration for clock driver—RTMR_BYP = 1 to bypass retimer to clock driver and SSC phase interpolator—EX_DLY_SEL = 00b9.Set the recommended PLLS settings for XFI•SD1: PLLSCR3 (offset 0x0510) = 0x0000_3000—SSC_SEL = 00b no PLL modulation—SSC_SLP_OFF = 0000000000b for no slope offset—Bit 13 = 1—Bit 12 = 110.Set the recommended PLLS settings for XFI•SD1: PLLSCR4 (offset 0x0514) = 0x0000_1000—SSC_BIAS_BST = 000b SSC bias boost—SSC_SAW_MIN = 0000000000b SSC minimum sawtooth frequency offset—SSC_PI_BST = 00010b SSC phase interpolator Iqdiv2 boost—SSC_SAW_MAX = 0000000000b SSC maximum sawtooth frequency offset11.Change the PLL assignment for PCIe on the transmitter for lanes C, D, G, H from PLLS to PLLF•SD1: LNmTGCR0 (offsets 0x0A24 for lane C, 0x0B24 for lane D, 0x0E24 for lane G, 0x0F24 for lane H) = 0x0100_0200—USE_SLOW_PLL = 0 transmit uses PLLF—BY_N_RATE_SEL = 001b PCIe is half rate—CM_DLY_MATCH = 1 changes in LNmTRSTCTL[OUT_CM] are delay matched to changes in transmit data 12.Change the PLL assignment for PCIe on the receiver for lanes C, D, G, H from PLLS to PLLF•SD1: LNmRGCR0 (offsets 0x0A44 for lane C, 0x0B44 for lane D, 0x0E44 for lane G, 0x0F44 for lane H) =0x0100_0001—USE_SLOW_PLL = 0 receive uses PLLF—BY_N_RATE_SEL = 001b PCIe is half rate—PTRM_VCM_SEL = 01b Common mode is HiZ if PLLnRST[EN] or LNmRRSTCTL[EN] is negated.13.Change the protocol for lanes A, B, E, F from SGMII to XFI•SD1: LNmGCR0 (offsets 0x0800 for lane A, 0x0900 for lane B, 0x0C00 for lane E, 0x0D00 for lane F) =0x0000_0052—Bit 28 = 0 Must be 0 for all protocols—PORT_LN0_B = 0 Single-lane protocol—PROTO_SEL = 01010b for XFI—IF_WIDTH = 010b 20-bit interface width14.Set the PLL assignment for XFI on the transmitter for lanes A, B, E, F to PLLS•SD1: LNmTGCR0 (offsets 0x0824 for lane A, 0x0924 for lane B, 0x0C24 for lane E, 0x0D24 for lane F) =0x1000_0000—USE_SLOW_PLL = 1 transmit uses PLLS—BY_N_RATE_SEL = 000b 10G is full rate—CM_DLY_MATCH = 0 changes in LNmTRSTCTL[OUT_CM] are not delay matched to changes in transmit data15.Configure the transmit equalization for lanes A, B, E, F for XFI•SD1: LNmTECR0 (offsets 0x0830 for lane A, 0x0930 for lane B, 0x0C30 for lane E, 0x0D30 for lane F) =0x1080_8307—EQ_TYPE = 001b for 2-tap equalization—EQ_SGN_PREQ = 1 for positive sign for pre-cursor—EQ_PREQ = 0000b for 1.0x drive strength of transmit full swing transition bit to pre-cursor—EQ_SGN_POST1Q = 1 for positive sign for first post-cursor—EQ_POST1Q = 00011b for 1.14x drive strength of transmit full swing transition bit to first post-cursor—EQ_AMP_RED = 000111b for 0.585x overall amplitude reduction16.Set the PLL assignment for XFI on the receiver for lanes A, B, E, F to PLLS•SD1: LNmRGCR0 (offsets 0x0844 for lane A, 0x0944 for lane B, 0x0C44 for lane E, 0x0D44 for lane F) =0x1000_0000—USE_SLOW_PLL = 1 receive uses PLLS—BY_N_RATE_SEL = 000b 10G is full rate—PTRM_VCM_SEL = 00b Common mode impedance is always calibrated to SD_GND17.Set the recommended XFI settings for lanes A, B, E, F•SD1: LNmRGCR1 (offsets 0x0848 for lane A, 0x0948 for lane B, 0x0C48 for lane E, 0x0D48 for lane F) =0x1000_0000—RX_ORD_ELECIDLE = 0 Do not put into ordered idle state—Bit 28 = 1—ENTER_IDLE_FLT_SEL = 00b Bypass unexpected entrance into idle—EXIT_IDLE_FLT_SEL = 000b Force immediate exit from idle state AFTER order idle released and min time in idle—DATA_LOST_TH_SEL = 000b Disable loss of signal detection18.Disable receive equalization gain overrides for lanes A, B, E, F•SD1: LNmRECR0 (offsets 0x0850 for lane A, 0x0950 for lane B, 0x0C50 for lane E, 0x0D50 for lane F) =0x0000_000019.Set the recommended the receive equalization for XFI for lanes A, B, E, F•SD1: LNmRECR2 (offsets 0x0858 for lane A, 0x0958 for lane B, 0x0C58 for lane E, 0x0D58 for lane F) =0x8100_0020—Bit 31 = 1—EQ_BLW_SEL = 01b baseline wander for 10G—Bits 5:4 = 10bThe PBI sequence is shown below:.pbiwrite 0x01EA10A0,0x00000000write 0x01EA10B0,0x99009900write 0x01EA0404,0x00000000write 0x01EA0408,0x90300008write 0x01EA0410,0x00003000write 0x01EA0414,0x00000000write 0x01EA0504,0x00040000write 0x01EA0508,0x86100008write 0x01EA0510,0x00003000write 0x01EA0514,0x00001000write 0x01EA0A24,0x01000200write 0x01EA0A44,0x01000001write 0x01EA0B24,0x01000200write 0x01EA0B44,0x01000001write 0x01EA0E24,0x01000200write 0x01EA0E44,0x01000001write 0x01EA0F24,0x01000200write 0x01EA0F44,0x01000001write 0x01EA0800,0x00000052write 0x01EA0900,0x00000052write 0x01EA0C00,0x00000052write 0x01EA0D00,0x00000052write 0x01EA0824,0x10000000write 0x01EA0924,0x10000000write 0x01EA0C24,0x10000000RCWSR29 override write 0x01EA0D24,0x10000000write 0x01EA0830,0x10808307write 0x01EA0930,0x10808307write 0x01EA0C30,0x10808307write 0x01EA0D30,0x10808307write 0x01EA0844,0x10000000write 0x01EA0944,0x10000000write 0x01EA0C44,0x10000000write 0x01EA0D44,0x10000000write 0x01EA0848,0x10000000write 0x01EA0948,0x10000000write 0x01EA0C48,0x10000000write 0x01EA0D48,0x10000000write 0x01EA0850,0x00000000write 0x01EA0950,0x00000000write 0x01EA0C50,0x00000000write 0x01EA0D50,0x00000000write 0x01EA0858,0x81000020write 0x01EA0958,0x81000020write 0x01EA0C58,0x81000020write 0x01EA0D58,0x81000020.end4RCWSR29 overrideThe Reset Configuration Word Status Registers (RCWSR1:RCWSR32) are written with the RCW information that are read from flash memory by the device at power-on-reset. The RCWSR register values are read-only after exiting reset.Software (U-boot) reads the selected SerDes protocol from RCWSR29. It looks at the SerDes configuration table to find the entry for protocol 31 and its corresponding interfaces. In order for software (U-boot) to read the updated SerDes 1 protocol value of 31, the following steps must be performed:1.Add an entry for SerDes 1 protocol 31 in the SerDes configuration table in U-boot2.Override the RCWSR29 with the updated SerDes 1 protocol value of 31•Write to address 0x7_00100170 the new protocol SRDS_PRTCL_S1 = 31.•The SerDes 2 and SerDes 3 configuration fields should remain unchanged.•Note: The RCWSR29 cannot be updated from the PBI phase. The update must be done in the initial stages of the the board-specific U-boot code so that the correct SerDes protocol is read as U-boot continues execution.Table 2.Address 0x7_0010017031302928272625242322212019181716 SRDS_PRTCL_S3SRDS_PRTCL_S2SRDS_PRTCL_S1SRDS_REFCLKF_DIS_S11514131211109876543210Table continues on the next page...Table 2.Address 0x7_00100170 (continued)ReservedSRDS_PLL_P D_PLL6SRDS_PLL_P D_PLL5SRDS_PLL_P D_PLL4SRDS_PLL_P D_PLL3SRDS_PLL_P D_PLL2SRDS_PLL_P D_PLL1Any support, information, and technology (“Materials”) provided by NXP are provided AS IS, without any warranty express or implied, and NXP disclaims all direct and indirect liability and damages in connection with the Material to the maximum extent permitted by the applicable law. NXP accepts no liability for any assistance with applicationsor product design. Materials may only be used in connection with NXP products. Any feedback provided to NXP regarding the Materials may be used by NXP without restriction.5Revision historyThe table below summarizes the revisions to this document.Table 3.Revision history Revision historyHow To Reach Us Home Page: Web Support: /support Information in this document is provided solely to enable system and software implementersto use NXP products. There are no express or implied copyright licenses granted hereunderto design or fabricate any integrated circuits based on the information in this document. NXP reserves the right to make changes without further notice to any products herein.NXP makes no warranty, representation, or guarantee regarding the suitability of its products for any particular purpose, nor does NXP assume any liability arising out of the applicationor use of any product or circuit, and specifically disclaims any and all liability, includingwithout limitation consequential or incidental damages. “Typical” parameters that may be provided in NXP data sheets and/or specifications can and do vary in different applications, and actual performance may vary over time. All operating parameters, including “typicals,”must be validated for each customer application by customer's technical experts. NXP does not convey any license under its patent rights nor the rights of others. NXP sells products pursuant to standard terms and conditions of sale, which can be found at the following address: /SalesTermsandConditions.Security — Customer understands that all NXP products may be subject to unidentifiedor documented vulnerabilities. Customer is responsible for the design and operation of its applications and products throughout their lifecycles to reduce the effect of these vulnerabilities on customer’s applications and products. Customer’s responsibility also extends to other open and/or proprietary technologies supported by NXP products for use in customer’s applications. NXP accepts no liability for any vulnerability. Customer should regularly check security updates from NXP and follow up appropriately. Customer shall select products with security features that best meet rules, regulations, and standards of the intended application and make the ultimate design decisions regarding its products and is solely responsible for compliance with all legal, regulatory, and security related requirements concerning its products, regardless of any information or support that may be provided by NXP. NXP has a Product Security Incident ResponseTeam(PSIRT)(************************)thatmanagestheinvestigation, reporting, and solution release to security vulnerabilities of NXP products.NXP, the NXP logo, Freescale, the Freescale logo, CodeWarrior, Layerscape, and QorIQ are trademarks of NXP B.V. All other product or service names are the property of their respective owners. Arm and Cortex are registered trademarks of Arm Limited (or its subsidiaries) in the US and/or elsewhere. The related technology may be protected by any or all of patents, copyrights, designs and trade secrets. All rights reserved. The Power Architecture and word marks and the Power and logos and related marks are trademarks and service marks licensed by .© NXP B.V. 2020.All rights reserved.For more information, please visit: Forsalesofficeaddresses,pleasesendanemailto:**********************Date of release: 10/2020Document identifier: AN13022。
SONIX 8位单片机 SN8P2711A 用户说明书

2.1.1.1 复位向量(0000H)........................................................................................................................................... 10
2.1.3 数据存储器(RAM) ................................................................................................................................................... 16
1.1
功能特性............................................................................................................................................................................. 6
目 录................................................................................................................................................................................................ 3
2.1.1.2 中断向量(0008H)........................................................................................................................................... 11
uni-calendar中change方法

在编写这篇文章时,首先我们需要对uni-calendar中change方法进行深入的评估。
change方法是uni-calendar组件中非常重要的一个方法,它负责响应用户选择日期时的变化。
在这篇文章中,我们将从多个角度对change方法进行讨论,并深入探究其内部原理和实际应用。
1. uni-calendar中change方法的基本功能change方法是uni-calendar组件中用于响应用户选中日期变化的方法。
当用户在日历中进行日期选择时,change方法会被触发,并返回用户选择的日期信息。
这个方法的基本功能是对用户选择的日期进行处理,并将处理后的数据返回给开发者,以便进行进一步的操作。
2. change方法的参数和返回值在uni-calendar组件中,change方法通常会接受一个参数,这个参数是用户选择的日期数据。
开发者可以通过change方法中的参数,获取用户选择的具体日期信息,比如年份、月份、日期等。
而change 方法的返回值通常是经过处理的用户选择的日期数据,开发者可以根据返回的数据来进行后续的操作,比如渲染页面、修改数据等。
3. change方法的内部实现原理在uni-calendar组件中,change方法的内部实现原理通常是通过监听用户的操作,并在用户选择日期时触发相应的事件。
这个事件会调用change方法,从而将用户选择的日期信息传递给change方法进行处理。
在内部实现原理方面,change方法通常会涉及到一些数据处理、逻辑判断和事件触发等操作。
4. change方法的实际应用场景在实际开发中,change方法通常会被应用在需要用户进行日期选择的场景中。
比如在预订机票、酒店、活动等业务中,我们经常会看到日期选择的功能。
而在这些业务中,change方法就扮演了非常重要的角色,它负责处理用户选择的日期信息,并将处理后的数据传递给开发者,以便进行后续的操作。
5. 我的观点和理解就我个人而言,change方法在uni-calendar组件中的作用非常重要。
StatusChanged事件中值得注意的是

//TODO:通知用于Kinect已拔出}}break;//TODO:处理其他情况下的状态}}}上面的代码注释很详细,首先定义了一个私有变量kinect,应用程序应该定义一个私有的变量来存储对获取到的KincectSensor对象的引用,当应用程序不在需要KinectSensor产生数据时,可以使用这个局部变量来释放对KinectSensor对象的引用从而释放资源。
我们还定义了一个Kinect属性来对这个私有变量进行包装,使用属性的目的是保证能够以正确的方式初始化和反初始化KinectSensor对象。
在Set方法中我们可以看到,自由待赋值的对象的组航太是Connected的时候我们才进行赋值操作,任何将没有处在Connected状态的传感器对象复制给KinectSensor对象时都会抛出InvalidOperationException异常。
在构造函数中有两个匿名方法,一个用来监听Loaded事件,一个用来监听Unloaded事件。
当卸载时应该将Kinect属性置为空。
在窗口的Loaded事件中程序通过DiscoverKinectSensor 方法试图调用一个连接了的传感器。
在窗体的Loaded和Unloaded事件中注册这两个事件用来初始化和释放Kinect对象,如果应用程序没有找到Kinect对象,将会通知用户。
StatusChanged事件中值得注意的是,当状态为KinectSensor.Connected的时候,if语句限制了应用程序只能有一个kinect传感器,他忽略了电脑中可能连接的其他Kinect传感器。
以上代码展示了用于发现和引用Kinect设备的最精简的代码,随着应用的复杂,可能需要更多的代码来保证线程安全以及能让垃圾回收器及时释放资源以防止内存泄露。
1.2 打开传感器一旦发现了传感器,在应用程序能够使用传感器之前必须对其进行初始化。
传感器的初始化包括三个步骤。
首先,应用程序必须设置需要使用的数据流,并将其状态设为可用。
VC中GetLastErro返回的错误码

VC中GetLastErro返回的错误码〖0〗-操作成功完成。
〖1〗-功能错误。
〖2〗-系统找不到指定的⽂件。
〖3〗-系统找不到指定的路径。
〖4〗-系统⽆法打开⽂件。
〖5〗-拒绝访问。
〖6〗-句柄⽆效。
〖7〗-存储控制块被损坏。
〖8〗-存储空间不⾜,⽆法处理此命令。
〖9〗-存储控制块地址⽆效。
〖10〗-环境错误。
〖11〗-试图加载格式错误的程序。
〖12〗-访问码⽆效。
〖13〗-数据⽆效。
〖14〗-存储器不⾜,⽆法完成此操作。
〖15〗-系统找不到指定的驱动器。
〖16〗-⽆法删除⽬录。
〖17〗-系统⽆法将⽂件移到不同的驱动器。
〖18〗-没有更多⽂件。
〖19〗-介质受写⼊保护。
〖20〗-系统找不到指定的设备。
〖21〗-设备未就绪。
〖22〗-设备不识别此命令。
〖23〗-数据错误 (循环冗余检查)。
〖24〗-程序发出命令,但命令长度不正确。
〖25〗-驱动器⽆法找出磁盘上特定区域或磁道的位置。
〖26〗-⽆法访问指定的磁盘或软盘。
〖27〗-驱动器找不到请求的扇区。
〖28〗-打印机缺纸。
〖29〗-系统⽆法写⼊指定的设备。
〖30〗-系统⽆法从指定的设备上读取。
〖31〗-连到系统上的设备没有发挥作⽤。
〖32〗-进程⽆法访问⽂件,因为另⼀个程序正在使⽤此⽂件。
〖33〗-进程⽆法访问⽂件,因为另⼀个程序已锁定⽂件的⼀部分。
〖36〗-⽤来共享的打开⽂件过多。
〖38〗-到达⽂件结尾。
〖39〗-磁盘已满。
〖50〗-不⽀持⽹络请求。
〖51〗-远程计算机不可⽤。
〖52〗-在⽹络上已有重复的名称。
〖53〗-找不到⽹络路径。
〖54〗-⽹络忙。
〖55〗-指定的⽹络资源或设备不再可⽤。
〖56〗-已到达⽹络 BIOS 命令限制。
〖57〗-⽹络适配器硬件出错。
〖58〗-指定的服务器⽆法运⾏请求的操作。
〖59〗-发⽣意外的⽹络错误。
〖60〗-远程适配器不兼容。
〖61〗-打印机队列已满。
〖62〗-⽆法在服务器上获得⽤于保存待打印⽂件的空间。
〖63〗-删除等候打印的⽂件。
Oracle Exalogic Elastic Cloud X2-2 用户指南说明书

Oracle® Enterprise Manager Ops CenterEnabling Single Root Input Output Virtualization in Exalogic Elastic Cloud12c Release 1 (12.1.2.0.0)E35262-01November 2012This guide provides an end-to-end example for how to use Oracle Enterprise ManagerOps Center.IntroductionOracle Exalogic Elastic Cloud X2-2 solution includes a set of compute nodesinterconnected through QDR InfiniBand IO Fabric. In order to be able to virtualize theInfiniBand IO of Exalogic compute nodes, the Single Root Input Output Virtualization(SR-IOV) option must be enabled in BIOS.After compute node ILOM and BIOS is updated, the BIOS configuration settings of theExalogic node are set to default, leaving the SR-IOV settings disabled. For properfunctioning of the appliance, this option has to be re-enabled. You can change theSR-IOV settings in BIOS using the following procedures.■Enabling Single-Root Input Output Virtualization Using Oracle EnterpriseManager Ops Center UI■Enabling Single-Root Input Output Virtualization using ILOM CLI CommandsBoth these procedures are explained in this document.What You Will NeedYou will need the following to enable single-root input output virtualization:■ A configured Enterprise Controller■Oracle Exalogic Elastic Cloud (version 2.2 or later) installed on Oracle EnterpriseManager Ops Center■Ensure popup is enabled on the web browser■You must have the role of System Admin to enable SR-IOV actions■Login credentials to login to ILOM (administrative login credentials)Enabling Single-Root Input Output Virtualization Using OracleEnterprise Manager Ops Center UIIf Oracle Enterprise Manager Ops Center is available and fully functional, you can usethis procedure to enable single-root IO virtualization through the Oracle EnterpriseManager Ops Center UI.1.On the Navigation pane, under Assets, select a Server.2.On the Actions pane, click Launch LOM Controller. The web-based ILOM loginscreen for the asset opens.3.Enter the User Name and Password (Admin login credentials for the serviceprocessor of the asset) and click Log In.4.After logging in, click Remote Control, then click Host Control.5.In the Next Boot Device field, select BIOS.6.Click Save.7.Click the Logout button on the top right corner of the screen to logout of LOMController.■The server moves into locked state indicated by a padlock on the OS of the server.8.In the Navigation pane, under Assets, expand the Server node that you have justedited and select the hypervisor node under it.9.On the Actions pane, click Reboot Oracle VM Server Host.10.Click Reboot Oracle VM Server. The VM server is rebooted.11.On the Navigation pane, under Assets, select the server.12.In the center pane, click the Console tab, then click the Enable Console Connectionicon.■Wait until the job is complete. The BIOS menu opens.13.In the BIOS menu, using arrow keys, select Advanced, then select I/OVirtualization.14.Change the SR-IOV Supported value to Enabled.15.Press Esc key to go back to the Main menu. Using the arrow key, select Exit.16.Click OK to save the changes and exit.■The server reboots and the Operating System is started. This might take a few minutes. After the server has rebooted, the padlock icon on the OS disappearsand the OS is ready to host the virtual guests.17.Click Disable the Console Connection icon to disable the console.Enabling Single-Root Input Output Virtualization using ILOM CLI CommandsIf Oracle Enterprise Manager Ops Center is not installed, you can enable SR-IOV using ILOM CLI commands.1.Login to the ILOM console using SSH and your admin login credentials.2.Type ssh root@<xxx.xx.xx.x> to log in to the ILOM console (xxx.xx.xx.xx is the IP ofthe ILOM).Run the following commands after logging in to the server’s LDOM CLI console.1.Type set /HOST boot_device=BIOS .2.Type reset /SYS .3.Type start /SP/console .■It might take a few minutes for the BIOS menu to appear.4.In the BIOS menu, using arrow keys, select Advanced, then select I/O Virtualization.5.Change the SR-IOV Supported value to Enabled.6.Press Esc key to go back to the Main menu. Using the arrow key, select Exit.7.Click OK to save the changes and exit.The server reboots and the Operating System is started. This might take a fewminutes. After the server has rebooted, the padlock icon on the OS disappears and the OS is ready to host the virtual guests.Related Articles and ResourcesThe following chapter in the Oracle Enterprise Manager Ops Center Feature Reference Guide contains more information:Note:The ILOM CLI console IP address is read from the ECUconfiguration spreadsheet.■Oracle Exalogic Elastic CloudSee the How To library at/pls/topic/lookup?ctx=oc121&id=howtoDocumentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at/pls/topic/lookup?ctx=acc&id=docacc.Access to Oracle SupportOracle customers have access to electronic support through My Oracle Support. For information, visit /pls/topic/lookup?ctx=acc&id=info or visit /pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Oracle Enterprise Manager Ops Center Enabling Single Root Input Output Virtualization in Exalogic Elastic Cloud, 12c Release 1 (12.1.2.0.0)E35262-01Copyright © 2007, 2012, Oracle and/or its affiliates. All rights reserved.This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.。
Photochem. Photobiol. Sci. 2012, 11, 785-793

aDipartimento di Chimica, Università di Perugia, 06123 Perugia, Italy. E-mail: ortica@unipg.it bCINaM, UMR 7325 CNRS, Aix-Marseille University, France † Electronic supplementary information (ESI) available. See DOI: 10.1039/c2pp05372a
forms shift to the red, with a resulting colour modulation in a
Bacnet vs Lon

Router
Building Controller
Application Specific Controllers
BACnet 协议传输/媒体
传输 BACnet “信息”的设备间的物理连接
Ethernet Peer-to-peer CSMA/CD LAN operating at 10 Mbps or 100 Mbps
PTP
BACnet 协议传输/媒体
LonTalk Based on Neuron Chip developed by Echelon with transceiver operating at 78 KBaud or 1.2 MBaud
Twisted pair Power line carrier Wireless connections
Coax cable Twisted pair Fiberoptic cable.
BACnet 协议传输/媒体
MS/TP EIA-485 LAN which can operate at 9600, 19.2 K, 38.4 K, and 76.8 K bps. Master devices are peer devices that pass a token. Slave devices co-exist on the same wire but can only respond to Master devices. EIA-232 protocol that provides serial communications between two BACnet devices, connected continuously or via dial-up modem.
Network Database
Thermo Scientific Orion Star A325 pH Conductivity

The Thermo Scientific Orion StarA325 pH/Conductivity PortableMeter is the top choice fortesting samples anywhere.It is rugged and dependable,making it ideal for every sample,every day, everywhere.The Thermo Scientific Orion Star A325 pH/Conductivity Portable Meter is the top choice foradvanced measurements on location. Get theinformation you need quickly and easily from thelarge, backlit graphic LCD display. Informativedisplay shows individual pH/mV/RmV orconductivity/TDS/salinity/resistivity results withtemperature, or all results at once. Additionalhelpful information include electrode status,time, date, sample ID, user ID and calibrationpoints. Advanced features such as stability andaveraging options provide additional optionsallowing for laboratory accuracy everywhereyou need it.Features and Benefits• Anyone can use this meter with its plainlanguage screen prompts, soft keysthat update for easy selection and amultilanguage interface that supportsEnglish, Spanish, French, Italian, Germanand Chinese• Don’t miss a reading – AUTO-READ™ locksin the stable reading on your screen, readyindicator alerts when readings are stableand timed reading gathers data in specifictime intervals• Up to 5 point pH calibration with automaticrecognition for USA/NIST and DIN buffers• Fix pH calibration errors without a completerecalibration with calibration editing• Selectable cell constant allows for use with2- or 4-cell conductivity cells• For advanced accuracy in conductivityreadings, selectable reading referencetemperatures of 5, 10, 15, 20 or 25 °C withlinear, non-linear, nLFu or EP curve options• Choice of practical salinity or natural seawater curves for salinity readings• Linear or ISO/EN 27888 curves for TDS• Non-volatile memory holds up to 5000 datapoints with time and date stamp• Easily transfer data and keep metersoftware up-to-date with the USB andRS232 ports and complimentary dataanalysis software• Four AA batteries (included) provide over800 hours of operation or purchase theuniversal power adapter (sold separately)to use AC power• Perfectly portable, waterproof and protectedto take anywhere with a IP67-rated housing• 3 year meter replacement warranty Thermo ScientificOrion Star A325 pH/Conductivity Portable MeterNorth America 166 Cummings Center Beverly, MA 01915 USA Toll Free: 1-800-225-1480 Tel: 1-978-232-6000 *********************NetherlandsTel: (31) 033-2463887 ************************IndiaTel: (91) 22-4175-8800*************************©2011 Thermo Fisher Scientific Inc. All rights reserved. All trademarks are the property of Thermo Fisher Scientific Inc. and its subsidiaries. ROSS and the COIL tradedress are trademarks of Thermo Fisher Scientific Inc. US Patent 6,793,787.ChinaTel: (86) 21-68654588 *************************SingaporeTel: (65) 6778-6876*************************JapanTel: (81) 045-453-9175*************************AustraliaTel: (613) 9757-4300****************************Water Analysis Instruments/waterThermo Scientific Orion Star A325 pH/Conductivity Portable MeterS-STARA325-E-1011-RevBOrdering InformationFor more information, contact your local Thermo Scientific products dealer or call our customer and technical service experts at 1-800-225-1480(for the US and Canada) or visit /water .。
Update .NET Framework 3.5 on Windows 8, Windows Server 2012 R2

Update for the .NET Framework 3.5 on Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2INTRODUCTIONThis update resolves an issue that prevents the optional Microsoft .NET Framework 3.5 feature from being enabled after you install security update 2966827 or 2966828 (described in Microsoft Security Bulletin MS14-046) for the Microsoft .NET Framework 3.5.This update applies to Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.SummaryMicrosoft has released update 3005628 for the .NET Framework 3.5 on Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.∙Individual, small-business, and organizational users should use the Windowsautomatic-updating feature to install the fixes from Microsoft Update. To do this, see Get security updates automatically .∙ IT professionals should refer to the "Download information" and "Command-line switchesfor this update" sections. SymptomsAfter you install security update 2966827 or 2966828 (described in Microsoft Security Bulletin MS14-046) for the Microsoft .NET Framework 3.5 and then try to enable the optional Microsoft .NET Framework 3.5 feature in Windows Features for the first time, the feature may not be enabled.When this problem occurs, you may receive an error message that resembles one of the following.Error code Error messages0x800F0906 The source files could not be downloaded.Use the "source" option to specify the location of the files that are requiredto restore the feature. For more information on specifying a source location,see /fwlink/?LinkId=243077.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logWindows couldn't complete the requested changes.Windows couldn't connect to the Internet to download necessary files. Make surethat you're connected to the Internet, and click "Retry" to try again.Installation of one or more roles, role services, or features failed.The source files could not be found. Try installing the roles, role services,or features again in a new Add Roles and Features Wizard session, and on theConfirmation page of the wizard, click "Specify an alternate source path" tospecify a valid location of the source files that are required for theinstallation. The location must be accessible by the computer account of thedestination server.0x800F0906 - CBS_E_DOWNLOAD_FAILURE0x800F081F The source files could not be found.Use the "Source" option to specify the location of the files that are requiredto restore the feature. For more information on specifying a source location,see /fwlink/?LinkId=243077. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log0x800F081F - CBS_E_SOURCE_MISSINGError code: 0x800F081FError: 0x800F081FCauseSecurity updates 2966827 and 2966828 (described in Microsoft Security Bulletin MS14-046) for the .NET Framework 3.5 require metadata that is added to the system only when the Microsoft .NET Framework 3.5 feature is enabled. Updates that apply to the .NET Framework3.5 are meant to be installed only after the .NET Framework 3.5 feature is installed. This issue is also described in the following Microsoft Knowledge Base: 3002547 Enabling the Microsoft .NET Framework 3.5 optional Windows feature in Windows 8, Windows Server 2012, Windows 8.1, or Windows Server 2012 R2 may fail after you install security update 2966827 or 2966828ResolutionTo resolve this issue, install update 3005628.Update 3005628 will remove security update 2966827 or 2966828 from any system that does not have the .NET Framework 3.5 feature content installed and present in Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2. Going forward, security updates 2966827 and 2966828 will be offered only to applicable systems that have the .NET Framework 3.5 feature enabled.Customers who have security update 2966828 predeployed to their system by their device manufacturer or who have the security update predeployed by their system administrator by using "/StartComponentCleanup" and "/ResetBase" option of the Deployment Image Servicing and Management (DISM) tool should install update 3005628. See the "Download information" section for links to the appropriate updates.Customers who receive and install update 3005628 from Microsoft Update channels do not have to take any additional action. Individual customers or IT professionals who decide to run update 3005628 manually or within their managed environments should refer to the "Download information" and "Command-line switches for this update" sections for more information. Download informationThe following files are available for download from the Microsoft Download Center.For all supported x86-based systemsDownload the NDPFixit-KB3005628-X86.exe package now.For all supported x64-based systemsDownload the NDPFixit-KB3005628-X64.exe package now.Customers who are aware that the DISM "/StartComponentCleanup" and "/ResetBase"option was used on their system should download and install the following update:For all supported x86-based systemsDownload the Windows8.1-KB2966828-x86.msu package now.For all supported x64-based systemsDownload the Windows8.1-KB2966828-x64.msu package now.Command-line switches for this updateThere are no command line switches that are applicable to this update. The update executable must be run by using elevated administrative credentials.Restart informationThis update does not require a system restart after you apply it unless files that are being updated are locked or are being used.More informationThe information in this article applies to the following:∙The Microsoft .NET Framework 3.5 on Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.Security update patch bulletin .NET Framework for MS14-06 KB2966827 KB2966828 KB3002547 KB3005628 enabling .NET Framework 3.5PropertiesArticle ID: 3005628 - Last Review: 04/23/2015 08:27:00 - Revision: 2.2Applies to∙Microsoft .NET Framework 3.5Keywords:kbexpertiseinter kbinfo kbsecadvisory kbsecurity kbsecvulnerability kbmsifixme kbfixme KB3005628Can’t Install Microsoft .NET Framework 3.5 in Windows 8 and LaterBut there are a few people who have faced problems while installing .NET Framework 3.5. When they try to install it, they receive error messages such as the source files could not be found or downloaded, etc. These error messages contain different error codes such as 0x800F081F or 0x800F0906.To fix these problems, we posted a troubleshooting article which allows you to install .NET Framework 3.5 in Windows 8 and later without receiving any error messages:The above mentioned guide helped a lot of people and fixed the error messages but still there were a few people who were not able to install .NET Framework 3.5 in Windows 8 and later. Then an AskVG reader Patrik posted a different solution which worked for those people.Patrik: I have three Surface Pro 3 with Windows Pro 8.1 that have the same issue. .NET Framework 3.5 will not install. I've tried both via DISM, Programs and Features and via full install setup. I have tried to uninstall every single Windows update on the machine and then install via DISM, but that didn't help either. I even tried to install all three KB-updates (KB2966826-8) to see if I can uninstall them to get rid of potential dll-files that could be interfere with the .Net 3.5 setup. So I then decided to wipe it clean via Windows own restore system guide. But it didn't even work after I have done a clean Windows install. Immediately after Windows installed I tried to enable the .NET 3.5 feature, and of course DISM didn't work either. I have called MS support to get some assistance, but I guess they will call back in a few days or so. Finally, I have solved the issue after many hours. I found a setting in the local computer policy.Today in this article, we are going to share the solution given by our reader Patrik so that all Windows 8 and later users can install .NET Framework 3.5 without any problem.This solution should work for all devices whether its a Desktop PC, laptop or Surface tablet running on Windows 8, Windows 8.1 or Windows 10 operating systems.If you are also facing problems while installing .NET Framework 3.5 in Windows 8 or later, check out following method to fix the issue:1.Type gpedit.msc in RUN or Start search box and press Enter. It'll open Group Policy Editor.2. Now go to:Computer Configuration -> Administrative Templates -> System3. In right-side pane, look for "Specify settings for optional component installation and component repair" option.4.The option would be set to Not Configured. Double-click on it, set it to Enabled and enable "Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS)" option.That's it. Now try to install .NET Framework 3.5 again using Control Panel -> Programs and Features or by using DISM command and now you'll not face any problem.Attempting to Install .NET Framework 3.5 on Windows Server 2012 R2 Fails with Error Code 0x800F0906 or “the source files could not be downloaded”, even when supplying sourceCharity ShelbourneCharity ShelbourneMSFT11,886 Points 4 2 1Recent AchievementsBlog Commentator II Blog Party Starter Blog Conversation StarterView Profile29 Sep 2014 6:50 AM∙Comments 52∙LikesIn one of my prior posts, I mentioned a step required when installing .Net Framework 3.5 on Windows Server 2012 or later operating systems. Specifically, I mentioned the need to supply the source for the .Net files because this is one of the few components we do not stage to the component store on Windows Server 2012 and later. One of the bullets in the things to keep in mind section at the bottom of this blog reads:If you are attempting to install .Net Framework 3.5 on Windows Server 2012, instead of specifying the install.wim, you need to specify the Sources\SxS directory on the DVD or if providing the source, the files in the SXS directory copied from the DVD are just for .Net Framework 3.5. You can host them on a share and supply them through the GUI or through Group Policy just like any other feature.Recently one of my customers ran into an issue when attempting to install .Net Framework 3.5 on Windows Server 2012 R2 using the following command:Install-WindowsFeature –name NET-Framework-Core –source F:\sources\sxsF:\ is the mounted Windows Server 2012 R2 ISO.Yet it still failed with the following error:The request to add or remove features on the specified server failed. The source files could not be downloaded. Use the "source" option to specify the location of the files that are required to restore the feature. Error: 0x800F0906Or if you doing this via the GUI, it will look something like the following:Looking at the cbs.log file from the C:/Windows/logs/cbs directory, we see the following:2014-09-22 14:27:18, Info CBS Not able to find package:Package_78_for_KB2966828~31bf3856ad364e35~amd64~~6.3.1.4 from the cached windows update index. [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX] 2014-09-22 14:27:18, Info CBS Failed to find package:Package_78_for_KB2966828~31bf3856ad364e35~amd64~~6.3.1.4 from the index mapping [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]2014-09-22 14:27:18, Info CBS Failed to get WU category/updateID for package: Package_78_for_KB2966828~31bf3856ad364e35~amd64~~6.3.1.4 [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]2014-09-22 14:27:18, Info CBS Failed to get the category and update ID for package: Package_78_for_KB2966828~31bf3856ad364e35~amd64~~6.3.1.4, component:amd64_microsoft-windows-wpfcorecomp.resources_31bf3856ad364e35_6.3.9600.20708_en-us _a3b67b207d2057ab, file: PresentationHostDLL.dll.mui [HRESULT = 0x800f090e -CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]2014-09-22 14:27:18, Info CBS Exec: Missing files are found during staging attempt but failed to download content from WU. [HRESULT = 0x800f090e -CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]2014-09-22 14:27:18, Info CBS CommitPackagesState: Started persisting state of packages2014-09-22 14:27:18, Info CBS CommitPackagesState: Completed persisting state of packages2014-09-22 14:27:18, Info CSI 00000010@2014/9/22:19:27:18.968 CSI Transaction @0x69943b49e0 destroyed2014-09-22 14:27:18, Info CBS Perf: Stage chain complete.2014-09-22 14:27:18, Info CBS Failed to stage execution chain. [HRESULT =0x800f0906 - CBS_E_DOWNLOAD_FAILURE]2014-09-22 14:27:18, Error CBS Failed to process single phase execution. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]So why are we getting these errors despite supplying the source?We released a security update in August 2014 that updates .Net components. The security updates are as follows:KB2966828: MS14-046: Description of the security update for the .NET Framework 3.5 on Windows 8.1 and Windows Server 2012 R2: August 12, 2014KB2966827: MS14-046: MS14-046: Description of the security update for the .NET Framework 3.5 on Windows 8 and Windows Server 2012: August 12, 2014If either of these updates are installed, you will run into the above issue if your server does not have access to the Internet to pull the updated components.How do we resolve this?Since this customer’s servers do not have internet access, in their case, they did the following:1) Uninstalled the security update2) Installed .Net Framework 3.5 (which installed without error)3) Reinstalled the update==================================================================== ==============**UPDATE**A fixit package just released for this issue. Please install the update in the following article to correct this issue:/kb/3005628==================================================================== ==============Take a look at the following TechNet article for .Net Framework 3.5 deployment considerations:/en-us/library/dn482066.aspxHere’s a link to the official Knowledge Base article on this issue:https:///kb/3002547How do you keep from running into this in the future?I personally recommend that you proactively enable .Net Framework 3.5 on the server images and templates in your environment to prevent having to troubleshoot or take additional steps such as this going forward.~ Charity .net Shelbourne。
Microsoft Dynamics AX 2012 R3 运输管理(TMS)引擎实现与部署指南说明

Microsoft Dynamics AX 2012 R3Pawel Kruk May 2014This document describes the typical steps for building Transportation management (TMS) engines and utilizing them in Microsoft Dynamics AX.Implementing anddeploying Transportation management enginesContentsImplementing and deploying Transportation management engines 3 Prerequisites 3 Architectural background 3 Tutorial: Construct a Hello-World rate engine 4 Tutorial: Enable a Hello-World rate engine 7 More about TMS engine implementation 8Implementing and deploying Transportation management enginesThe Transportation management (TMS) module includes a number of extension points that let you implement custom algorithms to perform tasks that are related to the rating of transport and freight reconciliation. The implementations of the algorithms are called Transportation management engines (also referred to as TMS engines or engines). The engines are delivered as implementations of specific .NET interfaces and deployed on the Microsoft Dynamics AX Application Object Server (AOS) tier. Each Transportation management engine can be switched on and off, and it can also be tuned at runtime, based on Microsoft Dynamics AX data. Some of the most important objectives of these engines are as follows:•Calculation of transportation rate•Calculation of travel distance from point to point•Calculation of the time it takes to travel from point to point•Zone identification of addresses•Distribution of transportation charges for shipments across source document lines (also referred to as apportionment of charges).Microsoft Dynamics AX 2012 R3 includes a number of fully functional engines that are available out of the box. However, in many cases, new engines might be required in order to satisfy contract requirements. For example, there is no engine that calculates freight charge by using a particular algorithm, or an engine might be required to retrieve rating data directly from a web service provided by the carrier.This document explains the typical steps for building Transportation management engines and utilizing them in Microsoft Dynamics AX. It is targeted to engineers who want to learn how to implement and deploy custom Transportation management engines.PrerequisitesMicrosoft Visual Studio Tools for Microsoft Dynamics AX must be installed. For more information, see/en-us/library/gg889157.aspx.Architectural backgroundThe following illustration shows a simplified view of the TMS system.Within TMS, a number of operations might require some kind of data processing that is specific to a particular carrier, such as transportation rate calculation. Typically, this kind of calculation requires a lot of input data, such as the origin and delivery addresses, the size, weight, and number of packages, and the requested delivery date. For a rate shopping operation, you can track this information from the Rate route workbench form. When you initiate a rate shoppingrequest, request XML is constructed in TMS by using one of the X++ classes that are derived from TMSProcessXML_Base. The request XML is passed to the processing system encapsulated in the .NET assembly named Microsoft.Dynamics.Ax.TMS (also referred to as the TMS managed system). The further processing involves instantiation and utilization of one or more Transportation management engines. The final response from the TMS managed system consists of XML, which is interpreted into a result that is persisted in the Microsoft Dynamics AX database.The source code of the TMS managed system is available in the Microsoft Dynamics AX Application Object Tree (AOT), under the following path: \Visual Studio Projects\C Sharp Projects\Microsoft.Dynamics.AX.Tms.All of the engines that are available out of the box in AX 2012 R3 are defined within the TMS managed system itself. We recommend that all custom engines be implemented in a stand-alone assembly. This assembly should be constructed by using Visual Studio Tools for Microsoft Dynamics AX, and its project should be hosted in the AOT. The Microsoft Dynamics AX server infrastructure ensures that the actual project output is deployed to a server-binary location upon AOS startup. Microsoft Dynamics AX models are the recommended vehicles for distributing the TMS engine implementations to customers. For more information about Microsoft Dynamics AX models, see/en-us/library/hh335184.aspx.Tutorial: Construct a Hello-World rate engineFollow these steps to implement a simple rate engine.1.Follow these steps to enable debugging and hot-swapping of assemblies on the Microsoft Dynamics AX server:1.Open the Microsoft Dynamics AX Server Configuration Utility.2.Create a new configuration.3.Select the Enable breakpoints to debug X++ code running on this server and Enable the hot-swapping ofassemblies for each development session check boxes.The following illustration shows the new configuration.4.Click OK to restart the AOS service.2.From the AOT, follow these steps to open the source of Microsoft.Dynamics.Ax.TMS in a new instance of VisualStudio:1.Navigate to \Visual Studio Projects\C Sharp Projects\Microsoft.Dynamics.AX.Tms.2.On the context menu, click Edit to open Visual Studio.3.Follow these steps to add a new C# Class Library project to the solution:1.In Solution Explorer, right-click your solution node, and then click Add > New Project.2.In the C# project templates, select Class Library.3.Enter HelloWorldEngines as the project name.4.Click OK.4.In Solution Explorer, right-click the HelloWorldEngines project node, and then click Add HelloWorldEngines to AOT.5.Follow these steps to add a project-to-project reference from your project to Microsoft.Dynamics.AX.Tms:1.In Solution Explorer, right-click the HelloWorldEngines project node, and then click Add Reference.2.On the Projects tab, select Microsoft.Dynamics.AX.Tms.3.Click OK.The following illustration shows what your solution should now look like in Solution Explorer.6.Follow these steps to enable deployment of the project output to the Microsoft Dynamics AX server:1.In Solution Explorer, select the project node.2.In the Properties window, set the Deploy to Server property to Yes.The following illustration shows the project properties after this change has been made.7.Follow these steps to implement a rate engine called HelloWorldRateEngine:1.In Solution Explorer, rename Class1.cs to HelloWorldRateEngine.cs.2.Implement the HelloWorldRateEngine class.The following example shows how to implement this class.namespace HelloWorldEngines{using System;using System.Xml.Linq;using Microsoft.Dynamics.Ax.Tms;using Microsoft.Dynamics.Ax.Tms.Bll;using Microsoft.Dynamics.Ax.Tms.Data;using Microsoft.Dynamics.Ax.Tms.Utility;/// <summary>///Sample rate engine class using rating formula of quantity * factor./// </summary>public class HelloWorldRateEngine : BaseRateEngine{private const string RATE_FACTOR = “RateFactor”;private decimal rateFactor;/// <summary>///Initializes the engine instance./// </summary>/// <param name=”rateEngine”>Rate engine setup record.</param>/// <param name=”ratingDto”>Rating data transfer object.</param>public override void Initialize(TMSRateEngine rateEngine,RatingDto ratingDto){base.Initialize(rateEngine, ratingDto);RateEngineParameters parameters =new RateEngineParameters(TMSEngine.RateEngine,rateEngine.RateEngineCode);// Try to retrieve decimal value of RateFactor parameter specified// on engine setup Parametersif (!Decimal.TryParse(parameters.RetrieveStringValue(RATE_FACTOR),out rateFactor)){// Throw TMS Exception. The exception message is shown in infolog.// Additional exception data is recorded in// “Transportation system error log”throw TMSException.Create(“HelloWorldRateEngine requires definition of RateFactor parameter with valid decimal value”,TMSExceptionType.TMSEngineSetupException);}}/// <summary>///Calculates rate./// </summary>/// <param name=”transactionFacade”>The request transaction facade.</param>/// <param name=”shipment”>Rated shipment element.</param>/// <param name=”rateMasterCode”>Rate master code.</param>/// <returns>Updated rating data transfer object.</returns>public override RatingDto Rate(TransactionFacade transactionFacade,XElement shipment,string rateMasterCode){// Use extension method to sum down the item// quantity from the shipment XML elementdecimal quantity = shipment.SumDown(ElementXmlConstants.Quantity);// Retrieve or create rating elementXElement rateEntity = shipment.RetrieveOrCreateRatingEntity(this.RatingDto);// Use extension method to record rate// This method does not record additional information// like unit counts, currency etc.rateEntity.AddRate(TmsRateType.Rate, quantity * rateFactor);return this.RatingDto;}}}8.In Solution Explorer, select the HelloWorldEngines project node, and then click Add HelloWorldEngines to AOT.9.Follow these steps to deploy the engine assembly:1.In Solution Explorer, right-click your project node, and then click Deploy.2.Restart AOS.Your engine assembly is now available for use in Microsoft Dynamics AX. You can verify that HelloWorldEngines.dll is available in the following folder: [AOS installation location]\bin\VSAssemblies.Tutorial: Enable a Hello-World rate engineFollow these steps to enable the engine that you implemented and deployed in the previous tutorial.1.Follow these steps to create a rating engine in Microsoft Dynamics AX:1.Click Transportation Management > Setup > Engines > Rate engine to open the Rate engine form.2.Create a new record that refers to the engine that you created in step 4 of the previous tutorial:•Rate engine: HelloWorld•Name: Hello World Rate Engine•Engine assembly: HelloWorldEngines.dll•Engine type: HelloWorldEngines.HelloWorldRateEngineThe following illustration shows the new record.Note: Because your engine does not source any data from Microsoft Dynamics AX, you don’t need to construct andassign a rate base type for it.2.Follow these steps to specify a value for the RateFactor parameter:1.In the Rate engine form, click Parameters.2.Create a parameter record for RateFactor, and assign a value of3.Your engine is now ready for use.To test the engine, assign it to the rating profile of an active carrier, and run the rating, based on a source document that includes at least one line with a specific quantity. The total rate is computed as (Total lines quantity) * (RateFactor value). The Hello-World engine implementation is not currency-sensitive.For more information about how to associate shipping carriers with rate engines, see Set up shipping carriers and carrier groups.More about TMS engine implementation•Extension types– The following table enumerates the most important interfaces and abstract classes for building engine extensions. All these base types are defined in the Microsoft.Dynamics.Ax.Tms.Bll namespace.•User messages– To format a language-specific user message, use the Microsoft.Dynamics.Ax.Tms.TMSGlobal class that is defined in the TMS managed system. This class contains an overloaded method, called getLabel, that lets you retrieve a Microsoft Dynamics AX label in the current user language.•Language-sensitive data– The input and output XML can contain elements that carry language-sensitive data, such as dates or decimal numbers. The TMS managed system enforces that the current language of the thread is set to invariant. Use System.Globalization.CultureInfo.CurrentCulture to serialize and de-serialize XML data. •Accessing data from Microsoft Dynamics AX– A rate engine might require read or write access to the Microsoft Dynamics AX database. We highly recommend that you use proxy classes for .NET interop for interaction with tables in Microsoft Dynamics AX. For more information about proxy classes, see /en-us/library/gg879799.aspx.If you use proxy classes to interact with the Microsoft Dynamics AX database, consider using LINQ to Microsoft Dynamics AX to build and run queries. For more information about LINQ to Microsoft Dynamics AX, see/en-us/library/jj677293.aspx.Out of the box, the TMS managed system provides access to interaction with some of the TMS-specific tables by using proxy classes for .NET interop and LINQ to Microsoft Dynamics AX. You can use theMicrosoft.Dynamics.Ax.Tms.Data.AXDataRepository class to retrieve IQueryable objects for these tables.•Using the common engine data infrastructure– All the engines that are shipped out of the box with AX 2012 R3 require Microsoft Dynamics AX data in order to do the actual calculations. To reduce the cost of building engines that must source data from Microsoft Dynamics AX, the TMS system includes an implementation of a common engine data infrastructure. This feature enables the recording of engine-specific data, without the need to add new Microsoft Dynamics AX tables and build additional Microsoft Dynamics AX forms to maintain data. For more information about how to set up engine metadata, see “Transportation management engines” and “Set uptransportation management engines” under Rating setup in online Help.The TMS system defines a number of tables and Microsoft Dynamics AX forms that enable the recording of engine-specific data. This data is stored in physical table records that contain a number of generic table fields that can be reused for different purposes, depending on the specific engine implementation. For proper UI interpretation of data at runtime, metadata is recorded. For each group of data records that are used by a particular engine, a number of metadata records are required. These metadata records describe the caption, data type, lookup type, and a few other properties for each generic field that the engine is using.Use the following table to find the Microsoft Dynamics AX table that contains data and metadata for a particular type of engine.Send feedback.Microsoft Dynamics is a line of integrated, adaptable business management solutions that enables you and your people to make business decisions with greater confidence. Microsoft Dynamics works like and with familiar Microsoft software, automating and streamlining financial, customer relationship, and supply chain processes in a way that helps you drive business success. United States and Canada toll free: (888) 477-7989Worldwide: (1) (701) 281-6500/dynamics。
C#两种方式反编译修改源码(dnspy,ildasmilasm)

C#两种⽅式反编译修改源码(dnspy,ildasmilasm)⼀:背景1. 讲故事周五下午运营反馈了⼀个紧急bug,说客户那边⼀个信息列表打不开,急需解决,附带的⽇志⽂件也发过来了,看了下⽇志⼤概是这样的:⽇期:2020-11-13 12:25:45,923 线程ID:[3924] ⽇志级别:INFO 错误类:xxx property:[(null)] - 错误描述:应⽤程序出现了未捕获的异常,Message:该字符串未被识别为有效的 DateTime。
; StackTrace: 在 System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)在 System.Data.ConstNode..ctor(DataTable table, ValueType type, Object constant, Boolean fParseQuotes)在 System.Data.ExpressionParser.Parse()在 System.Data.DataExpression..ctor(DataTable table, String expression, Type type)在 System.Data.Select..ctor(DataTable table, String filterExpression, String sort, DataViewRowState recordStates)在 System.Data.DataTable.Select(String filterExpression)从异常信息可以看到,⼤概就是 DataTable.Select 的时候抛出了异常,通过调⽤堆栈追查了下代码⼤概是这样的。
public Task<DataTable> QueryDataTable(){var dt = new DataTable();dt.Columns.Add(new DataColumn("SendTime"));dt.Rows.Add(dt.NewRow()["SendTime"] = "2020/11/14");var where = $" SendTime < #{DateTime.Now.ToString()}#";var query = dt.Select(where).CopyToDataTable();}⼤坑就在这⾥,绝⼤多数时候过滤 DataTable 可以采⽤这样的写法 : SendTime < #2020/11/5#,但是客户在新加坡,全英⽂操作系统,⽽且时间格式也不知道设置成啥样了,我估计时间格式包含了类似的 #,正好⼜遇到了前后缀 # ,拆分上就出错了,导致了经典的该字符串未被识别为有效的DateTime 异常被抛出。
ISD-DEMO2360微控制器基础系统设计指南说明书

ISD-DEMO2360 User ManualThe information contained in this document is the exclusive intellectual property of Nuvoton Technology Corporation and shall not be reproduced without permission from Nuvoton.Nuvoton provides this document for reference purposes only in the design of ISD ChipCorder®microcontroller-based systems. Nuvoton assumes no responsibility for errors or omissions.All data and specifications are subject to change without notice.For additional information, please contact: Nuvoton Technology Corporation atPublication Release Date: Apr 13, 2016Contents1. Overview (3)2. Board Description (5)2.1. ISD-DEMO2360_QFN32 for QFN32 package (5)2.1.1. ISD-DEMO2360_QFN32 Jumper Description (5)2.2. ISD-DEMO2360_SOP16 for SOP16 package (6)2.2.1. ISD-DEMO2360_SOP16 Jumper Description (6)2.3. 2x5 connector pin assignment (7)3. Operation Description (7)3.1. Software Installation (7)3.2. Operation under VPE (8)4. ISD-DEMO2360 board schematic (10)4.1. ISD-DEMO2360_QFN32 schematic (10)4.2. ISD-DEMO2360_SOP16 schematic (11)5. Appendix: ISD-VPE Video Tutorial (12)6. Revision History (13)Publication Release Date: Apr 13, 20161.OverviewThe ISD2360 demo board is a small board dedicated for ISD2360 device evaluation andapplication development. The ISD2360 comes in two packages: QFN32 and SOP16, hence there are two types of demo boards for the ISD2360.-For QFN32 package: ISD-DEMO2360_QFN32 – shown in Picture 1-1 ISD-DEMO2360_QFN32-For SOP16 package: ISD-DEMO2360_SOP16 – shown in Picture 1-2Picture 1-1 ISD-DEMO2360_QFN32Picture 1-2 ISD-DEMO2360_SOPPublication Release Date: Apr 13, 2016The ISD2360 evaluation kit consists of three parts:-ISD-DEMO2360 (QFN or SOP)-ISD-ES_MINI_USB: a small interface board providing USB connection to PC-ISD-VPE2360: free downloadable GUI evaluation software for ISD2360.The ISD2360 demo board connecting to the ISD-ES_MINI_USB board, along with the ISD-VPE2360, makes up a small but complete evaluation system for ISD2360, as shown in Picture 1-3 A complete ISD2360 evaluation system.Picture 1-3 A complete ISD2360 evaluation systemPublication Release Date: Apr 13, 20162.Board Description2.1.ISD-DEMO2360_QFN32 for QFN32 package2.1.1.ISD-DEMO2360_QFN32 Jumper DescriptionJ1 – 2-pin power connector, to connect battery pack or external power supply J2 – 2-pin speaker connector directly connecting to ISD2360 PWM outputJ3 – Audio jack directly connecting to ISD2360 PWM outputJ4 – 2x5 10-pin connector connecting to ISD-ES_MINI_USB donglePublication Release Date: Apr 13, 2016J5 – Reserved, not to be used.2.2.ISD-DEMO2360_SOP16 for SOP16 package2.2.1.ISD-DEMO2360_SOP16 Jumper DescriptionJ2 – 2x5 10-pin connector connecting to ISD-ES_MINI_USB dongleJ3 – Audio jack directly connecting to ISD2360 PWM outputJ4 – 2-pin speaker connector directly connecting to ISD2360 PWM outputJ7 – Reserved, not to be used.J8 – 2-pin power connector, to connect battery pack or external power supplyPublication Release Date: Apr 13, 20162.3.2x5 connector pin assignmentThe ISD2360 demo board can be connected to ISD USB dongle via a 2x5 10-pinconnector. Table 2-1 shows the pin assignment.3.Operation Description3.1.Software InstallationSoftware DownloadThe ISD2360 user can use ISD-VPE2360 (VPE stands for Voice Prompt Editor) GUIsoftware to control the demo board, and fully evaluate the ISD2360 device.The ISD-VPE2360 software is freely downloaded from Nuvoton website, or from the link below:https:///FS/v.aspx?v=8a6e688761676eb6a4ad.During the software installation, user will be prompted for username and password. The user should email Nuvoton ChipCorder team at **********************, to requestPublication Release Date: Apr 13, 2016the username and password. In the email user should provide the detailed companyname and company address, city, including country name if outside of US. Thisinformation is required by Nuvoton to generate the username and password and tocontact the user for future software updates.System RequirementsThe ISD-VPE2360 is PC windows application software; it currently supports Windows XP, Windows 7- 32bit, and Windows 7- 64bit.3.2.Operation under VPEThe user can follow the sequence below to launch the ISD2360 VPE and start evaluating the ISD2360 chip functionality with the ISD-DEMO2360 board.-Connect a demo board to USB dongle-Plug in USB dongle into a PC USB port-Launch VPETo connect demo board with the USB dongle, both board need to face up for the connection.Please refer to Picture 3.2-1Demo board connects to USB dongle board with both boardsfacing up below.Publication Release Date: Apr 13, 2016Picture 3.2-1 Demo board connects to USB dongle board with both boards facing upPublication Release Date: Apr 13, 20164.ISD-DEMO2360 board schematic 4.1.ISD-DEMO2360_QFN32 schematicPublication Release Date: Apr 13, 20164.2.ISD-DEMO2360_SOP16 schematicPublication Release Date: Apr 13, 20165.Appendix: ISD-VPE Video TutorialThere are ISD-VPE video tutorials available online which can help users who are new to the ISD-VPE GUI software. Users can access these video tutorials using the web links below:o A Simple VPE project: https:///watch?v=BXTa7Kaux0oo A GPIO Trigger project: https:///watch?v=XVDcPGpHtkIo Record and playback project: https:///watch?v=o-L-6L3TXvcPublication Release Date: Apr 13, 20166.Revision HistoryPublication Release Date: Apr 13, 2016。
- 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。
Orion Status UpdateApril 2012Kennedy Space Center Orion Team Welcomes New ArrivalThe Orion Ground Test Vehicle arrived at NASA’s Kennedy Space Center Operations & Checkout (O&C) Facility on April 21. The vehicle traveled more than 1,800 miles from Lockheed Martin's Waterton Facility near Denver, Colo., where it successfully completed a series of rigorous acoustic, modal and vibration tests that simulated launch and spaceflight environments.The ground test vehicle will now be used for pathfinding operations at the O&C in preparation for the Orion spaceflight test vehicle's arrival this summer. The spaceflight vehicle is currently being fabricated atNASA’s Michoud Assembly Facility in New Orleans, La., and is slated for NASA’s Exploration Flight Test (EFT-1) in 2014.Orion -- the na tion’s first interplane tary spacecraft forhuman space exploration beyond low Earth orbit -- will be fully assembled and integrated on site at Kennedy Space Center , a new capability that provides significant time and cost savings. The O&C’s 90,000 square feet of air-bearing floor space and specially designed air-bearing pallets enable a small crew to effortlessly maneuver spacecraft across the factory floor. Click here to view a production operation demonstration.After pathfinding operations are completed, new backshell panels will be installed on the ground test vehicle at the O&C prior to the vehicle’s trek to Langley Research Center in Virginia for splash down testing at NASA's Hydro Impact Basin . Click here to see what the Orion ground test vehicle looks like after the backshell panels are applied to the structure.Also in the O&C, the High Efficiency Particulate Air (HEPA) wall filtering equipment was installed and powered up for the first time. The portableclean room enclosure components (pictured at left,behind the crew module) are placed throughout the O&C high bay to achieve cleanliness levels required to integrate all the elements of the Orion spacecraft. This modular system, coupled with modern energy efficient Heating, Ventilation & Air Conditioning (HVAC) and electrical systems, will further enhance cost savings for the life cycle of the facility. This system enables the 90,000-square-foot high bay to maintain the proper environments to meet the cleanliness levels required for spacecraft processing without taking on unnecessary costs associated with fixed clean room systems.There are currently about 300 employees with NASA, Lockheed Martin, USA, and Honeywell working on the Orion program at Kennedy Space Center. That number is expected to grow to 350-400 by the end of 2013 as the flight test date approaches.At Michoud Assembly Facility, the Orion team is nearingcompletion of welds on the Orion flight test vehicle using theinnovative self-reacting friction stir weld process createdcollaboratively by NASA and Lockheed Martin.Welding operations progressed on t he crew module structure(pictured at right) as the barrel-to-aft-bulkhead weld and the aftbulkhead cap weld were completed in March.The team also started the non-destructive evaluation (NDE)process and preliminary visual inspections. The remaining welds tocomplete the crew module structure include: the tunnel to forwardbulkhead weld, the forward bulkhead to cone weld, and the finalcloseout weld joining the cone section to the barrel.Fabrication of the composite service module panels also showedsignificant progress. The team completed work on the shear panels,inboard walls, and forward walls. In addition, several of the panelscompleted fiberplacement,non-destructive evaluation and trim testing. All the servicemodule panels are made of a mix of carbon and epoxylaminate and have a lightweight core, providing structuralstrength with minimal weight.The Orion crew module and service module structural elementswill be delivered to the O&C facility this summer for finalassembly and systems outfitting on the flight test vehicle.Pictured at left is fiber placement work in progress on one of theOrion service module shear panels.All photos courtesy of NASAFor more information:Linda SingletonLockheed Martin Orion Communications832-526-8089 linda.singleton@/orion or /orion。