Pulse Modbus Driver

Version 8.07

User Guide
 Copyright
The information in this document is subject to change without notice and does not represent a
commitment on the part of Afcon Software and Electronics Ltd.

No part of this document may be used or reproduced in any manner whatsoever without written
permission from Afcon Software and Electronics Ltd.

The software described in this document is provided under a license agreement or a nondisclosure
agreement.
The software may be used or copied only in accordance with the terms of the agreement. It is
against the law to copy this software on any other medium for any purpose other than the
purchaser's personal use.

 Copyright 2011 Afcon Software and Electronics Ltd.

All rights reserved.

Pulse logos, P-CIM and P-CIM logos are registered trademarks of Afcon Software and Electronics
Ltd.

Afcon and the Afcon logos are registered trademarks of Afcon Software and Electronics Ltd.

Windows is a trademark of Microsoft Corporation.

Modbus Driver 8.07 User Guide (for Pulse) 2

 Contents
Copyright.................................................................................................................... 2

Introduction................................................................................................................... 5

Requirements .............................................................................................................. 6

Installation ................................................................................................................... 7

File Paths ................................................................................................................. 10

Hardware..................................................................................................................... 11

Communication Setup................................................................................................ 16

Assigning the Modbus Driver to a Port .................................................................... 16

Defining Multiple P-CIM Ports for a Single PLC ....................................................... 17

Configuring Driver Parameters ................................................................................. 18

Scheduling Parameters .......................................................................................... 19

Instructions for RS-232 .......................................................................................... 20

Instructions for Ethernet and Packet Data............................................................ 22

Instructions for Modbus Plus ................................................................................. 25

Instructions for Modem .......................................................................................... 27

Defining Advanced Parameters ............................................................................. 31

Defining Polling Configurations.............................................................................. 32

Basic Information ....................................................................................................... 34

Bit Representation ................................................................................................. 34

CollapseWrite .......................................................................................................... 34

ReflectWrite............................................................................................................. 34

Rounding ................................................................................................................. 35

Referencing Driver Data in Pulse .............................................................................. 36

Address Syntax .......................................................................................................... 36

Syntax Table ............................................................................................................ 37

Direct Access Syntax ................................................................................................. 39

Conversions ............................................................................................................... 40

Modbus Driver 8.07 User Guide (for Pulse) 3

 Conversion Links..................................................................................................... 41

$Variables ............................................................................................................... 44

Troubleshooting - Alarm Handler Messages............................................................. 48

Error Codes ................................................................................................................ 49

Appendix A - Specifications........................................................................................ 50

Supported Protocols ............................................................................................... 50

Supported Serial Parameters................................................................................. 50

Ethernet Supported Parameters............................................................................ 50

MBPlus Supported Parameters ............................................................................. 51

Packet Data Supported Parameters...................................................................... 51

Appendix B - Checking Communication .................................................................... 52

Using Data Scope to Check Communication Status............................................... 52

Using the Alarm Summary to Monitor Communication Status .............................. 53

Monitoring Communication Event Messages.......................................................... 54

Using the Drivers Server to Check Communication Status .................................... 54

Appendix C - Solved Issues ....................................................................................... 55

Appendix D - Known Issues ....................................................................................... 60

Appendix E - New Features ....................................................................................... 61

Modbus Driver 8.07 User Guide (for Pulse) 4

Introduction
This document discusses the Modbus driver, how it is installed, referenced and configured
in Pulse to read and write values to and from addresses in runtime. The Modbus driver and
its runtime parameters are defined in the P-CIM Configurator dialog box and can run in
either normal or emulation mode.

The Modbus driver, during runtime, runs in the background continually, communicating
with PLCs, and providing access to PLC data by continuously polling Pulse addresses. Data
is written to the PLC on operator or application demand after the constant transaction is
completed.
Alarm and event messages are displayed in the Alarm Explorer and/or Alarm Handler
module.

The Modbus driver supports cellular communications when Packet Data settings are defined
in the Communication Settings dialog box.

The Modbus driver supports Pulse Hot Redundancy Mode.

The following formats are supported by the Modbus driver:

• ASCII

• RTU

• TCP/IP

• MBPLUS protocol variants

• Packet data

The Modbus driver communicates with these PLC models:

• 4 digit: 384 and 484

• 5 digit: 584, 884, and 984

• 6 digit: L984-785, E984-785, and 140 CPU-424 02486

The number of digits shows the syntax used in the P-CIM Configurator.

The following types of communications are used by the Modbus driver:

• The driver communicates through COM 1 and COM 255 ports, or, the PC’s
Ethernet adapter port.

• For MBPLUS protocol, communication is through SA85 or SM85 adapters.

• The driver communicates through each PC port with up to 255 separate PLCs,
numbered 1 to 255.

Modbus Driver 8.07 User Guide (for Pulse) 5

Requirements
Hardware:

• Modems for connecting to networks.

• For an Ethernet network: Communication card.

• For an MBPLUS network: Pulse communicates by one or two SA85 or SM85

network adapters installed in an IBM-PC (or compatible) platform running
Pulse.

For modem networks: no extra hardware is needed for connecting to a single

PLC by an RS232 connection through COM1 or COM2.

Software:

• Windows XP, Windows 2003 Server

• Pulse 1.10 or higher

• For Ethernet network: fixed IP address

• For a Modbus Plus Network: Modicon device driver.

For MBPlus networks: check that SA85 or SM85 are installed correctly.

Computer Resources: The driver needs roughly 5 MB of disk space.

Modbus Driver 8.07 User Guide (for Pulse) 6

Installation
The Modbus driver can only be installed after Afcon Pulse is installed on a computer. Below
are instructions for installing the Modbus driver from the Pulse DVD. The driver can also be
downloaded from the AFCON Web site (www.afcon-inc.com). Click the Products link, and
then click Drivers 32 bit to locate and download the relevant driver zip file to your
computer. Additionally, the Install Driver option in the Communications Setup dialog box
enables assigning an installed driver to a Pulse project. From all of these entry points, the
Driver Setup Wizard will execute the installation.

Installing the Modbus driver from the Afcon DVD

NOTE: When installing drivers, make sure that Pulse is shut down.

1 Insert the AFCON DVD into the DVD drive on your computer. Wait for it to open on
your screen.

2 Select Pulse, select Communication Drivers and then Open to open the
Communication Drivers dialog box.

Modbus Driver 8.07 User Guide (for Pulse) 7

3 Select the Modbus driver and click the Install button.
The Pulse Driver Setup wizard is displayed.

4 Click Next. Select a project or install the driver into multiple projects using the
standard Windows selection key combinations (<Shift>+click, <Ctrl>+click, <Ctrl>+A
[for all]).

5 Click Next. Review the summary information. You may expand the driver table to see
which files the driver setup will install and their destination folder.

Modbus Driver 8.07 User Guide (for Pulse) 8

6 Click Install. The Install Progress page shows you the progress and status of the
driver installation. When the Current Task and Setup Status bars display “100%”, the
installation is done.
As an option, you can generate, store, and print installation reports:

Report All Generate a report detailing the installation of the driver files.
Generate a report detailing any errors which may have occurred
Report Errors
during the driver installation.

Modbus Driver 8.07 User Guide (for Pulse) 9

7 Click Next. If successful, the wizard notifies that the driver was successfully installed.
If you want to install another driver, click Install Another Driver to start the process
again. Otherwise, click Finish to close the wizard.

