Micro-informatique

Industrielle & scientifique

User Guide

March 2011 Edition

e-mail : inIosaphir.Ir - http://www.saphir.Ir
50, Rue du Mail 38530 BARRAUX FRANCE
Tel. : 33 (0) 438 92 15 50 Fax : 33 (0) 476 45 12 55
SAS au capital de 400 000 t - RCS GRENOBLE 352 293 898 SIRET 00032 APE 6202A
N d`identiIication Intracommunautaire FR 67 352293898
Foreword - SoItware conIiguration

ModBusVIEWoTCP - User Guide 2/29
www.saphir.Ir
CONTENTS

1. FOREWORD............................................................................................................................................................. 3
2. CONFIGURATION................................................................................................................................................... 4
2.1. SOFTWARE CONFIGURATION............................................................................................................................... 4
2.2. HARDWARE : NETWORK CONNECTION................................................................................................................. 4
3. MODBUSVIEWOTCP.............................................................................................................................................. 5
3.1. MODBUSVIEWOTCP WITHIN LABVIEW .......................................................................................................... 5
4. MODBUSVIEWOTCP COMPONENTS ................................................................................................................ 6
4.1. FOREWORD AND WRITING CONVENTIONS............................................................................................................ 6
4.2. CLIENT TOOLS..................................................................................................................................................... 6
4.2.1- open ............................................................................................................................................................... 6
4.2.2- close............................................................................................................................................................... 7
4.2.3- requests JIs ................................................................................................................................................... 7
4.2.4- Advanced palette ......................................................................................................................................... 11
4.2.5- EZ Coding JIs ............................................................................................................................................. 12
4.3. SERVER TOOLS.................................................................................................................................................. 13
4.3.1- connections scanning................................................................................................................................... 13
4.3.2- requests management .................................................................................................................................. 14
4.4. TOOLS............................................................................................................................................................... 18
4.4.1- ModBusJIEW over TCP Client ................................................................................................................... 19
4.4.2- ModBusJIEW over TCP Server .................................................................................................................. 21
5. MODBUSVIEW ACTIVATION............................................................................................................................ 23
6. MODBUSVIEW SUPPORT................................................................................................................................... 24
7. MODBUSVIEW DRIVER ERRORS .................................................................................................................... 25
7.1. SPECIFIC ERRORS .............................................................................................................................................. 25
7.2. EXCEPTION CODES ............................................................................................................................................ 25
8. FREQUENTLY ASKED QUESTIONS................................................................................................................. 26

Foreword - SoItware conIiguration
3/29
www.saphir.Ir
1. FOREWORD
TCP/IP ModBus protocol is a communication protocol based on a client server structure. The
network can be composed oI several clients and several servers connected with a RJ45 link. One or
several ModBus networks can be implemented on a same platIorm.
Through this protocol, only the client can prompt the exchange with the server by sending a
request and waiting Ior an answer. The validity oI the communication is controlled by the TCP/IP
layer.
ModBusVIEWoTCP driver encapsulates all these layers in order to make it easy Ior the developer
to insert a computer, as client or server, within such a network.
The Iollowing Iunctionalities, hidden to the user, are managed:
- Link and Network low layers oI ModBus procedure
- Encoding/decoding ModBus Irames
- Frames control through identiIication and timeout
- TCP/IP communication management
ConIiguration - SoItware conIiguration

ModBusVIEWoTCP - User Guide 4/29
www.saphir.Ir
2. CONFIGURATION
2.1. SOFTWARE CONFIGURATION
ModBusJIEWoTCP driver runs under the Iollowing LabVIEW:
- 2010

And on the Iollowing platIorms:
- PC under Windows 9x / 2000 / Me / NT 4.0 / XP / Linux
- RT system (Real Time)
2.2. HARDWARE : NETWORK CONNECTION
There are 2 ways to connect a computer to an Ethernet ModBus network:
- Point to point link :
The computer and the equipment are networked through a crossed Ethernet wire.
- Ethernet network :
The computer is connected to an existing network through a straight Ethernet wire.

Contact us Ior Iurther inIormation concerning Iormer LabVIEW versions.

MODBUSVIEWoTCP - ModBusVIEWoTCP within LabVIEW
5/29
www.saphir.Ir
3. MODBUSVIEWOTCP
3.1. MODBUSVIEWOTCP WITHIN LABVIEW
ModBusJIEWoTCP driver installation adds the ModBusViEWoTCP palette to LabVIEW
Iunctions palette.













Figure 1 : ModBusVIEWoTCP within LabVIEW functions palette

MODBUSVIEWoTCP components - Foreword and writing conventions

ModBusVIEWoTCP - User Guide 6/29
www.saphir.Ir
4. MODBUSVIEWOTCP COMPONENTS
4.1. FOREWORD AND WRITING CONVENTIONS
The set oI VIs that composes ModBusVIEWoTCP driver Iollows the connector model below:

Figure 2 : Connector model of ModBusVIEWoTCP driver
error in describes the error conditions Iound beIore the VI. The deIault value corresponds to "no
error". II an error is transmitted to the error in input oI the VI, this error is relayed to error out
without the VI executing its Iunction. II an error occurs when the Iunction is running, this error is
automatically relayed to error out.
The connectors respect LabVIEW conventions as Iollows:
- The label connectorname (x) means x is the deIault value associated with this connector iI no
other value is conveyed to its Input.
- The connectors which names appear in bold in the context help oI a VI, must be wired.
Otherwise the caller vi will not be able to run (broken arrow).
4.2. CLIENT TOOLS
This chapter describes the VIs to use to realise a client Ior a ModBus network. These VIs are
Iound in the Functions palette by selecting Functions ~ SAPHIR ~ ModBusVIEWoTCP ~
ClientTools.

Figure 3 : Clients VIs palette
4.2.1- OPEN

MODBUSVIEWoTCP components - Client tools
7/29
www.saphir.Ir
Figure 4 : MBVTCP_open.vi
This VI initializes the TCP/IP communication described by Aetwork. AetRef1CP out, unique
reIerence to the network, is required by the other ModBusJIEWoTCP VIs managing the same client.
Aetwork input is deIined by the two Iollowing elements:
- server address : IP address oI the server concerned by the requests (ex :196.168.25.42).
- remote port (52): port used Ior the TCP/IP communication.
II the connection is not opened within the time deIined by timeout ms (), the VI generates
an error.
4.2.2- CLOSE

Figure 5 : MBV_close.vi
This VI closes the TCP/IP communication oI the Network associated with AetRef in.
It is imperative Ior the release process to be done properly to Iree the memory resources oI the
computer.
4.2.3- REQUESTS VIS
4.2.3-1. CONNECTOR MODEL
The set oI VIs that composes the Client part oI ModBusJIEWoTCP driver, Iollows the connector
model below :

Figure 6 : Connector model of Clients VIs
- NetReITCP in / NetReITCP out: AetRef1CP in is the reIerence to the ModBus network
obtained at the opening oI the communication (cI 4.2.1-) AetRef1CP out is a copy oI AetRef1CP
in.
- error in / error out : error in describes the errors conditions Iound beIore the VI. The deIault
value corresponds to "no error". II an error is transmitted to the error in input oI the VI, this error is
relayed to error out without the VI executing its Iunction. II an error occurs when the Iunction is
running, this error is automatically relayed to error out.
- Timeout : II the client request does not get any response within the time deIined by timeout
ms (1), the VI exits with an error.
MODBUSVIEWoTCP components - Client tools

ModBusVIEWoTCP - User Guide 8/29
www.saphir.Ir
- Unit identiIier: Unit identifier (xFF) is used Ior the communication with a serial network
through a gateway.
- InIormation out : Information out is a cluster that contains the Iollowing inIormation:
Unit IdentiIier: Identical to Unit identifier (xFF).
exceptionCode: Code reIering to ModBus protocol exceptions (cI. 7.2). The deIault value is
0: no exception occurred.
IunctionCode: Number oI the used request
sendFrame: String sent to the slave equipment. (This data is given Ior inIormation,
ModBusJIEWoTCP driver deals with the sending oI the Irame by itselI).
receivedFrame: String received by the master (sent by the slave as an answer to the request)
4.2.3-2. REQUEST 1 : READING OF N OUTPUT BITS

Figure 7 : MBVTCP_lecNBitsSortie(1).vi
This VI is used to read consecutive output Bits deIined in the memory oI the destination server.

- Bit address: address oI the Iirst bit
- Quantity of bits (1): number oI bits to read
- Bits: value oI the read bits
4.2.3-3. REQUEST 2 : READING OF N INPUT BITS

Figure 8 : MBVTCP_lecNBitsEntree(2).vi
This VI is used to read consecutive input Bits deIined in the memory oI the destination server.
- Bit address: address oI the Iirst bit
- Quantity of bits (1): the number oI bits to read
- Bits: value oI the read bits
MODBUSVIEWoTCP components - Client tools
9/29
www.saphir.Ir
4.2.3-4. REQUEST 3 : READING OF N OUTPUT WORDS

Figure 9 : MBVTCP_lecNMotsSortie(3).vi
This VI is used to read consecutive output Words deIined in the memory oI the destination server.
- Word address: address oI the Iirst word
- Quantity of Words (1): number oI words to read
- Words value oI the read words
4.2.3-5. REQUEST 4 : READING OF N INPUT WORDS

Figure 10 : MBVTCP_lecNMotsEntree(4).vi
This VI is used to read consecutive input Words deIined in the memory oI the destination server.
- Word address: address oI the Iirst word
- Quantity of Words (1): number oI words to read
- Words value oI the read words
4.2.3-6. REQUEST 5 : WRITING OF AN OUTPUT BIT

Figure 11 : MBVTCP_ecrBitSortie(5).vi
This VI is used to write (at 0 or at 1) an output Bit in the memory oI the destination server
- Bit address: address oI the bit to write
- Bit (F): value oI the bit to write
MODBUSVIEWoTCP components - Client tools

ModBusVIEWoTCP - User Guide 10/29
www.saphir.Ir
4.2.3-7. REQUEST 6 : WRITING OF AN OUTPUT WORD

Figure 12 : MBVTCP_ecrMotSortie(6).vi
This VI is used to write an output Word in the memory oI the destination server
- Word address: address oI the word to write
- Word (): value oI the word to write
4.2.3-8. REQUEST 15 : WRITING OF N OUTPUT BITS

Figure 13 : MBVTCP_ecrNBitsSortie(15).vi
This VI is used to write (at 0 or at 1) a group oI consecutive output bits in the memory oI the
destination server.
- Bit address: address oI the Iirst bit to write
- Bits: number oI bits to write and their values

The driver sends groups oI 8 bits. II the number oI bits written is not a multiple oI 8, the
driver Iills the missing bits as FALSE. Depending on the equipment oI destination, these
bits can be interpreted or not.
4.2.3-9. REQUEST 16 : WRITING OF N OUTPUT WORDS

Figure 14 : MBVTCP_ecrNmotsSortie(16).vi
This VI is used to write a group oI consecutive output words (16 bits) in the memory oI the
destination server.
- Word address: address oI the Iirst word to write
MODBUSVIEWoTCP components - Client tools
11/29
www.saphir.Ir
- Words: number oI words to write and their values
4.2.3-10. REQUEST 7 : STATUS READING

Figure 15 : MBVTCP_lecStatusException(7).vi
This VI permits to reach the 8 bits oI the server status.
- Status: bits array representing the server state
The meaning oI the status bits is speciIic to the equipment used. For more inIormation reIer
to the manuIacturer`s documentation.
4.2.3-11. REQUEST 8 : DIAGNOSIS

