PLC Programming.io
Learn PLCs free
Intermediate25 min readPackaging

Honeywell Structured Text for Bottle Filling

Learn Structured Text programming for Bottle Filling using Honeywell ControlEdge Builder / Experion PKS / SoftMaster. Includes code examples, best practices, and step-by-step implementation guide for Packaging applications.

💻
Platform
ControlEdge Builder / Experion PKS / SoftMaster
📊
Complexity
Intermediate to Advanced
⏱️
Project Duration
3-6 weeks

Learning to implement Structured Text for Bottle Filling using Honeywell's ControlEdge Builder / Experion PKS / SoftMaster is a useful skill for PLC programmers working in Packaging. This guide walks through the fundamentals with clear explanations and an illustrative example that you can adapt to a simulator or test bench.

The example uses Honeywell terminology and references controller families such as ControlEdge PLC and ControlEdge HC900. Confirm the exact instructions, data types, firmware requirements, and licensing in the current vendor documentation before choosing hardware or deploying a project.

The Structured Text approach is particularly well-suited for Bottle Filling because complex calculations, data manipulation, advanced control algorithms, and when code reusability is important. This combination allows you to leverage powerful for complex logic while managing the typical challenges of Bottle Filling, including precise fill volume and high-speed operation.

Throughout this guide, you'll find step-by-step implementation guidance, an illustrative code example, and a verification checklist specific to Packaging. Whether you're programming your first Bottle Filling exercise or transitioning from another PLC platform, use the material as a starting point and validate it in your exact ControlEdge Builder / Experion PKS / SoftMaster version and controller environment.

Honeywell ControlEdge Builder / Experion PKS / SoftMaster for Bottle Filling

ControlEdge Builder / Experion PKS / SoftMaster is a programming environment associated with Honeywell controller families such as ControlEdge PLC, ControlEdge HC900, ControlEdge UOC. This guide uses Structured Text 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 Structured Text constructs

  • The project version matches the installed ControlEdge Builder / Experion PKS / SoftMaster 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 Bottle Filling exercise, map the required inputs and outputs before writing logic. The example considers 5 sensor types, including Level sensors, Flow meters, Pressure sensors, and 5 actuator types.

Control Equipment for Bottle Filling:

  • Filling nozzles (gravity, pressure, vacuum)

  • Product tanks with level control

  • CIP (clean-in-place) systems

  • Cap feeding and sorting equipment


Controller-family references used in this guide include:

  • ControlEdge PLC: Confirm CPU, I/O, memory, communications, and Structured Text support in the current selection guide

  • ControlEdge HC900: Confirm CPU, I/O, memory, communications, and Structured Text support in the current selection guide

  • ControlEdge UOC: Confirm CPU, I/O, memory, communications, and Structured Text support in the current selection guide

  • Experion C300: Confirm CPU, I/O, memory, communications, and Structured Text 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 Honeywell 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 Bottle Filling 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 Structured Text for Bottle Filling

Structured Text (ST) is a high-level, text-based programming language defined in IEC 61131-3. It resembles Pascal and provides powerful constructs for complex algorithms, calculations, and data manipulation.

Execution Model:

Code executes sequentially from top to bottom within each program unit. Variables maintain state between scan cycles unless explicitly reset.

Core Advantages for Bottle Filling:

  • Powerful for complex logic: Critical for Bottle Filling when handling intermediate to advanced control logic

  • Excellent code reusability: Critical for Bottle Filling when handling intermediate to advanced control logic

  • Compact code representation: Critical for Bottle Filling when handling intermediate to advanced control logic

  • Good for algorithms and calculations: Critical for Bottle Filling when handling intermediate to advanced control logic

  • Familiar to software developers: Critical for Bottle Filling when handling intermediate to advanced control logic


Why Structured Text Fits Bottle Filling:

Bottle Filling systems in Packaging typically involve:

  • Sensors: Bottle presence sensors (fiber optic or inductive) for container detection, Level sensors (capacitive, ultrasonic, or optical) for fill detection, Load cells for gravimetric (weight-based) filling

  • Actuators: Servo-driven filling valves for precise flow control, Pneumatic pinch valves for on/off flow control, Bottle handling star wheels and timing screws

  • Complexity: Intermediate to Advanced with challenges including Preventing dripping and stringing after fill cutoff


Programming Fundamentals in Structured Text:

