OSI Agent Advanced

note this driver is available for manufacturing connect edge version 3 11 0 and later review the following information for setting up and configuring the osi agent driver important the dh historian agent can only have one osi pi agent and one osi pi server connection with one username/password configured for the osi pi server the username/password in the devicehub configuration is to access the dh historian agent, not the osi pi server if you would like to manage access to tags/data being sent through the osi pi agent and server, you can set up multiple manufacturing connect edge connections through the nats connector see set up edge cascading with the nats connector docid\ rkd0bfd0gya90nukydj9x to learn more set up the osi agent see set up the osi agent docid 3gio6woqvq4h3tr poh d to review how to set up and configure the osi agent driver osi agent advanced driver settings in manufacturing connect edge if you review or edit the settings of the osi agent advanced device, refer to the following parameters parameter value type osi driver osi agent advanced network port the port configured in the dh historian agent the default value is 4777 interface you have the option of selecting the interface for accepting client connections the default value is 0 0 0 0, which means using all network interfaces for accepting connections from clients user the username configured in the dh historian agent password the password configured in the dh historian agent enable tls disable or enable nats connection name the nats connection name, which should be the same as the windows based osi agent setting nats request timeout (ms) 5000 browse request items count 500 when you add tags docid\ ioanzd2awqnkuppgee3eh 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\ f b720nivllber44rfyhn tag formula variables docid\ pwd 7p kzjxkt pyawaow register table name value types r float64, bool\[], sbyte\[], byte\[], int32\[], sbyte, int16, int64, uint64\[], float64\[], string, uint16\[], float32\[], bool, byte, float32, uint64, string\[], int16\[], uint32\[], int64\[], uint16, int32, uint32 state byte, string status json tag parameters name select r value type select a value type tag name enter a name for the tag description (optional) enter a description for the tag publishing interval enter the publishing interval is seconds 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)