Driver

Pulse Modbus Driver
User Guide
July 2015
Copyright
The information in this document is subject to change without prior notice and does not
represent a commitment on the part of AFCON Control and Automation Ltd., AFCON
Software and Electronics Division.
No part of this document may be used or reproduced in any manner whatsoever without
written permission from AFCON Control and Automation Ltd., AFCON Software and
Electronics Division.
The software described in this document is furnished 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 2015 AFCON Control and Automation Ltd., AFCON Software and Electronics
Division.
All rights reserved.
Pulse logos are registered trademarks of AFCON Control and Automation Ltd., AFCON
Software and Electronics Division.
Windows is a registered trademark of Microsoft Corporation in the United States and other
countries.
Modbus Driver User Guide
Table of Contents
Copyright....................................................................................................... 2
Introduction ...................................................................................................... 4
Requirements ................................................................................................. 5
Hardware .................................................................................................. 5
Software ................................................................................................... 5
Computer Resources .................................................................................. 5
Installation ........................................................................................................ 6
File Paths ....................................................................................................... 9
Hardware..................................................................................................... 10
Linking to a Single PLC in an RS232 Network ............................................... 10
Linking to a Network of PLCs for an RS-485 or RS-422 Network ..................... 10
Network Cable Wiring ............................................................................... 11
Network Requirements for Ethernet ............................................................ 11
Linking to a Network of PLCs for an SM85 or SA85 Network ........................... 12
Linking to a Modem .................................................................................. 12
Packet Data Connections ........................................................................... 13
Modbus Plus Connections .......................................................................... 13
Communication Setup.................................................................................... 14
Assigning the Modbus Driver to a Port......................................................... 14
Defining Multiple P-CIM Ports for a Single PLC ................................................... 15
Configuring Driver Parameters ........................................................................ 16
Scheduling Parameters ............................................................................. 17
Instructions for RS-232............................................................................. 18
Instructions for Ethernet and Packet Data.................................................... 20
Instructions for Modbus Plus ...................................................................... 23
Instructions for Modem ............................................................................. 25
Defining Advanced Parameters................................................................... 29
Defining Polling Configurations................................................................... 29
Basic Information ............................................................................................ 31
Bit Representation................................................................................... 31
CollapseWrite .......................................................................................... 31
ReflectWrite ............................................................................................ 31
Rounding ................................................................................................ 32
Referencing Driver Data in Pulse ..................................................................... 32
Address Syntax........................................................................................ 32
Syntax Table ........................................................................................... 32
Direct Access Syntax ..................................................................................... 37
Conversions ................................................................................................. 38
Conversion Links...................................................................................... 39
$Variables............................................................................................... 42
Troubleshooting - Alarm Handler Messages ..................................................... 46
Error Codes .................................................................................................. 47
Appendix A - Specifications ............................................................................. 48
Supported Protocols ................................................................................. 48
Supported Serial Parameters ..................................................................... 48
Ethernet Supported Parameters ................................................................. 48
MBPlus Supported Parameters ................................................................... 49
Packet Data Supported Parameters............................................................. 49
Appendix B - Checking Communication............................................................ 50
Using Data Scope to Check Communication Status ............................................ 50
Using the Alarm Summary to Monitor Communication Status .............................. 51
Monitoring Communication Event Messages ...................................................... 52
Using the Drivers Server to Check Communication Status................................... 52
Appendix C - Known Issues ............................................................................ 53
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
NOTE
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 PCs 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.
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.
NOTE
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
NOTE
For MBPlus networks: check that SA85 or SM85 are installed correctly.
Computer Resources
The driver needs roughly 5 MB of disk space.
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.
Select Pulse, select Communication Drivers and then Open to open the
Communication Drivers dialog box.
Select the Modbus driver and click the Install button.

The Pulse Driver Setup wizard is displayed.
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]).
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.
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
Generates a report detailing the installation of the driver files.
Report Errors
Generates a report detailing any error which may have occurred

during the driver installation.
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
Server
The Pulse Server starts up after you click Finish. After the
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
\Communication folder
Driver configuration program
MODBUSDR.DLL
Runtime driver
MODBUS.INI
Driver configuration initialization

file
DrvrPort.INI
This file contains all the

