Technical Specifications

FAQ

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

The 3500/22M-01-01-00 is a Transient Data Interface module used in the Bently Nevada 3500 monitoring system. Its primary function is to provide the interface between the 3500 rack and higher-level monitoring and diagnostic software while collecting and transferring monitoring data. The module can continuously acquire steady-state data from compatible M-Series monitors and, depending on the system configuration, collect transient dynamic and waveform data. The information can then be transferred through an Ethernet network to a host monitoring system for condition analysis and equipment diagnostics. The module is particularly useful in rotating machinery applications where both continuous operating information and detailed transient data may be required to investigate changes in machine behavior.

2. Where should the 3500/22M-01-01-00 be installed in a 3500 rack?

The 3500/22M should be installed in Slot 1 of the 3500 rack, next to the power supply module. This position is specifically allocated for the TDI or related rack interface functionality within the 3500 system architecture. During installation, the module should be fully inserted into the rack and secured correctly so that the electrical backplane connection is reliable. The installation position should not be changed arbitrarily because the module provides important rack-level data and communication functions. After installation, the module LEDs, Ethernet connection and host software communication should be checked to confirm that the system recognizes the module and monitoring data can be accessed normally.

3. What types of machinery data can the 3500/22M acquire?

The 3500/22M can acquire steady-state data from compatible 3500 Series M-Series monitors and, depending on the system configuration, can also support transient and high-resolution waveform data. Steady-state data is typically used for continuous monitoring of machinery operating conditions, including vibration, position and other parameters processed by the installed monitoring modules. When an abnormal event, alarm or configured trigger occurs, transient data can provide additional information about how the monitored parameters changed during the event. This makes the TDI particularly useful for detailed machinery diagnostics. The exact data available depends on the installed monitor modules, configured channels, system options and the monitoring requirements of the specific application.

4. What is the difference between the 3500/22M and the 3500/20 RIM?

The 3500/22M TDI combines rack interface functionality with data acquisition and communication capabilities, allowing it to provide both system-level interfacing and monitoring data transfer. It is designed to communicate information from the 3500 monitoring system to compatible host software through Ethernet and can support transient and waveform data acquisition depending on the system configuration. The 3500/20 RIM is primarily associated with rack interface functionality, while the 3500/22M provides broader data acquisition and communication capabilities. When upgrading an existing 3500 system, hardware compatibility should not be the only consideration. Software compatibility, communication settings, installed monitor modules and the required data acquisition functions should all be checked before replacing a RIM with a TDI.

5. What should be checked if the 3500/22M cannot communicate with the host system?

Start by checking the power and LED status of the 3500/22M to confirm that the module has started normally. Next, inspect the Ethernet cable, connector and network equipment to verify that the physical network link is available. Because the module uses 10Base-T/100Base-TX Ethernet communication, the host network configuration and applicable communication parameters should also be checked. It is useful to verify basic network connectivity first and then determine whether the monitoring software can identify the 3500 system. If the network connection is functioning but the software cannot retrieve monitoring data, check the system configuration, communication settings and software compatibility. In networks containing multiple industrial devices, IP address conflicts and network switch configuration should also be considered. After replacing a TDI or network device, compare the new communication settings with the original configuration to prevent configuration-related communication failures.

6. What should be checked if the 3500/22M cannot acquire transient data correctly?

If steady-state data is available but transient data cannot be acquired, first verify that the required transient data functions are configured in the 3500 system and that the installed M-Series monitors support the required data type. The 3500/22M provides standard data interface functionality, while specific transient or high-resolution waveform capabilities can depend on system options and configuration. Check the monitor channels, data acquisition configuration, enabled options and event settings. Trigger conditions should also be reviewed because transient data may only be captured when the configured trigger condition occurs. If the configuration appears correct, controlled testing can be used to verify whether the monitor generates the expected transient information and whether the TDI transfers that data correctly. This process helps determine whether the issue originates from configuration, the monitor module or the TDI itself.

7. What should be done if the 3500/22M LED status is abnormal?

The LED indicators provide important information about the operating condition of the 3500/22M. If the LED status does not correspond to normal operation, first record the current indication and review the available 3500 system diagnostic information. Confirm that the module is correctly installed in Slot 1 and inspect the rack connection, power supply and related modules. If the module starts normally but Ethernet communication is unavailable, investigate the network connection and communication configuration. If the abnormal LED condition occurs together with a loss of monitoring data, the rack connection and system configuration should also be checked. For persistent hardware fault indications, repeatedly resetting the module is not an effective substitute for diagnosis. The fault condition and diagnostic information should be recorded before further troubleshooting or module replacement is performed.

8. What maintenance is recommended for the 3500/22M-01-01-00?

Routine maintenance should focus on the module installation, rack connection, Ethernet communication and data acquisition functions. Periodically verify that the module remains securely installed in Slot 1 of the 3500 rack and inspect the connectors for looseness, contamination or physical damage. The Ethernet connection and communication status should also be checked to ensure that the host monitoring system continues to receive 3500 data correctly. For critical rotating machinery monitoring systems, steady-state values and historical trends should be reviewed regularly to confirm that the TDI is continuously transferring the expected information. If transient or waveform data functions are used, the related channel configuration, enabled options and trigger settings should also be verified. Before replacing or upgrading the module, save the existing configuration and communication parameters. After replacement, verify the module status, network communication, steady-state data and transient data acquisition before returning the monitoring system to normal operation.