Description
Product Core Brief
- Model: 3500/92
- Brand: Bently Nevada
- Series: 3500 Machinery Protection System
- Core Function: Acts as the communication bridge between the 3500 rack and external control systems (DCS, PLC, SCADA).
- Product Type: Communication Gateway Module
- Key Specs: Modbus TCP/IP & RTU | Dual Ethernet (Redundant) | RS232/485 Serial
- Condition: New Original (New Surplus)
BENTLY 3500/92
Product Introduction
The BENTLY 3500/92 is the Communication Gateway Module for the Bently Nevada 3500 Machinery Protection System. It serves as the “nerve center” for data integration, allowing operators and control engineers to access real-time vibration, displacement, temperature, and alarm data from the 3500 rack via standard industrial protocols.
This module supports Modbus TCP/IP (via Ethernet) and Modbus RTU (via Serial), making it universally compatible with most plant automation systems. It also supports the Bently Nevada proprietary protocol for configuration and data acquisition software. The 3500/92 is typically installed in the dedicated communication slot (usually the rightmost slot) of the 3500 rack.
Key Technical Specifications
- Module Type: Communication Gateway
- Supported Protocols: Modbus TCP/IP, Modbus RTU, Bently Nevada Proprietary Protocol
- Ethernet Interface: Dual RJ-45 (10BASE-T), supports redundancy
- Serial Interface: RS232 (DB9) & RS485 (DB9/Terminal)
- Power Consumption: ~5.0 Watts (Typical)
- Indicators: OK LED (System Health), TX/RX LED (Communication Activity)
- Operating Temperature: -30°C to +65°C
- Software Requirements: 3500 Rack Configuration Software / System 1
BENTLY 3500/92
Quality Control Process (Engineer’s Perspective)
- Incoming Verification: Verify part number (e.g., 3500/92-04-01-00) and key component numbers (e.g., 136180-01 Main Board, 136188-02 Terminal Board). Inspect RJ-45 and DB9 connectors for pin damage.
- Visual Inspection: Check for physical damage on the main board and terminal block. Verify no corrosion on the Euro-connector.
- Live Functional Test: Install in rack. Verify “OK” LED is solid green. Check “TX/RX” LED flashes when polling data.
- Protocol Test: Connect via Ethernet. Verify Modbus TCP register read/write capability. Connect via Serial. Verify Modbus RTU response.
- Final QC & Packaging: Seal in anti-static bag. Apply QC Passed label with date.
Replacement Pitfall Guide
❗ Terminal Board Matching: The 3500/92 often requires a specific terminal board (e.g., 136188-02) for physical wiring. Ensure you have the matching terminal board if replacing the entire assembly.
❗ Protocol Limitations: The 3500/92 does not support the legacy “Main Value Modbus Registers” in the same way as the older 3500/90. It uses a configurable Modbus register utility. Verify your DCS/PLC mapping matches the 3500/92 register map.
❗ Slot Placement: This module must be installed in the designated communication slot (typically the rightmost slot). Installing it in a standard monitor slot will prevent operation.
❗ Redundancy Configuration: If using dual Ethernet for redundancy, ensure both cables are connected and the redundancy mode is enabled in the 3500 Configuration Software. A single cable failure should not drop communication.
❗ Protection Path Independence: The 3500/92 is for data communication only. It is not part of the critical protection path. A gateway failure will not trip the machine or affect local relay outputs.
❗ Firmware Compatibility: Ensure the firmware version on the 3500/92 is compatible with your 3500 Rack Configuration Software version. Mismatched versions can cause communication timeouts.
Keep these in mind and you’ll cut 90% of rework time.
Compatibility Matrix & Benchmarks
- 3500/92 → 3500/91 : Alternative — Use 3500/91 for older Ethernet-only applications (no Modbus RTU)
- 3500/92 → 3500/22M : Complementary — 3500/22M is for System 1/Waveform data; 3500/92 is for DCS/PLC Modbus
- 3500/92 → 136188-02 : Accessory — Required Terminal Board for external wiring
Benchmarks:
- Modbus TCP Response: < 100 ms (Typical)
- Max Modbus Registers: Configurable (Check Utility)
- Boot Time: < 30 seconds to “OK” LED
