Technical Specifications

FAQ

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

The 3500/91-01-01-BR is an EGD Communication Gateway Module designed to provide communication between a Bently Nevada 3500 machinery protection rack and compatible external control or monitoring systems. It transfers rack-monitored values and status information through an Ethernet-based communication path, allowing external controllers to access information generated by the 3500 monitoring system. This makes it suitable for industrial applications where machinery condition data needs to be integrated into a larger automation or supervisory control architecture. The gateway can provide information from different rack modules and channels while allowing the dedicated 3500 machinery monitoring and protection functions to remain within the 3500 system.

2. Which communication protocols does the 3500/91-01-01-BR support?

The 3500/91-01-01-BR supports Ethernet Global Data (EGD) Version 2.01 and Ethernet UDP/IP communication. The Ethernet interface is based on IEEE 802.3 and IEEE 802.3u standards and supports 10 Mbps and 100 Mbps communication. The Ethernet connection provides a suitable communication path for transferring 3500 monitoring information to compatible controllers. During commissioning, the external controller must be configured with communication parameters that correspond to the gateway configuration. Network addressing, EGD data exchanges, and communication mapping should be checked carefully because an incorrect configuration can prevent the external controller from receiving valid data even when the physical Ethernet connection is functioning correctly.

3. What types of data can the 3500/91-01-01-BR transmit?

The gateway can provide several types of information from the 3500 rack, including rack status, module status, channel status, data value status, floating-point measurement values, and floating-point setpoints. This allows an external control or monitoring system to obtain both measurement information and the status information required to correctly interpret those measurements. 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 according to the machinery protection strategy because some of them can affect alarm or protection-related behavior. Proper data mapping is particularly important when multiple monitoring modules and channels are installed in the same 3500 rack.

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

Yes. The 3500/91 EGD gateway is designed to provide data communication between the 3500 machinery monitoring system and compatible external controllers, which can include PLC, DCS, or other EGD-compatible automation platforms. The 3500 system can continue to perform dedicated machinery monitoring and protection functions while selected monitoring data and status information are transferred to the plant-level control system. During integration, engineers should define the required measurements, channel status information, alarm states, and setpoints before configuring the external controller. Signals intended only for monitoring should also be separated from signals that are allowed to participate in control, interlock, or alarm logic.

5. What system requirements are needed for the 3500/91-01-01-BR?

The 3500/91 EGD gateway requires a compatible 3500/22M TDI to communicate with the monitoring modules installed in the rack. The applicable TDI firmware should be Version 1.20 or higher, and the 3500 Rack Configuration Software should meet the required compatible version. Only one EGD gateway is permitted per 3500 rack. The gateway must also be correctly integrated with the Ethernet network and external EGD-compatible controller. Before commissioning, the rack configuration, TDI status, communication parameters, Ethernet connection, and EGD data exchanges should all be verified. This helps prevent communication problems caused by incompatible firmware, incorrect rack configuration, or inconsistent controller settings.

6. How should communication problems with the 3500/91-01-01-BR be troubleshot?

When communication problems occur, first check the OK and TX/RX LEDs on the front panel. The OK LED should indicate normal module operation, while the TX/RX LED provides an indication of communication activity with the 3500 rack. Next, inspect the 3500 rack power supply, module installation, and 3500/22M TDI communication. The Ethernet cable, RJ-45 connector, network switch, and external controller connection should then be checked. If the physical network is functioning correctly, verify the EGD configuration, network settings, data exchange parameters, and data mapping in the external controller. If the entire rack is unavailable, the gateway, TDI, or network path should be investigated first. If only one measurement is affected, the corresponding monitoring module or channel should also be checked.

7. What should be checked if the external system receives incorrect or missing data?

If the external PLC, DCS, or monitoring system can communicate with the 3500/91-01-01-BR but receives incorrect, incomplete, or outdated information, first compare the external data configuration with the actual 3500 rack configuration. Check the EGD data exchange definitions, data addresses, data types, and channel mapping. If only one channel produces incorrect information, inspect the associated monitoring module and field input. If several modules or channels are affected at the same time, the gateway, TDI, and Ethernet communication path should be investigated. It is also important to verify the original measurement inside the 3500 system because a communication gateway only transfers the available data; it cannot correct an incorrect measurement generated by a sensor or monitoring module.

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

Before replacing the 3500/91-01-01-BR, confirm that the gateway is actually responsible for the communication problem. Check the module LEDs, rack power, module seating, 3500/22M TDI communication, Ethernet cable, RJ-45 connection, network equipment, and external controller configuration. If only selected data points are affected, inspect the associated monitoring channels before replacing the gateway. Once the gateway has been identified as the source of the problem, record the existing EGD configuration and data mapping before removal. After installing the replacement module, verify rack communication, Ethernet connectivity, EGD data exchanges, measurement values, channel status, alarm information, and any configured consumer exchanges. The system should be returned to normal operation only after stable communication and correct data transmission have been confirmed.