MVX

User Manual
 MVX
User Manual

Reference Document : DOC3021

Date : December 2015
Revision : F
Name : MVX User Manual

www.acoemgroup.com
Copyright ©

This document is the property of 01dB-Metravib. No part of this publication may be duplicated,
reprinted or transmitted by electronic, mechanical, photographic or other means, or recorded,
translated, edited, abridged or expanded without the prior written consent of the owner
 Table of contents
1 Introduction ....................................................................................................... 7
1.1 Hazardous areas .......................................................................................... 7
1.2 Installation .................................................................................................... 7
1.3 Version compatibility .................................................................................... 8
1.4 Hardware identification ................................................................................. 9
2 Evolutions ........................................................................................................ 10
2.1 Main evolutions of firmware version 5.4.0-7 ............................................... 10
2.2 Main evolutions of MVX version 5.1 ........................................................... 10
2.3 Main evolutions of MVX version 5.0 ........................................................... 10
2.3.1 Monitoring on 100% of the signal ........................................................ 10
2.3.2 “Time waves on event” signals recording ............................................ 13
2.3.3 DAT option performance optimisation ................................................. 14
2.3.4 BGI: for the monitoring of structures ................................................... 14
2.3.5 GCI: for particle counting..................................................................... 14
2.4 Main evolutions of MVX version 4 .............................................................. 15
2.4.1 New « Shock FinderTM » indicator (SFI) ............................................. 15
2.4.2 Increase of the efficiency..................................................................... 16
2.5 Main evolutions of MVX version 3.1 ........................................................... 16
2.5.1 Compatibility with the ESA analysis by ONEPROD-System ............... 16
2.5.2 Short-term memory ............................................................................. 16
2.5.3 OPC parameters via XCOM ................................................................ 17
2.5.4 Priority management ........................................................................... 17
2.5.5 Alarm triggering delay ......................................................................... 17
2.5.6 Vector tracking .................................................................................... 18
3 MVX Operating ................................................................................................. 19
3.1 Principle ..................................................................................................... 19
3.2 Operating conditions .................................................................................. 19
3.3 Operating in “Monitoring” mode .................................................................. 19
3.4 Operating in “Predictive Maintenance” mode ............................................. 20
4 Set-up ............................................................................................................... 21
4.1 Setup with OneProd CSM .......................................................................... 21
4.2 Set-up with ONEPROD XPR ...................................................................... 21
5 Indicator lights on the front panel.................................................................. 22
6 Connecting MVX on an Ethernet network ..................................................... 23
6.1 Ethernet port selection ............................................................................... 23
6.2 IP addressing mode ................................................................................... 24
6.2.1 Default address mode ......................................................................... 24
6.2.2 MVX dynamic address mode .............................................................. 25
6.2.3 MVX fixed address mode .................................................................... 25
6.3 How to check the Ethernet connection ....................................................... 26
6.4 Examples ................................................................................................... 27
6.4.1 Connecting one MVX with one PC in a point to point connection through
the MVX right port.............................................................................................. 27
6.4.2 Two MVX and two PC connected together as a “local network” .......... 28
6.5 MVX Web interface .................................................................................... 29
7 Using the MODBUS output interface ............................................................. 30
7.1 General points ............................................................................................ 30
7.2 Communication principles .......................................................................... 30
7.2.1 Serial MODBUS with RS485 connection ............................................. 30
7.2.2 MODBUS-TCP with Ethernet connection ............................................ 31
7.3 Data format................................................................................................. 31
7.3.1 Available indicators ............................................................................. 31
7.3.2 Modbus requests ................................................................................. 32
7.3.3 Number of indicators ........................................................................... 32
7.3.4 Values of indicators ............................................................................. 32
7.3.5 Status of indicators .............................................................................. 33
7.3.6 Units of indicators................................................................................ 34
7.3.7 Threshold values ................................................................................. 35
7.3.8 Values of operating parameters .......................................................... 37
8 Maintenance ..................................................................................................... 38
8.1 Preventive maintenance operations ........................................................... 38
8.2 Replacement of the battery ........................................................................ 38
8.3 1st level diagnosis ....................................................................................... 38
8.3.1 Normal boot sequence ........................................................................ 38
8.3.2 Regular working operations................................................................. 39
8.3.3 Bias voltage monitoring ....................................................................... 39
8.3.4 Offset compensation ........................................................................... 39
 8.3.5 Defects indicated by the MVX leds ...................................................... 39
8.3.6 Summary ............................................................................................. 41
8.4 MVX Hard Reset ........................................................................................ 42
8.5 MVX Firmware upgrade ............................................................................. 42
 7

1 Introduction

Thank you for purchasing the ONEPROD MVX monitoring and predictive
maintenance system.

This performing system allows for the monitoring of industrial machines using 8, 16,
24 or 32 measurement channels, depending on the selected model.

ONEPROD MVX can also act as a synchronous multichannel acquisition system

when connected to a predictive maintenance platform based on the ONEPROD
NEST ANALYST (XPR) software package.

ONEPROD MVX can be connected to many transducers, even though its prime
objective remains vibration measurement and analysis.

In case of a problem, please contact OneProd Hotline:

oneprod.support@acoemgroup.com

1.1 Hazardous areas

WARNING
REFER TO INSTALLATION MANUAL BEFORE ANY INSTALLATION IN A HAZARDOUS
AREA.
SEE DOC3012 2015-12 G or later.

