TITLE PAGE

Instruction Manual

VM600 Networking

Vibro-Meter SA
Route de Moncor 4
CH - 1701 Fribourg
SWITZERLAND
www.vibro-meter.com

VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 REVISION RECORD SHEET

Date Written by / PM
Edition Description Signature
of Issue Modified by No.

1 07.10.03 R. Meyer --- Original edition

2 31.03.06 N. Parker --- Update to reflect new corporate identity

Department Name Date Signature

HR
Development H. Reiss
Technical content of original
issue approved by SA
Product Management S. Adamo

RA
Document released by Technical Publications R. Arnaud

The duly signed master copy of this page is stored by the Technical Publications Department of
Vibro-Meter S.A. and can be obtained by writing to the Technical Publications Manager.

ii VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 COPYRIGHT

IMPORTANT NOTICE

All statements, technical information, and recommendations in this document which relate to the products supplied
by Vibro-Meter SA are based on information believed to be reliable, but unless otherwise expressly agreed in writing
with Vibro-Meter the accuracy or completeness of such data is not guaranteed. Before using this product, you must
evaluate it and determine if it is suitable for your intended application. Unless otherwise expressly agreed in writing
with Vibro-Meter, you assume all risks and liability associated with such use. Vibro-Meter takes no responsibility for
any statements related to the product which are not contained in a current English language Vibro-Meter
publication, nor for any statements contained in extracts, summaries, translations or any other documents not
authored and produced by Vibro-Meter.

COPYRIGHT

Copyright © Vibro-Meter SA, 2007

All rights reserved

Published and printed by Vibro-Meter SA in Fribourg, Switzerland

The names of actual companies and products mentioned

herein may be the trademarks of their respective owners.

The information contained in this document is subject to change without notice.

This information shall not be used, duplicated or disclosed, in whole or in part,
without the express written permission of Vibro-Meter.

VM600 Networking Instruction Manual MAVM600-NET/E iii

Edition 2 - Mar 31/06
 THIS PAGE INTENTIONALLY LEFT BLANK

iv VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 TABLE OF CONTENTS

TITLE PAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

REVISION RECORD SHEET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii

COPYRIGHT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

1 NETWORKING INTRODUCTION AND OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 Communication Possibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.2 Some Networking Terms and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.2.1 Network Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.2.2 Connectivity Within Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.2.3 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.2.4 Network Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
1.2.5 IP Addressing (TCP/IP Protocol) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

2 VT100 TERMINAL SESSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.2 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2.1 If a VT100 Terminal is Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2.2 Emulating a VT100 terminal from Windows (HyperTerminal) . . . . . . . . . . 2-1
2.3 Changing the IP Address of the Rack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.4 Activating a Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
2.4.1 When is a Gateway Necessary? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
2.4.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.5 Editing Modbus Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.5.1 Opening the Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.5.2 Changing the Modbus Address of the Rack . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.5.3 Changing the Modbus Communications Parameters (Device Definition). 2-12
2.6 Using the vi Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

VM600 Networking Instruction Manual MAVM600-NET/E v

Edition 2 - Mar 31/06
3 SETTING UP AN ETHERNET CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.4 Using VM600 Software with an Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.4.1 Using MPS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.4.2 Using CMS Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

4 SETTING UP A PPP CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1.1 IP Address Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Installing a Null Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.3 Configuring the Null Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.4 Setting up the PPP Network Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.5 Testing the Network Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.6 Using VM600 Software with a PPP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.6.1 Using MPS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.6.2 Using CMS Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

5 SETTING UP A MODBUS CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.2 Description of Modbus RTU Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.2.1 Frame and Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.2.2 Communications Parameters for the VM600 . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.2.3 Modbus Functions Supported by the VM600 . . . . . . . . . . . . . . . . . . . . . . . 5-3
5.2.4 Function Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
5.3 Description of Modbus TCP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.4 Definition of Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.4.1 Parameters Concerning MPC 4 Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

6 TECHNICAL SUPPORT AND REPAIRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.1 Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.2 Repairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

vi VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 PREFACE

About This Manual

This manual provides reference information on using Vibro-Meter’s VM600 Series systems
in a networked configuration. It is applicable to the following VM600 systems :
• Machinery Protection System (MPS)
• Condition Monitoring System (CMS)

Who Should Use This Manual ?

The manual is written for operators of process monitoring/control systems using the VM600
Series systems.
The operator is assumed to have the necessary technical training in electronics and
mechanical engineering (professional certificate/diploma, or equivalent) to enable him to
install, program and use the system(s).

Structure of the Manual

This section gives an overview of the structure of the document and the information contained
within it. Some information has been deliberately repeated in different sections of the
document to minimize cross-referencing and to facilitate understanding through reiteration.
The chapters are presented in a logical order. You should read those that are most relevant
to you and then keep the document at hand for future reference.
The structure of the document is as follows :

Chapter 1 Networking Introduction and Overview

Describes how to use a VT100 terminal (or emulator) to change the IP
address of the VM600 rack and edit Modbus configuration files. A brief
description of the vi editor is also provided.
Chapter 2 VT100 Terminal Sessions
Introduces the networking options possible with the VM600. Provides a brief
overview to networking terms and principles (intended principally for those
not familiar with the field).
Chapter 3 Setting up an Ethernet Connection
Provides information on how to configure your PC to communicate with the
VM600 over an Ethernet link.
Chapter 4 Setting up a PPP Connection
Provides information on how to configure your PC to communicate with the
VM600 over an RS-232 link using the Point-to-Point Protocol (PPP).
Chapter 5 Setting up a Modbus Connection
Describes the Modbus RTU and Modbus TCP protocols. Provides detailed
information on reading discrete inputs and registers from the VM600 rack.

VM600 Networking Instruction Manual MAVM600-NET/E vii

Edition 2 - Mar 31/06
 Chapter 6 Technical Support and Repairs
Provides contact details for technical queries and for getting equipment
repaired.
Appendix Abbreviations
Contains a list of abbreviations used in this document.
Product Defect Report
Allows the user to indicate problems observed on a module/unit, thus
enabling our Customer Support department to repair the equipment as
quickly as possible.
Documentation Evaluation Form
Allows the user to provide us with valuable feedback on our documentation.

Related Publications and Documentation

For further information, the operator is referred to one or more of the following software
manuals (the choice depending on the customer’s specific application) :
• VM600 Condition Monitoring System (CMS) Software Manual, Volumes 1 and 2
Vibro-Meter Document No. MACMS-SW/E
• VM600 Condition Monitoring System (CMS) Quick Start Manual
Vibro-Meter Document No. MACMS-QS/E
• MPCC Configuration Software for VM600 Series Machinery Protection Card
Vibro-Meter Document No. MAMPCC/E
• MPS1 Configuration Software for VM600 Series Machinery Protection System
Vibro-Meter Document No. MAMPS1-SW/E
• MPS2 Configuration Software for VM600 Series Machinery Protection System
Vibro-Meter Document No. MAMPS2-SW/E
The operator is also referred to one or more of the following hardware manuals (the choice
depending on the customer’s specific application) :
• VM600 Series Condition Monitoring System (CMS) Hardware Manual
Vibro-Meter Document No. MACMS-HW/E
• VM600 Series Machinery Protection System (MPS)
Vibro-Meter Document No. MAMPS-HW/E

viii Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 NETWORKING INTRODUCTION AND OVERVIEW
Communication Possibilities

1 NETWORKING INTRODUCTION AND OVERVIEW

1.1 Communication Possibilities

A number of possibilities exist for communicating with a VM600 rack :
• Ethernet / TCP/IP
Allows configuration of a rack using Vibro-Meter’s MPS software (e.g. MPS1, MPS2) or
CMS software
• Communication possible via CPU M card or IOC N card.
Refer to Chapter 3 for further information.
• Ethernet / Modbus TCP
Allows a Distributed Control System (DSC) to read discrete inputs and registers.
Communication possible via IOC N card.
Refer to Chapter 5 for further information.
• RS-232, RS-485/422 / Modbus RTU
Allows a Distributed Control System (DSC) to read discrete inputs and registers.
Communication possible via IOC N card.
Refer to Chapter 5 for further information.
• RS-232 / VT100 terminal
Allows communication directly with the CPU M card in order to configure an IP address,
modify Modbus parameters (baudrate, parity, etc.) and modify the allocation of Modbus
registers.
Communication possible via CPU M card.
Refer to Chapter 2 for further information.
• RS-232 / PPP (Point-to-Point Protocol)
Allows configuration of a rack using Vibro-Meter’s MPS software (e.g. MPS1, MPS2) or
CMS software
Communication possible via CPU M card.
Refer to Chapter 4 for further information.
• RS-232 / Proprietary protocol
Allows configuration of a stand-alone rack using Vibro-Meter’s software (e.g. MPS1)
Communication possible via MPC 4 or AMC 8 card.
This is not strictly a case of “networking” and it will not be considered further in this
manual.
These possibilities are summarized in Figure 1-1.

VM600 Networking Instruction Manual MAVM600-NET/E 1-1

Edition 2 - Mar 31/06
NETWORKING INTRODUCTION AND OVERVIEW
Some Networking Terms and Definitions

ETHERNET

(1a) ETHERNET / TCP/IP

(Rack configuration using VM600 software
Distributed packages, e.g. MPS1, MPS2, CMS)
Control System
RS-232, RS-485/422 / Modbus
RTU (Read discrete inputs & (2) ETHERNET / Modbus TCP
(3) registers) (Read discrete inputs & registers)

ETHERNET / TCP/IP
(1b) (Rack configuration using VM600
software packages, e.g. MPS1, VM600 Rack
MPS2, CMS)

(6) RS-232 / Proprietary protocol

RS-232 / VT100 terminal (Rack configuration using
(4) (Configure IP address, Modbus MPS1 configuration software)
parameters)

RS-232 / PPP protocol

(5)
(Rack configuration using VM600 software
packages, e.g. MPS1, MPS2, CMS)

Figure 1-1 : Overview of communications possibilities

1.2 Some Networking Terms and Definitions

This section provides a brief overview of networking terms and definitions. It is intended for
users who are unfamiliar with this field.
Further information may be found on numerous web sites.

1.2.1 Network Types

Two principal types are outlined below. Refer also to Figure 1-2.

1.2.1.1 Local Area Network (LAN)

• Usually limited to short distances
• Owned by the organization that uses it

1-2 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 NETWORKING INTRODUCTION AND OVERVIEW
Some Networking Terms and Definitions

• Usually employs solid cable, though wireless LANs are increasingly common
• Transmission rates tend to be in the range of 10 Mbps to 100 Mbps

1.2.1.2 Wide Area Network (WAN)

• Cover extremely large areas
• Usually owned by major communications companies
• Systems often connected to WAN through public networks such as the telephone
system.
• Most common WAN protocol is TCP/IP
• The Internet is an example of a WAN.

(a) Local Area

Network (LAN)

(b) Wide Area

Network (WAN)

Figure 1-2 : Network types (LAN and WAN)

1.2.2 Connectivity Within Networks

The following devices may be found in networks (see also Figure 1-3) :
1- Hubs
• Hubs can be used to interconnect networks but are more commonly used to extend
a network
• Most hubs simply rebroadcast signals to all ports
• Intelligent hubs enable each port to be configured
• Switching hubs read the destination address and rebroadcast signals only to the
actual destination port
2- Repeaters
• Amplify signals on networks

VM600 Networking Instruction Manual MAVM600-NET/E 1-3

Edition 2 - Mar 31/06
NETWORKING INTRODUCTION AND OVERVIEW
Some Networking Terms and Definitions

• Most commonly used to increase the length of the network backbone

• Normally signals should not pass through more than two repeaters before reaching
their destination
3- Bridges
• Selectively sends signals from one segment to the other
• Can filter signals based on the protocol type
• Transparent bridges contain the addresses of each computer and calculate the
shortest route to the destination computer
• Source-routing bridges : sender determines the proper route
4- Routers
• Connect independent networks
• Dynamic and static routers exist
• Distance-vector routing :
Each router sends its table to all other routers at regular intervals
Link-state routing :
Instead of sending the entire table, only the changes are sent
5- Gateways
• Connect networks that use dissimilar protocol
• Connect networks with different address groups (subnets).
• Data transmission is usually slowed when passing through a gateway due to
protocol translation
• Gateway devices are usually more expensive than routers

1-4 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 NETWORKING INTRODUCTION AND OVERVIEW
Some Networking Terms and Definitions

X
Station

Hub
(Section 1 of first
network)

Bridge

Hub
(Section 2 of first
Gateway network)

Repeater
Second Network

Repeater

Figure 1-3 : Network devices

1.2.3 Ethernet
Ethernet provides a method for high-bandwidth communication between devices on a LAN.
It is presently the most commonly used system.
The original Ethernet specification served as a basis for the IEEE 802.3 standard. This
designates both physical transmission media and the method of transmission along the
media.
Over 20 variations of Ethernet are presently available. The ones most applicable to the
VM600 system are :
1- 10Base-2 (also known as Thinnet)
• Operates at 10 Mbps and uses baseband transmission methods
• Uses 50 Ω coaxial cable
• Maximum cable segment length is 185 meters (600 feet)
• Maximum cable length with repeaters is 925 meters (3000 feet)
• Cables use BNC connectors

VM600 Networking Instruction Manual MAVM600-NET/E 1-5

Edition 2 - Mar 31/06
NETWORKING INTRODUCTION AND OVERVIEW
Some Networking Terms and Definitions