information defined in the Project
Communication Setup dialog box
file
MODBUS.HLP
Modbus driver Help
MBPTRANS.DLL
Modbus Plus transport driver.
NOTE
All files are restored by reinstalling the Modbus driver.
Hardware
This chapter displays the physical connections between a PC and the PLCs with which it
communicates.
NOTE
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
SHLD
CD
1 SHLD
RX 2
RX
RX
2 TX
TX 3
TX
TX
3 RX
DTR 4
DTR
DTR
4 RTS
GND 5
GND
GND
5 CTS
DSR 6
DSR
DSR
6 DSR
RTS 7
RTS
RTS
7 GND
CTS 8
CTS
CTS
8 CD
NC
20 DTR
Linking to a Network of PLCs for an RS-485 or RS-422 Network

The diagram below shows a PLC network layout.
P-CIM
RS485/RS232
PLC
RS232/RS485
RS485/RS232
PLC
RS485/RS232
PLC
10
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 TX
TX
3 RX
DTR
4 RTS
GND
5 CTS
DSR
6 DSR
RTS
7 GND
CTS
8 NC
NC
20 DTR
Network Requirements for Ethernet

NO CPU
NO CPU
HUB
Interface adapter
installed 3COM
P-CIM
11
Linking to a Network of PLCs for an SM85 or SA85 Network

P-CIM
SM85 or SA85 network adapter installed
Modbus plus network
PLC
PLC
PLC
Linking to a Modem
The diagram below shows linking to a modem.
P-CIM
Modem
Line
Telephone
Service
PLC
Modem
PLC
Modem
Line
Line
12
Packet Data Connections

The diagram below shows packet data connections which can be used for cellular
connections.
Line
Modem
P-CIM
PLC
Line
Modem
PLC
Line
Modem
Modbus Plus Connections

The diagram below shows MBPLUS connections.
12?
12?
4
9
3
8
2
7
Terminator
4
9
-------Network--------
3
8
2
7
1
6
4
9
3
8
2
7
1
6
Terminator
13
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 is displayed.
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 is displayed.
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.
14
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
system
This field defines the read bit access used. For example, if Octal is
used, the digits 8, 9 are not available. It is recommended to leave
the setting at its default of 10 decimal.
Lowest bit
number
Select 1 from the drop-down list to define the bit numbering for this
driver as 1-16.
When 0 is selected, the bit numbering for this driver is 0-15.
Emulation
Mode
When checked, the driver runs in emulation mode.

In emulation mode, the driver does not communicate with field
devices but reads and writes internally. Use this mode during
development.
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.
15
Configuring Driver Parameters

Define the Modbus drivers 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 parameters are described in Scheduling Parameters on page 17.

Transport and Station Parameters, where different dialog boxes are displayed according
to the selected network type.
Additional parameters (P-CIM Port, Use Secondary Transport)
16
Scheduling Parameters
Use the information in this table to complete the Scheduling parameters for all network
types.
Field
Description
P-CIM port
Displays the port selected in the Pulse Communication Setup

dialog box, Assigned Ports field.
Polling Configuration
When clicked, displays the Polling Configuration dialog box

where you can define blocks for a driver address with different
scan settings to that of the default scan parameters.
Simulate I/O
Check this option to work in Emulation mode only.

When checked, read items receive random values
continuously.
Read Before Bit Write
Reads and checks the registers last value immediately before

writing to a specific bit in the register.
Force Multiple Write

for all Stations
Check this option to instruct the driver to use the multiple

write function to force write a single register.
Timeout
The defined amount of time the driver waits 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
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
The minimum amount of time in minutes the Pulse driver waits

before trying to reconnect to a PLC declared as failed.
The default is 1 minute.
Default Min. Address

Length
Set the minimal address length.To match the minimal 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.
17
Instructions for RS-232

Defining Transport Parameters
1
In the Network Type field, select RS232 from the drop-down list to display the
Transport Parameters RS232 dialog box.
Complete this dialog box using the following information.
Field
Description
COM Port
Shows the computers export port.
Baud Rate
Shows the communication speed of the device.
Data Bits
Shows the number of bits in one byte.
Parity
Checks the correct combined bits of each byte in a message.
Stop Bits
Shows the number of bits in each byte signaling the end of the byte.
COM Mode
Suggests the communication type which can be:
RTU
ASCII
Station
Parameters
When clicked, displays the Station Parameters RS232 dialog box.
18
Defining Station Parameters

