Module org.refcodes.serial
Package org.refcodes.serial

Interface ReadyToReceiveTransmission

All Superinterfaces:
EnquiryStandbyTimeMillisAccessor, org.refcodes.mixin.LengthAccessor, ReadyToReceiveMagicBytesAccessor, ReadyToReceiveRetryNumberAccessor, ReadyToReceiveSegmentPackagerAccessor, ReadyToReceiveTimeoutMillisAccessor, org.refcodes.mixin.Resetable, org.refcodes.schema.Schemable, Serializable, Transmission
All Known Implementing Classes:
AbstractReadyToReceiveTransmissionDecorator, ReadyToReceiveSectionDecorator, ReadyToReceiveSegmentDecorator
public interface ReadyToReceiveTransmission extends EnquiryStandbyTimeMillisAccessor, ReadyToReceiveMagicBytesAccessor, ReadyToReceiveRetryNumberAccessor, ReadyToReceiveSegmentPackagerAccessor, ReadyToReceiveTimeoutMillisAccessor, Transmission
The ReadyToReceiveTransmission interface defines functionality for achieving a RTR "software" handshake between a receiver having the active RTR ("ready-to-receive") role and a transmitter being CTS ("clear-to-send") where the transmitter waits for a RTR signal from the receiver (the receiver signals to be ready for receiving data by issuing an RTR signal to the transmitter): TRANSMITTER RECEIVER | | Wait till enquiry-timeout | | Send RTR magic-bytes for RTR magic-bytes |←-----RTR------| Try RTR retry-number of times | | Wait till RTR retry-timeout/retry Send payload upon RTR | | magic-bytes or break-out |----PAYLOAD---→| Receive payload upon enquiry-timeout | | Handshake specific signals are only transmitted through the return channel, the data channel is only used indirectly for handshaking by transporting the payload data in response to the return channel signals. No handshake specific signals are transmitted through the data channel, so in case there is no return channel, the ReadyToReceiveTransmission behaves invisible.