Foxboro Evo FDSI Triconex integrator driver product

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.