ControlLogix L71 Reading from 5/80E ver D.1

[just_lionel]

Trying to setup a message read via Ethernet.

I have the path setup as 1, 1, 2, 192.168.66.10

I get an error code 1, ext err 315.

I am beating my head against the wall trying to figure out what's going on

 

[Cheeseface]

in an offline project, add the controller to the i/o tree then in MSG config dialog, pick the path from the i/o tree item. then delete the i/o tree item, and the path remains.

 

[just_lionel]

You can't add an PLC5 to the I/O tree can you??

 

[Cheeseface]

just add anything

 

[Ken Roach]

That's a CIP connection error, to be sure. But I don't think that CIP paths are so complex that you need to fake out Logix 5000.

> 1, 1, 2, 192.168.66.10

That is correct for a 1756-ENxT module in Slot 01 (the second slot from the left) and a PLC-5E at that IP address.

>PLC-5/80E ver D.1

The Series letter will matter. If it's a PLC-5/80E Series E, Version D.1 then that's the first version that supported CIP protocol and can accept a message from a ControlLogix. Are you using the PLC-5 Typed Read or PLC-5 Typed Write command ?

Using the Windows PowerShell "tnc" command to check if the PLC-5 supports CIP would be my test.

Verify the PLC-5's embedded webserver on Port 80
tnc 192.168.66.10 -p 80

Verify the old PLC-5 CSPv4 protocol on Port 2222
tnc 192.168.66.10 -p 2222

Verify the modern CIP protocol on Port 44818
tnc 192.168.66.10 -p 44818

 

[Ken Roach]

An example of what a successful tnc looks like, for a 1756-ENBT in my lab:

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Users\kroach> tnc 192.168.18.228 -p 44818
ComputerName     : 192.168.18.228
RemoteAddress    : 192.168.18.228
RemotePort       : 44818
InterfaceAlias   : Ethernet
SourceAddress    : 192.168.18.104
TcpTestSucceeded : True

 

[just_lionel]

Thanks Ken, I'll try it here within the next hour.

I'm using the PLC5 read. I'll post results here soon .

Thanks again.

 

[just_lionel]

This is what I get from powershell

Here is the Message Config

 

[Contr_Conn]

If you have support contract then you can read Technote QA2752 | Access Levels: TechConnect.
This specific error is related to the incorrect message path, but also linked to the manipulation MSG block bits, specifically for PLC5.
I would create a completely new tag first, then deleting old tag. Also remember that message executes only once when rung condition changes from False to True. Use NO contac and toggle it for a test.

 

[just_lionel]

If you have support contract then you can read Technote QA2752 | Access Levels: TechConnect.
This specific error is related to the incorrect message path, but also linked to the manipulation MSG block bits, specifically for PLC5.
I would create a completely new tag first, then deleting old tag. Also remember that message executes only once when rung condition changes from False to True. Use NO contac and toggle it for a test.

That fixed it. Not sure how I missed that in the KB ...