Variables:
- declaration: VAR / VAR_INPUT / VAR_OUTPUT / VAR_IN_OUT / VAR_GLOBAL sections
- initialization: Variables can be initialized at declaration: Counter : INT := 0;
- constants: VAR CONSTANT section for read-only values

Operators:
- arithmetic: + - * / MOD (modulo)
- comparison: = <> < > <= >=
- logical: AND OR XOR NOT

ControlStructures:
- if: IF condition THEN statements; ELSIF condition THEN statements; ELSE statements; END_IF;
- case: CASE selector OF value1: statements; value2: statements; ELSE statements; END_CASE;
- for: FOR index := start TO end BY step DO statements; END_FOR;

Best Practices for Structured Text:

  • Use meaningful variable names with consistent naming conventions

  • Initialize all variables at declaration to prevent undefined behavior

  • Use enumerated types for state machines instead of magic numbers

  • Break complex expressions into intermediate variables for readability

  • Use functions for reusable calculations and function blocks for stateful operations


Common Mistakes to Avoid:

  • Using = instead of := for assignment (= is comparison)

  • Forgetting semicolons at end of statements

  • Integer division truncation - use REAL for decimal results

  • Infinite loops from incorrect WHILE/REPEAT conditions


Typical Applications:

1. PID control: Directly applicable to Bottle Filling
2. Recipe management: Related control patterns
3. Statistical calculations: Related control patterns
4. Data logging: Related control patterns

Understanding these fundamentals prepares you to implement effective Structured Text solutions for Bottle Filling using Honeywell ControlEdge Builder / Experion PKS / SoftMaster.

Implementing Bottle Filling with Structured Text

Bottle filling control systems manage the precise dispensing of liquids into containers at high speeds while maintaining accuracy and preventing spillage. PLCs coordinate container handling, fill control, capping, and quality inspection in an integrated packaging line.

This walkthrough demonstrates practical implementation using Honeywell ControlEdge Builder / Experion PKS / SoftMaster and Structured Text programming.

System Requirements:

A typical Bottle Filling implementation includes:

Input Devices (Sensors):
1. Bottle presence sensors (fiber optic or inductive) for container detection: Critical for monitoring system state
2. Level sensors (capacitive, ultrasonic, or optical) for fill detection: Critical for monitoring system state
3. Load cells for gravimetric (weight-based) filling: Critical for monitoring system state
4. Flow meters (magnetic or mass flow) for volumetric filling: Critical for monitoring system state
5. Encoder feedback for rotary filler position: Critical for monitoring system state

Output Devices (Actuators):
1. Servo-driven filling valves for precise flow control: Primary control output
2. Pneumatic pinch valves for on/off flow control: Supporting control function
3. Bottle handling star wheels and timing screws: Supporting control function
4. Capping chuck drives (servo or pneumatic): Supporting control function
5. Torque limiters for cap tightening: Supporting control function

Control Equipment:

  • Filling nozzles (gravity, pressure, vacuum)

  • Product tanks with level control

  • CIP (clean-in-place) systems

  • Cap feeding and sorting equipment


Control Strategies for Bottle Filling:

1. Primary Control: Automated bottle filling and capping systems using PLCs for precise volume control, speed optimization, and quality assurance.
2. Safety Interlocks: Preventing Precise fill volume
3. Error Recovery: Handling High-speed operation

Implementation Steps:

Step 1: Characterize product flow properties (viscosity, foaming, temperature sensitivity)

In ControlEdge Builder / Experion PKS / SoftMaster, characterize product flow properties (viscosity, foaming, temperature sensitivity).

Step 2: Determine fill method based on accuracy requirements and product type

In ControlEdge Builder / Experion PKS / SoftMaster, determine fill method based on accuracy requirements and product type.

Step 3: Design container handling for smooth, jam-free operation

In ControlEdge Builder / Experion PKS / SoftMaster, design container handling for smooth, jam-free operation.

Step 4: Implement fill sequence with proper valve timing and deceleration

In ControlEdge Builder / Experion PKS / SoftMaster, implement fill sequence with proper valve timing and deceleration.

Step 5: Add bulk/dribble transition logic for gravimetric filling

In ControlEdge Builder / Experion PKS / SoftMaster, add bulk/dribble transition logic for gravimetric filling.

Step 6: Program calibration routines for automatic fill adjustment