Start Pulse The Pulse Server will start up after you click Finish. After the
Server Server completes startup, the Driver Setup wizard closes.

File Paths
The files associated with this driver and files common to all drivers in the system are listed
below in their default locations:

File Path Notes

MODBUS.EXE C:\AFCON\Pulse\projectname\ Driver configuration program

Communication folder

MODBUSDR.DLL C:\AFCON\Pulse\projectname\ Runtime driver

Communication folder

MODBUS.INI C:\AFCON\Pulse\projectname\ Driver configuration

Communication folder initialization file

DrvrPort.INI C:\AFCON\Pulse\projectname\ This file contains all the

Communication folder information defined in the
Project Communication Setup
dialog box file

MODBUS.HLP C:\AFCON\Pulse\projectname\ Modbus driver Help

Communication folder

MBPTRANS.DLL C:\AFCON\Pulse\projectname\ Modbus Plus transport

Communication folder driver.

All files are restored by reinstalling the Modbus driver.

Modbus Driver 8.07 User Guide (for Pulse) 10

Hardware
This chapter displays the physical connections between a PC and the PLCs with which it
communicates.

Further information on hardware installation can be found in Modicon

documentation.

Linking to a Single PLC in an RS232 Network

This diagram displays the wiring for the cables that link a single PLC to the 9 pin or 25 pin
serial port connector of the PC.

PC AT 9 pin PLC 9 pin PC AT 9 pin PLC 25 pin

NC 1 1 SHLD CD 1 1 SHLD
RX 2 2 RX RX 2 2 TX
TX 3 3 TX TX 3 3 RX
DTR 4 4 DTR DTR 4 4 RTS
GND 5 5 GND GND 5 5 CTS
DSR 6 6 DSR DSR 6 6 DSR
RTS 7 7 RTS RTS 7 7 GND
CTS 8 8 CTS CTS 8 8 CD
9 NC 20 DTR

Modbus Driver 8.07 User Guide (for Pulse) 11

Linking to a Network of PLCs for an RS-485 or RS-422 Network
The diagram below shows a PLC network layout.

P-CIM
RS232/RS485

RS485/RS232 RS485/RS232 RS485/RS232

PLC PLC PLC

Network Cable Wiring

This diagram displays the wiring for the cables linking to a networking of PLCs to 9 pin or
25 pin serial port connectors of the PC.

PC AT 9 PIN J478/S978
25 PIN
SHLD 1 1 SHLD
RX 2 2 TX
TX 3 3 RX
DTR 4 4 RTS
GND 5 5 CTS
DSR 6 6 DSR
RTS 7 7 GND
CTS 8 8 NC
NC 9 20 DTR

Modbus Driver 8.07 User Guide (for Pulse) 12

Network Requirements for Ethernet
The diagram below shows a PLC network layout.

NO CPU NO CPU

HUB

Interface adapter
installed 3COM
P-CIM

Linking to a Network of PLCs for an SM85 or SA85 Network

The diagram below shows a PLC network layout.

P-CIM SM85 or SA85 network adapter installed

Modbus plus network

PLC PLC PLC

Modbus Driver 8.07 User Guide (for Pulse) 13

Linking to a Modem
The diagram below shows linking to a modem.

Line
P-CIM Modem

Telephone
Service
PLC

Line
Modem

PLC
Line
Modem

Packet Data Connections

The diagram below shows packet data connections which can be used for cellular
connections.

Line
P-CIM Modem

PLC

Line
Modem

PLC
Line
Modem

Modbus Driver 8.07 User Guide (for Pulse) 14

Modbus Plus Connections
The diagram below shows MBPLUS connections.

12?

12?

5 4 3 2 1 5 4 3 2 1 5 4 3 2 1

9 8 7 6 9 8 7 6 9 8 7 6

Terminator -------Network-------- Terminator

Modbus Driver 8.07 User Guide (for Pulse) 15

Communication Setup

Assigning the Modbus Driver to a Port

In Project Communication Setup you assign logical Pulse ports to the driver (see below,
To assign a port to the driver) and then select the physical COM ports and configure the
appropriate communication parameters for those ports.You can setup or change the
communication settings while Pulse is running or not running. However, the new settings
will take effect only after Pulse is restarted.

To assign a port to the driver

1 Go to Pulse Setup and click Communication. The Project Communication Setup

dialog box appears on your screen.

2 To assign a new port to a driver, click the New button; to edit an already assigned port,
select the appropriate port in the Assigned ports box and click the Edit button. The
Port Properties dialog box appears on your screen.

3 To assign a new port, type a number between 1-255 in the Port Name box. For an
already assigned port, the port number is displayed.

Modbus Driver 8.07 User Guide (for Pulse) 16

4 Select the parameter values according to the following:

Field Description

Port name This is a virtual port that has no functionality in the software. A
virtual port number can be anything between 1 and 255 and can be
used only once.

Driver name This list holds the names of all the drivers installed in the current
project. A driver can be used any number of times.

Bit numbering This field defines the read bit access used. For example if Octal is
system used the digits 8, 9 are not available. Our recommendation is to
leave the setting at its default of 10 decimal.

Lowest bit Select 1 in this field to define the bit numbering for this driver is
number 1-16. (When 0 is selected, it defines the bit numbering for this driver
is 0-15).

Emulation When checked, the driver runs in emulation mode.

mode
In emulation mode the driver does not communicate with field
devices, but reads and writes internally. Use this mode is during
development.

5 Click OK.
The Port Properties dialog box is closed. The assigned port, the name of the new driver
and the mode all appear in the Assigned ports box in the Project Communication Setup
dialog box. The port allocation is recorded in the DRVRPORT.INI file.

Defining Multiple P-CIM Ports for a Single PLC

It is possible to define multiple P-CIM ports for a single PLC. P-CIM manages each port's
communication in parallel. When a PLC response time takes longer and have many polling
requests leading to longer scan times of polled data, applying multiple P-CIM ports for the
same PLC can help achieve a faster scan rate and avoid delays of polled data from the PLC.

Note that it is possible to define communication on a single PLC via two or more P-CIM ports
and communication for multiple PLCs via a single P-CIM port can be defined.

Modbus Driver 8.07 User Guide (for Pulse) 17

Configuring Driver Parameters
Define the Modbus driver’s parameters in the P-CIM configurator for Modbus Driver dialog
box.

Opening the P-CIM configuration program dialog box

In the Project Communication Setup dialog box, select the relevant assigned port and click
the Properties button

This dialog box has three sections:

• Scheduling, the fields in this section are described on page 19.

• Transport and Station Parameters, where different dialog boxes open according
to the selected network type.

• Additional parameters (P-CIM Port, Use Secondary Transport)

Modbus Driver 8.07 User Guide (for Pulse) 18

Scheduling Parameters
Use the information in this table to complete the Scheduling parameters for all network
types.

Table 1: Scheduling Parameters

Field Description

P-CIM port Displays the port selected in the Pulse Communication Setup
dialog box, Assigned Ports field.

Polling When clicked opens the Polling Configuration dialog box where
configurations you define blocks of driver address with different scan settings
to that of the default scan parameters.

Simulate I/O This applies to when working in emulation mode only:

When checked read items receive random values continuously.

Read before bit write Reads and checks the register’s last value immediately before
writing to a specific bit in the register.

Force multiple write Instructs the driver to use the multiple write function to force
for all stations write a single register.

