Euromap63 (Gen1)

review the following information for setting up and configuring the euromap63 (gen1) driver manufacturing connect edge compatible series compatibility parameter compatible items driver type file based validated devices/series euromap 63 the euromap 63 standard defines the data exchange with injection molding machines through files when configuring tags for this driver, you must enter the case sensitive register name exactly as it is defined in the plc see the free tags section below to learn more supported commands the euromap63 (gen1) driver supports the following commands in the specification euromap63 command use in manufacturing connect edge getid browses available tags report retrieves tag values from the injection molding machine set up and configure the the euromap63 driver to set up and configure the euromap63 create a shared folder see create a shared folder in windows 10 docid\ i94fn1ihu9ok2vjatfnak to learn more in manufacturing connect edge, follow the steps to mount external storage docid\ skxdvocfhgfpcevxwdqqu and configure the following parameters mount point name enter the name of the shared folder you created previously share enter the share name in the following format //\[ip address of the pc running the simulator]/\[shared folder name] for example //192 168 53 34/euromap63folder read only uncheck the checkbox username enter the linux samba username you configured password enter the password for the linux samba username you configured in manufacturing connect edge, follow the steps to connect a device docid\ rfvijdxz7dbad8mwbisma and configure the following parameters configure other parameters as needed device type select euromap63 driver name select euromap63 (gen1) path enter the path of the shared folder in the following format /data/\[shared folder name] for example /data/euromap63folder follow the steps to browse tags docid\ vddnslvnu mnguwwiessp and add tags to the devicehub device if you need to manually add tags docid\ ioanzd2awqnkuppgee3eh to the device, refer to the following tag parameters and available value types refer to the following additional resources organize device and tag data by using metadata docid\ f b720nivllber44rfyhn tag formula variables docid\ pwd 7p kzjxkt pyawaow free tags this driver doesn't have a list of available register names in the devicehub add tag form to add tags, you must enter the case sensitive register name exactly as it is defined in the plc a connected status for the device won't display until a tag with a correct register name is created available value types int float int64 float64 string tag parameters name enter the case sensitive register name exactly as it is defined in the plc value type select a data type from the drop down list 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 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)