ProSoft Technology 5204SE-MNET-PDPMV1 ProductsPROFIBUS Master for Modicon Modbus TCP/IP Owner's Manual

PDPMV1

ProLinx Gateway

PROFIBUS DPV1 Master

PROTOCOL MANUAL

February 8, 2017

Your Feedback Please

We always want you to feel that you made the right decision to use our products. If you have suggestions, comments, compliments or complaints about our products, documentation, or support, please write or call us.

How to Contact Us

ProSoft Technology, Inc.

9201 Camino Media, Suite 200

Bakersfield, CA 93311

+1 (661) 716-5100

+1 (661) 716-5101 (Fax) www.prosoft-technology.com [email protected]

Copyright © 2017 ProSoft Technology, Inc. All rights reserved.

PDPMV1 Protocol Manual

February 8, 2017

ProSoft Technology

®

, ProLinx

®

, inRAx

®

, ProTalk

®

, and RadioLinx

®

are Registered Trademarks of ProSoft

Technology, Inc. All other brand or product names are or may be trademarks of, and are used to identify products and services of, their respective owners.

ProSoft Technology

®

Product Documentation

In an effort to conserve paper, ProSoft Technology no longer includes printed manuals with our product shipments.

User Manuals, Datasheets, Sample Ladder Files, and Configuration Files are provided on the enclosed CD-ROM in

Adobe

®

Acrobat Reader file format (.PDFs). These product documentation files may also be freely downloaded from our web site: www.prosoft-technology.com

Important Installation Instructions

Power, Input, and Output (I/O) wiring must be in accordance with Class I, Division 2 wiring methods, Article 501-4 (b) of the National Electrical Code, NFPA 70 for installation in the U.S., or as specified in Section 18-1J2 of the Canadian

Electrical Code for installations in Canada, and in accordance with the authority having jurisdiction. The following warnings must be heeded:

WARNING - EXPLOSION HAZARD - SUBSTITUTION OF COMPONENTS MAY IMPAIR SUITABILITY FOR CLASS

I, DIV. 2;

WARNING - EXPLOSION HAZARD - WHEN IN HAZARDOUS LOCATIONS, TURN OFF POWER BEFORE

REPLACING OR WIRING MODULES

WARNING - EXPLOSION HAZARD - DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN

SWITCHED OFF OR THE AREA IS KNOWN TO BE NON-HAZARDOUS.

THIS DEVICE SHALL BE POWERED BY CLASS 2 OUTPUTS ONLY.

ProLinx

®

Products Warnings

WARNING – EXPLOSION HAZARD – DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN

SWITCHED OFF OR THE AREA IS KNOWN TO BE NON-HAZARDOUS.

AVERTISSEMENT – RISQUE D'EXPLOSION – AVANT DE DÉCONNECTER L'EQUIPMENT, COUPER LE

COURANT OU S'ASSURER QUE L'EMPLACEMENT EST DÉSIGNÉ NON DANGEREUX.

ProLinx Gateways with Ethernet Ports

Series C ProLinx™ Gateways with Ethernet ports do NOT include the HTML Web Server. The HTML Web Server must be ordered as an option. This option requires a factory-installed hardware addition. The HTML Web Server now supports:



8 MB file storage for HTML files and associated graphics files (previously limited to 384K)



32K maximum HTML page size (previously limited to 16K)

To upgrade a previously purchased Series C model

Contact your ProSoft Technology distributor to order the upgrade and obtain a Returned Merchandise Authorization

(RMA) to return the unit to ProSoft Technology.

PDPMV1 ♦ ProLinx Gateway


Contents

Contents

Protocol Manual

Your Feedback Please ........................................................................................................................ 2

How to Contact Us .............................................................................................................................. 2

ProSoft Technology ® Product Documentation .................................................................................... 2

Important Installation Instructions ....................................................................................................... 3

ProLinx

®

Products Warnings ............................................................................................................... 3

ProLinx Gateways with Ethernet Ports ............................................................................................... 3

To upgrade a previously purchased Series C model ..................................................................... 3

1 Functional Overview

1.1

1.2

1.3

1.3.1

1.3.2

1.4

1.3.3

1.3.4

1.5

1.6

9

About the PROFIBUS Protocol ............................................................................... 10

Compatibility Note ................................................................................................... 11

PROFIBUS DP Architecture .................................................................................... 12

How Cable Length Affects Communication Rate .................................................... 12

Bus Access .............................................................................................................. 12

Token Passing ......................................................................................................... 13

Master/Slave Polling ................................................................................................ 13

Communication Types ............................................................................................. 14

Master/Slave Communication Phases .................................................................... 15

Gateway Internal Database ..................................................................................... 16

2 Configuration

2.1

2.1.1

2.1.2

2.1.3

2.2

2.2.1

2.2.2

2.2.3

2.2.4

2.2.5

2.2.6

2.2.7

2.2.8

2.2.9

2.2.10

2.2.11

2.2.12

2.2.13

2.2.14

2.2.15

2.3

2.4

2.4.1

2.4.2

2.5

2.4.3

2.4.4

17

Configuring the Gateway ......................................................................................... 18

Installing ProSoft Configuration Builder Software ................................................... 18

Setting Up the Project ............................................................................................. 22

Setting Gateway Parameters .................................................................................. 24

PROFIBUS Master DPV1........................................................................................ 26

Input Start Register ................................................................................................. 26

Input Data Size ........................................................................................................ 26

Output Start Register ............................................................................................... 26

Output Data Size ..................................................................................................... 26

Input Byte Swap ...................................................................................................... 27

Output Byte Swap ................................................................................................... 27

Mailbox Register ...................................................................................................... 28

Slave Diagnostics Register ..................................................................................... 29

Alarm Register ......................................................................................................... 29

Status Data Register ............................................................................................... 29

Minimum Command Delay ...................................................................................... 29

Response Timeout .................................................................................................. 29

Watchdog Register .................................................................................................. 29

Watchdog Timeout .................................................................................................. 30

Watchdog Reset Value ............................................................................................ 30

PROFIBUS Master Commands .............................................................................. 31

Example Mailbox Commands ................................................................................. 33

Set Operating Mode ................................................................................................ 33

Get Live List ............................................................................................................ 38

Start/Stop Slaves ..................................................................................................... 43

Other Mailbox Commands....................................................................................... 49

Configuring the PROFIBUS DP Network ................................................................ 52

ProSoft Technology, Inc.

February 8, 2017

Page 5 of 150

Contents

Protocol Manual

2.6

2.7

2.5.1

2.5.2

2.5.3



Installing the GSD Files .......................................................................................... 52

Configuring the PROFIBUS Slaves ........................................................................ 53

Printing the ProLinx Memory Map .......................................................................... 69

Downloading the Project to the Gateway ............................................................... 71

Backing Up the Project ........................................................................................... 72

3 Mailbox Messaging

3.1

3.1.1

3.2

3.2.1

3.2.2

3.2.3

3.2.4

3.2.5

3.2.6

3.2.7

3.2.8

3.2.9

3.2.10

3.3

3.3.1

3.3.2

3.3.3

3.3.4

3.3.5

75

Mailbox Message Queuing ..................................................................................... 76

Queue Timeouts ..................................................................................................... 76

Special Function Mailbox Messaging Commands .................................................. 77

Mailbox Message: Set Operating Mode ................................................................. 78

Mailbox Message: Set Slave Mode ........................................................................ 80

Mailbox Message: Get Slave Diagnostics .............................................................. 83

Mailbox Message: Get Slave Configuration ........................................................... 86

Mailbox Message: Get Database Information ........................................................ 87

Mailbox Message: Get Live List .............................................................................. 90

Mailbox Message: Acyclic Data Read: Class 1 ...................................................... 92

Mailbox Message: Acyclic Data Write: Class 1 ...................................................... 94

Mailbox Message: Start Slave ................................................................................ 96

Mailbox Message: Stop Slave ................................................................................ 97

Mailbox Messaging Error Codes........................................................................... 100

Acyclic Message Status Word .............................................................................. 100

Return Codes ........................................................................................................ 101

Error Codes ........................................................................................................... 102

DP-V1 Error Codes ............................................................................................... 103

Command Error Codes ......................................................................................... 104

4 Diagnostics and Troubleshooting

4.1

4.2

4.3

4.3.1

4.3.2

4.4

4.5

4.5.1

4.5.2

4.6

4.6.1

4.6.2

4.6.3

4.6.4

4.7

4.6.5

4.6.6

4.7.1

105

Required Hardware ............................................................................................... 106

Basic Troubleshooting Steps ................................................................................ 107

PROFIBUS DP-V1 (PDPMV1 Driver) Master LED Indicators .............................. 108

PROFIBUS Master Indicators ............................................................................... 108

Examples .............................................................................................................. 109

Viewing the Online Status of the PROFIBUS Network ......................................... 110

Using ProSoft Configuration Builder (PCB) for Diagnostics ................................. 112

Using the Diagnostic Window in ProSoft Configuration Builder - PLX ................. 112

Main Menu ............................................................................................................ 115

Standard PROFIBUS Slave Diagnostic Bytes ...................................................... 117

Byte 0 - Station Status 1 Bits ................................................................................ 117



Byte 3 - Master Address ....................................................................................... 118

Byte 4 - Ident Number High .................................................................................. 118

Byte 5 - Ident Number Low ................................................................................... 118

Status and Status Mapping ................................................................................... 119

PDPMV1 Command Status Data Area ................................................................. 120

5 Reference

5.1

5.1.1

Page 6 of 150

121

PROFIBUS comDTM ............................................................................................ 122

ProSoft Technology Product Availability ............................................................... 122


February 8, 2017



5.1.2

5.1.3

5.1.4

5.2

5.1.5

5.1.6

5.3

5.4

5.5

5.6

Contents

Protocol Manual

Introduction to PROFIBUS comDTM .................................................................... 123

System Requirements ........................................................................................... 126

Installation ............................................................................................................. 127

Quick Start ............................................................................................................. 128

Verifying the comDTM Version and comDTM Install Version ............................... 133

RS-232 Configuration/Debug Port ........................................................................ 139

DB9 to Mini-DIN Adaptor (Cable 09) ..................................................................... 140

PROFIBUS Master Port ........................................................................................ 141

Supported PROFIBUS Services ........................................................................... 142

Constructing a Bus Cable for PROFIBUS DP ....................................................... 143

6 Support, Service & Warranty

6.1

6.2

147

Contacting Technical Support ............................................................................... 147

Warranty Information ............................................................................................. 148

149 Index


February 8, 2017

Page 7 of 150

Contents

Protocol Manual



Page 8 of 150 ProSoft Technology, Inc.

February 8, 2017



1 Functional Overview

Functional Overview

Protocol Manual

In This Chapter

 About the PROFIBUS Protocol .............................................................. 10

 Compatibility Note ................................................................................. 11

 PROFIBUS DP Architecture .................................................................. 12

 Communication Types ........................................................................... 14

 Master/Slave Communication Phases ................................................... 15

 Gateway Internal Database ................................................................... 16

The PROFIBUS Master protocol driver exists as a single port implementation.

The driver can be configured as a Class 1 and Class 2 PROFIBUS Master to interface with other PROFIBUS slave devices. The unit is also used for configuration of the nodes on the PROFIBUS network. It provides access to standard and extended diagnostic information, as well as freeze/sync capability,

Acyclic Communication (DPV1, Class 1 and 2), and Alarm Handling (DPV1). The

PROFIBUS Master port can be used to continuously interface with PROFIBUS slave devices over a serial communication interface (RS-485).


February 8, 2017

Page 9 of 150

Functional Overview

Protocol Manual

1.1 About the PROFIBUS Protocol



PROFIBUS (Process Field Bus) is a widely used, open-standards protocol created by a consortium of European factory automation suppliers in 1989.

PROFIBUS is a Master/slave protocol. The Master establishes a connection to the remote slave. When the connection is established, the Master sends the

PROFIBUS commands to the slave.

The ProLinx PDPMV1 gateway unit acts as an input/output module between devices on a PROFIBUS DP network and any other communication protocol. The gateway uses an internal database to send data and mailbox requests and responses to all PROFIBUS slaves on the PROFIBUS DP network.

PROFIBUS supports a variety of network types. The network type supported by the PLX-PDPMV1 gateway is PROFIBUS DP version 1.0, which is designed for remote I/O systems, motor control centers, and variable speed drives.


February 8, 2017



1.2 Compatibility Note

Functional Overview

Protocol Manual

The PDPMV1 product is not backward-compatible with the PDPM product due to new enhancements and command structure. The PDPMV1 PROFIBUS DP-V1

Master gateway provides enhanced features beyond the PDPM DP-V0 gateway as follows:

1 Increased Cyclic I/O. The PDPMV1 provides 768 Words of Input and 768

Words of Output.

2 ProSoft Configuration Builder (PCB) complete support. The PCB provides module-level configuration and integrated PROFIBUS Master network configuration support.

3 The PDPMV1 Master supports DP-V1 Class 1 or Class 2 DPV1 features such as acyclic communication with slaves for parameterization and other slave settings, alarm handling, extended diagnostics.


February 8, 2017

Page 11 of 150

Functional Overview

Protocol Manual

1.3 PROFIBUS DP Architecture



The PROFIBUS DP-V1 Master network supports multiple Master systems with several slaves.

The following table shows the most important features of PROFIBUS DP-V1

Master:

Standard EIN 501 70

DIN 19245

Transmission equipment (Physical) EIA RS-485

IEC 1158-2 (through link or coupler)

Fiber Optic Cable (not available)

Transfer procedure Half-duplex

Bus topology

Bus cable type

Connector

Number of nodes on the bus

Linear bus with active bus termination

Shielded twisted pair conductors

9-pin D-Sub

Max: 32 with no repeaters

Max: 125 with 3 repeaters in 4 segments

1.3.1 How Cable Length Affects Communication Rate

Max Bus Cable Length Per Segment

1.2 km

1.2 km

1.2 km

1.0 km

0.5 km

0.2 km

0.1 km

0.1 km

0.1 km

Baud Rates (for 12 Mbps cable)

9.6 kbit/sec

19.2 kbit/sec

93.75 kbit/sec

187.5 kbit/sec

500 kbit/sec

1.5 Mbit/sec

3 Mbit/sec

8 Mbit/sec

12 Mbit/sec

1.3.2 Bus Access

Two different bus access procedures handle the various communication requirements for the PROFIBUS DP-V1 Master topology:

 Token Passing

 Polling


February 8, 2017



1.3.3 Token Passing

Functional Overview

Protocol Manual

Token passing ring is the basis for communication between the more complex, active stations. All stations have the same rights in that a token is passed from station to station in a logical ring. The token is passed to each station with a maximum, definable token cycle time. A station is given transmission rights for the duration of time that it has the token.

1.3.4 Master/Slave Polling

Master/slave polling guarantees a cyclic, real-time based data exchange between the station with transmission rights, the active station, and its subordinates, the passive stations. In this case, the Master is able to pass data to the slave and/or receive data. The services in layer 2 (field-bus data link in ISO-

OSI reference model) organize this communication.


February 8, 2017

Page 13 of 150

Functional Overview

Protocol Manual

1.4 Communication Types



In addition to point-to-point data transfer, the PROFIBUS protocol can also handle the following types of communication.

 Broadcast communication: An active node sends an unacknowledged message to all other nodes (Master and slaves)

 Multicast communication (control instructions): An active node sends an unacknowledged message to a group of nodes (Master and slaves)


February 8, 2017



1.5 Master/Slave Communication Phases

Functional Overview

Protocol Manual

The communication between the Master and the slaves takes place in the following phases:

 Parameterization and configuration phase

 Usable data transfer phase

Before a DP slave can be integrated into the usable data transfer phase, the parameterization and configuration phase runs a device identification test that verifies that the planned configuration matches the actual device configuration for each slave in the PROFIBUS network. The test verifies that:

 The device is actually there

 It is the right type of device

 The station address set on the device matches the station address in the bus configuration

 The formats, telegram length information, and bus parameters are correct and

 The number of configured inputs and outputs is correct


February 8, 2017

Page 15 of 150

Functional Overview

Protocol Manual

1.6 Gateway Internal Database



The internal database is central to the functionality of the gateway. This database is shared between all the ports on the gateway and is used as a conduit to pass information from one device on one network to one or more devices on either connected network. This permits data from devices on one communication port or network to be viewed and controlled by devices on another port or network.

In addition to data from the Master and slave ports, status and error information generated by the gateway can also be mapped into the internal database.


February 8, 2017



2 Configuration

In This Chapter

 Configuring the Gateway ....................................................................... 18

 PROFIBUS Master DPV1 ...................................................................... 26

 PROFIBUS Master Commands ............................................................. 31

 Example Mailbox Commands ................................................................ 33

 Configuring the PROFIBUS DP Network ............................................... 52

 Downloading the Project to the Gateway .............................................. 71

 Backing Up the Project .......................................................................... 72

Configuration

Protocol Manual


February 8, 2017

Page 17 of 150

Configuration

Protocol Manual

2.1 Configuring the Gateway



Because the task of configuring the PROFIBUS network can be challenging,

ProSoft Technology has provided a configuration tool called ProSoft

Configuration Builder (PCB) that will help you with the following tasks:

 Creating a configuration project (page 22)

 Setting gateway parameters (page 24)

 Configuring the PROFIBUS network (page 52) (Master and slaves)

 Downloading the project to the gateway (page 71)

The following topics of this chapter explain each task step-by-step.

2.1.1 Installing ProSoft Configuration Builder Software

You must install the ProSoft Configuration Builder (PCB) software to configure the gateway. You can always get the newest version of ProSoft Configuration

Builder from the ProSoft Technology website.

To install ProSoft Configuration Builder from the ProSoft Technology website

1 Open your web browser and navigate to http://www.prosoft-

technology.com/pcb

2 Click the D

OWNLOAD

H

ERE

link to download the latest version of ProSoft

Configuration Builder.

3 Choose S

AVE

or S

AVE

F

ILE

when prompted.

4 Save the file to your Windows Desktop, so that you can find it easily when you have finished downloading.

5 When the download is complete, locate and open the file, and then follow the instructions on your screen to install the program.

If you do not have access to the Internet, you can install ProSoft Configuration

Builder from the ProSoft Solutions Product CD-ROM, included in the package with your gateway.


February 8, 2017



To install ProSoft Configuration Builder from the Product CD-ROM

Configuration

Protocol Manual

1 Insert the ProSoft Solutions Product CD-ROM into the CD-ROM drive of your

PC. Wait for the startup screen to appear.

2 On the startup screen, click P

RODUCT

D

OCUMENTATION

. This action opens a

Windows Explorer file tree window.

3 Click to open the U

TILITIES

folder. This folder contains all of the applications and files you will need to set up and configure your gateway.

4 Double-click the S

ETUP

C

ONFIGURATION

T

OOL

folder, double-click the

PCB_*.

EXE

file and follow the instructions on your screen to install the software on your PC. The information represented by the "*" character in the file name is the PCB version number and, therefore, subject to change as new versions of PCB are released.

Note: Many of the configuration and maintenance procedures use files and other utilities on the

CD-ROM. You may wish to copy the files from the Utilities folder on the CD-ROM to a convenient location on your hard drive.

Using the Online Help

Most of the information needed to help you use ProSoft Configuration Builder is provided in a Help System that is always available whenever you are running

ProSoft Configuration Builder. The Help System does not require an Internet connection.

To view the help pages, start ProSoft Configuration Builder, open the H

ELP

menu, and then choose C

ONTENTS

.

Adding a Location to an Existing Project File

1 Right-click the P

ROJECT

icon and select A

DD

L

OCATION

. A new Location icon appears. or

Select the P

ROJECT

icon.

2 Choose P

ROJECT

from the P

ROJECT

menu, and then choose A

DD

L

OCATION

.

A new Location icon appears. or

If the Default Location has not been named (is not already an existing project), right-click the folder and choose R

ENAME

.

3 Type in the Location name.

Adding a Project to an Existing Project File

1 Select the D

EFAULT

P

ROJECT

icon.

2 Open the P

ROJECT

menu, choose P

ROJECT

,

and then choose A

DD

P

ROJECT

.

This action opens a new Project folder.


February 8, 2017

Page 19 of 150

Configuration

Protocol Manual



Adding a Module

Begin the process of creating your custom application configuration by selecting the module type of your ProLinx gateway.

1 Double-click the D

EFAULT

M

ODULE

icon to open the Choose Module Type dialog box.

2 In the Choose Module Type dialog box, select the M

ODULE

type.

Or

1 Open the

P

ROJECT

menu and choose L

OCATION

.

2 On the L

OCATION

menu, choose A

DD

M

ODULE

.

To add a module to a different location

1 Right-click the L

OCATION

folder and choose A

DD

M

ODULE

. A new Module icon appears.

Or

1 Select the L

OCATION

icon.

2 From the P

ROJECT

menu, select L

OCATION

, and then select A

DD

M

ODULE

.


February 8, 2017



Configuring Gateway Parameters

1 Click the [+] sign next to the module icon to expand gateway information.

Configuration

Protocol Manual

2 Click the

[+]

sign next to any icon to view gateway information and configuration options.

3 Double-click any icon to open an Edit dialog box.

4 To edit a parameter, select the parameter in the left pane and make your changes in the right pane.

5 Click OK to save your changes.

Creating Optional Comment Entries

1 Click the [+] to the left of the comments.

2 Double-click the appears.

icon to expand the module

icon. The Edit - Module Comment dialog box

3 Enter your comment and click OK to save your changes.

Printing a Configuration File

1 Select the module icon, and then click the right mouse button to open a shortcut menu.

2 On the shortcut menu, choose V

IEW

C

ONFIGURATION

. This action opens the

View Configuration window.

3 In the View Configuration window, open the F

ILE

menu, and choose P

RINT

.

This action opens the Print dialog box.

4 In the Print dialog box, choose the printer to use from the drop-down list, select printing options, and then click OK.


February 8, 2017

Page 21 of 150

Configuration

Protocol Manual

2.1.2 Setting Up the Project



To begin, start ProSoft Configuration Builder. If you have used other Windows configuration tools before, you will find the screen layout familiar. ProSoft

Configuration Builder’s window consists of a tree view on the left, an information pane and a configuration pane on the right side of the window. When you first start ProSoft Configuration Builder, the tree view consists of folders for Default

Project and Default Location, with a Default Module in the Default Location folder. The following illustration shows the ProSoft Configuration Builder window with a new project.

Your first task is to add the PDPMV1 gateway to the project.

1 Use the mouse to select D

EFAULT

M

ODULE

in the tree view, and then click the right mouse button to open a shortcut menu.


February 8, 2017



Configuration

Protocol Manual

2 On the shortcut menu, select C

HOOSE

M

ODULE

T

YPE

. This action opens the

Choose Module Type dialog box.

3 In the Product Line Filter area of the dialog box, select the gateway series

(PLX5K for wired gateways, or PLX6K for wireless gateways). In the Select

Module Type dropdown list, select the model number for your gateway (for example, 5204-MNET-PDPMV1), and then click OK to save your settings and return to the ProSoft Configuration Builder window.

The next task is to set the gateway parameters.


February 8, 2017

Page 23 of 150

Configuration

Protocol Manual

2.1.3 Setting Gateway Parameters



Notice that the contents of the information pane and the configuration pane changed when you added the PDPMV1 gateway to the project. The red "X" icon indicates that the gateway’s configuration is incomplete.

1 Click the plus sign [+] next to the module icon to expand the module tree, and then expand the PLX PDPM-V1 tree.

2 Double-click the PROFIBUS

M

ASTER

DPV1 object. This action opens the Edit dialog box.

3 In the Edit dialog box, enter the values for Input Data Size and Output Data

Size (PROFIBUS input and output point words) to match the values required by your application. To change a value, select the parameter to modify in the left pane, and then type the new value in the edit field in the right pane.


February 8, 2017



Configuration

Protocol Manual

For the sample application, the input and output data size values are fixed to a value of 768.

4 Click OK to save your settings and return to the ProSoft Configuration Builder window.

At this time, you may wish to rename the Default Project and Default Location folders in the tree view.

To rename an object

1 Select the object, and then click the right mouse button to open a shortcut menu. From the shortcut menu, choose R

ENAME

.

2 Type the name to assign to the object.

3 Click away from the object to save the new name.


February 8, 2017

Page 25 of 150

Configuration

Protocol Manual

2.2 PROFIBUS Master DPV1



2.2.1 Input Start Register

0 to 3230

Database start register for input data.

2.2.2 Input Data Size

0 to 768

Total number of PROFIBUS Input Words (one word equals two bytes) from all

PROFIBUS slaves. These Input Words will be the data received from slave devices on the PROFIBUS network.

2.2.3 Output Start Register

0 to 3230

Database start register for output data.

2.2.4 Output Data Size

0 to 768

Total number of PROFIBUS Output Words (one word equals two bytes) to be sent to all PROFIBUS slaves. These Output Words will be the data sent to slave devices on the PROFIBUS network.


February 8, 2017



2.2.5 Input Byte Swap

Configuration

Protocol Manual

Y

ES

or N

O

This parameter determines if the bytes in the PROFIBUS Input Data area are swapped before being stored in the gateway memory database. If the parameter is set to N

O

, no swapping will be applied. If the parameter is set to Y

ES

, the order of bytes in each word will be swapped before being stored in memory.

Example:

 With Input Byte Swap set to N

O

, incoming order is unchanged - ABCDEF

 With Input Byte Swap set to Y

ES

, each byte pair is swapped - BADCFE

2.2.6 Output Byte Swap

Y

ES

or N

O

This parameter determines if the bytes in the PROFIBUS Output Data area are swapped before being transmitted to slaves on the PROFIBUS network. If the parameter is set to N

O

, no swapping will be applied. If the parameter is set to

Y

ES

, the order of bytes in each word will be swapped before being transmitted.

Example:

 With Output Byte Swap set to N

O

, outgoing output order is unchanged -

ABCDEF

 With Output Byte Swap set to Y

ES

, each output byte pair is swapped -

BADCFE


February 8, 2017

Page 27 of 150

Configuration

Protocol Manual

2.2.7 Mailbox Register



0 to 3700, -1 to disable

Enter the database register for DPV1 mailbox messages, or -1 to disable mailbox messages.

Mailbox messages can be sent through the database to the PROFIBUS Master.

This functionality requires 290 registers of the database. The map of the database area utilized for this purpose is as follows.

Offset Description

0 This is the handshake word used to tell the PROFIBUS driver when a new acyclic message is ready to send. If the value at this location is zero (0), no message will be sent. If the value is not zero, then the PROFIBUS driver will send an acyclic message using the contents of words 1 through 144. This handshake word should be set to a non-zero value only after the complete acyclic message is stored in offsets 1 to 144. After the PROFIBUS driver has added the acyclic message to the queue, this register will be set to zero (0), so that the message is not repeated and to indicate that a new acyclic message may be prepared.

NOTE: It would be a good practice to check the value of word 145 to be sure it is set to zero (indicating that no acyclic messages are awaiting processing) before setting this word to a non-zero value, triggering an acyclic message. This will help avoid acyclic data collisions and data loss.

1 to 144

145

This area holds the acyclic message bytes to send. Please refer to Mailbox

Messaging (page 75) for the format of this data area.

NOTE: The header words (first 32 bytes) are stored in little-endian format and the gateway will change the order to big-endian format before sending.

This handshake word indicates when a new acyclic response message has been received by the PROFIBUS driver. If the value is zero (0), no response message has been received. If the value is non-zero, a response message has been received and stored in words 146 to 289. This data should be transferred by the other gateway protocol for external processing. After the acyclic message has been externally processed, a message should be returned through the other protocol that sets this address to zero, to indicate readiness to receive and process a new acyclic response message.

146 to 289 This area holds the acyclic message response bytes. Please refer to Mailbox

Messaging (page 75) for the format of this data area. The header words (first 32

bytes) are stored in little-endian format to make it easier to use.

Alarm acyclic messages are sent from the PROFIBUS driver to the database if this feature is enabled by entering a valid database register in the configuration file. This feature requires 145 database registers. The format of the data area is as follows.

Offset

0

1 to 144

Description

This is the alarm handshake word. If the value is not zero (0), alarm data is present in the words 1 through 144. This register should be set to zero after the alarm is process, so another alarm can be passed through the database. If this register is zero (0), the database area is ready to receive a new alarm message.

This area holds the alarm acyclic message received by the PROFIBUS Master

device. Please refer to Mailbox Messaging (page 75) for a description of this acyclic

message. The header (first 32 bytes) of the message is stored in little-endian format to make it easier to process.


February 8, 2017



2.2.8 Slave Diagnostics Register

Configuration

Protocol Manual

0 to 3600, -1 to disable

Enter the database register start location for DPV1 slave diagnostics messages, or -1 to disable slave diagnostics.

When this register is enabled, the gateway will automatically place 378 words of collected slave diagnostic data into the specified database start register.

Each slave requires 3 words of data. Data is gathered for slaves 0 to 125. The application will poll for a new slave every 100 milliseconds.

2.2.9 Alarm Register

0 to 3900, -1 to disable

Enter the database register for DPV1 alarm messages, or -1 to disable alarm messages.

2.2.10 Status Data Register

0 to 3900, -1 to disable

Enter the gateway memory database register for DP-V1 status data messages, or -1 to disable status data messages.

2.2.11 Minimum Command Delay

0 to 32767

Minimum number of milliseconds between each command.

2.2.12 Response Timeout

0 to 5000 milliseconds

Number of milliseconds to wait for response to command. The value is set depending upon the communication network used and the expected response time of the slowest device on the network.

2.2.13 Watchdog Register

The Watchdog function allows the gateway to monitor a database register, the

Watchdog Register, to check for loss of communication with the non-PROFIBUS communication protocol. If this function is used, the other gateway protocol is expected to change the value in the Watchdog Register at an interval less than the amount of time specified in the Watchdog Timeout parameter. If the value in the Watchdog Register does not change within this amount of time, a communication loss is assumed and the Watchdog function will set the

PROFIBUS outputs to the default value specified in the Watchdog Reset Value parameter. To disable this function, set this parameter to a value of -1.


February 8, 2017

Page 29 of 150

Configuration

Protocol Manual

2.2.14 Watchdog Timeout



Sets the period of time (in 0.1s increments) for the gateway to wait for communication loss detection. For example, set this parameter to 100 to set a waiting period of 10 seconds. To disable this function, set this parameter to a value of -1.

2.2.15 Watchdog Reset Value

Sets the value that will be sent to the PROFIBUS output byte registers upon communication loss as detected by the Watchdog function. To disable this function, set this parameter to a value of -1.


February 8, 2017



2.3 PROFIBUS Master Commands

Configuration

Protocol Manual

Type

 Disabled: command will not be executed.

 Enabled Continuous: command will be executed as frequently as set by Poll

Interval parameter.

 Enabled Conditional: command will only be executed if the values at the database at address set by Database Register parameter changes.

 Enabled With Trigger: command will be executed if database trigger value

(set by Database Trigger parameter) is different from 0. After the command is executed then the database trigger value is automatically set to 0 (zero).

Database Register

 Database location for the operate mode if the count is set to 0 (zero).

Count

 If Count is equal to zero, operate mode for command is derived from the

Database Register parameter in the gateway database. If the count is nonzero, then the value in the Operation Mode field is used with the command.

Poll Interval

 Sets how frequently in seconds the command will be executed if type is configured as Enabled Continuous.

Swap

 On requests used only for Function Code 33 (Acyclic Write).

 On responses used for Function Code 4, 23, 24 and 32.

Database Trigger

 This functionality requires the type parameter to be set as Enabled With

Trigger. The command will be executed if the database value set by this parameter is non-zero. After the command is executed this value will be automatically set to zero.

Function

 Set Operate Mode (FC-2)

 Set Slave Mode ( FC-3)

 Get Slave Diagnostic Data (FC-4)

 Get Slave Configuration (FC-5)

 Start/Stop Slaves Dynamically (FC-11/FC-12)

 Get Database Information (FC-23) (should be viewed in ASCII for CRC

Values)

 Get Live List (FC-24)

 Acyclic Read (FC-32)


February 8, 2017

Page 31 of 150

Configuration

Protocol Manual

 Acyclic Write (FC-33)



Operation Mode

 This field is required if the count field is set to 1 and represents the new operation mode as follows: o o o

64=Stop

128=Clear

192=Operate


February 8, 2017



2.4 Example Mailbox Commands

Configuration

Protocol Manual

The following examples show how to issue mailbox commands for Set Operating

Mode, Get Live List and Start/Stop Slaves. The rest of the supported mailbox commands are configured the same way.

2.4.1 Set Operating Mode

1 In ProSoft Configuration Builder (PCB), expand the PLX PDPM-V1 section.

2 Select P

ROFIBUS

M

ASTER

C

OMMANDS

S

ET

O

PERATE

M

ODE

, click the right mouse button, and then choose C

ONFIGURE

.


February 8, 2017

Page 33 of 150

Configuration

Protocol Manual



This action opens the Edit - Profibus Master Commands dialog box. This dialog box allows you to add commands, one row at a time, with all the necessary parameters.

3 To add a command, click A

DD

R

OW

. This action adds a command to the list, populated with the default values for the command.


February 8, 2017



Configuration

Protocol Manual

4 To change the settings for the command, select the row, and then click E

DIT

R

OW

. This action opens the Edit - Row 1 dialog box.

Command Layout for Set Operating Mode

Column

Type

DB_Reg

Count

Poll_Int

Swap

DB_Trigger

Func

Param_1

Value

0 to 3

2

64, 128 or

192

Description

2

3

0

1

Command Disabled

Command Enabled, use poll interval

Command executed when database changes (Func 2, 3, 11, 12 or 33 only)

Command executed when database trigger set Not equal to 0

If the count is set to 0, this is the database location for the operate mode. Place a value of

64 or 128 or 192 in parameter 1 for description.

If Count is equal to 0, operate mode for command is derived from the DB_Reg in the gateway database. If the count is not equal to 0, then the value in the Param_1 field is used with the command.

Only if type = 1

Not used

This functionality requires the type parameter to be set as Enabled With Trigger. The command will be executed if the database value set by this parameter is nonzero. After the command is executed this value will be automatically set to zero.

Set Operate Mode.

This field is required if the count field is set to 1 and represents the new operation mode as follows: 64=Stop, 128=Clear and 192=Operate.


February 8, 2017

Page 35 of 150

Configuration

Protocol Manual



For this example, the command will stop the Master using database trigger register 3200. Any nonzero value placed in this register will trigger the command to execute. When the command has executed, the database register will be reset to zero.

The following illustration shows the parameters that execute this command.

In the following illustration, from the Diagnostics window in ProSoft Configuration

Builder, the Master's operation state is Operate (C0 hex). To see this screen, press [2] from the Main menu.


February 8, 2017



Configuration

Protocol Manual

When you download the configuration containing this mailbox command to the gateway, and then return to the Diagnostics window, press [F] at the Main menu, and then press [S] to view the command list. The following illustration shows the command list. Notice that the first command matches the settings you made in the Edit - Profibus Master Commands dialog box.

Press [M] to return to the Main menu, and then press [2] to view the Fieldbus

Data again. Notice that the Operation State has changed to Stop (40 hex).


February 8, 2017

Configuration

Protocol Manual

2.4.2 Get Live List




2 Select P

ROFIBUS

M

ASTER

C

OMMANDS

G

ET

L

IVE

L

IST


ONFIGURE

.

This action opens the Edit - Profibus Master Commands dialog box. This dialog box allows you to add commands, one row at a time, with all the necessary parameters.


February 8, 2017



Configuration

Protocol Manual


DD

R

