Mô đun giao diện (Standard Transient Data Interface Module)
Xuất sứ: USA
Nhà cung cấp: ANS Đà Nẵng
Hãng sản xuất: Bently Nevada Việt Nam
0934 039 951
Mô đun giao diện (Standard Transient Data Interface Module) - Bently Nevada
Model: 138607-01
Description:
The 3500 Transient Data Interface (TDI) is the interface between the 3500 monitoring system and GE’s System 1* machinery management software. The TDI combines the capability of a 3500/20 Rack Interface Module (RIM) with the data collection capability of a communication processor such as TDXnet. The TDI operates in the RIM slot of a 3500 rack in conjunction with the M series monitors (3500/40M, 3500/42M, etc.) to continuously collect steady state and transient waveform data and pass this data through an Ethernet link to the host software. (Refer to the Compatibility section at the end of this document.) Static data capture is standard with the TDI, however using an optional Channel Enabling Disk will allow the TDI to capture dynamic or transient data as well. The TDI features improvements in several areas over previous communication processors and incorporates the Communication Processor function within the 3500 rack. Although the TDI provides certain functions common to the entire rack it is not part of the critical monitoring path and has no effect on the proper, normal operation of the overall monitor system. Every 3500 rack requires one TDI or RIM, which always occupies Slot 1 (next to the power supplies). For Triple Modular Redundant (TMR) applications, the 3500 System requires a TMR version of the TDI. In addition to all the standard TDI functions, the TMR TDI also performs “monitor channel comparison”. The 3500 TMR configuration executes monitor voting using the setup specified in the monitor options. Using this method, the TMR TDI continually compares the outputs from three (3) redundant monitors. If the TDI detects that the information from one of those monitors is no longer equivalent (within a configured percent) to that of the other two monitors, it will flag the monitor as being in error and place an event in the System Event List.
