Specify the Communication Details

If	Then
The I/O configuration of the controller has the module that gets the message.	Browse to select the module.
The I/O configuration of the controller has only the local communication module.	Browse to select the local communication module and type the rest of the path.
The I/O configuration of the controller does not have any of the modules required for the message.	Type the path.

Where	Is
	For this network	Type
Port	Backplane	1
	DF1 (serial, serial channel 0)	2
	ControlNet
	EtherNet/IP
	DH+ channel A
	DH+ channel B	3
	DF1 channel 1 (serial channel 1)
Next_address	Backplane	Slot number of the module
	DF1 (serial)	Station address (0-254)
	ControlNet	Node number (1-99 decimal)
	DH+	8# followed by the node number (1-77 octal) For example, to specify the octal node address of 37, type 8#37.
	EtherNet/IP	Specify a module on an EtherNet/IP network by using any of these formats: IP address. For example, 10.10.10.10 IP address:Port. For example, 10.10.10.10:24 DNS name. For example, tanks DNS name:Port. For example, tanks:24

This functionality for RSLogix 5000 software, beginning with version 18, enhances the ability to define the route and message type that are required to send a message to its destination.

On the
Controller Organizer
, right-click
Controller
, and select
Properties
. The
Controller Properties
dialog box appears.
Click the
System Protocol
tab.
Select
DF1 Master
in the
Protocol
box. The Polling mode defaults ‘Message Based’ (slave can initiate messages).
Click
OK
.
In ladder logic, click the box inside the MSG tag. The
Message Configuration
dialog box appears with the
Configuration
tab open.
In the
Message Type
box, select
CIP Data Table Write
.
Click
OK
.You have enabled the
Broadcast
button on the
Communication
tab.
Click the
Communication
tab.
Next to the
Broadcast
button, select a channel in the combo box. The number of channels in the combo box depends on the controller.
When you select channel 0 or 1, the corresponding message path on the
Message Configuration
dialog box defaults to 2,255 (channel 0) or 3,255 (channel 1). The Path grays out to not allow you to manually enter a path value.
Click
OK
.

Create or open an existing controller in the application.
On the
Controller Organizer
, right-click the controller name, and select
Properties
.The
Controller Properties
dialog box appears.
If you controller has a serial port, click
System Protocol
tab.

In the Protocol box, select a protocol.
IMPORTANT:
The
Message Type
box on the
Message Configuration Tab
dialog box must be write-typed to be compatible with the system protocol. Otherwise, the
Broadcast
button is disabled.
Enter the information on the
System Protocol
tab for each protocol outlined in the following tables.
Topic	Description
Protocol	DF-1 Master
Station Address	Type controller station address number
Transmit Retries	3
ACK Timeout	50
Reply Message Wait	5
Polling Mode	Select from the following modes: Message Based Poll the slave using message instruction Slave can initiate message for slave to slave broadcast Standard . to have the schedule poll for the slave
Error Detection	BCC
Duplicate Detection	Enabled (checked)
Topic	Description
Protocol	DF-1 Slave
Station Address	Type controller station address number
Transmit Retries	3
Slave Poll Timeout	3000
EOT Suppression	Disable (unchecked)
Error Detection	BCC
Duplicate Detection	Enabled (checked)
Topic	Description
Protocol	DF-1 Slave
Station Address	Type controller station address number
Enable Store and Forward	Enable box (checkmark) to use store and forward tag
Error Detection	BCC
Click
OK
.

For block-transfers over this network:	Add these modules to the I/O configuration:
ControlNet	Local communication module (for example, 1756-CNB module) Remote adapter module (for example, 1771-ACN module)
Universal remote I/O	Local communication module (for example, 1756-DHRIO module) One remote adapter module (for example, 1771-ASB module) for each rack, or portion of a rack, in the chassis Block-transfer module (optional)

If the destination device is	Select	And specify
Logix 5000 controller	CIP	No other specifications required.
PLC-5 controller over an EtherNet/IP network
PLC-5 controller over a ControlNet network
SLC 5/05 controller
PLC-5 controller over a DH+ network	DH+	Channel	Channel A or B of the 1756-DHRIO module that is connected to the DH+ network.
SLC controller over a DH+ network		Source Link	Link ID assigned to the backplane of the controller in the routing table of the 1756-DHRIO module. The source node in the routing table is automatically the slot number of the controller.
PLC-3 processor		Destination Link	Link ID of the remote DH+ link where the target device resides.
PLC-2 processor		Destination Node	Station address of the target device, in octal.
		If there is only one DH+ link and you did not use the RSLinx Classic software to configure the DH/RIO module for remote links, specify 0 for both the Source Link and the Destination Link.