OW



DIT

R

OW



February 8, 2017

Page 39 of 150

Configuration

Protocol Manual

Command Layout for Get Live List

Column

Type

Value

0, 1 or 3

DB_Reg

Count

Poll_Int

Swap

DB_Trigger

Func 24



Description

Type 0 Command Disabled

1 Command Enabled, use poll interval

3 Command executed when database trigger set != 0

Location where the results from the command are placed.

This parameter specifies the number of word registers in the reply to place in the database.

Only if type = 1

Utilized on response message

This functionality requires the type parameter to be set as Enabled With Trigger. The command will be executed if the database value set by this parameter is nonzero.

After the command is executed this value will be automatically set to zero.

Get Live List

For this example, the command will retrieve the list of Masters and slaves using database trigger register 3201. Any nonzero value placed in this register will trigger the command to execute. When the command has executed, the database register will be reset to zero. Data from the response will be placed at database address 3300, with a length of 128 words.



February 8, 2017



Configuration

Protocol Manual

When you download the configuration containing this mailbox command to the gateway, and then return to the Diagnostics window, press [F] at the Main menu, and then press [S] to view the command list. The following illustration shows the command list. Notice that the first command matches the settings you made in the Edit - Profibus Master Commands dialog box.


February 8, 2017

Page 41 of 150

Configuration

Protocol Manual



Any nonzero value placed in register 3201 issues mailbox command Get Live

List. The results of this command are placed in the database starting at register

3300.

 A value of 03 HEX indicates this is the Master address which is in this case is

01.

 A value of 04 HEX indicates the slave is not configured and not connected.

 A value of 00 HEX means this slave is configured and connected. In this case

Slave #2 and Slave #6 are connected to the Master and are exchanging cyclic data.


February 8, 2017



2.4.3 Start/Stop Slaves

Configuration

Protocol Manual


2 Select P

ROFIBUS

M

ASTER

C

OMMANDS

S

TART

/S

TOP

S

LAVE


ONFIGURE

. This action opens the Edit -

Profibus Master Commands dialog box. This dialog box allows you to add commands, one row at a time, with all the necessary parameters.


February 8, 2017

Page 43 of 150

Configuration

Protocol Manual




DD

R

OW



DIT

R

OW



February 8, 2017



Command Layout for Start/Stop Slaves

Column Value

Type 0 to 3

DB_Reg

Count

Poll_Int

Swap

DB_Trigger

Func 11

12

Param_1

Configuration

Protocol Manual

Description

Type 0

1

2

3

Command Disabled

Command Enabled, use poll interval

Command executed when database changes

(Func 2, 3, 11, 12 or 33 only)

Command executed when database trigger set

Not equal to 0

This is the database location where the 126 bytes of data for the message to be constructed for the mailbox command is present.

This field is not used as the message is always 63-words in length

Only if type = 1

Utilized on request and response message

Used if type is 3

Start Slave(s)

Stop Slave(s)

This field contains the database address where the 63-words of response data from the mailbox is written. Set to -1, if the data is not to be written to the database.

For this example, the command will stop and start the specified slave(s) using

Database trigger register 3199 (stop) and 3198 (start). Any nonzero value placed in either register will trigger the command to execute. When the command has executed, the database register will be reset to zero. Data will be read from database register 3200 for a count of 63 words. The response will be placed at

Database address 3500 with a length of 63 words.



February 8, 2017

Page 45 of 150

Configuration

Protocol Manual



When you download the configuration containing this mailbox command to the gateway, and then return to the Diagnostics window, press [F] at the Main menu, and then press [S] to view the command list. The following illustration shows the command list. Notice that the first two commands match the settings you made in the Edit - Profibus Master Commands dialog box.

When you place any value at database register 3199, this will issue the command for the mailbox Stop slave(s). Slaves that are required to stop communicating with the master will show RED. This is a byte map value entered at database address 3200-3263. A decimal value of 257 in database register

3205 will stop slaves 10 and 11.


February 8, 2017



Configuration

Protocol Manual

The Monitor/Modify Slave screen in ProSoft Configuration Builder for PROFIBUS will show that the slave is working properly.

Double-click on Slave 10.


February 8, 2017

Page 47 of 150

Configuration

Protocol Manual



The Diagnostic tab contains the following information for Slave 10, indicating that the slave has stopped exchanging cyclic data.

To start the slaves again, place any value in database register 3198.

Important Note: Values in DB register are byte mapped values of 1 and 257. Use decimal values only. There are 126 byte for 126 allowed PROFIBUS addresses. To stop slave address 100, place a value of 1 in DB 50 of the 63. To stop slave address 10 and 11, place a value of 257 at Database address 5 of the 63. If the Database start address is 3200, place a value of 257 at Database address 3205.

Refer to Mailbox Message: Start Slave (page 96) and Mailbox Message: Stop Slave (page 97) for

more information on these commands.

DB_register and Param_1 should be same for both function codes 11 and 12. If you stop a certain slave address, you must restart the same address.


February 8, 2017



2.4.4 Other Mailbox Commands

Configuration

Protocol Manual

3 - Set Slave Mode

Field

Type

DB_Reg

Count

Poll_Int

Swap

DB_Trigger

Func

Param_1

Param_2

Param_3

Value

0 to 3

3

Description

Database location for the three values used by the command.

If count == 0, the three values for the command are derived from the database. If count != 0, the three parameters for the command are present in the command list.

Only if type = 1

Not used

0 to 125 or 127

Group Select

This field represents the slave address for the command.

Address 127 is used for multicast address.

Refer to Mailbox Message: Set Slave Mode (page 80)

Control Command Refer to Mailbox Message: Set Slave Mode (page 80)

4 - Get Slave Diagnostic Data

Field

Type

DB_Reg

Value

0, 1 or 3

Count

Poll_Int

Swap

DB_Trigger

Func

Param_1

Param_2

4

0 to 125

Type of Req

Description

This is the database location where the results of the command will be placed

This parameter specifies the number of words in the response message to place in the database.

Only if type = 1



If 0, internal database used. If 1, data polled on network.

This last option is used if the slave is not controlled by this

Master.


February 8, 2017

Page 49 of 150

Configuration

Protocol Manual

5 - Get Slave Configuration

Field

Type

DB_Reg

Value

0, 1 or 3

Count

Poll_Int

Swap

DB_Trigger

Func

Param_1

5

1 to 125



Description

This is the database location where the results of the command will be placed

This parameter specifies the number of words in the response message to place in the database.

Only if type = 1



23 - Get Database Information

Field

Type

DB_Reg

Value

0, 1 or 3

Count

Poll_Int

Swap

DB_Trigger

Func 23

Description

Location of the 4 words received in the response to this request.

This field is not used as the message is always 4-words in length

Only if type = 1


32 - Acyclic Read

Field

Type

DB_Reg

Count

Value

0, 1 or 3

Poll_Int

Swap

DB_Trigger

Func

Param_1

Param_2

Param_3

Param_4

Page 50 of 150

32

Slave Addr

Slot

Index

Len

Description

Database location where read data placed

Number of words in response message to write to the database.

Only if type = 1

Applied to data in response message

Slave address to read data from

Slot in slave to access

Index in slave to access

Length in bytes of data to be sent from the slave.


February 8, 2017



33 - Acyclic Write

Field

Type

DB_Reg

Count

Value

0 to 3

33

Slave Addr

Slot

Index

Len

Poll_Int

Swap

DB_Trigger

Func

Param_1

Param_2

Param_3

Param_4

Configuration

Protocol Manual

Description

Starting database location of the write data.

Number of word registers to read from the database into the command.

Only if type = 1

Applied to data in request message

Slave address to write to with data

Slot in slave to access

Index in slave to access

Length in bytes of data to be sent to the slave.


February 8, 2017

Page 51 of 150

Configuration

Protocol Manual

2.5 Configuring the PROFIBUS DP Network



To configure your PROFIBUS DP network you must perform four tasks:

1 Install any PROFIBUS slave-specific device configuration files, typically

called .GSD files (page 52).

2 Configure the ProLinx PROFIBUS DP Master (page 52).

3 Configure the PROFIBUS slaves.

4 Print the Unity Passthru Memory Map.

2.5.1 Installing the GSD Files

ProSoft Configuration Builder (PCB) uses PROFIBUS slave device definition files

(GSD files) to obtain basic configuration information about the PROFIBUS slaves you add to the network. The GSD configuration files identify the slave’s capabilities so that the PDPMV1 can communicate with it correctly. Slave device manufacturers provide the GSD files for the equipment they make. Slave device files sometimes come in various languages. When a manufacturer provides slave device files in several languages, it is a common practice to use the third letter of the file extension to indicate the language used in the file. For instance: o o o o o

.GSD is the most commonly used file extension and will usually be in either English or German

.GSE will usually be in English

.GSS will usually be in Spanish

.GSF will usually be in French other combinations may also be seen, as well as other languages using the letters indicated above

Follow these steps to install the GSD file or files for your slave device or devices.

Tip: GSD configuration files for popular PROFIBUS slaves and ProSoft Technology solutions are included with PCB. Before installing GSD files, browse the list of available slaves in the Tree View window to see if GSD files for your slave are already installed.

GSD files are often both model number specific as well as model revision specific. Just because you may have an older GSD file from a manufacturer for the particular make and model of your slave device does not guarantee it will work for a newer revision of that device. Be sure you obtain from the device manufacturer the correct GSD file or files for your PROFIBUS slave or slaves.


February 8, 2017



To install GSD files manually

Configuration

Protocol Manual

1 In ProSoft Configuration Builder tree view, click [+] to expand the module tree, and then double-click the PROFIBUS DP icon. This action opens the

PDPMV1 PROFIBUS Master Setup dialog box.

2 Click the C

ONFIGURE

PROFIBUS button. This action opens the ProSoft

Configuration Builder for PROFIBUS application.

3 Open the T

OOLS

menu, and then choose I

NSTALL NEW

GS*

FILE

. This action opens a dialog box that allows you to browse for the location of the GSD configuration files to install. (Depending on the device and language used in the file, the actual extension may be ".GSD", ".GSE", ".GSS", or other combinations; hence the generic reference to ".GS*" files, where "*" is a wildcard that stands for any letter.)

4 Choose the file to install, and then click O

PEN

. If the file already exists in the configuration file path, you will be prompted to overwrite the file.

5 You will be prompted to associate the GSD configuration file with a bitmap image of the slave device. Use the F

ILE

/ O

PEN

dialog box to browse for the location of the image file to use. If you have no device-specific bitmap file, you may C

ANCEL

the bitmap upload, and a generic device icon will be used in the Bus Configuration window for this slave device.

2.5.2 Configuring the PROFIBUS Slaves

There are two essential steps to configuring a slave:

1 Add the slave in ProSoft Configuration Builder (PCB) as a device connected to the PROFIBUS Master, specifying the slave address and any necessary input and output configuration. Download the PROFIBUS Master configuration to the PDPMV1 module.

2 Configure the slave (using PCB or the configuration tool supplied by the manufacturer, for some PROFIBUS slaves). Verify that the slave address configured in the slave module matches the slave address configured in PCB.

Download the PROFIBUS Slave configuration to the slave module.

Scanning for Slaves Manually

Important: The GSD file for this example is not included on the ProLinx Solutions CD-ROM, and is used for illustrative purposes only. You can download a variety of example GSD files from the

PROFIBUS Trade Organization website at www.profibus.org, or from the manufacturer's website for your PROFIBUS slaves.

The following steps describe how to add and configure a Siemens EM 277 I/O chassis to the PROFIBUS network. The configuration information (.GSD file) for this device must be installed according to the procedure found in Install the GSD

Files (page 52). Most other PROFIBUS slaves can be configured in a similar

manner.


February 8, 2017

Page 53 of 150

Configuration

Protocol Manual



1 In ProSoft Configuration Builder for PROFIBUS, click the plus sign [+] to expand the PROFIBUS

DP

tree.

2 Navigate to the folder containing the type of slave device to add

(PLC

S

/S

IEMENS

/EM

277, in this example), and then click the plus sign [+] to expand the folder.


February 8, 2017



Configuration

Protocol Manual

3 Click the

EM 277

PROFIBUS-DP icon in the tree view and drag and drop the icon into the Bus Configuration view. This action adds the slave device and connects it to the Master in a network relationship.

4 In the tree view, click the plus sign [+] to expand the slave device you added.

This action opens a list of device configuration values. The following illustration shows the possible input/output configuration values for a Siemens

EM 277. The selections available for other devices may be different, so you should review the specifications for the product you are installing in order to determine the correct values to use.


February 8, 2017

Page 55 of 150

Configuration

Protocol Manual



5 Drag the input and output parameters to the slot location grid (Subscriber

List) below the Bus Configuration window. The slot view displays the slot number, configuration data, and input and output addresses. The PROFIBUS

DP Master uses this information to identify and communicate with individual slaves on the network.

For this example, we will configure 8 words of input and 32 words of output.

These input and output words are assigned to addresses within the gateway's internal database.

For each new slave added to the PROFIBUS network, ProSoft Configuration

Builder automatically converts the input/output byte addresses to word input/output addresses.

Tip: To make it easier to view the data from individual slaves, you can create a spreadsheet with all added slaves and input and output data offsets, or you can view and print the data map.


February 8, 2017



6 Double-click the S

LAVE

icon to view the Slave properties dialog box.

Configuration

Protocol Manual

ProSoft Configuration Builder automatically assigns a PROFIBUS address to each new slave. The slave address assignment begins at address 3 for the first slave added to the network (addresses 0, 1, and 2 are reserved for use with PROFIBUS Masters), and is incremented by 1 for each new slave added to the network. You may, however, assign any address, 0-125 to any Master or slave node as long as you do not assign the same address to more than one device. You can change the address in the C

OMMON

tab of the Slave

properties dialog box. ProSoft Configuration Builder will not allow you to assign a PROFIBUS address that is already in use by another device on this network.

Leave the remaining settings unchanged for now, and click OK to close the

Slave properties dialog box.

7 Repeat steps 2 through 6 for all slaves you intend to place on the network.

8 When you are finished adding slaves, open the P

ROJECT

menu and choose

E

XIT

.

Click Y

ES

to save the project and return to the PROFIBUS Master Setup dialog box.


February 8, 2017

Page 57 of 150

Configuration

Protocol Manual

Using The Autoscan Feature



The concept of Automatic network scanning means that the user can instruct the

Bus Configuration window to automatically gather information about slaves that are connected to the network. When the scan is completed the user can adopt the detected slaves to the bus configuration and download to the Master.

This is a quick way to get a network up and running. However, one should be aware that it is not guaranteed that any particular slave will enter data exchange since the user parameter data might not match. This is especially obvious if no associated GSD-file is found during the network scan, this means that no user parameter data would be sent to the slave.

N

ETWORK SCAN

is selectable from the Online menu as well as from the dropdown menu for the M

ASTER

icon.


February 8, 2017



Configuration

Protocol Manual

When the download is completed, the PROFIBUS Master Configuration window will initialize the Master to operate as a Class 2 Master only. In this mode it is possible to initialize the Master even if the database does not contain any slaves.

After successful initialization, the PROFIBUS Master Configuration window will issue the following mailboxes in order to gather information about the connected slaves:

1 1. Send FB_APPL_GET_LIVE_LIST in order to detect connected slaves,

2 2. Send FB_APPL_GET_SLAVE_DIAG (external request) to all devices identified as slaves according to the Live list.

3 3. Send FB_APPL_GET_SLAVE_CONFIG to all devices identified as slaves according to the Live list.

When the information is collected the PROFIBUS Master Configuration window will find a matching GSD-file and extract information from it. Refer to the flowchart below for this sequence:


February 8, 2017

Page 59 of 150

Configuration

Protocol Manual

GSD Selection Algorithm



If two or more matching GSD-files are found, the first one found should be selected. The other compatible files should be stored so that the user can select one of them instead. If the user selects another GSD-file, the PROFIBUS Master

Configuration window will run through the Module Selection Algorithm (described below) again.

Module Selection Algorithm

The algorithm used to find modules in the GSD based on the Identifier byte(s) is as follows:

Select the module that matches the largest number of Identifier bytes. If the GSD contains two or more modules with the exact set of Identifier bytes, use the first module found.

Example:

If a slave responds with identifier bytes: 0x11, 0x21, 0x31 and that the associated

GSD-fi le contains five modules: “A” = 0x11, “B” = 0x21, “C” = 0x31, “AB” = 0x11,

0x21 and “BC” = 0x21, 0x31. The PROFIBUS Master Configuration window will then select modules "AB" and "C".

Note: If no matching module is found in the GSD, The PROFIBUS Master Configuration window will display the identifier byte(s) instead.

Network scan window

The information extracted from the GSD-file(s) will be displayed in the Network

scan window.

Select

In this column all found slaves will be marked as selected by default, except for slaves with the special address 126 (refer to the next section that describes the

Address column). Only selected slaves will be added to the PROFIBUS Master

Configuration when the A

DOPT SELECTED SLAVES

button is clicked.

Address

In this column the node address of the slaves will be displayed. Found slaves should be listed in ascending order according to their node addresses.


February 8, 2017



Special address 126 -Set Slave address:

Configuration

Protocol Manual

If a slave with node address 126 is detected during the network scan, the

PROFIBUS Master Configuration window will display the address in red color. It will not be possible for the user to adopt the slave to the configuration since it is not allowed to exchange data with devices having this address. The check box in the Select column will be grayed out.

To be able to adopt a slave with address 126 the user must first assign a valid address by clicking the icon next to the node address. By doing so the Set Slave

Address dialog box is started.

Note that the Old slave address is preset to a value of 126 that is not editable (grayed out).


February 8, 2017

Configuration

Protocol Manual



If the Slave is in the configuration already then it will not affect the addressing.

Example:

After scanning, the network finds these other slaves: 2, 6, 25, and 40

Slaves 2, 6, and 25 are found, but are marked as in the bus configuration (the mapping of the inputs and outputs will not be affected)