1
To display the Station Parameters RS232 dialog box, click the Station
Parameters button in either the P-CIM Configurator for Modbus Driver or the
Transport Parameters dialog boxes.
Click the Add button to open the Add New Stations dialog box.
Field
Description
PLC Number
Marks the logical number of the PLC in Pulse at runtime.
Min. Address
Length __
Digits
Sets the minimal address length. To match the minimal 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
Advanced
Parameters
When checked, displays the Advanced Parameters options, see

Defining Advanced Parameters on page 29 for further
information.
Select the number and PLC Type using information from the above table.
Click OK to save these definitions and to return to the Station Parameters dialog box.
Secondary Transport
Select the Use Secondary Transport option to enable the use of a secondary
communications channel (i.e, port, secondary server) in a Redundancy configuration.
19
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 display the Transport Parameters Ethernet or Transport Parameters
Packet Data dialog box.
Field
Description
Default Remote
Port
Defines the bidirectional connection method to the PLC from and

to the PC. In Packet Data, the default remote port value is 1195,
which can be changed.
Transport Protocol
Specify whether the transport protocol for the network is TCP or

UDP.
Multi Sockets
When checked, indicates that communication for each IP address

is made simultaneously when more than one IP address and port
are defined.
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. To avoid a long delay, you can disable the
Use Ping option.
Support
Unsolicited
Messages
When checked, sets Pulse in passive mode, in which the PLC

sends burst messages to Pulse. This method of communication
can only be used once per driver.
Station Parameters
Click this button to open the Station Parameters Ethernet

dialog box.
20

Field
Description
Number
Shows the logical number of the PLC in Pulse at runtime.
Min. Address
Length
Sets the minimal address length. To match the minimal length defined,
a leading 0 is added to every address that is below the threshold. An
address that is equal to or higher than the defined threshold, is not
changed.
IP Address
Shows the IP address of the PLC.
Port
Defines the bi-directional 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.
21
Field
Description
PLC Number
Marks the logical number of the PLC in Pulse at runtime.
IP Address
Shows 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
Length

threshold. An address that is equal to or higher than the defined
threshold, is not changed.
Show
Advanced
Parameters
When this option is checked, it displays the Advanced Parameters

options, see page Defining Advanced Parameters on page 29 for
further information.
Secondary Transport
22
Instructions for Modbus Plus

Defining Transport parameters
1
In the Network Type field, select MBPlus from the drop-down list to display the
Transport Parameters MBPlus dialog box.
Field
Description
LAN number
Shows the ID of the MBPlus card in the computer, for

example: SA85.
Data Paths
Shows the maximum paths where messages can be sent

simultaneously.
Station
Parameters
When clicked, displays the Station Parameters RS232

dialog box.

To open this dialog box, click the Station Parameters button from the P-CIM
Configurator for Modbus Driver or in the Transport Parameters dialog box.
23
Field
Description
PLC Number
Shows the logical number of the PLC in Pulse at runtime.
Min. Address
Length __ Digits

threshold. An address that is equal to or higher than the defined
threshold, is not changed.
Route
Sets the PLC routing address
Redundant Route
Sets the redundant PLC route. Use this option as a backup in case
the driver is unable to connect to the primary PLC.
Show Advanced
Parameters
When this option clicked, it displays the Advanced Parameters

options, see Defining Advanced Parameters on page 29 for
further information.
Complete this dialog box using the information from the above table.
Click OK to save these definitions and to return to the Station Parameters dialog
box.
Secondary Transport
24
Instructions for Modem

The Transport and Station parameters for this dialog box are similar to that of an RS232
connection, with the 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
Parameters dialog box.
This dialog box has the following fields:
Field
Description
Initialization
String
Initializes the connection between the modem and the PLC.
Default Phone
Number
The phone number used when a PLC does not have a specified
phone number.
Dial Using
Select the dialing mode, which can be either Tone or Pulse.
Phone
Parameters
Click this button to display the Phone Parameters dialog box

where PLCs and phone numbers can be assigned and displayed in a
list, see Defining phone parameters on page 28.
Redial
Parameters
This area defines the modem settings used for redialling to the PLC
when communication is not successful.
25
Redial After
__ Minutes
Defines the period in minutes the modem should

wait until it retries to reconnect to the PLC.
Max Retries
Defines the number of communication retries to

perform before communication failure is
declared.
A retry is an attempt to send a task to the PLC.
Auto-Answer
Enable
When the checkbox option is enabled, the PLC ID Parameters

options becomes active. In this mode, it immediately tries to
communicate to the relevant PLC after a PC receives ID string burst
messages.
PLC ID
Parameters
Click this button to display the PLC ID Parameters dialog box

where an identification string can be configured for each PLC.
Number of
Rings
The number of rings before auto-answer is employed.
Scheduling
This area has the following scheduling options:

Permanent
Connection
Check this checkbox option for a permanent

connection between the modems.
Ignore Delay
After Modem
Connection
Check this checkbox option to instruct the driver

to poll the PLC immediately after the connect
message is received from the remote modem.
Connect Every
__ Minutes
Define the schedule to connect in xxx amount of

minutes.
Every
Connection
Defines the number of time/scans when

connection is attempted.
Select Scans or Time from the drop-down list to
specify the type to use for every connection.
26
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.
Click the PLC ID Parameters button to display the PLC ID Parameters dialog box.
Click the Add button to open the Add PLC ID String dialog box.
Scroll to the relevant PLC number and then type in the string in the ID String field.
Click OK to return to the PLC ID Parameters dialog box. Complete this dialog box using
the information below:
Field
Description
Hang-up After
Getting PLC ID
String
Check when using two modems connected to two ports for:
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
waiting time
The waiting time (in seconds) for receiving information (range 1 - 15,
default is 1).
27
Defining phone parameters

1
Click the Phone Parameters button in the Modem Parameters dialog box to display
the Phones Parameters dialog box.
Click the Add button to open the Add Phone dialog box, where the association
between the Modem and PLC is defined.
In the Phone Number field type in the phone number that is associated with a PLC.
In the PLC list click the relevant PLC number.

The phone number is displayed next to the selected PLC number.
Click OK to confirm and to return to the Phone Parameters dialog box where the
associated PLC and phone numbers are listed.
28
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.
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.
29
Click the Add button to open the Add Polling Block dialog box.
This dialog box has the following fields and buttons:
Field
Description
Always OnScan
When checked, defines that item/s are continually scanned, even

if an item is not an advised item in the application.
PLC
The number of the relevant PLC.
Start Address
The first address in the block that is configured.
Quantity
The total number of addresses in the addresses block.
Scan time
The total amount of time the address block is scanned.
Fill the Add Polling Block dialog box using the information above.
Click OK.
The definitions are displayed in the Polling Configuration dialog box.
30
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.
NOTE
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.
31
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.
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 drivers 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.
Syntax Table
Table 1: Driver Syntax
Modicon Syntax
Application
Syntax
Read,
Write
Type
Value Range
4-Digit
Note
1
Output
0001 - 0999
R/W
bit
0-1
Input
1001 - 1999
bit
0-1
Input Register
3001 - 3999
register
0-65535
Input Register Float
F3001 - F3998
32 bits
IEEE
Floating
Point
Input Register Long
L3001 - L3998
32 bits
Unsigned
Long
0-4294967295
32
Table 1: Driver Syntax (Continued)

Input Register Time
T3001 - T3998
Time
Format
0D0H0M0S0M
s49D17H2M47S
295Ms
Input Register Sign
S3001 - S3999
16 bits
Signed
Integer
-32768 +32767
Input Register Double
D3001 - D3996
64 bits
Floating
Point
Input Register Signed Long
SL3001 - SL3998
32 bits
Signed
Long
-2147483648 +2147483647
Holding Register
4001 - 4999
R/W
register
0-65535
Holding Register
- Float
F4001 - F4998
R/W
float num.
Holding Register
- Long
L4001 - L4998
R/W
long num.
0-4294967295
Holding Register
- Time
T4001 - T4998
R/W
string
0D0H0M0S0M
s49D17H2M47S
295Ms
Holding Register
- Sign
S4001 - S4999
R/W
16 bits
Signed
Integer
-32768 +32767
Holding Register
- Double
D4001 - D4996
R/W
64 bits
Floating
Point
Holding Register
- Signed Long
SL4001 - SL4998
R/W
32 bits
Signed
Long
-2147483648 +2147483647
Holding Register
- Write Only
W4001 - W4999
Event Status
EV0 EV191
bit
0-1
Alarm Status
AL0 AL191
bit
0-1
Output
00001 - 09999
R/W
bit
0-1
Input
10001 - 19999
bit
0-1
Input Register
30001 - 39999
register
0-65535
5-Digit
33

