ISO 15745-5:2007

INTERNATIONAL ISO
STANDARD 15745-5
First edition
2007-02-01

Industrial automation systems and
integration — Open systems application
integration framework —
Part 5:
Reference description for HDLC-based
control systems
Systèmes d'automatisation industrielle et intégration — Cadres
d'intégration d'application pour les systèmes ouverts —
Partie 5: Description de référence pour les systèmes de contrôle fondés
sur HDLC



Reference number
ISO 15745-5:2007(E)
©
ISO 2007

---------------------- Page: 1 ----------------------
ISO 15745-5:2007(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.


©  ISO 2007
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland

ii © ISO 2007 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 15745-5:2007(E)
Contents Page
Foreword .iv
Introduction.v
1 Scope.1
2 Normative references.1
3 Terms and definitions.1
4 Abbreviated terms.2
5 Technology specific elements and rules .2
5.1 Integration models and IAS interfaces.2
5.2 Profile templates.2
5.3 Technology specific profiles.3
6 Device and communication network profiles for HDLC-based control systems .3
6.1 General.3
6.2 CC-Link.4

Annex A (normative) CC-Link profile templates .16

Annex B (informative) UML terminology and notation .87
Bibliography.88

© ISO 2007 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 15745-5:2007(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 15745-5 was prepared by Technical Committee ISO/TC 184, Industrial automation systems and
integration, Subcommittee SC 5, Architecture, communications and integration frameworks.
ISO 15745 consists of the following parts under the title Industrial automation systems and integration — Open
systems application integration framework
⎯ Part 1: Generic reference description
⎯ Part 2: Reference description for ISO 11898-based control systems
⎯ Part 3: Reference description for IEC 61158-based control systems
⎯ Part 4: Reference description for Ethernet-based control systems
⎯ Part 5: Reference description for HDLC-based control systems
iv © ISO 2007 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 15745-5:2007(E)
Introduction
The application integration framework (AIF) described in ISO 15745 defines elements and rules that facilitate:
⎯ the systematic organization and representation of the application integration requirements using
integration models;
⎯ the development of interface specifications in the form of application interoperability profiles (AIPs) that
enable both the selection of suitable resources and the documentation of the "as built" application.
ISO 15745-1 defines the generic elements and rules for describing integration models and AIPs, together
with their component profiles - process profiles, information exchange profiles, and resource profiles. The
context of ISO 15745 and a structural overview of the constituents of an AIP are given in Figure 1 of
ISO 15745-1:2003.
This part of ISO 15745 extends the generic AIF described in ISO 15745-1 by defining the technology specific
elements and rules for describing both communication network profiles and the communication related
1) 2)
aspects of device profiles specific to HDLC -based control systems (CC-Link ). CC-Link is based on HDLC
technology.
In particular, this part of ISO 15745 describes technology specific profile templates for the device profile and
the communication network profile. Within an AIP, a device profile instance or a communication network
profile instance is part of the resource profile defined in ISO 15745-1. The device profile and the
communication network profile XML instance files are included in a resource profile XML instance using the
ProfileHandle_DataType as specified in ISO 15745-1:2003, 7.2.5.
AIFs specified using the elements and rules of ISO 15745-1 can be easily integrated with the component
profiles defined using the elements and rules specified in this part of ISO 15745.

1)
HDLC is used in this document as a synonym for ISO/IEC 13239.
2)
CC-Link is the trade name of the CC-Link Partner Association (CLPA). This information is given for the convenience of
users of ISO 15745 and does not constitute an endorsement by ISO of the trade name holder or any of its products.
Compliance to this part of ISO 15745 does not require use of the trade name CC-Link. Use of the trade name CC-Link

requires permission of the CLPA.
© ISO 2007 – All rights reserved v

---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 15745-5:2007(E)

Industrial automation systems and integration — Open systems
application integration framework — Part 5: Reference
description for HDLC-based control systems
1 Scope
This part of ISO 15745 defines the technology specific elements and rules for describing both communication
network profiles and the communication related aspects of device profiles specific to HDLC-based control
systems.
NOTE Generic elements and rules for describing integration models and application interoperability profiles, together
with their component profiles (process profiles, information exchange profiles, and resource profiles) are specified in ISO
15745-1.
This part of ISO 15745 is to be used in conjunction with ISO 15745-1 to describe an application integration
framework.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 15745-1:2003, Industrial automation systems and integration – Open systems application integration
framework – Part 1: Generic reference description
ISO/IEC 13239, Information technology – Telecommunications and information exchange between systems –
High-level data link control (HDLC) procedures
REC-xml-20040204, Extensible Markup Language (XML) 1.0 Third Edition – W3C Recommendation 04
February 2004
REC-xmlschema-1-20010502, XML Schema Part 1: Structures – W3C Recommendation 02 May 2001
REC-xmlschema-2-20010502, XML Schema Part 2: Datatypes – W3C Recommendation 02 May 2001
UML V1.4, OMG - Unified Modeling Language Specification (Version 1.4, September 2001)
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 15745-1 apply.
NOTE The UML terminology and notation used in this part of ISO 15745 is described in Annex A of ISO 15745-1:2003
and Annex B of this part of ISO 15745.
© ISO 2007 – All rights reserved 1

---------------------- Page: 6 ----------------------
ISO 15745-5:2007(E)
4 Abbreviated terms
AIF Application Integration Framework
AIP Application Interoperability Profile
ASCII American Standard Code for Information Interchange
CSP CC-Link System Profile (see BAP-05028)
HDLC High-level Data Link Control (see ISO/IEC 13239)
IAS Industrial Automation Systems
I/O Input and Output
LT CC-Link/LT
OSI Open System Interconnection
RWr Remote register for read
RWw Remote register for write
RX Remote input
RY Remote output
SEMI Semiconductor Equipment and Materials International (in this context refer to SEMI standard,
SEMI E54.12-0701)
UML Unified Modeling Language (see UML V1.4)
XML eXtensible Markup Language (see REC-xml-20040204)
5 Technology specific elements and rules
5.1 Integration models and IAS interfaces
The AIP developer shall develop the integration model using the rules described in ISO 15745-1, and shall
ensure that the HDLC-based device and communication network profiles (whether representing the interface
requirements or those derived from existing devices/communication networks) include the necessary IAS
interfaces. The IAS interfaces included in the profile shall be identified in the header section (see ISO 15745-
1:2003, 7.2.2).
NOTE IAS interfaces are described in ISO 15745-1:2003, Annex B.
5.2 Profile templates
5.2.1 General
The HDLC-based technology specific profile templates are derived from the generic profile templates specified
in ISO 15745-1:2003, clause 7.
2 © ISO 2007 – All rights reserved

---------------------- Page: 7 ----------------------
ISO 15745-5:2007(E)
5.2.2 Contents and syntax
ISO 15745 specifies profile templates that are XML schemas (REC-xmlschema-1-20010502 and REC-
xmlschema-2-20010502) and use a common general structure. The device and communication network
profiles based on these templates typically contain:
⎯ information needed to identify the connected device,
⎯ a description of device data that can be accessed via the network,
⎯ a description of the communication capabilities supported by the device,
⎯ additional vendor-specific information.
However, CC-Link technology uses specific legacy ASCII syntax. Hence, for backward compatibility, template
definitions (see Annex A) include the following:
⎯ communication network and device profile templates, as defined in ISO 15745-1,
⎯ ISO 15745 template to encapsulate files with legacy ASCII syntax ("wrapper").
5.2.3 Header
The profile template header defined in ISO 15745-1:2003, 7.2.2, is used for HDLC-based technology specific
profile templates. Each technology uses one or more names to identify the technology or its particular
component(s) (see Table 1). The selected name shall be stored in the ProfileTechnology attribute in the
header section.
Table 1 — ProfileTechnology names
ProfileTechnology name Technology
CC-Link CC-Link
CSP CC-Link

5.3 Technology specific profiles
The technology specific communication network profile structure and communication related aspects of device
profile structure based on HDLC technology are described in clause 6. The technology included is CC-Link
(see 6.2).
The related profile template definitions are specified in Annex A.
6 Device and communication network profiles for HDLC-based control systems
6.1 General
The CC-Link technology specific device and communication network profiles are described in 6.2.
© ISO 2007 – All rights reserved 3

---------------------- Page: 8 ----------------------
ISO 15745-5:2007(E)
6.2 CC-Link
6.2.1 Device profile
6.2.1.1 General
Figure 1 shows the class structure of the CC-Link device profile.
DeviceProfile
0.*
ApplicationProcess
1
DeviceIdentity
1
DeviceManager
1.*
DeviceFunction

Figure 1 — CC-Link device profile class diagram
The DeviceProfile class of any version of CC-Link except version LT may include the ApplicationProcess class.
The DeviceProfile class of CC-Link version LT shall not include the ApplicationProcess class.
The available formats for CC-Link device profiles are described in A.2.
The XML schema representing the CC-Link device profiles template is defined in A.2.1.3. The file name of this
XML schema shall be “CC-Link_DeviceProfile.xsd”.
The XML schema representing the encapsulation of a CC-Link CSP into the ISO 15745 device profile
template is defined in A.2.2.2. The file name of this XML schema shall be “CSP_DeviceProfile_wrapper.xsd”.
The legacy CSP ASCII syntax itself is described in A.4.
6.2.1.2 Device identity
Figure 2 shows the class structure of the DeviceIdentity class.
DeviceIdentity
1
DevVer
1
CcLinkVer
0.1
StationNumber
1
VendName
1
StationType
1
VendID
0.1
RemDevType
1
DevModel

Figure 2 — CC-Link DeviceIdentity class diagram
The DeviceIdentity class shall consist of the child classes shown in Figure 2 and specified in Table 2. Child
classes of DeviceIdentity class apply to profile, type, and instance.
4 © ISO 2007 – All rights reserved

---------------------- Page: 9 ----------------------
ISO 15745-5:2007(E)
Table 2 — Child classes of DeviceIdentity class
Class Description
CcLinkVer CC-Link version used by the device
VendName vendor name
VendID vendor code
DevModel model name
DevVer version number
StationNumber Identifier of the device
StationType type code for slave station
RemDevType type code for remote device station

6.2.1.3 Device manager
6.2.1.3.1 General
Figure 3 shows the structure of the DeviceManager class.
DeviceManager
1
Mode
1
NumOccupiedStations
0.1
TotalIO
0.1
ExtendedCycleConf
0.1
IOType
0.1
BmpFile
0.1
SEMISupport
0.1
ErrReg
0.1
LEDList
0.1
UpDownLoadF
1.*
LED
0.1
MasterFlg

Figure 3 — CC-Link DeviceManager class diagram
The DeviceManager class consists of the child classes shown in Figure 3 and Table 3.
© ISO 2007 – All rights reserved 5

---------------------- Page: 10 ----------------------
ISO 15745-5:2007(E)
Table 3 — Child classes of DeviceManager class
Class Version 1.00 / 1.10 Version 1.11 Version 2.00 Version LT
NumOccupiedStations Mandatory Mandatory Mandatory Mandatory
ExtendedCycleConf Not applicable Not applicable Optional Not applicable
BmpFile Mandatory Mandatory Mandatory Not applicable
ErrReg Optional Optional Optional Not applicable
UpDownLoadF Mandatory Mandatory Mandatory Not applicable
MasterFlg Optional Optional Optional Not applicable
Mode Mandatory Mandatory Mandatory Mandatory
TotalIO Optional Optional Optional Optional
IOType Optional Optional Optional Optional
SEMISupport Not applicable Optional Optional Not applicable
LEDList Optional Optional Optional Optional
NOTE The four right hand columns indicate whether a certain child class is mandatory,
optional, or not applicable for a device profile of a specified CC-Link version.

6.2.1.3.2 NumOccupiedStations
NumOccupiedStations is the number of occupied stations.
6.2.1.3.3 ExtendedCycleConf
ExtendedCycleConf is the extension level of an amount of I/O points used in the extended cyclic
communication.
6.2.1.3.4 BmpFile
BmpFile is the name of the associated bitmap file.
6.2.1.3.5 ErrReg
ErrReg is a register used to store an error code.
6.2.1.3.6 UpDownLoadF
UpDownLoadF indicates whether an upload and download is applicable or not.
6.2.1.3.7 MasterFlg
MasterFlg indicates whether the device can be a standby master or not.
6.2.1.3.8 Mode
Mode indicates supporting operation modes (see Table A.3).
6.2.1.3.9 TotalIO
TotalIO is the total number of I/O points (see Table A.4).
6 © ISO 2007 – All rights reserved

---------------------- Page: 11 ----------------------
ISO 15745-5:2007(E)
6.2.1.3.10 IOType
IOType is the type of I/O (see Table A.5).
6.2.1.3.11 SEMISupport
SEMISupport indicates whether the SEMI standard function is supported or not.
6.2.1.3.12 LEDList, LED
The LEDList is a listing of available LEDs. The LED describes the name and the possible state of the LED on
the device (see Table A.6).
6.2.1.4 Device function
Figure 4 shows the structure of the DeviceFunction class.
DeviceFunction
DevFuncData
0.1

Figure 4 — CC-Link DeviceFunction class diagram
NOTE The definition of the DevFuncData of the DeviceFunction is outside the scope of this part of ISO 15745.
6.2.1.5 Application process
6.2.1.5.1 General
Figure 5 shows the class structure of the ApplicationProcess class.
ApplicationProcess
0.1
0.1
RemoteIOMemoryMap {XOR} RemoteDeviceMemoryMap
0.*
SelectPrm
2
0.2
IO_Info_R
0.*
PrmSet
2
IO_Info_RW
0.*
GrpItem
0.2
IO_RW_Bit
0.1
Method
0.*
CmdPtrn

Figure 5 — CC-Link ApplicationProcess class diagram
© ISO 2007 – All rights reserved 7

---------------------- Page: 12 ----------------------
ISO 15745-5:2007(E)
6.2.1.5.2 RemoteIOMemoryMap
6.2.1.5.2.1 General
RemoteIOMemoryMap is a CSP profile equivalent for a remote I/O device. The CSP profile is described in A.4.
6.2.1.5.2.2 IO_Info_R
Figure 6 shows the class structure of the IO_Info_R class.
IO_Info_R
1.*
BEntry
0.1
OffName
1
PrmName
0.1
OnName
1
RegNo

Figure 6 — CC-Link IO_Info_R class diagram
The IO_Info_R represents IO_Info_RX section and IO_Info_RY section of the CSP profile. A BEntry shall
contain the child classes shown in Figure 6 and A.2.1.2.4.1.
6.2.1.5.3 RemoteDeviceMemoryMap
6.2.1.5.3.1 General
RemoteDeviceMemoryMap is a CSP profile equivalent for a remote device.
6.2.1.5.3.2 IO_Info_R
The class structure of the IO_Info_R class is described in 6.2.1.5.2.2.
6.2.1.5.3.3 IO_Info_RW
Figure 7 shows the class structure of IO_Info_RW class.
8 © ISO 2007 – All rights reserved

---------------------- Page: 13 ----------------------
ISO 15745-5:2007(E)
IO_Info_RW
0.1 1.*
Comment WEntry
0.1
UnitStr
1
PrmName
1
HandReq
1
RWNo
1
HandAns
1
0.1
SelectPrm DatTypFlg
0.1
ReadReg
0.1
SecNameRef
{XOR}
0.1
ILock
0.1
0.1
PrmSet Default
0.1
InterReq
0.1
Range
0.1
InterAns

Figure 7 — CC-Link IO_Info_RW class diagram
Comment class is used to annotate. A WEntry contains the child classes shown in Figure 7 and A.2.1.2.4.2. A
WEntry represents parameters of a word register.
6.2.1.5.3.4 IO_RW_Bit
Figure 8 shows the class structure of IO_RW_Bit class.
IO_RW_Bit
1.*
IO_RW_Bit_Reg
1 0.1
1.*
RegNo WBEntry CmdPtrnRef CmdPtrn
1
0.1
OffName
1
PrmName
0.1
OnName
1
RWBit

Figure 8 — CC-Link IO_RW_Bit class diagram
© ISO 2007 – All rights reserved 9

---------------------- Page: 14 ----------------------
ISO 15745-5:2007(E)
IO_RW_Bit_Reg class is a container of the associated subclasses. RegNo class represents register number.
WBEntry class contains the child classes shown in Figure 8 and A.2.1.2.4.3. WBEntry class represents
parameters of bits used in a word register. CmdPtrnRef is a reference to CmdPtrn.
6.2.1.5.3.5 SelectPrm
Figure 9 shows the class structure of SelectPrm class.
SelectPrm CmdPtrn
0.1
1.*
0.1
{XOR}
SEntry
0.1
UnitStr
1
PrmName
0.1
SecNameRef
0.1
CodeNo
0.1 0.1
UpDwnTyp PrmSet