Slaves 40 is new and could be added and the input/output addressing will be appended to the end as shown on the last screen.


February 8, 2017



Configuration

Protocol Manual

The PROFIBUS Master Configuration window will prevent the user from selecting a New slave address that is already occupied by another device; this includes detected Master stations as well. If the user selects an occupied address, a message similar to the one shown here will open.

When an address has been successfully assigned, the PROFIBUS Master

Configuration window will update the Network scan window as shown here. The node address will be updated to the one that the user selected in the Set Slave dialog box. The check box in the Select column will be marked allowing the user to adopt the slave to the configuration.

Slave

In this column the name of the slave as stated in the assigned GSD-file will be displayed. If no matching GSD-file is found the Ident number will be displayed in red color in the drop-down list.

Module

This column shows the name of the module(s) as stated in the assigned GSDfile, which matches the Identifier byte(s) derived from the GetCfg mailbox message. If no GSD-file or no matching module is found the Identifier byte(s) will be displayed in red color. If the configuration for a slave is constructed of several modules, the modules will be listed under each other.


February 8, 2017

Page 63 of 150

Configuration

Protocol Manual



If there is more than one module in the GSD-file that matches the Identifer bytes, the first matching module will be displayed in blue color in a drop-down list. The drop-down list will contain all other matching modules so that the user can select the desired one.

Note: Only modules that have the exact same Identifer bytes as the first matching module will be displayed in the drop-down list.

GSD-file

This column shows the name of the GSD-file that matches the Ident number derived from the SlaveDiag mailbox message. If there are more files with the same Ident number in the device catalog, the first matching GSD-file will be displayed in blue color in a drop-down list.

This could be the case if the device catalog contains two or more brand labeled devices, or GSD-files for two or more languages (for example NICEDEV.GSD and NICEDEV.GSE) exist.

Note: If the user selects another GSD-file, The PROFIBUS Master Configuration window will update the modules for that slave accordingly.


February 8, 2017



Configuration

Protocol Manual

If no GSD-file is found the user will be able to copy the expected GSD to the device catalog by clicking the icon next to the text No GSD found. This will start the Install new GS*-file dialog box. When the file is installed, the PROFIBUS

Master Configuration window will verify that the installed file matches the slave and update the modules for the slave accordingly.

Rescan

Pressing the Y

ES

button will trigger a new network scan. Before proceeding with the scan a message similar to the one below will appear. If a new scan is accepted, detected slaves found during the previous scan will be lost.

Adopt selected slaves

Pressing this button will cause all selected slaves to be adopted to the

PROFIBUS Master Configuration window. Before carrying on with this action a message similar to the one below will appear.


February 8, 2017

Page 65 of 150

Configuration

Protocol Manual



If accepted, the network scan window will close and the PROFIBUS Master

Configuration window will be populated with the slaves that were found during the network scan.

Note: Slave: is equal to the Ident number and that the Device path: and Order number/designation fields are left empty.

Cancel and Help

If the C

ANCEL

button is pressed a message similar to the one below will appear.

If the H

ELP

button is pressed the online help will start.


February 8, 2017



Configuration

Protocol Manual

Set_Param (SAP61)

ProSoft PROFIBUS slave (PDPS) devices have a configurable parameter for

SPC3 User Prm Byte. The following illustration shows the value of this parameter in ProSoft Configuration Builder for PROFIBUS, the configuration tool for ProSoft

PROFIBUS Master devices.


February 8, 2017

Page 67 of 150

Configuration

Protocol Manual

Parameter Data Structure



SPC3 evaluates the first seven data bytes (without user prm data), or the first eight data bytes (with user prm data). The first seven bytes are specified according to the standard. The eighth byte is used for SPC3-specific communications. The additional bytes are available to the application.

Byte

0

1

2

3

4

5

6

7

8 to 243

Lock

Reg

Bit Position

7 6

Unio

Req

5

Sync

Req

4

Free

Req

3 2

WD on Res

1

Res

0

Res

Designation

Station status

WD_Fact_1

WD_Fact_2

MinTSDR

Ident_Number_High

Ident_Number_Low

Group_Ident

Spec_User_Prm_Byte

User_Prm_Data

Byte 7 Spec_User_Prm_Byte

Bit Name

0

1

2

3 to 4

5

6 to 7

Dis_Startbit

Dis_Stopbit

WD_Base

Res

Publisher_Enable

Res

Significance

The start bit monitoring in the receiver is switched off with this bit

Stop bit monitoring in the receiver is switched off with this bit

This bit specifies the time base used to clock the watchdog.

WD_Base = 0: time base 10 ms

WD_Base = 1: time base 1 ms

To be parameterized with 0

DXB-publisher-functionality of the

SPC3 is activated with this bit

To be parameterized with 0

Default State

Dis_Startbit = 1,

Start bit monitoring is switched off.

Dis_Stopbit = 0

Stop bit monitoring is not switched off.

WD_Base = 0

The time base is 10 ms.

0

Publisher_Enable = 0, DXB-requesttelegrams are ignored;

Publisher_Enable = 1, DXB-requesttelegrams are processed

0


February 8, 2017



2.5.3 Printing the ProLinx Memory Map

Configuration

Protocol Manual

The ProLinx Memory Map dialog box uses the information about your

PROFIBUS Master and slaves to display the data types that are configured. You need this information to know the starting address of cyclic I/O and gateway status data.


February 8, 2017

Page 69 of 150

Configuration

Protocol Manual

To view or print the ProLinx Memory Map



1 In the Master Setup dialog box, click the S

HOW

PLX M

EMORY

M

AP

button, near the bottom of the window. This action opens ProLinx Memory Map window.

Note: This window uses 16-bit word addressing. The PROFIBUS Master configuration of the slaves uses 8-bit byte addressing.

2 Notice that there are buttons in the Display area of the dialog box to show inputs and outputs. These input and output maps correspond to the input and

output data you configured for the PROFIBUS slaves (page 53). Notice also

that there are check boxes to display slot numbers and PROFIBUS addresses.

3 Click P

RINT

to print the input and output maps for reference. Note that you must do this for both input and output maps.

4 When you have finished printing the ProLinx memory maps, click OK to close the dialog box. Click OK again to close the Master Setup dialog box.

5 Keep the printed memory maps available so you can refer to them when you configure the sample ladder logic in RSLogix. The sample ladder logic contains input and output arrays that must be cross-referenced with the variables.

The next step is to download the project to the ProLinx gateway.


February 8, 2017



2.6 Downloading the Project to the Gateway

Configuration

Protocol Manual

In order for the gateway to use the PROFIBUS network settings you configured, you must download (copy) the updated Project file from your PC to the gateway.

To download the project file

1 In the tree view in ProSoft Configuration Builder, click once to select the gateway that has PLX PDPMV1 section.

2 Open the P

ROJECT

menu, and then choose M

ODULE

 D

OWNLOAD

. The program will scan your PC for a valid com port (this may take a few seconds).

When PCB has found a valid com port, the following dialog box will open.

3 Choose the com port to use from the dropdown list, and then click the

D

OWNLOAD

button.

The gateway will perform a platform check to read and load its new settings.

When the platform check is complete, the status bar in ProSoft Configuration

Builder will be updated with the message Module Running.


February 8, 2017

Page 71 of 150

Configuration

Protocol Manual

2.7 Backing Up the Project



In this step, you will create a backup copy of your project and configuration files.

The backup procedure saves your data for reuse on another machine, or allows you to restore your data in the event of a system failure.

To save your project and configuration files

1 In ProSoft Configuration Builder tree view, click [+] to expand the PDPMV1 tree, and then double-click the PROFIBUS

DP

icon. This action opens the

PDPMV1 PROFIBUS Master Setup dialog box.

2 In the PDPMV1 PROFIBUS Master Setup dialog box, click the E

XPORT

M

ASTER

C

ONFIG

button. This action saves the PROFIBUS network configuration for your gateway in an XML file. The recommended location for this file is your My Documents folder.

Tip: You can use the XML file created by ProSoft Configuration Builder in this step to simplify the task of configuring additional PROFIBUS network modules. Because it saves the entire network configuration, you can add modules quickly by modifying only the items that are unique for each device, typically the slot number and I/O addresses. To use this saved configuration, open

Windows Explorer, navigate to the folder where you saved the Master Configuration XML file, and then drag the file onto the new PROFIBUS DP icon in the ProSoft Configuration Builder tree view.

3 In ProSoft Configuration Builder, open the F

ILE

menu, and then choose S

AVE

A

S

.

4 Name the project file, and click

S

AVE

. The recommended location for this file is your My Documents folder.

Note: All PCB project files and module-related files are automatically saved to C:\PCBExportfFiles.

A complete backup consists of the Project and Master Configuration files, plus the GSD configuration files. The default location for the GSD files is

C:\Documents and Settings\All Users\Application Data\ProSoft\GSD (Windows

XP / 2000) or C:\My Documents\.


February 8, 2017



Configuration

Protocol Manual

PCB does this complete backup for you automatically. The default location for these backup files is C:\PCBExportFiles. All the files associated with your PCB configuration will be stored in a folder with the same name as the name you used to save your PCB configuration (.ppf) file. When you exit PCB, you will be prompted to overwrite your Export folder files.

If you have made changes to your configuration settings, you should click the

Y

ES

button every time you see this dialog box to have the backup files updated.

Having all the files for your PCB configuration stored in one folder makes it easier to transfer the application from one system to the other or to send your files to

ProSoft Technical Support when you need assistance.


February 8, 2017

Page 73 of 150

Configuration

Protocol Manual




February 8, 2017



Mailbox Messaging

Protocol Manual

3 Mailbox Messaging

In This Chapter

 Mailbox Message Queuing .................................................................... 76

 Special Function Mailbox Messaging Commands ................................. 77

 Mailbox Messaging Error Codes ......................................................... 100

The PDPMV1 PROFIBUS DP Master uses a process called Mailbox Messaging to exchange parameter data between the processor, Master, and slave devices.

This process provides a way to encapsulate and prioritize commands and data sent between the PROFIBUS Master and slaves.

The PROFIBUS DP-V1 protocol specifies two types of data transmission messages (telegrams): Cyclic Data Telegrams and Acyclic Data Telegrams.

Cyclic data communication is the exchange of normal slave input and output (I/O) data and is handled automatically by the Master in a defined, recurring, deterministic sequence based on the configuration you create in ProSoft

Configuration Builder (PCB).

Acyclic communication extends data communication beyond normal I/O data to allow moving field device parameterization and calibration data over the bus during runtime and to allow for extended diagnostics and alarm messages.

Acyclic data telegrams are transmitted in the gaps between cyclic data telegrams and, therefore, have a lower priority and get less bandwidth than cyclic data.

Mailbox Messaging commands are incorporated into the sample ladder logic.

Mailbox messages and responses to mailbox messages are stored in mailbox data types.

The following chapter discusses these features in more detail.


February 8, 2017

Page 75 of 150

Mailbox Messaging

Protocol Manual

3.1 Mailbox Message Queuing



The PDPMV1 gateway operates asynchronously on the Mailbox Messages and as such provides for the queuing of the messages as they are received. The queue sizes used in the gateway are as follows:

Queue Type

Output Message from processor

Input Messages for processor

Alarm Messages from slaves for processor

Queue Size Max Description

20

20

20

Number of messages that the ProLinx gateway will queue by type of message. Note that status of the queues can be monitored via the Queue Message Count values.

3.1.1 Queue Timeouts

The PDPMV1 gateway will only allow a message to stay in a queue for up to 10 seconds. If the PROFIBUS Master (for output messages) or the processor (for input and alarm messages) has not successfully received a message within 10 seconds, the gateway will clear the message out of the queue.


February 8, 2017



3.2 Special Function Mailbox Messaging Commands

Mailbox Messaging

Protocol Manual

The PDPMV1 gateway supports some extended PROFIBUS functions, using a mailbox data exchange mechanism implemented in the gateway.

The PDPMV1 gateway supports the following special functions through this mailbox messaging scheme.

Important Note: When you use the database to send your mailbox command, the application places a value of B0 into the first byte of the Message ID word. This value identifies the mailbox command issued, and differentiates the source of the message: either the database or the command structure. You should use a message ID value between 1 and 255 in the message ID header.

Initiated from ProSoft Configuration Builder

Message

Set Operation Mode

Set Slave Mode

Get Slave Diag

Get Slave Config

Get Database Information

Get Live List

MSAC1 Read

MSAC1 Write

Start Slave

Stop Slave

Description

Controls the operating state of the PROFIBUS Master

Sends special control command to one or several slaves

(Sync/Freeze)

Gest diagnostic information from a slave

Gets slave configuration

Gets information from all nodes on the network

DPV1 acyclic read (Class 1)

DPV1 acyclic write (Class 1)

Start Slaves Dynamically

Stop Slaves Dynamically

DPV1 Alarm Handling: Generated by Slave Devices

Message

Alarm Indications

Alarm Confirmation

Description

Spontaneous alarm indication from DPV1 slave. Structure of data is slave-dependent

This message is sent by the ProLinx gateway automatically as a confirmation to the alarm indications.

The provided Function Blocks simplify the processor logic required to implement these messaging mailbox exchanges.

Sending a mailbox message to the PDPMV1 gateway is a relatively simple process, however, it is important to follow a certain sequence.


February 8, 2017

Page 77 of 150

Mailbox Messaging

Protocol Manual

Mailbox Message Structure: To PDPMV1 Gateway

Byte Offset

0

Type

Message ID



Description

Processor logic or user set. The Message ID field is used by the ProLinx gateway to detect a new message in the

PROFIBUS Output data image.

When a non-zero value is detected, the message is processed immediately. The sample ladder logic assigns specific message IDs to different mailbox messages.

See individual commands for data values to be entered in each of these register locations

10

11

12

13

6

7

8

9

1

2

3

4

5

14

15

-

149

Message Info

Command

Data Size

Frame Count

Frame Number

Offset High

Offset Low

Extended Word 1

Extended Word 2

Extended Word 3

Extended Word 4

Extended Word 5

Extended Word 6

Extended Word 7

Extended Word 8

See individual commands

3.2.1 Mailbox Message: Set Operating Mode

This command allows setting the operating mode of the PROFIBUS Master

(STOP, CLEAR, or OPERATE).

Parameter

Command Initiator

Command Name

Command Number

Fragmented

Extended Header Data

Description

Application

SET OPERATING MODE

0200h

No

Fault information may be returned in the header of the response.


February 8, 2017



Command and Response Layout: Set Operating Mode

Command

Response

(ID)

4002h

Message ID

Acyclic Message Status

Word

Command

Data size

Frame count

Frame number

Offset high

Offset low

Extended word 1

0002h

0000h

0001h

0001h

Mode

0000h

0000h

Conf. Req

(ID)

0002h

0002h

0000h

0001h

0001h

Mode

0000h

0000h

Conf. Req

Extended word 2

Extended word 3

Extended word 4

Extended word 5

Extended word 6

Extended word 7

Extended word 8

-

-

-

-

-

-

-

-

-

-

-

-

Appl. Specific Error Code

Fault Information

Mailbox Messaging

Protocol Manual

Set Operation Mode

Mode

40h: STOP

80h: CLEAR

C0h: OPERATE

Conf. Req.

00h: Confirmation is not required

01h: Confirmation required. All confirmations are automatically sent by the

Master; the user is not required to send a confirmation message.

Fault Information

If "Invalid Other" is returned in the Acyclic Message Status Word in the header of the response, information about the fault can be found here. Refer to Return

Codes (page 101) for more information.

0100h: Invalid operating mode

FF00h: Module not initialized


February 8, 2017

Page 79 of 150

Mailbox Messaging

Protocol Manual

3.2.2 Mailbox Message: Set Slave Mode



In addition to station-related user data transfer, which is executed automatically, the Master can send control commands to a single slave, a group of slaves, or all slaves simultaneously. These control commands are transmitted as multicast commands. This permits use of sync and freeze modes for event-controlled synchronization of the slaves.

The slaves begin sync mode when they receive a sync command from their assigned Master. The outputs of all addressed slaves are then frozen in their current state. During subsequent user data transmissions, the output data are stored on the slaves, but the output states remain unchanged. The stored output data are not sent to the outputs until the next sync command is received. Sync mode is concluded with the unsync command.

Similarly, a freeze control command causes the addressed slaves to assume freeze mode. In this operating mode, the states of the inputs are frozen until the

Master sends the next freeze command. Freeze mode is concluded with the unfreeze command.

Note 1: It is only possible to send control commands when operating mode is either CLEAR or

OPERATE.

Note 2: Not all slaves support this feature. Refer to the documentation for the actual slave for more information.

Parameter

Command Initiator

Command Name

Command Number

Fragmented


Description

Application

SET SLAVE MODE

0300h

No



February 8, 2017



Command and Response Layout: Set Slave Mode

Command

Response

Message ID (ID)


Word

Command

4002h

0003h

Data size 0000h

Frame count 0001h

Frame number 0001h

Offset high 0000h

Offset low

Extended word 1 Slave

Address

Extended word 2 Control

Command

Extended word 3

0000h

Group Select

-

Extended word 4 -

Extended word 5 -

Extended word 6 -

Extended word 7 -

Extended word 8

(ID)

0002h

0003h

0000h

0001h

0001h

Slave

Address

Control

Command

0000h

0000h

Group Select

-

-

Set Slave Mode

-

-

Extended Fault Information

Fault Information

Mailbox Messaging

Protocol Manual

Acyclic Message Status Word

Refer to Acyclic Message Status Word (page 100).

Slave Address

Range 1 to 125; 127

If the request applies for only one slave, that Slave Address must be entered in the range 1 to 125. If a slave group is to be addressed, Slave Address should be

127 (Multicast address).


February 8, 2017

Page 81 of 150

Mailbox Messaging

Protocol Manual

Group Select



Range 01h to FFh (Bit Coded)

This parameter determines which group to address. Refer to the following example:

