Transfer Errors Sample Clauses

The Transfer Errors clause defines the procedures and responsibilities related to mistakes or inaccuracies that occur during the transfer of funds or assets between parties. Typically, this clause outlines the steps for identifying, reporting, and correcting such errors, and may specify timeframes for notification and resolution, as well as which party bears the risk or cost of the error. Its core function is to ensure that any transfer mistakes are addressed promptly and fairly, thereby minimizing financial loss and maintaining trust between the parties involved.
Transfer Errors. Transfer errors for isochronous errors fall into four categories: ?? transmission ?? sequence ?? time ?? system 4.3.2.3.5.1 Transmission Errors Since there is no handshake for isochronous transfers, the Host Controller can detect transmission errors for transfers only from an endpoint to the host (IN). The error may be either a CRC error, a BITSTUFFING error, or a DEVICENOTRESPONDING error. If any of these errors occurs during the transfer, the ConditionCode of PacketStatusWord[R] is set accordingly and the size field reflects the number of bytes received (up to the size of the buffer defined for the frame) and placed in the memory buffer. For a bit stuffing error, the Host Controller writes up only to the last byte received before the bit stuffing error is detected. If a transmission error is detected along with a sequence or system error, the transmission error is the one that is reported in the ConditionCode . A PID check error in the PID from an endpoint is reported with a ConditionCode of PIDCHECKFAILURE. 4.3.2.3.5.2 Sequence Errors A sequence error occurs when the endpoint sends more or less data than is expected and a transmission error is not present. If the endpoint sends more data than will fit in the specified buffer, the ConditionCode for the PacketStatusWord is set to DATAOVERRUN and the size field is set to the size of the buffer. The Host Controller writes the received data to memory up to the limit of the buffer defined for the frame. If the endpoint sends less data than defined by the buffer, the ConditionCode for the PacketStatusWord is set to DATAUNDERRUN. 4.3.2.3.5.3 Time Errors Each packet has a specific frame in which it is to be transferred. It is possible that the Host Controller cannot start or complete the transfer in the specified frame. There are two manifestations of this type of error: skipped packets and late retirement of an Isochronous TD. Skipped packets occur if the Host Controller does not process an Isochronous TD in a frame for which the Isochronous TD has data. A skipped packet is indicated when an Offset/PacketStatusWord is set to NOT ACCESSED after the Isochronous TD is retired. This indicates that the Host Controller did not process the Isochronous TD for the frame and therefore did not change the Offset to a PacketStatusWord. When the Host Controller skips the last packet of the Isochronous TD, a more significant error occurs. Since the Isochronous TD was not processed in the frame in which it should have been ret...
View SourceView Similar (4)
Transfer Errors. If we do not properly complete a Transfer or Payment on time or we made a Transfer or Payment in an amount less than you requested, our liability is limited to any related late fees or finance charges that you reasonably incur as a result, provided that, your account with the payee was otherwise current and in good standing. • Cancellation Errors. If we fail to cancel a Transfer according to your cancellation instructions or if we make a Transfer in an amount in excess of that you requested, our liability is limited to a refund of the amount erroneously paid, plus interest thereon lost as a result for the period beginning with the date on which the funds associated with such Transfer are withdrawn from your account to the date of such refund. However, in no event will this interest period exceed 60 days. • Interest. If we become liable to you for interest under this Services Agreement or other applicable law, such interest shall be calculated based upon the average Federal Funds Rate at the Federal Reserve Bank in the Federal Reserved District in which we are headquartered for each day interest is due, computed on the basis of a 360-day year.
View Source
Transfer Errors. There are several types of transfer errors that must be handled by the HC. They fall into the following categories: • transmission • sequence • system Transmission errors are errors that occur in communicating information over the USB wires and manifest themselves as CRC errors, BITSTUFFING errors, DEVICENOTRESPONDING errors. Sequence errors occur when the number of data bytes received does not match the number of bytes expected from an endpoint. System errors occur when the Host Controller has a problem resulting from the HC’s system environment that cannot otherwise be attributed to USB. 4.3.1.3.6.1 Transmission Errors For errors in this category, USB defines a policy that allows the transaction to be retried for up to three times before the transfer is failed and returned to the client. The Host Controller supports this policy with the ErrorCount field. This field is initialized to 0 by the Host Controller Driver when the General TD is queued. This field is updated after each transaction attempt. If there is no transmission error, the field is written to 0. If, however, there is a transmission error, the field is incremented. If the ErrorCount field reaches 2 (10b) and another transmission error occurs (the third error in a row), the TD is retired to the Done Queue and the endpoint is halted. Data toggle mismatches on input data are counted as transmission errors. The cause of a data toggle mismatch is either failure of the endpoint to receive an ACK or a broken device. Data received when the data toggle mismatches is discarded and never written to host memory. An error in the PID check field is counted as a transmission error and is reported with a ConditionCode of PIDCHECKFAILURE. 4.3.1.3.6.2 Sequence Errors Sequence errors occur only on reads from an endpoint to the Host Controller (IN). Sequence errors are not checked unless the data packet is received without a transmission error. There are two types of sequence errors: data overrun and data underrun. When either of these error conditions is encountered, the ConditionCode field is set accordingly, the General TD is retired, and the endpoint is halted. A data overrun error occurs when the number of bytes received from an endpoint exceeds either Maximum Packet Size or the number of bytes remaining in a General TD’s buffer. In the case of an overrun condition, the Host Controller writes to memory all of the data received up to the point where the data overrun condition was created. When the General TD...
View Source

