Technical Specifications

FAQ

1. What is the main function of the Bently Nevada 3500/91-01-01-01?

The 3500/91-01-01-01 is an EGD Communication Gateway Module designed to transfer monitoring values and status information from a Bently Nevada 3500 machinery protection rack to compatible external control or monitoring systems. It uses Ethernet-based communication and EGD Version 2.01 to provide a high-speed data path suitable for controller applications. The gateway can make rack, module, channel, measurement status, floating-point data, and setpoint information available to external systems. It can therefore be used to integrate the 3500 machinery protection system with a wider plant automation architecture while keeping the dedicated 3500 monitoring and protection functions operating independently.

2. Which communication protocols are supported by the 3500/91-01-01-01?

The 3500/91-01-01-01 supports Ethernet Global Data (EGD) Version 2.01 and Ethernet UDP/IP communication. Its Ethernet communication conforms to IEEE 802.3 and IEEE 802.3u standards and supports 10 Mbps and 100 Mbps communication speeds. The gateway is intended for EGD-compatible controllers and automation systems that need access to 3500 rack data. The communication architecture supports both data producer and data consumer functions, allowing the gateway not only to provide monitoring information but also to receive specific control-related exchanges such as group reset, trip multiply, alarm inhibit, and special alarm inhibit commands when properly configured.

3. What data can the 3500/91-01-01-01 provide to an external controller?

The gateway can provide several categories of 3500 system information through its producer exchanges. These include rack status, module status, channel status, data value status, floating-point measurement values, and floating-point setpoints. This allows an external controller or monitoring platform to obtain both actual measurement information and the associated status information needed to interpret that data correctly. The gateway also supports consumer exchanges such as Group Reset, Group Trip Multiply, Group Alarm Inhibit, and Group Special Alarm Inhibit. These functions should be configured carefully because they can affect how the 3500 system handles certain operational or alarm-related commands.

4. Can the 3500/91-01-01-01 be integrated with a PLC or DCS?

Yes. The 3500/91-01-01-01 is specifically intended to provide Ethernet-based communication between a 3500 machinery protection rack and compatible external controllers or automation systems. In an industrial installation, the external system can be a PLC, DCS, supervisory monitoring platform, or another EGD-compatible controller. The 3500 system continues to perform its dedicated machinery monitoring and protection functions, while the communication gateway makes selected monitoring values and status information available to the plant control architecture. During integration, engineers should carefully define the data exchanged between the systems and distinguish between information intended for operator monitoring and signals that are permitted to influence control or interlock logic.

5. What are the requirements for using the 3500/91-01-01-01 in a 3500 system?

The 3500/91 EGD gateway requires a compatible 3500/22M Transient Data Interface for communication with the monitor modules. The applicable TDI firmware should be Version 1.20 or higher, while the 3500 Rack Configuration Software should be Version 3.70 or higher. For EGD communication, only one 3500/91 EGD gateway is permitted per rack. During commissioning, the gateway configuration, TDI firmware, rack configuration software, Ethernet settings, and external controller configuration should all be checked. Confirming these requirements before installation helps prevent communication problems caused by incompatible firmware, software, or rack architecture.

6. What should be checked if the TX/RX LED does not indicate normal communication?

If the TX/RX LED does not indicate the expected communication activity, first check whether the gateway is correctly installed and whether the OK LED indicates normal module operation. Next, inspect the Ethernet connection, RJ-45 connector, network cable, and external network equipment. The communication configuration of the connected controller should then be checked to ensure that the EGD settings match the 3500/91 configuration. It is also important to verify that the 3500/22M TDI is communicating correctly with the monitor modules inside the rack. If the gateway itself is operating normally but no external data is available, the problem may be related to the Ethernet network, controller configuration, EGD data mapping, or external system rather than the gateway hardware.

7. Can the 3500/91-01-01-01 send control commands back to the 3500 system?

The 3500/91 EGD gateway supports consumer exchanges in addition to its producer data functions. Supported consumer exchanges include Group Reset, Group Trip Multiply, Group Alarm Inhibit, and Group Special Alarm Inhibit. These functions allow compatible external systems to send specific commands or control-related information to the 3500 system. However, these functions should not be treated as general-purpose control interfaces. They should be configured according to the machinery protection design and carefully evaluated during commissioning. Any command that can influence reset, trip multiplication, or alarm inhibition should be subject to appropriate authorization, interlock design, and operational procedures to prevent unintended changes to the machinery protection system.

8. What should be checked before replacing the 3500/91-01-01-01?

Before replacing the 3500/91-01-01-01, first determine whether the problem is actually caused by the gateway. Check the OK and TX/RX indicators, 3500 rack power, module seating, 3500/22M TDI communication, Ethernet cabling, RJ-45 connections, and external controller configuration. If communication is available but specific values are missing or incorrect, inspect the EGD data configuration and determine whether the issue affects the gateway or an individual monitoring module. Before removing the existing module, record the relevant configuration and data mapping information. After installing the replacement gateway, verify the rack communication, Ethernet link, EGD data exchange, measurement values, status information, and required consumer exchanges. The system should be returned to normal operation only after the communication path and all required data points have been confirmed to function correctly.