F30001 - F39998
32 bits
IEEE
Floating
Point
Input Register Long
L30001 - L39998
32 bits
Unsigned
Long
0-4294967295
Input Register Time
T30001 - T39998
Time
Format
0D0H0M0S0M
s49D17H2M47S
295Ms
Input Register Sign
S30001 S39999
16 bits
Signed
Integer
1:1:5400500
D30001 D39996
64 bits
Floating
Point
SL30001 SL39998
32 bits
Signed
Long
1:1:5400500
Holding Register
40001 - 49999
R/W
register
0-65535
Holding Register
- Float
F40001 - F49998
R/W
float num.
Holding Register
- Long
L40001 - L49998
R/W
long num.
0-4294967295
Holding Register
- Time
T40001 - T49999
R/W
string
0D0H0M0S0M
s49D17H2M47S
295Ms
Holding Register
- Sign
S40001 S49999
R/W
16 bits
Signed
Integer
1:1:5400500
Holding Register
- Double
D40001 D49996
R/W
64 bits
Floating
Point
Holding Register
- Signed Long
SL40001 SL49998
R/W
32 bits
Signed
Long
1:1:5400500
Holding Register
- Write Only
W40001 W46536
Event Status
EV0 EV191
bit
0-1
Alarm Status
AL0 AL191
bit
0-1
34

6-Digit
Output
000001 - 065535
R/W
bit
0-1
Input
100001 - 165535
bit
0-1
Input Register
300001 - 365535
register
0-65535
F300001 F365535
32 bits
IEEE
Floating
Point
Input Register Long
L300001 L365535
32 bits
Unsigned
Long
0-4294967295
Input Register Time
T300001 T365535
Time
Format
0D0H0M0S0M
s49D17H2M47S
295Ms
Input Register Sign
S300001 S365536
16 bits
Signed
Integer
-32768 +32767
D300001 D365533
64 bits
Floating
Point
SL300001 SL365535
32 bits
Signed
Long
-2147483648 +2147483647
Holding Register
400001 - 465536
R/W
register
0-65535
Holding Register
- Float
F400001 465535
R/W
float num.
Holding Register
- Long
L400001
L465535
R/W
long num.
0-4294967295
Holding Register
- Time
T400001 T465535
R/W
string
0D0H0M0S0M
s49D17H2M47S
295Ms
Holding Register
- Sign
S400001 S465536
R/W
16 bits
Signed
Integer
-32768 +32767
Holding Register
- Double
D400001 D465533
R/W
64 bits
Floating
Point
Holding Register
- Signed Long
SL400001 SL465535
R/W
32 bits
Signed
Long
Holding Register
- Write Only
W400001 W465536
-2147483648 +2147483647
35

Extended
Memory
600000 - 699999
R/W
register
0-65535
Extended
Memory - Float
F600000 F699998
R/W
float num.
Extended
Memory - Long
L600000
L699998
R/W
long. num.
0-4294967295
Extended
Memory - Time
T600000 T699998
R/W
Time
Format
0D0H0M0S0M
s49D17H2M47S
295Ms
Extended
Memory - Sign
S600000 S699999
R/W
16 bits
Signed
Integer
-32768 +32767
Extended
Memory Double
D600000 D699996
R/W
64 bits
Floating
Point
Extended
Memory - Signed
Long
SL600000 SL699999
R/W
32 bits
Signed
Long
-2147483648 +2147483647
Extended
Memory - Write
Only
W600000 SL699998
Event Status
EV0 EV191
bit
0-1
Alarm Status
AL0 AL191
bit
0-1
NOTE
1
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
Year - after 2000, for example: year 2015 => 15

For example: Set the string value 1.8.15 12:30:00 to the address 1:1:TS400001 causes
the PLC 1 to update its current date and time to 1.8.15 12:30:00
If you want, you can add the field of milliseconds after . . Another use of this prefix
is to synchronize the PLC time and the PC time. This is done by writing the string value
PC to an address with the prefix of TS (i.e., 1:1:TS400001). By doing so, the PLC
updates its current date and time to the PC date and time.
36
Direct Access Syntax

When defining blocks in the Database Explorer, you should only set the Item in the blocks
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:
Separately, in three labeled fields