Time-out The driver waits the defined amount of time for a valid reply
from the PLC, and retries the transaction twice if a reply is not
received or is garbled.
The default value is 1-second, ranging from 0.5 to 50 seconds.

Default scan time Default value is 0:0 seconds.

Scan time suggests the frequency the driver scans and gets
readings for a specific address from the PLC.
Default scan time is a global parameter, defining scan time of
addresses globally.

Scan time ranges from 0.0-255.0 seconds, where a resolution

of 0.1 seconds can be defined:

• When set to minimum value of 0.0, the driver

constantly scans addresses in the PLC

• When set to the maximum 255.0, it will scan once

every 255 seconds.

Max retries Defines the number of communication retries performed

before communication failure is declared. A retry is an attempt
to send a task to the PLC.

Min reconnect Defines the minimum amount of time in minutes the Pulse
driver waits before trying to reconnect to a PLC declared as
failed.
Default is 1-minute.

Default Min. Address Sets the minimal address length. To match the minimal length
Length defined, a leading 0 is added to every address that is below
this threshold. Addresses that are equal to or higher than the
defined threshold are not changed.

Modbus Driver 8.07 User Guide (for Pulse) 19

Instructions for RS-232
Defining Transport Parameters

1 In the Network Type field select RS232 from the drop-down list to open the Transport
Parameters – RS232 dialog box.

2 Complete this dialog box using the following information.

Field Description

COM port Showing the computer’s export port.

Baud rate Showing the communication speed of the device.

Data bits Showing the number of bits in one byte.

Parity Checks the correct combined bits of each byte in a message.

Stop bits Showing the number of bits in each byte signaling the end of the byte.

Com mode Suggesting the communication type which can be:

• RTU

• ASCII

Station When clicked opens the Station Parameters – RS232 dialog box.
parameters

Modbus Driver 8.07 User Guide (for Pulse) 20

Defining Station Parameters

1 To open this dialog box, click the Station Parameters button in either the P-CIM
configurator for Modbus Driver or in the Transport Parameters dialog boxes.

2 Click the Add button to open the Add New Stations dialog box.

Field Description

PLC Number Marking the logical number of the PLC in Pulse at runtime.

Min. Address Sets the minimal address length. To match the minimal length
Length defined, a leading 0 is added to every address that is below this
threshold. Address that are equal to or higher than the defined
threshold, are not changed.

Show When checked displays the Advanced Parameters options. See

advanced page 31 for further information.
parameters

3 Select the number and PLC Type using the information in the table above.

4 Click OK to save these definitions and to return to the Station Parameters dialog box.

Secondary Transport

1 Select the Use Secondary Transport option to enable the use of a secondary
communications channel (i.e, port, secondary server) in a Redundancy configuration.

Modbus Driver 8.07 User Guide (for Pulse) 21

Instructions for Ethernet and Packet Data
Defining Transport Parameters

1 In the Network Type field, select Ethernet or Packet Data from the drop-down list to
open the Transport Parameters – Ethernet (or Packet Data) dialog box.

2 Complete this dialog box using the following information.

Field Description

Default remote Defines the bidirectional connection method to the PLC from and
port to the PC. In Packet data the default for the default remote port
is 1195, which can be changed.

Transport Protocol Specify the transport protocol of the network: TCP or UDP.

Multi Sockets When checked indicates that if more than one IP address and port
are defined, communication for each IP address is made
simultaneously.
Checked by default.

Use Ping Enables the system to send a ping, during Pulse startup, to check
which PLCs are connected and operating. This option is enabled
by default.

NOTE: If the network contains a large number of PLCs, and many

are disconnected, the ping process time may take several seconds
to complete. If you don’t want to pass through this long delay, you
can disable the Use Ping option.

Support unsolicited When checked sets Pulse in “passive” mode, in which the PLC
messages sends burst messages to Pulse. This method of communication
can only be used once per driver.

Station parameters When clicked opens the Station Parameters – Ethernet dialog box.

Modbus Driver 8.07 User Guide (for Pulse) 22

Defining Station Parameters

Complete this dialog box using the following information.

Field Description

Number Showing the logical number of the PLC in Pulse at runtime.

Min. Sets the minimal address length. To match the minimal length defined, a
Address leading 0 is added to every address that is below this threshold. Address
Length that are equal to or higher than the defined threshold, are not changed.

IP address Showing the IP address of the PLC.

Port Defines the bidirectional connection method to the PLC from and to the
PC.

Index When more than one PLC is connected to the same IP address an Index
is used to distinguish between PLCs.

3 Click the Add button to open the Add New Stations dialog box.

Modbus Driver 8.07 User Guide (for Pulse) 23

 Field Description

PLC Number Marking the logical number of the PLC in Pulse at runtime.

IP address Showing the IP address of the PLC.

Port Defines the bidirectional connection method to the PLC from and to
the PC.

Index When more than one PLC is connected to the same IP address an
Index is used to distinguish between PLCs.

Min. Address Sets the minimal address length. To match the minimal length
Length defined, a leading 0 is added to every address that is below this
threshold. Address that are equal to or higher than the defined
threshold, are not changed.

Show When checked displays the Advanced Parameters options. See

advanced page 31 for further information.
parameters

Secondary Transport

1 Select the Use Secondary Transport option to enable the use of a secondary
communications channel (i.e, port, secondary server) in a Redundancy configuration.

Modbus Driver 8.07 User Guide (for Pulse) 24

Instructions for Modbus Plus
Defining Transport parameters

1 In the Network Type field select MBPlus from the drop-down list to open the Transport
Parameters – MBPlus dialog box.

Complete this dialog box using the following information.

Field Description

LAN number Showing the ID of the MBPlus card in the computer, for
example: SA85.

Data paths Showing the maximum paths to which messages can be

sent simultaneously.

Station When clicked opens the Station Parameters – RS232

parameters dialog box.

Modbus Driver 8.07 User Guide (for Pulse) 25

Defining Station Parameters

1 To open this dialog box, click the Station Parameters button in either the P-CIM
Configurator for Modbus Driver or in the Transport Parameters dialog boxes.

2 Click the Add button to open the Add New Stations dialog box.

Field Description

PLC Number Showing the logical number of the PLC in Pulse at runtime.

Min. Address Sets the minimal address length. To match the minimal length
Length defined, a leading 0 is added to every address that is below this
threshold. Address that are equal to or higher than the defined
threshold, are not changed.

Route Sets the PLC routing address

Redundant Route Sets the redundant PLC route. Use this option as a backup in case
when the driver is unable to connect to primary PLC.

Show advanced When clicked displays the Advanced Parameters options for
parameters further information see page 31.

3 Complete this dialog box using the information in the table above.

4 Click OK to save these definitions and to return to the Station Parameters dialog box.

Secondary Transport

1 Select the Use Secondary Transport option to enable the use of a secondary
communications channel (i.e, port, secondary server) in a Redundancy configuration.

Modbus Driver 8.07 User Guide (for Pulse) 26

Instructions for Modem
The Transport and Station parameters for this dialog box are similar to those of an RS232
connection, with exception to the network type set to Modem and the Modem button, which
opens the Modem Parameters dialog box.

Defining Modem parameters

1 In the Transport dialog box click the Modem Parameters button to open the Modem
dialog box.

This dialog box has the following fields:

Table 2: Modem Parameters

Field Description

Initialization Defining the string used to initialize connection between the

string modem and the PLC.