In ControlEdge Builder / Experion PKS / SoftMaster, program calibration routines for automatic fill adjustment.


Honeywell Function Design:

FB libraries are central — Honeywell ships standard control-module libraries plus EPC partners maintain extensive private libraries. Library reuse is enforced by project standards rather than treated as optional.

Common Challenges and Solutions:

1. Preventing dripping and stringing after fill cutoff

  • Solution: Structured Text addresses this through Powerful for complex logic.


2. Handling foaming products that give false level readings

  • Solution: Structured Text addresses this through Excellent code reusability.


3. Maintaining accuracy at high speeds

  • Solution: Structured Text addresses this through Compact code representation.


4. Synchronizing multi-head rotary fillers

  • Solution: Structured Text addresses this through Good for algorithms and calculations.


Safety Considerations:

  • Guarding around rotating components

  • Interlocked access doors with safe stop

  • Bottle breakage detection and containment

  • Overpressure protection for pressure filling

  • Chemical handling safety for cleaning solutions


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

Honeywell Diagnostic Tools:

ControlEdge Builder online mode with breakpoints,Experion System Status diagnostics,Honeywell Forge cyber-event correlation,Trace tool with multi-channel capture,Profibus / Profinet topology diagnostics,OPC UA server diagnostics page,HART pass-through instrument diagnostics,Built-in event log with audit-trail export,TÜV functional-safety audit-trail tooling,Honeywell global service desk support

Use the monitoring and diagnostic functions available in your ControlEdge Builder / Experion PKS / SoftMaster version, and record the software, firmware, hardware, workload, and test procedure with every result.

Honeywell Structured Text Example for Bottle Filling

Illustrative Structured Text example for Bottle Filling using Honeywell terminology. Adapt the syntax to your ControlEdge Builder / Experion PKS / SoftMaster release, compile it, and verify it in an isolated test environment before use on equipment.

(* Honeywell ControlEdge Builder / Experion PKS / SoftMaster - Bottle Filling Control *)
(* Structured Text Implementation for Packaging *)
(* Project naming standards inherit from Experion plant tag-numbering — i *)

PROGRAM PRG_BOTTLE_FILLING_Control

VAR
    (* State Machine Variables *)
    eState : E_BOTTLE_FILLING_States := IDLE;
    bEnable : BOOL := FALSE;
    bFaultActive : BOOL := FALSE;

    (* Timers *)
    tonDebounce : TON;
    tonProcessTimeout : TON;
    tonFeedbackCheck : TON;

    (* Counters *)
    ctuCycleCounter : CTU;

    (* Process Variables *)
    rLevelsensors : REAL := 0.0;
    rServomotors : REAL := 0.0;
    rSetpoint : REAL := 100.0; (* Illustrative value; replace with a reviewed requirement *)
END_VAR

VAR CONSTANT
    (* Packaging Process Parameters *)
    C_DEBOUNCE_TIME : TIME := T#500MS;
    C_PROCESS_TIMEOUT : TIME := T#30S; (* Illustrative value; verify for the process *)
    C_BATCH_SIZE : INT := 50; (* Illustrative value; replace with a reviewed requirement *)
END_VAR

(* Input Conditioning *)
tonDebounce(IN := bStartButton, PT := C_DEBOUNCE_TIME);
bEnable := tonDebounce.Q AND NOT bEmergencyStop AND bSafetyOK;

(* Main State Machine - Pattern: Sequence step logic encapsulated in dedi *)
CASE eState OF
    IDLE:
        rServomotors := 0.0;
        ctuCycleCounter(RESET := TRUE);
        IF bEnable AND rLevelsensors > 0.0 THEN
            eState := STARTING;
        END_IF;

    STARTING:
        (* Ramp up output - Gradual start *)
        rServomotors := MIN(rServomotors + 5.0, rSetpoint);
        IF rServomotors >= rSetpoint THEN
            eState := RUNNING;
        END_IF;

    RUNNING:
        (* Bottle Filling active - Bottle filling control systems manage the precise  *)
        tonProcessTimeout(IN := TRUE, PT := C_PROCESS_TIMEOUT);
        ctuCycleCounter(CU := bCyclePulse, PV := C_BATCH_SIZE);

        IF ctuCycleCounter.Q THEN
            eState := COMPLETE;
        ELSIF tonProcessTimeout.Q THEN
            bFaultActive := TRUE;
            eState := FAULT;
        END_IF;

    COMPLETE:
        rServomotors := 0.0;
        (* Log production data - Logging happens at the historian tier — Honeywell Uniformance PHD or third-party PI / Wonderware historians — with ControlEdge streaming process data via OPC UA. *)
        eState := IDLE;

    FAULT:
        rServomotors := 0.0;
        (* Alarms are configured at Experion tier with severity, suppression, audit logging, and operator-action recording. PLC-tier alarm logic feeds Experion via OPC UA / proprietary buses. *)
        IF bFaultReset AND NOT bEmergencyStop THEN
            bFaultActive := FALSE;
            eState := IDLE;
        END_IF;
