August 15, 2026

DOL Motor Start Stop

DOL Motor Start Stop

Siemens S7-1200 PLC application with SCL, LAD, FBD, and schematic diagram

Category

Motor and Drive Control

TIA Portal Block

FB_001_DOLMotorStartStop

Template Type

motor

Application

DOL Motor Start Stop

Source Files

SCL/001_DOLMotorStartStop.scl | LAD/001_DOLMotorStartStop_LAD.md | FBD/001_DOLMotorStartStop_FBD.md

Schematic Diagram


Functional schematic overview for the PLC application.

I/O and Internal Tags

Area

Tag

Type

Default

Description

INPUT

StartPB

Bool

 

 

INPUT

StopPB

Bool

 

 

INPUT

ResetPB

Bool

 

 

INPUT

AutoMode

Bool

TRUE

 

INPUT

EStopOK

Bool

 

 

INPUT

Permissive1

Bool

 

 

INPUT

Permissive2

Bool

 

 

INPUT

FeedbackOK

Bool

 

 

INPUT

FeedbackDelay

Time

T#3s

 

OUTPUT

RunCommand

Bool

 

 

OUTPUT

RunLamp

Bool

 

 

OUTPUT

ReadyLamp

Bool

 

 

OUTPUT

FaultLamp

Bool

 

 

OUTPUT

FaultCode

Int;

 

0 none, 1 estop, 2 permissive1, 3 permissive2, 4 feedback

VAR

StartPB

Bool

 

 

VAR

StopPB

Bool

 

 

VAR

ResetPB

Bool

 

 

VAR

AutoMode

Bool

TRUE

 

VAR

EStopOK

Bool

 

 

VAR

Permissive1

Bool

 

 

VAR

Permissive2

Bool

 

 

VAR

FeedbackOK

Bool

 

 

VAR

FeedbackDelay

Time

T#3s

 

SCL Program

// Application 001: DOL Motor Start Stop

// Category: Motor and Drive Control

// PLC: Siemens S7-1200

// Language: SCL for TIA Portal

// Note: Training template. Validate all safety and machine behavior before commissioning.

 

FUNCTION_BLOCK "FB_001_DOLMotorStartStop"

{ S7_Optimized_Access := 'TRUE' }

VERSION : 1.0

 

VAR_INPUT

    StartPB : Bool;

    StopPB : Bool;

    ResetPB : Bool;

    AutoMode : Bool := TRUE;

    EStopOK : Bool;

    Permissive1 : Bool;

    Permissive2 : Bool;

    FeedbackOK : Bool;

    FeedbackDelay : Time := T#3s;

END_VAR

 

VAR_OUTPUT

    RunCommand : Bool;

    RunLamp : Bool;

    ReadyLamp : Bool;

    FaultLamp : Bool;

    FaultCode : Int; // 0 none, 1 estop, 2 permissive1, 3 permissive2, 4 feedback

END_VAR

 

VAR

    RunLatch : Bool;

    FeedbackTimer : TON;

    FeedbackFault : Bool;

END_VAR

 

BEGIN

    IF ResetPB AND EStopOK AND Permissive1 AND Permissive2 THEN

        FeedbackFault := FALSE;

        FaultCode := 0;

    END_IF;

 

    IF NOT EStopOK THEN

        FaultCode := 1;

    ELSIF NOT Permissive1 THEN

        FaultCode := 2;

    ELSIF NOT Permissive2 THEN

        FaultCode := 3;

    ELSIF FeedbackFault THEN

        FaultCode := 4;

    END_IF;

 

    IF StopPB OR (FaultCode <> 0) OR NOT AutoMode THEN

        RunLatch := FALSE;

    ELSIF StartPB AND AutoMode AND EStopOK AND Permissive1 AND Permissive2 AND (FaultCode = 0) THEN

        RunLatch := TRUE;

    END_IF;

 

    RunCommand := RunLatch AND AutoMode AND EStopOK AND Permissive1 AND Permissive2 AND (FaultCode = 0);

 

    FeedbackTimer(IN := RunCommand AND NOT FeedbackOK, PT := FeedbackDelay);

    IF FeedbackTimer.Q THEN

        FeedbackFault := TRUE;

        RunLatch := FALSE;

        FaultCode := 4;

    END_IF;

 

    RunLamp := RunCommand AND FeedbackOK;

    ReadyLamp := AutoMode AND EStopOK AND Permissive1 AND Permissive2 AND (FaultCode = 0) AND NOT RunCommand;

    FaultLamp := FaultCode <> 0;

