Foxboro Evo FDSI Triconex integrator driver product

Foxboro Evo FDSI Triconex integrator driver product

Product basic information

Key content of the project

Product Name Foxboro Evo FDSI Triconex Integrated Driver

Brand Foxboro (formerly Invensys, under Schneider Electric)

Document version PSS 31S-3A9 B3

The core positioning is an integrated driver based on the TSAA protocol, which enables data exchange and unified management between the Triconex security controller and the Foxboro system

The core protocol Triconex System Access Application (TSAA) protocol is designed specifically for secure applications

Core carrier FBM232 (single module, non redundant), FBM233 (dual module, redundant)

Core functions and advantages

（1） System integration and data interaction

Bidirectional data read and write: Supports real-time data exchange between Foxboro system and Triconex controller, including input and output of analog (integer/IEEE single precision floating-point) and digital quantities.

Efficient access method: The I/O points of the Triconex controller can be directly accessed through the TriStation tag name or Modbus alias without additional adaptation.

Batch operation support: A single write command can achieve multi-point writing, improving data transmission efficiency.

System Function Reuse: Directly supports the standard factory management functions (such as startup and fault detection) and operator display interface of Foxboro Evo/I/A Series, without the need for separate development.

（2） Redundancy and reliability design

Redundant configuration: FBM233 dual modules can form a redundant architecture, which is divided into a master module and a tracker module. The modules monitor the health status and share device information through communication links.

Fault switching: When the main module fails, it automatically switches to the tracking module without data loss during the switching process, and can also be manually triggered through System Manager.

Fault maintenance: When FBM or network faults occur, replacing modules or repairing the network will not affect the normal transmission of on-site I/O signals.

（3） Diagnostic and monitoring capabilities

Enhanced Diagnostic Monitoring (EnDM): Supports the integration of Triconex Enhanced Diagnostic Monitor software, which can be directly launched from Foxboro System Manager to monitor the hardware, communication, and application status of the Triconex controller.

Diagnostic data output: All diagnostic data of Triconex devices are provided through DCI input blocks, which can quickly develop FoxView process graphics to display diagnostic information and status.

Connection detection: System Monitor can detect the real-time connection status of devices. When a device fails, the FDSI ECB201 object will enter a warning state and trigger a system alarm.

（4） SOE event logging function

Event Collection: Sequence of Events (SOE) messages generated by the Triconex system can be collected and recorded to the AIM * Historian or Alarm Provider application through the Aprint mechanism.

Configuration management: SOE configuration information (device IP, event destination, alarm block, time zone, SOE point list) is stored in an XML file, independent of the control application configuration.

Capacity support: The TSAA workstation driver supports up to 10000 Triconex tags for SOE data collection.

Software and hardware compatibility and requirements

（1） Hardware compatibility

Hardware type, supported models, and requirements

FBM module FBM232 (single module, 10/100 Mbps Ethernet), FBM233 (redundant module, 10/100 Mbps Ethernet)

Triconex controllers Tricon v9.7. x and above, Trident v1.2 and above (excluding v2.0-2.1.1), Tri GP v2.1.2 and above

The communication module Tricon requires installation of NCM/TCM module, while Trident requires installation of CM module

Network devices support switches; Trident v3.0 CIM module does not support hubs

（2） Software and System Requirements

Category specific requirements

Foxboro system version I/A Series software v8.4 and above, Control Core Services v9.0 and above

Operating System Windows XP ®、 Windows 7 ®、 Windows Server ®  In 2003 Windows Server ®  2008 R2

Configure software FDSI Configurator (to configure Ethernet ports), TriStation (to configure Triconex devices)

Diagnostic software Triconex EnDM v2.8.0+(requires System Manager v2.5+for direct startup)

Key technical parameters

Parameter category specific specifications

Single FBM supports up to 10 Triconex devices (actual quantity depends on performance and configuration)

DCI connection capacity up to 2000 (used for reading and writing Triconex controller data)

Data point capacity of up to 32000 digital I/O points, or up to 2000 analog systems/I/O values (can be mixed configured)

