Getting Started with PMCE for the Bristol FB300 RTU

Quick Answer

PMCE (Process Monitoring and Control Engine) is Emerson's configuration and programming environment for Bristol ControlWave and FB300 RTUs. It replaces the legacy ACCOL Workbench and provides a modern graphical interface for I/O configuration, control logic development, communication setup, and online diagnostics.

What Is PMCE?

PMCE is the primary tool that field engineers and system integrators use to program and maintain Bristol FB300 RTUs in oilfield SCADA systems. It runs on Windows and communicates with the RTU over serial (RS-232) or Ethernet (TCP/IP). Key capabilities include:

• Graphical I/O configuration: Define analog inputs, digital I/O, and communication ports through a tree-based project navigator.
• Control logic programming: Build control strategies using function blocks (analog scaling, alarms, timers, PID, flow calculation, math, and logic operations).
• Online monitoring: Connect to a running FB300 and view live point values, force outputs for testing, and trend variables in real time.
• Program download/upload: Transfer the complete configuration to the RTU or retrieve the running configuration for backup.
• Diagnostic tools: View system status, communication statistics, error logs, and memory utilization.

Step 1 — Install PMCE

1. Obtain the PMCE installer from Emerson's Guardian support portal or your Emerson sales representative. PMCE is bundled with the ControlWave Designer suite in newer releases.
2. Run the installer on a Windows 10 or Windows 11 workstation. PMCE requires .NET Framework 4.x or later.
3. Install any required USB-to-serial drivers if you will be connecting to the FB300 via RS-232 through a USB adapter.
4. Record the installed PMCE version number in your project records for traceability and compatibility tracking.

Step 2 — Create a New Project

1. Launch PMCE and select File > New Project.
2. Enter the project name (use the site or RTU identifier, e.g., TB01_FB300 for Tank Battery 01).
3. Select the target device type — choose the FB300 model that matches your installed hardware. The device selection determines which I/O card types, communication options, and firmware features are available in the configuration.
4. Set the project save location. Use a version-controlled directory (Git, SVN) so that configuration changes are tracked.

Step 3 — Understand the PMCE Workspace

The PMCE workspace is organized into these key areas:

• Project Navigator (left panel): A tree view showing the RTU hardware configuration, I/O modules, communication ports, control tasks, and system parameters. This is where you add and organize all configuration elements.
• Configuration Editor (center panel): When you select an item in the Project Navigator, its configuration parameters appear here. This is where you set point names, scaling values, alarm limits, and function block parameters.
• Output/Messages (bottom panel): Displays compilation results, download progress, error messages, and search results.
• Toolbar: Quick access to compile, download, upload, connect/disconnect, and online monitoring functions.

Step 4 — Connect to the FB300

1. Configure the communication path in PMCE:
   • Serial: Select the COM port, set baud rate (typically 9600 or 19200), parity (None or Even), and 1 stop bit.
   • Ethernet: Enter the FB300's IP address and the TCP port (default varies by firmware version).
2. Click Connect (or use the Online menu). PMCE will establish a session with the FB300 and display the RTU status — firmware version, run mode, and communication statistics.
3. If this is a new (factory-default) RTU, the connection establishes with default communication parameters. If the RTU has an existing configuration, verify you are connecting to the correct unit by checking the RTU name and serial number in the status display.

Step 5 — The PMCE Programming Model

PMCE organizes the FB300 configuration using these core concepts:

Tasks

A task is a unit of execution that runs at a defined scan rate. The FB300 supports multiple tasks with different priorities and scan intervals. Typical task organization:

• Fast task (100–500 ms): Critical control loops, safety shutdowns, and fast-responding analog readings.
• Normal task (1–5 seconds): Standard I/O scanning, alarm processing, and communication handling.
• Slow task (10–60 seconds): Calculations, logging, and non-time-critical operations.

Blocks

Within each task, blocks are the functional units that perform specific operations — reading an analog input, applying scaling, comparing against alarm setpoints, executing a PID algorithm, or driving a digital output. Blocks are connected by wiring their input/output parameters.

Parameters

Each block has parameters that configure its behavior (e.g., an analog input block has parameters for channel number, scaling zero, scaling span, engineering units, and filter time constant). Parameters can be constants, references to other block outputs, or system variables.

Step 6 — First Compile and Download

1. After configuring at least one I/O point and a basic control task, click Compile. PMCE validates the configuration and reports any errors (undefined references, address conflicts, resource limits).
2. Fix any compilation errors — the most common are duplicate point names and I/O channel conflicts.
3. Click Download to transfer the compiled configuration to the FB300. PMCE will prompt for confirmation since downloading replaces the running configuration.
4. After download, verify the RTU enters RUN mode and the I/O points are scanning correctly by switching to online monitoring mode.

Best Practices

• Version control: Store PMCE project files in a Git repository. Commit after every successful download to the RTU.
• Naming conventions: Use consistent point names across all FB300 units in your SCADA system (e.g., TB01_TK101_LVL).
• Backup before changes: Always upload the current running configuration before making modifications, so you have a rollback point.
• Test in simulation: PMCE supports offline simulation for testing control logic before deploying to live hardware.