| Table of Contents |
|---|
| maxLevel | 2 |
|---|
| minLevel | 2 |
|---|
| indent | 10px |
|---|
| exclude | Steps |
|---|
| style | none |
|---|
|
Enable OPC UA Server
Expose your UNS to external OPC UA clients.
Steps
- Navigate to Runtime → Startup
- In Startup Modules, check OPCServer
- Navigate to Unified Namespace → Data Servers
- Click the OPC UA Server edit icon [??]
- Configure settings:
- Port: 4840 (default)
- Security Mode: Select based on requirements
- Authentication: Configure user access
- Click OK to save
- Restart solution for changes to take effect
Verify
- Start the solution
- Use an OPC UA client to connect to
opc.tcp://localhost:4840 - Browse the address space to see your UNS tags
Enable MQTT Broker
Provide publish/subscribe access for IoT devices and cloud platforms.
Steps
- Navigate to Runtime → Startup
- In Startup Modules, check MQTTBroker
- Navigate to Unified Namespace → Data Servers
- Click the MQTT Broker edit icon [??]
- Configure settings:
- TCP Port: 1883 (default)
- WebSocket Port: 8083 (or 0 to disable)
- Authentication: Configure as needed
- TLS: Enable if required
- Click OK to save
- Restart solution for changes to take effect
Verify
- Start the solution
- Use an MQTT client to connect to
localhost:1883 - Subscribe to topics to see your UNS data
Enable MCP for Runtime
Allow AI models to query live solution data.
Steps
- Navigate to Scripts → Classes
- Create a new Script Class or use existing
- (Optional) Add custom MCP tools with [McpTool] attribute:
[McpTool("GetTemperature", "Returns current temperature")]
public double GetTemperature(string tagPath)
{
return Tag[tagPath].Value;
}
- Save and build the solution
- Start the solution
- Configure your AI client (e.g., Claude Desktop) to connect
Edit claude_desktop_config.json:
{
"mcpServers": {
"MySolution": {
"command": "<ProductPath>\\fx-10\\net8.0\\TMCPServerStdio\\TMCPServerStdio.exe",
"args": ["/host:127.0.0.1", "/port:<port>"],
"transport": "stdio"
}
}
}
Verify
- Restart Claude Desktop
- Check Settings → Developer shows "running"
- In a new chat, verify solution appears in "Search and Tools"
→ See AI MCP for Runtime Connector for detailed setup → See AI MCP for Runtime Tutorial for complete walkthrough
Enable DataHub Service
Synchronize data between multiple FrameworX solutions.
Steps (Publisher - Edge Solutions)
- Navigate to Runtime → Startup
- In Execution Environment, check Publish to a DataHub Service
- Click the gear icon [??] to configure
- Set Access Mode to appropriate level
- Click OK to save
- Restart solution
Steps (Subscriber - UI Solution)
- Navigate to Runtime → Startup
- In Execution Environment, check Publish to a DataHub Service
- Click the gear icon [??] to configure
- Set Listening Port: 30001 (default)
- Configure Access Key if required
- Click OK to save
- Restart solution
Verify
- Start all solutions (edge + UI)
- Navigate to Unified Namespace → Services Monitor
- Verify DataHub connections show "Connected"
→ See Data Hub Communication Service for architecture details
Verify All Services
After enabling services, verify they're running:
- Start the solution (Runtime → Startup → Run Startup)
- Navigate to Unified Namespace → Services Monitor
- Check status for each enabled service:
| Service | Expected Status |
|---|
| OPC UA Server | Running on port 4840 |
| MQTT Broker | Running on port 1883 |
| MCP for Runtime | Running (if Scripts enabled) |
| DataHub | Connected / Listening |
Troubleshooting
Service Won't Start
- Check if port is already in use by another application
- Verify the service is checked in Runtime → Startup
- Check Windows Firewall allows the port
External Client Can't Connect
- Verify the solution is running
- Check firewall rules for the port
- Verify authentication settings match client configuration
- For remote access, ensure IP/hostname is correct (not localhost)
MCP Not Showing in Claude
- Verify
claude_desktop_config.json path is correct - Restart Claude Desktop after config changes
- Check solution is running before starting Claude
See Also
- Data Servers — Concept overview
- UNS Data Servers Reference — All settings and options
- AI MCP for Runtime Connector — MCP details