Versions Compared

Old Version 8

changes.mady.by.user admin

Saved on

compared with

New Version 9

changes.mady.by.user admin

Saved on

Key

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



Your Focus Areas in FrameworX

As a control engineer working with

Learning Path - Control Engineers

Target Audience

...

PLCs, HMIs, and SCADA systems

...

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

, this guide helps you navigate FrameworX documentation efficiently.

Start Here

Core Concepts to Understand

Platform Overview

  • [Architecture] - Understand system topology and deployment
  • [Technology Foundation] → [Vendor-Native Drivers vs OPC UA] - Critical for device connectivity
  • [The Four Pillars] - Focus on P2: Process Modules

Essential Tutorials

Get Connected Quickly

  • [First Solution - 5 min] - Quick system overview
  • [Connect to a Modbus Device Tutorial] - Most common starting point
  • [P2: Process Modules / Industrial Operations Tutorial] - Your primary learning path

Key How-to Guides

Daily Tasks

  • [Devices Module (How-to Guide)] - Step-by-step device configuration
  • [Alarms Module (How-to Guide)] - Alarm setup and management
  • [Historian Module (How-to Guide)] - Data logging configuration
  • [Displays Module (How-to Guide)] - Building operator screens

Technical References

Device Communication

  • [Devices Module (Reference)] - Complete driver documentation
  • [Connectors Library] - Browse 100+ native drivers
  • Communication protocols you likely need:
    • Allen-Bradley EtherNet/IP
    • Siemens S7
    • Modbus TCP/RTU
    • OPC UA

Standards Compliance

Relevant to control engineering:

  • [ISA-95 Implementation] - Equipment hierarchy
  • [ISA-18.2 Alarm Management] - Alarm standards
  • [IEC 61131-3] - Programming languages support

Setting Up PLCs

  1. Review [Connectors Library] for your PLC brand
  2. Follow [Devices Module (How-to Guide)]
  3. Check [Device Communication Troubleshooting]

Building HMIs

  1. Start with [Displays Module (Concept)]
  2. Use [Canvas Displays vs Dashboards] to choose approach
  3. Apply [HMI Design Best Practices]

Implementing Alarms

  1. Read [Alarms Module (Concept)] for philosophy
  2. Configure using [Alarms Module (How-to Guide)]
  3. Follow [ISA-18.2 Alarm Management] standards

Recommended Learning Sequence

Week 1: Connectivity

  • Connect your first PLC
  • Import tags to UNS
  • Verify communication

Week 2: Visualization

  • Build basic displays
  • Create motor/valve symbols
  • Test runtime operation

Week 3: Alarms & History

  • Configure process alarms
  • Set up data logging
  • Build trending displays

Week 4: Integration

  • Add control logic
  • Implement calculations
  • Complete your first project

Community Resources

  • [Community Forum - Devices Section] - Device-specific questions
  • [Sample Projects] - Control system examples
  • [Symbol Library] - Pre-built HMI components

Need Help?

Common Issues:

  • PLC won't connect → [Device Troubleshooting Guide]
  • Tags not updating → [UNS Configuration Guide]
  • Display performance → [Optimization Best Practices]

Support Channels:

  • [Technical Support] - Direct assistance
  • [Community Forum] - Peer support
  • [Knowledge Base] - Searchable solutions

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

...