Add Tag(s) to DeviceHub for one Litmus Edge

to add tag(s) with litmus excel add ins, you should be familiar with how tags work in devicehub docid 55lxgtilwfsygkxzrdfod on litmus edge before you begin you have installed the litmus excel add ins extension see install litmus excel add ins docid\ gzdhbj1xzznddthyocuuu for details you have prepared a prepare a new tool file to manage devicehub tag(s) docid\ p1a a8cn h5o1cbu64xpm initial preparation open a new tag management tool file in excel if prompted, enable content to allow the code to run make sure the the tool is set to fast mode for the sheet mode option and connect to is set to one le add tag(s) in fast mode notes tag(s) will have their own set of tag properties depending on the respective driver the steps below show an example using one of the over 100 drivers mandatory tag settings the two d's and t provide the following three tag settings to start the definition of a tag device name select the device for which you want to add the tag driver name for device select the driver which is used for the device notes the driver name will be automatically set, if the device name is selected first tag name provide the name for the tag notes the tool will verify that the entries for this column are unique per device name and notify the user in case the same tag name was already used it is recommended to click the compare vs le button to check if a tag for the provided device and with this name may already be defined on litmus edge if no tag for the selected device and with the name combination is defined, the row will stay as a for the action if a tag for the selected driver and with the name combination is already defined, the row will change to m for the action and the settings of the tag will be pulled notes this doesn't need to be done for every tag individually but can instead be done once all desired tags have been added to the sheet tag definition properties tag definition properties are a mandatory set of tag settings, which are required for the request the data from a device based on the driver, the tag definition properties can be added using either the add tag(s) to devicehub for one litmus edge /#tag address translator or for opcua the add tag(s) to devicehub for one litmus edge /#tag browser most tags require a set of three values to define the tag definition register type the type of the register used when the tag was setup on the device this is driver specific tag value data type the value type of the tag this is driver specific register address / path the numeric register address of a tag on the device or the path string of the tag this is driver specific the tool will automatically pull potential add tag(s) to devicehub for one litmus edge /#not mandatory tag settings in fast mode with a default configuration for the driver similar to how the ui on litmus edge prepopulates the tag wizard notes for some drivers, tags can require different tag definition properties, which can lead to certain columns being grayed out as they do not apply to read data for these tags, users provide the respective settings through the add tag(s) to devicehub for one litmus edge /#not mandatory tag settings in fast mode column if all add tag(s) to devicehub for one litmus edge /#mandatory tag settings ( ) tag settings are provided, as well as all add tag(s) to devicehub for one litmus edge docid\ zw6smucz3prv3hzw4uwyl settings are changed, the tag is ready to be added to litmus edge notes to add more tags to the sheet, repeat the process described under add tag(s) to devicehub for one litmus edge /#add tags in fast mode for every tag you want to add tag address translator for some drivers, the tool features a tag address translator which can be used to provide the address in their typical format and translates it into the tag definition properties used by litmus to be able to use the tag address translator, the column (optional) tag address translator has to be not grayed out tag address translator not available tag address translator available type in the tag address in their typical driver specific format example siemens s7 1500 the tag address translator will parse the provided address and set the respecitve three tag definition properties and potential driver specifics example siemens s7 1500 notes it is possible that an address could be defined with one of multiple tag data value types example a siemens tag with and address like dbx d y could be of tag data value type dword > default dint real in these cases the tag address translator will by default request from the user to select the tag data value type the form shows the default tag data type which you can accept without the need of selecting it using the use default button otherwise select the tag value data type you need from the drop down and press the save button the user can also force the tag address translator to always use the default tag data value type tag browser for the opc ua client advanced driver and litmus edge versions after 3 16 x which support the new browse for tags (after 3 16 x) docid\ i3ezgnliqb29yycpnkfzs , the tool offers the option to browse for tags and import their settings into the tool before you will be able to browse for tag with the excel tool, you will need to setup at least one browse for tags (after 3 16 x) docid\ i3ezgnliqb29yycpnkfzs and have it being completed you can see if tag browsing is avialable if the tag browse wizard docid\ n4vrurrdo6linifpjgygb button is shown in the litmusconfiguration ribbon when a cell in any of the columns tag name (optional) tag address translator register type tag value data type register address / path is selected press the tag browse button select the browse task to use and press the browse button select the tag(s) you want to import and press the import button this will import the tag(s) with their suggested tag name as tag name and the tag definition properties important this will overwrite any previous value in column tag name the selected tag(s) with their settings are imported into the sheet once finished, the user can either p erform another search using the new search button finish the import using the close button executing actions when all add tag(s) to devicehub for one litmus edge /#mandatory tag settings and add tag(s) to devicehub for one litmus edge /#not mandatory tag settings in fast mode settings for all tag(s) are set, they are ready to be added it is recommended but not mandatory to verify the configuration first without executing the action by pressing the verify only button this will check that all required tag settings are provided and logically correct and provide any finding to the user example below the user did not set a register address / path important the tool can not verify if all provided tag settings are factually correct for example it can not verify that the register address provided for the tag is the correct register address on the plc the tag(s) can be added to litmus edge by pressing the verify + execute button this will check that all required tag settings are provided and logically correct and provide any finding to the user if no issues have been identified, the tool will verify that the user wants to execute all the actions from the action column a add tag(s) m modify tag(s) d delete tag(s) i ignore tag(s) > do nothing to perform all actions, press the yes button the tool will perform all actions when finished, a result summary is shown close the result summary by pressing the x close button the tool will ask if the user wants to re compare the tag(s) against litmus edge to re compare, press the yes button to not re compare, press the no button if the user selected to press the yes button from aboves messagebox, the tool will pull all the tag settings from litmus edge again including the registerid and also change the action to m for each tag with a registerid or a for devices with no registerid not mandatory tag settings in fast mode each device has a number of not mandatory settings which can be used to meeat specific needs polling interval in seconds the time between the litmus edge requesting data from the device for millisecond values, provide the value as decimal driver specifics many drivers require very unique tag definition properties specific to their make and model this column combines all of these as a single json object with a default configuration it is recommended to use the driver specific wizard docid 48vyrem4nexaxpxe5ci7x when setting your specific values for these driver specific settings add tag(s) in extended mode to be able to fully cutomize all possible tag settings set the tool to extended mode for the sheet mode option this will provide the user with all available add tag(s) to devicehub for one litmus edge /#not mandatory tag settings in extended mode tag settings setting add tag(s) to devicehub for one litmus edge /#mandatory tag settings and add tag(s) to devicehub for one litmus edge /#executing actions is the same process as for add tag(s) to devicehub for one litmus edge /#add tags in fast mode not mandatory tag settings in extended mode each tag has a number of not mandatory settings which can be used to meet specific needs tag description a short description of the tag polling interval in seconds the time between the litmus edge requesting data from the device for millisecond values, provide the value as decimal count the number of consecutive registers including the one defined for this tag if the value is larger 1, the returned data will be an array publish on cov only only publish a new value to the message broker if the value changes tag formula enter a formula for the tag to process the generated data see tag formula variables docid\ io7xgyrdvv vmpnfxoaci to learn more meta data provide a json object which holds all the meta data you want to add to the tag see organize device and tag data by using metadata docid\ mu 6j6zhi0cvchdad0w8n to learn more it is recommended to use the meta data wizard docid\ geidkenk7d4poixgwtpwm driver specifics many drivers require very unique tag definition properties specific to their make and model this column combines all of these as a single json object with a default configuration it is recommended to use the driver specific wizard docid 48vyrem4nexaxpxe5ci7x when setting your specific values for these driver specific settings troubleshooting the tool will perform several checks throughout the proces of defining the tag settings if they do not pass successfully, the user will be notified the checks include tag name uniqueness on a device level the tool checks if a tag name already exist for a specific device name in the tool allowed and not allowed ascii characters for names and descriptions docid\ fnwhcidrnnpizczkuwiyz for tag names and descriptions the user is shown a message box as notification the character(s) are highlighted in red and also shown in a note see allowed and not allowed ascii characters for names and descriptions docid\ fnwhcidrnnpizczkuwiyz for a full list for both names and descriptions correct json formating for meta data , and driver specifics example for an invalid json formatting of the driver specifics valid entry for register address / path, if value has to be a number, to be a number and withhin allowed range example for an invalid entry for the register address / path is the column driver specifics empty if they are, and the driver requires driver specifics the default json object will be automaticly added for some drivers the tool also verifies if there exist mandatory json key value pairs in column driver specifics with a value being empty null empty array " \[] " empty json object " {} " for drivers which use queries to read data from databases the tool also verifies the query defined in the column driver specifics is setup to perform sql injection