Learning to implement Function Blocks for Motor Control using Wecon's Wecon PLC Editor / PIStudio is an essential skill for PLC programmers working in Industrial Manufacturing. This comprehensive guide walks you through the fundamentals, providing clear explanations and practical examples that you can apply immediately to real-world projects.
Wecon has established itself as Moderate in OEM machinery, packaging, textiles, plastics, and small-scale process equipment, making it a strategic choice for Motor Control applications. With <1% global global market share and 7 popular PLC families including the LX3V and LX5V, Wecon provides the robust platform needed for beginner to intermediate complexity projects like Motor Control.
The Function Blocks approach is particularly well-suited for Motor Control because process control, continuous operations, modular programming, and signal flow visualization. This combination allows you to leverage visual representation of signal flow while managing the typical challenges of Motor Control, including soft start implementation and overload protection.
Throughout this guide, you'll discover step-by-step implementation strategies, working code examples tested on Wecon PLC Editor / PIStudio, and industry best practices specific to Industrial Manufacturing. Whether you're programming your first Motor Control system or transitioning from another PLC platform, this guide provides the practical knowledge you need to succeed with Wecon Function Blocks programming.
Wecon Wecon PLC Editor / PIStudio for Motor Control
Wecon PLC Editor is a free Windows-based IDE for the LX series (LX3V, LX5V, LX5S, LX6S, LX7) that mirrors Mitsubishi FX programming conventions almost completely — instruction names, soft-element addressing, and project-file structure are deliberately FX-compatible to ease migration of OEM machine-builders away from FX hardware. PIStudio is the companion HMI tool for Wecon's PI panel range. Both tools are free of license cost, which combined with Mitsubishi-style familiarity has driven Wecon ado...
Platform Strengths for Motor Control:
- Mitsubishi FX-instruction-compatible — direct migration path
- Free PLC Editor and PIStudio HMI software
- Combined PLC + HMI bundles at sharp price points
- Built-in motion, pulse, and PID on compact units
Unique ${brand.software} Features:
- Free PLC Editor + PIStudio HMI software
- Mitsubishi-FX-compatible instruction set and soft-element model
- Combined PLC + HMI bundles available at single SKU
- Built-in motion / pulse / PID on compact CPUs
Key Capabilities:
The Wecon PLC Editor / PIStudio environment excels at Motor Control applications through its mitsubishi fx-instruction-compatible — direct migration path. This is particularly valuable when working with the 5 sensor types typically found in Motor Control systems, including Current sensors, Vibration sensors, Temperature sensors.
Control Equipment for Motor Control:
- Motor control centers (MCCs)
- AC induction motors (NEMA/IEC frame)
- Synchronous motors for high efficiency
- DC motors for precise speed control
Wecon's controller families for Motor Control include:
- LX3V: Suitable for beginner to intermediate Motor Control applications
- LX5V: Suitable for beginner to intermediate Motor Control applications
- LX5S: Suitable for beginner to intermediate Motor Control applications
- LX6S: Suitable for beginner to intermediate Motor Control applications
Hardware Selection Guidance:
Wecon CPU selection runs from LX3V (entry, FX1N-class), LX5V / LX5S (mid-tier, FX3U-class with extended motion and Ethernet on -E variants), LX6S (extended I/O and faster scan), and LX7 (high-end with EtherCAT and advanced motion). Choice usually mirrors what an FX equivalent would have been — LX3V for compact textile / packaging machinery, LX5V for mid-tier OEM equipment, LX7 for multi-axis appli...
Industry Recognition:
Moderate in OEM machinery, packaging, textiles, plastics, and small-scale process equipment. Rare in Tier 1 automotive — Wecon is not typically on multinational OEM specs. Seen in Chinese aftermarket fixturing, dunnage racks, conveyor sub-systems, and Tier 3 component-manufacturer support equipment....
Investment Considerations:
With $ pricing, Wecon positions itself in the value segment. For Motor Control projects requiring beginner skill levels and 1-3 weeks development time, the total investment includes hardware, software licensing, training, and ongoing support.
Understanding Function Blocks for Motor Control
Function Block Diagram (FBD) is a graphical programming language where functions and function blocks are represented as boxes connected by signal lines. Data flows from left to right through the network.
Execution Model:
Blocks execute based on data dependencies - a block executes only when all its inputs are available. Networks execute top to bottom when dependencies allow.
Core Advantages for Motor Control:
- Visual representation of signal flow: Critical for Motor Control when handling beginner to intermediate control logic
- Good for modular programming: Critical for Motor Control when handling beginner to intermediate control logic
- Reusable components: Critical for Motor Control when handling beginner to intermediate control logic
- Excellent for process control: Critical for Motor Control when handling beginner to intermediate control logic
- Good for continuous operations: Critical for Motor Control when handling beginner to intermediate control logic
Why Function Blocks Fits Motor Control:
Motor Control systems in Industrial Manufacturing typically involve:
- Sensors: Current transformers for motor current monitoring, RTD or thermocouple for motor winding temperature, Vibration sensors for bearing monitoring
- Actuators: Contactors for direct-on-line starting, Soft starters for reduced voltage starting, Variable frequency drives for speed control
- Complexity: Beginner to Intermediate with challenges including Managing starting current within supply limits
Programming Fundamentals in Function Blocks:
StandardBlocks:
- logic: AND, OR, XOR, NOT - Boolean logic operations
- comparison: EQ, NE, LT, GT, LE, GE - Compare values
- math: ADD, SUB, MUL, DIV, MOD - Arithmetic operations
TimersCounters:
- ton: Timer On-Delay - Output turns ON after preset time
- tof: Timer Off-Delay - Output turns OFF after preset time
- tp: Pulse Timer - Output pulses for preset time
Connections:
- wires: Connect output pins to input pins to pass data
- branches: One output can connect to multiple inputs
- feedback: Outputs can feed back to inputs for state machines
Best Practices for Function Blocks:
- Arrange blocks for clear left-to-right data flow
- Use consistent spacing and alignment for readability
- Label all inputs and outputs with meaningful names
- Create custom FBs for frequently repeated logic patterns
- Minimize wire crossings by careful block placement
Common Mistakes to Avoid:
- Creating feedback loops without proper initialization
- Connecting incompatible data types
- Not considering execution order dependencies
- Overcrowding networks making them hard to read
Typical Applications:
1. HVAC control: Directly applicable to Motor Control
2. Temperature control: Related control patterns
3. Flow control: Related control patterns
4. Batch processing: Related control patterns
Understanding these fundamentals prepares you to implement effective Function Blocks solutions for Motor Control using Wecon Wecon PLC Editor / PIStudio.
Implementing Motor Control with Function Blocks
Motor control systems use PLCs to start, stop, and regulate electric motors in industrial applications. These systems provide protection, speed control, and coordination for motors ranging from fractional horsepower to thousands of horsepower.
This walkthrough demonstrates practical implementation using Wecon Wecon PLC Editor / PIStudio and Function Blocks programming.
System Requirements:
A typical Motor Control implementation includes:
Input Devices (Sensors):
1. Current transformers for motor current monitoring: Critical for monitoring system state
2. RTD or thermocouple for motor winding temperature: Critical for monitoring system state
3. Vibration sensors for bearing monitoring: Critical for monitoring system state
4. Speed encoders or tachometers: Critical for monitoring system state
5. Torque sensors for load monitoring: Critical for monitoring system state
Output Devices (Actuators):
1. Contactors for direct-on-line starting: Primary control output
2. Soft starters for reduced voltage starting: Supporting control function
3. Variable frequency drives for speed control: Supporting control function
4. Brakes (mechanical or dynamic): Supporting control function
5. Starters (star-delta, autotransformer): Supporting control function
Control Equipment:
- Motor control centers (MCCs)
- AC induction motors (NEMA/IEC frame)
- Synchronous motors for high efficiency
- DC motors for precise speed control
Control Strategies for Motor Control:
1. Primary Control: Industrial motor control using PLCs for start/stop, speed control, and protection of electric motors.
2. Safety Interlocks: Preventing Soft start implementation
3. Error Recovery: Handling Overload protection
Implementation Steps:
Step 1: Calculate motor starting current and verify supply capacity
In Wecon PLC Editor / PIStudio, calculate motor starting current and verify supply capacity.
Step 2: Select starting method based on motor size and load requirements
In Wecon PLC Editor / PIStudio, select starting method based on motor size and load requirements.
Step 3: Configure motor protection with correct thermal curve
In Wecon PLC Editor / PIStudio, configure motor protection with correct thermal curve.
Step 4: Implement control logic for start/stop with proper interlocks
In Wecon PLC Editor / PIStudio, implement control logic for start/stop with proper interlocks.
Step 5: Add speed control loop if VFD is used
In Wecon PLC Editor / PIStudio, add speed control loop if vfd is used.
Step 6: Configure acceleration and deceleration ramps
In Wecon PLC Editor / PIStudio, configure acceleration and deceleration ramps.
Wecon Function Design:
Reusable logic is most often P-label subroutines. Parameterised function blocks are available on newer CPUs but adoption is uneven; copy-paste reuse remains the dominant pattern in the field.
Common Challenges and Solutions:
1. Managing starting current within supply limits
- Solution: Function Blocks addresses this through Visual representation of signal flow.
2. Coordinating acceleration with driven load requirements
- Solution: Function Blocks addresses this through Good for modular programming.
3. Protecting motors from frequent starting (thermal cycling)
- Solution: Function Blocks addresses this through Reusable components.
4. Handling regenerative energy during deceleration
- Solution: Function Blocks addresses this through Excellent for process control.
Safety Considerations:
- Proper machine guarding for rotating equipment
- Emergency stop functionality with safe torque off
- Lockout/tagout provisions for maintenance
- Arc flash protection and PPE requirements
- Proper grounding and bonding
Performance Metrics:
- Scan Time: Optimize for 5 inputs and 5 outputs
- Memory Usage: Efficient data structures for LX3V capabilities
- Response Time: Meeting Industrial Manufacturing requirements for Motor Control
Wecon Diagnostic Tools:
PLC Editor online monitoring with rung-state highlighting,Soft-element watch table,Built-in offline simulator,M8000-range system flags for hardware diagnostics,PIStudio communication analyzer for HMI-side issues,Modbus RTU / TCP test utilities (third-party),Distributor loaner CPUs and test rigs,Wecon community forum threads for protocol-specific issues
Wecon's Wecon PLC Editor / PIStudio provides tools for performance monitoring and optimization, essential for achieving the 1-3 weeks development timeline while maintaining code quality.
Wecon Function Blocks Example for Motor Control
Complete working example demonstrating Function Blocks implementation for Motor Control using Wecon Wecon PLC Editor / PIStudio. Follows Wecon naming conventions. Tested on LX3V hardware.
(* Wecon Wecon PLC Editor / PIStudio - Motor Control Control *)
(* Reusable Function Blocks Implementation *)
(* Reusable logic is most often P-label subroutines. Parameteri *)
FUNCTION_BLOCK FB_MOTOR_CONTROL_Controller
VAR_INPUT
bEnable : BOOL; (* Enable control *)
bReset : BOOL; (* Fault reset *)
rProcessValue : REAL; (* Current transformers for motor current monitoring *)
rSetpoint : REAL := 100.0; (* Target value *)
bEmergencyStop : BOOL; (* Safety input *)
END_VAR
VAR_OUTPUT
rControlOutput : REAL; (* Contactors for direct-on-line starting *)
bRunning : BOOL; (* Process active *)
bComplete : BOOL; (* Cycle complete *)
bFault : BOOL; (* Fault status *)
nFaultCode : INT; (* Diagnostic code *)
END_VAR
VAR
(* Internal Function Blocks *)
fbSafety : FB_SafetyMonitor; (* Safety logic *)
fbRamp : FB_RampGenerator; (* Soft start/stop *)
fbPID : FB_PIDController; (* Process control *)
fbDiag : FB_Diagnostics; (* Alarms are M-flag banks latched on fault detection. Active-alarm rollup is ORed into a single HMI alarm-banner tag. Historical alarm logging is offloaded to PIStudio's built-in alarm-history feature, which writes to internal flash or external SD card depending on HMI model. *)
(* Internal State *)
eInternalState : E_ControlState;
tonWatchdog : TON;
END_VAR
(* Safety Monitor - Proper machine guarding for rotating equipment *)
fbSafety(
Enable := bEnable,
EmergencyStop := bEmergencyStop,
ProcessValue := rProcessValue,
HighLimit := rSetpoint * 1.2,
LowLimit := rSetpoint * 0.1
);
(* Main Control Logic *)
IF fbSafety.SafeToRun THEN
(* Ramp Generator - Prevents startup surge *)
fbRamp(
Enable := bEnable,
TargetValue := rSetpoint,
RampRate := 20.0, (* Industrial Manufacturing rate *)
CurrentValue => rSetpoint
);
(* PID Controller - Process regulation *)
fbPID(
Enable := fbRamp.InPosition,
ProcessValue := rProcessValue,
Setpoint := fbRamp.CurrentValue,
Kp := 1.0,
Ki := 0.1,
Kd := 0.05,
OutputMin := 0.0,
OutputMax := 100.0
);
rControlOutput := fbPID.Output;
bRunning := TRUE;
bFault := FALSE;
nFaultCode := 0;
ELSE
(* Safe State - Emergency stop functionality with safe torque off *)
rControlOutput := 0.0;
bRunning := FALSE;
bFault := NOT bEnable; (* Only fault if not intentional stop *)
nFaultCode := fbSafety.FaultCode;
END_IF;
(* Diagnostics - Logging is HMI-tier rather than PLC-tier. PIStudio's data-logger feature writes CSV files to SD card or USB at configurable intervals, polled from D-register sample tags. Cloud upload is supported on newer PI panels via MQTT to brand-agnostic brokers. *)
fbDiag(
ProcessRunning := bRunning,
FaultActive := bFault,
ProcessValue := rProcessValue,
ControlOutput := rControlOutput
);
(* Watchdog - Detects frozen control *)
tonWatchdog(IN := bRunning AND NOT fbPID.OutputChanging, PT := T#10S);
IF tonWatchdog.Q THEN
bFault := TRUE;
nFaultCode := 99; (* Watchdog fault *)
END_IF;
(* Reset Logic *)
IF bReset AND NOT bEmergencyStop THEN
bFault := FALSE;
nFaultCode := 0;
fbDiag.ClearAlarms();
END_IF;
END_FUNCTION_BLOCKCode Explanation:
- 1.Encapsulated function block follows Reusable logic is most often P-label sub - reusable across Industrial Manufacturing projects
- 2.FB_SafetyMonitor provides Proper machine guarding for rotating equipment including high/low limits
- 3.FB_RampGenerator prevents startup issues common in Motor Control systems
- 4.FB_PIDController tuned for Industrial Manufacturing: Kp=1.0, Ki=0.1
- 5.Watchdog timer detects frozen control - critical for beginner to intermediate Motor Control reliability
- 6.Diagnostic function block enables Logging is HMI-tier rather than PLC-tier. PIStudio's data-logger feature writes CSV files to SD card or USB at configurable intervals, polled from D-register sample tags. Cloud upload is supported on newer PI panels via MQTT to brand-agnostic brokers. and Alarms are M-flag banks latched on fault detection. Active-alarm rollup is ORed into a single HMI alarm-banner tag. Historical alarm logging is offloaded to PIStudio's built-in alarm-history feature, which writes to internal flash or external SD card depending on HMI model.
Best Practices
- ✓Follow Wecon naming conventions: Engineers code Wecon in FX-style raw-address conventions — X0, Y0, M100, D100, T
- ✓Wecon function design: Reusable logic is most often P-label subroutines. Parameterised function blocks
- ✓Data organization: No structured-DB equivalent. Persistent data lives in the D / HD register banks
- ✓Function Blocks: Arrange blocks for clear left-to-right data flow
- ✓Function Blocks: Use consistent spacing and alignment for readability
- ✓Function Blocks: Label all inputs and outputs with meaningful names
- ✓Motor Control: Verify motor running with current or speed feedback, not just contactor status
- ✓Motor Control: Implement minimum off time between starts for motor cooling
- ✓Motor Control: Add phase loss and phase reversal protection
- ✓Debug with Wecon PLC Editor / PIStudio: Use the offline simulator to validate logic before downloading
- ✓Safety: Proper machine guarding for rotating equipment
- ✓Use Wecon PLC Editor / PIStudio simulation tools to test Motor Control logic before deployment
Common Pitfalls to Avoid
- ⚠Function Blocks: Creating feedback loops without proper initialization
- ⚠Function Blocks: Connecting incompatible data types
- ⚠Function Blocks: Not considering execution order dependencies
- ⚠Wecon common error: Battery-low alarm on legacy LX3V causing D-range loss
- ⚠Motor Control: Managing starting current within supply limits
- ⚠Motor Control: Coordinating acceleration with driven load requirements
- ⚠Neglecting to validate Current transformers for motor current monitoring leads to control errors
- ⚠Insufficient comments make Function Blocks programs unmaintainable over time
Related Certifications
Mastering Function Blocks for Motor Control applications using Wecon Wecon PLC Editor / PIStudio requires understanding both the platform's capabilities and the specific demands of Industrial Manufacturing. This guide has provided comprehensive coverage of implementation strategies, working code examples, best practices, and common pitfalls to help you succeed with beginner to intermediate Motor Control projects.
Wecon's <1% global market share and moderate in oem machinery, packaging, textiles, plastics, and small-scale process equipment demonstrate the platform's capability for demanding applications. The platform excels in Industrial Manufacturing applications where Motor Control reliability is critical.
By following the practices outlined in this guide—from proper program structure and Function Blocks best practices to Wecon-specific optimizations—you can deliver reliable Motor Control systems that meet Industrial Manufacturing requirements.
Next Steps for Professional Development:
1. Certification: Pursue Wecon distributor-led training to validate your Wecon expertise
2. Advanced Training: Consider Project-based engineer certificates for specialized Industrial Manufacturing applications
3. Hands-on Practice: Build Motor Control projects using LX3V hardware
4. Stay Current: Follow Wecon PLC Editor / PIStudio updates and new Function Blocks features
Function Blocks Foundation:
Function Block Diagram (FBD) is a graphical programming language where functions and function blocks are represented as boxes connected by signal line...
The 1-3 weeks typical timeline for Motor Control projects will decrease as you gain experience with these patterns and techniques. Remember: Verify motor running with current or speed feedback, not just contactor status
For further learning, explore related topics including Temperature control, Fan systems, and Wecon platform-specific features for Motor Control optimization.