How is the OPC-DA file structured for importing tags with folders?

Overview

This page explains how to structure a file for importing OPC-DA tags, including how folders and tags are defined within a single import file.

Key Concepts

1. Single File, Multiple Folders

• You do not need to import folders separately.

• A single file can define and load multiple folders.

• Each folder is declared using a special directive.

2. Folder Definition (#folder)

The #folder directive defines where tags will be organized.

Format:

Notes:

• Values are separated by commas.

• Both top-level and sub-folder must be provided.

3. Tag Assignment

• All lines following a #folder definition belong to that folder.

• Tags use dot notation, not commas.

Format:

4. File Format Clarification

{info:title=Important} Although the file resembles a CSV, it may not look like a typical one.

• The separator is a comma (,) — not a space.

• Tag lines themselves do not use commas. {info}

Example File Structure

How it works

The system reads the #folder line.

All following tag entries are assigned to that folder.

When a new #folder appears, subsequent tags are assigned to the new folder.

Best Practices

• Always define folders before listing tags.

• Keep naming consistent between folder names and tag prefixes.

• Avoid unintended extra spaces.

• Ensure correct comma placement in #folder lines.

Common Pitfalls

|| Issue || Explanation || | Using spaces instead of commas | Breaks folder parsing | | Using commas in tag lines | Invalid format | | Missing #folder before tags | Tags may not be assigned correctly | | Inconsistent naming | Causes mismatched folder/tag mapping |

Summary

{panel:title=Quick Summary}

• Use #folder to define folder structure

• Use comma-separated values only for folder definitions

• Use dot notation for tags

• Multiple folders can be handled in a single import file {panel}