EtherIP South Plugin

The foglamp-south-etherip plugin is a south plugin that supports PLC Tags read operation for Allen Bradley/Rockwell PLCs. This is based on libplctag and API level details can be read at wiki

Configuration Parameters

An EtherIP south service is added in the same way as any other south service in FogLAMP,

  • Select the South menu item

  • Click on the + icon in the top right

You will be presented with the following page

etherip_1

  • Select etherip from the plugin list

  • Enter a name for your etherip service

  • Click Next

  • You will be presented with the following configuration page

etherip_2

  • Asset Name: This is the name of the asset that will be used for the data read by this service. This will be used as prefix to output asset in case of “reading per PLC tag”. Default Value PLCTags

  • Reading Structure: This option allows the choice of either a “reading per PLC tag” or “single reading” with all the tags included as data points within that reading. Default Value reading per PLC tag

  • Timeout (ms): The request timeout when communicating with a PLC device. Default value is 5000 (milliseconds). Set this timeout value suitably based on number of tags to read/write and network conditions/RTT/latency, etc.

etherip_3

  • PLC IP Address: This is the IP Address of the PLC Tags server, Default value 127.0.0.1

  • PLC: This is the type of the PLC from which the user wants to read the tags, Default value controllogix, the following have been supported:

    • Allen-Bradley ControlLogix & CompactLogix PLCs

    • Allen-Bradley Micro8x0 PLCs

    • Rockwell/Allen-Bradley PLCs accessed over a DH+ bridge (i.e. a LGX chassis with a DHRIO module) such as PLC/5, SLC 500 and MicroLogix

    • Omron NX/NJ series PLCs as for Allen-Bradley Micro8x0

  • Path: This is the slot/rack(e.g. 0,1) to use to connect to your PLCTags device. This attribute is required for CompactLogix/ControlLogix tags and for tags using a DH+ protocol bridge (i.e. a DHRIO module) to get to a PLC/5, SLC 500, or MicroLogix PLC on a remote DH+ link. The attribute is ignored if it is not a DH+ bridge route, but will generate a warning if debugging is active. Note that Micro8x0 connections must not have a path attribute.

etherip_4

  • Tags to read: The map defines which PLCTags user wants to read. The map is a complex JSON object which is described in more detail below.

etherip_5

  • Tags to write: The map defines which PLCTags user wants to write to. The map is a complex JSON object which is described in more detail below.

Map

The map of tags to read/write is a JSON object with a single array tags, each element of this array is a JSON object that defines a single item of data that will be stored in FogLAMP or written as set-point control. These objects support a number of properties and values, these are

Property

Description

name

The name of the PLCTag that we are reading/writing. In case of read, this becomes the name of the datapoint with the asset.

type

The datatype of the PLCTag that we are reading/writing.

program

This defines the scope of the PLCTag that we are reading/writing, possible values being Program level scope or Global/Controller level scope. The Program name needs to be specified here if it is a tag with program level scope. For global/controller level tags ‘program’ attribute in map can be omitted or set to JSON null value or empty.

Example JSON Map

In this example we will assume we have a Micro8x0 PLC and we want to read one tag with name Tag1, type UINT32 and having global/controller level scope. Also we want to write to a tag with name Tag2, type UDINT and having global/controller level scope.

The Tags to read Map attribute for this example would be as follow:

{
    "tags": [
        {
            "name": "Tag1",
            "type": "UINT32",
            "program": "",
            "asset": "Asset",
            "datapoint": "Datapoint"
        }
    ]
 }
  • name : The name of the tag to be read.

  • type : The data type of the tag to be read.

  • program : The program name, to be left blank if Global scoped program.

  • asset : The asset name to be associated with the reading corresponding to the tag value being read.

  • datapoint : The datapoint name to be associated with the reading corresponding to the tag value being read.

The Tags to write Map attribute for this example would be as follow:

{
    "tags": [
        {
            "name": "Tag2",
            "type": "UDINT",
            "program": ""
        }
    ]
 }
  • name : The name of the tag to be written.

  • type : The data type of the tag to be written.

  • program : The program name, to be left blank if Global scoped program.

See Also

foglamp-south-ABB - A south plugin to pull data from the ABB cloud

foglamp-south-Beckhoff - A Beckhoff ADS data ingress plugin for FogLAMP, this monitors Beckhoff PLCs and returns the state of internal variables within the PLC

foglamp-south-ModbusC - A FogLAMP south plugin that implements modbus-tcp and modbus-rtu

foglamp-south-S7 - A south plugin that uses the S7 Communications protocol to read data from a Siemens S7 series PLC.

foglamp-south-dnp3 - A south plugin for FogLAMP that implements the DNP3 protocol

foglamp-south-opcua - A FogLAMP south service that pulls data from an OPC-UA server

foglamp-south-s2opcua - An OPCUA south plugin based on the Safe & Secure OPCUA library. This plugin offers similar functionality to the foglamp-south-opcua plugin but also offers encryption and authentication.