Condition Code Description Clause Samples

The Condition Code Description clause defines and explains the specific codes used to indicate the status or condition of goods, services, or transactions within a contract or agreement. Typically, this clause lists each code alongside a brief description, clarifying what each code represents, such as 'delivered,' 'damaged,' or 'pending.' By providing clear definitions for each condition code, the clause ensures all parties interpret these codes consistently, reducing misunderstandings and facilitating accurate communication and record-keeping.
Condition Code Description. For General TDs, the condition codes in ConditionCode have meaning to software only if the General TD is on the Done Queue. For CRC, BITSTUFFING, and DEVICENOTRESPONDING errors, the General TD is not moved to the Done Queue unless errors are encountered in three successive accesses of the device (error does not have to be the same in all three attempts.) For STALL, DATAOVERRUN, or DATAUNDERRUN, the General TD is moved to the done queue on the first occurrence of the error. BUFFEROVERRUN or BUFFERUNDERRUN are not used for General TDs. When a General TD is moved to the done queue with the ConditionCode set to other than NOERROR, the Halted bit in the ED for the endpoint is set to halt processing of General TDs for the endpoint until software clears the error condition. For an Isochronous TD, condition codes appear in two places: in ConditionCode of Dword0 and in each of the Offset/PacketStatusWords. For each data packet processed, the Host Controller converts OffsetR into PSWR by setting the ConditionCode field. All condition codes are valid for a PacketStatusWord. The ConditionCode in Dword0 of the Isochronous TD is set when the TD is moved to the done queue. The Isochronous TD can be moved to the done queue when the last data packet is transferred (in which case the ConditionCode will be NOERROR) or due to the frame for the last data packet having passed (in which case the ConditionCode will be DATAOVERRUN.) In no case does the Host Controller set the Halted bit in the ED for an Isochronous TD. An Isochronous TD with a NOERROR ConditionCode may contain PacketStatusWords with ConditionCodes other than NOERROR.
View SourceView Similar (2)

Related to Condition Code Description

  • Site Description {Buyer Comment: Provide a legal description of the Site, including the Site map.}

  • System Description The wet detention basin is designed to trap 80% of sediment in runoff and maintain pre-development downstream peak flows. The basin has two forebays (smaller ponds) located at the low end of two grass ▇▇▇▇▇▇. In addition to runoff conveyance, the grass ▇▇▇▇▇▇ also allow infiltration and filtering of pollutants, especially from smaller storms. The forebays are each 4 feet deep. They are connected to the main pool by 18 and 24-inch metal pipes that outlet onto a rock chute. The forebays will trap coarse sediments in runoff, such as road sands, thus reducing maintenance of the main basin. The main pool will trap the finer suspended sediment. To do this, the pond size, water level and outlet structures must be maintained as specified in this Agreement (see Figures 1, 2 and 3). The main basin receives runoff from a 67.1 acre drainage area (41.2 acres within the subdivision and 25.9 acres off- site drainage coming from the east). During high rainfall or snow melt events, the water level will temporarily rise and slowly drain down to the elevation of the control structure. The water level is controlled by a 12-inch concrete pipe extending through the berm in the northwest corner of the basin (see Figures 1 and 3). On the face of the 12- inch pipe, there is metal plate with a 3-inch drilled hole (orifice) with stone in front of it. This orifice controls the water level and causes the pond to temporarily rise during runoff events. Washed stone (1-2” diameter) is placed in front of the orifice to prevent clogging. High flows may enter the grated concrete riser or flow over the rock lined emergency spillway. “As-built” construction drawings of the basin, showing actual dimensions, elevations, outlet structures, etc. will be recorded as an addendum(s) to this agreement within 60 days after Waukesha County accepts verification of construction from the project engineer.

  • Work Description T-804 Opening Roads - Removal of closure devices, cleaning ditches, removing berms, and blading the traveled-way T-811 Closing Roads - Entrance treatment for 150' cross-rip; debris block (slash, earth, berm, rocks, etc.) + seed + water bar T-811 Closing Roads - Water bar frequency per BMPs for remainder of road T-811 Closing Roads - Engineering Rep. or Construction Inspector must be notified prior to performing closeout 9314A Single Lane / Level 1 NFSR 9314 0.00 END 0.20

  • Long Description (If Applicable Training to provide the knowledge, skills and abilities needed as a result of agency mission, policies, or procedures. . Training to acquire the knowledge, skills and abilities needed as a result of assignment to new duties and responsibilities when such training is not part of a planned, career development program (e.g., training provided to a staffing specialist who has been newly assigned to a position involving classification duties).

  • Task Description This task includes activities associated with permit-required monitoring conducted in accordance with the conditions specified by state or federal regulatory agencies. All monitoring tasks must be located within or adjacent to the Project area and follow the Department’s Regional Coastal Monitoring Program and FWC's marine turtle and shorebird monitoring programs. Guidance for monitoring of nearshore resources is available in the Department's Standard Operation Procedures For Nearshore Hardbottom Monitoring Of Beach Nourishment Projects. The Local Sponsor must submit work products directly to the appropriate state or federal regulatory agencies in accordance with permit conditions to be eligible for reimbursement under this task, unless otherwise directed.