b7 b6 b5 b4 b3 b2 b1 b0

Group 8 Group 7 Group 6 Group 5 Group 4 Group 3 Group 2 Group 1

Example: To address Group 1, 2, and 4, the Group Select value should be D0h.

If an individual slave should be addressed, the correct group selection must also be made, because the slave will ignore the message if it does not belong to the requested group(s).

What group(s) a slave belongs to is determined during network configuration, and is downloaded during initialization to each slave via the PROFIBUS telegram

"Set_Prm".

Control Command

This parameter specifies the command to send:

Bit

0 (LSB)

1

2

3

4

5

6

7 (MSB)

Explanation

Reserved, set to zero


Unfreeze input data

Freeze input data

Unsynchronize output data

Synchronize output data



Combinations of the bits (Unsync/Sync and Unfreeze/Freeze)

Bits 0 or 6

0

0

1

1

Bits 1 or 7

0

1

0

1

Explanation

No Function

Function will be activated

Function will be inactive

Function will be inactive


February 8, 2017



Fault Information and Extended Fault Information

Mailbox Messaging

Protocol Manual

"Fault Information" Contents

0100h Address out of range

"Extended Fault Information" Contents

-

0200h -

0A00h

Group number 0 not permitted

Failed to send Global

Control request

0A00h

0150h

0250h

0350h

0450h

Incorrect operation mode (Clear/Operate Only)

Invalid Freeze Group (Group is not initiated to be

Freeze Group)

Invalid Sync Group (Group is not initiated to be

Sync Group)

Incorrect Control Command

No Sync -/ or Freeze groups enabled in Master configuration

FE00h

FF00h

Command not possible in Class 2 only mode

-

Module not initialized -

3.2.3 Mailbox Message: Get Slave Diagnostics

This command reads diagnostic data from a specified slave.

Note: The response data size depends on the actual slave implementation. Range 6 to 244.

Parameter

Command Initiator

Command Name

Command Number

Fragmented


Description

Application

GET SLAVE DIAGNOSTICS

0400h

No



February 8, 2017

Page 83 of 150

Mailbox Messaging

Protocol Manual

Command and Response Layout: Get Slave Diagnostics

Command Response

(ID)

4002h

Message ID


Word

Command

Data size

Frame count

Frame number

Offset high

Offset low

Extended word 1

Extended word 2

Extended word 3

Extended word 4

Extended word 5

0004h

0000h

0001h

0001h

Slave

Address

0000h

0000h

Type of

Request

-

-

-

-

(ID)

0002h

Extended word 6

Extended word 7

Extended word 8

-

-

-



0004h

(Size of data)

0001h

0001h

Get Slave Diagnostics

Slave

Address

0000h

0000h

Type of

Request

-

-

-

Error Code 1 Error Code

2

Error Code 3 Error Code

4

Extended Fault Info

Fault Information

Station

Status 1

Station

Status 3

Station

Status 2

Station

Status 4

Ident Number

Response data word 1



Extended Diagnostic Data Response data word 4

...

...

Response data word n



Slave Address

Range 1 to 125; specifies the slave from which to read diagnostics.


February 8, 2017



Type of request

Mailbox Messaging

Protocol Manual

00h: Internal slave diagnostic request. Returns the diagnostic information stored in the Master. Can only be requested for slaves configured by the Master.

Note: Not allowed when operating in "Class 2-Only" mode.

01h: External slave diagnostic request. Sends a diagnostic request on the network to the specified slave. Can be requested for all slaves on the network.

Error code [1 ...4]

If "Return Code" equals 8030h ("Negative indication from lower layer"), status values according to the DP-specification may be available in "Error Code 1".

Error Codes 2 to 4 are reserved.

Refer to Mailbox Messaging Error Codes (page 100).

Return Code

Refer to Mailbox Messaging Error Codes (page 100)


If "Invalid Other" is returned in the Acyclic Message Status Word in the header of the response, information about the fault can be found here.

0100h: Address out of range.

0200h: Incorrect "Type of request"

0A00h: Failed to read diagnostic data from slave. Refer to Return Codes (page

101) for additional fault information.

0B00h: Remote station failure. Refer to Return Codes (page 101) for additional

fault information.

FE00h: Command not possible; module operates as a Class 2 Master only.

FF00h: Module offline (not initialized or no valid database).

Station Status [1 ... 3]

Refer to EN50170 Vol. 2 for more information.

Master Address

Address of the Master that parameterized the slave.

Ident Number

Unique ID assigned by the PROFIBUS User Organization.


February 8, 2017

Page 85 of 150

Mailbox Messaging

Protocol Manual

Extended Diagnostic Data



Slave user-specific data. Refer to the documentation for the actual slave for more information.

3.2.4 Mailbox Message: Get Slave Configuration

This command reads the actual configuration (identifier bytes) of a specified slave.

Note: The response data size depends on the actual slave implementation. Range 6 to 244.

Parameter

Command Initiator

Command Name

Command Number

Fragmented


Description

Application

GET SLAVE CONFIGURATION

0500h

No


Command and Response Layout: Get Slave Configuration

Message ID


Word

Command

Data size

Command

(ID)

4002h

0005h

0000h

Response

(ID)

0002h

Frame count

Frame number

Offset high

Offset low

Extended word 1

Extended word 2

Extended word 3

Extended word 4

Extended word 5

Extended word 6

Extended word 7

Extended word 8

Slave

Address

0001h

0001h

0000h

0000h

-

-

-

-

-

-

-

0005h

(Size of data)

Slave

Address

0001h

0001h

0000h

0000h

-

-

-

Error Code 1 Error Code 2

Get Slave Configuration

Number of identifier bytes

(n)


Return Code

Fault Information


February 8, 2017




Identifier byte 1

Identifier byte 2

Identifier byte 3

...

Identifier byte n




...

Response data word n



Slave Address

Range 1 to 125; specifies the slave from which to read the configuration.

Mailbox Messaging

Protocol Manual

Error Code [1 … 4]

If "Return Code" equals 3080h ("Negative indication from lower layer"), status values according to the DP-specification may be available in "Error Code 1",

Error Codes 2 through 3 are reserved. Refer to Mailbox Messaging Error Codes

(page 100).

Return Code

Refer to Mailbox Messaging Error Codes (page 100).


If "Invalid other" is returned in the Acyclic Message Status Word in the header of the response, information about the fault can be found here. Refer to Acyclic

Message Status Word (page 100).

0100h: Address out of range.

0A00h: Failed to execute request. Refer to Return Codes (page 101) for

additional information.

0B00h: Remote station failure. Refer to Return Codes (page 101) for additional

information.

FF00h: Module not initialized.

Identifier Bytes [1 … n]

Refer to EN50170 Vol. 2 for information on the structure of these bytes. In addition, refer to the documentation provided with the slave device for more information.

3.2.5 Mailbox Message: Get Database Information

This command fetches information about the stored database (that is, userspecific data that was downloaded to the gateway in the Message Data 1 to 32 via mailbox "FB_APPL_END_DATABASE_DOWNLOAD" or from the configuration tool).


February 8, 2017

Page 87 of 150

Mailbox Messaging

Protocol Manual



This message also returns information about the amount of allocated I/O-data in the input and output areas. These sizes can be used by the application to set up the I/O-lengths for the ANYBUS_INIT message.

Parameter

Command initiator

Command Name

Command number

Fragmented

Firmware Revision

Description

Application

FB_APPL_GET_DATABASE_INFO

0017h

No

All

Command and Response Layout: Get Database Information

Command Response

Message ID


Word

Command

(ID)

4002h

0017h

(ID)

0002h

0017h

Data size

Frame count

Frame number

Offset high

Offset low

Extended word 1

Extended word 2

Extended word 3

Extended word 4

Extended word 5

Extended word 6

Extended word 7

Extended word 8

0000h

-

-

-

0001h

0001h

0000h

0000h

-

-

-

-

0040h

Get Database Info

Number of identifier bytes

(n)

0001h

0001h

0000h

0000h

Total Output Length

Total Input Length

Init Output Size

Init Input Size

No. of

Slaves

-

-

-

Fault Information

Database Description

(ASCII, 64 characters)

Response data word 1 to 32


February 8, 2017



Command Response

Mailbox Messaging

Protocol Manual


February 8, 2017

Page 89 of 150

Mailbox Messaging

Protocol Manual



Total Input Length, Total Output Length: The sum of Input/Output lengths for all slaves in the database (in bytes).

Init Input size, Init Output size: Required initialization Input/Output sizes for the current database. If the slaves are located in a contiguous block these sizes are the same as total Input/Output lengths.

Note: The input/output direction refers to the directions and naming used for the DPRAM areas, not to the input/output directions used in the bus database or the The Bus Configuration window-

PB.

Database Description: String of ASCII characters that describes the data base file. This is the string that was written to the database by the

"FB_APPL_END_DATABASE_DOWNLOAD" command.

No. of Slaves: Number of configured slaves in the database.


If "Invalid Other" is returned in the Acyclic Message Status Word in the header of the response, information about the fault can be found here. Refer to Return

Codes (page 101) for more information.

0001h: No database in flash, or download in progress.

3.2.6 Mailbox Message: Get Live List

This command returns 127 bytes of information about the nodes on the network.

Every byte stands for one bus subscriber, and the position of the byte in the response data assigns the address (0 to 126); the content assigns the Station

Type.

This command can be sent in all operation modes (STOP, CLEAR, and

OPERATE); however, the module must be initialized properly.

Parameter

Command Initiator

Command Name

Command Number

Fragmented


Description

Application

GET LIVE LIST

1800h

No



February 8, 2017



Command and Response Layout: Get Live List

Message ID


Word

Command

Data size

Command

(ID)

4002h

0018h

0000h

Frame count

Frame number

Offset high

Offset low

Extended word 1

Extended word 2

Extended word 3

Extended word 4

Extended word 5

Extended word 6

Extended word 7

Extended word 8

Message Data byte 1

Message Data byte 2

Message Data byte 3

...

Message Data byte "n"

-

-

-

-

-

-

0001h

0001h

0000h

0000h

-

-

Response

(ID)

0002h

0018h

007Fh

-

-

-

-

0001h

0001h

0000h

0000h

-

-

Return Code

Fault Information

Station Type 0

Station Type 1

Station Type 2

...

Station Type 126

Mailbox Messaging

Protocol Manual

Get Live List

127 Bytes of Data

Response Data Byte 1







Station Type [0 … 126]

00h: Slave Station

01h: Master Station not yet ready for Token ring (station only physically at the bus)

02h: Master Station ready to enter Token ring (there is not yet any Token transmission)

03h: Master Station in Token Ring (Token transmission through the station)

04h: Station does not exist


If "Invalid Other" is returned in the Acyclic Message Status Word in the header of the response, information about the fault can be found here. Refer to Acyclic

Message Status Word (page 100).

0AH00: Failed to build Live List.


February 8, 2017

Page 91 of 150

Mailbox Messaging

Protocol Manual

FF00h: Module offline (not initialized or no valid database)



3.2.7 Mailbox Message: Acyclic Data Read: Class 1

This command initiates a DPV1 Class 1 acyclic read request. Refer to EN50170

(DPV1) for more information.

Parameter

Command Initiator

Command Name

Command Number

Fragmented


Description

Application

MSAC1 READ

2000h

No


Command and Response Layout: Acyclic Read


Message ID (ID) (ID)


Word

Command

4002h 0002h

0020h 0020h Acyclic Read

Data size 0000h (Size of data) Number of data bytes (n)

Frame count 0001h 0001h

Frame number 0001h 0001h

Offset high 0000h 0000h

Offset low 0000h 0000h

Extended word 1 Slave Addr. Slot Number Slave Addr. Slot Number

Extended word 2

Extended word 3

Extended word 4

Extended word 5

Extended word 6

Extended word 7

Extended word 8

Index

-

-

-

-

-

-

Length Index Length

-

-

Error

Decode


Extended Fault information

Fault Information

Data 1 Response Data byte 1



... ...

Data n Response Data byte 1


February 8, 2017





Slave Address

Station address of the slave responder.

Slot Number and Slot Index

Used in the slave to address the desired data block.

Mailbox Messaging

Protocol Manual

Length

This parameter specifies the number of bytes of the data block to read. If the server data block length is less than requested, the length of the response will be the actual length of the data block. If the server data block is greater or equal, the response will contain the same amount of data.

The slave may answer with an error response if data access is not allowed.

Data [1 … n]

Returned data.


If "Invalid Other" is returned in the Acyclic Message Status Word in the header of the response, information about the fault can be found here.

"Fault Information"


0A00h Failed to execute request

FE00h Command not possible in "Class 2-

Only" mode

FF00h Module offline (not initialized or no valid database)

"Extended Fault Information" Contents

-

Refer to Return Codes (page 101).

0B00h Remote station failure

1000h Remote station DPV1 failure Function_Number

1100h Length out of range (>240 bytes) -

1200h Slave does not support DPV1

1300h Slave not active or not present in configuration

-

-

-

-

Error Decode, Error Code 1 and Error Code 2

If "Fault Information" contains error code 1000h, more information according to the DPV1 specification can be found here.


February 8, 2017

Page 93 of 150

Mailbox Messaging

Protocol Manual

3.2.8 Mailbox Message: Acyclic Data Write: Class 1



This command initiates a DPV1 Class 1 acyclic write request. Refer to EN50170

(DPV1) for more information.

Parameter

Command Initiator

Command Name

Command Number

Fragmented


Description

Application

MSAC1 WRITE

2100h

No


Command and Response Layout: Acyclic Write




Word

Command

4002h 0002h

0021h 0021h Acyclic Write

Data size (Size of data) (Size of data)





Extended word 1 Slave Addr. Slot Number Slave Addr. Slot Number

Extended word 2 Index Length Index Length

Extended word 3 - -

Number of data bytes (n)

Extended word 4

Extended word 5

Extended word 6

Extended word 7

Extended word 8

Message Data byte 1

-

-

-

-

-

Data 1

-

Error

Decode-


Extended Fault information

Fault Information

Data 1

Message Data byte 2

Message Data byte 3

...

Message Data byte n

Data 2

Data 3

...

Data n

Data 2

Data 3

...

Data n




February 8, 2017



Slave Address

Station address of the slave responder.

Mailbox Messaging

Protocol Manual

Slot Number and Slot Index

Used in the slave to address the desired data block.

Length

This parameter specifies the number of bytes to write. If the destination data block size is less than requested, the response will contain an error message. If the data block length is greater than or equal to the requested length, the response contains the number of bytes that have been written. The slave may answer with an error response if data access is not allowed.

Data [1 … n]

Data that should be written.


If "Invalid Other" is returned in the Acyclic Message Status Word in the header of the response, information about the fault can be found here:

"Fault Information" "Extended Fault Information" Contents


0A00h Failed to execute request

0B00h Remote station failure

1000h Remote station DPV1 failure

-

Refer to Return Codes (page 101).

Function_Number

1100h Length out of range (>240 bytes) -

1200h Slave does not support DPV1 -

- 1300h Slave not active or not present in configuration

FE00h Command not possible in "Class 2-

Only" mode

FF00h Module offline (not initialized or no valid database)

-

-

Error Decode, Error Code 1, and Error Code 2

If "Fault Information" contains error code 1000h, more information according to the DPV1 specification can be found here.


February 8, 2017

Page 95 of 150

Mailbox Messaging

Protocol Manual

3.2.9 Mailbox Message: Start Slave



This mailbox message starts a selection of slaves that was previously removed from the processing cycle by means of the mailbox message

FB_APPL_STOP_SLAVE.

This message is allowed in all operation modes (STOP, CLEAR and OPERATE).

Note: The message will be accepted even if one or several slaves are not part of the configuration and can therefore obviously not be started. The application can, however, find out about this situation by evaluating the "Fault information" and "Message data words" of the response.

Command and Response Layout: Start Slave




Word

Command

4002h 0002h

000Bh 000Bh

Data size 007Eh 007Eh





Extended word 1

Extended word 2 - -

Extended word 3 - -

Extended word 4 - -

Extended word 5 - -

Extended word 6 - -

Extended word 7 - Additional Fault Information

Extended word 8 - Fault Information

Message data word 1 Slave 0


Message data word 3 to

62

...

Slave 1

Slave 3

...

Slave 0

Slave 2

...

Message data word 63 Slave 124 Slave 125 Slave 124

Command:

Slave 1

Slave 3

...

Slave 125

Start Slave

 Message data word 1-63

Byte-array stating which slave/slaves to start. Array index is equal to slave address.

0: Do not affect slave


February 8, 2017



1: Start slave

2-255: Reserved

Mailbox Messaging

Protocol Manual

Response:

 Acyclic Message Status Word (in response header)

"Invalid Data Size" is returned if Data size in the command header does not equal 126.

If "Invalid Other" is returned, further information is to be found in Extended word 8.

 Additional Fault information (Extended word 7)

If Extended word 8 equals 0x000A -"Failed to execute request" additional info can be found here

 Fault information (Extended word 8)

0x0001: Invalid setting in Message data word 1-63 of the command.

0x0002: At least one slave reports a warning. Refer to Message data word 1-

63.

0x000A: Failed to execute request. Additional fault information is to be found in Extended word 7.

0x00FE: Command not possible, module operates as Class 2 Master only.

0x00FF: Module not initialized (this command is only possible after

END_INIT).


Byte-array stating the status of the slaves. Array index is equal to slave address.

0: Slave unaffected

1: Slave started

2: Warning - Slave could not be started because it is not part of the configuration

3.2.10 Mailbox Message: Stop Slave

This mailbox message stops a selection of slaves from the processing cycle.

This message is allowed in all operation modes (STOP, CLEAR and OPERATE).

Note: The message will be accepted even if one or several slaves are not part of the configuration and can therefore obviously not be stopped. The application can, however, find out about this situation by evaluating the "Fault information" and "Message data words" of the response.


February 8, 2017

Page 97 of 150

Mailbox Messaging

Protocol Manual

