Controllogix to Compact logix talking

Roboman7s

Member
Join Date
Jan 2009
Location
iowa
Posts
4
Ok guys so I'm trying to do some messaging between a 1756-L60M03Se Version 17 and a New compactlogix 1769-L36ERM Version 20. I tried to do some produced and consumed tags but I'm not sure how I can add the L36ERM to the L60?

In my haste I decided to do regular old messaging but it gives me an IOI syntax error I copied the tag so its spelled correct and they are both dints.

Any ideas would be greatly appreciated thanks.

Brandon
 
Welcome to the PLCTalk forum !

The new 5370 family CompactLogix controllers consider both the controller and the Ethernet module to be in Slot 0, which is different from the older CompactLogix 1769-L32E and -L35E.

I know it was an issue with a 1756 controller prior to version 16.22 consuming tags produced by a modern 5370 controller.

But a 1756-L6x family controller with Version 17 should be able to treat a modern 1769-L36ERM as though it was a 1769-L35E for the purposes of Consuming tags and sending Messages. Put the CompactLogix into the I/O tree of the 1756-L60M03SE as an 1769-L35E.
 
Thanks Ken, I have been a member for awhile and can usually find my answer with a little search hence my first post. I figured there had to be a way to cheat this, I will try this out because this issue has been a real pain in rear for me.

Brandon
 
http://i87.photobucket.com/albums/k156/z28camaro82/control_problem_zpsp2xaoax0.png

Well of course it works going to the L36erm, but when I try to go back the other way the L60 keeps timing out my connection to the L36erm




control_problem_zpsp2xaoax0.png
 
Maybe there's something about that 1756-L60M03SE that is different than its other L6 siblings.

The Knowledgebase articles I've read suggest that a 1756 controller with version 16.22 or later firmware should be able to Consume tags from a 5370 family CompactLogix by substituting an older 1769-L35E in the I/O tree.

KB Article ID 471085: Adding a CompactLogix 5370 Controller to the IO Tree of a v19 or earlier controller (Access Level: Everyone)

KB Article ID 591167: Produced/Consumed Tags between 1756-L1 and 5730 CompactLogix Controllers (Access Level: TechConnect)

The fact that the connection failure triangle shows up on the controller, not the Ethernet module, suggests that the problem is related to the CIP path differences between the older CompactLogix and the modern 5370 family CompactLogix.

Check the revision of your 1756-ENBT bridge module; that first Knowledgebase document says it should be 5.001 or later.
 

Similar Topics

Read and write the Tags direct using pycomm3 and LogixDriver. Just in case anybody wanted to know. Here's a sample: from pycomm3 import...
Replies
0
Views
799
I've recently replaced an 1756-L72 and 1756-ENBT with a 1756-L81E & 1756-ENBT2R on a ControLogix chasis. The machine ran fine for two days after...
Replies
5
Views
1,673
My new friend Ron Beaufort got me thinking about the issues with using OTL's in regards to a power cycle. While you can use a first scan bit...
Replies
10
Views
4,797
Hi, I'm currently putting together a schedule to bring all our compact and controllogix processors up to a standard firmware level, and then...
Replies
3
Views
1,603
Can someone help me understand in detail the differences and limitations between Ethernet IP on a Compact / Controllogix Controller and Ethernet...
Replies
2
Views
2,022
Back
Top Bottom