
66
Message Communications Characteristics
Section 5-2
Slice Bus
Communications
Time
(T
SL-IN
and T
SL-OUT
)
The Slice bus communications time is the time required to communicate with
an Input Unit (T
SL-IN
) or Output Unit (T
SL-OUT
) in the Slice I/O Terminal.
T
SL-IN
= 0.01 × number of input data bytes [ms]
T
SL-OUT
= 0.18 + total number of output data bytes × 0.002 [ms]
5-2
Message Communications Characteristics
5-2-1
Message Communications Time
The message communications time is the time required for a message sent to
the Slice I/O Terminal to travel over the Network and arrive at the Slice I/O
Terminal. (The message may be data from a SEND(090)/RECV(098) instruc-
tion or a FINS command from a CMND(490)/IOWR(223) instruction.)
Communications
Time to the DeviceNet
Communications Unit
Use the following equation to calculate the message communications time to
the DeviceNet Communications Unit.
Message communications time = DeviceNet communications cycle time
(T
RM
) × {(Number of message bytes + 15) ÷ 6 + 1}
The number of message bytes is the number of bytes of data after the FINS
command’s command code. The equation for the DeviceNet communications
cycle time (T
RM
) is in
5-1 Remote I/O Communications Characteristics
.
Communications
Time to the Slice I/O
Unit
If a Slice I/O Unit is the final message destination, the message communica-
tions time over the Slice bus must be added to calculate the total message
communications time. Use the following equation to calculate the message
communications time over the Slice bus.
Message communications time = T
SL
× Number of frames
Number of frames = Number of message bytes ÷ 30 (round up fractions)
Note
(1) If the CPU Unit attempts to send another message or receives a message
from another node before the message communications time has fin-
ished, the response message being sent or the message being received
from another node may be destroyed. Always perform message commu-
nications at intervals longer than the message communications time and
use message instructions (SEND(090), RECV(098), CMND(490), and
IOWR(223)). Never send messages to any one node at intervals less
than the message communications time.
If send or receive messages are destroyed, the error record will be placed
in the error history of the Master Unit. If an error occurs, read the error
history using the FINS command or monitor the error history from the
Configurator.
(2) The above equations provide find the approximate message communica-
tions time, but not the maximum time. The message communications
time will depend on the frequency of the message communications, the
load on the remote node, the communications cycle time, and other fac-
tors. For any one Master Unit, the message communications time may be
greatly increased due to heavy loads.
Summary of Contents for SMARTSLICE - 04-2008
Page 1: ...DeviceNet Communications Unit Cat No W454 E1 03 SmartSlice GRT1 DRT OPERATION MANUAL ...
Page 2: ...SmartSlice GRT1 DRT DeviceNet Communications Unit Operation Manual Revised April 2008 ...
Page 3: ...iv ...
Page 5: ...vi ...
Page 13: ...xiv ...
Page 27: ...8 Basic Operating Procedure Section 1 5 ...
Page 57: ...38 Unit Functions Section 2 3 ...
Page 101: ...82 DeviceNet Explicit Messages Appendix A ...
Page 113: ...94 Standard Models Appendix C ...
Page 115: ...96 Power Consumption Tables Appendix D ...
Page 117: ...98 I O Current Consumption Appendix E ...
Page 119: ...100 Glossary ...