• Computer network interface card (NIC) requires T-connector. Any unused connector
must have 50 Ω termination.
• Cheaper than 10Base-5 (also known as Thicknet)
• More expensive than unshielded twisted pair (UTP) used by 10Base-T
• Break in any one cable can bring down the entire network
2- 10Base-T
• Operates at 10 Mbps and uses baseband transmission methods
• Uses least expensive cable type, i.e. shielded twisted pair (STP) or unshielded
twisted pair (UTP) cable (most use UTP)
• Maximum cable segment length is 100 meters
• Cables use RJ-45 connectors
• Star or star-bus topology is created, with systems connected to each other via hubs
• Easy to expand
3- 10Base-FL
• Operates at 10 Mbps and uses baseband transmission methods
• Uses light transmitted through a pair of fiber optic cables rather than electricity to
transmit signals, so is insensitive to EMI and RFI
• Maximum cable segment length is 2000 meters
• Network interface cards require fiber optic transceivers
• Star topology, therefore requires a hub
4- 100Base-T (also known as Fast Ethernet)
• Operates at 100 Mbps and uses baseband transmission methods
• Variants depending on physical transmission media are :
100Base-TX (2 pairs of high-quality twisted pairs, allowing full duplex transmission)
100Base-T4 (4 pairs of normal-quality twisted pairs)
100Base-FX (2 multimode fiber optic cables)
• Star topology, therefore requires a hub
• Used mainly for network backbones or server-to-server connections (clustering)
In terms of the VM600, Ethernet communication is nevertheless possible with a very simple
configuration that uses a crossover cable to connect the VM600 rack directly to the host
computer. Refer to Section 3.1 for further information.

1.2.4 Network Protocols

Important network protocols for the VM600 system are :
1- TCP/IP (Transmission Control Protocol / Internet Protocol)
2- PPP (Point-to-Point Protocol)

1.2.4.1 The TCP/IP Protocol

• The most widely used protocol suite in the world (used on Internet)
• Most major network operating systems (NOSs) support the use of TCP/IP
• Originally designed for WAN use, now commonly used for LANs as well
• Routable protocol that offers true internetworking and interoperability between disparate
NOSs
• Dynamic Host Configuration Protocol (DHCP) allows automatic IP address assignment

1-6 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 NETWORKING INTRODUCTION AND OVERVIEW
Some Networking Terms and Definitions

• Not as fast as NetBEUI (a proprietary Microsoft networking protocol) on small networks

• Provides full internetwork routing support

1.2.4.2 The Point-to-Point Protocol (PPP)

• Developed in the early 1990s
• Designed to overcome the problems with Serial Line Internet Protocol (SLIP)
• Can be used with Internet Protocol (IP), Internetwork Packet Exchange (IPX) protocol
and NetBEUI (a proprietary Microsoft networking protocol)
• Includes cyclic redundancy check (CRC) to check for errors
• Includes compression so it does not have to rely on hardware compression
The structure of a PPP frame is shown in Figure 1-4.

Flag 0X7E Flag 0XFF Control 0X03 Protocol Type

(1 byte) (1 byte) (1 byte) (2 bytes)

PPP Header

Data
(up to 1500 bytes in total)

CRC Flag 0X7E

Data (continued)
(2 bytes) (1 byte)

Figure 1-4 : Constitution of a PPP frame

1.2.5 IP Addressing (TCP/IP Protocol)

1.2.5.1 Basic Rules

• Each network must have a unique network address
• Each workstation on a network must have a unique host address
• Your IP address must be unique to the rest of the network
• Never use an IP address not assigned to you if you are going to be connected to a
network, e.g. the Internet.

1.2.5.2 IP Addressing and Address Classes

IP addressing uses a 32-bit (4-byte) address with two parts :
• Network number
• Host number
Each byte is converted into a decimal number between 1 and 255 and they are separated by
periods (dots). Example :

VM600 Networking Instruction Manual MAVM600-NET/E 1-7

Edition 2 - Mar 31/06
NETWORKING INTRODUCTION AND OVERVIEW
Some Networking Terms and Definitions

• 100.100.100.100
Three common IP address classes exist (see also Figure 1-5) :
• Class A
Supports approx. 16 million hosts on each of 127 networks
Address format : Network.Host.Host.Host
• Class B
Supports approx. 65 000 hosts on each of approximately 16 000 networks
Address format : Network.Network.Host.Host
• Class C
Supports 254 hosts on each of approximately 2 million networks
Address format : Network.Network.Network.Host

1.2.5.3 Subnets and Subnet Masks (Netmasks)

Subnets allow you to subdivide a larger network into smaller, more manageable units. You
must provide a subnet mask (also known as a netmask).
Benefits of subnetting :
• Reduced network traffic by selecting the path any information has to be sent to
• Optimized network performance
• Simplified management
• Facilitates spanning large geographical distances
Default subnet masks (also known as “natural masks”) are :
• Class A :255.0.0.0 (decimal)
11111111.00000000.00000000.00000000 (binary)
• Class B :255.255.0.0
11111111.11111111.00000000.00000000
• Class C :255.255.255.0
11111111.11111111.11111111.00000000

1-8 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 NETWORKING INTRODUCTION AND OVERVIEW
Some Networking Terms and Definitions

Class A
Network Host Host Host
0
8 bits 8 bits 8 bits 8 bits

Binary network address starts with “0”, so first byte can be between 1 and 127 (decimal).
The first byte identifies the network and the remaining 3 bytes identify the host.
Example : 104.122.245.10 (where “104” identifies the network and “122.245.10” the host)
Number of possible networks : 127
Max. number of hosts : 16 777 214

Class B
Network Network Host Host
1 0
8 bits 8 bits 8 bits 8 bits

Binary network address starts with “10”, so first byte can be between 128 and 191 (decimal).
The first 2 bytes identifies the network and the remaining 2 bytes identify the host.
Example : 155.113.16.102 (where “155.113” identifies the network and “16.102” the host)
Number of possible networks : 16 384
Max. number of hosts : 65 534

Class C
Network Network Network Host
1 1 0
8 bits 8 bits 8 bits 8 bits

Binary network address starts with “110”, so first byte can be between 192 and 223 (decimal).
The first 3 bytes identifies the network and the remaining 1 byte identifies the host.
Example : 210.222.126.55 (where “210.222.126” identifies the network and “55” the host)
Number of possible networks : 2 097 152
Max. number of hosts : 254
(Note : although theoretically 256 host addresses should be possible, the addresses “00000000”
and “11111111” are reserved)

Figure 1-5 : Overview of IP address classes

VM600 Networking Instruction Manual MAVM600-NET/E 1-9

Edition 2 - Mar 31/06
NETWORKING INTRODUCTION AND OVERVIEW
Some Networking Terms and Definitions

THIS PAGE INTENTIONALLY LEFT BLANK

1 - 10 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 VT100 TERMINAL SESSIONS
Purpose

2 VT100 TERMINAL SESSIONS

2.1 Purpose
A VT100 connection allows parameters in the CPU M card’s operating system files to be
customized before the VM600 is used with an Ethernet connection or before a Modbus
configuration is set up. These system files are on the card’s “disk-on-chip”.
Using the a VT100 terminal session, you can:
• Configure an IP address for the VM600 rack
• Modify Modbus communication parameters such as baud rate and parity.
• Modify the allocation of Modbus registers

2.2 Getting Started

2.2.1 If a VT100 Terminal is Available

If you have a VT100 terminal, use a suitable serial cable to connect it to the 9-pole RS-232
connector on the front panel of the CPU M card. The required settings are :
• 57600 baud
• 8 bits
• 1 stop bit
• No parity
If no VT100 terminal is available, you can use a Windows tool (such as HyperTerminal) to
emulate one (see Section 2.2.2).

2.2.2 Emulating a VT100 terminal from Windows (HyperTerminal)

NOTE : This description assumes that Windows 2000 is the operating system used. If this
is not the case, contact your System Administrator or Vibro-Meter for further
information.

VM600 Networking Instruction Manual MAVM600-NET/E 2-1

Edition 2 - Mar 31/06
VT100 TERMINAL SESSIONS
Getting Started

To get started, proceed as follows .

1- Click the Start > Programs > Accessories > Communications and choose
HyperTerminal. The Connection Description dialog box appears (see Figure 2-1).

Figure 2-1 : The “Connection Description” dialog box

2- Select an appropriate icon from the choice provided, then type in a suitable name for the
terminal emulation. Click OK to obtain the Connect To dialog box (see Figure 2-2).

Figure 2-2 : The “Connect To” dialog box

2-2 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 VT100 TERMINAL SESSIONS
Getting Started

3- Set the communication parameters for the chosen port as shown in Figure 2-3, then click
OK.

Figure 2-3 : Defining the port settings

VM600 Networking Instruction Manual MAVM600-NET/E 2-3

Edition 2 - Mar 31/06
VT100 TERMINAL SESSIONS
Getting Started

4- Choose Properties from the File menu and set the communication parameters for the
chosen port as shown in Figure 2-4.

Figure 2-4 : Configuring the Settings dialog box for a VT100 terminal

5- Click in turn the Terminal Setup and ASCII Setup keys and check the resulting screens
are as shown in Figure 2-5.

Figure 2-5 : The Terminal Settings and ASCII Settings dialog boxes

2-4 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 VT100 TERMINAL SESSIONS
Getting Started

6- Login by typing (see Figure 2-6)

login : user (press the <Enter> key
password : config(press the <Enter> key)

Figure 2-6 : Logging in to the session

7- Use the “ls” command to list the files in the directory (see Figure 2-7).

Figure 2-7 : Listing the files in the directory

VM600 Networking Instruction Manual MAVM600-NET/E 2-5

Edition 2 - Mar 31/06
VT100 TERMINAL SESSIONS
Getting Started

The following files are typically found :

mbcfg.2 Configuration file for Modbus communication through 9-pole RS-232

connector on front of CPU M card
File contains the Modbus address for the rack, the definition of
communications parameters (baud rate, parity, etc.) and the definition of all
discrete inputs and registers that can be read.
mbcfg.3 Configuration file for Modbus communication through RS connector
(RJ11-type) on IOC N card
File contains the Modbus address for the rack, the definition of
communications parameters (baud rate, parity, etc.) and the definition of all
discrete inputs and registers that can be read.
mbcfg.tcp Configuration file for Modbus communication through Ethernet connector
on IOC N card
File contains the Modbus address for the rack, the definition of
communications parameters (baud rate, parity, etc.) and the definition of all
discrete inputs and registers that can be read.
hosts This file contains the local host address, the IP address of the VM600 rack
(= the “node1” address) and the IP address of the gateway (if applicable)

Depending on the CPU sub-module options ordered and installed, the following files can also
be found :

mbcfg.4 Configuration file for Modbus communication through the two “A” connectors
(RJ11-type) on IOC N card
File contains the Modbus address for the rack, the definition of
communications parameters (baud rate, parity, etc.) and the definition of all
discrete inputs and registers that can be read.
mbcfg.5 Configuration file for Modbus communication through the two “B” connectors
(RJ11-type) on IOC N card
File contains the Modbus address for the rack, the definition of
communications parameters (baud rate, parity, etc.) and the definition of all
discrete inputs and registers that can be read.

2-6 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 VT100 TERMINAL SESSIONS
Changing the IP Address of the Rack

2.3 Changing the IP Address of the Rack

The hosts file on the CPU M card’s “disk-on-chip” must be edited in order to change the IP
address of the VM600 rack :
1- Use the vi command to edit the hosts file (see Figure 2-8).

Figure 2-8 : To edit the “hosts” file

2- Modify the line defining the IP address of the rack. This line is shown in Figure 2-9.

“127.1” is the local host

address.
This should not be modified.

Gateway address (if applicable).

Note : In this example it is
“commented out” by the #
character.

“10.10.56.56” is the IP address of

the VM600 rack (= factory setting).
This can be modified if required.
Note : Do not change the host
name from “node1”

Figure 2-9 : To edit the IP address of the rack

3- If a gateway is required, remove the # character preceding the gateway address This will
activate the address. Refer to Section 2.4 for further information.
4- Use the “wq” command to save the changes and leave the VT100 editor.
5- Power down and restart the VM600 rack.

VM600 Networking Instruction Manual MAVM600-NET/E 2-7

Edition 2 - Mar 31/06
VT100 TERMINAL SESSIONS
Activating a Gateway

If you are unable to power down the rack you can use the shutdown -f command
instead.

NOTE : Further information on VT100 commands (vi Editor) can be found in Section 2.6.

2.4 Activating a Gateway

2.4.1 When is a Gateway Necessary?

In general terms, a gateway is needed to allow communication between two different subnets
(see Figure 2-10).
In the example shown, System 1 can communicate directly with System 2, as both have an
IP address beginning with 10.10.
System 1 cannot communicate directly with System 3 as the IP addresses are very different.
A gateway is therefore needed.
System 1 can communicate with the gateway as both have an IP address beginning with
10.10. Likewise, System 3 can communicate with the gateway as both have an IP address
beginning with 194.11.227.
Note that if the subnet mask for subnet “1” was changed from 255.255.0.0 to 255.255.255.0,
communication would no longer be possible between System 1 and System 2 or between
System 1 and the gateway.

Subnet “1” (10.10.xxx.xxx) Subnet “2” (194.11.227.xxx)

System 1
IP address =
Communication
10.10.56.56
possible
Subnet mask =
255.255.0.0

10.10.1.254 194.11.227.90 Gateway

Communication
Communication
possible
possible

System 3
System 2 IP address =
IP address = 194.11.227.5
10.10.57.5 Subnet mask =
Subnet mask = 255.255.255.0
255.255.0.0

Figure 2-10 : Communication between two subnets via a gateway

2-8 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 VT100 TERMINAL SESSIONS
Activating a Gateway

In terms of the VM600 rack, Ethernet communication between the host PC and the VM600
rack (CPU M card) can only take place if the IP addresses of the host PC and the VM600 rack
belong to the same subnet.
To get round this potential problem, a gateway must be defined in the CPU M card’s
“disk-on-chip”.

NOTE : For proper operation, the IP addresses of the gateway and the CPU M must belong
to the same subnet. If this is not the case, the gateway cannot be accessed by the
CPU M.

The host PC and the gateway must also have IP addresses that are visible to each other.
Finally, the host PC can run on any operating system but must be able to emulate a VT100
terminal.

2.4.2 Procedure
To activate the gateway, proceed as follows :
1- Add (or activate) the IP address of the gateway in the “hosts” file found on the CPU M
card’s “disk-on-chip” (refer to Section 2.3).
The hosts file may already contain a commented out line defining the IP address of the
gateway, as shown in Figure 2-9. In this case, it is sufficient to remove the # character at
the beginning of the line and type in the actual IP address of your gateway.
Otherwise, type in the IP address (followed by the word “gateway”) as shown in
Figure 2-11.

Gateway address

Figure 2-11 : The “hosts” file with the gateway address activated

2- The file on the “disk-on-chip” called tcpip.1 must now be modified.

Use the following “vi” command to edit this file :
# vi /etc/config/bin/tcpip.1

VM600 Networking Instruction Manual MAVM600-NET/E 2-9

Edition 2 - Mar 31/06
VT100 TERMINAL SESSIONS
Editing Modbus Configuration Files

3- Activate the following line at the end of the file by removing the # character (see
Figure 2-12) :
/usr/ucb/route add default gateway

