Implementation of Common industrial Protocol (CIP) via EtherNet [EtherNet/IP (CIP)]

EtherNet_IP_PCCC

Use these set of VIs to communicate with MicroLogix Series PLCs Via EtherNet.

These VIs use simple TCP/IP Communication.

Communication : Ethernet, TCP/IP
Protocol : EtherNet/IP
Service :CIP (For Connection Management), CIP Service for PCCC
Command : PCCC

Tested with : MicroLogix 1100, MicroLogix 1500,1200(with NET-ENI)

No OPC Server Required
No Automation Server Required
No NI-DSC Module Required.

Note: These VIs access N7 Integer File. To access other Files in the PLCs, just replace the "Fileno" Constant(0x07) with a Control and make it as a parameter to the SubVI.

EtherNet_IP_CIP

Use these set of VIs to communicate with CompactLogix, Control Logix Series PLCs, Any Device that supports CIP(EtherNet/IP)

These VIs uses simple TCP/IP Communication.

Communication : Ethernet, TCP/IP
Protocol : EtherNet/IP
Service :CIP (For Connection Management, Read, Write)
Command : CIP Commands

Tested with : Compact Logix Series PLCs

No OPC Server Required
No Automation Server Required
No NI-DSC Module Required.

Visit : ODVA Website for EtherNet/IP Protocol Specification

This post has been edited by siva: Sep 11 2007, 06:49 AM

I've been wanting to create Ethernet/IP VIs for some time now, Nice job! I have a ControlLogix 5555 CPU and a 1756-ENBT/A Ethernet/IP card to test these VIs. Once I have some free time, I will post my results.

siva,


I'm using a ControlLogix 5561 Controler R16, with a 1765-ENBT/A Ethernet Bridge. Any possibility of getting EtherNet_IP_CIP unlocked ?

Sure..


Attached the Unlocked VIs.

I would appreciate, if somebody updates the code as per guidelines and makes it available free to all.

Thanks and Regards
Siva



This post has been edited by siva: Sep 11 2007, 03:53 PM

I am Sorry for uploading some VIs with password protection in previous posts and for having very bad documentation..

I've removed some junk code in the VIs and now i've attached the unlocked VIs.

Thanks and Regards

Siva

it so great. thanks very much

Hi Siva,

thanks for sharing your work and I guess that took some time to fiddle through the bytearrays. I have just two hints (I hope you don´t see them as nagging) after looking at the code.

I my eyes every cluster and enums should be typedefs (always).

Using normal "Divide" by 2 for array lengths may have unwanted sideeffects for different odd length-arrays (due to DBL->Intger Rounding).

I normally have more confidence in the "Quotient Remainder" function for this.



just my 2 cents
and thanks again for sharing your code!

Hi beckerg,

Thanks for your suggestions. Your suggestions are included into the code along with some other changes. I am waiting for the testing to happen. Once tested, the updated code will be uploaded into the LAVA code repository.

I've analysed the sub vi for this issue.

The Number of elements in the frame will always be an even number. Hence, Int(SizeOf(@array)/2) gives the same result as Quotient(Number=SizeOf(@array), Divisor=2). At no case, the frame will get composed of odd number of elements. Thats why the component is running with no-errors.

anyway, its good to use quo-rem operator for this purpose. thanks for the suggestion

The Present set of VIs does not fully support reading/writing of the following types of tages

1) Timer Tags
2) Control Tags
3) Counter Tags
4) Data Structures

However ACC, PRE elements of timer\control\counter tag-structures can be accessed.

To access ACC element of a Timer, say timer-1, use "timer1.ACC" as Tag-name and Datatype as DINT. Similiarly, to access Preset Element, use "timer1.PRE" as tag-name and DINT as datatype. By using this method, ACC, PRE of Timer, Control and Counter tags can be accessed.

Note: "ACC", "PRE" should be in Upper Case.

Siva:

Thanks for creating these VI's -- this will save a great deal of effort!

Thanks!

- Keith

This post has been edited by mysterj: Nov 28 2007, 04:05 PM

Hi Siva,
I am attempting to use your EtherNet_IP_PCCC.zip files to communicate with a MicroLogix 1500. My problem is with writing to the PLC. I made a small test vi that uses your init, update registers, scan registers, and terminate vis. If i write a value, say 1F3A, to offset 0 all is well. I can read the 1F3A in the register array with no errors. But if i try to write to any other offset, say 2 or 4, i get a data error on the update register vi and when i try to read that offset i get a value that looks like a timer that is continually scanning. I guess i dont understand the registers

Where did you get the information to set up the clusters for your vis? This is probably what would point me in the right direction.

Thanks so much for the vis! i can tell that you have spent alot of time/work creating them. Once i get an understanding of the registry on the 1500 i feel sure communications will be a breeze

Hi longzoo,

I'm afraid that the Number of Registers in N7 File of your PLC is configured as 1. Configure the N7 File Size accordingly before using the VIs.(You can set the no of registers in N7 as 256).

Hope this would solve the problem. If not, Please send a Snapshot of the test VIs.

I got the protocol information by Reverse engineering the TCP messages between PLC/SCADA. and by using DF1 Protocol Spec Document, 5000 Data access document., You can find these docs in Rockwell Software Knowledge Base Section. If you are not able to find, then please drop me a mail at sivamgr@gmail.com and I ll send you all the docs and notes.

This post has been edited by siva: Dec 4 2007, 06:46 PM