Command String Format Sample Clauses

Command String Format. The Core Processor issues commands to the DSPs using the first timeslot on the first buffered serial port using point-to-point HDLC protocol. Each command consists of a variable length command string, which is composed of the following fields: a command type (CMD_type) command subtype (CMD_subtype), the channel number (CMD_channel), the message length in bytes (CMD_length), and command parameters (CMD_params). o CMD_type and CMD_subtype are each 4 bits long, and together they combine for the first byte of all command messages. CMD_type is in the high nibble. o CMD_channel is one byte long for commands that are channel specific; for commands that have no associated channel, the CMD_channel field is 0 bytes long (not present). o CMDJength is one byte long for all command messages o The CMD_params field's length is variable, N one byte increments. For certain CMD3ype / CMD_subtype combinations, the CMD_params field is 0 bytes long (not present). The command string shall have one of the following structures, depending on whether the CMD_channel field is present: -------------------------------------------------------- 1 CMD_type | CMD_subtype -------------------------------------------------------- 2 CMD_channel -------------------------------------------------------- 3 CMD_length -------------------------------------------------------- 4+ CMD_params -------------------------------------------------------- Table 7-1: Command structure when CMD channel is present EVP-SRM (DSP) Software Design Specification 63 ------------------------------------------------------------------------ -------------------------------------------------------- 1 CMD_type CMD_subtype -------------------------------------------------------- 2 CMD_length -------------------------------------------------------- 3+ CMD_params -------------------------------------------------------- Table 7-2: Command structure when CMD_channel is not present
View Source

Related to Command String Format

  • Directory Assistance Service Updates 8.3.3.1 BellSouth shall update end user listings changes daily. These changes include: 8.3.3.1.1 New end user connections 3.3.1.2 End user disconnections

  • Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-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.

  • EPP query-­‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

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