Corresponds to default subnet

mask (255.255.0.0)
This line can be changed if
necessary.

Appearance of line once the #

character has been removed.

Figure 2-12 : Editing the “tcpip.1” file to activate the gateway

4- The default subnet mask is set to 255.255.0.0.

If the subnet mask has to be changed, modify the line beginning NETMASK (see
Figure 2-12). For example, if the required subnet mask is 255.255.255.0, change this line
as follows :
NETMASK = 0 x f f f f f f 0 0
5- Power down and restart the VM600 rack.
If you are unable to power down the rack you can use the shutdown -f command
instead.

2.5 Editing Modbus Configuration Files

It is sometimes necessary to change the Modbus address of a rack or various
communications parameters such as baud rate or parity. This is done by editing one of the
following configuration files stored on the CPU M card’s “disk on chip” :

mbcfg.2 When communication occurs through 9-pole RS-232 connector on front of

CPU M card
mbcfg.3 When communication occurs through the RS connector (type RJ11) on
IOC N card
mbcfg.4 When communication occurs through the “A” connectors (RJ11) on IOC N
card
mbcfg.5 When communication occurs through the “B” connectors (RJ11) on IOC N
card
mbcfg.tcp When communication occurs through Ethernet connector on IOC N card

2 - 10 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 VT100 TERMINAL SESSIONS
Editing Modbus Configuration Files

2.5.1 Opening the Configuration File

1- Start the VT100 terminal session as described in Section 2.2.
2- Use the “vi” command to edit the file in question. A screen similar to that shown in
Figure 2-13 will appear.

Figure 2-13 : Editing a Modbus configuration file (e.g. mbcfg.2)

2.5.2 Changing the Modbus Address of the Rack

1- Open the configuration file as described in Section 2.5.1.

VM600 Networking Instruction Manual MAVM600-NET/E 2 - 11

Edition 2 - Mar 31/06
VT100 TERMINAL SESSIONS
Using the vi Editor

2- Modify the line containing the existing Modbus address (see Figure 2-14).

Line defining the Modbus

address of the rack
(shown as “1” here)

Figure 2-14 : Changing the Modbus address

2.5.3 Changing the Modbus Communications Parameters (Device Definition)

1- Open the configuration file as described in Section 2.5.1.
2- Modify the line containing the existing device definition (see Figure 2-15).

Line defining the Modbus

communications parameters
In this example :
* 9600 baud
* 8 bits
* no parity
* stop bit

Figure 2-15 : Changing the Modbus communications parameters

2.6 Using the vi Editor

The vi editor is a screen-based editor used by the VT100 terminal. It is also the editor used
when a VT100 terminal is emulated using HyperTerminal. It has two distinct operating modes
: a “command mode” (<Esc> key) and a “text insertion mode” (i key).
The most commonly required vi commands are listed in Table 2-1. For further information,
consult one of the various sites on the internet offering short guides.

2 - 12 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 VT100 TERMINAL SESSIONS
Using the vi Editor

Command Function

vi file1 Invokes the editor

Use the arrow keys to move the cursor around the text.
j k h l
Alternatively, use j instead of the up arrow, k instead of the down arrow,
h instead of the left arrow and l instead of the right arrow.

:wq Writes and quits the editor (changes are saved)

:q! Quits the editor (changes are discarded)

i Changes to text insertion mode, at cursor position

<Esc> Toggles to command mode

dd Erases the current line

ndd Erases n lines, starting from the current line

a Toggles to text insertion mode, after cursor position

<Ctrl> f Scrolls down one page

<Ctrl> b Scrolls up one page

1G Goes to first line of the file

G Goes to last line of the file

x Erases current character

u Undoes last command

/xyz Searches the next occurrence of xyz

?xyz Searches the previous occurrence of xyz

n Repeats the most recent search command, in the same direction

:1,$s/xyz/abc Replaces all occurrences of xyz by abc, from first to last line

J Joins two lines

yy Copies current line (into a temporary area)

nyy Copies n lines starting from the current line

p Inserts copied lines at the current line

:r file2 Inserts contents of file2 at current line

Table 2-1 : Common vi commands

VM600 Networking Instruction Manual MAVM600-NET/E 2 - 13

Edition 2 - Mar 31/06
VT100 TERMINAL SESSIONS
Using the vi Editor

THIS PAGE INTENTIONALLY LEFT BLANK

2 - 14 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP AN ETHERNET CONNECTION
Introduction

3 SETTING UP AN ETHERNET CONNECTION

3.1 Introduction
A direct Ethernet connection is the quickest and simplest method of communicating with the
VM600 rack (see Figure ).

Personal

Ethernet 1
computer (PC)

Crossover cable
P/N 962.02.10.0031
CPU M / IOC N

VM600 rack

Direct connection of a PC to a VM600 rack (without using LAN)

For this you will require :

• A CPU M card with an Ethernet sub-module.
• A crossover cable allowing Ethernet communication via the CPU M or the IOC N.
This is available from Vibro-Meter : P/N 962.02.10.0031
If your CPU M does not allow Ethernet communications, you can still communicate with the
rack using a PPP connection. Refer to Chapter 4 for further information.

NOTE : The exact procedure to be followed depends on the operating system used. This
description assumes Windows 2000 is installed. If you are using a different
operating system you can still follow this description for guidance, but the menus
and dialog boxes shown in screen shots may look quite different.

In case of questions or problems, please consult first the Windows online help
utility or contact your System Administrator. If still no solution can be found, contact
your nearest Vibro-Meter representative.

3.2 Requirements
1- One of the following operating systems (or higher) :
• Windows 98
• Windows NT 4
• Windows 2000
• Windows XP

VM600 Networking Instruction Manual MAVM600-NET/E 3-1

Edition 2 - Mar 31/06
SETTING UP AN ETHERNET CONNECTION
Requirements

2- A CPU M card with a fully-installed Ethernet sub-module (plug & play)

You should check the CPU M card visually to confirm the presence of this sub-module.
It is installed on the lower half of the card (see Figure 3-1).
3- A unique IP address for your PC
4- A unique IP address for your VM600 rack

NOTE : The IP address of the VM600 rack (CPU M card) is set in the factory to
10.10.56.56.
It is highly recommended to change this address.
To do this, change the address in the “hosts” file stored on the CPU card’s
“disk-on-chip” using a VT100 terminal (or emulator such as HyperTerminal). Refer
to Section 2.3 for further information.

CPU sub-module

Ethernet sub-module

Front panel of
CPU M card

Figure 3-1 : Position of Ethernet submodule on the CPU M card

3-2 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP AN ETHERNET CONNECTION
Configuration

3.3 Configuration
1- An Ethernet card has to be defined, as shown in the example in Figure 3-2.

Figure 3-2 : Defining an Ethernet card

2- A protocol (TCP/IP) has to be defined, as shown in the example in Figure 3-3.

Figure 3-3 : Defining a protocol

VM600 Networking Instruction Manual MAVM600-NET/E 3-3

Edition 2 - Mar 31/06
SETTING UP AN ETHERNET CONNECTION
Configuration

3- Click the Properties key to get the Internet Protocol (TCP/IP) Properties dialog box (see
Figure 3-4). Enter an IP address for the PC (and for the gateway if applicable) and the
correct subnet mask.

IP address of PC
(example)

Subnet mask
(example)

IP address of gateway
(should be entered if
applicable)

Figure 3-4 : Setting up the IP address and subnet mask

4- Open the “hosts” file on your system disk using Notepad or a similar editor. This file is in
the Windows area of the system disk. If Windows 2000 is installed it will be in :
C:\winnt\system32\drivers\etc

3-4 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP AN ETHERNET CONNECTION
Configuration

A window like that shown in Figure 3-5 appears.

VM600 rack having IP

address 10.10.56.56 is given
the hostname “rack1”
(example)

VM600 rack having IP address

10.10.56.58 is given the
hostname “rack3” (example).
NB: This rack is “commented
out” by the # character

Figure 3-5 : Typical “hosts” file

NOTE : If you read or modify this file, be careful to save it without a file extension (i.e.
don’t give it the extension .txt).

5- Define a suitable hostname for the rack. Host names for several racks can be defined in
this file. The # character can be used to temporarily “comment out” a line until it is
required some time in the future (see Figure 3-5)

NOTE : The IP address of the rack is not actually defined in this “hosts” file, but in a different
“hosts” file on the CPU M card’s “disk-on-chip”. Refer to Section 2.3 for further
information.
The IP address of a given rack should of course be the same in both of these
“hosts” files.

6- Find the application called “cmd.exe” which is located in the Windows directory. When
you run this application, a window like that shown in Figure 3-6 appears.

“ping” command
for IP address
10.10.56.56
(example)

Figure 3-6 : Using the “ping” command to check the connection

VM600 Networking Instruction Manual MAVM600-NET/E 3-5

Edition 2 - Mar 31/06
SETTING UP AN ETHERNET CONNECTION
Using VM600 Software with an Ethernet Connection

7- Use the “ping” command to check the connection to the VM600 rack. Enter the IP
address of the VM600 rack.

3.4 Using VM600 Software with an Ethernet Connection

3.4.1 Using MPS Software

1- Start up the MPS software (refer to the relevant MPS software manual for further
information).
2- Select the rack in question from the “tree” on the left-hand side of the screen (see
Figure 3-7).

Highlight the
rack

Choose from the list the hostname that corresponds to the VM600
rack in question.
(Alternatively, enter the IP address of the rack directly in the field)

Figure 3-7 : Defining the hostname in the MPS software

3- Activate the CPU Present radio button.

4- Drop down the Hostname list and select the host name (i.e. rack name) that corresponds
to the rack in question (see Figure 3-7).
Alternatively, you can type the IP address of the rack (e.g. 10.10.56.56) directly in the
Hostname field.
Communication via Ethernet should now be possible.

3.4.2 Using CMS Software

1- Start up the CMS software (refer to the relevant CMS software manual for further
information).
2- Display the Architectural view.

3-6 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP AN ETHERNET CONNECTION
Using VM600 Software with an Ethernet Connection

3- Select the rack in question from the “tree” on the left-hand side of the screen (see
Figure 3-8).

Highlight the
rack

Choose from the list the hostname that corresponds to the

VM600 rack in question.
(Alternatively, enter the IP address of the rack directly in the field)

Figure 3-8 : Defining the hostname in the CMS software

4- Activate the CPU Present radio button.

5- Drop down the Hostname or TCP/IP Address list and select the hostname (i.e. rack
name) that corresponds to the rack in question (see Figure 3-8).
Alternatively, you can type the IP address of the rack (e.g. 10.10.56.56) directly in the
field.
Communication via Ethernet should now be possible.

VM600 Networking Instruction Manual MAVM600-NET/E 3-7

Edition 2 - Mar 31/06
SETTING UP AN ETHERNET CONNECTION
Using VM600 Software with an Ethernet Connection

THIS PAGE INTENTIONALLY LEFT BLANK

3-8 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A PPP CONNECTION
Requirements

4 SETTING UP A PPP CONNECTION

NOTE : The exact procedure to be followed will depend on the operating system used. This
description assumes Windows 2000 is installed. If you are using a different
operating system you can still follow this description for guidance, but the menus
and dialog boxes shown in screen shots may look quite different.

In case of questions or problems, please consult first the Windows on-line help or
contact your System Administrator. If still no solution can be found, contact your
nearest Vibro-Meter representative.

4.1 Requirements
1- One of the following operating systems (or higher) :
• Windows 98
• Windows NT 4
• Windows 2000
• Windows XP
2- An RS-232 communication port on your PC
3- An RS-232 cable as shown in Figure 4-1
These cables are available from Vibro-Meter : P/N = 957.18.09.030X

Connect to Connect to
CPU M card personal computer

Male connector Female connector

Figure 4-1 : Interface cable to connect CPU M card to the serial port of
personal computer to allow PPP communication

4- An Ethernet address (IP address) for the VM600 rack.

Refer to Section 2.3 for information on changing the IP address of the rack.

NOTE : Refer to Section 4.1.1 for information concerning restrictions on IP addresses.

4.1.1 IP Address Restrictions