1.2 Installation
See the dedicated manual for MVX Installation:
 DOC3012

Brand of ACOEM
 8

1.3 Version compatibility

The following combinations must be fulfilled in order to guarantee an optimal working.

MVX
Release date / MVX type CAST CSM VIO XPR
(firmware)

Until September 2007 1.0xx 1.01.xx 1.00x 1.00x 3.05

From October 2007 2.0xx 2.xx 2.xx 2.xx 4.xx

From October 2009 3.1.xx 3.1.xx 3.0.xx 2.0.x 4.1.x

From Novembre 2009 4.1.xx 3.2.x 3.0.xx 2.0.x 4.3.x

From January 2011

4.2.xx 3.4.3 3.0.xx 2.0.x 4.4.1
(restrained diffusion)

From June 2011 5.0x 3.4.9 5.0.xx 5.0.x 4.5.x

From June 2013
MVX1001000 type 5.1.0-1 3.5.3 5.0.4 5.0.4 4.6.0
MVX1002000 type

ONLY FOR :
5.1.0-2 3.5.4 5.0.4 5.0.4 4.6.5
MVX1027000

ONLY FOR :
MVX1027000A
MVX1027000B 5.4.0-7 3.7.3 - - 4.6.7
MVX1029000
MVX1031000

Brand of ACOEM
 9

1.4 Hardware identification

Year after year, MVX Hardware supported some changes.
The hardware version of each MVX is available on the side label that is pasted on the
left side, just near the fan entry.
The following table gives the technical differences between the hardware versions:

Compatibility
Maximum
Original operating
Type number of ATEX Zone 2 RAM
system
channels
(or Cl.1-Div2)
(2) (1)
MVX1001000 16 NO 256 Mo WinCE
(2) (1)
MVX1002000 32 NO 256 Mo WinCE
(2) (1)
MVX1001000A 16 YES 256 Mo WinCE
(2) (1)
MVX1002000A 32 YES 256 Mo WinCE

MVX1001000B 16 YES 512 Mo Linux

MVX1002000B 32 YES 512 Mo Linux

MVX1001000C 16 YES 512 Mo Linux

MVX1002000C 32 YES 512 Mo Linux

MVX1001000D 16 YES 512 Mo Linux

MVX1002000D 32 YES 512 Mo Linux

MVX1001000E 16 YES 512 Mo Linux

MVX1002000E 32 YES 512 Mo Linux

MVX1027000
MVX1027000A 16 NO 1 Go Linux
MVX1027000B
MVX1029000 32 NO 1 Go Linux

MVX1031000 16 YES 1 Go Linux

(1)
: Upgrade of WinCE is not supported anymore.
(2)
: Upgrading RAM is NOT possible

Brand of ACOEM
 10

2 Evolutions

2.1 Main evolutions of firmware version 5.4.0-7

WARNING : This firmware version is ONLY for MVX 1027000A, MVX1027000B,
MVX1029000 and MVX1031000.
 Firmware update through the MVX Web interface (not CAST anymore).
 Operating conditions management: only 1 operating condition can be valid at a
time. If more than 1 operating condition is valid, MVX takes the first valid
condition of the list (list from XPR operating condition pannel)
 Improved definition of operating condition limits :
o Low limit included(≥), high limit exclude (>)
 Operating conditions can be available by OPC or by Modbus, not both at the
same time.
 Possibility to disable automatic reset in case of bad configuration in remote
locations

2.2 Main evolutions of MVX version 5.1

 Modbus Digital Inputs: Refer XPR software user manual to see the
implementation of this feature. This mode cannot be used with CSM
 The operating parameters are available through MVX Modbus output: cf. §
7.3.8
 New management Ethernet ports: cf. § 6

2.3 Main evolutions of MVX version 5.0

2.3.1 Monitoring on 100% of the signal
This new functionality is available only on Premium MVX version
From V5.0.xx version MVX Premium is able to compute in real time a selection of
indicators. The aim of such a function consists in ensuring that 100% of the signal is
actually monitored.

Brand of ACOEM
 11

Illustration:
 “Standard” indicators are achieved at each cycle by MVX.
Thus, a very short phenomenon can be ignored if it happens during a processing
phase.

Acquisition Processing Acquisition Processing Acquisition Processing

t
1 cycle

 RT indicators (Real Time) are achieved permanently during acquisition

Thus, 100% of the signal is actually monitored.

Acq. 1 Acq. 2 Acq. 3 Acq. 4 Acq. 5 Acq. 6

t
Proc. 1 Proc. 2 Proc. 3 Proc. 4 Proc. 5 Proc. 6

Thus the smallest transient phenomena can be detected (even if it happens only
once and if it lasts some milliseconds), according adapted parameters (i.e. pick
detection).
Besides it is obVIOusly possible to choose another set of parameters, which erases
transient phenomena in order to avoid false alerts (i.e. RMS detection with several
seconds time constant).
As a complement to such real time monitoring, MVX can record a new “Time waves
on event” signal category (Please see next §).
The following processing parameters can be applied to define real time indicators
which are monitored on 100% of the signals.
 High pass filter : 2Hz or 10Hz
 Signal integration : 0 or 1
 Low pass filter : 1000Hz or no filter (i.e.20kHz)
 Processing : RMS, pk or pk-pk
 Averaging : continuous exponential with time constant between 1s and 25s
 Averaged DC level (for process and GAP signals)
 BGI indicator (Blade Guard Index)
 GCI indicator (Gearbox Condition Index, see next §)
 Broad band and narrow band extraction on real time FFT :
