Acoustic MAC layer specification Sample Clauses

Acoustic MAC layer specification. The initial Seatrac transceiver devices use UNEW’s orthogonal linear frequency modulation (OLFM) spread spectrum signalling to achieve highly reliable communication at 100bps data rate. An efficient MAC layer protocol has been developed to make maximum use of this and to facilitate the CADDY messaging and positioning protocols described in later sections. Acoustic messages always start with a synchronisation chirp (50ms linear frequency sweep) followed by a header field containing information about who sent the packet, who should receive it, how it should be responded to and the payload it contains. After the header field and optional data payload may be included that defines additional content used by higher layers in the protocol stack. Finally, after the header and payload (if included), a CRC16 checksum is used to ensure data integrity of the message. Data values are always transmitted most-significant-bit first and, in header and checksum fields, most-significant-byte first (Big Endean). Optionally, certain message types require the packet being terminated with a 50ms USBL chirp to allow for positioning information to be computed. An acoustic message uses the packet structure shown in figure 5.1. SYNC Chirp Message Header (15 bits) Payload Header (optional - 5 bits) Payload Data (up to 31 bytes) Message Checksum (16 bits) USBL Chirp (optional) Bits 14:11 10:7 6:4 3:0 The message header is a 15-bit long field (figure 5.2) that contains the following fields, and is transmitted MSB first.  DEST_ID DEST_ID is a numeric identifier representing a beacon address (Beacon ID) within the current communications setup, that the packet is intended for. On reception, the receiving beacon will examine the DEST_ID value first, and reject any messages not intended for it (aborting subsequent reception and shutting down the receiver until the next SYNC chirp). The special case value of “0x0” is used to specify “broadcast to all” packets that will be decoded by all beacons.  SRC_ID SRC_ID is a numeric identifier that specifies the address (or ID) of the beacon that is sending the packet. The special case value of “0xF” is reserved specifies the source beacon is considered “anonymous” and reserved for future use. (Possibly for protocols that automatically allocate a beacon ID address on the fly).  MSG_TYPE The MSG_TYPE field specifies how the receiver should handle the message. Valid types are…  0x0 – OWAY A One-Way message that requires no response.  0x1 – OWAYU On...
Sample 1
AutoNDA by SimpleDocs

Related to Acoustic MAC layer specification

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Class Specifications The Human Resources Division shall determine:

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

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