The PC used for PPP communication with the VM600 rack may already be connected to a
network (LAN). If this is the case, its Ethernet card will already have been configured with an
IP address (belonging to “Subnet 1”) allowing communication with other systems on the
network (see Figure 4-2).

VM600 Networking Instruction Manual MAVM600-NET/E 4-1

Edition 2 - Mar 31/06
SETTING UP A PPP CONNECTION
Installing a Null Modem

The VM600 rack you are trying to communicate with must have an IP address that does not
belong to Subnet 1, but to some other subnet (e.g. “Subnet 2”).

NOTE : Subnet 1 and Subnet 2 must be different to allow messages to be directed onto
either physical interface.n

Serial port Personal

(e.g. COM1) computer

Ethernet 1
(PC)

LAN PPP connection using

Subnet 1 RS-232 cable
P/N 957.198.09.030X

Subnet 2

VM600 rack

IP address in Subnet 2
RS-232 connector on (Subnet 1 different
CPU M front panel from Subnet 2)

Figure 4-2 : PPP connection to a VM600 rack (serial communications)

4.2 Installing a Null Modem

A “null modem” must be installed before PPP communication is attempted :
1- Click Start > Contol Panel.

4-2 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A PPP CONNECTION
Installing a Null Modem

2- Double-click the Phone and Modem Options icon to obtain the dialog box shown in
Figure 4-3.

Figure 4-3 : The Phone and Modem Options icon and dialog box

3- Select the Modems thumb tab (see Figure 4-4) and click on Add to call up the
Add/Remove Hardware Wizard. Configure the first page of the wizard as shown.

Figure 4-4 : The Phone and Modem Options icon and dialog box

VM600 Networking Instruction Manual MAVM600-NET/E 4-3

Edition 2 - Mar 31/06
SETTING UP A PPP CONNECTION
Installing a Null Modem

4- Select NULL Modem Types (see Figure 4-5). Click on the Have Disk key to find and
select the file called mdmcisc2.inf as shown. You should then select the model called
“RAS Serial Cable between 2 PCs”.

Figure 4-5 : Setting up for NULL modem type

5- Select a communications port for the modem as shown in Figure 4-6. Click on Finish to
end the wizard. The modem is now installed.

Figure 4-6 : Selecting a communications port

4-4 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A PPP CONNECTION
Configuring the Null Modem

4.3 Configuring the Null Modem

1- Select the modem (“RAS Serial Cable between 2 PCs”) from the Modems thumb tab of
the Phone and Modem Options dialog box (see Figure 4-7). Click on the Properties key
and check that the fields/options on the General and Diagnostics thumb tabs are
configured as shown in Figure 4-7.

Figure 4-7 : The General and Diagnostics thumb tabs

2- Select the Advanced thumb tab (see Figure 4-8). Click on the Change Default
Preferences key and check that the fields/options on the General and Advanced thumb
tabs are configured as shown in Figure 4-8.

VM600 Networking Instruction Manual MAVM600-NET/E 4-5

Edition 2 - Mar 31/06
SETTING UP A PPP CONNECTION
Configuring the Null Modem

Figure 4-8 : Changing the default preferences

4-6 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A PPP CONNECTION
Setting up the PPP Network Connection

4.4 Setting up the PPP Network Connection

1- Click Start > Settings, point to Network and Dial-up Connections and select Make
New Connection (see Figure 4-9). The Network Connection Wizard will appear.

Figure 4-9 : Starting the Network Connection Wizard

2- Follow the wizard and select “Dial-up to a private network” (see Figure 4-10). Choose a
device from the list.

Figure 4-10 : Choosing the connection type and selecting a device

VM600 Networking Instruction Manual MAVM600-NET/E 4-7

Edition 2 - Mar 31/06
SETTING UP A PPP CONNECTION
Setting up the PPP Network Connection

3- The following two screens of the wizard (Phone Number to Dial and Connection
Availability) can be configured as shown in Figure 4-11.

Figure 4-11 : Phone Number to Dial and Connection Availability screens

4- Complete the wizard by entering a suitable name for the connection (see Figure 4-12).

Figure 4-12 : Completing the Network Connection Wizard

4-8 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A PPP CONNECTION
Setting up the PPP Network Connection

5- When the Finish key is clicked, a screen resembling the one in Figure 4-13 will appear.
(This screen can also be obtained from the Start > Settings > Network and Dial-up
Connections menu).

Figure 4-13 : The “Connect Dial-up My VM600 Rack” dialog box

6- Click on the Properties key of the screen in Figure 4-13 to get the General thumb tab
(see Figure 4-14). Select a modem from the list. Press the Configure key to obtain the
Modem Configuration dialog box and set it up as shown in Figure 4-14

Figure 4-14 : General modem configuration

VM600 Networking Instruction Manual MAVM600-NET/E 4-9

Edition 2 - Mar 31/06
SETTING UP A PPP CONNECTION
Setting up the PPP Network Connection

7- Configure the Options and Security dialog boxes as shown in Figure 4-15.

Figure 4-15 : The Options and Security dialog boxes

8- Select the Networking thumb tab (see Figure 4-16). Select PPP as the type of dial-up
server. Choose Internet Protocol (TCP/IP) from the list of components (put a tick in the
box). Click on the Settings key to obtain the PPP Settings dialog box and configure it as
shown in Figure 4-16.

Figure 4-16 : PPP settings

9- Click Properties (Figure 4-16) to obtain the Internet Protocol (TCP/IP) Properties dialog
box (see Figure 4-17). Enter an IP address for the host PC used for the PPP connection.
This address must be different from the actual IP address of the rack, but must belong
to the same subnet.

4 - 10 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A PPP CONNECTION
Setting up the PPP Network Connection

This subnet is dedicated to the PPP connection and must be different from any other
subnet used by the PC for other network devices such as Ethernet cards.
For example, if the rack’s IP address is 10.10.56.56, a valid IP address for the host PC
used for PPP connection would be 10.10.56.1.

IP address for PPP

communication
(example)

Figure 4-17 : The TCP/IP Properties dialog box

10- Select the Sharing dialog box and configure it as shown in Figure 4-18. Clicking on OK
will return you to the screen shown on the right of the figure.

Figure 4-18 : The Sharing dialog box

11- It is advisable to check the network connection as described in Section 4.5.

VM600 Networking Instruction Manual MAVM600-NET/E 4 - 11

Edition 2 - Mar 31/06
SETTING UP A PPP CONNECTION
Testing the Network Connection

4.5 Testing the Network Connection

To test the network connection once it is installed, proceed as follows :
1- Call up the “Connect ...” screen (e.g. “Connect Dial-up My VM600 Rack” ) as shown in
Figure 4-19. You can obtain this screen from the Start > Settings > Network and
Dial-up Connections and then selecting the desired connection (called “Dial-up My
VM600 Rack” in this example).

Figure 4-19 : Obtaining the Pre-Dial Terminal Screen

2- Click on the Dial key to obtain the Pre-Dial Terminal Screen (Figure 4-19). Login by
typing :
login : pppuser
password : ppp (remember to click the <Enter> key)
Click the Continue key to proceed further.

4 - 12 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A PPP CONNECTION
Using VM600 Software with a PPP Connection

3- A small icon appears on the Windows taskbar (see Figure 4-20). Double-click the icon to
obtain status information if required (you do not have to keep this window open).

Figure 4-20 : Icon and status information

4- Find the application called “cmd.exe” which is located in the Windows directory. When
you run this application, a window like the one shown in Figure 4-21 appears.

“ping” command
for IP address
10.10.56.56
(example)

Figure 4-21 : Using the “ping” command to check the connection

5- Use the “ping” command to check the connection to the VM600 rack. Enter the IP
address of the VM600 rack.

4.6 Using VM600 Software with a PPP Connection

4.6.1 Using MPS Software

1- Start up the PPP network connection as described in the first 3 steps of Section 4.5 (refer
to Figure 4-19 and Figure 4-20).
2- Start up the MPS software (refer to the relevant MPS software manual for further
information).

VM600 Networking Instruction Manual MAVM600-NET/E 4 - 13

Edition 2 - Mar 31/06
SETTING UP A PPP CONNECTION
Using VM600 Software with a PPP Connection

3- Select the rack in question from the “tree” on the left-hand side of the screen (see
Figure 4-22).

Highlight the
rack

Choose from the list the hostname that corresponds to the MPS rack in
question.
(Alternatively, enter the IP address of the rack directly in the field)

Figure 4-22 : Defining the hostname in the MPS software

4- Activate the CPU Present radio button.

5- Drop down the Hostname list and select a hostname (i.e. rack name) that corresponds
to the rack in question (see Figure 4-22).
Alternatively, you can type the IP address of the rack (e.g. 10.10.56.56) directly in the
Hostname field.
Communication via the PPP connection should now be possible.

4.6.2 Using CMS Software

1- Start up the PPP network connection as described in the first 3 steps of Section 4.5 (refer
to Figure 4-19 and Figure 4-20).
2- Start up the CMS software (refer to the relevant CMS software manual for further
information).
3- Display the Architectural view.

4 - 14 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A PPP CONNECTION
Using VM600 Software with a PPP Connection

4- Select the rack in question from the “tree” on the left-hand side of the screen (see
Figure 4-23).

Highlight
the rack

Choose from the list the hostname that corresponds to the VM600
rack in question.
(Alternatively, enter the IP address of the rack directly in the field)

Figure 4-23 : Defining the hostname in the CMS software

5- Activate the CPU Present radio button.

6- Drop down the Hostname or TCP/IP Address list and select a hostname (i.e. rack
name) that corresponds to the rack in question (see Figure 4-23).
Alternatively, you can type the IP address of the rack (e.g. 10.10.56.56) directly in the
field.
Communication via the PPP connection should now be possible.

VM600 Networking Instruction Manual MAVM600-NET/E 4 - 15

Edition 2 - Mar 31/06
SETTING UP A PPP CONNECTION
Using VM600 Software with a PPP Connection

THIS PAGE INTENTIONALLY LEFT BLANK

4 - 16 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A MODBUS CONNECTION
Introduction

5 SETTING UP A MODBUS CONNECTION

5.1 Introduction
This chapter describes the implementation of the Modbus software interface for the VM600
rack.
Communication is done through either :
• A serial line using the Modicon standard Modbus RTU protocol
and/or
• An Ethernet line using the Modicon standard Modbus TCP protocol
The transmitted data consists of real-time values (vibration level, pressure, etc…) and status
information (alarms). This data can be used by any external system (e.g. distributed control
system) for the purposes of machinery monitoring.
The interface presently supports the following VM600 cards :
• MPC 4
• AMC 8
The Modbus RTU protocol can be used indifferently with RS-232 and RS-485 serial
interfaces. In RS-485 mode, a master device can address up to 99 instruments. The link can
be half-duplex or full-duplex with selectable transmission rates from 1200 to 19200 bits/s.

NOTE : Note that when the CPU M card contains an optional RS-485 / RS-422
communications module (allowing communication over the “A” and “B” pairs of
connectors on the IOC N), only full duplex transmission is possible.

The Modbus TCP protocol has exactly the same layout as the Modbus RTU protocol, with the
exception of the "framing" sequence check pattern and the address interpretation.
Communications are based on the master-slave principle. The VM600 rack is the slave in the
system. The master equipment requests data from the addressed slave, which can only
respond. The slave cannot initiate a transaction. The master can address individual slaves to
request or send data. It can also request an action to be taken by one or all the slaves in the
network.

5.2 Description of Modbus RTU Protocol

5.2.1 Frame and Timing

NOTE : The following definitions of the Modbus protocol are adapted to the VM600 MPS.

The Modbus RTU protocol is a serial data transmission format widely used in
communications with programmable controllers. It is easily adaptable to other types of
remote units thanks to its particular message structure (it doesn't operate with variables but
with memory addresses).
The first character of a frame is the slave address, followed by the Modbus function number
and the information field. Finally, two bytes are reserved for an error check code based on
cyclic redundancy checking (CRC). Refer to Figure 5-1.
Each character is composed of 10 bits : 1 start bit, 8 data bits and 1 stop bit

VM600 Networking Instruction Manual MAVM600-NET/E 5-1

Edition 2 - Mar 31/06
SETTING UP A MODBUS CONNECTION
Description of Modbus RTU Protocol

Modbus
Slave CRC
Function Information
Address (2 bytes)
Number

Figure 5-1 : Constitution of a frame

The Modbus RTU protocol has no delimiter character at the beginning and the end of a
message. Each frame must be preceded by and followed by a silent interval of at least 3.5 CT
(where CT = character time). Refer to Figure 5-2.
The connected equipment (VM600 rack) detects the start of a message when any valid
character (containing its address or the address 00) has been received after a silent interval
of at least 3.5 CT. The end of a message is interpreted by a silent interval of the same
duration.

Request Frame Response Frame Request Frame

Addr. -- -- CRC Addr. -- -- -- CRC Addr. -- -- CRC

T1 T2 T3

T1 = time between two characters (min. = 0, max. = 3.5 CT)

Baud Time for
T2 = time between request and response (min. 3.5 CT)
T3 = time between response and next request (min. 3.5 CT) (bits/s) 3.5 CT
CT = 1 character time (= the time needed to transmit one
character consisting of 10 bits) 1200 30 ms
2400 15 ms
4800 8 ms
9600 4 ms
19200 2 ms
Figure 5-2 : Timing considerations

5.2.2 Communications Parameters for the VM600

By default, the communications parameters for the VM600 are :
• Baud rate 9600
• Parity None
• Number of bits 8
• Number of stop bits 1
• Slave address 1
These settings can be modified if required by editing the appropriate configuration file (e.g.
“mbcfg.2”, “mbcfg.3”, “mbcfg.4” or “mbcfg.5”). This is done using a VT100 terminal (or
emulator from the Windows environment). Refer to Section 2.5 for further information.

