Hardware Control Pins Sample Clauses

Hardware Control Pins. ‌ The CFP4 Module supports real-time control functions via hardware pins, listed in Table 1-1. Specifications of the CFP4 hardware control pins are given in Ref.[1], with the following changes listed below. Table 1-1: Control Pins‌ Pin # Symbol Description I/O Logic “H” “L” Pull-up /down 11 TX_DIS (PRG_CNTL) Transmitter Disable (Optionally configurable as Programmable Control after Reset1) I 3.3V LVCMOS Disable2 Enable2 Pull – Up3 14 MOD_LOPWR Module Low Power Mode I 3.3V LVCMOS Low Power Enable Pull – Up3 16 MOD_RSTn Module Reset, Active Low (invert) I 3.3V LVCMOS Enable Reset Pull – Down4 1 When Programmable Control is configured, MSA Default is TXDIS. 2 Per CFP MSA Management Interface Specification [3] when PRG_CNTL is configured for this pin.
Sample 1Sample 2Sample 3See All (9)
AutoNDA by SimpleDocs
Hardware Control Pins. The CFP2 Module supports real-time control functions via hardware pins, listed in Table 2-1. Specifications of the CFP2 hardware control pins are given in Ref. [1], with the following changes listed below.
Sample 1Sample 2See All (4)
Hardware Control Pins. The CFP2 Module supports real-time control functions via hardware pins, listed in Table 2-1. Specifications of the CFP2 hardware control pins are given in Ref. [1], with the following changes listed below. Table 2-1: Control Pins Pin # Symbol Description I/O Logic “H” “L” Pull-up /down Programmable Control 1 17 PRG_CNTL1 MSA Default: TRXIC_RSTn, TX & RX ICs reset, I 3.3V LVCMOS Pull – Up2 "0": reset, "1"or NC: enabled per CFP MSA MIS Ref. [7] 18 PRG_CNTL2 Programmable Control 2 MSA Default: Hardware Interlock LSB I 3.3V LVCMOS Pull – Up2 19 PRG_CNTL3 Programmable Control 3 MSA Default: Hardware Interlock MSB I 3.3V LVCMOS Pull – Up2 24 TX_DIS Transmitter Disable I 3.3V LVCMOS Disable Enable Pull – Up2 26 MOD_LOPWR Module Low Power Mode I 3.3V LVCMOS Low Power Enable Pull – Up2 28 MOD_RSTn Module Reset, Active Low (invert) I 3.3V LVCMOS Enable Reset Pull – Down3 2Pull-Up resistor (4.7 kOhm to 10 kOhm) is located within the CFP2 module 3Pull-Down resistor (4.7 kOhm to 10 kOhm) is located within the CFP2 module
Sample 1Sample 2
Hardware Control Pins. Functional Description‌
Sample 1Sample 2
Hardware Control Pins non-MDIO The CFP Module supports alarm, control and monitor functions via hardware pins and via an MDIO bus. Upon module initialization, these functions are available. The CFP uses pins in the electrical connector for control signals, listed in Table 2-1: Control Pins. Table 2-1: Control Pins
Sample 1
Hardware Control Pins. Functional Description Per specifications given in CFP MSA Hardware Specification, Revision 1.4, June 7, 2010 [1] except as noted below.
Sample 1
Hardware Control Pins. FUNCTIONAL DESCRIPTION‌
Sample 1
AutoNDA by SimpleDocs

Related to Hardware Control Pins

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process.

  • Quality Control Plan Within forty five (45) days after the design development documents are approved, the Design-Builder shall develop a quality control plan for the Project (the “Quality Control Plan”). A draft of the Quality Control Plan shall be submitted to the Department and shall be subject to the Department’s review and approval. The Quality Control Plan shall be tailored to the specific products/type of construction activities contemplated by the GMP Basis Documents, and in general, shall include a table of contents, quality control team organization, duties/responsibilities of quality control personnel, submittal procedures, inspection procedures, deficiency correction procedures, documentation process, and a list of any other specific actions or procedures that will be required for key elements of the Work.

  • Quality Control Program The Contractor shall describe the Quality Control Program in a written document which shall be reviewed by the Engineer prior to the start of any production, construction, or off-site fabrication. The written Quality Control Program shall be submitted to the Engineer for review at least ten (10) calendar days before the start of construction. The Quality Control Program shall be organized to address, as a minimum, the following items:

  • Local Number Portability Database 10.6.1 The Permanent Number Portability (PNP) database supplies routing numbers for calls involving numbers that have been ported from one local service provider to another. BellSouth agrees to provide access to the PNP database at rates, terms and conditions as set forth by BellSouth and in accordance with an effective FCC or Commission directive.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • PERFORMANCE MANAGEMENT SYSTEM 5.1 The Employee agrees to participate in the performance management system that the Employer adopts or introduces for the Employer, management and municipal staff of the Employer.

  • Local Health Integration Networks and Restructuring In the event of a health service integration with another service provider the Employer and the Union agree to meet.

Time is Money Join Law Insider Premium to draft better contracts faster.