Step 6: Configuring a Tag

Optional Step - Tag Groups & Subgroups

TOP Server provides the ability to configure optional groups and subgroups to provide for multi-level organization of tags.

Tag groups allow you to tailor the layout of OPC data in logical groupings that fit the needs of your application.

Using tag groups allows multiple sets of identical tags to be added under the same device. This can be very convenient when a single device handles a number of similar machine segments. From an OPC client standpoint, the use of tag grouping allows you to segregate your OPC data into smaller tag lists, which can make finding a specific tag easier when browsing the server.

To add a new tag group to your project, right click on either an existing device or tag group branch and select "New Tag Group" from the context menu.

Enter in a logical Name for your tag group.

Adding Tags

Next you will need to add tags to your configuration. 

NOTE: Tags aren't required if your Client can support the device memory address in it’s tag database.  Click to learn more about TOP Server’s flexible tag configuration options for static and dynamic tags.

It is recommended that at least one valid tag be configured for each device for communications checking with the OPC Quick Client.

Highlight the device or group you want to add you tags to and then click “Click to add a static tag” as shown here. You can also use the add tag icon or the Edit menu, but make sure the correct location for the tags is highlighted first. The following screen will be displayed:

1. Enter a tag Name and Address. The tag name can be any meaningful name while the address must be the correct syntax for the device memory address.
    
2. The Hints iconcan be used to help determine the available memory addresses and ranges for your chosen device model from when you configured your device.
   
3. The Check Address iconcan be used to have TOP Server attempt to validate if the address you have entered is valid in memory type and range for the chosen device model.  Note that in some drivers if you pick an open device model, TOP Server will check for a valid memory type but will not check to see if the address is within a valid range.
   
4. You can also enter a longer, optional Description.
    
5. Data type can often just be left at default unless your using a device that uses multiple Word or Byte addresses to support larger data types such as float.
    
6. The Scan rate is only used with DDE type connectivity and does not need to be set if you use the Scan rate override in the Alias map for DDE connections.
    
7. Scaling can also be set at this point if the device and client values need to be in different units. Click here for more information on TOP Server scaling.
   
   
   

This completes your configuration of a TOP Server driver.  Next you could use the OPC Quick Client to test your configuration as you did in Step 3 with the sample simulation project.

Or you could connect your HMI/SCADA application using one of our HMI/SCADA application notes.

More Information on Startup & Testing Features can be found here.