5-2 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A MODBUS CONNECTION
Description of Modbus RTU Protocol

5.2.3 Modbus Functions Supported by the VM600

The Modbus functions supported by the VM600 are shown in Table 5-1.

Function
Function Description
Number

01 Read coils
02 Read discrete inputs
03 Read multiple registers
04 Read input registers

Table 5-1 : Modbus functions supported

Function 01 Used to read status information (e.g. alarm, danger, OK status).

Function 02 Used to read status information (e.g. alarm, danger, OK status).

NOTE : Function 01 and Function 02 can be used indifferently and there is no reason to
use one rather than the other. They both return the same result.

Function 03 Used to read dynamic values in 16-bit integer format

Function 04 Used to read dynamic values in 16-bit integer format.

NOTE : Function 03 and Function 04 can be used indifferently and there is no reason to
use one rather than the other. They both return the same result.

NOTE : If any other function (apart from the above 4) is requested, an exception code “01”
will be returned to indicate the use of an illegal function.

5.2.4 Function Formats

5.2.4.1 Reading Discrete Inputs

Discrete data (alarm, danger, OK status) can be read using Function 01 or Function 02 of the
Modbus protocol. Both functions return the same result.

NOTE : A maximum of 2040 discrete values (coils) can be requested at one time.

The Request and Response frame formats are shown in Figure 5-3.

VM600 Networking Instruction Manual MAVM600-NET/E 5-3

Edition 2 - Mar 31/06
SETTING UP A MODBUS CONNECTION
Description of Modbus RTU Protocol

Function 01 (Read Coils)

Request frame

1 byte 1 byte 2 bytes 2 bytes 2 bytes

Slave Modbus First coil address Number of coils CRC
address function to be read to be read

Response Frame

1 byte 1 byte 1 byte n bytes 2 bytes

