MergeWorX Quick Start

To get started in MergeWorX, follow these steps that quickly provide a sample merge configuration using a CSV file:

  1. In the Workbench, expand your project, then expand the Historical Data node. The MergeWorX provider node should appear.

    Note: If the MergeWorX provider node does not appear in the tree explorer, you can add it by double-clicking the project node at the top of the tree explorer (or selecting the project node then clicking on the Edit button in the Edit section of the Home ribbon in the Workbench). This opens the project properties in the right side of the Workbench, where you can select which provider to add to the project by clicking on the checkbox to the left of its name and then Apply (or Apply & Close). When you close the project properties, your selected provider should now appear in the tree explorer.

  2. Create the triggers that will trigger the data merge with Hyper Historian:

    1. If you want to manually click a button to execute, you have to create a new register as described in the Registers topic. On the register's Properties tab, select a Data Type of Short and make the register Writable. On the Register Input/Output tab select an Input Tag of None, check the Use Initial Value (value set as 0) check box and disable the Output Tag.

    2. Then create a new data trigger (as described in the Data Triggers topic). For the Trigger Type, select On any data change (event) and specify the currently-created register as the Data Tag.

    3. Now all you have to do is to create an application that will be able to write a value into the register you created. You can use GraphWorX to do so. Create a GraphWorX display and put a button on it. In its dynamics, for the DataSource add the new UDM register you just created. Set Command to ToggleValue,  ValueOne to 1, and ValueTwo to 0. You can also add a process point to monitor the value in register to make sure you configured that in proper way. Go to runtime and test the button and see if process point value changes as you click the button. For help using GraphWorX, start with the GraphWorX64 Displays topic.

    4. Time triggers are mostly used for fully automatic or planned execution of Merge action. In this example create a trigger that fires event every minute. For more information, refer to the Time Triggers topic.

  3. In the configuration database, create a Plug-in as described in the Adding a Plug-in to the MergeWorX Configuration Database topic. For its trigger point, specify the data trigger you created in step 3.

  4. Create a CSV file. (The data you are loading into Hyper Historian but be in the CSV file format described in the MergeWorX CSV File Formats topic.) Create a CSV file named example1.scv with this content:

    @DataPoint,opc.tcp://[Your HH PC]:7011/HyperHistorian\\Configuration/LogGrp/OPCUA/Sine
    Value,Timestamp
    10,2011-03-08 5:14:00 PM
    100,2011-03-08 5:15:00 PM
    1000,2011-03-08 5:16:00 PM

    Note: Modify the timestamps and Hyper Historian address according to your setup.

    The default CSV plugin source path is C:\ProgramData\ICONICS\MergeWorX\Plugins\CSV\Source. Put your CSV file there.
     

  5. If the datapoint names in the CSV files are not fully-qualified Hyper Historian names or if you need to do some processing with data, then you must add MergeWorX tags to map the tags that are in the CSV file to Hyper Historian by creating MergeWorX tags, as described in the Creating a MergeWorX Tag topic.

  6. When you trigger the CSV plug-in (by clicking a button in GraphWorX as described above), MergeWorX engine searches for new files in Source location. It will find your CSV file and process it. When it is done the file will be moved to processed files location that is by default C:\ProgramData\ICONICS\MergeWorX\Plugins\CSV\Processed. Now you know the file was processed and you can see those three values in Hyper Historian.

  7. After testing your configuration, Review the Status of MergeWorX Processing.

See also:

MergeWorX