END_CASE;

(* Safety Override - Always executes *)
IF bEmergencyStop OR NOT bSafetyOK THEN
    rServomotors := 0.0;
    eState := FAULT;
    bFaultActive := TRUE;
END_IF;

END_PROGRAM

Code Explanation:

  • 1.Enumerated state machine (Sequence step logic encapsulated in dedicated SFC POUs or CASE-of-state structured-text patterns, with each step calling control-module FBs for actuator commands and waiting on instrument-tag conditions.) for clear Bottle Filling sequence control
  • 2.Constants use clearly marked illustrative values that must be replaced with reviewed project requirements
  • 3.Input conditioning with debounce timer prevents false triggers in industrial environment
  • 4.STARTING state implements soft-start ramp - prevents mechanical shock
  • 5.Process timeout detection flags a possible stuck condition for investigation
  • 6.The final override illustrates a software permissive only; it is not a safety-rated function and must not replace a validated safety system

Best Practices

  • ✓Follow Honeywell naming conventions: Project naming standards inherit from Experion plant tag-numbering — instrument-
  • ✓Honeywell function design: FB libraries are central — Honeywell ships standard control-module libraries plu
  • ✓Data organization: Structured types for instrument data, control-module instances, alarm records, a
  • ✓Structured Text: Use meaningful variable names with consistent naming conventions
  • ✓Structured Text: Initialize all variables at declaration to prevent undefined behavior
  • ✓Structured Text: Use enumerated types for state machines instead of magic numbers
  • ✓Bottle Filling: Use minimum 10 readings for statistical fill tracking
  • ✓Bottle Filling: Implement automatic re-zero of scales at regular intervals
  • ✓Bottle Filling: Provide separate parameters for each product recipe
  • ✓Debug with ControlEdge Builder / Experion PKS / SoftMaster: Run project comparison against the last validated baseline before depl
  • ✓Safety: Guarding around rotating components
  • ✓Use a compatible simulator or isolated test rig to test Bottle Filling logic before deployment

Common Pitfalls to Avoid

  • ⚠Structured Text: Using = instead of := for assignment (= is comparison)
  • ⚠Structured Text: Forgetting semicolons at end of statements
  • ⚠Structured Text: Integer division truncation - use REAL for decimal results
  • ⚠Honeywell common error: Encrypted project-file key mismatches after CPU swap without key transfer
  • ⚠Bottle Filling: Preventing dripping and stringing after fill cutoff
  • ⚠Bottle Filling: Handling foaming products that give false level readings
  • ⚠Neglecting to validate Bottle presence sensors (fiber optic or inductive) for container detection leads to control errors
  • ⚠Insufficient comments make Structured Text programs unmaintainable over time

Related Certifications

🏆Honeywell Certified Experion Engineer
🏆ControlEdge PLC training certificates
🏆TÜV Functional Safety Engineer (Honeywell-specific)
🏆Honeywell Forge cybersecurity training
🏆Advanced Honeywell Programming Certification

Applying Structured Text to Bottle Filling using Honeywell ControlEdge Builder / Experion PKS / SoftMaster 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 to advanced Bottle Filling 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 ControlEdge Builder / Experion PKS / SoftMaster 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

Structured Text Foundation:

Structured Text (ST) is a high-level, text-based programming language defined in IEC 61131-3. It resembles Pascal and provides powerful constructs for...

Project duration depends on scope, reviews, hardware availability, software and firmware versions, testing, commissioning, and site constraints. Remember: Use minimum 10 readings for statistical fill tracking

For further learning, explore related topics including Recipe management, Pharmaceutical liquid filling, and Honeywell platform-specific features for Bottle Filling optimization.