Cutler-Hammer ELC Ethernet
6 min
review the following information for setting up and configuring the cutler hammer elc ethernet driver litmus edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series cutler hammer elc pv28 series replaces gen 1 driver(s) n/a to set up and configure this device in litmus edge, you will need to do the following step 1 set up and configure the plc device step 2 set up the plc device in litmus edge devicehub step 3 configure the list of registers step 1 set up and configure the plc device if the device is configured for ethernet access, find its network parameters (ip address and port number, typically port 502) step 2 set up the plc device in litmus edge devicehub configure the following parameters when you connect a device docid\ pal6abpzbrimdu9lvgj30 with this driver update default values to the specific setup of your device ethernet connection parameters parameter value type eaton driver elc ethernet & serial network address the device ip address you recorded in step 1 port 502 zero based addressing enabled (default) response timeout 2000 (ms) maximum packet size 512 (bytes) step 3 configure the list of registers when you add a tag docid\ tuy hh0gi8djvot70wroh to the connected device, refer to the following register table and tag parameters refer to the following additional resources organize device and tag data by using metadata docid\ mu 6j6zhi0cvchdad0w8n tag formula variables docid\ io7xgyrdvv vmpnfxoaci register table name value types access types address format min address max address description x bit r/o ooo 0 255 discrete input y bit r/w ooo 0 255 discrete output m bit r/w dddd 0 4095 main relay to bit r/w ddd 0 255 timer status co bit r/w ddd 0 255 counter status s bit r/w dddd 0 1023 step point t word, int16, int32, uint32, int64, uint64, float32, float64 r/w ddd 0 255 timer current value t bit bit r/w ddddd 0 25515 timer current value c word, int16, int32, uint32, int64, uint64, float32, float64 r/w ddd 0 255 counter current value c bit bit r/w ddddd 0 25515 counter current value d word, int16, int32, uint32, int64, uint64, float32, float64, string r/w dddd 0 9999 data register d bit bit r/w dddddd 0 999915 data register tag parameters name select a register name from the drop down list the available options depend on the names in the register table value type select a data type from the drop down list the available options depend on the register name selected polling interval enter a value in seconds this determines how often the tag should poll the register for data tag name enter a name for the tag description (optional) enter a description for the tag address enter a tag address in decimal format, within the allowed min/max range omit the leading zeros the address format uses d for decimal and o for octal for bit tags, append the bit address without the bit separator the lowercase letters in the address format indicate how many digits you should enter in the bit address count enter the number of register values to read a count higher than 1 will generate an array of values from the address value configured and respective subsequent address values length available for string data registers enter the number of characters for tag values tag formula enter a formula for the tag to process the generated data two variables are permitted value (current tag value) and timestamp (current tag unix time in milliseconds) the following math functions are available sin cos sqrt tan power power( x ) performs the operation 10^x log log( x ) is the natural logarithm (the logarithm is in base e ) exp exp( x ) performs the operation e^x only publish on change of value select the checkbox to customize nats messages to be published only when the value parameter changes to a new one change of value only applies to boolean, numeric (such as int or float), and simple string data types it does not apply to complex types, such as json or array poll once topics will not be affected by change of value settings these topics will still only see a single message meta data metadata summarizes basic information about data this feature allows you to define key value pair data for the device output payload later on it can then be used to find, use, and reuse particular instances of data note if you use special characters in meta data key names, the special characters are replaced with underscore characters in the payload this can cause two key names to be combined into one for example, configuring the key names a b and a&\&b will cause only one key name to be created (a b)