Learn PLCs free
Intermediate20 min readPackaging

Mitsubishi Ladder Logic for Bottle Filling

Learn Ladder Logic programming for Bottle Filling using Mitsubishi GX Works2/GX Works3. Includes code examples, best practices, and step-by-step implementation guide for Packaging applications.

💻
Platform
GX Works2/GX Works3
📊
Complexity
Intermediate to Advanced
⏱️
Project Duration
3-6 weeks

Implementing Ladder Logic for Bottle Filling using Mitsubishi GX Works2/GX Works3 requires a documented design, applicable standards, and project-specific acceptance criteria. This guide organizes practical checks for code structure, diagnostics, testing, and maintenance.

The example references FX5-family terminology, but model capabilities vary. Verify the controller manual, the installed GX Works2/GX Works3 version, and any applicable machinery, process, electrical, or functional-safety requirements for the actual project.

Best practices for Bottle Filling encompass multiple dimensions: proper handling of 5 sensor types, safe control of 5 different actuators, managing precise fill volume, and ensuring compliance with relevant industry standards. The Ladder Logic approach, when properly implemented, provides highly visual and intuitive and easy to troubleshoot, both critical for intermediate to advanced projects.

This guide presents a reviewable approach to Mitsubishi Ladder Logic programming for Bottle Filling, covering code organization, documentation, test procedures, and maintenance handoff. The sample logic is educational and must be compiled, simulated, peer-reviewed, and tested against the project's acceptance criteria before use on equipment.

Mitsubishi GX Works2/GX Works3 for Bottle Filling

GX Works2/GX Works3 is a programming environment associated with Mitsubishi controller families such as FX5, iQ-R, iQ-F. This guide uses Ladder Logic 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 Ladder Logic constructs

  • The project version matches the installed GX Works2/GX Works3 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:

  • FX5: Confirm CPU, I/O, memory, communications, and Ladder Logic support in the current selection guide

  • iQ-R: Confirm CPU, I/O, memory, communications, and Ladder Logic support in the current selection guide

  • iQ-F: Confirm CPU, I/O, memory, communications, and Ladder Logic support in the current selection guide

  • Q Series: Confirm CPU, I/O, memory, communications, and Ladder Logic 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 Mitsubishi 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 Ladder Logic for Bottle Filling

Ladder Logic (LAD) is a graphical programming language that represents control circuits as rungs on a ladder. It was designed to mimic the appearance of relay logic diagrams, making it intuitive for electricians and maintenance technicians familiar with hardwired control systems.

Execution Model:

Programs execute from left to right, top to bottom. Each rung is evaluated during the PLC scan cycle, with input conditions on the left determining whether output coils on the right are energized.

Core Advantages for Bottle Filling:

  • Highly visual and intuitive: Critical for Bottle Filling when handling intermediate to advanced control logic

  • Easy to troubleshoot: Critical for Bottle Filling when handling intermediate to advanced control logic

  • Industry standard: Critical for Bottle Filling when handling intermediate to advanced control logic

  • Minimal programming background required: Critical for Bottle Filling when handling intermediate to advanced control logic

  • Easy to read and understand: Critical for Bottle Filling when handling intermediate to advanced control logic


Why Ladder Logic 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 Ladder Logic:

Contacts:
- xic: Examine If Closed (XIC) - Normally Open contact that passes power when the associated bit is TRUE/1
- xio: Examine If Open (XIO) - Normally Closed contact that passes power when the associated bit is FALSE/0
- risingEdge: One-Shot Rising (OSR) - Passes power for one scan when input transitions from FALSE to TRUE

Coils:
- ote: Output Energize (OTE) - Standard output coil, energized when rung conditions are true
- otl: Output Latch (OTL) - Latching coil that remains ON until explicitly unlatched
- otu: Output Unlatch (OTU) - Unlatch coil that turns off a latched output

Branches:
- parallel: OR logic - Multiple paths allow current flow if ANY path is complete
- series: AND logic - All contacts in series must be closed for current flow
- nested: Complex logic combining parallel and series branches

Best Practices for Ladder Logic:

  • Keep rungs simple - split complex logic into multiple rungs for clarity

  • Use descriptive tag names that indicate function (e.g., Motor_Forward_CMD not M001)

  • Place most restrictive conditions first (leftmost) for faster evaluation

  • Group related rungs together with comment headers

  • Use XIO contacts for safety interlocks at the start of output rungs


