PLC5 read in Logix5000 msg

[mwiggins]

I am trying to to a PLC 5 read in a Logix 5000 to get data from a PLC 5. I am confused about the routing. Could anyone help.

I have it set up as PLC 5 Type read in the Configuration Tab. The number of elements is 1.

I am trying to configure the routing in the Communication tab.

Here is my path.

Logix processor
Backplane
slot 2 1756 DHRIO Chnl B Link 2
DH+
Node 70 1756 DHRIO Slot 2 Chnl A Link 7
Backplane
Slot 3 1756 DHRIO Chnk B Link 4
DH+
Node 35 PLC 5 Processor

Any hints on the routing would be appreciated. I know I must be missing something simple.


Thanks
Marty

 

[djs]

Hello;
I think you might try 2,3,70,1,3,3,35

 

[djs]

Hello;
In Rslogix 5000 help:

When you configure a MSG instruction, you specify these details on the Communication tab:

Specify a path

The path describes the route the message takes to get to the destination. It uses either names from the I/O configuration, numbers you type, or both:

If: Then:
The I/O configuration of the controller has the module that gets the message. Click the Browse button to select the module.
The I/O configuration of the controller has only the local communication module. Click the Browse button to select the local communication module and type the rest of the path.
The I/O configuration of the controller doesn’t have any of the modules you need for the message. Type the path.
To type a path, use this format:
port, next_address, port, next_address

Where: For this: Is:
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 network You can specify a module on an EtherNet/IP network using any of these formats:§ IP address (e.g., 10.10.10.10)§ IP addressort (e.g., 10.10.10.10:24)§ DNS name (e.g., tanks)§ DNS nameort (e.g., tanks:24)
For block transfer messages, add the following modules to the I/O configuration of the controller.

For block transfers over the network: Add these modules to the I/O configuration:
ControlNet § local communication module (e.g., 1756-CNB module)§ remote adapter module (e.g., 1771-CAN module)
universal remote I/O § local communication module (e.g., 1756-DHRIO module)§ one remote adapter module (e.g., 1771-ASB module) for each rack, or portion of a rack, in the chassis§ block transfer module (optional)
Example 1: Sample path over ControlNet

Path: peer_controller, where peer_controller is the name of the controller that receives the message.

Example 2: Sample path over EtherNet/IP

Path: Local_ENB,2,17.127.127.12

Where: Is the:
Local_ENB name of the 1756-ENBx module in the local chassis
2 Ethernet port of the 1756-ENBx module in the local chassis
127.127.127.12 IP address of the SLC 5/05 controller
Example 3: Sample path for a DH+ message

Path: Local_DHRIO, where Local_DHRIO is the name in the 1756-DHRIO module in the same chassis as the controller that sends the message.

Specify a communication method or module address

Use the following table to select a communication method or module address for the message.

If the destination device is a: Then select: And specify:
Logix5000 controller CIP no other specifications required
PLC-5 controller over an EtherNet/IP network
PLC-5 controller over an EtherNet/IP 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 controller Destination Link Link ID of the remote DH+ link where the target device resides
PLC-2 controller Destination Node Station address of the target device, in octal
If there is only one DH+ link and you did not use the RSLinx 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 CIP with Source ID(This allows the application to receive data from a controller.) Source Link Remote ID of the topic in RSLinx
Destination Link Virtual Link ID set up in RSLinx (0-65535)
Destination Node Destination ID (0-77 octal) provided by the application to RSLinx. For a DDE topic in RSLinx, 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 in which the module resides
block transfer module over a ControlNet network ControlNet Slot Slot number in which the module resides
Choose a cache option

Depending on how you configure a MSG instruction, it may use a connection to send or receive data.

This type of message: And this communication method: Uses a connection
CIP data table read or write è ü
PLC2, PLC3, PLC5 or SLC (all types) CIP
CIP with Source ID
DH+ ü
CIP generic è your option *
block transfer read or write è ü
* You can connect CIP generic messages, but for most applications, we recommend that you leave CIP generic messages unconnected.
If a MSG instruction uses a connection, you have the option to leave the connection open (cache) or close the connection when the message has finished transmitting.

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.
The controller has the following limits on the number of connections you can cache.

If you have this software and firmware revision:
Then you can cache:
11.x or earlier § block transfer messages for up to 16 connections§ other types of messages for up to 16 connections
12.x or later up to 32 connections
If several messages go to the same device, the messages may be able to share a connection.

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 instructions share the connection (i.e., together, they count as 1 connection).
Guidelines

As you plan and program your MSG instructions, follow these guidelines:

Guideline Details
For each MSG instruction, create a control tag. Each MSG instruction requires its own control tag.Data Type = MESSAGEScope = ControllerThe 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 only access tags that are in the Controller Tags foler in the Controller Organizer.
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, refer to the Logix5000 Controllers Common Procedures 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.
If you want to enable more than 16 MSGs at one time, use some type of management strategy. If you enable more than 16 MSGs at one time, some MSG instructions may experience delays in entering the queue. To guarantee the execution of each message, use one of these options:§ Enable each message in sequence.§ Enable the messages in groups.§ Program a message to communicate with multiple devices.§ Program logic to coordinate the execution of messages.
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.§ 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 the previous guideline.

 

[mwiggins]

I got it. Thanks for the help. Here was my problem.

2,"3",70,1,3,3,35 I was not using the 3 for the B chnl of the DHRIO card.

I knew it was something simple.

the solution looks more like this.

1,2,3,56,1,3 Then select the chnl and the destination node.