Motorola 68P02958C00-B - Manual (Page 106)

Site Configuration
5-49
Data frames are the information stored in Txbuf in case of transmission, and in Rxbuf in case
of reception.
RTU-to-RTU Number of TX retries <0-20> [1]:
The number of retries that should take place at source/destination level if an answer was not
received for a transmission via SndFrm (and not via TxFrm).
RTU-to-RTU Interval between TX retries <1-1000> Sec [60]:
The interval of time that should elapse between retries. This period of time starts after the Data
Link layer of the MDLC protocol finalizes the transmission of a frame (that is, after it received
an appropriate ACK or exhausted all retries at From/To level).
RTU-to-RTU Password <Enable/Disable> [Enable]:
Enables the user to add a communication password to data frames. The value of this parameter
must be identical in both the transmitting and receiving side.
RTU-to-RTU Authentication <Enable/Disable> [Enable]:
For future use.
Event and Burst
Event and Burst Number of boxes <1-31> [8]:
The number of boxes allocated at any given time for transmitting data frames via the Burst and
TxEvnt functions.
Event and Burst Number of TX retries <0-20> [1]:
Number of retries to be performed by the RTU towards the central unit, if it does not receive
“Application Data-Ack from central” to Burst or TxEvnt calls. If the value of the “Application
Data-Ack from central” is NO, this parameter is irrelevant (because the system relies on ACK
at Data Link level, that is, at From/To level, and does not need any further acknowledgments
at RTU/Central Unit level).
Event and Burst Interval between TX retries <1-1000> Sec [60]:
The interval of time that should elapse between two retries from the RTU towards the central
unit. (Retries may be requested if the RTU does not receive “Application Data-Ack from
central” to Burst or TxEvnt calls. See previous parameter.)
This period of time starts after the Data Link layer of the MDLC protocol finalizes the
transmission of a frame (that is, after it has received an appropriate ACK or exhausted all
retries at From/To level).
If the value of the “Application Data-Ack from central” is NO, this parameter is irrelevant
(because the system relies on ACK at Data Link level, that is, at From/To level, and does not
need any further acknowledgments at RTU/Central Unit level).
Event and Burst Application Data-Ack from central [YES]:
The valid values are: