Fatek Function Blocks for Traffic Light Control: Complete Programming Guide

Learning to implement Function Blocks for Traffic Light Control using Fatek's WinProladder / FATEK Programming Software is a useful skill for PLC programmers working in Infrastructure. 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 Fatek terminology and references controller families such as FBs-MA and FBs-MC. Confirm the exact instructions, data types, firmware requirements, and licensing in the current vendor documentation before choosing hardware or deploying a project.

The Function Blocks approach is particularly well-suited for Traffic Light 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 Traffic Light Control, including timing optimization and emergency vehicle priority.

Throughout this guide, you'll find step-by-step implementation guidance, an illustrative code example, and a verification checklist specific to Infrastructure. Whether you're programming your first Traffic Light Control exercise or transitioning from another PLC platform, use the material as a starting point and validate it in your exact WinProladder / FATEK Programming Software version and controller environment.

Fatek WinProladder / FATEK Programming Software for Traffic Light Control

WinProladder / FATEK Programming Software is a programming environment associated with Fatek controller families such as FBs-MA, FBs-MC, FBs-MN. This guide uses Function Blocks 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 Function Blocks constructs

The project version matches the installed WinProladder / FATEK Programming Software 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 Traffic Light Control exercise, map the required inputs and outputs before writing logic. The example considers 5 sensor types, including Vehicle detection loops, Pedestrian buttons, Camera sensors, and 4 actuator types.

Control Equipment for Traffic Light Control:

NEMA TS2 or ATC traffic controller cabinets

Conflict monitors for signal verification

Malfunction management units (MMU)

Uninterruptible power supplies (UPS)

Controller-family references used in this guide include:

FBs-MA: Confirm CPU, I/O, memory, communications, and Function Blocks support in the current selection guide

FBs-MC: Confirm CPU, I/O, memory, communications, and Function Blocks support in the current selection guide

FBs-MN: Confirm CPU, I/O, memory, communications, and Function Blocks support in the current selection guide

FBs-CB (compact): Confirm CPU, I/O, memory, communications, and Function Blocks 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 Fatek 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 Traffic Light 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 Function Blocks for Traffic Light 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 Traffic Light Control:

Visual representation of signal flow: Critical for Traffic Light Control when handling beginner control logic

Good for modular programming: Critical for Traffic Light Control when handling beginner control logic

Reusable components: Critical for Traffic Light Control when handling beginner control logic

Excellent for process control: Critical for Traffic Light Control when handling beginner control logic

Good for continuous operations: Critical for Traffic Light Control when handling beginner control logic

Why Function Blocks Fits Traffic Light Control:

Traffic Light Control systems in Infrastructure typically involve:

Sensors: Inductive loop detectors embedded in pavement for vehicle detection, Video detection cameras with virtual detection zones, Pedestrian push buttons with ADA-compliant features

Actuators: LED signal heads for vehicle indications (red, yellow, green, arrows), Pedestrian signal heads (walk, don't walk, countdown), Flashing beacons for warning applications

Complexity: Beginner with challenges including Balancing main street progression with side street delay

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 Traffic Light 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 Traffic Light Control using Fatek WinProladder / FATEK Programming Software.

Implementing Traffic Light Control with Function Blocks

Traffic signal control systems manage the safe and efficient flow of vehicles and pedestrians at intersections. PLCs implement signal timing plans, coordinate with adjacent intersections, respond to traffic demands, and interface with central traffic management systems.

This walkthrough demonstrates practical implementation using Fatek WinProladder / FATEK Programming Software and Function Blocks programming.

System Requirements:

A typical Traffic Light Control implementation includes:

Input Devices (Sensors):
1. Inductive loop detectors embedded in pavement for vehicle detection: Critical for monitoring system state
2. Video detection cameras with virtual detection zones: Critical for monitoring system state
3. Pedestrian push buttons with ADA-compliant features: Critical for monitoring system state
4. Preemption receivers for emergency vehicle detection (optical or radio): Critical for monitoring system state
5. Railroad crossing interconnect signals: Critical for monitoring system state

Output Devices (Actuators):
1. LED signal heads for vehicle indications (red, yellow, green, arrows): Primary control output
2. Pedestrian signal heads (walk, don't walk, countdown): Supporting control function
3. Flashing beacons for warning applications: Supporting control function
4. Advance warning flashers: Supporting control function
5. Cabinet cooling fans and environmental controls: Supporting control function

Control Equipment:

NEMA TS2 or ATC traffic controller cabinets

Conflict monitors for signal verification

Malfunction management units (MMU)

Uninterruptible power supplies (UPS)

Control Strategies for Traffic Light Control:

1. Primary Control: Automated traffic signal control using PLCs for intersection management, timing optimization, and pedestrian safety.
2. Safety Interlocks: Preventing Timing optimization
3. Error Recovery: Handling Emergency vehicle priority

Implementation Steps:

Step 1: Survey intersection geometry and traffic patterns

In WinProladder / FATEK Programming Software, survey intersection geometry and traffic patterns.

Step 2: Define phases and rings per NEMA/ATC standards

In WinProladder / FATEK Programming Software, define phases and rings per nema/atc standards.

Step 3: Calculate minimum and maximum green times for each phase

In WinProladder / FATEK Programming Software, calculate minimum and maximum green times for each phase.

Step 4: Implement detector logic with extending and presence modes

In WinProladder / FATEK Programming Software, implement detector logic with extending and presence modes.

Step 5: Program phase sequencing with proper clearance intervals

In WinProladder / FATEK Programming Software, program phase sequencing with proper clearance intervals.

Step 6: Add pedestrian phases with accessible pedestrian signals

In WinProladder / FATEK Programming Software, add pedestrian phases with accessible pedestrian signals.

Fatek Function Design:

P-label subroutines for reuse; some manufacturer-supplied FBs for motion and protocol-specific functions. Library reuse beyond manufacturer FBs is uncommon.

Common Challenges and Solutions:

1. Balancing main street progression with side street delay

Solution: Function Blocks addresses this through Visual representation of signal flow.

2. Handling varying traffic demands throughout the day

Solution: Function Blocks addresses this through Good for modular programming.

3. Providing adequate pedestrian crossing time

Solution: Function Blocks addresses this through Reusable components.

4. Managing detector failures gracefully

Solution: Function Blocks addresses this through Excellent for process control.

Safety Considerations:

Conflict monitoring to detect improper signal states

Yellow and all-red clearance intervals per engineering standards

Flashing operation mode for controller failures

Pedestrian minimum walk and clearance times per MUTCD

Railroad preemption for track clearance

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

Fatek Diagnostic Tools:

WinProladder online monitor,Soft-element watch table,Built-in offline simulator,Modbus RTU / TCP communication analyzer,FvDesigner HMI runtime diagnostics,M8000-range system flags for hardware diagnostics,Distributor support engineers and loaner CPUs,Fatek user community forums (Taiwan-led)

Use the monitoring and diagnostic functions available in your WinProladder / FATEK Programming Software version, and record the software, firmware, hardware, workload, and test procedure with every result.

Fatek Function Blocks Example for Traffic Light Control

Illustrative Function Blocks example for Traffic Light Control using Fatek terminology. Adapt the syntax to your WinProladder / FATEK Programming Software release, compile it, and verify it in an isolated test environment before use on equipment.

(* Fatek WinProladder / FATEK Programming Software - Traffic Light Control Control *)
(* Reusable Function Blocks Implementation *)
(* P-label subroutines for reuse; some manufacturer-supplied FB *)

FUNCTION_BLOCK FB_TRAFFIC_LIGHT_CONTROL_Controller

VAR_INPUT
    bEnable : BOOL;                  (* Enable control *)
    bReset : BOOL;                   (* Fault reset *)
    rProcessValue : REAL;            (* Inductive loop detectors embedded in pavement for vehicle detection *)
    rSetpoint : REAL := 100.0;  (* Illustrative value; replace with a reviewed requirement *)
    bEmergencyStop : BOOL;           (* Safety input *)
END_VAR

VAR_OUTPUT
    rControlOutput : REAL;           (* LED signal heads for vehicle indications (red, yellow, green, arrows) *)
    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;         (* M-flag banks latched on fault detection; HMI alarm-banner integration via FvDesigner or third-party HMI. *)

    (* Internal State *)
    eInternalState : E_ControlState;
    tonWatchdog : TON;
END_VAR

(* Safety Monitor - Conflict monitoring to detect improper signal states *)
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,  (* Illustrative value; tune and verify for the process *)
        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 - Yellow and all-red clearance intervals per engineering standards *)
    rControlOutput := 0.0;
    bRunning := FALSE;
    bFault := NOT bEnable;  (* Only fault if not intentional stop *)
    nFaultCode := fbSafety.FaultCode;
END_IF;

(* Diagnostics - HMI-tier CSV logging via FvDesigner data-logger feature; PLC-tier logging is uncommon. *)
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_BLOCK

Code Explanation:

1.Encapsulated function block follows P-label subroutines for reuse; some manu - reusable across Infrastructure projects
2.FB_SafetyMonitor illustrates status checks and high/low limits; it is not a certified safety function
3.FB_RampGenerator prevents startup issues common in Traffic Light Control systems
4.FB_PIDController tuned for Infrastructure: Kp=1.0, Ki=0.1
5.Watchdog timer illustrates one way to flag an unchanged output for diagnosis
6.Diagnostic function block enables HMI-tier CSV logging via FvDesigner data-logger feature; PLC-tier logging is uncommon. and M-flag banks latched on fault detection; HMI alarm-banner integration via FvDesigner or third-party HMI.

Best Practices

✓Follow Fatek naming conventions: FX-style raw-address conventions dominate (X0, Y0, M100, D100, R0); symbolic nam
✓Fatek function design: P-label subroutines for reuse; some manufacturer-supplied FBs for motion and pro
✓Data organization: No structured DB; D / R register banks with engineer-documented range convention
✓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
✓Traffic Light Control: Use passage time (extension) values based on approach speed
✓Traffic Light Control: Implement detector failure fallback to recall or maximum timing
✓Traffic Light Control: Log all phase changes and detector events for analysis
✓Debug with WinProladder / FATEK Programming Software: Use the offline simulator before live download
✓Safety: Conflict monitoring to detect improper signal states
✓Use a compatible simulator or isolated test rig to test Traffic Light 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
⚠Fatek common error: Battery-low alarm on legacy FBs causing D-range loss
⚠Traffic Light Control: Balancing main street progression with side street delay
⚠Traffic Light Control: Handling varying traffic demands throughout the day
⚠Neglecting to validate Inductive loop detectors embedded in pavement for vehicle detection leads to control errors
⚠Insufficient comments make Function Blocks programs unmaintainable over time

Related Certifications

🏆Fatek distributor-led engineer training

🏆WinProladder course completions

🏆Advanced Fatek Programming Certification

Applying Function Blocks to Traffic Light Control using Fatek WinProladder / FATEK Programming Software 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 beginner Traffic Light 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 WinProladder / FATEK Programming Software 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

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...

Project duration depends on scope, reviews, hardware availability, software and firmware versions, testing, commissioning, and site constraints. Remember: Use passage time (extension) values based on approach speed

For further learning, explore related topics including Temperature control, Highway ramp metering, and Fatek platform-specific features for Traffic Light Control optimization.