For Control Engineers

Explanation of concepts and architecture, understanding the platform.

Home → Start | Next | Platform | Tutorials | How-to | Reference | Connectors | Cases | Resources

Your Role & Focus Areas

Control engineers work with PLCs, HMIs, and SCADA systems. This guide helps you navigate FrameworX documentation for device connectivity, operator interfaces, and process control.

Core Responsibilities:

• Field device integration (PLCs, RTUs, instruments)
• Operator display development
• Alarm management and historian configuration
• Control logic implementation

Your Learning Path:

1. Connect devices and import tags
2. Build operator displays
3. Configure alarms and data logging
4. Implement control strategies

Foundation & Connectivity

Getting Started

System Overview:

• [First Solution - 5 min] - Build working demo
• [Solution Lifecycle Tutorials] - Development workflow
• [Designer Tutorial] - Your primary workspace

Device Connection

Essential Tutorials:

• [Devices Connection Tutorials] - PRIMARY FOCUS
  • Modbus, Allen-Bradley, Siemens configurations
  • Direct PLC tag import
• [Add Tags to UNS Tutorial] - Organize imported tags
• [Connectors Library] - Browse 100+ native drivers

By PLC Brand:

• Allen-Bradley → [EtherNet/IP setup], [ControlLogix import]
• Siemens → [S7 protocol], [TIA Portal integration]
• Modbus → [TCP/RTU configuration], [Register mapping]

Operator Interface Development

HMI Display Creation

Core Learning:

• [Displays Design Tutorials] - CRITICAL PATH
  • Canvas displays for P&ID graphics
  • Dashboard displays for KPIs
  • Symbol library usage
• [Canvas Displays vs Dashboards] - Choose right approach
• [Runtime Tutorial] - Test your displays

Standards & Best Practices

• [ISA-101 HMI Standards] - Display guidelines
• [High Performance HMI] - Effective visualization

Process Control Implementation

Alarm Management

• [Alarms and Audit-Trail Tutorial] - Configuration basics
• [ISA-18.2 Alarm Management] - Industry standards
• [Alarm Rationalization Guide] - Prevent alarm floods

Data Historian

• [Historian Module Tutorials] - Time-series data logging
• [Trending Configuration] - Real-time and historical trends
• [Data Retention Policies] - Storage optimization

Control Logic

• [Scripts and Data Enrichment Tutorial] - Automation logic
• [Expression Editor] - Simple calculations
• [Control Examples Library] - Pre-built functions

Advanced Technologies

Edge Computing

• [Cisco IR1101 Container Tutorial] - Router deployment
• [MQTT Broker and Client Tutorial] - IoT protocols
• [Store and Forward] - Handle intermittent connections

Modern Enhancements

• [Edge AI with ML.NET Tutorial] - Anomaly detection
• [Python and .NET Integration] - Custom algorithms
• [OPC UA Implementation] - Unified architecture

Quick Task Reference

Recommended Workflow

Week 1: Connect devices → Import tags → Verify communication Week 2: Build displays → Create symbols → Test visualization Week 3: Configure alarms → Setup historian → Build trends Week 4: Add control logic → Implement calculations → Complete project

Resources & Support

Documentation:

• [Devices Module (Reference)] - Complete driver details
• [Displays Module (Reference)] - Display configuration
• [Alarms Module (Reference)] - Alarm system details

Troubleshooting:

• Can't connect? → [Device communication guide]
• Display issues? → [Performance optimization]
• Alarm floods? → [Alarm management best practices]

Community:

• [Forum - Devices section]
• [Sample projects]
• [Symbol library]

Claude can make mistakes.
Please double-check responses.

In this section...