Learn PLCs free
Intermediate15 min readWater & Wastewater

B&R Industrial Automation Data Types for Pump Control

Learn Data Types programming for Pump Control using B&R Industrial Automation Automation Studio. Includes code examples, best practices, and step-by-step implementation guide for Water & Wastewater applications.

💻
Platform
Automation Studio
📊
Complexity
Intermediate
⏱️
Project Duration
2-4 weeks

Optimizing Data Types for Pump Control applications in B&R Industrial Automation's Automation Studio requires measuring the baseline and understanding the demands of Water & Wastewater. This guide focuses on techniques you can evaluate with task timing, scan-time traces, memory use, and controlled fault tests.

For intermediate applications like Pump Control, check which diagnostics and profiling tools are available in your installed Automation Studio version. Controller model, firmware, task configuration, communications, and I/O update behavior can all affect the result.

Performance considerations for Pump Control systems extend beyond basic functionality. Critical factors include 5 sensor types, 5 actuators, communications load, and the need to handle pressure regulation. Evaluate whether memory optimization helps the design, then measure the actual task and I/O timing on the selected configuration.

This guide covers memory management, execution order, Data Types-specific tuning, and a repeatable measurement plan for Pump Control applications. Treat every optimization as a hypothesis: record the baseline, change one variable, retest the same workload, and keep the change only when the measured result and code maintainability both improve.

B&R Industrial Automation Automation Studio for Pump Control

Automation Studio is a programming environment associated with B&R Industrial Automation controller families such as X20 CPU series, X90 Mobile, APC2100. This guide uses Data Types terminology from the supplied guide dataset, but controller capabilities and language support can change by model, firmware, software edition, and license.

Verify Before You Start:

  • The selected controller supports the required Data Types constructs

  • The project version matches the installed Automation Studio release

  • Required communications, motion, safety, and simulation options are licensed

  • Firmware and device-description files are compatible with the project

  • The vendor manuals used for the design match the exact hardware revision


Application Planning:

For a Pump Control exercise, map the required inputs and outputs before writing logic. The example considers 5 sensor types, including Pressure transmitters, Flow meters, Level sensors, and 5 actuator types.

Control Equipment for Pump Control:

  • Centrifugal pumps for high flow applications

  • Positive displacement pumps for metering

  • Submersible pumps for wet well applications

  • Booster pump systems for pressure maintenance


Controller-family references used in this guide include:

  • X20 CPU series: Confirm CPU, I/O, memory, communications, and Data Types support in the current selection guide

  • X90 Mobile: Confirm CPU, I/O, memory, communications, and Data Types support in the current selection guide

  • APC2100: Confirm CPU, I/O, memory, communications, and Data Types support in the current selection guide

  • APC3100: Confirm CPU, I/O, memory, communications, and Data Types support in the current selection guide


Hardware Selection Checklist:

  • Count local and remote I/O, including planned expansion

  • Measure the required task and communications update rates

  • Identify memory, data-retention, diagnostics, and cybersecurity requirements

  • Treat safety functions as a separate, standards-led design activity

  • Confirm lifecycle status, regional availability, licensing, and support


Source and Validation Note:

This page does not represent a vendor certification or a hardware acceptance test. Use current B&R Industrial Automation manuals, release notes, and safety documentation as the authority for product-specific behavior. Validate adapted logic in a simulator or isolated test setup before connecting it to equipment.

Investment Considerations:

For Pump Control projects, compare hardware, software licensing, training, engineering, test equipment, commissioning, spares, and ongoing support. Obtain current pricing and lifecycle information directly from the vendor or an authorized regional supplier.

Understanding Data Types for Pump Control

PLC data types define how values are stored, their valid ranges, and operations that can be performed. Proper type selection ensures accuracy and memory efficiency.

Execution Model:

For Pump Control applications, Data Types offers significant advantages when all programming applications - choosing correct data types is fundamental to efficient plc programming.