Together, in one field usually labeled Link. the vertical bar ("|") and exclamation mark
("!") separators are used. For example: Server|Topic!Item "
NOTE
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
37
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)
NOTE
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
38
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 nonnegative 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 2:
Conv.
Raw Range
Raw to Eng. Units
Eng. Units to Raw
NONE
Default, no
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]*(HL)+L
R=3096*(E-L)/(HL)+1000
LIN5
4096 - 8191
E=[(R-4096)/4095]*(HL)+L
R=4095*(E-L)/(HL)+4096
LIN6
0001 - 8191
E=[(R-1)/8190]*(HL)+L
R=8190*(E-L)/(H-L)+1
-32768 - 32767
E=[(R+32768)/65535]*
(H-L)+L
R=65535*(E-L)/(H-L)32768
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
LIN7
39
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 3: Generic Conversions
Conversion
Returns
ValueOK
OK/BAD
BCD(n)
Binary Coded Decimal
n=no. of bits
DIV(n.m)
Divides the raw data by n.m and multiplies

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

by n.m the value written to the controller
n.m=float no.
LIN(eng_Lo,
eng_Hi,
raw_Lo,
raw_Hi)
Maps the range raw_Lo to raw_Hi as

eng_Lo to eng_Hi
The conversion
performs a clamping
operation
Byte(n)
for n=1 returns 0 to 255

for n=2 returns 0 to 255
the decimal representation of the n byte
n=1 or 2
Note
40
Nib(n)
for n=0 returns the raw value

for n=1 - 4 returns the n nibble decimal
value, range 0 15
n=1 to 4
Alarm(alarm_L Returns 0 if raw value in alarm_Lo to

alarm_Hi range. Returns 1 if raw value
o, alarm_Hi)
outside this range
NOTE
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.
41
$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.
$Variable
Description
Type
R/W
INI
$PortRounding
Rounding
R/W
$PortDebugMode
Port debug status (On/Off)
$PortEmulation
Port emulation mode
$PortFailures
Number of failures per port after

loading driver
$PortReadAfterWrite
Port read after write
R/W
$PortReconnectTimeMin
Port min. reconnect time
R/W
$PortRetries
Number of retries per port after loading

driver
$PortRetriesMax
Port max retries
R/W
$PortScanTimeDefault
Port default scan time
R/W
Port converts to ASCII. Driver converts

saved in file bytes to ASCII characters
when possible
R/W
$PortSpyFileSize
Port spy file size in Mbytes
R/W
$PortSpyFileSizeTotal
Port spy total file size in Mbytes
R/W
$PortSpyMode
Port debug spy status (On/Off)
R/W
$PortTimeOut
Port timeout
R/W
$PortWriteCollapse
Collapse write
R/W
$PortWriteQueueMax
Port max. write queue if CollapseWrite

is 0
R/W
Port reflect write - update read

table after successful write
operation
R/W
$PortSpyASCII
$PortWriteReflect
42
$Port Variables for Two Transport Drivers
$Variable
Description
Type
R/W
INI
Global go to transport (per port),

where:
1 - go to primary
2 - go to secondary
0 - secondary not operative
Auto return to primary transport
$PortTransportSec
Use secondary transport (for two

transport drivers)
$PortTransportTest
Time
Checking secondary transport

validation time
R/W
$PortRetriesPrim
Number of retries per port on primary

transport after loading the driver
$PortRetriesSec
Number of retries per port on secondary

transport after loading the driver
Number of failures per port on the

primary transport after loading the
driver
Number of failures per port on the

secondary transport after loading the
driver
$Variable
Description
Type
R/W
INI
$StationAdvised
Starts/stops advising and scanning

items from this station
R/W
$StationFailures
Number of failures per station after

loading driver
Minimum reconnect time per station
R/W
$StationRetries
Number of retries per station after

loading driver
$StationRetriesLast
Number of retries per station after the

last successful transaction
$PortTransport
$PortTransport
RetAuto
$PortFailuresPrim
$PortFailuresSec
$Station Variables
$StationReconnect
TimeMin
43
$Station Variables for Two Transport Drivers
$Variable
Description
Type
R/W
INI
Go to transport (per station), where:

1-Go to primary
2-Go to secondary
0-Failed communication
R/W
$StationRetriesLast
Prim
Number of retries per station on the

primary transport after the last
successful transaction
$StationRetries
Prim

driver
$StationFailures
Prim
Number of failures per station on the

driver
$StationRetries
LastSec

secondary transport after the last
successful transaction.

secondary transport after the driver was
loaded.
Number of failures per station on the