Common Mistakes to Avoid:

  • Using the same OTE coil in multiple rungs (causes unpredictable behavior)

  • Forgetting to include stop conditions in seal-in circuits

  • Not using one-shots for counter inputs, causing multiple counts per event

  • Placing outputs before all conditions are evaluated


Typical Applications:

1. Start/stop motor control: Directly applicable to Bottle Filling
2. Conveyor systems: Related control patterns
3. Assembly lines: Related control patterns
4. Traffic lights: Related control patterns

Understanding these fundamentals prepares you to implement effective Ladder Logic solutions for Bottle Filling using Mitsubishi GX Works2/GX Works3.

Implementing Bottle Filling with Ladder Logic

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 Mitsubishi GX Works2/GX Works3 and Ladder Logic 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 GX Works2/GX Works3, characterize product flow properties (viscosity, foaming, temperature sensitivity).

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

In GX Works2/GX Works3, determine fill method based on accuracy requirements and product type.

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

In GX Works2/GX Works3, design container handling for smooth, jam-free operation.

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

In GX Works2/GX Works3, implement fill sequence with proper valve timing and deceleration.

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

In GX Works2/GX Works3, add bulk/dribble transition logic for gravimetric filling.

Step 6: Program calibration routines for automatic fill adjustment

In GX Works2/GX Works3, program calibration routines for automatic fill adjustment.


Mitsubishi Function Design:

Function block (FB) programming in Mitsubishi creates reusable logic modules with defined interfaces encapsulating complexity. FB definition includes input variables (VAR_INPUT), output variables (VAR_OUTPUT), internal variables (VAR), and retained variables (VAR_RETAIN) maintaining values between calls. Creating motor control FB: inputs include Start_Cmd (BOOL), Stop_Cmd (BOOL), Speed_SP (INT), outputs include Running_Sts (BOOL), Fault_Sts (BOOL), Actual_Speed (INT), internal variables store timers, state machine stages, and diagnostic counters. FB instantiation creates instance: Motor1 (Motor_FB) with unique variable storage, allowing multiple instances Motor1, Motor2, Motor3 controlling different motors using same logic. Array of FB instances: Motors : ARRAY[1..10] OF Motor_FB accessed as Motors[3].Running_Sts checking status of motor 3. Standard function (FUN) differs from FB by lacking internal memory, suitable for calculations or conversions: Temp_Conversion_FUN(Celsius) returns Fahrenheit without retaining historical data. Structured text programming within FBs/FUNs provides clearer logic for complex algorithms compared to ladder: IF-THEN-ELSIF-ELSE structures, FOR loops, CASE statements expressing intent more directly than ladder equivalents. EN/ENO functionality enables conditional execution: EN (enable input) controls whether FB executes, ENO (enable output) indicates successful execution detecting errors within block. Library management exports FBs to library files (.glib) shared across projects and engineering teams, versioned to track modifications and ensure consistency. The intelligent function module (IFM) templates provide pre-built FBs for common applications: PID control, analog scaling, motion positioning reducing development time and providing tested reliable code. Simulation mode tests FB logic without hardware, allowing desktop development and unit testing before commissioning. Protection functionality encrypts FB contents preventing unauthorized viewing or modification, useful for proprietary algorithms or OEM machine builders distributing programs to end users.

Common Challenges and Solutions:

1. Preventing dripping and stringing after fill cutoff

  • Solution: Ladder Logic addresses this through Highly visual and intuitive.


2. Handling foaming products that give false level readings

  • Solution: Ladder Logic addresses this through Easy to troubleshoot.


3. Maintaining accuracy at high speeds

  • Solution: Ladder Logic addresses this through Industry standard.


4. Synchronizing multi-head rotary fillers

  • Solution: Ladder Logic addresses this through Minimal programming background required.


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

Mitsubishi Diagnostic Tools:

Device memory monitor: Real-time table displaying current values for X, Y, M, D devices with force capability,Entry data monitor: Shows actual rung logic states with contact ON/OFF indication during program execution,Device test: Manually control outputs and set internal relays for wiring verification without program influence,Intelligent module diagnostics: Buffer memory display showing module status, error codes, and configuration,Scan time monitor: Displays current, maximum, and minimum scan times identifying performance issues,Error code history: Chronological log of system errors, module faults, and CPU events with timestamps,CC-Link/network diagnostics: Visual network status showing connected stations, errors, and communication statistics,SD card operation log: Records all SD card read/write operations, file transfers, and access timestamps,Remote diagnosis via Ethernet: Connect GX Works over network for monitoring and troubleshooting without local access,Sampling trace: Records device value changes over time with trigger conditions for intermittent fault analysis,System monitor: Displays CPU load, memory usage, and battery status for predictive maintenance,Safety diagnosis (safety CPU): Dedicated diagnostics for safety I/O discrepancy detection and emergency stop chain status

