GE Ethernet Global Data

review the following information for setting up and configuring the ge ethernet global data (egd) ethernet driver ethernet global data is a publish and subscribe protocol a controller publishes a block of data called an exchange at a fixed rate, and any device on the network configured to consume that exchange receives it litmus edge (le) works in both directions consumer tags read data from exchanges that a controller produces, and producer tags contribute data to an exchange that le produces the driver connects on port 18246 by default it does not support device discovery or tag browsing, so you enter the network and exchange details manually note this driver is experimental some features may not work as expected compatibility compatibility parameter compatible items driver type ethernet validated devices/series ge devices that support egd transactions and use cpu 364 or higher how to configure the plc 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 confirm that the controller supports egd transactions and uses cpu 364 or higher configure the exchanges the controller produces, and note the exchange id and the size of each one note the controller's ip address you enter it as the producer id on each consumer tag identify the network interface on the le system that reaches the controller, and note its address and subnet mask note the driver does not support device discovery or tag browsing enter every value manually step 2 set up the plc device in litmus edge devicehub configure the following parameters when you connect a device with this driver update default values to the specific setup of your device parameter value type ge fanuc driver ge egd ethernet name enter a name for the device default ge egd ethernet device description (optional) enter a description for the device network interface enter the address and subnet mask of the le network interface that reaches the controller, in cidr notation network port enter the egd port, from 0 to 65535 default 18246 producer exchange destination enter the destination address for the exchange that le produces default 192 168 0 1 producer exchange id enter the id of the exchange that le produces, from 1 to 65535 default 1 producer exchange size enter the size in bytes of the exchange that le produces, from 1 to 1400 default 1 note the three producer exchange parameters describe the exchange that le publishes set them only if you add producer or producer bits tags 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 select the register name in the name list, then supply the address consumer registers read from an exchange that a controller produces, so they also need a producer id and an exchange id to identify which exchange to read producer registers write into the exchange that le produces, which you configured in step 2, so they need no producer details the address range depends on the register bit registers accept 0 to 11199 word registers accept 0 to 1399 name value types access types description consumer uint8, uint16, uint32, uint64, int8, int16, int32, int64, float32, float64 r/o reads a value from an exchange produced by a controller consumer bits bool r/o reads a bit from an exchange produced by a controller producer uint8, uint16, uint32, uint64, int8, int16, int32, int64, float32, float64 r/w contributes a value to the exchange that litmus edge produces producer bits bool r/w contributes a bit to the exchange that litmus edge produces tag parameters parameter value name select a register name from the drop down list available options depend on the names in the register table value type select a data type from the drop down list available options depend on the register name selected producer id enter the ip address of the controller that produces the exchange this parameter applies to consumer and consumer bits registers exchange id enter the id of the exchange to consume, from 1 to 16383 default 1 together with the producer id , this identifies which messages to consume this parameter applies to consumer and consumer bits registers address enter the offset within the exchange default 0 for consumer bits and producer bits, the range is 0 to 11199 for consumer and producer, the range is 0 to 1399 count enter the number of values to read, from 1 to 65535 default 1 a count higher than 1 generates an array of values from the address configured and the addresses that follow it tag name enter a name for the tag description (optional) enter a description for the tag tag formula enter a formula to process tag data see tag formula below only publish on change of value select the checkbox to publish nats messages only when the value parameter changes to a new value 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 are not 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) note this driver has no polling interval parameter egd data arrives when the producing controller publishes an exchange, so the controller sets the rate 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 function description sin sine cos cosine sqrt square root tan tangent power(x) performs the operation 10^x log(x) natural logarithm (base e) exp(x) performs the operation e^x