Versions Compared

Old Version 8

changes.mady.by.user admin

Saved on

compared with

New Version Current

changes.mady.by.user admin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Role-specific learning path for device connectivity, operator interfaces, and process control

Next → Control | IT | Operations | System Integrators

Learning Topics

Control engineers work with

Learning Path - Control Engineers

Target Audience

...

PLCs, HMIs, and SCADA systems

...

. This guide navigates you through FrameworX documentation for device connectivity, operator

...

interfaces, and

...

process control.

...

Your Role

...

Primary Focus

...

Essential Pages

...

Advanced Topics

...

Control Engineer

...

Field connectivity
Process Control

...

Solution Lifecycle
P1: UNS Foundation

...

P2: Process Modules
Devices Module

...

Alarms Module
Historian Module

Core Responsibilities:

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

Table of Contents
maxLevel2
minLevel2
excludeLearning
stylenone
printablefalse


Excerpt

Understand the Platform and Modules:

  • Platform Overview - review the entire section. For Technology, focus only on your areas of interest.
  • Modules - review the Solution Lifecycle and the modules in your area of interest.

Learn by doing:

Connectivity - Devices Module

Essential Tutorials:

  • [Devices Connection Tutorials] - PRIMARY FOCUS
    • [Connect to a Modbus Device Tutorial]
    • [Connect to a MQTT broker Tutorial]
  • [Add Tags to UNS Tutorial] - Organize imported tags
  • [Connectors Library] - Browse 100+ native drivers

By PLC Brand, Connectors:

  • Allen-Bradley → [AB Rockwell ControlLogix Connector]
  • Siemens → [Siemens S7 Devices Connector]
  • Modbus → [Modbus Master Connector]
  • Codesys → [Codesys PLC Handler Connector]

Operator Interface Development

HMI Display Creation

Core Learning:

  • [Displays Design Tutorials] - CRITICAL PATH
    • [Design Canvas Displays Tutorials] - P&ID graphics
    • [Design Dashboard Displays Tutorials] - KPIs
    • [Add Symbols to Displays Tutorials] - Reusable components
  • [Layouts and Navigation Tutorial] - Multi-screen navigation
  • [Runtime Tutorial] - Test your displays

Display Types

  • [Creating Canvas Displays How-to Guide] - Process diagrams
  • [Creating Dashboard Displays How-to Guide] - Responsive layouts

Industrial and Business Operations Modules

Alarm Management

  • [Alarms and Audit Trail Tutorial] - Configuration basics
  • [Alarms Module How-to Guide] - Detailed procedures
  • [Alarm Areas Example] - Organization strategies

Data Historian

  • [Historian Module Tutorial] - Time-series data logging
  • [TrendChart Control Reference] - Real-time and historical trends
  • [Historian Export to CSV Example] - Data export

Control Logic

  • [Scripts Module Tutorial] - Automation logic
  • [Scripts Expressions Reference] - Simple calculations
  • [Scripting Code Library] - Pre-built functions

Advanced Technologies

Edge Computing

  • [Edge AI with ML.NET Tutorial] - Anomaly detection
  • [Edge AI with MCP Tool Tutorial] - AI integration
  • [MQTT Tutorials] - IoT protocols

Modern Protocols

  • [OPC UA Client Connector] - Client implementation
  • [OPC UA Server Connector] - Server functionality
  • [MQTT Client Connector] - MQTT integration

Quick Task Reference

Common TaskTutorial/How-toReference
Connect to PLC[Devices Connection Tutorials][Devices Protocols Reference]
Import PLC tags[Solution Import Tags Reference][UNS Tags Reference]
Build motor control[Displays Symbols Reference][Symbols Control Reference]
Setup tank alarms[Alarms Module How-to Guide][Alarms Items Reference]
Create trends[Historian Module Tutorial][TrendChart Control Reference]
Add control logic[Scripts Module Tutorial][Scripts Tasks Reference]

Recommended Learning Schedule

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

Examples:

  • [Process HMI Example] - Complete HMI project
  • [Andon Dashboards Example] - Production monitoring
  • [OEE Calculation Example] - Performance metrics

Community:

  • [Getting Help] - Support options
  • Technical Tuesday sessions on Discord

In this section...

Page Tree
root@parent


  

Learning Objectives

  • Connect and configure industrial devices
  • Design effective operator UI
  • Implement alarm management strategies
  • Create control logic and calculations
  • Build trending and historical displays

Week 1: Foundation

Day 1-2: Device Communication

Exercise 1: Driver Selection

  1. Navigate to Designer → Devices
  2. Review available drivers:
    • Allen-Bradley (EtherNet/IP)
    • Siemens (S7)
    • Modbus (TCP/RTU)
    • OPC UA
  3. Document which drivers match your PLCs