o FFT 400 pts, 800 pts, 1600 pts ou 3200 pts
o FFT 1kHz, 2kHz, 5kHz, 10kHz ou 20kHz,
o FFT with 50% fixed overlapping

Brand of ACOEM
 12

Real time indicators are achieved in the limit of the available MVX processing
capability.
An automatic control of the parameters embeds a checking of MVX processing load
and cautions the operator when launching if overload is predictable.

Brand of ACOEM
 13

2.3.2 “Time waves on event” signals recording

MVX Premium with DAT option is required
Besides real time monitoring MVX can record specific time waves that can be trigged
at all time and that includes « pre-trigger » capability. I.e. possibility to include what
happened BEFORE the trigger event.

Event

Alarm threshold
Real Time Parameter
t
Time wave on event Pre-trigger
Total time wave duration

 Possible trigger events:

o Real time indicator alarm level VIOlation,
o Change in the operating condition,
o Manual measurement request (from XPR)
 Time wave on event parameters:
o Fixed sampling rate: 51.2 kHz.
o Length: 1s to 30s on 32 channels
o Maximum length can be overstepped if less than 32 channels have
to be recorded at the same time:

Number of channels concerned by time wave on event 32 24 16 8 4 3 2 1

Maximum duration (s) 30 40 60 120 240 320 480 480

 Pre-trigger duration: 0 to total wave length (*).

(*) For first generation MVX which have been updated with V5.xx, the following
limitations (due to internal RAM) are to be considered:
To know if your product is affected please have a look on §12

Brand of ACOEM
 14

Complementary limitations, only for 1st generation MVX

Number of channels with Time wave on event 32 24 16 8 4 3 2 1

Maximal duration (in s) with pre-trigger = 0 30 40 60 120 240 320 480 480

Maximal duration (in s) with pre-trigger = full length 9 13 19 39 78 117 156 156

Note: Internal RAM cannot be upgraded.

2.3.3 DAT option performance optimisation

Firmware version 5.0.x.x improves substantially DAT performance in optimizing RAM
management in two directions:
Limiting RAM consumption for a given configuration
Involving the additional RAM that is available on the last generation products (Please
see §12)

2.3.4 BGI: for the monitoring of structures

BGI = Blade Guard Index.
BGI is a specific indicator, dedicated to monitor structural resonance phenomena. It
can be particularly suitable for wind turbine blades when associated to specific
sensors.
BGI requires DAT option in order to get time wave on alarm signal.

2.3.5 GCI: for particle counting

GCI (Gearbox Condition Index) is dedicated to particles counting.
GCI is available with MVX Easy or Premium.
Particle sensor (i.e. GASTOPS / MetalSCAN) are especially useful for degradations
of the wind turbine gearboxes.
GCI is performed on 100% of time.
GCI is made with 3 sub-indicators:
 GCI-h : number of particle detected in the last hour
 GCI-d : number of particle detected in the last 24 hours (performed in a
slipping mode)
 GCI-t : Total number of detected particle
Each sub-indicator is monitored with its own set of thresholds.

Brand of ACOEM
 15

2.4 Main evolutions of MVX version 4

In addition to the new functions described in the preVIOus chapter, Version #4.1 of
the MVX firmware includes the following evolutions:

2.4.1 New « Shock FinderTM » indicator (SFI)

This new indicator is able to detect abnormal shocks<;

It is especially suitable for low speed machineries, where standard indicators (i.e.
filtered RMS vlalues) are not always completely pertinent

Thus Shock FinderTM is suitable for windturbine rotor monitoring, steelmill or

papermill monitoring, etc.

It can be used for rolling element bearings as well as gearbox monitoring.

Shock FinderTM also incorporates a smooth function dedicated for decreasing false
alarm risk.

Please consult XPR300 V4.3 user manual (chapter 14.8) for more details about SFI
set up.

Shock FinderTM can be setup with ONEPROD NEST ANALYST (XPR)

Shock FinderTM can’t be setup with OneProd CSM

Brand of ACOEM
 16

2.4.2 Increase of the efficiency

MVX firmware V4.1 is based on a new operating system. Consequently MVX

efficiency is increased.

The main observable improvement concerns the processing times that are lower vs
preVIOus firmware versions.

Consequently a decrease of the cycle time is observed, allowing an improvement of

the monitoring rate.

2.5 Main evolutions of MVX version 3.1

Version 3.1xxx of the MVX firmware includes mainly the following new functions:

2.5.1 Compatibility with the ESA analysis by ONEPROD-

System

MVX is now compatible with the electric signal analysis (ESA) functions available in
ONEPROD NEST ANALYST (XPR).

The analysis of electric signals consists in acquiring and analysing the power supply
voltages and currents of a motor and detecting the distinctive characteristics thereof
that indicate anomalies.
Electric or mechanical anomalies on the motor can thus be evidenced (unbalance,
misalignment, broken bar, etc.).

2.5.2 Short-term memory

MVX stored in a FIFO buffer all or part of the indicators that were worked out during
the monitoring measurements.