Application on a workstation that is receiving an unsolicited message routed over an EtherNet/IP or ControlNet network through RSLinx Classic or FactoryTalk Linx software	CIP with Source ID This lets the application receive data from a controller.	Source Link	Remote ID of the topic in RSLinx Classic software, or the shortcut in FactoryTalk Linx .
		Destination Link	Virtual Link ID set up in RSLinx Classic or FactoryTalk Linx software (0…65535).
		Destination Node	Destination ID (0…77 octal) provided by the application to RSLinx Classic or FactoryTalk Linx . For a DDE topic in RSLinx Classic , use 77.
		The slot number of the ControlLogix controller is used as the Source Node.
Block transfer module over a universal remote I/O network	RIO	Channel	Channel A or B of the 1756-DHRIO module that is connected to the RIO network.
		Rack	Rack number (octal) of the module.
		Group	Group number of the module.
		Slot	Slot number of the module.
Block transfer module over a ControlNet network	ControlNet	Slot	Slot number of the module.

Message type:	Communication method:	Uses a connection:
CIP data table read or write		Your option(1)
PLC-2, PLC-3, PLC-5, or SLC (all types)	CIP CIP with Source ID
	DH+	X
CIP generic		Your option(2)
Block-transfer read or write		X

CIP data table read or write messages can be connected or unconnected. For most applications,
Rockwell Automation
recommends that you leave CIP data table read or write messages connected.
CIP generic messages can be connected or unconnected. But, for most applications, we recommend you leave CIP generic messages unconnected.

If you:	Then:
Cache the connection	The connection stays open after the MSG instruction is done. This optimizes execution time. Opening a connection each time the message executes increases execution time.
Do not cache the connection	The connection closes after the MSG instruction is done. This frees up that connection for other uses.

If you have this controller:	Then you can cache:
CompactLogix 5370 or ControlLogix 5570	Up to 32 connections.
ControlLogix 5580	Up to 256 connections.

If the MSG instructions are to:	And they are:	Then:
Different devices		Each MSG instruction uses 1 connection.
Same device	Enabled at the same time	Each MSG instruction uses 1 connection.
	NOT enabled at the same time	The MSG instruction uses 1 connection and 1 cached buffer. They share the connection and the buffer.

Guideline	Details
For each MSG instruction, create a control tag.	Each MSG instruction requires its own control tag.
	Data type = MESSAGE
	Scope = controller
	The tag cannot be part of an array or a user-defined data type.
Keep the source and/or destination data at the controller scope.	A MSG instruction can access only tags that are in the Controller Tags folder (controller scope).
If your MSG is to a device that uses 16-bit integers, use a buffer of INTs in the MSG and DINTs throughout the project.	If your message is to a device that uses 16-bit integers, such as a PLC-5 or SLC 500 controller, and it transfers integers (not REALs), use a buffer of INTs in the message and DINTs throughout the project.
	This increases the efficiency of your project because Logix controllers execute more efficiently and use less memory when working with 32-bit integers (DINTs).
	To convert between INTs and DINTs, see the Logix 5000 Controllers Common Procedures Programming Manual, publication 1756-PM001.
Cache the connected MSGs that execute most frequently.	Cache the connection for those MSG instructions that execute most frequently, up to the maximum number permissible for your controller revision. This optimizes execution time because the controller does not have to open a connection each time the message executes.
For the CompactLogix 5370 or ControlLogix 5570 controllers , if you want to enable more than 16 MSGs at one time, use some type of management strategy. For the ControlLogix 5580 controllers, if you want to enable more than 256 MSGs at one time, use some type of management strategy.	For the CompactLogix 5370 or ControlLogix 5570 controllers, if you enable more than 16 MSGs at one time, some MSG instructions may experience delays in entering the queue. For the ControlLogix 5580 controllers, if you enable more than 256 MSGs at one time, some MSG instructions may experience delays in entering the queue. To help make sure that each message executes, use one of these options:
	Enable each message in sequence.
	Enable the messages in groups.
	Program a message to communicate with multiple devices. For more information, see the Logix 5000 Controllers Common Procedures Programming Manual, publication 1756-PM001.
	Program logic to coordinate the execution of messages. For more information, see the Logix 5000 Controllers Common Procedures Programming Manual, publication 1756-PM001.
(For the CompactLogix 5370 or ControlLogix 5570 controllers only) Keep the number of unconnected and uncached MSGs less than the number of unconnected buffers.	The controller can have 10…40 unconnected buffers. The default number is 10 for the CompactLogix 5370 or ControlLogix 5570 controllers.
	If all the unconnected buffers are in use when an instruction leaves the message queue, the instruction errors and does not transfer the data.
	You can increase the number of unconnected buffers (40 max), but continue to follow guideline 5.
	To increase the number of unconnected buffers, see the Logix 5000 Controllers Common Procedures Programming Manual, publication 1756-PM001.