General Information

Core Description

The 3500/22-01-01-01 is a Bently Nevada 3500/22M standard transient data interface (TDI) module configured with a standard 10Base-T/100Base-TX copper Ethernet I/O interface and CSA/NRTL/C hazardous area approvals. This single-slot, chassis-resident processor bridges the 3500 machinery protection rack with System 1 condition monitoring and configuration software platforms. It continuously multiplexes steady-state metrics and synchronous or asynchronous dynamic waveforms across M-series monitors, utilizing internal communication processing layers to pass advanced diagnostic waveforms via a secure Ethernet TCP/IP link without interrupting critical protection trip paths.

Specific Application

• Plant-Wide Predictive Diagnostic Networking: Interfacing a 3500 machinery protection rack with System 1 software to continuously stream high-resolution startup, coastdown, and alarm dynamic waveform variables.
• Classified Industrial Enclosure Hosting: Operating as the centralized communications link and rack configuration terminal inside standard Class I Division 2 hazardous plant environments.

Ordering Information

3500/22-01-01-01

System Compatibility

• System Compatibility: The 3500/22-01-01-01 resides exclusively in Slot 1 (the front slot adjacent to the rack power supplies) and requires 1 full-height front slot combined with 1 full-height rear slot for its companion I/O card. It interfaces directly with M-series monitors (e.g., 3500/40M, 3500/42M) over the internal backplane to capture 48 channels of DC-coupled waveforms and supports up to 4 system Keyphasor signals across speed ranges up to 100,000 rpm. Network integration permits a maximum copper cable run of 100 meters, carrying standard BN Host and BN TDI communication protocols.
• Direct Application Alternates: 3500/22-01-02-01 (Fiber-Optic Standard Alternate) and 3500/20 (Legacy Rack Interface Module / RIM).
• Key Differences from Alternates (3500/22-01-01-01 vs. Fiber-Optic / Legacy RIM):
• Physical Media Interface: The 3500/22-01-01-01 utilizes a standard RJ-45 copper port for 10Base-T/100Base-TX connections limited to a 100-meter range. In contrast, the 3500/22-01-02-01 features an MT-RJ male fiber-optic port for 100Base-FX cabling, expanding the distance boundary up to 2000 meters while providing total immunity against high-voltage electromagnetic interference (EMI).
• Dynamic Waveform Collection: The 3500/20 Legacy RIM acts purely as a basic configuration bridge and lacks independent diagnostic processing. The 3500/22-01-01-01 combines the functions of the legacy RIM with a communication processor (like TDXnet), enabling it to collect, buffer, and stream detailed steady-state data alongside 2.5 minutes of pre-alarm waveform captures that the legacy 3500/20 cannot process.

Installation & Troubleshooting FAQ

Q1: What strict component sequence must be followed when upgrading a 3500 rack from a legacy 3500/20 RIM to a 3500/22 TDI?

A: You must completely isolate the chassis power and perform the hardware swap in a precise chronological sequence: 1) Remove the old front RIM, 2) Remove the old rear RIM I/O module, 3) Insert the new TDI I/O module, and 4) Insert the front TDI module. Leaving the old legacy RIM I/O card in the rear slot when sliding in or powering up the new front 3500/22 TDI will cause immediate, catastrophic hardware damage to the new TDI circuit board components.

Q2: The front panel USB-B port is failing to link with my laptop during an on-line configuration download. How do I resolve this ground loop?

A: To maintain critical electrical isolation between the machine chassis and your host system ground, you must utilize the specialized 10-foot A-to-B USB cable (Part Number 123M4610) shipped with the unit. Crucially, the computer or field laptop attached to this USB configuration port must be operating strictly from its internal batteries (unplugged from any AC wall outlets). Keeping the laptop connected to a standard mains utility line will establish a hazardous ground loop that corrupts the serial data stream or triggers an interface dropout.

Q3: What do the OK and CONFIG OK LEDs indicate, and what happens when the Trip Multiply (TM) light turns on?

A: The front panel contains 4 functional LED visual anchors: The OK LED illuminates solid when the internal processor passes its boot diagnostics; the TX/RX LED flashes to track active backplane bus traffic with other monitors; and the CONFIG OK LED confirms the rack houses a validated software configuration matrix. If the TM LED turns on, it indicates the system has been placed into Trip Multiply mode via the rear contacts or software override, which temporarily scales the alarm setpoints by a factory factor to prevent false trips during machine startup transients.

Q4: How do I utilize the front panel Keylock switch to prevent unauthorized or accidental modifications to the monitoring loop parameters?

A: The front-panel configuration keylock provides physical security for your protection logic. Turning the key to the RUN position locks out all local or remote software configuration changes, keeping the rack secure against accidental edits while allowing full data visualization. Turning the key to the PROGRAM position permits real-time local or remote edits via the network. Because the physical key can be removed from the keyhole in either slot setting, you should lock the module in RUN and store the key in a secure instrument vault to maintain compliance with safety-instrumented rules.

Q5: The system log shows a "NOT OK Relay Fault." How does the internal OK relay behave under normal operating states?

A: The I/O module houses a dedicated hardware OK Relay designed to annunciate system errors. This relay always operates as Normally Energized under healthy runtime conditions. If a major fault is detected inside the processor or if backplane power fails, the relay instantly drops out (de-energizes). Field engineers can wire their external annunciator circuits to either the "OPEN" or "CLOSED" dry contacts on the rear terminal block to trigger an automated warning whenever the monitoring path drops off-line.