MVX can store up to 1000 values for each indicator, with a periodicity ranging from a
few seconds (*) to 600 seconds.

This new function is available from ONEPROD NEST ANALYST (XPR) only.

Brand of ACOEM
 17

(*): for a given application, the periodicity cannot be shorter than that for the
calculation of the indicators by MVX.

Example:
When an indicator goes into alarm mode, one can know whether this indicator
increased suddenly or progressively before reaching the alarm threshold.

2.5.3 OPC parameters via XCOM

When MVX is connected to XCOM (communication engine of ONEPROD NEST

ANALYST (XPR)), it can now:
 Monitor original OPC parameters (*)
 Use original OPC parameters (*), such as condition parameters

(*): MVX does not have a local OPC connection. Parameters called “original OPC
parameters” are retrieved by the OPC client of the XCOM component, which is
physically located on the same PC as ONEPROD NEST ANALYST (XPR)

2.5.4 Priority management

MVX can now take into account three possible priority levels for each task.

This function allows for a better monitoring of machines with complex or random
operating conditions.

2.5.5 Alarm triggering delay

The purpose of this function is to avoid untimely alarms due to interference or

transient phenomena (e.g., related to the start of a neighbouring machine). It consists
in, on request, acknowledging an alarm status ONLY if it is confirmed during a given
period.

This function is accessible only from ONEPROD NEST ANALYST (XPR). A

triggering delay is defined in seconds. If it is shorter than the cycling time, MVX
performs at least one confirmation measurement.

Brand of ACOEM
 18

MVX keeps it operating cycle and must confirm the presence of the alarm on all
measurements collected over the defined time.

If the alarm level remains present during the defined time, MVX triggers the alarm
status: relay, MODBUS status, acquisition on status change. If the level disappears,
the alarm is no longer effective.

2.5.6 Vector tracking

MVX can now, and on request from ONEPROD NEST ANALYST (XPR), calculate
phased spectra.
The phase reference that is taken into account is that of the trigger input
corresponding to the machine under study.

Brand of ACOEM
 19

3 MVX Operating

3.1 Principle
Unlike most predictive maintenance system on the market, ONEPROD MVX
performs sequences of simultaneous acquisitions on all measurement channels.

These acquisitions are really synchronous and in phase.

3.2 Operating conditions

Signal acquisitions can be performed (depending on the configuration) under specific
operating conditions for the machine(s) under monitoring.

These operating conditions can be:

 A rotation speed, acquired by MVX through a “trigger input”-type frequency

signal connected to one of the analogue inputs.
 Values of one or two process parameters (power, temperature, etc.) acquired
by MVX one of the analogue inputs through a continuous voltage or 4-20 mA
current signal.
 Up two 3 logical data (TTL signal) acquired by MVX on its logical inputs.

3.3 Operating in “Monitoring” mode

When MVX is set up to perform monitoring operations, the processing of data
acquired simultaneously aims at calculating indicators and comparing them to alarm
thresholds.

This calculation is performed:

 During acquisition for the real time indicators (MVX Premium only)
 After each acquisition phase for the standard indicators.

Thus, MVX alternates acquisition and processing phases and a set of updated
“results” indicators is available after each processing phase.

Brand of ACOEM
 20

Spectra calculated for the extraction of indicators can neither be viewed nor stored by
MVX.

3.4 Operating in “Predictive Maintenance” mode

When MVX is set up to perform predictive maintenance tasks, it performs the

required acquisition(s) as soon as the fixed period or date has expired.

In this case, all signals (spectra and/or time signals) and indicators described in the
configuration are stored by MVX in order to be integrated into the predictive
maintenance database, either at once, or later on.

Between two scheduled operations, MVX can permanently calculate scalar indicators
described in the settings and compare them to alarm thresholds, like in the
monitoring mode.
In case of status change (threshold VIOlation), all measurements (spectra and/or
time signals) and indicators described in the parameter settings are stored by MVX to
be later integrated to the predictive maintenance database.

Short-term memory:
Furthermore, and for each calculated parameter, MVX will store in a FIFO buffer the
short-term history of scalar values.

The size of this FIFO buffer can be set up to 1000 values per indicators.

The periodicity for storage in the short term memory can also be programmed and
can range from a few seconds (i.e., MVX stores all calculated values) to 600 s.

By storing 1000 values with a periodicity of 600s, the capacity of this short-term
memory can thus reach 600 000s, i.e., about 1 week.

Brand of ACOEM
 21

4 Set-up

When only monitoring tasks (to the exclusion of any predictive maintenance tasks)
are to be assigned to MVX, the OneProd CSM set-up interface should be used.
This interface is used to set up MVX; it does not allow for visual display or processing
of measurement results.
To assign predictive maintenance tasks to MVX, one should use MVX jointly with the
ONEPROD NEST ANALYST (XPR) predictive maintenance software program.
This platform will perform the set up of MVX, as well as the processing of
measurement results.
In both cases, the communication between MVX and the computer hosting OneProd
CSM or ONEPROD NEST ANALYST (XPR) used an Ethernet connection: existing
network or point-to-point connection.

4.1 Setup with OneProd CSM

While remaining a user-friendly interface, CSM can be used to set up simple, as well
as more specific, monitoring tasks.
The use of ONEPROD CSM is described in detail in a dedicated user manual.
Note:
CSM isn’t suitable to setup real time indicators
CSM isn’t suitable to setup SFI indicator (Shock FinderTM).
CSM isn’t suitable to setup GCI indicator (Gearbox Condition IndexTM)
CSM isn’t suitable to setup time wave signals

