Beckhoff ADS/AMS Ethernet (Gen1)

review the following information for setting up and configuring the beckhoff ads/ams ethernet (gen1) driver litmus edge compatible series 224,284 false true unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type 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 otherwise, follow the steps below note make sure litmus edge ip address is configured in twincat to configure your device 1\ note down the following information and refer to it as needed device beckhoff cx1100 002 communication i/f ethernet refer to the following figures 2\ launch twincat v2 11 build 2302 software note the beckhoff plc is also a pc with its own os, and an ip address can be set up like a pc 3\ click the twincat icon in the notification area, launch the system, and then click the system status indicator switch from config node (blue) to running (green) 4\ launch the plc 5\ set up the target 6\ select the target 7\ launch twincat system manager and twincat plc control 8\ click online > login , and then download the program and run the plc step 2 set up the plc device in litmus edge devicehub configure the following parameters when you connect a device docid 3eyafppweuvmblcey17sq with this driver update default values to the specific setup of your device 154,368 false true unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type step 3 configure the list of registers when you add tags docid 8se7z3pmrfwl1nmzcwalx 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 583p fbuozem6whgrdgkq tag formula variables docid\ ifbwcou90qtfodk hrysr register table refer to the appropriate register table depending on your version of litmus edge register table for litmus edge 3 11 0 and later 68,106,139,112,116,118 true left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type register table for litmus edge 3 5 6 and earlier 71,101,138,113,119,118 trueleft unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type 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 the value must in the decimal format, within the allowed min/max range omit the leading zeros the device might use the decimal (d), hexadecimal (h), or octal (o) address format see the register table at the bottom of the dialog box 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 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 from a previous value 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)