Welcome to EtherNet/IP Driver for Communication to Allen Bradley ControlLogix PLCs

[Charlie Silver]

Eric,

Those are really helpful suggestions.  The problem does indeed seem to be latency at the PLC end (as you anticipated).  However, adjusting the PLC ethernet module's speed/duplex settings doesn't seem to have any effect.  Are you aware of any other settings that might cause this type of delay?

I appreciate your experience here because Allen-Bradley won't touch it once you say the words "third party"!

Charlie

[mjo]

Third Party eh? hmmm, With all this development aimed at integrating with the AB controllers, is NI looking at becoming one of the 'Encompass' Partners?...

[GRNDRCHR]

I was wondering if anyone has used this protocol to talk directly to an SMC air solinoid manifold with either an ex250 or ex500 ethernet module. I am new to lab view and any help would greatly be apreciated. I have packet captures of the comunications between the SMC manifold and an AllenBradle PLC if they are needed.

[BlueCheese]

If you attach a packet capture or manual for the device it might help to see how it is communicating.

Thanks,
Eric 

[GRNDRCHR]

Is there an email address to send you the files. There is quite a bit of data that I've captured. To much to put all of it on here but none the less here is one set.

No.     Time        Source                Destination           Protocol Info
   5641 45.702389   10.110.203.102        10.110.205.213        ENIP     Connection:  ID=0x750F0381, SEQ=0000047438

Frame 5641 (70 bytes on wire, 70 bytes captured)
Ethernet II, Src: Rockwell_03:ac:37 (00:00:bc:03:ac:37), Dst: HmsField_03:5e:34 (00:30:11:03:5e:34)
Internet Protocol, Src: 10.110.203.102 (10.110.203.102), Dst: 10.110.205.213 (10.110.205.213)
User Datagram Protocol, Src Port: 60877 (60877), Dst Port: EtherNet/IP-1 (2222)
EtherNet/IP (Industrial Protocol)
    Item Count: 2
        Type ID: Sequenced Address Item (0x8002)
            Length: 8
            Connection ID: 0x750f0381
            Sequence Number: 47438
        Type ID: Connected Data Item (0x00b1)
            Length: 10
            Data (10 bytes)

0000  19 c8 01 00 00 00 00 00 00 00                     ..........
                Data: 19C80100000000000000
                [Length: 10]

No.     Time        Source                Destination           Protocol Info
   5642 45.706891   10.110.205.213        239.192.59.128        ENIP     Connection:  ID=0x095303A0, SEQ=0000043257

Frame 5642 (68 bytes on wire, 68 bytes captured)
Ethernet II, Src: HmsField_03:5e:34 (00:30:11:03:5e:34), Dst: IPv4mcast_40:3b:80 (01:00:5e:40:3b:80)
Internet Protocol, Src: 10.110.205.213 (10.110.205.213), Dst: 239.192.59.128 (239.192.59.128)
User Datagram Protocol, Src Port: EtherNet/IP-1 (2222), Dst Port: EtherNet/IP-1 (2222)
EtherNet/IP (Industrial Protocol)
    Item Count: 2
        Type ID: Sequenced Address Item (0x8002)
            Length: 8
            Connection ID: 0x095303a0
            Sequence Number: 43257
        Type ID: Connected Data Item (0x00b1)
            Length: 8
            Data (8 bytes)

0000  ff ff 00 00 00 00 00 0c                           ........
                Data: FFFF00000000000C
                [Length: 8]

No.     Time        Source                Destination           Protocol Info
   5643 45.713294   10.110.30.27          10.110.203.102        CIP      Change Complete