END_FUNCTION_BLOCK

Ladder Logic (LAD) Networks

Network 1 - Reset and fault selection

ResetPB AND EStopOK AND Permissive1 AND Permissive2 ---- FeedbackFault (R)

ResetPB AND EStopOK AND Permissive1 AND Permissive2 ---- MOVE 0 -> FaultCode

NOT EStopOK -------------------------------------------- MOVE 1 -> FaultCode

NOT Permissive1 ---------------------------------------- MOVE 2 -> FaultCode

NOT Permissive2 ---------------------------------------- MOVE 3 -> FaultCode

FeedbackFault ------------------------------------------ MOVE 4 -> FaultCode

 

Network 2 - Run latch

StartPB AND AutoMode AND EStopOK AND Permissive1 AND Permissive2 AND [FaultCode = 0] ---- RunLatch (S)

StopPB OR [FaultCode <> 0] OR NOT AutoMode ------------------------------------------------ RunLatch (R)

 

Network 3 - Run command

RunLatch AND AutoMode AND EStopOK AND Permissive1 AND Permissive2 AND [FaultCode = 0] ----( ) RunCommand

 

Network 4 - Feedback supervision

RunCommand AND NOT FeedbackOK -> TON FeedbackTimer, PT = FeedbackDelay

FeedbackTimer.Q ------------- FeedbackFault (S)

FeedbackTimer.Q ------------- RunLatch (R)

FeedbackTimer.Q ------------- MOVE 4 -> FaultCode

 

Network 5 - Indication

RunCommand AND FeedbackOK ----------------------------------------------------( ) RunLamp

AutoMode AND EStopOK AND Permissive1 AND Permissive2 AND [FaultCode = 0] AND NOT RunCommand --( ) ReadyLamp

[FaultCode <> 0]-------------------------------------------------------------( ) FaultLamp

 

 

Commissioning reminder: validate all I/O mapping, permissive behavior, feedback wiring, emergency-stop circuits, and local safety requirements before running real equipment.

Function Block Diagram (FBD) Networks

Network 1 - Reset/fault logic

AND(ResetPB, EStopOK, Permissive1, Permissive2) -> RESET FeedbackFault, MOVE 0 -> FaultCode

NOT(EStopOK) -> MOVE 1 -> FaultCode

NOT(Permissive1) -> MOVE 2 -> FaultCode

NOT(Permissive2) -> MOVE 3 -> FaultCode

FeedbackFault -> MOVE 4 -> FaultCode

 

Network 2 - Run latch

SR RunLatch

S := AND(StartPB, AutoMode, EStopOK, Permissive1, Permissive2, EQ(FaultCode, 0))

R := OR(StopPB, NE(FaultCode, 0), NOT(AutoMode))

 

Network 3 - Output and feedback

AND(RunLatch, AutoMode, EStopOK, Permissive1, Permissive2, EQ(FaultCode, 0)) -> RunCommand

TON FeedbackTimer(IN := AND(RunCommand, NOT(FeedbackOK)), PT := FeedbackDelay)

FeedbackTimer.Q -> SET FeedbackFault, RESET RunLatch, MOVE 4 -> FaultCode

 

Network 4 - Indication

AND(RunCommand, FeedbackOK) -> RunLamp

AND(AutoMode, EStopOK, Permissive1, Permissive2, EQ(FaultCode, 0), NOT(RunCommand)) -> ReadyLamp

NE(FaultCode, 0) -> FaultLamp

 

 

Commissioning reminder: validate all I/O mapping, permissive behavior, feedback wiring, emergency-stop circuits, and local safety requirements before running real equipment.