4.2 Set-up with ONEPROD XPR

XPR is a global, multi-technique, performing predictive maintenance software
package.
In particular, it allows for the management of production assets under both “off-line”
and “on-line” monitoring.
There is a separate user manual devoted to ONEPROD NEST ANALYST (XPR).

CAUTION
Although set-up structures are compatible, we strongly recommend that the use of
XPR and CSM never be combined to set up a MVX module.

Brand of ACOEM
 22

5 Indicator lights on the front panel

There are 10 indicator lights on the front panel of MVX.

Power:
Valid
supply voltage

Danger:
At least one channel with
violation of a danger
threshold

Alarm:
At least one channel with
violation of an alarm
threshold

Sensor:
Measurement problem
on a least one channel
(sensor, cable, etc.)

System:
Detection of an
internal system
defect

485 in
Signal being
received
on line RS-485
485 out
Signal being
emitted
On lige RS-485
A
Acquisition in progress (*)

B
Processing in progress (*)

C
Communication in progress (*)

Brand of ACOEM
 23

(*) Lights A, B and C:

These indicator lights may switch function in case of system defect (see Maintenance
Chapter).

6 Connecting MVX on an Ethernet network

6.1 Ethernet port selection

There are two RJ45 type Ethernet sockets on MVX: A & B.
They are located on the bottom of the MVX case.
Connecting MVX to an Ethernet network is possible using A or B socket.
Only one socket can be used at a time.

 These two connectors may be used but their pin assignment are not identical:

Addressing mode led: fixed or dynamic addressing mode netwok led indicators

2 USB ports (not used)

Ethernet A port Ethernet B port

 Port A (or « left »port): standard (non crossed, same as a PC):

In order to connect MVX to a factory network through A port, you have to use a
standard (uncrossed) cable.
In order to connect MVX to a PC through A port, you have to use a crossed
cable and to setup beforehand MVX in Fixed IP address mode.

 Port B (or "right" port): crossed.

In order to connect MVX to a factory network through B port, you have to use a
crossed cable.
In order to connect MVX to a PC through B port, you have to use a standard
cable.

Brand of ACOEM
 24

Please note that some recent Ethernet switch and portable PC automatically cross or
uncross their port.
IMPORTANT - Rules for the use of Ethernet ports:
 It is recommended to use preferably the port B. This port can handle the
communication with the software OneProd (XPR, CAST, MSC, VIO) and PLC
via Modbus TCP.
 If the Modbus devices are on a different network then connect them on port A

When the connection is OK, a green indicator lights on the RJ45 socket (high & right
corner, see on the upper scheme)

 You have to reboot the MVX after any change on the network connection

After connecting MVX to an Ethernet network:

- Startup MVX
- Please verify that the light is green on the RJ45 socket. If this indicator
remains off, the network is off or the cable isn’t appropriate.

6.2 IP addressing mode

6.2.1 Default address mode

As default, the two MVX Ethernet ports are « Dynamic IP » configured:

When starting, MVX looks for a DHCP server on the network in order to get an IP
address.
 If a DHCP server is present on the network (dynamic IP addresses network),
MVX IP address isn’t known, and the serial number of the MVX is used as
the « hostname ».
 If no DHCP server is present on the network, then MVX chooses an IP free
address in the range 169.254.x.y on its B port, right side. In this case use
also MVX serial number as « hostname » to address it.

This addressing mode can be restored using the Reset button: cf. § 8.4

Warning : from V4.1.x .x MVX firmware, A port doesn’t focus automatically to a

default fixed IP address. You shall use B port or you shall setup A port in fied
IP address mode with CAST

Brand of ACOEM
 25

6.2.2 MVX dynamic address mode

This is the simplest case: MVX IP address is arbitrary because chosen by the DHCP
server.
MVX user does not use this IP address.
He names each MVX with its “Hostname”, which is in fact its serial number.
When MVX is running with an Ethernet port programmed in dynamic address mode,
the led in the high & left corner of the RJ45 socket is light on in GREEN.

6.2.3 MVX fixed address mode

Reminder: When MVX is set up in dynamic addressing mode and when no DHCP
server exists at the same time on the network, then MVX chooses an IP free address
in the range 169.254.x.y on its B port, right side. In this case use also MVX serial
number as « hostname » to address it.
In order to connect several MVX on a fixed IP addresses network, you have
beforehand:
 To define the MVX list with the serial number and the IP address of each.
 To connect each MVX with a PC in a « point to point » network, in order to
assign its fix address.
This operation may be achieved with CAST toolbox which is delivered together with
MVX.
 Start CAST toolbox in the “expert” mode (password needed)
 Enter the MVX serial number or its “old” IP address
 Click on the “connect to MVX” button
 Choose the “configuration” page
 In the “Set fixed IP address” area:
o choose the MVX port that you want to use: A port (left), or B port (right)
o Enter the new IP address
o Enter the subnet mask
o Enter the default gateway
o Click on "configure"
 This may cause MVX re-boot.
When MVX is running with an Ethernet port programmed in fixed address mode, the
led in the high & left corner of the RJ45 socket is light on in RED.

Brand of ACOEM
 26