Core Advantages for Pump Control:

  • Memory optimization: Critical for Pump Control when handling intermediate control logic

  • Type safety: Critical for Pump Control when handling intermediate control logic

  • Better organization: Critical for Pump Control when handling intermediate control logic

  • Improved performance: Critical for Pump Control when handling intermediate control logic

  • Enhanced maintainability: Critical for Pump Control when handling intermediate control logic


Why Data Types Fits Pump Control:

Pump Control systems in Water & Wastewater typically involve:

  • Sensors: Pressure transmitters for discharge and suction pressure, Flow meters (magnetic, ultrasonic, or vortex), Level transmitters for tank or wet well level

  • Actuators: Variable frequency drives (VFDs) for speed control, Motor starters (DOL or soft start), Control valves for flow regulation

  • Complexity: Intermediate with challenges including Preventing cavitation at low suction pressure


Control Strategies for Pump Control:

  • constant: Maintain fixed speed or output

  • pressure: PID control to maintain discharge pressure setpoint

  • flow: PID control to maintain flow rate setpoint


Programming Fundamentals in Data Types:

Data Types in Automation Studio follows these key principles:

1. Structure: Data Types organizes code with type safety
2. Execution: Scan-cycle integration defines when the 5 sensor inputs are read and processed; verify the timing on the selected controller
3. Data Handling: Proper data types for 5 actuator control signals