Figure 9 — CC-Link SelectPrm class diagram
SEntry class contains the child classes shown in Figure 9 and A.2.1.2.4.4. A SEntry represents an entry of the
"Select parameter section" defined in a CSP profile.
6.2.1.5.3.6 PrmSet
Figure 10 shows the class structure of PrmSet class.
PrmSet
1.* 1
1
PrmSetGrp Default
1 1
GrpItemRef GrpItem
1
GrpName
1
0.1
MethodRef MethodEntry
1
GrpNum

Figure 10 — CC-Link PrmSet class diagram
PrmSetGrp class contains the child classes shown in Figure 10 and A.2.1.2.4.5. PrmSetGrp represents an
entry of the parameter set section defined in a CSP profile. The Default class is a reference to the default
PrmSetGrp.
6.2.1.5.3.7 GrpItem
Figure 11 shows the class structure of GrpItem class.
10 © ISO 2007 – All rights reserved

---------------------- Page: 15 ----------------------
ISO 15745-5:2007(E)
GrpItem
1.*
PEntry
0.1
Default
1
ItemName
0.1
Range
0.1
PrmNo
0.1
UnitStr
0.1
RegNo
1
0.1
MethodRef MethodEntry
1
DatTypFlg

Figure 11 — CC-Link GrpItem class diagram
A PEntry contains the child classes shown in Figure 11 and A.2.1.2.4.6. PEntry represents the items of a
parameter entry defined in a CSP profile.
6.2.1.5.3.8 Method
Figure 12 shows the class structure of Method class.
Method
1.*
MethodEntry
0.1
TrueCnd
1
CmdRegNoCode
0.1
ErrReg
0.1
ReqRY
0.1
TrueCnd2
0.1
EndRX
0.1
ILock
0.1
ErrEnd
0.1
InterReq
0.1
ReplyRW
0.1
InterAns

Figure 12 — CC-Link Method class diagram
MethodEntry contains the child classes shown in Figure 12 and A.2.1.2.4.7. A MethodEntry represents a
method defined in a CSP profile.
© ISO 2007 – All rights reserved 11

---------------------- Page: 16 ----------------------
ISO 15745-5:2007(E)
6.2.1.5.3.9 CmdPtrn
Figure 13 shows the class structure of CmdPtrn class.
CmdPtrn
0.1 1.*
Comment WEntry

Figure 13 — CC-Link CmdPtrn class diagram
Comment class is used to annotate. A WEntry contains the child classes shown in Figure 7 and A.2.1.2.4.2. A
WEntry represents parameters of a word register.
6.2.2 Communication network profile
6.2.2.1 General
Figure 14 shows the class structure of the CC-Link communication network profile.
CommNetworkProfile
1 1 0.1
ApplicationLayers TransportLayers
NetworkManagement

Figure 14 — CC-Link communication network profile class diagram
The available formats for CC-Link communication network profiles are described in A.3.
The XML schema representing the CC-Link communication network profile template is defined in A.3.1.3. The
file name of this XML schema shall be “CC-Link_CommNetworkProfile.xsd.”
The XML schema representing the encapsulation of a CC-Link CSP file into the ISO 15745 communication
network profile template is defined in A.3.2.2. The file name of this XML schema shall be
"CSP_CommNetworkProfile_wrapper.xsd."
6.2.2.2 Application layers
The ApplicationLayers class represents the combined profiles for the upper 3 OSI layers of the communication
network integration model. It states the supported application service elements and their associate services.
ApplicationLayers class consists of the child classes shown in Figure 15 and Table 4.
12 © ISO 2007 – All rights reserved

---------------------- Page: 17 ----------------------
ISO 15745-5:2007(E)
1 Master
ApplicationLayers
{XOR}
1
Slave
0.1
Cyclic
0.1
ExtendedCyclic
0.1
Transient
0.*
OptionCommand
1
CommandType
1
Comment
1
BroadcastSupport
1
ReqRes
0.1
Message