Command and Response Layout: Stop Slave

Command

Response

(ID)

4002h

Message ID


Word

Command

Data size

Frame count

Frame number

Offset high

Offset low

Extended word 1

000Ch

007Eh

0001h

0001h

0000h

0000h

-

(ID)

0002h

000Ch

007Eh

0001h

0001h

0000h

0000h

-

Extended word 2

Extended word 3

Extended word 4

Extended word 5

Extended word 6

Extended word 7

Extended word 8


-

-

-

-

-

-

-

Slave 1

-

-

-

-

-

Additional Fault Information

Fault Information

Slave 0 Slave 1



Stop Slave

Message data word 2 Slave 2 Slave 3 Slave 2 Slave 3

Message data word 3 to

62

... ...

Message data word 63 Slave 124 Slave 125

... ...

Slave 124 Slave 125

Command:


Byte-array stating which slave/slaves to stop. Array index is equal to slave address.

0: Do not affect slave

1: Stop slave

2-255: Reserved


February 8, 2017



Mailbox Messaging

Protocol Manual

Response:

 Acyclic Message Status Word (in response header)

"Invalid Data Size" is returned if Data size in the command header does not equal 126.

If "Invalid Other" is returned, further information is to be found in Extended word 8.

 Additional Fault information (Extended word 7)

If Extended word 8 equals 0x000A -"Failed to execute request" additional info can be found here.

 Fault information (Extended word 8)

0x0001: Invalid setting in Message data word 1-63 of the command.

0x0002: At least one slave reports a warning. Refer to Message data word 1-

63.

0x000A: Failed to execute request. Additional fault information is to be found in Extended word 7.

0x00FE: Command not possible, module operates as Class 2 Master only.

0x00FF: Module not initialized (this command is only possible after

END_INIT).


Byte-array stating the status of the slaves. Array index is equal to slave address.

0: Slave unaffected

1: Slave stopped

2: Warning - Slave could not be stopped because it is not part of the configuration

3: Warning - Slave already stopped


February 8, 2017

Page 99 of 150

Mailbox Messaging

Protocol Manual

3.3 Mailbox Messaging Error Codes



3.3.1 Acyclic Message Status Word

This register contains bit and code information about the mailbox message. The register is divided into five areas according to the following illustration:

b15 b14 b13 b12 b11 b10 b9 b8

Message Type

b7 b6 b

5

ER

R

C/

R

b4 b

3 b2

(reserved) Error Code

b1 b0

Bit / Field Description

ERR This bit indicates if the received command contained any errors.

C/R This bit specifies whether the message is a command or a response.

Error Code If the ERR bit is set, this field contains additional information about the error.

Message

Type

This field specifies the type of the message.

Contents

0:

1:

Message OK

Error (See also "Error Code" below)

0:

1:

Response Message

Command Message

0h:

1h:

2h:

3h:

4h:

5h:

6h:

8h:

9h:

Fh:

Invalid Message ID

Invalid Message Type

Invalid Command

Invalid Data Size

Message header malformed (offset 008h)

Message header malformed (offset 00Ah)

Message header malformed (offset 00Ch to 00Dh)

Invalid Response

Flash Config Error

Invalid Other

(All other values are reserved)

1h: Application Message

2h: PROFIBUS Specific Message

3h: Memory Message

5h: Reset Message

(All other values are reserved)


February 8, 2017



3.3.2 Return Codes

Mailbox Messaging

Protocol Manual

Possible error codes in Message Data word "Return Code" (The Return Codes

can be byte swapped)

Return Code Name

8010h DPMC_ERR_V1C_CLOSED

8011h DPMC_ERR_V1C_STOPPED

8012h

8013h

DPMC_ERR_V1C_STARTED

DPMC_ERR_V1C_STATE_UNKNOWN

8042h

8043h

80C1h

80C2h

80C3h

80C4h

80C5h

8021h

8022h

8023h

8024h

8025h

8026h

8028h

8030h

8031h

80C6h

80C7h

80C8h

80C9h

80CAh

80CBh

80CCh

DPMC_ERR_V1C_REQ_ACTIVE

DPMC_ERR_V1C_NOT_ALLOWED

DPMC_ERR_V1C_INVALID_PAR

DPMC_ERR_V1C_MEM_ALLOC

DPMC_ERR_V1C_L2_REQ

DPMC_ERR_V1C_TIMEOUT

DPMC_ERR_V1C_INVALID_LEN

DPMC_ERR_V1C_REQ_NEG

1

DPMC_ERR_V1C_REQ_RE

DPMC_ERR_V1C_REQ_WITHDRAW

DPMC_ERR_V1C_REQ_NOT_FOUND

DPMC_ERR_V1C_MM_FE

DPMC_ERR_V1C_MM_NI

DPMC_ERR_V1C_MM_AD

DPMC_ERR_V1C_MM_EA

DPMC_ERR_V1C_MM_LE

DPMC_ERR_V1C_MM_RE

DPMC_ERR_V1C_MM_IP

DPMC_ERR_V1C_MM_SC

DPMC_ERR_V1C_MM_SE

DPMC_ERR_V1C_MM_NE

DPMC_ERR_V1C_MM_DI

DPMC_ERR_V1C_MM_NC

Meaning

Internal DPMC instance no longer exists

Internal DPMC instance has already been stopped

Internal DPMC instance has already been started

Internal DPMC instance has entered an undefined state

A request is already active

Internal DPMC module not initialized correctly

Invalid parameter in user request

Internal memory allocation error

Unknown opcode in the confirmation

Active request terminated with timeout

Invalid length in user request

Negative indication from lower layer

Message frame format error in response

Request was recalled

Associated request block not found

Format error in request frame

Function not implemented

Access denied

Area too large

Data block length too large

Format error in response frame

Invalid parameter

Sequence conflict

Sequence error

Area non-existent

Data incomplete or incorrect

Master parameter set not compatible

Refer to Error Codes (page 102).


February 8, 2017

Page 101 of 150

Mailbox Messaging

Protocol Manual

3.3.3 Error Codes



If the return code indicates DPMC_ERR_V1C_REQ_NEG, the status values according to the DP-standard may be available in Error Code 1. Refer to the

PROFIBUS DP specification for information on how to interpret these status values.

Error Code

01h

02h

03h

0Ch

0Dh

0Fh

Name

L2_STATUS_UE

L2_STATUS_RR

L2_STATUS_RS

L2_STATUS_RDL

L2_STATUS_RDH

L2_STATUS_NA

Meaning

Refer to PROFIBUS DP specification


February 8, 2017



3.3.4 DP-V1 Error Codes

Mailbox Messaging

Protocol Manual

Possible error codes in Message Data word "Return Code".

0044h

0045h

0046h

0047h

0048h

0049h

004Ah

004Bh

004Ch

004Dh

004Eh

0034h

0035h

0036h

0037h

0038h

0040h

0041h

0042h

0043h

Return Code Name

0003h DPMC_ERR_M_MEM_ALLOC

0004h

0005h

0007h

0012h

0018h

0021h

0022h

0023h

0024h

002Fh

0031h

DPMC_ERR_M_L2_REQ

DPMC_ERR_M_INVALID_PAR

DPMC_ERR_M_NOT_IN_DATA

Meaning

Internal memory allocation error

Unknown opcode in the configuration

Invalid parameter in user request

Slave is not in DataExchange (thus no DP-V1 request can exist)

A request is already active DPMC_ERR_M_REQ_ACTIVE

DPMC_ERR_M_NOT_ALLOWED

DPMC_ERR_M_CLOSED

DPMC_ERR_M_STOPPED

Internal DPMC module not initialized correctly

Internal DPMC instance no longer exists

Internal DPMC instance has already been stopped

DPMC_ERR_M_STARTED

DPMC_ERR_M_STATE_UNKNOWN

Internal DPMC instance has already been started

Internal DPMC instance has entered an undefined state

DPMC_ERR_M_SLAVE_NOT_FOUND Slave does not respond

DPMC_ERR_M_TIMEOUT Active request terminated with timeout

DPMC_ERR_M_INVALID_LEN

DPMC_ERR_M_REQ_NEG

DPMC_ERR_M_REQ_RE

DPMC_ERR_M_REQ_WITHDRAW

DPMC_ERR_M_REQ_NOT_FOUND

DPMC_ERR_M_MM_FE

DPMC_ERR_M_MM_NI

DPMC_ERR_M_MM_AD

DPMC_ERR_M_MM_EA

Invalid length in user request

Negative indication from lower layer

Message frame format error in response

Request was recalled

Associated request block not found

Format error in request frame

Function not implemented

Access denied

Area too large

DPMC_ERR_M_MM_LE

DPMC_ERR_M_MM_RE

DPMC_ERR_M_MM_IP

DPMC_ERR_M_MM_SC

DPMC_ERR_M_MM_SE

DPMC_ERR_M_MM_NE

DPMC_ERR_M_MM_DI

DPMC_ERR_M_MM_NC

DPMC_ERR_M_S7_XA

DPMC_ERR_M_S7_XR

DPMC_ERR_M_S7_XW

Data block length too large

Format error in response frame

Invalid parameter

Sequence conflict

Sequence error

Area non-existent

Data incomplete or incorrect

Master parameter set not compatible

PROFIBUS error for DP-V1 (NRS-PDU received)


February 8, 2017

Page 103 of 150

Mailbox Messaging

Protocol Manual

3.3.5 Command Error Codes



Errors reported from the command list of the gateway require 8 bytes or 4 words per command. If the first 7 bytes of the error are 0xFF, this is a gatewaygenerated error as follows:

Value of Last Byte Error Definition

0x00 Too few parameters for command in command list section of configuration file.

0x01

0x02

0x03

0x04

0x05

0x10

0xFF

Invalid type value specified for command.

Invalid database offset specified for command.

Invalid swap type code specified for command.

Invalid database trigger address

Invalid database address and count combination

Invalid function code specified for command.

Response timeout for command recognized.

Refer to Error Codes (page 102) for an explanation of other error codes.

The 8 bytes (4 words) represent the extended words 5 to 8 in response messages.


February 8, 2017



Diagnostics and Troubleshooting

Protocol Manual

4 Diagnostics and Troubleshooting

In This Chapter

 Required Hardware ............................................................................. 106

 Basic Troubleshooting Steps ............................................................... 107

 PROFIBUS DP-V1 (PDPMV1 Driver) Master LED Indicators .............. 108

 Viewing the Online Status of the PROFIBUS Network ........................ 110

 Using ProSoft Configuration Builder (PCB) for Diagnostics................. 112

 Standard PROFIBUS Slave Diagnostic Bytes ..................................... 117

 Status and Status Mapping ................................................................. 119

There are two ways to troubleshoot ProLinx gateways:

 Using the LEDs located on the front of the gateway

 Using the Debug port, which provides a view into the gateway's internal database.


February 8, 2017

Page 105 of 150


Protocol Manual

4.1 Required Hardware



You can connect di rectly from your PC’s serial port to the serial port on the gateway to view configuration information, perform maintenance, and send or receive configuration files.

ProSoft Technology recommends the following minimum hardware to connect your PC to the gateway:

 80486 based processor (Pentium preferred)

 1 megabyte of memory

 At least one UART hardware-based serial communications port available.

USB-based virtual UART systems (USB to serial port adapters) often do not function reliably, especially during binary file transfers, such as when uploading/downloading configuration files or gateway firmware upgrades.


February 8, 2017



4.2 Basic Troubleshooting Steps


Protocol Manual

1 Verify that the gateway is installed correctly, and the Main menu is displayed.

2 Install the most current version of ProSoft Configuration Builder.

3 Note the color and behavior of the LED Status Indicators (lights) on the front panel. Refer to the chart in the following section for examples.


February 8, 2017

Page 107 of 150


Protocol Manual



4.3 PROFIBUS DP-V1 (PDPMV1 Driver) Master LED Indicators

The LEDs indicate the gateway’s operating status.

PROFIBUS Master Status LEDs o o o o

COM STAT

DBASE STAT

MAST STAT

TKN HOLD

4.3.1 PROFIBUS Master Indicators

LED

TKN HLD

State

GREEN

OFF

DBASE STAT GREEN

GREEN-Flashing

RED

OFF

MSTR STAT GREEN

GREEN-Flashing

RED

OFF

COM STAT GREEN

GREEN-Flashing

RED

OFF

ALL LEDs RED

Description

The gateway has the token

The gateway does not have the token

Database OK

Database download in progress

Invalid database

No databases have been downloaded

Operating mode

Clear mode

Stop mode

Offline

Data exchange with all configured slaves

Data exchange with at least one configured slave but not all configured slaves

Bus control error (possible bus short circuit or configuration error)

No data exchange with any configured slave

Fatal error


February 8, 2017



4.3.2 Examples

Gateway

Status

Normal operation ACTIVE

(ON)

PROFIBUS Master

Status

PROFIBUS Master is stopped

ACTIVE

Master not communicating with slaves

ACTIVE


Protocol Manual

PROFIBUS Master Status LED

Description

COM STAT (GREEN):

Master is communicating with all configured slaves.

DBASE STAT (GREEN):

PROFIBUS has been configured.

TKN HOLD (GREEN):

Gateway is holding the PROFIBUS token.

MSTR STAT (GREEN):

Master is in operating mode.

COM STAT (OFF):

Master is not communicating with configured slaves.





MSTR STAT (RED):

Master is in STOP mode.

COM STAT (OFF):

Master is operating but there are no slaves responding.





MSTR STAT (GREEN):

Master is in operating mode.


February 8, 2017

Page 109 of 150


Protocol Manual

4.4 Viewing the Online Status of the PROFIBUS Network



Note: For this procedure, you must connect a serial cable from the serial port on your PC to the

RJ45 to DB9M adaptor cable on the PDPMV1 gateway.

1 In ProSoft Configuration Builder for PROFIBUS, open the

O

NLINE

menu, and then choose

M

ONITOR

/M

ODIFY

. ProSoft Configuration Builder will establish communication with the PDPMV1 gateway, and will indicate communication status. o o o

If the slave icon in the Bus Configuration window has a green border, then the PDPMV1 gateway is correctly communicating with the PROFIBUS slave.

If the slave icon in the Bus Configuration window has a red border, then the gateway is not communicating with the slave.

If the slave icon in the Bus Configuration window has a blue border, the slave is communicating with the Master, but is generating diagnostic data.

To view diagnostic data for the slave, select the slave, and click the right mouse button to open a shortcut menu. On the shortcut menu, choose

O

NLINE

P

ROPERTIES

.


February 8, 2017




Protocol Manual

2 In the Online Slave Properties dialog box, click the D

IAGNOSTIC

tab, and select (

CHECK

) D

ETAILS FOR SLAVE DIAGNOSTIC

. Slave diagnostic information will appear in the Diagnostic window. Refer to the documentation for your

PROFIBUS slave to determine the meaning of the diagnostic data.


February 8, 2017

Page 111 of 150


Protocol Manual



4.5 Using ProSoft Configuration Builder (PCB) for Diagnostics

The Configuration and Debug menu for this gateway is arranged as a tree structure, with the Main menu at the top of the tree, and one or more sub-menus for each menu command. The first menu you see when you connect to the gateway is the Main menu.

Because this is a text-based menu system, you enter commands by typing the

[command letter] from your computer keyboard in the Diagnostic window in

ProSoft Configuration Builder (PCB). The gateway does not respond to mouse movements or clicks. The command executes as soon as you press the

[

COMMAND LETTER

]

— you do not need to press [E

NTER

].

When you type a

[

COMMAND LETTER

], a new screen will be displayed in your terminal application.

4.5.1 Using the Diagnostic Window in ProSoft Configuration Builder

- PLX

Tip: You can have a ProSoft Configuration Builder Diagnostics window open for more than one module or gateway at a time.


February 8, 2017



To connect to the gateway’s Configuration/Debug serial port


1 Start ProSoft Configuration Builder with the application file to be tested.

Right-click the module icon.

Protocol Manual

2 On the shortcut menu, choose D

IAGNOSTICS

.

3 This action opens the following dialog box. Press [?] to display the Main menu.

If there is no response from the gateway, follow these steps.


February 8, 2017

Page 113 of 150


Protocol Manual



1 Verify that the cables are connected properly between your computer and the gateway. o o

PROFIBUS cable to PROFIBUS port

Null modem cable to Config/Debug port

2 On computers with more than one serial port, verify that your communication program is connected to the same port that is connected to the gateway.

If you are still not able to establish a connection, you can contact ProSoft

Technical Services for assistance.

Navigation

All of the submenus for this gateway contain commands to redisplay the menu or return to the previous menu. You can always return from a submenu to the next higher menu by pressing [M] on your keyboard.

The organization of the menu structure is represented in simplified form in the following illustration:

The remainder of this section shows the menus available for this gateway, and briefly discusses the commands available to you.

Keystrokes

The keyboard commands on these menus are usually not case sensitive. You can enter most commands in lowercase or uppercase letters.

The menus use a few special characters (?, -, +, @) that must be entered exactly as shown. Some of these characters will require you to use the SHIFT, CTRL, or

ALT

keys to enter them correctly. For example, on US English keyboards, enter the ? command as SHIFT and /.

Also, take care to distinguish the different uses for uppercase letter "eye" (I), lowercase letter "el" (

L

), and the number one (1). Likewise, uppercase letter "oh"

(O) and the number zero (0) are not interchangeable. Although these characters look alike on the screen, they perform different actions on the gateway and may not be used interchangeably.


February 8, 2017



4.5.2 Main Menu


Protocol Manual

When you first connect to the gateway’s Ethernet port from your computer, your terminal screen will be blank. To activate the main menu, press the [?] key on your computer’s keyboard. If the gateway is connected properly, the following menu will appear.

Caution: Some of the commands available to you from this menu are designed for advanced debugging and system testing only, and can cause the gateway to stop communicating with the processor or with other devices, resulting in potential data loss or other communication failures.