Best Practices for Data Types:

  • Use smallest data type that accommodates the value range

  • Use REAL for analog values that need decimal precision

  • Create UDTs for frequently repeated data patterns

  • Use meaningful names for array indices via constants

  • Document units in comments (e.g., // Temperature in tenths of degrees)


Common Mistakes to Avoid:

  • Using INT for values that exceed 32767

  • Losing precision when converting REAL to INT

  • Array index out of bounds causing memory corruption

  • Not handling negative numbers correctly with unsigned types


Typical Applications:

1. Recipe management: Directly applicable to Pump Control
2. Data logging: Related control patterns
3. Complex calculations: Related control patterns
4. System configuration: Related control patterns

Understanding these fundamentals prepares you to implement effective Data Types solutions for Pump Control using B&R Industrial Automation Automation Studio.

Implementing Pump Control with Data Types

Pump control systems use PLCs to regulate liquid flow in industrial processes, water treatment, and building services. These systems manage pump operation, protect equipment, optimize energy use, and maintain process parameters.

This walkthrough demonstrates practical implementation using B&R Industrial Automation Automation Studio and Data Types programming.

System Requirements:

A typical Pump Control implementation includes:

Input Devices (Sensors):
1. Pressure transmitters for discharge and suction pressure: Critical for monitoring system state
2. Flow meters (magnetic, ultrasonic, or vortex): Critical for monitoring system state
3. Level transmitters for tank or wet well level: Critical for monitoring system state
4. Temperature sensors for bearing and motor monitoring: Critical for monitoring system state
5. Vibration sensors for predictive maintenance: Critical for monitoring system state

Output Devices (Actuators):
1. Variable frequency drives (VFDs) for speed control: Primary control output
2. Motor starters (DOL or soft start): Supporting control function
3. Control valves for flow regulation: Supporting control function
4. Isolation valves (actuated for remote operation): Supporting control function
5. Check valves to prevent backflow: Supporting control function

Control Equipment:

  • Centrifugal pumps for high flow applications

  • Positive displacement pumps for metering

  • Submersible pumps for wet well applications

  • Booster pump systems for pressure maintenance


Control Strategies for Pump Control:

  • constant: Maintain fixed speed or output

  • pressure: PID control to maintain discharge pressure setpoint

  • flow: PID control to maintain flow rate setpoint

  • level: Control tank/wet well level within band


Implementation Steps:

Step 1: Characterize pump curve and system curve

In Automation Studio, characterize pump curve and system curve.

Step 2: Size VFD for application (constant torque vs. variable torque)

In Automation Studio, size vfd for application (constant torque vs. variable torque).

Step 3: Implement primary control loop (pressure, flow, or level)

In Automation Studio, implement primary control loop (pressure, flow, or level).

Step 4: Add pump protection logic (minimum flow, temperature, seal)

In Automation Studio, add pump protection logic (minimum flow, temperature, seal).

Step 5: Program lead/lag sequencing with alternation

In Automation Studio, program lead/lag sequencing with alternation.

Step 6: Implement soft start/stop ramps for smooth operation

In Automation Studio, implement soft start/stop ramps for smooth operation.


B&R Industrial Automation Function Design:

B&R is famous for mapp Technology: a library of pre-engineered FBs covering motion (mapp Motion), robotics (mapp Robotics), HMI (mapp View), alarming (mapp Alarm), recipes (mapp Recipe), data logging (mapp Logger), auditing (mapp Audit), and cybersecurity (mapp Security). OEMs build atop mapp components rather than reimplementing. Private libraries of OEM-specific FBs are common, maintained in versioned Automation Studio libraries.

Common Challenges and Solutions:

1. Preventing cavitation at low suction pressure

  • Solution: Data Types addresses this through Memory optimization.


2. Managing minimum flow requirements

  • Solution: Data Types addresses this through Type safety.


3. Coordinating VFD speed with system pressure

  • Solution: Data Types addresses this through Better organization.


4. Handling pump cycling with varying demand

  • Solution: Data Types addresses this through Improved performance.


Safety Considerations:

  • Dry run protection using flow or level monitoring

  • Overtemperature protection for motor and bearings

  • Overload protection through current monitoring

  • Vibration trips for mechanical failure detection

  • Emergency stop with proper system depressurization


Performance Metrics:

  • Task and I/O timing: Record minimum, average, and maximum values under a defined test load

  • Accuracy: Define an acceptable tolerance and compare it with calibrated reference measurements

  • Throughput: Count completed cycles over a fixed interval and record rejected or incomplete cycles

  • Fault response: Measure detection, safe-state, alarm, and recovery behavior for each test case

  • Resource use: Record memory, communications load, and diagnostic-buffer behavior

B&R Industrial Automation Diagnostic Tools:

Automation Studio integrated debugger with breakpoints in every IEC language,System Diagnostics Manager — System-wide runtime health with historical retention,mapp View Diagnostic pages — ready-made diagnostic overlays for machine operators,ARsim integrated simulator — full offline machine testing without hardware,Motion commissioning via mapp Motion oscilloscope — waveform view during axis tuning,Task Class Monitor — per-task cycle time, jitter, and deadline violation tracking,System Designer — topology view of controllers, X2X modules, and powerlink devices,Logger module (mapp Logger) for structured event capture with severity classification,Online comparison between running controller and project — finds out-of-sync changes,mapp Audit — full audit trail of operator actions (GAMP 5 / 21 CFR Part 11 aligned)

Use the monitoring and diagnostic functions available in your Automation Studio version, and record the software, firmware, hardware, workload, and test procedure with every result.

B&R Industrial Automation Data Types Example for Pump Control

Illustrative Data Types example for Pump Control using B&R Industrial Automation terminology. Adapt the syntax to your Automation Studio release, compile it, and verify it in an isolated test environment before use on equipment.

// B&R Industrial Automation Automation Studio - Pump Control Control
// Data Types Implementation for Water & Wastewater
// B&R projects follow strict Hungarian-style naming with prefi

// ============================================
// Variable Declarations
// ============================================
VAR
    bEnable : BOOL := FALSE;
    bEmergencyStop : BOOL := FALSE;
    rPressuretransmitters : REAL;
    rCentrifugalpumps : REAL;
END_VAR

// ============================================
// Input Conditioning - Pressure transmitters for discharge and suction pressure
// ============================================
// Standard input processing
IF rPressuretransmitters > 0.0 THEN
    bEnable := TRUE;
END_IF;

// ============================================
// Safety Interlock - Dry run protection using flow or level monitoring
// ============================================
IF bEmergencyStop THEN
    rCentrifugalpumps := 0.0;
    bEnable := FALSE;
END_IF;

// ============================================
// Main Pump Control Control Logic
// ============================================
IF bEnable AND NOT bEmergencyStop THEN
    // Pump control systems use PLCs to regulate liquid flow in ind
    rCentrifugalpumps := rPressuretransmitters * 1.0; (* Illustrative scaling only *)

    // Process monitoring
    // Add specific control logic here
ELSE
    rCentrifugalpumps := 0.0;
END_IF;

Code Explanation:

  • 1.Data Types structure organized for a Pump Control training example
  • 2.Input conditioning handles Pressure transmitters for discharge and suction pressure signals
  • 3.Safety interlock ensures Dry run protection using flow or level monitoring always takes priority
  • 4.Main control implements Pump control systems use PLCs to regulat
  • 5.Adapt the scan-cycle assumptions to the selected X20 CPU series task configuration and verify them by measurement

Best Practices

  • Follow B&R Industrial Automation naming conventions: B&R projects follow strict Hungarian-style naming with prefixes (b for BOOL, n f
  • B&R Industrial Automation function design: B&R is famous for mapp Technology: a library of pre-engineered FBs covering moti
  • Data organization: B&R uses IEC 61131-3 global variable lists, PROGRAM VAR sections, and strongly-t
  • Data Types: Use smallest data type that accommodates the value range
  • Data Types: Use REAL for analog values that need decimal precision
  • Data Types: Create UDTs for frequently repeated data patterns
  • Pump Control: Use PID with derivative on PV for pressure control
  • Pump Control: Implement soft start ramps even with VFD (200-500ms)
  • Pump Control: Add flow proving before considering pump operational
  • Debug with Automation Studio: Use Automation Studio breakpoints in ST — available across all IEC lan
  • Safety: Dry run protection using flow or level monitoring
  • Use a compatible simulator or isolated test rig to test Pump Control logic before deployment

Common Pitfalls to Avoid

  • Data Types: Using INT for values that exceed 32767
  • Data Types: Losing precision when converting REAL to INT
  • Data Types: Array index out of bounds causing memory corruption
  • B&R Industrial Automation common error: Task class priority conflicts causing missed cycles in mid-priority application
  • Pump Control: Preventing cavitation at low suction pressure
  • Pump Control: Managing minimum flow requirements
  • Neglecting to validate Pressure transmitters for discharge and suction pressure leads to control errors
  • Insufficient comments make Data Types programs unmaintainable over time

Related Certifications

🏆B&R Certified Specialist
🏆B&R Certified Professional
🏆ABB University Automation Studio certifications

Applying Data Types to Pump Control using B&R Industrial Automation Automation Studio requires understanding the platform, the process, and the project's acceptance criteria. This guide has covered implementation structure, an illustrative code example, verification practices, and common pitfalls for a intermediate Pump Control exercise.

Use the practices outlined here to create a design that can be reviewed and tested. Define performance targets in the project requirements and confirm them with repeatable measurements.

Next Steps:

1. Check Sources: Read the current Automation Studio help, controller manual, release notes, and relevant standards
2. Practice Safely: Adapt the example in a simulator or isolated training setup
3. Review: Have the I/O map, state behavior, faults, and recovery steps reviewed
4. Test: Record normal, boundary, fault, restart, and communications test results

Data Types Foundation:

PLC data types define how values are stored, their valid ranges, and operations that can be performed. Proper type selection ensures accuracy and memo...

Project duration depends on scope, reviews, hardware availability, software and firmware versions, testing, commissioning, and site constraints. Remember: Use PID with derivative on PV for pressure control

For further learning, explore related topics including Data logging, Wastewater treatment, and B&R Industrial Automation platform-specific features for Pump Control optimization.