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.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing iNetworks traffic to Verizon, the subtending arrangements between Verizon Tandems and Verizon End Offices 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 iNetworks, the subtending arrangements between iNetworks Tandems and iNetworks End Offices shall be the same as the Tandem/End Office subtending arrangements that iNetworks maintains for the routing of its own or other carriers’ traffic.

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

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

  • System for Award Management (XXX) Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a XXX.xxx proof of registration and Commercial and Government Entity (CAGE) number. Grantee will continue to maintain an active XXX registration with current information at all times during which it has an active award under this Agreement.

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.

  • Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:

  • Training Requirements Grantee shall:

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