Controller partner
The CPUM Mk2 processes rack data while IOCN Mk2 600-051 exposes the configured external paths.
Product Overview
At the communications layer, Meggitt Vibro-Meter IOCN Mk2 600-051 is the VM600Mk2 interface module. It links the rack controller to the external Ethernet and fieldbus paths used by the configured monitoring system.
IOCN Mk2 600-051 operates with a CPUM Mk2 rather than acting as a measurement card. Its J2 and J4 connectors serve the fieldbus path, while J6 and J7 serve the Ethernet path, keeping the two external connection types distinct.
Within the rack, IOCN Mk2 600-051 exchanges data with the controller through the VM600Mk2 connection. The selected protocol and cable route are functions of the installed interface arrangement, not of a sensor channel.
Product Data
| Technical item |
|
|---|---|
| Brand | Meggitt Vibro-Meter |
| Product type | Communications interface module |
| Product family | VM600Mk2 |
| Part number | 600-051 |
| Card family | IOCN Mk2 |
| Paired controller | CPUM Mk2 |
| Rack interface | VM600Mk2 connection |
| Fieldbus connectors | J1/J2 for FIELDBUS1; J4/J5 for FIELDBUS2 |
| Ethernet connectors | J6 and J7 |
| Interface role | External network and fieldbus routing |
| Channel role | Communications, not sensor input |
| Rack compatibility | VM600Mk2 ABE04x system rack |
| Module position | Rear of rack, directly behind CPUM Mk2 |
| Backplane connection | Two connectors to the rack backplane |
| Fieldbus ports | 2 interfaces, serial and Ethernet connector per port |
| PROFIBUS interface | RS-485, up to 12 Mbps with automatic baud detection |
| Modbus TCP interface | 10/100BASE-TX, up to 100 Mbps |
| Isolation | 700 VRMS RS-485; 1500 VRMS fieldbus Ethernet |
| Input protection | EMI and signal-surge protection |
| Configuration path | CPUM Mk2 and VibroSight software |
| Status indication | Ethernet and fieldbus link/activity LEDs |
| Rack-side source | Paired CPUM Mk2 controller |
| Protocol layer | Configured Ethernet or fieldbus service |
| Cable grouping | J2/J4 fieldbus; J6/J7 Ethernet |
| Controller partner | CPUM Mk2 rack controller |
System Integration: IOCN and CPUM Pairing
IOCN Mk2 600-051 occupies the communications layer beside the CPUM Mk2 controller in the VM600Mk2 rack.
→
Rack exchange
The two cards exchange their internal data through the VM600Mk2 rack connection.
→
External links
The IOCN connectors carry the selected Ethernet or fieldbus connection away from the rack.
Configuration and Programming: IOCN Protocol Routing
The connector groups on IOCN Mk2 600-051 keep the external protocol routes separate.
J2 and J4
These connectors serve the configured fieldbus route and are not sensor terminals.
-
J6 and J7
These connectors serve the Ethernet route used by the external communications arrangement. -
Protocol mapping
The active protocol follows the installed interface configuration and its cable mapping. -
Controller link
IOCN Mk2 600-051 receives the rack-side data path from the paired CPUM Mk2 before routing the selected protocol.
Frequently Asked Questions
How does IOCN Mk2 600-051 work with the VM600Mk2 rack controller?
IOCN Mk2 600-051 is the communications interface paired with CPUM Mk2 in the VM600Mk2 rack. The controller handles rack processing while the IOCN Mk2 exposes the configured external Ethernet or fieldbus path.
Which connector path should be followed when IOCN Mk2 600-051 has no fieldbus traffic?
In the rack path for IOCN Mk2 600-051, trace the J2/J4 fieldbus path separately from the J6/J7 Ethernet path, then check the paired CPUM Mk2 and the rack connection. The two connector groups serve different external communication routes.
Can IOCN Mk2 600-051 identify whether the rack uses PROFIBUS or Ethernet by its code alone?
No. IOCN Mk2 600-051 identifies the interface card, not the protocol selected by the installed configuration. The connected port, cable and configured communication service must be checked together.
Why is IOCN Mk2 600-051 not a replacement for a VM600 measurement card?
IOCN Mk2 600-051 routes system communications between the rack and external devices. Measurement cards provide the signal channels, so replacing a channel card with a communications interface would change the signal path.
What should be verified before wiring IOCN Mk2 600-051?
When documenting IOCN Mk2 600-051, verify the IOCN Mk2 rack position, the CPUM Mk2 pairing, the selected connector group and the protocol assigned to that path. This confirms that the cable is connected to the intended interface rather than to a measurement input.
How can an installer distinguish an IOCN Mk2 600-051 interface problem from a controller problem?
During a IOCN Mk2 600-051 review, check whether the CPUM Mk2 is exchanging data over the backplane before testing the external IOCN Mk2 connector path. Internal rack data and external protocol traffic are separate checks in the same VM600Mk2 communication chain.
Why Choose Moore Automation
Why Choose Moore Automation
MOORE AUTOMATION
https://www.mvme.cn/
Moore Automation keeps the submitted model visible beside the enquiry details, which helps separate a specific card or interface from a wider product family.
The contact route is presented with the model and destination fields so technical questions can be answered against the same request record.
No related record found