General D_PDU structure Sample Clauses

General D_PDU structure. The structure of the various D_PDUs shall be as shown in Figure C-1. SYNC (16 bits) HEADER USER DATA (max 1023 bytes) DATA CRC Figure C-1 (a). Format for DATA-ONLY, DATA-ACK, EXPEDITED DATA-ONLY, NON-ARQ DATA, and EXPEDITED NON-ARQ DATA D_PDUs HEADER SYNC (16 bits) Figure C-1 (b). Format for all other D_PDU types (1, 3, 5, 6 and 15) All D_PDUs, regardless of type, begin with the same 16 bit synchronisation sequence. The 16 bit sequence shall be the 16-bit Maury-Styles sequence shown below, with the least significant bit (LSB) transmitted first: Unless specified otherwise, the order of bit transmission shall be as described in CCITT V.42 paragraph 8.1.2.2, which specifies that the least significant bit (LSB, bit 0 in the figures below) of byte 0 of all D_PDUs shall be transmitted first. The remaining bytes shall be transmitted sequentially, also beginning with the LSB of each byte. The first 34 bytes of all headers contain the same fields: a 4 bit type field, which identifies the type of D_PDU; an engineering order wire (EOW) field or MANAGEMENT message field (12 bits); an end of transmission (EOT) field (8 bits), and one byte which indicates both the size of the address field (3 bits) and the size of the header (5 bits). The last two bytes of every header are a CRC (these bytes are not included in the size of header value). The next 0 to 7 bytes of every header contain address information. Bits shall be mapped into fields in accordance with CCITT V.42, 8.1.2.3, which states that: • when a field is contained within a single octet, the lowest bit number of the field represents the lowest-order value • when a field spans more than one octet, the order of bit values within each octet progressively decreases as the octet number increases. The lowest bit number associated with the field represents the lowest-order value. Unless specified otherwise, the order of bit transmission shall be as described in CCITT V.42 paragraph 8.1.2.2, which specifies that the least significant bit (LSB, bit 0 in the figures below) of byte 0 of all D_PDUs shall be transmitted first. The remaining bytes shall be transmitted sequentially, also beginning with the LSB of each byte.
Sample 1
AutoNDA by SimpleDocs

Related to General D_PDU structure

  • Master Feeder Structure If permitted by the 1940 Act, the Board of Trustees, by vote of a majority of the Trustees, and without a Shareholder vote, may cause the Trust or any one or more Series to convert to a master feeder structure (a structure in which a feeder fund invests all of its assets in a master fund, rather than making investments in securities directly) and thereby cause existing Series of the Trust to either become feeders in a master fund, or to become master funds in which other funds are feeders.

  • Management Structure Describe the overall management approach toward planning and implementing the contract. Include an organization chart for the management of the contract, if awarded. 3.2

  • BUILDINGS AND STRUCTURES 1. Repair or retrofit of buildings less than 45 years old.

  • Changes to Fee Structure In the event of Listing, the Company and the Advisor shall negotiate in good faith to establish a fee structure appropriate for a perpetual-life entity.

  • Corporate Structure The corporate structure, capital structure and other material debt instruments, material accounts and governing documents of the Borrowers and their Affiliates shall be acceptable to the Administrative Agent in its sole discretion.

  • Classification Structure All employees working under this Agreement shall be classified according to the skill based classification structure set out in Appendix A.

  • Agreement Structure 2.1 An “Agreement” hereunder shall consist of this Master Agreement, the Schedule, and their applicable attachments and represents the complete and exclusive agreement between the Parties regarding the subject matter of the Schedule, and replaces any prior oral or written communications between the Parties relating thereto. Each Lease is effective when the Schedule containing such Lease is executed by the Parties thereto.

  • Structure of Agreement The Trust is entering into this Agreement solely on behalf of the Fund. Without limiting the generality of the foregoing: (a) no breach of any term of this Agreement shall create a right or obligation with respect to any series of the Trust other than the Fund; (b) under no circumstances shall the Advisor have the right to set off claims relating to the Fund by applying property of any other series of the Trust; and (c) the business and contractual relationships created by this Agreement, consideration for entering into this Agreement, and the consequences of such relationship and consideration relate solely to the Trust and the Fund.

  • Change in Structure Except as expressly permitted under Section 5.3, no Credit Party shall, and no Credit Party shall permit any of its Subsidiaries to amend any of its Organization Documents in any respect materially adverse to an Agent (in its capacity as such) or Lenders (in their capacities as such).

  • Organizational Structure The ISO will be governed by a ten (10) person unaffiliated Board of Directors, as per Article 5 herein. The day-to-day operation of the ISO will be managed by a President, who will serve as an ex-officio member of the ISO Board, in accordance with Article 5 herein. There shall be a Management Committee as per Article 7 herein, which shall report to the ISO Board, and shall be comprised of all Parties to the Agreement. There shall be at least two additional standing committees, the Operating Committee, as provided for in Article 8, and the Business Issues Committee, as provided for in Article 9, both of which shall report to the Management Committee. A Dispute Resolution Process will be established and administered by the ISO Board in accordance with Article 10.

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