Use the monitoring and diagnostic functions available in your GX Works2/GX Works3 version, and record the software, firmware, hardware, workload, and test procedure with every result.

Mitsubishi Ladder Logic Example for Bottle Filling

Illustrative Ladder Logic example for Bottle Filling using Mitsubishi terminology. Adapt the syntax to your GX Works2/GX Works3 release, compile it, and verify it in an isolated test environment before use on equipment.

// Mitsubishi GX Works2/GX Works3 - Bottle Filling Control
// Ladder Logic Implementation
// Naming: Mitsubishi programming supports both traditional device addr...

NETWORK 1: Input Conditioning - Bottle presence sensors (fiber optic or inductive) for container detection
    |----[ Level_sensors ]----[TON Timer_Debounce]----( Enable )
    |
    | Timer: On-Delay, PT: 500ms (debounce for Packaging environment)

NETWORK 2: Safety Interlock Chain - Emergency stop priority
    |----[ Enable ]----[ NOT E_Stop ]----[ Guards_OK ]----+----( Safe_To_Run )
    |                                                                          |
    |----[ Fault_Active ]------------------------------------------+----( Alarm_Horn )

NETWORK 3: Main Bottle Filling Control
    |----[ Safe_To_Run ]----[ Flow_meters ]----+----( Servo_motors )
    |                                                           |
    |----[ Manual_Override ]----------------------------+

NETWORK 4: Sequence Control - State machine
    |----[ Motor_Run ]----[CTU Cycle_Counter]----( Batch_Complete )
    |
    | Counter: PV := 50 (illustrative batch size; replace with a reviewed requirement)

NETWORK 5: Output Control with Feedback
    |----[ Servo_motors ]----[TON Feedback_Timer]----[ NOT Motor_Feedback ]----( Output_Fault )

Code Explanation:

  • 1.Network 1: Input conditioning with Mitsubishi-specific TON timer for debouncing in Packaging environments
  • 2.Network 2: Safety interlock chain ensuring Guarding around rotating components compliance
  • 3.Network 3: Main Bottle Filling control with manual override capability for maintenance
  • 4.Network 4: Production counting using Mitsubishi CTU counter for batch tracking
  • 5.Network 5: Output verification monitors actuator feedback - critical for intermediate to advanced applications
  • 6.Online monitoring: Online connection in GX Works provides multiple monitoring modes observing PLC o

Best Practices

  • Follow Mitsubishi naming conventions: Mitsubishi programming supports both traditional device addressing (M0, D100, X1
  • Mitsubishi function design: Function block (FB) programming in Mitsubishi creates reusable logic modules wit
  • Data organization: Mitsubishi uses file registers (R devices) and structured data in function block
  • Ladder Logic: Keep rungs simple - split complex logic into multiple rungs for clarity
  • Ladder Logic: Use descriptive tag names that indicate function (e.g., Motor_Forward_CMD not M001)
  • Ladder Logic: Place most restrictive conditions first (leftmost) for faster evaluation
  • 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 GX Works2/GX Works3: Use sampling trace to capture high-speed events occurring faster than
  • Safety: Guarding around rotating components
  • Use a compatible simulator or isolated test rig to test Bottle Filling logic before deployment

Common Pitfalls to Avoid

  • Ladder Logic: Using the same OTE coil in multiple rungs (causes unpredictable behavior)
  • Ladder Logic: Forgetting to include stop conditions in seal-in circuits
  • Ladder Logic: Not using one-shots for counter inputs, causing multiple counts per event
  • Mitsubishi common error: Error 2110: Illegal device specified - accessing device outside configured range
  • 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 Ladder Logic programs unmaintainable over time

Related Certifications

🏆Mitsubishi PLC Programming Certification

Applying Ladder Logic to Bottle Filling using Mitsubishi GX Works2/GX Works3 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 GX Works2/GX Works3 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

Ladder Logic Foundation:

Ladder Logic (LAD) is a graphical programming language that represents control circuits as rungs on a ladder. It was designed to mimic the appearance ...

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 Conveyor systems, Pharmaceutical liquid filling, and Mitsubishi platform-specific features for Bottle Filling optimization.