Commissioning Checklist

·        Map every PLC tag to the correct physical input, output, HMI tag, or memory address.

·        Compile in TIA Portal and adjust tag names, timers, and setpoints for the real machine.

·        Test normal sequence, stop, reset, feedback failure, timeout, and alarm conditions in simulation first.

·        Use certified safety hardware or fail-safe logic for emergency stops, guards, and hazardous motion.

August 14, 2026

Pressure Transmitter for Industrial Automation in Power Plant: Complete Practical Guide

Introduction

For students and maintenance engineers, this topic is useful because it connects textbook principles with real plant symptoms, commissioning checks, and daily troubleshooting. In a power plant, pressure transmitter is often connected with the boiler auxiliary system, where boiler feed or cooling water must be monitored or controlled safely. This version is written from the troubleshooting and plant reliability point of view, so it focuses on practical decisions: where to install the device, how to wire it, what the PLC should see, which alarms matter, and how a technician should react when the reading is wrong. Use this as a practical bridge between P&ID reading and real plant operation.

Quick Answer

Pressure Transmitter is used to measure or control pressure and convert that process condition into a plant-readable signal such as 4-20 mA with HART. In a power plant, the signal normally travels from the field device to a junction box, PLC panel, HMI screen, and SCADA system. The main benefit is reliable operation: operators can see the process condition, alarms can warn before damage occurs, and maintenance teams can troubleshoot faults such as blocked impulse line or wrong range.

What Is Pressure Transmitter?

Pressure Transmitter is an industrial instrumentation and automation topic related to pressure measurement. The main field device is the pressure transmitter, which handles pressure and communicates using 4-20 mA with HART. In real plants, it is never just a standalone device. It must match the process connection, material compatibility, wiring method, PLC module, HMI display, SCADA alarm philosophy, and maintenance procedure. For SEO readers, the important point is simple: this topic explains how a measured or controlled process condition becomes useful information for operators and engineers.

Why It Matters in This Industry

In a power plant, the boiler auxiliary system can affect production quality, equipment protection, utility consumption, and safety. The process medium is usually boiler feed or cooling water, so installation details such as wetted material, sealing, grounding, and calibration access must be selected carefully. A wrong reading may cause unnecessary shutdowns, poor product quality, unsafe operation, or hidden equipment damage.

Working Principle in Simple Words

The working principle is: A sensing diaphragm converts process pressure into an electrical signal proportional to the applied force. The device output is converted into a standard signal that the PLC can understand. The PLC then scales the raw signal into engineering units, compares it with alarm limits or set point, and shows it on the HMI and SCADA screen. If the loop is part of automatic control, the PLC can also send a command to a control valve, VFD, motor starter, solenoid valve, or alarm system.

Process and Instrumentation Diagram

Figure 1. Pressure Transmitter overview in Power Plant: process flow, tank, pump, instruments, PLC, HMI, SCADA, and instrument air.

Image alt text: Pressure Transmitter in Power Plant process instrumentation diagram with PLC, HMI, SCADA, transmitter, pump, tank, motor, control valve, and instrument air system.

Industrial Example

Consider a boiler auxiliary system in a power plant. The operator starts the system from the HMI, while the PLC checks tank level, pressure, flow, motor feedback, emergency stop, and valve status. The pressure transmitter sends 4-20 mA with HART to the PLC. If the value moves outside the expected range, SCADA records an alarm and the maintenance team can compare the trend with pump current, valve position, and process demand. This example is realistic because protects pumps, filters, vessels, and pipelines from abnormal pressure, and the same loop concept appears in many water, chemical, power, food, HVAC, and manufacturing plants.

PLC, HMI and SCADA Integration












Figure 2. Pressure Transmitter loop wiring, PLC I/O, HMI, SCADA, calibration, troubleshooting, and safety architecture.

Image alt text: Pressure Transmitter PLC loop wiring diagram showing field instrument, junction box, terminal block, PLC input, HMI, SCADA, calibration, safety, and troubleshooting blocks.

