Lines Matching full:receiver

201     as soon as the receiver NACKs a byte the transmit will stop, but the
207     This setting can be used to test how well a receiver deals with
213     without ever sending an EOM. This can be used to test how a receiver
220     and not for the final byte. The receiver should ignore the last byte in
222     same reason the whole message is typically ignored. The receiver should be
232     This command can be used to test buffer overflows in the receiver. E.g.
238     two bytes long. The receiver should ignore messages that are too short.
247     than is allowed and the receiver should respond with a Low Drive
251     because the receiver also looks for an Arbitration Lost condition in
264     a receiver will do. It might just accept it, or it might time out and
269     because the receiver also looks for an Arbitration Lost condition in
278     allowed and the receiver should return to Idle state when this is detected.
285     valid and the receiver should return to Idle state when this is detected.
288     what a receiver will do. It might just accept it, or it might time out and
295     hasn't been received yet. This command can be used to test how the receiver
303     receiver handles Low Drive conditions. Note that if this happens at bit
304     positions 0-3 the receiver can interpret this as an Arbitration Lost