Lines Matching refs:receiver

197     as soon as the receiver NACKs a byte the transmit will stop, but the
203     This setting can be used to test how well a receiver deals with
209     without ever sending an EOM. This can be used to test how a receiver
216     and not for the final byte. The receiver should ignore the last byte in
218     same reason the whole message is typically ignored. The receiver should be
228     This command can be used to test buffer overflows in the receiver. E.g.
234     two bytes long. The receiver should ignore messages that are too short.
243     than is allowed and the receiver should respond with a Low Drive
247     because the receiver also looks for an Arbitration Lost condition in
260     a receiver will do. It might just accept it, or it might time out and
265     because the receiver also looks for an Arbitration Lost condition in
274     allowed and the receiver should return to Idle state when this is detected.
281     valid and the receiver should return to Idle state when this is detected.
284     what a receiver will do. It might just accept it, or it might time out and
291     hasn't been received yet. This command can be used to test how the receiver
299     receiver handles Low Drive conditions. Note that if this happens at bit
300     positions 0-3 the receiver can interpret this as an Arbitration Lost