Set Up the OSI Agent

review the following information for setting up and configuring the osi agent driver before you begin install an osi server and osi agent on a windows system follow up with your account executive to download the osi agent and required files make sure the osi client dll is on the same system running the osi agent open port 443 and 4777 between windows and manufacturing connect edge otherwise, the osi agent won't work configure windows authentication so that the osi pi server can work docid\ vfyols3usyp1pyop64crk in manufacturing connect edge step 1 install osi agent install the zip file with the osi agent and all required files on a windows system step 2 run and configure the dh historian agent to run and configure the dh historian agent run the dh historian agent exe file a windows service starts and connects to the osi agent so that it can collect data from the osi agent review the introductory screen and click next the appearance configuration settings displays configure the appearance settings click save , and then next the server settings section displays in the pi server section, click the load pi servers button you will be able to view all pi servers properly set up with dcom rules on the correct network open the drop down list for server to view accessible servers and select the appropriate server select an authentication method pi user this is local user to define the dcom rules for this user, open the pi system management tool and navigate to security > pi users and groups enter the correct username and password windows the pi server needs to be properly configured to use windows authentication once the pi server is configured, click test connection verify the status is success or fail in the operation mode section, select how data will be collected both modes allow the first value on startup to get published to nats events based the recommended selection whenever the value changes on the pi server, you will receive a nats message polling define the polling interval in seconds the timestamp for the message is when the data was published to the dh historian agent, not when manufacturing connect edge collects the data in the logs section, select how to view logs the logs will records failures with details events log to view logs, start the osi agent log file folder define a local folder to store log files click save , and then next the site settings section displays configure the site settings host enter the ip address for the manufacturing connect edge instance port enter 4777 user enter the username to connect to the server in devicehub password enter the password to connect to the server in devicehub api token follow the steps to docid\ vfyols3usyp1pyop64crk , copy the token, and paste it here the token is used to create the device and tags device name enter the name for the device that will be created in manufacturing connect edge devicehub device id this field is optional the id is automatically generated click test connection to ensure the settings are configured correctly click create device if a device is successfully created, a created a new device message will display the osi agent driver device will be created in the manufacturing connect edge devicehub pane click save , and then next the tags section displays search for tags you want to add you can search by using regular expression the character displays all tags on the server the server tags column displays tags on the osi agent the agent tags column displays tags that will be sent to manufacturing connect edge and mapped to the osi agent driver device in devicehub after selecting tags to be sent to manufacturing connect edge, click update tags the tags will be added to the osi driver in manufacturing connect edge you can view them in devicehub > tags if needed, click save this saves the settings in the devicehubagentmain ui execonfig file, which is a password encrypted text file the next time you start the historian agent, the saved settings from the configuration file will load in the folder that installed the dh historian agent, navigate to the pi agent sub folder double click the devicehubagentsvc exe file this will enable the connection to the server follow the command to install the service once installed and the task management is properly set up to run the service when logged off, data will still be sent to the driver when users are logged out log in to manufacturing connect edge and navigate to devicehub > devices you should see a connected status for the osi agent device osi agent driver settings in manufacturing connect edge if you review or edit the settings of the osi agent device, refer to the following parameters parameter value type osi driver osi agent 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 tag parameters in manufacturing connect edge if you docid\ ioanzd2awqnkuppgee3eh in manufacturing connect edge, select the r register name, and then refer to the following supported data types and tag parameters uint32 uint64 float64 string byte\[] float32\[] bool byte float64\[] string\[] uint16 int64 uint16\[] sbyte int16 int16\[] int32\[] int64\[] uint64\[] float32 bool\[] uint32\[] int32 sbyte\[] 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 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)