6.3 How to check the Ethernet connection

The network “connection status” should indicate “connected”.
With Windows XP, the connection status is available through:

 A double-click on the icon into the “task bar”

 Or in the “network connections” item of the “control panel”.
The “ping” command may be used in order to check the MVX response time.
 Click on Start - Run
 Type cmd and click on OK : A DOS window is open
 Type ping [MVX IP address] or ping [MVX serial number]
Example:

C:\>ping 192.168.103.240

Pinging 192.168.103.240 with 32 bytes of data:

Reply from 192.168.103.240 : bytes=32 time<1ms TTL=128

Reply from 192.168.103.240 : bytes=32 time<1ms TTL=128
Reply from 192.168.103.240 : bytes=32 time<1ms TTL=128
Reply from 192.168.103.240 : bytes=32 time<1ms TTL=128

Ping statistics for 192.168.103.240 :

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Brand of ACOEM
 27

6.4 Examples
6.4.1 Connecting one MVX with one PC in a point to point
connection through the MVX right port
MVX: dynamic IP mode
Default address: serial number
used as “Hostname”
(IP = 169.254.x.y)

Standard
MVX : B Straight cable
Ethernet port

PC, dynamic IP
mode

In this example the PC and the MVX may be let in the dynamic IP address mode.

Brand of ACOEM
 28

6.4.2 Two MVX and two PC connected together as a “local

network”

MVX1: Fixed IP
192.168.103.240 MVX2: Fixed IP
192.168.103.241

Standard straight cables

each on MVX A port

SWITCH

PC2: Fixed IP
192.168.103.101
PC1: Fixed IP
192.168.103.100

Brand of ACOEM
 29

 Each PC must be setup with a fixed IP address:

192.168.103.100 & 192.168.103.101.

 Each MVX must be setup with a fixed IP address using CAST:

192.168.103.240 & 192.168.103.241.

6.5 MVX Web interface

The web interface allows to
Look at MVX information, Modbus configuration, log files, date and time information,
configuration files and also allows to update the firmware.
To connect, use a web browser by entering the following address :