Address Function Byte Bit values (least significant bit CRC
count is first coil value

NOTE : When requesting a variable that is out of the range configured in the VM600,
the exception code “02” will be returned to indicate the use of an illegal data
address.

Example : Read 8 discrete values from Modbus address 01, starting from first coil
(= coil 0)

H’01 H’01 H’00 H’00 H’00 H’08 H’?? H’??

First register
Slave Modbus
address to be read 8 bits to be read CRC
address function
= H’0000
Response (supposing value of coil
0 is 0 Least significant bit
1 is 1
2 is 1
3 is 0
4 is 1
5 is 0
6 is 0
7 is 1 Most significant bit )
Binary value is B’10010110, corresponding to hexadecimal H’96
Response frame :

H’01 H’01 H’01 H’96 2 bytes

Address Function Byte 1 byte of data CRC
count

Figure 5-3 : Formats and example for Modbus Function 01

5-4 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A MODBUS CONNECTION
Description of Modbus RTU Protocol

5.2.4.2 Reading Registers

Registers can be read using Function 03 or Function 04 of the Modbus protocol. Both
functions return the same result.

NOTE : A maximum of 127 registers can be requested at one time.

The Request and Response frame formats are shown in Figure 5-4.

Function 03 (Read Multiple Register)

Request frame
1 byte 1 byte 2 bytes 2 bytes 2 bytes
Slave Modbus First register address Number of words CRC
address function to be read (registers) to be read

Response Frame
1 byte 1 byte 1 byte n bytes 2 bytes
Address Function Byte Register values CRC
count

NOTE : When requesting a variable that is out of the range configured in the VM600,
the exception code “02” will be returned to indicate the use of an illegal data

Example : Read 1 register from Modbus address 01, starting from register 55 (decimal)

H’01 H’03 H’00 H’36 H’00 H’01 H’?? H’??

Slave Modbus First register address 1 register to be read CRC
address function to be read = H’0036
(See Note 1)

Note 1 :
Register 1 (decimal) has register address H’00
Register 17 (decimal) has register address H’10
Register 49 (decimal) has register address H’30
etc.
If the value of register 55 is 4660 (decimal), corresponding to hexadecimal H’1234, the
response will be as follows :

H’01 H’03 H’02 H’12 H’34 2 bytes

Address Function Byte Register value CRC
count

Figure 5-4 : Formats and example for Modbus Function 03

5.2.4.3 Error Handling

If an error occurs, the slave returns a message in which the Modbus function has its most
significant bit forced to “1” (see Figure 5-5) :

VM600 Networking Instruction Manual MAVM600-NET/E 5-5

Edition 2 - Mar 31/06
SETTING UP A MODBUS CONNECTION
Description of Modbus TCP Protocol

• Function 01 is replaced by Function 81

• Function 03 is replaced by Function 83
This is followed by one of the following exception codes :
• Exception code 01=Illegal function
• Exception code 02=Illegal data address

Error Handling

Example : Read 1 register from Modbus address 01, starting from register 256 (decimal)

H’01 H’03 H’00 H’FF H’00 H’01 H’?? H’??

Slave Modbus First register address 1 register to be read CRC
address function to be read = H’00FF
(See Note 1)

Note 1 :
Register 1 (decimal) has register address H’00
Register 17 (decimal) has register address H’10
Register 256 (decimal) has register address H’FF
etc.
Assuming register 256 does not exist, the response will be as follows :

H’01 H’83 H’02 2 bytes

Address Function Exception CRC
code

Figure 5-5 : Formats and example for error message

5.3 Description of Modbus TCP Protocol

The Modbus TCP protocol has exactly the same layout as the Modbus RTU protocol, with the
exception of the "framing" sequence check pattern (CRC) and the address interpretation.

NOTE : All requests are sent via TCP on registered port 502.

Requests are normally sent in half-duplex mode on a given connection. Effectively, there is
no benefit in sending additional requests on a single connection while a response is
outstanding.
The Modbus 'slave address' field is replaced by a single-byte 'Unit Identifier'. This may be
used to communicate via devices such as bridges and gateways which use a single IP
address to support multiple independent end units. The VM600 does not use this feature. In
the response, this field is always set to the received value, but it is not checked by the system.
The request and response are prefixed by six bytes as follows :
Byte 0 Transaction identifier - copied by server - usually 0
Byte 1 Transaction identifier - copied by server - usually 0
Byte 2 Protocol identifier = 0
Byte 3 Protocol identifier = 0

5-6 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A MODBUS CONNECTION
Definition of Registers

Byte 4 Length field (upper byte) = 0 (since all messages are smaller than 256)
Byte 5 Length field (lower byte) = number of bytes following
Byte 6 Unit identifier (previously 'slave address') - copied by server but ignored
Byte 7 Modbus function code
Byte 8 onwards Data as needed
Example :
If request is “Read 1 register at offset 55” and if returned value is decimal 4660 (=
hexadecimal H’1234), this would give :

TCP Modbus
Request : 00 00 00 00 00 06 0F 03 00 36 00 01
Response : 00 00 00 00 00 05 0F 03 02 12 34

Refer to Section 5.2 for examples of data.

Users familiar with Modbus RTU should note that the 'CRC-16' or 'LRC' check fields are NOT
needed in Modbus TCP. The TCP/IP and link layer (e.g. Ethernet) checksum mechanisms
are used instead to verify accurate delivery of the data packet.

5.4 Definition of Registers

The register allocation is defined in files that are read when the VM600 rack is started up.
These files are :
• mbcfg.2 For Modbus RTU communication through 9-pole RS-232 connector on front of
CPU M card
• mbcfg.3 For Modbus RTU communication through RS connector (RJ11-type) on
IOC N card
• mbcfg.tcp For Modbus TCP communication through Ethernet connector on IOC N
card
These files can be modified if required by editing them with a VT100 terminal (or emulator
from the Windows environment). Refer to Section 2.5 for further information.
Each file is organized in 7 columns (see Figure 5-6) :

Slot This is the number of the slot occupied by the DAU (data acquisition
unit, i.e. card) in the VM600 rack.
It can have a value of between 3 and 14.
DAU Indicates the type of card in the slot :
• MPC = MPC 4
• AMC = AMC 8
Output Defines the channel and/or output of the card in question. See
Section 5.4.1
Type Specifies whether the (analog) value returned is the actual measured
value or the full-scale setting defined for the output in question :
• VAL = Measured value
• FSD = Full-scale value

VM600 Networking Instruction Manual MAVM600-NET/E 5-7

Edition 2 - Mar 31/06
SETTING UP A MODBUS CONNECTION
Definition of Registers

STS/NOT Defines whether the discrete values concerning the output in question
are requested or not :
• STS = Values requested (NB : STS = status)
• NOT = Values not requested
Analog Reg. No. Register used for analog values concerning the output in question
Digital Reg. No. Register used for discrete (digital) values concerning the output in
question

The registers for analog values and discrete values are numbered sequentially and in
parallel. The configuration file is scanned, with the numbering of both sets of registers starting
at 1 (addressed as 0). Each time an analog register declaration or a discrete input is
encountered, the register number (current number) is incremented.

Current number

Discrete values
Analog values

Figure 5-6 : Extract from a typical configuration file

5.4.1 Parameters Concerning MPC 4 Cards

5.4.1.1 Definition of Outputs for MPC 4 Cards

The outputs listed in column 3 of the configuration file (see example in Figure 5-6) can have
11 possible values for MPC 4 cards, as defined in Table 5-2.

Output
Definition
Number

0 Measurement Channel 1, Output 1

1 Measurement Channel 1, Output 2
2 Measurement Channel 2, Output 1
3 Measurement Channel 2, Output 2
4 Measurement Channel 3, Output 1

Table 5-2 : Output channel coding for MPC 4 cards (Part 1 of 2)

5-8 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A MODBUS CONNECTION
Definition of Registers

Output
Definition
Number

5 Measurement Channel 3, Output 2

6 Measurement Channel 4, Output 1
7 Measurement Channel 4, Output 2
8 Dual Channel 1&2, Output 1
9 Dual Channel 3&4, Output 1
10 Speed Channel 1, Output 1
11 Speed Channel 2, Output 1

Table 5-2 : Output channel coding for MPC 4 cards (Part 2 of 2)

5.4.1.2 Analog Values (Registers)

Possible settings are :
• VAL Actual measured value
VAL is coded as a 16-bit signed value.
16383 represents 100% of the full-scale defined in the FSD register.
• FSD Full-scale value
FSD is coded as a 16-bit unsigned value
Example :
A value of 10000 is returned with a full-scale defined as 4.
(The physical unit is mm/s, but this information is not available via Modbus.)
The corresponding mechanical value is then calculated as follows :
(10000 / 16383) x 4 = 2.44 mm/s.

NOTE : The two speed values (outputs 10 and 11 in Table 5-2) are coded differently, i.e.
directly in RPM divided by 4.
To obtain RPM values, simply multiply the returned value by 4.

5.4.1.3 Discrete Values (Coils, Discrete Inputs)

The possible settings are :
• STS Status (values) requested
• NOT Status (values) not requested

VM600 Networking Instruction Manual MAVM600-NET/E 5-9

Edition 2 - Mar 31/06
SETTING UP A MODBUS CONNECTION
Definition of Registers

The map of all discrete values available for an output can be activated or not using the STS
or NOT indication. The 8 discrete values available for the output will be mapped as shown in
Table 5-3.

Bit Definition

b0 1 = Point is defined
(= LSB) 0 = Point is not defined
1 = Point is in Alarm+ condition
b1
0 = Point is not in Alarm+ condition
1 = Point is in Alarm- condition
b2
0 = Point is not in Alarm- condition
1 = Point is in Danger+ condition
b3
0 = Point is not in Danger+ condition
1 = Point is in Danger- condition
b4
0 = Point is not in Danger- condition
1 = OK status indicates no problem at the point
b5 0 = OK status indicates there is a problem at the
point
b6 Reserved
b7
Reserved
(= MSB)

Table 5-3 : Mapping of discrete values (MPC 4 card)

Discrete values are not available individually (e.g. you cannot request only bit b3). All 8 bits
have to be requested.

5.4.1.4 Table of Register Definitions

All registers are defined in Table 5-4.

Analog Discrete Additional

Output Type STS/NOT
Rack Card Register Register Numbers Information
Number (for (for
Slot (DAU) Number (& Hex. Addresses) Chan. = Channel,
(see Analog Discrete Dual = Dual
No. Type Registers) Registers)
(and Hex. (Sequence : Bits b0 - b7 Channel,
Table 5-2)
Address) of Table 5-3) O/P = Output

3 MPC 4 0 VAL STS 1 (H’0000) 1 - 8 (H’0000 - H’0007) Chan. 1, O/P 1

3 MPC 4 0 FSD NOT 2 (H’0001) Chan. 1, O/P 1

3 MPC 4 1 VAL STS 3 (H’0002) 9 - 16 (H’0008 - H’000F) Chan. 1, O/P 2

3 MPC 4 1 FSD NOT 4 (H’0003) Chan. 1, O/P 2

3 MPC 4 2 VAL STS 5 (H’0004) 17 - 24 (H’0010 - H’0017) Chan. 2, O/P 1

3 MPC 4 2 FSD NOT 6 (H’0005) Chan. 2, O/P 1

Table 5-4 : Modbus Register Definitions (Part 1 of 10)

5 - 10 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A MODBUS CONNECTION
Definition of Registers

Analog Discrete Additional

Output Type STS/NOT
Rack Card Register Register Numbers Information
Number (for (for
Slot (DAU) Number (& Hex. Addresses) Chan. = Channel,
(see Analog Discrete Dual = Dual
No. Type Registers) Registers)
(and Hex. (Sequence : Bits b0 - b7 Channel,
Table 5-2)
Address) of Table 5-3) O/P = Output

3 MPC 4 3 VAL STS 7 (H’0006) 25 - 32 (H’0018 - H’001F) Chan. 2, O/P 2

3 MPC 4 3 FSD NOT 8 (H’0007) Chan. 2, O/P 2

3 MPC 4 4 VAL STS 9 (H’0008) 33 - 40 (H’0020 - H’0027) Chan. 3, O/P 1

3 MPC 4 4 FSD NOT 10 (H’0009) Chan. 3, O/P 1

3 MPC 4 5 VAL STS 11 (H’000A) 41 - 48 (H’0028 - H’002F) Chan. 3, O/P 2

3 MPC 4 5 FSD NOT 12 (H’000B) Chan. 3, O/P 2

3 MPC 4 6 VAL STS 13 (H’000C) 49 - 56 (H’0030 - H’0037) Chan. 4, O/P 1

3 MPC 4 6 FSD NOT 14 (H’000D) Chan. 4, O/P 1

3 MPC 4 7 VAL STS 15 (H’000E) 57 - 64 (H’0038 - H’003F) Chan. 4, O/P 2

3 MPC 4 7 FSD NOT 16 (H’000F) Chan. 4, O/P 2

3 MPC 4 8 VAL STS 17 (H’0010) 65 - 72 (H’0040 - H’0047) Dual 1&2, O/P 1

3 MPC 4 8 FSD NOT 18 (H’0011) Dual 1&2, O/P 1

3 MPC 4 9 VAL STS 19 (H’0012) 73 - 80 (H’0048 - H’004F) Dual 3&4, O/P 1

3 MPC 4 9 FSD NOT 20 (H’0013) Dual 3&4, O/P 1

3 MPC 4 10 VAL STS 21 (H’0014) 81 - 88 (H’0050 - H’0057) Speed 1, O/P 1

3 MPC 4 11 VAL STS 22 (H’0015) 89 - 96 (H’0058 - H’005F) Speed 2, O/P 1

4 MPC 4 0 VAL STS 23 (H’0016) 97 - 104 (H’0060 - H’0067) Chan. 1, O/P 1

4 MPC 4 0 FSD NOT 24 (H’0017) Chan. 1, O/P 1

4 MPC 4 1 VAL STS 25 (H’0018) 105 - 112 (H’0068 - H’006F) Chan. 1, O/P 2

4 MPC 4 1 FSD NOT 26 (H’0019) Chan. 1, O/P 2

4 MPC 4 2 VAL STS 27 (H’001A) 113 - 120 (H’0070 - H’0077) Chan. 2, O/P 1

4 MPC 4 2 FSD NOT 28 (H’001B) Chan. 2, O/P 1

4 MPC 4 3 VAL STS 29 (H’001C) 121 - 128 (H’0078 - H’007F) Chan. 2, O/P 2

4 MPC 4 3 FSD NOT 30 (H’001D) Chan. 2, O/P 2

4 MPC 4 4 VAL STS 31 (H’001E) 129 - 136 (H’0080 - H’0087) Chan. 3, O/P 1

4 MPC 4 4 FSD NOT 32 (H’001F) Chan. 3, O/P 1

4 MPC 4 5 VAL STS 33 (H’0020) 137 - 144 (H’0088 - H’008F) Chan. 3, O/P 2

4 MPC 4 5 FSD NOT 34 (H’0021) Chan. 3, O/P 2

4 MPC 4 6 VAL STS 35 (H’0022) 145 - 152 (H’0090 - H’0097) Chan. 4, O/P 1

4 MPC 4 6 FSD NOT 36 (H’0023) Chan. 4, O/P 1

4 MPC 4 7 VAL STS 37 (H’0024) 153 - 160 (H’0098 - H’009F) Chan. 4, O/P 2

4 MPC 4 7 FSD NOT 38 (H’0025) Chan. 4, O/P 2

Table 5-4 : Modbus Register Definitions (Part 2 of 10)

VM600 Networking Instruction Manual MAVM600-NET/E 5 - 11

Edition 2 - Mar 31/06
SETTING UP A MODBUS CONNECTION
Definition of Registers

Analog Discrete Additional

Output Type STS/NOT
Rack Card Register Register Numbers Information
Number (for (for
Slot (DAU) Number (& Hex. Addresses) Chan. = Channel,
(see Analog Discrete Dual = Dual
No. Type Registers) Registers)
(and Hex. (Sequence : Bits b0 - b7 Channel,
Table 5-2)
Address) of Table 5-3) O/P = Output

4 MPC 4 8 VAL STS 39 (H’0026) 161 - 168 (H’00A0 - H’00A7) Dual 1&2, O/P 1

4 MPC 4 8 FSD NOT 40 (H’0027) Dual 1&2, O/P 1

4 MPC 4 9 VAL STS 41 (H’0028) 169 - 176 (H’00A8 - H’00AF) Dual 3&4, O/P 1

4 MPC 4 9 FSD NOT 42 (H’0029) Dual 3&4, O/P 1

4 MPC 4 10 VAL STS 43 (H’002A) 177 - 184 (H’00B0 - H’00B7) Speed 1, O/P 1

4 MPC 4 11 VAL STS 44 (H’002B) 185 - 192 (H’00B8 - H’00BF) Speed 2, O/P 1

5 MPC 4 0 VAL STS 45 (H’002C) 193 - 200 (H’00C0 - H’00C7) Chan. 1, O/P 1

5 MPC 4 0 FSD NOT 46 (H’002D) Chan. 1, O/P 1

5 MPC 4 1 VAL STS 47 (H’002E) 201 - 208 (H’00C8 - H’00CF) Chan. 1, O/P 2

5 MPC 4 1 FSD NOT 48 (H’002F) Chan. 1, O/P 2

5 MPC 4 2 VAL STS 49 (H’0030) 209 - 216 (H’00D0 - H’00D7) Chan. 2, O/P 1

5 MPC 4 2 FSD NOT 50 (H’0031) Chan. 2, O/P 1

5 MPC 4 3 VAL STS 51 (H’0032) 217 - 224 (H’00D8 - H’00DF) Chan. 2, O/P 2

5 MPC 4 3 FSD NOT 52 (H’0033) Chan. 2, O/P 2

5 MPC 4 4 VAL STS 53 (H’0034) 225 - 232 (H’00E0 - H’00E7) Chan. 3, O/P 1

5 MPC 4 4 FSD NOT 54 (H’0035) Chan. 3, O/P 1

5 MPC 4 5 VAL STS 55 (H’0036) 233 - 240 (H’00E8 - H’00EF) Chan. 3, O/P 2

5 MPC 4 5 FSD NOT 56 (H’0037) Chan. 3, O/P 2

5 MPC 4 6 VAL STS 57 (H’0038) 241 - 248 (H’00F0 - H’00F7) Chan. 4, O/P 1

5 MPC 4 6 FSD NOT 58 (H’0039) Chan. 4, O/P 1

5 MPC 4 7 VAL STS 59 (H’003A) 249 - 256 (H’00F8 - H’00FF) Chan. 4, O/P 2

5 MPC 4 7 FSD NOT 60 (H’003B) Chan. 4, O/P 2

5 MPC 4 8 VAL STS 61 (H’003C) 257 - 264 (H’0100 - H’0107) Dual 1&2, O/P 1

5 MPC 4 8 FSD NOT 62 (H’003D) Dual 1&2, O/P 1

5 MPC 4 9 VAL STS 63 (H’003E) 265 - 272 (H’0108 - H’010F) Dual 3&4, O/P 1

5 MPC 4 9 FSD NOT 64 (H’003F) Dual 3&4, O/P 1

5 MPC 4 10 VAL STS 65 (H’0040) 273 - 280 (H’0110 - H’0117) Speed 1, O/P 1

5 MPC 4 11 VAL STS 66 (H’0041) 281 - 288 (H’0118 - H’011F) Speed 2, O/P 1

6 MPC 4 0 VAL STS 67 (H’0042) 289 - 296 (H’0120 - H’0127) Chan. 1, O/P 1

6 MPC 4 0 FSD NOT 68 (H’0043) Chan. 1, O/P 1

6 MPC 4 1 VAL STS 69 (H’0044) 297 - 304 (H’0128 - H’012F) Chan. 1, O/P 2

Table 5-4 : Modbus Register Definitions (Part 3 of 10)

5 - 12 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A MODBUS CONNECTION
Definition of Registers

Analog Discrete Additional

Output Type STS/NOT
Rack Card Register Register Numbers Information
Number (for (for
Slot (DAU) Number (& Hex. Addresses) Chan. = Channel,
(see Analog Discrete Dual = Dual
No. Type Registers) Registers)
(and Hex. (Sequence : Bits b0 - b7 Channel,
Table 5-2)
Address) of Table 5-3) O/P = Output

6 MPC 4 1 FSD NOT 70 (H’0045) Chan. 1, O/P 2

6 MPC 4 2 VAL STS 71 (H’0046) 305 - 312 (H’0130 - H’0137) Chan. 2, O/P 1

6 MPC 4 2 FSD NOT 72 (H’0047) Chan. 2, O/P 1

6 MPC 4 3 VAL STS 73 (H’0048) 313 - 320 (H’0138 - H’013F) Chan. 2, O/P 2

6 MPC 4 3 FSD NOT 74 (H’0049) Chan. 2, O/P 2

6 MPC 4 4 VAL STS 75 (H’004A) 321 - 328 (H’0140 - H’0147) Chan. 3, O/P 1

6 MPC 4 4 FSD NOT 76 (H’004B) Chan. 3, O/P 1

6 MPC 4 5 VAL STS 77 (H’004C) 329 - 336 (H’0148 - H’014F) Chan. 3, O/P 2

6 MPC 4 5 FSD NOT 78 (H’004D) Chan. 3, O/P 2

6 MPC 4 6 VAL STS 79 (H’004E) 337 - 344 (H’0150 - H’0157) Chan. 4, O/P 1

6 MPC 4 6 FSD NOT 80 (H’004F) Chan. 4, O/P 1

6 MPC 4 7 VAL STS 81 (H’0050) 345 - 352 (H’0158 - H’015F) Chan. 4, O/P 2

6 MPC 4 7 FSD NOT 82 (H’0051) Chan. 4, O/P 2

6 MPC 4 8 VAL STS 83 (H’0052) 353 - 360 (H’0160 - H’0167) Dual 1&2, O/P 1

6 MPC 4 8 FSD NOT 84 (H’0053) Dual 1&2, O/P 1

6 MPC 4 9 VAL STS 85 (H’0054) 361 - 368 (H’0168 - H’016F) Dual 3&4, O/P 1

6 MPC 4 9 FSD NOT 86 (H’0055) Dual 3&4, O/P 1

6 MPC 4 10 VAL STS 87 (H’0056) 369 - 376 (H’0170 - H’0177) Speed 1, O/P 1

6 MPC 4 11 VAL STS 88 (H’0057) 377 - 384 (H’0178 - H’017F) Speed 2, O/P 1

7 MPC 4 0 VAL STS 89 (H’0058) 385 - 392 (H’0180 - H’0187) Chan. 1, O/P 1

7 MPC 4 0 FSD NOT 90 (H’0059) Chan. 1, O/P 1

7 MPC 4 1 VAL STS 91 (H’005A) 393 - 400 (H’0188 - H’018F) Chan. 1, O/P 2

7 MPC 4 1 FSD NOT 92 (H’005B) Chan. 1, O/P 2

7 MPC 4 2 VAL STS 93 (H’005C) 401 - 408 (H’0190 - H’0197) Chan. 2, O/P 1

7 MPC 4 2 FSD NOT 94 (H’005D) Chan. 2, O/P 1

7 MPC 4 3 VAL STS 95 (H’005E) 409 - 416 (H’0198 - H’019F) Chan. 2, O/P 2

7 MPC 4 3 FSD NOT 96 (H’005F) Chan. 2, O/P 2

7 MPC 4 4 VAL STS 97 (H’0060) 417 - 424 (H’01A0 - H’01A7) Chan. 3, O/P 1

7 MPC 4 4 FSD NOT 98 (H’0061) Chan. 3, O/P 1

7 MPC 4 5 VAL STS 99 (H’0062) 425 - 432 (H’01A8 - H’01AF) Chan. 3, O/P 2

7 MPC 4 5 FSD NOT 100 (H’0063) Chan. 3, O/P 2

Table 5-4 : Modbus Register Definitions (Part 4 of 10)

VM600 Networking Instruction Manual MAVM600-NET/E 5 - 13

Edition 2 - Mar 31/06
SETTING UP A MODBUS CONNECTION
Definition of Registers

Analog Discrete Additional

Output Type STS/NOT
Rack Card Register Register Numbers Information
Number (for (for
Slot (DAU) Number (& Hex. Addresses) Chan. = Channel,
(see Analog Discrete Dual = Dual
No. Type Registers) Registers)
(and Hex. (Sequence : Bits b0 - b7 Channel,
Table 5-2)
Address) of Table 5-3) O/P = Output

7 MPC 4 6 VAL STS 101 (H’0064) 433 - 440 (H’01B0 - H’01B7) Chan. 4, O/P 1

7 MPC 4 6 FSD NOT 102 (H’0065) Chan. 4, O/P 1

7 MPC 4 7 VAL STS 103 (H’0066) 441 - 448 (H’01B8 - H’01BF) Chan. 4, O/P 2

7 MPC 4 7 FSD NOT 104 (H’0067) Chan. 4, O/P 2

7 MPC 4 8 VAL STS 105 (H’0068) 449 - 456 (H’01C0 - H’01C7) Dual 1&2, O/P 1

7 MPC 4 8 FSD NOT 102 (H’0069) Dual 1&2, O/P 1

7 MPC 4 9 VAL STS 107 (H’006A) 457 - 464 (H’01C8 - H’01CF) Dual 3&4, O/P 1

7 MPC 4 9 FSD NOT 108 (H’006B) Dual 3&4, O/P 1

7 MPC 4 10 VAL STS 109 (H’006C) 465 - 472 (H’01D0 - H’01D7) Speed 1, O/P 1

7 MPC 4 11 VAL STS 110 (H’006D) 473 - 480 (H’01D8 - H’01DF) Speed 2, O/P 1

8 MPC 4 0 VAL STS 111 (H’006E) 481 - 488 (H’01E0 - H’01E7) Chan. 1, O/P 1

8 MPC 4 0 FSD NOT 112 (H’006F) Chan. 1, O/P 1

8 MPC 4 1 VAL STS 113 (H’0070) 489 - 496 (H’01E8 - H’01EF) Chan. 1, O/P 2

8 MPC 4 1 FSD NOT 114 (H’0071) Chan. 1, O/P 2

8 MPC 4 2 VAL STS 115 (H’0072) 497 - 504 (H’01F0 - H’01F7) Chan. 2, O/P 1

8 MPC 4 2 FSD NOT 116 (H’0073) Chan. 2, O/P 1

8 MPC 4 3 VAL STS 117 (H’0074) 505 - 512 (H’01F8 - H’01FF) Chan. 2, O/P 2

8 MPC 4 3 FSD NOT 118 (H’0075) Chan. 2, O/P 2

8 MPC 4 4 VAL STS 119 (H’0076) 513 - 520 (H’0200 - H’0207) Chan. 3, O/P 1

8 MPC 4 4 FSD NOT 120 (H’0077) Chan. 3, O/P 1

8 MPC 4 5 VAL STS 121 (H’0078) 521 - 528 (H’0208 - H’020F) Chan. 3, O/P 2

8 MPC 4 5 FSD NOT 122 (H’0079) Chan. 3, O/P 2

8 MPC 4 6 VAL STS 123 (H’007A) 529 - 536 (H’0210 - H’0217) Chan. 4, O/P 1

8 MPC 4 6 FSD NOT 124 (H’007B) Chan. 4, O/P 1

8 MPC 4 7 VAL STS 125 (H’007C) 537 - 544 (H’0218 - H’021F) Chan. 4, O/P 2

8 MPC 4 7 FSD NOT 126 (H’007D) Chan. 4, O/P 2

8 MPC 4 8 VAL STS 127 (H’007E) 545 - 552 (H’0220 - H’0227) Dual 1&2, O/P 1

8 MPC 4 8 FSD NOT 128 (H’007F) Dual 1&2, O/P 1

8 MPC 4 9 VAL STS 129 (H’0080) 553 - 560 (H’0228 - H’022F) Dual 3&4, O/P 1

8 MPC 4 9 FSD NOT 130 (H’0081) Dual 3&4, O/P 1

8 MPC 4 10 VAL STS 131 (H’0082) 561 - 568 (H’0230 - H’0237) Speed 1, O/P 1

8 MPC 4 11 VAL STS 132 (H’0083) 569 - 576 (H’0238 - H’023F) Speed 2, O/P 1

Table 5-4 : Modbus Register Definitions (Part 5 of 10)

5 - 14 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A MODBUS CONNECTION
Definition of Registers

Analog Discrete Additional

Output Type STS/NOT
Rack Card Register Register Numbers Information
Number (for (for
Slot (DAU) Number (& Hex. Addresses) Chan. = Channel,
(see Analog Discrete Dual = Dual
No. Type Registers) Registers)
(and Hex. (Sequence : Bits b0 - b7 Channel,
Table 5-2)
Address) of Table 5-3) O/P = Output

9 MPC 4 0 VAL STS 133 (H’0084) 577 - 584 (H’0240 - H’0247) Chan. 1, O/P 1

9 MPC 4 0 FSD NOT 134 (H’0085) Chan. 1, O/P 1

9 MPC 4 1 VAL STS 135 (H’0086) 585 - 592 (H’0248 - H’024F) Chan. 1, O/P 2

9 MPC 4 1 FSD NOT 136 (H’0087) Chan. 1, O/P 2

9 MPC 4 2 VAL STS 137 (H’0088) 593 - 600 (H’0250 - H’0257) Chan. 2, O/P 1

9 MPC 4 2 FSD NOT 138 (H’0089) Chan. 2, O/P 1

9 MPC 4 3 VAL STS 139 (H’008A) 601 - 608 (H’0258 - H’025F) Chan. 2, O/P 2

9 MPC 4 3 FSD NOT 140 (H’008B) Chan. 2, O/P 2

9 MPC 4 4 VAL STS 141 (H’008C) 609 - 616 (H’0260 - H’0267) Chan. 3, O/P 1

9 MPC 4 4 FSD NOT 142 (H’008D) Chan. 3, O/P 1

9 MPC 4 5 VAL STS 143 (H’008E) 617 - 624 (H’0268 - H’026F) Chan. 3, O/P 2

9 MPC 4 5 FSD NOT 144 (H’008F) Chan. 3, O/P 2

9 MPC 4 6 VAL STS 145 (H’0090) 625 - 632 (H’0270 - H’0277) Chan. 4, O/P 1

9 MPC 4 6 FSD NOT 146 (H’0091) Chan. 4, O/P 1

9 MPC 4 7 VAL STS 147 (H’0092) 633 - 640 (H’0278 - H’027F) Chan. 4, O/P 2

9 MPC 4 7 FSD NOT 148 (H’0093) Chan. 4, O/P 2

9 MPC 4 8 VAL STS 149 (H’0094) 641 - 648 (H’0280 - H’0287) Dual 1&2, O/P 1

9 MPC 4 8 FSD NOT 150 (H’0095) Dual 1&2, O/P 1

9 MPC 4 9 VAL STS 151 (H’0096) 649 - 656 (H’0288 - H’028F) Dual 3&4, O/P 1

9 MPC 4 9 FSD NOT 152 (H’0097) Dual 3&4, O/P 1

9 MPC 4 10 VAL STS 153 (H’0098) 657 - 664 (H’0290 - H’0297) Speed 1, O/P 1

9 MPC 4 11 VAL STS 154 (H’0099) 665 - 672 (H’0298 - H’029F) Speed 2, O/P 1

10 MPC 4 0 VAL STS 155 (H’009A) 673 - 680 (H’02A0 - H’02A7) Chan. 1, O/P 1

10 MPC 4 0 FSD NOT 156 (H’009B) Chan. 1, O/P 1

10 MPC 4 1 VAL STS 157 (H’009C) 681 - 688 (H’02A8 - H’02AF) Chan. 1, O/P 2

10 MPC 4 1 FSD NOT 158 (H’009D) Chan. 1, O/P 2

10 MPC 4 2 VAL STS 159 (H’009E) 689 - 696 (H’02B0 - H’02B7) Chan. 2, O/P 1

10 MPC 4 2 FSD NOT 160 (H’009F) Chan. 2, O/P 1

10 MPC 4 3 VAL STS 161 (H’00A0) 697 - 704 (H’02B8 - H’02BF) Chan. 2, O/P 2

10 MPC 4 3 FSD NOT 162 (H’00A1) Chan. 2, O/P 2

10 MPC 4 4 VAL STS 163 (H’00A2) 705 - 712 (H’02C0 - H’02C7) Chan. 3, O/P 1

Table 5-4 : Modbus Register Definitions (Part 6 of 10)

VM600 Networking Instruction Manual MAVM600-NET/E 5 - 15

Edition 2 - Mar 31/06
SETTING UP A MODBUS CONNECTION
Definition of Registers

Analog Discrete Additional

Output Type STS/NOT
Rack Card Register Register Numbers Information
Number (for (for
Slot (DAU) Number (& Hex. Addresses) Chan. = Channel,
(see Analog Discrete Dual = Dual
No. Type Registers) Registers)
(and Hex. (Sequence : Bits b0 - b7 Channel,
Table 5-2)
Address) of Table 5-3) O/P = Output

10 MPC 4 4 FSD NOT 164 (H’00A3) Chan. 3, O/P 1

10 MPC 4 5 VAL STS 165 (H’00A4) 713 - 720 (H’02C8 - H’02CF) Chan. 3, O/P 2

10 MPC 4 5 FSD NOT 166 (H’00A5) Chan. 3, O/P 2

10 MPC 4 6 VAL STS 167 (H’00A6) 721 - 728 (H’02D0 - H’02D7) Chan. 4, O/P 1

10 MPC 4 6 FSD NOT 168 (H’00A7) Chan. 4, O/P 1

10 MPC 4 7 VAL STS 169 (H’00A8) 729 - 736 (H’02D8 - H’02DF) Chan. 4, O/P 2

10 MPC 4 7 FSD NOT 170 (H’00A9) Chan. 4, O/P 2

10 MPC 4 8 VAL STS 171 (H’00AA) 737 - 744 (H’02E0 - H’02E7) Dual 1&2, O/P 1

10 MPC 4 8 FSD NOT 172 (H’00AB) Dual 1&2, O/P 1

10 MPC 4 9 VAL STS 173 (H’00AC) 745 - 752 (H’02E8 - H’02EF) Dual 3&4, O/P 1

10 MPC 4 9 FSD NOT 174 (H’00AD) Dual 3&4, O/P 1

10 MPC 4 10 VAL STS 175 (H’00AE) 753 - 760 (H’02F0 - H’02F7) Speed 1, O/P 1

10 MPC 4 11 VAL STS 176 (H’00AF) 761 - 768 (H’02F8 - H’02FF) Speed 2, O/P 1

11 MPC 4 0 VAL STS 177 (H’00B0) 769 - 776 (H’0300 - H’0307) Chan. 1, O/P 1

11 MPC 4 0 FSD NOT 178 (H’00B1) Chan. 1, O/P 1

11 MPC 4 1 VAL STS 179 (H’00B2) 777 - 784 (H’0308 - H’030F) Chan. 1, O/P 2

11 MPC 4 1 FSD NOT 180 (H’00B3) Chan. 1, O/P 2

11 MPC 4 2 VAL STS 181 (H’00B4) 785 - 792 (H’0310 - H’0317) Chan. 2, O/P 1

11 MPC 4 2 FSD NOT 182 (H’00B5) Chan. 2, O/P 1

11 MPC 4 3 VAL STS 183 (H’00B6) 793 - 800 (H’0318 - H’031F) Chan. 2, O/P 2

11 MPC 4 3 FSD NOT 184 (H’00B7) Chan. 2, O/P 2

11 MPC 4 4 VAL STS 185 (H’00B8) 801 - 808 (H’0320 - H’0327) Chan. 3, O/P 1

11 MPC 4 4 FSD NOT 186 (H’00B9) Chan. 3, O/P 1

11 MPC 4 5 VAL STS 187 (H’00BA) 809 - 816 (H’0328 - H’032F) Chan. 3, O/P 2

11 MPC 4 5 FSD NOT 188 (H’00BB) Chan. 3, O/P 2

11 MPC 4 6 VAL STS 189 (H’00BC) 817 - 824 (H’0330 - H’0337) Chan. 4, O/P 1

11 MPC 4 6 FSD NOT 190 (H’00BD) Chan. 4, O/P 1

11 MPC 4 7 VAL STS 191 (H’00BE) 825 - 832 (H’0338 - H’033F) Chan. 4, O/P 2

11 MPC 4 7 FSD NOT 192 (H’00BF) Chan. 4, O/P 2

11 MPC 4 8 VAL STS 193 (H’00C0) 833 - 840 (H’0340 - H’0347) Dual 1&2, O/P 1

11 MPC 4 8 FSD NOT 194 (H’00C1) Dual 1&2, O/P 1

Table 5-4 : Modbus Register Definitions (Part 7 of 10)

5 - 16 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A MODBUS CONNECTION
Definition of Registers

Analog Discrete Additional

Output Type STS/NOT
Rack Card Register Register Numbers Information
Number (for (for
Slot (DAU) Number (& Hex. Addresses) Chan. = Channel,
(see Analog Discrete Dual = Dual
No. Type Registers) Registers)
(and Hex. (Sequence : Bits b0 - b7 Channel,
Table 5-2)
Address) of Table 5-3) O/P = Output

11 MPC 4 9 VAL STS 195 (H’00C2) 841 - 848 (H’0348 - H’034F) Dual 3&4, O/P 1

11 MPC 4 9 FSD NOT 196 (H’00C3) Dual 3&4, O/P 1

11 MPC 4 10 VAL STS 197 (H’00C4) 849 - 856 (H’0350 - H’0357) Speed 1, O/P 1

11 MPC 4 11 VAL STS 198 (H’00C5) 857 - 864 (H’0358 - H’035F) Speed 2, O/P 1

12 MPC 4 0 VAL STS 199 (H’00C6) 865 - 872 (H’0360 - H’0367) Chan. 1, O/P 1

12 MPC 4 0 FSD NOT 200 (H’00C7) Chan. 1, O/P 1

12 MPC 4 1 VAL STS 201 (H’00C8) 873 - 880 (H’0368 - H’036F) Chan. 1, O/P 2

12 MPC 4 1 FSD NOT 202 (H’00C9) Chan. 1, O/P 2

12 MPC 4 2 VAL STS 203 (H’00CA) 881 - 888 (H’0370 - H’0377) Chan. 2, O/P 1

12 MPC 4 2 FSD NOT 204 (H’00CB) Chan. 2, O/P 1

12 MPC 4 3 VAL STS 205 (H’00CC) 889 - 896 (H’0378 - H’037F) Chan. 2, O/P 2

12 MPC 4 3 FSD NOT 206 (H’00CD) Chan. 2, O/P 2

12 MPC 4 4 VAL STS 207 (H’00CE) 897 - 904 (H’0380 - H’0387) Chan. 3, O/P 1

12 MPC 4 4 FSD NOT 208 (H’00CF) Chan. 3, O/P 1

12 MPC 4 5 VAL STS 209 (H’00D0) 905 - 912 (H’0388 - H’038F) Chan. 3, O/P 2

12 MPC 4 5 FSD NOT 210 (H’00D1) Chan. 3, O/P 2

12 MPC 4 6 VAL STS 211 (H’00D2) 913 - 920 (H’0390 - H’0397) Chan. 4, O/P 1

12 MPC 4 6 FSD NOT 212 (H’00D3) Chan. 4, O/P 1

12 MPC 4 7 VAL STS 213 (H’00D4) 921 - 928 (H’0398 - H’039F) Chan. 4, O/P 2

12 MPC 4 7 FSD NOT 214 (H’00D5) Chan. 4, O/P 2

12 MPC 4 8 VAL STS 215 (H’00D6) 929 - 936 (H’03A0 - H’03A7) Dual 1&2, O/P 1

12 MPC 4 8 FSD NOT 216 (H’00D7) Dual 1&2, O/P 1

12 MPC 4 9 VAL STS 217 (H’00D8) 937 - 944 (H’03A8 - H’03AF) Dual 3&4, O/P 1

12 MPC 4 9 FSD NOT 218 (H’00D9) Dual 3&4, O/P 1

12 MPC 4 10 VAL STS 219 (H’00DA) 945 - 952 (H’03B0 - H’03B7) Speed 1, O/P 1

12 MPC 4 11 VAL STS 220 (H’00DB) 953 - 960 (H’03B8 - H’03BF) Speed 2, O/P 1

13 MPC 4 0 VAL STS 221 (H’00DC) 961 - 968 (H’03C0 - H’03C7) Chan. 1, O/P 1

13 MPC 4 0 FSD NOT 222 (H’00DD) Chan. 1, O/P 1

13 MPC 4 1 VAL STS 223 (H’00DE) 969 - 976 (H’03C8 - H’03CF) Chan. 1, O/P 2

13 MPC 4 1 FSD NOT 224 (H’00DF) Chan. 1, O/P 2

13 MPC 4 2 VAL STS 225 (H’00E0) 977 - 984 (H’03D0 - H’03D7) Chan. 2, O/P 1

Table 5-4 : Modbus Register Definitions (Part 8 of 10)

VM600 Networking Instruction Manual MAVM600-NET/E 5 - 17

Edition 2 - Mar 31/06
SETTING UP A MODBUS CONNECTION
Definition of Registers

Analog Discrete Additional

Output Type STS/NOT
Rack Card Register Register Numbers Information
Number (for (for
Slot (DAU) Number (& Hex. Addresses) Chan. = Channel,
(see Analog Discrete Dual = Dual
No. Type Registers) Registers)
(and Hex. (Sequence : Bits b0 - b7 Channel,
Table 5-2)
Address) of Table 5-3) O/P = Output

13 MPC 4 2 FSD NOT 226 (H’00E1) Chan. 2, O/P 1

13 MPC 4 3 VAL STS 227 (H’00E2) 985 - 992 (H’03D8 - H’03DF) Chan. 2, O/P 2

13 MPC 4 3 FSD NOT 228 (H’00E3) Chan. 2, O/P 2

13 MPC 4 4 VAL STS 229 (H’00E4) 993 - 1000 (H’03E0 - H’03E7) Chan. 3, O/P 1

13 MPC 4 4 FSD NOT 230 (H’00E5) Chan. 3, O/P 1

13 MPC 4 5 VAL STS 231 (H’00E6) 1001 - 1008 (H’03E8 - H’03EF) Chan. 3, O/P 2

13 MPC 4 5 FSD NOT 232 (H’00E7) Chan. 3, O/P 2

13 MPC 4 6 VAL STS 233 (H’00E8) 1009 - 1016 (H’03F0 - H’03F7) Chan. 4, O/P 1

13 MPC 4 6 FSD NOT 234 (H’00E9) Chan. 4, O/P 1

13 MPC 4 7 VAL STS 235 (H’00EA) 1017 - 1024 (H’03F8 - H’03FF) Chan. 4, O/P 2

13 MPC 4 7 FSD NOT 236 (H’00EB) Chan. 4, O/P 2

13 MPC 4 8 VAL STS 237 (H’00EC) 1025 - 1032 (H’0400 - H’0407) Dual 1&2, O/P 1

13 MPC 4 8 FSD NOT 238 (H’00ED) Dual 1&2, O/P 1

13 MPC 4 9 VAL STS 239 (H’00EE) 1033 - 1040 (H’0408 - H’040F) Dual 3&4, O/P 1

13 MPC 4 9 FSD NOT 240 (H’00EF) Dual 3&4, O/P 1

13 MPC 4 10 VAL STS 241 (H’00F0) 1041 - 1048 (H’0410 - H’0417) Speed 1, O/P 1

13 MPC 4 11 VAL STS 242 (H’00F1) 1049 - 1056 (H’0418 - H’041F) Speed 2, O/P 1

14 MPC 4 0 VAL STS 243 (H’00F2) 1057 - 1064 (H’0420 - H’0427) Chan. 1, O/P 1

14 MPC 4 0 FSD NOT 244 (H’00F3) Chan. 1, O/P 1

14 MPC 4 1 VAL STS 245 (H’00F4) 1065 - 1072 (H’0428 - H’042F) Chan. 1, O/P 2

14 MPC 4 1 FSD NOT 246 (H’00F5) Chan. 1, O/P 2

14 MPC 4 2 VAL STS 247 (H’00F6) 1073 - 1080 (H’0430 - H’0437) Chan. 2, O/P 1

14 MPC 4 2 FSD NOT 248 (H’00F7) Chan. 2, O/P 1

14 MPC 4 3 VAL STS 249 (H’00F8) 1081 - 1088 (H’0438 - H’043F) Chan. 2, O/P 2

14 MPC 4 3 FSD NOT 250 (H’00F9) Chan. 2, O/P 2

14 MPC 4 4 VAL STS 251 (H’00FA) 1089 - 1096 (H’0440 - H’0447) Chan. 3, O/P 1

14 MPC 4 4 FSD NOT 252 (H’00FB) Chan. 3, O/P 1

14 MPC 4 5 VAL STS 253 (H’00FC) 1097 - 1104 (H’0448 - H’044F) Chan. 3, O/P 2

14 MPC 4 5 FSD NOT 254 (H’00FD) Chan. 3, O/P 2

14 MPC 4 6 VAL STS 255 (H’00FE) 1105 - 1112 (H’0450 - H’0457) Chan. 4, O/P 1

14 MPC 4 6 FSD NOT 256 (H’00FF) Chan. 4, O/P 1

14 MPC 4 7 VAL STS 257 (H’0100) 1113 - 1120 (H’0458 - H’045F) Chan. 4, O/P 2

Table 5-4 : Modbus Register Definitions (Part 9 of 10)

5 - 18 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 SETTING UP A MODBUS CONNECTION
Definition of Registers

Analog Discrete Additional

Output Type STS/NOT
Rack Card Register Register Numbers Information
Number (for (for
Slot (DAU) Number (& Hex. Addresses) Chan. = Channel,
(see Analog Discrete Dual = Dual
No. Type Registers) Registers)
(and Hex. (Sequence : Bits b0 - b7 Channel,
Table 5-2)
Address) of Table 5-3) O/P = Output

14 MPC 4 7 FSD NOT 258 (H’0101) Chan. 4, O/P 2

14 MPC 4 8 VAL STS 259 (H’0102) 1121 - 1128 (H’0460 - H’0467) Dual 1&2, O/P 1

14 MPC 4 8 FSD NOT 260 (H’0103) Dual 1&2, O/P 1

14 MPC 4 9 VAL STS 261 (H’0104) 1129 - 1136 (H’0468 - H’046F) Dual 3&4, O/P 1

14 MPC 4 9 FSD NOT 262 (H’0105) Dual 3&4, O/P 1

14 MPC 4 10 VAL STS 263 (H’0106) 1137 - 1144 (H’0470 - H’0477) Speed 1, O/P 1

14 MPC 4 11 VAL STS 264 (H’0107) 1145 - 1152 (H’0478 - H’047F) Speed 2, O/P 1

Table 5-4 : Modbus Register Definitions (Part 10 of 10)

VM600 Networking Instruction Manual MAVM600-NET/E 5 - 19

Edition 2 - Mar 31/06
SETTING UP A MODBUS CONNECTION
Definition of Registers

THIS PAGE INTENTIONALLY LEFT BLANK

5 - 20 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 TECHNICAL SUPPORT AND REPAIRS
Technical Support

6 TECHNICAL SUPPORT AND REPAIRS

6.1 Technical Support

For technical advice, spare parts, troubleshooting site visits and general enquiries, customers
should contact their local I&M Division representative. Your nearest representative can be
found on the Vibro-Meter web site :
www.vibro-meter.com
Alternatively, customers can contact :
Vibro-Meter SA
Attn: I&M Customer Support
Route de Moncor 4
P. O. Box
CH-1701 Fribourg
Switzerland
Phone : +41 26 407 11 11 (Switchboard)
Fax : +41 26 407 15 55 (General Customer Support)
E-mail addresses :
support@vibro-meter.com (General Customer Support)
techsupport.ch@vibro-meter.com (Technical Support)
techpubs.ch@vibro-meter.com (Technical Documentation)

6.2 Repairs
For warranty repairs and replacements, customers should contact their local I&M Division
representative. Your nearest representative can be found on the Vibro-Meter web site :
www.vibro-meter.com

Alternatively, customers can contact :

Vibro-Meter SA
Attn: Repairs Department
Route de Moncor 4
P. O. Box
CH-1701 Fribourg
Switzerland
Phone : +41 26 407 13 43 (Direct)
Fax : +41 26 407 17 05 (Direct)
E-mail : repairs.ch@vibro-meter.com

VM600 Networking Instruction Manual MAVM600-NET/E 6-1

Edition 2 - Mar 31/06
TECHNICAL SUPPORT AND REPAIRS
Repairs

THIS PAGE INTENTIONALLY LEFT BLANK

6-2 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 ABBREVIATIONS
Table A-1 defines the abbreviations found in this manual as well as in associated Vibro-Meter
documentation.

CMS Condition Monitoring System

CRC Cyclic Redundancy Check

DCS Distributed Control System

IP Internet Protocol

IPX Internetwork Packet Exchange

LAN Local Area Network

MPS Machinery Protection System

NetBEUI A proprietary Microsoft networking protocol

NIC Network Interface Card

NOS Network Operating System

PLC Programmable Logic Controller

PPP Point-to-Point Protocol

RAS Remote Access Service

RTU (Modbus) Remote Terminal Unit

SCADA Supervisory Control and Data Acquisition

SLIP Serial Line Internet Protocol

STP Shielded Twisted Pair

TCP/IP Transmission Control Protocol / Internet Protocol

UTP Unshielded Twisted Pair

WAN Wide Area Network

Table A-1 : List of abbreviations

VM600 Networking Instruction Manual MAVM600-NET/E A-1

Edition 2 - Mar 31/06
 THIS PAGE INTENTIONALLY LEFT BLANK

A-2 VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 PRODUCT DEFECT REPORT
Should you have any problem with your Vibro-Meter product, please contact your Vibro-Meter agent. You
may need to return a defective unit to Vibro-Meter. If you do, please photocopy then fill in this form (in
English) and attach it to the defective unit. Your completed Product Defect Report is important
because it can help us rapidly solve the problem.

NOTE : Always provide a filled-in photocopy of the Product Defect Report for each defective unit. The
report must accompany the unit at all times.

Contact Details: You or the designated Contact Person for your company.
Name Job Title
Company Email
Address
Country Post Code
Telephone Fax
Signature Date

Product Details: Plug-in modules display Product Detail information on a sticker pasted on the unit.
Module type:
Serial number (S/N): Part number (P/N):
Vibro-Meter order number:
Date of purchase: Site where used:

Problems Observed:

(Please continue on back of sheet if necessary)

Is the problem (put an ⌧ where appropriate) :
Always evident ? Intermittent ? Temperature dependent?

VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
Please use this space for any additional information: ¨

VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
 DOCUMENT EVALUATION FORM
Vibro-Meter welcomes your evaluation of this document. Your comments and suggestions help us
improve the quality of our documentation.
Document Title VM600 Networking Instruction Manual :

Date of
Reference : MAVM600-NET/E Edition : Edition 2 Mar 31/06
Issue :

Circle Yes or No to answer the following questions:

• Is the document well organized? Yes No
• Is the information technically accurate? Yes No
• Would you like more technical detail? Yes No
• Are the instructions clear and complete? Yes No
• Are the descriptions easy to understand? Yes No
• Are the examples and diagrams/photos helpful? Yes No
• Are there enough examples and diagrams/photos? Yes No
• Is the style/wording easy to read? Yes No
• Is any information not included? (please list in “Comments” below) Yes No
Comments

(Please continue on back of sheet if necessary)

Contact Details: You or the designated Contact Person for your company:
Name Job Title
Company Email
Address
Signature Date
Please mail, email or fax this document evaluation form to:
Technical Publications
Vibro-Meter SA
Route de Moncor 4
1701 Fribourg, Switzerland
web: www.vibro-meter.com , email: techpubs.ch@vibro-meter.com, Fax: +41 (0)26 407 15 55

VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06
Please use this space for any additional comments:

VM600 Networking Instruction Manual MAVM600-NET/E

Edition 2 - Mar 31/06