The fastest data scanning rate is 50 milliseconds per time (not exceeding the Triconex controller's own scanning rate, default is 200 milliseconds per time)

Communication timeout setting: If the controller does not receive a data request for 2 minutes, it will stop sending data

Support control block ECB block (ECB200/FBM232, ECB202/FBM233, ECB201/Triconex devices); DCI block (13 types including BIN, BOUT, IIN, IOUT, etc., including redundancy types)

Supports 13 core commands of TSAA (such as data request/response, clock read/write/adjust, SOE data request, etc.)

Installation and Configuration

Installation feature: Driver installation does not require shutting down system software or restarting workstations/servers; When updating the driver, it can be directly downloaded to FBM232/FBM233 without affecting the operation of other parts of the Foxboro system.

Configuration tool:

Driver configuration: Use FDSI Configurator (to be installed on a compatible workstation/server);

Device configuration: Use the TriStation Configurator to configure the Triconex controller;

SOE configuration: Maintain SOE point and device configuration information through XML files, independent of control applications.

Network configuration:

The Triconex controller needs to be connected to the FBM through a primary/backup hub/switch;

The Trident V3.0 CIM module only supports switches and does not support hubs.

Key issues

Question 1: What is the core integration value of FDSI Triconex Integrated Driver? How to achieve efficient interconnection between Triconex safety controller and Foxboro system?

Answer: The core integration value lies in the deep integration of Triconex security system and Foxboro automation system without the need for separate interface development. It directly reuses the factory management functions, operating interface, and diagnostic tools of Foxboro system, reducing integration costs and improving system consistency. Efficient interconnection implementation method: ① Based on the TSAA protocol designed by Triconex for secure applications, establish a 10/100 Mbps Ethernet connection through FBM232 (single module) or FBM233 (redundant module); ② Support direct access to device I/O points using TriStation tag names or Modbus aliases, and enable multi-point writing with a single command; ③ Driver installation and updates do not require downtime, the configuration process is simple, and a single FBM can connect up to 10 Triconex devices, meeting the integration requirements of medium and large-scale projects.

Question 2: What are the redundant configuration and fault handling designs of this driver? How to ensure the reliability of data transmission?

Answer: Redundancy and fault handling design: ① Hardware redundancy: FBM233 dual modules are used to form a master-slave architecture, with real-time monitoring of health status and sharing of device information between modules; ② Fault switching: When the main module fails, it automatically switches to the tracking module without data loss, and also supports manual switching; ③ Maintenance convenience: In case of FBM or network failure, replacing modules or repairing the network will not affect on-site I/O signals. Data transmission reliability guarantee: ① Communication link redundancy: Build dual links through primary/backup hubs/switches; ② Data scanning mechanism: a scanning rate of up to 50 milliseconds per scan (adapted to controller capabilities) to ensure real-time performance; ③ Timeout protection: If the controller does not receive a request within 2 minutes, it will stop sending to avoid invalid transmission; ④ Diagnostic warning: System Monitor detects connection status in real-time, DCI block outputs diagnostic data, EnDM tool monitors equipment status, and detects potential faults in advance.

Question 3: What Triconex controller models and system environments does the driver support? How can data processing capabilities match project requirements of different scales?

Answer: Compatibility between controller and system environment: ① Supported Triconex controllers: Tricon v9.7. x and above, Trident v1.2 and above (excluding v2.0-2.1.1), Tri GP v2.1.2 and above; ② Compatible Foxboro systems: I/A Series v8.4 and above, Control Core Services v9.0 and above; ③ Supported operating systems: Windows XP/7/Server 2003/2008 R2. Data processing capability adaptation: ① Equipment capacity: A single FBM can support up to 10 Triconex devices, which can be expanded through multiple FBMs; ② Data point capacity: Supports up to 32000 digital I/O points or 2000 analog values, meeting the signal acquisition needs of small (single device) to medium to large (multi device cluster) projects; ③ Connection capacity: 2000 DCI connections can cover the data exchange needs of multiple devices, SOE logs support the collection of 10000 tags, and are suitable for high demand security event tracing scenarios.