Hardware Signaling Pin Timing Requirements Sample Clauses

Hardware Signaling Pin Timing Requirements. ‌ Per specifications given in Ref.[2]
AutoNDA by SimpleDocs
Hardware Signaling Pin Timing Requirements. Per specifications given in Ref.[2] 2 The MSA recommends host termination resistor value of 560 Ohms, which provides the best balance of performance for both open-drain and active tri-state driver in the module. Host termination resistor values below 560Ohms are allowed, to a minimum of 250 Ohms, but this degrades active driver performance. Host termination resistor values above 560 Ohms are allowed but this degrades open-drain driver performance. The above drawings, with maximum host load capacitance of 200pF, also define the measurement set-up for module MDC timing verification. The capacitor in the drawing indicates the stray capacitance on the line. Don’t put any physical capacitor on the line. 3 MODULE MANAGEMENT INTERFACE DESCRIPTION The CFP4 module utilizes MDIO IEEE Std 802.3TM-2012 clause 45 [8] for its management interface. The CFP4 MDIO implementation is defined in a separate document entitled, “CFP MSA Management Interface Specification” [3]. When multiple CFP4 modules are connected via a single bus, a particular CFP4 module can be selected by using the Physical Port Address pins.
Hardware Signaling Pin Timing Requirements. Timing requirements for Hardware Signaling Pins can be found in Table 2-5. Table 2‐5: Timing Parameters for CFP Hardware Signal Pins Parameter Symbol Min. Max. Unit Notes & Conditions Hardware MOD_LOPWR assert t_MOD_LOPWR_assert 1 ms Application Specific. May depend on current state condition when signal is applied. See Vendor Data Sheet Hardware MOD_LOPWR deassert t_MOD_LOPWR_deassert ms Value is dependent upon module start-up time. Please see register “Maximum High-Power-up Time” in CFP MSA Management Interface Specification [7] Receiver Loss of Signal Assert Time t_loss_assert 100 µs Maximum value designed to support telecom applications Receiver Loss of Signal De-Assert Time t_loss_deassert 100 µs Maximum value designed to support telecom applications Global Alarm Assert Delay Time GLB_ALRMn_assert 150 ms This is a logical "OR" of associated MDIO alarm & status registers. Please see CFP MSA Management Interface Specification [7] for further details Global Alarm De-Assert Delay Time GLB_ALRMn_deassert 150 ms This is a logical "OR" of associated MDIO alarm & status registers. Please see CFP MSA Management Interface Specification [7] for further details Management Interface Clock Period t_prd 250 ns MDC is 4 MHz or less Host MDIO t_setup t_setup 10 ns Host MDIO t_hold t_hold 10 ns CFP MDIO t_delay t_delay 0 175 ns Initialization time from Reset t_initialize 2.5 s Transmitter Disabled (TX_DIS asserted) t_deassert 100 µs Application Specific Transmitter Enabled (TX_DIS de-asserted) t_assert 20 ms From TX-Off state.
Hardware Signaling Pin Timing Requirements. ‌ 4 Per specifications given in Ref. [2]

Related to Hardware Signaling Pin Timing Requirements

  • Screening Requirements Xxxxxx shall ensure that all prospective and current Covered Persons are not Ineligible Persons, by implementing the following screening requirements.

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

  • Monitoring Requirements This Schedule sets out the contract management requirements which are applicable to the delivery of the Services.

  • Metering Requirements Seller shall comply with all applicable rules in installing a meter appropriate for deliveries pursuant to the Full Buy/Sell or Excess Sale arrangement selected in paragraph 2.2, above, which can be electronically read daily by:

  • Trunking Requirements 7.2.2.9.1 The Parties will provide designed Interconnection facilities that meet the same technical criteria and service standards, such as probability of blocking in peak hours and transmission standards, in accordance with current industry standards.

  • Testing Requirements 12.1. Workplaces -

  • 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.

  • Web-based-WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the HTTP response for only one HTTP request. If Registry Operator implements a multiple-step process to get to the information, only the last step shall be measured. If the RTT is 5-times or more the corresponding SLR, the RTT will be considered undefined.

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