Figure 15 — CC-Link ApplicationLayers class diagram
Table 4 — Constraints for child classes of ApplicationLayers class
Class Version 1.00 / 1.10 Version 1.11 Version 2.00 Version LT
Master Mandatory Mandatory Mandatory Mandatory
Slave Mandatory Mandatory Mandatory Mandatory
Cyclic Mandatory Mandatory Optional Mandatory
ExtendedCyclic Not applicable Not applicable Mandatory Not applicable
Transient Optional Optional Optional Not applicable
Message Not applicable Mandatory Optional Not applicable
NOTE The four right hand columns indicate whether a certain child class is mandatory,
optional, or not applicable in a device profile of a specified CC-Link version.

The child classes of ApplicationLayers represent the following:
⎯ Master indicates that the device is a master;
⎯ Slave indicates that the device is a slave;
© ISO 2007 – All rights reserved 13

---------------------- Page: 18 ----------------------
ISO 15745-5:2007(E)
⎯ Cyclic indicates that the device supports cyclic communication;
⎯ ExtendedCyclic indicates that the device supports extended cyclic communication;
⎯ Transient indicates whether or not the device supports transient communication and documents optional
commands defined by the vendor;
⎯ Message indicates whether or not the device supports message communication.
6.2.2.3 Transport layers
6.2.2.3.1 General
The TransportLayers class represents the combined profiles for the lower 4 OSI layers of the CC-Link
communication network integration model. TransportLayers class consists of the child classes shown in
Figure 16.
TransportLayers
1 1
DatalinkLayerInterface PhysicalLayerInterface
0.1
DLConfigParams
0.1
DLVariables

Figure 16 — CC-Link TransportLayers class diagram
6.2.2.3.2 PhysicalLayerInterface
The PhysicalLayerInterface class defines the properties associated with the physical layer of CC-Link.
6.2.2.3.3 DatalinkLayerInterface
The DatalinkLayerInterface class defines the properties associated with the data link layer of CC-Link. The
child classes of DatalinkLayerInterface are represented as follows:
⎯ DLConfigParams defines the properties associated with data link layer configuration;
⎯ DLVariables defines the properties associated with data link layer monitoring.
6.2.2.4 Network management
The NetworkManagement class represents the properties relating to the network management of the CC-Link
communication network integration model. The NetworkManagement class consists of the child classes
shown in Figure 17 and Table 5.
14 © ISO 2007 – All rights reserved

---------------------- Page: 19 ----------------------
ISO 15745-5:2007(E)
NetworkManagement
0.1 0.1 0.1
NetworkStatusInfo
OtherStationsMInfoList SlaveTransInfoLT
0.1 1.* 0.64
SelfStationStatus OtherStationManagementInfo SlaveStationInfo
0.1 0.64
FarStationStatus STInfo
0.1
MasterToSlaveST
0.*
SlaveToMasterST
0.64
ReceivingInfoLT
0.64
SlaveStatusLT

Figure 17 — CC-Link NetworkManagement class diagram
Table 5 — Constraints of the child classes of CC-Link NetworkManagement class
class Version 1.00 / 1.10 Version 1.11 Version 2.00 Version LT
NetworkStatusInfo Optional Optional Optional Optional
OtherStationsMInfoList Optional Optional Optional Not applicable
SlaveTransInfoLT Not applicable Not applicable Not applicable Optional
NOTE The four right hand columns indicate whether a certain child class is mandatory, optional, or not
applicable in a device profile of a specified CC-Link version.

The child classes of NetworkManagement class are as follows:
⎯ NetworkStatusInfo and the associated child classes define the properties associated with status of CC-
Link network;
⎯ OtherStationsMInfoList and OtherStationManagementInfo define the properties associated with the other
stations;
⎯ SlaveTransInfoLT and the associated child classes define the properties associated with the transmission
information of slave stations.
© ISO 2007 – All rights reserved 15

---------------------- Page: 20 ----------------------
ISO 15745-5:2007(E)
Annex A
(normative)

CC-Link profile templates
A.1 General
Configuration tools currently available for CC-Link devices use a specially formatted ASCII file, referred to as
the CSP (CC-Link System Profile). The CSP provides information about a device, such as:
⎯ information needed to identify the connected device,
⎯ a description of device data that can be accessed via the network (e.g. configurable parameters),
⎯ a description
...