Bently Nevada 60M500 vbOnline Pro Monitoring System
The ordering-family base for a distributed permanent-monitoring package combining dynamic channels, condition data and plant-system communication.
Key Information
60M500 identifies the Bently Nevada vbOnline Pro ordering family. An orderable unit requires the approval and System 1 license suffixes after this base, so the complete nameplate code should be captured before replacement or quotation.
The platform acquires machinery-condition signals and can transfer direct, bias, speed, gap and channel-status values to a plant system through Modbus over Ethernet.
Functions
- Collects condition-monitoring data from supported constant-current accelerometers and proximity-transducer channels.
- Provides local acquisition for distributed machinery assets without requiring every channel to terminate in a central rack.
- Communicates selected condition and channel-status variables to a DCS or other Modbus-capable system.
- Works with the associated configuration and condition-monitoring software environment.
Specifications
| Manufacturer | Bently Nevada, a Baker Hughes business |
|---|---|
| Ordering Family | 60M500-AA-BB |
| Submitted Base Code | 60M500 |
| Product Platform | vbOnline Pro |
| Mounting | DIN rail |
| Communication | Modbus over Ethernet |
| Supported Sensor Classes | Constant-current accelerometers and Bently Nevada proximity probes |
| Operating Temperature | -40 to +70 °C |
| Storage Temperature | -45 to +85 °C |
| Humidity | 0 to 95% non-condensing |
| Ordering Decision AA | Approval selection |
| Ordering Decision BB | System 1 license selection |
Installation
- Confirm the complete 60M500-AA-BB order code before treating a base-family page as a replacement specification.
- Map each sensor type, power arrangement, channel purpose and machinery point before cabinet installation.
- Provide suitable DIN-rail space, environmental control, grounding and separation from high-energy wiring.
- Validate Ethernet addressing, Modbus mapping, channel status and software connectivity before the system is accepted.
Lifecycle
- Archive the final channel map, device configuration, network settings and software-license details.
- Keep the exact approval and license suffixes with the asset record to avoid ordering an incomplete variant.
- Review sensor health, network communication and stored configuration during planned maintenance.
FAQ
Is 60M500 a complete orderable model?
It is the ordering-family base. The approval and System 1 license fields must be added as 60M500-AA-BB for an exact unit.
Which suffix choices must be confirmed for 60M500?
Confirm whether multi-approvals are required and whether the unit includes a System 1 license.
What sensor information is needed for a 60M500 enquiry?
Provide sensor type, sensitivity, channel count, cable arrangement, machine points and the required static or waveform data.
Can 60M500 replace a machinery-protection rack?
Do not use the family as a substitute for a hardwired protection system unless the complete machine risk and protection architecture have been engineered for that purpose.
What network details matter before installing 60M500?
Document IP addressing, switch topology, Modbus register use, DCS polling and cybersecurity requirements.
How can IndustryParts identify the exact 60M500 variant?
Send a clear nameplate photograph, approval markings, software-license requirement and the existing configuration record.