Use these commands only if you fully understand their potential effects, or if you are specifically directed to do so by ProSoft Technology Technical Support Engineers.

There may be some special command keys that are not listed on the menu but that may activate additional diagnostic or debugging features. If you need these functions, you will be advised how to use them by Technical Support. Please be careful when pressing keys so that you do not accidentally execute an unwanted command.

Redisplaying the Menu

Press [?] to display the current menu. Use this command when you are looking at a screen of data, and want to view the menu choices available to you.

Viewing PROFIBUS Configuration

Press [C] to view the PROFIBUS Configuration screen.

Use this command to display the current configuration and statistics for the gateway.

Viewing PROFIBUS Data

Press [2] to view PROFIBUS data. Use this command to view information related to the status of each slave in the PROFIBUS network, and to verify that each slave is configured (SLAVE CFG LIST), exchanging data with the Master

(TRANSFER LIST) and in diagnostic mode (SLAVE DIAG LIST).

You can also check the gateway's operation state, where:

 00 = Offline

 40 = Stop

 80 = Clear

 C0 = Operate


February 8, 2017

Page 115 of 150


Protocol Manual



Viewing Gateway Status

Press [1] to view status information about the gateway. This screen also contains useful information for mailbox troubleshooting:

 Scan count

 Mailbox counters

 Alarm counters

 Number of acyclic read and write operations performed by the gateway

You can also view the number of mailbox messages in the input and output queues, and the number of alarms in the alarm queue.

Viewing Control Registers

Press [3] to view information about the PROFIBUS Master’s Control Registers.

Use this command to view general information about the gateway, such as the firmware version and its serial number. The gateway status contains two possible codes:

 0400 = gateway is running but not communicating with slaves

 0401 = gateway is running and communicating with slaves

If the gateway is in STOP mode, the status code is displayed as 0400.

Exiting the Program

Press [ESC] to restart the gateway and force all drivers to be loaded. The gateway will use the configuration stored in the gateway's flash memory to configure the gateway.


February 8, 2017



4.6 Standard PROFIBUS Slave Diagnostic Bytes


Protocol Manual

The diagnostic information consists of 6 bytes of standard diagnostic information plus any user-related diagnostic information. The standard information is shown in the tables below.

2

3

4

5

Byte

0

1

Description

Station status 1

Station status 2

Station status 3

Master address

Ident number high

Ident number low

4.6.1 Byte 0 - Station Status 1 Bits

2

3

4

5

6

7

Bit

0

1

Description

Station not existent

Station not ready

Configuration fault

Extended diagnostic data present

Not supported

Invalid slave response

Parameter fault

Master lock


Bit

0

1

2

3

4

5

6

7

Description

Parameter request

Static diagnostic

Slave device

Watchdog on

Freeze mode

Sync mode

Reserved

Slave deactivated


February 8, 2017

Page 117 of 150


Protocol Manual


Bit

0

1

2

3

4

5

6

7

Description

Reserved

Reserved

Reserved

Reserved

Reserved

Reserved

Reserved

Extended diagnostic overflow



4.6.4 Byte 3 - Master Address

This byte shows the address of the assigned PROFIBUS Master after parameterization. If there is an error during the parameterization process, this byte will display the value FF (hexadecimal).

4.6.5 Byte 4 - Ident Number High

This byte shows the high byte of the specific Ident Number assigned to the module by the PROFIBUS User Organization.

4.6.6 Byte 5 - Ident Number Low

This byte shows the low byte of the specific Ident Number assigned to the module by the PROFIBUS User Organization.


February 8, 2017



4.7 Status and Status Mapping


Protocol Manual

23

24

25

26

42

58

74

75

If the Status Data Register parameter is set to any value between 0 and 3900 in the PCB configuration, gateway status data will be placed in the gateway's database, starting at the register specified by the parameter. The status data is organized as follows.

14

16

18

20

22

Byte Offset

Start End

0

10

12

9

11

13

15

17

19

21

22

23

24

25

41

57

73

74

75

Description

Unique gateway 10-byte pattern as text

Reserved

User-configured PROFIBUS input data size stated as a word count

User-configured PROFIBUS output data size stated as a word count

Database starting address for input data

Database starting address for output data

Reserved for future use

User-configured flag to indicate if input data is swapped before placing in the input image for the controller. If 0, no swapping. If not 0, then swap bytes.

User-configured flag to indicate if output data is swapped after receiving from the output image of the controller. If 0, no swapping. If not 0, then swap bytes.

Gateway software major version number.

Gateway software minor version number

Fieldbus data of slave configuration list

Fieldbus data of slave data transfer list

Fieldbus data of slave diagnostic list

Fieldbus pad byte to make data word aligned (not used)

Fieldbus operating state (00h=Offline, 40h=Stop, 80h=Clear & C0h=Operate)

76

77

78

82

83

84

85

76

77

81

82

83

84

85

104

106

108

110

112

114

86

90

94

96

98

100

102


February 8, 2017

105

107

109

111

113

115

89

93

95

97

99

101

103

Fieldbus identification number most significant byte (MSB)

Fieldbus identification number least significant byte (LSB)

Control data gateway serial number

Control data gateway version number MSB

Control data gateway version number LSB

Control data gateway status MSB (00h=App stopped, 04h=App running)

Control data gateway status LSB (bit 0=data exchange, bit 1=slave input frozen/cleared, bit 4=reset)

PROFIBUS configuration CRC32

Gateway configuration CRC32

Gateway program scan counter

Gateway PROFIBUS output image data update counter

Gateway PROFIBUS input image data update counter

Gateway out mailbox counter

Gateway in mailbox counter

Gateway alarm IND receive counter

Gateway alarm CON receive counter

Gateway acyclic read request message counter

Gateway acyclic write request message counter

Reserved

Reserved

Page 119 of 150


Protocol Manual

148

150

152

154

156

134

136

138

140

142

144

146

Byte Offset

Start

116

118

End

117

119

120

122

124

126

128

130

132

121

123

125

127

129

131

133

149

151

153

155

157

135

137

139

141

143

145

147

Description

Reserved

Gateway File Error Word (bitmapped)

Reserved

Reserved

Reserved

Reserved

Reserved

Reserved

Configured response timeout

Reserved

Reserved

Database register for mailbox messaging

Alarm Register for mailbox messaging

Reserved

Status Register

Number of message in the in mailbox queue

Number of message in the out mailbox queue

Number of message in the alarm queue

Reserved

Reserved

Reserved



4.7.1 PDPMV1 Command Status Data Area

Status Register

13100

13101

13102

13103

13104

13105

13106

13107

13108

13109

13110

13111 to 13910

13911 to 13999

Description

Command Count

Command Request Count

Command Response Count

Command Error Count

Number of Request Packets

Number of Response Packets

Errors Sent

Errors Received

Configuration Error Word

Current Error

Last Error

Command List Errors (8 bytes per command for 800-word registers)

Reserved for future use


February 8, 2017



5 Reference

In This Chapter

 PROFIBUS comDTM........................................................................... 122

 RS-232 Configuration/Debug Port ....................................................... 139

 DB9 to Mini-DIN Adaptor (Cable 09) ................................................... 140

 PROFIBUS Master Port....................................................................... 141

 Supported PROFIBUS Services .......................................................... 142

 Constructing a Bus Cable for PROFIBUS DP ..................................... 143

Reference

Protocol Manual


February 8, 2017

Page 121 of 150

Reference

Protocol Manual

5.1 PROFIBUS comDTM



DTM (Device Type Manager) is a standard way to provide all necessary data and functionality for a communication device, for example a PROFIBUS DP card.

This technology is similar to the way Microsoft Windows supports printer drivers supplied by manufacturers and available to any Windows application, rather than requiring a custom printer driver for each specific application.

PROFIBUS comDTM, distributed by ProSoft Technology, is a DTM for PTQ and

MVI series PDPMV1 modules and ProLinx PDPMV1 gateways. Configuration is available through Ethernet for the PTQ and ProLinx series PDPMV1, and through

RS-232 serial for the MVI series PDPMV1 modules. Ethernet configuration is also available through the CIPConnect

®

feature for MVI56-PDPMV1 and

MVI69-PDPMV1 modules (see note).

PROFIBUS comDTM allows configuration tools, instruments, and communication devices on a field network to recognize and use the module's capabilities.

Communication Channels Supported

Serial

Product

MVI46-PDPMV1

MVI56-PDPMV1

MVI69-PDPMV1

PTQ-PDPMV1

ProLinx PDPMV1

Local RS-232 Port

Supported

Supported

Supported

Local Ethernet Port

Supported

Supported

Ethernet

CIPconnect

Supported (see note)

Supported (see note)

Note: MVI56-PDPMV1 requires firmware version 1.28.000 or later to support CIPconnect-enabled

PC programs (1756-ENBT support). The 1756-ENBT card must be located in the same rack as the

MVI56-PDPMV1. Bridging through multiple racks is not supported by the comDTM software.

MVI69-PDPMV1 requires firmware version 1.37.002 or later to support CIPconnect through the

Ethernet port to L32E and L35E CompactLogix processors.

Note: This functionality requires comDTM version 1.0.1.5 with install version 1.01.0003. For information on how to check the comDTM version and install version, refer to Verifying the

comDTM Version and comDTM Install Version (page 133).

5.1.1 ProSoft Technology Product Availability

Part Number

PSW-cDTM-PDPM

Description

PROFIBUS DPV1 Master comDTM software gateway


February 8, 2017



5.1.2 Introduction to PROFIBUS comDTM

Reference

Protocol Manual

Why Use PROFIBUS comDTM?

Customers from around the world have different machines, fieldbusses, and other end-user equipment. Each is equipped with the field bus requested by their end-user. Since there are so many variations, the automation solution in their standard machine ends up being different from case to case.

This means that service engineers need to have different configuration tools for every fieldbus. Or maybe even one for every device. You want one, but the reality is you have many. This is where PROFIBUS comDTM can help with configuring and communicating with different networks, products and suppliers.

What is FDT?

FDT (Field Device Tool) is the specification for software interfaces for the integration of field devices, drives, and controls in engineering and configuration tools. FDT is manufacturer-independent and allows for trouble-free parameterization and configuration of the user's specific processing system.

FDT technology standardizes the communication interface between field devices and systems. The key feature is its independence from the communication protocol and the software environment of either the device or the host system.

FDT allows any device to be accessed from any host through any protocol.

The FDT container implements the FDT specification. It serves as an interface between FDT and a superior application. It uses the DTMs to gain access to the devices. FDT frame application is an engineering or configuration tool which has an FDT container.

FDT technology comprises three key components: the Frame Application, Device

DTMs, and Communication DTMs.

 The DTM (Device Type Manager) is used for the configuration and maintenance of field devices, drives and so on. It is only functional with an

FDT container.

 The FDT container implements the FDT specification. It serves as interface between FDT and a superior application. It uses the DTMs to gain access to devices.

 FDT frame application is an engineering or configuration tool that has an FDT container. The user interface of the DTMs is displayed here.

To better understand the functionality of these components, consider the analogy of the Internet - a standard web browser allows users to view countless web pages created by many content providers. The host system supplier typically creates the Frame Application, just as Microsoft supplies the Internet Explorer web browser. Just as a web browser opens a web page that contains code from the company that makes the web page, an FDT frame opens the Device DTM, which is the plug-in software from the device vendor.


February 8, 2017

Page 123 of 150

Reference

Protocol Manual



Similar to a web browser, the Frame Application has menu bars, toolbars, and a navigation tree. Visually, the frame application sur rounds the device vendor’s

DTM. Like opening a web page from a ‘favorites' navigation tree, a user can navigate down a tree that lists the field device tags, click on one, and open the device vendor’s DTM inside the frame. And, like web pages that let users interact with a reservation system or a shopping service, the Device DTMs let the user interact with the field device in a wide variety of ways. The Device DTM vendor can create a graphically rich user interface that does virtually anything possible in an advanced Windows PC-type interface. The third part of the technology, the

Communication DTM, provides a standardized communication Application

Process Interface (API) inside the PC, interfacing between the Device Vendor’s

DTM and the host system’s specific driver that handles pass-through communications from the PC down to the fieldbus interface card.

The host system vendor supplies a Communication DTM (comDTM) for each supported fieldbus protocol. This ensures that the details of the PC, network, interface cards, and pass-through protocols of the host system, are transparent to the device vendor’s DTM. This correlates back to the internet analogy where: the web page is transparent to the PC it’s running in, the brand of the network interface card in the PC, or whether communication is DSL or broadband cable.

FDT technology complements and expands existing device description languages. It does not replace but rather builds upon existing DDs.

In particular, FDT expands the capabilities of DD for complex devices. Device

Description languages have limitations in the graphical representation of the device at the user interface and allow only a limited integration of special features. FDT/DTM removes these limitations.

Typical frame applications are

 Pactware from The PACTware Consortium e.V (freeware)

 FieldCare from Endress & Hauser

 Field Control from ABB


February 8, 2017



What is DTM?

Reference

Protocol Manual

DTM (Device Type Manager) is a standard way to provide all necessary data and functionality for a communication device, for example a PROFIBUS DP card.

This technology is similar to the way Microsoft Windows supports printer drivers supplied by manufacturers and available to any Windows application, rather than requiring a custom printer driver for each specific application.

PROFIBUS comDTM, distributed by ProSoft Technology, is a DTM for PTQ and

MVI series PDPMV1 modules and ProLinx PDPMV1 gateways. It allows configuration tools, instruments and communication devices on a field network to recognize and use the module’s capabilities.

What is PROFIBUS?

PROFIBUS (Process Field Bus) is a widely-used, open-standards protocol created by a consortium of European factory automation suppliers in 1989.

PROFIBUS is a Master/slave protocol. The Master establishes a connection to the remote slave. When the connection is established, the Master sends the

PROFIBUS commands to the slave.

PROFIBUS supports a variety of network types. The network type supported by the PTQ and MVI series PROFIBUS modules is PROFIBUS DP (Device Bus) version 1.0, which is designed for remote I/O systems, motor control centers, and variable speed drives.


February 8, 2017

Page 125 of 150

Reference

Protocol Manual

5.1.3 System Requirements



Confirm that your system meets the following hardware and software requirements before you start the installation.

Hardware Requirements (Recommended)

 Pentium 4 processor rated for at least 2 GHz

 450 MB hard drive space for DTM Libraries

 Video card capable of 1024 X 768 resolution at 64k colors

 Ethernet Network Interface Card (NIC)

 One of the following ProSoft Technology PROFIBUS DPV1 Master modules: o o o o

ProLinx PDPMV1 Ethernet only, serial port not supported

PTQ-PDPMV1 Ethernet only, serial port not supported

MVI series PDPMV1 RS232 serial

MVI56-PDPMV1 (with 1756-ENBT for Ethernet support)

Note for PTQ Users: The Ethernet connection implements UDP protocol, which dynamically allocates a random UDP port for every connection. This implementation limits the possibility of using most serial to Ethernet converters to access the PDPMV1 serial port through an Ethernet connection. Several Ethernet to serial converters require the configuration of a fixed UDP port, which is not available for the current implementation.

Software Requirements (Minimum)

 Windows NT 4.0 Service Pack 6A, Windows 2000 SP3 or Windows XP

Professional SP2, or better

 Microsoft Internet Explorer Version 6.0, or better

 FDT 1.2.1 compliant FDT frame application. Compatible applications include: o o o

PACTware

FieldCare

M&M fdtCONTAINER

Some FDT Containers require the following components:

 Microsoft Management Console

 Adobe Acrobat Reader 5.0, or better


February 8, 2017



5.1.4 Installation

Reference

Protocol Manual

Important: You must have Administrator rights on your computer to install this application.

Important: Please open and read the Readme file before starting the installation. The Readme file is located in Utilities > comDTM > Readme on the ProSoft Solutions Product CD-ROM.

To install comDTM

1 Insert the ProSoft Solutions Product CD-ROM in an available CD-ROM drive in your computer. Wait for the startup screen to appear.

2 On the startup screen, click P

RODUCT

D

OCUMENTATION

. This action opens a

Windows Explorer file tree window.

3 Double-click to open the U

TILITIES

folder, then navigate to

COM

DTM >

COM

DTM I

NSTALL

.

4 Double-click the

SETUP

.

EXE

file. This action starts the installation wizard.

5 Follow the instructions on the installation wizard to install the program.

6 Click F

INISH

to complete the installation. If you are prompted to restart your computer, save your work in any applications that are running, close the applications, and allow the computer to restart.

Note: During installation, you will be prompted to accept or change the location for the database folder. The default location for this folder is the Program Files directory on your local hard drive

(normally Drive C:). If you intend to allow multiple workstations to access the same database folder, you should choose a network drive that other workstations can access.


February 8, 2017

Page 127 of 150

Reference

Protocol Manual

5.1.5 Quick Start



The following steps demonstrate how to start the FDT (Field Device Tool) program and configure the PROFIBUS comDTM.

Starting FDT

1 Start the FDT program and login as administrator. The following procedures use PACTware 3.0 software.

2 Click the U

PDATE DEVICE CATALOG

button. If PROFIBUS comDTM was installed successfully, it will appear in the Device Catalog window.

3 Select the P

RO

S

OFT

T

ECHNOLOGY COM

DTM entry in the device catalog, and then click A

DD

.

4 Repeat steps 1 through

3 to add any other manufacturer’s device DTMs installed on your computer. Select the correct address for each device, and then click OK to proceed.

Note: You must use the same PROFIBUS device address that you used when setting up the device.


February 8, 2017



Reference

Protocol Manual

Connecting the comDTM to the Master to Establish Communication

Note: The features described in this section require the current version of PROFIBUS comDTM.

You can always download the newest version from www.prosoft-technology.com.

1 From the Windows S

TART

button, navigate to P

ROGRAMS

> P

RO

S

OFT

T

ECHNOLOGY

, and then choose P

RO

S

OFT

T

RANSPORT

P

ATH

E

DITOR

.

2 If you have not created a communication path, click the A

DD