Lab: Connect to Allen-Bradley ControlLogix

  1. Create Channel:
    • Protocol: Allen-Bradley ControlLogix
    • Connection: Ethernet
    • Timeout: 3000ms
  2. Add Node:
  3. Import Tags:
    • Use automatic tag import
    • Map to UNS namespace
  4. Verify Communication:
    • Check status indicators
    • Monitor update rates

Day 3-4: HMI Design Fundamentals

Standard Display Layout

Code Block
???????????????????????????????
? Header (Title, Time, Alarms)?
???????????????????????????????
?                             ?
?   Main Process Graphic      ?
?   (P&ID representation)     ?
?                             ?
???????????????????????????????
?      Navigation Bar         ?
???????????????????????????????

Exercise: Build Motor Control Faceplate

  1. Create new symbol "MotorControl"
  2. Add elements:
    • Status indicator (Running/Stopped)
    • Start/Stop buttons
    • Speed display (if VFD)
    • Fault indicator
    • Local/Remote mode
  3. Link to Motor UDT
  4. Test in runtime

Day 5: Alarm Configuration

Alarm Priority Matrix

Priority

Range

Color

Response Time

Consequence

Critical

1-200

Red

Immediate

Safety shutdown

High

201-400

Orange

10 minutes

Process upset

Medium

401-600

Yellow

30 minutes

Efficiency loss

Low

601-999

Blue

Next shift

Maintenance required

Lab: Configure Process Alarms

Tank Level Alarm Configuration:

Alarm

Trigger

Priority

Deadband

Delay On

Delay Off

HiHi

95%

250

2%

5 sec

3 sec

Hi

85%

400

2%

5 sec

3 sec

Lo

15%

400

2%

5 sec

3 sec

LoLo

5%

250

2%

5 sec

3 sec

Week 2: Advanced Topics

Day 1-2: Control Logic Implementation

Pump Control Script Example

Code Block
languagecsharp
public void PumpControl()
{
    // Read process values
    float tankLevel = @Tag.Tank01.Level;
    float setpoint = @Tag.Tank01.Setpoint;
    bool pumpAvailable = @Tag.Pump01.Available;
    
    // Control logic
    if (pumpAvailable)
    {
        if (tankLevel < (setpoint - 5))
        {
            @Tag.Pump01.StartCmd = true;
            @Tag.Pump01.Speed = CalculateSpeed(tankLevel, setpoint);
        }
        else if (tankLevel > (setpoint + 2))
        {
            @Tag.Pump01.StartCmd = false;
        }
    }
    
    // Alarm generation
    if (!pumpAvailable && tankLevel < 10)
    {
        @Tag.Alarms.LowLevelNoPump = true;
    }
}

private float CalculateSpeed(float level, float sp)
{
    float error = sp - level;
    return Math.Max(30, Math.Min(100, error * 5));
}

Day 3-4: Trending Configuration

Trend Setup Parameters

Component

Configuration

Time Axis

Real-time (last hour), Historical (date range), Resolution (1 sec - 1 day)

Y-Axes

Primary (0-100%), Secondary (0-150°F), Auto-scale option

Pens

Multiple process values with distinct colors

Exercise: Build Trending Display

  1. Create new display "ProcessTrends"
  2. Add trend object
  3. Configure 4 pens for related process values
  4. Add time navigation controls
  5. Include data export button

Day 5: Performance Optimization

Optimization Guidelines

Area

Technique

Benefit

Scan Rates

Match process dynamics

Reduce network load

Display Updates

Limit animations

Improve client performance

Alarm Deadbands

Prevent chattering

Reduce alarm floods

Script Efficiency

Avoid loops in expressions

Lower CPU usage

Standard Component Library

Motors

  • Motor_Simple (On/Off)
  • Motor_VFD (Variable Speed)
  • Motor_Reversing (Forward/Reverse)

Valves

  • Valve_OnOff
  • Valve_Control (Analog)
  • Valve_3Way

Process Equipment

  • Pump_Centrifugal
  • Tank_Level
  • Heat_Exchanger

Instruments

  • Transmitter_Analog
  • Switch_Digital
  • Controller_PID

Communication Quick Reference

PLC Type

Protocol

Default Settings

Allen-Bradley

EtherNet/IP

Slot 0, RPI 100ms

Siemens

S7 TCP

Rack 0, Slot 2

Modbus Devices

Modbus TCP

Port 502, Unit ID 1

Schneider

Modbus TCP

Port 502, Holdings

Omron

FINS

Port 9600, Node 1

Troubleshooting Guide

Issue

Check

Solution

PLC won't connect

IP address, subnet

Verify network settings

Tags not updating

Point mapping

Check addresses match PLC

Alarms flooding

Deadband, delays

Adjust alarm settings

HMI slow

Graphics complexity

Simplify animations

Trends gaps

Historian settings

Check storage configuration

Certification Path

FrameworX Control Specialist

  • Prerequisites: FrameworX Certified Developer + control experience
  • Focus Areas: Advanced control logic, PLC integration, alarm management
  • Format: Online exam + practical project
  • Duration: 4 hours

Additional Resources

...