Frame 5643 (116 bytes on wire, 116 bytes captured)
Ethernet II, Src: Dell_a7:ff:11 (00:1a:a0:a7:ff:11), Dst: Rockwell_03:ac:37 (00:00:bc:03:ac:37)
Internet Protocol, Src: 10.110.30.27 (10.110.30.27), Dst: 10.110.203.102 (10.110.203.102)
Transmission Control Protocol, Src Port: adobeserver-4 (3704), Dst Port: EtherNet/IP-2 (44818), Seq: 180755, Ack: 172112, Len: 62
EtherNet/IP (Industrial Protocol), Session: 0x13021400, Send Unit Data
    Encapsulation Header
        Command: Send Unit Data (0x0070)
        Length: 38
        Session Handle: 0x13021400
        Status: Success (0x00000000)
        Sender Context: 0000000000000000
        Options: 0x00000000
    Command Specific Data
Common Industrial Protocol

No.     Time        Source                Destination           Protocol Info
   5644 45.719395   10.110.203.102        10.110.30.27          CIP      Success

Frame 5644 (104 bytes on wire, 104 bytes captured)
Ethernet II, Src: Rockwell_03:ac:37 (00:00:bc:03:ac:37), Dst: Dell_a7:ff:11 (00:1a:a0:a7:ff:11)
Internet Protocol, Src: 10.110.203.102 (10.110.203.102), Dst: 10.110.30.27 (10.110.30.27)
Transmission Control Protocol, Src Port: EtherNet/IP-2 (44818), Dst Port: adobeserver-4 (3704), Seq: 172112, Ack: 180817, Len: 50
EtherNet/IP (Industrial Protocol), Session: 0x13021400, Send Unit Data
    Encapsulation Header
        Command: Send Unit Data (0x0070)
        Length: 26
        Session Handle: 0x13021400
        Status: Success (0x00000000)
        Sender Context: 0000000000000000
        Options: 0x00000000
    Command Specific Data
Common Industrial Protocol

No.     Time        Source                Destination           Protocol Info
   5645 45.722374   10.110.203.102        10.110.205.213        ENIP     Connection:  ID=0x750F0381, SEQ=0000047439

Frame 5645 (70 bytes on wire, 70 bytes captured)
Ethernet II, Src: Rockwell_03:ac:37 (00:00:bc:03:ac:37), Dst: HmsField_03:5e:34 (00:30:11:03:5e:34)
Internet Protocol, Src: 10.110.203.102 (10.110.203.102), Dst: 10.110.205.213 (10.110.205.213)
User Datagram Protocol, Src Port: 60877 (60877), Dst Port: EtherNet/IP-1 (2222)
EtherNet/IP (Industrial Protocol)
    Item Count: 2
        Type ID: Sequenced Address Item (0x8002)
            Length: 8
            Connection ID: 0x750f0381
            Sequence Number: 47439
        Type ID: Connected Data Item (0x00b1)
            Length: 10
            Data (10 bytes)

0000  3a c8 01 00 00 00 01 00 00 00                     :.........
                Data: 3AC80100000001000000
                [Length: 10]

[BlueCheese]

GRNDRCHR,

Could you attach the capture as an attachment to your post?

Thanks,
Eric 

[BlueCheese]

In case anyone is interested, I have updated the version to 1.0.4 off the main download page. The main change is adding official support for LabVIEW 2009 in the installer.

Eric 

[GRNDRCHR]

Here are the files from the SMC Manifold

[BlueCheese]

Hi GRNDRCHR,

Sorry, you may need to ask SMC for more details about the CIP objects that your device presents. From the packet captures I see a lot of explicit messages to many different object classes on the device. You may be able to use the Get Attribute Single/Set Attribute Single to interact with some of those objects via explicit messages.

I also see some implicit I/O data connections with data assemblies on the device. We don't currently support initiating such connections (only being the target of them) as we are an adapter and not a scanner. However, you may be able to use explicit messages to read/write these assemblies directly if the SMC device supports the Assembly object. You might want to check the SMC manual or their support about this.

Eric 

[dazach]

 How to get it to work in 2009? What are all the required pieces? I copied ethernetip folder from addons over and the EthernetIPinterface.dll is installed. What else do I need to do?

It will work with the current version if you manually copy all the required pieces over to the new 2009 directory. I'll try to get a new installer up soon that supports and installs into 2009 seamlessly.

Eric