ABB Robot Web Services

review the following information for setting up and configuring the abb robot web services driver manufacturing connect edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series robotware 6 0 (revision k and later) replaces gen 1 driver(s) none to set up and configure this device in manufacturing connect edge, you will need to do the following step 1 set up and configure the robot device step 2 set up the robot device in manufacturing connect edge devicehub step 3 configure the list of registers step 1 set up and configure the robot device ensure the abb robot controller has robot web services enabled with robotware 6 0 revision k or later installed verify network connectivity to the robot controller and record its ip address confirm the robot web services port (default is 80 for http or 443 for https) if using authentication, ensure you have the necessary credentials configured on the robot controller step 2 set up the robot device in manufacturing connect edge devicehub configure the following parameters when you connect a device docid\ nm1lqfefya dsiffitity with this driver update default values to the specific setup of your device parameter value type robot driver abb robot web services network address the robot controller ip address you recorded in step 1 port 80 (http) or 443 (https) url path / authentication type none (or as configured on your robot) enable tls select if using https (port 443) query params json=1 request timeout 2000 (ms) retry count 0 websocket timeout 30 (seconds) step 3 configure the list of registers when you add tags docid\ h5heqicxrcy3nch9kbg9i 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\ jouzsq77y8z4dt jdgct tag formula variables docid 4yhyz92z7ggpgswqp05tf register table name value types access type description request raw, json, string, bool, uint, int, float, string\[], bool\[], uint\[], int\[], float\[] r/o rest request for polling data from the robot via http/https subscription raw, json, string, bool, uint, int, float, string\[], bool\[], uint\[], int\[], float\[] r/w websocket subscription for real time data streaming elog subscription json r/w event log websocket subscription for monitoring robot events 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 and include raw, json, string, bool, uint, int, float, and array variants (string\[], bool\[], uint\[], int\[], float\[]) polling interval enter a value in milliseconds this determines how often the tag should poll the register for data only applicable for request register type tag name enter a name for the tag description (optional) enter a description for the tag request type select the http method for rest requests 0 get 1 post 2 put 3 delete url path enter the api endpoint path relative to the base url configured in device settings leave empty to use the device level url path path params enter path parameters for the url if required by the specific api endpoint query params enter query string parameters for the request multiple parameters should be separated with & leave empty to use device level query parameters payload for post/put requests, enter the request body data payload encoding select the encoding type for the payload 0 plain text 1 base64 response parse pattern enter a jsonpath or regex pattern to extract specific data from the api response use $ to capture the entire response headers enter custom http headers in key format multiple headers should be separated by semicolons allow multiple matches select to allow the parse pattern to return multiple matching values as an array allow empty matches select to allow empty/null responses without generating errors 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)