Default phone Indicating the phone number used when a PLC does not have a
number phone number mentioned.

Dial using Defines the dialing mode used, which can be either Tone or Pulse.

Phone When clicked opens the Phone Parameters dialog box where PLCs
parameters and phone numbers can be assigned and displayed in a list, see
page 24.

Redial This field defines the settings by which the modem tries to redial
parameters to the PLC when communication is not successful.

Modbus Driver 8.07 User Guide (for Pulse) 27

 Table 2: Modem Parameters (Continued)

Redial after Defines the number of minutes after which the

modem tries to reconnect to the PLC.

Max retries Defines the number of communication retries

performed before communication failure is
declared.

A retry is an attempt to send a task to the PLC.

AutoAnswer/ When Enabled turns-on the PLC ID Parameters options. In this

enable mode after a PC receives an ID string burst messages it
immediately tries to communicate to the relevant PLC.

PLC ID When clicked opens the PLC ID Parameters dialog box where an
parameters identification string can be configured for each PLC.

Scheduling This field has the following scheduling options:

Permanent When checked, indicates that there is a

connection permanent connection between the modems.

Ignore delay When checked instructs the driver to poll the

after modem PLC immediately after the ‘connect’ message
connection was received from the remote modem.

Connect Defines that scheduling is every xxx amount of

every minutes.

Every Defines the time/scans that communication is

connection/ tried.
minutes or
scans

Modbus Driver 8.07 User Guide (for Pulse) 28

Defining PLC ID Parameters

1 In the Modems dialog box Auto Answer field check the Enable checkbox. The PLC ID
Parameters button option is enabled.

2 Click the PLC ID Parameters button to open the PLC ID Parameters dialog box.

3 Click the Add button to open the Add PLC ID String dialog box.

4 Scroll to the relevant PLC number and then type in the string in the ID String field.

5 Click OK to return to the PLC ID Parameters dialog box. Complete this dialog box using
the information below:

Field Description

Hang-up after Check when using two modems connected to two ports for:
getting PLC ID
string • Outgoing calls

• Incoming calls

When checked the driver hangs up after receiving the call and calls
back using the port configured for outgoing calls.

PLC ID string Defines the waiting time (in seconds) for receiving information (range
waiting time 1 - 15, default is 1).

Modbus Driver 8.07 User Guide (for Pulse) 29

Defining phone parameters

1 Click the Phone Parameters button in the Modem Parameters dialog box to open the
Phones Parameters dialog box.

2 Click the Add button to open the Add Phone dialog box, where the association between
the Modem and PLC is defined.

3 In the Phone Number field type in the phone number that is associated with a PLC.

4 In the PLC list click the relevant PLC number. The phone number is displayed next to
the selected PLC number.

5 Click OK to confirm and to return to the Phone Parameters dialog box where the
associated PLC and phone numbers are listed.

Modbus Driver 8.07 User Guide (for Pulse) 30

Defining Advanced Parameters
The Advanced Parameters dialog box displays the addresses used in the driver and their
memory range.

Accessing the Advanced Parameters dialog box

In the Add New Station dialog box, check the Show Advanced Parameters checkbox
to access the Advanced Parameters dialog box.

Modbus Driver 8.07 User Guide (for Pulse) 31

Defining Polling Configurations
Polling block definitions are defined in the Add Polling Configuration dialog box, and these
definitions are displayed in the Polling Configuration dialog box.

Accessing the Polling Configurations dialog box

1 In the P-CIM Configurator for Modbus Driver dialog box, click the Polling
Configuration button to open the program.

2 Click the Add button to open the Add Polling Block dialog box.

This dialog box has the following fields and buttons:

Field Description

Always on scan When checked defines that item/s are continually scanned,
even if an item is not an advised item in the application.

PLC Suggesting the number of the relevant PLC.

Start address Showing the first address in the block that is configured.

Quantity Showing the total number of addresses in the addresses block.

Scan time Showing the total amount of time the address block is scanned.

Modbus Driver 8.07 User Guide (for Pulse) 32

3 Fill the Add Polling Block dialog box using the information above. Click OK, the
definitions are displayed in the Polling Configuration dialog box.

Modbus Driver 8.07 User Guide (for Pulse) 33

Basic Information

Bit Representation
In the application the driver enables access to a specific reference bit. This bit is regarded
as a digital point. Bits can be referenced in the decimal range. Pulse bit numbering
convention for a data reference is:

• 1-16, (default) where bit 1 is the least significant

• 0-15 numbering, where bit 0 is the least significant

The BitZero token is used to configure port settings individually. In the MODBUS.INI file
the default for each configured port is: BitZero=0, showing that bit numbering for the port
is 1-16.

The syntax is reversed to that used when programming the PLC.

Changing port bit numbering to 0-15

To change the bit numbering for the port to 0-15, open the INI File Editor and in the
MODBUS.INI file, select the relevant port and change the setting to BitZero=1.

CollapseWrite
This MODBUS.INI file setting enables sequential writing to a reference. By default,
CollapseWrite=0 (sequential writing) is enabled.

Disabling sequential writing to a reference

Open the Pulse INI File Editor and change the default setting to CollapseWrite=1.
The driver switches automatically to CollapseWrite=1.

The Alarm Summary displays a message if more than 4096 write addresses are in the
queue. This setting can be changed in the MODBUS.INI file, section: ['Port'], token:
MaxWrite Queue.

ReflectWrite
When the token ReflectWrite=1,(by default) token is defined, the driver returns an
updated value immediately after a successful read operation.

Disabling/refreshing data after a write action

Open the INI File Editor and make the following change: MODBUS.INI.Set
ReflectWrite=0.

Modbus Driver 8.07 User Guide (for Pulse) 34

Rounding
The MODBUS.INI file setting enables automatic rounding off a decimal value when inserting
a value to a reference. By default, Rounding=1 (rounding off enabled).

Disabling automatic rounding off

Open the Pulse INI File Editor and change the default setting 1 to Rounding=0. This enables
truncation of any decimal value inserted to a reference.

Modbus Driver 8.07 User Guide (for Pulse) 35

Referencing Driver Data in Pulse
This chapter discusses the address syntax, conversions and $variables supported by the
Modbus driver.

Address Syntax
PLC data handled by the driver is accessed by the Pulse Kernel and the driver’s server by
a callback and a DDE link in the following format:
Server, Topic, Item

Server PFWDRVR or DBSR

Topic PCIM

Item The format port ":"station":"address where

Port Pulse port number (decimal)

Station PLC station number (decimal)

Address Address in the PLC.

For information on working with bits, see page 34.

Modbus Driver 8.07 User Guide (for Pulse) 36

Syntax Table

Table 3: Driver Syntax

Modicon Syntax Application Read, Write Type Value Note

Syntax Range

4-DIGIT 1

Output 0001 0999 R/W bit 0-1

Input 1001 1999 R bit 0-1

Input register 3001 3999 R register 0-65535

Holding register 4001 4999 R/W register 0-65535

Holding register F4001 F4998 R/W float num.

(float)

Holding register L4001 L4998 R/W long num. 0-

(long) 4294967295

Data GD00001-32 R/W register 0-65535 4,5

5-DIGIT 2

Output 00001 09999 R/W bit 0-1

Input 10001 19999 R bit 0-1

Input register 30001 39999 R register 0-65535

Holding register 40001 49999 R/W register 0-65535

Holding register F40001 F49998 R/W float num.

(float)

Holding register L40001 L49998 R/W long num. 0-