secondary transport after the driver was
loaded.
$StationTransport
$StationRetriesSec
$StationFailuresSec
44
$Modem Variables
$Variable
Description
Typ
e
R/W
INI
$PortModemConnect
Interval
Connection to PLC interval (in seconds

or scans)
R/W
$PortModemConnect
IntervalUnit
Defines measure unit of

$EveryConnection (1=seconds,
0=scans).
R/W
$PortModemConnect
Perm
Permanent PLC scanning after

connection
R/W
$PortModemDialin
Using by answer code of modem
$PortModemDialin
IDWait
PLC identification string waiting time

interval, in seconds.
R/W
Hangup after PLC identification
R/W
Number of rings for auto answer
Number of dial attempt failures
Number of trying connect with PLC
R/W
Time in minutes to next dialing
R/W
$PortModemDialout
RestoreTime
Time in minutes for next dialing to PLC

after trying $RedialMaxRetries connect
with it
R/W
$PortModemUsed
If a modem is used
$StationModem
Connected
There is connection with PLC. Write 0 to

hang up
R/W
$StationModem
ConnectedTime
Time in seconds from start of

connection
PLC request connection
R/W
Time in seconds before dialing to PLC
R/W
$PortModemDialin
Mode
$PortModemDialin
Rings
$PortModemDialout
Attempts
$PortModemDialout
AttemptsMax
$PortModemDialout
Interval
$StationModem
ConnectReverse
$StationModem
DialoutNextTime
45
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:
Read
Driver
Correct the configuration and restart Pulse
PLC
Correct PLC configuration
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.
46
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.
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.
47
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
Programmable
Controllers
Per port: 255
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 computers 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
Port
Support
Unsolicited
Messages
0-65535. Default value 502

The default port identifying the socket application.
When checked supports burst messages arriving from the
PLC.
48
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
Default Remote
Port
Support
Unsolicited
Messages
Your computers Local Internet Protocol Address.

0-65535. Default value 1199
The default port identifying the socket application.
When checked supports burst messages arriving from the
PLC.
49
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 Workstations Tools ribbon, click DataScope.
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.
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.
50
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 Summarys File menu, click Show Daily Log.
Scroll to the top to view all the system messages in the list.
During Pulse startup, the Alarm Summary is refreshed.
51
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.
In the List of Loaded Drivers, check if the name of the driver is displayed in the
Assigned Ports list.
52
Appendix C - Known Issues

Work Item No.
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.
53

Driver

Uploaded by

Copyright:

Available Formats

Driver

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Driver

Uploaded by

Copyright:

Available Formats

Pulse Modbus Driver

Modbus Driver User Guide

Modbus Driver User Guide

4 digit: 384 and 484

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

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

Modbus Driver User Guide

Modbus Driver User Guide

Select the Modbus driver and click the Install button.

Modbus Driver User Guide

Modbus Driver User Guide

Generates a report detailing the installation of the driver files.

Generates a report detailing any error which may have occurred

Modbus Driver User Guide

Driver configuration program

Driver configuration initialization

This file contains all the

Modbus driver Help

Modbus Plus transport driver.

All files are restored by reinstalling the Modbus driver.

Modbus Driver User Guide

Further information on hardware installation can be found in Modicon

Linking to a Single PLC in an RS232 Network

Linking to a Network of PLCs for an RS-485 or RS-422 Network

Modbus Driver User Guide

Network Cable Wiring

Network Requirements for Ethernet

Modbus Driver User Guide

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

SM85 or SA85 network adapter installed

Modbus plus network

Modbus Driver User Guide

Packet Data Connections

Modbus Plus Connections

Modbus Driver User Guide

Go to Pulse Setup and click Communication.

Modbus Driver User Guide

Select the parameter values according to the following:

This is a virtual port that has no functionality in the software. A

When checked, the driver runs in emulation mode.

Defining Multiple P-CIM Ports for a Single PLC

Modbus Driver User Guide

Configuring Driver Parameters

This dialog box has three sections:

Scheduling parameters are described in Scheduling Parameters on page 17.

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

Modbus Driver User Guide

Displays the port selected in the Pulse Communication Setup

When clicked, displays the Polling Configuration dialog box

Check this option to work in Emulation mode only.

Read Before Bit Write

Reads and checks the registers last value immediately before

Force Multiple Write

Check this option to instruct the driver to use the multiple

Default Scan Time

Default value is 0:0 seconds.

When set to minimum value of 0.0, the driver constantly

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

The number of communication retries performed before

The minimum amount of time in minutes the Pulse driver waits