button. If you have already created a path, skip to step 5.

3 For PTQ-PDPMV1 and ProLinx-PDPMV1 users: Select the E

THERNET

tab, and enter the IP Address of the module or gateway. Enter a descriptive path name.

Note: Do not include the underscore ( _ ) for the path name.


February 8, 2017

Page 129 of 150

Reference

Protocol Manual



For MVI-PDPMV1 users: Select the S

ERIAL

tab and enter the COM port number on your PC connected to the module. Enter a descriptive path name.

For MVI56-PDPMV1 and MVI69-PDPMV1 users with CIPconnect: Select the

CIP

CONNECT

tab, and then click the A

DD

button.

Click the CIP

CONNECT

P

ATH

E

DIT

button to define the path for this application.


February 8, 2017



The CIPconnect Path Editor allows the configuration of the path between your PC and the MVI56-PDPMV1 or MVI69-PDPMV1 module.

For the following example, the PC will be connected through Ethernet to a

1756-ENBT communication card (IP=192.168.0.100) and the MVI56-

PDPMV1 card is located in slot 3 of the same rack.

Reference

Protocol Manual

For more information, please refer to Using the CIPconnect Path Editor.

Note: CIPconnect is available for MVI56-PDPMV1 firmware version 1.28.000 (or later) and for

MVI69-PDPMV1 firmware version 1.37.002 (or later). This functionality requires comDTM version

1.0.1.5 with install version 1.01.0003 (or later). For information on how to check the comDTM version and install version, refer to Verifying the comDTM Version and comDTM Install Version

(page 133).

4 When you have configured the communication path, click the OK button to confirm. The communication path will be displayed at the top grid panel as shown in the following illustration.


February 8, 2017

Reference

Protocol Manual



5 Select the path and click the OK button to exit the Transport Path Editor window.

6 Select the

COM

DTM icon and click the right mouse button to open a shortcut menu. On the shortcut menu, choose C

ONNECT

. If the connection is successful, the icon will be highlighted, as shown in the following illustration.

When the comDTM is connected with the Master, PACTware indicates the connection Master by displaying a green plug in the status bar.

This completes the installation and Quick Start Guide for the ProSoft Technology

PROFIBUS comDTM. Refer to the online help and documentation additional information on each DTM component you have installed and configured.

The comDTM provides a Guided Tour section in the online help that explains the basic features and operation of the program. To open the online help, click the right mouse button on P

RO

S

OFT

T

ECHNOLOGY COM

DTM, and choose A

DDITIONAL

F

UNCTIONS

> O

NLINE

H

ELP

from the shortcut menu.


February 8, 2017



Click the G

UIDED

T

OUR

icon. Use the navigation buttons on each help page to view the help topics.

Reference

Protocol Manual

Refer to the documentation and online help for your FDT frame program for specific FDT frame instructions.

5.1.6 Verifying the comDTM Version and comDTM Install Version

Introduction

There are two versions associated to the comDTM

– the comDTM version and the comDTM install version. Starting with comDTM version 1.0.1.5, each upgrade will indicate the same comDTM version but a different comDTM install version.

This section describes how to check the comDTM version and comDTM install version.


February 8, 2017

Page 133 of 150

Reference

Protocol Manual



Checking the comDTM Version

Refer to the Version column indicated when you add the comDTM to the DTM

Container project.

Checking the comDTM Install Version

1 Click the S

TART

menu and then choose C

ONTROL

P

ANEL

.


February 8, 2017



2 In the list of C

ONTROL

P

ANEL

applets, select A

DD OR

R

EMOVE

P

ROGRAMS

.

Reference

Protocol Manual

3 Select P

RO

S

OFT

T

ECHNOLOGY

COM-DTM, and then click on the link C

LICK

HERE FOR SUPPORT INFORMATION

.


February 8, 2017

Reference

Protocol Manual



4 You will see the comDTM Install Version in the Version field, as shown in the following illustration (1.01.0003 for this example).

Checking the Install Version for Vista

1 Select C

ONTROL

P

ANEL

.


February 8, 2017



2 Select U

NINSTALL

P

ROGRAMS

.

Reference

Protocol Manual

3 Select Prosoft Technology COM-DTM (click once)


February 8, 2017

Reference

Protocol Manual

4 Click the O

RGANIZE

tab and select L

AYOUT

> D

ETAILS

P

ANE

.



5 Check the Install Version at the bottom right portion of the window.


February 8, 2017



5.2 RS-232 Configuration/Debug Port

Reference

Protocol Manual

This port is physically an eight-pin, Mini-DIN8F connection. A Mini-DIN8M to

DB9M adapter cable is included with the gateway. This port permits a PC-based terminal emulation program to view configuration and status data in the gateway and to control the gateway. Here are the cable pinouts for RS-232 communication on this port.


February 8, 2017

Page 139 of 150

Reference

Protocol Manual

5.3 DB9 to Mini-DIN Adaptor (Cable 09)




February 8, 2017



5.4 PROFIBUS Master Port

Reference

Protocol Manual

The following diagram has been imported from the PROFIBUS Master documentation. Note that the signals to reference are the D-Sub signals in the table.


February 8, 2017

Page 141 of 150

Reference

Protocol Manual

5.5 Supported PROFIBUS Services



The following table lists all available services according to the PROFIBUS specification.

Service

DDLM_Data-Exchange

DDLM_Set_Prm

DDLM_Chk_cfg

DDLM Slave Diag

DDLM_Global_Control

DDLM_Get_Cfg

DDLM_Set_Slave_Add

DDLM_Read_Input

DDLM_Read_Output

DDLM_Get_Master_Diag

DDLM_Start_Seq

DDLM_Download

DDLM_Upload

DDLM_End_Seq

DDLM_Act_Param_Brct

DDLM_Act_Param

MSAC1_Read

MSAC1_Write

MSAL1_Alarm

MSAL1_Alarm_Ack

MSAC2_Initiate

MSAC2_Read

MSAC2_Write

MSAC2_DataTransport

MSAC2_Abort

Data_eXchange_Broadcast

Isochrone_mode (Takt sync)

Extended_Set_Prm (Subscriber)

PROFIBUS

Version

DP-V1

DP-V1

DP-V1

DP-V2

DP-V2

DP-V2

DP-V0

DP-V0

DP-V1

DP-V1

DP-V1

DP-V1

DP-V1

DP-V1

DP-V0

DP-V0

DP-V0

DP-V0

DP-V0

DP-V0

DP-V0

DP-V0

DP-V0

DP-V0

DP-V0

DP-V0

DP-V0

DP-V0

No

No

No

Yes

Yes

Master Class 1

Request Response

Yes

Yes

Yes

Yes

Yes

No

No

Yes

No

No

No

No

Yes

Yes

No

No

No

No

No

No

No

No

No

No

No

Yes

Yes

No

No

No

No

No

No

Master Class 2

Request Response

No


February 8, 2017



5.6 Constructing a Bus Cable for PROFIBUS DP

Reference

Protocol Manual

The bus cable for connecting PROFIBUS DP devices must be constructed by the user. A special PROFIBUS cable (twisted pair) is required here. This standard cable is available from various manufacturers and is a Belden part number

3079A.

If you plan to construct your own bus cable, the following part numbers are provided for your convenience.

 PROFIBUS connector: Siemens part number 6ES7972-0BA40-0XA0

 PROFIBUS cable: Belden part number 3079A.

To construct the cable, proceed as follows:

1 Cut the cable to the required length.

2 Prepare the cable ends as shown in the illustration (dimensions in mm):

J PVC Jacket

S Braided shielding

3 Remove the PVC jacket J to the indicated length.

4 Wrap the provided copper shielding F around the shield braiding S:

J PVC jacket

S Braided shielding

F Copper foil shielding

Additional foil can be obtained from 3M.

5 Plug the leads of the corresponding cable(s) into the terminals as shown: o o

Green leads in terminal A

Red lead in terminal B

Note: Do not tighten the corresponding screws yet.


February 8, 2017

Page 143 of 150

Reference

Protocol Manual

Connection terminal assignment on the PROFIBUS DP:



A Incoming cable

B Outgoing cable

C Connection terminals (only once (B,A))

D Cable cleat for reliving tension

E Bus connector screws

6 Attach the cables with the provided cable cleat to create a robust shielded connection and to relieve any tension as shown:

J PVC Jacket

S Braided shielding with foil shielding

C Cable cleat

Note: Half of the cable jacket must lie under the cable cleat!

Pay attention to the cable cleat installation instructions.

7 Fasten the individual wires of the PROFIBUS cable to the terminals


February 8, 2017



8 Close the connector housing.

Note: The shielding of both cables is connected internally with the metal housing of the connector.

Reference

Protocol Manual

9 Complete the Central Shielding Measures (below) and grounding operations for the shielding before you connect the cable connector to the gateway.

10 Plug the PROFIBUS DP connector into the gateway and secure it with the screws.

Bus Begin and Bus End

The PROFIBUS connector with termination is required at the beginning and the end of the bus. These connectors emulate the line impedance.

It is recommended that at least one connector with diagnostics interface is used.

Wiring diagram for a PROFIBUS DP cable

Grounding and Shielding for Systems with Equipotential Bonding

Each cable shield should be galvanically grounded with the earth using FE/PE grounding clamps immediately after the cable has been connected to the cabinet.

This example indicates the shielding connection from the PROFIBUS cable to the

FE/PE rail.

Note: An equalization current can flow across a shield connected at both ends because of fluctuations in ground potential. To prevent this, it is imperative that there is potential equalization between all the attached installation components and devices.


February 8, 2017

Page 145 of 150

Reference

Protocol Manual



This example indicates the system components and devices in a system with equipotential bonding.

Grounding and Shielding for Systems without Equipotential Bonding

Note: Grounding and shielding is to be carried out the same as for systems with equipotential bonding.

If this is not possible because of system or construction specific reasons however, use distributed ground with a capacitive coupling of high frequency interference signals.

This representation shows distributed grounding with capacitive coupling.


February 8, 2017



Support, Service & Warranty

Protocol Manual

6 Support, Service & Warranty

In This Chapter

 Contacting Technical Support ............................................................. 147

 Warranty Information ........................................................................... 148

6.1 Contacting Technical Support

ProSoft Technology, Inc. is committed to providing the most efficient and effective support possible. Before calling, please gather the following information to assist in expediting this process:

1 Product Version Number

2 System architecture

3 Network details

If the issue is hardware related, we will also need information regarding:

1 Module configuration and associated ladder files, if any

2 Module operation and any unusual behavior

3 Configuration/Debug status information

4 LED patterns

5 Details about the serial, Ethernet or Fieldbus devices interfaced to the module, if any.

Note: For technical support calls within the United States, ProSoft’s 24/7 after-hours phone support

is available for urgent plant-down issues. Detailed contact information for all our worldwide

locations is available on the following page.


February 8, 2017

Page 147 of 150

Support, Service & Warranty

Protocol Manual

Internet

Asia Pacific

(location in Malaysia)

Asia Pacific

(location in China)

Web Site: www.prosoft-technology.com/support

E-mail address: [email protected]

Tel: +603.7724.2080

E-mail: [email protected]

Languages spoken include: Chinese, English

Tel: +86.21.5187.7337 x888


Languages spoken include: Chinese, English

Europe

(location in Toulouse,

France)

Europe

(location in Dubai, UAE)

North America

(location in California)

Tel: +33 (0) 5.34.36.87.20


Languages spoken include: French, English

Tel: +971-4-214-6911


Languages spoken include: English, Hindi

Tel: +1.661.716.5100


Languages spoken include: English, Spanish

Latin America

(Oficina Regional)

Latin America

(location in Puebla, Mexico)

Tel: +52-222-3-99-6565


Languages spoken include: Spanish

Brasil

(location in Sao Paulo)

Tel: +1-281-2989109

E-Mail: [email protected]

Languages spoken include: Spanish, English

Tel: +55-11-5083-3776


Languages spoken include: Portuguese, English



6.2 Warranty Information

For complete details regarding ProSoft Technology’s TERMS & CONDITIONS

OF SALE, WARRANTY, SUPPORT, SERVICE AND RETURN MATERIAL

AUTHORIZATION INSTRUCTIONS, go to www.prosoft-technology.com/legal

Documentation is subject to change without notice.


February 8, 2017



Index

2

23 - Get Database Information • 50

3

3 - Set Slave Mode • 49

32 - Acyclic Read • 50

33 - Acyclic Write • 51

4

4 - Get Slave Diagnostic Data • 49

5

5 - Get Slave Configuration • 50

A

About the PROFIBUS Protocol • 10

Acyclic Message Status Word • 81, 84, 87, 91, 93, 94,

100

Adding a Location to an Existing Project File • 19

Adding a Module • 20

Adding a Project to an Existing Project File • 19

Alarm Register • 29

B

Backing Up the Project • 72

Basic Troubleshooting Steps • 107

Bus Access • 12

Byte 0 - Station Status 1 Bits • 117



Byte 3 - Master Address • 118

Byte 4 - Ident Number High • 118

Byte 5 - Ident Number Low • 118

C

Checking the comDTM Install Version • 134

Checking the comDTM Version • 134

Checking the Install Version for Vista • 136

Command Error Codes • 104

Command Layout for Get Live List • 40

Command Layout for Set Operating Mode • 35

Command Layout for Start/Stop Slaves • 45

Communication Types • 14

Compatibility Note • 11

Configuration • 17

Configuring Gateway Parameters • 21

Configuring the Gateway • 18

Configuring the PROFIBUS DP Network • 18, 52

Configuring the PROFIBUS Slaves • 53, 70


February 8, 2017

Index

Protocol Manual

Connecting the comDTM to the Master to Establish

Communication • 129

Constructing a Bus Cable for PROFIBUS DP • 143

Contacting Technical Support • 147

Creating Optional Comment Entries • 21

D

DB9 to Mini-DIN Adaptor (Cable 09) • 140

Diagnostics and Troubleshooting • 105

Downloading the Project to the Gateway • 18, 71

DP-V1 Error Codes • 103

E

Error Codes • 101, 102, 104

Example Mailbox Commands • 33

Examples • 109

Exiting the Program • 116

F

Functional Overview • 9

G

Gateway Internal Database • 16

Get Live List • 38

H

Hardware Requirements (Recommended) • 126

How Cable Length Affects Communication Rate • 12

How to Contact Us • 2

I

Important Installation Instructions • 3

Input Byte Swap • 27

Input Data Size • 26

Input Start Register • 26

Installation • 127

Installing ProSoft Configuration Builder Software • 18

Installing the GSD Files • 52, 53

Introduction • 133

Introduction to PROFIBUS comDTM • 123

K

Keystrokes • 114

M

Mailbox Message

Acyclic Data Read

Class 1 • 92

Acyclic Data Write

Class 1 • 94

Get Database Information • 87

Get Live List • 90

Get Slave Configuration • 86

Get Slave Diagnostics • 83

Set Operating Mode • 78

Set Slave Mode • 49, 80

Start Slave • 48, 96

Page 149 of 150

Index

Protocol Manual

Stop Slave • 48, 97

Mailbox Message Queuing • 76

Mailbox Messaging • 28, 75

Mailbox Messaging Error Codes • 85, 87, 100

Mailbox Register • 28

Main Menu • 115

Master/Slave Communication Phases • 15

Master/Slave Polling • 13

Minimum Command Delay • 29

N

Navigation • 114

O

Other Mailbox Commands • 49

Output Byte Swap • 27

Output Data Size • 26

Output Start Register • 26

P

PDPMV1 Command Status Data Area • 120

Pinouts • 3, 140, 143

Printing a Configuration File • 21

Printing the ProLinx Memory Map • 69

PROFIBUS comDTM • 122

PROFIBUS DP Architecture • 12

PROFIBUS DP-V1 (PDPMV1 Driver) Master LED

Indicators • 108

PROFIBUS Master Commands • 31

PROFIBUS Master DPV1 • 26

PROFIBUS Master Indicators • 108

PROFIBUS Master Port • 141

ProLinx Gateways with Ethernet Ports • 3

ProLinx® Products Warnings • 3

ProSoft Technology Product Availability • 122

ProSoft Technology® Product Documentation • 2

Q

Queue Timeouts • 76

Quick Start • 128

R

Redisplaying the Menu • 115

Reference • 121

Required Hardware • 106

Response Timeout • 29

Return Codes • 79, 85, 87, 90, 93, 95, 101

RS-232 Configuration/Debug Port • 139

S

Scanning for Slaves Manually • 53

Set Operating Mode • 33

Set_Param (SAP61) • 67

Setting Gateway Parameters • 18, 24

Setting Up the Project • 18, 22

Slave Diagnostics Register • 29

Software Requirements (Minimum) • 126

Page 150 of 150



Special Function Mailbox Messaging Commands • 77

Standard PROFIBUS Slave Diagnostic Bytes • 117

Start/Stop Slaves • 43

Starting FDT • 128

Status and Status Mapping • 119

Status Data Register • 29

Support, Service & Warranty • 147

Supported PROFIBUS Services • 142

System Requirements • 126

T

To upgrade a previously purchased Series C model • 3

Token Passing • 13

U

Using ProSoft Configuration Builder (PCB) for

Diagnostics • 112

Using The Autoscan Feature • 58

Using the Diagnostic Window in ProSoft Configuration

Builder - PLX • 112

Using the Online Help • 19

V

Verifying the comDTM Version and comDTM Install

Version • 122, 131, 133

Viewing Control Registers • 116

Viewing Gateway Status • 116

Viewing PROFIBUS Configuration • 115

Viewing PROFIBUS Data • 115

Viewing the Online Status of the PROFIBUS Network •

110

W

Warranty Information • 148

Watchdog Register • 29

Watchdog Reset Value • 30

Watchdog Timeout • 30

What is DTM? • 125

What is FDT? • 123

What is PROFIBUS? • 125

Why Use PROFIBUS comDTM? • 123

Your Feedback Please • 2

Y


February 8, 2017

No results