·     PLC input or output must match the selected signal type: 4-20 mA with HART.

·     HMI should show process value, set point, mode, alarm status, device health, and manual/auto selection.

·     SCADA should record trends, alarms, operator action, maintenance event, and calibration date.

·     Engineering units and alarm limits must match the datasheet, P&ID, PLC program, and HMI screen.


Installation Guidelines

·     Install the device where it is readable, accessible, drainable, and safe to isolate.

·     Use correct process tapping, impulse line slope, gasket, grounding, cable gland, and tag plate.

·     Avoid routing analog signal cable beside VFD power cable or high-current motor feeders.

·     Check flow direction, valve fail action, junction box sealing, and shield termination.

·     Apply site-specific safety rule: respect high pressure, high temperature, and electrical isolation procedures.

Calibration and Loop Check

Calibration confirms the instrument reading against a known standard. For this topic, the recommended method is: Apply known pressure points with a pressure calibrator and verify zero, span, linearity, and damping. A loop check goes one step further. It proves that the field signal reaches the junction box, terminal block, PLC tag, HMI display, SCADA trend, and alarm system correctly.

1.    Confirm tag number, range, units, process isolation, and permit.

2.    Apply known input points or simulate the output signal.

3.    Verify field display, PLC raw count, scaled value, HMI value, SCADA value, and alarm response.

4.    Record as-found and as-left results.

5.    Remove forces, bypasses, test links, and temporary wiring before handover.

Common Faults and Troubleshooting

Symptom

Likely Cause

Field Action

Value is zero or bad quality

No loop power, open circuit, wrong channel, fuse failure, or device fault.

Check 24 VDC, polarity, terminal tightness, PLC module LED, and device diagnostics.

Value is noisy

Poor grounding, shield issue, vibration, air bubbles, electrical noise, or bad damping.

Check cable route, shield termination, installation point, and transmitter damping.

Value is stuck

Possible blocked impulse line or wrong range, device simulation mode, blocked process connection, or frozen output.

Inspect process connection, remove simulation, and test with a calibrator.

Control output hunts

PID tuning, sticky valve, wrong action, oversized valve, or unstable measurement.

Check controller action, valve stroke, process lag, and trend data.

SCADA alarm not appearing

Wrong tag mapping, disabled alarm, bad deadband, or communication issue.

Verify PLC tag, SCADA tag, alarm limit, deadband, and historian event.

 

Preventive Maintenance Tips

·     Review trends weekly to identify slow drift, intermittent signal loss, and process instability.

·     Inspect cable glands, junction boxes, tubing, impulse lines, air filters, and panel ventilation.

·     Check calibration due date and compare current reading with a portable reference when possible.

·     Keep PLC and HMI backups after any modification.

·     Update loop drawings after field changes so future technicians do not troubleshoot from old information.

Safety Precautions

·     Use lockout and tagout before opening panels or removing field devices.

·     Depressurize and drain process connections before removing transmitters or valves.

·     Do not bypass trips or alarms unless approved by written procedure.

·     Verify hazardous area classification before opening enclosures.

·     Wear PPE suitable for process liquid, heat, pressure, and plant environment.

FAQs


Question

Answer

What is pressure transmitter used for?

It is used to measure or control pressure and send useful information to PLC, HMI, and SCADA systems.

How does pressure transmitter work?

A sensing diaphragm converts process pressure into an electrical signal proportional to the applied force. The result is converted into a signal such as 4-20 mA with HART.

Where is pressure transmitter used in a power plant?

It is used around the boiler auxiliary system, especially where boiler feed or cooling water must be monitored or controlled.

What is the most common troubleshooting point?

A common issue is blocked impulse line or wrong range, but wiring, scaling, grounding, and PLC configuration must also be checked.

How often should calibration be done?

The interval depends on plant criticality, legal requirements, process severity, and instrument history. Many plants use quarterly, six-monthly, or yearly schedules.

What should be shown on HMI?

Process value, set point, engineering unit, alarm state, device status, output percentage, mode, and trend shortcut should be visible.