Overview

FrameworX 10.1 provides comprehensive connectivity options to integrate with industrial equipment, enterprise systems, and cloud platforms. With 70+ native drivers included at no additional cost, protocol standards support, and certified partner integrations, you can connect to virtually any data source in your industrial environment.

Where It Fits in Your Solution

Connectivity & Integration components work across all four pillars of the FrameworX architecture:

Native Drivers - All Included, No Additional Licenses

FrameworX includes 70+ native communication drivers with your solution license. Scale by I/O points only - never pay extra for protocol support.

Popular Manufacturers

By Protocol Category

Protocol Standards

MQTT & Sparkplug B

OPC UA

REST APIs & Web Services

Partner Integrations

Historian & Time-Series

Cloud Platforms

Specialized Systems

Configuration in Designer

Adding a Device Connection

  1. Navigate to Devices → Channels
  2. Click New Channel and select protocol type
  3. Configure channel properties (IP address, port, timeout)
  4. Add Node under the channel for specific device
  5. Create Points and map to UNS tags

Setting Up OPC UA Server

  1. Go to Devices → OPC UA Server
  2. Enable server and set endpoint URL
  3. Configure security policies and certificates
  4. Select tags to expose via OPC UA
  5. Set update rates and quality codes

Configuring MQTT Connection

  1. Navigate to Devices → MQTT Client
  2. Enter broker address and credentials
  3. Configure topic structure and QoS levels
  4. Map topics to tags using templates
  5. Enable Sparkplug B if required

Best Practices

Driver Selection

Performance Optimization

Security Considerations

Troubleshooting

SymptomLikely CauseSolution
Driver not connectingIncorrect IP or portVerify network settings and firewall rules
Intermittent data lossNetwork congestionAdjust polling rates, implement buffering
High CPU usageToo many synchronous readsUse asynchronous operations, optimize scan groups
Certificate errorsExpired or untrusted certsUpdate certificates, check system time
Tag quality "Bad"Communication timeoutIncrease timeout values, check physical connection

Common Integration Patterns

Pattern 1: PLC to Cloud

Connect field PLCs via native drivers, process data locally, send filtered data to cloud via MQTT/HTTPS

Pattern 2: Multi-Protocol Gateway

Use FrameworX as protocol converter between legacy systems (Modbus, DF1) and modern standards (OPC UA, MQTT)

Pattern 3: Store and Forward

Buffer data locally during network outages, automatically forward when connection restored

Pattern 4: Redundant Data Paths

Configure primary Ethernet connection with secondary serial backup for critical devices

Related Modules

AI Assistant Data

<details> <summary>Structured Information for AI Tools</summary>

json

{
  "module": "Connectivity & Integration",
  "category": "Infrastructure",
  "relatedPillars": ["UNS", "Process", "Application"],
  "keyFeatures": {
    "nativeDrivers": 70,
    "protocols": ["MQTT", "OPC UA", "Modbus", "EtherNet/IP"],
    "cloudPlatforms": ["AWS", "Azure", "Google Cloud"],
    "licensing": "All-inclusive, scale by I/O points only"
  },
  "commonTasks": [
    "Configure PLC connection",
    "Setup MQTT broker connection",
    "Enable OPC UA server",
    "Map external data to tags",
    "Configure redundant connections"
  ],
  "dependencies": {
    "required": ["Devices Module", "Tags"],
    "optional": ["Scripts", "Datasets", "Historian"]
  },
  "typicalUsers": ["Control Engineers", "System Integrators", "IT Professionals"]
}

</details>

Claude can make mistakes.
Please double-check responses.