(long) 4294967295

Data GD00001-32 R/W register 0-65535 4.5

6-DIGIT 3

Output 00001 065535 R/W bit 0-1

Input 100001 165535 R bit 0-1

Input register 300001 365535 R register 0-65535

Holding register 400001 465535 R/W register 0-65535

Extended 600000 699999 R/W register 0-65535

memory

Holding register F400001 465534 R/W float num. 4,5

(float)

Holding register L400001 L465534 R/W long num. 0-

(long) 4294967295

Extended F600000 F699998 R/W float num. 4

memory (float)

Modbus Driver 8.07 User Guide (for Pulse) 37

 Table 3: Driver Syntax (Continued)

Extended memory L600000 L699998 R/W long. num. 0-

(long) 4294967295

Data GD00001-32 R/W register 0-65535 5

Time Register T40001 - 49999 R/W string 0D0H0M0S0 6,7

Ms-
49D17H2M47
S295Ms

Sign S30001 - S39999 R/W string -32767 -

32767
S40001 - S49999

S60001 - S69999

1 Models 84, 384, 484

2 Models 584, 884, 984 (regular)

3 Models L984-785, E984-785, 140 CPU-424 02486 (6-digit PLC models).

3.4E+/-38 (7 digits)

4 Addresses in MBPLUS mode can only be written to when the PLC number
equals the Adapter Number (for example: 2:8:GD30).

5 Port: Adapter:address of GD, where Adapter is the Adapter Number in the

Transport section of the P-CIM Configurator for the MODBUS driver

6 The maximum supported values are: 49 Days, 17 Hours, 2 Minutes,

47 Second and 295 MS.

Example: 2d13h14m12s3.5ms= 2 days 13 hours 14 min 12 sec 3.5 ms

Modbus Driver 8.07 User Guide (for Pulse) 38

Direct Access Syntax
When defining blocks in the Database Explorer, you should only set the Item in the block’s
Address field. The Server and Topic fields are implied.

The Server, Topic, and Item (DDE Link) are usually mentioned in Windows client
applications in one of two formats:

1 Separately, in three labeled fields

2 Together, in one field usually labeled Link. the vertical bar ("|") and exclamation mark
("!") separators are used. For example: Server|Topic!Item "

Some applications (for example, Microsoft Excel) require an identifier with

special characters enclosed in single quotes.

DDE Link Example

The DDE specification for:

Address: 40004, PLC No: 2, Connected to Pulse port: 3, Bit No: 12 (of same address)

Can be either:

Server: DBSR Topic: PCIM Item: 3:2:40004

and

Server: DBSR Topic: PCIM Item: 3:2:40004:12

Or:

Link: DBSR|PCIM!3:2:40004

and

Link: DBSR|PCIM!3:2:40004:12

Modbus Driver 8.07 User Guide (for Pulse) 39

Conversions
The driver supports algorithms that convert the data received by the driver from the PLC
into different format and/or different scaling. The algorithms operate bidirectionally.

Conversions can be used in the Pulse database, together with the fields Conversion, Low
scale and High scale for specific block types. Driver conversions can also be accessed at
runtime with the DBSR, PFWDRVR and Modbus server. The syntax is described below:

Server|Topic!Item,Conv

where Conv is one of the driver supported conversions

For example:

The DDE specification for conversion DIV10 of the address 40004 is:

Link: DBSR|PCIM!3:2:40004,DIV(10)

The DDE specification for conversion LIN1 of the address 40004 is:

Link: DBSR|PCIM!3:2:40004,LIN1(Low, High)

The DBSR server has a LIN conversion, whose syntax is:

address,LIN(Slow,Shigh,Clow,Chigh)

Slow: Server side low point

Shigh: Server side high point

Clow: Client side low point

Chigh: Client side high point

Modbus Driver 8.07 User Guide (for Pulse) 40

Conversion Links
The LIN, LIN1, LIN2, LIN3, LIN4, LIN5, LIN6, LIN7, LIN8, LINM linear conversions map
predefined ranges of raw data into engineering units defined as low scale to high scale
ranges of an Analog Value or Analog Pointer block. The raw data is interpreted as a non-
negative binary syntax.

The linear conversion algorithms listed below have the following abbreviations:

R = Raw value

L = Low scale

E = Engineering Units value

H = High scale

Table 4: Driver Conversions

Conv. Raw Range Raw to Eng. Units Eng. Units to Raw

Default, no
NONE conversion

LIN 0 - 4095 E=(R/4095)*(H-L)+L R=4095*(E-L)/(H-L)

LIN1 0 - 1023 E=(R/1023)*(H-L)+L R=1023*(E-L)/(H-L)

LIN2 0 - 999 E=(R/999)*(H-L)+L R=999*(E-L)/(H-L)

LIN3 0 - 9999 E=(R/9999)*(H-L)+L R=9999*(E-L)/(H-L)

LIN4 1000 - 4096 E=[(R-1000)/3096]*(H- R=3096*(E-L)/(H-L)+1000

L)+L

LIN5 4096 - 8191 E=[(R-4096)/4095]*(H- R=4095*(E-L)/(H-L)+4096

L)+L

LIN6 0001 - 8191 E=[(R-1)/8190]*(H-L)+L R=8190*(E-L)/(H-L)+1

LIN7 -32768 - E=[(R+32768)/65535]* R=65535*(E-L)/(H-L)-32768

32767 (H-L)+L

LIN8 0 - 65535 E=(R/65535)*(H-L)+L R=65535*(E-L)/(H-L)

LINM 0 - 32000 E=(R/32000)*(H-L)+L R=32000*(E-L)/(H-L)

M10 Multiplies the raw data by 10 and divides the value written to the controller
by 10

M100 Multiplies the raw data by 100 and divides the value written to the controller
by 100

M1K Multiplies the raw data by 1000 and divides the value written to the controller
by 1000

D10 Divides the raw data by 10 and multiplies the value written to the controller
by 10

D100 Divides the raw data by 100 and multiplies the value written to the controller
by 100

Modbus Driver 8.07 User Guide (for Pulse) 41

Displaying Driver Conversions

To display driver conversions, in the Project Communication Setup dialog box select a line
and then click the Get Info button.

Using Generic Conversions

The Pulse Drivers Server - PFWDRVR, has customizable conversions that can be configured
and used in your applications.

The required syntax is:

‘address’,‘conversion’

or
address’;‘conversion’, for national language support if the list separator is ';'
where address is the actual direct address or block name of the data to be converted.
The conversion can be one of the following:

Table 5: Generic Conversions

Conversion Returns Note

ValueOK OK/BAD

BCD(n) Binary Coded Decimal n=no. of bits

DIV(n.m) Divides the raw data by n.m and multiplies n.m=float no.
by n.m the value written to the controller for n=0, m=0 returns
the raw value

MUL(n.m) Multiplies the raw data by n.m and divides n.m=float no.
by n.m the value written to the controller

LIN(eng_Lo, Maps the range raw_Lo to raw_Hi as The conversion

eng_Hi, eng_Lo to eng_Hi performs a clamping
raw_Lo, operation
raw_Hi)

Byte(n) for n=1 returns 0 to 255 n=1 or 2

for n=2 returns 0 to 255
the decimal representation of the ‘n’ byte

Modbus Driver 8.07 User Guide (for Pulse) 42

 Table 5: Generic Conversions (Continued)

Nib(n) for n=0 returns the raw value n=1 to 4