Figure 16 : MBV_diagnostic(8).vi
This VI is used to run Client/Server communication tests or to check the server is Iunctional.
- Subfunction Code: type oI test to run.
- Data in: data associated with the requested test iI necessary.
- Data out: test result iI necessary
Diagnosis Iunctions are speciIic to the equipment used. For more inIormation reIer to the
manuIacturer`s documentation.
4.2.4- ADVANCED PALETTE
These VIs manage basics communication Iunctions and make it possible to gain perIormance in
comparison with the requests VIs that are more high level.




MODBUSVIEWoTCP components - Client tools

ModBusVIEWoTCP - User Guide 12/29
www.saphir.Ir

The MBVTCPSendRequest.vi Sends a request to a ModBus server and return a reIerence to this
request through the Expected answer Iield. This reIerence is used to get the associate answer with
MBVTCPReceiveResponse.vi.
The Send frame is given just Ior inIormation.
According to the request type the type oI data received will be diIIerent (some data in the
dataReceived Irame may be empty).
4.2.5- EZ CODING VIS
EZ Coding VIs are to be dropped on an existing VI. They propose a starting architecture to the
implementation oI a ModBus client.



Drop this VI into the block diagram to place his content and customized it.


This code implements a simple request to a ModBus server.

MODBUSVIEWoTCP components - Server tools
13/29
www.saphir.Ir

This code implements a way to interpret 2 words to obtain a single.

This code implements a way to interpret a single to obtain 2 words.
4.3. SERVER TOOLS
This chapter describes the VIs to use to realise a Server Ior ModBus network. These VIs are
Iound in the Functions palette by selecting Functions ~ SAPHIR ~ ModBusVIEWoTCP ~
ServerTools.

Figure 17 : Server VIs palette
In Server mode, the computer never initiates the communication. It carries out three diIIerent
tasks:
- Supervise clients` connections and disconnections.
- Receive the requests sent by the clients.
- Answer to the clients' requests.
4.3.1- CONNECTIONS SCANNING
The scanning oI the clients' connections and the managing oI the communications with the clients
must be carried out independently.
MODBUSVIEWoTCP components - Server tools

