3500/50-01-00-01-0 Bently Nevada Speed Monitor Module

• Brand
  Bently Nevada
• Model
  3500/50-01-00-01-0
• Product Name
  Speed Monitor Module
• Dimensions
  349 mm × 206 mm × 30 mm
• Weight
  0.86 kg
• Place of Origin
  United States
• HS Code
  8537101190
• Operating Temperature
  -20 °C to +60 °C
• Storage Temperature
  -40 °C to +85 °C
• Power Supply
  0.32 A
• Warranty
  12 month
• Status
  new brand

Bently Nevada 3500/50-01-00-01-0 Tachometer Module

Voltage & Current

Rack backplane operating power: 24 VDC; typical power consumption: 5.8 W

Transducer excitation output: -24 VDC, maximum 40 mA per channel

Analog recorder output: 4-20 mA, max load resistance 600 Ω

Inputs

2 independent tachometer input channels, compatible with proximity probes and magnetic pick-ups; input signal range: +10 V ~ -24 VDC with internal over-range protection; input impedance: 20 kΩ (standard mode), 40 kΩ (TMR mode); frequency response: 0.5 Hz-10 kHz

Backplane communication input: internal 3500 rack backplane bus for configuration download and data interaction

Outputs

Buffered transducer signal output: front-panel coaxial connectors for each channel; output impedance 550 Ω, short-circuit and ESD-protected

2-channel isolated analog recorder output: 4-20 mA signal proportional to full-scale RPM value

Conditioned Keyphasor signal output to rack backplane for other 3500 monitoring modules

Alarm signal transmitted to 3500 series relay modules; alert and danger thresholds support speed, zero-speed and reverse-rotation monitoring

Digital measurement and diagnostic data output to 3500 rack backplane for host-system access

Supported Systems

Bently Nevada 3500 machinery protection rack system; works cooperatively with 3500/20 communication gateway, 3500/22M TDI transient data interface, 3500 relay modules

Interfaces with external DCS, PLC and SCADA systems via 3500 communication modules; supports Modbus-TCP, Modbus-RTU and proprietary Bently Nevada protocol

Supported Software

3500/01 Configuration Software: module parameter setting, alarm threshold setup, function configuration and diagnostic checking

System 1 Software: real-time machinery condition monitoring, trend analysis, fault diagnosis and historical-data recordingBaker Hugh...

Compatible with third-party HMI/SCADA software for data reading through system-level communication interfaces
3500/22-01-01-01
3500/22 288055-01
1900/65A
24765-02-01
3500/91-01-01-01
3500/44-02-01
TK-3E
177313-02-01
1900/65A-01-01-04-CN-00
2300/20-CN

Common Faults and Troubleshooting for Bently Nevada 3500/50‑01‑00‑01‑0 Tachometer Module

No RPM Reading / Zero‑Speed Indication

Possible causes: Defective magnetic pickup or proximity probe, damaged sensor cable, incorrect probe wiring, missing trigger pulses from the rotating gear, improper channel configuration (gear tooth quantity, trigger threshold), poor backplane contact.

Handling: Check continuity of sensor wiring; examine probe installation gap; inspect the condition of trigger gear; validate tooth‑count and trigger‑threshold parameters within 3500 configuration software; remove and reseat the module in its rack slot; measure ‑24 VDC sensor excitation output.

Fluctuating or Unstable RPM Readings

Possible causes: Inadequate sensor cable shielding, electromagnetic interference, excessive probe vibration, damaged trigger gear with missing teeth, loose terminal connections, signal amplitude close to trigger threshold.

Handling: Route sensor cables away from high‑power cables; verify single‑end grounding for cable shields; fasten all loose terminals; perform visual inspection of trigger gear; fine‑tune signal trigger threshold; check mechanical runout of the rotating shaft.

Channel Fault Alarm / Module Diagnostic Alarm

Possible causes: Sensor short‑circuit or open‑circuit condition, excitation circuit overload, internal module hardware fault, mismatched firmware revision, backplane communication error.

Handling: Disconnect sensor wiring and test for short‑circuit or open‑circuit faults; monitor ‑24 VDC excitation current; install matching firmware version; reload project configuration; perform spare‑module swap test to confirm whether the fault moves with the module.

Loss of Keyphasor Signal

Possible causes: Keyphasor function disabled in software configuration, faulty keyphasor probe, absent or defective trigger notch, incorrect trigger polarity, signal attenuation caused by long‑distance cable transmission.

Handling: Activate Keyphasor function via configuration software; observe keyphasor signal waveform; verify notch depth and physical position; adjust trigger polarity setting; inspect cable integrity.

Abnormal 4‑20 mA Analog Recorder Output

Possible causes: Incorrect full‑scale RPM parameter setting, overloaded output loop, short‑circuit or open‑circuit on signal loop wiring, analog output function disabled.

Handling: Confirm full‑scale RPM configuration; measure actual loop current; ensure external load resistance does not exceed 600 Ω; inspect loop‑circuit wiring; enable analog output channel.

Backplane Communication Failure

Possible causes: Poor electrical contact between module and rack backplane, defective 3500/20 gateway module, abnormal rack power supply, inconsistent project configuration.

Handling: Power down the rack, pull out and re‑insert the module; verify normal 24 VDC rack power supply; check gateway operating status; download valid complete project configuration.

False Zero‑Speed or Reverse‑Rotation Alarm

Possible causes: Improper zero‑speed delay parameter, noise‑induced false trigger pulses, incorrect rotation‑direction configuration, intermittently loose sensor connections.

Handling: Optimize zero‑speed time‑delay setting; take measures to reduce signal noise; double‑check rotation‑direction configuration; tighten and inspect all sensor‑side connections.