Technical Specifications

FAQ

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

The 3500/91-01-02-00 is an EGD Communication Gateway Module designed to provide an Ethernet communication path between a Bently Nevada 3500 machinery monitoring rack and compatible external control systems. It allows monitored values and status information from the 3500 rack to be exchanged with controllers using the Ethernet Global Data protocol. The module can transmit rack, module, channel, and data-value status information, as well as floating-point measurement values and setpoints. It can also receive specific control-related exchanges such as group reset, trip multiply, alarm inhibit, and special alarm inhibit commands, making it suitable for integrating machinery monitoring information into a plant control architecture.

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

The 3500/91-01-02-00 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. Because this particular configuration uses the 100BASE-FX I/O module, the network connection is provided through an MT-RJ fiber-optic interface. When integrating the gateway into an existing control network, the controller must support the required EGD communication method and the network configuration should be coordinated with the plant’s Ethernet architecture.

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

The gateway can act as a data producer and provide several categories of information from the 3500 monitoring system. Producer exchanges include rack, module, channel, and data-value status information, floating-point data values, and floating-point setpoints. This allows an external controller to receive important machinery monitoring information without requiring individual hardwired connections for every measurement or status signal. The actual data exchanged depends on the 3500 rack configuration and the controller’s EGD configuration. During commissioning, the data mapping should be verified carefully so that each received value corresponds to the correct monitored channel and engineering variable.

4. Can the 3500/91-01-02-00 receive commands from an external control system?

Yes. In addition to producing monitoring data, the gateway supports specific consumer exchanges from an external controller. These include Group Reset, Group Trip Multiply, Group Alarm Inhibit, and Group Special Alarm Inhibit. These functions allow compatible control systems to interact with selected functions of the 3500 monitoring system through the communication network. Because these commands can affect monitoring and protection behavior, the communication configuration should be carefully validated before the system is placed into service. Particular attention should be given to command permissions, network reliability, controller logic, and the expected behavior of the 3500 rack when communication commands are received.

5. What does the OK LED indicate on the 3500/91-01-02-00?

The OK LED on the front panel provides a basic indication of the operating condition of the gateway module. When the module is operating correctly, the OK indication should show the expected normal state. If the indication does not show the normal operating condition, the module’s installation, rack connection, power supply, configuration, and compatibility with the 3500 rack should be checked. The TX/RX LED provides additional information about communication activity between the 3500/91 module and other modules in the rack. These indicators are useful during commissioning because they provide a quick way to distinguish a basic module or rack problem from a network communication problem.

6. What should be checked if the 3500/91-01-02-00 cannot communicate with the control system?

Troubleshooting should begin with the physical Ethernet connection and the status indicators on the module. Because the 3500/91-01-02-00 configuration uses a 100BASE-FX I/O module, the fiber connection and associated network equipment should be inspected carefully. The EGD configuration, controller settings, network addressing, data exchange configuration, and expected communication parameters should then be verified. It is also important to confirm that the external controller supports the required EGD protocol and that the 3500 rack has the appropriate firmware compatibility. If the module operates normally but no data reaches the controller, the problem is more likely to involve network configuration or EGD data mapping than the basic operation of the gateway itself.

7. How many 3500/91 EGD Gateway Modules can be installed in one 3500 rack?

Only one 3500/91 EGD Communication Gateway Module is permitted per 3500 rack. The main gateway module occupies one full-height slot on the front of the rack, while its associated I/O module occupies one full-height rear slot. This rack-space requirement should be considered when planning a new installation or replacing an existing communication module. Before installation, the available rack positions should be checked and the existing 3500 configuration should be reviewed to ensure that the gateway and its I/O module can be installed correctly without conflicting with other system components.

8. What firmware requirements should be considered when installing the 3500/91-01-02-00?

The 3500/91 EGD gateway requires a compatible 3500/22M Transient Data Interface configuration, with Version 1.20 or higher firmware specified for the gateway application. Firmware compatibility is important because the gateway relies on the 3500 rack’s internal data and communication infrastructure to obtain monitored values and exchange information with the external controller. Before commissioning a replacement module, the existing 3500/22M firmware version should therefore be checked. If the firmware does not meet the required level, the communication functions may not operate as expected. After installation, the module status, rack communication, EGD data exchange, and controller-side data mapping should all be verified before the monitoring system is returned to normal operation.