ModBusVIEWoTCP - User Guide 14/29
www.saphir.Ir
The three Iollowing VIs are used to implement the scanning oI the diIIerent connections to the
server.
4.3.1-1. INITIALIZATION OF THE SCANNING

Figure 18 : MBVTCP_initializeListener.vi
- port (52): number oI the port to scan.
-
listener ID out: reIerence needed Ior the scanning oI the connections.

4.3.1-2. LISTENING OF THE CONNECTIONS

Figure 19 : MBVTCP_listenConnections.vi
- listener ID in: reIerence obtained during the initialization oI the listening.
- 1imeOut ms (1): maximum time to wait Ior a connection.
- listener ID out: copy oI listener ID in.
- [connections outj: array containing the TCP/IP communication reIerence (NetReITCP out)
and the IP address (remote address) oI each client connected to the server.
- # of connections in progress: number oI clients connected to the server.
4.3.1-3. STOP OF THE SCANNING
When you stop the server, you must close the listener ID reIerence with the above VI.
This process makes it possible to release properly the memory resources oI the computer.

Figure 20 : MBVTCP_closeListener.vi
- listener ID in: reIerence to close.
4.3.2- REQUESTS MANAGEMENT
4.3.2-1. REQUESTS RECEPTION
The reception oI the requests sent by the client(s) is carried out with the Iollowing VI:
MODBUSVIEWoTCP components - Server tools
15/29
www.saphir.Ir

Figure 21 : MBVTCP_listenRequest.vi
- [received requestj returns a table oI which each element describes the request received :
Connection ID: TCP/IP reIerence oI the client who sent the request.
remote address: IP address oI the client who sent the request.
receivedFrame: String written in the request.
Transaction IdentiIier: SpeciIic number oI the request sent by the client allowing identiIying the
answer to send.
Unit IdentiIier: identiIies a client located on a serial network and communicating through the
Ethernet network.
exceptionCode: Code reIering to ModBus protocol exceptions (cI. 7.2). 0 by deIault, no
exception occured.
IunctionCode: Number oI the request sent.
data : Data contained in the request.
- # of received request: number oI requests received.
AIter receiving a request, the answer must be sent as soon as possible to avoid timeout errors
on the Client side.
4.3.2-2. CONNECTOR MODEL OF ANSWER TO THE REQUESTS VIS
The set oI VIs that composes the answer request part oI ModBusJIEWoTCP driver, Iollows the
connector model below :

Figure 22 : Connector model of answer to requests VIs
- Received request: Received request contains data about the processed request
- error in / error out : error in describes the errors conditions Iound beIore the VI. The deIault
value corresponds to "no error". II an error is transmitted to the error in input oI the VI, this error is
relayed to error out without the VI executing its Iunction. II an error occurs when the Iunction is
running, this error is automatically relayed to error out.
- Send Irame: Send frame describes the Irame sent by the server to the client. (This data is
given just Ior inIormation)
MODBUSVIEWoTCP components - Server tools

ModBusVIEWoTCP - User Guide 16/29
www.saphir.Ir
4.3.2-3. ANSWER TO REQUESTS 1 AND 2 (READING N INPUT OR OUTPUT BITS)

Figure 23 : MBVTCP_repLectureNBits(1_2).vi
This VI permits to answer to the requests 1 or 2 sent by the client through ModBus network

- Bits: array containing the values oI all the registers oI the server
4.3.2-4. ANSWER TO REQUESTS 3 AND 4 (READING N INPUT OR OUTPUT WORDS)

Figure 24 : MBVTCP_repLectureNMots(3_4).vi
This VI permits to answer to the requests 3 or 4 sent by the client through ModBus network

- Words: array containing the values oI all the registers oI the server
4.3.2-5. ANSWER TO REQUEST 5 (WRITING AN OUTPUT BIT)

Figure 25 : MBV_repEcritureBit(5).vi
This VI permits to answer to request 5 sent by the client through ModBus network
- Bits in: array containing the values oI all the registers oI the server
- Bits out: values oI the server registers aIter the processing oI the request
4.3.2-6. ANSWER TO REQUEST 6 (WRITING AN OUTPUT WORD)

Figure 26 : MBVTCP_repEcritureMot(6).vi
This VI permits to answer to request 6 sent by the client through ModBus network
- Words in: array containing the values oI all the registers oI the server
- Words out: values oI the server registers aIter the processing oI the request.
MODBUSVIEWoTCP components - Server tools
17/29
www.saphir.Ir
4.3.2-7. ANSWER TO REQUEST 15 (WRITING N OUTPUT BITS)

Figure 27 : MBVTCP_repEcritureNBits(15).vi
This VI permits to answer to request 15 sent by the client through ModBus network
- Bits in: array containing the values oI all the registers oI the server
- Bits out: values oI the server registers aIter the processing oI the request
4.3.2-8. ANSWER TO REQUEST 16 (WRITING OF N OUTPUT WORDS)

Figure 28 : MBV_repEcritureNMots(16).vi
This VI permits to answer to request 16 sent by the client through ModBus network
- Words in: array containing the values oI all the registers oI the server
- Words out: values oI the server registers aIter the processing oI the request
4.3.2-9. GENERATION OF AN EXCEPTION CODE

Figure 29 : MBV_repException.vi
This VI returns an exception to a ModBus network client in case its request is not supported by
the server
- Exception Code: Code oI the exception to send (cI 7.2).
MODBUSVIEWoTCP components - Tools

ModBusVIEWoTCP - User Guide 18/29
www.saphir.Ir

4.4. TOOLS
This chapter describes tools to quickly simulate a ModBus client or server. You will Iind them in
the LabVIEW Tools menu bar.

Figure 30 : Tools to simulate ModBus network elements
MODBUSVIEWoTCP components - Tools
19/29
www.saphir.Ir

4.4.1- MODBUSVIEW OVER TCP CLIENT
'ModBusVIEW over TCP Client will quickly test the communication with a server through
ModBus network.

Figure 31 : Client window
The interIace Ialls into two sections:
- Network

settings deIines the TCP/IP parameters oI the ModBus network:
Server address. IP address oI the server to test.
Remote port. Number oI the port used Ior the TCP/IP communication.
Timeout (in ms). maximum time to wait to receive the server answer.
MODBUSVIEWoTCP components - Tools

ModBusVIEWoTCP - User Guide 20/29
www.saphir.Ir

- Communication test










Figure 32 : Communication test interface in Client mode

All the types oI Request oI ModBusView driver are managed :

Figure 33 : Requests choice.
Unit Identifier identiIies an equipment located on a serial network and communicating through
the Ethernet network. II the contacted server is on the Ethernet network, keep the FF hexadecimal
value (256 in decimal).
The Iirst register to read or write is deIined by From address.
The Iield With N is only available Ior requests 1, 2, 3 and 4. It represents the number oI bit(s) or
word(s) to read or to write.
Request parameters
Request data
Content oI the sent and
received Irames
MODBUSVIEWoTCP components - Tools
21/29
www.saphir.Ir
The data zone, located below the request parameters, permits to determine the values to write
during the use oI writing requests.
When all the settings are done, click on SEND REQUEST button to start the communication with
the slave. The content oI the Irames sent and received by the client is displayed below the data zone.
The Exception cod reIers to ModBus protocol exceptions (cI. 7.2).
4.4.2- MODBUSVIEW OVER TCP SERVER
'ModBusVIEW over TCP Server application simulates a server oI which registers are
represented with an array oI bits and an array oI words.
A ModBus network client can read or write these tables.

Figure 34 : Server window
Three sections compose this interIace:
- The Network settings permits to conIigure the ModBus server parameters:
Remote port (502) : Ethernet communication port oI the server
Timeout (in ms): time leIt Ior each scanning oI the Ethernet port.
MODBUSVIEWoTCP components - Tools

ModBusVIEWoTCP - User Guide 22/29
www.saphir.Ir
When clicking on the RUN SERJER button the server begins to scan the clients connections
(listening state).
This change oI state is notiIied by the computer icon which becomes green . The
address and the Connection ID oI the connected clients are displayed in the array
besides.
The settings oI ModBus network can`t be modiIied when the server is listening.
The received and sent Irames are displayed in hexadecimal code below the register tables.
The server doesn`t stop instantaneously; the timeout determines the maximum time it could take.















Figure 35 : Communication test interface of the server

The Exception cod reIers to ModBus protocol exceptions (cI. 7.2).
Received and
sent Irames

Table oI words

Table oI bits

List oI current connections

MODBUSVIEW activation - Tools
23/29
www.saphir.Ir
5. MODBUSVIEW ACTIVATION
AIter the download and installation oI ModBusVIEWoTCP toolkit, an activation window will pop up
at LabVIEW lauching. Follow the steps oI the add-on activation as shown in the picture below.


You can try ModBusVIEWoTCP during 30 days. AIter this period toolkit`s VIs will become
broken. To activate the toolkit aIter this period, simply go to Help menu and select Activate Add-
ons.
MODBUSVIEW support - Tools

ModBusVIEWoTCP - User Guide 24/29
www.saphir.Ir
6. MODBUSVIEW SUPPORT
The 'Online Support & Ressources menu opens the Iollowing SAPHIR community page:
http://decibel.ni.com/content/groups/saphir-toolkit

All the support, discussions and other inIormation related to the product are gathered here.


MODBUSVIEW DRIVER ERRORS - SpeciIic errors
25/29
www.saphir.Ir
7. MODBUSVIEW DRIVER ERRORS
7.1. SPECIFIC ERRORS
Following errors can be generate by ModBusVIEWoTCP Iunctions
Error Explanation
6101 TimeOut error.
6102 Unable to connect server.
6103 Connection rejected by the server.
6104 The Iunction used to answer the request is not adapted to the request.

Table 1 : Errors specific to ModBusVIEW driver

7.2. EXCEPTION CODES
Following exception codes are speciIic to ModBus protocole.
Decimal Codes Explanation
1 Not implemented Iunction
2 Out oI limits address
3 Out oI limits data
4 DeIective equipment
5 Acquit/release.
6 Busy equipment
7 Impossible to release
8 Memory error

Table 2 : ModBus exception codes
Frequently asked questions - Exception codes

ModBusVIEWoTCP - User Guide 26/29
www.saphir.Ir
8. FREQUENTLY ASKED QUESTIONS
The list below collects the most common problems encountered during the implementation oI
ModBusJIEWoTCP driver:
- Network setting :
The IP address keyboarded must not contains any non-signiIicant zero (ex : 192.168.011.002
192.168.11.2).
- The values returned by the server do not correspond to the expected values :
To return a Iloat number (point) 32 or 64 bits, the server uses respectively 2 or 4 words. The
Figure below shows the most common way to interpret 2 words to make a 32 bits Iloat (number).

Figure 36 : Interpretation of 2 words in 32 bits float

The way to interpret words can change according to the type oI server. For more inIormation
reIer to the manuIacturer`s documentation.



ModBusVIEWoTCP - User Guide
www.saphir.Ir
INDEX
Figure 1 : ModBusVIEWoTCP within LabVIEW Iunctions palette 5
Figure 2 : Connector model oI ModBusVIEWoTCP driver 6
Figure 3 : Clients VIs palette 6
Figure 4 : MBVTCPopen.vi 7
Figure 5 : MBVclose.vi 7
Figure 6 : Connector model oI Clients VIs 7
Figure 7 : MBVTCPlecNBitsSortie(1).vi 8
Figure 8 : MBVTCPlecNBitsEntree(2).vi 8
Figure 9 : MBVTCPlecNMotsSortie(3).vi 9
Figure 10 : MBVTCPlecNMotsEntree(4).vi 9
Figure 11 : MBVTCPecrBitSortie(5).vi 9
Figure 12 : MBVTCPecrMotSortie(6).vi 10
Figure 13 : MBVTCPecrNBitsSortie(15).vi 10
Figure 14 : MBVTCPecrNmotsSortie(16).vi 10
Figure 15 : MBVTCPlecStatusException(7).vi 11
Figure 16 : MBVdiagnostic(8).vi 11
Figure 17 : Server VIs palette 13
Figure 18 : MBVTCPinitializeListener.vi 14
Figure 19 : MBVTCPlistenConnections.vi 14
Figure 20 : MBVTCPcloseListener.vi 14
Figure 21 : MBVTCPlistenRequest.vi 15
Figure 22 : Connector model oI answer to requests VIs 15
Figure 23 : MBVTCPrepLectureNBits(12).vi 16
Figure 24 : MBVTCPrepLectureNMots(34).vi 16
Figure 25 : MBVrepEcritureBit(5).vi 16
Figure 26 : MBVTCPrepEcritureMot(6).vi 16
Figure 27 : MBVTCPrepEcritureNBits(15).vi 17
Figure 28 : MBVrepEcritureNMots(16).vi 17
Figure 29 : MBVrepException.vi 17
Figure 30 : Tools to simulate ModBus network elements 18
Figure 31 : Client window 19
Figure 32 : Communication test interIace in Client mode 20
Figure 33 : Requests choice. 20
Figure 34 : Server window 21
Figure 35 : Communication test interIace oI the server 22
Figure 36 : Interpretation oI 2 words in 32 bits Iloat 26





ModBusVIEWoTCP - User Guide
www.saphir.Ir
HISTORY OF REVISIONS

Author Date Index Subject
JOURDAN Olivier 30/09/03 01-OJO-A30930 Creation
JOURDAN Olivier 20/02/04 02-OJO-A30930 V1.1 update
JAVELLE Sandra 28/01/11 02-OJO-A30930 V2.x update