Rack input
The backplane carries data from the installed cards into the CPUR2 controller path.
Product Introduction
The Meggitt Vibro-Meter CPUR2 601-026 / A1 | CPUR2 601-026 / A0 entry combines two supplied VM600 CPUR2 controller-card designations. The A1 and A0 suffixes remain visible as separate variant records within the combined comparison page.
In the VM600 rack, CPUR2 601-026 / A1 | CPUR2 601-026 / A0 occupies the controller layer. The backplane carries rack data into the controller path, while the paired communications interface provides the configured external service.
The combined record does not merge the two suffixes into a new part number. CPUR2 601-026 / A1 and CPUR2 601-026 / A0 remain the two exact supplied identifiers used when the controller variant and rack record are documented.
Technical Information
| Technical item |
|
|---|---|
| Brand | Meggitt Vibro-Meter |
| Product type | VM600 CPUR2 controller-card variant pair |
| Product family | CPUR2 |
| Variant A | 601-026 / A1 |
| Variant B | 601-026 / A0 |
| System | VM600 |
| Rack role | Controller-side processing |
| Rack interface | VM600 backplane |
| External relation | Paired communications interface |
| Data source | Installed VM600 rack cards |
| Data destination | Configured external service |
| Rack compatibility | Later VM600 ABE04x rack with I2C interface |
| Card position | Front of rack, typically slot 0 |
| Paired card position | IOCR2 directly behind CPUR2 |
| Backplane connection | Two connectors per card |
| Fieldbus capacity | Up to 2 fieldbus interfaces |
| System Ethernet | 2 × 10/100/1000BASE-T(X), up to 1 Gbps |
| Fieldbus data | Up to 244 input and 244 output bytes per PROFIBUS interface |
| Alarm reset | Front-panel button for latched MPC4 alarms |
| Configuration software | VibroSight software |
| Record rule | Keep A1 and A0 as separate supplied variants |
| Controller path | VM600 backplane to paired interface |
| Interface stage | Configured external network or fieldbus |
| Rack data source | Installed VM600 cards |
| Designation scope | Two separate supplied CPUR2 variant records |
Monitoring and Control: CPUR2 Variant Roles
CPUR2 601-026 / A1 | CPUR2 601-026 / A0 represents two controller-card records that occupy the VM600 controller layer.
→
Controller stage
Each listed CPUR2 variant handles the rack-side controller function.
→
External handoff
The paired communications interface carries the configured service beyond the rack.
Configuration and Programming: Variant Records
The combined page compares CPUR2 601-026 / A1 | CPUR2 601-026 / A0 without treating the suffixes as one interchangeable code.
A1 record
CPUR2 601-026 / A1 is retained exactly as the supplied controller designation.
-
A0 record
CPUR2 601-026 / A0 is retained separately as the second supplied designation. -
Rack mapping
The controller variant is recorded with its rack position and paired interface.
Frequently Asked Questions
Why are CPUR2 601-026 / A1 and CPUR2 601-026 / A0 shown together?
The relevant system record is CPUR2 601-026 / A1 | CPUR2 601-026 / A0. CPUR2 601-026 / A1 and CPUR2 601-026 / A0 are shown on one comparison page, but each remains a separate supplied controller-card designation.
Does the combined CPUR2 601-026 / A1 | CPUR2 601-026 / A0 entry create a new part number?
In the rack path for CPUR2 601-026 / A1 | CPUR2 601-026 / A0, no. The combined display groups two records for comparison; CPUR2 601-026 / A1 and CPUR2 601-026 / A0 remain the exact identifiers used in the rack record.
What rack path applies to CPUR2 601-026 / A1 | CPUR2 601-026 / A0?
To trace CPUR2 601-026 / A1 | CPUR2 601-026 / A0, the VM600 backplane carries rack data into the selected CPUR2 controller variant, and the paired communications interface carries the configured external service.
Can the A1 and A0 suffixes be treated as a protocol code on CPUR2 601-026 / A1 | CPUR2 601-026 / A0?
CPUR2 601-026 / A1 | CPUR2 601-026 / A0 does not choose the external protocol. A1 and A0 are retained as supplied variant notation; the external protocol belongs to the installed communications interface and its configuration.
Which hardware should be checked with CPUR2 601-026 / A1 | CPUR2 601-026 / A0?
When documenting CPUR2 601-026 / A1 | CPUR2 601-026 / A0, check the physical controller nameplate, VM600 rack position, paired communications interface and external cable path for the exact variant being documented.
How should a BOM list CPUR2 601-026 / A1 | CPUR2 601-026 / A0?
During a CPUR2 601-026 / A1 | CPUR2 601-026 / A0 review, list CPUR2 601-026 / A1 and CPUR2 601-026 / A0 as separate supplied identifiers under the combined comparison entry instead of shortening them to CPUR2.
Shipping Services
Shipping Services
MOORE AUTOMATION
https://www.mvme.cn/
Moore Automation links packing information, shipment handoff, delivery documents and tracking updates to the confirmed request.
The complete model and quantity remain visible during dispatch communication so logistics updates refer to the same requested parts.
No related record found