for n=1 - 4 returns the ‘n’ nibble decimal
value, range 0 – 15

Alarm(alarm_L Returns 0 if raw value in alarm_Lo to

o, alarm_Hi) alarm_Hi range. Returns 1 if raw value
outside this range

Use the generic conversions together with the driver address to create blocks
with the Database Explorer. To prevent unpredictable results, set the conversion
field to NONE in the block.

Modbus Driver 8.07 User Guide (for Pulse) 43

$Variables
$Variables can be used to modify and read driver parameters at runtime. In a project
$Variables can be used instead of a direct address.
For example in 1:1:$port the address part of the item port":"station":"address, is
replaced by the $Variable. The following table displays driver supported $Variables. The INI
column indicates when the $variable has an INI file.

Table 6: $Variables

$Variable Description Type R/W INI

$PortRounding Rounding D R/W Y

$PortDebugMode Port debug status (On/Off)

$PortEmulation Port emulation mode D R Y

$PortFailures Number of failures per port after A R N

loading driver

$PortReadAfterWrite Port read after write D R/W Y

$PortReconnectTimeMin Port min. reconnect time A R/W Y

$PortRetries Number of retries per port after loading A R N

driver

$PortRetriesMax Port max retries A R/W Y

$PortScanTimeDefault Port default scan time A R/W Y

$PortSpyASCII Port converts to ASCII. Driver converts D R/W Y

saved in file bytes to ASCII characters
when possible

$PortSpyFileSize Port spy file size in Mbytes A R/W Y

$PortSpyFileSizeTotal Port spy total file size in Mbytes A R/W Y

$PortSpyMode Port debug spy status (On/Off) D R/W Y

$PortTimeOut Port timeout A R/W Y

$PortWriteCollapse Collapse write D R/W Y

$PortWriteQueueMax Port max. write queue if CollapseWrite A R/W Y

is 0

$PortWriteReflect Port reflect write - update read table D R/W Y

after successful write operation

Modbus Driver 8.07 User Guide (for Pulse) 44

$Port Variables for Two Transport Drivers

$Variable Description Type R/W INI

$PortTransport Global go to transport (per port), D R N

where:
1 - go to primary
2 - go to secondary
0 - secondary not operative

$PortTransport Auto return to primary transport D R Y

RetAuto

$PortTransportSec Use secondary transport (for two D R Y

transport drivers)

$PortTransportTest Checking secondary transport A R/W Y

Time validation time

$PortRetriesPrim Number of retries per port on primary A R N

transport after loading the driver

$PortRetriesSec Number of retries per port on secondary A R N

transport after loading the driver

$PortFailuresPrim Number of failures per port on the A R N

primary transport after loading the
driver

$PortFailuresSec Number of failures per port on the A R N

secondary transport after loading the
driver

$Station Variables

$Variable Description Type R/W INI

$StationAdvised Starts/stops advising and scanning D R/W Y

items from this station

$StationFailures Number of failures per station after A R N

loading driver

$StationReconnect Minimum reconnect time per station A R/W Y

TimeMin

$StationRetries Number of retries per station after A R N

loading driver

$StationRetriesLast Number of retries per station after the A R N

last successful transaction

Modbus Driver 8.07 User Guide (for Pulse) 45

$Station Variables for Two Transport Drivers

$Variable Description Type R/W INI

$StationTransport Go to transport (per station), where: D R/W N

1-Go to primary
2-Go to secondary
0-Failed communication

$StationRetriesLast Number of retries per station on the A R N

Prim primary transport after the last
successful transaction

$StationRetries Number of retries per station on the A R N

Prim primary transport after loading the
driver

$StationFailures Number of failures per station on the A R N

Prim primary transport after loading the
driver

$StationRetries Number of retries per station on the A R N

LastSec secondary transport after the last
successful transaction.

$StationRetriesSec Number of retries per station on the A R N

secondary transport after the driver was
loaded.

$StationFailuresSec Number of failures per station on the A R N

secondary transport after the driver was
loaded.

$Modem Variables

$Variable Description Typ R/W INI

e

$PortModemConnect Connection to PLC interval (in seconds A R/W Y

Interval or scans)

$PortModemConnect Defines measure unit of D R/W Y

IntervalUnit $EveryConnection (1=seconds,
0=scans).

$PortModemConnect Permanent PLC scanning after D R/W Y

Perm connection

$PortModemDialin Using by answer code of modem D R Y

$PortModemDialin PLC identification string waiting time A R/W Y

IDWait interval, in seconds.

$PortModemDialin Hangup after PLC identification D R/W Y

Mode

Modbus Driver 8.07 User Guide (for Pulse) 46

 $PortModemDialin Number of rings for auto answer A R Y
Rings

$PortModemDialout Number of dial attempt failures A R N

Attempts

$PortModemDialout Number of trying connect with PLC A R/W Y

AttemptsMax

$PortModemDialout Time in minutes to next dialing A R/W Y

Interval

$PortModemDialout Time in minutes for next dialing to PLC A R/W Y

RestoreTime after trying $RedialMaxRetries connect
with it

$PortModemUsed If a modem is used D R Y

$StationModem There is connection with PLC. Write 0 to D R/W N

Connected hang up

$StationModem Time in seconds from start of A R N

ConnectedTime connection

$StationModem PLC request connection D R/W N

ConnectReverse

$StationModem Time in seconds before dialing to PLC A R/W N

DialoutNextTime

Modbus Driver 8.07 User Guide (for Pulse) 47

Troubleshooting - Alarm Handler
Messages
The messages described in this section are displayed during driver startup in the Alarm
Explorer and/or Alarm Handler module.

Startup This message appears during startup and displays the driver name,
networking type and operation mode.
Time (HH:MM:SS) MODBUS Driver Ethernet/RS232/MBPLUS)
Port n, successfully loaded Time (HH:MM:SS) MODBUS Driver,
Port n, successfully loaded in Emulation mode!
Check that the Modbus driver started up, and in the defined mode.

Failure This message indicates communication failure between the PLC and
PC and is displayed when a value cannot be read/written in the
specified Max Timeout.
Modbus Driver, Port n, PLC m, failed during INPUT Modbus
Driver, Port n, PLC m, failed during OUTPUT
Check the physical link between the PC and PLC

Reconnection This message indicates that communications between the PC and PLC
has been re-established.
Time (HH:MM:SS) MODBUS Driver, Port n, PLC m, RECONNECTED

Command This message is displayed when an address or number of addresses

