Technical Specifications

FAQ

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

The 3500/91-01-01-02 is an EGD Communication Gateway Module designed for the Bently Nevada 3500 machinery protection system. Its primary function is to transfer monitoring values, equipment status, and related system information from the 3500 rack to compatible external control and monitoring systems. The module provides an Ethernet-based communication path that allows EGD-compatible controllers to access information from the 3500 system. In installations containing multiple monitoring modules, the gateway provides centralized access to rack, module, and channel information, making it easier for PLCs, DCS platforms, and other supervisory systems to incorporate machinery condition data into a broader plant automation architecture.

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

The 3500/91-01-01-02 uses EGD communication and supports EGD Version 2.01 together with Ethernet UDP/IP. The Ethernet interface complies with IEEE 802.3 and IEEE 802.3u standards and supports 10BASE-T and 100BASE-TX connections. This communication architecture is suitable for industrial control systems that require access to 3500 machinery monitoring data. The external controller must support the appropriate EGD communication functions and must be configured with compatible network and data exchange parameters. If the controller, gateway, or network equipment uses inconsistent settings, communication may fail even when the physical Ethernet connection appears to be normal.

3. What monitoring data can the 3500/91-01-01-02 transmit?

The gateway can transmit a range of monitoring and status information from the 3500 rack, including rack status, module status, channel status, data value status, floating-point measurement values, and floating-point setpoints. These data points allow an external control system to obtain information about the condition and operation of the 3500 system and the associated machinery. The gateway also supports consumer exchanges such as Group Reset, Group Trip Multiply, Group Alarm Inhibit, and Group Special Alarm Inhibit. Because some of these functions can affect alarm or protection behavior, they should be configured according to the overall machinery protection design and controlled appropriately to prevent unintended changes to protection functions.

4. Can the 3500/91-01-01-02 be connected to a PLC or DCS?

Yes. The 3500/91-01-01-02 can use EGD Ethernet communication to provide 3500 rack data to compatible PLCs, DCS systems, and other industrial monitoring platforms. The 3500 system is typically responsible for dedicated machinery condition monitoring and protection, while the PLC or DCS handles process control and plant-level automation. Through the EGD gateway, measurement values, alarm conditions, channel status, and module status can be transferred to the higher-level control system for centralized monitoring. During integration, the required data points, communication addresses, data types, and update requirements should be clearly defined. Signals intended only for display should also be distinguished from those permitted to participate in alarm, interlock, or control logic.

5. What system requirements are needed to use the 3500/91-01-01-02?

The 3500/91-01-01-02 is designed to operate within a compatible 3500 system architecture and requires a 3500/22M TDI meeting the applicable firmware requirements. The system configuration software must also meet the required compatible version. Only one EGD Communication Gateway Module should be configured per 3500 rack, so the communication architecture should be planned according to the data requirements of the complete rack. After installation, both the internal communication between the gateway and the 3500 rack modules and the external Ethernet connection to the control system should be verified. Correct hardware compatibility alone is not sufficient; EGD network parameters and data exchange configurations must also be consistent for reliable data transmission.

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

When communication problems occur, first check the OK and TX/RX indicators on the front panel to determine whether the module is operating normally and whether communication activity is present. Next, verify the 3500 rack power supply, module seating, and communication status of the 3500/22M TDI. On the network side, inspect the RJ-45 connector, Ethernet cable, switch port, and associated network equipment. Once the physical connections have been confirmed, check the EGD configuration in the external controller, including network addressing, data exchange parameters, and data mapping. If all 3500 data is unavailable, the gateway and network communication path should be investigated first. If only one measurement is abnormal, the corresponding monitoring module, channel, and field sensor should also be checked.

7. What should be done if the PLC or DCS receives incorrect data?

If the PLC or DCS can communicate with the 3500/91-01-01-02 but receives incorrect, missing, or outdated values, first determine whether the problem is related to data mapping or the original measurement. Compare the external system’s data addresses, data types, and EGD configuration with the actual 3500 system configuration. If only one channel is affected, inspect the corresponding monitoring module and sensor signal. If multiple modules are affected simultaneously, the gateway, TDI, and network communication should be investigated. For values that are clearly incorrect, verify the original measurement inside the 3500 system as well. The communication gateway transfers data but cannot correct an incorrect measurement generated by a field sensor or monitoring module.

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

Before replacing the 3500/91-01-01-02, confirm that the communication problem is actually caused by the EGD gateway rather than the 3500/22M TDI, rack power supply, Ethernet cable, network switch, or external controller configuration. Check the OK and TX/RX indicators and verify that internal 3500 rack communication is functioning correctly. Then inspect the RJ-45 connection, network link, and EGD data configuration. If only certain monitoring values are affected, inspect the associated monitoring modules and channels before replacing the gateway. Once the gateway has been confirmed as faulty, record the existing communication parameters and data mapping. After replacement, verify rack communication, Ethernet connectivity, EGD data exchanges, measurement values, status information, and required control-related data functions before returning the system to normal operation.