Learn how to create and organize real-time data tags in FrameworX's Unified Namespace. Tags are the foundation of any solution, representing data points from devices, calculations, or user inputs.
→ Tutorial | Concept | How-to Guide | Reference
On this page:
What You'll Learn
- Create different tag types
- Organize tags with folders
- Configure tag properties
- Use UserTypes (UDTs)
Prerequisites
- FrameworX Designer installed
- Basic understanding of data types
Step 1: Understanding Tag Types
FrameworX supports these fundamental tag types:
Type | Use Case | Example |
---|---|---|
Digital | On/Off states | Motor_Running |
Integer | Whole numbers | Product_Count |
Double | Decimal values | Temperature |
Text | Strings | Batch_ID |
DateTime | Timestamps | Last_Update |
Step 2: Create Your First Tags
- Open Unified Namespace → Tags
- Click first empty row to add tag
- Create these example tags:
Digital Tag:
- Name:
Motor1_Running
- Type: Digital
- Description: Main motor status
Analog Tag:
- Name:
Tank1_Level
- Type: Double
- Min: 0, Max: 100
- Units: %
- Description: Tank level percentage
String Tag:
- Name:
Current_Recipe
- Type: Text
- Initial Value: "Recipe_001"
Step 3: Organize with Folders
- Right-click in tag grid → New Folder
- Name:
Production_Line_1
- Drag tags into folder
- Create hierarchy:
Production_Line_1/
Motors/
Motor1_Running
- Tanks/
- Tank1_Level
- Recipes/
- Current_Recipe
Step 4: Configure Tag Properties
Select a tag and configure:
Scaling (for analog tags):
- Engineering Units: Set Min/Max
- Raw Scale: Device Min/Max
- Auto-scales between device and engineering values
Retentive:
- Enable to preserve value through restart
Initial Value:
- Starting value when solution runs
Step 5: Create UserType
- Navigate to Unified Namespace → UserTypes
- Create new type:
Motor
- Add members:
- Running (Digital)
- Speed (Double)
- Hours (Double)
- Fault (Digital)
- Return to Tags
- Create tag from userType:
- Name:
Motor2
- Type: Select your Motor template
- Name:
Testing Your Tags
- Click Run (F5)
- Open Unified Namespace → Monitor
- See your tags updating
- Double-click to modify values
Best Practices
- Use consistent naming:
Area_Equipment_Signal
- Group related tags in folders
- Document with descriptions
- Set appropriate engineering units
- Use templates for repeated structures
Next Steps
- [Connect to Devices] - Get real data
- [Define Alarms] - Add alarm conditions
- [Operator UI Design] - Display tag values
In this section...
The root page @parent could not be found in space 93Draft.