Bently Nevada 60R/CMM01 Condition Monitoring Module
The two-slot Orbit 60 condition-monitoring module family for continuous System 1 data transfer and buffered historical capture.
Product Identification
60R/CMM01 identifies the two-slot Orbit 60 Condition Monitoring Module family. It listens to system measurements, waveforms, status, configuration, process data and event records without writing into the protection system.
The module transfers data to System 1 and buffers historical information in non-volatile storage when the connection is interrupted. Exact ordering requires the approval and SIL suffixes.
Engineering Data
| Manufacturer | Bently Nevada, a Baker Hughes business |
|---|---|
| Ordering Family | 60R/CMM01-AAA-B |
| Submitted Base Code | 60R/CMM01 |
| Module Type | Condition Monitoring Module |
| Rack Space | 2 slots |
| Ethernet Ports | 2 independently configurable RJ-45 ports |
| Ethernet Rate | 1000/100/10 Base-T, auto-negotiation |
| Maximum Cable Length | 100 m |
| Maximum Power Consumption | 14.2 W |
| Typical Power Consumption | 10.5 W |
| Data Direction | Read-only from the protection-system perspective |
| Historical Storage | Non-volatile buffer during host connection loss |
| Approval Field | AAA suffix required |
| SIL Field | B suffix required |
Functions
- Continuously transfers Orbit 60 condition data to System 1.
- Buffers historical information until it can be off-loaded after a network interruption.
- Supports extraction of additional measurements and waveforms configured by System 1.
- Allows multiple modules where independent System 1 client connections are required.
Applications
- System 1 condition-monitoring connection
- Historical waveform and event collection
- Independent business-network access to Orbit 60 data
Lifecycle
- Maintain current System 1 and module configuration backups.
- Track the full approval suffix and installed slot width.
- Monitor storage, link status and data off-load after communication interruptions.
FAQ
Is 60R/CMM01 a complete orderable code?
It is the two-slot CMM family base; approval and SIL suffixes are required to identify the exact installed module.
Can 60R/CMM02 replace 60R/CMM01 without rack changes?
The newer module occupies one slot, so a 60R/BLK01 blank is needed for the unused position and System 1 version compatibility must be checked.
Does 60R/CMM01 write commands into the protection system?
Its condition-monitoring path listens to system information without writing, which separates business-network access from protection control.
What happens when the System 1 connection to 60R/CMM01 is lost?
The module buffers historical data in non-volatile storage for later off-load, subject to the configured collection and available storage.
What should be supplied for a 60R/CMM01 enquiry?
Send the complete label, approval suffix, chassis type, occupied slots, System 1 version, network configuration and replacement objective.
What acceptance checks follow a 60R/CMM01 replacement?
Verify both links, System 1 recognition, real-time values, waveform requests, event transfer and recovery of buffered data after a controlled disconnect.