Related to Transfer Errors

  • Payroll Errors Any payroll error resulting in insufficient payment for an employee in the bargaining unit shall be corrected, and a supplemental check issued, not later than five (5) working days after the employee provides notice to the payroll department.

  • Trade Errors The Sub-Advisor will notify the Manager of any Trade Error(s), regardless of materiality, promptly upon the discovery such Trade Error(s) by the Sub-Advisor. Notwithstanding Section 5, the Sub-Advisor shall be liable to the Manager, the Fund or its shareholders for any loss suffered by the Manager or the Fund resulting from Trade Errors due to negligence, misfeasance, or disregard of duties of the Sub Advisor or any of its directors, officers, employees, agents (excluding any broker-dealer selected by the Sub-Advisor), or affiliates. For purposes under this Section 6, “Trade Errors” are defined as errors due to (i) erroneous orders by the Sub-Advisor for the Series that result in the purchase or sale of securities that were not intended to be purchased or sold; (ii) erroneous orders by the Sub-Advisor that result in the purchase or sale of securities for the Series in an unintended amount or price; or (iii) purchases or sales of financial instruments which violate the investment limitations or restrictions disclosed in the Fund’s registration statement and/or imposed by applicable law or regulation (calculated at the Sub-Advisor’s portfolio level), unless otherwise agreed to in writing.

  • Correction of Errors Contractor shall perform, at its own cost and expense and without reimbursement from the District, any work necessary to correct errors or omissions which are caused by the Contractor’s failure to comply with the standard of care required herein.

  • BILLING ERRORS In case of errors or questions about electronic fund transfers from your share and share draft accounts or if you need more information about a transfer on the statement or receipt, telephone us at the following number or send us a written notice to the following address as soon as you can. We must hear from you no later than 60 days after we sent the FIRST statement on which the problem appears. Call us at:

  • Pricing Errors Any material errors in the calculation of net asset value, dividends or capital gain information shall be reported immediately upon discovery to the Company. An error shall be deemed "material" based on our interpretation of the SEC's position and policy with regard to materiality, as it may be modified from time to time. Neither the Trust, any Fund, the Distributor, nor any of their affiliates shall be liable for any information provided to the Company pursuant to this Agreement which information is based on incorrect information supplied by or on behalf of the Company or any other Participating Company to the Trust or the Distributor.