in the PLC cannot be accessed.
Time (HH:MM:SS) MODBUS Driver, Port n, PLC m, Address x,
READ-ERR:(# Error Code)! Time (HH:MM:SS) MODBUS Driver,
Port n, PLC m, Address x, WRITE-ERR:(#Error Code)!

Do the following:

Driver Correct the configuration and restart Pulse

PLC Correct PLC configuration

Read This message can be displayed when scanning addresses that are not
defined in the PLC.
Time (HH:MM:SS) Modbus Driver, Port n, PLC m, Address x
OK!
Open the Add New Stations dialog box and in the Memory
Configuration field define the addresses that will not be scanned.

Failed to Open This message appears when a Pulse driver tries to communicate with
a physical port that is used by another device. For example, COM1 is
used by another software.
Modbus, Port “1”, (RS232 –RJU) Failed to open
Check that the physical port that is defined in the virtual Pulse port is
not in use.

Modbus Driver 8.07 User Guide (for Pulse) 48

Error Codes
The following error codes are used in the Alarm Summary:

Code Description

01 The function code received in the query is not an enabled action for the
slave. When a Poll Program Complete command is issued, this code
indicates that no program function preceded it.

02 The data address received in the query is not an enabled address for the
slave.

03 A value contained in the query data field is not an enabled value for the
slave.

04 An unrecoverable error occurred when the slave attempted to perform the

requested action.

05 The slave has accepted the request and is processing it. This will take a long
time. The response is returned to prevent a timeout error from occurring in
the master. The master can next issue a Poll Program Complete message
to determine if processing is completed.

06 The slave is engaged in processing a long program command. The master

should re-transmit the message later when the slave is free.

07 The slave cannot perform the program function received in the query. This
code is returned for an unsuccessful programming request using function
code 13 or 14 decimal. The master should request diagnostic or error
information from the slave.

08 The slave tried to read extended memory, but detected a parity error in the
memory. The master can retry the request, however the slave may require
maintenance.

Modbus Driver 8.07 User Guide (for Pulse) 49

Appendix A - Specifications

Supported Protocols

Protocol Variants ASCII, RTU, Ethernet, MBPLUS, Packet data

Data types Input Register, Holding Register, Input, Output, Holding

Register (float), Extended Memory, Extended Memory
(float), Holding Register (long), Data, Extended Memory
(long).

No of Per port: 255

Programmable
Controllers

Scan Time 0 - 255 seconds

Timeout 0.5 - 50 seconds

Supported Serial Parameters

PC Ports COM1 to COM255

Baud Rates 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 56600,
115200, 128000 and 256000.

Data Bits 7, 8

Stop Bits 1, 1.5, 2

Parity None, Even, Odd.

Ethernet Supported Parameters

Host IP Address Your computer’s Local Internet Protocol Address.

If a computer has two communication cards when

configuring Ethernet settings, the default Host IP address
setting is always the first communication card's IP address.

Default Remote 0-65535. Default value 502

Port
The default port identifying the socket application.

Support When checked supports burst messages arriving from the

Unsolicited PLC.
Messages

Modbus Driver 8.07 User Guide (for Pulse) 50

MBPlus Supported Parameters

LAN No 0, 1

Data Paths 1-8

Packet Data Supported Parameters

Packet data is used for cellular communications.

Host IP Address Your computer’s Local Internet Protocol Address.

Default Remote 0-65535. Default value 1199

Port
The default port identifying the socket application.

Support When checked supports burst messages arriving from the

Unsolicited PLC.
Messages

Modbus Driver 8.07 User Guide (for Pulse) 51

Appendix B - Checking
Communication
It is important to check that communications through the driver between Pulse server and
the PLCs are constantly normal during project development and runtime. Therefore, always
check that communications are working properly when you start to develop your project.

Using Data Scope to Check Communication Status

Use the Data Scope utility as a diagnostic tool to check for normal communication between
the Pulse server and the PLCs, or between a Pulse client and a Pulse server.

To open Data Scope

1 From the Workstation’s Tools ribbon, click DataScope.

2 In the Name box, enter the string specifying the data value to check, or use immediate
alias. This string is usually composed of a PLC source, port, and an item or alias.

3 In the Value box, enter the value and click OK. To enter an alias, enclose between
ampersands (&alias&). The result will appear in the Status column after the Pulse
Server responds.

Modbus Driver 8.07 User Guide (for Pulse) 52

Using the Alarm Summary to Monitor
Communication Status
The Alarm Summary window displays alarms and system messages in chronological order.
For example, during startup it displays the Success/failure status of module initialization,
and the communication status between the Pulse server and the data sources.

To open the Alarm Summary window

1 In the AFCON Pulse Program Group, open the Runtime folder and click Alarm
Handler. From the Alarm Summary’s File menu, click Show Daily Log.

2 Scroll to the top to view all the system messages in the list.
During Pulse startup, the Alarm Summary is refreshed.

Modbus Driver 8.07 User Guide (for Pulse) 53

Monitoring Communication Event Messages
During runtime, the driver indicates problems and other events via messages sent to the
Alarm Publisher. In the Alarm Explorer (accessed from Operator Workstation>Tools
ribbon>Alarm Explorer button), the name of the driver is identified in the message
immediately after the time stamp, followed by a description of the event.

Using the Drivers Server to Check Communication

Status
The Driver Server interfaces between the Pulse Server and Clients on one hand, and
communications drivers on the other hand. In addition, it is a diagnostic tool that helps you
keep track of the drivers in your system.

1 From the Windows tray, right-click the Pulse Kernel Server icon, point to
Communication and click Pulse Drivers Server.

2 In the List of Loaded Drivers, check if the name of the driver is displayed in the
Assigned Ports list.

Modbus Driver 8.07 User Guide (for Pulse) 54

Appendix C - Solved Issues

PQR # PQR Description Fixed in

Revision

6403 Fixed a problem in which following a Stop Port action in an 7.95

RS232 connection, the appropriate COM port did not become
free.

This issue has been fixed.

6273 In a Hot Standby Redundancy configuration connected to an 7.86

Ethernet network, the secondary P-CIM Server lost
connection immediately after startup.

This issue has been fixed.

6127 Fixed a problem in which the behavior of the primary port 7.86
connection, when a secondary port was also connected and
configured, was not consistent with the behavior when no
secondary port was configured. Some settings or features
performed differently.

This issue has been fixed.

6101 Fixed a problem in which the user needed to restart P-CIM 7.86
after turning the DebugSpy setting on (modbus.ini>[1]
token>DebugSpy string>0 to 1).

This issue has been fixed. From this version, you turn the
DebugSpy tool on or off by using the following syntax in an
advised item field: Port:Plc:$PortSpyMode.

For example: 1:1:$PortSpyMode.

5872 When the Modbus driver was used in an Ethernet connection 7.86
with Multiple Network Cards enabled but no Host IP Address
defined, the driver tried to connect to a disconnected network
card.

This issue has been fixed. The Multiple Network Cards and
Host IP Address options are no longer relevant and have been
removed.

Instead, the Use Ping option was added to the Ethernet

Transport Parameters. This option enables the system to send
a ping, during P-CIM startup in an Ethernet network, to check
which PLCs are connected and operating. This option is
enabled by default.

Note: If the network contains a large number of PLCs, and

many are disconnected, the ping process time may take
several seconds to complete. If you don’t want to pass
through this long delay, you can disable the Use Ping option.

Modbus Driver 8.07 User Guide (for Pulse) 55

 5846 MODBUS Driver v7.59, working with an application with a 7.66
large number of PLCs (especially, if some PLCs are
disconnected), sometimes stopped responding.

This issue has been fixed. In the current version, if working in

Hot Redundancy Mode, make sure that
P-CIM Setup>Communication>Properties>ETHERNET
Transport Parameters>Multiple Network Cards is NOT
selected.

5815 In MODBUS Driver Rev. 7.58, the driver did not reconnect to 7.66
the PLC when P-CIM tried to restart after being disconnected.

This issue has been fixed. In the current version, make sure
that P-CIM
Setup>Communication>Properties>ETHERNET
Transport Parameters>Multiple Network Cards is
selected.

5172 In MODBUS Driver Rev. 7.39, when writing a single coil 7.58
action, and the "Force Multiple Write for all Stations" option is
selected (or in case that the "Enable Multiple Write" option is
selected for a specific PLC), the driver used the single coil
write command (05) instead of the multi coil write command
(0F Hex).

This issue has been fixed.

5386 In the MODBUS Driver Rev. 7.27 Configurator, if the "Host IP 7.58
Address" field is blank, the driver did not proceed with the
configuration, displaying an error message stating that the
“Host IP Address” must contain a valid IP address.

This issue has been fixed. In the current version, if the “Host
IP Address” field is blank, the driver retrieves the address of
the connected communication card.

4777 Max # references in messages values ignored by driver 7.39

Fixed an error in the driver’s handling of inconsecutive

addresses range that was discovered in version 7.36 of the
Modbus driver. The driver failed to update values on ranges
consisting of more than 70 addresses, although the maximum
number of addresses in a single range is set to 125 addresses.

4763 Reconnecting attempts not logged 7.39

In previous versions the driver’s reconnecting attempts were

incorrectly logged to the debug spy file. The problem was
recorded to occur when the Max. Retries value was set to
more than 10 consecutive reconnect attempts. As of this
version, the driver loges every reconnect attempt to the
debug spy file and when the maximum number of attempts is
reached, the cause of the failure is clearly logged. (For
example, failed to send or receive data from PLC).

Modbus Driver 8.07 User Guide (for Pulse) 56

 6503 Memory leaks occurred even when the string was 7.97
CollapseWrite=1

The DBSR does not increase its memory usage anymore when
the string is CollapseWrite=1.

6789 The Modbus Ethernet I/O Addresses’ Response Time 8.07

was Delayed

The response time for the Modbus Ethernet I/O addresses was
delayed when the Pulse application contained multiple
frames. Some of the frames returned values after a relatively
long delay partly caused by the PLC.

The issue is fixed. The

SupportMultipleSocketForSinglePLC in the Modbus ini
[portn] is enabled by default and can be manually disabled by
setting it to ‘0’.

To manually avoid delayed response time for Modbus Ethernet

I/O addresses, configure multiple sockets for the same PLC.

The driver can manage multiple sockets for one physical PLC.
This assures that the data is copied to the advised addresses
specified in the application using the actual PLC number. Make
sure that the digit number per PLC is equal to the number in
the multiple rows.

Solution:

To configure multiple sockets for the same PLC:

1 Go to the Project Setup window and click the Open

Communication Setup icon.
The Project Communication Setup window is displayed.

2 Click the Properties button.

The P-CIM Configurator for Modbus Driver dialog box is
displayed.

3 Click the Station Parameters button.

The Station Parameters - ETHERNET window is displayed.

4 Click the Modify button.

The Modify Station Parameters dialog box is displayed.

5 Define the PLC Number, IP Address, Port, Index, click

the Multi-Socket PLC checkbox to select the option and
provide the number of digits for the Min. Address
Length and click OK.

6 Repeat Step 5 for each PLC.

7 Go to the Poling Configuration window and define the

Polling frames to work simultaneously with the Multi
Socket PLC and set them to Always on scan. It is not
necessary to add frames to the PLC number used in the
application blocks and displays.

Modbus Driver 8.07 User Guide (for Pulse) 57

 6694 Undefined PLC(s) in the Secondary Transport caused 8.07
the driver not to send undefined PLC Parameter
messages of the Secondary Transport to the Alarm
Summary

When the PLC(s) in the Secondary Transport had undefined

PLC Parameter messages, the ModBus Driver did not send all
the messages of the Secondary Transport to the Alarm
Summary. This happened when the network type was set to
TCP/IP communication types such as Ethernet, Packet Data,
etc.

Undefined PLC(s) of the Secondary Transport also caused the

driver not to send communication failure messages to the
Alarm Summary.

The issue has been fixed.

6693 The Modbus Driver did not send the Stop/Resume 8.07
messages of the Secondary Transport to the Alarm
Summary

When the Use Secondary Transport option is selected in

the P-CIM Configurator for ModBus Driver dialog box and
the selected Network Type was Ethernet, Packet Data, etc.;
the Modbus Driver did not send Stop/Resume messages of the
Secondary Transport to the Alarm Summary.

The issue has been fixed. Stop/Resume messages of the

Secondary Transport are now sent to the Alarm Summary
when the Use Secondary Transport option is selected.

6691 The Modbus driver closed and deleted all sockets when 8.07
a ‘Resume’ process began

The Modbus Driver did not close and delete all sockets before
stopping TCP/IP communications for Ethernet, Packet Data,
and more.

Instead the ModBus driver immediately closed and deleted all

sockets at the beginning of a ‘Resume’ process, which caused
problems in the Hot Redundancy process.

The issue has been fixed. The Modbus Driver now closes and
deletes all sockets before stopping the TCP/IP communication
for Ethernet or Packet Data.

6655 The driver did not close the common socket for all PLCs 8.07
having the same IP Address and Port number

When the application had more than one PLC with the same
IP Address and Port number in the previous Modbus Driver
version; the driver did not close the common socket for all the
PLCs having the same IP Address and Port number when an
Unadvised action to all items of the PLCs were made.

The issue has been fixed.

Modbus Driver 8.07 User Guide (for Pulse) 58

 6625 Each address type did not have one switch for all 8.07
address types for each PLC

Each address type had a separate switch for a Zero Based

Address for each PLC.

The issue has been fixed. Now, there is only one switch for all
address types for each PLC.

6587 Zero Based Address references were not supported by 8.07

the Modbus driver

The ModBus driver now supports references for Zero Based

Addresses. For instance, instead of 1:1:400001 as the first
address of type 4XXXXX; the address 400000 can now be
used.

6531 The $PortTransportTestTime dollar switch only 8.07

supported integers as its value

The $PortTransportTestTime dollar switch in the Modbus

Driver only supported integers (whole numbers) as its value.
For example, if a value of 2.7 was provided for the
$PortTransportTestTime dollar switch, the number changed
into 2.0 (whole number).

At runtime, the user was able to change the value to a number

with a decimal point via Data Scope using the
$PortTransportTestTime dollar switch (i.e.,
"1:1:$PortTransportTestTime ").

The issue has been fixed. the $PortTransportTestTime dollar

switch can now accept a number with a decimal point as its
value.

6530 The $PortReconnectTimeMin dollar switch only 8.07

supported integers as its value

The $PortReconnectTimeMin dollar switch in the ModBus

Driver only supported integers (whole numbers) as its value.
For example, if a value of 2.7 was provided for the
$PortReconnectTimeMin dollar switch, the number changed
into 2.0 (whole number).

The issue has been fixed. the $PortReconnectTimeMin dollar

switch can now accept a number with a decimal as its value.

Modbus Driver 8.07 User Guide (for Pulse) 59

Appendix D - Known Issues

PQR # PQR Description

6060 In a Hot Redundancy configuration, a P-CIM Server was

connected to the clients over one network and to the PLCs over a
second network. When communication to the Active Server was
lost, the Passive Server became active and continued
communication on the client network, but reconnection with the
PLCs did not occur.

Afcon Software And Electronics Ltd. confirms that this is a known

issue in Modbus version 7.86, and will be solved in a future
version.

Modbus Driver 8.07 User Guide (for Pulse) 60

Appendix E - New Features

PQR # PQR Description New in

Revi-
sion

6309 Conversion LINM was added. 7.95

LINM provides support for momentum conversions. The

range is 0-32000.

Modbus Driver 8.07 User Guide (for Pulse) 61