https://serialnumberofmymvx
it is important to use https
(exemple : https://lcf042563-322/)

Do not care about security message from your web browser.

Login : usermvx
Password : MVX

Brand of ACOEM
 30

7 Using the MODBUS output interface

7.1 General points

Whether it runs with XPR, with VIO or in stand-alone mode, MVX computes and
updates as often as possible a number of scalar levels (called “overall levels” or
“indicators”).

All these levels can be consulted using the dialogue function in MODBUS format.

The status of these indicators (OK, Alarm, etc.) is also available, along with their unit.

In any event, MVX is a MODBUS slave that answers requests issued by a Master.
This Master is usually a programmable automaton, a centralized management
system or a monitoring system.

7.2 Communication principles

Data in MODBUS format can be accessed:
 Either using the RS485 connection on MVX: “Serial MODBUS”
 Or using the Ethernet connection of MVX: “MODBUS-TCP”

7.2.1 Serial MODBUS with RS485 connection

The RS485 standard allows for the creation of a local network made up of a twisted
and shielded pair onto which up to 32 instruments can be connected.

In practice, one needs to connect one or several MVX instruments to a single

“master” instrument.

We recommend reading Chapter 3.9 of MVX installation manual P153.NUT.576

before achieving the physical connection of instruments.

It is possible to adjust RS485 configuration (baud rate, parity …) with CAST software.

Each MVX is assigned a MODBUS slave number ranging from 1 to 32. The
MODBUS slave address of each MVX is set from the ONEPROD NEST ANALYST
(XPR) software or from the OneProd CSM software.

Brand of ACOEM
 31

7.2.2 MODBUS-TCP with Ethernet connection

MODBUS data are available through a MODBUS TCP protocol, which is constantly
active over the network.

IMPORTANT - Rules for the use of Ethernet ports:

 It is recommended to use preferably the port B. This port can handle the
communication with the software OneProd (XPR, CAST, MSC, VIO) and PLC
via Modbus TCP.
 If the Modbus devices are on a different network then connect them on port A

Conventions:
 Data in MODBUS-TCP format are available through the standard 502 port.
 The MODBUS slave address must be set to 255 in requests (in this case, the
IP address is used to select each MVX).

CAUTION
The slave address had to be fixed at 1 (instead of 255) in the previous versions of
MVX.
This change can result in malfunction after upgrading MVX firmware to V5.0
Adress #255 allows for a better compatibility vs MODBUS-TCP standard..

7.3 Data format

The MODBUS interface is used to read values, statuses, units and thresholds of
indicators computed by MVX.

7.3.1 Available indicators

Using software programs XPR or CSM, one can program up to 255 different
indicators in MVX.

Each indicator is assigned a number (ranging from 1 to 255), which is part of the
indicator’s parameters and is entered upon programming.
For more details, refer to the user manuals of XPR or CSM.

It is to be noted that MVX channels do not correspond to the indicator numbers. As

an example, a single channel can result in the computation of about 10 different
indicators, whereas another channel, which remains unused, will not issue any
indicator and will therefore no longer exist in the MODBUS dialogue.

Brand of ACOEM
 32

7.3.2 Modbus requests

The MVX answers the function with code 03: Read Holding Registers.
Available data are described in the paragraphs below.

7.3.3 Number of indicators

The number of indicators programmed in MVX is available at address “zero”.

7.3.4 Values of indicators

Data are in IEEE floating format over 32 bits.
Two consecutive addresses are then required for each indicator value.

At address 1000 (& 1001), π (PI) value “3.1416” is displayed permanently, which
allows to check the proper operating of the connection.

Indicator values are available in an address range from 1002 to 1513 and sorted
according to the table below:

MODBUS memory address Content

1000
3.1416, set value
1001
1002
Value of indicator #1
1003
1004
Value of indicator #2
1005
...
....
...
1512
Value of indicator #256
1513

Brand of ACOEM
 33

7.3.5 Status of indicators

The logical status of each indicator can take 4 different values:

Value of logical status Description of indicator status

0 Normal (OK)
1 Alarm
2 Danger
Defect (transducer or other defect making measurement
3
impossible)

At address 2000, one can read hexadecimal 5555 value permanently, which allows
checking the proper operating of the transfer connection.
Logical statuses of indicators are available in an address range from 2000 to 2256
and sorted according to the table below:
MODBUS memory address Content

2000 Hexadecimal 5555, set value

2001 Logical status of indicator #1
2002 Logical status of indicator #2
… ..
… ..
2256 Logical status of indicator #256

Brand of ACOEM
 34

7.3.6 Units of indicators

Indicator units are coded as follows:
Value Unit
1 g
2 m / s²
3 inch / s
4 mm / s
5 mils
6 micrometer
7 def
8 Hz
9 rpm
10 bar
11 psi
3
12 m /s
13 L/s
14 kg / s
15 °C
16 °F
17 Pa
18 %
19 dBA
20 K
21 V
22 A
23 mA
24 W

At address 3000, one can read hexadecimal value AAAA permanently, which allows
checking the proper operating of the transfer connection.
Indicator units are available in the address range from 3000 to 3256, and sorted
according to the table below:
MODBUS memory address Content

3000 Hexadecimal AAAA, set value

3001 Logical status of indicator #1
3002 Logical status of indicator #2
… ..
… ..
3256 Logical status of indicator #256

Brand of ACOEM
 35

7.3.7 Threshold values

Alarm and Danger threshold values are available provided that the corresponding
indicators are achieved in one operating condition only.

In other words, this function is not suitable when indicators are calculated in several
operating conditions and monitored with different sets of thresholds,.

As well as indicators, data are stored in IEEE floating format over 32 bits.
Two consecutive addresses are then required for each indicator value.

There are 4 thresholds for each indicator, even if all of them are not used in all cases.

At address 4000 (& 4001), π (PI) value “3.1416” is displayed permanently, which
allows to check the proper operating of the connection.

Indicator threshold values are available in an address range from 4008 to 6055 and
sorted according to the table below:

Brand of ACOEM
 36

MODBUS memory address Content

4000
3.1416 (set value)
4001
4002
Not used
4003
4004
Not used
4005
4006
Not used
4007
4008
Value of threshold #1 of indicator #1
4009
4010
Value of threshold #2 of indicator #1
4011
4012
Value of threshold #3 of indicator #1
4013
4014
Value of threshold #4 of indicator #1
4015
4016
Value of threshold #1 of indicator #2
4017
4018
Value of threshold #2 of indicator #2
4019
4020
Value of threshold #3 of indicator #2
4021
4022
Value of threshold #4 of indicator #2
4023
4024
Value of threshold #1 of indicator #3
4025
...
....
...
6054
Value of threshold #4 of indicator #256
6055

Brand of ACOEM
 37

7.3.8 Values of operating parameters

Since version V5.1, operating parameters are also accessible via Modbus output
inteface
As well as indicators, data are stored in IEEE floating format over 32 bits.
Two consecutive addresses are then required for each indicator value.
Values are stored from address 7000 equipment by equipment in the following ordrer:
1. Rot speed Address : 7000
2. DC1 Address : 7002
3. DC2 Address : 7004
4. TOR1 Address : 7006
5. TOR2 Address : 7008
6. TOR3 Address : 7010
If several machines are connected to MVX, the second is at the following address
(7012) and so on. The order can be checked in the file produced by the "Export
Excel" function of the MVX
Adresse mémoire MODBUS Contenu

7000
Vit Rot Equipement 1
7001
7002
DC1 Equipement 1
7003
7004
DC2 Equipement 1
7005
7006
TOR1 Equipement 1
7007
7008
TOR2 Equipement 1
7009
7010
TOR3 Equipement 1
7011
7012
Vit Rot Equipement 2
7013
7014
DC1 Equipement 2
7015
…
…

Brand of ACOEM
 38

8 Maintenance

8.1 Preventive maintenance operations

The MVX system does not require any specific operation for its maintenance, except
for dust cleaning on the ventilation inlets.

To do so, disconnect MVX from the power supply.

In case of a particularly dusty atmosphere, it can be useful to get rid of the dust
accumulated inside MVX.

To do so, please contact 01dB-Metravib’s after-sales department.

8.2 Replacement of the battery

The theoretical lifetime of the data back-up battery is several dozen years for a MVX
module under constant voltage.

Replacing this battery may however be necessary every 10 years.

Also, we recommend that the battery be replaced as soon as the MVX module has
remained totally unused for more than a year.

To replace the back-up battery, please contact the 01dB-Metravib’s support.

(see page 2).

8.3 1st level diagnosis

8.3.1 Normal boot sequence
If To is the Power-on instant, the normal boot sequence is:

 To: The “power” green led lights. All the other leds are “ON” too.

Brand of ACOEM
 39

 ~To + 60 seconds: Red leds are flashing on the two RJ45 Ethernet
connectors.
 ~To +70 seconds: All the leds are flashing. Then A & B leds are staying lighted
for a moment.
 ~To + 100 seconds: Integrity relay becomes energised; A & B leds become
OFF: the MVX is ready to work.

8.3.2 Regular working operations

When MVX is normally working, A, B and C leds are flashing:
 A Led: lights during signal acquisition
 B Led: lights during post-processing operations
 C Led: fleetingly lights during each network access

8.3.3 Bias voltage monitoring

When bias voltage monitoring is activated, MVX inserts periodically a specific
sequence for that goal.

During this sequence, A Led flashes quickly 6 times.

8.3.4 Offset compensation

When a new configuration is transferred to MVX, it does not start immediately with its
nominal operating mode, as described in the previous two paragraphs.

MVX goes into an initialisation phase, during which the two LEDs A and B blink
quickly and simultaneously.

This phase usually lasts about 15 seconds.

However, if instrument property “Offset adjustment” is activated in XPR, this
initialisation phase may last several minutes.

8.3.5 Defects indicated by the MVX leds

8.3.5.1 All the leds are ON

If all the MVX leds are staying ON during more than 2 minutes after powering, it
means that an internal electronic failure exists.
In this case please contact the 01dB-Metravib’s Hot-line (see page 2).

Brand of ACOEM
 40

8.3.5.2 The “SYSTEM” led flashes quickly (3 times per second)

MVX could not start because of a general acquisition defect.
MVX is not able to work. Its integrity relay is not activated.
In this case please contact the 01dB-Metravib’s Hot-line (see page 2).

8.3.5.3 The “SYSTEM” led flashes slowly (once each 3 seconds)

A partial defect has been detected. Examples:
 One acquisition channel is defective.
 Acquisition memory is full because MVX work exceeds its possibilities.
 An acquisition operation has been delayed because more than 32 channels were
to be acquired simultaneously.
 The Compact-Flash memory is full because communication with XPR is defective.

In each case it is possible to know the defect details using the “Read MVX states”
button of the CAST Toolbox.

8.3.5.4 The SENSOR led flashes slowly (Once each 3 seconds)

There are 3 possibilities:
 One IEPE sensor (or more) has been detected defective,
 One channel (or more) has been detected as overloaded,
 The current in one of the “4-to-20mA” input is less than 3.5 mA, or more than
20.5 mA.

In all these cases the integrity relay is not energised

As well as before it’s possible to know the defect details using the “Read MVX status”
button of the CAST Toolbox.

Brand of ACOEM
 41

8.3.6 Summary
In case of a problem, MVX LEDs allow performing a first-level diagnosis, which
makes troubleshooting easier.

Status of indicator lights

Status of integrity
Power Sensor System A B C MVX status
relay

Start-up in progress (operating

yes no no yes yes no Disabled
soon)

Stopped or waiting for

yes no no no no no Active
conditions

Alternating, depending on the

yes no no Normal operation Active
current stage (as below)

yes * * yes no No Acquisition in progress *

yes * * no yes no Processing in progress *

yes * * no no yes Transmission in progress *

yes Flashes no Channel overload Active

One sensor or cable is

Blinks
yes no defective or 4-20 mA signal is Disabled
slowly
off-range

Blinks Storage memory is full in FIFO

yes no Active
slowly mode

Blinks Internal defect on

yes no Disabled
slowly measurement chain

Blinks Storage memory is full &

yes no
slowly measurement stopped Disabled

Blinks Temporary storage memory is

yes no Disabled
slowly saturated

Blinks Acquisition limit is exceeded

yes no Disabled
slowly (set-up problem)

Blinks
yes no General analogue defect Disabled
quickly

no no no No voltage or incorrect voltage Disabled

Start-up in progress (non

All 10 lights are on Disabled
operating)

Start-up in progress (operating

The 10 lights form a track Disabled
soon)

* : Depending on default status

Brand of ACOEM
 42

8.4 MVX Hard Reset

It is possible to make a Hard Reset of MVX, the reset has the effect:
 Restore dynamic addressing mode of the Ethernet ports
 Restore the HTTPS port to 403.
This reset is done by maintaining the reset push button pressed for 3 seconds with a
thin screwdriver (diameter <2 mm)
After reset the MVX restarts with its original settings.

Reset :
Push button

8.5 MVX Firmware upgrade

WARNING : only for MVX in version 5.4.0-7 or higher
Use the web interface to perform the firmware upgrade.
To connect, use a web browser by entering the following address :
https://serialnumberofmymvx
it is important to use https (exemple : https://lcf042563-322/)
Do not care about security message from your web browser.
Login : usermvx
Password : MVX

Go to Update tab
Browse for a .firm file
Upgrade the MVX

Brand of ACOEM
 43

200 chemin des Ormeaux

69578 LIMONEST – FRANCE
Tel.: +33 (0)4 72 52 48 00

www.acoemgroup.com

Asia
Tel. +66 (2) 7112 293 – Fax +66 (2) 7112 293
Brand of ACOEM

South America