ProSoft Technology ILX69-PBM - Manual (Page 82)

Contents ILX69-PBM ♦ CompactLogix or MicroLogix Platform
User Manual PROFIBUS Master Communication Module
Page 82 of 124 ProSoft Technology, Inc.
February 4, 2015
6.3 Acyclic Messaging
PROFIBUS DP acyclic services are supported by the Studio 5000 programming tool by
means of CIP messages using the "MSG" instruction. The ILX69-PBM sample ladder and
AOI include multiple PROFIBUS acyclic services such as read/write and slave diagnostic
request.
6.3.1 Supported PROFIBUS DP Messages
Below are the PROFIBUS DP message functions supported by the ILX69-PBM.
Service Cmd
Code Group Description
ILX69PBM_MSGDPV1Alarm 18 DPV1 Provides the means to acknowledge an alarm
indication originating from a slave
ILX69PBM_MSGDPV1Read 17 DPV1 A read request for a particular data block is sent to a
slave. This service is Slot- and Index-referenced.
ILX69PBM_MSGDPV1Write 17 DPV1 A write request is transferred to a slave, to write a
particular data block in the slave. This service is
Slot- and Index-referenced.
ILX69PBM_MSGSlaveControl 70 Standard Sending a command to one or several slaves
ILX69PBM_MSGSlaveDiagRequest 66 Standard Reading the diagnostics information from a slave
6.3.2 Standard Messaging
This section contains the description of each Standard Message function supported by the
ILX69-PBM. The CIP MSG setup of this request is as follows.
Parameter Value Description
Message Type CIP Generic Common Industrial Protocol (CIP) messaging
Service Type Custom -
Service Code 64 hex Service Code "Bridge Message"
Class 65 hex CIP Object "CIP_MSG_BRIDGE"
Instance 1 An integer identification value assigned to an object instance that
identifies it among all instances of the same class.
Attribute 0
A way of specifying a particular property or value within a CIP Object.
Source Element - Reference to a Tag of type
ILX69PBM.CONTROL.SlaveDiagnostic.GetSlaveDiag
Destination - Reference to a Tag of type SlaveDiagnostic.GetSlaveDiag.Response
Source Length 16 Corresponds to the size of the ILX69PBM_MSGSlaveDiagRequest
structure