QUICK START MANUAL Document reference MAVM600MK2MPS-QS/E
VM600
Mk2
machinery protection system (MPS) Edition 2 - February 2021
1-22
MPC4
Mk2
+IOC4
Mk2
module network interface
INTRODUCTION TO THE VM600
Mk2
MACHINERY PROTECTION SYSTEM (MPS)
If the automatic discovery does not work (for example, due to a network not meeting the
requirements of zeroconf), then connections between the VibroSight-system components
can be established manually by using the IP addresses of the components.
For example, for VibroSight software to VM600
Mk2
machinery protection system (MPS)
module communications, it is possible to connect from VibroSight System Manager to a
MPC4
Mk2
+IOC4
Mk2
module (even if the MPC4
Mk2
module does not have a valid IP address)
when the computer running VibroSight System Manager and the module are on the same
network. (If necessary, a direct connection between the computer and the device can be
made in order to bypass the network.)
1.10.2 VibroSight network requirements
A network that meets the requirements of zero-configuration networking (zeroconf) is
recommended in order to reduce the need to establish connections between
VibroSight-system components manually.
Network bandwidth and latency recommendations depend on the monitoring system
hardware being used:
For a VM600
Mk2
machinery protection system (MPS), a network that supports bandwidth and
latency requirements equivalent to 100 Mbps LAN or better is recommended.
For reference, for a a VM600 condition monitoring system using VM600 XMx16 + XIO16T
modules, a network that supports bandwidth and latency requirements equivalent to
1000 Mbps (1 Gbps) LAN or better is recommended.
NOTE: The highly configurable nature of the VibroSight software and monitoring system
hardware, and the wide variation in machinery monitoring applications makes it
impossible to define operating limits for a VibroSight network that are correct under
all circumstances.
1.10.3 Wide area networking
It is not recommended to use WANs between VibroSight-system components for reasons of
bandwidth, latency and security.
1.11MPC4
Mk2
+IOC4
Mk2
module network interface
The configuration of the network interface (IP address) of the MPC4
Mk2
must be known in
order to establish communications and work with a MPC4
Mk2
+IOC4
Mk2
module as part of a
VM600
Mk2
machinery protection system (MPS).
For a MPC4
Mk2
module delivered as part of a VM600
Mk2
solution, the module’s IP address
is normally configured as specified at the time of ordering.
For a MPC4
Mk2
module delivered as a spare part, the module’s IP address is normally
configured to used dynamic addressing (that is, DHCP).
See 2.2.3 MPC4
Mk2
module factory assigned defaults.
To Next Page
Loading...
Need help?
General