Control & Communication
System Profile Specification

BAP-C2008-00

K

Revisions
Sub
number*A

CLPA

Revision description

Issued date

The document number of this specification changed in line with the newnumbering system for specifications(Previous document number: BAP-C1607-001)
Added specifications for CC-Link IE Safety Communication Function Support
Unit
Added specifications for Ethernet Connection Unit
1. Corrected CSP+ Specification Version to 2.0
4.3.1. Clarified the fact that items DEFAULT, RANGE, MIN_INC, ENG_UNIT,
REF are not permitted with structural type elements
4.3.1.1. Clarified the fact that ACCESS items are not permitted in elements of
STRUCT part4.3.1.5. Clarified the fact that decimal and hexadecimal numbers can be
written in the CODE item
4.3.1.8. Same as No. 2
4.3.1.17. Added SEQ_TARGET to keywords
4.3.1.17. Label names starting with "P_" are reserved because they aredescriptions common to units
4.3.1.24. Added booleans to data types of elements that can be referenced
to ENUM parts
4.3.1.25. Appended conditions when writing reference in the READ_DATA
item
4.3.1.29. Written keyword "SEQ" in RELATED_MESSAGE, and added
specifications for running multiple messages consecutively
4.3.1.30. Written keyword "SEQ" in RELATED_METHOD, and added
specifications for running multiple methods consecutively
4.3.1.32. Clarified processing of empty bits when using STRUCT to write
values in REQUEST_DATA (write 0)
4.3.1.38. Added conventions for TARGET items when using "SEQ" in
RELATED_METHOD, RELATED_MESSAGE
4.3.1.40. Appended conditions when writing a reference in the WRITE_DATA
item
4.3.1.40. Clarified processing of empty bits when using STRUCT to write
values in WRITE_DATA (write 0)
4.3.3. Appended handling of control characters as an item common
convention
5.2.1.1. (2) Addition concerning data types of Version Elements
5.2.1.1. (2) (e) Appended handling (priority) when the value of VersionDisplay
elements change due to the version of CSP+
5.2.1.1. (2) (f) Appended the fact that it is recommended not to change thevalue of VersionPolicy elements according to CSP+ version
5.2.1.3. (3) Appended the fact that when the value of DeviceModel elements
are changed at the time CSP+ is updated, it is handled as a different
model
5.2.1.3. (4) Appended the fact that the same ProductID should be written forthe same model
5.5.1. Added the WarningStatus element to elements relating to the systemarea
5.5.3. Appended notes when using "SEQ" in a message, in the description ofparts and elements concerning error history information acquisition

February 2013
April 2015

BAP-C2008ENG-001-K

B

C

D

CLPA

Added specifications for CC-Link IE Field Network Basic connection unit
Added description specifications for acquiring energy management
information
Added description specifications for acquiring the status code and displaying
detailed information of Ethernet connection unit
1. Corrected CSP+ Specification Version to 2.1.
Defined a unit that has the SLMP (TCP/IP) connection function or CC-Link
IE Field Network Basic connection function as an "Ethernet connection
unit"
4.2.7. Added COMM_IF_INPUT, COMM_IF_OUTPUT, BLOCK_INPUT,BLOCK_OUTPUT, COMM_IF_COMMAND, and BLOCK_COMMAND
to the CSP+ file structure of Ethernet connection unit
5.3.1.1. Deleted SyncMinTime element and CommnunicationMinTime
element
5.3.1.3. Deleted the item descriptions of (63) SyncMinTime element and (64)CommnunicationMinTime element
5.5.8. Added conventions for acquiring energy management information
5.5.9. Added functions for acquiring status codes
Added description specifications for acquiring maintenance information
4.3.1.21. Added the type value "MAINTENANCE" and the detailed operating
specifications of "MONITOR"
4.3.1.22. Added the type value "MAINTENANCE" and the detailed operating
specifications of "MONITOR"
4.3.1.31. Added the keyword "POST"
4.3.1.32. Added the keyword "POST"
Added specifications for CC-Link IE TSN connection unit
1. Corrected CSP+ Specification Version to 3.0
4.1.1. Added arbitrary string to the CSP+ file name4.1.2. Added the object dictionary
4.2.8. Added the CSP+ file structure of the CC-Link IE TSN connection unit
4.2.9. Added the information for the CC-Link IE TSN safety communication
function support unit
4.3.1.3. Added addresses used in CC-Link IE TSN to ASSIGN conventions
4.3.1.6. Added the explanation when multiple comments are written to
COMMENT conventions
4.3.1.9. Added the explanation for using "< >" for CC-Link IE TSN to DATA
conventions
4.3.1.21. Added the message type that indicates the parameter automatic
setting of the slave station to MESSAGE_TYPE
4.3.1.31. Added the explanation of RELATED_ELE conventions
5.2.1. Added elements related to CC-Link IE TSN support to DEVICE_INFO
parts
5.3.1. Added elements related to CC-Link IE TSN support to
COMM_IF_INFO parts
5.5.1. Added elements of CC-Link IE TSN to elements related to the systemarea
5.5.10.1. Added conventions related to error information
5.5.10.2. Added conventions related to MESSAGE for slave station
parameter automatic setting
5.5.10.3. Added conventions related to parts and elements that indicate
parameters for safety communication function
5.5.10.4. Added conventions related to MESSAGE specifications for writing
parameters for safety communication function

January 2017

July 2017

November 2018

BAP-C2008ENG-001-K

E

F

G

H

Added specifications for CC-Link IE TSN connection unit
4.2.8.2. Added the note for setting multiple COMM_IF sections
4.3.1.37. Added description specifications of MESSAGE other than SLMP to
REQUEST_TYPE conventions
5.3.1.1. Added AutoSettingHeaderType element
5.3.1.1. Deleted SyncMinTime element and CommnunicationMinTime
element
5.3.1.3. (53) Added the note for writing multiple COMM_IF sections to theitem description of StationMode element
5.3.1.3. (56) Added the item description of AutoSettingHeaderType element
5.3.1.3. Deleted the item descriptions of (63) SyncMinTime element and (64)CommnunicationMinTime element
5.3.7.1. Added the note for CC-Link IE TSN to the item of REQUEST_TYPE
5.5.10.1.1 Added description specifications for a profile which has multiple
COMM_IF sections
5.5.10.2.2 Added the description specification when DATATYPE is constantto the MESSAGE part convention
1. Corrected CSP+ Specification Version to 3.1
5.3.1.1 Added CommunicationCycleMinTime_ns element andCommunicationCycleMinTime_s element to Figure 5-13
5.3.1.1 Added CommunicationCycleMinTime_ns element andCommunicationCycleMinTime_s element to Table 5-69
5.3.1.1 Added the descriptions that "CommunicationCycleMinTime_ns" maybe omitted for devices whose minimum communication cycle isrepresented in the unit of second to *3 in Table 5-69.
5.3.1.3 (63) Added the item description of CommunicationCycleMinTime_ns
5.3.1.3 (64) Added the item description of CommunicationCycleMinTime_s
5.5.10.1.1 Added the specification to be referred to for the error details
information
4.1.1 Corrected the CSP+ file name and supplementary explanation
4.3.1.19 Deleted and added the reserved words (Deleted:
RESPONSE_AREA, RESULT, and SELECT, Added:
RESPONSE_DATA) in Table 4-13
5.3.1.3 (32) Added the value to No.6 in Table 5-106
5.5.6.2 (2) (a) Corrected all the figures in Figure 5-49
5.5.10.4.1 Corrected supplementary explanation for Table 5-444
5.5.10.4.1 Added supplementary explanation for Table 5-445
5.5.10.4.3 (a) Corrected xml
Added specifications for CC-Link IE TSN main module and extension
modules in the following:
4.2.10, 5.5.10.5, 9.6
Table 5-304 in 5.5

April 2019

April 2019

November 2019

August 2020

3.3 Added models of the main module and extension modules
4.1.1 Corrected the description of the COMM_IF section in Figure 4-2
5.1.1.3 (6) Corrected a referenceI

CLPA

1. Corrected CSP+ Specification Version to 4.1
4.2.11 Added the CSP+ file structure of the integrated main/extension
module unit over CC-Link IE TSN
5.3.1.1 Added CyclicResMaxTime element and CertificationClassChoiceelement to Figure 5-13
5.3.1.1 Added CyclicResMaxTime element and CertificationClassChoiceelement to Table 5-69
5.3.1.3 (65) Added the item description of CyclicResMaxTime element
Added descriptions to the DATA item in Table 5-147
5.3.1.3 (73) Added the item description of CertificationClassChoice element
5.5.10.6 Added parts and elements related to the integrated main/extension
module unit
9.7 Added the additional specifications for CSP+ Specifications Version 4.1

January 2022

BAP-C2008ENG-001-K

J

K

CLPA

1. Corrected CSP+ Specification Version to 4.2
5.3.1.1 Added SupportFlg_IPAddressSet element andSupportFlg_NodeIndication element to Figure 5-13
5.3.1.1 Added SupportFlg_IPAddressSet element andSupportFlg_NodeIndication element to Figure 5-69
5.3.1.3 (74) Added the item description of SupportFlg_IPAddressSet element
5.3.1.3 (75) Added the item description of SupportFlg_NodeIndication
element
9.8 Added the additional specifications for CSP+ Specifications Version 4.2
1. Corrected CSP+ Specification Version to 4.3
5.3.1.1 Added ConnectionPortCableType element and ConnectionPortNum
element to Figure 5-13
5.3.1.1 Added ConnectionPortCableType element and ConnectionPortNum
element to Table 5-69
5.3.1.3 (61) Added the item description of ConnectionPortCableTypeelement
5.3.1.3 (62) Added the item description of ConnectionPortNum element
9.9 Added the additional specifications for CSP+ Specifications Version 4.3

January 2023

October 2023

BAP-C2008ENG-001-K

Table of Contents
1.

FOREWORD ............................................................................................................................................ 15

2.

OVERVIEW .............................................................................................................................................. 16
2.1
What is CSP+? .................................................................................................................................. 16
2.2
FEATURES ....................................................................................................................................... 17
2.3
Flow of CSP+ File Utilization ............................................................................................................. 18

3.

GENERAL CONCEPT OF CSP+ FILE DESCRIPTION SPECIFICATIONS ............................................ 19
3.1
Model of CC-Link Family Connected Module ................................................................................... 19
3.2
Models by Module Access Method.................................................................................................... 20
3.2.1
Access by cyclic transmission.................................................................................................... 20
3.2.2
Access by transient transmission .............................................................................................. 23
3.3
Models by Module Form .................................................................................................................... 26

4.

CSP+ FILE STRUCTURE AND DESCRIPTION SPECIFICATIONS ....................................................... 33
4.1
CSP+ File Management Specifications ............................................................................................. 33
4.1.1
CSP+ file name .......................................................................................................................... 33
4.1.2
Data configuration with compression management ................................................................... 34
4.2
CSP+ File Structure .......................................................................................................................... 35
4.2.1
Definitions of sections within a CSP+ file .................................................................................. 35
4.2.2
Definitions of parts within a CSP+ file section ........................................................................... 36
4.2.3
Definitions of elements and items of CSP+ parts ...................................................................... 39
4.2.4
CSP+ file structure of CC-Link connected module .................................................................... 42
4.2.5
CSP+ file structure of CC-Link IE Field Network connected modules ....................................... 47
4.2.6
In the case of the CC-Link IE Field Network Safety Communication Function Support Unit .... 52
4.2.7
CSP+ file structure of Ethernet connection unit ......................................................................... 53
4.2.8
CSP+ file structure of the CC-Link IE TSN connection unit ....................................................... 56
4.2.9
In the case of the CC-Link IE TSN safety communication function support unit ....................... 58
4.2.10 CSP+ file structure of the main module and extension modules over CC-Link IE TSN ............ 59
4.2.11 CSP+ file structure of the integrated main/extension module unit over CC-Link IE TSN .......... 61
4.2.12 Structure of sections, parts, and elements of a CSP+ file ......................................................... 62
4.3
SCP+ File Description Specifications ................................................................................................ 64
4.3.1
Item conventions ........................................................................................................................ 64
4.3.2
Prohibited XML character support ............................................................................................. 91
4.3.3
Common conventions related to item values ............................................................................. 92
4.3.4
Conventions for references that use labels ............................................................................... 97

5.

CSP+ File Details ................................................................................................................................... 101
5.1
FILE Section .................................................................................................................................... 102
5.1.1
FILE_INFO part ........................................................................................................................ 103
5.2
DEVICE Section ............................................................................................................................... 111
5.2.1
DEVICE_INFO part ................................................................................................................... 112
5.3
COMM_IF Section ........................................................................................................................... 141
5.3.1
COMM_IF_INFO part ............................................................................................................... 142
5.3.2
COMM_IF_INPUT part ............................................................................................................ 221
5.3.3
COMM_IF_OUTPUT part ........................................................................................................ 226
5.3.4
COMM_IF_PARAMETER part ................................................................................................. 229
5.3.5
COMM_IF_COMMAND part .................................................................................................... 234
5.3.6
METHOD part .......................................................................................................................... 238
5.3.7
MESSAGE part ........................................................................................................................ 246
5.3.8
STRUCT part ........................................................................................................................... 253
5.3.9
ENUM part ............................................................................................................................... 259
5.3.10 COMMAND_ARGUMENT part ................................................................................................ 265
5.4
BLOCK Section ............................................................................................................................... 270
5.4.1
BLOCK_INFO part ................................................................................................................... 271
5.4.2
BLOCK_INPUT part ................................................................................................................. 277
5.4.3
BLOCK_OUTPUT part ............................................................................................................. 282
5.4.4
BLOCK_PARAMETER part ..................................................................................................... 285
5.4.5
BLOCK_COMMAND part ......................................................................................................... 290
5.4.6
STRUCT part ........................................................................................................................... 293
5.4.7
ENUM part ............................................................................................................................... 295
5.4.8
COMMAND_ARGUMENT part ................................................................................................ 297
BAP-C2008ENG-001-K
CLPA
1-1

5.4.9CONDITION Parts ................................................................................................................... 298
5.5
Parts and Elements with Defined Applications ................................................................................ 306
5.5.1
Elements related to system area ............................................................................................. 307
5.5.2
Parts and elements related to parameter initialization based on initial settings ...................... 333
5.5.3
Parts and elements related to acquisition of error logs ........................................................... 336
5.5.4
Method Specifications for conducting error checks of equipment ........................................... 352
5.5.5
Parts and elements that indicated parameters for safety communication function ................. 357
5.5.6
MESSAGE Specifications for parameter writing of safety communication functions .............. 360
5.5.7
Conventions of read/write capable parameters using parameter IDs ..................................... 365
5.5.8
Parts and elements related to the acquisition of energy management information ................. 368
5.5.9
Convention for acquiring status codes ..................................................................................... 399
5.5.10 Specifications related to CC-Link IE TSN ................................................................................ 404
6.

CSP+ Description Method ...................................................................................................................... 468
6.1
CSP+ Version Management Method ............................................................................................... 468
6.2
Other Language Management ........................................................................................................ 469
6.3
CSP+ File Management .................................................................................................................. 470

7.

Control & Communication System Profile XML Scheme ....................................................................... 471
7.1
XML Schema ................................................................................................................................... 471

8.

Description Specifications of Object Dictionary File ............................................................................... 482
8.1
CSV File Format .............................................................................................................................. 482
8.2
Description Specifications for Each Item ........................................................................................ 483

9.

Additional specifications for CSP+ Specifications Version 1.1 or later .................................................. 485
9.1
Additional specifications for CSP+ Specifications Version 1.1........................................................ 485
9.2
Additional specifications for CSP+ Specifications Version 2.0........................................................ 485
9.3
Additional specifications for CSP+ specifications Version 2.1 ........................................................ 486
9.4
Additional specifications for CSP+ specifications Version 2.2 ........................................................ 486
9.5
Additional specifications for CSP+ Specifications Version 3.0........................................................ 487
9.6
Additional specifications for CSP+ Specifications Version 4.0........................................................ 488
9.7
Additional specifications for CSP+ Specifications Version 4.1........................................................ 488
9.8
Additional specifications for CSP+ Specifications Version 4.2........................................................ 488
9.9
Additional specifications for CSP+ Specifications Version 4.3........................................................ 488

10. Related Specification Documents .......................................................................................................... 489
Figure 2-1 CC-Link Family System Profile (CSP+) ......................................................................... 18
Figure 3-1 Model of CSP+ Module ................................................................................................. 19
Figure 3-2 Example of Input/Output by Cyclic Transmission .......................................................... 20
Figure 3-3 Example of Parameter Transmission/Reception by Cyclic Transmission ....................... 21
Figure 3-4 Example of Command Transmission by Cyclic Transmission ........................................ 22
Figure 3-5 Input/Output by SLMP .................................................................................................. 23
Figure 3-6 Parameter Transmission/Reception by SLMP ............................................................... 24
Figure 3-7 Command Transmission by SLMP ................................................................................ 25
Figure 3-8 Model of Module Connected to Single Network ............................................................. 26
Figure 3-9 Model of Module Used While Switching Between Multiple Networks ............................. 26
Figure 3-10 Model When Describing Information of Only the Main Module ..................................... 27
Figure 3-11 Model When Describing Information of the Main Module and Extension Mod ules
as an Individual Virtual Control Device ....................................................................... 28
Figure 3-12 Model When Describing Information of the Main Module and Extension Modules
as One Virtual Control Device .................................................................................... 29
Figure 3-13 Model When Creating Each CSP+ File for the Main Module and Extensi on
Modules ..................................................................................................................... 30
Figure 3-14 Description Example of When Accessing Extension Modules in Cyclic
Transmission.............................................................................................................. 31
Figure 3-15 Model of Integrated Main/Extension Module Unit ........................................................ 32
Figure 4-1 Configuration within Compressed File ........................................................................... 34
Figure 4-2 CSP+ File Structure ...................................................................................................... 35
BAP-C2008ENG-001-K
CLPA
1-2

Figure 4-3 Section Structure .......................................................................................................... 36
Figure 4-4 Part Structure ............................................................................................................... 39
Figure 4-5 General Model of CSP+ File for CC-Link Connected Module......................................... 43
Figure 4-6 Model of CSP+ File for CC-Link Remote I/O Station ..................................................... 44
Figure 4-7 Model of CSP+ File for CC-Link Remote Device Station, Intelligent Device
Station, and Local Station .......................................................................................... 45
Figure 4-8 Description Example of Multiple COMM_IF Sections with CC -Link ................................ 46
Figure 4-9 General Model of CSP+ File of CC-Link IF Field Network Connected Module ............... 48
Figure 4-10 Model of CSP+ File for CC-Link IE Field Network Connected Remote I/O ................... 49
Figure 4-11 Model of CSP+ File of CC-Link IE Field Network Connected Remote Device
Station, Intelligent Device Station, and Local Station .................................................. 50
Figure 4-12 Writing Multiple COMM_IF Sections in a CC-Link IE Field Network ............................. 51
Figure 4-13 General Model of CSP+ File for Ethernet Connection Unit .......................................... 54
Figure 4-14 Description Example of Multiple COMM_IF Sections with Ethernet Connection
Unit ............................................................................................................................ 55
Figure 4-15 General Model of CSP+ File of CC-Link IE TSN Connection Unit ................................ 56
Figure 4-16 Example of CC-Link IE TSN Devices for which Station Mode Can Be Changed .......... 57
Figure 4-17 General Model of CSP+ Files for the CC-Link IE TSN Main Module andExtension Modules ..................................................................................................... 59
Figure 4-18 General Model of CSP+ Files for Integrated Main/Extension Module Unit ................... 61
Figure 4-19 Structure of FILE Section............................................................................................ 62
Figure 4-20 Structure of DEVICE Section ...................................................................................... 62
Figure 4-21 Structure of COMM_IF Section ................................................................................... 63
Figure 4-22 Structure of BLOCK Section ....................................................................................... 63
Figure 5-1 Structure of FILE Section ........................................................................................... 102
Figure 5-2 Structure of FILE_INFO Part ....................................................................................... 103
Figure 5-3 Structure of Element of FILE_INFO Part ..................................................................... 103
Figure 5-4 Structure of DEVICE Section ...................................................................................... 111
Figure 5-5 Structure of DEVICE_INFO Part ................................................................................. 112
Figure 5-6 Structure of DEVICE_INFO Part for tool link in CC-Link IE TSN .................................. 112
Figure 5-7 Structure of Element of DEVICE_INFO Part................................................................ 113
Figure 5-8 Device Version Management Example ........................................................................ 117
Figure 5-9 Structure of COMM_IF Section ................................................................................... 141
Figure 5-10 Structure of COMM_IF_INFO parts (in the case of CC -Link) ..................................... 142
Figure 5-11 Structure of COMM_IF_INFO Part (in the case of CC -Link IE Field Network) ............ 143
Figure 5-12 Structure of COMM_IF_INFO Parts (in the case of Ethernet) .................................... 144
Figure 5-13 Structure of COMM_IF_INFO Part (CC-Link IE TSN) ................................................ 145
Figure 5-14 Detailed Structure of When a Safety Communication Function of CC -Link IE TSN
is Available .............................................................................................................. 146
Figure 5-15 Structure Definition for Element of COMM_IF_INFO Part .......................................... 146
Figure 5-16 Structure Definition of Element of COMM_IF_INPUT and COMM_IF_OUTPUT
Part .......................................................................................................................... 221
Figure 5-17 Structure Definition for Element of COMM_IF_PARAMETER Part ............................. 229
Figure 5-18 Structure Definition for Element of COMM_IF_COMMAND Part ................................ 234
Figure 5-19 Structure Definition for Element of METHOD Part ..................................................... 238
Figure 5-20 Flow of Procedure-Based Communication Service .................................................... 242
Figure 5-21 Operation of Communication Service Described in METHOD .................................... 243
Figure 5-22 METHOD Sequence ................................................................................................. 244
Figure 5-23 Structure Definition for Element of MESSAGE Part ................................................... 246
Figure 5-24 Operation of Communication Service Described in MESSAGE .................................. 250
Figure 5-25 MESSAGE Call-up and Operation Sequence ............................................................ 251
Figure 5-26 Structure Definition for Element of STRUCT Part ...................................................... 253
CLPA

BAP-C2008ENG-001-K
1-3

Figure 5-27 Structure Definition for Element of ENUM Part .......................................................... 259
Figure 5-28 Structure Definition for Element of COMMAND_ARGUMENT Part ............................ 265
Figure 5-29 Structure of BLOCK Section ..................................................................................... 270
Figure 5-30 Structure of BLOCK_INFO Part ................................................................................ 271
Figure 5-31 Structure Definition for Element of BLOCK_INFO Part .............................................. 271
Figure 5-32 Structure Definition for Element of BLOCK_INPUT Part and BLOCK_OUTPUT
Part .......................................................................................................................... 277
Figure 5-33 Structure Definition for Element of BLOCK_PARAMETER Part ................................. 285
Figure 5-34 Structure Definition for Element of BLOCK_COMMAND Part .................................... 290
Figure 5-35 Structure of CONDITION Parts ................................................................................. 298
Figure 5-36 Structure of conditionVariable parts in CONDITION Parts ......................................... 298
Figure 5-37 Structural definition of conditionMemmber parts in CONDITION Parts ...................... 299
Figure 5-38 Example of conditional expression (CONDITION) ..................................................... 304
Figure 5-39 Relationship between conditional expressions (CONDITION) and parameters .......... 305
Figure 5-40 Image of Structure When System Area Is Described ................................................. 308
Figure 5-41 Image of Structure When Parameter Initialization Based on Initial Settings Is
Described ................................................................................................................. 333
Figure 5-42 Image of Structure When Error Log Acquisition Is Described (When Error Logs
Are Managed on Module Main Body Side) ................................................................ 336
Figure 5-43 Image of Structure When Error Log Acquisition Is Described (When Error Logs
Are Managed on Communication Module Side) ........................................................ 337
Figure 5-44 Structural image when conducting error check of the equipment ............................... 352
Figure 5-45 Examples of METHOD & COMMAND that perform error check of equipment(some unwritable or optional items omitted) ............................................................. 356
Figure 5-46 Structural image in when writing parameters of safety communication functions ....... 357
Figure 5-47 Structural image when describing parameter writing of safety communication
functions .................................................................................................................. 360
Figure 5-48 Structural image when describing enabling parameters of safety communication
functions .................................................................................................................. 360
Figure 5-49 Example of MESSAGE for parameter writing of safety communication functions ....... 364
Figure 5-50 Structural image of read/write capable parameters using parameter IDs ................... 365
Figure 5-51 Image of Structure When Acquisition of Energy Management Information Is
Described (When Energy Management Information Is Managed on Module Main
Body Side) ............................................................................................................... 368
Figure 5-52 Image of Structure When Acquisition of Energy Management Information Is
Described (When Energy Management Information Is Managed on
Communication Module Side) ................................................................................... 368
Figure 5-53 Image of Structure When Acquisition of Status Information Is Described .................. 399
Figure 5-54 Image of Structure When Describing Error Related Information Acquisition .............. 404
Figure 5-55 Description Example of Parts and Elements Related to Error Related Information .... 412
Figure 5-56 Image of Structure When Describing MESSAGE for Slave Station Parameter
Automatic Setting ..................................................................................................... 413
Figure 5-57 Image of Structure When Describing Safety Communication Function
Parameters .............................................................................................................. 418
Figure 5-58 Image of Structure When Describing Parameter Writing of Safety
Communication Function .......................................................................................... 423
Figure 5-59 Image of Structure When Describing Enabling of Safety Communication Function
Parameters .............................................................................................................. 423
Figure 6-1 Version Update Example ............................................................................................ 469
Figure 8-1 CSV File Output Example ........................................................................................... 482
Table 4-1 Parts of a FILE Section .................................................................................................. 36
Table 4-2 Parts of a DEVICE Section ............................................................................................ 36
Table 4-3 Parts of a COMM_IF Section ......................................................................................... 37
BAP-C2008ENG-001-K
CLPA
1-4

Table 4-4 Parts of a BLOCK Section.............................................................................................. 38
Table 4-5 Items of Elements of Parts ............................................................................................. 39
Table 4-6 Items of Elements of METHOD and MESSAGE Parts ..................................................... 39
Table 4-7 Item List ........................................................................................................................ 40
Table 4-8 Definitions of Modules by I/O Type ................................................................................ 44
Table 4-9 ACCESS Attribute List ................................................................................................... 65
Table 4-10 Data Type List ............................................................................................................. 70
Table 4-11 Error PDU Name List ................................................................................................... 73
Table 4-12 Applicable Relational Operators ................................................................................... 74
Table 4-13 Characters Not Permitted in LABEL and LABEL2 Items ............................................... 75
Table 4-14 Values of MESSAGE_TYPE Item ................................................................................. 76
Table 4-15 Values of METHOD_TYPE Item ................................................................................... 77
Table 4-16 RELATED_MESSAGE Item Conventions ..................................................................... 83
Table 4-17 RELATED_METHOD Item Conventions ....................................................................... 85
Table 4-18 PDU Name List for SLMP Request ............................................................................... 86
Table 4-19 PDU Name List for SLMP Response ............................................................................ 87
Table 4-20 Items that Cannot Be Written in Elements WhereSEQ_TARGET Is Written .................. 88
Table 4-21 List of Input Items of Common Utility Software Display Information .............................. 89
Table 4-22 Entity References for Prohibited Characters ................................................................ 91
Table 4-23 Description Rules ........................................................................................................ 92
Table 4-24 List of Conventions Applicable to Each Item ................................................................ 94
Table 4-25 Convention Combined Use Rules ................................................................................. 96
Table 4-26 List of Reference Writable Items .................................................................................. 97
Table 4-27 Description Method of Data Size of Element .............................................................. 100
Table 5-1 CSP+ XML Element List .............................................................................................. 101
Table 5-2 profile Element Attribute List ........................................................................................ 101
Table 5-3 List of XML Child Elements of profile Element .............................................................. 102
Table 5-4 List of Attributes of file Element ................................................................................... 102
Table 5-5 List of XML Child Elements of file Element ................................................................... 102
Table 5-6 Element List for FILE_INFO Part.................................................................................. 104
Table 5-7 Item List for FILE_INFO Part ....................................................................................... 104
Table 5-8 Attribute List for fileInfo Element .................................................................................. 105
Table 5-9 XML Child Element List for fileInfo Element ................................................................. 105
Table 5-10 Attribute List for fileInfoMember Element ................................................................... 105
Table 5-11 XML Child Element List of fileInfoMember Element .................................................... 105
Table 5-12 Item Description Specifications of CreateDate Element .............................................. 106
Table 5-13 Item Description Specifications of CreateTime Element ............................................. 106
Table 5-14 Item Description Specifications of ModDate Element ................................................. 107
Table 5-15 Item Description Specifications of ModTime Element ................................................. 107
Table 5-16 Item Description Specifications of Language Element ................................................ 108
Table 5-17 Item Description Specifications of CCLinkFamilyProfileVersionElement ..................... 109
Table 5-18 Item Description Specifications of FileVersionElement ............................................... 110
Table 5-19 File Version Upgrade Rules ....................................................................................... 110
Table 5-20 List of Attributes of device Element ............................................................................ 111
Table 5-21 List of XML Child Elements of device Element ........................................................... 111
Table 5-22 Element List for DEVICE_INFO Part .......................................................................... 114
Table 5-23 Additional Element of DEVICE_INFO Part in CC-Link IE TSN .................................... 115
Table 5-24 Item List for DEVICE_INFO Part ................................................................................ 116
Table 5-25 Meaning of Each Value of VersionPolicy and Example of Modules that Use theValue ....................................................................................................................... 118
Table 5-26 Attribute List for deviceInfo Element .......................................................................... 120
CLPA

BAP-C2008ENG-001-K
1-5

Table 5-27 XML Child Element List for deviceInfo Element .......................................................... 120
Table 5-28 Attribute List for deviceInfoMember Element .............................................................. 120
Table 5-29 XML Child Element List of deviceInfoMember Element ............................................... 120
Table 5-30 Item Description Specifications of VendorName Element ........................................... 122
Table 5-31 Item Description Specifications of VendorCode Element ............................................ 122
Table 5-32 Item Description Specifications of DeviceModel Element ........................................... 123
Table 5-33 Item Description Specifications of ProductID Element ................................................ 124
Table 5-34 Item Description Specifications of DeviceTypeID Element .......................................... 124
Table 5-35 Item Description Specifications of DeviceTypeDetail Element .................................... 125
Table 5-36 Item Description Specifications of Version Element .................................................... 126
Table 5-37 Item Description Specifications of VersionDisplayFlg Element ................................... 127
Table 5-38 Item Description Specifications of VersionPolicyType Element ................................... 127
Table 5-39 Item Description Specifications of DisplayVersionValue Element ............................... 128
Table 5-40 Item Description Specifications of VersionComment Element ..................................... 128
Table 5-41 Item Description Specifications of DeviceConfigurationID Element ............................. 129
Table 5-42 Item Description Specifications of DeviceConfigurationComment Element ................. 129
Table 5-43 Item Description Specifications of ReferenceURL Element ......................................... 130
Table 5-44 Item Description Specifications of URLInfo Element ................................................... 130
Table 5-45 Item Description Specifications of Outline Element .................................................... 131
Table 5-46 Item Description Specifications of Feature Element ................................................... 131
Table 5-47 Item Description Specifications of SpecList Element .................................................. 132
Table 5-48 Item Description Specifications of PowerSupplyVoltage Element ............................... 132
Table 5-49 Item Description Specifications of ConsumptionCurrent Element ............................... 133
Table 5-50 Item Description Specifications of IconFileName Element .......................................... 133
Table 5-51 Item Description Specifications of GraphicsFileName Element ................................... 134
Table 5-52 Item Description Specifications of Height Element ..................................................... 134
Table 5-53 Item Description Specifications of Width Element ...................................................... 135
Table 5-54 Item Description Specifications of Depth Element ...................................................... 135
Table 5-55 Item Description Specifications of Weight Element ..................................................... 136
Table 5-56 Item Description Specifications of Price Element ....................................................... 136
Table 5-57 Item Description Specifications of UI_ATTRIBUTE_Window** Element ...................... 137
Table 5-58 Item Description Specifications of DedicatedToolFlg Element .................................... 138
Table 5-59 Item Description Specifications of DedicatedToolName Element ................................ 138
Table 5-60 Item Description Specifications of InstallRegistryKeyName Element .......................... 139
Table 5-61 Item Description Specifications of InstallRegistryValueName Element ....................... 139
Table 5-62 Item Description Specifications of ExePathRegistryKeyName Element ....................... 140
Table 5-63 Item Description Specifications of ExePathRegistryValueName Element .................... 140
Table 5-64 List of Attributes of commIf Element........................................................................... 141
Table 5-65 List of XML Child Elements of commIf Element .......................................................... 141
Table 5-66 Elements of COMM_IF_INFO Part with CC-Link ........................................................ 147
Table 5-67 Elements of COMM_IF_INFO Part with CC-Link IE Field Network .............................. 148
Table 5-68 Elements of COMM_IF_INFO parts in Ethernet .......................................................... 149
Table 5-69 Elements of COMM_IF_INFO Part with CC-Link IE TSN ............................................ 150
Table 5-70 Item List for COMM_IF_INFO Part ............................................................................. 152
Table 5-71 Attribute List for commIfInfo Element ......................................................................... 156
Table 5-72 XML Child Element List for commIfInfo Element ......................................................... 156
Table 5-73 Attribute List for commIfInfoMember Element ............................................................. 156
Table 5-74 XML Child Element List of commIfInfoMember Element ............................................. 157
Table 5-75 Item Description Specifications of VendorName Element ........................................... 157
Table 5-76 Item Description Specifications of VendorCode Element ............................................ 158
Table 5-77 Item Description Specifications of CommIFTypeID Element ....................................... 158
CLPA

BAP-C2008ENG-001-K
1-6

Table 5-78 Item Description Specifications of Version Element .................................................... 159
Table 5-79 Item Description Specifications of ReadVersionType Element .................................... 160
Table 5-80 Item Description Specifications of StationType Element ............................................. 161
Table 5-81 Item Description Specifications of StationTypeDetail Element .................................... 161
Table 5-82 Item Description Specifications of TotalNumOfIO Element ......................................... 162
Table 5-83 Item Description Specifications of IOType Element .................................................... 162
Table 5-84 Item Description Specifications of DevModel Element ................................................ 163
Table 5-85 Item Description Specifications of CcLinkVer Element ............................................... 163
Table 5-86 Item Description Specifications of ExtCycle Element .................................................. 164
Table 5-87 Item Description Specifications of NumOccupiedStations Element ............................. 164
Table 5-88 Item Description Specifications of ErrReg Element .................................................... 165
Table 5-89 Item Description Specifications of MasterFlg Element ................................................ 165
Table 5-90 Item Description Specifications of VendorName2 Element ......................................... 166
Table 5-91 Item Description Specifications of nodeType Element ................................................ 166
Table 5-92 Item Description Specifications of IOType Element .................................................... 167
Table 5-93 Item Description Specifications of ModelCode Element .............................................. 167
Table 5-94 Item Description Specifications of DevModel Element ................................................ 168
Table 5-95 Item Description Specifications of ModelName Element ............................................. 168
Table 5-96 Item Description Specifications of RYSize Element .................................................... 169
Table 5-97 Item Description Specifications of RWwSize Element ................................................. 169
Table 5-98 Item Description Specifications of RXSize Element .................................................... 170
Table 5-99 Item Description Specifications of RWrSize Element .................................................. 170
Table 5-100 Item Description Specifications of Ports Element ..................................................... 171
Table 5-101 Item Description Specifications of protcolVersion Element ....................................... 171
Table 5-102 Item Description Specifications of NodeNumberSettingFig Element ......................... 172
Table 5-103 Item Description Specifications of TransientReceptionFig Element .......................... 172
Table 5-104 Item Description Specifications of SMLPRecep tionFig Element ................................ 173
Table 5-105 Item description specifications of SafetyProtocolVersion element ............................ 173
Table 5-106 Item description specifications of SafetyNodeType element ..................................... 174
Table 5-107 Item description specifications of SafetyIn_XSize element ....................................... 174
Table 5-108 Item description specifications of SafetyOut_YSize element .................................... 175
Table 5-109 Item description specifications of SupportSafetyCommServ ice element ................... 175
Table 5-110 Services shown by each bit ...................................................................................... 175
Table 5-111 Item description specifications of SupportIPAddressSize ......................................... 176
Table 5-112 Item description specifications of TimeOutValue element ......................................... 176
Table 5-113 Item description specifications of SupportFlg_SearchNode ...................................... 177
Table 5-114 Item description specifications of SupportFlg_SetIPAddress ele ment ....................... 177
Table 5-115 Item description specifications of SupportFlg_CompareDeviceInfo ........................... 178
Table 5-116 Item description specifications of SupportFlg_GetParam element ............................ 178
Table 5-117 Item description specifications of SupportFlg_SetParam .......................................... 179
Table 5-118 Item description specifications of SupportFlg_StartSetParam element ..................... 179
Table 5-119 Item description specifications of SupportFl g_EndSetParam .................................... 180
Table 5-120 Item description specifications of SupportFlg_CancelSetParam element .................. 180
Table 5-121 Item description specifications of SupportFlg_ReadStatus ....................................... 181
Table 5-122 Item description specifications of SupportFlg_GetCommSetting element .................. 181
Table 5-123 Item description specifications of SupportFlg_ReadStatus2 element ........................ 182
Table 5-124 Item Description Specifications of DevModel Element .............................................. 182
Table 5-125 Item Description Specifications of NumOccupi edStations Element ........................... 183
Table 5-126 Item Description Specifications of CCIEFBasicProtocolVersion Element .................. 183
Table 5-127 Item Description Specifications of EthernetCommFunction Element ......................... 184
Table 5-128 Item Description Specifications of StationMode Element .......................................... 185
CLPA

BAP-C2008ENG-001-K
1-7

Table 5-129 Item Description Specifications of StationModeName Element ................................. 185
Table 5-130 Item Description Specifications of LocalFunction Element ........................................ 186
Table 5-131 Item Description Specifications of AutoSettingHeaderType Element ........................ 186
Table 5-132 Item Description Specifications of AutoSettingType Element .................................... 187
Table 5-133 Item Description Specifications of ModelCode Element ............................................ 188
Table 5-134 Item Description Specifications of ModelCodeEx Eleme nt ........................................ 188
Table 5-135 Item Description Specifications of DevModel Element .............................................. 189
Table 5-136 Item Description Specifications of ConnectionPortCableType Element ..................... 189
Table 5-137 Item Description Specifications of ConnectionPortNum Element .............................. 190
Table 5-138 Item Description Specifications of CanProfileNum Element ...................................... 190
Table 5-139 Item Description Specifications of ObjectDic tionaryFileName Element ..................... 191
Table 5-140 Item Description Specifications of CommunicationCycleMinTime_ns Element .......... 191
Table 5-141 Item Description specifications of CommunicationCycleMinTime_s Element ............ 192
Table 5-142 Item Description Specifications of CyclicResMaxTime Element ................................ 192
Table 5-143 Item Description Specifications of IEEE802_1ASFunction Element .......................... 193
Table 5-144 Item Description Specifications of ReceiveFunction100M Element ........................... 194
Table 5-145 Item Description Specifications of RelayFunction100M Element ............................... 194
Table 5-146 Item Description Specifications of ReceiveFunction1G Element ............................... 195
Table 5-147 Item Description Specifications of RelayFunction1G Element ................................... 195
Table 5-148 Item Description Specifications of MultiCastFunction Element .................................. 196
Table 5-149 Item Description Specifications of CertificationClass Element .................................. 196
Table 5-150 Item Description Specifications of CertificationClassChoice Element ....................... 197
Table 5-151 Item Description Specifications of SupportFlg_IPAddressSet Element ..................... 197
Table 5-152 Item Description Specifications of SupportFlg_NodeIndication Element ................... 198
Table 5-153 Item Description Specifications of S_B_DefaultSize Element ................................... 198
Table 5-154 Item Description Specifications of S_W_DefaultSize Element .................................. 199
Table 5-155 Item Description Specifications of R_B_DefaultSize Element ................................... 199
Table 5-156 Item Description Specifications of R_W_DefaultSize Element .................................. 200
Table 5-157 Item Description Specifications of L_B_DefaultSize Element .................................... 200
Table 5-158 Item Description Specifications of L_W_DefaultSize Element ................................... 201
Table 5-159 Item Description Specifications of S_B_MaxSize E lement ........................................ 201
Table 5-160 Item Description Specifications of S_W_MaxSize Element ....................................... 202
Table 5-161 Item Description Specifications of R_B_MaxSize Element ........................................ 202
Table 5-162 Item Description Specifications of R_W_MaxSize Element ....................................... 203
Table 5-163 Item Description Specifications of L_B_MaxSize Element ........................................ 203
Table 5-164 Item Description Specifications of L_W_MaxSize Element ....................................... 204
Table 5-165 Item Description Specifications of S_B_MinSize Element ......................................... 204
Table 5-166 Item Description Specifications of S_W_MinSize Element ........................................ 205
Table 5-167 Item Description Specifications of R_B_MinSize Element ......................................... 205
Table 5-168 Item Description Specifications of R_W_MinSize Element ........................................ 206
Table 5-169 Item Description Specifications of L_B_MinSize Element ......................................... 206
Table 5-170 Item Description Specifications of L_W_MinSize Element ........................................ 207
Table 5-171 Item Description Specifications of S_B_Address Element ........................................ 207
Table 5-172 Item Description Specifications of S_W_Address Element ....................................... 208
Table 5-173 Item Description Specifications of R_B_Address Element ........................................ 208
Table 5-174 Item Description Specifications of R_W_Address Element ....................................... 209
Table 5-175 Item Description Specifications of StsW_Address Element ....................................... 209
Table 5-176 Item Description Specifications of PDOConfigIndex+X Element ............................... 210
Table 5-177 Item Description Specifications of PDOConfigPDOType+X Element ......................... 210
Table 5-178 Item Description Specifications of PDOConfigMemoryAddress+X Element ............... 211
Table 5-179 Item Description Specifications of PDOConfigPossibleMapping+X Element ............. 211
CLPA

BAP-C2008ENG-001-K
1-8

Table 5-180 Item Description Specifications of S_General_Address Element .............................. 212
Table 5-181 Item Description Specifications of R_General_Address Element .............................. 212
Table 5-182 Item Description Specifications of SafetyProtocolVersion Element ........................... 213
Table 5-183 Item Description Specifications of SafetyNodeType Element .................................... 214
Table 5-184 Item Description Specifications of SupportSafetyCommService Element .................. 215
Table 5-185 Service Shown by Each Bit ...................................................................................... 215
Table 5-186 Item Description Specifications of SupportSafetyInvokeFunc Element ...................... 216
Table 5-187 Safety Function Shown by Each Bit.......................................................................... 216
Table 5-188 Item Description Specifications of S_Safe_DefaultSize Element .............................. 217
Table 5-189 Item Description Specifications of S_Safe_MaxSize Element ................................... 217
Table 5-190 Item Description Specifications of S_Safe_MinSize Element .................................... 218
Table 5-191 Item Description Specifications of S_Safe_Address Element .................................... 218
Table 5-192 Item Description Specifications of R_Safe_DefaultSize Element .............................. 219
Table 5-193 Item Description Specifications of R_Safe_MaxSize Element ................................... 219
Table 5-194 Item Description Specifications of R_Safe_MinSize Elem ent .................................... 220
Table 5-195 Item Description Specifications of R_Safe_Address Element ................................... 220
Table 5-196 List of Elements Defined in COMM_IF_Input Part and COMM_IF_OUTPUT Part ...... 222
Table 5-197 Attribute List for commIfInput Element ..................................................................... 223
Table 5-198 XML Child Element List for commIfInput Element ..................................................... 223
Table 5-199 Attribute List for commIfInputMember Element ......................................................... 223
Table 5-200 XML Child Element List of commIfInputMember Element ......................................... 223
Table 5-201 Item Description Example of Element ....................................................................... 225
Table 5-202 Attribute List for commIfOutput Element ................................................................... 226
Table 5-203 XML Child Element List for commIfOutput Element .................................................. 226
Table 5-204 Attribute List for commIfOutputMember Element ...................................................... 226
Table 5-205 XML Child Element List of commIfOutputMember Element ....................................... 226
Table 5-206 Item Description Example of Element ....................................................................... 228
Table 5-207 Item List for Elements Defined in COMM_IF_PARAMETER Part .............................. 230
Table 5-208 Attribute List for commIfParameter Element ............................................................. 231
Table 5-209 XMLChild Element List for commIfParameterElement ............................................... 231
Table 5-210 Attribute List for commIfParameterMember Element ................................................ 231
Table 5-211 XML Child Element List of commIfParameterMember Element ................................. 231
Table 5-212 Item Description Example of Element ....................................................................... 233
Table 5-213 Item List for Elements Defined in COMM_IF_COMMAND Part ................................. 234
Table 5-214 Attribute List for commIfCommand Element ............................................................. 235
Table 5-215 XML Child Element List for commIfCommandElement .............................................. 235
Table 5-216 Attribute List for commIfPCommandMember Element ............................................... 235
Table 5-217 XML Child Element List of commIfCommandMember Element .................................. 235
Table 5-218 Item Description Example of Element ....................................................................... 237
Table 5-219 Item List for Elements Defined in METHOD Part ...................................................... 239
Table 5-220 Attribute List for method Element ............................................................................. 240
Table 5-221 XML Child Element List for methodElement ............................................................. 240
Table 5-222 Attribute List for methodMember Element ................................................................ 240
Table 5-223 XML Child Element List of methodMemb er Element ................................................. 240
Table 5-224 Item Description Example of Element ....................................................................... 245
Table 5-225 Item List for Elements Defined in MESSAGE Part .................................................... 247
Table 5-226 Attribute List for message Element .......................................................................... 248
Table 5-227 XML Child Element List of message Element ........................................................... 248
Table 5-228 Attribute List for messageMember Element .............................................................. 248
Table 5-229 XML Child Element List of messageMember Element ............................................... 248
Table 5-230 Item Description Example of Element ....................................................................... 252
CLPA

BAP-C2008ENG-001-K
1-9

Table 5-231 Item List for Elements Defined in STRUCT Part ....................................................... 254
Table 5-232 Attribute List for struct Element ................................................................................ 255
Table 5-233 XML Child Element List for struct Element ............................................................... 255
Table 5-234 Attribute List for structMember Element ................................................................... 255
Table 5-235 XML Child Element List of structMember Element .................................................... 255
Table 5-236 Item Description Example of Element (ConvertEnable1) .......................................... 257
Table 5-237 Item Description Example of Element (ConvertEnable2) .......................................... 257
Table 5-238 Item Description Example of Element (ConvertEnable3) .......................................... 257
Table 5-239 Item Description Example of Element (ConvertEnable4) .......................................... 257
Table 5-240 Item List for Elements Defined in ENUM Part ........................................................... 260
Table 5-241 Attribute List for enum Element ................................................................................ 261
Table 5-242 XML Child Element List for enumElement ................................................................ 261
Table 5-243 Attribute List for enumMember Element ................................................................... 261
Table 5-244 XML Child Element List of enumMember Element .................................................... 261
Table 5-245 XML Child Element List of enumMember Element (For CC -Link IE TSN) .................. 262
Table 5-246 Item Description Example of Element (SelCH1) ....................................................... 263
Table 5-247 Item Description Example of Element (SelCH2) ....................................................... 263
Table 5-248 Item Description Example of Element (SelCH3) ....................................................... 263
Table 5-249 Item Description Example of Element (SelCH4) ....................................................... 263
Table 5-250 Item Description Example of Element (enum2) ......................................................... 263
Table 5-251 Item List for Elements Defined in COMMAND_ARGUMENT Part .............................. 266
Table 5-252 Attribute List for commandArgument Element .......................................................... 267
Table 5-253 XML Child Element List for commandArgumentElement ........................................... 267
Table 5-254 Attribute List for commandArgumentMember Element .............................................. 267
Table 5-255 XML Child Element List of commandArgumentMember Element ............................... 267
Table 5-256 Item Description Example of Element ....................................................................... 269
Table 5-257 List of Attributes of block Element ............................................................................ 270
Table 5-258 List of XML Child Elements of block Element ........................................................... 270
Table 5-259 Elements of BLOCK Part .......................................................................................... 272
Table 5-260 Item List of BLOCK_INFO Part ................................................................................. 272
Table 5-261 Attribute List for blockInfo Element .......................................................................... 273
Table 5-262 XML Child Element List for blockInfo Element .......................................................... 273
Table 5-263 Attribute List for blockInfoMember Element .............................................................. 273
Table 5-264 XML Child Element List of blockIfInfoMember Element............................................. 273
Table 5-265 Item Description Specifications of VendorName Element ......................................... 275
Table 5-266 Item Description Specifications of VendorCode Element .......................................... 275
Table 5-267 Item Description Specifications of Version Element .................................................. 276
Table 5-268 List of Items Defined inBLOCK_INPUT Part and BLOCK_OUTPUT Part ................... 278
Table 5-269 Attribute List for blockInput Element ........................................................................ 279
Table 5-270 XML Child Element List for blockInput Element ........................................................ 279
Table 5-271 Attribute List for blockInputMember Element ............................................................ 279
Table 5-272 XML Child Element List of blockIfInputMember Element ........................................... 279
Table 5-273 Item Description Example of Element ....................................................................... 281
Table 5-274 Attribute List for blockOutput Element ...................................................................... 282
Table 5-275 XML Child Element List for blockOutput Element ..................................................... 282
Table 5-276 Attribute List for blockOutputMember Element ......................................................... 283
Table 5-277 XML Child Element List of blockOutputMember Element .......................................... 283
Table 5-278 Item Description Example of Element ....................................................................... 284
Table 5-279 Item List for Elements Defined in BLOCK_PARAMETER Part .................................. 286
Table 5-280 Attribute List for blockParameter Element ................................................................ 287
Table 5-281 Child Element List for blockParameter Element ........................................................ 287
CLPA

BAP-C2008ENG-001-K
1-10

Table 5-282 Attribute List for blockParameterMember Element .................................................... 287
Table 5-283 Child Element List of blockParameterMember Element ............................................ 287
Table 5-284 Item Description Example of Element ....................................................................... 289
Table 5-285 Item List for Elements Defined in BLOCK_COMMAND Part ...................................... 290
Table 5-286 Attribute List for blockCommand Element ................................................................. 291
Table 5-287 XML Child Element List for blockCommand Element ................................................ 291
Table 5-288 Attribute List for blockCommandMember Element .................................................... 291
Table 5-289 List of XML Child Elements of blockCommandMemberElement ................................ 291
Table 5-290 Item Description Example of Element ....................................................................... 292
Table 5-291 Item Description Example of Element (STReturnCode1) .......................................... 293
Table 5-292 Item Description Example of Element (STReturnCode2) .......................................... 293
Table 5-293 Item Description Example of Element ....................................................................... 295
Table 5-294 Item Description Example of Element ....................................................................... 295
Table 5-295 Item Description Example of Element ....................................................................... 295
Table 5-296 Item Description Example of Element ....................................................................... 295
Table 5-297 Item Description Example of Element (enum2) ......................................................... 296
Table 5-298 Item Description Example of Element ....................................................................... 297
Table 5-299 List of conditionVariable parts of CONDITION Parts ................................................. 299
Table 5-300 List of conditionMember parts of CONDITION Parts ................................................. 299
Table 5-301 List of condition element attributes ........................................................................... 300
Table 5-302 List of XML subelements of the condition element .................................................... 300
Table 5-303 List of XML subelements of conditionVariable parts ................................................. 300
Table 5-304 List of XML subelements of conditionMember parts .................................................. 300
Table 5-305 List of attributes of the conditionXVariable element .................................................. 300
Table 5-306 List of attributes of the conditionXVariable element .................................................. 301
Table 5-307 List of attributes of the conditionXVariable element .................................................. 301
Table 5-308 Item description specifications of conditionVariable parts ......................................... 302
Table 5-309 Item description specifications of conditionMemmber parts ...................................... 303
Table 5-310 Network Usage List for Each Application .................................................................. 306
Table 5-311 Element List When the Communication Interface Described in the
COMM_IF_INPUT Part is CC-Link ............................................................................ 309
Table 5-312 Element List When the Communication Interface Described in the
COMM_IF_INPUT Part is the CC-Link IE Field Network ........................................... 309
Table 5-313 Element List When the Communication Interface Described in the
COMM_IF_INPUT Part is CC-Link IE TSN ................................................................ 309
Table 5-314 Element List When the Communication Interface Described in the
COMM_IF_OUTPUT Part is CC-Link ........................................................................ 309
Table 5-315 Element List When the Communication Interface Described in the
COMM_IF_OUTPUT Part is the CC-Link Field Network ............................................ 309
Table 5-316 Element List When the Communication Interface Described in the
COMM_IF_OUTPUT Part is CC-Link IE TSN ............................................................ 309
Table 5-317 Item Description Example of InitialDataProcessReq Element ................................... 310
Table 5-318 Item Description Specifications of InitialDataSetComp Element ............................... 311
Table 5-319 Item Description Specifications of ErrorStatus Element ............................................ 312
Table 5-320 Item Description Specifications of RemoteReady Element ....................................... 313
Table 5-321 Item Description Specifications of MessageTransReceive Element .......................... 314
Table 5-322 Item Description Specifications of MessageHandshakeRX Element ......................... 315
Table 5-323 Item Description Specifications of WarningStatus Element ....................................... 316
Table 5-324 Item Description Example of InitialDataProcessin gReq Element............................... 317
Table 5-325 Item Description Specifications of InitialDataSetComp Element ............................... 318
Table 5-326 Item Description Specifications of ErrorStatus Element ............................................ 319
Table 5-327 Item Description Specifications of RemoteReady Element ....................................... 320
CLPA

BAP-C2008ENG-001-K
1-11

Table 5-328 Item Description Example of WarningStatus Element ............................................... 321
Table 5-329 Item Description Specifications of ErrorStatus Element ............................................ 322
Table 5-330 Item Description Specifications of RemoteReady Element ....................................... 323
Table 5-331 Item Description Example of InitialDataProcessComp Element ................................ 324
Table 5-332 Item Description Specifications of InitialDataSetReq Element .................................. 325
Table 5-333 Item Description Specifications of ErrorResetReq Element ...................................... 326
Table 5-334 Item Description Specifications of MessageTransReq E lement ................................ 327
Table 5-335 Item Description Specifications of MessageHandshakeRY Element ......................... 328
Table 5-336 Item Description Example of InitialDataProcessComp Element ................................ 329
Table 5-337 Item Description Specifications of InitialDataSetReq Element .................................. 330
Table 5-338 Item Description Specifications of ErrorResetReq Element ...................................... 331
Table 5-339 Item Description Specifications of ErrorResetReq Ele ment ...................................... 332
Table 5-340 List of Elements Described in METHOD Part ............................................................ 333
Table 5-341 List of Elements Described in COMM_IF_PARAMETER Part .................................... 333
Table 5-342 Item Description Specifications of ParamInitialize Element ...................................... 334
Table 5-343 Item Description Specifications of Parameter1 Element ........................................... 335
Table 5-344 List of Elements Described in MESSAGE Part ......................................................... 337
Table 5-345 List of Elements Described in COMM_IF_COMMAND Part ....................................... 337
Table 5-346 List of Elements Described in BLOCK_COMMAND Part ........................................... 337
Table 5-347 List of Elements Described in COMMAND_ARGUMENT Part ................................... 338
Table 5-348 Item Description Specifications for SLMPGetErrorLogMessage* Element ................. 339
Table 5-349 Item Description of GetErrorLogCommand** Element .............................................. 341
Table 5-350 Item Description Specifications of GetErrorLogCommand** Element ........................ 342
Table 5-351 Item Description Specifications of ErrorCode Element ............................................. 343
Table 5-352 Item Description Specifications of ErrorYear Element .............................................. 344
Table 5-353 Item Description Specifications of ErrorMonth Element ............................................ 345
Table 5-354 Item Description Specifications of ErrorDay Element ................................................ 346
Table 5-355 Item Description Specifications of ErrorHour Element .............................................. 347
Table 5-356 Item Description Specifications of ErrorMinite Element ............................................ 348
Table 5-357 Item Description Specifications of ErrorSecond Element .......................................... 349
Table 5-358 Item Description Specifications of ErrorDayOfWeek Element ................................... 350
Table 5-359 Item Description Specifications of ErrorDetail** Element .......................................... 351
Table 5-360 List of elements written in METHOD part ................................................................. 352
Table 5-361 List of elements written in COMM_IF_COMMAND part ............................................. 352
Table 5-362 List of elements written in BLOCK_COMMAND part ................................................. 352
Table 5-363 METHOD Specifications for conducting error check of equipment (if error code
can be acquired) ...................................................................................................... 353
Table 5-364 METHOD Specifications for conducting error check of equipment (when error
code cannot be acquired) ......................................................................................... 354
Table 5-365 Example item description of elements of COMM_IF_COMM AND part....................... 355
Table 5-366 Item Description Specifications of BLOCK_COMMAND Element .............................. 355
Table 5-367 Item description example of ErrorCode element ....................................................... 356
Table 5-368 Example of item description in the case of ErrorCode elements ............................... 357
Table 5-369 List of elements written in BLOCK_PARAMETER parts ............................................ 357
Table 5-370 Item Description Specifications of P_TransIntervalMonitorTime Element of
COMM_IF_PARAMETER Part .................................................................................. 358
Table 5-371 Item Description Specifications of P_TransIntervalMonitorTime Element of
BLOCK_PARAMETER Part ...................................................................................... 359
Table 5-372 Reserved words that indicated read/write of CRC32 values ..................................... 360
Table 5-373 List of elements written in MESSAGE parts .............................................................. 361
Table 5-374 List of elements written in COM_IF_PARAMETER parts........................................... 361
Table 5-375 List of elements written in BLOCK_PARAMETER parts ............................................ 361
BAP-C2008ENG-001-K
CLPA
1-12

Table 5-376 List of elements written in BLOCK_PARAMETER parts ............................................ 361
Table 5-377 List of elements written in BLOCK_PARAMETER parts ............................................ 362
Table 5-378 Item Description Specifications of SLMP_P_Safety_ParameterWrite Element .......... 362
Table 5-379 Item Description Specifications of SLMP_P_Safety_EnableParam eter Element ....... 363
Table 5-380 Conventions of COMM_IF_PARAMETER parts ........................................................ 365
Table 5-381 List of elements written in P_ParamIDInfo* .............................................................. 365
Table 5-382 List of elements written in BLOCK_PARAMETER parts ............................................ 365
Table 5-383 Item description specifications of COMM_IF_PARAMETER elements ...................... 366
Table 5-384 Item description specifications of elements of BLOCK_PARAMETER parts .............. 367
Table 5-385 List of Elements Described in METHOD Part ............................................................ 369
Table 5-386 List of Elements Described in MESSAGE Part ......................................................... 369
Table 5-387 List of Elements Described in COMM_IF_COMMAND Part ....................................... 369
Table 5-388 List of Elements Described in BLOCK_COMMAND Part ........................................... 369
Table 5-389 List of Elements Described in COMMAND_ARGUMENT Part ................................... 370
Table 5-390 Item Description Specifications of P_GetEnergyInfo** Element ................................ 371
Table 5-391 Item Description Specifications of P_GetEnergyInfo** Element ................................ 373
Table 5-392 Item Description of GetEnergyInfoCommand Element .............................................. 375
Table 5-393 Item Description Specifications of GetEnergyInfoCommand** Element ..................... 376
Table 5-394 Item Description Specifications of P_AverageCurrent El ement ................................. 377
Table 5-395 Item Description Specifications of P_AverageVoltage Element ................................. 378
Table 5-396 Item Description Specifications of P_ElectricPower Element .................................... 379
Table 5-397 Item Description Specifications of P_ElectricEnergy Element ................................... 380
Table 5-398 Item Description Specifications of P_PowerDistributionTime Element ...................... 381
Table 5-399 Item Description Specifications of P_RunningTime Element ..................................... 382
Table 5-400 Item Description Specifications of P_1_PhaseCurrent Element ................................ 383
Table 5-401 Item Description Specifications of P_2_PhaseCurrent Element ................................ 384
Table 5-402 Item Description Specifications of P_3_PhaseCurrent Element ................................ 385
Table 5-403 Item Description Specifications of P_1_2lineVoltage Element .................................. 386
Table 5-404 Item Description Specifications of P_2_3lineVoltage Element .................................. 387
Table 5-405 Item Description Specifications of P_3_1lineVoltage Element .................................. 388
Table 5-406 Item Description Specifications of P_1_PhaseCurrentDemand Element ................... 389
Table 5-407 Item Description Specifications of P_2_PhaseCurrentDemand Element ................... 390
Table 5-408 Item Description Specifications of P_3_PhaseCurrentDemand Element ................... 391
Table 5-409 Item Description Specifications of P_ElectricPowerDemand Element ....................... 392
Table 5-410 Item Description Specifications of P_PowerFactor Element ...................................... 393
Table 5-411 Item Description Specifications of P_Frequency Element ......................................... 394
Table 5-412 Item Description Specifications of P_ReactiveEnergy Element ................................. 395
Table 5-413 Item Description Specifications of P_1_0PhaseVoltage Element .............................. 396
Table 5-414 Item Description Specifications of P_2_0PhaseVoltage E lement .............................. 397
Table 5-415 Item Description Specifications of P_3_0PhaseVoltage Element .............................. 398
Table 5-416 List of Elements Described in COMM_IF_COMMAND Part ....................................... 399
Table 5-417 List of Elements Described in BLOCK_COMMAND Part ........................................... 399
Table 5-418 List of Elements Described in COMMAND_ARGUMENT Part ................................... 400
Table 5-419 List of Elements Described in ENUM Part ................................................................ 400
Table 5-420 Item Description of P_GetStatusCommand Element ................................................. 401
Table 5-421 Item Description Specifications of Element .............................................................. 401
Table 5-422 Item Description Specifications of Element .............................................................. 402
Table 5-423 Item Description Specifications of ENUM Part Element ............................................ 403
Table 5-424 List of Elements Written in MESSAGE Part .............................................................. 405
Table 5-425 List of Elements Written in COMM_IF_COMMAND Part ........................................... 405
Table 5-426 List of Elements Written in BLOCK_COMMAND Part ............................................... 405
CLPA

BAP-C2008ENG-001-K
1-13

Table 5-427 List of Elements Written in COMMAND_ARGUMENT Part ........................................ 405
Table 5-428 List of Elements Written in ENUM Part ..................................................................... 405
Table 5-429 List of Elements Written in COMMAND_ARGUMENT Part for Detailed
Information Structure Definition ................................................................................ 406
Table 5-430 List of Elements Written in STRUCT Part ................................................................. 406
Table 5-431 Item Description Specifications of P_GetDiagCodeInfo Element ............................... 406
Table 5-432 Item Description Specifications of GetDiagCodeInfoCommand Element ................... 407
Table 5-433 Item Description Specifications of GetDiagCodeCommand Element ......................... 407
Table 5-434 Item Description Specifications of ErrorCo de Element ............................................. 408
Table 5-435 Item Description Specifications of Elements of ENUM Part ...................................... 409
Table 5-436 Item Description Specifications of COMMAND_ARGUMENT Part Element for
Detailed Information Structure Definition .................................................................. 410
Table 5-437 Item Description Specifications of STRUCT Part Element ........................................ 411
Table 5-438 List of Elements Written in MESSAGE Part .............................................................. 413
Table 5-439 List of Elements Written in COMM_IF_PARAMETER Part ........................................ 414
Table 5-440 Item Description Specifications of Element Written Using Only One Element ........... 414
Table 5-441 Item Description Specifications of Element to Write "SEQ_TARGET" to TARGET .... 415
Table 5-442 Item Description Specifications of Elements Referenced from "SEQ_TARGET"
Element ................................................................................................................... 416
Table 5-443 Item Description Specifications of COMM_IF_PARAMETER Part Element ............... 417
Table 5-444 List of Elements Written in COMM_IF_PARAMETER Part ........................................ 418
Table 5-445 List of Elements Written in BLOCK_PARAMETER Part ............................................ 418
Table 5-446 Item Description Specifications of P_TransIntervalMonitorTime Element in
COMM_IF_PARAMETER Part .................................................................................. 419
Table 5-447 Item Description Specifications of P_SafetyCertCode Element in
COMM_IF_PARAMETER Part .................................................................................. 420
Table 5-448 Item Description Specifications of P_TransIntervalMonitorTime Element in
BLOCK_PARAMETER Part ...................................................................................... 421
Table 5-449 Item Description Specifications of P_SafetyCertCode Element in
BLOCK_PARAMETER Part ...................................................................................... 422
Table 5-450 Reserved Words to Indicate Reading and Writing CRC32 Value .............................. 423
Table 5-451 List of Elements Described in MESSAGE Part ......................................................... 424
Table 5-452 List of Elements Described in COMM_IF_PARAMETER Part .................................... 424
Table 5-453 List of Elements Described in BLOCK_PARAMETER Part ........................................ 424
Table 5-454 List of Elements Described in COMM_IF_COMMAND Part ....................................... 425
Table 5-455 List of Elements Described in BLOCK_COMMAND Part ........................................... 425
Table 5-456 Item Description Specifications of SLMP_P_Safety_ParameterWrite Element .......... 425
Table 5-457 Item Description Specifications of COMM_IF_PARAMETER Part Element ............... 426
Table 5-458 Item Description Specifications of BLOCK_PARAMETER Part Element ................... 427
Table 5-459 Item Description Specifications of SLMP_P_Safety_EnableParameter Element ....... 428
Table 5-460 Item Description Specifications of COMM_IF_COMMAND Part Element ................... 429
Table 5-461 Item Description Specifications of BLOCK_COMMAND Part Element ....................... 429
Table 5-462 List of Elements Written in DEVICE_INFO Part .................................................................. 430
Table 5-463 List of Elements Written in DEVICE_INFO Part .................................................................. 436
Table 5-464 List of Elements Written in COMM_IF_INFO Part ............................................................... 439
Table 5-465 List of Elements Written in DEVICE_INFO Part ........................................................ 447
Table 5-466 List of Elements Written in COMM_IF_INFO Part ..................................................... 450
Table 5-467 List of Elements Written in DEVICE_INFO Part ........................................................ 454
Table 5-468 List of Elements Written in COMM_IF_INFO Part ..................................................... 457
Table 6-1 Information for Identifying CSP+ File and Management Method by Utility Software ...... 470
Table 8-1 CSV File Format .......................................................................................................... 482
Table 8-2 Item List ...................................................................................................................... 483
CLPA

BAP-C2008ENG-001-K
1-14

1.

FOREWORD
This document is the Control & Communication System Profile Specifications.
It contains conventions for CSP+ files usable in application software that launches, operates, andmaintains CC-Link family connection units (hereinafter referred to as "utility software")
The CC-Link family connection unit written in this document is a unit connected to the network by thefollowing connection interface.
(1) CC-Link(2) CC-Link IE Field Network(3) Ethernet(4) CC-Link IE TSN
Here, the Ethernet connection unit is a unit possessing an Ethernet physical layer interface, outfittedwith TCP/IP protocol stock, that performs CC-Link IE Field Network Basic communication or conducts
SLMP communication using TCP or UDP packets.
The version of Control & Communication Profile Specifications written in this document (hereinafterreferred to as CSP+ Specifications Version) is version 4.3. Usable conventions varies depending on
CSP+ Specifications Version. See Chapter 9 for details.

CLPA

BAP-C2008ENG-001-K
1-15

2.

OVERVIEW

2.1

What is CSP+?
Control & Communication Profile (CSP+) are specifications for for writing the necessary information tostart up, operate, and maintain CC-Link Family Connection units.
In the past, the CC-Link system profile (CSP) has been used to describe such information in relation to
CC-Link connected modules. Since the enactment of CSP specifications, however, the need for profile
specifications that offer a higher level of descriptiveness has increased due to reasons such as thefollowing:(1) Module diversification
While in the past single-function products with minimal setup were the mainstream, there has
been an increase in highly functional modules capable of complex setup and control in recent
years.
(2) Utility software application diversification
Not only has module input/output and parameter setup become increasingly diversified, but sohave the objectives of utility software usage, such as diagnostics and energy management (future
concept).
(3) Network diversification
Protocols for connecting modules, including CC-Link, CC-Link IE Field Network, SLMP (Seamless
Message Protocol), and CC-Link IE TSN have become increasingly diversified.
In this context, CSP+ is now to be defined as the protocol specifications for CC-Link family connected
modules.

CLPA

BAP-C2008ENG-001-K
1-16

2.2

FEATURESThis section describes the features of CSP+.
(1) Integrates the utility software environment
With CSP+, CSP+ files are imported into utility software when starting, running, and maintaining a
module, making it possible to manage all modules connected to the CC-Link family from a single
utility software. If the development vendor of the module creates a CSP+ file for the module to be
developed, there is no need to create individual utility software.
(2) Integrates different protocol profile specifications
CSP+ allows profile descriptions to be executed using the same format for modules that areconnected via different communication protocols, such as CC-Link connected modules and
CC-Link IE Field Network connected modules.
(3) Offers high descriptiveness, achieving utility software user-friendliness
CSP+ improves the user-friendliness of utility software with its high descriptiveness, such as itslabels applicable with ladders and groupings for collectively displaying parameters by function on
utility software screens.
(4) Offers application compatible descriptions
CSP+ offers application compatible profile descriptions, such as profile descriptions fordiagnostics and energy management (future concept), allowing the display of special screenswith layouts specialized for each application via utility software.

CLPA

BAP-C2008ENG-001-K
1-17

2.3

Flow of CSP+ File Utilization
This section describes the flow of CSP+ file utilization.
(1) Creating and distributing a CSP+ file
When a module development vendor develops a CC-Link family connected module, the vendor
creates a CSP+ file for the module to be developed, and distributes that file to the user. Whencreating the CSP+ file, refer to this document and create the file so that it is compliant with CSP+
specifications.
(2) Importing the CSP+ file
Next, the CSP+ file is imported into the utility software used for starting, running, and maintaining
the module to be utilized. To utilize CSP+ with utility software, the utility software must have afunction for importing CSP+. CSP+ compatible software includes, for example, a parameter setup
tool, monitor tool, diagnostics tool, and energy management tool. The vendor that develops themaster module or the vendor that develops applications for diagnostics, energy management, or
the like, provides the CSP+ compatible utility software.
(3) Utilizing the utility software
The utility software is then utilized to start, run, and maintain the target module. The functions
provided differ for each utility software. Select the utility software in accordance with the purposeof use.
Module development vendor
Utility software vendor
Create and distribute

Provide utility
Import
CSP+ compatible utility software
Parameter
setup tool

Monitortool

Diagnostics
tool

CSP+ file
User

Energy management…
tool

CSP+ file

Module setup
Energy management

Diagnostics

and monitor

Figure 2-1 CC-Link Family System Profile (CSP+)

CLPA

BAP-C2008ENG-001-K
1-18

GENERAL CONCEPT OF CSP+ FILE DESCRIPTION SPECIFICATIONS

3.

This chapter describes the basic concept of CSP+ file creation.

Model of CC-Link Family Connected Module

3.1

With CSP+, CC-Link family connected modules are separated into virtual field devices that represent
communication function sections and virtual control devices that represent module-specific sections.
These devices are then modeled and respectively described to support a variety of communication. At
this time, the input, output, parameter, and command access of the virtual control devices from theutility software via the network is considered to be respectively executed via the outputs, inputs,
parameters, and commands (see Section 3.2) of the corresponding network virtual field devices.
The descriptions related to the virtual control devices can be standardized between modules having
the same module-specific functions but different communication protocols by separately describing
communication protocol dependent virtual field devices and module-specific functions.
Module ofcommunication
method A

Utility software

Network of communication method A

Module of communication method A

From the module
functions, extract only
the control function
section

Virtualconnection

Outputs
Inputs

Outputs

Parameters

Parameters

Commands

Commands

Virtual field device of communication
method A

Module ofcommunication
method B

InputsFrom the module
functions, extract only
the communication
function section

Virtual control device
Communication
method通信方式の違いはdifferences
are absorbed
COMM_IF で吸収され、by the virtual
field device,
BLOCK
は共通化できる。
making standardization of
the control function
section possible.

Utility software

Network of communication method B

Module of communication
method B

Outputs

Inputs

Inputs

Outputs

Parameters

Parameters
Commands

Commands
Virtual connection

Virtual field device ofcommunication method B

Virtual control device

Figure 3-1 Model of CSP+ Module

CLPA

BAP-C2008ENG-001-K
1-19

3.2

Models by Module Access Method
This chapter describes a CSP+ module model for each module access method.
Below are described the items common to all module access modeling.
(1) Input/Output
When module input/output contacts or input/output areas are directly allocated for reading andwriting with cyclic transmission remote inputs/outputs or remote registers, or when transienttransmission is used to perform reading and writing with module input/output contacts or
input/output areas, input or output modeling is performed.
(2) Parameters
When part of the cyclic transmission area is temporarily used to send and receive moduleparameters, or when transient transmission is used to send and receive module parameters,
parameter modeling is performed.
(3) Commands
When part of the cyclic transmission area is temporarily used to request module commands, orwhen transient transmission is used to request module commands, command modeling is
performed.

3.2.1

Access by cyclic transmission
This section describes how the previously described common items are expressed in virtual control
devices and virtual field devices for module access via cyclic transmission.
(1) Input/Output
In a case where access via cyclic transmission is described for input/output, sometimes module
bit-unit data (input contacts, output contacts, etc.) is allocated in a fixed manner to cyclic
transmission remote input/output (RX, RY) and used, and sometimes byte-unit or word-unit datais allocated in a fixed manner to remote registers (RWr, RWw) and used.
At this time, the information input to the master station is described as virtual field device input,
with output further described for virtual control devices and information related to virtual control
device output further described for virtual field device input. Similarly, information output from themaster station is described as virtual field device output, with input further described for virtual
control devices and information related to virtual control device input further described for virtual
field device output.
Figure 3-2 shows an example of a case where access via cyclic transmission is described for
input and output. Figure 3-2 is an example of a case where RY0 is associated with output contact
1, and RX0 is associated with input contact 1. As shown in the figure, RY0 and RX0 of the module
are respectively described as the output and input of the virtual field device, and output contact 1
and input contact 1 of the module are respectively described as the input and output of the virtual
control device.
ModuleMaster station

Lamp
SwitchMasterstationModuleControl

RY0

RY0

Output contact 1

Lamp

program

RX0

RX0

Input contact 1

SwitchCSP+ model

Output

Input

Input

OutputVirtual field device

Virtual control device

Figure 3-2 Example of Input/Output by Cyclic Transmission
CLPA

BAP-C2008ENG-001-K
1-20

(2) Parameters
In a case where access via cyclic transmission is described for parameters, sometimes a part ofthe cyclic transmission remote register and remote input/output area is temporarily used totransmit and receive module parameters.
At this time, parameter related information is described as virtual field device parameters, withparameters further described for virtual control devices and information related to virtual control
device parameters further described for virtual field device parameters. In addition, information
related to parameter transmission/reception procedures is described as virtual field device
methods, with information related to virtual field device parameters described in the method.
Note that "a part of the cyclic transmission remote register and remote input/output area is
temporarily used to transmit and receive module parameters" refers to a case where parameterreading and writing is expressed by a procedure such as the following, for example (the following
is an example of parameter writing):[1]

The master station writes a parameter value to RWw1.

[2]

The master station turns RY1 ON.

[3]

The module detects RY1 ON.

[4]

The module reads the parameter value from RWw1.

[5]The module reflects the parameter value into the internal memory of the module.

Figure 3-3 shows an example of a case where access via cyclic transmission is described forparameters. Figure 3-3 is an example of a case where a module has the parameters parameter 1
and parameter 2, and RWw1 and RY1 are used in the parameter transmission/reception
procedure. As shown in Figure 3-3, parameter 1 and parameter 2 of the module are described as
the virtual field device parameter and virtual control device parameter, and the parametertransmission/reception procedure is described as the method.
MasterstationModuleMasterstationControl
programModuleRWw1

RWw1

Parameter 1

RY1

RY1

Parameter 2

CSP+ model
MethodVirtual field device

Parameter

Parameter
Virtual control device

Figure 3-3 Example of Parameter Transmission/Reception by Cyclic Transmission

CLPA

BAP-C2008ENG-001-K
1-21

(3) Commands
In a case where access via cyclic transmission is described for commands, sometimes a part ofthe cyclic transmission remote register and remote input/output area is temporarily used forcommand requests to modules.
At this time, command related information is described as virtual field device commands, withcommands further described for virtual control devices and information related to virtual control
device commands further described for virtual field device commands. In addition, information
related to command request procedures is described as virtual field device methods, withinformation related to virtual field device commands described in the method.
Note that "a part of the cyclic transmission remote register and remote input/output area
temporarily used for command requests to modules" refers to a case where command execution
requests held by devices are expressed by a procedure such as the following, for example:[1]

The master station writes a command code to RWw2.

[2]

The master station turns RY2 ON.

[3]

The module detects RY2 ON.

[4]

The module reads the command code from RWw2.

[5]The module executes the command.

Figure 3-4 shows an example of a case where access by cyclic transmission is described forcommands. Figure 3-4 is an example of a case where the module can execute the command
entitled command 1, and RWw2 and RY2 are used in the command request procedure. As shownin Figure 3-4, command 1 of the module is described as a virtual field device command andvirtual control device command, and the command request procedure is described as themethod.
Master station

ModuleMaster station
Control
programModule

RWw2

RWw2

RY2

RY2

Command 1

CSP+ model
MethodCommand

Virtual field device

Command
Virtual control device

Figure 3-4 Example of Command Transmission by Cyclic Transmission

CLPA

BAP-C2008ENG-001-K
1-22

3.2.2

Access by transient transmission
This section describes how the previously described common items are expressed in virtual control
devices and virtual field devices for module access via transient transmission.
Note that, with CSP+ specifications, access via SLMP can be described for transient transmission.
(1) Input/Output
In a case where access via transient transmission is described for input or output, sometimes
SLMP is used for input/output control.
At this time, the information input to the master station is described as virtual field device input,
with output further described for virtual control devices and information related to virtual control
device output further described for virtual field device input. In addition, SLMP command
information used by the master station for data reading is described as virtual field device
messages. Similarly, information outputted from the master station is described as virtual fielddevice output, with input further described for virtual control devices and information related tovirtual control device input further described for virtual field device output. Further, the SLMP
command information used for data writing is similarly described as virtual field device messages.
Figure 3-5 shows an example of a case where access via transient transmission is described for
input and output. Figure 3-5 is an example of a case where output contact 1 and input contact 1of the module are transmitted and received via SLMP messages. As shown in Figure 3-5, output
contact 1 and input contact 1 of the module are respectively described as the output and input ofthe virtual field device and the input and output of the virtual control device, and the SLMP
command information to be used is described as a message.
Master station

ModuleLamp
SwitchMaster station
Control
programModuleSLMP

Output contact 1

Lamp

Input contact 1

SwitchCSP+ model

Output

Input

Input

OutputMessage

Virtual field device

Virtual control device

Figure 3-5 Input/Output by SLMPCLPA

BAP-C2008ENG-001-K
1-23

(2) Parameters
In a case where access via transient transmission is described for parameters, sometimes SLMP
is used for module parameter transmission and reception.
At this time, parameter related information is described as virtual field device parameters, withparameters further described for virtual control devices and information related to the virtual
control device parameters further described for virtual field device parameters. In addition, SLMP
command information used for parameter reading and writing is described as virtual field device
messages, with information related to virtual field device parameters described in the messages.
Figure 3-6 shows an example of a case where access via transient transmission is described forparameters. Figure 3-6 is an example of a case where a module has the parameters parameter 1
and parameter 2, and transmission/reception is performed via SLMP messages. As shown in
Figure 3-6, parameter 1 and parameter 2 of the module are described as the virtual field device
parameter and virtual control device parameter, and the SLMP command information to be used
is described as the message.
When parts or elements with defined applications shown in Section 5.5 are used, the message
part may not need to be described (see Section 5.5.7). In this case, parameters are transmitted or
received using the method which is determined beforehand corresponding to the specific partname or element name (such as specific SLMP command).
Master station

Master station
Control
programModuleModuleParameter 1
SLMP
Parameter 2

CSP+ model
Message

Parameter

Virtual field device

Parameter
Virtual control device

Figure 3-6 Parameter Transmission/Reception by SLMPCLPA

BAP-C2008ENG-001-K
1-24

(3) Commands
In a case where access via transient transmission is described for commands, sometimes SLMP
is used for command requests to modules.
At this time, command related information is described as virtual field device commands, withcommands further described for virtual control devices and information related to virtual control
device commands further described for virtual field device commands. In addition, SLMP
command information used for command requests is described as virtual field device messages,
with information related to virtual field device commands described in the message.
Figure 3-7 shows an example of a case where access by transient transmission is described forcommands. Figure 3-7 is an example of a case where the module can execute the command
entitled command 1, and the request is made via an SLMP message. As shown in Figure 3-7,command 1 of the module is described as a virtual field device command and virtual control
device command, and the SLMP command information to be used is described as a message.
Master station

Master station
Control
programModuleModuleSLMP
Command 1

CSP+ model
Message

Command

Virtual field device

Command
Virtual control device

Figure 3-7 Command Transmission by SLMPCLPA

BAP-C2008ENG-001-K
1-25

3.3

Models by Module Form
This section describes a module model for CSP+ for each module form. Each model describes only
the information for one CSP+ file. Note that, for explanatory purposes, method and message
descriptions are omitted.
(1) Module connected to a single network
Figure 3-8 shows a model of a module connected to a single network. With CSP+, output, input,
parameter, and command descriptions are provided for the virtual field device, and input, output,
parameter, and command descriptions are provided for the virtual control device.
Master station

CC-Link family

Outputs

Inputs

Inputs

Outputs

Parameters

Parameters

Commands

Commands

ModuleVirtual field device

Virtual control device

Figure 3-8 Model of Module Connected to Single Network(2) Module used while switching between multiple networks
With a module that is used while switching between multiple networks, such as CC-Link and the
CC-Link IE Field Network, separate CSP+ files are created for each network. Distinguish the files
using the "arbitrary string" area in the CSP+ file name so that the file names are not duplicated(For descriptions of arbitrary string in the CSP+ file name, see Section 4.1.1).
Figure 3-9 shows a model used while switching between multiple networks.
CSP+ file of A network
Master station

A network
ModuleOutput

Input

Input

OutputParameter

Parameter

CommandCommand

Virtual field device

Virtual control device

CSP+ file of B network
Master station

B network

Output

Input

Input

OutputParameter

Parameter

CommandCommandModuleVirtual field device

Virtual control device

Figure 3-9 Model of Module Used While Switching Between Multiple Networks

CLPA

BAP-C2008ENG-001-K
1-26

(3) Module used together with other modules
There are three models for a module used together with other modules. The module configurationis the same for all three models: one main module and multiple extension modules. The following
are the definitions of each module.
Main module: A module that can be connected to a network and controls extension modules
Extension module: A module that can be connected to a main module
Each of three models are described below 1) to 3).
1) Model when describing information of only the main module to a CSP+ fileIn this case, the model is the same as that for a single module.
As shown in Figure 3-10, the input, output, parameters, and commands used in the main module
are described as the virtual control device information in a CSP+ file.
CSP+ file of the main module

Master station

Output

Input

Input

OutputParameters

Parameters

Commands

Commands

Virtual field device

Virtual control device

CC-Link family network

A

B

Main module
Extension modules

Figure 3-10 Model When Describing Information of Only the Main Module

CLPA

BAP-C2008ENG-001-K
1-27

2) Model when describing information of the main module and extension modules to one CSP+ file
When describing information of the main module and extension modules to one CSP+ file, each
module can be described as an individual virtual control device. Note that describing information ofeach module as an individual control device is optional. Information of the main module and themodule A can be described as one virtual control device.
Figure 3-11 shows an example of when information of the main module and the extension modules
are described as an individual virtual control device. In Figure 3-11, the extension modules aredescribed as module A and module B. Therefore, three virtual control devices are described for themain module, module A, and module B. In this example, each element described in the output,
input, parameters, commands of the virtual field device associates with each element described in
the input, output, parameters, and commands of the virtual control device of the communication
head module or the virtual control device of the module A.
CSP+ file
Master station

Input
OutputParameters

CC-Link family network

CommandsA

Main module

B

Extension modules

Virtual control device(main module)

OutputInput
Parameters
Commands

Input
OutputParameters
Commands

Virtual field device
Virtual control device(module A)

Input
OutputParameters
Commands
Virtual control device(module B)

Figure 3-11 Model When Describing Information of the Main Module and Extension Modules as an
Individual Virtual Control Device

CLPA

BAP-C2008ENG-001-K
1-28

Figure 3-12 shows an example of when information of the main module and the extension modules
are described as one virtual control device. In Figure 3-11, the extension modules are describedas the module A and module B.
Master station

CSP+ file

CC-Link family network

A

Main module

Input

Input of the main module

Input

Input of the module A

Output

Input

Input of the module B

Input

OutputOutput of the main module

Parameters

OutputOutput of the module A

Commands

OutputOutput of the module B

Parameters

Parameters of the main module

Parameters

Parameters of the module A

Parameters

Parameters of the module B

Commands

Commands of the main module

Commands

Commands of the module A

Commands

Commands of the module B

B

Extension modules

Virtual field device

Virtual control device

Figure 3-12 Model When Describing Information of the Main Module and Extension Modules as One
Virtual Control Device

CLPA

BAP-C2008ENG-001-K
1-29

3) Model when creating each CSP+ file for the main module and extension modules
Each CSP+ file is created for the main module and extension modules.
In the CSP+ file for the main module, information for connecting extension modules is describedin addition to the description of the single module.
In the CSP+ file for an extension module, the output, input, parameters, and commands aredescribed in the virtual field device connected to the main module. Also, the input, output,
parameters, and commands are described in the virtual control device.
Figure 3-13 shows an example of when each CSP+ file is created for extension modules. In
Figure 3-13, the main module is connected to the extension modules A and B. In the utility
software supporting the CSP+ file for extension modules, functions, such as parameter settingsand monitor function, of the extension modules are provided via the main module based on theconfiguration information of the extension modules A and B and the main module set in thesoftware and the CSP+ file information corresponding to the modules.

Master station

CC-Link family network

A

B

Main module

CSP+ file of the extension module A
Extension module A

Extension module B

Output

Input

Input

Output

CSP+ file of the main module

OutputInput

Parameters

Parameters

Input

OutputCommands

Commands

Parameters

Parameters

Commands

Commands

Virtualfield

deviceforaccessing the main module

Virtual control device

CSP+ file of the extension module B
Virtual field device

Virtual control device+ Extension moduleconnection device

Output

Input

Input

OutputParameters

Parameters

Commands

Commands

Virtualfield

deviceaccessing the main modulefor

Virtual control device

Figure 3-13 Model When Creating Each CSP+ File for the Main Module and Extension Modules

CLPA

BAP-C2008ENG-001-K
1-30

When accessing an extension module directly in transient transmission, describe how to access it
to the CSP+ file for the extension module. When accessing an extension module in cyclic
transmission, describe the cyclic transmission area for accessing the X-th extension module to
the CSP+ of the main module, and describe the information of how the area is used in theextension module to the CSP+ of the extension module.
Figure 3-14 shows an example of the output of the extension module in cyclic transmission. RY0
to RYF for the 1st extension module and RY10 to RY1F for the 2nd extension module aredescribed to the CSP+ file for the main module. By describing information of how the area is used
to the CSP+ of the extension module, the output contact 0 of the extension module B, forexample, can be accessed using RY10.
Master station

CC-Link family network

A

B

Main module

CSP+ file of the extension module A
Extension module A

Extension module B

Output 0

Output contact 0

Output 1

Output contact 1

CSP+ file of the main module

RY0

For 1sttoextension

RYF

module

･
･
･

･
･
･

CSP+ file of the extension module B

RY10
to
RY1F

For 2ndextension
moduleOutput 0

Output contact 0

Output 1

Output contact 1

･
･
･

･
･
･

Figure 3-14 Description Example of When Accessing Extension Modules in Cyclic Transmission

CLPA

BAP-C2008ENG-001-K
1-31

(4) Integrated main/extension module unit
Devices that are a single module but can be divided into a main module section and an extension
module section can model those sections separately.
The following are the definitions of each module section.
• Main module section: A section that can be connected to a network and controls extension module
sections• Extension module section: A section that operates as an extension module connected to the main
module section
In the integrated main/extension module unit, one CSP+ file is created each for the main module
section and the extension module section.
Figure 3-15 shows the model of the integrated main/extension module unit.

CC-Link family network
Integrated main/extension module unit

Extension module section
Main module section

CSP+ file of the main module section

CSP+ file of the extension module section

Commands

Commands

Commands

Commands

Virtual fielddeviceVirtual control
deviceVirtual fielddeviceVirtual control
deviceFigure 3-15 Model of Integrated Main/Extension Module Unit

CLPA

BAP-C2008ENG-001-K
1-32

4.

CSP+ FILE STRUCTURE AND DESCRIPTION SPECIFICATIONS

4.1

CSP+ File Management Specifications
CSP+ files can be managed together in multiple along with CSP+ file related files (icon files, graphics
files) as a compressed file.
If the utility software supports compressed files, the CSP+ files can then be imported by specifying thecompressed file. With this in mind, note that, in this document, importing a CSP+ file can also be readas importing a compressed file.

4.1.1

CSP+ file name
A CSP+ file is named as follows:
VendorCode_ModelName(DeviceConfigurationID)_DeviceVersion_LanguageInformation[_Arbitr
aryString].cssp･ Description in parentheses "( )" and "[ ]" may be omitted.
･ When using device configuration IDs, write the round parentheses "( )".
･ When using arbitrary strings, there is no need to write the square brackets "[ ]".
The vendor code is the code of the vendor that manufactured the module. The code is always
expressed using four digits. For example, "0x0000" is written as "0x0000" and not abbreviated to"0x0". In addition, "0x" which indicates a hexadecimal number must also be written. Use the value
written in the element "Vendor Code" of the part DEVICE_INFO described later.
The model name is the model name of the module. Use the string written in the element "Device
Model" of the part Device_INFO described later.
The device configuration ID is used for identification purposes when multiple profiles are defined by
the device configuration. When the device configuration ID is defined, add the ID after the model
name. Use the string written in the element "Device Configuration ID" of the part Device_INFO
described later. If a device configuration ID is not defined, the string in the "(Device Configuration ID)"
section is not required.
The device version is the device version of the module. Use the string written in the element "Display
Version Value" of the part Device_INFO described later. However, if the element "Display Version
Value" is omitted, use the string written in the element "Version" of the part DEVICE_INFO.
The language information is the information that indicates the language supported by the CSP+ filedescription. Use the string written in the element "Language" of the part FILE_INFO described later.
An arbitrary string is used to prevent file names from being duplicated when CSP+ files are created foreach network with the devices that can be connected to different networks.
The following describes the reference examples for the arbitrary string.
• CC-Link• CC-Link IE Field• Ethernet *Including Basic• CC-Link IE TSN: CCLink: CCLinkIEField: Ethernet: CCLinkIETSNAll of this information is used for the file name as well. If an unpermitted character (such as "/") is usedin the file name, that character is omitted.
The vendor code, model name, device version, and language information are all described in the
CSP+ file as module information and file information as well. For details, see Chapter 5.

CLPA

BAP-C2008ENG-001-K
1-33

Data configuration with compression management

4.1.2

This section describes the specifications of compressed files.
Usage of compressed files allows you to manage multiple CSP+ files and CSP+ file associated icon
files, graphics files, and object dictionary files together. Compress and manage compressed files in zip
format. Creation of a compressed file requires compliance with the following specifications.
The files and folders within a compressed file need to be configured as shown in Figure 4-1.
Compress the files by specifying one or more CSP+ files in the upper most level of thecompressed file, and a folder that stores graphics ("Folder" in Figure 4-1), without preparing an
upper-most folder that includes all of the files to be compressed.
 The names of the CSP+ files must comply with the specifications indicated in Section 4.1.1.
 The graphics folder name must be the vendor code. Note the following:➢ Always indicate the vendor code using a 4-digit number. For example, write "0x0000" as"0x0000" and not the abbreviated "0x0".
➢ "0x", which indicates a hexadecimal number, needs to be written as well.
➢ Use the value written in the element "VendorCode" of the part DEVICE_INFO described later.
➢ If graphics files are not required, a graphics folder is not necessary.







Each file name needs to be the file name written as the icon file name, graphics file name, andobject dictionary file name in the CSP+ file. Write the icon file name in the element"IconFileName" of the part DEVICE_INFO described later. Write the graphics file name in theelement "GraphicsFileName" in the part DEVICE_INFO described later. Write the object
dictionary file name in the element "ObjectDictionaryFileName" of the COMM_IF_INFO partdescribed later.
(For icon file name, graphics file name, and object dictionary file name details, see Chapter 5.)
All of the icon file, graphics file, and object dictionary file must be stored in the same folder("Folder" in Figure 4-1).
CSP+ files from multiple vendors cannot be managed together.
The names of all files and folders to be compressed must be written using single-bytealphanumeric characters and symbols.
The name of the compressed file can be freely determined by the vendor.
CSP+ file 1
CSP+ file 2···

FolderGraphics file 1
Graphics file 2
Object dictionary file···Figure 4-1 Configuration within Compressed File
[Note] The object dictionary file is required when the CAN compatible device of CC-Link IE TSN isused. For details, see Section 4.2.8.4.

CLPA

BAP-C2008ENG-001-K
1-34

4.2

CSP+ File Structure
CSP+ files are written using XML.

4.2.1

Definitions of sections within a CSP+ file
A CSP+ file comprises a FILE section, DEVICE section, BLOCK section, and COMM_IF section.
Figure 4-2 shows the structure of a CSP+ file.

Figure 4-2 CSP+ File Structure

CLPA

BAP-C2008ENG-001-K
1-35

4.2.2

Definitions of parts within a CSP+ file section
Each section of a CSP+ file comprises multiple parts. Figure 4-3 shows the structure within a section.

Section
Part
Part

Part
Figure 4-3 Section Structure
The configuration of a part is determined for each section. Table 4-1 to Table 4-4 list the parts thatmake up each section.
Table 4-1 Parts of a FILE Section
No.

Part

Information Described
CSP+ file management information
FILE_INFO(Examples of elements: File creation date, language information,(See Section 5.1.1.)
file version)
One FILE_INFO part needs to be written in a FILE section.


1.

Table 4-2 Parts of a DEVICE Section
No.

Part

Information Described
Module identification information(Examples of elements: Vendor name, model name)
DEVICE_INFO Module product information(See Section 5.2.1.)(Examples of elements: Specification information, power supply
voltage, current consumption, external dimensions)
One DEVICE_INFO part needs to be written in a DEVICE section.


1.

CLPA

BAP-C2008ENG-001-K
1-36

Table 4-3 Parts of a COMM_IF Section
No.

Part


1.

COMM_IF_INFO(See Section 5.3.1.)

2.

COMM_IF_OUTPUT(See Section 5.3.2.)

3.

COMM_IF_INPUT(See Section 5.3.3.)

4.

COMM_IF_PARAMETER(See Section 5.3.4.)

5.

COMM_IF_COMMAND(See Section 5.3.5.)












6.

METHOD(See Section 5.3.6.)

7.

MESSAGE(See Section 5.3.7.)

8.
9.
10.

STRUCT(See Section 5.3.8.)
ENUM(See Section 5.3.9.)
COMMAND_ARGUMENT(See Section 5.3.10.)



Information Described
Communication function identification information(Examples of elements: Vendor name, communication method)
Communication function specifications(Examples of elements: Station type, CC-Link version, number ofoccupied stations)
Reference (address assignment) information for "Control function
input information"
Communication function output information(Examples of elements: CC-Link module error reset request flag)
Reference (address assignment) information for "Control function
output information"
Communication function input information(Examples of elements: CC-Link module remote ready)
Reference information for "Control function parameter information"
Communication function parameter information(Examples of elements: Operation at communication reset)
Reference information for "Control function command information"
Communication function dedicated command information(Examples of elements: Communication reset)
Communication service information for "Procedures and data area
specification"
Used for communication services, handshakes, andreading/writing.
Register information.
Communication service information for "Data format specification"
Communication service target, and request and response data
format information

Remote register (RWw/RWr) bit assignments
Setting range options
Argument information for the part COMM_IF_COMMAND

The COMM_IF section includes parts that may be omitted.
One COMM_IF_INFO part needs to be written in the COMM_IF section.
All parts other than the COMM_IF_INFO part can be written in multiple within the section.

CLPA

BAP-C2008ENG-001-K
1-37

Table 4-4 Parts of a BLOCK Section
No.
1.

Part
BLOCK_INFO(See Section 5.4.1.)

2.

BLOCK_INPUT(See Section 5.4.2.)

3.

BLOCK_OUTPUT(See Section 5.4.3.)

4.

BLOCK_PARAMETER(See Section 5.4.4.)

5.

BLOCK_COMMAND(See Section 5.4.5.)

6.
7.
8.

STRUCT(See Section 5.4.6.)
ENUM(See Section 5.4.7.)
COMMAND_ARGUMENT(See Section 5.4.8.)







Information Described
Control function identification information(Examples of elements: Vendor name)Control function input information(Examples of elements: Output current value, forward run
command)Control function output information(Examples of elements: Voltage input value, in forward run)Control function parameter information(Examples of elements: Range settings, upper limit frequency,
lower limit frequency)
Control function command information(Examples of elements: Reset, parameter batch clear, dataacquisition at error)

Bit assignments of the part COMMAND_ARGUMENT
Setting range options
Argument information for the part BLOCK_COMMAND

The BLOCK section includes parts that may be omitted.
One BLOCK_INFO part needs to be written in the COMM_IF section.
All parts other than the BLOCK_INFO part can be written in multiple within the section.

CLPA

BAP-C2008ENG-001-K
1-38

4.2.3

Definitions of elements and items of CSP+ parts
Each part of a section of a CSP+ file is made up of one or more elements. Each element is made up of
one or more items. Figure 4-4 shows the relationship between elements, which make up a part, anditems, which make up an element.

SectionPart

Element
Element

Item

Element

Item

Element

Item
Figure 4-4 Part Structure

Table 4-5 and Table 4-6 list the items of each part.

Item Name

SectionType
FILE
DEVICE

COMM_IFBLOCK

Part Type
FILE_INFODEVICE_INFO
COMM_IF_INFO
COMM_IF_INPUTCOMM_IF_OUTPUT
COMM_IF_PARAMETER
COMM_IF_COMMANDMETHODMESSAGESTRUCT
ENUM
COMMAND_ARGUMENTBLOCK_INFOBLOCK_INPUTBLOCK_OUTPUTBLOCK_PARAMETERBLOCK_COMMANDSTRUCT
ENUM
COMMAND_ARGUMENT
CONDITIONLABELLABEL2
CATEGORYNAME
DATATYPEDATADEFAULTRANGE
MIN_INC
ENG_UNITACCESSASSIGNUI_ATTRIBUTE
WRITE_ORDER
ARGUMENT
OFFSET
CODE
RELATED_ELE
CONDITIONx
RESULTx
REF
COMMENT

Table 4-5 Items of Elements of Parts● ○ ○ ○ ● ●● ○ ○ ○ ● ●● ○ ○ ○ ● ●● ○ ○ ○ ○○ ○ ○ ○ ○ ○ ○● ○ ○ ○ ○○ ○ ○ ○ ○ ○ ○● ○ ○ ○ ○○ ○ ○ ○ ○ ○ ○ ○● ○ ○ ○○
Described in separate table
Described in separate table● ○ ○ ○ ○○ ○ ○ ○●
● ○ ○ ●
● ○● ○ ○ ● ●○ ○ ○ ○ ● ○● ○ ○ ○ ● ●● ○ ○ ● ●○ ○ ○ ○ ○○● ○ ○ ● ●○ ○ ○ ○ ○○● ○ ○ ● ●○ ○ ○ ○ ●○ ○● ○ ○ ●○
● ○ ○ ● ●○ ○ ○ ○●
● ○ ○ ●
● ○● ○ ○ ● ●○ ○ ○ ○ ● ○○:Optional●:Required
○ ○
○ ○
○ ○
○ ○

○ ○
○
○
○
○
○
○
○
○
○
● ●

CLPA

○

COMMENTERR_YPERELATED_MESSAGERESPONSE_DATATYPERESPONSE_TYPERESPONSE_DATAREQUEST_DATATYPE

REQUEST_DATA● ○ ○ ● ●REQUEST_TYPE

RELATED_METHOD● ○ ○ ● ● ● ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○MESSAGENAMEMETHODMESSAGE_TYPE

ERR_REGISTER

ERR_CONDITIONEND_CONDITION

REQ_FLAG

INTERROCKREAD_DATATYPE

READ_DATAREAD_REGISTERWRITE_DATATYPE

WRITE_DATAWRITE_REGISTERMETHOD_TYPE

TARGET

CATEGORY

Part NameLABELLABEL2Item Name

ERR_CODE_RANGE

Table 4-6 Items of Elements of METHOD and MESSAGE Parts○● ● ○ ○ ○ ○ ○ ○ ○ ○BAP-C2008ENG-001-K
1-39

Table 4-7 shows a list of items. The items available for each part are described in Chapter 5.
Table 4-7 Item List
No.

Item Name

1. ACCESS
2. ARGUMENT
3. ASSIGN
4. CATEGORY
5. CODE
6. COMMENT
7. CONDITIONx
8. CONDITIONXVARIABLE
9. DATA
10. DATATYPE
11. DEFAULT
12. END_CONDITION
13. ENG_UNIT
14. ERR_CODE_RANGE
15. ERR_CONDITION
16. ERR_REGISTER
17. ERR_TYPE
18. INTERLOCK
19. LABEL
20. LABEL2
21. MESSAGE_TYPE
22. METHOD_TYPE
23. MIN_INC
24. NAME
25. OFFSET
26. RANGE
27. READ_DATA
28. READ_DATATYPE
29. READ_REGISTER
30. REF
31. RELATED_ELE
CLPAOverview
Describes access attributes.
Describes label names that indicate arguments.
Describes assignments.
Describes the group name with which the element isaffiliated.
Describes codes.
Describes comments.
Writes the range of conditions for determination of conditional
expressions.
Writes reference to elements used for determination of
conditional expressions.
Describes data.
Describes data types.
Describes default values.
Describes normal end conditions.
Describes the engineering unit.
Described the error code range.
Describes abnormal end conditions.
Describes the name of the register that stores error codes.
Describes the type of the response processing data format
when an error occurs.
Describes conditional expressions using register names.
Describes labels.
Describes labels used for other language support.
Describes the message type.
Describes the method type.
Describes the minimum increment.
Describes the name.
Describes the assigned offset of the structure interior.
Describes the setting range.
Describes the storage destination of read data.
Describes the data type of the register to be read.
Describes the register that is to implement reading.
Describes a reference.
Describes a reference.

Description
Location
Section 4.3.1.1
Section 4.3.1.2
Section 4.3.1.3
Section 4.3.1.4
Section 4.3.1.5
Section 4.3.1.6
Section 4.3.1.7
Section 4.3.1.8
Section 4.3.1.9
Section
4.3.1.10
Section 4.3.1.11
Section
4.3.1.12
Section
4.3.1.13
Section
4.3.1.14
Section
4.3.1.15
Section
4.3.1.16
Section
4.3.1.17
Section
4.3.1.18
Section
4.3.1.19
Section
4.3.1.20
Section
4.3.1.21
Section
4.3.1.22
Section
4.3.1.23
Section
4.3.1.24
Section
4.3.1.25
Section
4.3.1.26
Section
4.3.1.27
Section
4.3.1.28
Section
4.3.1.29
Section
4.3.1.30
Section
4.3.1.31

BAP-C2008ENG-001-K
1-40

32. RELATED_MESSAGE
33. RELATED_METHOD
34. REQ_FLAG
35. REQUEST_DATA
36. REQUEST_DATATYPE
37. REQUEST_TYPE
38. RESPONSE_DATA
39. RESPONSE_DATATYPE
40. RESPONSE_TYPE
41. RESULTx
42. TARGET
43. UI_ATTRIBUTE
44. WRITE_DATA
45. WRITE_DATATYPE
46. WRITE_ORDER
47. WRITE_REGISTER

CLPA

Describes a reference to a message that indicatesprocessing prior to the message.
Describes a reference to a method that indicates processing
prior to the method.
Describes the request flag name.
Describes the storage destination of the value to be delivered
in request processing.
Describes the data type of REQUEST_DATA.
Describes the type of the data format for request processing.
Describes the value to be returned in response processing.
Describes the data type of RESPONSE_DATA.
Describes the type of the data format of the data used in
response processing.
Writes the value applied when conditions are satisfied.
Describes the communication parameters or communicationcommands to serve as the target of the method or message.
Describes the display method when displaying data using
utility software.
Describes the write value.
Describes the data type of the register for writing.
Describes the writing order.
Describes the register that is to implement writing.

Section
4.3.1.32
Section
4.3.1.33
Section
4.3.1.34
Section
4.3.1.35
Section
4.3.1.36
Section
4.3.1.37
Section
4.3.1.38
Section
4.3.1.39
Section
4.3.1.40
Section
4.3.1.41
Section
4.3.1.42
Section
4.3.1.43
Section
4.3.1.44
Section
4.3.1.45
Section
4.3.1.46
Section
4.3.1.47

BAP-C2008ENG-001-K
1-41

4.2.4

CSP+ file structure of CC-Link connected module
Figure 4-5 shows a general model of a CSP+ file of a CC-Link connected module.
The details of each part described in the COMM_IF section and BLOCK section as well as thereference relationships are as follows.
(1) COMM_IF section output and BLOCK section input
Output as viewed from the communication function side (same as output as viewed from themaster station) is described in the COMM_IF_OUTPUT part of the COMM_IF section, and in the
BLOCK_INPUT part of the BLOCK section.
The direction of input/output of the BLOCK section is the same as the input/output from thecontrol function side to the communication function side. As a result, the output from thecommunication function side is the input to the control function side. Thus, the BLOCK_INPUT
part corresponds to the COMM_IF_OUTPUT part.
The remote output (RY) and remote register (RWw) information is described in each element of
the COMM_IF_OUTPUT part, and the module output contact and output area information as well
as module set values, flags, and the like are described in each element of the BLOCK_INPUT
part.
There is no need to describe data that is not mounted or used by the module. However, theaddresses of remote outputs and remote registers for which corresponding elements are notdescribed in cyclic transmission areas that can be used based on module settings indicate thatthe areas are not accessible by the sequence program and utility software. If you want to clearly
indicate the reason why an area is not accessible, describe the non-accessible element with thereason written in the name.
Each element of the COMM_IF_OUTPUT part refers to the elements of the associated
BLOCK_INPU part.
Non-associated elements may be present.
(2) COMM_IF section input and BLOCK section output
Input as viewed from the communication function side (same as input as viewed from the masterstation) is described in the COMM_IF_INPUT part of the COMM_IF section, and in the
BLOCK_OUTPUT part of the BLOCK section.
The input to the communication function side is the output from the control function side. Thus,
the BLOCK_OUTPUT part corresponds to the COMM_IF_INPUT part.
The remote input (RX) and remote register (RWr) information is described in each element of the
COMM_IF_INPUT part, and the module input contact and input area information as well as
module present values, status information, and the like are described in each element of the
BLOCK_OUTPUT part.
There is no need to describe data that is not mounted or used by the module. However, theaddresses of remote inputs and remote registers for which corresponding elements are notdescribed in cyclic transmission areas that can be used based on module settings indicate thatthe areas are not accessible by the sequence program and utility software. If you want to clearly
indicate the reason why an area is not accessible, describe the non-accessible element with thereason written in the name.
Each element of the COMM_IF_INPUT part refers to the elements of the associated
BLOCK_OUTPUT part.
Non-associated elements may be present.

CLPA

BAP-C2008ENG-001-K
1-42

(3) Parameters
Parameters are described in the COMM_IF_PARAMETER part of the COMM_IF section, and the
BLOCK_PARAMETER part of the BLOCK section.
The procedures for reading and writing parameters and information regarding the parameters
used are described in the METHOD part.
Each element of the COM_IF_PARAMETER part and BLOCK_PARAMETER part is associated
so that the elements of the METHOD part refer to the elements of the COMM_IF_PARAMETER
part, and the elements of the COMM_IF_PARAMETER part refer to the elements of the
BLOCK_PARAMETER part.
(4) Commands
Commands are described in the COMM_IF_COMMAND part of the COMM_IF section, and the
BLOCK_COMMAND part of the BLOCK section.
The procedures for executing commands and information regarding the arguments used aredescribed in the METHOD part.
Each element of the COMM_IF_COMMAND part and BLOCK_COMMAND part is associated sothat the elements of the METHOD part refer to the elements of the COMM_IF_COMMAND part,and the elements of the COMM_IF_COMMAND part refer to the elements of the
BLOCK_COMMAND part.
FILE

FILE_INFODEVICEDEVICE_INFO

COMM_IFCOMM_IF_INFO
COMM_IF_OUTPUT
RY0
RY1

Output contact 0
Output contact 1

...

RWw0
RWw1

Output area 0
Output area 1

...

...

COMM_IF_INPUTRX0RX1

BLOCK_OUTPUT
Input contact 0
Input contact 1

...

...

RWr0
RWr1

Input area 0
Input area 1

...

...

COMM_IF_PARAMETERBLOCK_PARAMETER

Parameter 1

Parameter 1...

... ... ... ...

...

Method 1

BLOCK_INPUT...

METHODBLOCK
BLOCK_INFO

COMM_IF_COMMANDBLOCK_COMMAND

Command 1

Command 1

...

...

Indicates a reference relationship.

Figure 4-5 General Model of CSP+ File for CC-Link Connected Module

CLPA

BAP-C2008ENG-001-K
1-43

4.2.4.1 CSP+ file structure of remote I/O station
Figure 4-6 shows a model of the structure of a CSP+ file for a remote I/O station of a CC-Link
connected module. With a remote I/O station, the parts COMM_IF_INPUT, COMM_IF_OUTPUT,BLOCK_INPUT, and BLOCK_OUTPUT are used.
With a remote I/O station, the parts METHOD, COMM_IF_PARAMETER, COMM_IF_COMMAND,BLOCK_PARAMETER, and BLOCK_COMMAND are not written. Further, for input/output, only remote
input/output (RX, RY) is described.
FILE

FILE_INFODEVICEDEVICE_INFO

COMM_IFCOMM_IF_INFOBLOCK
BLOCK_INFO

COMM_IF_OUTPUTBLOCK_INPUT

RY0
RY1
RY2

Output contact 0
Output contact 1
Output contact 2

...

...

COMM_IF_INPUT
RX0
RX1
RX2

BLOCK_OUTPUT
Input contact 0
Input contact 1
Input contact 2

...

...

Indicates a reference relationship.

Figure 4-6 Model of CSP+ File for CC-Link Remote I/O Station
All remote I/O stations cannot necessarily be mounted with an input/output function. The mountable
information is defined for each I/O type as shown in Figure 4-8.
Table 4-8 Definitions of Modules by I/O TypeNo.

I/O Type

1.
2.
3.

Input
OutputFront/Back mixed, mixed

CLPA

COMM_IF_OUTPUT Part,
BLOCK_INPUT Part


COMM_IF_INPUT Part,
BLOCK_OUTPUT Part

BAP-C2008ENG-001-K
1-44

4.2.4.2 CSP+ file structure of remote device station, intelligent device station, and local station
The models of a remote device station, intelligent device station, and local station of CC-Link
connected module are the same as that of a general model. Figure 4-7 shows a model of the CSP+
file.
Note that there is no need to describe references from all elements of the COMM_IF section to the
BLOCK session. An example is described below.
[1] CC-Link system area
[2] Communication module dedicated parameter and command information of communication module
type modules[3] Input/Output information not directly related with the device control function, such as flags formethod handshakes
While a local station is capable of referring to values outputted by all stations in the same manner as amaster station, only the input/output information assigned to the location station (the input/output
information that can be read/written by the local station only) is described in the COMM_IF_OUTPUT
part and COMM_IF_INPUT part. At this time, the last two points of remote input/output (RX, RY) are
not described. As a result, for example, the remote input/output of 30 points is described for one
occupied station at 1x, and the remote input/output of 446 points is described for four occupied
stations at 4x.
FILE

FILE_INFODEVICEDEVICE_INFO

COMM_IFCOMM_IF_INFOBLOCK
BLOCK_INFO

COMM_IF_OUTPUTBLOCK_INPUT

RY0
RY1

Output contact 0
Output contact 1

...

...

RYn0
RYn1
...

COMM_IF_INPUTRX0RX1

BLOCK_OUTPUT
Input contact 0
Input contact 1

...

...

RXn0
RXn1
...

METHOD

Parameter 1
Parameter 2

BLOCK_PARAMETER

Command 1
Command 2...

...

Method 1
Method 2
Method 3
Method 4

COMM_IF_PARAMETER...

COMM_IF_COMMANDBLOCK_COMMAND

Command 1
Command 2

Command 1

...

...

Indicates a reference relationship.
n: Indicates the system area. (No. of occupied stations: ･2-1)*However, if the device if fixed to 32 I/O points, n = 1,
regardless of the number of occupied stations.

Figure 4-7 Model of CSP+ File for CC-Link Remote Device Station, Intelligent Device Station, andLocal Station
CLPA

BAP-C2008ENG-001-K
1-45

4.2.4.3 CSP+ file structure when multiple COMM_IF sections are written
When the number of occupied stations (1, 2, 3, or 4), the CC-Link version (1.00, 1.10, 1.11, 2.00), or
the extended cyclic setting (with a CC-Link version of 2.00) is variable, a COMM_IF section needs tobe written for each setting. (The section needs to be described taking combinations into consideration
as well.) With the utility software, only the settings described in COMM_IF sections need to beacknowledged.
If the communication specifications change as a result of changes in module operation settings,
regardless if the above settings remain the same, we recommend that you write a COMM_IF section
for each operation setting. In such a case, if multiple COMM_IF sections are written, the content
indicated by each COMM_IF section needs to be described in the COMMENT item.
Note that, if the module function does not change even if multiple COMM_IF sections are written, theassociations from the multiple COMM_IF sections to a common BLOCK section are to be described.
Figure 4-8 shows the section configuration in a case where the number of occupied stations isselectable from the values 1 to 4.
FILE

FILE_INFODEVICEDEVICE_INFO

COMM_IF
1 occupied station

COMM_IF_INFOBLOCK
BLOCK_INFO

COMM_IF_OUTPU
T
RY0

...
RWw0

...
COMM_IF_INPUT
RX0

...
RWr0

Output area 0...

Parameter 1

Method 1...

... ... ... ...

COMM_IF_COMMAND

Command 1... ...

2 occupied stations

Output contact 0

...

...
COMM_IF_PARAMETERMETHODBLOCK_INPUTCOMM_IF_INFOBLOCK_OUTPUT...

Input contact 0

COMM_IF_INPUT

Input contact 0...

COMM_IF_OUTPUT

...

...
COMM_IF_PARAMETER...

METHOD

Method 1...

COMM_IF_COMMAND...

3 occupied stations

COMM_IF_INFO
COMM_IF_OUTPUT...

Parameter 1...

COMM_IF_INPUTBLOCK_PARAMETER...
COMM_IF_PARAMETER...

METHOD

Method 1...

COMM_IF_COMMAND...

4 occupied stations

COMM_IF_INFO
COMM_IF_OUTPUTBLOCK_COMMAND
Command 1...

...
COMM_IF_INPUT...
COMM_IF_PARAMETER...

METHOD

Method 1...

COMM_IF_COMMAND...
Indicates a reference
relationship.

Figure 4-8 Description Example of Multiple COMM_IF Sections with CC-Link
CLPA

BAP-C2008ENG-001-K
1-46

4.2.5

CSP+ file structure of CC-Link IE Field Network connected modules
Figure 4-9 shows a general model of a CSP+ file of a CC-Link IE Field Network connected module.
With a CC-Link IE Field Network connected module, you can write messages for accessing inputs,
outputs, parameters, and commands using SLMP in addition to parameter setup and commandexecution using the same methods as with CC-Link connected modules. The differences in thereference relationship with the contents of each part described in the COMM_IF and BLOCK sections
from that with a CC-Link connected module (see Section 4.2.4) are as follows.
(1) COMM_IF section output and BLOCK section input
In addition to the contents that can be written with CC-Link connected modules, the following
descriptions are also possible.
Information regarding the input contacts and input areas of data read using SLMP commands is
described in each element of the COMM_IF_INPUT part. In addition, information related to SLMP
commands used for data reading is described in the MESSAGE part of the COMM_IF section.
The descriptions of each element of the BLOCK_OUTPUT part are the same as that for accessvia cyclic transmission. Each element of the COMM_IF_INPUT part is associated by reference
from with the elements of the MESSAGE part, with the elements of the MESSAGE part referringto the elements of the COMM_IF_INPUT part. (The reference relationship between the elementsof the COMM_IF_INPUT part and each element of the BLOCK_OUTPUT part is the same as thatfor access via cyclic transmission.)
Note that access via SLMP and access via cyclic transmission can be used in combination. In
such a case, as shown in Figure 4-9, the BLOCK_OUTPUT part is referred to by two
COMM_IF_INPUT parts.
(2) COMM_IF section input and BLOCK section output
In addition to the contents that can be written with CC-Link connected modules, the following
descriptions are also possible.
Information regarding the output contacts and output areas of data to be written using SLMP
commands is described in each element of the COMM_IF_OUTPUT part. In addition, information
related to SLMP commands to be used for data writing is described in the MESSAGE part of the
COMM_IF section. The descriptions of each element of the BLOCK_INPUT part are the same as
those for access via cyclic transmission. Each element of the COMM_IF_OUTPUT part isassociated by reference with the elements of the MESSAGE part, with the elements of the
MESSAGE part referring to the elements of the COMM_IF_OUTPUT part. (The reference
relationship between the elements of the COMM_IF_OUTPUT part and each element of the
BLOCK_INPUT part is the same as that for access via cyclic transmission.)
Note that access via SLMP and access via cyclic transmission can be used in combination. In
such a case, as shown in Figure 4-9, the BLOCK_INPUT part is referred to by two
COMM_IF_OUTPUT parts.
(3) Parameters
In addition to the contents that can be written with CC-Link connected modules, the following
descriptions are also possible.
Information related to SLMP commands to be used for parameter reading and writing is describedin the MESSAGE part of the COMM_IF section. Each element of the COMM_IF_PARAMETER
part is associated by reference with the elements of the MESSAGE part, with the elements of the
MESSAGE part referring to the elements of the COMM_IF_PARAMETER part. (The reference
relationship between the elements of the COMM_IF_PARAMETER part and the elements of the
BLOCK_PARAMETER part is the same as that for access via cyclic transmission.)(4) Commands
In addition to the contents that can be written with CC-Link connected modules, the following
descriptions are also possible.
Information related to SLMP commands to be used for command execution is described in the
MESSAGE part of the COMM_IF section. Each element of the COMM_IF_COMMAND part isassociated by reference with the elements of the MESSAGE part, with the elements of the
MESSAGE part referring to the elements of the COMM_IF_COMMAND part. (The reference
relationship between the elements of the COMM_IF_COMMAND part and the elements of the
BLOCK_COMMAND part is the same as that for access via cyclic transmission.)

CLPA

BAP-C2008ENG-001-K
1-47

FILE

FILE_INFODEVICEDEVICE_INFO

COMM_IFCOMM_IF_INFO...

COMM_IF_OUTPU
T
RY0
RY1

BLOCK
BLOCK_INFOBLOCK_INPUT

RWw0
RWw1

Output contact 0
Output contact 1

...

...

Output area 0
Output area 1...

COMM_IF_OUTPU
T
Output contact0
Output contact 1...
Output area 0
Output area 1...

COMM_IF_INPUT
RX0
RX1

COMM_IF_INPUT

Input area 0
Input area 1...

Input contact 0
Input contact 1...

... ... ...

Input contact 1...

Message 1

BLOCK_OUTPU
T
Input contact
0

...

...

MESSAGE

RWr0
RWr1

Input area 0
Input area 1...
COMM_IF_PARAMETERMETHODBLOCK_PARAMETER

Parameter 1

COMM_IF_COMMANDBLOCK_COMMAND

Command 1...

Command 1
Command 2

Parameter 10...

Parameter 10...

... ... ... ...

COMM_IF_PARAMETER...

Method 1

Parameter 1
Parameter 2...
: Indicates a reference relationship.

Figure 4-9 General Model of CSP+ File of CC-Link IF Field Network Connected Module

CLPA

BAP-C2008ENG-001-K
1-48

4.2.5.1 Structure of CSP+ file of remote I/O station
Figure 4-10 shows a model of the structure of a CSP+ file of a remote I/O station of a CC-Link IE Field
Network connected module. With a remote I/O station, the parts COMM_IF_INPUT,
COMM_IF_OUTPUT, BLOCK_INPUT, and BLOCK_OUTPUT are used.
The parts METHOD, MESSAGE, COMM_IF_PARAMETER, COMM_IF_COMMAND,BLOCK_PARAMETER, and BLOCK_COMMAND cannot be written with a remote I/O station. Further,for input/output as well, only remote input/output (RX, RY) is described.
FILE

FILE_INFODEVICEDEVICE_INFO

COMM_IFCOMM_IF_INFOBLOCK
BLOCK_INFO

COMM_IF_OUTPUTBLOCK_INPUT

RY0
RY1
RY2

Output contact 0
Output contact 1
Output contact 2

...

...

COMM_IF_INPUT
RX0
RX1
RX2

BLOCK_OUTPUT
Input contact 0
Input contact 1
Input contact 2

...

...

: Indicates a reference relationship.

Figure 4-10 Model of CSP+ File for CC-Link IE Field Network Connected Remote I/O
All remote I/O stations are not necessarily capable of mounting an input/output function. As shown in
Table 4-8, the mountable information is defined for each I/O type.

CLPA

BAP-C2008ENG-001-K
1-49

4.2.5.2 CSP+ file structure of remote device station, intelligent device station, and local station
The model for a remote device station, intelligent device station, and local station of a CC-Link IE Field
Network connected module is the same as the general model. Figure 4-11 shows a model of the CSP+
file.
Note that there is no need to describe references from all elements of the COMM_IF section to the
BLOCK session. Examples are described below.
(1) System area of CC-Link IE Field Network(2) Communication module dedicated parameter and command information of communication
module type module
For the parts COMM_IF_INPUT and COMM_IF_OUTPUT, the data that is refreshed in the cyclic area
and the data that is accessed by SLMP (referred to by a MESSAGE part) need to be described indifferent parts.
Further, while remote inputs/outputs that cannot be described exist for a CC-Link connected local
station, all remote inputs/outputs can be described for a CC-Link IE Field Network connected local
station.
(The fact that only the input/output information assigned to a local station is described in the parts
COMM_IF_OUTPUT and COMM_IF_INPUT holds true for CC-Link connected local stations as well.)
FILE

FILE_INFODEVICEDEVICE_INFO

COMM_IFCOMM_IF_INFO
COMM_IF_OUTPUT

...

RY0
RY1

BLOCK
BLOCK_INFOBLOCK_INPUT

RWw0
RWw1

Output contact 0
Output contact 1

...

...

COMM_IF_OUTPUT

Output area 0
Output area 1...

Output contact 0
Output contact 1...
Output area 0
Output area 1...

COMM_IF_INPUT
RX0
RX1
...

RWr0
RWr1

Input contact 0
Input contact 1...

Message 1...

MESSAGEBLOCK_OUTPUT

Input area 0
Input area 1...

Input contact 0
Input contact 1...

... ... ...

COMM_IF_INPUT

Input area 0
Input area 1...
COMM_IF_PARAMETERMETHODBLOCK_PARAMETER

Parameter 1

COMM_IF_COMMANDBLOCK_COMMAND

Command 1...

Command 1
Command 2

Parameter 10...

Parameter 10...

... ... ... ...

COMM_IF_PARAMETER...

Method 1

Parameter 1
Parameter 2...
: Indicates a reference relationship.

Figure 4-11 Model of CSP+ File of CC-Link IE Field Network Connected Remote Device Station,
Intelligent Device Station, and Local Station
CLPA

BAP-C2008ENG-001-K
1-50

4.2.5.3 CSP+ file structure when multiple COMM_IF sections are written
If communication specifications change when module operation settings are changed, we recommendthat you write a COMM_IF section for each operation setting. If, in this case, multiple COMM_IF
sections are written, an explanation of what is indicated by each COMM_IF section needs to be written
in COMMENT.
Such a scenario applies to a module in which the operation mode can be set to CC-Link compatiblemode (in which SLMP cannot be used), for example. In this example, as shown in Figure 4-12, the filedescribes a COMM_IF section in which SLMP is applicable, and a COMM_IF section in which SLMP
is not applicable (a COMM_IF section for CC-Link compatible mode).
To write multiple COMM_IF sections in CC-Link IE TSN, use conventions described in Section 4.2.8.2.
FILE

FILE_INFODEVICEDEVICE_INFO

COMM_IFSLMP applicable mode

BLOCK
COMM_IF_INFO
COMM_IF_OUTPUTBLOCK_INFO

Output contact 0
Output contact 1

BLOCK_INPUT...

Output area 0
Output area 1

COMM_IF_INPUT

Output area 10...

... ... ...

Input area 0
Input area 1

METHOD

COMM_IF_PARAMETER

Parameter 1

COMM_IF_COMMAND
Command 1

BLOCK_OUTPUT
Input contact 0
Input contact 1...

... ... ... ...

...

Method 1...

Message 1...

Input contact 0
Input contact 1

...

...

MESSAGE

Output contact 0
Output contact 1...

Output area 0
Output area 1

Input area 0
Input area 1

...

...

Input area 10...

CC-Link compatible mode

COMM_IF_INFO
COMM_IF_OUTPUT

RY0
RY1

...
RWw0
RWw1

Parameter 1

...

...

Parameter 10...

COMM_IF_INPUTRX0RX1

BLOCK_PARAMETER

...
RWr0
RWr1

COMM_IF_PARAMETER

Command 10...

Method 1

Command 1

...

...

METHODBLOCK_COMMAND...

... ... ... ...

Parameter 10

COMM_IF_COMMAND
Command 10...
: Indicates a reference relationship.

Figure 4-12 Writing Multiple COMM_IF Sections in a CC-Link IE Field Network

CLPA

BAP-C2008ENG-001-K
1-51

4.2.6In the case of the CC-Link IE Field Network Safety Communication Function Support Unit
In the case of the CC-Link IE Field Network Safety Communication Function Support Unit, it isnecessary to write specific information such as special device names and elements. In the case of the
Safety Communication Function Support Unit, in addition to the description of the unit of the normal
Field Network, the following descriptions are also conducted.
(1) COMM_IF_INFO Part safety communication function support element (See Section 5.3.1)(2) CONDITION Part (See Section 4.3.1.7)(3) Safety communication function parameters (See Section 5.5.5)(4) Messages for safety parameter writing (See Section 5.5.6)

CLPA

BAP-C2008ENG-001-K
1-52

4.2.7

CSP+ file structure of Ethernet connection unit
Figure 4-13 shows a general model of a CSP+ file of a unit connected to the Ethernet.
For the Ethernet connection unit, parameters can be described for reading and writing parameters of
the unit by specifying parameter IDs. When doing so, since specific SLMP commands are preparedand used to perform communication, messages are not described.
(1) COMM_IF section output and BLOCK section input
Output as viewed from the communication function side (same as output as viewed from themaster station) is described in the COMM_IF_OUTPUT part of the COMM_IF section, and in the
BLOCK_INPUT part of the BLOCK section.
The direction of the input/output of the BLOCK section is the same as the input/output from thecontrol function side to the communication function side. As a result, the output from thecommunication function is the same as the input to the control function side. Thus, the
BLOCK_INPUT part corresponds to the COMM_IF_OUTPUT part.
The remote output (RY) and remote register (RWw) information is described in each element of
the COMM_IF_OUTPUT part, and the module output contact and output area information as well
as module set values, flags, and the like are described in each element of the BLOCK_INPUT
part.
There is no need to describe data that is not mounted or used by the module. However, theaddresses of remote outputs and remote registers for which corresponding elements are notdescribed in cyclic transmission areas that can be used based on module settings indicate thatthe areas are not accessible by the sequence program and utility software. If you want to clearly
indicate the reason why an area is not accessible, describe the non-accessible element with thereason written in the name.
Each element of the COMM_IF_OUTPUT part refers to the elements of the associated
BLOCK_INPUT part.
Non-associated elements may be present.
(2) COMM_IF section input and BLOCK section output
Input as viewed from the communication function side (same as input as viewed from the masterstation) is described in the COMM_IF_INPUT part of the COMM_IF section, and in the
BLOCK_OUTPUT part of the BLOCK section.
The input to the communication function side is the output from the control function side. Thus,
the BLOCK_OUTPUT part corresponds to the COMM_IF_INPUT part.
The remote input (RX) and remote register (RWr) information is described in each element of the
COMM_IF_INPUT part, and the module input contact and input area information as well as
module present values, status information, and the like are described in each element of the
BLOCK_OUTPUT part.
There is no need to describe data that is not mounted or used by the module. However, theaddresses of remote inputs and remote registers for which corresponding elements are notdescribed in cyclic transmission areas that can be used based on module settings indicate thatthe areas are not accessible by the sequence program and utility software. If you want to clearly
indicate the reason why an area is not accessible, describe the non-accessible element with thereason written in the name.
Each element of the COMM_IF_INPUT part refers to the elements of the associated
BLOCK_OUTPUT part.
Non-associated elements may be present.
(3) Parameter
Parameters that perform read/write can be written by specifying parameter ID.
Parameters are written in association by writing them as elements of COMM_IF_PARAMETER
part and BLOCK_PARAMETER part, and referring elements of BLOCK_PARAMETER part fromelements of COMM_IF_PARAMETER part. (See Section 5.5.7.)(4) Command
Commands are described in the COMM_IF_COMMAND part of the COMM_IF section, and the
BLOCK_COMMAND part of the BLOCK section.
The elements of the METHOD part refer to the elements of the COMM_IF_COMMAND part, andthe elements of the COMM_IF_COMMAND part refer to the elements of the BLOCK_COMMAND
part. Thus, each element of the COMM_IF_COMMAND part and BLOCK_COMMAND part isassociated.

CLPA

BAP-C2008ENG-001-K
1-53

FILE

FILE_INFODEVICEDEVICE_INFO

COMM_IFCOMM_IF_INFOBLOCK
BLOCK_INFO

COMM_IF_OUTPUTBLOCK_INPUT

RY0
RY1

Output contact 0
Output contact1

...

...

RWw0
RWw1

Output area 0
Output area 1

...

...

COMM_IF_OUTPUTBLOCK_INPUT

RX0
RX1

Input contact 0
Input contact 1

...

...

RWr0
RWr1

Input area 0
Input area 1

...

...

COMM_IF_PARAMETERBLOCK_PARAMETER

Parameter 1

Parameter 1

...

...

COMM_IF_COMMANDBLOCK_COMMAND

Command 1

Command 1
Indicates a reference relationship.

Figure 4-13 General Model of CSP+ File for Ethernet Connection Unit
* At the time of version 2.1, only one type of command (status code acquisition command) is defined.

CLPA

BAP-C2008ENG-001-K
1-54

4.2.7.1 CSP+ file structure when multiple COMM_IF sections are written
When the number of occupied stations (1 to 64) is variable, a COMM_IF section needs to be written
for each setting. With the utility software, only the settings described in COMM_IF sections need to beacknowledged.
If the communication specifications change as a result of changes in module operation settings,
regardless if the above settings remain the same, we recommend that you write a COMM_IF section
for each operation setting. In such a case, if multiple COMM_IF sections are written, the content
indicated by each COMM_IF section needs to be described in the COMMENT item.
Note that, if the module function does not change even if multiple COMM_IF sections are written, theassociations from the multiple COMM_IF sections to a common BLOCK section are to be described.
Figure 4-14 shows the section configuration in a case where the number of occupied stations isselectable from the values 1 to 4.
FILE

FILE_INFODEVICEDEVICE_INFO

COMM_IF
1 occupied station

COMM_IF_INFOBLOCK
BLOCK_INFO

COMM_IF_OUTPUT

RY0
･･
･
RWw0
･･
･
COMM_IF_INPUT

RX0
･･
･
RWr0
･･
･
COMM_IF_PARAMETER

Parameter 1･･･

BLOCK_INPUT
Output contact 0･･･
Output area 0･･･

COMM_IF_COMMAND

Command 1･･････
2 occupied stations

COMM_IF_INFO
COMM_IF_OUTPUTBLOCK_OUTPUT･･･

Input contact 0

COMM_IF_INPUT

･･
･

･･
･
Input area 0･･･

COMM_IF_PARAMETER･･･
COMM_IF_COMMAND･･･
3 occupied stations

COMM_IF_INFO
COMM_IF_OUTPUT･･･

BLOCK_PARAMETER

COMM_IF_INPUT

Parameter 1
･･
･

･･
･
COMM_IF_PARAMETER･･･
COMM_IF_COMMAND･･･
4 occupied stations

COMM_IF_INFO
COMM_IF_OUTPUT･･･

BLOCK_COMMAND

Command 1･･･

COMM_IF_INPUT･･･
COMM_IF_PARAMETER･･･
COMM_IF_COMMAND･･･

Indicates a reference
relationship.

Figure 4-14 Description Example of Multiple COMM_IF Sections with Ethernet Connection Unit

CLPA

BAP-C2008ENG-001-K
1-55

4.2.8

CSP+ file structure of the CC-Link IE TSN connection unit
Figure 4-15 shows a general model of a CSP+ file of the CC-Link IE TSN connection unit.
With a CC-Link IE TSN connection unit, you can write messages for accessing inputs, outputs,
parameters, and commands using parameter setup, command execution, and SLMP using the same
methods as with the CC-Link IE Field Network connection unit. There are no differences in thereference relationship with the contents of each part described in the COMM_IF and BLOCK sections
from that with a CC-Link IE Field Network connected module (see Section 4.2.5). In the case of CAN
compatible devices, the object dictionary information needs to be written and added as a CSV file. (Fordetails on creating an object dictionary file, see Section 4.2.8.4.)
FILE

FILE_INFODEVICE
COMM_IFDEVICE_INFO
COMM_IF_INFO
COMM_IF_OUTPUT

RY0
RY1
･･･
RWw0
RWw1
･･･
COMM_IF_OUTPUT
Output contact 0
Output contact 1

BLOCK
BLOCK_INFOBLOCK_INPUT
Output contact 0
Output contact 1･･･
Output area 0
Output area 1･･････
Output area 0
Output area 1･･･

COMM_IF_INPUT
RX0
RX1
･･･
RWr0
RWr1
･･･
MESSAGE

Message 1
･･･
･･･
･･･

COMM_IF_INPUT
Input contact 0
Input contact 1

BLOCK_OUTPUT
Input contact 0
Input contact 1･･･
Input area 0
Input area 1･･････
Input area 0
Input area 1･･･
COMM_IF_PARAMETERMETHOD

Method 1
･･･
･･･
･･･
･･･

Parameter 1
Parameter 2
COMM_IF_PARAMETER

Parameter 10･･･
COMM_IF_COMMAND

Command 1
Command 2･･･

BLOCK_PARAMETER

Parameter 1･･･
Parameter 10･･･
BLOCK_COMMAND

Command 1･･･: Indicates thereference
relationship.

Object dictionary CSV fileFigure 4-15 General Model of CSP+ File of CC-Link IE TSN Connection Unit

CLPA

BAP-C2008ENG-001-K
1-56

4.2.8.1 CSP+ file structure of a local station (slave station with the local station function enabled)
The model of a local station (slave station with the local station function enabled) of a CC-Link IE TSN
connection unit is the same as that of a general model. (See Figure 4-15.)
With regard to the descriptions of CC-Link IE TSN connected local stations, a local station is capableof acquiring the values output by all stations in the same manner as a master station, but only the
input/output information assigned to the location station is written in the COMM_IF_INPUT and
COMM_IF_OUTPUT parts.

4.2.8.2 Devices for which station mode can be changed
In the case of devices for which station mode can be changed, set different COMM_IF sections forevery operation setting [Required]. (For details on the station mode, see CC-Link IE TSNSpecifications (Overview) BAP-C2011ENG-001.)
Information on the station mode is written in the StationMode element (Section 5.3.1.3(53)) of the
COMM_IF_INFO part. [Required] Figure 4-16 shows a description image of devices for which
each mode can be switched.

If the device specifications do not change even though the information of station mode ischanged, create one common BLOCK section and set the BLOCK section to be referred frommultiple COMM_IF sections.
When multiple COMM_IF sections are set and the device can acquire the error related
information, matching descriptions of each COMM_IF section is required. For details, see Section
5.5.10.1.
For switching the mode with other than CC-Link IE TSN, use the conventions described in Section
4.2.5.3.


FILE

FILE_INFODEVICE
COMM_IF(IO mode)

DEVICE_INFO
COMM_IF_INFOBLOCK

BLOCK_INFO

COMM_IF_OUTPUT
RY0

BLOCK_INPUT
RY0

RY1
･･
･

RY1
･･
･

METHOD

COMM_IF_COMMANDBLOCK_COMMANDMETHOD1･･･

Command 1･･･

Command 1
･･
･
･･
･
･･
･

COMM_IF(Motion mode)

COMM_IF_INFO
COMM_IF_OUTPUT
RY0
RY1
･･
･

METHOD

COMM_IF_OUTPUT

METHOD1
･･
･
･･
･

RY0
RY1
･･
･
COMM_IF_COMMANDMESSAGEMESSAGE1･･･

Command 1
･･
･
･･
･
･･
･

Figure 4-16 Example of CC-Link IE TSN Devices for which Station Mode Can Be Changed

CLPA

BAP-C2008ENG-001-K
1-57

4.2.8.3 Description specifications in common between devices
In the case of devices that can execute the functions described in this section of CC-Link IE TSN, theCOMM_IF_COMMAND part needs to follow the description method using MESSAGE.
[1] Acquiring error related information
In the case of devices that can acquire error codes and error history information using SNMP, use
the MESSAGE part for the diagnostics code information for description. For details, see Section
5.5.10.1.
[2] MESSAGE for slave station parameter automatic settingThis function automatically writes the parameters when a CC-Link IE TSN slave station isreconnected or introduced by turning on its power. Use MESSAGE for slave station parameter
automatic setting for description. For details, see Section 5.5.10.2.

4.2.8.4 Object dictionary description specifications(1) Overview
Various data such as control parameters and instruction values held by a CAN compatible deviceof a CC-Link IE TSN connection unit are treated as objects composed of Index, SubIndex, andothers of the description details. A collection of these objects is an object dictionary.
(2) CSV file description specifications
Describe the object dictionary in a CSV file which is different from the CSP+ file. For details on
the configuration in the compressed file, see Section 4.1.2.
For the description method and details of the CSV file, see Chapter 8.

4.2.9

In the case of the CC-Link IE TSN safety communication function support unit
In the case of the CC-Link IE TSN safety communication function support unit, it is necessary to write
specific information such as special device names and elements. For a safety communication function
support unit, describe the following in addition to the descriptions of a normal CC-Link IE TSN unit.
(1) CC-Link IE TSN safety communication function compatible elements of COMM_IF_INFO part(see Section 5.3.1)(2) Parameters of safety communication function (see Section 5.5.10.3)(3) Messages for writing safety parameters (see Section 5.5.10.4)

CLPA

BAP-C2008ENG-001-K
1-58

4.2.10

CSP+ file structure of the main module and extension modules over CC-Link IE TSN

Figure 4-17 shows a general model of CSP+ files for the main module and extension modules, which are
CC-Link IE TSN connection units.
Device model of the 1st extension module

Device model of the main module

DEVICEDEVICE_INFO

COMM_IFBLOCK

COMM_IF_INFOBLOCK_INFO

COMM_IF_OUTPUTBLOCK_INPUTFor main_1

For main_1

For main_2

For main_2

･
･
･

･
･
･

For extension 1_ 1

For extension 1_ 1

For extension 1_ 2

For extension 1_ 2

･
･
･

･
･
･

For extension 2_ 1

For extension 2_ 1

･
･
･

･
･
･

COMM_IF_
INPUT

BLOCK
_OUTPUT

For main_1

For main_1

For main_2

For main_2

･
･
･

･
･
･

For extension 1_ 1

For extension 1_ 1

For extension 1_ 2

For extension 1_ 2

･
･
･

･
･
･

For extension 2_ 1

For extension 2_ 1

･
･
･

･
･
･

(The description about CC-Link
IE TSN connection units (single
module) is omitted.)

DEVICEDEVICE_INFODEVICE_INF
DEVICEDEVICE_INF
BLOCK
COMM_IF O
DEVICE COMM_I
O
BLOCK
COMM_IF_INFOBLOCK_INFO
COMM_ICOMM_IF_IN
BLOCK_INF
F
BLOCK
COMM_IF_IN
BLOCK_INF
FFO
O
COMM_IF_FOO BLOCKCOMM_IF_BLOCKOUTPUT_INPUT
COMM_IF_
BLOCK
Exte nsion output
Exte nsion output
OUTPUT_INPUT
1
1
Extension
Extension
OUTPUT_INPUT
Exte nsion output
Exte nsion output
Extension
Extension
output 21
output 21
Extension
Extension
outputoutputExtension
Extension
outputoutput･1 2･1 2
outputoutput
･ ･2
･ ･2
･ ･
･ ･
COMM_IF_･･ BLOCKCOMM_IF_
BLOCK
INPUT
_OUTPUTCOMM_IF_BLOCKOUTPUT_INPUT
Exte nsion input 1
Exte nsion input 1
Extension
Extension
OUTPUT_INPUT
Exte
nsion
input
2
Exte nsion input 2
Extension
Extension
input 1input
1Extension
Extension
input
1
input
1
Extension
Extension
input
2
input
･
･ 2
input
input
2
･ 2
･
･
･
･ ･
･ ･
･COMM_IF_･ BLOCK_PARAMETERPARAMETER
COMM_IF_BLOCK_
COMM_IF_BLOCK_PARAMETE
PARAMETE
Extension Prm1
Extension Prm1
Extension
Extension
PARAMETE
PARAMETE
R
R
Extension
Prm2
Extension Prm2
MESSAGE Extension
Extension
RPrm1
RPrm1
Extension
Extension
MESSAGE
Prm1
Prm1
Extension
Extension
Prm2
Prm2
･
･
MESSAGE
Extension 1
Prm2
Prm2
･
･ ･
･
Extension･ ･･ ･Extension
2
Extension
1
Extension･･BLOCK_
1Extension
3
COMM_IF_
Extension
2 ･Extension
COMM_IF_BLOCK_COMMAND
COMMAND
2 ･ 3･･
Extension
COMM_IF_BLOCK_COMMAND
COMMAND
3･ ･Extension
Extension
COMMAND
COMMAND
Exte nsion Cmd1
Exte nsion Cmd1
･ ･
Extension
Extension
Cmd1
Cmd1
Extension
Extension
Exte nsion Cmd2
Exte nsion Cmd2
･
Cmd1
Cmd1
Extension
Extension
Cmd2
Cmd2
･
･
Cmd2
Cmd2
･ ･
･ ･
･ ･
･ ･
･
･
･
･
･

･
･
･

･
･
･

･
･
･

･
･
･

･
･
･

･
･
･

･
･
･

Figure 4-17 General Model of CSP+ Files for the CC-Link IE TSN Main Module and Extension Modules

CLPA

BAP-C2008ENG-001-K
1-59

In the CSP+ file for the main module, information of which inputs (RX, RWr) and which outputs (RY, RWw)
can be used in which extension module is described in addition to the descriptions of the single module(see Section 4.2.8 "CSP+ file structure of the CC-Link IE TSN connection unit").
In the CSP+ file for extension modules, messages for accessing parameters and commands using the
SLMP can be described in the same manner as the single module. Note that the parameter settings andthe command execution using a method cannot be described. The following describe the description
methods related to the input and output.
(1) COMM_IF section output and BLOCK section input
Output via the main module over CC-Link IE TSN (same as output as viewed from the master station)
is described in the COMM_IF_OUTPUT part of the COMM_IF section, and in the BLOCK_INPUT partof the BLOCK section.
Details of how the remote output (RY) and remote register (RWw) information, assigned to the n-th
extension module is used by the main module, are described in each element of the
COMM_IF_OUTPUT part. The module output contact and output area information as well as module
set values, flags, and the like are described in each element of the BLOCK_INPUT part.
(2) COMM_IF section input and BLOCK section output
Input to a module via the main module over CC-Link IE TSN (same as input as viewed from themaster station) is described in the COMM_IF_INPUT part of the COMM_IF section, and in the
BLOCK_OUTPUT part of the BLOCK section.
Details of how the remote input (RX) and remote register (RWr) information, assigned to the n-th
extension module is used by the main module, are described in each element of the COMM_IF_INPUT
part. The module input contact and input area information as well as module present values, status
information, and the like are described in each element of the BLOCK_OUTPUT part.

For details on the specific descriptions for the main module and extension modules, see Section 5.5.10.5"Parts and elements related to the main module and extension modules".

CLPA

BAP-C2008ENG-001-K
1-60

4.2.11

CSP+ file structure of the integrated main/extension module unit over CC-Link IE TSN

Figure 4-18 shows a general model of CSP+ files for the integrated main/extension module unit, which is a
CC-Link IE TSN connection unit.

CSP+ file of the main module section
DEVICE
COMM_IF

CSP+ file of the extension module section
DEVICEDEVICE_INFOBLOCK

COMM_IF_INFOBLOCK_INFOInformation
unrelated toextension CSP+
(Such asdiagnostics)

Information
unrelated toextension CSP+
(Such asdiagnostics)

COMM_IFDEVICE_INFOBLOCK

COMM_IF_INFOBLOCK_INFOError related
information

Error related
information
Objectdictionary.csv

Figure 4-18 General Model of CSP+ Files for Integrated Main/Extension Module Unit
One CSP+ file is created each for the main module section and the extension module section. The main
module section operates assuming that the number of extension modules described in the maximum
number of extension modules in the DEVICE_INFO part (EXTExtensionMax) is always being connected(or integrated in other words).
For the following reasons, the integrated main/extension module unit does not use the INPUT, OUTPUT,
PARAMETER, and METHOD description specifications. The MESSAGE and COMMAND description
specifications can only be used for error related information.
• Normal cyclic transmission should not be performed.
• Information related to PDO communication should be complete with the description in COMM_IF_INFO.
• Parameters and commands related to PDOs should not be described in CSP+.
For details on the specific descriptions for the main module section and extension module section in the
integrated main/extension module unit, see Section 5.5.10.6 "Parts and elements related to the integrated
main/extension module unit".

CLPA

BAP-C2008ENG-001-K
1-61

4.2.12Structure of sections, parts, and elements of a CSP+ fileFigure 4-19 to Figure 4-22 show images of the structures of each section written in a CSP+ file, in
XML format.

Structure of FILE section<p:file label="FileSection">
Structure of part<p:fileInfo label="FileInfo">
Structure of element<p:fileInfoMember label="CreateDate"><p:label2><p:item> File creation date </p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item> File creation date </p:item></p:name><p:datatype><p:item>STRING_FLEX(10)</p:item></p:datatype><p:data><p:item>2011/12/01</p:item></p:data></p:fileInfoMember>:</p:fileInfo></p:file>
Figure 4-19 Structure of FILE Section

Structure of DEVICE section<p:device label="DeviceSection">
Structure of part<p:deviceInfo label="DeviceInfo">
Structure of element<p:deviceInfoMember label="VendorName"><p:label2><p:item> Vendor name </p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item> Vendor name </p:item></p:name><p:datatype><p:item>STRING_FLEX(64)</p:item></p:datatype><p:data><p:item> CC-Link Association </p:item></p:data></p:deviceInfoMember>:</p:deviceInfo></p:device>
Figure 4-20 Structure of DEVICE Section

CLPA

BAP-C2008ENG-001-K
1-62

Structure of COMM_IF section<p:commIf label="CommIfSection">
Structure of part<p:commIfOutput label="CommIfOutput">
Structure of element<p:commIfInputMember label="CH1_digital_output_val"><p:label2><p:item>CH1_ Digital output value </p:item></p:label2><p:name><p:item>CH1 Digital output value </p:item></p:name><p:datatype><p:item>INT16</p:item></p:datatype><p:access><p:item>RF_IN</p:item></p:access><p:assign><p:item>RWr0</p:item></p:assign><p:ref><p:item>BlockSection.BlockOutput.CH1_digital_output_val</p:item></p:ref><p:comment><p:item> Enable if remote READY and CH1 A/D conversion completed flag are ON </p:item></p:comment></p:commIfInputMember>:</p: commIfOutput>:</p:commIf>
Figure 4-21 Structure of COMM_IF Section

Structure of BLOCK section<p:block label="BlockSection">
Structure of part<p:blockOutput label="BlockOutput">
Structure of element<p:blockOutputMember label="CH1_digital_output_val"><p:label2><p:item>CH1_ Digital output value </p:item></p:label2><p:name><p:item>CH1 Digital output value </p:item></p:name><p:datatype><p:item>INT16</p:item></p:datatype><p:default><p:item>0</p:item></p:default><p:access><p:item>RF_OUT</p:item></p:access><p:comment><p:item> Enable if remote READY and CH1 A/D conversion completed flag are ON </p:item></p:comment></p:blockOutputMember>:</p:blockOutput>:</p:block>Figure 4-22 Structure of BLOCK Section

CLPA

BAP-C2008ENG-001-K
1-63

4.3

SCP+ File Description Specifications
The following describes the conventions that are common to each section.

Item conventions

4.3.1

This section describes item conventions.
(1) Describe all items other than LABEL as an "XML element." Describe a LABEL item as an "attributeof an XML element."(2) Describe a LABEL item as information that identifies sections and parts other than elements.
(3) Describe a COMMENT item as comment information that identifies sections and parts other thanelements.
(4) If an item has an arbitrary description and does not require value setup, do not describe anything
following the item tags.
(5) If you want to describe a reference to a STRUCT part, describe the reference as an element of"structRefItem." The following shows an example of a case where reference to a STRUCT part isdescribed in a DATATYPE item.
(Example: <p:datatype><p:structRefItem>STMonitorCode1and2</p:structRefItem></p:datatype>)
The items DEFAULT, RANGE, MIN_INC, ENG_UNIT, and REF cannot be written in an element ofa structure type (in an element where the DATATYPE is STRUCT).
(6) If you want to describe a reference to an ENUM part, describe the reference as an element of"enumRefItem." The following shows an example of a case where reference to a ENUM part isdescribed in a RANGE item.
(Example: <p:range><p:enumRefItem>enumFaultDefinition</p:enumRefItem></p:range>)(7) If you want to describe a reference to a RESULTx item of a CONDITION part, describe thereference as an element of "conditionRefItem". The following shows an example of a case wherereference to a RESULT1 item of a CONDITION part is described in an ACCESS item.
(Example:<p:access><p:conditionRefItem>C_AvgTimeCount.RESULT1</p:conditionRefItem></p:access>)(8) Describe all items other than the above three cases and LABEL as an element of "item". The
following shows an example of a case where a NAME item is described.
(Example: <name><item> Product name </item></name>)(9) The 6 items LABEL2, NAME, CATEGORY, DATA, ENG_UNIT, and COMMENT require modification
with support for other languages.
The following shows item description examples.
Description example of element that uses "item" only
If common information such as STRUCT is not used, describe the element as shown below. (Thefollowing example is a case where the value of the item REF is"CH2.BlockParamter.AvgOrSample".)<ref><item>Ch2.BlockParamter.AvgOrSample</item></ref>

Description example of item that uses structure information (STRUCT)
If the value of the item DATATYPE is structure information, describe structRefItem. The followingshows a description example.
<datatype><structRefItem>Prm_Struct</structRefItem></datatype>Description example of item that uses an option list (ENUM)
If the value of the item RANGE is an option list, describe enumRefItem. The following shows adescription example.
<range><enumRefItem>enumFaultDefinition</enumRefItem></range>Description example of a case where a set of values is described in an item
If you want to describe multiple values in a single item, describe the values by dividing the item
into multiple items. The following shows a description example.
<data>CLPA

BAP-C2008ENG-001-K
1-64

<item>11:DC input</item><item>12:DC input</item></data>4.3.1.1 ACCESS conventions
An ACCESS item describes access using the values shown in Table 4-9, according to part type.
For parameter and command argument elements, write "R," "W," or "RW," which indicates thereading/writing attribute.
Write "RF" for input and output elements capable of refresh by cyclic communication, etc.
Further, write "NA" for elements that are not accessible, regardless of the parameter or input/output,
and omit the description if the element does not require access setup. If setup is omitted, access is inaccordance with the access attribute of the element set as a reference. However, when setup isomitted in the parts BLOCK_INPUT and BLOCK_OUTPUT, the setup is regarded as writable(BLOCK_INPUT part) or readable (BLOCK_OUTPUT part).
ACCESS cannot be written in an element of a STRUCT part. The ACCESS value of an element of a
STRUCT type of the reference source (an element where the DATATYPE is STRUCT) is applied to allelements within the STRUCT part. Further, even if ACCESS is written in an element referred to by a
REF item from each element of the STRUCT part, that value is not used.
Table 4-9 ACCESS Attribute List

No.

Value

Meaning

1.
2.
3.
4.

"R"
"W"
"RW"
"RF"

5.

"NA"

6.

No
item

Readable
Writable
Readable and writable
Auto refreshable
Element not accessible(Used with elementsthat are not accessible
according toconditions, etc.)
No setting (Used whensettings are
determined according
to the access attributeof the element of thereference)

Settable Part Type : Settable : Not settable
COMM_IF_ BLOCK_PARAMETERPARAMETER COMMAND_ARGUMENT

COMM_IF_INPUTCOMM_IF_OUTPUTBLOCK_INPUTBLOCK_OUTPUT





































4.3.1.2 ARGUMENT conventions
An ARGUMENT item describes label references for a COMMAND_ARGUMENT part (see Section
5.3.10) in order to indicate the arguments to be used by the element. For label reference conventions,
see Section 4.3.4.

4.3.1.3 ASSIGN conventions
An ASSIGN item describes codes and addresses assigned to the element. This item may be omitted if
not needed. For the method used to express the addresses for module specific resources (moduleinternal memory, internal register, etc.),refer to the specifications of the module.
The remote input, remote output, and remote register addresses of CC-Link, the CC-Link IE Field
Network, and CC-Link IE TSN are expressed as follows.



CLPA

Write the prefixes which indicate address type as follows: Remote input: RX
 Remote output: RY
 Remote register (write area): RWw
 Remote register (read area): RWr* The upper case and lower case letters are fixed as shown above. (Example: "Rx0" is not
permitted.)
The description of the address type is standardized to the type as viewed from the mastermodule.
BAP-C2008ENG-001-K
1-65

For example, while the meanings of RX and RY of a local station are the reverse of the meanings
of a remote I/O in CC-Link specifications, write RX and RWr for the address (COMM_IF_INPUT)
that is to send data to the master station, and RY and RWw for the address(COMM_IF_OUTPUT) that is to receive data from the master station.

CLPA

BAP-C2008ENG-001-K
1-66

Write the address number as described below.
 Add the number (hexadecimal) after the prefix (example: RX12, RYC, RWw1, RWrA).
 While n, which indicates an address assigned to the master module by station number setup,
is sometimes written with protocol specifications and the like, such as RXn9, n must not be
written in profile descriptions.
 If the initial value of the number is any value between A to F, you can simply add 0 or 1
before that number (example: RYC can be written as RY0C, and RXD2 can be written as
RX0D2).

When you want to specify a bit register within a word register (remote register), enter a dot (".")
after the string indicating the word register, and write the bit register number in hexadecimalformat (example: bit 7 of RWw3 is written as "RWw3.7").
The letters A to F, which indicate hexadecimal numbers, can only be used in upper case. Lowercase is not permitted.
The size of the area used by the element is regulated by data type.

Expressions that extend across multiple word devices cannot be written (example: a data type of
UINT8, an ASSIGN item of W0.A). Note, however, that such an expression can be written if theelement is assigned to each one of the multiple word devices (example: a data type of UINT32,
and an ASSIGN item of W1 are acceptable).
When the ASSIGN item is written in CC-Link IE TSN, the following restrictions apply.
 Duplication of the ASSIGN items is prohibited among the elements in the same section.
1) Duplication among all elements referenced from TARGET of MESSAGE for parameter
writing is prohibited.
 For a MESSAGE part where MESSAGE_TYPE item for MESSAGE for parameter
writing is PARAMETER and reference to VALUE is written in REQUEST_DATA
2) Duplication among all elements referenced from TARGET of MESSAGE for slave station
parameter auto setting (see Section 5.5.10.2) is prohibited.
The ASSIGN items can be duplicated among the above 1) and 2) elements. However, in thatcase, not only the ASSIGN items but also values of all items must be the same.
[Example]
When CommIfParameter1 part is referred in the TARGET item of MESSAGE forparameter writing and CommIfParameter2 part is referred in TARGET of MESSAGE forslave station parameter auto setting, the ASSIGN in the element of CommIfParameter1
and element of CommIfParameter2 can be duplicated. However, these are only different
in writing method and the writing target is the same. When the NAME or others aredifferent, the engineering tool users utilizing CSP+ may misunderstand, therefore, write
same items to display the same in the parameter writing screen and parameter auto
setting screen.
Further, an address number can also be used to specify a memory number during access via SLMP. In
such a case, for the ASSIGN item, be sure to write an appropriate value that can be used by the
REQUEST_DATA item since the ASSIGN item is referred to by the REQUEST_DATA item (seeSection 4.3.1.35).


4.3.1.4 CATEGORY conventions
A CATEGORY item describes the group name with which the element is affiliated. For elements thatyou want to arrange in the same group, write the same group name in the CATEGORY item. If theelement is not to be categorized, this item can be omitted.
When other languages are supported, write this label name in keeping with the descriptions of the
LANGUAGE element and FILE_INFO part of the FILE section.

4.3.1.5 CODE conventions
A CODE item describes the value that identifies an element of the part ENUM (see Section 5.3.9.3).
The CODE item also allows you to set a value that is out of range for the DATATYPE item (see Section
4.3.1.10) of an element that uses the part ENUM. As a result, the same ENUM part can be madecommon to elements of DATATYPE items having different value ranges.
Integers (decimal/hexadecimal) can be written in CODE items.

CLPA

BAP-C2008ENG-001-K
1-67

4.3.1.6 COMMENT conventions
A COMMENT item describes information such as the element itself, the meaning of each value, andusage precautionary points, using any string. Utility software uses the COMMENT item whendisplaying the data as additional information on the screen. This item may be omitted when notneeded.
When other languages are supported, write this label name in keeping with the descriptions of the
LANGUAGE element and FILE_INFO part of the FILE section.
The following describes the precautions to follow when writing a COMMENT.
(1) When describing the value of an element
When you want to describe a value of an element, describe the value along with the data type ofthe element. For example, a comment that is to indicate a value of an element handled in decimalformat, such as UINT16, is written in decimal format, and a comment that is to indicate a value sothat it is handled in hexadecimal format, such as WORD, is written in hexadecimal format (with"0x" at the start of the value). Further, for methods and messages, describe the meaning of eachvalue that is to be read and written, the meaning of the value of the error register, and the like, as
needed.
(2) When describing the value of an element in which the item MIN_INC is described
When describing in a comment the value of an element in which the item MIN_INC is described,
describe the value based on one of the following:[1]

Describe the value based on the value prior to calculation by the item MIN_INC.

[2] Describe the value based on the unit and setup specified in the item ENG_UNIT.
For example, if you want to write a comment for an element in which the RANGE item is [0,5000],
the MIN_INC item is 0.01, and the ENG_UNIT item is %, either write "Set 2500 or higher whenfunction A is used" using the description method of 1 above, or write "Set the value to 25% orhigher when function A is used" using the description method of 2 above. Note, however, that thedescription method of 1 should always be used for an element for which the utility software
cannot express the item MIN_INC or ENG_UNIT (in a case where "NA" is written for the item
ENG_UNIT or MIN_INC of an element of a COMM_IF section serving as a reference source).
(3) When describing a parameter, method, or message that is potentially not applicable, dependingon the device version
For a parameter, method, or message that is potentially not applicable with older devices, werecommend that you describe the applicable (or non-applicable) version information in the
COMMENT item.
(4) When describing multiple types of comments for one element
Basically, describe a comment for one element with one item. However, in a part such as ENUM
(see Section 5.3.9), which has the specification in which comments with multiple meanings canbe described for one element, multiple comments can be described. When multiple comments
can be described, the meaning of each comment is clearly specified in the specification.
[Note] The comments can be described only in CC-Link IE TSN.

4.3.1.7 Conventions of CONDITIONx
Write in CONDITION part, and write the range of conditions in order to conditionally determine thevalue of elements referenced from item CONDITIONXVARIABLE. For detailed conventions, see
Section 5.4.9.
(1) Use with RESULTx (See Section 4.3.1.41) in the conditionMember division of CONDITION part(See Section 5.4.9).
(2) A maximum of 32 CONDITIONx items can be written in 1 conditionMember division.

CLPA

BAP-C2008ENG-001-K
1-68

4.3.1.8 Conventions of CONDITIONXVARIABLE
Write in CONDITION parts, and write references to elements used in conditional determination. For
detailed conventions, see Section 5.4.9.
(1) Use in the conditionVariable division of CONDITION part (See Section 5.4.9).
(2) A maximum of 32 CONDITIONXVARIABLE items can be written in 1 conditionVariable division.

4.3.1.9 DATA conventions
A DATA item describes the contents of the element. Describable values are in accordance with thespecifications of the element defined in the parts FILE_INFO, DEVICE_INFO, COMM_IF_INFO, and
BLOCK_INFO. If not clearly defined, the description range is equivalent to that for the DATATYPE itemof the element. For details, see Sections 5.1.1.3, 5.2.1.3, 5.3.1.3, and 5.4.1.3.
When other languages are supported, write this label name in keeping with the descriptions of the
LANGUAGE element and FILE_INFO part of the FILE section. For CC-Link IE TSN, the specificelement of COMM_IF_INFO part can be described in array type. Place the value in brackets (seeSection 4.3.3) and describe multiple contents of the element.
[Note] The description in which the value described between "<" and ">" can be used only in CC-Link
IE TSN.

4.3.1.10 DATATYPE conventions
A DATATYPE item describes the data type of the value corresponding to the element. The data typenot only indicates the type of the element, but also specifies the memory size occupied when theelement is assigned to a module as well. lists the data types that can be specified.
Excluding cases where reference is made to other elements using the REF item (see Section
4.3.1.30), DATATYPE may be omitted.

CLPA

BAP-C2008ENG-001-K
1-69

Data TypeBool

Bit string(Hexadecimal
expression)*2
Signedinteger(INT)(Decimal
expression)*2
Unsigned
integer(UINT)(Decimal
expression)*2
BCD integer(BCD)(Decimal
expression)*2

Real number(Decimal
expression)*2

String*3

Expression

Table 4-10 Data Type List
Description

BOOL

A bit that indicates the status of twoalternatives, such as ON and OFF

BYTE
WORD
DWORD

A bit array of 8 bits
A bit array of 16 bits
A bit array of 32 bits

BIT_STRINGx(x=2 to 15)

A bit array of x bits, where x is an
integer between 2 and 15

INT8
INT16
INT32
INTx
(x=2 to 15)
UINT8
UINT16
UINT32
UINTx(x=2 to 15)
BCD8
BCD16
BCD32
BCDx
(x=4,12)

A signed integer of 8 bits
A signed integer of 16 bits
A signed integer of 32 bits
A signed integer of x bits, where x is
an integer between 2 and 15
An unsigned integer of 8 bits
An unsigned integer of 16 bits
An unsigned integer of 32 bits
An unsigned integer of x bits, where x
is an integer between 2 and 15
An 8-bit BCD type integer
A 16-bit BCD type integer
A 32-bit BCD type integer
An x-bit BCD type integer, where x iseither 4 or 12

REAL

A 32-bit real number

LREAL

A 64-bit real number

STRING(x)(x = An integer
greater than orequal to 1)
STRING_U(x)(x = An integer
greater than orequal to 1)
Data type +"()" (Example:
INT8(),STRIN
G(10)())
STRUCT

Value Range
0 or 1
0: Indicates FALSE.
1: Indicates TRUE.(*4)
0x00 to 0xFF
0x0000 to 0xFFFF
0x00000000 to 0xFFFFFFFF
0x0 to 0x7FFF*(The maximum value differs
according to the number of bits of x.)-128 to 127-32768 to 32767-2147483648 to 2147483647-2x－1 to (2x-1-1 )0 to 255
0 to 65535
0 to 4294967295
0 to (2x-1)
0 to 99
0 to 9999
0 to 99999999
Positive integer of (x/4) digits-3.402823E+38 to -1.175494E38,0,1.175494E-38 to 3.402823+38(Number of significant digits: 7)-1.797693134862315E+308 to 2.225073858507202E-308,0,2.225073858507202E-308, to
1.797693134862315E+308(Number of significant digits: 15)

Indicates a string (alphanumericcharacters or symbols) that can be
expressed in ASCII code

The maximum value differs according
to the value of x.

Indicates a string based on Unicode(utf-8)The maximum value differs according
to the value of x.

Indicates a set type. Using a set typeThe range of the value of each set
enables enumerated descriptions of
Set*3
element is in accordance with themultiple sets of information for thedata type.
item DATA (see Section 4.3.1.9).
Structure type
Structure type*1
Shows a constant value. Used when
it is necessary to read/write constantsin METHODS and MESSAGES.
Cannot be used in FILE_INFO,"CONST"+" "DEVICE_INFO, BLOCK_INFO,+Data
COMM_IF_INFO (Even if CONST is
Type
Follows the data type written after
not written, the value of DATA shows
Constant Type [Ex]constants).
"CONST".
CONST INT8, Types that can be written in data
CONST
types in each part are the same as
WORD"
types that can be used alone without
writing CONST.
However, structural type cannot be
written.
*1: For a structure type, describe the details of the data structure using the part STRUCT (seeBAP-C2008ENG-001-K
CLPA
1-70

Section 5.3.8). This type cannot be used with all elements. Rather, it is only applicable to theelements of the parts COMM_IF_INPUT, COMM_IF_OUTPUT, COMM_IF_PARAMETER, andCOMMAND_ARGUMENT (it cannot be written with the parts of a BLOCK section other than theparts STRUCT and COMMAND_ARGUMENT). Further, the data size of a structure type ishandled in word units. Even if an offset for the number of bits is used up to F, the data size israised and handled in word units (example: the size is regarded as 3 even if the offset is used
only up to 2.4). Note, however, that, in a case where the size has been clearly defined as handledin bit units (see Section 4.3.1.42), an exception is made and the number of bits used is regarded
as the size (example: the number of bits is 36 when the offset is used up to 2.4).
The items DEFAULT, RANGE, MIN_INC, ENG_UNIT, and REF cannot be written in an element ofa structure type (in an element where the DATATYPE is STRUCT).
*2: The value of each item (such as DEFAULT, RANGE, COMMENT, etc.) of an element in which theitem DATATYPE is an integer type (INT, UINT, BCD) or real number type, is described using adecimal expression. The value of each item of an element in which the item DATATYPE is a bit
string type, such as WORD, must be written using a hexadecimal expression (written with "0x" atthe start of the value). Note that, when you want to write a hexadecimal value, we recommendthat you do not omit high-order zeros in keeping with the data size. (If the type is WORD, werecommend that you do not write 0x3F, but rather 0x003F.)*3: Not applicable to any parts other than FILE_INFO, DEVICE_INFO, BLOCK_INFO, and
COMM_INFO.
*4: A description such as "FALSE," "TRUE," "OFF," or "ON" is not permitted, unless a description
method based on "ON" and "OFF" is clearly indicated in the specification, such as for the item
INTERLOCK (see Section 4.3.1.18).
*5: Not applicable to any parts other than FILE_INFO, DEVICE_INFO, BLOCK_INFO,
COMM_IF_INFO, COMM_IF_PARAMETER, and BLOCK_PARAMETER.
[Note] The DATATYPE item is restricted in terms of specifiable content, according to the element asfollows:(1) With an element of the part COMM_IF_INPUT: When the ASSIGN item has the prefix "RX," only
types of the following sizes can be written: 1, 4, 8, 12, 16, and 32 bits.
(2) With an element of the part COMM_IF_INPUT: When the ASSIGN item has the prefix "RWr," onlya type of a 16-bit or 32-bit size or a structure type can be written. Note, however, that in a casewhere a STRUCT part is used for reference purposes, an element distributed across multiple
RWrs cannot be written.
(3) With an element of the part COMM_IF_OUTPUT: : When the ASSIGN item has the prefix "RY,"
only types of the following sizes can be written: 1, 4, 8, 12, 16, and 32 bits.
(4) With an element of the part COMM_IF_OUTPUT: When the ASSIGN item has the prefix "RWw,"
only a type of a 16-bit or 32-bit size or a structure type can be written. Note, however, that in acase where a STRUCT part is used for reference purposes, an element distributed acrossmultiple RWrs cannot be written.

CLPA

BAP-C2008ENG-001-K
1-71

4.3.1.11 DEFAULT conventions
A DEFAULT item describes the default value of the element. Default values are restricted as follows.
(1) Relationship with DATATYPE item
The default value must be within the range of the data type described in the DATATYPE item (seeSection 4.3.1.10). A value outside of the range of the RANGE item (see Section 4.3.1.26) can be
written as long as the value is in accordance with the DATATYPE item. For example, for anelement with a RANGE item described as 1 to 100, you can write 0, an invalid number, as thedefault value.
Further, a default value cannot be written when the DATATYPE item is an element of the part
STRUCT. In such a case, write the default value in the DEFAULT item of each element defined in
the STRUCT part.
(2) Description when default value is undefined
When the default value is not uniquely defined, the description may be omitted.
(3) Description when the default value cannot be indicated based on a specific communication
method.
When the default value is undefined based on communication type or communication settings,
write "NA" in the element of the COMM_IF section.

4.3.1.12 END_CONDITION conventions
An END_CONDITION item describes the condition for ending reading (writing) based on a conditional
expression. Note that when a process is to end upon satisfaction of the conditions of the item
REQ_FLAG (see Section 4.3.1.34), this item may be omitted. The basic conventions for this item are
the same as those for the INTERLOCK item (see Section 4.3.1.18), but the item may also include thefollowing description as well:(1) When wait time is required prior to end assessment, write WAIT(X) prior to the conditional
expression and separated by a comma. X is any integer between 1 and 65535, and indicates thata wait time of X ms is required. A comma cannot be entered at any location other than
immediately after WAIT(X).
(Example: WAIT(1000),RX8==ON),(Example: WAIT(1000)),(Example of unpermitted description: RX8==ON,WAIT(1000))* The utility software does not need to guarantee that the conditional expression will beassessed the instant that X ms elapse. The conditional expression is assessed after X ms
elapse.
* While not described in the ERR_CONDITION item, error assessment is also performed after
waiting X ms as well.

4.3.1.13 ENG_UNIT conventions
An ENG_UNIT item describes a string that indicates the unit of measurement. For example, when you
want to indicate the duration of a second, write "s". The following describes the description
specifications.
(1) This item may be omitted when an engineering unit is not needed.
(2) The item can be written using any string.
(3) When the engineering unit cannot be indicated when a specific communication method is used,
enter "NA" in the ENG_UNIT item of the element of the COMM_IF section.
(4) This item cannot be described when the item DATATYPE (see Section 4.3.1.10) is an element of
the part STRUCT. Describe the engineering unit in the item ENG_UNIT (see Section 4.3.1.26) ofeach element defined in the part STRUCT.
Further, a default value cannot be written when the DATATYPE item (see Section
4.3.1.10) is an element of the STRUCT part. In such a case, write the default value in the ENG
UNIT item (see Section 4.3.1.26) of each element defined in the STRUCT part.
When other languages are supported, write this label name in keeping with the descriptions of the
LANGUAGE element and FILE_INFO part of the FILE section.
(5)

4.3.1.14 ERR_CONDITION conventions
An ERR_CONDITION item describes an abnormal end flag during read (write) command execution
using a conditional expression. Note that, for processing in which an error does not occur [in a case
CLPA

BAP-C2008ENG-001-K
1-72

where the conditions of the END_CONDITION item (see Section 4.3.1.12) are always satisfied], thisitem may be omitted. The conventions are the same as those for the INTERLOCK item (see Section
4.3.1.18).

4.3.1.15 ERR_CODE RANGE conventions
An ERR_CODE RANGE item describes the range of an error code. While the conventions are thesame as those for the RANGE item (see Section 4.3.1.26), indicate correspondence with the stringthat indicates the meaning of the value of the error code basically by using the ENUM part description.
Note that omission of the description of the ERR_CODE_RANGE item indicates that all values thatcan be expressed using endCode within the error PDU specified by the ERR_TYPE item (for the itemof a MESSAGE part; see Section 4.3.1.17) or any device specified by the ERR REGISTER item (forthe item of a METHOD part; see Section 4.3.1.16) are within the error code range.

4.3.1.16 ERR_REGISTER conventions
An ERR_REGISTER item describes the device name that stores error codes when an error occurs.
Write the device name following the conventions below.
(1) Write the name using the same conventions as those for the ASSIGN item (see Section 4.3.1.3).
(2) Write the name by referring to the ASSIGN item of the element using a reference specification(see Section 4.3.3) by "$()".
If not needed, the ERR_REGISTER item may be omitted.

4.3.1.17 ERR_TYPE conventions
An ERR_TYPE item describes the type of the data format to be used in response processing when anerror occurs.
Write a string that connects the error PDU name and ASCII or Binary using "_". For the error PDU
name, see "PDU name" in Table 4-11. [The table is an extraction from the "CC-Link IE Field Network
Specification (SLMP Specification Overview) BAP-C1605-005-A." For details of the contents describedin the table, see the "PDU List" in the "CC-Link IE Field Network Specification (SLMP Specification
Overview) BAP-C1605-005-A."] ASCII and Binary respectively indicate that the data is to be sent in
ASCII mode or Binary mode. This item may be omitted when errors do not occur (when error
information is not required).
[Description example] rdErrST_Binary,wrErrMT_ASCII
Table 4-11 Error PDU Name List
Type SLMPPDU
ST rdErrST-PDU
wrErrST-PDU
MT rdErrMT-PDU
wrErrMT-PDUPDU NamerdErrSTwrErrSTrdErrMTwrErrMT

4.3.1.18 INTERLOCK conventions
INTERLOCK describes an interlock using a conditional expression. The description specifications aredescribed below. This item may be omitted if an interlock does not exist (if there are no start
conditions).
(1) For the term on the left of the operator, directly write the address of the register name, forexample, or use a reference specification via "$()" (see Section 4.3.3) to refer to the ASSIGN item
(see Section 4.3.1.3) of the element.
(2) If you describe the interlock by a reference using "$()" in the left term, the data type of the left
term is in accordance with the description of the DATATYPE item of the element of the reference.
If you directly write a word device, the data size is regarded as 16 bits, and the type category is inaccordance with the value of the right term.
(3) Make sure that the data sizes and type categories of the left and right terms coincide.
(4) The relational operators shown in Table 4-12 can be used operators.

CLPA

BAP-C2008ENG-001-K
1-73

Table 4-12 Applicable Relational Operators
Operator
==
!=
<
>
<=
>=

Description
Equal toNot equal toLess thanGreater thanLess than or equal to
Greater than or equal to(5) If you want to execute a bit device comparison, write "ON" or "OFF" in the right term.
(Example: RYC==ON)(6) If multiple conditions need to be satisfied, write the conditions side-by-side using the conjunction
operator "&&".
(Example: RYC==ON&&RXE==OFF)

4.3.1.19 LABEL conventions
A LABEL item is used to refer to the element. Write a label name that identifies the section, part, orelement. The LABEL item can be written using a 32-character Unicode alphanumeric string. Table
4-13 shows the characters that are cannot be used.
The following restrictions apply to the label name written using the LABEL item:(1) The label name of a section needs to be written so that there are no duplicates.
(2) The label name of a part needs to be written so that there are no duplicates within the same
section.
(3) The label name of an element needs to be written so that there are no duplicates within the same
part.
(4) Label name comparisons are assessed without upper/lower case sensitivity ("VAR1" and "var1"
are regarded as duplicate names).
(5) If multiple COMM_IF INPUT or COMM_IF_OUTPUT parts containing cyclic address information
exist in the same section, the label names need to be written so that there are no duplicatesamong the elements of the different parts.
The LABEL item is not only used when you want to refer to other elements within a profile description,
but also when the utility software deploys a sequence program label name based on the profile
description.
When elements are compared across profile descriptions having the same model name but different
CSP+ specification versions, file versions, device versions, or supported language information, theelements are regarded as having the same meaning if the LABEL items of the sections, the LABEL
items of the parts, and the LABEL items of the elements are the same. For this reason, caution isrequired when profile descriptions are to be changed as a result of version upgrades.

CLPA

BAP-C2008ENG-001-K
1-74

Table 4-13 Characters Not Permitted in LABEL and LABEL2 Items
Category
Characters not
permitted in LABEL item
Characters not
permitted at head of
LABEL item
Reserved words

Prohibited Characters!, ", #, $, %, &, ', (, ), *, +, , , -, ., /, :, ;, <, =, >, ?, @, [, ¥, ], ^, `, {, |, }, ~0, 1, 2, 3, 4, 5, 6, 7, 8, 9, _ACCESS, AUTO_PARAMETER, ARGUMENT, ASSIGN, BLOCK,BLOCK_COMMAND, BLOCK_INFO, BLOCK_INPUT, BLOCK_OUTPUT,BLOCK_PARAMETER, CATEGORY, CODE, COMM_IF,
COMM_IF_COMMAND, COMM_IF_INFO, COMM_IF_INPUT,
COMM_IF_OUTPUT, COMM_IF_PARAMETER, COMMAND,COMMAND_ARGUMENT, COMMENT, COMMENTx (x = An integer
greater than or equal to 1), COMMON, CONDITION, CONDITIONx (x = An
integer greater than or equal to 1), DATA, DATATYPE, DEFAULT, DEVICE,
DEVICE_INFO, DUMMY, END_CONDITION, ENG_UNIT, ENUM,
ERR_CODE_RANGE, ERR_CONDITION, ERR_REGISTER, ERR_TYPE,
FILE, FILE_INFO, INTERLOCK, LABEL, LABEL2, MAINTENANCE,MESSAGE, MESSAGE_TYPE, METHOD, METHOD_TYPE, MIN_INC,
MONITOR, NA, NAME, OFFSET, OTHER, PARAMETER,
PARENT_TARGET, RANGE, READ_DATA, READ_DATATYPE,
READ_REGISTER, REF, RELATED_ELE, RELATED_MESSAGE,
RELATED_METHOD, REQ_FLAG, REQUEST_DATA,REQUEST_DATATYPE, REQUEST_TYPE, RESPONSE_DATA,RESPONSE_DATATYPE, RESPONSE_TYPE, RESULTx (x = An integer
greater than or equal to 1), SEQ_TARGET, STRUCT, TARGET,UI_ATTRIBUTE, VALUE, WRITE_DATA, WRITE_DATATYPE,WRITE_ORDER, WRITE_REGISTER The above strings cannot be used, regardless of the upper/lower casesetting. (Example: LABEL and laBel and label are all reserved words.)
 Any string that fully matches one of the above is not permitted. (Example:
A_LABEL and LABELA can be used.) Strings that start with "P_" are reserved for future expansion.
 Strings that start with "SLMP_P_" are reserved for SLMP message
use.
Space
Both single-byte and double-byte spaces are not permitted.
Note that the applications of the regulated label names described in Section 5.5 are alreadydetermined. The names cannot be used for any other application.
Further, label names that start with "P" will be used in the future for extending descriptions common tomodules defined in Section 5.5. Do not, therefore, use the label names that start with "P" with labels of
elements or parts that describe module specific functions.


4.3.1.20 LABEL2 conventions
A LABEL2 item describes the label name used for element identification in keeping with supported
language information. The LABEL2 item can be written using a 32-character Unicode string (including
characters other than alphanumeric as well). Table 4-13 shows the characters that are cannot be
used.
If the LABEL item and the LABEL2 item have the same descriptions, the LABEL2 item may beomitted.
The following restrictions apply to the label name written using the LABEL2 item:(1) The label name of an element needs to be written so that there are no duplicates within the same
part.
(2) Label name comparisons are assessed without upper/lower case sensitivity ("VAR1" and "var1"
are regarded as duplicate names).
(3) If multiple COMM_IF INPUT or COMM_IF_OUTPUT parts containing cyclic address information
exist in the same section, the label names need to be written so that there are no duplicatesamong the elements of the different parts.
The LABEL2 item is sometimes used when the utility software deploys a name as a sequence
program label name based on the profile description.
CLPA

BAP-C2008ENG-001-K
1-75

When you want to describe the same elements when profile descriptions are changed due to a version
upgrade, we recommend that you do not change the contents of the LABEL item as well as the
LABEL2 item. Note, however, that sometimes elements are assessed as the same if simply the LABEL
items match, depending on the utility software.
When other languages are supported, write this label name in keeping with the descriptions of the
LANGUAGE element and FILE_INFO part of the FILE section.

4.3.1.21 MESSAGE_TYPE conventions
A MESSAGE_TYPE item describes the message type by describing a TYPE value of Table 4-14. The
MESSAGE_TYPE item cannot be omitted. If you want to write multiple TYPE values, write them as aset (see Section 4.3.3, Table 4-23 [2]).
This description is used to assess whether the data is to be displayed in the parameter settings ofgeneral-purpose utility software, displayed at command execution, or not displayed.
Table 4-14 Values of MESSAGE_TYPE Item
No. TYPE Value
1.
PARAMETER
2.
COMMAND

3.

MONITOR

4.

MAINTENANCE

5.

OTHER

6.

AUTO_PARAMETER

Meaning
Indicates that the message is a parameter related message.
Indicates that the message is a command related message.
Indicates that the message is processed not just once but consecutively. As
for the method, the MONITOR type does not mean that the method
processing is executed consecutively all the time. As for the message,
however, the message is always executed consecutively.
Note that only the corresponding message is executed consecutively. (If"PRE" and "POST" are described in RELATED_MESSAGE, those messages
are executed once before and after the consecutive execution of thecorresponding message.)
Indicates that the message is a maintenance related message.
If the message is to acquire maintenance information, information may be
acquired periodically. Note the following.
 When "MONITOR" is defined to MESSAGE_TYPE as a set, informationis acquired according to the operating specifications of the MONITOR
type.
Indicates a message that is not displayed by general-purpose utility software.
Also describes a method that has significance for the first time after anothermethod is called by a RELATED_MESSAGE item.
Indicates that the message is a message for slave station parameter auto
setting in CC-Link IE TSN. [Note] Available only in CC-Link IE TSN.

4.3.1.22 METHOD_TYPE conventions
A METHOD_TYPE item describes the type of the method by describing a TYPE value of Table 4-15.
The METHOD_TYPE item cannot be omitted. If you want to describe multiple TYPE values, describe
them as a set (see Section 4.3.3, Table 4-23 [2]).
This description is used to assess whether the data is to be displayed in the parameter settings ofgeneral-purpose utility software, displayed at command execution, or not displayed.

CLPA

BAP-C2008ENG-001-K
1-76

Table 4-15 Values of METHOD_TYPE ItemNo.
TYPE Value
1. PARAMETER
2. COMMAND

3.

MONITOR

4.

MAINTENANCE

5.

OTHER

Meaning
Indicates that the method is a parameter related method.
Indicates that the method is a command related method.
Indicates that the method is processed not just once but consecutively. This
does not mean that the method processing is executed consecutively all thetime. This means that processing that can obtain effect is executed
consecutively. For example, as for the method that reads values in the result
output register, the method itself is not executed consecutively, but the readprocessing is executed consecutively.
Note that only the corresponding method is executed consecutively. (If "PRE"and "POST" are described in RELATED_METHOD, those methods are
executed once before and after the consecutive execution of the corresponding
method.)Indicates that the method is a maintenance related method.
If the method is to acquire maintenance information, information may be
acquired periodically. Note the following.
 When "MONITOR" is defined to METHOD_TYPE as a set, information is
acquired according to the operating specifications of the MONITOR type.
Indicates a method that is not displayed by general-purpose utility software,such as a method that has significance, for example, when utilized withparameter setup or a ladder in the case of the AD converter initial setup
function, but not when displayed by general-purpose utility software.
Also describes a method that has significance for the first time after anothermethod is called by a RELATED_METHOD item.

4.3.1.23 MIN_INC conventions
A MIN_INC item describes the minimum resolution value separately from the ENG_UNIT item (seeSection 4.3.1.13). The description specifications are as follows:(1) This item cannot be described for elements in which an ENG_UNIT item is not described.
(2) You can write the item for an element in which the DATATYPE item (see Section 4.3.1.10) is asigned integer type (INT), an unsigned integer type (UINT), or a BCD integer type (BCD)(elements that treat values in decimal format).
(3) The writable value is 10n (where n is an integer); write the calculation result in decimal format(. . ., 0.01, 0.1, 1, 10, 100, . . . ). Note that an element with the MIN_INC item omitted is treated asif the minimum increment is 1.
(4) In a case where the MIN_INC item cannot be indicated when a specific communication method isused, write "NA" in the MIN_INC item of the element of the COMM_IF section.
(5) When using a specific communication system, if MIN_INC items cannot be shown, write "NA" inthe MIN_IC item of elements of the COMM_IF section.
The values of elements of the RANGE item (see Section 4.3.1.26), DEFAULT item (see Section
4.3.1.11), and the like are values maintained by the module. The value of the ENG_UNIT item can beacquired by multiplying such values by the MIN_INC item.
For example, in a case of the element described below, the value maintained by existing equipment isin the range of 1000 to 2000. However, since 0.01 is written in the MIN_INC item, the actual setting
range becomes 10.00 Hz (0.01 Hz x 1000) to 20.00 Hz (0.01 Hz x 2000). The following shows anexample of an element in which the minimum increment is described.
<blockInputMember label="SetingFreq"><label2><item> Output frequency </item></label2><name><item> Output frequency </item></name><datatype><item>UINT16</item></datatype><default><item>0</item></default><range><item>[1000,2000]</item></range><minInc><item>0.01</item></minInc><emgUnit><item>Hz</item></engUnit></blockInputMember>

CLPA

BAP-C2008ENG-001-K
1-77

4.3.1.24 NAME conventions
A NAME item describes the name of the element. The written string is used to display the name orcontents of the element by utility software.
The NAME item cannot be omitted, unless the element is an element that refers to another element
using the REF item described later (see Section 4.3.1.30) or an element of the FILE_INFO,DEVICE_INFO, COMM_IF_INFO, or BLOCK_INFO part.
When other languages are supported, write this label name in keeping with the descriptions of the
LANGUAGE element and FILE_INFO part of the FILE section.

4.3.1.25 OFFSET conventions
An OFFSET item describes the offset assigned within the structure. The following describes the rules
for offset descriptions:(1) Write the description of the OFFSET item as "NumberOfWords.NumberOfBits" with the offset for
the number of words (hexadecimal number) and the offset for the number of bits (hexadecimal
number) separated by a dot. (Example: 0.1, 2.D, F.3)
(2) The sequence of the elements within a part does not have to match the order of the offset values
described for the elements.
(3) The OFFSET item cannot be omitted.
(4) Duplication of an offset in elements within the same STRUCT part is prohibited. (Example: Givena data type of UINT4 and elements with the offsets "0.0" and "0.3," bit 3 is duplicated, and thus
the description is not permitted.)(5) An empty offset is permitted. (Example: A STRUCT description having the offsets "0.0," "0.2," and"0.8" with all data types as BOOL is permitted.)

4.3.1.26 RANGE conventions
A RANGE item describes the range of a value to be set for the element. The following describes thedescription method of the setting range.
(1) When directly describing a value and value range
For a value range that describes a "value" and the "value range" one after the other, write the twovalues of the value range within brackets and separate the two values with a comma (","). The left
value indicates the low limit, and the right value indicates the high limit. A closed interval is written
using "[","]" and an open interval is written using "(",")". If there are multiple value ranges, list theranges one after the other as a set.
Example: "[1,600]" "[7000,7010]" "8800"
With an XML file: (<item>[1,600]</item><item>[7000,7010]</item><item>8800</item>)(2) When using an ENUM part
With an ENUM part, you can indicate the setting range by describing the available options in the
ENUM part and writing a reference to the ENUM part (see Section 5.3.9).
Use an ENUM part if you want to determine the value selected via a list box or pull-down menu of
the utility software, or if you want to display the meaning of each value during monitoring.
Note, however, that an ENUM part can only be used if the DATATYPE item (see Section 4.3.1.10)
is a Boolean type , integer type (INT, UINT, BCD), or a bit string type (BYTE, WORD, etc.).
(3) When the range is equal to the range of the value for the DATATYPE item
When the setting range is equal to the range of the DATATYPE item, the RANGE item may beomitted.
(4) When the setting range cannot be displayed (does not need to be displayed) by utility software
When the RANGE item is handled by utility software and does not need to be displayed (cannot
be displayed), write "NA".
(5) When writable values differ from readable values
Read and write attributes cannot be set for each value written in a RANGE item.
As a result, an element for which the readable values are 0 to 10 and the writable values are 0 to
5, for example, cannot be expressed using the RANGE item.
In such a case, we recommend writing [0,10] for the RANGE item, and writing that 6 and above
are not writable in the COMMENT item (see Section 4.3.1.6).
(6) When the DATATYPE item is a structure type
CLPA

BAP-C2008ENG-001-K
1-78

In this case, a RANGE item cannot be written. Write the values in the RANGE item of eachelement defined in the STRUCT part.
(7) When a DATATYPE item is structural type
RANGE items are not permitted. Write in the RANGE items of various elements defined in
STRUCT part.
(8) When the set values of other parameters are used as the upper limit or lower limit of the setting
range
Using the conventions in Table 4-23 (3) (reference destination specification by "$()"), reference
the VALUE of other parameters to write. Not only maximum value and minimum value, but also
descriptions such as "Over 1 but less than parameter A, or over parameter B but less than 1000"
are permitted.
This convention can only be written when CC-Link IE Safety Communication Function Support
Unit.
This convention is only usable with elements of BLOCK_PARAMETER part, and reference islimited to elements of those parts. (Parameter values can only show the setting range ofparameters) Cannot reference anything except VALUE, such as DATA).
Ex 1: When the setting range is greater than 1, but less than the set value of ParamA, write as[1,$(ParamA.VALUE)]
Ex 2: When the setting range is greater than 1 but less than ParamA, or greater than ParamB but
less than 1000, write as "[1,$(ParamA.VALUE)),[$( ParamB.VALUE),1000)"

4.3.1.27 READ_DATA conventions
A READ_DATA item indicates the value to be read, and is described following the conventions below.
Note that the value specified needs to comply with the data type of the READ_DATATYPE item (seeSection 4.3.1.28).
(1) Specify the value by writing a reference to the VALUE held by the element of the TARGET item
(see Section 4.3.1.42), the size of the DATATYPE item (see Section 4.3.1.10), the ASSIGN item
(see Section 4.3.1.3), and the element of the COMMAND_ARGUMENT part, placing thereference between "$(" and ")" (see Section 4.3.3).
(Example: $(VALUE),$(ARGUMENT.ReadFrequencyData.VALUE)* When specifying an element of COMMAND_ARGUMENT, you cannot specify an element thatis not readable (NA, W, etc.) by the ACCESS item (see Section 4.3.1.1).
* When describing the reading of all elements inside TARGET using an asterisk (example:$(*.VALUE)), you cannot describe an element that is not readable in TARGET.
* When multiple elements are referenced in TARGET and one of the elements is to be selected
and read, you can write an element that is not readable in TARGET.
* In an element in which the METHOD_TYPE is PARAMETER and VALUE is referenced by
WRITE_DATA, you cannot describe a VALUE reference in READ_DATA.
(2) If multiple read registers have been written using the READ_REGISTER item (see Section
4.3.1.47), specify the same number of write values as read registers, placing the READ_DATA
item between "<" and ">" (see Section 4.3.3) as well.
(Example: <0x40><$(VALUE)>,<$(*.VALUE)>)(3) This item cannot be omitted if the READ_REGISTER item is omitted.

CLPA

BAP-C2008ENG-001-K
1-79

4.3.1.28 READ_DATATYPE conventions
A READ_DATATYPE item indicates the data type of the data type to be read, and is written following
the conventions below.
(1) Write the data type directly (see Section 4.3.1.10).
(2) Specify the data type by writing a reference to the DATATYPE item (see Section 4.3.1.10) of theelement, placing the reference between "$(" and ")" (see Section 4.3.3).
(Example: $(DATATYPE))* A reference cannot be made via a LABEL item (see Section 4.3.1.19) of an element in which a
TARGET item (see Section 4.3.1.42) is not described.
* Specification of an element or argument in which the ACCESS item (see Section 4.3.1.1) is
not readable ("NA", "W", etc.) is not permitted. Note, however, that writing a description thatrefers to multiple elements using the TARGET item and including an element that is notreadable is unproblematic.
(3) When you want to write multiple read registers using the READ_REGISTER item (see Section
4.3.1.29), specify the same number of data types as read registers, placing the
READ_DATATYPE item between "<" and ">" (see Section 4.3.3) as well.
(Example: <WORD><$(DATATYPE)>,<$(*.DATATYPE)>)(4) This item cannot be written if the READ_REGISTER item is omitted.

4.3.1.29 READ_REGISTER conventions
A READ_REGISTER item specifies the register to be read using the conventions below. The readvalue needs to comply with the READ_DATA item (see Section 4.3.1.27).
(1) Directly describe the register using a string. [For the conventions, see the ASSIGN item (seeSection 4.3.1.3).](Example: RWr1)(2) Specify the register by referring to the ASSIGN item of the element via a reference specification
using "$(ASSIGN)" in a case where a reference has been described in the TARGET item (seeSection 4.3.1.42). (No item other than ASSIGN can be used as reference.)(Example: $(InitParameters.CH1_AvgTime.ASSIGN),$(ARGUMENT.ReadFrequencyData.ASSIGN))(3) If you want to specify multiple registers to be read, write the register names in order, placing eachname between "<" and ">" (see Section 4.3.3).
(Example: <RWr4><$(ASSIGN)>, <$(*.ASSIGN)>)
Note that, if multiple registers are described, reading is performed in order, starting from theregister written on the left.
(4) In a case where there are multiple content descriptions in the corresponding READ_DATA item,
including content that does not need to be read, write the content description of the
READ_REGISTER item corresponding to the content that does not need to be read as$(DUMMY). The content of the READ_DATA item corresponding to $(DUMMY) will not be readfrom the register. (Example: In a case where three content descriptions exist in the READ_DATA
item and the first content does not need to be read, write the READ_REGISTER item as follows:<$(DUMMY)><RWr2><RWR3>.)(5) This item may be omitted if the method does not require reading.

CLPA

BAP-C2008ENG-001-K
1-80

4.3.1.30 REF conventions
A REF item describes a reference from the COMM_IF section to the BLOCK section. For reference
conventions, see Section 4.3.4.
(1) For a COMM_IF_INPUT part, write a reference to the corresponding BLOCK_OUTPUT element.
(2) For a COMM_IF_OUTPUT part, write a reference to the corresponding BLOCK_INPUT element.
(3) For a COMM_IF_PARAMETER part, write a reference to the corresponding
BLOCK_PARAMETER element.
(4) For a COMM_IF_COMMAND part, write a reference to the corresponding BLOCK_COMMAND
element. When an ARGUMENT item (see Section 4.3.1.2) is written, the REF item cannot be
described.
(5) For a STRUCT part, write a reference to be referred to by the element. Such a reference is used
to refer to the inputs/outputs and parameters of the BLOCK section from each element of thestructure. The referable elements differ according to the reference source of the STRUCT part.
 For a STRUCT part in which a reference is made via the DATATYPE item (see Section
4.3.1.10) of the COMM_IF_INPUT part, it is possible to describe a reference to an elementof the BLOCK_OUTPUT part using the REF item.
 For a STRUCT part in which a reference is made via the DATATYPE item of the
COMM_IF_OUTPUT part, it is possible to describe a reference to an element of the
BLOCK_INPUT part using the REF item.
 For a STRUCT part in which a reference is made via the DATATYPE item of the
COMM_IF_PARAMETER part, it is possible to describe a reference to an element of the
BLOCK_PARAMETER part using the REF item.
 For a STRUCT part in which a reference is made via the DATATYPE item of
COMMAND_ARGUMENT, this item cannot be written.
(6) If a reference to a STRUCT part is described in a DATATYPE item of an element that has a REF
item, a reference cannot be written in the REF item.
(7) If the same items exist in the reference source and reference and the values of the items in thereference source and reference are the same, write the value in the element of the reference, andomit the item in the element of the reference source.
(8) If the same items exist in the reference source and reference and the values of the items in thereference source and reference differ, write the value in both the elements of the reference source
and reference. In such a case, the utility software uses the value of the reference source.
(9) If multiple COMM_IF sections are written and the setting range, access attributes, etc., differ
according to the COMM_IF section used, you can overwrite the value written in the reference by
writing the value in the element of the reference source.
(10) It is possible to describe a reference from a single element to multiple elements (a one-to-manyreference) or a reference from multiple elements to one element (a many-to-one reference). A
one-to-many reference indicates that, when the inputs, outputs, and parameters indicated by theelement of the reference source are accessed, the outputs, inputs, and parameters indicated by
all elements of the reference are accessible. A many-to-one reference indicates that the outputs,
inputs, and parameters of the reference are accessible from the inputs, outputs, and parametersindicated by all elements of the reference source. The following lists the precautions related to
one-to-many and many-to-one references.
 One-to-many reference
When the item of the element of the reference source is omitted, write the same value for theitem of all reference elements.
 Many-to-one reference
We recommend that you do not use a many-to-one reference in any case other than thefollowing:

CLPA

[1]

A many-to-one reference from different COMM_IF sections[2]

A many-to-one reference from elements of different METHOD or MESSAGE parts

BAP-C2008ENG-001-K
1-81

4.3.1.31 RELATED_ELE conventions
A RELATED_ELE item describes a reference from the ENUM part to the COMMAND_ARGUMENT
part. If the reference is not required, this can be omitted. For reference conventions, see Section 4.3.4.
[Note] A RELATED_ELE item can be used only in CC-Link IE TSN.

4.3.1.32 RELATED_MESSAGE conventions
A RELATED_MESSAGE item describes a message required as message pre-processing, using theconventions indicated in Table 4-16.
(1) In order to share a TARGET item (see Section 4.3.1.42) in a MESSAGE part of a reference
source and reference of a RELATED_MESSAGE item, you need to write a "PARENT_TARGET"
in the TARGET item of the element of the reference. If you want to describe selection from aplurality in a TARGET item of the element of the reference source, always select and execute thesame element using the MESSAGE part of the reference source and reference.
(2) If you want to specify multiple MESSAGE parts, write the convention shown in Table 4-16 in
multiple, placing "<" and ">" (See Section 4.3.3) around each. The maximum number of
MESSAGE parts specifiable is sixteen.
(3) A RELATED_MESSAGE item cannot be written with a message of a reference from a
RELATED_MESSAGE item.
(4) With a reference message or reference source message from a RELATED_MESSAGE item,
reference can be made to a VALUE of an element written in a TARGET item or a VALUE of anelement of a COMMAND_ARGUMENT part. However, each message related to the
RELATED_MESSAGE item must be in accordance with the following:(a) You cannot refer to a VALUE of the same element using both the REQUEST_DATA item
(see Section 4.3.1.35) and the RESPONSE_DATA item (see Section 4.3.1.38).
(b) With the REQUEST_DATA item, you can refer to a VALUE of the same element multiple
times.
(c) With the RESPONSE_DATA item, you cannot refer to a VALUE of the same element multiple
times.
(Example: When "<PRE MessageB><PRE MessageC>" are written in the item
RELATED_MESSAGE of MessageA, MessageA is executed after the sequential executionof MessageB and MessageC.)(d) VALUE descriptions need to be unified to either the write side (REQUEST_DATA) or the readside (RESPONSE_DATA). Only in a case where the message that describes VALUE
involves only one element can the descriptions be made on both the write side and the readside.
(e) The part types of elements targeted by VALUE (elements described in TARGET) need to beunified. For example, you cannot mix a message that targets the VALUE of an element of
COMM_IF_PARAMETER and a message that targets the VALUE of an element of
COMMAND_ARGUMENT (COMM_IF_COMMAND) and refer to the data using SEQ.
(f) When the elements of COMM_IF_INPUT, COMM_IF_OUTPUT, and COM_IF_PARAMETER
are described in TARGET of each message, element duplication is prohibited (duplication is
only possible with COMM_IF_COMMAND). Duplication is prohibited not only for elements of
COMM_IF, but also for elements of BLOCK that arereferenced using the item REF from anelement of COMM_IF.
(5) If you want to indicate a message to be executed as message pre-processing, describe themessage using the keyword "PRE". To share TARGET between the reference source andreference destination messages of RELATED_MESSAGE, the "PARENT_TARGET" needs to be
described in the TARGET of the element of the reference destination (see Section 4.3.1.42). If
multiple elements are described in TARGET of the element of the reference source, the sameelements must always be selected and executed in the reference source and reference
destination messages.
(6) If you want to indicate a message to be executed as message post-processing, describe themessage using the keyword "POST". To share TARGET between the reference source andreference destination messages of RELATED_MESSAGE, the "PARENT_TARGET" needs to be
described in the TARGET of the element of the reference destination (see Section 4.3.1.42). If
multiple elements are described in TARGET of the element of the reference source, the sameelements must always be selected and executed in the reference source and reference
destination messages.
CLPA

BAP-C2008ENG-001-K
1-82

(7) If you want to indicate the consecutive processing of a message, describe the processing using
the keyword "SEQ". The description method in a case where the keyword "SEQ" is used is
described below.
(a) "SEQ" can be described only with message elements in which "SEQ_TARGET" is describedin TARGET. This message is used to describe the definition of the consecutive processing
only, and not communication processing.
(b) The MESSAGE_TYPE of the consecutive processing in general is in accordance with the
MESSAGE_TYPE of the message that describes "SEQ" in RELATED_MESSAGE. Note thatthe type does not need to match the MESSAGE_TYPE of the message referenced by SEQ.
(c) A message in which multiple elements are described in TARGET and one element isselected and targeted from the described elements cannot be referenced by "SEQ"(example: a message in which $(VALUE) and $(DATATYPE) are described in each item
cannot be referenced). Reference can be made using "SEQ" for descriptions that target allelements of TARGET (example: $(*.VALUE) and messages in which a reference($(ARGUMENT.Element.VALUE)) to an element of COMMND_ARGUMENT is described.
Table 4-16 RELATED_MESSAGE Item Conventions
KeywordPRE

Meaning
Indicates a message
executed as message
pre-processing.

Conventions""PRE" + " " (single-byte space)+ Message label name"

POST

Indicates a message
executed as message
post-processing.

""POST" + " " (single-byte
space) + Message label name"

SEQ

Indicates that multiple
messages areconsecutively
executed.

""SEQ" + " " (single-byte space)+ message label name"ExampleWhen "<PRE MessageB><PRE
MessageC> is described in the
RELATED_MESSAGE of
MessageA→ After MessageB and MessageCare executed in that order,
MessageA is executed.
When "<POST MessageB><POST
MessageC> is described in the
RELATED_MESSAGE of
MessageA→ After MessageA is executed,
MessageB and MessageC are
executed in that order.
When "<SEQ MessageB><SEQ
MessageC> is described in the
RELATED_MESSAGE of
MessageA→ MessageB and MessageC are
executed in that order.
* MessageA itself cannot describe
communication processing and istherefore not executed.

4.3.1.33 RELATED_METHOD conventions
A RELATED_METHOD item describes a method required as method pre-processing, using theconventions indicated in Table 4-17. The RELATED_METHOD item may be omitted if not required.
(1) In order to share a description of a TARGET item (see Section 4.3.1.42) using a method of thereference source and reference of a RELATED_METHOD item, you need to write a"PARENT_TARGET" in the TARGET item of the element of the reference. If you want to describe
selection from a plurality in a TARGET item of the element of the reference source, select andexecute the same element using the method of the reference source and reference.
(2) If you want to specify multiple methods, write the convention shown in Table 4-17 in multiple,
placing "<" and ">" (See Section 4.3.3) around each. The maximum number of methods
specifiable is sixteen.
(3) A RELATED_METHOD item cannot be written with a method of a reference from a
RELATED_METHOD item.
CLPA

BAP-C2008ENG-001-K
1-83

(4) With a reference method or reference source method from a RELATED_METHOD item,
reference can be made to a VALUE of an element written in a TARGET item or a VALUE of anelement of a COMMAND_ARGUMENT part. However, each method related to the
RELATED_METHOD item must be in accordance with the following:(a) You cannot refer to a VALUE of the same element with both the WRITE_DATA item (seeSection 4.3.1.44) and the READ_DATA item (see Section 4.3.1.27).
(b) With the WRITE_DATA item, you can refer to a VALUE of the same element multiple times.
(c) With the READ_DATA item, you cannot refer to a VALUE of the same element multiple
times.
(Example: When "<PRE MethodB><PRE MethodC>" are written in the item
RELATED_METHOD of MethodA, MethodA is executed after the sequential execution of
MethodB and MethodC.)(d) VALUE descriptions need to be unified to either the write side (WRITE_DATA) or the readside (READ_DATA). Only in a case where the method that describes VALUE involves only
one element can the descriptions be made on both the write side and the read side.
(e) The part types of elements targeted by VALUE (elements described in TARGET) need to beunified. For example, you cannot mix a method that targets the VALUE of an element of
COMM_IF_PARAMETER and a method that targets the VALUE of an element of
COMMAND_ARGUMENT (COMM_IF_COMMAND) and refer to the data using SEQ.
(f) When the elements of COMM_IF_INPUT, COMM_IF_OUTPUT, and COM_IF_PARAMETER
are described in TARGET of each method, element duplication is prohibited (duplication is
only possible with COMM_IF_COMMAND). Duplication is prohibited not only for elements of
COMM_IF, but also for elements of BLOCK that are referenced using the item REF from anelement of COMM_IF.
(5) If you want to indicate a method to be executed as the method pre-processing, describe themethod using the keyword "PRE". To share a TARGET between the reference source andreference destination methods of RELATED_METHOD, the "PARENT_TARGET" needs to be
described in TARGET of the element of the reference destination (see Section 4.3.1.42). If
multiple elements are described in TARGET of the element of the reference source, the sameelements must always be selected and executed in the reference source and reference
destination methods.
(6) If you want to indicate a method to be executed as the method post-processing, describe themethod using the keyword "POST". To share a TARGET between the reference source andreference destination methods of RELATED_METHOD, the "PARENT_TARGET" needs to be
described in TARGET of the element of the reference destination (see Section 4.3.1.42). If
multiple elements are described in TARGET of the element of the reference source, the sameelements must always be selected and executed in the reference source and reference
destination methods.
(7) If you want to indicate consecutive processing of a method, describe the processing using the
keyword "SEQ". The description method in a case where the keyword "SEQ" is used is described
below.
(a) "SEQ" can be described only with method elements in which "SEQ_TARGET" is described in
TARGET. This method is used to describe the definition of the consecutive processing only,
and not communication processing.
(b) The METHOD_TYPE of the consecutive processing in general is in accordance with the
METHOD_TYPE of the method that describes "SEQ" in RELATED_METHOD. Note that thetype does not need to match the METHOD_TYPE of the method referenced by SEQ.
(c) A method in which multiple elements are described in TARGET and one element is selected
and targeted from the described elements cannot be referenced by "SEQ" (example: amethod in which $(VALUE) and $(DATATYPE) are described in each item cannot bereferenced). Reference can be made using "SEQ" for descriptions that target all elements of
TARGET (example: $(*.VALUE)) and methods in which a reference($(ARGUMENT.Element.VALUE) to an element of COMMND_ARGUMENT is described.

CLPA

BAP-C2008ENG-001-K
1-84

Table 4-17 RELATED_METHOD Item Conventions
KeywordPRE

Meaning
Indicates a method
executed as method
pre-processing.

Conventions""PRE" + " " (single-byte space)+ Method label name"

POST

Indicates a method
executed as method
post-processing.

""POST" + " " (single-byte
space) + Method label name"

SEQ

Indicates thatmultiple messages
are consecutively
executed.

""SEQ" + " " (single-byte space)+ method label name"ExampleWhen "<PRE MethodB><PRE
MethodC> is described in the
RELATED_METHOD of
MethodA→ After MethodB and MethodC
are executed in that order,
MethodA is executed.
When "<POST
MethodB><POST MethodC> isdescribed in the
RELATED_METHOD of
MethodA→ After MethodA is executed,
MethodB and MethodC are
executed in that order.
When "<SEQ MethodB><SEQ
MethodC> is described in the
RELATED_METHOD of
MethodA→ MessageB and MessageCare executed in that order.
* MethodA itself cannot describe
communication processing
and is therefore not executed.

4.3.1.34 REQ_FLAG conventions
A REQ_FLAG item describes a read (write) request flag using an assignment expression.
(1) Express the assignment operator using "=".
(2) The description specifications for the left term are the same as those for the bit type of the
INTERLOCK item (see Section 4.3.1.18).
(3) Write "ON" or "OFF" for the right term. (Example: RYC=ON)(4) You cannot write information that indicates cancellation of the request flag separately. When therequest flag is ON, cancellation is OFF. When the request flag is OFF, cancellation is ON.
(5) If multiple flags need to be set up simultaneously, write the flags separately as a set.
(Example: "RY8=ON" "RY9=ON"
With an XML file: "<item>RY8=ON</item><item>RY9=ON</item>")
When it is acceptable to start processing immediately after the writing of the WRITE_REGISTER item
(refer to Section 4.3.1.47) and not cancel the request flag after execution ends, this item may beomitted.

4.3.1.35 REQUEST_DATA conventions
A REQUEST_DATA item describes a value that is to be sent using the data format specified by the
REQUEST_TYPE item (see Section 4.3.1.37). The item describes the value that is to be set by amessage. The value is written following the conventions described below. Note that the value specified
needs to comply with the data type of the REQUEST_DATATYPE item (see Section 4.3.1.36).
(1) Write the value directly. (Example: 0x40)(2) Specify the value by writing a reference to the VALUE of an element of a TARGET item (seeSection 4.3.1.38), the size of a DATATYPE item (see Section 4.3.1.8), an ASSIGN item (seeSection 4.3.1.3), and an element of a COMMAND_ARGUMENT part, placing the reference
between "$(" and ")" (see Section 4.3.3).
(Example: $(VALUE), <$(ARGUMENT.WriteFrequencyData.VALUE)>,$(DATATYPE).WORDSIZE)

CLPA

BAP-C2008ENG-001-K
1-85

(3) When you want to write multiple values (when you have written a REQUEST_TYPE item so thatmultiple values are to be described), write the values in list format, placing each between "<" and">" (see Section 4.3.3).
(Example: <0x40><$(VALUE)>,<$(*.VALUE)>)(4) Within the configuration of a PDU specified in the REQUEST_TYPE item, write the order of thedata other than the header section (command, subCommand, reqData) and the order of the datatypes in sequence.
(5) If the REQUEST_TYPE item is omitted, or data other than the header section does not exist, omit
this item.
(6) When processing that specifies and writes elements of a STRUCT type, which has empty spacein the offset, to a REQUEST_DATA item of a message, zero is written to the empty section of theoffset. When a fixed value other than zero needs to be written, write an element in which the
DATATYPE is constant inside the STRUCT part.

4.3.1.36 REQUEST_DATATYPE conventions
A REQUEST_DATATYPE item describes the data type of a value (REQUEST_DATA) to be sent by
request processing, using the conventions below.
(1) Write the data type directly (see Section 4.3.1.10).
(2) Specify the data type by writing a reference to a DATATYPE item (see Section 4.3.1.10) of anelement, placing the reference between "$(" and ")" (see Section 4.3.3).
(Example: $(DATATYPE))(3) When multiple write registers have been written using the REQUEST_DATA item (see Section
4.3.1.35), specify the same number of data types as REQUEST_DATA items, placing each data
type between "<" and ">" (see Section 4.3.3).
(Example: <WORD><$(DATATYPE)>,<$(*.DATATYPE)>)(4) This item cannot be written when the REQUEST_DATA item is omitted.
(5) Within the configuration of a PDU specified in the REQUEST_TYPE item, write the order of thedata other than the header section (command, subCommand, reqData) and the order of the datatypes in sequence.
(6) If the REQUEST_TYPE item is omitted, or data other than the header section does not exist, omit
this item.

4.3.1.37 REQUEST_TYPE conventions
A REQUEST_TYPE item describes the type of data format for performing request processing.
Write a string that connects the request PDU name and ASCII or Binary using "_". For the request
PDU name, see "PDU name" in Table 4-18. [The table is an extraction from the "CC-Link IE Field
Network Specification (SLMP Specification Overview) BAP-C1605-005-A." For details of the contents
described in the table, see the "PDU List" in the "CC-Link IE Field Network Specification (SLMPSpecification Overview) BAP-C1605-005-A."] ASCII and Binary indicate that the data is to be sent in
ASCII mode or Binary mode, respectively.
Although REQUEST_TYPE item must be written in SLMP MESSAGE, MESSAGE other than SLMP
can be written for CC-Link IE TSN. In such a case, MESSAGE should be written according to eachspecifications. For details, see Section 5.5.10.1 and 5.5.10.2.
[Description example] rdReqST_Binary, wrReqMT_ASCII
Table 4-18 PDU Name List for SLMP RequestType
SLMPPDU
ST
rdReqST-PDU
wrReqST-PDU
odReqST-PDU
MT
rdReqMT-PDU
wrReqMT-PDU
odReqMT-PDU

CLPAPDU NamerdReqST
wrReqST
odReqST
rdReqMT
wrReqMT
odReqMT

BAP-C2008ENG-001-K
1-86

4.3.1.38 RESPONSE_DATA conventions
A RESPONSE_DATA item specifies variables for storing a value to be returned by response
processing in the utility software using the data format specified by the RESPONSE_TYPE item (seeSection 4.3.1.40), following the conventions below. Note that the value specified needs to comply withthe data type of the RESPONSE_DATATYPE item (see Section 4.3.1.39).
(1) Specify the value by writing a reference to VALUE of an element of the TARGET item (seeSection 4.3.1.42), placing the reference between "$(" and ")"(see Section 4.3.3).
(Example: $(VALUE), $(ARGUMENT.ReadFrequencyData.VALUE))
When you want to write multiple values (when the RESPONSE_TYPE item is written so thatmultiple values are to be described), write the values in list format, placing each between "<" and">" (see Section 4.3.3).
(Example: <0x40><$(VALUE)>, <$(*.VALUE)>)(2) Within the configuration of a PDU specified in the RESPONSE_TYPE item, write the order of thedata other than the header section (command, subCommand, reqData) and the order of the datatypes in sequence.
(3) If the RESPONSE_TYPE item is omitted, or data other than the header section does not exist,
omit this item.

4.3.1.39 RESPONSE_DATATYPE conventions
A RESPONSE_DATATYPE item describes the data type of a value (RESPONSE_DATA) to be
returned by response processing, using the conventions below.
(1) Write the data type directly (see Section 4.3.1.10).
(2) Specify the data type by writing a reference to a DATATYPE item (see Section 4.3.1.10) of anelement, placing the reference between "$(" and ")" (see Section 4.3.3).
(Example: $(DATATYPE))(3) When multiple write registers have been written using the RESPONSE_DATA item (see Section0), specify the same number of data types as RESPONSE_DATA items, placing the
RESPONSE_DATATYPE items between "<" and ">" (see Section 4.3.3) as well.
(Example: <WORD><$(DATATYPE)>, <$(*.DATATYPE)>)(4) This item cannot be written when the RESPONSE_DATA item is omitted.
(5) Within the configuration of a PDU specified in the RESPONSE_TYPE item, write the order of thedata other than the header section (command, subCommand, reqData) and the order of the datatypes in sequence.
(6) If the RESPONSE_TYPE item is omitted, or data other than the header section does not exist,
omit this item.

4.3.1.40 RESPONSE_TYPE conventions
A RESPONSE_TYPE item describes the type of data format used in response processing.
Write a string that connects the response PDU name and ASCII or Binary using "_". For the response
PDU name, see "PDU name" in Table 4-19. [The table is an extraction from the "CC-Link IE Field
Network Specification (SLMP Specification Overview) BAP-C1605-005-A." For details of the contents
described in the table, see the "PDU List" in the "CC-Link IE Field Network Specification (SLMPSpecification Overview) BAP-C1605-005-A."] ASCII and Binary indicate that the data is to be sent in
ASCII mode or Binary mode, respectively. If a response is not performed (not required), omit this item.
[Description example] rdReqST_Binary, wrReqMT_ASCII
Table 4-19 PDU Name List for SLMP Response
Type
SLMPPDU
ST
rdResST-PDU
wrResST-PDU
MT
rdResMT-PDU
wrResMT-PDU

CLPAPDU NamerdResST
wrResST
rdResMT
wrResMT

BAP-C2008ENG-001-K
1-87

4.3.1.41 Convention of RESULTx
Write RESULTx in order to show the value applied when conditions are satisfied in theconditionMember division of CONDITION part (See Section 5.4.9). See Section 5.4.9 for details of thisconvention.
(1) A maximum of 32 RESULTx items can be written in 1 conditionMember division.

4.3.1.42 TARGET conventions
A TARGET item describes a reference to an element of a COMM_IF_INPUT part,
COMM_IF_OUTPUT part, COMM_IF_PARAMETER part, or COMM_IF_COMMAND part used in amethod or message. The conventions are indicated below. For the specifications of other items in acase where a reference is described in the TARGET item, see Section 4.3.4.
(1) In a case where reference is to be made to multiple elements in a TARGET item, write thedescription based on one of the below. Note, however, that you cannot write multiple references
to an element of a COMM_IF_COMMAND part.
Further, you cannot write a reference that mixes elements of different part types.
[1] List the elements as a set.
[2] Describe the elements with a "part label name.*" (when reference is to be made to allelements included in one part).
(Example: CommParameter.*)[3] Use a combination of the above (when reference is to be made to all elements of multiple
parts).
(2) Write "PARENT_TARGET" in a TARGET item of a method that is to serve as reference bydescribing the RELATED_METHOD item.
(3) Write "SEQ_TARGET" in elements that use SEQ in a RELATED_METHOD (see Section 4.3.1.33)
and RELATED_MESSAGE (see Section 4.3.1.32). Communication information cannot be
described in elements where "SEQ_TARGET" is written. Thus, the following items cannot be
described.
Table 4-20 Items that Cannot Be Written in Elements WhereSEQ_TARGET Is Written
Part Type
MethodMessage

CLPA

Items that Cannot Be Written
WRITE_REGISTER, WRITE_DATA, WRITE_DATATYPE, READ_REGISTER,
READ_DATA, READ_DATATYPE, INTERLOCK, REQ_FLAG, END_CONDITION,ERR_CONDITION, ERR_REGISTERREQUEST_TYPE, REQUEST_DATA, REQUEST_DATATYPE, RESPONSE_TYPE,RESPONSE_DATA, RESPONSE_DATATYPE, ERR_TYPE, ERR_CODE_RANGE

BAP-C2008ENG-001-K
1-88

4.3.1.43 UI_ATTRIBUTE conventions
A UI_ATTRIBUTE item describes the display window number and display sequence of elements of autility software display. The item describes the two values shown in Table 4-21 in order, withinbrackets. This item may be omitted if not required.
When you want to display one element in multiple utility software windows, write multiple numbers asa set (see Section 4.3.3, [2]).
(Example: [<1><1>] [<2><1>]
With an XML file: [<item>&lt;1&gt;&lt;1&gt;</item><item>&lt;2&gt;&lt;1&gt;</item>])
Table 4-21 List of Input Items of Common Utility Software Display Information
No.

Name

1.

Meaning

Window number (*1)

Setting
value
UINT8

Describes the window number to be displayed on the tool.
 Elements in which the same number is set are set up
and monitored in the same window. Even if theelements are from different BLOCK sections, theelements appear in the same window when the same
window number is written.
 The name of each window is written in the element"UI_ATTRIBUTE_Window**" of the DEVICE_INFO part.
Mapping is performed using the value of "**" and thewindow number. A "UI_ATTRIBUTE_Window**" that
corresponds to a window number is not required (theitem does not have to be written).
 When the UI_ATTRIBUTE item is written, the window
number cannot be omitted.
2. Display sequence
Describes the display sequence for the elements to be
UINT16, displayed in the same window.
 The elements are displayed in ascending order on eachwindow.
 The display sequence when the same value is set isfreely determined on the utility software side.
 Specify the window number and enter "-" when
specification of a display sequence is not required(example: <6><->). In this case, the display sequence isfreely determined on the utility software side.
 The "display sequence" is the display sequence, not the
number of rows displayed. The same value can be
written in another element, as described above. For
utility software that displays structure types in multiple
rows, even without value duplication, the number ofrows is no longer indicated if the structure types are
mixed.
*1: While the name is "Window number," this does not necessarily mean that the elements are divided
into windows when displayed using utility software. For example, a display in which the elements
are divided and switched via tabs, etc., is unproblematic.
*

CLPA

Elements can be classified using the UI_ATTRIBUTE item as well as the CATEGORY item. In acase where it is best to divide the screen, classify the elements using the UI_ATTRIBUTE item. To
classify elements within a screen, we recommend using the CATEGORY item.

BAP-C2008ENG-001-K
1-89

4.3.1.44 WRITE_DATA conventions
A WRITE_DATA item indicates the value to be written and is described following the conventions
below. Note that the value specified needs to comply with the data type of the WRITE_DATATYPE
item (see Section 4.3.1.45).
(1) Write the value directly. (Example: 0x40)(2) Specify the value by writing a reference to the VALUE of an element of a TARGET item (seeSection 4.3.1.42), the size of a DATATYPE item (see Section 4.3.1.10), an ASSIGN item (seeSection 4.3.1.3), and an element of a COMMAND_ARGUMENT part, placing the reference
between "$(" and ")" (see Section 4.3.3).
(Example: $(VALUE), <$(ARGUMENT.WriteFrequencyData.VALUE)>,$(DATATYPE).WORDSIZE)* When specifying the element of COMMAND_ARGUMENT, you cannot specify an element thatis not readable (NA, R, etc.) by the ACCESS item (see Section 4.3.1.1).
* When describing the writing of all elements inside TARGET using an asterisk (example:$(*.VALUE)), you cannot describe an element that is not writable in TARGET.
* When multiple elements are referenced in TARGET and one of the elements is to be selected
and written, you can write an element that is not writable in TARGET.
* In an element in which the METHOD_TYPE is PARAMETER and VALUE is referenced by
READ_DATA, you cannot describe a VALUE reference in WRITE_DATA.
(3) When multiple write registers have been described using the WRITE_REGISTER item (seeSection 4.3.1.47), specify the same number of write values as write registers, placing each
WRITE_DATA item between "<" and ">" (see Section 4.3.3) as well.
(Example: <0x40><$(VALUE)>, <$(*.VALUE)>)(4) This item cannot be written when the WRITE_REGISTER item is omitted.
(5) When processing that specifies and writes elements of a STRUCT type, which has empty spacein the offset, to a WRITE_DATA item of a method, zero is written to the empty section of theoffset. When a fixed value other than zero needs to be written, write an element in which the
DATATYPE is constant inside the STRUCT part.

4.3.1.45 WRITE_DATATYPE conventions
A WRITE_DATATYPE item describes the data type of the data to be written, using the conventions
below.
(1) Write the data type directly (see Section 4.3.1.10).
(2) Specify the data type by writing a reference to a DATATYPE item (see Section 4.3.1.10) of anelement, placing the reference between "$(" and ")" (see Section 4.3.3).
(Example: $(DATATYPE))(3) When multiple WRITE_DATA items (see Section 4.3.1.44) have been written using the
WRITE_REGISTER item (see Section 4.3.1.47), specify the same number of data types as
WRITE_DATA items, placing each WRITE_DATATYPE item between "<" and ">" (see Section
4.3.3) as well.
(Example: <WORD><$(DATATYPE)>, <$(*.DATATYPE)>)(4) This item cannot be written when the WRITE_REGISTER item is omitted.

4.3.1.46 WRITE_ORDER conventions
A WRITE_ORDER item sets the write order when the utility software writes multiple parameters to amodule. The write order specifications are described below.
(1) The writable values are 0 to 65535 (in decimal format).
(2) Write the numerical values starting from the lower number.
(3) Duplication of numerical values is permitted. If there is a duplicate, the order in which theparameters are written is freely determined on the utility software side.
(4) The numerical values do not need to be continuous. Numerical value gaps are permitted.
(5) The order does not need to be specified. If the element can be written last, this item may beomitted.
CLPA

BAP-C2008ENG-001-K
1-90

4.3.1.47 WRITE_REGISTER conventions
A WRITE_REGISTER item specifies the register for writing following the conventions below. The value
written needs to comply with the WRITE_DATA item (see Section 4.3.1.44).
(1) Write the link register directly using a string. For conventions, see the ASSIGN item (see Section
4.3.1.3). (Example: RWw1)(2) Specify the register by referring to the ASSIGN item of the element using a reference specification
based on "$(ASSIGN)" when a reference has been written in the TARGET item (see Section
4.3.1.42). (Reference cannot be made to any item other than the ASSIGN item.)(Example: $(InitParameters.CH1_AvgTime.ASSIGN),$(ARGUMENT.WriteFrequencyData.ASSIGN))* Reference cannot be made to a LABEL item (see Section 4.3.1.19) of an element notdescribed in the TARGET item.
* An element or argument in which the ACCESS item (see Section 4.3.1.1) is not writable ("NA,""R," etc.) cannot be specified. Note, however, that specification is unproblematic in a casewhere a description that refers to multiple elements in the TARGET item is written and theelements include an element that is not writable.
(3) If you want to specify multiple registers for writing, write the registers in list format in order, placing
each register name between "<" and ">" (see Section 4.3.3.).
(Example: <RWw4><$(ASSIGN)>)
Note that when multiple registers are written, writing is performed in order, starting from theregister written on the left.
(4) In a case where there are multiple content descriptions in the corresponding WRITE_DATA item,
including content that does not need to be written, write the content description of the
WRITE_REGISTER item corresponding to the content that does not need to be written as$(DUMMY). The content of the WRITE_DATA item corresponding to $(DUMMY) will not be read
written to the register. (Example: In a case where three content descriptions exist in the
WRITE_DATA item and the first content does not need to be written, write the
WRITE_REGISTER item as follows: <$(DUMMY)><RWw2><RWw3>.)(5) This item may be omitted if the method does not require writing.
When describing the WRITE_REGISTER item, describe the item so that writing is performed in unitsof 1 bit or in units of words. Note that if you specify writing in units of words by, for example, describing
writing in pairs to RWw0.0 with a data type of UINT8 and writing to RWw0.8 with a data type of UINT8,
in the WRITE_REGISTER item of a single METHOD part element, each WRITE_REGISTER item
does not need to be set to word units.

Prohibited XML character support

4.3.2

If you want to use prohibited XML characters as text between tags (<Tag> Use here </Tag>), write thecharacters in XML using an entity reference as shown in Table 4-22.
Table 4-22 Entity References for Prohibited Characters

*

CLPA

Prohibited Character
Entity Reference
<
&lt;
>
&gt;
&
&amp;
While entity references are defined for a double quote (") and apostrophe (') as well, thesecharacters can be used as is without using the entity references in XML text sections (use entity
references only when using the characters with attribute values). With CSP+ attribute values, thesecharacters cannot be written. Therefore, be sure to use the " and ' entity values with CSP+.

BAP-C2008ENG-001-K
1-91

4.3.3

Common conventions related to item values
The following describes the common description rules that apply when writing item values.
Table 4-23 Description Rules

No.
Rule
Meaning[1] "<>"
When you want to describe multiple contents in(single-byte angle an item, describe the multiple contents in list
brackets)format in order, placing each between "<" and">" (single-byte angle brackets.)
When you use single-byte angle brackets, youneed to use the brackets with all values of that
cell.
Sets and single-byte angle brackets cannot be
used in locations enclosed by single-byte angle
brackets.
[Examples]"<0x04><70>" and "'<0x16><70>''<0x18><80>'" are acceptable.
"<0x04>70", "'>0x16><70>' '0x18'", and"<<0><1><2>>" are not acceptable.
When a reference is used such as"<0x04>$(aaa.bbb.ASSIGN)," the value of thereference is acceptable if enclosed in angle
brackets.
* " 'A' 'B' " indicates a set of A and B.
[2] Description of
When you want to describe multiple data for themultiple data as a same item in a single cell, write "item" multiple
settimes in list format.

[3] "$()"[4] Value range
specification"[", "(", ")", "]"CLPA

Remarks"<" ">" (single-byte angle
brackets) fall under the categoryof prohibited XML characters. In
CSP+, write the brackets as "&lt;"
and "&gt;". (See Section 4.3.2.)[Description Example]<assign><item>&lt;0x04&gt;&lt;70&gt;&lt;3&gt;</item></assign>[Description Example]<ref><item>
CH1.BlockParameter.OffsetGain</item><item>
CH2.BlockParameter.OffsetGain</item></ref>
Use this when you want to differentiate a[Description Example]
reference description from a regular string (such $(InitParameters.OffsetGain)as for a METHOD argument, etc.). Enter roundparentheses after "$", writing the reference
inside the round parentheses.
For the reference description method, see
Section 4.3.4.
* A reference is always described with REF(see Section 4.3.1.30) and TARGET (seeSection 4.3.1.42). In these cases, directly
write the reference without using "$()".
A value range is indicated by entering two
 Closed intervalvalues separated by a comma (",") between[a,b] = {x | a ≤ x ≤ b}
brackets. Ranges can only be specified using Open interval
numerical values, not strings.
(a,b) = {x | a < x < b}
The left value indicates the lower limit, and the  Closed left and open right
right value indicates the upper limit. A closed
interval, closed left semi-openinterval is expressed using "[" , "]" (single-byte
intervalsquare brackets), and an open interval is[a,b) = {x | a ≤ x < b}expressed using "(", ")" (single-byte round Open left and closed rightbrackets).
interval, closed right semiIn a case where the upper limit or lower limit isopen interval
not to be specified, do not write a numerical(a,b] = {x | a < x ≤ b}
value. (Example: For a value less than or equal
to 6, write [,6].) Further, both the upper limit andthe lower limit may be omitted. (The range thenbecomes that indicated by the DATATYPE item.)
BAP-C2008ENG-001-K
1-92

No.
[5] "*"

Meaning
Remarks[METHOD and MESSAGE limit conventions][Description Example]
When you want to refer to all elements included CommParameter.*in a single part, write "Part label name.*" or<$(*.VALUE)>"<$(*.Item name)>". For details, see Section
4.3.4.
[6] Treatment of
Excluding items in which any string is writable, [Description Example]
special characters when you want to use any of the following¥, ¥$, ¥<, ¥>, ¥[, ¥], ¥(, ¥), ¥¥symbols in a string as a character, write thecode symbol following "¥".
"$" (dollar)"<", ">", "[", "]", "(", ")" (brackets)"¥" (backslash)[Items in which any string is writable]* While the convention "$()" of (3) is applicablewith a DATA item of designated elements, theconvention cannot be used with any of theother items. For this reason, special
characters can be written without using "¥".
[7] Space input
You can freely use spaces with any item that
permits input of any string and with any cell thattreats input values as a string type. However,you cannot use spaces in cells that treat input
values as any value other than a string type.
[8] Treatment of line To make strings easier to view when displayed
feedsusing utility software, you can enter a line feedin NAME, COMMENT, and DATA items only. You
cannot insert a line feed in any other item.
Note, however, that whether or not the line feedcode is reflected at the time of display depends
on the specifications of the utility software (notrequired).
[9] Use of common
Reference can be made to common information
information
defined in parts.
 Structure(STRUCT) Option list
(ENUM)
 Commandargument list
(COMMAND_
ARGUMENT)[10] "#"
Use this when you want to specify up to theThis may be combined with any
elements defined within the STRUCT part when convention. For example, you canreferring to an element in which the data type is write # within $(). Note, however,structure. (See Section 4.3.4.)
that you cannot write "#" inmultiple within a single reference
description. (The reference
description AA.BB#CC.DD#EE is
not possible.)[11] Handling ofControl characters other than return cannot be Example: TAB (horizontal tab)
control characters written.
cannot be written.

CLPA

Rule

BAP-C2008ENG-001-K
1-93

1 LABEL
2 LABEL2
3 CATEGORY
4 NAME
5 DATATYPE
6 DEFAULT
7 RANGE
8 MIN_INC
9 ENG_UNIT
10 ASSIGN
11 ACCESS
12 REF
13 COMMENT
14 UI_ATTRIBUTE
15 WRITE_ORDER
16 DATA
17 ARGUMENT
18 TARGET
19 METHOD_TYPE
20 WRITE_REGISTER
21 WRITE_DATA
22 WRITE_DATATYPE
23 READ_REGISTER
24 READ_DATA
25 READ_DATATYPE
26 INTERLOCK
27 REQ_FLAG
28 END_CONDITION
29 ERR_CONDITION
30 ERR_REGISTER
31 RELATED_METHOD
32 MESSAGE_TYPE
33 REQUEST_TYPE
34 REQUEST_DATA
35 REQUEST_DATATYPE
36 RESPONSE_TYPE
37 RESPONSE_DATA
38 RESPONSE_DATATYPE
39 ERR_TYPE
40 ERR_CODE_RANGE
41 RELATED_MESSAGE
42 OFFSET
43 CODE
44 CONDITIONXVARIABLE
45 CONDITIONx
46 RESULTx
47 RELATED_ELE *7

CLPA

X
X
X
X
X
X
X
X
X
O
X
X
X
O
X
*6
X
X
X
O
O
O
O
O
O
X
X
X
X
X
O
X
O
O
O
O
O
O
O
X
O
X
X
X
X
X
X

X
X
X
X
X
X
O
X
X
X
X
O
X
O
X
O
X
O
O
X
X
X
X
X
X
X
O
O
X
X
X
O
X
X
X
X
X
X
X
O
X
X
X
X
O
*5
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
*2
X
X
X
O
O
O
O
O
O
O
O
O
O
O
X
X
X
O
O
X
O
O
X
X
X
X
X
X
O
*5
X

X
X
X
X
X
X
O
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
O
X
X
X
X
O
*5
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
O
X
O
O
O
O
O
O
X
X
X
X
X
X
X
X
O
O
X
O
O
X
X
X
X
X
X
X
X
X

X
X
X
X
O
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X *4
X
X
X *4
X
X
X
X
X
X
X
X
X
X *4
X
X
X *4
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
O
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
O
X
X
X
X
X
*5
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
O
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
O

CONDITION Reference(*3)

COMMAND_ARGUMENT
Reference

ENUM Reference

STRUCT Reference (*1)

Reference to All Elements
Using * [(5)]Range Specification
Using [] or () [(4)]Reference Description
Using $() [(3)]Multiple Descriptions
as a Set [(2)]Multiple Descriptions
Using <>[(1)]Table 4-24 List of Conventions Applicable to Each Item

X
X
X
X
X
X
O
O
O
X
O
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X

BAP-C2008ENG-001-K
1-94

*1: For STRUCT part references, applicable items as well as applicable parts are predetermined.
(See Section 4.3.1.10.)*2: $() of a DATA item can only be written with specific elements defined in the specification.
*3: Can only be written with elements of BLOCK_PARAMETER.
*4: Cannot write direct references, but it does not matter if the DATATYPE item of the elements
referenced with the TARGET item is STRUCT type. Therefore, the result of solving the reference of$(DATATYPE) can be of STRUCT type.
*5: Follows the specifications of the item which is the reference source of RESULTx.
(Ex: range specifications with [] or () can be used in RESULTx referenced from RANGE items.)*6: Brackets in DATA can only be written with specific elements of CC-Link IE TSN (the elements inwhich the data type is specified as the array type).
*7: Can only be used under the specific conditions. For details, see descriptions of each item.
The following shows the combinability of these conventions in a single item. The combinability inrelation to common information (STRUCT part, ENUM part, and COMMAND_ARGUMENT part)references is described below.
Table 4-25 shows the combination rules related to other conventions.
(1) STRUCT part
In an item that describes a reference to a STRUCT part, combined use with other conventions is
not permitted.
(2) ENUM part
In an item that describes a reference to an ENUM part, combined use with other conventions is
not permitted .
(3) COMMAND_ARGUMENT part
In an item that describes a reference to a COMMAND_ARGUMENT part, combined use withother conventions is not permitted .
(4) CONDITION parts
In items which have written references to CONDITION parts, this convention cannot be used withother conventions.

CLPA

BAP-C2008ENG-001-K
1-95

Table 4-25 Convention Combined Use Rules"-" (Abbreviationsome values)"< >" (Multiple value"," (Multiple value
representation byrepresentation byhalf-width angle
commas)brackets)"$()" (Reference)"[", " (", ")", "]"(Specified range ofvalues)"*" (wild card)

Multiplearrangements areprohibited. However,multiple descriptionsof <-> are permitted.
(Ex: <3><->, <5><->in UI_ATTRIBUTE ispermitted)-- can be written
inside < >.

<>Multiple- is only permitted
Representations when inside < >.

Combination not
permitted$()"[", "(" ,")", "]"

Combination not
permitted

Combination not
permitted*

Multiple description
such as "<a><b>"are permitted.
Writing <> inside <>is not permitted.
Description like
Multiple description"<3><4>, <5><6>" issuch as "a, b, c" ispermitted. <,> arepermitted.
not permitted.
Combination such
Combination suchas "$()<a><b>" areas $(), $() ispermitted. <$()> arepermitted. $(,) is notalso permitted. $(<>)
permitted.
is not permitted.
Combination ispermitted whenwriting multiple
Combination notranges such as " [1,permitted2], [10, 15]". Only
one "," can be
written insidebrackets.

Combination suchas "<$(*.VALUE>)"is permitted.

$($()) can be used.
Combination suchas $(),$() ispermitted.
Combination ispermitted.
(Combination when
specifying upper
limit and lower with
set values of otherparameters)

Multiple description Combinationof reference using * permitted such as
is permitted.
"<$(*.VALUE>)".

Multiple description
using commas ispermitted, such as"[1, 2], [10, 15]".
Writing brackets
inside brackets is
not permitted.

Combination not
permitted

Multiple description
using commas ispermitted, such as"xx.*, yy.*". Writing
multiple "*" in strings
not separated bycommas or < > isnot permitted, suchas "*.xx.*".

: Combined use not permitted

CLPA

BAP-C2008ENG-001-K
1-96

4.3.4

Conventions for references that use labels(1) Common conventions
When you want to refer to a value of a part, element, or item of an element, you can describe thereference using a label name (you cannot use a Label2 name). The following describes thedescription specifications for references based on a label name.
(a) When you want to refer to an element within the same part, write only the label name of theelement.
(b) When you want to refer to a part within the same section, write the label name of the part.
(c) When you want to refer to an element of a different part within the same section, write "Partlabel name. Element label name".
(d) When you want to refer to a value of an item of an element, write "Element label name.Itemname". Note, however, that the specifiable items are only ASSIGN, DATATYPE, and
ARGUMENT items.
(e) When you want to refer to an element beyond the section, write "Section label name.Part
label name. Element label name", adding the label name of the section at the start of thepath. Note, however, that for common information (STRUCT part, ENUM part,
COMMAND_ARGUMENT part), a reference cannot be made beyond the section.
(f) The type of reference (part, element, item) is uniquely determined by the item that describes
the reference, as shown in Table 4-26. When determining a reference, make sure that thereference type is appropriate.
(g) When the data type of the element of the reference is structure and you want to refer to only
one element defined within the STRUCT part, use # and write "Element label name ofreference#Element label name within STRUCT part".
(h) When the data type of the element of the reference is structure and you want to refer to theaddress information of one element defined within the STRUCT part, use # and write"Element label name of reference#Element label name within STRUCT part.ASSIGN".
* While STRUCT does not have the item ASSIGN, reference is made to the ASSIGN item
to indicate that reference is being made to address information, making a distinction froma case where reference is made to the value of the item OFFSET itself.
Table 4-26 List of Reference Writable Items

Reference
Reference to part

Reference Writable Item
Items in which common information(STRUCT, ENUM,
COMMAND_ARGUMENT) can beused

Reference to element

REF, TARGET, RELATED_METHOD,
RELATED_MESSAGE
Items in which a reference description
using $() can be used in Table 4-24
• Reference to RESULTx item of
CONDITION part• Reference to item used for
conditional determination from
CONDITIONXVARIABLE item of
CONDITION part.

Reference to item

Remarks
While references to elements andreferences to items overlap in terms of
writable items, the conventions forcommon information are predetermined,
and thus the reference is assessable. For
items that can use common information,
see Table 4-24.
--(2) Conventions applicable to items within METHOD and MESSAGE parts only
[1] When you want to refer to all elements included in a single part in a TARGET item, write "Partlabel name.*".
Note that "*" is applicable to references to elements only. You cannot write "Section label
name.*" to refer to all parts within a section.
[2] If you want to refer to an item of an element specified by a TARGET item set up in a METHOD
or MESSAGE part from an item other than a TARGET item, omit the path up to the element of
the part and write the item name only.

CLPA

BAP-C2008ENG-001-K
1-97

[3] If "<$(*.Item name)>" is written, the description describes all elements of the TARGET item
enclosed by angle brackets based on the conventions of (1) of Table 4-23.
(Example: "<$(*.ASSIGN)>" is equivalent to "<$(First element of TARGET.ASSIGN)><$(Second element of TARGET.ASSIGN)><(Third element of TARGET.ASSIGN)>. . . ".)[4] In the TARGET item of a METHOD part referred to by a RELATED_METHOD item (seeSection 4.3.1.33), be sure to write "PARENT_TARGET", which indicates that the sameelement as the TARGET item used in the reference source is always used. The same holds
true for the TARGET item of a MESSAGE part referred to by a RELATED_MESSAGE item
(see Section 4.3.1.32).
[5] If you want to describe a reference to argument information referred to by an ARGUMENT
item of a COMM_IF_COMMAND part in a method or message that refers to the element of a
COMM_IF_COMMAND part in a TARGET item, enter a "." after "ARGUMENT" followed by adescription of the reference to the element of the argument.
(Example: <$(ARGUMENT.WriteFrequencyData.ASSIGN)>)[6] When you want to write or read all arguments of a command when the TARGET item is acommand, write <$(ARGUMENT.*.Item name)>. ("VALUE" can be written as the item name aswell.)
Example: In a case where the COMMAND_ARGUMENT of a COMMAND part referred to by
TARGET has the elements "Ele1", "Ele2", and "Ele3", then <$(ARGUMENT.*.VALUE)> written
in the WRITE_DATA item means<$(ARGUMENT.Ele1.VALUE)><$(ARGUMENT.Ele2.VALUE)><$(ARGUMENT.
"Ele3.VALUE)>, for example.
[7] When you want to acquire a write value from utility software for inputs, outputs, parameters,
and commands specified in a TARGET item, or when you want to indicate that a read value isto be displayed with utility software, use VALUE as described below.
 For inputs, outputs, parameters: $(VALUE) For COMMAND arguments: $(ARGUMENT.Element label name.VALUE)
Such a description indicates that the value acquired from the utility software is to be used
when written in the WRITE_DATA or REQUEST_DATA item, or that the read value is to be
returned to the utility software when written in the READ_DATA or RESPONSE_DATA item.
Note that VALUE based references can only be used with references to elements specified by
the TARGET item, as described above. Such references cannot be used as references toregular elements. (A description such as Section LABEL.PartLABEL.Element LABEL.VALUE
is not permitted.)[8] When you want to indicate that the data size of an element selected in the TARGET item is tobe written using a REQUEST_DATA item or WRITE_DATA item, write the description using thedescription method of

CLPA

BAP-C2008ENG-001-K
1-98

Table 4-27. Note that it is not possible to write the data size by directly referring to an element
other than that of TARGET. [A description such as$(CommParameter.SelectParam.DATATYPE.WORDSIZE) is not permitted.]* For example, depending on the SLMP command, the data size needs to be written in the
REQUEST_DATA item. When multiple parameters are specified in the TARGET item andthe data size differs for each parameter, you can switch the data size for each parameterselected by using this convention.

CLPA

BAP-C2008ENG-001-K
1-99

Table 4-27 Description Method of Data Size of Element
No.
Description Method
1.
$(DATATYPE).WORDSIZE

2.

$(DATATYPE).BITSIZE

Meaning
Indicates the word size of the data type of the referred element.
Indicates 2 for DWORD and 4 for LREAL, for example. Applicable tostructure-type elements as well. Indicates a raised value if the latter
half of the word is not assigned. (Example: Indicates 3 if only up to 2.A
is used within STRUCT.)
Indicates the bit size of the data type of the referred element.
Indicates 1 for BOOL and 8 for BYTE, for example. Applicable tostructure-type elements as well. Does not raise a value as is donewith WORDSIZE, but rather indicates the used value as is.
(Example: Indicates 42 if only up to 2.A is used within STRUCT.)[9] Reference from each item of a METHOD or MESSAGE part can only be made to a part orelement within the same COMM_IF section. Reference cannot be made directly to an elementof a BLOCK section. (Refer to an element of a COMM_IF section that refers to a BLOCK
section from a METHOD or MESSAGE part.)

CLPA

BAP-C2008ENG-001-K
1-100

CSP+ File Details

5.

This chapter describes the details of CSP+ file conventions.
A single CSP+ file is written as a single XML element enclosed by the XML tag name "profile" (namespace: "http://cc-link.org/cspplus/ver1/"; hereinafter the same and thus omitted). The following shows adescription example of an XML tag that expresses a single CSP+ file description.
<p:profile xsi:schemaLocation="http://cc-link.org/cspplus/ver1/ CSPPSchema.xsd"
xmlns:p="http://cc-link.org/cspplus/ver1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">:::</p:profile>[Name Space]
With XML, a name space is used to indicate the specifications in which the XML element name or
attribute name is defined. In the above example,
http://cc-link.org/cspplus/ver1/
http://www.w3.org/2001/XMLSchema-instance
written in lines two and three indicate the name space, with the former serving as the name space of
CSP+ specifications, and the latter as the name space of XML specifications.
The name space increases in length when described for all XML element names and attribute names,
and thus an abbreviated format is declared and used as is done in lines two and three in the above
example. The abbreviated format of the name space is declared using the following format:
xmlns: Prefex = "Name space"In this example, the prefix "p: " expresses the name space of CSP+ specifications on line two, and theprefix "xsi" expresses the name space of XML specifications on line three. In the above example,
p:profile is the XML element name defined in CSP+ specifications, and xsi:schemaLocation is theattribute name defined in XML specifications. The string used in the abbreviated format may be a string
other than that shown in the above example as well. For example, in a case where the following is
declared in line two:
"xmlns:cspp="http://cc-link.org/cspplus/ver1/"
the abbreviated format is written as "cspp:profile" rather than "p:profile".
With CSP+ descriptions, the attribute defined in CSP+ specifications is described "without a namespace".
Table 5-1 shows a list of CSP+ XML elements, and Table 5-2 shows a list of attributes of the element"profile".
Table 5-1 CSP+ XML Element List
No. XML Element Name
1. profile

Description Details
Describes CC-Link family protocol (CSP+).

Required/Optional
Required

Table 5-2 profile Element Attribute List
No.

Description Details
Required/Optional
Indicates the location of XML schema of CSP+. This
attribute is defined in XML specifications, and thus isused along with the name space
1. schemaLocation"http://www.w3.org/2001/SMLSchema-instance" defined
Optional
in XML specifications.
Specify "http://cclink.org/cspplus/ver1/CSPPSchema.xsd".
Further, an element that expresses a section is written as one XML child element of the profile element
indicated by CSP+. One section is described as one XML element. Table 5-3 shows a list of childelements of the profile element.

CLPA

Attribute NameBAP-C2008ENG-001-K
1-101

Table 5-3 List of XML Child Elements of profile Element
No.
1.
2.
3.
4.

XML Element Name
filedeviceblock
commIfDescription Details
Describes the contents of the FILE section
Describes the contents of the DEVICE section
Describes the contents of the BLOCK section
Describes the contents of the COMM_IF section

Required/Optional
Required
Required
Required
Required

FILE Section

5.1

The FILE section comprises one FILE_INFO part only. The one part is written as a single XML
element. A comment may also be written (option).
FILE section
FILE_INFO part

Describes the contents of the FILE_INFO part.
Figure 5-1 Structure of FILE Section

In XML format, the FILE section is written as an XML element of the XML element name "file". Table
5-4 shows a list of the attributes of the file element, and Table 5-5 shows a list of XML child elements.
Table 5-4 List of Attributes of file Element
No.
1.

Attribute Name

Description Details
Describes the label that identifies the FILE section.
(See Section 4.3.1.19.) (Example: "FileSection")label

Required/Optional
Required

Table 5-5 List of XML Child Elements of file Element
No.

XML Element Name1.

comment2.

fileInfo

CLPA

Description Details
Describes the comment related to the FILE section.
(See Section 4.3.1.6.)
Describes the contents of the FILE_INFO part.

Required/Optional
Optional
Required

BAP-C2008ENG-001-K
1-102

5.1.1

FILE_INFO part5.1.1.1 Overview
A FILE_INFO part describes information related to the CSP+ file, such as the file modification date andtime.
Figure 5-2 shows the elements that make up the FILE_INFO part.

Figure 5-2 Structure of FILE_INFO Part
The configuration of each element of the FILE_INFO part, that is, the items that should be describedwithin each element, is the same. Figure 5-3 shows the configuration of an element of the FILE_INFO
part.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
DATATYPE item
DATA item
Figure 5-3 Structure of Element of FILE_INFO Part

CLPA

BAP-C2008ENG-001-K
1-103

Table 5-6 lists the elements. A single element is described as a single XML element. For the detailed
description specifications of each element, see Section 5.1.1.3.
Table 5-6 Element List for FILE_INFO PartNo.

Element Name

1.

CreateDate

2.

CreateTime

3.
4.

ModDateModTime5.

Language

6.

CCLinkFamilyProfileVersion

7.

FileVersion

Description Details
Describes the date on which the CSP+ file wascreated.
Describes the time at which the CSP+ file wascreated.
(Used when the utility software supports anotherlanguage.)
Describes the last modification date.
Describes the last modification time.
Describes the information of the language inwhich the CSP+ file is written.
Describes the version of CSP+ description
specifications.
Describes the version of the profile information
for the target equipment.

Required/Optional
Required
Required
Required
Required
Required
Required
Required

Table 5-7 shows the items described in the elements of the FILE_INFO part.
Table 5-7 Item List for FILE_INFO Part
No.

Item Name

Description Details

1.

LABEL

Describes the label for identifying the element.

2.

LABEL2

Describes the label for identifying the element. (Usedwhen the utility software supports another language.)

3.

CATEGORY

Describes the category for grouping the element.

4.

NAME

Describes the name of the element.

5.

DATATYPE

Describes the data type of the contents described in
the DATA item.

6.

DATA

Describes the contents of the element.

CLPA

Description
Specifications
See Section
4.3.1.19
See Section
4.3.1.20
See Section
4.3.1.4
See Section
4.3.1.24
See Section
4.3.1.10
See Section
4.3.1.9

Required/Optional
Required
Optional
Optional
Optional
Required
Required

BAP-C2008ENG-001-K
1-104

5.1.1.2 XML format of FILE_INFO partIn XML format, the FILE_INFO part is described as an XML element having the XML element name"fileInfo". Table 5-8 shows a list of the attributes of the fileInfo element, and Table 5-9 shows a list of
the XML child elements.
Table 5-8 Attribute List for fileInfo Element
No.
1.

Attribute Name

Description Details
Describes the label for identifying the FILE_INFO part.
(See Section 4.3.1.19.) (Example: "FileInformation")label

Required/Optional
Required

Table 5-9 XML Child Element List for fileInfo Element
No.

XML Element Name1.

comment2.

fileInfoMember

Description Details
Describes the comment related to the FILE_INFO part.
(See Section 4.3.1.6.)
Describes the contents of the elements of the
FILE_INFO part.

Required/Optional
Optional
RequiredIn XML format, the element of the FILE_INFO part is described as an XML element having the XML
element name "fileInfoMember". Table 5-10 shows a list of attributes of the fileInfoMember element,
and Table 5-11 shows a list of XML child elements.
Table 5-10 Attribute List for fileInfoMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.(See
Section 4.3.1.19.) The contents written for this label are
regulated by CSP+ specifications. For details, see
Section 5.1.1.3.

Required/Optional
Required

Table 5-11 XML Child Element List of fileInfoMember Element
No.
1.
2.
3.
4.
5.

XML Element Namelabel2
category
namedatatype
data

Description Details
Describes the LABEL2 item
Describes the CATEGORY item
Describes the NAME item
Describes the DATATYPE item
Describes the DATA item

Write the FILE_INFO part using a format such as shown below.
<p:fileInfo label="Write in accordance with the description details of Table 5-8 ‘AttributeName label’”><p:comment>”Write in accordance with the description details of Table 5-9 ‘XML Element
Name comment’”</p:comment><p:fileInfoMember label=”Write in accordance with the description details of Table 5-10
‘Attribute Name label’”><p:label2>”Write in accordance with the description details of Table 5-11 ‘XML Element
Name label2’”</p:label2><p:category>”Write in accordance with the description details of Table 5-11 ‘XML
Element Name category’”</p:category><p:name>”Write in accordance with the description details of Table 5-11 ‘XML Element
Name name’”</p:name><p:datatype>”Write in accordance with the description details of Table 5-11 ‘XML
Element Name datatype’”</p:datatype><p:data>”Write in accordance with the description details of Table 5-11 ‘XML Element
Name data’”</p:data></p:fileInfoMember><p:fileInfoMember label=”Write in accordance with the description details of Table 5-10
‘Attribute Name label’”>::</p:fileInfoMember >::</p:fileInfo>

CLPA

BAP-C2008ENG-001-K
1-105

5.1.1.3 Description details of each element(1) Item description of CreateDate element
Table 5-12 Item Description Specifications of CreateDate Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CreateDate"
Write "CreateDate" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON"
Write "File Creation Date" in the case of English CSP+ files[Recommended specifications]Write "STRING(10)"Write the file creation date.
Write the date in the format yyyy/mm/dd.
Write the year based on the Western calendar.
Do not suppress any zeros in the month or day.

(a) Item description example of CreateDate element<p:fileInfoMember label="CreateDate"><p:label2><p:item>CreateDate</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>File Creation Date</p:item></p:name><p:datatype><p:item>STRING(10)</p:item></p:datatype><p:data><p:item>2012/04/01</p:item></p:data></p:fileInfoMember>(2) Item description of CreateTime element
Table 5-13 Item Description Specifications of CreateTime Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CreateTime"
Write "CreateTime" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "File Creation Time" in the case of English CSP+ files[Recommended specifications]Write "STRING(8)"Write the file creation time.
Write the time in the format hh:mm:ss.
Do not suppress any zeros in the hour, minute, or second.

(a) Item description example of CreateTime element<p:fileInfoMember label="CreateTime"><p:label2><p:item>CreateTime</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>File Creation Time</p:item></p:name><p:datatype><p:item>STRING(8)</p:item></p:datatype><p:data><p:item>09:08:07</p:item></p:data></p:fileInfoMember>

CLPA

BAP-C2008ENG-001-K
1-106

(3) Item description of ModDate element
Table 5-14 Item Description Specifications of ModDate Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ModDate"
Write "ModDate" in the case of English CSP+ files [Recommended
specifications]Write "COMMON"
Write "Last Modified Date" in the case of English CSP+ files [Recommended
specifications]Write "STRING(10)"Write the last modification date.
Write the date in the format yyyy/mm/dd.
Write the year based on the Western calendar.
Do not suppress any zeros in the month or day.

(a) Item description example of the ModDate element<p:fileInfoMember label="ModDate"><p:label2><p:item>ModDate</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Last Modified Date</p:item></p:name><p:datatype><p:item>STRING(10)</p:item></p:datatype><p:data><p:item>2012/05/06</p:item></p:data></p:fileInfoMember>(4) Item description of ModTime element
Table 5-15 Item Description Specifications of ModTime Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ModTime"
Write "ModTime" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Last Modified Time" in the case of English CSP+ files[Recommended specifications]Write "STRING(8)"Write the last modification time.
Write the time in the format hh:mm:ss.
Do not suppress any zeros in the hour, minute, or second.

(a) Item description example of ModTime element<p:fileInfoMember label="ModTime"><p:label2><p:item>ModTime</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Last Modified Time</p:item></p:name><p:datatype><p:item>STRING(8)</p:item></p:datatype><p:data><p:item>11:22:33</p:item></p:data></p:fileInfoMember>

CLPA

BAP-C2008ENG-001-K
1-107

(5) Item description of Language element
Table 5-16 Item Description Specifications of Language Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "Language"
Write "Language" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Supported Language" in the case of English CSP+ files[Recommended specifications]Write "STRING(12)"Write the information of the language in which CSP+ is written.
The following shows a list of defined language information as of May 2012:
 Japanese: "ja" English: "en"
 Chinese (simplified Chinese): "zh-Hans"
 Korean: "ko"
 Chinese (unsimplified Chinese): "zh-Hant"
 German: "de"
 French: "fr"
 Russian: "ru"
 Italian: "it"
 Spanish: "es"
 Portuguese: "pt"When you want to use a language code other than the above, you need tosubmit an application to the CC-Link Partner Association. For an updated listof language information, contact the CC-Link Partner Association.

(a) Item description example of the Language element<p:fileInfoMember label="Language"><p:label2><p:item>Language</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Supported Language</p:item></p:name><p:datatype><p:item>STRING(12)</p:item></p:datatype><p:data><p:item>ja</p:item></p:data></p:fileInfoMember>

CLPA

BAP-C2008ENG-001-K
1-108

(6) Item description of CCLinkFamilyProfileVersion element
Usable conventions varies depending on CSP+ Specifications Version described in this element. See
Chapter 9 for details.
Table 5-17 Item Description Specifications of CCLinkFamilyProfileVersionElement
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CCLinkFamilyProfileVersion"
Write "CCLinkFamilyProfileVersion" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "CSP+ Specification Version" in the case of English CSP+ files[Recommended specifications]Write "STRING(32)"
Write the CSP+ specification version.
For the CSP+ specification version, see Chapter 1.
Note that the CSP+ specification version is expressed using two(alpha)numeric characters separated by a dot ("."), such as "x.y".
x: Indicates the major version.
y: Indicates the minor version.
We recommend that the utility software execute operations in accordancewith defined specifications, even if the minor version is wrong.
The minor version may be omitted if the minor version is "0".

(a) Item description example of CCLinkFamilyProfileVersion element<p:fileInfoMember label="CCLinkFamilyProfileVersion"><p:label2><p:item>CCLinkFamilyProfileVersion</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>CSP+ Specification version</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>3.0</p:item></p:data></p:fileInfoMember>

CLPA

BAP-C2008ENG-001-K
1-109

(7) Item description of FileVersion element
Table 5-18 Item Description Specifications of FileVersionElement
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "FileVersion"
Write "FileVersion" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "File Version" in the case of English CSP+ files[Recommended specifications]Write "STRING(32)"
Write the file version.
Write the version using two (alpha)numeric characters separated by a dot("."), such as "x.y".
x: Describes the major version.
A higher major version for the same module indicates that the file is newer.
If the module is the same and the description information is the same for
CSP+ files having different supported language information, the value ofthe major number is used to determine whether or not the CSP+ files are
the same.
y: Describes the minor version.
A higher minor version with the same modules, supported languages, andmajor versions indicates that the file is newer.
The minor version may be omitted if the minor version is "0".
If the major version is increased, the minor version returns to 0.
Table 5-19 indicates the file version upgrade rules.
Table 5-19 File Version Upgrade Rules

No.
1.
2.
3.
4.

5.

Rule
Write a different file version for a CSP+ file when you change the contents ofthe file but the file has the same device version and supported language
information.
If the CSP+ files have the device versions, write a higher value for the fileversion of the newer file.
If you upgrade the device version, set the major version of the file version to1.
Write the same major number for the file versions of CSP+ files having thesame contents but different supported language information.
Upgrade the minor version if you upgrade only language dependent
information and do not need to upgrade the CSP+ files of other supported
language information. For any other modifications (including addition ofelements, etc.), major version must be updated. (However, this excludes
cases in which device version is updated.)• Modification of CATEGORY item, NAME item, COMMENT item
• Modification of DATA item of FILE_INFO part

Remarks(a) Item description example of FileVersion element<p:fileInfoMember label="FileVersion"><p:label2><p:item>FileVersion</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>File Version</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>1.0</p:item></p:data></p:fileInfoMember>

CLPA

BAP-C2008ENG-001-K
1-110

DEVICE Section

5.2

The DEVICE section comprises one DEVICE_INFO part only. The one part is written as a single XML
element. A comment may also be written (option).

DEVICE section
DEVICE_INFO part

Describes module identification information andinformation related to specifications.

Figure 5-4 Structure of DEVICE Section
In XML format, the DEVICE section is written as an XML element of the XML element name "device".
Table 5-20 shows a list of the attributes of the device element, and Table 5-21 shows a list of XML
child elements.
Table 5-20 List of Attributes of device Element
No.
1.

Attribute Namelabel

Description Details
Describes the label that identifies the DEVICE section.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-21 List of XML Child Elements of device Element
No.

XML Element Name

1.

label

2.

deviceInfo

CLPA

Description Details
Describes the comment related to the DEVICE section.
(See Section 4.3.1.6.)
Describes the contents of the DEVICE_INFO part.

Required/Optional
Optional
Required

BAP-C2008ENG-001-K
1-111

5.2.1

DEVICE_INFO part5.2.1.1 Overview
A DEVICE_INFO part describes product identification information and information related to productspecifications.
Figure 5-5 shows the elements that make up the DEVICE_INFO part.
Figure 5-6 shows the elements that make up the DEVICE_INFO part "for tool link" in CC-Link IE TSN.

Figure 5-5 Structure of DEVICE_INFO Part

DEVICE_INFO part for tool link
DedicatedToolFlg element

InstallRegistryValueName element

DedicatedToolName element

ExePathRegistryKeyName element

InstallRegistryKeyName element

ExePathRegistryValueName element

Figure 5-6 Structure of DEVICE_INFO Part for tool link in CC-Link IE TSN

CLPA

BAP-C2008ENG-001-K
1-112

The configuration of each element of the DEVICE_INFO part, that is, the items that should be
described within each element, is the same. Figure 5-7 shows the configuration of an element of the
DEVICE_INFO part.

Element

LABEL item
LABEL2 item
CATEGORY item
NAME item
DATATYPE item
DATA item

Figure 5-7 Structure of Element of DEVICE_INFO Part

CLPA

BAP-C2008ENG-001-K
1-113

Table 5-22 lists the elements. Table 5-23 lists the elements for tool link when the communicationinterface is CC-Link IE TSN. A single element is described as a single XML element. For details of thedescription specifications of each element, see Section 5.2.1.3.
Table 5-22 Element List for DEVICE_INFO PartNo.

Description Details
Required/Optional
Describes the name of the vendor that manufactured
1. VendorName
Requiredthe module.
Describes the vendor code of the vendor that
manufactured the module. Describes the fifth to eighth
2. VendorCode
Required
digits of the partner member number of the CC-Link
Partner Association.
3. DeviceModel
Describes the model of the module.
Required
Describes the product ID of the module. Describes the
4. ProductID
ID managed by the vendor that manufactured the*2module.
5. DeviceTypeID
Describes the ID that indicates the type of the module.
*1
6. DeviceTypeDetail
Describes the specific device type.
*1
7. Version
Describes the device version of the module.
Required
Describes whether the device version is to be shown to
8. VersionDisplayFlg
Requiredor hidden from the user.
Describes the policy of the relationship between themass production device version and the device version
9. VersionPolicyType
Required
written in the CSP+ file when accessing the mass
production device using the CSP+ file.
Describes the version value to be displayed when thevalue (Version) of the device version acquired from the
10. DisplayVersionValue
Optional
mass production device differs from the version value
displayed to the user on utility software.
11. VersionComment
Describes the comment related to the device version.
Optional
12. DeviceConfigurationID Describes the device configuration ID.
Optional
13. DeviceConfigurationComment Describes the device configuration comment.
Optional
Describes the URL when module information is
14. ReferenceURL
Optional
disclosed on the Web.
Describes an explanation of the information indicated
15. URLInfo
Optional
by ReferenceURL.
16. Outline
Describes the general specifications of the device.
Optional
17. Feature
Describes the features of the device.
Optional
Describes the device specifications using a set of
18. SpecList
Optional
strings.
19. PowerSupplyVoltage
Describes the power supply voltage in volts (V).
Optional
Describes the current consumption in milliamperes
20. ConsumptionCurrent
Optional(mA).
Describes the icon file name used when displaying the
21. IconFileName
module as an icon with utility software, including the
Optional
extension (.ico).
Describes the graphics file name used when the device
22. GraphicsFileName
is displayed with utility software, including the extension
Optional(.bmp, png, .jpg, .gif).
Describes the height of the external dimensions along
23. Height
Optional
with the unit of measurement.
Describes the width of the external dimensions along
24. Width
Optional
with the unit of measurement.
Describes the depth of the external dimensions along
25. Depth
Optional
with the unit of measurement.
Describes the weight along with the unit of
26. Weight
Optional
measurement.
27. Price
Describes the price along with the unit of measurement.
Optional
Describes the name of the window specified by
28. UI_ATTRIBUTE_Window**
Optional
UI_ATTRIBUTE. Describes the window number in "**".

CLPA

Element

BAP-C2008ENG-001-K
1-114

*1: Either the DeviceTypeID element or DeviceTypeDetail element must be written. Omitting both isprohibited. It is acceptable to write both, but in that case, the value of DeviceTypeDetail elementtakes precedence.
*2: This element is required in CC-Link IE TSN. This element is optional in other networks.
Table 5-23 Additional Element of DEVICE_INFO Part in CC-Link IE TSN
No.

Element

Description Details

Required/
Optional

Write whether or not there is a supported dedicatedOptional
tool.
2.
DedicatedToolName
Write the tool name of the supported dedicated tool.
*1
Write the existing registry key name only when the3.
InstallRegistryKeyName*1
supported dedicated tool is installed.
Write the existing registry value name only when the4.
InstallRegistryValueName*2
supported dedicated tool is installed.
Write the registry key name that has the path
5.
ExePathRegistryKeyName
information of the execution file (.exe) of the*1
supported dedicated tool.
Write the value name of the registry where the path
6.
ExePathRegistryValueNameof the execution file (.exe) of the supported*1
dedicated tool is written.
*1: Required when DedicatedToolFlg is written and its DATA is 1. Otherwise, writing is prohibited.
1.

DedicatedToolFlg*2: Optional when DedicatedToolFlg is written and its DATA is 1. Otherwise, writing is prohibited.

CLPA

BAP-C2008ENG-001-K
1-115

Table 5-24 shows the items described in the elements of the DEVICE_INFO part.
Table 5-24 Item List for DEVICE_INFO Part
No.

Item Name

Description Details

1.

LABEL

Describes the label for identifying the element.

2.

LABEL2

Describes the label for identifying the element. (Usedwhen the utility software supports another language.)

3.

CATEGORY

Describes the category for grouping the element.

4.

NAME

5.

DATATYPE

6.

DATA

Describes the name of the element. Used whendisplaying the name and contents of the element inutility software.
Describes the data type of the contents described in
the DATA item.
Describes the contents of the element.

Description
RequiredSpecifications /Optional
See Section
Required
4.3.1.19
See Section
Optional
4.3.1.20
See Section
Optional
4.3.1.4
See Section
4.3.1.24
See Section
4.3.1.10
See Section
4.3.1.9

Optional
Required
Required(1) DeviceTypeID element
If the device type does not fall under any of the categories, submit an application to the CC-Link
Partner Associate to add a code.
Please contact the CC-Link Association.
(2) Device version (Version element)
The device version indicates the version of the function of the module. This information is used toassociate the module and CSP+ file.
[Background]
When a module software version upgrade or the like is performed, specification changes, such asparameter or command additions, may occur. When module specifications are changed, the CSP+ filealso needs to be updated in accordance with that change.
[Purpose of device version]
The information that identifies the state before and after a specification change is the device version.
This information is used to indicate the correspondence between each CSP+ file and module
specifications.
(a) Purpose of use by utility software
By managing and using with distinction all CSP+ files of different device versions, the utility software iscapable of providing optimum functionality and UI in accordance with the version of the module used.
(b) Purpose of use by user
The user can select the CSP+ file for the device actually used by cross-checking the device version
stated in the CSP+ file and the version of the module used.
[Data type]The data type of the Version element is selectable per module from the following: bit string, signed
integer, unsigned integer, or string. Be sure to use the same data type for the CSP+ files of different
version corresponding to modules of the same model name.
(3)[Description format]
The description format of the device version can be freely determined for each module. Since thisvalue is used as an identifier in utility software and for automatic identification of the mass production
version, the values of the items related to the device version need to be managed and written inaccordance with the policies below.
(a) Updating the value in association with the module version
The device version indicates the version of the module with which the CSP+ file is used in
combination. For this reason, the device version described in the CSP+ file and the module version
CLPA

BAP-C2008ENG-001-K
1-116

need to be managed in association with each other. Note, however, that the CSP+ file can be
managed without upgrading the device version even if the module is one in which the device version is
upgraded. [See (h).]*The version of the module software/firmware may be written as the device version. However,when a defect is repaired, etc., these versions are upgraded even if the module function
does not change (even if there is no need to update the CSP+ file).
In the case of the example in Figure 5-8, when the device version is managed using thesoftware version, the device version described in the CSP+ file needs to be upgraded whena defect is corrected, even if there is no functional change. Thus, if possible, we recommendthat you do not use the software version for the device version, but rather a string thatindicates the version of the function of the module.
バージョン以外、
Profiledata otherthanversion is the
プロファイルデータはsame
同じ

When the software
version is used todescribe the device
versionProfile data
Version = A

Profile data
Version = B

Profile data
Version = C

Software version A

Software version B

Software version C

Bug correction

Parameter addition

Function version 1

When the version
indicating the function isused to described thedevice version

Profile data
Version = 1

Function version 2

Profile data
Version = 2

Figure 5-8 Device Version Management Example(b) Relationship with version value held by module
It is possible to specify a method that acquires the version of the module using the utility software sothat the version is indicated in the ReadVersionType element described in the COMM-IF_INFO part(see Section 5.3.1) described later. When the module is capable of acquiring the version value of themodule, the value that can be actually acquired from the module is written in the DATA item of the
VERSION element of the DEVICE_INFO part, and the data type of that value is written in the
DATATYPE item. With this arrangement, the version value of the module and the version value
described in the CSP+ file can be compared by the utility software. If the ReadVersionType element is
set to "NA", there is no need to match the value with the version value held by the module.
(c) When the module is never subjected to version upgrades
Even if the module is not subjected to version upgrades and the concept of version does not exist in
relation thereto, a value must be written in the Version element. (Write a value such as "1" or "A".)CLPA

BAP-C2008ENG-001-K
1-117

(d) Version value displayed to user of module(DisplayVersion element, VersionComment element)
As shown in (b), in a case where the module and utility software are connected and the version value
can be acquired, the version value is automatically assessed. However, even with such a module, if
the module is not connected, the user must select and use the CSP+ file of the appropriate device
version. In order to select the version, the version value needs to be displayed. The value of the
Version element is written as the value held by the module as is, and thus the user may not be able todetermine the version even upon viewing that value. When the version value held by the module
differs from the value that should be displayed to the user in this case, a string for display can be
written in the DisplayVersion element.
If the meaning of the version is unclear by the displayed version value alone, it is recommended thatyou describe the meaning of the version of the module using the VersionComment element.
(e) Showing/Hiding the device version value (VersionDisplaFlg element)
You can set whether or not the device version value needs to be displayed with the utility software
using the VersionDisplayFlg element. 0 indicates hide, and 1 indicates show.
With a module that is not subject to version management or a module that does not disclose thedevice version value to the user, there is no needs to display the device version value using the utility
software. Set the setting to hide.
When the values are mixed for a CSP+ of the same model names (when the show/hide specification
changes midstream), the show or hide specification of higher priority is prioritized. The priority order is
1 > 0. While it is not prohibited to change the value when CSP+ is updated when the device version
increases, etc., it is recommended since the value of lower priority is ignored as described above.
(f)

Device version comparison policy for module and CSP+ file (VersionPolicyType element)
The VersionPolicyType element is used to indicate the policy of device versions with respect to themodule and CSP+ file when the module is to be accessed using a CSP+ file. In a case where theutility software can automatically assess the device version of the module and the version written in
the CSP+ file, errors and alarms are assessed in accordance with the value of the VersionPolicyTypeelement. Even if the module is one that is not capable of automatic assessment, the user of themodule needs to assess the device version that should be used based on this value. It is therefore
recommended that the utility software indicates the meaning of this value (the value, in particular,needs to be a value other than 0).

Table 5-25 Meaning of Each Value of VersionPolicy and Example of Modules that Use the Value
Value
0

1

2

*

CLPA

Meaning
The device version always
uses the latest CSP+ file,regardless of the module
device version
The CSP+ file having theexact same device
version as the module is
used
The CSP+ file having thelatest device version,
which is earlier than themodule version, is used

Example of Module
When basically no problems will occur even if the device
versions differ between the module and CSP+ file When there is no need for the user to be aware of the device
version (no need for awareness) When problems may potentially occur if the device versions differ
between the module and CSP+ file When the CSP+ files corresponding to all device versions arealways disclosed When all old device version functions are to be kept with the newdevice version (when treating the module as an old module isunproblematic) When device versions are upgraded frequently due to bug repair,etc., and it is difficult to always disclose the CSP+ files that
correspond to all device versions
When VersionDisplayFlg is 0 (hide), the VersionPolicyTypemust be 0 as well.
*When the above-described values are mixed in the CSP+ files of the same model (when a policychanges midterm), the policy having the higher priority level is given higher priority. The priority
level sequence is 1 > 2 > 0.

*

While it is not prohibited to change the value when profile data is updated, it is not recommended
since the value of lower priority is ignored as described above.

BAP-C2008ENG-001-K
1-118

(g) Device version value comparison specifications
The newer/older device version comparison conducted according to VersionPolicy of (f) is
implemented by the method described below.
When the data type of Version is integer or bit string
Performed by numerical value comparison. (Example: 1 < 9 < 10)
When the data type of Version is string
Performed by lexicographic comparison. (Example: 1 < 10 < 9)(h) Management of CSP+ file in which the device version is not upgraded
Even with a module in which the software version is upgraded, it is possible to manage the CSP+ file
without upgrading the device version. In such a case, CSP+ file version management is performed
only with the file version [see Section 5.1.1.3(7)].
The advantages and disadvantages to not upgrading the device version are described below. For
modules that will be highly problematic as a result of the disadvantages, we recommend that you do
upgrade and manage the device version.
[Advantages to not upgrading the device version] The CSP+ file creator and manager do not need to manage the profiles of multiple device
versions (just simply manage one file).
 The user does not need to be shown the device version (the user does not need to be madeaware of version differences).
[Disadvantages to not upgrading the device version] The risk exists that inapplicable functions and parameters will be displayed by the utility
software.
Utility software uses the CSP+ file of the latest file version, regardless of the version of themodule. As a result, even if an older module is used, the newer CSP+ file will be used,causing inapplicable functions and parameters to be displayed on the older module.
If the user uses such functions and parameters without realizing it, problems will arise, suchas error occurrence on the module or the execution of an operation not intended by the user.
For modules that do not guarantee old/new compatibility, we recommended that do upgrade
the device version.

CLPA

BAP-C2008ENG-001-K
1-119

5.2.1.2 XML format of DEVICE_INFO partIn XML format, the DEVICE_INFO part is described as an XML element having the XML element
name "deviceInfo". Table 5-26 shows a list of the attributes of the deviceInfo element, and Table 5-27
shows a list of the XML child elements.
No.
1.

No.
1.
2.

Attribute Namelabel

Table 5-26 Attribute List for deviceInfo Element
Description Details
Describes the label for identifying the DEVICE_INFO
part.
(See Section 4.3.1.19.) (Example: "DeviceInformation")

Table 5-27 XML Child Element List for deviceInfo Element
XML Element Name
Description Details
Describes the comment related to the DEVICE_INFO
comment
part (See Section 4.3.1.6.)
Describes the contents of the elements of thedeviceInfoMember
DEVICE_INFO part

Required/Optional
Required

Required/Optional
Optional
RequiredIn XML format, the element of the DEVICE_INFO part is described as an XML element having the
XML element name "deviceInfoMember".
Table 5-28 shows a list of attributes of the deviceInfoMember element, and Table 5-29 shows a list of
XML child elements.
Table 5-28 Attribute List for deviceInfoMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.(See
Section 4.3.1.19.) The contents written for this label are
regulated by CSP+ specifications. For details, see
Section 5.2.1.3.

Required/Optional
Required

Table 5-29 XML Child Element List of deviceInfoMember Element
No.
1.
2.
3.
4.
5.

XML Element Namelabel2
category
namedatatype
data

Description Details
Describes the LABEL2 item
Describes the CATEGORY item
Describes the NAME item
Describes the DATATYPE item
Describes the DATA item

Write the DEVICE_INFO part using a format such as shown below.
<p:deviceInfo label=”Write in accordance with the description details of Table 5-26
‘Attribute Name label’”><p:comment>”Write in accordance with the description details of Table 5-27 ‘XML
Element Name comment’”</p:comment><p:deviceInfoMember label=”Write in accordance with the description details of Table
5-28 ‘Attribute Name label’”><p:label2>”Write in accordance with the description details of Table 5-29 ‘XML
Element Name label2’”</p:label2><p:category>”Write in accordance with the description details of Table 5-29 ‘XML
Element Name category’”</p:category><p:name>”Write in accordance with the description details of Table 5-29 ‘XML Element
Name name”</p:name><p:datatype>”Write in accordance with the description details of Table 5-29 ‘XML
Element Name datatype”</p:datatype><p:data>”Write in accordance with the description details of Table 5-29 ‘XML Element
Name data’”</p:data></p:deviceInfoMember><p:deviceInfoMember label=”Write in accordance with the description details of Table
5-28 ‘Attribute Name label’”>::</p:deviceInfoMember>:

CLPA

BAP-C2008ENG-001-K
1-120

:
</p:deviceInfo>

CLPA

BAP-C2008ENG-001-K
1-121

5.2.1.3 Description details of DEVICE_INFO part(1) Item description of VendorName element
Table 5-30 Item Description Specifications of VendorName Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "VendorName"
Write "VendorName" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Vendor Name" in the case of English CSP+ files[Recommended specifications]Write "STRING(64)"
Write the name of the vendor that manufactured the module(a) Item description example of VendorName element<p:deviceInfoMember label="VendorName"><p:label2><p:item>VendorName</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Vendor Name</p:item></p:name><p:datatype><p:item>STRING(64)</p:item></p:datatype><p:data><p:item>CLPA</p:item></p:data></p:deviceInfoMember>(2) Item description of VendorCode element
Table 5-31 Item Description Specifications of VendorCode Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "VendorCode"Write "VendorCode" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Vendor Code" in the case of English CSP+ files[Recommended specifications]Write "WORD"
Write the vendor code
The fifth to eighth digits of the partner member number of the CC-Link
Partner Association is the vendor code.
In the case of the CC-Link IE TSN support unit which has controller
information, write the vendor code of the controller information. In the caseof the device which does not have controller information, write the vendor
code of the network information.

(a) Item description example of VendorCode element<p:deviceInfoMember label="VendorCode"><p:label2><p:item>VendorCode</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Vendor Code</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:data><p:item>0x0000</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-122

(3) Item description of DeviceModel element
DeviceModel is information for specifying a module. If you change the value of this element at the timeof CSP+ updating, the CSP+ is treated as a CSP+ of a different module.
Table 5-32 Item Description Specifications of DeviceModel Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "DeviceModel"
Write "DeviceModel" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Device Model" in the case of English CSP+ files[Recommended specifications]Write "STRING(48)"
Write the model of the module managed by each vendor.
The model is used in the file name (see Section 4.1.1) of the CSP+ file, andthus the characters that are prohibited in the file name [¥/:?"<>|] cannot be
used. If model assessment processing is performed by the utility software,
there is no upper/lower case sensitivity.

(a) Item description example of the DeviceModel element<p:deviceInfoMember label="DeviceModel"><p:label2><p:item>DeviceModel</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Device Model</p:item></p:name><p:datatype><p:item>STRING(48)</p:item></p:datatype><p:data><p:item>CC-A1000</p:item></p:data></p:deviceInfoMember>(4) Item description of ProductID element
When you write the Product ID, write a unique ID having a one-to-one correspondence with themodule model name for each vendor. Write the same ProductID for all CSP+ files of different versionsof the same model names; do not change the ID.

CLPA

BAP-C2008ENG-001-K
1-123

Table 5-33 Item Description Specifications of ProductID Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ProductID"
Write "ProductID" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write the "Product ID" in the case of English CSP+ files[Recommended specifications]Write "STRING(256)"
Write the product ID of the module managed by the vendor.
In the case of the CC-Link IE Field Network Safety Communication Function
Support Unit, enter the value of unit_type_code. For unit_type_code, see"CC-Link IE Safety Communication Function Specification (Application Layer
Service and Protocol) (Communication Profile) BAP-C2007ENG-002, BAPC2007ENG-003".
When it is possible to acquire the type name code of the controller in the CCLink IE Field Network Support Unit, be certain to write the same value as thatvalue.
For the type name code of the controller, see "CC-Link IE Field Network
Specification (Application Layer Protocol) BAP-C2005-004".
In the case of the Ethernet connection unit, write the type name code with astring of hexadecimal representation granted "0x" at the head. For the typename code, see "SLMP (Seamless Message Protocol) Specification(Protocol) BAP-C2006ENG-003" and "CC-Link IE Field Network BasicSpecification (Application Layer Protocol) BAP-C2010ENG-004".
In the case of the CC-Link IE TSN support unit which has controller
information, write the type name code of the controller information in decimal.
In the case of the device which does not have controller information, write thetype name code of the network information in decimal. This item is required in
CC-Link IE TSN.

(a) Item description example of ProductID element<p:deviceInfoMember label="ProductID"><p:label2><p:item>ProductID</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Product ID</p:item></p:name><p:datatype><p:item>STRING(256)</p:item></p:datatype><p:data><p:item>0x00000001</p:item></p:data></p:deviceInfoMember>(5) Item description of DeviceTypeID element
Table 5-34 Item Description Specifications of DeviceTypeID Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "DeviceTypeID".
Write the "DeviceTypeID" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write the "Device Type ID" in the case of English CSP+ files[Recommended specifications]Write "WORD"
Write the ID that indicates the type of the module. For IDs, see Section
5.2.1.1(1).

(a) Item description example of the DeviceTypeID element<p:deviceInfoMember label=DeviceTypeID><p:label2><p:item>DeviceTypeID</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Device Type ID</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:data><p:item>0x04</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-124

(6) Item description of DeviceTypeDetail element
Table 5-35 Item Description Specifications of DeviceTypeDetail Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "DeviceTypeDetail"Write "DeviceTypeDetail" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Device Type Detail" in the case of English CSP+ files[Recommended specifications]Write "STRING_U(256)"
Write the details of the device type. Write this value when you want to indicate
a specific module type that cannot be expressed using DeviceTypeID. We
recommend that you write a string that indicates the module type using thiselement alone.

(a) Item description example of DeviceTypeDetail element<p:deviceInfoMember label="DeviceTypeDetail"><p:label2><p:item>DeviceTypeDetail</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Device Type Detail</p:item></p:name><p:datatype><p:item>STRING(256)</p:item></p:datatype><p:data><p:item>Inverter A1234</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-125

(7) Item description of Version element
Table 5-36 Item Description Specifications of Version Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "Version"
Write "Version" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Device Version" in the case of English CSP+ files.
[Recommended specifications]Write the value selecting from the following:
bit string type, signed integer type, unsigned integer type, and string type[using only the expression "STRING(x)"]. In the following example,"STRING(16)" is written.
In the case of Ethernet connection unit:
Write "WORD".
In the case of the CC-Link IE TSN connection unit:
Write "UINT16".
Write the function version of the module
The module function version is used to associate each version and profile ofthe module when profile description changes are required, such as parameterand command changes.
The description format may be freely determined for each module. However,since the device version is quoted in the CSP+ file name (see Section 4.1.1),
do not use characters that are prohibited in the file name [¥/:?"<>|]. For
details, see Section 5.2.1.1(2).
In the case of the CC-Link IE Field Network Safety Communication Function
Support Unit, write the value of the unit_version. For unit_version, see "CCLink IE Safety Communication Function Specification (Application Layer
Service and Protocol) (Communication profile) BAP-C2007ENG-002, BAPC2007ENG-003".
In the case of the Ethernet connection unit, write a value equivalent to theserverMachineVersion item stored in the answer data ResNodeSearch of"SLMP (Seamless Message Protocol) Specification (Protocol) BAPC2006ENG-003".
In the case of the CC-Link IE TSN support unit which has controller
information, write the device version of the controller information. In the caseof the device which does not have controller information, write the device
version of the network information. For the device version of the controller
information, see "CC-Link IE TSN Specifications (Overview) BAP-C2011ENG001".

(a) Item description example of Version element<p:deviceInfoMember label="Version"><p:label2><p:item>Version</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Device Version</p:item></p:name><p:datatype><p:item>STRING(16)</p:item></p:datatype><p:data><p:item>1.00A</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-126

(8) Item description of VersionDisplayFlg element
Table 5-37 Item Description Specifications of VersionDisplayFlg Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "VersionDisplayFlg ".
Write "VersionDisplayFlg " in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Device Version Display Flag" in the case of English CSP+ files.
[Recommended specifications]Write "BOOL".
Write whether or not the device version is to be shown to or hidden from theuser. Write the value based on the following [0: Hide, 1: Show]. For details,
see Section 5.2.1.1(2) [Description Format] (e).

(a) Item description example of VersionDisplayFlg element<p:deviceInfoMember label="VersionDisplayFlg"><p:label2><p:item>VersionDisplayFlg</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Device Version Display Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:deviceInfoMember>(9) Item description of VersionPolicyType element
Table 5-38 Item Description Specifications of VersionPolicyType Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "VersionPolicyType"
Write "VersionPolicyType" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Device Version Display Policy" in the case of English CSP+ files[Recommended specifications]Write "UINT16"
Write the policy regarding the relationship between the device version of themodule and the device version written in the CSP+ file when the mass
production device is to be accessed using the CSP+ file. [See Section
5.2.1.1(2).](a) Item description example of VersionPolicyType element<p:deviceInfoMember label="VersionPolicyType"><p:label2><p:item>VersionPolicyType</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Device Version Display Policy</p:item></p:name><p:datatype><p:item> UINT16</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-127

(10) Item description of DisplayVersionValue element
Table 5-39 Item Description Specifications of DisplayVersionValue Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "DisplayVersionValue"
Write "DisplayVersionValue" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Device Version (Display Value)" in the case of English CSP+ files[Recommended specifications]Write "STRING(32)"
Write the value of the version to be displayed when the value of the device
version acquired from the module differs from the value of the version to be
displayed to the user with the utility software. [See Section 5.2.1.1(2).] Thismay be omitted if the value is the same as the value of the Version element.

(a) Item description example of DisplayVersionValue element<p:deviceInfoMember label="DisplayVersionValue"><p:label2><p:item>DisplayVersionValue</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Device Version (Display Value)</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>1.00A</p:item></p:data></p:deviceInfoMember>(11) Item description of VersionComment element
Table 5-40 Item Description Specifications of VersionComment Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "VersionComment"
Write "VersionComment" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Version Comment" in the case of English CSP+ files[Recommended specifications]Write "STRING_U(256)"
Write the device version comment. [See Section 5.2.1.1(2).](a) Item description example of VersionComment element<p:deviceInfoMember label="VersionComment"><p:label2><p:item>VersionComment</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Version Comment</p:item></p:name><p:datatype><p:item>STRING_U(256)</p:item></p:datatype><p:data><p:item>Customized for Company A</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-128

(12) Item description of DeviceConfigurationID element
Table 5-41 Item Description Specifications of DeviceConfigurationID Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "DeviceConfigurationID"
Write "DeviceConfigurationID" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Device Configuration ID" in the case of English CSP+ files[Recommended specifications]Write "STRING(32)"
Write the identifier for the individual module configuration of the module
having a device configuration that can be changed by the user. The
prohibited characters are the same as those of the conventions for the
LABEL item. (See Section 4.3.1.19.)
A different CSP+ is identified based on the existence or nonexistence of adevice configuration ID and the difference in the written string. Users who
determine the device configuration ID need to manage the CSP+ files sothat the ID is unique within the environment used by the CSP+ file.
There is no need to standardize the management of file versions between
profiles having different device configuration IDs.
It is possible to create and operate multiple different profiles for one module
by using the device configuration ID. This is possible by with modules suchas described in Section (2).

(a) Item description example of DeviceConfigurationID element<p:deviceInfoMember label="DeviceConfigurationID"><p:label2><p:item>DeviceConfigurationID</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Device Configuration ID</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>A_Customize</p:item></p:data></p:deviceInfoMember>(13) Item description DeviceConfigurationComment element
Table 5-42 Item Description Specifications of DeviceConfigurationComment Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "DeviceConfigurationComment"
Write "DeviceConfigurationComment" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Device Configuration Comment" in the case of English CSP+ files[Recommended specifications]Write "STRING_U(64)"
Write a string for display for user identification of the profile to be identified
by the device configuration ID.

(a) Item description example of DeviceConfigurationComment element<p:deviceInfoMember label="DeviceConfigurationComment"><p:label2><p:item>DeviceConfigurationComment</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Device Configuration Comment</p:item></p:name><p:datatype><p:item>STRING_U(64)</p:item></p:datatype><p:data><p:item>Customized for Company A</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-129

(14) Item description of ReferenceURL element
Table 5-43 Item Description Specifications of ReferenceURL Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ReferenceURL".
Write "ReferenceURL" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON".
Write "Reference URL" in the case of English CSP+ files.
[Recommended specifications]
There are no restrictions on the number of characters of the data type
Write a value that is larger than the number of characters described for"data". In the following example, "STRING_U(1024)" is written.
Write the URL when the module information is disclosed on the Web
If the module information is not directly disclosed, write the Web page of thevendor.

(a) Item description example of ReferenceURL element<p:deviceInfoMember label="ReferenceURL"><p:label2><p:item>ReferenceURL</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Reference URL</p:item></p:name><p:datatype><p:item>STRING_U(1024)</p:item></p:datatype><p:data><p:item>http://wwwf2.mitsubishielectric.co.jp/melfansweb/index_j.htm</p:item></p:data></p:deviceInfoMember>(15) Item description of URLInfo element
Table 5-44 Item Description Specifications of URLInfo Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "URLInfo"
Write "URLInfo" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "URL Info" in the case of English CSP+ files[Recommended specifications]Write "STRING_U(256)"
Write a description of the information indicating ReferenceURL.

(a) Item description example of URLInfo element<p:deviceInfoMember label="URLInfo"><p:label2><p:item>URLInfo</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>URL Info</p:item></p:name><p:datatype><p:item>STRING_U(256)</p:item></p:datatype><p:data><p:item>Check Detail on MELFANS web</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-130

(16) Item description of Outline element
Table 5-45 Item Description Specifications of Outline Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "Outline"
Write "Outline" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Outline" in the case of English CSP+ files[Recommended specifications]Write "STRING_U(256)"
Write the general specifications of the module.

(a) Item description example of Outline element<p:deviceInfoMember label="Outline"><p:label2><p:item>Outline</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Outline</p:item></p:name><p:datatype><p:item>STRING_U(256)</p:item></p:datatype><p:data><p:item>A/D Converter 4CH 12-bit</p:item></p:data></p:deviceInfoMember>(17) Item description of Feature element
Table 5-46 Item Description Specifications of Feature Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "Feature"
Write "Feature" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Feature" in the case of English CSP+ files[Recommended specifications]Write "STRING_U(256)"
Write the module features(a) Item description example of Feature element<p:deviceInfoMember label="Feature"><p:label2><p:item>Feature</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Feature</p:item></p:name><p:datatype><p:item>STRING_U(256)</p:item></p:datatype><p:data><p:item>2 Channel</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-131

(18) Item description of SpecList element
Table 5-47 Item Description Specifications of SpecList Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "SpecList"
Write "SpecList" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Spec List" in the case of English CSP+ files[Recommended specifications]Write "STRING_U(256)()"
Write the module specification information as a set(a) Item description example of SpecList element<p:deviceInfoMember label="SpecList"><p:label2><p:item>SpecList</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Spec List</p:item></p:name><p:datatype><p:item>STRING_U(256)()</p:item></p:datatype><p:data><p:item>Total Accuracy 1%</p:item><p:item>Maximum conversion Speed: 1 ms/channel</p:item></p:data></p:deviceInfoMember>(19) Item description of PowerSupplyVoltage element
Table 5-48 Item Description Specifications of PowerSupplyVoltage Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "PowerSupplyVoltage"
Write "PowerSupplyVoltage" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Power Supply Voltage(V)" in the case of English CSP+ files[Recommended specifications]Write "REAL"
Write the power supply voltage (V)(a) Item description example of PowerSupplyVoltage element<p:deviceInfoMember label="PowerSupplyVoltage"><p:label2><p:item>PowerSupplyVoltage</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Power Supply Voltage(V)</p:item></p:name><p:datatype><p:item>REAL</p:item></p:datatype><p:data><p:item>24</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-132

(20) Item description of ConsumptionCurrent element
Table 5-49 Item Description Specifications of ConsumptionCurrent Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "ConsumptionCurrent"
Write "ConsumptionCurrent" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Consumption Current (mA)" in the case of English CSP+ files[Recommended specifications]Write "REAL"
Write the consumption current (mA)(a) Item description example of ConsumptionCurrent element<p:deviceInfoMember label="ConsumptionCurrent"><p:label2><p:item>ConsumptionCurrent</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Consumption Current(mA)</p:item></p:name><p:datatype><p:item>REAL</p:item></p:datatype><p:data><p:item>120</p:item></p:data></p:deviceInfoMember>(21) Item description IconFileName element
Table 5-50 Item Description Specifications of IconFileName Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "IconFileName"
Write "IconFileName" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Icon File Name" in the case of English CSP+ files[Recommended specifications]Write "STRING(52)"
Write the icon file name to be used when a module icon is to be displayed using theutility software.
For a file name, only one-byte alphanumerical characters and symbols are usable.
Include a 16x16 pixel icon in the ico file.

(a) Item description example of IconFileName element<p:deviceInfoMember label="IconFileName"><p:label2><p:item>IconFileName</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Icon File Name</p:item></p:name><p:datatype><p:item>STRING(52)</p:item></p:datatype><p:data><p:item>AJ65BT-64AD.ico</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-133

(22) Item description of GraphicsFileName element
Table 5-51 Item Description Specifications of GraphicsFileName Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "GraphicsFileName"
Write "GraphicsFileName" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Graphics File Name" in the case of English CSP+ files[Recommended specifications]Write "STRING(52)"
Write the graphics file name to be used when a module is to be displayedusing the utility software.
For a file name, only one-byte alphanumerical characters and symbols areusable. The applicable file types are as follows:
PNG file:.png
BMP file:.bmp
JPEG file:.jpg
GIF file:.gif
Create a bitmap size within the range of 32x32 to 256x256 pixels.

(a) Item description example of GraphicsFileName element<p:deviceInfoMember label="GraphicsFileName"><p:label2><p:item>GraphicsFileName</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Graphics File Name</p:item></p:name><p:datatype><p:item>STRING(52)</p:item></p:datatype><p:data><p:item>AJ65BT-64AD.bmp</p:item></p:data></p:deviceInfoMember>(23) Item description of Height element
Table 5-52 Item Description Specifications of Height Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "Height"
Write "Height" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Height" in the case of English CSP+ files[Recommended specifications]Write "STRING_U(256)"
Write the height of the external dimensions. Write the value along with theunit of measurement.

(a) Item description example of Height element<p:deviceInfoMember label="Height"><p:label2><p:item>Height</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Height</p:item></p:name><p:datatype><p:item>STRING_U(256)</p:item></p:datatype><p:data><p:item>65mm</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-134

(24) Item description of Width element
Table 5-53 Item Description Specifications of Width Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "Width"
Write "Width" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Width" in the case of English CSP+ files[Recommended specifications]Write "STRING_U(256)"
Write the width of the external dimensions. Write the value along with theunit of measurement.

(a) Item description example of Width element<p:deviceInfoMember label="Width"><p:label2><p:item>Width</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Width</p:item></p:name><p:datatype><p:item>STRING_U(256)</p:item></p:datatype><p:data><p:item>151.9mm</p:item></p:data></p:deviceInfoMember>(25) Item description of Depth element
Table 5-54 Item Description Specifications of Depth Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "Depth"
Write "Depth" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Depth" in the case of English CSP+ files[Recommended specifications]Write "STRING_U(256)"
Write the depth of the external dimensions. Write the value along with theunit of measurement.

(a) Item description example of Depth element<p:deviceInfoMember label="Depth"><p:label2><p:item>Depth</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Depth</p:item></p:name><p:datatype><p:item>STRING_U(256)</p:item></p:datatype><p:data><p:item>63mm</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-135

(26) Item description of Weight element
Table 5-55 Item Description Specifications of Weight Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "Weight"
Write "Weight" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Weight" in the case of English CSP+ files[Recommended specifications]Write "STRING_U(256)"
Write the weight. Write the value along with the unit of measurement.

(a) Item description example of Weight element<p:deviceInfoMember label="Weight"><p:label2><p:item>Weight</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Weight</p:item></p:name><p:datatype><p:item>STRING_U(256)</p:item></p:datatype><p:data><p:item>0.35kg</p:item></p:data></p:deviceInfoMember>(27) Item description of Price element
Table 5-56 Item Description Specifications of Price Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "Price"
Write "Price" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Price" in the case of English CSP+ files[Recommended specifications]Write "STRING_U(256)"
Write the price
Write the value along with the unit of measurement.

(a) Item description example of Price element<p:deviceInfoMember label="Price"><p:label2><p:item>Price</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Price</p:item></p:name><p:datatype><p:item>STRING_U(256)</p:item></p:datatype><p:data><p:item>90000 yen</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-136

(28) Item description of UI_ATTRIBUTE_Window** element
Table 5-57 Item Description Specifications of UI_ATTRIBUTE_Window** Element
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "UI_ATTRIBUTE_Window**". Enter the window number in the area
marked "**".
Write "UI_ATTRIBUTE_Window**" in the case of English CSP+ files.
[Recommended specifications]Write ** so that it is the same as the LABEL item.
Write "COMMON".
Write "Display Info **" in the case of English CSP+ files.
[Recommended specifications]Write ** so that it is the same as the LABEL item.
Write "STRING_U(256)".
Write the name of the window specified in UI_ATTRIBUTE.

(a) Item description example of UI_ATTRIBUTE_Window1 element<p:deviceInfoMember label="UI_ATTRIBUTE_Window1"><p:label2><p:item>UI_ATTRIBUTE_Window1</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Display Info 1</p:item></p:name><p:datatype><p:item>STRING_U(256)</p:item></p:datatype><p:data><p:item>Window1</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-137



Description of DEVICE_INFO part for tool link when the communication interface is CC-Link IE TSN(29) Item description of DedicatedToolFlg element
Table 5-58 Item Description Specifications of DedicatedToolFlg Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "DedicatedToolFlg".
Write "DedicatedToolFlg" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON".
Write "Dedicated Tool Available/Unavailable Flag" in the case of English
CSP+ files. [Recommended specifications]Write "BOOL".
Write whether or not there is a supported dedicated tool.
0: None
1: Available
If omitted, 0 is regarded to be set.

(a) Item description example of DedicatedToolFlg element<p:deviceInfoMember label="DedicatedToolFlg"><p:label2><p:item>DedicatedToolFlg</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Dedicated Tool Available/Unavailable Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:deviceInfoMember>(30) Item description of DedicatedToolName element
Table 5-59 Item Description Specifications of DedicatedToolName Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "DedicatedToolName".
Write "DedicatedToolName" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON".
Write "Dedicated Tool Name" in the case of English CSP+ files.
[Recommended specifications]Write "STRING_U(256)".
Write the tool name of the supported dedicated tool.

(a) Item description example of DedicatedToolName element<p:deviceInfoMember label="DedicatedToolName"><p:label2><p:item>DedicatedToolName</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>DedicatedToolName</p:item></p:name><p:datatype><p:item>STRING_U(256)</p:item></p:datatype><p:data><p:item>Dedicated tool</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-138

(31) Item description of InstallRegistryKeyName element
Table 5-60 Item Description Specifications of InstallRegistryKeyName Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "InstallRegistryKeyName".
Write "InstallRegistryKeyName" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON".
Write "Install Registry Key Name" in the case of English CSP+ files.
[Recommended specifications]Write "STRING(255)".
Write the existing registry key name only when the supported dedicatedtool is installed. For the key name that can be written, only one of"HKEY_LOCAL_MACHINE" can be used. Write the key name of"HKEY_LOCAL_MACHINE¥" or after.

(a) Item description example of InstallRegistryKeyName element<p:deviceInfoMember label="InstallRegistryKeyName"><p:label2><p:item>InstallRegistryKeyName</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Install Registry Key Name/p:item></p:name><p:datatype><p:item>STRING(255)</p:item></p:datatype><p:data><p:item>SOFTWARE¥AAA</p:item></p:data></p:deviceInfoMember>(32) Item description of InstallRegistryValueName element
Table 5-61 Item Description Specifications of InstallRegistryValueName Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "InstallRegistryValueName".
Write "InstallRegistryValueName" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON".
Write "Install Registry Value Name" in the case of English CSP+ files.
[Recommended specifications]Write "STRING(255)".
Write the existing registry value name only when the supported dedicatedtool is installed. This does not need to be written when installation can be
determined from only the key name written in InstallRegistryKeyName.

(a) Item description example of InstallRegistryValueName element<p:deviceInfoMember label="InstallRegistryValueName"><p:label2><p:item>InstallRegistryValueName</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Install Registry Value Name</p:item></p:name><p:datatype><p:item>STRING(255)</p:item></p:datatype><p:data><p:item>AppMain</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-139

(33) Item description of ExePathRegistryKeyName element
Table 5-62 Item Description Specifications of ExePathRegistryKeyName Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ExePathRegistryKeyName".
Write "ExePathRegistryKeyName" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON".
Write "Exe Path Registry Key Name" in the case of English CSP+ files.
[Recommended specifications]Write "STRING(255)".
Write the registry key name that has the path information of the execution
file (.exe) of the supported dedicated tool. Write the key name of"HKEY_LOCAL_MACHINE¥" or after.

(a) Item description example of ExePathRegistryKeyName element<p:deviceInfoMember label="ExePathRegistryKeyName"><p:label2><p:item>ExePathRegistryKeyName</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Exe Path Registry Key Name</p:item></p:name><p:datatype><p:item>STRING(255)</p:item></p:datatype><p:data><p:item>SOFTWARE¥AAA</p:item></p:data></p:deviceInfoMember>(34) Item description of ExePathRegistryValueName element
Table 5-63 Item Description Specifications of ExePathRegistryValueName Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ExePathRegistryValueName".
Write "ExePathRegistryValueName" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON".
Write "Exe Path Registry Value Name" in the case of English CSP+ files.
[Recommended specifications]Write "STRING(255)".
Write the value name of the registry where the path of the execution file(.exe) of the supported dedicated tool is written.

(a) Item description example of ExePathRegistryValueName element<p:deviceInfoMember label="ExePathRegistryValueName"><p:label2><p:item>ExePathRegistryValueName</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Exe Path Registry Value Name</p:item></p:name><p:datatype><p:item>STRING(255)</p:item></p:datatype><p:data><p:item>AppMain</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-140

COMM_IF Section

5.3

The COMM_IF section comprises multiple parts as shown below. One part is written as a single XML
element. A comment may also be written (option).

COMM_IF section
COMM_IF_INFO part

Describes communication interface identification
information and communication specifications.

COMM_IF_INPUT part

Describes communication interface input information.

COMM_IF_OUTPUT part

Describes communication interface output information.

COMM_IF_PARAMETER part
COMM_IF_COMMAND part
METHOD part
MESSAGE part

Describes communication interface parameter information.
Describes the command executable by the communicationinterface.
Describes information related to the commands that canbe issued from the communication interface andparameter settings.
Describes information required for communication
processing to be executed, specifying a data format.
Describes the structure of input/output constituted by
不複数の要素で構成する入出力の構造を記述する。

STRUCT part

multiple elements.
Describes the options for values to be set in the element
and return values.

ENUM part
COMMAND_ARGUMENT part

Describes the argument information of
COMM_IF_COMMAND.

Figure 5-9 Structure of COMM_IF Section
In XML format, the COMM_IF section is written as an XML element of the XML element name"commIf". Table 5-64 shows a list of the attributes of the commIf element, and Table 5-65 shows a listof XML child elements.
Table 5-64 List of Attributes of commIf Element
No.
1.

Attribute Namelabel

Description Details
Describes the label that identifies the COMM_IF
section.
(See Section 4.3.1.19.) (Example: "CommIfSection")

Required/Optional
Required

Table 5-65 List of XML Child Elements of commIf Element
No.

XML Element Name1.

comment2.

commIfInfo

CLPA

Description Details
Describes the comment related to the COMM_IF
section.
(See Section 4.3.1.6.)
Describes the contents of the COMM_IF_INFO part.

Required/Optional
Optional
Required

BAP-C2008ENG-001-K
1-141

COMM_IF_INFO part

5.3.1

5.3.1.1 Overview
A COMM_IF_INFO part describes communication interface identification information and information
related to communication specifications.
Figure 5-10 shows the elements that make up the COMM_IF_INFO part when the communicationinterface is CC-Link. Figure 5-11 shows the elements that make up the COMM_IF_INFO part when thecommunication interface is CC-Link IE Field Network. Figure 5-12 shows the elements that make up
the COMM_IF_INFO part when the communication interface is Ethernet. Figure 5-13 shows theelements that make up the COMM_IF_INFO part when the communication interface is CC-Link IE
TSN. In the case of CC-Link IE Field Network, elements written as "When a safety communication
function is available", only write in the case of the safety communication function support unit. In thecase of CC-Link IE TSN, elements written as "When a safety communication function is available",
only write in the case of the safety communication function support unit.
COMM_IF_INFO Part
VendorName Element

IOType Element

VendorCode Element

DevModel Element

CommIFTypeID Element

CcLinkVer Element

Version Element

ExtCycle Element

ReadVersionType Element

NumOccupiedStations Element

StationType Element

ErrReg Element

StationTypeDetail Element

MasterFlg Element

TotalNumOfIO Element

Figure 5-10 Structure of COMM_IF_INFO parts (in the case of CC-Link)

CLPA

BAP-C2008ENG-001-K
1-142

COMM_IF_INFO Part
VendorName Element

RYSize Element

VendorCode Element

RWwSize Element

CommIFTypeID Element

RXSize Element

Version Element

RWrSize Element

ReadVersionType Element

Ports Element

GetDeviceVersion Element

protcolVersion Element

nodeType Element

NodeNumberSettingFlg Element

IOType Element

TransientReceptionFlg Element

ModelCode Element

SLMPReceptionFlg Element

ModelName Element
When a safety communication function is held
SafetyProtocolVersion

SafetyOut_YSize

SafetyNodeType

SupportSafetyCommService

SafetyIn_XSize

Figure 5-11 Structure of COMM_IF_INFO Part (in the case of CC-Link IE Field Network)

CLPA

BAP-C2008ENG-001-K
1-143

COMM_IF_INFO Part
VendorName Element

SupportFlg_SetParam Element

VendorCode Element

SupportFlg_StartSetParam Element

CommIFTypeID Element

SupportFlg_EndSetParam Element

Version Element

SupportFlg_CancelSetParam Element

ReadVersionType Element

SupportFlg_ReadStatus Element

SupportIPAddressSize Element

SupportFlg_GetCommSetting Element

TimeOutValue Element

SupportFlg_ReadStatus2 Element

SupportFlg_SearchNode Element

DevModel Element

SupportFlg_SetIPAddress Element

NumOccupiedStations Element

SupportFlg_CompareDeviceInfo Element

CCIEFBasicProtocolVersion Element

SupportFlg_GetParam Element

EthernetCommFunction Element

Figure 5-12 Structure of COMM_IF_INFO Parts (in the case of Ethernet)

CLPA

BAP-C2008ENG-001-K
1-144

COMM_IF_INFO part

VendorName element

S_B_DefaultSize element

VendorCode element

S_W_DefaultSize element

CommIFTypeID element

R_B_DefaultSize element

Version element

R_W_DefaultSize element

StationMode element

L_B_DefaultSize element

StationModeName element

L_W_DefaultSize element

LocalFunction element

S_B_MaxSize element

AutoSettingHeaderType element

S_W_MaxSize element

AutoSettingType element

R_B_MaxSize element

ModelCode element

R_W_MaxSize element

ModelCodeEx element

L_B_MaxSize element

DevModel element

L_W_MaxSize element

ConnectionPortCableType element

S_B_MinSize element

ConnectionPortNum element

S_W_MinSize element

CanProfileNum element

R_B_MinSize element

ObjectDictionaryFileName element

R_W_MinSize element

CommunicationCycleMinTime_ns element

L_B_MinSize element

CommunicationCycleMinTime_s element

L_W_MinSize element

CyclicResMaxTime element

S_B_Address element

IEEE802_1ASFunction element

S_W_Address element

ReceiveFunction100M element

R_B_Address element

RelayFunction100M element

R_W_Address element

ReceiveFunction1G element

StsW_Address element

RelayFunction1G element

PDOConfigIndex+X element

MultiCastFunction element

PDOConfigPDOType+X element

CertificationClass element

PDOConfigMemoryAddress+X element

CertificationClassChoice element

PDOConfigPossibleMapping+X element

SupportFlg_IPAddressSet element

S_General_Address element

SupportFlg_NodeIndication element

R_General_Address element

When the safety communication function of CC-Link IE TSN is available (For details, see Figure 5-14.)

Figure 5-13 Structure of COMM_IF_INFO Part (CC-Link IE TSN)
CLPA

BAP-C2008ENG-001-K
1-145

When a safety communication function is available
SafetyProtocolVersion

S_Safe_MinSize

SafetyNodeType

S_Safe_Address

SupportSafetyCommService

R_Safe_DefaultSize

SupportSafetyInvokeFunc

R_Safe_MaxSize

S_Safe_DefaultSize

R_Safe_MinSize

S_Safe_MaxSize

R_Safe_Address

Figure 5-14 Detailed Structure of When a Safety Communication Function of CC-Link IE TSN is
Available
The configuration of each element of the COMM_IF_INFO part, that is, the items that should be
described within each element, is the same. Figure 5-15 shows the configuration of an element of the
COMM_IF_INFO part.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
DATATYPE item
DATA item

Figure 5-15 Structure Definition for Element of COMM_IF_INFO Part

CLPA

BAP-C2008ENG-001-K
1-146

Table 5-66 lists the items to be described in the elements of the COMM_IF_INFO part when thecommunication interface is CC-Link. A single element is described as a single XML element. For
details of the description specifications of each element, see Section 5.3.1.3.
Table 5-66 Elements of COMM_IF_INFO Part with CC-Link

Network Dependent Area

Common Area

No.

CLPA

Element Name

1.

VendorName

2.

VendorCode

3.

CommIFTypeID

4.

Version5.

ReadVersionType

6.

StationType

7.

StationTypeDetail

8.
9.
10
11.

TotalNumOfIO
IOTypeDevModelCcLinkVer

12.

ExtCycle

13.
14.

NumOccupiedStations
ErrReg15.

MasterFlg

Description Details
Describes the name of the vendor that
manufactured the module.
Describes the vendor code of the vendor that
manufactured the module.
Describes the ID that indicates thecommunication interface type using a string.
Describes the firmware version using a string.
Describes the device version acquisition methodof the module.
Describes the station type.
Not written when the station type is 0: Remote
I/O station or 1: Remote device station.
Describes the station type details when thestation type is 2: Intelligent device station or
local station.
Describes the total number of I/O points.
Describes the I/O type.
Describes the model.
Describes the CC-Link version.
Not written when the CC-Link version is earlier
than 2.00. Describes the extended cyclic
settings when the CC-Link version is 2.00 orlater.
Describes the number of occupied stations.
Describes the error code storage register.
Describes whether the module can become thestandby master or not.

Required/Optional
Required
Required
Required
Required
Required
Required
See left.
Optional
Required
Required
Required
See left.
Required
Optional
Optional

BAP-C2008ENG-001-K
1-147

Table 5-67 shows the items described in the elements of the COMM_IF_INFO part when thecommunication interface is the CC-Link IE Field Network. A single element is described as a single
XML element. For details of the description specifications of each element, see Section 5.3.1.3.
Table 5-67 Elements of COMM_IF_INFO Part with CC-Link IE Field Network
Element Name

Description Details
Required/Optional
Describes the name of the vendor that
1. VendorName
Requiredmanufactured the module
Describes the vendor code of the vendor that
2. VendorCode
Requiredmanufactured the module
Describes the ID that indicates the
3. CommIFTypeID
Requiredcommunication interface type using a string
4. Version
Describes the firmware version using a string
Required
Describes the device version acquisition
5. ReadVersionType
Required
method of the module
6. VendorName2
Describes the vendor name
Optional
7. nodeType
Describes the node type
Required
8. IOType
Describes the I/O type
Required
9. ModelCode
Describes the model code
Required
10 DevModel
Describes the model
Required
Describes the model acquirable from the
11. ModelName
Optional
module12. RYSize
Describes the RY size
Required
13. RWwSize
Describes the RWw size
Required
14. RXSize
Describes the RX size
Required
15. RWrSize
Describes the RWr size
Required
16. Ports
Describes the number of ports
Required
17. protcolVersion
Describes the protocol version
Required
Describes whether or not there is a node
18. NodeNumberSetting
Requirednumber setting function
Describes whether or not there is a transient
19. TransientReception
Required
reception function
Describes whether or not there is an SLMP
20. SLMPReception
Required
reception function
Write the CC-Link IE Safety Communication
21. SafetyProtocolVersion*1
Function protocol version.
22. SafetyNodeType
Write the safety station type.
*1
23. SafetyIn_XSize
Write the size of safety input data.
*1
24. SafetyOut_YSize
Write the size of safety output data.
*1
SupportSafetyComm Write supported safety communication service.
25.
*2Service(optional)*1: Required during safety communication function support. Prohibited when not supported.
*2: Optional during safety communication function support. Prohibited when not supported.

Function
Dependent Division(SafetyCommunication
Function)

Network Dependent Area

Common Area

No.

CLPA

BAP-C2008ENG-001-K
1-148

When the communication interface is Ethernet, show the items written with the elements of
COMM_IF_INFO parts in Table 5-61. Write each element as one XML element. For details of
description specifications of elements, see Section 5.3.1.3.
Table 5-68 Elements of COMM_IF_INFO parts in Ethernet

Network Dependent Area

Common Area

No.

Element Name

Description Details

1. VendorName

Required/Optional
Required
RequiredWrite the name of the vendor that produced the unit.
Write the vendor code of the vendor that produced the
2. VendorCodeunit.
Write a string that shows the communication interface
Required
3. CommIFTypeID
type.
4. Version
Write the machine version of the unit.
Required
5. ReadVersionType
Write the machine version acquisition method of the unit. Required
6. SupportIPAddressSize
Write the byte size of the IP address.
Optional
7. TimeOutValue
Write the timeout value.
Optional
Write whether the SLMP command "SearchNode" is
8. SupportFlg_SearchNode
Optional
supported or not.
Write whether the SLMP command "SetIPAddress" is
9. SupportFlg_SetIPAddress
Optional
supported or not.
Write whether the SLMP command
10. SupportFlg_CompareDeviceInfo
Optional"CompareDeviceInformation" is supported or not.
Write whether the SLMP command "GetParameter" is
11. SupportFlg_GetParam
Optional
supported or not.
Write whether the SLMP command "SetParameter" is
12. SupportFlg_SetParam
Optional
supported or not.
Write whether the SLMP command "StartSetParameter"
13. SupportFlg_StartSetParam
Optional
is supported or not.
Write whether the SLMP command "EndSetParameter" is
14. SupportFlg_EndSetParam
Optional
supported or not.
Write whether the SLMP command
15. SupportFlg_CancelSetParam
Optional"CancelSetParameter" is supported or not.
Write whether the SLMP command "ReadStatus" is
16. SupportFlg_ReadStatus
Optional
supported or not.
Write whether the SLMP command
17. SupportFlg_GetCommSetting
Optional"GetCommunicationSetting" is supported or not.
Write whether the SLMP command "ReadStatus2" is18. SupportFlg_ReadStatus2
Optional
supported or not.
19. DevModel
Write the model.
*1
20. NumOccupiedStations
Write the number of occupied stations.
*1
Write the protocol version of CC-Link IE Field Network
21. CCIEFBasicProtocolVersion
Optional
Basic.
Write whether or not there is a communication function
22. EthernetCommFunction*2
supported by a Ethernet device.
*1: Required in corresponding to CC-Link IE Field Network Basic. Prohibited when not supported.
*2: Required for the CC-Link IE Field Basic communication function

CLPA

BAP-C2008ENG-001-K
1-149

Table 5-69 shows the items described in the elements of the COMM_IF_INFO part when thecommunication interface is the CC-Link IE TSN. Write one element as one XML element. For details of
the description specifications of each element, see Section 5.3.1.3.
Table 5-69 Elements of COMM_IF_INFO Part with CC-Link IE TSN

Network Dependent Area

Common Area

No.

CLPA

Element Name

1.

VendorName

2.

VendorCode

3.

CommIFTypeID

4.
5.
6.
7.

VersionStationMode
StationModeName
LocalFunction

8.

AutoSettingHeaderType

9.
10.
11.
12.
13.
14.
15.
16.

AutoSettingType
ModelCodeModelCodeEx
DevModelConnectionPortCableType
ConnectionPortNum
CanProfileNum
ObjectDictionaryFileName

17.

CommunicationCycleMinTime_ns18.

CommunicationCycleMinTime_s

19.

CyclicResMaxTime

20.

IEEE802_1ASFunction

21.

ReceiveFunction100M

22.

RelayFunction100M

23.

ReceiveFunction1G

24.

RelayFunction1G

25.

MultiCastFunction

26.
27.

CertificationClass
CertificationClassChoice28.

SupportFlg_IPAddressSet

29.

SupportFlg_NodeIndication

30.
31.
32.
33.
34.
35.
36.

S_B_DefaultSize
S_W_DefaultSize
R_B_DefaultSize
R_W_DefaultSize
L_B_DefaultSize
L_W_DefaultSize
S_B_MaxSize

Required/Optional

Description Details
Write the name of the vendor that
manufactured the module.
Write the vendor code of the vendor that
manufactured the module.
Write the ID that indicates thecommunication interface type using a string.
Write the firmware version using a string.
Write the station mode setting value.
Write the station mode name.
Write whether or not there is a local function.
Write the automatic setting header type
number.
Write the automatic setting type.
Write the model code.
Write the extended model code.
Write the model.
Write the cable type of the connection port.
Write the number of the connection ports.
Write the supported CiA standard number.
Write the object dictionary file name.
Write the minimum communication cycle thatcan be supported by devices in the unit ofns.
Write the minimum communication cycle thatcan be supported by devices in the unit of s.
Write the maximum response time for thetime managed polling method.
Write whether the IEEE802.1AS function isavailable or not.
Write whether or not there is a 100Mbps
receive function.
Write whether or not there is a 100Mbps
relay function.
Write whether or not there is a 1Gbps fullrate receive function.
Write whether or not there is a 1Gbps fullrate relay function.
Write whether or not there is abroadcast/multicast function.
Write the CC-Link IE TSN Class.
Write the CC-Link IE TSN Class choices.
Write whether the SLMP command"IPAddressSet" is supported or not.
Write whether the SLMP command"NodeIndication" is supported or not.
Write the default-size send bit data.
Write the default-size send word data.
Write the default-size receive bit data.
Write the default-size receive word data.
Write the default-size link relay.
Write the default-size link register.
Write the maximum size send bit data.

Required
Required
Required
Required
Optional*1
Optional
Optional
Optional
Required
Optional
Required
Optional*2
Optional
*3
*4
*4
*5
Required
Required
Required
Required
Required
Required
Required*6
Optional
Optional
Required
Required
Required
Required
Optional
Optional
Required

BAP-C2008ENG-001-K
1-150

No.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.

S_W_MaxSize
R_B_MaxSize
R_W_MaxSize
L_B_MaxSize
L_W_MaxSize
S_B_MinSize
S_W_MinSize
R_B_MinSize
R_W_MinSize
L_B_MinSize
L_W_MinSize

48.

S_B_Address

49.

S_W_Address

50.

R_B_Address

51.

R_W_Address

52.

StsW_Address

53.

PDOConfigIndex+X*9

54.

PDOConfigPDOType+X*9

55.
56.

Function Dependent Area (Safety Communication Function)

PDOConfigMemoryAddress+X*
9
PDOConfigPossibleMapping+X*
9Description Details
Write the maximum size send word data.
Write the maximum size receive bit data.
Write the maximum size receive word data.
Write the maximum size link relay.
Write the maximum size link register.
Write the minimum size send bit data.
Write the minimum size send word data.
Write the minimum size receive bit data.
Write the minimum size receive word data.
Write the minimum size link relay.
Write the minimum size link register.
Write the start address used for send bit
data communication.
Write the start address used for send word
data communication.
Write the memory address used for receive
bit data communication.
Write the memory address used for receive
word data communication.
Write the memory address for status
notification device.
Write the index of the PDO configuration.
Write the PDO type of the PDO
configuration.
Write the memory address of the PDO
configuration.
Write the mapping of the PDO configuration.

Write the memory address for general send
access.
Write the memory address for general
58.
R_General_Address
receive access.
Write whether the CC-Link IE TSN safety
59.
SafetyProtocolVersion
communication function protocol version
exists or not.
Write the safety node type.
60.
SafetyNodeType
Write the service of the supported safety
61.
SupportSafetyCommService
communication layer.
Write the supported safety function.
SupportSafetyInvokeFunc
62.
Write the default-size safety send bit data.
63.
S_Safe_DefaultSize
Write the maximum size safety send bit
64.
S_Safe_MaxSize
data.
Write the minimum size safety send bit data.
65.
S_Safe_MinSize
Write the start address to be stored in the
66.
S_Safe_Address
sub payload for safety send data
communication.
Write the default-size safety receive bit data.
67.
R_Safe_DefaultSize
Write the maximum size safety receive bit
68.
R_Safe_MaxSize
data.
Write the minimum size safety receive bit
69.
R_Safe_MinSize
data.
Write the start address of the sub payload
70.
R_Safe_Addressfor safety receive data communication.
*1: Write prohibited when StationMode is not written. When StationMode is written,"StationModeName" is required.
*2: Writing is required when the ConnectionPortCableType element is written.
Writing is optional when the ConnectionPortCableType element is not written.
57.

CLPA

Element Name

S_General_Address

Required/Optional
Required
Required
Required
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
*7
*7
*7
*7
Required
*8
*9
*9
*9
*7
*7
Optional
*12
*10
*10
*12
*12
*12
*13
*12
*12
*12
*14

BAP-C2008ENG-001-K
1-151

*3: The CAN compatible device (device with CanProfileNum written) is required. Prohibited when notsupported.
*4: For the devices whose minimum communication cycle cannot be defined or the devices that do
not require checking the minimum communication cycle, this may be omitted.
"CommunicationCycleMinTime_s" may be omitted for the devices whose minimum
communication cycle is less than 1 second.
"CommunicationCycleMinTime_ns" may be omitted for the devices whose minimum
communication cycle is represented in seconds ("CommunicationCycleMinTime_ns" is 0).
*5: This element can be written only for devices (or station mode) supporting the time managed
polling method. Otherwise, description is prohibited.
*6: This element is required when multiple certification classes can be selected in the same station
mode. Otherwise, description is prohibited.
*7: The memory address information of the available communication type is required. Prohibited towrite the memory addresses of the communication types for which communication is not possible.
*8: Devices for performing PDO communication are required. Write the number of indexes required.
Prohibited when not supported.
*9: Be sure to write the corresponding elements when PDOConfigIndex is written. Prohibited when
PDOConfigIndex is not written.
*10: Write elements that are written by entering numeric values for X as follows.
• Write elements that have the same numeric value in the order shown in Table 5-69, and be sureto write them consecutively.
• The elements must be written using consecutive numbers, and omitting (skipping) a number isprohibited.
• Write the elements so that they will be in ascending order.
*11: Prohibited for a device other than a safety compatible device (device without
SafetyProtocolVersion written).
*12: Required for a safety compatible device (device with SafetyProtocolVersion written). Otherwise,
writing is prohibited.
*13: Required in the case of devices with the safety send function (device of which the maximum sizeof the safety send data is 1 or larger). Otherwise, writing is prohibited.
*14: Required in the case of devices with the safety receive function (device of which the maximum
size of the safety receive data is 1 or larger). Otherwise, writing is prohibited.
Table 5-70 shows the items described in a COMM_IF_INFO element.
Table 5-70 Item List for COMM_IF_INFO Part
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

CLPA

Description Details
Describes the label for identifying the element
Describes the label for identifying the element(Used when the utility software supports anotherlanguage.)
Describes the category for grouping the element
Describes the name of the element.
Used when the name and contents of theelement are displayed with the utility software.
Describes the data type of the contents
described in the DATA item.
Describes the contents of the element.

Description
Specifications
See Section 4.3.1.19

Required/Optional
Required

See Section 4.3.1.20

Optional

See Section 4.3.1.4

Optional

See Section 4.3.1.24

Optional

See Section 4.3.1.10

Required

See Section 4.3.1.9

Required

BAP-C2008ENG-001-K
1-152

(1) Use rules of the extended model code (ModelCodeEx)
The extended model code should be installed in the device according to the following specifications
first, then described in the CSP+ file.
[Purpose]
When developing a compatible device that takes over the existing module functions, use a extended
model name to change the model name (* with same model code) and to make its engineering tool(such as reading/writing the parameter) compatible (to use a newly developed device with the CSP+
file of the existing module).
[Extended model code specifications]
The code starts from the number "zero" and the host devices have a larger number. The upper limit is65535.
(a) Reading/writing the parameterNo restrictions. The parameter can be read and written in all combinations.

n Module A-1
Model code: A
Extended model
code: 1n Module A-2
Model code: A
Extended model
code: 2The parameters of the
combination with arrows
can be read and written.

n Profile A-1
Model code: A
Extended model
code: 1n Profile A-2
Model code: A
Extended model
code: 2(b) Automatic detection
If there is the profile with the same extended model code, it is displayed.
If not, the profile of other extended model name with the same model code is searched.
The priority order is determined based on the following.

n Module A-2
Model code: A
Extended model
code: 22)n Profile A-1
Model code: A
Extended model
code: 1

CLPA

· Profile with the value larger than the extended
model code of the device· Profile with the value smaller than the extended
model code
Among them, the profile with "smaller value" takes
priority1)n Profile A-2
Model code: A
Extended model
code: 2n Module A-3
Model code: A
Extended model
code: 33)

3)
n Profile A-3
Model code: A
Extended model
code: 3n Profile A-1
Model code: A
Extended model
code: 1

· Multiple profiles with the value smaller than the extended
model code of the device· Multiple profiles with the value larger than the extended model
code of the device
Among them, the profile with "larger value" takes priority

2)n Profile A-2
Model code: A
Extended model
code: 2

1)
n Profile A-3
Model code: A
Extended model
code: 3

BAP-C2008ENG-001-K
1-153

[Operation rule](a) The parameter can be normally read/written from the old device profile (profile with asmall extended model code).
Normal: The parameters that can be set in the old device without an error can be read/written
in the same way.
While reading, the parameter added with the new device is ignored.
While writing, the parameter added with the new device should be set completely
without an error even though it is not written.
n Module A-1
Model code: A
Extended model
code: 1n Module A-2
Model code: A
Extended model
code: 2n Module A-3
Model code: A
Extended model
code: 3The parameters of the
combination with arrows
can be read and written.

n Profile A-1
Model code: A
Extended model
code: 1n Profile A-2
Model code: A
Extended model
code: 2n Profile A-3
Model code: A
Extended model
code: 3

The following shows the example of parameter reading/writing.
n Profile A-1
Model code: A
Extended model
code: 1n Profile A-1
Model code: A
Extended model
code: 1

Parameter A
Parameter B
Parameter C[Parameter read]
The tool reads the data of parameters A to C from the module. The
module responds normally to the request from the tool, and sends
only the data of A to C.
n Module A-2
Model code: A
Extended model
code: 2

Parameter A
Parameter B
Parameter C
Parameter D→ Parameter that is not in the module A-1

Parameter A
Parameter B
Parameter C[Parameter write]
The tool writes the data of parameters A to C to the module. The module responds
normally to the request from the tool, and reflects only the data of A to C to themodule operation.
n Module A-2
Model code: A
Extended model
code: 2

Parameter A
Parameter B
Parameter C
Parameter D→ Parameter that is not in the module A-1<Reason>
It is assumed that the old device went out of production and the device should be replacedwith a new device, although functions of the new device are not necessary and just the same
operation as the old device is required. (Same applies to the diagnostics window)
When the new device uses a different profile, the profile needs to be updated, which bothers
customers. When the new device and old device have the same model profiles, the modules
cannot be distinguished on the engineering tool, especially the remote module cannot bechecked with the module, which is also inconvenient for customers.
The specification "extended model code" will solve those problems.

CLPA

BAP-C2008ENG-001-K
1-154

(b) Reading/writing the parameter from the new device profile (profile with a large
extended model) is optional.
n Profile A-2
Model code: A
Extended model
code: 2

Parameter A
Parameter B
Parameter C
Parameter D→ Parameter that is not in the module
A-1[Parameter read]
The tool reads the data of parameters A to D from the module.
Whether the module responds normally or with error is optional.
n Module A-1
Model code: A
Extended model
code: 1n Profile A-2
Model code: A
Extended model
code: 2→ Parameter that is not in themodule A-1[Parameter write]
The tool writes the data of parameters A to D to the module.
Whether the module responds normally or with error is optional.
n Module A-1
Model code: A
Extended model
code: 1

Parameter A
Parameter B
Parameter C

Parameter A
Parameter B
Parameter C
Parameter D

Parameter A
Parameter B
Parameter C

The following operations are the examples.
• The module responds to an error and notifies the user that no profile corresponds to themodule model.
• Only the parameters that normally response and can be recognized (parameters A to C in
the above example) are read and written.
"0" is returned for the data that cannot be recognized while reading.
The data that cannot be recognized while writing is discarded after being received.
However, the reserved area should be made in advance for this specifications.
(c) The contents of the network parameter should not be changed between the old andnew profiles. When they are, use a device with other model code.
Contents of the network parameter: Minimum/maximum number of send cyclic points, memory
address, station specific code
<Reason>
These rules are to prevent the network parameter from being changed unintendedly.
When the parameter of the A-2 unit is written to PLC with the A-2 profile and read from PLC
with the personal computer that has only the A-1 profile, it changes to A-1 on theconfiguration window. These rules prevent the network parameter from being changed when
it is written to PLC in the state.
(d) For the device version policy (VersionPolicyType), set "0: Always use the latest" or"2: Use the latest device version before the actual device version".
Also, when the extended model code is used, it is recommended not to update the device
version for the operation.
<Reason>The profile of the old extended model code and module of the new extended model code,and the profile of new extended model code and module of the old extended model code
are used together respectively. If the device version is different in the combination, thecombination becomes complicated.

CLPA

BAP-C2008ENG-001-K
1-155

5.3.1.2 XML format of COMM_IF_INFO partIn XML format, the COMM_IF_INFO part is described as an XML element having the XML element
name "commIfInfo". Table 5-71 shows a list of the attributes of the commIfInfo element, and Table 5-72
shows a list of the XML child elements.
Table 5-71 Attribute List for commIfInfo Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the COMM_IF_INFO
part.
(See Section 4.3.1.19.) (Example: "CommIfInformation")

Required/Optional
Required

Table 5-72 XML Child Element List for commIfInfo Element
No.

XML Element Name1.

comment2.

commIfInfoMember

Description Details
Describes the comment related to the COMM_IF_INFO
part. (See Section 4.3.1.6.)
Describes the contents of the elements of the
COMM_IF_INFO part.

Required/Optional
Optional
RequiredIn XML format, the element of the COMM_IF_INFO part is described as an XML element having the
XML element name "commIfInfoMember".
Table 5-73 shows a list of attributes of the commIfInfoMember element, and Table 5-74 shows a list of
XML child elements.
Table 5-73 Attribute List for commIfInfoMember Element
No.
1.

CLPA

Attribute Namelabel

Description Details
Describes the label for identifying the element.(See
Section 4.3.1.19.) The contents written for this label are
regulated by CSP+ specifications, and cannot be
arbitrarily written by the user. For details, see Section
5.3.1.3.

Required/Optional
Required

BAP-C2008ENG-001-K
1-156

Table 5-74 XML Child Element List of commIfInfoMember Element
No.
1.
2.
3.
4.
5.

XML Element Namelabel2
category
namedatatype
data

Description Details
Describes the LABEL2 item
Describes the CATEGORY item
Describes the NAME item
Describes the DATATYPE item
Describes the DATA item

Write the COMM_IF_INFO part using a format such as shown below.
<p:commIfInfo label="Write in accordance with the description details of Table 5-71
‘Attribute Name label’”><p:comment> Write in accordance with the description details of Table 5-72 ‘XML
Element Name comment’</p:comment><p:commIfInfoMember label="Write in accordance with the description details of Table
5-73 ‘Attribute Name label’”><p:label2> Write in accordance with the description details of Table 5-74 ‘XML
Element Name label2’</p:label2><p:category> Write in accordance with the description details of Table 5-74 ‘XML
Element Name category’ </p:category><p:name> Write in accordance with the description details of Table 5-74 ‘XML
Element Name name’ </p:name><p:datatype> Write in accordance with the description details of Table 5-74 ‘XML
Element Name datatype’</p:datatype><p:data> Write in accordance with the description details of Table 5-74 ‘XML
Element Name data’</p:data></p:commIfInfoMember><p:commIfInfoMember label=" Write in accordance with the description details of Table
5-73 ‘Attribute Name label’">::</p:commIfInfoMember>::</p:commIfInfo>

5.3.1.3 Description of COMM_IF_INFO part
 Description details of common area
Of the elements described in the COMM_IF_INFO part, item numbers 1-5 of Table 5-66 and Table 5-67
describe common elements that remain the same regardless of changes in the communication interface.
For these elements, write "COMMON" as the contents of the item name "CATEGORY".
(1) Item description of VendorName element
Table 5-75 Item Description Specifications of VendorName Element
No. Item Name
1. LABEL
2. LABEL2
3. CATEGORY
4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "VendorName"
Write "VendorName" in the case of English CSP+ files [Recommended specifications]Write "COMMON"
Write "Vendor Name" in the case of English CSP+ files [Recommended
specifications]Write "STRING_U(64)"
Write the name of the vendor that created the communication function[Note] When multiple COMM_IF sections are written in CC-Link IE TSN, the samevalue must be written in all the COMM_IF_INFO parts.

(a) Item description example of VendorName element<p:commIfInfoMember label="VendorName"><p:label2><p:item>VendorName</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Vendor Name</p:item></p:name><p:datatype><p:item>STRING_U(64)</p:item></p:datatype><p:data><p:item>CC-Link Partner Association</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-157

(2) Item description of VendorCode element
Table 5-76 Item Description Specifications of VendorCode Element
No.
1.
2.
3.
4.
5.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPE

6.

DATA

Description Details
Write "VendorCode"Write "VendorCode" in the case of English CSP+ files [Recommended specifications]Write "COMMON"
Write "Vendor Code" in the case of English CSP+ files [Recommended specifications]Write "WORD"
Write the code of the vendor that created the communication function
Write the fifth to eighth digits of the partner member number of the CC-Link Partner
Association.
[Note] When multiple COMM_IF sections are written in CC-Link IE TSN, the samevalue must be written in all the COMM_IF_INFO parts.

(a) Item description example of VendorCode element<p:commIfInfoMember label="VendorCode"><p:label2><p:item>VendorCode</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Vendor Code</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:data><p:item>0x0000</p:item></p:data></p:commIfInfoMember>(3) Item description of CommIFTypeID element
Table 5-77 Item Description Specifications of CommIFTypeID Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CommIFTypeID"
Write "CommIFTypeID" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Communication Interface Type ID" in the case of English CSP+ files[Recommended specifications]Write "STRING(32)"
Write the ID that indicates the COMM_IF type
Write "CC-Link" when the module supports CC-Link.
Write "CCLinkIEField" when the module supports the CC-Link IE Field Network.
Write "Ethernet" when the module supports the Ethernet.
Write "CCLinkIETSN" for CC-Link IE TSN connection unit.
[Note] When multiple COMM_IF sections are written in CC-Link IE TSN, the samevalue must be written in all the COMM_IF_INFO parts.

(a) Item description example of CommIFTypeID element<p:commIfInfoMember label="CommIFTypeID"><p:label2><p:item>CommIFTypeID</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Communication Interface Type ID</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>CCLink</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-158

(4) Item description of Version element
Table 5-78 Item Description Specifications of Version Element
No.
1.
2.
3.
4.

Item NameLABELLABEL2
CATEGORYNAME

5.

DATATYPE

6.

DATA

Description Details
Write "Version"
Write "Version" in the case of English CSP+ files [Recommended specifications]Write "COMMON"
Write "Version" in the case of English CSP+ files. [Recommended specifications]Write "STRING(4)" when the module supports CC-Link.
Select from "UINT8" and "STRING(4)" when the module supports the CC-Link IE
Field Network.
In the case of Ethernet connection unit, write "WORD".
Write "UINT16" when the module supports CC-Link IE TSN.
When the module supports CC-Link
Write the value in accordance with the software version of the CC-Link Partner
Association: CC-Link Specification (Overview/Protocol) BAP-C2001-001. Write A, B,
C . . ., which indicates the meaning, and not 1, 2, 3 . . of the mass production device.
Write "NONE" when the module does not have a software version.
When the module supports the CC-Link IE Field Network
Write the value equivalent to the fwVersion of the CC-Link IE Field Network
Specification (Device Profile) BAP-C2005-007. In this case, the DATATYPE item
needs to be "UINT8". Write "NONE" when the module does not have a FW version.
In the example below, "A" is written.
In the case of Ethernet connection unit,
write the machine version of the target unit (the same value of the Version Element of
DEVICE_INFO Part)
When the module supports CC-Link IE TSN
Write the value equivalent to the Device Version of Network information of the CCLink IE TSN Specifications (Overview) BAP-C2011ENG-001.
[Note] When multiple COMM_IF sections are written in CC-Link IE TSN, the samevalue must be written in all the COMM_IF_INFO parts.

(a) Item description example of Version element<p:commIfInfoMember label="Version"><p:label2><p:item>Version</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Version</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>A</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-159

(5) Item description of ReadVersionType element
Table 5-79 Item Description Specifications of ReadVersionType Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ReadVersionType"
Write "ReadVersionType" in the case of English CSP+ files[Recommended specifications]Write "COMMON"
Write "Device Version Acquisition Method" in the case of English CSP+ files[Recommended specifications]Write "STRING(128)"
Describe the means for acquiring the module version (Version element of
DEVICE_INFO part) via CC-Link.
 Write "NA" when device version comparison is not required or the device version
cannot be acquired.
 Write "SoftwareVersion" when the "software version" acquired based on CC-Link
standard specifications is the device version.
 Write "NetworkFWVersion" when the "network firmware version" acquired basedon CC-Link IE Field Network standard specifications is the device version.
 Write "ControllerFWVersion" when the "controller firmware version" acquired
based on CC-Link IE Field Network standard specifications is the device version.
 In the case of Ethernet connection unit, write "MachineVersion".
 Not used in the case of CC-Link IE TSN connection unit.
 Write a reference to the METHOD or MESSAGE part using the conventions ofSection 4.3.3(3) when there is a method or message for version acquisition.
[Example: $(MethodSec.GetVersion)]
Note that we recommend that the method/message used for reference be set as
follows:
 Set the WRITE_DATA item and REQUEST_DATA item as fixed values (do not use
a VALUE reference).
 Set only one reference to VALUE described in the READ_DATA item and
RESPONSE_DATA item, and indicate the device version value to be acquired bythat VALUE.

(a) Item description example of ReadVersionType element<p:commIfInfoMember label="ReadVersionType"><p:label2><p:item>ReadVersionType</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Device Version Acquisition Method</p:item></p:name><p:datatype><p:item>STRING(128)</p:item></p:datatype><p:data><p:item>$(MethodSec.GetVersion)</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-160

• Description of COMM_IF_INFO part when communication interface is CC-Link
Of the elements described in the COMM_IF_INFO part, item numbers 6-15 of Table 5-59 are elements
described when the communication interface is CC-Link. For these elements, write "COMMON_CC-Link"
as the contents of the item name "CATEGORY".
(6) Item description of StationType element
Table 5-80 Item Description Specifications of StationType Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "StationType"
Write "StationType" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link"
Write "Station Type" in the case of English CSP+ files[Recommended specifications]Write "UINT16"
Write the station type.
0: Remote I/O station
1: Remote device station
2: Intelligent device station or local station(a) Item description example of StationType element<p:commIfInfoMember label="StationType"><p:label2><p:item>StationType</p:item></p:label2><p:category><p:item>COMMON_CC-Link</p:item></p:category><p:name><p:item>Station Type</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>2</p:item></p:data></p:commIfInfoMember>(7) Item description of StationTypeDetail element
Table 5-81 Item Description Specifications of StationTypeDetail Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "StationTypeDetail"Write "StationTypeDetail" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link"
Write "Station Type Detail" in the case of English CSP+ files[Recommended specifications]Write "UINT16"
Write the details of the station type when the station type is [2].
When the station type is [2] and the station type details are omitted, the details are
regarded as "0: Intelligent device station."
0: Intelligent device station
1: Local station(a) Item description example of StationTypeDetail element<p:commIfInfoMember label="StationTypeDetail"><p:label2><p:item>StationTypeDetail</p:item></p:label2><p:category><p:item>COMMON_CC-Link</p:item></p:category><p:name><p:item>Station Type Detail</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-161

(8) Item description of TotalNumOfIO element
Table 5-82 Item Description Specifications of TotalNumOfIO Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "TotalNumOfIO"
Write "TotalNumOfIO" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link"
Write "Total IO Points" in the case of English CSP+ files[Recommended specifications]Write "UINT16"
Write the total number of I/O points.
0: Depends on number of occupied stations
1: 8 points
2: 32 points
3: 16 points(a) Item description example of TotalNumOfIO element<p:commIfInfoMember label="TotalNumOfIO"><p:label2><p:item>TotalNumOfIO</p:item></p:label2><p:category><p:item>COMMON_CC-Link</p:item></p:category><p:name><p:item>Total IO Points</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:commIfInfoMember>(9) Item description of IOType element
Table 5-83 Item Description Specifications of IOType Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "IOType"
Write "IOType" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link"
Write "IO Type" in the case of English CSP+ files[Recommended specifications]Write "UINT16"
Write the I/O type.
0: Front/Back mixture
1: Input
2: Output
3: Mixed(a) Item description example of IOType element<p:commIfInfoMember label="IOType"><p:label2><p:item>IOType</p:item></p:label2><p:category><p:item>COMMON_CC-Link</p:item></p:category><p:name><p:item>IO Type</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-162

(10) Item description of DevModel element
Table 5-84 Item Description Specifications of DevModel Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "DevModel"
Write "DevModel" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link"
Write "Model Name" in the case of English CSP+ files[Recommended specifications]Write "STRING(48)"
Write the model using a string. Write the model of the communication module whenthe module type is communication module.

(a) Item description example of DevModel element<p:commIfInfoMember label="DevModel"><p:label2><p:item>DevModel</p:item></p:label2><p:category><p:item>COMMON_CC-Link</p:item></p:category><p:name><p:item>Model Name</p:item></p:name><p:datatype><p:item>STRING(48)</p:item></p:datatype><p:data><p:item>AJ65BT-D75P2-S3</p:item></p:data></p:commIfInfoMember>(11) Item description of CcLinkVer element
Table 5-85 Item Description Specifications of CcLinkVer Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CcLinkVer"
Write "CcLinkVer" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link"
Write "CC-Link Version" in the case of English CSP+ files[Recommended specifications]Write "STRING(7)"Write the CC-Link version
Write any of the following values: 1.00, 1.10, 1.11, 2.00.

(a) Item description example of CcLinkVer element<p:commIfInfoMember label="CcLinkVer"><p:label2><p:item>CcLinkVer</p:item></p:label2><p:category><p:item>COMMON_CC-Link</p:item></p:category><p:name><p:item>CC-Link Version</p:item></p:name><p:datatype><p:item>STRING(7)</p:item></p:datatype><p:data><p:item>1.10</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-163

(12) Item description of ExtCycle element
Table 5-86 Item Description Specifications of ExtCycle Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ExtCycle"
Write "ExtCycle" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link"
Write "Extended Cyclic Setting" in the case of English CSP+ files[Recommended specifications]Write "UINT(16)"Write the extended cyclic setting when the CC-Link version is [2.00].
Write any of the following values: 1, 2, 4, 8.

(a) Item description example of ExtCycle element<p:commIfInfoMember label="ExtCycle"><p:label2><p:item>ExtCycle</p:item></p:label2><p:category><p:item>COMMON_CC-Link</p:item></p:category><p:name><p:item>Extended Cyclic Setting</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(13) Item description of NumOccupiedStations element
Table 5-87 Item Description Specifications of NumOccupiedStations Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "NumOccupiedStations"Write "NumOccupiedStations" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link"
Write "Number of Occupied Stations" in the case of English CSP+ files[Recommended specifications]Write "UINT16"
Write the number of occupied stations.
Write any of the following values: 1, 2, 3, 4.

(a) Item description example of NumOccupiedStations element<p:commIfInfoMember label="NumOccupiedStations"><p:label2><p:item>NumOccupiedStations</p:item></p:label2><p:category><p:item>COMMON_CC-Link</p:item></p:category><p:name><p:item>Number of Occupied Stations</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>4</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-164

(14) Item description of ErrReg element
Table 5-88 Item Description Specifications of ErrReg Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "ErrReg"
Write "ErrReg" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link"
Write "Error Code Storage Register" in the case of English CSP+ files[Recommended specifications]Write "STRING(7)"Write the error code storage register(a) Item description example of ErrReg element<p:commIfInfoMember label="ErrReg"><p:label2><p:item>ErrReg</p:item></p:label2><p:category><p:item>COMMON_CC-Link</p:item></p:category><p:name><p:item>Error Code Storage Register</p:item></p:name><p:datatype><p:item>STRING(7)</p:item></p:datatype><p:data><p:item>RWr1</p:item></p:data></p:commIfInfoMember>(15) Item description of MasterFlg element
Table 5-89 Item Description Specifications of MasterFlg Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "MasterFlg"
Write "MasterFlg" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link"
Write "Standby Master Flag" in the case of English CSP+ files[Recommended specifications]Write "UINT16"
Write whether the module can become a standby master when the station type islocal.
0: Cannot become standby master
1: Can become standby master(a) Item description example of MasterFlg element<p:commIfInfoMember label="MasterFlg"><p:label2><p:item>MasterFlg</p:item></p:label2><p:category><p:item>COMMON_CC-Link</p:item></p:category><p:name><p:item>Standby Master Flag</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-165

• Description of COMM_IF_INFO part when communication interface is CC-Link IE Field Network
Of the elements described in the COMM_IF_INFO part, item numbers 6 to 20 of Table 5-67 are elements
described when the communication interface is CC-Link IE Field Network. For these elements, write"COMMON_CC-Link_IE_Field" as the contents of the item name "CATEGORY".
(16) Item description of VendorName2 element
Table 5-90 Item Description Specifications of VendorName2 Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "VendorName2"
Write "VendorName2" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "Vendor Name 2" in the case of English CSP+ files[Recommended specifications]Write "STRING(32)"
Write the name of the vendor that created the communication function. Write thevalue corresponding to VendorName of the CC-Link IE Field Network Specification(Device Profile) BAP-C2005-007.
(1) This may be omitted when the description is the same as VendorName.

(a) Item description example of VendorName2 element<p:commIfInfoMember label="VendorName2"><p:label2><p:item>VendorName2</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>Vendor Name 2</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>MELSEC</p:item></p:data></p:commIfInfoMember>(17) Item description of nodeType element
Table 5-91 Item Description Specifications of nodeType Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "nodeType"
Write "nodeType" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "Node Type" in the case of English CSP+ files[Recommended specifications]Write "BYTE"
Write the node type. Write the value corresponding to nodeType of the CC-Link IE
Field Network Specification (Device Profile) BAP-C2005-007.
0x32: Local station
0x33: Intelligent device station
0x34: Remote device station
0x35: Remote I/O station(a) Item description example of nodeType element<p:commIfInfoMember label="nodeType"><p:label2><p:item>nodeType</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>Node Type</p:item></p:name><p:datatype><p:item>BYTE</p:item></p:datatype><p:data><p:item>0x34</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-166

(18) Item description of IOType element
Table 5-92 Item Description Specifications of IOType Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "IOType"
Write "IOType" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-link_IE_Field"
Write "IO Type" in the case of English CSP+ files[Recommended specifications]Write "UINT(16)"Write the I/O type. Write the value corresponding to ioType in the CC-Link IE Field
Network Specification (Device Profile) BAP-C2005-007.
0: Front/Back mixture
1: Input
2: Output
3: Mixed(a) Item description example of IOType element<p:commIfInfoMember label="IOType"><p:label2><p:item>IOType</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>IO Type</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:commIfInfoMember>(19) Item description of ModelCode element
Table 5-93 Item Description Specifications of ModelCode Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ModelCode"Write "ModelCode" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "Model Code" in the case of English CSP+ files[Recommended specifications]Write "UINT32"
Write the model code.
Write the value corresponding to modelCode of the CC-Link IE Field Network
Specification (Device Profile) BAP-C2005-007.
Write the model code of the communication module when the module type iscommunication module.

(a) Item description example of ModelCode element<p:commIfInfoMember label="ModelCode"><p:label2><p:item>ModelCode</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>Model Code</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>1234</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-167

(20) Item description of DevModel element
Table 5-94 Item Description Specifications of DevModel Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "DevModel"
Write "DevModel" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "Model Name" in the case of English CSP+ files[Recommended specifications]Write "STRING(48)"
Write the model name (model).
Write the model name (model) of the communication module when the module type iscommunication module.

(a) Item description example of DevModel element<p:commIfInfoMember label="DevModel"><p:label2><p:item>DevModel</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>Model Name</p:item></p:name><p:datatype><p:item>STRING(48)</p:item></p:datatype><p:data><p:item>CC-LinkIEFieldEthernetAdapter</p:item></p:data></p:commIfInfoMember>(21) Item description of ModelName element
Table 5-95 Item Description Specifications of ModelName Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ModelName"
Write "ModelName" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "Model Name" in the case of English CSP+ files[Recommended specifications]Write "STRING(20)"Write the model name acquirable from the module. Write the value corresponding tomodelName of the CC-Link IE Field Network Specification (Device Profile) BAPC2005-007. Write the model name of the communication module when the module
type is communication module. This may be omitted when the value is the same as
DevModel.

(a) Item description example of ModelName element<p:commIfInfoMember label="ModelName"><p:label2><p:item>ModelName</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>Model Name</p:item></p:name><p:datatype><p:item>STRING(20)</p:item></p:datatype><p:data><p:item>EthernetAdapter</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-168

(22) Item description of RYSize element
Table 5-96 Item Description Specifications of RYSize Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "RYSize"
Write "RYSize" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "RY Size" in the case of English CSP+ files[Recommended specifications]Write "UINT16"
Write the size of RY of the module.
Write the value corresponding to rySize of the CC-Link Field Network Specification(Device Profile) BAP-C2005-007.

(a) Item description example of RYSize element<p:commIfInfoMember label="RYSize"><p:label2><p:item>RYSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>RY Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>1024</p:item></p:data></p:commIfInfoMember>(23) Item description of RWwSize element
Table 5-97 Item Description Specifications of RWwSize Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "RWwSize"
Write "RWwSize" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "RWw Size" in the case of English CSP+ files[Recommended specifications]Write "UINT16"
Write the size of RWw of the module.
Write the value corresponding to rwwSize of the CC-Link Field Network Specification(Device Profile) BAP-C2005-007.

(a) Item description example of RWwSize element<p:commIfInfoMember label="RWwSize"><p:label2><p:item>RWwSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>RWw Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>1024</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-169

(24) Item description of RXSize element
Table 5-98 Item Description Specifications of RXSize Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "RXSize"
Write the "RXSize" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write the "RX Size" in the case of English CSP+ files[Recommended specifications]Write "UINT16"
Write the size of RX of the module. Write the value corresponding to rxSize of the
CC-Link Field Network Specification (Device Profile) BAP-C2005-007.

(a) Item description example of RXSize element<p:commIfInfoMember label="RXSize"><p:label2><p:item>RXSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>RX Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>1024</p:item></p:data></p:commIfInfoMember>(25) Item description of RWrSize element
Table 5-99 Item Description Specifications of RWrSize Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "RWrSize"
Write "RWrSize" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "RWr Size" in the case of English CSP+ files[Recommended specifications]Write "UINT16"
Write the size of RWr of the module. Write the value corresponding to rwrSize of the
CC-Link Field Network Specification (Device Profile) BAP-C2005-007.

(a) Item description example of RWrSize element<p:commIfInfoMember label="RWrSize"><p:label2><p:item>RWrSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>RWr Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>1024</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-170

(26) Item description of Ports element
Table 5-100 Item Description Specifications of Ports Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "Ports"
Write "Ports" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "Number of Ports" in the case of English CSP+ files[Recommended specifications]Write "UINT16"
Write the number of ports of the module. Write the value corresponding to Ports of
the CC-Link IE Field Network Specification (Device Profile) BAP-C2005-007.

(a) Item description example of Ports element<p:commIfInfoMember label="Ports"><p:label2><p:item>Ports</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>Number of Ports</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:commIfInfoMember>(27) Item description of protcolVersion element
Table 5-101 Item Description Specifications of protcolVersion Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "protcolVersion"
Write "protcolVersion" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "Protcol Version" in the case of English CSP+ files[Recommended specifications]Write "STRING(32)"
Write the protocol version. Write the value corresponding to protocolVersion of the
CC-Link Field Network Specification (Device Profile) BAP-C2005-007.

(a) Item description example of protcolVersion element<p:commIfInfoMember label="protcolVersion"><p:label2><p:item>protcolVersion</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>Protcol Version</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-171

(28) Item description of NodeNumberSettingFig element
Table 5-102 Item Description Specifications of NodeNumberSettingFig Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "NodeNumberSettingFig"
Write "NodeNumberSettingFig" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "Node Number Setting Valid or Invalid" in the case of English CSP+ files[Recommended specifications]Write "BOOL"
Write whether or not there is a node number setting function available. Write thevalue corresponding to availableFuncs of the CC-Link IE Field Network Specification(Application Layer Protocol).
BAP-C2005-004.
0: Function not available
1: Function available(a) Item description example of NodeNumberSettingFig element<p:commIfInfoMember label="NodeNumberSettingFig"><p:label2><p:item>NodeNumberSettingFig</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>Node Number Setting Valid or Invalid</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:commIfInfoMember>(29) Item description of TransientReceptionFig element
Table 5-103 Item Description Specifications of TransientReceptionFig Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "TransientReceptionFig"
Write "TransientReceptionFig" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "Transient Receive Function Valid or Invalid" in the case of English CSP+ files[Recommended specifications]Write "BOOL"
Write whether or not the transient reception function is available. Write the value
corresponding to availableFuncs of the CC-Link IE Field Network Specification(Application Layer Protocol) BAP-C2005-004.
0: Function not available
1: Function available(a) Item description example of TransientReceptionFig element<p:commIfInfoMember label="TransientReceptionFig"><p:label2><p:item>TransientReceptionFig</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>Transient Receive Function Valid or Invalid</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-172

(30) Item description of SMLPReceptionFig element
Table 5-104 Item Description Specifications of SMLPReceptionFig Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SMLPReceptionFig"
Write "SMLPReception" in the case of English CSP+ files[Recommended specifications]Write "COMMON_CC-Link_IE_Field"
Write "SLMP Receive Function Valid or Invalid" in the case of English CSP+ files[Recommended specifications]Write "BOOL"
Write whether or not the SLMP reception function is available.
0: Function not available
1: Function available(a) Item description example of SLMPReceptionFig element<p:commIfInfoMember label="SLMPReceptionFig"><p:label2><p:item>SLMPReception</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field</p:item></p:category><p:name><p:item>SLMP Receive Function Valid or Invalid</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:commIfInfoMember>• Details of safety communication function dependent unit
Of elements written in COMM_IF_INFO, this defines elements dependent on safety communication
functions.
Of elements written in COMM_IF_INFO, items 21 to 25 of Table 5-60 are the elements written when thecommunication interface is CC-Link IE Field Network. Write "COMMON_CC-Link_IE_Field_Safety" in thecontent of the "CATEGORY" item of these elements. Only write these elements in the case of the safety
communication function support unit of the CC-Link IE Field Network. Safety communication functions
conform to the specifications of CC-Link IE Field safety communication functions, so see "CC-Link IE
Safety Communication Function Specifications (Application Layer Service and Protocol) BAP-C2007ENG002, (Communication Profile) BAP-C2007ENG-003".
(31) Item descriptions of SafetyProtocolVersion element
Table 5-105 Item description specifications of SafetyProtocolVersion element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SafetyProtocolVersion".
Write "SafetyProtocolVersion" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_CC-Link_IE_Field_Safety". [Recommended Specifications]Write "Safety Communication Function protocol version" in the case of English CSP+
files. [Recommended Specifications]Write "BYTE".
Write the safety communication function protocol version.
0x00, 0x01, …, 0xFF
For the safety communication function protocol version, see "CC-Link IE Safety
Communication Function Specifications (Application Layer Service and Protocol)
BAP-C2007ENG-002, (Communication Profile) BAP-C2007ENG-003".

(a) Example of item descriptions of SafetyProtocolVersion element<p:commIfInfoMember label="SafetyProtcolVersion"><p:label2><p:item>SafetyProtcolVersion</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field_Safety</p:item></p:category><p:name><p:item>Safety Communication Function protocol version</p:item></p:name><p:datatype><p:item>BYTE</p:item></p:datatype><p:data><p:item>0x02</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-173

(32) Item descriptions of SafetyNodeType element
Table 5-106 Item description specifications of SafetyNodeType element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SafetyNodeType".
Write "SafetyNodeType" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_CC-Link_IE_Field_Safety". [Recommended Specifications]Write "Safety Station Type" in the case of English CSP+ files. [Recommended
Specifications]Write "BYTE".
Write "Safety Node Type" with the following values.
0x03: Safety intelligent device
0x04: Safety Remote Device
0x05: Safety Remote I/O
See "CC-Link IE Safety Communication Function Specification (Application Layer
Service and Protocol) BAP-C2007ENG-002, (Communication Profile) BAPC2007ENG-003", IESM-SetSafetyStationInfo.

(a) Item descriptions of SafetyNodeType element<p:commIfInfoMember label=" SafetyNodeType "><p:label2><p:item>SafetyNodeType</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field_Safety</p:item></p:category><p:name><p:item>Safety Station Type</p:item></p:name><p:datatype><p:item>BYTE</p:item></p:datatype><p:data><p:item>0x05</p:item></p:data></p:commIfInfoMember>(33) Item descriptions of SafetyIn_XSize element
Table 5-107 Item description specifications of SafetyIn_XSize element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "SafetyIn_XSize".
Write "SafetyIn_XSize" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_CC-Link_IE_Field_Safety". [Recommended Specifications]Write "Size of safety input data" in the case of English CSP+ files. [Recommended
Specifications]Write "BYTE".
Write the size of safety input data.

(a) Item descriptions of SafetyIn_XSize element<p:commIfInfoMember label=" SafetyIn_XSize "><p:label2><p:item>SafetyIn_XSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field_Safety</p:item></p:category><p:name><p:item>Size of safety input data</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>16</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-174

(34) Item descriptions of SafetyOut_YSize element
Table 5-108 Item description specifications of SafetyOut_YSize element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "SafetyOut_YSize".
Write "SafetyOut_YSize" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_CC-Link_IE_Field_Safety". [Recommended Specifications]Write "Size of safety output data" in the case of English CSP+ files. [Recommended
Specifications]Write "UINT16".
Write the size of safety output data.

(a) Example of item descriptions of SafetyOut_YSize element<p:commIfInfoMember label=" SafetyOut_YSize "><p:label2><p:item>SafetyOut_YSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field_Safety</p:item></p:category><p:name><p:item>Size of safety output data</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>32</p:item></p:data></p:commIfInfoMember>(35) Item descriptions of SupportSafetyCommService element
Table 5-109 Item description specifications of SupportSafetyCommService element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportSafetyCommService".
Write "SupportSafetyCommService" in the case of English CSP+ files.
[Recommended Specifications]Write "COMMON_CC-Link_IE_Field_Safety". [Recommended Specifications]Write "Supported safety communication service" in the case of English CSP+ files.
[Recommended Specifications]Write "DWORD".
Each bit of the DWORD value displays the subject service, so turn ON the bit whichshows the service supported by the device. (See Table 5-102 for bit and service
correspondence).
Write the value when turned ON of bits for services not supported.
If not even one service shown in Table 5-102 is not supported, either omit it or write
0x00000000. (If omitted, it will be counted as 0x00000000)
When showing that there is need to support multiple services, write the value ofmultiple bits turned ON.

(a) Example of item descriptions of SupportSafetyCommService element<p:commIfInfoMember label="SupportSafetyCommService"><p:label2><p:item>SupportSafetyCommService</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_Field_Safety</p:item></p:category><p:name><p:item>Supported safety communication service</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000001</p:item></p:data></p:commIfInfoMember>Table 5-110 Services shown by each bit
Bit Position
Service
0
IESS-Start
1
IESS-InvokeFunc
2 to 31
For future expansion (Set to 0).
For safety communication service, see "CC-Link IE Safety Communication Function Specification(Application Layer Service and Protocol) (Communication Profile) BAP-C2007ENG-002, BAPC2007ENG-003".

CLPA

BAP-C2008ENG-001-K
1-175

• Description of COMM_IF_INFO Part when the communication interface is Ethernet
Of elements written in COMM_IF_INFO Part, items 5 to 18 of Table 5-61 are the elements written when thecommunication interface is Ethernet. Write "COMMON_Ethernet" in the content of the "CATEGORY" itemof these elements.
(36) Item descriptions of SupportIPAddressSize element
Either omit this element, or if it is written, set the value of the DATA item to "4".
Table 5-111 Item description specifications of SupportIPAddressSize
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportIPAddressSize".
Write "SupportIPAddressSize" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "Support IP Address Size" in the case of English CSP+ files. [Recommended
Specifications]Write "UINT16".
Write The byte size of the IP address supported in set type notation.
"4" (IPv4), "16" (IPv6) or both of those listed can be considered for the value of thiselement, but for the time being it will only support 4 (IPv4).
If this element is omitted, it is considered in the same manner as "4".

(a) Example of item descriptions of SupportIPAddressSize element<p:commIfInfoMember label="SupportIPAddressSize"><p:label2><p:item>SupportIPAddressSize</p:item></p:label2><p:category><p:item>COMMON_Ethernet</p:item></p:category><p:name><p:item>Support IP Address Size</p:item></p:name><p:datatype><p:item>UINT16()</p:item></p:datatype><p:data><p:item>4</p:item></p:data></p:commIfInfoMember>(37) Item descriptions of TimeOutValue element
Table 5-112 Item description specifications of TimeOutValue element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "TimeOutValue".
Write "TimeOutValue" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "Time Out Value"" in the case of English CSP+ files. [Recommended
Specifications]Write "UINT16".
IF the IP address of the unit can be set in SLMP, write the time out value of the Set IP
Address command in integers of millisecond units.
If this element is omitted, it is considered in the same manner as if "30000" (30seconds) was entered.

(a) Example of item description of TimeOutValue element<p:commIfInfoMember label="TimeOutValue"><p:label2><p:item>TimeOutValue</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>Time Out Value</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>100</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-176

(38) Item descriptions of SupportFlg_SearchNode
Table 5-113 Item description specifications of SupportFlg_SearchNode
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_SearchNode".
Write "SupportFlg_SearchNode" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "SupportFlg_SearchNode" in the case of English CSP+ files. [Recommended
Specifications]Write "BOOL".
Write whether the SLMP command "SearchNode" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_SearchNode element<p:commIfInfoMember label="SupportFlg_SearchNode"><p:label2><p:item>SupportFlg_ SearchNode</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>SupportFlg_ SearchNode</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(39) Item descriptions of SupportFlg_SetIPAddress element
Table 5-114 Item description specifications of SupportFlg_SetIPAddress element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_SetIPAddress".
Write "SupportFlg_SetIPAddress" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "SupportFlg_SetIPAddress" in the case of English CSP+ files. [Recommended
Specifications]Write "BOOL".
Write whether the SLMP command "SetIPAddress" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_SetIPAddress element<p:commIfInfoMember label="SupportFlg_SetIPAddress"><p:label2><p:item>SupportFlg_SetIPAddress</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>SupportFlg_SetIPAddress</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-177

(40) Item descriptions of SupportFlg_CompareDeviceInfo
Table 5-115 Item description specifications of SupportFlg_CompareDeviceInfo
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_CompareDeviceInfo".
Write "SupportFlg_CompareDeviceInfo" in the case of English CSP+ files.
[Recommended Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "SupportFlg_CompareDeviceInfo" in the case of English CSP+ files.
[Recommended Specifications]Write "BOOL".
Write whether the SLMP command "CompareDeviceInfo" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_CompareDeviceInfo element<p:commIfInfoMember label="SupportFlg_CompareDeviceInfo"><p:label2><p:item>SupportFlg_CompareDeviceInfo</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>SupportFlg_CompareDeviceInfo</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(41) Item descriptions of SupportFlg_GetParam element
Table 5-116 Item description specifications of SupportFlg_GetParam element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_GetParam".
Write "SupportFlg_GetParam" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "SupportFlg_GetParam" in the case of English CSP+ files. [Recommended
Specifications]Write "BOOL".
Write whether the SLMP command "GetParameter" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_GetParam element<p:commIfInfoMember label="SupportFlg_GetParam"><p:label2><p:item>SupportFlg_GetParam</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>SupportFlg_GetParam</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-178

(42) Item descriptions of SupportFlg_CompareDeviceInfo
Table 5-117 Item description specifications of SupportFlg_SetParam
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_SetParam".
Write "SupportFlg_SetParam" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "SupportFlg_SetParam" in the case of English CSP+ files. [Recommended
Specifications]Write "BOOL".
Write whether the SLMP command "SetParameter" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_SetParam element<p:commIfInfoMember label="SupportFlg_SetParam"><p:label2><p:item>SupportFlg_SetParam</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>SupportFlg_SetParam</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(43) Item descriptions of SupportFlg_StartSetParam element
Table 5-118 Item description specifications of SupportFlg_StartSetParam element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_StartSetParam".
Write "SupportFlg_StartSetParam" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "SupportFlg_StartSetParam" in the case of English CSP+ files. [Recommended
Specifications]Write "BOOL".
Write whether the SLMP command "StartSetParameter" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_StartSetParam element<p:commIfInfoMember label="SupportFlg_StartSetParam"><p:label2><p:item>SupportFlg_StartSetParam</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>SupportFlg_StartSetParam</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-179

(44) Item descriptions of SupportFlg_EndSetParam
Table 5-119 Item description specifications of SupportFlg_EndSetParam
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_EndSetParam".
Write "SupportFlg_EndSetParam" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "SupportFlg_EndSetParam" in the case of English CSP+ files. [Recommended
Specifications]Write "BOOL".
Write whether the SLMP command "EndSetParameter" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_EndSetParam element<p:commIfInfoMember label="SupportFlg_EndSetParam"><p:label2><p:item>SupportFlg_EndSetParam</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>SupportFlg_EndSetParam</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(45) Item descriptions of SupportFlg_CancelSetParam element
Table 5-120 Item description specifications of SupportFlg_CancelSetParam element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_CancelSetParam".
Write "SupportFlg_CancelSetParam" in the case of English CSP+ files.
[Recommended Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "SupportFlg_CancelSetParam" in the case of English CSP+ files.
[Recommended Specifications]Write "BOOL".
Write whether the SLMP command "CancelSetParameter" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_CancelSetParam element<p:commIfInfoMember label="SupportFlg_CancelSetParam"><p:label2><p:item>SupportFlg_CancelSetParam</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>SupportFlg_CancelSetParam</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-180

(46) Item descriptions of SupportFlg_ReadStatus
Table 5-121 Item description specifications of SupportFlg_ReadStatus
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_ReadStatus".
Write "SupportFlg_ReadStatus" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "SupportFlg_ReadStatus" in the case of English CSP+ files. [Recommended
Specifications]Write "BOOL".
Write whether the SLMP command "ReadStatus" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_ReadStatus element<p:commIfInfoMember label="SupportFlg_ReadStatus"><p:label2><p:item>SupportFlg_ReadStatus</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>SupportFlg_ReadStatus</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(47) Item descriptions of SupportFlg_GetCommSetting element
Table 5-122 Item description specifications of SupportFlg_GetCommSetting element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_GetCommSetting".
Write "SupportFlg_GetCommSetting" in the case of English CSP+ files.
[Recommended Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "SupportFlg_GetCommSetting" in the case of English CSP+ files.
[Recommended Specifications]Write "BOOL".
Write whether the SLMP command "GetCommunicationSetting" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_GetCommSetting element<p:commIfInfoMember label="SupportFlg_GetCommSetting"><p:label2><p:item>SupportFlg_GetCommSetting</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>SupportFlg_GetCommSetting</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-181

(48) Item descriptions of SupportFlg_ReadStatus2 element
Table 5-123 Item description specifications of SupportFlg_ReadStatus2 element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_ReadStatus2".
Write "SupportFlg_ReadStatus2" in the case of English CSP+ files. [Recommended
Specifications]Write "COMMON_Ethernet". [Recommended Specifications]Write "SupportFlg_ReadStatus2" in the case of English CSP+ files. [Recommended
Specifications]Write "BOOL".
Write whether the SLMP command " ReadStatus2" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_ReadStatus2 element<p:commIfInfoMember label="SupportFlg_ReadStatus2"><p:label2><p:item>SupportFlg_ReadStatus2</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>SupportFlg_ReadStatus2</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(49) Item description of DevModel element
Table 5-124 Item Description Specifications of DevModel Element
No. Item Name
1. LABEL
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DATA

Description Details
Write "DevModel".
Write "DevModel" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_Ethernet".
Write "Model Name" in the case of English CSP+ files. [Recommended specifications]Write "STRING(48)".
Write the model using a string.

(a) Item description example of DevModel element<p:commIfInfoMember label="DevModel"><p:label2><p:item>DevModel</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>Model Name</p:item></p:name><p:datatype><p:item>STRING(48)</p:item></p:datatype><p:data><p:item>DIGITALOUT-CCIESIM-16</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-182

(50) Item description of NumOccupiedStations element
Table 5-125 Item Description Specifications of NumOccupiedStations Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "NumOccupiedStations".
Write "NumOccupiedStations" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_Ethernet".
Write "Number of Occupied Stations" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the number of occupied stations.
Write any integer value from 1 to 64.

(a) Item description example of NumOccupiedStations element<p:commIfInfoMember label="NumOccupiedStations"><p:label2><p:item>NumOccupiedStations</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>Number of Occupied Stations</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>2</p:item></p:data></p:commIfInfoMember>(51) Item description of CCIEFBasicProtocolVersion element
Table 5-126 Item Description Specifications of CCIEFBasicProtocolVersion Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CCIEFBasicProtocolVersion".
Write "CCIEFBasicProtocolVersion" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_Ethernet".
Write "CCIEF Basic Protocol Version" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the protocol version of CC-Link IE Field Network Basic.
If this element is omitted, it will be regarded as description of "1".

(a) Item description example of CCIEFBasicProtocolVersion element<p:commIfInfoMember label="CCIEFBasicProtocolVersion"><p:label2><p:item>CCIEFBasicProtocolVersion</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>CCIEF Basic Protocol Version</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-183

(52) Item description of EthernetCommFunction element
Table 5-127 Item Description Specifications of EthernetCommFunction Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "EthernetCommFunction".
Write "EthernetCommFunction" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_Ethernet".
Write "Ethernet Communication Functions" in the case of English CSP+ files.
[Recommended specifications]Write "DWORD".
Write whether or not there is a communication function supported by a Ethernet
device. Express the presence or absence of one communication function per bit. The
meanings of each bit value are described as follows:
0: Not functional
1: Functional
Functions corresponding to each bit value are described as follows:
bit0: SLMP communication function
bit1: CC-Link IE Field Network Basic communication function
bit2 to bit3: For future extension use (treating this as 0 in this version)
If this element is omitted, it will be regarded as description of "0x00000001".

(a) Item description example of EthernetCommFunction element<p:commIfInfoMember label="EthernetCommFunction"><p:label2><p:item>EthernetCommFunction</p:item></p:label2><p:category><p:item>COMMON_ Ethernet</p:item></p:category><p:name><p:item>Ethernet Communication Functions</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000002</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-184

• Description of COMM_IF_INFO part when communication interface is the CC-Link IE TSN
For the elements described in the COMM_IF_INFO part, item number 5 to 52 of Table 5-69 are theelements described when the communication interface is CC-Link IE TSN. For the item name
"CATEGORY", write "COMMON_CC-Link_IE_TSN" as the contents.
(53) Item description of StationMode element
Table 5-128 Item Description Specifications of StationMode Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "StationMode".
Write "StationMode" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Station Mode Setting Value" in the case of English CSP+ files. [Recommended
specifications]Write "WORD".
Write the station mode setting value.
[Note] When multiple COMM_IF sections are written in CC-Link IE TSN, different
values must be written in all the COMM_IF_INFO parts.

(a) Item description example of StationMode element<p:commIfInfoMember label="StationMode"><p:label2><p:item>StationMode</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Station Mode Setting Value</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:data><p:item>0x0001</p:item></p:data></p:commIfInfoMember>(54) Item description of StationModeName element
Table 5-129 Item Description Specifications of StationModeName Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "StationModeName".
Write "StationModeName" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Station Mode Name" in the case of English CSP+ files. [Recommended
specifications]Write "STRING_U(32)".
Write the station mode name.

(a) Item description example of StationModeName element<p:commIfInfoMember label="StationModeName"><p:label2><p:item>StationModeName</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Station Mode Name</p:item></p:name><p:datatype><p:item>STRING_U(32)</p:item></p:datatype><p:data><p:item>Motion Mode</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-185

(55) Item description of LocalFunction element
Table 5-130 Item Description Specifications of LocalFunction Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "LocalFunction".
Write "LocalFunction" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Local Function" in the case of English CSP+ files. [Recommended
specifications]Write "BOOL".
Write the local function.
0: Disabled
1: Enabled
If this element is omitted, it is considered in the same manner as "0".
[Note] When multiple COMM_IF sections are written in CC-Link IE TSN, the samevalue must be written in all the COMM_IF_INFO parts.

(a) Item description example of LocalFunction element<p:commIfInfoMember label="LocalFunction"><p:label2><p:item>LocalFunction</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Local Function</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(56) Item description of AutoSettingHeaderType element
Table 5-131 Item Description Specifications of AutoSettingHeaderType Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "AutoSettingHeaderType".
Write "AutoSettingHeaderType" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Automatic Setting Header Type" in the case of English CSP+ files. [Recommended
specifications]Write "BYTE".
Write the header type number (0x00 to 0xFF).
For the header type number, see the parameter automatic setting file format in "CC-Link IE
TSN Specifications (Application Layer Protocol) BAP-C2011ENG-004".
If this element is not written, it shall be considered the same as if "0x00" was written.

(a) Item description example of AutoSettingHeaderType element<p:commIfInfoMember label="AutoSettingHeaderType"><p:label2><p:item>AutoSettingHeaderType</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Automatic Setting Header Type</p:item></p:name><p:datatype><p:item>BYTE</p:item></p:datatype><p:data><p:item>0x00</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-186

(57) Item description of AutoSettingType element
Table 5-132 Item Description Specifications of AutoSettingType Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "AutoSettingType".
Write "AutoSettingType" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Auto Setting Type" in the case of English CSP+ files. [Recommended
specifications]Write "WORD".
Write the automatic setting type.
0x0000: Function not available (default)
0x0001: Settable for individual parameters only
0x0002: Settable for batch parameters only
If this element is not written, it shall be considered the same as if "0x0000" waswritten.
If this element is omitted, it is considered in the same manner as "0".
When 0x0001 is set, always write MESSAGE for parameter auto setting describedin Section 5.5.10.2.
When 0x0002 is set, parameter related information (values of METHOD_TYPE item
and MESSAGE_TYPE item are elements of PARAMETER and
AUTO_PARAMETER) is not supported.

(a) Item description example of AutoSettingType element<p:commIfInfoMember label="AutoSettingType"><p:label2><p:item>AutoSettingType</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Auto Setting Type</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:data><p:item>0x0001</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-187

(58) Item description of ModelCode element
Table 5-133 Item Description Specifications of ModelCode Element
No.
1.
2.
3.
4.
5.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPE

6.

DATA

Description Details
Write "ModelCode".
Write "ModelCode" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Model Code" in the case of English CSP+ files. [Recommended specifications]Write "UINT32".
Write the model code.
Write the model code of the network information of the CC-Link IE TSNSpecifications (Overview) BAP-C2011ENG-001.
Write the model of the communication module when the module type iscommunication module.
[Note] When multiple COMM_IF sections are written in CC-Link IE TSN, the samevalue must be written in all the COMM_IF_INFO parts.

(a) Item description example of ModelCode element<p:commIfInfoMember label="ModelCode"><p:label2><p:item>ModelCode</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Model Code</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>1234</p:item></p:data></p:commIfInfoMember>(59) Item description of ModelCodeEx element
Table 5-134 Item Description Specifications of ModelCodeEx Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ModelCodeEx".
Write "ModelCodeEx" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Extended Model Code" in the case of English CSP+ files. [Recommended
specifications]Write "UINT16".
Write the extended model code.
Write the extended model code of the CC-Link IE TSN Specifications (Overview)
BAP-C2011ENG-001.
[Note] When multiple COMM_IF sections are written in CC-Link IE TSN, the samevalue must be written in all the COMM_IF_INFO parts.
For the application rules for the extended model code, see (1) in Section 5.3.1.1.

(a) Item description example of ModelCodeEx element<p:commIfInfoMember label="ModelCodeEx"><p:label2><p:item>ModelCodeEx</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Extended Model Code/p:item></p:name><p:datatype><p:item> UINT16</p:item></p:datatype><p:data><p:item>9876</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-188

(60) Item description of DevModel element
Table 5-135 Item Description Specifications of DevModel Element
No.
1.
2.
3.

Item NameLABELLABEL2
CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "DevModel".
Write "DevModel" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Model Name" in the case of English CSP+ files. [Recommended
specifications]Write "STRING(48)".
Write the model.
Write the model name of the communication module when the module type iscommunication module.
[Note] When multiple COMM_IF sections are written in CC-Link IE TSN, the samevalue must be written in all the COMM_IF_INFO parts.

(a) Item description example of DevModel element<p:commIfInfoMember label="DevModel"><p:label2><p:item>DevModel</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Model Name</p:item></p:name><p:datatype><p:item>STRING(48)</p:item></p:datatype><p:data><p:item> CC-Link IE TSNEthernetAdapter </p:item></p:data></p:commIfInfoMember>(61) Item description of ConnectionPortCableType element
Table 5-136 Item Description Specifications of ConnectionPortCableType Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ConnectionPortCableType".
Write "ConnectionPortCableType" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Connection Port Cable Type" in the case of English CSP+ files.
[Recommended specifications]Write "WORD".
Write the cable type of the connection port.
0x0000: Twisted pair cable (default)
0x0001: Optical cable
0x0002 or later: For future expansion
If this element is omitted, it will be regarded as "0x0000 (Twisted pair cable)".
Write only the information of the port corresponding to CC-Link IE TSN defined by
the COMM_IF section to which the COMM_IF_INFO part describing this element
belongs.
For devices connected to multiple networks, such as gateways, port information of
unrelated networks is not written. The same applies to devices connected to multiple
CC-Link IE TSN.
[Note] When multiple COMM_IF sections are written in CC-Link IE TSN, the samevalue must be written in all the COMM_IF_INFO parts.

(a) Item description example of ConnectionPortCableType element<p:commIfInfoMember label="ConnectionPortCableType"><p:label2><p:item>ConnectionPortCableType</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Connection Port Cable Type</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:data><p:item>0x0000</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-189

(62) Item description of ConnectionPortNum element
Table 5-137 Item Description Specifications of ConnectionPortNum Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ConnectionPortNum".
Write "ConnectionPortNum" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Number of Connection Ports" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the number of the connection ports (1 or more).
If this element is omitted, it will be regarded as "Undefined".
Write only the information of the port corresponding to CC-Link IE TSN defined by
the COMM_IF section to which the COMM_IF_INFO part describing this element
belongs.
For devices connected to multiple networks, such as gateways, port information of
unrelated networks is not written. The same applies to devices connected to multiple
CC-Link IE TSN.
[Note] When multiple COMM_IF sections are written in CC-Link IE TSN, the samevalue must be written in all the COMM_IF_INFO parts.

(a) Item description example of ConnectionPortNum element<p:commIfInfoMember label="ConnectionPortNum"><p:label2><p:item>ConnectionPortNum</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Number of Connection Ports</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>2</p:item></p:data></p:commIfInfoMember>(63) Item description of CanProfileNum element
Table 5-138 Item Description Specifications of CanProfileNum Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CanProfileNum".
Write "CanProfileNum" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Supported CiA Standard Number" in the case of English CSP+ files.
[Recommended specifications]Write "STRING(32)".
Write the supported CiA standard number.
401: The CiA401 standard is supported.
402: The CiA402 standard is supported.
If this element is omitted, it is considered that CAN is not supported.

(a) Item description example of CanProfileNum element<p:commIfInfoMember label="CanProfileNum"><p:label2><p:item>CanProfileNum</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Supported CiA Standard Number</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>401</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-190

(64) Item description of ObjectDictionaryFileName element
Table 5-139 Item Description Specifications of ObjectDictionaryFileName Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ObjectDictionaryFileName".
Write the "ObjectDictionaryFileName" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write the "Object Dictionary File Name" in the case of English CSP+ files.
[Recommended specifications]Write "STRING(52)".
Write the object dictionary file name with the extension (.csv).
For a file name, only one-byte alphanumerical characters and symbols are usable.

(a) Item description example of ObjectDictionaryFileName element<p:commIfInfoMember label="ObjectDictionaryFileName"><p:label2><p:item>ObjectDictionaryFileName</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Object Dictionary File Name</p:item></p:name><p:datatype><p:item>STRING(52)</p:item></p:datatype><p:data><p:item>A1234.csv</p:item></p:data></p:commIfInfoMember>(65) Item description of CommunicationCycleMinTime_ns element
Table 5-140 Item Description Specifications of CommunicationCycleMinTime_ns Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CommunicationCycleMinTime_ns".
Write "CommunicationCycleMinTime_ns" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "CommunicationCycleMinTime_ns" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
When using devices in the supported station mode, write the minimum
communication cycle that can be supported by the devices in the unit of ns. The
writable range is 0 to 999999999.
[Note] When the minimum communication cycle is 1 second or longer, write it with
CommunicationCycleMinTime_s as a set.

(a) Item description example of CommunicationCycleMinTime_ns element<p:commIfInfoMember label=" CommunicationCycleMinTime_ns "><p:label2><p:item>CommunicationCycleMinTime_ns </p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>CommunicationCycleMinTime_ns</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>10000</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-191

(66) Item description of CommunicationCycleMinTime_s element
Table 5-141 Item Description specifications of CommunicationCycleMinTime_s Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CommunicationCycleMinTime_s".
Write "CommunicationCycleMinTime_s" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "CommunicationCycleMinTime_s" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
When using devices in the supported station mode, write the minimum
communication cycle that can be supported by the devices in the unit of s. The
writable range is 0 to 65535.

(a) Item description example of CommunicationCycleMinTime_s element<p:commIfInfoMember label="CommunicationCycleMinTime_s"><p:label2><p:item>CommunicationCycleMinTime_s</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>CommunicationCycleMinTime_s</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(67) Item description of CyclicResMaxTime element
Table 5-142 Item Description Specifications of CyclicResMaxTime Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CyclicResMaxTime".
Write "CyclicResMaxTime" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Maximum Response Time for the Time Managed Polling Method" in the caseof English CSP+ files. [Recommended specifications]Write "UINT8".
The writable range is 0 to 20.
The actual response time is expressed in 2x µs when x is the value set for this item.
Example) When the setting value is "3", the maximum response time is 23 = 8 µs.
If this item is omitted, the default value is 0.
(Assuming that the device is not using the time managed polling method)
If multiple certification classes can be selected in the same station mode and theavailability of the time managed polling method differs by certification class, write theresponse time of the certification class that can support the time managed polling
method.

(a) Item description example of CyclicResMaxTime element<p:commIfInfoMember label="CyclicResMaxTime><p:label2><p:item>CyclicResMaxTime</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Maximum Response Time for the Time Managed Polling Method</p:item></p:name><p:datatype><p:item>UINIT8</p:item></p:datatype><p:data><p:item>10</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-192

(68) Item description of IEEE802_1ASFunction element
Table 5-143 Item Description Specifications of IEEE802_1ASFunction Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "IEEE802_1ASFunction".
Write "IEEE802_1ASFunction" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "IEEE802_1AS Function" in the case of English CSP+ files. [Recommended
specifications]Write "BOOL".
Write whether the IEEE802.1AS function is available or not.
0: Function not available
1: Function available
Write whether the IEEE802.1AS function used in CC-Link IE TSN Specification (Overview)
BAP-C2011ENG-001 is available or not.

(a) Item description example of IEEE802_1ASFunction element<p:commIfInfoMember label="IEEE802_1ASFunction"><p:label2><p:item>IEEE802_1AS Function</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>IEEE802_1AS Function</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-193

(69) Item description of ReceiveFunction100M element
Table 5-144 Item Description Specifications of ReceiveFunction100M Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ReceiveFunction100M".
Write "ReceiveFunction100M" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Receive Function_100Mbps" in the case of English CSP+ files.
[Recommended specifications]Write "BOOL".
Write whether or not there is a 100Mbps full-rate receive function.
0: Function not available
1: Function available
Write the value equivalent to the certification class information in the CC-Link IE TSNSpecifications (Overview) BAP-C2011ENG-001.

(a) Item description example of ReceiveFunction100M element<p:commIfInfoMember label="ReceiveFunction100M"><p:label2><p:item>ReceiveFunction100M</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Receive Function_100Mbps</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(70) Item description of RelayFunction100M element
Table 5-145 Item Description Specifications of RelayFunction100M Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "RelayFunction100M".
Write "RelayFunction100M" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Relay Function_100Mbps" in the case of English CSP+ files. [Recommended
specifications]Write "BOOL".
Write whether or not there is a 100Mbps full-rate relay function.
0: Function not available
1: Function available
Write the value equivalent to the certification class information in the CC-Link IE TSNSpecifications (Overview) BAP-C2011ENG-001.

(a) Item description example of RelayFunction100M element<p:commIfInfoMember label="RelayFunction100M"><p:label2><p:item>RelayFunction100M</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Relay Function_100Mbps</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-194

(71) Item description of ReceiveFunction1G element
Table 5-146 Item Description Specifications of ReceiveFunction1G Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ReceiveFunction1G".
Write "ReceiveFunction1G" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Receive Function_1Gbps" in the case of English CSP+ files. [Recommended
specifications]Write "BOOL".
Write whether or not there is a 1Gbps full-rate receive function.
0: Function not available
1: Function available
Write the value equivalent to the certification class information in the CC-Link IE TSNSpecifications (Overview) BAP-C2011ENG-001.

(a) Item description example of ReceiveFunction1G element<p:commIfInfoMember label="ReceiveFunction1G"><p:label2><p:item>ReceiveFunction1G</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Receive Function_1Gbps</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:commIfInfoMember>(72) Item description of RelayFunction1G element
Table 5-147 Item Description Specifications of RelayFunction1G Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "RelayFunction1G".
Write "RelayFunction1G" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Relay Function_1Gbps" in the case of English CSP+ files. [Recommended
specifications]Write "BOOL".
Write whether or not there is a 1Gbps full-rate relay function.
0: Function not available
1: Function available
Write the value equivalent to the certification class information in the CC-Link IE TSNSpecifications (Overview) BAP-C2011ENG-001.

(a) Item description example of RelayFunction1G element<p:commIfInfoMember label="RelayFunction1G"><p:label2><p:item>RelayFunction1G</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Relay Function_1Gbps</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-195

(73) Item description of MultiCastFunction element
Table 5-148 Item Description Specifications of MultiCastFunction Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "MultiCastFunction".
Write "MultiCastFunction" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Broad_MultiCast Function" in the case of English CSP+ files.
[Recommended specifications]Write "BOOL".
Write whether or not there is a broadcast/multicast function.
0: Function not available
1: Function available
Write the value equivalent to the certification class information in the CC-Link IE TSNSpecifications (Overview) BAP-C2011ENG-001.

(a) Item description example of MultiCastFunction element<p:commIfInfoMember label="MultiCastFunction"><p:label2><p:item>MultiCastFunction</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Broad_MultiCast Function</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(74) Item description of CertificationClass element
Table 5-149 Item Description Specifications of CertificationClass Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CertificationClass".
Write "CertificationClass" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Certification Class" in the case of English CSP+ files. [Recommended
specifications]Write "STRING_U(2)".
Write the CC-Link IE TSN Class in one-byte uppercase characters.
Example: A
Write the character equivalent to the CC-Link IE TSN Class information described in
the CC-Link IE TSN Specifications (Overview) (BAP-C2011ENG-001).
[For devices in which multiple CC-Link IE TSN Classes can be selected in the same
station mode]• In this element, write only the default CC-Link IE TSN Class.
• The description of the CertificationClassChoice element is required.

(a) Item description example of CertificationClass element<p:commIfInfoMember label="CertificationClass"><p:label2><p:item>CertificationClass</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Certification Class</p:item></p:name><p:datatype><p:item>STRING_U(2)</p:item></p:datatype><p:data><p:item>A</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-196

(75) Item description of CertificationClassChoice element
Table 5-150 Item Description Specifications of CertificationClassChoice Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CertificationClassChoice".
Write "CertificationClassChoice" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Certification Class Choice" in the case of English CSP+ files. [Recommended
specifications]Write "STRING_U(2)()".
Write the CC-Link IE TSN Classes that can be selected in the same station mode inaggregative notation. The description format of each element is the same as that of
the CertificationClass element. Also, always set the first element to the same value
as the CertificationClass element.
When the CC-Link IE TSN Class is changed due to the station mode change, write
each CC-Link IE TSN Class in a separate COMM_IF section.

(a) Item description example of CertificationClassChoice element<p:commIfInfoMember label="CertificationClassChoice"><p:label2><p:item>CertificationClassChoice</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Certification Class Choice</p:item></p:name><p:datatype><p:item>STRING_U(2)()</p:item></p:datatype><p:data><p:item>A</p:item><p:item>B</p:item></p:data></p:commIfInfoMember>(76) Item description of SupportFlg_IPAddressSet element
Table 5-151 Item Description Specifications of SupportFlg_IPAddressSet Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_IPAddressSet".
Write "SupportFlg_IPAddressSet" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "SupportFlg_IPAddressSet" in the case of English CSP+ files.
[Recommended specifications]Write "BOOL".
Write whether the SLMP command "IPAddressSet" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_IPAddressSet element<p:commIfInfoMember label="SupportFlg_IPAddressSet"><p:label2><p:item>SupportFlg_IPAddressSet</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>SupportFlg_IPAddressSet</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-197

(77) Item description of SupportFlg_NodeIndication element
Table 5-152 Item Description Specifications of SupportFlg_NodeIndication Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportFlg_NodeIndication".
Write "SupportFlg_NodeIndication" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "SupportFlg_NodeIndication" in the case of English CSP+ files.
[Recommended specifications]Write "BOOL".
Write whether the SLMP command "NodeIndication" is supported or not.
0: Not supported
1: Supported
If this item is not written, it will be regarded as "0".

(a) Item description example of SupportFlg_NodeIndication element<p:commIfInfoMember label="SupportFlg_NodeIndication"><p:label2><p:item>SupportFlg_NodeIndication</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>SupportFlg_NodeIndication</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(78) Item description of S_B_DefaultSize element
Table 5-153 Item Description Specifications of S_B_DefaultSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_B_DefaultSize".
Write "S_B_DefaultSize" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Send Bit Data Default Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the default size of the send bit data (RX) in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".

(a) Item description example of S_B_DefaultSize element<p:commIfInfoMember label="S_B_DefaultSize"><p:label2><p:item>S_B_DefaultSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Send Bit Data Default Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>30</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-198

(79) Item description of S_W_DefaultSize element
Table 5-154 Item Description Specifications of S_W_DefaultSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_W_DefaultSize".
Write "S_W_DefaultSize" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Send Word Data Default Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the default size of the send word data (RWr, TPDO, general send access) in
the number of words.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
In the case of devices that use TPDO communication, write a value equal to or larger
than the default number of TPDO mapping points.

(a) Item description example of S_W_DefaultSize element<p:commIfInfoMember label="S_W_DefaultSize"><p:label2><p:item>S_W_DefaultSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Send Word Data Default Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>15</p:item></p:data></p:commIfInfoMember>(80) Item description of R_B_DefaultSize element
Table 5-155 Item Description Specifications of R_B_DefaultSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "R_B_DefaultSize".
Write "R_B_DefaultSize" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Receive Bit Data Default Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the default size of the receive bit data (RY) in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".

(a) Item description example of R_B_DefaultSize element<p:commIfInfoMember label="R_B_DefaultSize"><p:label2><p:item>R_B_DefaultSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Receive Bit Data Default Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>18</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-199

(81) Item description of R_W_DefaultSize element
Table 5-156 Item Description Specifications of R_W_DefaultSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "R_W_DefaultSize".
Write "R_W_DefaultSize" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Receive Word Data Default Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the default size of the receive word data (RWw, RPDO, general receive
access) in the number of words.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
In the case of devices that use RPDO communication, write a value equal to or
larger than the default number of RPDO mapping points.

(a) Item description example of R_W_DefaultSize element<p:commIfInfoMember label="R_W_DefaultSize"><p:label2><p:item>R_W_DefaultSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Receive Word Data Default Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>14</p:item></p:data></p:commIfInfoMember>(82) Item description of L_B_DefaultSize element
Table 5-157 Item Description Specifications of L_B_DefaultSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "L_B_DefaultSize".
Write "L_B_DefaultSize" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Link Relay Default Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the default size of the link relay data (LB) in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
Prohibited for a device that does not support the local function.

(a) Item description example of L_B_DefaultSize element<p:commIfInfoMember label="L_B_DefaultSize"><p:label2><p:item>L_B_DefaultSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Link Relay Default Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>30</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-200

(83) Item description of L_W_DefaultSize element
Table 5-158 Item Description Specifications of L_W_DefaultSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "L_W_DefaultSize".
Write "L_W_DefaultSize" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Link Register Default Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the default size of the link register data (LW) in the number of words.
Write a numerical value other than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
Prohibited for a device that does not support the local function.

(a) Item description example of L_W_DefaultSize element<p:commIfInfoMember label="L_W_DefaultSize"><p:label2><p:item>L_W_DefaultSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Link Register Default Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>50</p:item></p:data></p:commIfInfoMember>(84) Item description of S_B_MaxSize element
Table 5-159 Item Description Specifications of S_B_MaxSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_B_MaxSize".
Write "S_B_MaxSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Send Bit Data Maximum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the maximum size of the send bit data (RX) in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".

(a) Item description example of S_B_MaxSize element<p:commIfInfoMember label="S_B_MaxSize"><p:label2><p:item>S_B_MaxSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Send Bit Data Maximum Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>1024</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-201

(85) Item description of S_W_MaxSize element
Table 5-160 Item Description Specifications of S_W_MaxSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_W_MaxSize".
Write "S_W_MaxSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Send Word Data Maximum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the maximum size of the send word data (RWr, TPDO, general send access) in
the number of words.
Write a numerical equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
In the case of devices that use TPDO communication, write a value equal to or larger
than the number of TPDO mapping points in the maximum size.

(a) Item description example of S_W_MaxSize element<p:commIfInfoMember label="S_W_MaxSize"><p:label2><p:item>S_W_MaxSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Send Word Data Maximum Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>512</p:item></p:data></p:commIfInfoMember>(86) Item description of R_B_MaxSize element
Table 5-161 Item Description Specifications of R_B_MaxSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "R_B_MaxSize".
Write "R_B_MaxSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Receive Bit Data Maximum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the maximum size of the receive bit data (RY) in the number of bits.
Write a numerical equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".

(a) Item description example of R_B_MaxSize element<p:commIfInfoMember label="R_B_MaxSize"><p:label2><p:item>R_B_MaxSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>R_B_MaxSize</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>2048</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-202

(87) Item description of R_W_MaxSize element
Table 5-162 Item Description Specifications of R_W_MaxSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "R_W_MaxSize".
Write "R_W_MaxSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Receive Word Data Maximum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the maximum size of the receive word data (RWw, RPDO, general receive
access) in the number of words.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
In the case of devices that use RPDO communication, write a value equal to or
larger than the number of RPDO mapping points at the maximum size.

(a) Item description example of R_W_MaxSize element<p:commIfInfoMember label="R_W_MaxSize"><p:label2><p:item>R_W_MaxSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Receive Word Data Maximum Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>512</p:item></p:data></p:commIfInfoMember>(88) Item description of L_B_MaxSize element
Table 5-163 Item Description Specifications of L_B_MaxSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "L_B_MaxSize".
Write "L_B_MaxSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Link Relay Maximum Size" in the case of English CSP+ files. [Recommended
specifications]Write "UINT32".
Write the maximum size of the link relay data (LB) in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
Prohibited for a device that does not support the local function.

(a) Item description example of L_B_MaxSize element<p:commIfInfoMember label="L_B_MaxSize"><p:label2><p:item>L_B_MaxSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Link Relay Maximum Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>1024</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-203

(89) Item description of L_W_MaxSize element
Table 5-164 Item Description Specifications of L_W_MaxSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "L_W_MaxSize".
Write "L_W_MaxSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Link Register Maximum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the maximum size of the link register data (LW) in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
Prohibited for a device that does not support the local function.

(a) Item description example of L_W_MaxSize element<p:commIfInfoMember label="L_W_MaxSize"><p:label2><p:item>L_W_MaxSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Link Register Maximum Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>512</p:item></p:data></p:commIfInfoMember>(90) Item description of S_B_MinSize element
Table 5-165 Item Description Specifications of S_B_MinSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_B_MinSize".
Write "S_B_MinSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Send Bit Data Minimum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the minimum size of the send bit data (RX) in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
If omitted, 0 is regarded to be set.

(a) Item description example of S_B_MinSize element<p:commIfInfoMember label="S_B_MinSize"><p:label2><p:item>S_B_MinSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Send Bit Data Minimum Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-204

(91) Item description of S_W_MinSize element
Table 5-166 Item Description Specifications of S_W_MinSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_W_MinSize".
Write "S_W_MinSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Send Word Data Minimum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the minimum size of the send word data (RWr, TPDO, general send access) in
the number of words.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
If omitted, 0 is regarded to be set.
In the case of devices that use TPDO communication, write a value equal to or larger
than the number of TPDO mapping points at the minimum size.

(a) Item description example of S_W_MinSize element<p:commIfInfoMember label="S_W_MinSize"><p:label2><p:item>S_W_MinSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Send Word Data Minimum Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:commIfInfoMember>(92) Item description of R_B_MinSize element
Table 5-167 Item Description Specifications of R_B_MinSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "R_B_MinSize".
Write "R_B_MinSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Receive Bit Data Minimum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the minimum size of the receive bit data (RY) in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
If omitted, 0 is regarded to be set.

(a) Item description example of R_B_MinSize element<p:commIfInfoMember label="R_B_MinSize"><p:label2><p:item>R_B_MinSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Receive Bit Data Minimum Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>2</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-205

(93) Item description of R_W_MinSize element
Table 5-168 Item Description Specifications of R_W_MinSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "R_W_MinSize".
Write "R_W_MinSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Receive Word Data Minimum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the minimum size of the receive word data (RWw, RPDO, general receive
access) in the number of words.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
If omitted, 0 is regarded to be set.
In the case of devices that use RPDO communication, write a value equal to or
larger than the number of RPDO mapping points at the minimum size.

(a) Item description example of R_W_MinSize element<p:commIfInfoMember label="R_W_MinSize"><p:label2><p:item>R_W_MinSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Receive Word Data Minimum Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(94) Item description of L_B_MinSize element
Table 5-169 Item Description Specifications of L_B_MinSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "L_B_MinSize".
Write "L_B_MinSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Link Relay Minimum Size" in the case of English CSP+ files. [Recommended
specifications]Write "UINT32".
Write the minimum size of the link relay data (LB) in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
If omitted, 0 is regarded to be set.
Prohibited for a device that does not support the local function.

(a) Item description example of L_B_MinSize element<p:commIfInfoMember label="L_B_MinSize"><p:label2><p:item>L_B_MinSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Link Relay Minimum Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-206

(95) Item description of L_W_MinSize element
Table 5-170 Item Description Specifications of L_W_MinSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "L_W_MinSize".
Write "L_W_MinSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Link Register Minimum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the minimum size of the link register data (LW) in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".
If omitted, 0 is regarded to be set.
Prohibited for a device that does not support the local function.

(a) Item description example of L_W_MinSize element<p:commIfInfoMember label="L_W_MinSize"><p:label2><p:item>L_W_MinSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Link Register Minimum Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(96) Item description of S_B_Address element
Table 5-171 Item Description Specifications of S_B_Address Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "S_B_Address".
Write "S_B_Address" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Send Bit Data Address" in the case of English CSP+ files. [Recommended
specifications]Write "DWORD".
Write the start address used for send bit data (Rx) communication.

(a) Item description example of S_B_Address element<p:commIfInfoMember label="S_B_Address"><p:label2><p:item>S_B_Address</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Send Bit Data Address</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000123</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-207

(97) Item description of S_W_Address element
Table 5-172 Item Description Specifications of S_W_Address Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "S_W_Address".
Write "S_W_Address" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Send Word Data Address" in the case of English CSP+ files. [Recommended
specifications]Write "DWORD".
Write the start address used for send word data (RWr) communication.

(a) Item description example of S_W_Address element<p:commIfInfoMember label="S_W_Address"><p:label2><p:item>S_W_Address</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Send Word Data Address</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000456</p:item></p:data></p:commIfInfoMember>(98) Item description of R_B_Address element
Table 5-173 Item Description Specifications of R_B_Address Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "R_B_Address".
Write "R_B_Address" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Receive Bit Data Address" in the case of English CSP+ files. [Recommended
specifications]Write "DWORD".
Write the memory address used for receive bit data (RY) communication.

(a) Item description example of R_B_Address element<p:commIfInfoMember label="R_B_Address"><p:label2><p:item>R_B_Address</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Receive Bit Data Address</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000789</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-208

(99) Item description of R_W_Address element
Table 5-174 Item Description Specifications of R_W_Address Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "R_W_Address".
Write "R_W_Address" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Receive Word Data Address" in the case of English CSP+ files.
[Recommended specifications]Write "DWORD".
Write the memory address used for receive word data (RWw) communication.

(a) Item description example of R_W_Address element<p:commIfInfoMember label="R_W_Address"><p:label2><p:item>R_W_Address</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Receive Word Data Address</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000159</p:item></p:data></p:commIfInfoMember>(100)

Item description of StsW_Address element
Table 5-175 Item Description Specifications of StsW_Address Element

No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "StsW_Address".
Write "StsW_Address" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "Status Notification Device Address" in the case of English CSP+ files.
[Recommended specifications]Write "DWORD".
Write the memory address for the status notification device (StsW).

(a) Item description example of StsW_Address element<p:commIfInfoMember label="StsW_Address"><p:label2><p:item>StsW_Address</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>Status Notification Device Address</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000753</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-209

(101)

Item description of PDOConfigIndex+X element
Table 5-176 Item Description Specifications of PDOConfigIndex+X Element

No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "PDOConfigIndex+X".
Write an integer equal to or larger than 1 for X in order. This value cannot be
omitted.
Write "PDOConfigIndex+X" in the case of English CSP+ files. [Recommended
specifications]Write any integer for X.
Write "COMMON_CC-Link_IE_TSN".
Write "PDO Configuration Index +X" in the case of English CSP+ files.
[Recommended specifications]Write any integer for X.
Write "WORD".
Write the index of the PDO configuration.
Write the range referring to "D.2 PDO Config" in the CC-Link IE TSN Specifications(Overview) BAP-C2011ENG-001.

(a) Item description example of PDOConfigIndex1 element<p:commIfInfoMember label="PDOConfigIndex1"><p:label2><p:item>PDOConfigIndex1</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>PDO Configuration Index 1</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:data><p:item>0x1C00</p:item></p:data></p:commIfInfoMember>(102)

Item description of PDOConfigPDOType+X element
Table 5-177 Item Description Specifications of PDOConfigPDOType+X Element

No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "PDOConfigPDOType+X".
Write the same value as PDOConfigIndex for X. This value cannot be omitted.
Write "PDOConfigPDOType+X" in the case of English CSP+ files. [Recommended
specifications]Write any integer for X.
Write "COMMON_CC-Link_IE_TSN".
Write "PDO Configuration PDO Type +X" in the case of English CSP+ files.
[Recommended specifications]Write any integer for X.
Write "BYTE".
Write the PDO type of the PDO configuration.
0x00:RPDO
0x01:TPDO(a) Item description example of PDOConfigPDOType1 element<p:commIfInfoMember label="PDOConfigPDOType1"><p:label2><p:item>PDOConfigPDOType1</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>PDO Configuration PDO Type 1</p:item></p:name><p:datatype><p:item>BYTE</p:item></p:datatype><p:data><p:item>0x01</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-210

(103)

Item description of PDOConfigMemoryAddress+X element
Table 5-178 Item Description Specifications of PDOConfigMemoryAddress+X Element

No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "PDOConfigMemoryAddress+X".
Write the same value as PDOConfigIndex for X. This value cannot be omitted.
Write "PDOConfigMemoryAddress+X" in the case of English CSP+ files.
[Recommended specifications]Write any integer for X.
Write "COMMON_CC-Link_IE_TSN".
Write "PDO Configuration Memory Address +X" in the case of English CSP+ files.
[Recommended specifications]Write any integer for X.
Write "DWORD".
Write the memory address of the PDO configuration.
For RPDO: Write the memory address of the sub payload.
For TPDO: Write the start address of the data to be stored in the sub payload.

(a) Item description example of PDOConfigMemoryAddress1 element<p:commIfInfoMember label="PDOConfigMemoryAddress1"><p:label2><p:item>PDOConfigMemoryAddress1</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>PDO Configuration Memory Address 1</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000001</p:item></p:data></p:commIfInfoMember>(104)

Item description of PDOConfigPossibleMapping+X element
Table 5-179 Item Description Specifications of PDOConfigPossibleMapping+X Element

No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "PDOConfigPossibleMapping+X".
Write the same value as PDOConfigIndex for X. This value cannot be omitted.
Write "PDOConfigPossibleMapping+X" in the case of English CSP+ files.
[Recommended specifications]Write any integer for X.
Write "COMMON_CC-Link_IE_TSN".
Write "PDO Configuration Mapping Candidate +X" in the case of English CSP+ files.
[Recommended specifications]Write any integer for X.
* Write a name for NAME in consideration of 0x00 of SubIndex of the object
dictionary.
Write "WORD[x]".
Number of x elements: 1 to 512
Write the PDO mapping objects that can be set in PDO Assignment of the PDO
configuration as an array in priority order.
Example: <0x1600><0x1601> The first element will be the default.

(a) Item description example of PDOConfigPossibleMapping1 element<p:commIfInfoMember label="PDOConfigPossibleMapping1"><p:label2><p:item>PDOConfigPossibleMapping1</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>PDO Configuration Mapping Candidate 1/p:item></p:name><p:datatype><p:item>WORD[2]</p:item></p:datatype><p:data><p:item><0x1600><0x1601></p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-211

(105)

Item description of S_General_Address element
Table 5-180 Item Description Specifications of S_General_Address Element

No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "S_General_Address".
Write "S_General_Address" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "General Send Memory Address" in the case of English CSP+ files.
[Recommended specifications]Write "DWORD".
Write the memory address for general send access.

(a) Item description example of S_General_Address element<p:commIfInfoMember label="S_General_Address"><p:label2><p:item>S_General_Address</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>General Send Memory Address</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000741</p:item></p:data></p:commIfInfoMember>(106)

Item description of R_General_Address element
Table 5-181 Item Description Specifications of R_General_Address Element

No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "R_General_Address".
Write "R_General_Address" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN".
Write "General Receive Memory Address" in the case of English CSP+ files.
[Recommended specifications]Write "DWORD".
Write the memory address for general receive access.

(a) Item description example of R_General_Address element<p:commIfInfoMember label="R_General_Address"><p:label2><p:item>R_General_Address</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN</p:item></p:category><p:name><p:item>General Receive Memory Address</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000369</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-212

• Details of CC-Link IE TSN safety communication function dependent area
Of elements written in the COMM_IF_INFO part, this defines those elements that are dependent on thesafety communication function. For the elements described in the COMM_IF_INFO part, item number 53 to
64 of Table 5-69 are the elements described when the communication interface is CC-Link IE TSN. For theitem name "CATEGORY", write "COMMON_CC-Link_IE_TSN_Safety" as the contents. Only write theseelements in the case of the safety communication function support unit of CC-Link IE TSN. The CC-Link IE
TSN safety communication function conforms to the specifications of the CC-Link IE TSN safety
communication function, so see "CC-Link IE Safety Communication Function Specification (Application
Layer Service and Protocol) BAP-C2007ENG-002 and (Communication Profile) BAP-C2007ENG-003".
(107) Item description of SafetyProtocolVersion element
Table 5-182 Item Description Specifications of SafetyProtocolVersion Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SafetyProtocolVersion".
Write "SafetyProtocolVersion" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN_Safety".
Write "Safety Communication Function Protocol Version" in the case of English
CSP+ files.
[Recommended specifications]Write "BYTE".
Write the safety communication function protocol version.
0x00, 0x01, ...0xFF
For details on the safety communication function protocol version, see the safety
communication function protocol version of "CC-Link IE Safety Communication
Function Specifications (Application Layer and Service Protocol) BAP-C2007ENG002 and (Communication Profile) BAP-C2007ENG-003".

(a) Item description example of SafetyProtocolVersion element<p:commIfInfoMember label="SafetyProtocolVersion"><p:label2><p:item>SafetyProtocolVersion</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN_Safety</p:item></p:category><p:name><p:item>Safety Communication Function Protocol Version</p:item></p:name><p:datatype><p:item>BYTE</p:item></p:datatype><p:data><p:item>0x01</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-213

(108) Item description of SafetyNodeType element
Table 5-183 Item Description Specifications of SafetyNodeType Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SafetyNodeType".
Write "SafetyNodeType" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN_Safety".
Write "Safety Node Type" in the case of English CSP+ files. [Recommended
specifications]Write "BYTE".
Write the safety node type.
0x02: Safety local
0x06: Safety remote(a) Item description example of SafetyNodeType element<p:commIfInfoMember label="SafetyNodeType"><p:label2><p:item>SafetyNodeType</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN_Safety</p:item></p:category><p:name><p:item>Safety Node Type</p:item></p:name><p:datatype><p:item>BYTE</p:item></p:datatype><p:data><p:item>0x02</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-214

(109) Item description of SupportSafetyCommService element
Table 5-184 Item Description Specifications of SupportSafetyCommService Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportSafetyCommService".
Write "SupportSafetyCommService" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN_Safety".
Write "Support Safety Communication Service" in the case of English CSP+ files.
[Recommended specifications]Write "DWORD".
Each bit of the DWORD value shows a target service. Turn ON a bit indicating aservice supported by the device. (See Table 5-185 for the bit and service
correspondence.)
Do not write the value with a bit corresponding to an unsupported service turned ON.
If not even one service shown in Table 5-185 is supported, omit this or write"0x00000000". If this is omitted, it will be regarded to be "0x00000000".
To show that there is a need to support multiple services, write the value withmultiple bits turned ON.

(a) Item description example of SupportSafetyCommService element<p:commIfInfoMember label="SupportSafetyCommService"><p:label2><p:item>SupportSafetyCommService</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN_Safety</p:item></p:category><p:name><p:item>Support Safety Communication Service</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000001</p:item></p:data></p:commIfInfoMember>Table 5-185 Service Shown by Each Bit
Bit Position0
1
2 to 31

Service
IESS-Start
IESS-InvokeFunc
For future expansion (Set to 0).

For details on safety communication services, see "CC-Link IE Safety Communication Function
Specifications (Application Layer and Service Protocol) BAP-C2007ENG-002 and (Communication
Profile) BAP-C2007ENG-003".

CLPA

BAP-C2008ENG-001-K
1-215

(110) Item description of SupportSafetyInvokeFunc element
Table 5-186 Item Description Specifications of SupportSafetyInvokeFunc Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "SupportSafetyInvokeFunc".
Write "SupportSafetyInvokeFunc" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN_Safety".
Write "Support Safety Function" in the case of English CSP+ files. [Recommended
specifications]Write "DWORD".
Each bit of the DWORD value shows a target safety function. Turn ON a bit
indicating a safety function supported by the device. (For the correspondence
between bit and safety function, See Table 5-187.)
Do not write the value with a bit corresponding to an unsupported safety function
turned ON.
If not even one safety function shown in Table 5-187 is supported, write"0x00000000". If this value is omitted,"Station unique setting information check code
verification" (0x00000002) is regarded to be ON.
To show that there is a need to support multiple safety function, write the value withmultiple bits turned ON.
This can be used when the IESS-InvokeFunc service of the
SupportSafetyCommService element is ON. (For details on bits of IESS-InvokeFunc,
see Table 5-185.)(a) Item description example of SupportSafetyInvokeFunc element<p:commIfInfoMember label="SupportSafetyInvokeFunc"><p:label2><p:item>SupportSafetyInvokeFunc</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN_Safety</p:item></p:category><p:name><p:item>Support Safety Function</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000002</p:item></p:data></p:commIfInfoMember>Table 5-187 Safety Function Shown by Each Bit
Bit Position0
1
2
3 to 31

Safety Function
Station unique ID information verification
Station unique setting information checkcode verification
Station unique setting information writing
For future expansion (Set to 0).

For details on safety functions, see "CC-Link IE Safety Communication Function Specifications(Application Layer and Service Protocol) BAP-C2007ENG-002 and (Communication Profile) BAPC2007ENG-003".

CLPA

BAP-C2008ENG-001-K
1-216

(111) Item description of S_Safe_DefaultSize element
Table 5-188 Item Description Specifications of S_Safe_DefaultSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_Safe_DefaultSize".
Write "S_Safe_DefaultSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN_Safety".
Write "Safety Send Bit Data Default Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the default size of the safety send bit data in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".

(a) Item description example of S_Safe_DefaultSize element<p:commIfInfoMember label="S_Safe_DefaultSize"><p:label2><p:item>S_Safe_DefaultSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN_Safety</p:item></p:category><p:name><p:item>Safety Send Bit Data Default Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>32</p:item></p:data></p:commIfInfoMember>(112) Item description of S_Safe_MaxSize element
Table 5-189 Item Description Specifications of S_Safe_MaxSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_Safe_MaxSize".
Write "S_Safe_MaxSize" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN_Safety".
Write "Safety Send Bit Data Maximum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the maximum size of the safety send bit data in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".

(a) Item description example of S_Safe_MaxSize element<p:commIfInfoMember label="S_Safe_MaxSize"><p:label2><p:item>S_Safe_MaxSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN_Safety</p:item></p:category><p:name><p:item>Safety Send Bit Data Maximum Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>256</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-217

(113) Item description of S_Safe_MinSize element
Table 5-190 Item Description Specifications of S_Safe_MinSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_Safe_MinSize".
Write "S_Safe_MinSize" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN_Safety".
Write "Safety Send Bit Data Minimum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the minimum size of the safety send bit data in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".

(a) Item description example of S_Safe_MinSize element<p:commIfInfoMember label="S_Safe_MinSize"><p:label2><p:item>S_Safe_MinSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN_Safety</p:item></p:category><p:name><p:item>Safety Send Bit Data Minimum Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>2</p:item></p:data></p:commIfInfoMember>(114) Item description of S_Safe_Address element
Table 5-191 Item Description Specifications of S_Safe_Address Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_Safe_Address".
Write "S_Safe_Address" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN_Safety".
Write "Safety Send Bit Data Address" in the case of English CSP+ files.
[Recommended specifications]Write "DWORD".
Write the start address of the data to be stored in the sub payload for safety senddata communication.

(a) Item description example of S_Safe_Address element<p:commIfInfoMember label="S_Safe_Address"><p:label2><p:item>S_Safe_Address</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN_Safety</p:item></p:category><p:name><p:item>Safety Send Bit Data Address</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00000123</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-218

(115) Item description of R_Safe_DefaultSize element
Table 5-192 Item Description Specifications of R_Safe_DefaultSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "R_Safe_DefaultSize".
Write "R_Safe_DefaultSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_CC-Link_IE_TSN_Safety".
Write "Safety Receive Bit Data Default Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the default size of the safety receive bit data in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".

(a) Item description example of R_Safe_DefaultSize element<p:commIfInfoMember label="R_Safe_DefaultSize"><p:label2><p:item>R_Safe_DefaultSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN_Safety</p:item></p:category><p:name><p:item>Safety Receive Bit Data Default Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>16</p:item></p:data></p:commIfInfoMember>(116) Item description of R_Safe_MaxSize element
Table 5-193 Item Description Specifications of R_Safe_MaxSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "R_Safe_MaxSize".
Write "R_Safe_MaxSize" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN_Safety".
Write "Safety Receive Bit Data Maximum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the maximum size of the safety receive bit data in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".

(a) Item description example of R_Safe_MaxSize element<p:commIfInfoMember label="R_Safe_MaxSize"><p:label2><p:item>R_Safe_MaxSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN_Safety</p:item></p:category><p:name><p:item>Safety Receive Bit Data Maximum Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>512</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-219

(117) Item description of R_Safe_MinSize element
Table 5-194 Item Description Specifications of R_Safe_MinSize Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "R_Safe_MinSize".
Write "R_Safe_MinSize" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN_Safety".
Write "Safety Receive Bit Data Minimum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT32".
Write the minimum size of the safety receive bit data in the number of bits.
Write a numerical value equal to or larger than 0.
The value must be within the range "minimum ≤ default ≤ maximum".

(a) Item description example of R_Safe_MinSize element<p:commIfInfoMember label="R_Safe_MinSize"><p:label2><p:item>R_Safe_MinSize</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN_Safety</p:item></p:category><p:name><p:item>Safety Receive Bit Data Minimum Size</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:commIfInfoMember>(118) Item description of R_Safe_Address element
Table 5-195 Item Description Specifications of R_Safe_Address Element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "R_Safe_Address".
Write "R_Safe_Address" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_CC-Link_IE_TSN_Safety".
Write "Safety Receive Bit Data Address" in the case of English CSP+ files.
[Recommended specifications]Write "DWORD".
Write the start address of the sub payload for safety receive data communication.

(a) Item description example of R_Safe_Address element<p:commIfInfoMember label="R_Safe_Address"><p:label2><p:item>R_Safe_Address</p:item></p:label2><p:category><p:item>COMMON_CC-Link_IE_TSN_Safety</p:item></p:category><p:name><p:item>Safety Receive Bit Data Address</p:item></p:name><p:datatype><p:item>DOWRD</p:item></p:datatype><p:data><p:item>0x00000789</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-220

5.3.2

COMM_IF_INPUT part5.3.2.1 Overview
A COMM_IF_INPUT part describes information related to the input information of the communicationinterface.
Describe a COMM_IF_INPUT part when there is information to be outputted from the control side of
the target module. The part applies to the remote input RX area of the remote I/O module, the A/D
conversion completed flag of the digital analog converter, the digital output value of the analog digitalconverter, etc.
The elements that make up the COMM_IF_INPUT part are defined in accordance with the target
module.
The configuration of each element of the COMM_IF_INPUT part, that is, the items that should be
described within each element, is the same. Figure 5-16 shows the configuration of an element of the
COMM_IF_INPUT part.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
DATATYPE item
DEFAULT item
RANGE item
MIN_INC item
ENG_UNIT itemACCESS item
ASSIGN itemUI_ATTRIBUTE item
REF item
COMMENT item

Figure 5-16 Structure Definition of Element of COMM_IF_INPUT and COMM_IF_OUTPUT Part
A single element is described as a single XML element.

CLPA

BAP-C2008ENG-001-K
1-221

Table 5-196 shows the items included in an element of the COMM_IF_INPUT part.
Table 5-196 List of Elements Defined in COMM_IF_Input Part and COMM_IF_OUTPUT Part
Element Name

1.

LABEL

Describes the label for identifying the element

2.

LABEL2

Describes the label for identifying the element(Used when the utility software supports anotherlanguage.)

See Section
4.3.1.20

Optional

3.

CATEGORY

Describes the category for grouping the element

See Section
4.3.1.4

Optional

4.

NAME

Describes the name of the element
Used when the name and contents of the element
are displayed with the utility software.

See Section
4.3.1.24

Optional

5.

DATATYPE

Describes the data type of the element

6.

DEFAULT

Describes the default value set in the element

7.

RANGE

Describes the setting range of the element

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

CLPA

Description Details

Description
RequiredSpecifications /Optional
See Section
Required
4.3.1.19

No.

Describes the minimum increment applied to thevalue of the element
Describes the engineering unit applied to the value ofthe element
Describes the access attribute of the element
Describes the remote input/output and remoteregister assigned to the value of the element
Describes the display method when the element isdisplayed in the utility software
Describes a reference to the BLOCK_OUTPUT partfor a COMM_IF_INPUT part
Describes a reference to the BLOCK_INPUT part for
a COMM_IF_OUTPUT part
Describes the meaning of the element as well asusage precautions.

See Section
4.3.1.10
See Section
4.3.1.11
See Section
4.3.1.26
See Section
4.3.1.23
See Section
4.3.1.13
See Section
4.3.1.1
See Section
4.3.1.3
See Section
4.3.1.43

Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional

See Section
4.3.1.30

Optional

See Section
4.3.1.6

Optional

BAP-C2008ENG-001-K
1-222

5.3.2.2 XML format of COMM_IF_INPUT partIn XML format, the COMM_IF_INPUT part is described as an XML element having the XML element
name "commIfInput". Table 5-197 shows a list of the attributes of the commIfInput element, and Table
5-198 shows a list of the XML child elements.
Table 5-197 Attribute List for commIfInput Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the COMM_IF_INPUT
part. (See Section 4.3.1.19.) (Example: "CommIfInput")

Required/Optional
Required

Table 5-198 XML Child Element List for commIfInput Element
No.

XML Element Name1.

comment2.

commIfInputMember

Description Details
Describes the comment related to the COMM_IF_INPUT
part(See Section 4.3.1.6.)
Describes the contents of the elements of the
COMM_IF_INPUT part

Required/Optional
Optional
RequiredIn XML format, the element of the COMM_IF_INPUT part is described as an XML element having the
XML element name "commIfInputMember".
Table 5-199 shows a list of attributes of the commIfInputMember element, and Table 5-200 shows alist of XML child elements.
Table 5-199 Attribute List for commIfInputMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-200 XML Child Element List of commIfInputMember Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.

CLPA

XML Element Namelabel2
category
namedatatypedefault
range
minIncengUnit
accessassignuiAttributerefcomment

Description Details
Describes the LABEL2 item.
Describes the CATEGORY item.
Describes the NAME item.
Describes the DATATYPE item.
Describes the DEFAULT item.
Describes the RANGE item.
Describes the MIN_INC item.
Describes the ENG_UNIT item.
Describes the ACCESS item.
Describes the ASSIGN item.
Describes the UI_ATTRIBUTE item.
Describes the REF item.
Describes the COMMENT item.

BAP-C2008ENG-001-K
1-223

Write the COMM_IF_INPUT part using a format such as shown below.
<p:commIfInput label=”Write in accordance with the description details of Table 5-197‘Attribute Name label’”><p:comment>”Write in accordance with the description details of Table 5-198 ‘XML
Element Name comment’”</p:comment><p:commIfInputMember label=”Write in accordance with the description details of Table
5-199 ‘Attribute Name label’”><p:label2>”Write in accordance with the description details of Table 5-200 ‘XML
Element Name label2’”</p:label2><p:category>”Write in accordance with the description details of Table 5-200 ‘XML
Element Name categor’y”</p:category><p:name>”Write in accordance with the description details of Table 5-200 ‘XML
Element Name name’”</p:name><p:datatype>”Write in accordance with the description details of Table 5-200 ‘XML
Element Name datatype’”</p:datatype><p:default>”Write in accordance with the description details of Table 5-200‘XML
Element Name default’”</p:default><p:range>”Write in accordance with the description details of Table 5-200 ‘XML
Element Name range’”</p:range><p:minInc>”Write in accordance with the description details of Table 5-200 ‘XML
Element Name minInc”</p:minInc><p:engUnit>”Write in accordance with the description details of Table 5-200 ‘XML
Element Name engUnit’”</p:engUnit><p:access>”Write in accordance with the description details of Table 5-200 ‘XML
Element Name access’”</p:access><p:assign>”Write in accordance with the description details of Table 5-200 ‘XML
Element Name assign’”</p:assign><p:uiAttribute>”Write in accordance with the description details of Table 5-200‘XML Element Name uiAttribute’”</p:uiAttribute><p:ref>”Write in accordance with the description details of Table 5-200 ‘XML
Element Name ref’”</p:ref><p:comment>”Write in accordance with the description details of Table 5-200 ‘XML
Element Name comment’”</p:comment></p:commIfInputMember><p:commIfInputMember label=”Write in accordance with the description details of Table
5-199 ‘Attribute Name label’”>::</p:commIfInputMember>::</p:commIfInput>

CLPA

BAP-C2008ENG-001-K
1-224

5.3.2.3 Description example of each element
The following shows item description examples of the elements of the COMM_IF_INPUT part. In theexamples, the element name is set to "CH1_digital_output_val".
Table 5-201 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESSASSIGNUI_ATTRIBUTE
REF
COMMENT

Description Details
Write "CH1_digital_output_val"
Write "CH1_digital_output_val"
Omittable item. Not written.
Write "CH1 Digital Output Value"
Write "INT16"
In this case, the value of the reference of the REF item is used. Not written.
In this case, the value of the reference of the REF item is used. Not written.
In this case, the value of the reference of the REF item is used. Not written.
In this case, the value of the reference of the REF item is used. Not written.
Write "RF"Write "RWr0"
Omittable item. Not written.
Write "BlockSection.BlockOutput.CH1_digital_output_val".
Omittable item. Not written.

(a) Item description example of element<p:commIfInputMember label="CH1_digital_output_val"><p:label2><p:item>CH1_digital_output_val</p:item></p:label2><p:name><p:item>CH1 Digital Output Value</p:item></p:name><p:datatype><p:item>INT16</p:item></p: datatype ><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RWr0</p:item></p:assign><p:ref><p:item>BlockSection.BlockOutput.CH1_digital_output_val</p:item></p:ref></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-225

5.3.3

COMM_IF_OUTPUT part5.3.3.1 Overview
The COMM_IF_OUTPUT part describes information related to the output information of thecommunication interface. This part is described when there is information to be inputted to the control
side of the target module. The part pertains to the remote output RY area of the remote I/O module,
and the digital input value of the digital/analog converter, for example.
The configuration of each element of the COMM_IF_OUTPUT part, that is, the items that should be
described within each element, is the same as that of the COMM_IF_INPUT part (see Figure 5-16). A
single element is described as a single XML element.
For items included in the elements of the COMM_IF_OUTPUT part, see Table 5-196.

5.3.3.2 XML format of COMM_IF_OUTPUT partIn XML format, the COMM_IF_OUTPUT part is described as an XML element having the XML element
name "commIfOutput". Table 5-202 shows a list of the attributes of the commIfOutput element, andTable 5-203 shows a list of the XML child elements.
Table 5-202 Attribute List for commIfOutput Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the
COMM_IF_OUTPUT part. (See Section 4.3.1.19.)(Example: "commIfOutput")

Required/Optional
Required

Table 5-203 XML Child Element List for commIfOutput Element
No.

XML Element Name1.

comment2.

commIfOutputMember

Description Details
Describes the comment related to the
COMM_IF_OUTPUT part. (See Section 4.3.1.6.)
Describes the contents of the elements of the
COMM_IF_OUTPUT part.

Required/Optional
Optional
RequiredIn XML format, the element of the COMM_IF_OUTPUT part is described as an XML element having
the XML element name "commIfOutputMember".
Table 5-204 shows a list of attributes of the commIfOutputMember element, and Table 5-205shows alist of XML child elements.
Table 5-204 Attribute List for commIfOutputMember Element
No.
1.

Attribute Name
Label

Description Details
Describes the label for identifying the element.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-205 XML Child Element List of commIfOutputMember Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.

XML Element Namelabel2
category
namedatatypedefault
range
minIncengUnit
accessassignuiAttributerefcomment

Description Details
Describes the LABEL2 item
Describes the CATEGORY item
Describes the NAME item
Describes the DATATYPE item
Describes the DEFAULT item
Describes the RANGE item
Describes the MIN_INC item
Describes the ENG_UNIT item
Describes the ACCESS item
Describes the ASSIGN item
Describes the UI_ATTRIBUTE item
Describes the REF item
Describes the COMMENT item

Write the COMM_IF_OUTPUT part using a format such as shown below.
CLPA

BAP-C2008ENG-001-K
1-226

<p:commIfOutput label=“Write in accordance with the description details of Table 5-202‘Attribute Name label’”><p:comment>“Write in accordance with the description details of Table 5-203 ‘XML
Element Name comment’”</p:comment><p:commIfOutputMember label=“Write in accordance with the description details of Table
5-204 ‘Attribute Name label’”><p:label2>“Write in accordance with the description details of Table 5-205 ‘XML
Element Name label2’”</p:label2><p:category>“Write in accordance with the description details of Table 5-205 ‘XML
Element Name category’”</p:category><p:name>“Write in accordance with the description details of Table 5-205 ‘XML
Element Name name’”</p:name><p:datatype>“Write in accordance with the description details of Table 5-205 ‘XML
Element Name datatype’”</p:datatype><p:default>“Write in accordance with the description details of Table 5-205 ‘XML
Element Name default’”</p:default><p:range>“Write in accordance with the description details of Table 5-205 ‘XML
Element Name range’”</p:range><p:minInc>“Write in accordance with the description details of Table 5-205 ‘XML
Element Name minInc’”</p:minInc><p:engUnit>“Write in accordance with the description details of Table 5-205 ‘XML
Element Name engUnit’”</p:engUnit><p:access>“Write in accordance with the description details of Table 5-205 ‘XML
Element Name access’”</p:access><p:assign>“Write in accordance with the description details of Table 5-205 ‘XML
Element Name assign’”</p:assign><p:uiAttribute>“Write in accordance with the description details of Table 5-205‘XML Element Name uiAttribute’”</p:uiAttribute><p:ref>“Write in accordance with the description details of Table 5-205 ‘XML
Element Name ref’”</p:ref><p:comment>“Write in accordance with the description details of Table 5-205 ‘XML
Element Name comment’”</p:comment></p:commIfOutputMember><p:commIfOutputMember label=“Write in accordance with the description details of Table
5-204 ‘Attribute Name label’”>::</p:commIfOutputMember>::</p:commIfOutput>

CLPA

BAP-C2008ENG-001-K
1-227

5.3.3.3 Description example of each element
The following shows item description examples of the elements of the COMM_IF_OUTPUT part. In theexamples, the element name is set to "CH1_ave_time_number_of_times".
Table 5-206 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESSASSIGNUI_ATTRIBUTE
REF
COMMENT

Description Details
Write "CH1_ave_time_number_of_times"
Write "CH1_ave_time_number_of_times"
Omittable item. Not written.
Write "CH1 Average Time Number"
Write "INT16"
In this case, the value of the reference of the REF item is used
In this case, the value of the reference of the REF item is used
In this case, the value of the reference of the REF item is used
In this case, the value of the reference of the REF item is used
Write "RF"Write "RWw1"
Omittable item. Not written.
Write "BlockSection.BlockInput.CH1_ave_time_number_of_times".
Omittable item. Not written.

(a) Item description example of element<p:commIfOutputMember label="CH1_ave_time_number_of_times"><p:label2><p:item>CH1_ave_time_number_of_times</p:item></p:label2><p:name><p:item>CH1 Average Time Number</p:item></p:name><p:datatype><p:item>INT16</p:item></p: datatype ><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RWw1</p:item></p:assign><p:ref><p:item>BlockSection.BlockInput.CH1_ave_time_number_of_times</p:item></p:ref></p:commIfOutputMember>

CLPA

BAP-C2008ENG-001-K
1-228

5.3.4

COMM_IF_PARAMETER part

5.3.4.1 Overview
The COMM_IF_PARAMETER part describes information related to the parameters of the target
module.
This part pertains to the voltage/current specification of the analog-digital converter and the CH1
average processing specification, for example. Note that information that cannot be set or used as
reference via the communication interface, such as values set using the DIP switch, cannot be written.
The elements that make up the COMM_IF_PARAMETER part are defined in accordance with thecommunication function of the target module.
The configuration of each element of the COMM_IF_PARAMETER part, that is, the items that should
be described within each element, is the same. Figure 5-17 shows the configuration of an element of
the COMM_IF_PARAMETER part.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
DATATYPE item
DEFAULT item
RANGE item
MIN_INC item
ENG_UNIT itemACCESS item
WRITE_ORDER item
ASSIGN itemUI_ATTRIBUTE item
REF item
COMMENT item
Figure 5-17 Structure Definition for Element of COMM_IF_PARAMETER Part
A single element is described as a single XML element. For element description examples, see
Section 5.3.4.3.

CLPA

BAP-C2008ENG-001-K
1-229

The items included in the element are described in Table 5-207.
Table 5-207 Item List for Elements Defined in COMM_IF_PARAMETER Part
No.

Item Name

Description Details

Description
Specifications
See Section
4.3.1.19

Required/Optional

1.

LABEL

Describes the label for identifying the element.

2.

LABEL2

Describes the label for identifying the element.
(Used when the utility software supports anotherlanguage.)

See Section
4.3.1.20

Optional

3.

CATEGORY

Describes the category for grouping the element.

See Section
4.3.1.4

Optional

4.

NAME

Describes the name of the element.
Used when the name and contents of the element
are displayed with the utility software.

See Section
4.3.1.24

Optional

5.

DATATYPE

Describes the data type of the element.

6.

DEFAULT

Describes the default value set in the element.

7.

RANGE

Describes the setting range of the element.

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.
12.
13.
14.
15.

CLPA

Describes the minimum increment applied to thevalue of the element and the ENG_UNIT item.
Describes the engineering unit applied to the valueof the element and the MIN_INC item.
Describes the access attribute of the element.

See Section
4.3.1.10
See Section
4.3.1.11
See Section
4.3.1.26
See Section
4.3.1.23
See Section
4.3.1.13
See Section
4.3.1.1
See Section
4.3.1.46
See Section
4.3.1.3
See Section
4.3.1.43

Describes the order in which elements are to be
written to the module.
Describes the address and code to be assigned to
ASSIGNthe element.
Describes the display method when the element is
UI_ATTRIBUTE
displayed in the utility software.
Describes a reference to an element of the
See Section
REF
BLOCK_PARAMETERreferred to by an element of
4.3.1.30
the communication parameter list.
Describes the meaning of the element as well as
See Section
COMMENT
usage precautions.
4.3.1.6*1: This item is required in CC-Link IE TSN and optional in other networks.
WRITE_ORDER

Required

Optional
Optional
Optional
Optional
Optional
Optional
Optional*1
Optional
Optional
Optional

BAP-C2008ENG-001-K
1-230

5.3.4.2 XML format of COMM_IF_PARAMETER partIn XML format, the COMM_IF_PARAMETER part is described as an XML element having the XML
element name "commIfParameter". Table 5-208 shows a list of the attributes of the commIfParameter
element, and Table 5-209 shows a list of the XML child elements.
Table 5-208 Attribute List for commIfParameter Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the
COMM_IF_PARAMETER part. (See Section 4.3.1.19.)

Required/Optional
Required

Table 5-209 XMLChild Element List for commIfParameterElement
No.

XML Element Name1.

comment2.

commIfParameter
MemberDescription Details
Describes the comment related to the
COMM_IF_PARAMETER part.
(See Section 4.3.1.6.)
Describes the contents of the elements of the
COMM_IF_PARAMETER part.

Required/Optional
Optional
RequiredIn XML format, the element of the COMM_IF_PARAMETER part is described as an XML element
having the XML element name "commIfParameterMember".
Table 5-210 shows a list of attributes of the commIfParameterMember element, and Table 5-211
shows a list of XML child elements.
Table 5-210 Attribute List for commIfParameterMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-211 XML Child Element List of commIfParameterMember Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.

CLPA

XML Element Namelabel2
category
namedatatypedefault
range
minIncengUnit
accesswriteOrderassignuiAttributerefcomment

Description Details
Describes the LABEL2 item
Describes the CATEGORY item
Describes the NAME item
Describes the DATATYPE item
Describes the DEFAULT item
Describes the RANGE item
Describes the MIN_INC item
Describes the ENG_UNIT item
Describes the ACCESS item
Describes the WRITE_ORDER item
Describes the ASSIGN item
Describes the UI_ATTRIBUTE item
Describes the REF item
Describes the COMMENT item

BAP-C2008ENG-001-K
1-231

Write the COMM_IF_PARAMETER part using a format such as shown below.
<p:commIfParameter label=“Write in accordance with the description details of Table
5-208 ‘Attribute Name label’”><p:comment>“Write in accordance with the description details of Table 5-209 ‘XML
Element Name comment’”</p:comment><p:commIfParameterMember label=“Write in accordance with the description details ofTable 5-210 ‘Attribute Name label’”><p:label2>“Write in accordance with the description details of Table 5-211 ‘XML
Element Name label2’”</p:label2><p:category>“Write in accordance with the description details of Table 5-211 ‘XML
Element Name category’”</p:category><p:name>“Write in accordance with the description details of Table 5-211 ‘XML
Element Name name’”</p:name><p:datatype>“Write in accordance with the description details of Table 5-211 ‘XML
Element Name datatype’”</p:datatype><p:default>“Write in accordance with the description details of Table 5-211 ‘XML
Element Name default’”</p:default><p:range>“Write in accordance with the description details of Table 5-211 ‘XML
Element Name range’”</p:range><p:minInc>“Write in accordance with the description details of Table 5-211 ‘XML
Element Name minInc’”</p:minInc><p:engUnit>“Write in accordance with the description details of Table 5-211 ‘XML
Element Name engUnit’”</p:engUnit><p:access>“Write in accordance with the description details of Table 5-211 ‘XML
Element Name access’”</p:access><p:writeOrder>“Write in accordance with the description details of Table 5-211‘XML Element Name writeOrder”</p:writeOrder><p:assign>“Write in accordance with the description details of Table 5-211 ‘XML
Element Name assign’”</p:assign><p:uiAttribute>“Write in accordance with the description details of Table 5-211‘XML Element Name uiAttribute’”</p:uiAttribute><p:ref>“Write in accordance with the description details of Table 5-211 ‘XML
Element Name ref’”</p:ref><p:comment>“Write in accordance with the description details of Table 5-211 ‘XML
Element Name comment’”</p:comment></p:commIfParameterMember><p:commIfParameterMember label="Write in accordance with the description details ofTable 5-208 ‘Attribute Name label’”>::</p:commIfParameterMember>::</p:commIfParameter>

CLPA

BAP-C2008ENG-001-K
1-232

5.3.4.3 Description example of element
The following shows item description examples of the elements of the COMM_IF_PARAMETER part.
In the examples, the element name is set to "Parameter1".
Table 5-212 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS
WRITE_ORDER

12.

ASSIGN

13.
14.
15.

UI_ATTRIBUTE
REF
COMMENT

Description Details
Write "Parameter1"
Write "Parameter1"
Omittable item. Not written.
Write "Parameter 1"
In this case, the value of the reference of the REF item is used. Not written.
In this case, the value of the reference of the REF item is used. Not written.
In this case, the value of the reference of the REF item is used. Not written.
In this case, the value of the reference of the REF item is used. Not written.
In this case, the value of the reference of the REF item is used. Not written.
In this case, the value of the reference of the REF item is used. Not written.
In this case, the value of the reference of the REF item is used. Not written.
Write "<0x5E><0xDE><0x01>"(with XML file: "&lt;0x5E&gt;&lt;0xDE&gt;&lt;0x01&gt;").
Omittable item. Not written.
Write "BlockSec.BlockParameter.Parameter1"
Omittable item. Not written.

(a) Item description example of element<p:commIfParameterMember label="Parameter1"><p:label2><p:item>Parameter1</p:item></p:label2><p:name><p:item>Parameter 1</p:item></p:name><p:assign><p:item>&lt;0x5E&gt;&lt;0xDE&gt;&lt;0x1&gt;</p:item></p:assign><p:ref><p:item>BlockSec.BlockParameter.Parameter1</p:item></p:ref></p:commIfParameterMember>

CLPA

BAP-C2008ENG-001-K
1-233

5.3.5

COMM_IF_COMMAND part5.3.5.1 Overview
The COMM_IF_COMMAND part describes information related to the commands issued by thecommunication interface. This part pertains to the CH1 conversion enable/disable specification of theanalog-digital converter, for example.
The elements that make up the COMM_IF_COMMAND part are defined in accordance with thecommunication function of the target module.
The configuration of each element of the COMM_IF_COMMAND part, that is, the items that should be
described within each element, is the same. Figure 5-18 shows the configuration of an element of the
COMM_IF_COMMAND part.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
ARGUMENT item
REF item
COMMENT item

Figure 5-18 Structure Definition for Element of COMM_IF_COMMAND Part
A single element is described as a single XML element. For description examples of each element,
see Section 5.3.5.3.
The items included in the element are described in Table 5-213.
Table 5-213 Item List for Elements Defined in COMM_IF_COMMAND Part
No.

Item Name

Description Details

1.

LABEL

Describes the label for identifying the element.

2.

LABEL2

Describes the label for identifying the element. (Usedwhen the utility software supports another language.)

3.

CATEGORY

Describes the category for grouping the element.

4.

NAME

5.

ARGUMENT

6.

REF

7.

COMMENT

CLPA

Describes the name of the item. Used when thename and contents are displayed with the utility
software.
Describes the label corresponding to the
COMMAND_ARGUMENT part for indicatingarguments used by the element.
Describes the reference to the BLOCK_COMMAND
part from the element.
Describes the meaning of the element as well asusage precautions.

Description
RequiredSpecifications /Optional
See Section
Required
4.3.1.19
See Section
Optional
4.3.1.20
See Section
Optional
4.3.1.4
See Section
4.3.1.24

Optional

See Section
4.3.1.2

Optional

See Section
4.3.1.30
See Section
4.3.1.6

Optional
Optional

BAP-C2008ENG-001-K
1-234

5.3.5.2 XML format of COMM_IF_COMMAND partIn XML format, the COMM_IF_COMMAND part is described as an XML element having the XML
element name "commIfCommand". Table 5-214 shows a list of the attributes of the commIfCommand
element, and Table 5-215 shows a list of the XML child elements.
Table 5-214 Attribute List for commIfCommand Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the
COMM_IF_COMMAND part.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-215 XML Child Element List for commIfCommandElement
No.

XML Element Name1.

comment2.

commIfCommand
MemberDescription Details
Describes the comment related to the
COMM_IF_COMMAND part.
(See Section 4.3.1.6.)
Describes the contents of the elements of the
COMM_IF_COMMAND part.

Required/Optional
Optional
RequiredIn XML format, the element of the COMM_IF_COMMAND part is described as an XML element having
the XML element name "commIfCommandMember". Table 5-216 shows a list of attributes of thecommIfCommandMember element, and Table 5-217 shows a list of XML child elements.
Table 5-216 Attribute List for commIfPCommandMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element. (See
Section 4.3.1.19.)

Required/Optional
Required

Table 5-217 XML Child Element List of commIfCommandMember Element
No.
1.
2.
3.
4.
5.
6.

CLPA

XML Element Namelabel2
category
nameargument
refcomment

Description Details
Describes the LABEL2 item
Describes the CATEGORY item
Describes the NAME item
Describes the ARGUMENT item
Describes the REF item
Describes the COMMENT item

BAP-C2008ENG-001-K
1-235

Write the COMM_IF_COMMAND part using a format such as shown below.
<p:commIfCommand label=“Write in accordance with the description details of Table 5-214‘Attribute Name label’”><p:comment>“Write in accordance with the description details of Table 5-215 ‘XML
Element Name comment’”</p:comment><p:commIfCommandMember label=“Write in accordance with the description details ofTable 5-216 ‘Attribute Name label’”><p:label2>“Write in accordance with the description details of Table 5-217‘XML
Element Name label2’”</p:label2><p:category>“Write in accordance with the description details of Table 5-217 ‘XML
Element Name category’”</p:category><p:name>“Write in accordance with the description details of Table 5-217 ‘XML
Element Name name’”</p:name><p:argument>“Write in accordance with the description details of Table 5-217 ‘XML
Element Name argument”</p:argument><p:ref>“Write in accordance with the description details of Table 5-217 ‘XML
Element Name ref’”</p:ref><p:comment>“Write in accordance with the description details of Table 5-217 ‘XML
Element Name comment’”</p:comment></p:commIfCommandMember><p:commIfCommandMember label=“Write in accordance with the description details ofTable 5-216 ‘Attribute Name label’”>::</p:commIfCommandMember>::</p:commIfCommand>

CLPA

BAP-C2008ENG-001-K
1-236

5.3.5.3 Description example of element
The following shows an item description example of the elements of the COMM_IF_COMMAND part.
In the example, the element name is set to "CmdGetFaultRecord".
Table 5-218 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.
7.

Item NameLABELLABEL2
CATEGORYNAME
ARGUMENTREF
COMMENT

Description Details
Write "CmdGetFaultRecord"
Write "CmdGetFaultRecord"
Omittable item. Not written.
Write "Fault Record Acquisition"
In this case, the value of the reference of the REF item is used
Write "BlockSection.BlockCommand.CmdGetFaultRecord"
Omittable item. Not written.

(a) Item description example of element<p:commIfCommandMember label="CmdGetFaultRecord"><p:label2><p:item>CmdGetFaultRecord</p:item></p:label2><p:name><p:item>Fault Record Acquisition</p:item></p:name><p:ref><p:item>BlockSection.BlockCommand.CmdGetFaultRecord</p:item></p:ref></p:commIfCommandMember>

CLPA

BAP-C2008ENG-001-K
1-237

5.3.6METHOD part5.3.6.1 Overview
The METHOD part provides information related to the communication service.
This part describes the procedures of the I/O read service for the remote input RX and remote register
RWr areas, the I/O write service for the remote output RY and remote register RWw areas, theparameter write service for the parameter area, the parameter read service, and the commandexecution service.
The configuration of each element of the METHOD part, that is, the items that should be describedwithin each element, is the same. Figure 5-19 shows the configuration of an element of the METHOD
part.
Elements
LABEL item

READ_DATA item

LABEL2 item

READ_DATATYPE item

CATEGORY item

INTERLOCK item

NAME item

REQ_FLAG item

TARGET item

END_CONDITION item

METHOD_TYPE item

ERR_CONDITION item

WRITE_REGISTER item

ERR_REGISTER item

WRITE_DATA item

ERR_CODE_RANGE item

WRITE_DATATYPE item

RELATED_METHOD item

READ_REGISTER item

COMMENT item

Figure 5-19 Structure Definition for Element of METHOD Part

CLPA

BAP-C2008ENG-001-K
1-238

A single element is described as a single XML element. For details of element description
specifications, see Section 5.3.6.4.
The items included in the element are described in Table 5-219.
Table 5-219 Item List for Elements Defined in METHOD Part
No.

Item Name

Description Details

1. LABEL

Describes the label for identifying the element.

2. LABEL2

Describes the label for identifying the element. (Usedwhen the utility software supports another language.)

3. CATEGORY

Describes the category for grouping the element.

4. NAME
5. TARGET
6. METHOD_TYPE
7. WRITE_REGISTER
8. WRITE_DATA

9. WRITE_DATATYPE
10. READ_REGISTER

11. READ_DATA

12. READ_DATATYPE
13. INTERLOCK
14. REQ_FLAG
15. END_CONDITION
16. ERR_CONDITION
17. ERR_REGISTER18.

ERR_CODE_RANG
E

19. RELATED_METHOD
20. COMMENT

CLPA

Describes the name of the element.
Used when the name and contents are displayed withthe utility software.
Describes the element to be processed by the
METHOD part based on the same description
specifications as the REF item (see Section 4.3.1.30).
Describes the type of the METHOD part.
Describes the remote output and remote register for
writing.
Describes the write value.
Describes the same number of write values as in the
WRITE_REGISTER item above when specified in
multiple in the WRITE_REGISTER item.
Describes the remote output and remote register data
type for writing. Describes the same number of datatypes as in the WRITE_REGISTER item above when
specified in multiple in the WRITE_REGISTER item.
Describes the remote input and remote register forreading.
Describes the reference to the storage destination of
the read value. Describes the same number of readvalue storage destinations as in the
READ_REGISTER item when specified in multiple in
the READ_REGISTER item.
Describes the remote input and remote register data
type for reading. Describes the same number of datatypes as in the READ_REGISTER item when specified
in multiple in the READ_REGISTER item.
Describes the interlock remote input/output, remoteregister, and on/off status or value.
Describes the request flag for handshake
implementation using an assignment expression.
Describes the normal completion conditions forhandshake implementation.
Describes the abnormal completion conditions forhandshake implementation.
Describes the remote register that stores values whenan error occurs.
Describes the error code range.
Describes the reference to the METHOD part thatindicates the pre-processing of the METHOD part.
Describes the meaning of the element as well asusage precautions.

Description Required
Specifications /Optional
See Section
Required
4.3.1.19
See Section
Optional
4.3.1.20
See Section
Optional
4.3.1.4
See Section
Required
4.3.1.24
See Section
Required
4.3.1.42
See Section
Required
4.3.1.22
See Section
Optional
4.3.1.47
See Section
4.3.1.44

Optional

See Section
4.3.1.45

Optional

See Section
4.3.1.29

Optional

See Section
4.3.1.27

Optional

See Section
4.3.1.28

Optional

See Section
4.3.1.18
See Section
4.3.1.34
See Section
4.3.1.12
See Section
4.3.1.14
See Section
4.3.1.16
See Section
4.3.1.15
See Section
4.3.1.33
See Section
4.3.1.6

Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional

BAP-C2008ENG-001-K
1-239

5.3.6.2 XML description of METHOD partIn XML format, the METHOD part is described as an XML element having the XML element name"method". Table 5-220 shows a list of the attributes of the method element, and Table 5-221 shows alist of the XML child elements.
Table 5-220 Attribute List for method Element
No.
1.

Attribute Name

Description Details
Describes the label for identifying the METHOD part.
(See Section 4.3.1.19.)

label

Required/Optional
Required

Table 5-221 XML Child Element List for methodElement
No.

XML Element Name1.

comment2.

methodMember

Description Details
Describes the comment related to the METHOD part.
(See Section 4.3.1.6.)
Describes the contents of the elements of the METHOD
part.

Required/Optional
Optional
RequiredIn XML format, the element of the METHOD part is described as an XML element having the XML
element name "methodMember". Table 5-222 shows a list of attributes of the methodMember element,
and Table 5-223 shows a list of XML child elements.
Table 5-222 Attribute List for methodMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.
(See Section 4.3.1.17.)

Required/Optional
Required

Table 5-223 XML Child Element List of methodMember Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.

CLPA

XML Element Namelabel2
category
nametargetmethodType
writeRegister
writeData
writeDatatype
readRegister
readData
readDatatypeinterlock
reqFlag
endCondition
errCondition
errRegister
errCodeRange
relatedMethod
comment

Description Details
Describes the LABEL2 item
Describes the CATEGORY item
Describes the NAME item
Describes the item
Describes the METHOD_TYPE item
Describes the WRITE_REGISTER item
Describes the WRITE_DATA item
Describes the WRITE_DATATYPE item
Describes the READ_REGISTER item
Describes the READ_DATA item
Describes the READ_DATATYPE item
Describes the INTERLOCK item
Describes the REQ_FLAG item
Describes the END_CONDITION item
Describes the ERR_CONDITION item
Describes the ERR_REGISTER item
Describes the ERR_CODE_RANGE item
Describes the RELATED_METHOD item
Describes the COMMENT item

Required/Optional
Optional
Optional
Required
Required
Required
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional

BAP-C2008ENG-001-K
1-240

Write the METHOD part using a format such as shown below.
<p:method label=“Write in accordance with the description details of Table 5-220‘Attribute Name label’”><p:comment>“Write in accordance with the description details of Table 5-221 ‘XML
Element Name comment’”</p:comment><p:methodMember label=“Write in accordance with the description details of Table 5-222‘Attribute Name label’”><p:label2>“Write in accordance with the description details of Table 5-223 ‘XML
Element Name label2’”</p:label2><p:category>“Write in accordance with the description details of Table 5-223 ‘XML
Element Name category’”</p:category><p:name>“Write in accordance with the description details of Table 5-223 ‘XML
Element Name name’”</p:name><p:target>“Write in accordance with the description details of Table 5-223 ‘XML
Element Name target’”</p:target><p:methodType>“Write in accordance with the description details of Table 5-223‘XML Element Name methodType’”</p:methodType><p:writeRegister>“Write in accordance with the description details of Table 5-223‘XML Element Name writeRegister’”</p:writeRegister><p:writeData>“Write in accordance with the description details of Table 5-223‘XML Element Name writeData’”</p:writeData><p:writeDatatype>“Write in accordance with the description details of Table 5-223‘XML Element Name writeDatatype’”</p:writeDatatype><p:readRegister>“Write in accordance with the description details of Table 5-223‘XML Element Name readRegister’”</p:readRegister><p:readData>“Write in accordance with the description details of Table 5-223 ‘XML
Element Name readData’”</p:readData><p:readDatatype>“Write in accordance with the description details of Table 5-223‘XML Element Name readDatatype’”</p:readDatatype><p:interlock>“Write in accordance with the description details of Table 5-223‘XML Element Name interlock’”</p:interlock><p:reqFlag>“Write in accordance with the description details of Table 5-223 ‘XML
Element Name reqFlag’”</p:reqFlag><p:endCondition>“Write in accordance with the description details of Table 5-223‘XML Element Name endCondition’”</p:endCondition><p:errCondition>“Write in accordance with the description details of Table 5-223‘XML Element Name errCondition’”</p:errCondition><p:errRegister>“Write in accordance with the description details of Table 5-223‘XML Element Name errRegister’”</p:errRegister><p:errCodeRange>“Write in accordance with the description details of Table 5-223‘XML Element Name errCodeRange’”</p:errCodeRange><p:relatedMethod>“Write in accordance with the description details of Table 5-223‘XML Element Name relatedMethod’”</p:relatedMethod><p:comment>“Write in accordance with the description details of Table 5-223 ‘XML
Element Name comment’”</p:comment></p:methodMember><p:methodMember label=“Write in accordance with the description details of Table 5-222‘Attribute Name label’”>::</p:methodMember>::</p:method>

CLPA

BAP-C2008ENG-001-K
1-241

5.3.6.3 METHOD operation
When a procedure-based communication service is executed by the utility software on a module, aprocedure such as described below is performed (see Figure 5-20).
(1) Verify interlock(2) Write setting value(3) Set request flag
WRITE_REGISTE
Message(4)
R

Verify completion(5) Read acquired value(6) Clear request
This procedure is developed into a model as METHOD, describing remote register and sharedmemory based procedures as well as data area information.
FA device(1) Verify interlock(2) Write setting value(3) Set request flag(4) Verify completion(5) Read acquired value(6) Clear request

Figure 5-20 Flow of Procedure-Based Communication Service

CLPA

BAP-C2008ENG-001-K
1-242

The following items are described in METHOD. For details of these items, see Table 5-219 of Section
5.3.6.1.











TARGET
WRITE_DATA
READ_DATAWRITE_REGISTER
READ_REGISTERINTERLOCKREQ_FLAG
ERR_REGISTEREND_CONDITIONERR_CONDITION

Figure 5-21 shows an operation image of a communication service based on the above items.
Utility

ModuleMETHOD
processing

Module Communication Function（COMM_IF）

2. Verify
INTERLOCK
3. Write

Write data area

COMM_IF_PARAMETER/
COMM_IF_COMMANDMETHOD

REQ_FLAG

6. Read5. Check

WIRTE_REGISTER

7. SetWRITE_DATA

4. SetrequestRead data area
1. Write
INTERLOCK

13. Verify
completion

END_CONDITION

14. Read

ERR_CONDITION

READ_DATA

15. Clear
requestMETHOD(communication
service)

8. Execute

TARGET9. Acquire

11. Write (normal)
12. Write (error)

10. Write

READ_REGISTER
ERR_REGISTER

Figure 5-21 Operation of Communication Service Described in METHOD

CLPA

BAP-C2008ENG-001-K
1-243

The following shows the METHOD call-up and operation sequence. Figure 5-22 shows a sequence
diagram of the sequence.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.

Remove INTERLOCK conditions when the communication service described in METHOD
becomes executable.
Read the data area written in INTERLOCK and assess whether or not the communication service
described in METHOD is executable.
Write the command codes and setting values described in WRITE_DATA to WRITE_REGISTER.
Set the REQ_FLAG for requesting the communication service.
Check if the REQ_FLAG is set and, if so, execute the communication service of Step 6 andbeyond.
Read the command codes and setting values from WRITE_REGISTER.
Set the setting values in TARGET in accordance with the communication service and commandcodes.
Execute the processing of TARGET in accordance with the communication service and commandcodes.
Get the acquired values of TARGET in accordance with the communication service and commandcodes.
Write the acquired values, statuses, and error codes to READ_REGISTER and ERR_REGISTER.
Set END_CONDITION when the communication service ends normally.
Set ERR_CONDITION when the communication service ends abnormally.
Monitor the END_CONDITION and ERR_CONDITION, and verify completion.
Once completion is verified, read the acquired values, statuses, and error codes of
READ_REGISTER and ERR_REGISTER.
Clear the REQ_FLAG.
Check if the REQ_FLAG has been cleared and, if so, clear END_CONDITION and
ERR_CONDITION. (Note: Omitted in Figure 5-22 due to illustration complexities.)
ModuleUtility

METHOD(communication
service)

Data area

2.

Assess INTERLOCK

3.

Write setting value

4.

Set request

1.

Remove INTERLOCK
conditions

5.

Check request setting

6.

Read setting value

10. Write acquired value

TARGET(access target)

7.

Set

8.

Execute

9.

Get

11. Write normal end
12. Write abnormal end

13. Check end
14. Read acquired value
15. Clear request

16-1. Check request
16-2 Clear end value

Figure 5-22 METHOD Sequence

CLPA

BAP-C2008ENG-001-K
1-244

5.3.6.4 Description example of element
The following shows an item description example of an element of the METHOD part. In the example
below, the element name is set to "Method1".
Table 5-224 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.

Item NameLABELLABEL2
CATEGORYNAME
TARGETMETHOD_TYPE
WRITE_REGISTERWRITE_DATAWRITE_DATATYPE
READ_REGISTER
READ_DATAREAD_DATATYPE
INTERLOCKREQ_FLAG
END_CONDITIONERR_CONDITIONERR_REGISTER
ERR_CODE_RANGE
RELATED_METHODCOMMENT

Description Details
Write "Method1"
Write "Method1"
Omittable item. Not written.
Write "Read Parameter"
Write "CommParameter"
Write "PARAMETER"
Write "RWw9"
Write "$(ASSIGN)"
Write "UINT16"
Write "RWr9"
Write "$(VALUE)"
Write "$(DATATYPE)"
Write "RX1B==ON"
Write "RY0F==ON"
Write "RX0F==ON"
Write "RX1A==ON"
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.

(a) Item description example of element<p:methodMember label="Method1"><p:label2><p:item>Method1</p:item></p:label2><p:name><p:item>Read Parameter</p:item></p:name><p:target><p:item>CommParameter.*</p:item></p:target><p:methodType><p:item>PARAMETER</p:item></p:methodType><p:writeRegister><p:item>RWw9</p:item></p:writeRegister><p:writeData><p:item>$(ASSIGN)</p:item></p:writeData><p:writeDatatype><p:item>UINT16</p:item></p:writeDatatype><p:readRegister><p:item>RWr9</p:item></p:readRegister><p:readData><p:item>$(VALUE)</p:item></p:readData><p:readDatatype><p:item>$(DATATYPE)</p:item></p:readDatatype><p:interlock><p:item>RX1B==ON</p:item></p:interlock><p:reqFlag><p:item>RY0F=ON</p:item></p:reqFlag><p:endCondition><p:item>RX0F==ON</p:item></p:endCondition><p:errCondition><p:item>RX1A==ON</p:item></p:errCondition></p:methodMember>

CLPA

BAP-C2008ENG-001-K
1-245

5.3.7MESSAGE part5.3.7.1 Overview
The MESSAGE part, similar to the METHOD part, describes information related to the commands tobe issued from the communication interface and the parameter setup procedure. The MESSAGE partdescribes the commands that use transient commands, and the data format for parameter setup.
The elements that make up the MESSAGE part are defined in accordance with the communication
function of the target module.
Figure 5-23 shows the configuration of an element of the MESSAGE part. The items described in theelement differ for each part.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
TARGET item
MESSAGE_TYPE item
REQUEST_TYPE item
REQUEST_DATA item
REQUEST_DATA_TYPE itemRESPONSE_TYPE itemRESPONSE_DATA itemRESPONSE_DATA_TYPE item
ERR_TYPE item
ERR_CODE_RANGE item
RELATED_MESSAGE item
COMMENT item
Figure 5-23 Structure Definition for Element of MESSAGE Part

CLPA

BAP-C2008ENG-001-K
1-246

A single element is described as a single XML element. For details of the description specifications ofeach element, see Section 5.3.7.4.
The following describes the procedure information required for parameter setup and commandexecution with the items of the MESSAGE part.
Table 5-225 Item List for Elements Defined in MESSAGE Part
No.

Item Name

Description Details
Describes the label for identifying the element.
Write "SLMP" as a prefix for an SLMP-based
MESSAGE.
Example: SLMPGetParam, SLMPInvReset
Describes the label for identifying the element.
(Used when the utility software supports anotherlanguage.)

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

TARGET

6.

MESSAGE_TYPE

Describes the type of the MESSAGE part.

7.

REQUEST_TYPE

Describes the data format type for executing
request processing.

8.

REQUEST_DATA

Describes the value for request processing.

Describes the category for grouping the element.
Describes the name of the element. Used when
the name and contents are displayed with theutility software.
Describes the element to be processed in the
MESSAGE part.

Describes the data type of the REQUEST_DATA
item.
Describes the type of the data format used in
10. RESPONSE_TYPE
response processing.
Describes the value to be returned by response
11. RESPONSE_DATA
processing.
Describes the data type of the
12. RESPONSE_DATA_TYPERESPONSE_DATA item.
Describes the type of the data format used in the
13. ERR_TYPE
response processing when an error occurs.
9.

REQUEST_DATA_TYPE

14. ERR_CODE_RANGE Describes the error code range.

Description
Specifications

Required/Optional

See Section
4.3.1.19

Required

See Section
4.3.1.20

Optional

See Section
4.3.1.4

Optional

See Section
4.3.1.24

Required

See Section
4.3.1.42
See Section
4.3.1.21
See Section
4.3.1.37
See Section
4.3.1.35
See Section
4.3.1.36
See Section
4.3.1.40
See Section
4.3.1.38
See Section
4.3.1.39
See Section
4.3.1.17
See Section
4.3.1.15

Required
Required
Required*1
Optional
Optional
Optional
Optional
Optional
Optional
Optional

Describes the reference to a MESSAGE partSee Section
15. RELATED_MESSAGE that indicates the pre-processing of the
Optional
4.3.1.32
MESSAGE part.
Describes the meaning of the element as well as See Section
16. COMMENT
Optional
usage precautions.
4.3.1.6*1. It may not be required for CC-Link IE TSN. For details, see REQUEST_TYPE conventions (Section
4.3.1.37).

CLPA

BAP-C2008ENG-001-K
1-247

5.3.7.2 XML description of MESSAGE partIn XML format, the MESSAGE part is described as an XML element having the XML element name"message". Table 5-226 shows a list of attributes of the message element, and Table 5-227 shows alist of XML child elements.
Table 5-226 Attribute List for message Element
No.
1.

Attribute Name

Description Details
Describes the label for identifying the MESSAGE
part.(See Section 4.3.1.19.)

label

Required/Optional
Required

Table 5-227 XML Child Element List of message Element
No.

XML Element Name1.

comment2.

messageMember

Description Details
Describes the comments related to the MESSAGE part.
(See Section 4.3.1.6.)
Describes the contents of the element of the MESSAGE
part

Required/Optional
Optional
RequiredIn XML format, the MESSAGE part is described as an XML element having the XML element name"messageMember". Table 5-228 shows a list of the attributes of the messageMember element, andTable 5-229 shows a list of the XML child elements.
Table 5-228 Attribute List for messageMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-229 XML Child Element List of messageMember Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.

CLPA

XML Element Namelabel2
category
nametargetmessageTyperequestTyperequestData
requestDatatype
responseType
responseData
responseDatatypeerrTypeerrCodeRange
relatedMessage
comment

Description Details
Describes the LABEL2 item.
Describes the CATEGORY item.
Describes the NAME item.
Describes the TARGET item.
Describes the MESSAGE_TYPE item.
Describes the REQUEST_TYPE item
Describes the REQUEST_DATA item
Describes the REQUEST_DATA_TYPE item
Describes the RESPONSE_TYPE item
Describes the RESPONSE_DATA item
Describes the RESPONSE_DATA_TYPE item
Describes the ERR_TYPE item
Describes the ERR_CODE_RANGE item
Describes the RELATED_MESSAGE item
Describes the COMMENT item

BAP-C2008ENG-001-K
1-248

Write the MESSAGE part using a format such as shown below.
<p:message label="Write in accordance with the description details of Table 5-226‘Attribute Name label’”><p:comment>"Write in accordance with the description details of Table 5-227 ‘XML
Element Name comment’”</p:comment><p:messageMember label="Write in accordance with the description details of Table
5-228 ‘Attribute Name label’”><p:label2>"Write in accordance with the description details of Table 5-229 ‘XML
Element Name label2’”</p:label2><p:category>"Write in accordance with the description details of Table 5-229 ‘XML
Element Name category’”</p:category><p:name>"Write in accordance with the description details of Table 5-229 ‘XML
Element Name name’”</p:name><p:target>"Write in accordance with the description details of Table 5-229 ‘XML
Element Name target’”</p:target><p:messageType>"Write in accordance with the description details of Table 5-229 ‘XML Element
Name messageType’”</p:messageType><p:requestType>"Write in accordance with the description details of Table 5-229 ‘XML Element
Name requestType’”</p:requestType><p:requestData>"Write in accordance with the description details of Table 5-229 ‘XML Element
Name requestData’”</p:requestData><p:requestDatatype>"Write in accordance with the description details of Table 5-229 ‘XML Element
Name requestDatatype’”</p:requestDatatype><p:responseType>"Write in accordance with the description details of Table 5-229 ‘XML Element
Name responseType’”</p:responseType><p:responseData>"Write in accordance with the description details of Table 5-229 ‘XML Element
Name responseData’”</p:responseData><p:responseDatatype>"Write in accordance with the description details of Table 5-229 ‘XML Element
Name responseDatatype’”</p:responseDatatype><p:errType>"Write in accordance with the description details of Table 5-229 ‘XML
Element Name errType’”</p:errType><p:errCodeRange>"Write in accordance with the description details of Table 5-229 ‘XML Element
Name errCodeRange’”</p:errCodeRange><p:relatedMessage>"Write in accordance with the description details of Table 5-229 ‘XML Element
Name relatedMessage’”</p:relatedMessage><p:comment>"Write in accordance with the description details of Table 5-229 ‘XML
Element Name name’”</p:comment></p:messageMember><p:messageMember label="Write in accordance with the description details of Table
5-228 ‘Attribute Name label’”>::</p:messageMember>::</p:message>

CLPA

BAP-C2008ENG-001-K
1-249

5.3.7.3 MESSAGE operation
When a communication service for which the data format is specified is executed by the utility software
on a module, the service request data format to the module (RequestFrame), service response data
format from the module at normal end (ResponseFrame), and error response data format from themodule at error occurrence (ErrorFrame) are defined and the service is executed using the format.
This format information is developed into a model as MESSAGE. The following items are described in
MESSAGE. For the details of these items, see Table 5-225 of Section 5.3.7.1.
Message








TARGET
REQUEST_TYPE
REQUEST_DATARESPONSE_TYPERESPONSE_DATAERR_TYPE

Figure 5-24 shows an operation image of a communication service based on the above items.
FA DeviceEngineering Tool
MESSAGE Procedure
Request Frame
1. Create
RequestFrame inaccordance with
REQUEST_TYPE

FA Device Communication Function (COMM_IF)
Request Frame

HeaderHeader

REQUEST_DATA1REQUEST__DATA 1

REQUEST_DATA 2REQUEST__DATA 2::

3. Interpret

MESSAGE(Communication
service)

2. Send RequestFrame
7-2 Receive ResponseFrame

4. Set
5. Execute

Response Frame
7-3 Interpret
ResponseFrame inaccordance with
Response_Type

COMM_IF_PARAMETER/
COMM_IF_COMMANDMESSAGETARGET

Response Frame
7-1 Create

HeaderHeaderRESPONSE_DATA 1RESPONSE_DATA 1RESPONSE_DATA 2RESPONSE_DATA 2::

Error Frame

Error Frame

6. Get8-2 Receive ErrorFrame
8-1 Create
8-3 Interpret ErrorFrame inaccordance with
ERR_TYPEHeaderHeaderErrorCodeErrorCode

Figure 5-24 Operation of Communication Service Described in MESSAGE

CLPA

BAP-C2008ENG-001-K
1-250

The following shows the MESSAGE call-up and operation sequence. Figure 5-25 shows a sequence
diagram of the sequence.
FA deviceEngineering tool

Request/Response
Frame(Engineering tool)

Request/ResponseFrame(FA device)

MESSAGE(Communication
service)

TARGET(Access target)

1. Create RequestFrame

2. Send RequestFrame
3. Interpret RequestFrame
4. Set
5. Execute
6. Get7. Create ResponseFrame(ErrorFrame)
8. Receive ResponseFrame(ErrorFrame)
9. Interpret ResponseFrame(ErrorFrame)

Figure 5-25 MESSAGE Call-up and Operation Sequence(1) Create a RequestFrame of the data format determined by REQUEST_TYPE, and set
REQUEST_DATA.
(2) Send the RequestFrame to the communication function of the FA device.
(3) The communication function of the FA device receives and passes the RequestFrame, reading
the command code and setting value.
(4) Set the setting value in TARGET in accordance with the communication service and commandcode.
(5) Execute the processing of TARGET in accordance with the communication service and commandcode.
(6) Get the acquired value of TARGET in accordance with the communication service and commandcode.
[A. When a normal end occurs](7) Set the acquired value in the ResponseFrame in accordance with the data format corresponding
to RESPONSE_TYPE, in accordance with the communication service and command code.
(8) Receive the ReseponseFrame from the communication function of the FA device.
(9) Interpret the ResponseFrame based on the data format determined by RESPONSE_TYPE, andread the RESPONSE_DATA.
[B. When an abnormal end occurs](7) Set the acquired value in the ErrorFrame in accordance with the data format corresponding to
ERR_TYPE, in accordance with the communication service and command code.
(8) Receive the ErrorFrame from the communication function of the FA device.
(9) Interpret the ErrorFrame based on the data format determined by ERR_TYPE, and read theErrorCode.

CLPA

BAP-C2008ENG-001-K
1-251

5.3.7.4 Description example of element
The following shows an item description example of an element of the MESSAGE part. In the example
below, the element name is set to "SLMPGetParam".
Table 5-230 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.
7.

Item NameLABELLABEL2
CATEGORYNAME
TARGETMESSAGE_TYPE
REQUEST_TYPE

8.

REQUEST_DATA

9.

REQUEST_DATATYPE

10.
11.
12.
13.
14.

RESPONSE_TYPERESPONSE_DATARESPONSE_DATATYPEERR_TYPEERR_CODERANGE

15.

RELATED_MESSAGE

16.

COMMENT

Description Details
Write "SLMPGetParam".
Write "SLMPGetParam".
Omittable item. Not written.
Write "Parameter Read".
Write "Prm.*."Write "PARAMETER".
Write "RdReqSt_Binary".
Write "<0x0401><0x0000><$(ASSIGN)><$(DATATYPE).WORDSIZE>"(with XML file:"&lt;0x0401&gt;&lt;0x0000&gt;&lt;$(ASSIGN)&gt;&lt;$(DATATYPE).WORDSIZ
E&gt;")".
Write "<WORD><WORD><DWORD><WORD>"(with XML file:"&lt;WORD&gt;&lt;WORD&gt;&lt;DWORD&gt;&lt;WORD&gt;").
Write "rdResST_Binary".
Write "$(VALUE)".
Write "$(DATATYPE)".
Write "rdErr_Binary".
Write a reference to the ENUM part "ErrorCode".
Write a reference to the element of the MESSAGE part that indicates the preprocessing of the element of the MESSAGE part.
Omittable item. Not written.
Omittable item. Not written.

(a) Item description example of element<p:messageMember label="SLMPGetParam"><p:label2><p:item>SLMPGetParam</p:item></p:label2><p:name><p:item>Parameter Read</p:item></p:name><p:target><p:item>Prm.*</p:item></p:target><p:messageType><p:item>PARAMETER</p:item></p:messageType><p:requestType><p:item>rdReqST_Binary</p:item></p:requestType><p:requestData><p:item>&lt;0x0401&gt;&lt;0x0000&gt;&lt;$(ASSIGN)&gt;&lt;$(DATATYPE).WO
RDSIZE&gt;</p:item></p:requestData><p:requestDatatype><p:item>&lt;WORD&gt;&lt;WORD&gt;&lt;DWORD&gt;&lt;WORD&gt;</p:ite
m></p:requestDatatype><p:responseType><p:item>rdResST_Binary</p:item></p:responseType><p:responseData><p:item>$(VALUE)</p:item></p:responseData><p:responseDatatype><p:item>$(DATATYPE)</p:item></p:responseDatatype><p:errType><p:item>rdErr_Binary</p:item></p:errType><p:errCodeRange><p:enumRefItem>ErrorCode</p:enumRefItem></p:errCodeRange></p:messageMember>

CLPA

BAP-C2008ENG-001-K
1-252

5.3.8STRUCT part

5.3.8.1 Overview
The STRUCT part (structure) describes information related to the structure of the inputs and outputs ofmultiple elements. A structure is used when an area is divided. Each of the elements that make up the
structure needs to be assigned a consecutive address. When an element within the COMM_IF sectionrefers to a description of a STRUCT part, the STRUCT part is described within the same COMM_IF
section.
The elements that make up the STRUCT part are defined in accordance with the structure used by thetarget module.
The configuration of each element of the STRUCT part, that is, the items that should be describedwithin an element, is the same. Figure 5-26 shows the configuration of an element of the STRUCT
part.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
DATATYPE item
DEFAULT item
RANGE item
MIN_INC item
ENG_UNIT itemOFFSET item
REF item
COMMENT item

Figure 5-26 Structure Definition for Element of STRUCT Part

CLPA

BAP-C2008ENG-001-K
1-253

A single element is described as a single XML element. For the detailed description specifications ofeach element, see Section 5.3.8.3.
Table 5-231 describes the items included in an element.
Table 5-231 Item List for Elements Defined in STRUCT Part
No.

Item Name

Description Details

1.

LABEL

Describes the label for identifying the element

2.

LABEL2

Describes the label for identifying the element. (Usedwhen the utility software supports another language.)

3.

CATEGORY

Describes the category for grouping the element

4.

NAME

Describes the name of the element

5.

DATATYPE

Describes the data type of the element

6.

DEFAULT

Describes the default value set for the element

7.

RANGE

Describes the setting range of the element

8.

MIN_INC

9.

ENG_UNIT10.

OFFSET

11.

REF

12.

COMMENT

CLPA

Describes the minimum increment applied to thevalue of the element
Describes the engineering unit applied to the value ofthe element
Describes the offset position of the element
Describes the reference to be referred to by theelement. Used to refer to the input/output of a
BLOCK section from each element of the structure
when the structure is defined in the COMM_IF
section.
* For describable references, see Section 4.3.1.30.
Describes the meaning of the element as well asusage precautions.

Description
RequiredSpecifications /Optional
See Section
Required
4.3.1.19
See Section
Optional
4.3.1.20
See Section
Optional
4.3.1.4
See Section
Optional
4.3.1.24
See Section
Optional
4.3.1.10
See Section
Optional
4.3.1.11
See Section
Optional
4.3.1.26
See Section
Optional
4.3.1.23
See Section
Optional
4.3.1.13
See Section
Required
4.3.1.25
See Section
4.3.1.30

Optional

See Section
4.3.1.6

Optional

BAP-C2008ENG-001-K
1-254

5.3.8.2 XML format of STRUCT partIn XML format, the STRUCT part is described as an XML element having the XML element name"struct". Table 5-232 shows a list of the attributes of the struct element, and Table 5-233 shows a list of
the XML child elements.
Table 5-232 Attribute List for struct Element
No.
1.

Attribute Name

Description Details
Describes the label for identifying the STRUCT part.
(See Section 4.3.1.19.)

label

Required/Optional
Required

Table 5-233 XML Child Element List for struct Element
No.

XML Element Name1.

comment2.

structMember

Description Details
Describes the comment related to the STRUCT part.
(See Section 4.3.1.6.)
Describes the contents of the elements of the STRUCT
part.

Required/Optional
Optional
RequiredIn XML format, an element of the STRUCT part is described as an XML element having the XML
element name "structMember". Table 5-234 shows a list of attributes of the structMember element,
and Table 5-235 shows a list of XML child elements.
Table 5-234 Attribute List for structMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-235 XML Child Element List of structMember Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.

CLPA

XML Element Namelabel2
category
namedatatypedefault
range
minIncengUnit
offsetrefcomment

Description Details
Describes the LABEL2 item
Describes the CATEGORY item
Describes the NAME item
Describes the DATATYPE item
Describes the DEFAULT item
Describes the RANGE item
Describes the MIN_INC item
Describes the ENG_UNIT item
Describes the OFFSET item
Describes the REF item
Describes the COMMENT item

BAP-C2008ENG-001-K
1-255

Write the STRUCT part using a format such as shown below.
<p:struct label=" Write in accordance with the description details of Table 5-232‘Attribute Name label’”><p:comment>"Write in accordance with the description details of Table 5-233 ‘XML
Element Name comment’”</p:comment><p:structMember label="Write in accordance with the description details of Table 5-234‘Attribute Name label’”><p:label2>"Write in accordance with the description details of Table 5-235 ‘XML
Element Name label2’”><p:category>"Write in accordance with the description details of Table 5-235 ‘XML
Element Name category’”</p:category><p:name>"Write in accordance with the description details of Table 5-235 ‘XML
Element Name name’”</p:name><p:datatype>"Write in accordance with the description details of Table 5-235 ‘XML
Element Name datatype’”</p:datatype><p:default>"Write in accordance with the description details of Table 5-235 ‘XML
Element Name default’”</p:default><p:range>"Write in accordance with the description details of Table 5-235 ‘XML
Element Name range’”</p:range><p:minInc>"Write in accordance with the description details of Table 5-235 ‘XML
Element Name minInc’”</p:minInc><p:engUnit>"Write in accordance with the description details of Table 5-235 ‘XML
Element Name engUnit’”</p:engUnit><p:offset>"Write in accordance with the description details of Table 5-235 ‘XML
Element Name offset’”</p:offset><p:ref>"Write in accordance with the description details of Table 5-235 ‘XML
Element Name ref’”</p:ref><p:comment>"Write in accordance with the description details of Table 5-235 ‘XML
Element Name comment’”</p:comment></p:structMember><p:structMember label="Write in accordance with the description details of Table 5-234‘Attribute Name labe’l”>::</p:structMember>::</p:struct>

CLPA

BAP-C2008ENG-001-K
1-256

5.3.8.3 Description example of element
The following shows item description examples of an element of the STRUCT part. In the examples,the element names are set to "ConvertEnable1", "ConvertEnable2", "ConvertEnable3", and"ConvertEnable4", respectively.
Table 5-236 Item Description Example of Element (ConvertEnable1)
No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2NAME
DATATYPE
OFFSET
REF

Description Details
Write "ConvertEnable1"
Write "ConvertEnable1"
Write "Convert Enable CH1"
Write "BOOL"
Write "0.0"Write "BlockCH1.BlockInput.ConvertEnable"

Table 5-237 Item Description Example of Element (ConvertEnable2)
No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2NAME
DATATYPE
OFFSET
REF

Description Details
Write "ConvertEnable2"
Write "ConvertEnable2"
Write "Convert Enable CH2"
Write "BOOL"
Write "0.1"
Write "BlockCH2.BlockInput.ConvertEnable"

Table 5-238 Item Description Example of Element (ConvertEnable3)
No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2NAME
DATATYPE
OFFSET
REF

Description Details
Write "ConvertEnable3"
Write "ConvertEnable3"
Write "Convert Enable CH3"
Write "BOOL"
Write "0.2"
Write "BlockCH3.BlockInput.ConvertEnable"

Table 5-239 Item Description Example of Element (ConvertEnable4)
No.
1.
2.
3.
4.
5.
6.

CLPA

Item NameLABELLABEL2NAME
DATATYPE
OFFSET
REF

Description Details
Write "ConvertEnable4"
Write "ConvertEnable4"
Write "Convert Enable CH4"
Write "BOOL"
Write "0.3"
Write "BlockCH4.BlockInput.ConvertEnable"

BAP-C2008ENG-001-K
1-257

(a) Item description example of STConvertEnable element<p:struct label="STConvertEnable"><p:structMember label="ConvertEnable1"><p:label2><p:item>ConvertEnable1</p:item></p:label2><p:name><p:item>Convert Enable CH1</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:offset><p:item>0.0</p:item></p:offset><p:ref><p:item>BlockCH1.BlockInput.ConvertEnable</p:item></p:ref></p:structMember><p:structMember label="ConvertEnable2"><p:label2><p:item>ConvertEnable2</p:item></p:label2><p:name><p:item>Convert Enable CH2</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:offset><p:item>0.1</p:item></p:offset><p:ref><p:item>BlockCH2.BlockInput.ConvertEnable</p:item></p:ref></p:structMember><p:structMember label="ConvertEnable3"><p:label2><p:item>ConvertEnable3</p:item></p:label2><p:name><p:item>Convert Enable CH3</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:offset><p:item>0.2</p:item></p:offset><p:ref><p:item>BlockCH3.BlockInput.ConvertEnable</p:item></p:ref></p:structMember><p:structMember label="ConvertEnable4"><p:label2><p:item>ConvertEnable4</p:item></p:label2><p:name><p:item>Convert Enable CH4</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:offset><p:item>0.3</p:item></p:offset><p:ref><p:item>BlockCH4.BlockInput.ConvertEnable</p:item></p:ref></p:structMember></p:struct>

CLPA

BAP-C2008ENG-001-K
1-258

5.3.9ENUM part

5.3.9.1 Overview
The ENUM part (option list) describes information related to options for values and return values to be
set for an element. Refer to an ENUM part with elements in which you want to set settings based on alist box or elements for which you want to display the meaning of each value at the time a value isread using the utility software. If you want to refer to an ENUM part from an element within a
COMM_IF section, write the ENUM part in the same COMM_IF section.
The elements that make up the ENUM part are defined in accordance with the options of the value tobe used by the target module.
The configuration of each element of the ENUM part, that is, the items that should be described within
an element, is the same. Figure 5-27 shows the configuration of an element of the ENUM part.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
CODE item
RELATED_ELE item
COMMENT item
Figure 5-27 Structure Definition for Element of ENUM Part
A single element is described as a single XML element. For the detailed description specifications ofeach element, see Section 5.3.9.3.

CLPA

BAP-C2008ENG-001-K
1-259

Table 5-240 describes the items included in an element.
Table 5-240 Item List for Elements Defined in ENUM Part
No.

Item Name

Description Details

1.

LABEL

Describes the label for identifying the element

2.

LABEL2

Describes the label for identifying the element. (Usedwhen the utility software supports another language.)

3.

CATEGORY

Describes the category for grouping the element.

4.

NAME

5.

CODE

6.

RELATED_ELE

7.

COMMENT

CLPA

Describes the name of the element. Used when thename and contents of the element are displayed withthe utility software.
Describes the value for identifying the element.
Cross-checks the value indicated by the element of
the reference source with the value of the code, andselects the matching element.
Describes the element information related toelements by referring to the
COMMAND_ARGUMENT part.
[Note] This is available only in CC-Link IE TSN.
Describes the meaning of the element as well asusage precautions.
[Note] In the case of CC-Link IE TSN, multiple
COMMENT can be described. COMMENT1 and
COMMENT2 are used.

Description
Specifications
See Section
4.3.1.19
See Section
4.3.1.20
See Section
4.3.1.4

Required/Optional
Required
Optional
Optional

See Section
4.3.1.24

Required

See Section
4.3.1.5

Required

See Section
4.3.1.31

Optional

See Section
4.3.1.6

Optional

BAP-C2008ENG-001-K
1-260

5.3.9.2 XML format of ENUM partIn XML format, the ENUM part is described as an XML element having the XML element name"enum". Table 5-241 shows a list of the attributes of the enum element, and Table 5-242 shows a list of
the XML child elements.
Table 5-241 Attribute List for enum Element
No.
1.

Attribute Name

Description Details
Describes the label for identifying the ENUM part.
(See Section 4.3.1.19.)

label

Required/Optional
Required

Table 5-242 XML Child Element List for enumElement
No.

XML Element Name1.

comment2.

enumMember

Description Details
Describes the comment related to the ENUM part.
(See Section 4.3.1.6.)
Describes the contents of the elements of the ENUM
part.

Required/Optional
Optional
RequiredIn XML format, an element of the ENUM part is described as an XML element having the XML element
name "enumMember". Table 5-243 shows a list of attributes of the enumMember element, and Table
5-244 shows a list of XML child elements. Table 5-245 shows a list of the XML child elements for CCLink IE TSN.
Table 5-243 Attribute List for enumMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-244 XML Child Element List of enumMember Element
No.
1.
2.
3.
4.
5.

XML Element Namelabel2
category
namecodecomment

Description Details
Describes the LABEL2 item
Describes the CATEGORY item
Describes the NAME item
Describes the CODE item
Describes the COMMENT item

Write the ENUM part using a format such as shown below.
<p:enum label=" Write in accordance with the description details of Table 5-241‘Attribute Name label’”><p:comment>"Write in accordance with the description details of Table 5-242 ‘XML
Element Name comment’”</p:comment><p:enumMember label=" Write in accordance with the description details of Table 5-243‘Attribute Name label’”><p:label2>"Write in accordance with the description details of Table 5-244 ‘XML
Element Name label2’”</p:label2><p:category>"Write in accordance with the description details of Table 5-244 ‘XML
Element Name category”</p:category><p:name>"Write in accordance with the description details of Table 5-244 ‘XML
Element Name name’”</p:name><p:code>"Write in accordance with the description details of Table 5-244 ‘XML
Element Name code’”</p:code><p:comment>"Write in accordance with the description details of Table 5-244 ‘XML
Element Name comment’”</p:comment></p:enumMember><p:enumMember label="Write in accordance with the description details of Table 5-243‘Attribute Name label’”>::</p:enumMember>::</p:enum>

CLPA

BAP-C2008ENG-001-K
1-261

Table 5-245 XML Child Element List of enumMember Element (For CC-Link IE TSN)
No.
1.
2.
3.
4.
5.
6.
7.

XML Element Namelabel2
category
namecoderelatedEle
comment index="1"comment index="2"

Description Details
Writes LABEL2 item.
Writes CATEGORY item.
Writes NAME item.
Writes CODE item.
Writes RELATED_ELE item. [Note] Available only in CC-Link IE TSN.
Writes COMMENT1 item.
Writes COMMENT2 item.

Write the ENUM part using a format such as shown below.
<p:enum label="Write in accordance with the description details of Table 5-241 'AttributeName label'"><p:comment>"Write in accordance with the description details of Table 5-242 'XML
Element Name comment'"</p:comment><p:enumMember label="Write in accordance with the description details of Table 5-243'Attribute Name label'"><p:label2>"Write in accordance with the description details of Table 5-245 'XML
Element Name label2'"</p:label2><p:category>"Write in accordance with the description details of Table 5-245 'XML
Element Name category'"</p:category><p:name>"Write in accordance with the description details of Table 5-245 'XML
Element Name name'"</p:name><p:code>"Write in accordance with the description details of Table 5-245 'XML
Element Name code'"</p:code><p:relatedEle>"Write in accordance with the description details of Table 5-245'XML Element Name relatedEle'"</p:relatedEle><p:comment index="1">"Write in accordance with the description details of Table 5-245 'XML Element
Name comment index="1"'"</p:comment><p:comment index="2">"Write in accordance with the description details of Table 5-245 'XML Element
Name comment index="2"'"</p:comment></p:enumMember><p:enumMember label="Write in accordance with the description details of Table 5-243'Attribute Name label'">::</p:enumMember>::</p:enum>

The above describes the format for CC-Link IE TSN. A description example is shown in Table 5-250 ofSection 5.3.9.3.

CLPA

BAP-C2008ENG-001-K
1-262

5.3.9.3 Description example of element
The following shows item description examples of an element of the ENUM part. In the examples, theelement names are set to "SelCH1", "SelCH2", "SelCH3", and "SelCH4", respectively. In the exampleof CC-Link IE TSN, the element name is set to "enum2".
Table 5-246 Item Description Example of Element (SelCH1)
No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2
CATEGORYNAME
CODE
COMMENT

Description Details
Write "SelCH1"
Write "SelCH1"
Omittable item. Not written.
Write "SelCH1"
Write "1"
Write "bit0"
Table 5-247 Item Description Example of Element (SelCH2)

No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2
CATEGORYNAME
CODE
COMMENT

Description Details
Write "SelCH2"
Write "SelCH2"
Omittable item. Not written.
Write "SelCH2"
Write "2"
Write "bit1"
Table 5-248 Item Description Example of Element (SelCH3)

No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2
CATEGORYNAME
CODE
COMMENT

Description Details
Write "SelCH3"
Write "SelCH3"
Omittable item. Not written.
Write "SelCH3"
Write "3"
Write "bit2"
Table 5-249 Item Description Example of Element (SelCH4)

No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2
CATEGORYNAME
CODE
COMMENT

Description Details
Write "SelCH4"
Write "SelCH4"
Omittable item. Not written.
Write "SelCH4"
Write "4"
Write "bit3"
Table 5-250 Item Description Example of Element (enum2)

No.
1.
2.
3.
4.
5.

Item Name
Description Details
LABEL
Write "enum2".
LABEL2
Write "enum2".
CATEGORY Omittable item. Not written.
NAME
Write "Error Outside Input Value Range"
CODE
Write "0x105".
RELATED_E
6.
Write "InputError".
LE
7. COMMENT1 Write "A value larger than the maximum value set for the parameter has been input.".
8. COMMENT2 Write "Review the input or review the parameter setting.".
[Note] This description example can be used with CC-Link IE TSN only.

CLPA

BAP-C2008ENG-001-K
1-263

(a) Item description example of element<p:enum label="enumChannelSelect "><p:enumMember label="SelCH1"><p:label2><p:item>SelCH1</p:item></p:label2><p:name><p:item>SelCH1</p:item></p:name><p:code><p:item>1</p:item></p:code><p:comment><p:item>bit0</p:item></p:comment></p:enumMember><p:enumMember label="SelCH2"><p:label2><p:item>SelCH2</p:item></p:label2><p:name><p:item>SelCH2</p:item></p:name><p:code><p:item>2</p:item></p:code><p:comment><p:item>bit1</p:item></p:comment></p:enumMember><p:enumMember label="SelCH3"><p:label2><p:item>SelCH3</p:item></p:label2><p:name><p:item>SelCH3</p:item></p:name><p:code><p:item>3</p:item></p:code><p:comment><p:item>bit2</p:item></p:comment></p:enumMember><p:enumMember label="SelCH4"><p:label2><p:item>SelCH4</p:item></p:label2><p:name><p:item>SelCH4</p:item></p:name><p:code><p:item>4</p:item></p:code><p:comment><p:item>bit3</p:item></p:comment></p:enumMember></p:enum><p:enum label="ErrorCodeList"><p:enumMember label="enum2"><p:label2><p:item>enum2</p:item></p:label2><p:name><p:item>Error Outside Input Value Range</p:item></p:name><p:code><p:item>0x105</p:item></p:code><p:relatedEle><p:item>InputError</p:item></p:relatedEle><p:comment index="1"><p:item>A value larger than the maximum value set for the parameter has been
input. </p:item></p:comment><p:comment index="2"><p:item>Review the input or review the parameter setting. </p:item></p:comment></p:enumMember></p:enum>

CLPA

BAP-C2008ENG-001-K
1-264

5.3.10

COMMAND_ARGUMENT part5.3.10.1 Overview
The COMMAND_ARGUMENT part (command argument list) describes information related tocommand arguments. When you want to refer to a description in a COMMAND_ARGUMENT part froman element within the COMM_IF section, write the COMMAND_ARGUMENT part in the same
COMM_IF section.
The configuration of each element of the COMMAND_ARGUMENT part, that is, the items that should
be described within an element, is the same. Figure 5-28 shows the configuration of an element of the
COMMAND_ARGUMENT part.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
DATATYPE item
DEFAULT item
RANGE item
MIN_INC item
ENG_UNIT itemACCESS item
ASSIGN item
REF item
COMMENT item

Figure 5-28 Structure Definition for Element of COMMAND_ARGUMENT Part

CLPA

BAP-C2008ENG-001-K
1-265

A single element is described as a single XML element. For the detailed description specifications ofeach element, see Section 5.3.10.3.
The items of the COMMAND_ARGUMENT part describe the argument information of a command.
Table 5-251 describes the items included in an element.
Table 5-251 Item List for Elements Defined in COMMAND_ARGUMENT Part
No.

Item Name

Description Details

1.

LABEL

Describes the label for identifying the element.

2.

LABEL2

Describes the label for identifying the element. (Usedwhen the utility software supports another language.)

3.

CATEGORY

Describes the category for grouping the element.

4.

NAME

Describes the name of the element. Used when thename and contents of the element are displayed withthe utility software.

5.

DATATYPE

Describes the data type of the element.

6.

DEFAULT

Describes the setting value to be set for the element.

7.

RANGE

Describes the setting range of the element.

8.

MIN_INC

9.

ENG_UNIT

10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

CLPA

Describes the minimum increment applied to the valueof the element of the command argument list along with
ENG_UNIT.
Describes the engineering unit applied to the value ofthe element of the command argument list along with
MIN_INC.
Describes the access attribute of the element.
Describes the address and code to be assigned to theelement.
Describes the reference to be referred to by theelement. Use prohibited under current specifications.
Describes the meaning of the element as well as usage
precautions.

Description Required
Specifications /Optional
See Section
Required
4.3.1.19
See Section
Optional
4.3.1.20
See Section
Optional
4.3.1.4
See Section
4.3.1.24
See Section
4.3.1.10
See Section
4.3.1.11
See Section
4.3.1.26

Required
Required
Optional
Optional

See Section
4.3.1.23

Optional

See Section
4.3.1.13

Optional

See Section
4.3.1.1
See Section
4.3.1.3
See Section
4.3.1.30
See Section
4.3.1.6

Required
Optional
Optional
Optional

BAP-C2008ENG-001-K
1-266

5.3.10.2 XML format of COMMAND_ARGUMENT partIn XML format, the COMMAND_ARGUMENT part is described as an XML element having the XML
element name "commandArgument". Table 5-252 shows a list of the attributes of thecommandArgument element, and Table 5-253 shows a list of the XML child elements.
Table 5-252 Attribute List for commandArgument Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the
COMMAND_ARGUMENT part. (See Section 4.3.1.19.)

Required/Optional
Required

Table 5-253 XML Child Element List for commandArgumentElement
No.

XML Element Name1.

comment2.

commIfInfoMember

Description Details
Describes the comment related to the
COMMAND_ARGUMENT part(See Section 4.3.1.6.)
Describes the contents of the elements of the
COMMAND_ARGUMENT part

Required/Optional
Optional
RequiredIn XML format, an element of the COMMAND_ARGUMENT part is described as an XML element
having the XML element name "commandArgumentMember". Table 5-254 shows a list of attributes of
the commandArgumentMember element, and Table 5-255 shows a list of XML child elements.
Table 5-254 Attribute List for commandArgumentMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-255 XML Child Element List of commandArgumentMember Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.

CLPA

XML Element Namelabel2
category
namedatatypedefault
range
minIncengUnit
accessassignrefcomment

Description Details
Describes the LABEL2 item
Describes the CATEGORY item
Describes the NAME item.
Describes the DATATYPE item
Describes the DEFAULT item
Describes the RANGE item
Describes the MIN_INC item.
Describes the ENG_UNIT item
Describes the ACCESS item.
Describes the ASSIGN item.
Describes the REF item. Use prohibited under current specifications.
Describes the COMMENT item.

BAP-C2008ENG-001-K
1-267

Write the COMMAND_ARGUMENT part using a format such as shown below.
<p:commandArgument label=" Write in accordance with the description details of Table
5-252 ‘Attribute Name label’"><p:comment>"Write in accordance with the description details of Table 5-253 ‘XML
Element Name comment’”</p:comment><p:commandArgumentMember label=" Write in accordance with the description details ofTable 5-254 ‘Attribute Name label’"><p:label2>"Write in accordance with the description details of Table 5-255 ‘XML
Element Name label2’”</p:label2><p:category>"Write in accordance with the description details of Table 5-255 ‘XML
Element Name category’”</p:category><p:name>"Write in accordance with the description details of Table 5-255 ‘XML
Element Name name’”</p:name><p:datatype>"Write in accordance with the description details of Table 5-255 ‘XML
Element Name datatype’”</p:datatype><p:default>"Write in accordance with the description details of Table 5-255 ‘XML
Element Name default’”</p:default><p:range>"Write in accordance with the description details of Table 5-255 ‘XML
Element Name range’”</p:range><p:minInc>"Write in accordance with the description details of Table 5-255 ‘XML
Element Name minInc’”</p:minInc><p:engUnit>"Write in accordance with the description details of Table 5-255 ‘XML
Element Name engUnit’”</p:engUnit><p:access>"Write in accordance with the description details of Table 5-255 ‘XML
Element Name access’”</p:access><p:assign>"Write in accordance with the description details of Table 5-255 ‘XML
Element Name assign’”</p:assign><p:ref>"Write in accordance with the description details of Table 5-255 ‘XML
Element Name ref’”</p:ref><p:comment>"Write in accordance with the description details of Table 5-255 ‘XML
Element Name comment’”</p:comment></p:commandArgumentMember><p:commandArgumentMember label=" Write in accordance with the description details ofTable 5-254 ‘Attribute Name label’">::</p:commandArgumentMember>::</p:commandArgument>

CLPA

BAP-C2008ENG-001-K
1-268

5.3.10.3 Description example of element
The following shows an item description example of an element of the COMMAND_ARGUMENT part.
In the example below, the element name is set to "CH1_AvgOrSample".
Table 5-256 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESSASSIGNREF
COMMENT

Description Details
Write "CH1_AvgOrSample"
Write "CH1_AvgOrSample"
Omittable item. Not written.
Write "CH1 Sampling and Averaging Process Specification"
Write "BOOL"
Write "0"Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Write "W"
Omittable item. Not written.
Use prohibited
Omittable item. Not written.

(a) Item description example of element<p:commandArgumentMember label="CH1_AvgOrSample"><p:label2><p:item>CH1_AvgOrSample</p:item></p:label2><p:name><p:item>CH1 Sampling and Averaging Process Specification</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:default><p:item>0</p:item></p:default><p:access><p:item>W</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-269

BLOCK Section

5.4

The BLOCK section comprises multiple parts as shown below. One part is written as a single XML
element. A comment may also be written (option).

BLOCK section
BLOCK_INFO part

Describes function block identification information.

BLOCK_INPUT part

Describes function block input information.

BLOCK_OUTPUT part

Describes function block output information.

BLOCK_PARAMETER part

Describes function block parameter information.

BLOCK_COMMAND part

Describes the commands executable by the function
block.
Describes the structure of the inputs and outputs ofmultiple elements.
Describes the options for values to be set in the element
and return values.

STRUCT part
ENUM part
COMMAND_ARGUMENT part

Describes the argument information of
BLOCK_COMMAND.

Figure 5-29 Structure of BLOCK Section
In XML format, the BLOCK section is written as an XML element of the XML element name "block".
Table 5-257 shows a list of the attributes of the block element, and Table 5-258 shows a list of XML
child elements.
Table 5-257 List of Attributes of block Element
No.
1.

Attribute Namelabel

Description Details
Describes the label that identifies the BLOCK section.
(See Section 4.3.1.19.) (Example: "BlockSection")

Required/Optional
Required

Table 5-258 List of XML Child Elements of block Element
No.

XML Element Name1.

comment2.

blockInfo

CLPA

Description Details
Describes the comment related to the BLOCK section(See Section 4.3.1.6.)
Describes the contents of the BLOCK_INFO part

Required/Optional
Optional
Required

BAP-C2008ENG-001-K
1-270

5.4.1BLOCK_INFO part5.4.1.1 Overview
A BLOCK_INFO part describes information related to function block identification.
Figure 5-30 shows the elements that make up the BLOCK_INFO part.

BLOCK_INPUT part
VendorName element

VendorCode element

Version element

Figure 5-30 Structure of BLOCK_INFO Part
The configuration of each element of the BLOCK_INFO part, that is, the items that should be
described within each element, is the same. Figure 5-31 shows the configuration of an element of the
BLOCK_INFO part.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
DATATYPE item
DATA item

Figure 5-31 Structure Definition for Element of BLOCK_INFO Part

CLPA

BAP-C2008ENG-001-K
1-271

Table 5-259 lists the elements of the BLOCK_INFO part. A single element is described as a single
XML element. For the detailed description specifications of each element, see Section 5.4.1.3.
Table 5-259 Elements of BLOCK PartNo.

Element1.

VendorName

2.

VendorCode

3.

VersionDescription Details
Describes the name of the vendor that manufactured themodule.
Describes the vendor code of the vendor that
manufactured the module. Describes the fifth to eighth
digits of the partner member number of the CC-Link
Partner Association.
Describes the firmware version. Described using astring.

Required/Optional
Required
Required
Required

Table 5-260 shows the items described in the elements of the BLOCK_INFO part.
Table 5-260 Item List of BLOCK_INFO PartNo.

Element Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Describes the label for identifying theelement.
Describes the label for identifying theelement. (Used when the utility
software supports another language.)
Describes the category for grouping theelement.
Describes the name of the element.
Used when the name and contents ofthe element are displayed with theutility software.
Describes the data type of the contents
described in the DATA item.
Describes the contents of the element.

Description
Specifications
See Section
4.3.1.19

Required/Optional
Required

See Section
4.3.1.20

Optional

See Section
4.3.1.4

Optional

See Section
4.3.1.24

Optional

See Section
4.3.1.10
See Section
4.3.1.9

Optional
Required

Based on the elements described in BLOCK_INFO, the information indicated in Table 5-259 is
described as elements common to each device. Note, however, that LABEL2 and NAME arerecommended specifications and may be omitted. For these items, we recommend writing"COMMON" for the CATEGORY.
In addition to the information shown in Table 5-259, information that is unique to the device may be
added to BLOCK_INFO.

CLPA

BAP-C2008ENG-001-K
1-272

5.4.1.2 XML format of BLOCK_INFO partIn XML format, the BLOCK_INFO part is described as an XML element having the XML element name"blockInfo". Table 5-261 shows a list of the attributes of the blockInfo element, and Table 5-262 showsa list of the XML child elements.
Table 5-261 Attribute List for blockInfo Element
No.
1.

Attribute Name

Description Details
Describes the label for identifying the BLOCK_INFO
part. (See Section 4.3.1.19.)

label

Required/Optional
Required

Table 5-262 XML Child Element List for blockInfo Element
No.

XML Element Name1.

comment2.

blockInfoMember

Description Details
Describes the comment related to the BLOCK_INFO
part(See Section 4.3.1.6.)
Describes the contents of the elements of the
BLOCK_INFO part

Required/Optional
Optional
RequiredIn XML format, the element of the BLOCK_INFO part is described as an XML element having the XML
element name "blockInfoMember". Table 5-263 shows a list of attributes of the blockInfoMember
element, and Table 5-264 shows a list of XML child elements.
Table 5-263 Attribute List for blockInfoMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.(See
Section 4.3.1.19.) The contents written for this label are
regulated by CSP+ specifications, and cannot be
arbitrarily written by the user. For details, see Section
5.4.1.3.

Required/Optional
Required

Table 5-264 XML Child Element List of blockIfInfoMember Element
No.
1.
2.
3.
4.
5.

XML Element Namelabel2
category
namedatatype
data

Description Details
Describes the LABEL2 item
Describes the CATEGORY item
Describes the NAME item
Describes the DATATYPE item
Describes the DATA item.

Write the BLOCK_INFO part using a format such as shown below.
<p:blockInfo label=" Write in accordance with the description details of Table 5-261‘Attribute Name label’"><p:comment>"Write in accordance with the description details of Table 5-262 ‘XML
Element Name comment”</p:comment><p:blockInfoMember label=" Write in accordance with the description details of Table
5-263“Attribute Name label’"><p:label2>"Write in accordance with the description details of Table 5-264 ‘XML
Element Name label2”</p:label2><p:category>"Write in accordance with the description details of Table 5-264 ‘XML
Element Name category”</p:category><p:name>"Write in accordance with the description details of Table 5-264 ‘XML
Element Name name”</p:name><p:datatype>"Write in accordance with the description details of Table 5-264 ‘XML
Element Name datatype”</p:datatype><p:data>"Write in accordance with the description details of Table 5-264 ‘XML
Element Name data”</p:data></p:blockInfoMember><p:blockInfoMember label=""Write in accordance with the description details of Table
5-263‘Attribute Name label’">::</p:blockInfoMember>
:
:

CLPA

BAP-C2008ENG-001-K
1-273

</p:blockInfo>

CLPA

BAP-C2008ENG-001-K
1-274

5.4.1.3 Description details of each element(1) Item description of VendorName element
Table 5-265 Item Description Specifications of VendorName Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "VendorName"
Write "VendorName" in the case of English CSP+ files [Recommended
specifications].
Write "COMMON"
Write "VendorName" in the case of English CSP+ files [Recommended
specifications].
Write "STRING_U(64)"
Write the name of the vendor that created the device(a) Item description example of VendorName element<p:blockInfoMember label="VendorName"><p:label2><p:item>VendorName</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Vendor Name</p:item></p:name><p:datatype><p:item>STRING(64)</p:item></p:datatype><p:data><p:item>CC-Link Partner Association</p:item></p:data></p:blockInfoMember>(2) Item description of VendorCode element
Table 5-266 Item Description Specifications of VendorCode Element
No. Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "VendorCode".
Write "VendorCode" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON".
Write "VendorCode" in the case of English CSP+ files.
[Recommended specifications]Write "WORD".
Write the code of the vendor that created the device.
Write the fifth to eighth digits of the partner member number of the CC-Link Partner
Association.

(a) Item description example of VendorCode element<p:blockInfoMember label="VendorCode"><p:label2><p:item>VendorCode</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Vendor Code</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:data><p:item>0x0000</p:item></p:data></p:blockInfoMember>

CLPA

BAP-C2008ENG-001-K
1-275

(3) Item description of Version element
Table 5-267 Item Description Specifications of Version Element
No.
1.
2.
3.
4.

Item NameLABELLABEL2
CATEGORYNAME

5.

DATATYPE

6.

DATA

Description Details
Write "Version"
Write "Version" in the case of English CSP+ files. [Recommended specifications]Write "COMMON"
Write "Version" in the case of English CSP+ files. [Recommended specifications]
Select and write a value from the following: bit string type, signed integer type,unsigned integer type, string type [expressed as "STRING(x) only". "STRING(32) iswritten in the example below.
Write the version of the control function of the device. For the version method, see
Section 5.2.1.1(1).

(a) Item description example of Version element<p:blockInfoMember label="Version"><p:label2><p:item>Version</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Version</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>1.00A</p:item></p:data></p:blockInfoMember>

CLPA

BAP-C2008ENG-001-K
1-276

5.4.2BLOCK_INPUT part5.4.2.1 Overview
A BLOCK_INPUT part describes information related to function block input.
The elements that make up the BLOCK_INPUT part are defined in accordance with the function of thetarget module.
The configuration of each element of the BLOCK_INPUT part, that is, the items that should be
described within each element, is the same. Figure 5-32 shows the configuration of an element of the
BLOCK_INPUT part.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
DATATYPE item
DEFAULT item
RANGE item
MIN_INC item
ENG_UNIT itemACCESS itemUI_ATTRIBUTE item
COMMENT item

Figure 5-32 Structure Definition for Element of BLOCK_INPUT Part and BLOCK_OUTPUT Part
A single element is described as a single XML element. For element description examples, see
Section 5.4.2.3.

CLPA

BAP-C2008ENG-001-K
1-277

Table 5-268 describes the items included in an element.
Table 5-268 List of Items Defined inBLOCK_INPUT Part and BLOCK_OUTPUT PartNo.

Element Name

Description Details
Describes the label for identifying the element. (Usedwhen the utility software supports another language.)
Describes the label for identifying the element. (Usedwhen the utility software supports another language.)

1.

LABEL

2.

LABEL2

3.

CATEGORY

Describes the category for grouping the element.

4.

NAME

Describes the name of the element. Used when thename and contents are displayed with the utility
software.

5.

DATATYPE

Describes the data type of the contents.

6.

DEFAULT

Describes the default value to be set for the element.

7.

RANGE

Describes the setting range of the element.

8.

MIN_INC

9.

ENG_UNIT

10. ACCESS
11. UI_ATTRIBUTE
12. COMMENT

CLPA

Describes the minimum increment applied to the valueof the element along with "engUnit". Required when
engUnit is described.
Describes the engineering unit applied to the value ofthe element along with "minInc. "Describes the access attribute of the element.
Describes the display method when the element isdisplayed with the utility software.
Describes the meaning of the element as well asusage precautions.

Description
Specifications
See Section
4.3.1.19
See Section
4.3.1.20
See Section
4.3.1.4
See Section
4.3.1.24
See Section
4.3.1.10
See Section
4.3.1.11
See Section
4.3.1.26
See Section
4.3.1.23
See Section
4.3.1.13
See Section
4.3.1.1
See Section
4.3.1.43
See Section
4.3.1.6

Required/Optional
Required
Optional
Optional
Required
Required
Optional
Optional
Optional
Optional
Optional
Optional
Optional

BAP-C2008ENG-001-K
1-278

5.4.2.2 XML format of BLOCK_INPUT partIn XML format, the BLOCK_INPUT part is described as an XML element having the XML element
name "blockInput". Table 5-269 shows a list of the attributes of the blockInput element, and Table
5-270 shows a list of the XML child elements.
Table 5-269 Attribute List for blockInput Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the BLOCK_INPUT
part. (See Section 4.3.1.19.)

Required/Optional
Required

Table 5-270 XML Child Element List for blockInput Element
No.

XML Element Name1.

comment2.

blockInputMember

Description Details
Describes the comment related to the BLOCK_INPUT
part. (See Section 4.3.1.6.)
Describes the contents of the elements of the
BLOCK_INPUT part

Required/Optional
Optional
RequiredIn XML format, the element of the BLOCK_INPUT part is described as an XML element having the
XML element name "blockInputMember". Table 5-271 shows a list of attributes of theblockInputMember element, and Table 5-272 shows a list of XML child elements.
Table 5-271 Attribute List for blockInputMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-272 XML Child Element List of blockIfInputMember Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.

CLPA

XML Element Namelabel2
category
namedatatypedefault
range
minIncengUnit
accessuiAttributecomment

Description Details
Describes the LABEL2 item.
Describes the CATEGORY item.
Describes the NAME item.
Describes the DATATYPE item.
Describes the DEFAULT item.
Describes the RANGE item.
Describes the MIN_INC item.
Describes the ENG_UNIT item
Describes the ACCESS item.
Describes the UI_ATTRIBUTE item
Describes the COMMENT item.

BAP-C2008ENG-001-K
1-279

Write the BLOCK_INPUT part using a format such as shown below.
<p:blockInput label=" Write in accordance with the description details of Table 5-269‘Attribute Name label’"><p:comment>"Write in accordance with the description details of Table 5-270 ‘XML
Element Name comment’”</p:comment><p:blockInputMember label=" Write in accordance with the description details of Table
5-271“Attribute Name label’"><p:label2>"Write in accordance with the description details of Table 5-272 ‘XML
Element Name label’2”</p:label2><p:category>"Write in accordance with the description details of Table 5-272 ‘XML
Element Name category’”</p:category><p:name>"Write in accordance with the description details of Table 5-272 ‘XML
Element Name name’”</p:name><p:datatype>"Write in accordance with the description details of Table 5-272 ‘XML
Element Name datatype’”</p:datatype><p:default>"Write in accordance with the description details of Table 5-272 ‘XML
Element Name default’”</p:default><p:range>"Write in accordance with the description details of Table 5-272 ‘XML
Element Name range’”</p:range><p:minInc>"Write in accordance with the description details of Table 5-272 ‘XML
Element Name minInc’”</p:minInc><p:engUnit>"Write in accordance with the description details of Table 5-272 ‘XML
Element Name engUnit’”</p:engUnit><p:access>"Write in accordance with the description details of Table 5-272 ‘XML
Element Name access’”</p:access><p:uiAttribute>"Write in accordance with the description details of Table 5-272‘XML Element Name uiAttribute’”</p:uiAttribute><p:comment>"Write in accordance with the description details of Table 5-272 ‘XML
Element Name comment’”</p:comment></p:blockInputMember><p:blockInputMember label="Write in accordance with the description details of Table
5-271‘Attribute Name label’">::</p:blockInputMember>::</p:blockInput>

CLPA

BAP-C2008ENG-001-K
1-280

5.4.2.3 Description example of element
The following shows an item description example of an element of the BLOCK_INPUT part. In theexample below, the element name is set to "CH1_ADConversionComp".
Table 5-273 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESSUI_ATTRIBUTE
COMMENT

Description Details
Write "CH1_ADConversionComp"
Write "CH1_ADConversionComp" in the case of English CSP+ files
Omittable item. Not written.
Write "CH1 A/D Conversion Complete Flag" in the case of English CSP+ files
Write "BOOL"
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.

(a) Item description example of element<p:blockInputMember label="CH1_ADConversionComp"><p:label2><p:item>CH1_ADConversionComp</p:item></p:label2><p:name><p:item>CH1 A/D Conversion Complete Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype></p:blockInputMember>

CLPA

BAP-C2008ENG-001-K
1-281

5.4.3BLOCK_OUTPUT part

5.4.3.1 Overview
A BLOCK_OUTPUT part describes information related to function block output.
The elements that make up the BLOCK_OUTPUT part are defined in accordance with the function of
the target module.
The configuration of each element of the BLOCK_OUTPUT part, that is, the items that should be
described within each element, is the same. For the configuration of an element of the
BLOCK_OUTPUT part, see Figure 5-32 (same as BLOCK_INPUT).
A single element is described as a single XML element. For the detailed description specifications ofeach element, see Section 5.4.3.3.
Table 5-268 (same as BLOCK_INPUT) describes the items included in an element.

5.4.3.2 XML format of BLOCK_OUTPUT partIn XML format, the BLOCK_OUTPUT part is described as an XML element having the XML element
name "blockOutput". Table 5-274 shows a list of the attributes of the blockOutput element, and Table
5-275shows a list of the XML child elements.
Table 5-274 Attribute List for blockOutput Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the BLOCK_OUTPUT
part. (See Section 4.3.1.19.)

Required/Optional
Required

Table 5-275 XML Child Element List for blockOutput Element
No.

XML Element Name1.

comment2.

blockOutputMember

CLPA

Description Details
Describes the comment related to the BLOCK_OUTPUT
part. (See Section 4.3.1.6.)
Describes the contents of the elements of the
BLOCK_OUTPUT part.

Required/Optional
Optional
Required

BAP-C2008ENG-001-K
1-282

In XML format, the element of the BLOCK_OUTPUT part is described as an XML element having the
XML element name "blockOutputMember". Table 5-276 shows a list of attributes of theblockOutputMember element, and Table 5-277 shows a list of XML child elements.
Table 5-276 Attribute List for blockOutputMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-277 XML Child Element List of blockOutputMember Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.

XML Element Namelabel2
category
namedatatypedefault
range
minIncengUnit
accessuiAttributecomment

Description Details
Describes the LABEL2 item.
Describes the CATEGORY item.
Describes the NAME item.
Describes the DATATYPE item.
Describes the DEFAULT item.
Describes the RANGE item.
Describes the MIN_INC item.
Describes the ENG_UNIT item
Describes the ACCESS item.
Describes the UI_ATTRIBUTE item
Describes the COMMENT item.

Write the BLOCK_OUTPUT part using a format such as shown below.
<p:blockOutput label=" Write in accordance with the description details of Table 5-274‘Attribute Name label’"><p:comment>“Write in accordance with the description details of Table 5-275 ‘XML
Element Name comment”</p:comment><p:blockOutputMember label=" Write in accordance with the description details of Table
5-276“Attribute Name label’"><p:label2>“Write in accordance with the description details of Table 5-277 ‘XML
Element Name label2”</p:label2><p:category>“Write in accordance with the description details of Table 5-277 ‘XML
Element Name category”</p:category><p:name>“Write in accordance with the description details of Table 5-277 ‘XML
Element Name name”</p:name><p:datatype>“Write in accordance with the description details of Table 5-277 ‘XML
Element Name datatype”</p:datatype><p:default>“Write in accordance with the description details of Table 5-277 ‘XML
Element Name default”</p:default><p:range>“Write in accordance with the description details of Table 5-277 ‘XML
Element Name range”</p:range><p:minInc>“Write in accordance with the description details of Table 5-277 ‘XML
Element Name minInc”</p:minInc><p:engUnit>“Write in accordance with the description details of Table 5-277 ‘XML
Element Name engUnit”</p:engUnit><p:access>“Write in accordance with the description details of Table 5-277 ‘XML
Element Name access”</p:access><p:uiAttribute>“Write in accordance with the description details of Table 5-277‘XML Element Name uiAttribute”</p:uiAttribute><p:comment>“Write in accordance with the description details of Table 5-277 ‘XML
Element Name comment”</p:comment></p:blockOutputMember><p:blockOutputMember label=“Write in accordance with the description details of Table
5-276 ‘Attribute Name label’">::</p:blockOutputMember>::</p:blockOutput>

CLPA

BAP-C2008ENG-001-K
1-283

5.4.3.3 Description example of element
The following shows an item description example of an element of the BLOCK_OUTPUT part. In theexample below, the element name is set to "VoltageCurrentSelect".
Table 5-278 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESSUI_ATTRIBUTE
COMMENT

Description Details
Write "VoltageCurrentSelect"
Write "VoltageCurrentSelect"
Omittable item. Not written.
Write "Voltage Current Selection"
Write "BOOL"
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Write "0: Voltage, 1: Current".

(a) Item description example of element<p:blockOutputMember label="VoltageCurrentSelect"><p:label2><p:item>VoltageCurrentSelect</p:item></p:label2><p:name><p:item>Voltage Current Selection</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:comment><p:item>0: Voltage, 1: Current</p:item></p:comment></p:blockOutputMember>

CLPA

BAP-C2008ENG-001-K
1-284

5.4.4BLOCK_PARAMETER part

5.4.4.1 Overview
A BLOCK_PARAMETER part describes information related to the parameters of the control function of
the target module.
The elements that make up the BLOCK_OUTPUT part are defined in accordance with the target
module communication function.
The configuration of each element of the BLOCK_PARAMETER part, that is, the items that should be
described within each element, is the same. For the configuration of an element of the
BLOCK_PARAMETER part, see Figure 5-33.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
DATATYPE item
DEFAULT item
RANGE item
MIN_INC item
ENG_UNIT itemACCESS item
WRITE_ORDER itemUI_ATTRIBUTE item
COMMENT item

Figure 5-33 Structure Definition for Element of BLOCK_PARAMETER Part

CLPA

BAP-C2008ENG-001-K
1-285

A single element is described as a single XML element. For the detailed description specifications ofeach element, see Section 5.4.4.3.
An element of the BLOCK_PARAMETER part describes the parameters to be set in the module
function area.
An element described in the BLOCK_PARAMETER part describes information about the parameters
to be set in the function block.
Table 5-279 describes the items included in an element.
Table 5-279 Item List for Elements Defined in BLOCK_PARAMETER Part
No.

Item Name

Description Details

1.

LABEL

Describes the label for identifying the element.

2.

LABEL2

Describes the label for identifying the element. (Usedwhen the utility software supports another language.)

3.

CATEGORY

Describes the category for grouping the element.

4.

NAME

Describes the name of the element. Used when thename and contents are displayed with the utility
software.

5.

DATATYPE

Describes the data type of the element.

6.

DEFAULT

Describes the default value set for the element.

7.

RANGE

Describes the setting range of the element.

8.

MIN_INC

9.

ENG_UNIT

10. ACCESS
11. WRITE_ORDER
12. UI_ATTRIBUTE
13. COMMENT

CLPA

Describes the minimum increment applied to the valueof the element along with "engUnit".
Describes the engineering unit applied to the value ofthe element along with "minInc".
Describes the access attribute of the element.
Describes the order in which elements are to be
written to the module.
Describes the display method when the element isdisplayed with common utility software.
Describes the meaning of the element as well asusage precautions.

Description
Specifications
See Section
4.3.1.19
See Section
4.3.1.20
See Section
4.3.1.4
See Section
4.3.1.24
See Section
4.3.1.10
See Section
4.3.1.11
See Section
4.3.1.26
See Section
4.3.1.23
See Section
4.3.1.13
See Section
4.3.1.1
See Section
4.3.1.46
See Section
4.3.1.43
See Section
4.3.1.6

Required/Optional
Required
Optional
Optional
Required
Required
Optional
Optional
Optional
Optional
Required
Optional
Optional
Optional

BAP-C2008ENG-001-K
1-286

5.4.4.2 XML format of BLOCK_PARAMETER partIn XML format, the BLOCK_PARAMETER part is described as an XML element having the XML
element name "blockParameter". Table 5-280 shows a list of the attributes of the blockParameter
element, and Table 5-281 shows a list of the XML child elements.
Table 5-280 Attribute List for blockParameter Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the
BLOCK_PARAMETER part. (See Section 4.3.1.19.)

Required/Optional
Required

Table 5-281 Child Element List for blockParameter Element
No.

XML Element Name1.

comment2.

blockParameter
MemberDescription Details
Describes the comment related to the
BLOCK_PARAMETER part. (See Section 4.3.1.6.)
Describes the contents of the elements of the
BLOCK_PARAMETER part.

Required/Optional
Optional
RequiredIn XML format, the element of the BLOCK_PARAMETER part is described as an XML element having
the XML element name "blockParameterMember". Table 5-282 shows a list of attributes of theblockParameterMember element, and Table 5-283 shows a list of child elements.
Table 5-282 Attribute List for blockParameterMember Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-283 Child Element List of blockParameterMember Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.

CLPA

XML Element Namelabel2
category
namedatatypedefault
range
minIncengUnit
accesswriteOrderuiAttributecomment

Description Details
Describes the LABEL2 item.
Describes the CATEGORY item.
Describes the NAME item.
Describes the DATATYPE item.
Describes the DEFAULT item.
Describes the RANGE item.
Describes the MIN_INC item.
Describes the ENG_UNIT item
Describes the ACCESS item.
Describes the WRITE_ORDER item.
Describes the UI_ATTRIBUTE item
Describes the COMMENT item.

BAP-C2008ENG-001-K
1-287

Write the BLOCK_PARAMETER part using a format such as shown below.
<p:blockParameter label="Write in accordance with the description details of Table 5-280‘Attribute Name label’"><p:comment>“Write in accordance with the description details of Table 5-281 ‘XML
Element Name comment’”</p:comment><p:blockParameterMember label=" Write in accordance with the description details ofTable 5-282 ‘Attribute Name label’"><p:label2>“Write in accordance with the description details of Table 5-283 ‘XML
Element Name label2’”</p:label2><p:category>“Write in accordance with the description details of Table 5-283 ‘XML
Element Name category’”</p:category><p:name>“Write in accordance with the description details of Table 5-283 ‘XML
Element Name name’”</p:name><p:datatype>“Write in accordance with the description details of Table 5-283 ‘XML
Element Name datatype’”</p:datatype><p:default>“Write in accordance with the description details of Table 5-283 ‘XML
Element Name default’”</p:default><p:range>“Write in accordance with the description details of Table 5-283 ‘XML
Element Name range’”</p:range><p:minInc>“Write in accordance with the description details of Table 5-283 ‘XML
Element Name minInc’”</p:minInc><p:engUnit>“Write in accordance with the description details of Table 5-283 ‘XML
Element Name engUnit’”</p:engUnit><p:access>“Write in accordance with the description details of Table 5-283 ‘XML
Element Name access’”</p:access><p:writeOrder>“Write in accordance with the description details of Table 5-283‘XML Element Name writeOrder’”</p:writeOrder><p:uiAttribute>“Write in accordance with the description details of Table 5-283‘XML Element Name uiAttribute’”</p:uiAttribute><p:comment>“Write in accordance with the description details of Table 5-283 ‘XML
Element Name comment’”</p:comment></p:blockParameterMember><p:blockParameterMember label=" Write in accordance with the description details ofTable 5-282 ‘Attribute Name label’::</p:blockParameterMember>::</p:blockParameter>

CLPA

BAP-C2008ENG-001-K
1-288

5.4.4.3 Description example of element
The following shows an item description example of an element of the BLOCK_PARAMETER part. In
the example below, the element name is set to "Parameter1".
Table 5-284 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS
WRITE_ORDERUI_ATTRIBUTE
COMMENT

Description Details
Write "Parameter1"
Write "Parameter1"
Omittable item. Not written.
Write "Parameter 1"
Write "UINT16"
Write "0"Write " [0,65535]"
Write "0.01"
Write "Hz"Write "RW"
Write "10"Omittable item. Not written.
Omittable item. Not written.

(a) Item description example of element<p:blockParameterMember label="Parameter1"><p:label2><p:item>Parameter1</p:item></p:label2><p:name><p:item>Parameter 1</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:default><p:item>0</p:item></p:default><p:range><p:item>[0,65535]</p:item></p:range><p:minInc><p:item>0.01</p:item></p:minInc><p:engUnit><p:item>Hz</p:item></p:engUnit><p:access><p:item>RW</p:item></p:access><p:writeOrder><p:item>10</p:item></p:writeOrder></p:blockParameterMember>

CLPA

BAP-C2008ENG-001-K
1-289

5.4.5BLOCK_COMMAND part5.4.5.1 Overview
A BLOCK_COMMAND part describes information related to the commands to be executed by thecontrol function of the target module.
The elements that make up the BLOCK_COMMAND part are defined in accordance with the functionof the target module.
The configuration of each element of the BLOCK_COMMAND part, that is, the items that should be
described within each element, is the same. For the configuration of an element of the
BLOCK_COMMAND part, see Figure 5-34.

Element
LABEL item
LABEL2 item
CATEGORY item
NAME item
ARGUMENT item
COMMENT item

Figure 5-34 Structure Definition for Element of BLOCK_COMMAND Part
A single element is described as a single XML element. For the detailed description specifications ofeach element, see Section 5.4.5.3.
Table 5-285 shows the items described in an element of the BLOCK_COMMAND part.
Table 5-285 Item List for Elements Defined in BLOCK_COMMAND Part
No.

Item Name

Description Details

1.

LABEL

Describes the label for identifying the element.

2.

LABEL2

Describes the label for identifying the element. (Usedwhen the utility software supports another language.)

3.

CATEGORY

Describes the category for grouping the element.

4.

NAME

5.

ARGUMENT

6.

COMMENT

CLPA

Describes the name of the item.
Used when the name and contents are displayedwith the utility software.
Describes the label of the COMMAND_ARGUMENT
part for indicating the arguments used by theelement.
Describes the meaning of the element as well asusage precautions.

Description
Specifications
See Section
4.3.1.19
See Section
4.3.1.20
See Section
4.3.1.4

Required/Optional
Required
Optional
Optional

See Section
4.3.1.24

Required

See Section
4.3.1.2

Required

See Section
4.3.1.6

Optional

BAP-C2008ENG-001-K
1-290

5.4.5.2 XML format of BLOCK_COMMAND partIn XML format, the BLOCK_COMMAND part is described as an XML element having the XML element
name "blockCommand". Table 5-286 shows a list of the attributes of the blockCommand element, andTable 5-287 shows a list of the XML child elements.
Table 5-286 Attribute List for blockCommand Element
No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the
BLOCK_COMMAND part. (See Section 4.3.1.19.)

Required/Optional
Required

Table 5-287 XML Child Element List for blockCommand Element
No.
1.
2.

XML Element Name

Description Details
Required/Optional
Describes the comment related to thecomment
Optional
BLOCK_COMMAND part. (See Section 4.3.1.6.)
blockCommand
Describes the contents of the elements of theRequiredMemberBLOCK_COMMAND part.
In XML format, the element of the BLOCK_COMMAND part is described as an XML element having
the XML element name "blockCommandMember". Table 5-288 shows a list of attributes of theblockCommandMember element, and Table 5-289 shows a list of XML child elements.
Table 5-288 Attribute List for blockCommandMember Element

No.
1.

Attribute Namelabel

Description Details
Describes the label for identifying the element.
(See Section 4.3.1.19.)

Required/Optional
Required

Table 5-289 List of XML Child Elements of blockCommandMemberElement
No.

XML Element Name1.

label22.

category

3.

name

4.

argument

5.

comment

Description Details
Describes the label for identifying the element. (Usedwhen the utility software supports another language.)
Describes the category for grouping the element.
Describes the name of the item. Used when the nameand contents are displayed with the utility software.
Describes the label of the COMMAND_ARGUMENT partfor indicating the argument to be used by the element.
Describes the meaning of the element as well as usage
precautions.

Required/Optional
Optional
Optional
Required
Required
Optional

Write the BLOCK_COMMAND part using a format such as shown below.
<p:blockCommand label="Write in accordance with the description details of Table 5-286‘Attribute Name label’"><p:comment>“Write in accordance with the description details of Table 5-287 ‘XML
Element Name comment’”</p:comment><p:blockCommandMember label="Write in accordance with the description details of Table
5-288 ’Attribute Name label’"><p:label2>“Write in accordance with the description details of Table 5-289 ‘XML
Element Name label2’”</p:label2><p:category>“Write in accordance with the description details of Table 5-289 ‘XML
Element Name category’”</p:category><p:name>“Write in accordance with the description details of Table 5-289 ‘XML
Element Name name’”</p:name><p:argument>“Write in accordance with the description details of Table 5-289 ‘XML
Element Name argument’”</p:argument><p:comment>“Write in accordance with the description details of Table 5-289 ‘XML
Element Name comment’”</p:comment></p:blockCommandMember><p:blockCommandMember label="Write in accordance with the description details of Table
5-288‘Attribute Name label’">::</p:blockCommandMember>::</p:blockCommand>

CLPA

BAP-C2008ENG-001-K
1-291

5.4.5.3 Description example of element
The following shows an item description example of an element of the BLOCK_COMMAND part. In
the example below, the element name is set to "CmdGetFaultRecord".
Table 5-290 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2
CATEGORYNAME
ARGUMENT
COMMENT

Description Details
Write "CmdGetFaultRecord"
Write "CmdGetFaultRecord"
Omittable item. Not written.
Write "Fault Record Acquisition"
Write "ArgGetFaultRecord"
Omittable item. Not written.

(a) Item description example of element<p:blockCommandMember label="CmdGetFaultRecord"><p:label2><p:item>CmdGetFaultRecord</p:item></p:label2><p:name><p:item>Fault Record Acquisition</p:item></p:name><p:argument><p:item>ArgGetFaultRecord</p:item></p:argument></p:blockCommandMember >CLPA

BAP-C2008ENG-001-K
1-292

5.4.6

STRUCT part

5.4.6.1 Overview
The STRUCT part (structure) describes information related to the structure of the inputs and outputs ofmultiple elements. A structure is used when an area is divided. Each of the elements that make up the
structure needs to be assigned a consecutive address. When an element within the BLOCK sectionrefers to a description of a STRUCT part, the STRUCT part is described within the same BLOCK
section. A STRUCT part described in a BLOCK section defines the configuration of the elements
described in the COMMAND_ARGUMEN part.
The elements that make up the STRUCT part are the same as those defined within a COMM_IF
section. See Section 5.3.8. Note that when writing in a BLOCK section, the Name item and
DATATYPE item are required, and the REF item is prohibited.

5.4.6.2 Description example of element
The following shows item description examples of an element of the STRUCT part. In the examples
below, the element names are set to "STReturnCode1" and "STReturnCode2".
Table 5-291 Item Description Example of Element (STReturnCode1)
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITOFFSET
REF
COMMENT

Description Details
Write "STReturnCode1".
Write "STReturnCode1".
Omittable item. Not written.
Write "Reply Code 1".
Write "BYTE".
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Write "0.0".
Omittable item. Not written.
Omittable item. Not written.

Table 5-292 Item Description Example of Element (STReturnCode2)
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.

CLPA

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITOFFSET
REF
COMMENT

Description Details
Write "STReturnCode2".
Write "STReturnCode2".
Omittable item. Not written.
Write "Reply Code 2".
Write "BYTE".
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.
Write "0.8".
Omittable item. Not written.
Omittable item. Not written.

BAP-C2008ENG-001-K
1-293

(a) Item description example of element<p:struct label="STReturnCode"><p:structMember label="ReturnCode1"><p:label2><p:item>ReturnCode1</p:item></p:label2><p:name><p:item>Reply Code 1</p:item></p:name><p:datatype><p:item>BYTE</p:item></p:datatype><p:offset><p:item>0.0</p:item></p:offset></p:structMember><p:structMember label="ReturnCode2"><p:label2><p:item>ReturnCode2</p:item></p:label2><p:name><p:item>Reply Code 2</p:item></p:name><p:datatype><p:item>BYTE</p:item></p:datatype><p:offset><p:item>0.8</p:item></p:offset></p:structMember></p:struct>

CLPA

BAP-C2008ENG-001-K
1-294

5.4.7

ENUM part

5.4.7.1 Overview
The ENUM part (option list) describes information related to the options of values to be set for anelement. Refer to an ENUM part with elements in which you want to set settings based on a list box orelements for which you want to display the meaning of each value at the time a value is read using theutility software. If you want to refer to a description of an ENUM part from an element within a BLOCK
section, write the ENUM part in the same BLOCK section.
The configuration of the ENUM part is the same as that defined for within the COMM_IF section. See
Section 5.3.9.

5.4.7.2 Description example of element
The following shows item description examples of an element of the ENUM part. In the examples
below, the element names are set to "PrmClear_CommPrmClear", "PrmClear_CommPrmNotClear","AllPrmClear_CommPrmClear", and "AllPrmClear_CommPrmNotClear", respectively. In the exampleof CC-Link IE TSN, the element name is set to "enum2".
Table 5-293 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2
CATEGORYNAME
CODE
COMMENT

Description Details
Write "PrmClear_CommPrmClear"
Write "PrmClear_CommPrmClear"
Omittable item. Not written.
Write "Parameter Clear (Communication Prameters Cleared)"Write "38550"
Write "Command code: 9696h"
Table 5-294 Item Description Example of Element

No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2
CATEGORYNAME
CODE
COMMENT

Description Details
Write "PrmClear_CommPrmNotClear"
Write "PrmClear_CommPrmNotClear"
Omittable item. Not written.
Write "Parameter Clear (Communication Prameters Not Cleared)"Write "23130"
Write "Command code: 5A5Ah"
Table 5-295 Item Description Example of Element

No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2
CATEGORYNAME
CODE
COMMENT

Description Details
Write "AllPrmClear_CommPrmClear"
Write "AllPrmClear_CommPrmClear"
Omittable item. Not written.
Write "All Parameter Clear (Communication Prameters Cleared)"Write "39270"
Write "Command code: 9966h"
Table 5-296 Item Description Example of Element

No.
1.
2.
3.
4.
5.
6.

CLPA

Item NameLABELLABEL2
CATEGORYNAME
CODE
COMMENT

Description Details
Write "AllPrmClear_CommPrmNotClear"
Write "AllPrmClear_CommPrmNotClear"
Omittable item. Not written.
Write "All Parameter Clear (Communication Prameters Not Cleared)"Write "21930".
Write "Command code: 55AAh".

BAP-C2008ENG-001-K
1-295

Table 5-297 Item Description Example of Element (enum2)
No.
Item Name
Description Details
1. LABEL
Write "enum2".
2. LABEL2
Write "enum2"
3. CATEGORY
Omittable item. Not written.
4. NAME
Write "Error Outside Input Value Range"
5. CODE
Write "0x105".
6. RELATED_ELE Write "InputError".
7. COMMENT1
Write "A value larger than the maximum value set for the parameter has been input.".
8. COMMENT2
Write "Review the input or review the parameter setting.".
[Note] This description example can be used with CC-Link IE TSN only.
(a) Item description example of element<p:enum label="enumPrmClearMode"><p:enumMember label="PrmClear_CommPrmClear"><p:label2><p:item>PrmClear_CommPrmClear</p:item></p:label2><p:name><p:item>Parameter Clear (Communication Prameters
Cleared)</p:item></p:name><p:code><p:item>38550</p:item></p:code><p:comment><p:item> Command code:9696h</p:item></p:comment></p:enumMember><p:enumMember label="PrmClear_CommPrmNotClear"><p:label2><p:item>PrmClear_CommPrmNotClear</p:item></p:label2><p:name><p:item>Parameter Clear (Communication Prameters Not
Cleared)</p:item></p:name><p:code><p:item>23130</p:item></p:code><p:comment><p:item> Command code:5A5Ah</p:item></p:comment></p:enumMember><p:enumMember label="AllPrmClear_CommPrmClear"><p:label2><p:item>AllPrmClear_CommPrmClear</p:item></p:label2><p:name><p:item>All Parameter Clear (Communication Prameters
Cleared)</p:item></p:name><p:code><p:item>39270</p:item></p:code><p:comment><p:item> Command code:9966h</p:item></p:comment></p:enumMember><p:enumMember label="AllPrmClear_CommPrmNotClear"><p:label2><p:item>AllPrmClear_CommPrmNotClear</p:item></p:label2><p:name><p:item>All Parameter Clear (Communication Prameters Not
Cleared)</p:item></p:name><p:code><p:item>21930</p:item></p:code><p:comment><p:item> Command code:55AAh</p:item></p:comment></p:enumMember></p:enum><p:enum label="ErrorCodeList"><p:enumMember label="enum2"><p:label2><p:item>enum2</p:item></p:label2><p:name><p:item>Error Outside Input Value Range</p:item></p:name><p:code><p:item>0x105</p:item></p:code><p:relatedEle><p:item>InputError</p:item></p:relatedEle><p:comment index="1"><p:item>A value larger than the maximum value set for the parameter has been
input. </p:item></p:comment><p:comment index="2"><p:item>Review the input or review the parameter setting. </p:item></p:comment></p:enumMember></p:enum>

CLPA

BAP-C2008ENG-001-K
1-296

5.4.8COMMAND_ARGUMENT part

5.4.8.1 Overview
The COMMAND_ARGUMENT part (command argument list) describes information related tocommand arguments. When you want to refer to a description in a COMMAND_ARGUMENT part froman element within the BLOCK section, write the COMMAND_ARGUMENT part in the same BLOCK
section.
The configuration of the COMMAND_ARGUMENT part is the same as that defined for within the
COMM_IF section. See Section 5.3.10.

5.4.8.2 Description example of element
The following shows a description example for a case where the element is set to "PrmClearMode".
Table 5-298 Item Description Example of Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESSASSIGNREF
COMMENT

Description Details
Write "PrmClearMode"
Write "PrmClearMode"
Omittable item. Not written.
Write "Prameter Clear Mode"
Write "UINT16"
Omittable item. Not written.
Write a reference to the ENUM part "enumPrmClearMode"
Omittable item. Not written.
Omittable item. Not written.
Write "W"
Omittable item. Not written.
Omittable item. Not written.
Omittable item. Not written.

(a) Item description example of element<p:commandArgumentMember label="PrmClearMode"><p:label2><p:item>PrmClearMode</p:item></p:label2><p:name><p:item>Prameter Clear Mode</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:range><p:enumRefItem>enumPrmClearMode</p:enumRefItem></p:range><p:access><p:item>W</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-297

5.4.9CONDITION Parts

5.4.9.1 Overview
In CONDITION Parts describes conditional expressions for when the value of items of elementschange due to the current value of other elements. Conditional expressions describe reference toelements used for conditional determination and the condition specified range for those elements, aswell as the results when it is true for each of the conditions specified range.
CONDITION Parts are, unlike the basic structure of parts shown in Section 4.2.3, composed of asingle conditionVariable part and several conditionMemmber parts. The structure of CONDITION Parts
is shown in Figure 5-35.
CONDITION Parts
conditionVariable partconditionMember part･･･
conditionMember part
Figure 5-35 Structure of CONDITION Parts
The structure of conditionVariable parts of CONDITION Parts is shown in Figure 5-36, and thestructure of conditionMemmber parts is shown in Figure 5-37.
conditionVariable part
CONDITIONXVARIABLE item
CONDITIONXVARIABLE item･･･
CONDITIONXVARIABLE item
Figure 5-36 Structure of conditionVariable parts in CONDITION Parts
conditionMember part

CLPA

CONDITIONx itemRESULTx item

CONDITIONx itemRESULTx item

CONDITIONx itemRESULTx item

BAP-C2008ENG-001-K
1-298

･
･
･

･
･
･

Figure 5-37 Structural definition of conditionMemmber parts in CONDITION Parts
Write 1 conditionVariable part/conditionMemmber part as 1 XML element. For the detailed description
specifications of each element, see Section 5.4.9.3.
Table 5-299 List of conditionVariable parts of CONDITION Parts
No.

Element Name

1.

CONDITIONXVARIA
BLE

Description Details
Writes reference to elements used for conditional
judgment.
When using multiple elements for conditional judgment,
write multiple CONDITIONXVARIABLE items in
conditionVariable parts.

Required/Optional
Required

Table 5-300 List of conditionMember parts of CONDITION Parts
No.

Element Name

1.

CONDITIONx

2

RESULTx

CLPA

Description Details
Writes the range of conditions specified.
If describing multiple ranges of conditions specified, it
writes multiple CONDITIONx items in
conditionMemmber parts.
Writes the value applied when conditions are satisfied.
If describing multiple results, it writes multiple RESULTx
items in conditionMemmber parts.

Required/Optional
Required

Required

BAP-C2008ENG-001-K
1-299

5.4.9.2 XML format of CONDITION Parts
In XML formats, CONDITION Parts are described as XML elements of XML element name "condition".
A list of condition element attributes is shown in Table 5-301, and a list of XML elements is shown in
Table 5-302.
Table 5-301 List of condition element attributes
No.

Element Name

1.

label

2

conditionNumber

3

resultNumber

Description Details
Writes labels that identify CONDITION parts. (See
4.3.1.19)(Example: "ParamCondition1")
Writes the number of conditions used in conditional
judgment with conditional expressions written in these
CONDITION Parts. It writes as many
CONDITIONXVARIABLE items/CONDITIONx items as
are shown here in the conditionVariable
parts/conditionMemmber parts in this CONDITION Part.
Writes the number of results shown by conditional
judgement with conditional expressions written in these
CONDITION Parts. It shows as many RESULTx items
as are shown here in the conditionMember parts in this
CONDITION Part.

Required/Optional
Required

Required

Required

Table 5-302 List of XML subelements of the condition element
No.
1.

XMLElement Namecomment2

conditionVariable3

conditionMember

Description Details
Writes comments on CONDITION Parts. (See 4.3.1.6)
Writes references to elements used in conditional
judgment of CONDITION Parts.
Writes results that apply as specified range of conditions
used for conditional judgement of CONDITION Parts.

Required/Optional
Optional
Required
RequiredconditionVariable parts and conditionMemmber parts of CONDITION Parts are written as the XML
elements "conditionVariable" or "conditionMember" in XML format. A list of XML subelements ofconditionVariable parts are shown in Table 5-304. conditionVariable parts and conditionMemmber
parts do not have such attributes as "label".
Table 5-303 List of XML subelements of conditionVariable parts
No. XML Element Name
1. conditionXVariable

Description Details
Writes CONDITIONXVARIABLE.

Table 5-304 List of XML subelements of conditionMember parts
No. XML Element Name
1. conditionX
2 resultX

Description Details
Writes CONDITIONx item.
Writes RESULTx item.

A list of the attributes of the conditionXVariable element, conditionX element, and resultX element are
shown in Table 5-305 to Table 5-307.
Table 5-305 List of attributes of the conditionXVariable element
No.
1.

CLPA

Attribute Name
index

Description Details
Following the order of arrangement of multiple
conditionXVariable elements written, writes integers inorder from 1 to a maximum of 32.

Required/Optional
Required

BAP-C2008ENG-001-K
1-300

Table 5-306 List of attributes of the conditionXVariable element
No.
1.

Attribute Name
index

Description Details
Writes the same value as the index value of thecorresponding conditionXVariable element.

Required/Optional
Required

Table 5-307 List of attributes of the conditionXVariable element
No.
1.

Attribute Name
index

Description Details
Following the order of arrangement of multiple
conditionXVariable elements written, writes integers inorder from 1 to a maximum of 32.

Required/Optional
Required

CONDITION parts are described in the following format.
<p:condition label=“Write according to the details of Table 5-301 “Attribute label””
conditionNumber=“Write according to the details of Table 5-301 “AttributeconditionNumber””
resultNumber=“Write according to the details of Table 5-301 “AttributeresultNumber”"><p:comment>“Write according to the details of Table 5-302 “XML element
comment””</p:comment><p:conditionVariable><p:conditionXVariable index="1">“Write according to the details of Table 5-303 “XML element
conditionXVariable””</p: conditionXVariable><p:conditionXVariable index="2">“Write according to the details of Table 5-303 “XML element
conditionXVariable””</p: conditionXVariable>::
p:conditionVariable><p:conditionMember><p:conditionX index="1">“Write according to the details of Table 5-304 “XML element conditionX””</p: conditionX><p:conditionX index="2">“Write according to the details of Table 5-304 “XML element conditionX””</p: conditionX>::<p:resultX index="1">“Write according to the details of Table 5-304 “XML element resultX””</p:resultX><p:resultX index="2">“Write according to the details of Table 5-304 “XML element resultX””</p:resultX>::</p:conditionMember><p:conditionMember>::</p:conditionMember>::</p:condition>

CLPA

BAP-C2008ENG-001-K
1-301

5.4.9.3 Description details of elements(1) Item descriptions of conditionVariable part
Table 5-308 Item description specifications of conditionVariable parts
No.

1.

Element Name

CONDITIONXVARIABLE

Description Details
Writes references to elements used for conditional judgment.
When using multiple elements for conditional judgment,
write multiple CONDITIONXVARIABLE items in conditionVariable parts.
Writes references as follows.
 Writes reference to the value used in conditional judgment. Cannot
write reference to other items.
 Cannot write references to structural type, array type, or constant typeelements.
 Cannot omit details of description.
 Can only write reference to elements of BLOCK_PARAMETER parts.
Can also write references elements of BLOCK_PARAMETER of parts
that differ from the reference source. Cannot write references toelements of sections that differ from the reference source.
 Cannot reference elements that apply results of this CONDITION part(value of RESULTx item) as elements used for conditional judgment of
the reference source CONDITION part. In other words, it cannot write
elements of BLOCK_PARAMETER parts that reference CONDITION
parts as the reference source in CONDITIONXVARIABLE item of thesame CONDITION parts.

Write a maximum of 32 CONDITIONXVARIABLE items in 1 conditionVariable part. In XML format, it
has index as an attribute of conditionXVariable of XML elements, and grants integer values from 1 to
32 in the order those items are written.

(a) Example item description of conditionVariable part<p:conditionVariable><p:conditionXVariable index="1"><p:item>BlockParameter.AvgOrSample.VALUE</p:item></p:conditionXVariable><p:conditionXVariable index="2"><p:item>BlockParameter.TimeOrCount.VALUE</p:item></p:conditionXVariable></p:conditionVariable>

CLPA

BAP-C2008ENG-001-K
1-302

(2) Item descriptions of conditionMemmber parts
Table 5-309 Item description specifications of conditionMemmber parts
No.

Element Name

1.

CONDITIONx

2

RESULTx

Description Details
Describes the range of conditions for conducting conditional judgment.
 The following conventions are available as ranges of conditions.
1. Describing range of conditions with numerical values
Specifies judgment conditions by numerical value. When enumerating
multiple values, uses "," (commas), and when indicating the range ofvalues, uses "[","]","(", and ")". (See [4] of Table 4-23)
Ex:
2 ≤ x ≤ 10 ⇒ [2,10]
2 < x < 10 ⇒ (2,10)
x < 10 ⇒ (,10)
x = 10 or 20 ≤ x < 30 or x = 40 ⇒ 10,[20,30),40
2. Describing range of conditions using values of other elements
Can perform conditional judgment with values of other elements of
BLOCK_PARAMETER using reference source index by "$()"Ex:
When judging whether a label name is below the value of the parameterof B, it can write this as[,$(B. VALUE)]
Describing string type conditions
3. Writes the string being judged as a judgment condition. When judging
string type, it is possible to specify conditions by perfect match with thestring. Range cannot be specified.
 Values usable in specifying the range of conditions shall be those values
allowed by DATATYPE of elements used in conditional judgment(elements written in CONDITIONXVARIABLE item). (Ex: If the DATATYPE
is word, hexadecimal numbers with "0x" can be used.) If this item is omitted, corresponding values are not judged.
 When using the fact that the value of the element referenced with theconditionVariable part has not been set (i.e., the item is not described),
write the keyword "EMPTY".
 In the final conditionMemmber part written, writes the keyword "DEFAULT"
in all CONDITIONx items. CondtionMemmber parts written this way
represent cases in which all conditional judgments were false. DEFAULT
must be written. Therefore, in the final conditionMemmber part written in
CONDITION part, be certain to perform description by this DEFAULT.
Write the values (results) applicable when conditions are satisfied.
 When writing multiple results, write multiple RESULTx items in theconditionMemmber part.
 Values written here must be writable in the reference source item
referencing this item (the item these results are applied to).

A maximum of 32 CONDITIONx items and RESULTx items can be written in 1 conditionMemmber
part. In XML format, they have index as attributes of the XML elements conditionX and ResultX, andgrant integer values from 1 to 32 in the order those items are written. When indicating individual
CONDITIONx items or RESULTx items, for convenience, replace the "x" part of those items with index
values, and denote them as CONDITION1, CONDITION2, ~CONDITION32, etc. Also when writing areference to RESULTx items in items of elements of BLOCK_PARAMETER, denote item names as
RESULT1, RESULT2, ~RESULT32.
The condition range specifications written in CONDITIONx items indicate the range of values of
elements referenced from CONDITIONXVARIABLE which holds an index of the same values asconditionVariable part.
Those CONDITIONx items correspond to the CONDITIONXVARIABLE items of the conditionVariable
part which holds the same index values, and if the values of elements written in
CONDITIONXVARIABLE item are within the range written in this item, judge it as satisfying thecondition.
CLPA

BAP-C2008ENG-001-K
1-303

When multiple CONDITIONXVARIABLE items are written in the conditionVariable part, judge multiple
conditions of those CONDITIONx items written in 1 conditionMemmber part as AND conditions. In
other words, when all conditions of CONDITIONx items written in the conditionMemmber part aresatisfied, the value of the RESULTx item written in that conditionMemmber part is applied as theresult.
Conditional judgement is performed in the order written in conditionMemmber parts. Therefore, when it
matches conditions written in multiple conditionMemmber parts, the results of the conditionMemmber
part written first are applied. It is possible to write the same values for all RESULTx items in multiple
conditionMemmber parts, and by changing the judgment conditions of CONDITIONx item, write
judgment by OR condition of multiple judgment conditions.

(a) Example of item description of a conditionMemmber part<p:conditionMember><p:conditionX index="1"><p:item>1</p:item></p:conditionX><p:conditionX index="2"><p:item>0</p:item></p:conditionX><p:resultX index="1"><p:item>NA</p:item></p:resultX><p:resultX index="2"><p:item>RW</p:item></p:resultX></p:conditionMember>

5.4.9.4 Writing conditional expressions
Conventions for conditional expressions of CONDITION parts are introduced here.
An example conditional expression is shown in Figure 5-38, and the relationship between conditional
expression (CONDITION) and parameters are shown here (Figure 5-39).
In the example in Figure 5-38, the number of elements used in conditional judgement (reference
source from CONDITIONXVARIABLE item) is 2, and the number of results from the conditional
judgment (RESULTx) is also 2.
Row 1 has the details written of each item of conditionVariable part, and rows 2 onwards have thedetails written of each item of conditionMemmber part.
When the values of the element written in the CONDITIONXVARIABLE of conditionVariable in the firstrow all match the condition range written in CONDITIONx items of conditionMemmber parts in rows 2
onward, the values written in RESULTx of those conditionMemmber are applied. This result is appliedby referencing from items of parameters written in BLOCK_PARAMETER.

Figure 5-38 Example of conditional expression (CONDITION)

CLPA

BAP-C2008ENG-001-K
1-304

Reference toelements used
for conditional
judgment
Condition Range
Specification

Figure 5-39 Relationship between conditional expressions (CONDITION) and parameters

Related items are written about below.

(1) References to elements used in conditional judgment (CONDITIONXVARIABLE items ofconditionVariable parts)
Specify the value used for conditional judgment by writing a reference to the values of the element
used for conditional judgment in CONDITIONXVARIABLE items of conditionVariable parts. See
Section 5.4.9.3 (1) for details about this convention.
(2) Condition range specification (CONDITIONx items of conditionMemmber parts)
Write judgment conditions of the value specified in (1) above using numerical values, strings, or otherelements. If the value is within the range written in this item it is judge as satisfying the condition. See
Section 5.4.9.3 (2) for details about this convention.
(3) Result (RESULTx item of conditionMemmber parts)
The value of the results are applied as the values of the item that references this result. Therefore, thevalues written here must be values writable with items of the reference source. In the example in
Figure 5-39, because both results are referenced from the ACCESS item, the value of the RESULTx
item is written according to the convention of the ACCESS item.
(4) Reference to results
Write references to results (RESULTx) in items that apply the results of CONDITION part.
Results can only be referenced from elements of BLOCK_PARAMETER parts. They cannot bereferenced from anything else.
In the example in Figure 5-39, the value of AvgOrSample and TimeOrCount of BLOCK_PARAMETER
part are judged, and the values applied to the ACCESS item of AvgTime and AvgCount are
determined. This proceeds as follows.
• If the value of AvgOrSample is 0 ⇒ ACCESS item of AvgTime is NA and ACCESS item of AvgCount isNA• If the value of AvgOrSample is 1 and the value of TimeOrCount is 0 ⇒ ACCESS item of AvgTime is NA
and ACCESS item of AvgCount is RW• If the value of AvgOrSample is 1 and the value of TimeOrCount is 1 ⇒ ACCESS item of AvgTime is RW
and ACCESS item of AvgCount is NA• Any other situation ⇒ ACCESS item of AvgTime is NA and ACCESS item of AvgCount is NA

CLPA

BAP-C2008ENG-001-K
1-305

5.5

Parts and Elements with Defined Applications
In CSP+ specifications, parts other than the FILE_INFO, DEVICE_INFO, COMM_IF_INFO, and
BLOCK_INFO parts do not specify elements that should be commonly included for all modules.
However, when a module has certain functions or information, there are rules related to the elements
used to express such functions or information. These rules exist as optional description specifications.
This section describes the specifications of such elements.
The applications of the elements described in this section are predetermined, and thus the labelnames defined in this section cannot be used for any other application. Additionally, while thespecifications of these optional descriptions indicate that descriptions of the functions or information
described in this section are preferably included in accordance with the specifications described in thischapter when present, the creator of the CSP+ file is free to decide whether or not to include thedescriptions. If the descriptions are included, however, they must be described in accordance with thespecifications described herein. For the network availability for each application, see Table 5-310.
Table 5-310 Network Usage List for Each Application
Application

Network
CC-Link IEF
Ethernet*1
Section 5.5.1-

CC-Link IE TSN
Elements related to system area
Section 5.5.1
Parts and elements related toparameter initial settings based on
Section 5.5.2 Section 5.5.2
initial settings
Parts and elements related to error
Section 5.5.3
history information acquisition
METHOD specifications for
conducting error checks of
Section 5.5.4 Section 5.5.4
equipment
Parts and elements indicating
parameters for safety communication
Section 5.5.5
Section 5.5.10.3
function
MESSAGE specifications for writing
the safety communication function
Section 5.5.6
Section 5.5.10.4
parameter
Conventions of read/write capable
Section 5.5.7
parameters using parameter IDs
Parts and elements related to energy
Section 5.5.8 Section 5.5.8
Section 5.5.8
management information acquisition
Convention related to status code
Section 5.5.9
Parts and elements related to error
Section 5.5.10.1
related information
Convention related to MESSAGE forslave station parameter automatic
Section 5.5.10.2
setting
Parts and elements related to theSection 5.5.10.5
main module and extension modules*: Will not be able to be used on the target network.
*1 For the Ethernet connected device, this indicates the CC-Link IE Field Network Basic communication and
SLMP communication.

CLPA

CC-Link
Section 5.5.1

BAP-C2008ENG-001-K
1-306

5.5.1Elements related to system area
The specifications related to the system area is specified in CC-Link, CC-Link IE Field Network, and
CC-Link IE TSN. This section describes the specifications of elements in a case where a flag of thesystem area is to be described.

5.5.1.1 Overview
A flag of the system area is described in the COMM_IF_INPUT or COMM_IF_OUTPUT part. Figure5-40 shows images of the respective structures when a system area flag is described for a case where
the communication interface is CC-Link, CC-Link IE Field Network, and CC-Link IE TSN.

CLPA

BAP-C2008ENG-001-K
1-307

COMM_IF section
COMM_IF_INPUT part
For CC-Link

For CC-Link IE Field Network

InitialDataProcessReq element

WarningStatus element

InitialDataSetComp element

InitialDataProcessReq element

ErrorStatus element

InitialDataSetComp element

RemoteReady element

ErrorStatus element

MessageTransReceive element

RemoteReady element

MessageHandshakeRX element

For CC-Link IE TSN
WarningStatus element
ErrorStatus element
RemoteReady element

COMM_IF section
COMM_IF_OUTPUT part
For CC-Link

For CC-Link IE Field Network

InitialDataProcessComp element

InitialDataProcessComp element

InitialDataSetReq element

InitialDataSetReq element

ErrorResetReq element

ErrorResetReq element

MessageTransReq element
MessageHandshakeRY element

For CC-Link IE TSN
ErrorResetReq element

Figure 5-40 Image of Structure When System Area Is Described

CLPA

BAP-C2008ENG-001-K
1-308

Table 5-311, Table 5-312 and Table 5-313 list the elements described in the COMM_IF_INPUT part.
For the detailed description specifications of each element, see Section 5.5.1.2.
Table 5-311 Element List When the Communication Interface Described in the COMM_IF_INPUT Part
is CC-Link
No.
1.
2.
3.
4.
5.
6.

Element Name
InitialDataProcessReq
InitialDataSetComp
ErrorStatus
RemoteReady
MessageTransReceive
MessageHandshakeRX

Description Details
Describes the initial data processing request flag.
Describes the initial data setting completed flag.
Describes the error status flag.
Describes the remote ready flag.
Describes message transmission reception.
Describes the input_message handshake flag.

Required/Optional
Optional
Optional
Optional
Optional
Optional
Optional

Table 5-312 Element List When the Communication Interface Described in the COMM_IF_INPUT Partis the CC-Link IE Field Network
No.
Element Name
1. WarningStatus
2.

InitialDataProcessReq

3.
4.
5.

InitialDataSetComp
ErrorStatus
RemoteReady

Description Details
Describes the warning status flag.
Describes the initial data processing requirement
flag.
Describes the initial data setting completed flag.
Describes the error status flag.
Describes the remote ready flag.

Required/Optional
Optional
Optional
Optional
Optional
Optional

Table 5-313 Element List When the Communication Interface Described in the COMM_IF_INPUT Part
is CC-Link IE TSN
No.
Element Name
1. WarningStatus
2. ErrorStatus
3. RemoteReady

Description Details
Describes the warning status flag.
Describes the error status flag.
Describes the remote ready flag.

Required/Optional
Optional
Optional
Optional

Table 5-314, Table 5-315 and Table 5-316 list the elements described in the COMM_IF_OUTPUT part.
For the detailed description specifications of each element, see Section 5.5.1.3.
Table 5-314 Element List When the Communication Interface Described in the COMM_IF_OUTPUT
Part is CC-Link
No.
1.
2.
3.
4.
5.

Element Name
InitialDataProcessComp
InitialDataSetReq
ErrorResetReq
MessageTransReq
MessageHandshakeRY

Description Details
Describes the initial data processing completed flag.
Describes the initial data setting request flag.
Describes the error reset request flag.
Describes message transmission request.
Describes the message handshake flag.

Required/Optional
Optional
Optional
Optional
Optional
Optional

Table 5-315 Element List When the Communication Interface Described in the COMM_IF_OUTPUT
Part is the CC-Link Field Network
No.
Element Name
1. InitialDataProcessComp
2. InitialDataSetReq
3. ErrorResetReq

Description Details
Describes the initial data request completed flag.
Describes the initial data setting request flag.
Describes the error reset request flag.

Required/Optional
Optional
Optional
Optional

Table 5-316 Element List When the Communication Interface Described in the COMM_IF_OUTPUT
Part is CC-Link IE TSN
No.
Element Name
1. ErrorResetReq

CLPA

Description Details
Describes the error reset request flag.

Required/Optional
Optional

BAP-C2008ENG-001-K
1-309

5.5.1.2 Description details of elements described in COMM_IF_INPUT part
• Description of system area flag elements when the communication interface is CC-Link
The following describes the description details of the elements described in the COMM_IF_INPUT partwhich are system area flag elements described when the communication interface is CC-Link.
(1) Item description of InitialDataProcessReq element
Table 5-317 Item Description Example of InitialDataProcessReq Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "InitialDataProcessReq".
Write "InitialDataProcessReq". [Recommended specifications]Write "System area". [Recommended specifications]Write "Initial Data Processing Request Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified. Write a value in the same manner as the regular
COMM_IF_INPUT part. Note that this item is normally not omitted, and thewritten value is the corresponding remote input address.
Not specified. Write a value in the same manner as the regular
COMM_IF_INPUT part.
Not specified. Write a value in the same manner as the regular
COMM_IF_INPUT part. Normally not written.
Not specified. Write a value in the same manner as the regular
COMM_IF_INPUT part.

(a) Item description example of InitialDataProcessReq element<p:commIfInputMember label="InitialDataProcessReq"><p:label2><p:item>InitialDataProcessReq</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Initial Data Processing Request Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX18</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-310

(2) Item description of InitialDataSetComp element
Table 5-318 Item Description Specifications of InitialDataSetComp Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "InitialDataSetComp".
Write "InitialDataSetComp". [Recommended specifications]Write "System area". [Recommended specifications]Write "Initial Data Processing Complete". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part. Notethat this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.

(a) Item description example of InitialDataSetComp element<p:commIfInputMember label="InitialDataSetComp"><p:label2><p:item>InitialDataSetComp</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Initial Data Processing Complete</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX19</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-311

(3) Item description of ErrorStatus element
Table 5-319 Item Description Specifications of ErrorStatus Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "ErrorStatus".
Write "ErrorStatus". [Recommended specifications]Write "System area". [Recommended specifications]Write "Error Status Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part. Notethat this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified. Write a value in the same manner as the regular
COMM_IF_INPUT part.

(a) Item description example of ErrorStatus element<p:commIfInputMember label="ErrorStatus"><p:label2><p:item>ErrorStatus</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Error Status Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX1A</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-312

(4) Item description of RemoteReady element
Table 5-320 Item Description Specifications of RemoteReady Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "RemoteReady".
Write "RemoteReady". [Recommended specifications]Write "System area". [Recommended specifications]Write "Remote Ready". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part. Notethat this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.

(a) Item description example of RemoteReady element<p:commIfInputMember label="RemoteReady"><p:label2><p:item>RemoteReady</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Remote Ready</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX1B</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-313

(5) Item description of MessageTransReceive element
Table 5-321 Item Description Specifications of MessageTransReceive Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "MessageTransReceive".
Write "MessageTransReceive". [Recommended specifications]Write "System area". [Recommended specifications]Write "Message Transmission Receive". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part. Notethat this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.

(a) Item description example of MessageTransReceive element<p:commIfInputMember label="MessageTransReceive"><p:label2><p:item>MessageTransReceive</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Message Transmission Receive</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX1C</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-314

(6) Item description of MessageHandshakeRX element
Table 5-322 Item Description Specifications of MessageHandshakeRX Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "MessageHandshakeRX".
Write "MessageHandshakeRX". [Recommended specifications]Write "System area". [Recommended specifications]Write "Input_Message Handshake Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part. Notethat this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.

(a) Item description example of MessageHandshakeRX element<p:commIfInputMember label="MessageHandshakeRX"><p:label2><p:item>MessageHandshakeRX</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Input_Message Handshake Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX1D</p:item></p:assign></p:commIfInputMember>• Description of system area flag elements when the communication interface is the CC-Link IE
Field Network
The following describes the description details of the elements described in the COMM_IF_INPUT partwhich are system area flag elements described when the communication interface is the CC-Link IE
Field Network.

CLPA

BAP-C2008ENG-001-K
1-315

Item description of WarningStatus element(7)

Table 5-323 Item Description Specifications of WarningStatus Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "WarningStatus".
Write "WarningStatus". [Recommended specifications]Write "System area". [Recommended specifications]Write "Warning Status Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part. Notethat this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.

(a) Item description example of WarningStatus element<p:commIfInputMember label="WarningStatus"><p:label2><p:item>WarningStatus</p:item></p:label2><p:category><p:item> System area </p:item></p:category><p:name><p:item>Warning Status Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX18</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-316

(8) Item description of InitialDataProcessReq element
Table 5-324 Item Description Example of InitialDataProcessingReq Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "InitialDataProcessReq".
Write "InitialDataProcessReq". [Recommended specifications]Write "System area". [Recommended specifications]Write "Initial Data Processing Request Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part. Notethat this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.

(a) Item description example of InitialDataProcessReq element<p:commIfInputMember label="InitialDataProcessReq"><p:label2><p:item>InitialDataProcessReq</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Initial Data Processing Request Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX18</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-317

(9) Item description of InitialDataSetComp element
Table 5-325 Item Description Specifications of InitialDataSetComp Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "InitialDataSetComp".
Write "InitialDataSetComp". [Recommended specifications]Write "System area". [Recommended specifications]Write "Initial Data Setting Complete Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part. Notethat this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.

(a) Item description example of InitialDataSetComp element<p:commIfInputMember label="InitialDataSetComp"><p:label2><p:item>InitialDataSetComp</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Initial Data Setting Complete Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX19</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-318

(10) Item description of ErrorStatus element
Table 5-326 Item Description Specifications of ErrorStatus Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "ErrorStatus".
Write "ErrorStatus". [Recommended specifications]Write "System area". [Recommended specifications]Write "Error Status Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part. Notethat this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.

(a) Item description example of ErrorStatus element<p:commIfInputMember label="ErrorStatus"><p:label2><p:item>ErrorStatus</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Error Status Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX1A</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-319

(11) Item description of RemoteReady element
Table 5-327 Item Description Specifications of RemoteReady Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "RemoteReady"Write "RemoteReady". [Recommended specifications]Write "System area". [Recommended specifications]Write "RemoteReady". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part. Notethat this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.

(a) Item description example of RemoteReady element<p:commIfInputMember label="RemoteReady"><p:label2><p:item>RemoteReady</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Remote Ready</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX1B</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-320

• Description of system area flag elements when the communication interface is CC-Link IE TSN
The following describes the description details of the elements described in the COMM_IF_INPUT partwhich are system area flag elements described when the communication interface is CC-Link IE TSN.
(12) Item description of WarningStatus element
Table 5-328 Item Description Example of WarningStatus Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "WarningStatus".
Write "WarningStatus". [Recommended specifications]Write "System area". [Recommended specifications]Write "Warning Status Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Note that this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.

(a) Item description example of WarningStatus element<p:commIfInputMember label="WarningStatus"><p:label2><p:item>WarningStatus</p:item></p:label2><p:category><p:item>System Area</p:item></p:category><p:name><p:item>Warning Status Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX18</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-321

(13) Item description of ErrorStatus element
Table 5-329 Item Description Specifications of ErrorStatus Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "ErrorStatus".
Write "ErrorStatus". [Recommended specifications]Write "System area". [Recommended specifications]Write "Error Status Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Note that this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.

(a) Item description example of ErrorStatus element<p:commIfInputMember label="ErrorStatus"><p:label2><p:item>ErrorStatus</p:item></p:label2><p:category><p:item>System Area</p:item></p:category><p:name><p:item>Error Status Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX1A</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-322

(14) Item description of RemoteReady element
Table 5-330 Item Description Specifications of RemoteReady Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "RemoteReady".
Write "RemoteReady". [Recommended specifications]Write "System area". [Recommended specifications]Write "Remote Ready". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Note that this item is normally not omitted, and the written value is thecorresponding remote input address.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_INPUT part.

(a) Item description example of RemoteReady element<p:commIfInputMember label="RemoteReady"><p:label2><p:item>RemoteReady</p:item></p:label2><p:category><p:item>System Area</p:item></p:category><p:name><p:item>Remote Ready</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX1B</p:item></p:assign></p:commIfInputMember>

CLPA

BAP-C2008ENG-001-K
1-323

5.5.1.3 Description details of elements described in COMM_IF_OUTPUT part
• Description of system area flag elements when the communication interface is CC-Link
The following describes the description details of the elements described in the COMM_IF_OUTPUT partwhich are system area flag elements described when the communication interface is CC-Link.
(1) Item description of InitialDataProcessComp element
Table 5-331 Item Description Example of InitialDataProcessComp Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "InitialDataProcessComp".
Write "InitialDataProcessComp". [Recommended specifications]Write "System area". [Recommended specifications]Write "Initial Data Processing Complete Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Note that this item is normally not omitted, and the written value is thecorresponding remote output address.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.

(a) Item description example of InitialDataProcessComp element<p:commIfOutputMember label="InitialDataProcessComp"><p:label2><p:item>InitialDataProcessComp</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Initial Data Processing Complete Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RY18</p:item></p:assign></p:commIfOutputMember>

CLPA

BAP-C2008ENG-001-K
1-324

(2) Item description of InitialDataSetReq element
Table 5-332 Item Description Specifications of InitialDataSetReq Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "InitialDataSetReq".
Write "InitialDataSetReq". [Recommended specifications]Write "System area". [Recommended specifications]Write "Initial Data Setting Request Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Note that this item is normally not omitted, and the written value is thecorresponding remote output address.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.

(a) Item description example of InitialDataSetReq element<p:commIfOutputMember label="InitialDataSetReq"><p:label2><p:item>InitialDataSetReq</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Initial Data Setting Request Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RY19</p:item></p:assign></p:commIfOutputMember>

CLPA

BAP-C2008ENG-001-K
1-325

(3) Item description of ErrorResetReq element
Table 5-333 Item Description Specifications of ErrorResetReq Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "ErrorResetReq".
Write "ErrorResetReq". [Recommended specifications]Write "System area". [Recommended specifications]Write "Error Reset Request Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Note that this item is normally not omitted, and the written value is thecorresponding remote output address.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.

(a) Item description example of ErrorResetReq element<p:commIfOutputMember label="ErrorResetReq"><p:label2><p:item>ErrorResetReq</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Error Reset Request Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RY1A</p:item></p:assign></p:commIfOutputMember>

CLPA

BAP-C2008ENG-001-K
1-326

(4) Item description of MessageTransReq element
Table 5-334 Item Description Specifications of MessageTransReq Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "MessageTransReq".
Write "MessageTransReq". [Recommended specifications]Write "System area". [Recommended specifications]Write "Message Transmission Request". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Note that this item is normally not omitted, and the written value is thecorresponding remote output address.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.

(a) Item description example of MessageTransReq element<p:commIfOutputMember label="MessageTransReq"><p:label2><p:item>MessageTransReq</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Message Transmission Request</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RY1C</p:item></p:assign></p:commIfOutputMember>

CLPA

BAP-C2008ENG-001-K
1-327

(5) Item description of MessageHandshakeRY element
Table 5-335 Item Description Specifications of MessageHandshakeRY Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "MessageHandshakeRY".
Write "MessageHandshakeRY". [Recommended specifications]Write "System area". [Recommended specifications]Write "Output_Message Handshake Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Note that this item is normally not omitted, and the written value is thecorresponding remote output address.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.

(a) Item description example of MessageHandshakeRY element<p:commIfOutputMember label="MessageHandshakeRY"><p:label2><p:item>MessageHandshakeRY</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Output_Message Handshake Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RY1D</p:item></p:assign></p:commIfOutputMember>• Description of system area flag elements when the communication interface is the CC-Link IE
Field Network
The following describes the description details of the elements described in the COMM_IF_OUTPUT
part which are system area flag elements described when the communication interface is the CC-Link
IE Field Network.
• Description of system area flag elements when the communication interface is CC-Link Field
Network
The following describes the description details of the elements described in the COMM_IF_OUTPUT
part which are system area flag elements described when the communication interface is CC-Link
Field Network.

CLPA

BAP-C2008ENG-001-K
1-328

(6) Item description of InitialDataProcessComp element
Table 5-336 Item Description Example of InitialDataProcessComp Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "InitialDataProcessComp".
Write "InitialDataProcessComp". [Recommended specifications]Write "System area". [Recommended specifications]Write "Initial Data Processing Complete Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Note that this item is normally not omitted, and the written value is thecorresponding remote output address.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.

(a) Item description example of InitialDataProcessComp element<p:commIfOutputMember label="InitialDataProcessComp"><p:label2><p:item>InitialDataProcessComp</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Initial Data Processing Complete Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RY18</p:item></p:assign></p:commIfOutputMember>

CLPA

BAP-C2008ENG-001-K
1-329

(7) Item description of InitialDataSetReq element
Table 5-337 Item Description Specifications of InitialDataSetReq Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "InitialDataSetReq".
Write "InitialDataSetReq". [Recommended specifications]Write "System area". [Recommended specifications]Write "Initial Data Setting Request Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Note that this item is normally not omitted, and the written value is thecorresponding remote output address.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.

(a) Item description example of InitialDataSetReq element<p:commIfOutputMember label="InitialDataSetReq"><p:label2><p:item>InitialDataSetReq</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Initial Data Setting Request Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RY19</p:item></p:assign></p:commIfOutputMember>

CLPA

BAP-C2008ENG-001-K
1-330

(8) Item description of ErrorResetReq element
Table 5-338 Item Description Specifications of ErrorResetReq Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "ErrorResetReq".
Write "ErrorResetReq". [Recommended specifications]Write "System area". [Recommended specifications]Write "Error Reset Request Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified. Write a value in the same manner as the regular
COMM_IF_OUTPUT part. Note that this item is normally not omitted, and thewritten value is the corresponding remote output address.
Not specified. Write a value in the same manner as the regular
COMM_IF_OUTPUT part.
Not specified. Write a value in the same manner as the regular
COMM_IF_OUTPUT part. Normally not written.
Not specified. Write a value in the same manner as the regular
COMM_IF_OUTPUT part.

(a) Item description example of ErrorResetReq element<p:commIfOutputMember label="ErrorResetReq"><p:label2><p:item>ErrorResetReq</p:item></p:label2><p:category><p:item>System area</p:item></p:category><p:name><p:item>Error Reset Request Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RY1A</p:item></p:assign></p:commIfOutputMember>

CLPA

BAP-C2008ENG-001-K
1-331

• Description of system area flag elements when the communication interface is CC-Link IE TSN
The following describes the description details of the elements described in the COMM_IF_OUTPUT partwhich are system area flag elements described when the communication interface is CC-Link IE TSN.
(9) Item description of ErrorResetReq element
Table 5-339 Item Description Specifications of ErrorResetReq Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESS

11.

ASSIGN12.

UI_ATTRIBUTE

13.

REF

14.

COMMENT

Description Details
Write "ErrorResetReq".
Write "ErrorResetReq". [Recommended specifications]Write "System area". [Recommended specifications]Write "Error Reset Request Flag". [Recommended specifications]Write "BOOL".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write "RF".
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Note that this item is normally not omitted, and the written value is thecorresponding remote output address.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.
Normally not written.
Not specified.
Write a value in the same manner as the regular COMM_IF_OUTPUT part.

(a) Item description example of ErrorResetReq element<p:commIfOutputMember label="ErrorResetReq"><p:label2><p:item>ErrorResetReq</p:item></p:label2><p:category><p:item>System Area</p:item></p:category><p:name><p:item>Error Reset Request Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RY1A</p:item></p:assign></p:commIfOutputMember>

CLPA

BAP-C2008ENG-001-K
1-332

5.5.2

Parts and elements related to parameter initialization based on initial settings
CC-Link and the CC-Link IE Field Network define specifications related to parameter initialization
based on initial settings. This section describes the specifications of parts and elements in a casewhere parameter initialization based on initial settings is to be described.

5.5.2.1 Overview
Parameter initialization based on initial settings is described in the METHOD part and
COMM_IF_PARAMETER part. Figure 5-41 shows an image of the structure when parameter
initialization based on initial settings is described. (These specifications are common to both CC-Link
and CC-Link IE Field Network communication interfaces.)

Figure 5-41 Image of Structure When Parameter Initialization Based on Initial Settings Is Described
Table 5-340 shows a list of elements described in the METHOD part. For details of the description
specifications of the elements, see Section 5.5.2.2.
Table 5-340 List of Elements Described in METHOD PartNo.
1.

Element Name
ParamInitialize

Description Details
Describes the method used to initialize parameters
based on initial settings.

Required/Optional
Required

Table 5-341 lists the elements described in the COMM_IF_PARAMETER part. For details of thedescription specifications of the elements, see Section 5.5.2.3.
Table 5-341 List of Elements Described in COMM_IF_PARAMETER PartNo.
1.

Element Name
(Any name)

Description Details
Describes the parameter information to be set byparameter initialization based on initial settings.
Requires description of all parameters subject toinitialization based on initial settings as elements.

Required/Optional
Required

While multiple parts are used to describe parameter initialization based on initial settings, there are no
regulations related to the label name of each part. (The CSP+ file creator can freely assign the labelnames.)
Further, there are no regulations related to the method used to change parameters set by initial
settings. Write the changes in accordance with the description specifications of the METHOD part.

CLPA

BAP-C2008ENG-001-K
1-333

5.5.2.2 Description details of elements described in METHOD part(1) Item description of ParamInitialize element
Table 5-342 Item Description Specifications of ParamInitialize Element
No.
Item Name
1. LABEL
2. LABEL2
3.

CATEGORY

4.

NAME

5.

TARGET

6.
7.
8.
9.
10.
11.
12.

METHOD_TYPE
WRITE_REGISTERWRITE_DATAWRITE_DATATYPE
READ_REGISTER
READ_DATAREAD_DATATYPE

13.

INTERLOCK14.

REQ_FLAG

15.

END_CONDITION16.

ERR_CONDITION17.

ERR_REGISTER18.

ERR_CODE_RANGE

19.

RELATED_METHOD

20.

COMMENT

Description Details
Write "ParamInitialize".
Write "ParamInitialize". [Recommended specifications]
Not specified. Write a value in the same manner as the regular METHOD
part.
Write "Initial Setting". [Recommended specifications]Write "’Part name’.* ". For ‘Part name’, write the label name of the
COMM_IF_PARAMETER part where the parameters specified in Table
5-341 are described.
Write "OTHER".
Write "<$(*.ASSIGN)>".
Write "<$(*.VALLUE)>".
Write "<$(*.DATATYPE)>".
Write prohibited.
Write prohibited.
Write prohibited.
Write that the initial data processing request flag is ON. The description
specifications are the same as those for a regular METHOD part.
Write that the initial data processing completed flag is to be turned ON, andthe initial data setting request flag is to be turned ON, in that order. The
descriptions must be written in this order. The description specifications are
the same as those for a regular METHOD part.
Write that the initial data processing request flag is OFF, and the initial datasetting completed flag is ON, in that order. The descriptions must be written
in this order. The description specifications are the same as those for aregular METHOD part.
Not specified. Write a value in the same manner as the regular METHOD
part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Write prohibited.
Not specified.
Write a value in the same manner as the regular METHOD part.

(a) Item description example of ParamInitialize element<p:methodMember label="ParamInitialize"><p:label2><p:item>ParamInitialize</p:item></p:label2><p:name><p:item>Initial Setting</p:item></p:name><p:target><p:item>PrmTable.*</p:item></p:target><p:methodType><p:item>OTHER</p:item></p:methodType><p:writeRegister><p:item>&lt;$(*.ASSIGN)&gt;</p:item></p:writeRegister><p:writeData><p:item>&lt;$(*.VALUE)&gt;</p:item></p:writeData><p:writeDatatype><p:item>&lt;$(*.DATATYPE)&gt;</p:item></p:writeDatatype><p:interlock><p:item>RX18==ON</p:item></p:interlock><p:reqFlag><p:item>RY18=ON</item><item>RY19=ON</p:item></p:reqFlag><p:endCondition><p:item>RX18==OFF&amp;&amp;RX19==ON</p:item></p:endCondition><p:comment><p:item>Batch Parameter Setting with Initial
Setting</p:item></p:comment></p:methodMember>

CLPA

BAP-C2008ENG-001-K
1-334

5.5.2.3 Description details of elements described in COMM_IF_PARAMETER part(1) Item description of element (of any name)
Table 5-343 Item Description Specifications of Parameter1 Element
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

WRITE_ORDER

12.

ASSIGN13.

UI_ATTRIBUTE

14.

REF

15.

COMMENT

Description Details
Not specified. Write a value in the same manner as the regular
COMM_IF_PARAMETER part.
Not specified. Write a value in the same manner as the regular
COMM_IF_PARAMETER part.
Not specified. Write a value in the same manner as the regular
COMM_IF_PARAMETER part.
Not specified. Write a value in the same manner as the regular
COMM_IF_PARAMETER part.
Not specified. Write a value in the same manner as the regular
COMM_IF_PARAMETER part.
Not specified. Write a value in the same manner as the regular
COMM_IF_PARAMETER part.
Not specified. Write a value in the same manner as the regular
COMM_IF_PARAMETER part.
Not specified. Write a value in the same manner as the regular
COMM_IF_PARAMETER part.
Not specified. Write a value in the same manner as the regular
COMM_IF_PARAMETER part.
Not specified. Write a value in the same manner as the regular
COMM_IF_PARAMETER part.
Not specified. Write a value in the same manner as the regular
COMM_IF_PARAMETER part.
Write cyclic address information for setting parameters based on initial
settings. The description specifications are the same as those for a regular
COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER
part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER
part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER
part.

(a) Item description example of Parameter1 element<p:commIfParameterMember label="Parameter1"><p:label2><p:item>Parameter1</p:item></p:label2><p:name><p:item>Parameter 1</p:item></p:name><p:access><p:item>RW</p:item></p:access><p:assign><p:item>RWw9</p:item></p:assign><p:ref><p:item>BlockSec.BlockParameter.Parameter1</p:item></p:ref></p:commIfParameterMember>

CLPA

BAP-C2008ENG-001-K
1-335

5.5.3

Parts and elements related to acquisition of error logs
CC-Link IE Field Network defines specifications related to error history information acquisition.
The module has a function that records the information of any errors that occur during module
operation, and acquires that error information as logs via SLMP via an external source. This section
describes the specifications of parts and elements in a case where error log acquisition processing is
to be described.

5.5.3.1 Overview
Error log acquisition is described in the MESSAGE, COMM_IF_COMMAND, BLOCK_COMMAND,
and COMMAND_ARGUMENT parts. Error logs are sometimes managed on the module main bodyside and sometimes on the communication module side, depending on the module mode andspecifications. The parts that are described, therefore, differ accordingly (parts can be describedbased on the concept of the COMM_IF section and BLOCK section). Figure 5-42 and Figure 5-43
show images of the structure when error log acquisition is described. (The specifications are for CCLink IE Field Network since a MESSAGE part is used.)

Figure 5-42 Image of Structure When Error Log Acquisition Is Described(When Error Logs Are Managed on Module Main Body Side)CLPA

BAP-C2008ENG-001-K
1-336

Figure 5-43 Image of Structure When Error Log Acquisition Is Described(When Error Logs Are Managed on Communication Module Side)
Table 5-344 shows a list of elements described in the MESSAGE part. For details of the description
specifications of the elements, see Section 5.5.3.2.
Table 5-344 List of Elements Described in MESSAGE PartNo.

Element Name

1.

SLMPGetErrorLogMessage*

Description Details
Describes the message used to acquire error
logs.
For "*", see detailed description specifications.

Required/Optional
Required

Table 5-345 lists the elements described in the COMM_IF_COMMAND part. For details of thedescription specifications of the elements, see Section 5.5.3.3.
Table 5-345 List of Elements Described in COMM_IF_COMMAND PartNo.
1.

Element Name
GetErrorLogCommand**Description Details
Describes the command information to be used
for error log acquisition.
For "**", see detailed description specifications.

Required/Optional
Required

Table 5-346 lists the elements described in the BLOCK_COMMAND part. For details of the description
specifications of the elements, see Section 5.5.3.4.
Table 5-346 List of Elements Described in BLOCK_COMMAND Part
No.
1.

CLPA

Element Name

Description Details
Required/Optional
Describes the command information to be used
GetErrorLogCommand**for error log acquisition.
Required*1
For "**", see detailed description specifications.
*1. Required only when a BLOCK_COMMAND part is used. Optional when a
BLOCK_COMMAND part is not used.

BAP-C2008ENG-001-K
1-337

Table 5-347 lists the elements described in the COMMAND_ARGUMENT part (specifications common
to COMM_IF and BLOCK sections). While all elements are optionally described, at least one element
must be described. (A description of only the COMMAND_ARGUMENT part in which these elements
are not described is not permitted.) For details of the description specifications of the elements, see
Section 5.5.3.5.
Table 5-347 List of Elements Described in COMMAND_ARGUMENT Part
No. Element Name
1. ErrorCode
2.
3.
4.
5.
6.
7.
8.

9.

10.

Description Details
Required/Optional
Describes the error code.
Optional
Describes the error occurrence date/time (year).
Optional
ErrorYear
Recommended: Write a description that can be read as the(However,four digits of the western calendar.
omission of
Describes the error occurrence date/time (month).
ErrorMonthelements
betweenDescribes the error occurrence date/time (day).
ErrorDaytwo included
Describes the error occurrence date/time (hour).
ErrorHourelements is
Describes the error occurrence date/time (minute).
ErrorMinuteprohibited.*1)
Describes the error occurrence date/time (second).
ErrorSecond
ErrorDayOfWeek Describes the error occurrence date/time (day of week).
Optional
Describes the error log details.
For "**", see detailed description specifications. Note thatmultiple details can be described by changing theErrorDetail**
Optional
information following the prefix. (Example: Frequency at
error occurrence, output value at error occurrence)
Application not specified. May be used for the following
applications:
Example: To describe dummy elements and express thedata order when error logs are acquired, including(Any name)
Optional
unnecessary data between error log details 1 and error log
details 2. (With a message, the order of the elements of the
COMMAND_ARGUMENT part s to correspond with theorder of the data during data reception.)*1. For example, while it is possible to simultaneously omit ErrorSecond and ErrorMinute, you
cannot omit ErrorMinute in a case where both ErrorHour and ErrorSecond are described. Withthe utility software, we recommend that you do not display omitted date/time information (nonacquirable date/time information), but rather display only the date/time information describedin the COMMAND_ARGUMENT part.

Note that while multiple parts are used to describe error log acquisition, there are no regulations
regarding the label name of each part. (The CSP+ file creator can freely assign label names.)

CLPA

BAP-C2008ENG-001-K
1-338

5.5.3.2 Description details of elements described in MESSAGE part(1) Item description of SLMPGetErrorLogMessage*
Table 5-348 Item Description Specifications for SLMPGetErrorLogMessage* Element
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

TARGET

6.

MESSAGE_TYPE

7.

REQUEST_TYPE

8.

REQUEST_DATA

9.

REQUEST_DATATYPE10.

RESPONSE_TYPE

11.

RESPONSE_DATA

12.

RESPONSE_DATATYPE

13.

ERR_TYPE

14.

ERR_CODE_RANGE

15.

RELATED_MESSAGE

16.

COMMENT

CLPA

Description Details
Write "SLMPGetErrorLogMessage*". Write a sequential numerical value
in the area marked by an asterisk (*), starting from 1. (99, maximum)(Example: SLMPGetErrorLogMessage1, SLMPGetErrorLogMessage2,…)
Write "SLMPGetErrorLogMessage*". [Recommended specifications]Write the same value as that of the LABEL item in the area marked by anasterisk (*).
Not specified. Write a value in the same manner as the regular
MESSAGE part.
Write "Error History Acquisition*". [Recommended specifications]Write the same value as that of the LABEL item in the area marked by anasterisk (*).
Write a reference to the COMM_IF_COMMAND part specified by Section
5.5.3.3.
Write "COMMAND".
However, in a case where a message that acquires multiple error history
information logs using "SEQ" in RELATED_MESSAGE is consecutively
executed, you can also write "OTHER" in MESSAGE TYPE for the
MESSAGE element that serves as the reference destination by SEQ. At
this time, write "COMMAND" in MESSAGETYPE for the MESSAGE
element that serves as the reference source.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Write a reference to the VALUE of an element of the
COMMAND_ARGUMENT part specified in Table 5-347.
A minimum of one reference description to the VALUE of the element isrequired.
Write the data type (representation string) or a reference to the
DATATYPE item of an element of the COMMAND_ARGUMENT part
specified in Table 5-347.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
You can also describe consecutive execution of a message that acquires
multiple error history information logs using the keyword "SEQ". In sucha case, writing a message of a label other than
"SLMPGetErrorLogMessage*" in the element referenced by SEQ is
prohibited.
Not specified.
Write a value in the same manner as the regular MESSAGE part. Write
an explanation of the error logs to be read if such an explanation isrequired. [Example: Write that only the lower two digits of the error
occurrence date/time (year) are displayed if only the lower two digits canbe acquired.]
BAP-C2008ENG-001-K
1-339

(a) Item description example of SLMPGetErrorLogMessage1 element<p:messageMember label="SLMPGetErrorLogMessage1"><p:label2><p:item>SLMPGetErrorLogMessage1</p:item></p:label2><p:name><p:item>Error History Acquisition 1</p:item></p:name><p:target><p:item>GetErrorLogCommand</p:item></p:target><p:messageType><p:item>COMMAND</p:item></p:messageType><p:requestType><p:item>rdReqST_Binary</p:item></p:requestType><p:requestData><p:item>&lt;0x0401&gt;&lt;0x0000&gt;&lt;0x00000000&gt;&lt;$0x0006&gt;</p:item></p:requestData><p:requestDatatype><p:item>&lt;WORD&gt;&lt;WORD&gt;&lt;DWORD&gt;&lt;WORD&gt;</p:item></p:requestDatatype><p:responseType><p:item>rdResST_Binary</p:item></p:responseType><p:responseData><p:item>$(ARGUMENT.*.VALUE)</p:item></p:responseData><p:responseDatatype><p:item>$(ARGUMENT.*.DATATYPE)</p:item></p:responseDatatype><p:errType><p:item>rdErr_Binary</p:item></p:errType><p:errCodeRange><p:item>EnumErrorCode</p:item></p:errCodeRange></p:messageMember>

CLPA

BAP-C2008ENG-001-K
1-340

5.5.3.3 Description details of elements described in COMM_IF_COMMAND part(1) Item description of GetErrorLogCommand** element
Table 5-349 Item Description of GetErrorLogCommand** Element
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

ARGUMENT

6.

REF

7.

COMMENT

Description Details
Write "GetErrorLogCommand**". Write any string, including spaces, in the area
marked by the asterisks (**).
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
[When error logs are managed on module main body side]
Write prohibited.
[When error logs are managed on communication module side]
Write a reference to the COMMAND_ARGUMENT part where an element
defined in Table 5-347 is described.
[When error logs are managed on module main body side]
Write a reference to the BLOCK_COMMAND specified in Section 5.5.3.4.
[When error logs are managed on communication module side]
Write prohibited.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.

(a) Item description example of GetErrorLogCommand element<p:commIfCommandMember label="GetErrorLogCommand"><p:label2><p:item>GetErrorLogCommand</p:item></p:label2><p:name><p:item>Error History Acquisition</p:item></p:name><p:ref><p:item>BlockSec.BlockCommand.GetErrorLogCommand</p:item></p:ref></p:commIfCommandMember>

CLPA

BAP-C2008ENG-001-K
1-341

5.5.3.4 Description details of elements described in BLOCK_COMMAND part(1) Item description of GetErrorLogCommand** element
Table 5-350 Item Description Specifications of GetErrorLogCommand** Element
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

ARGUMENT

6.

COMMENT

Description Details
Write "GetErrorLogCommand**". Write any string, including spaces, in the area
marked by the asterisks (**).
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Write a reference to the COMMAND_ARGUMENT part where an element
specified in Table 5-347 is described.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.

(a) Item description example of GetErrorLogCommand element<p:blockCommandMember label="GetErrorLogCommand"><p:name><p:item>GetErrorLogCommand</p:item></p:name><p:argument><p:item>ErrorLogArgument</p:item></p:argument></p:blockCommandMember>

CLPA

BAP-C2008ENG-001-K
1-342

5.5.3.5 Description details of elements described in COMMAND_ARGUMENT part(1) Item description of ErrorCode element
Table 5-351 Item Description Specifications of ErrorCode Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

ASSIGN

12.

REF

13.

COMMENT

Description Details
Write "ErrorCode".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Select and write one of the following: bit string type, signed integer type,unsigned integer type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified. Write a value in the same manner as the regular
COMMAND_ARGUMENT part. Note that you can define the meaning of an error
code or comment by writing a reference to an ENUM part in this item.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of ErrorCode element<p:commandArgumentMember label="ErrorCode"><p:label2><p:item>ErrorCode</p:item></p:label2><p:name><p:item>Error Code</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:range><p:enumRefItem>EnumErrorCode</p:enumRefItem></p:range><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-343

(2) Item description of ErrorYear element
Table 5-352 Item Description Specifications of ErrorYear Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

ASSIGN

12.

REF

13.

COMMENT

Description Details
Write "ErrorYear".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Select and write one of the following: unsigned integer type, BCD integer type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of ErrorYear element<p:commandArgumentMember label="ErrorYear"><p:label2><p:item>ErrorYear</p:item></p:label2><p:name><p:item>Error Occurrence Date and Time (Year)</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-344

(3) Item description of ErrorMonth element
Table 5-353 Item Description Specifications of ErrorMonth Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

ASSIGN

12.

REF

13.

COMMENT

Description Details
Write "ErrorMonth".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Select and write one of the following: unsigned integer type, BCD integer type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of ErrorMonth element<p:commandArgumentMember label="ErrorMonth"><p:label2><p:item>ErrorMonth</p:item></p:label2><p:name><p:item>Error Occurrence Date and Time (Month)</p:item></p:name><p:datatype><p:item>UINT4</p:item></p:datatype><p:range><p:item>[1,12]</p:item></p:range><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-345

(4) Item description of ErrorDay element
Table 5-354 Item Description Specifications of ErrorDay Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

ASSIGN

12.

REF

13.

COMMENT

Description Details
Write "ErrorDay".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Select and write one of the following: unsigned integer type, BCD integer type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of ErrorDay element<p:commandArgumentMember label="ErrorDay"><p:label2><p:item>ErrorDay</p:item></p:label2><p:name><p:item>Error Occurrence Date and Time (Date)</p:item></p:name><p:datatype><p:item>UINT8</p:item></p:datatype><p:range><p:item>[1,31]</p:item></p:range><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-346

(5) Item description of ErrorHour element
Table 5-355 Item Description Specifications of ErrorHour Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

ASSIGN

12.

REF

13.

COMMENT

Description Details
Write "ErrorHour".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Select and write one of the following: unsigned integer type, BCD integer type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of ErrorHour element<p:commandArgumentMember label="ErrorHour"><p:label2><p:item>ErrorHour</p:item></p:label2><p:name><p:item>Error Occurrence Date and Time (Hour)</p:item></p:name><p:datatype><p:item>UINT8</p:item></p:datatype><p:range><p:item>[0,23]</p:item></p:range><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-347

(6) Item description of ErrorMinite element
Table 5-356 Item Description Specifications of ErrorMinite Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

ASSIGN

12.

REF

13.

COMMENT

Description Details
Write "ErrorMinite".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Select and write one of the following: unsigned integer type, BCD integer type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of ErrorMinite element<p:commandArgumentMember label="ErrorMinite"><p:label2><p:item>ErrorMinite")</p:item></p:label2><p:name><p:item>Error Occurrence Date and Time (Minute)</p:item></p:name><p:datatype><p:item>UINT8</p:item></p:datatype><p:range><p:item>[0,59]</p:item></p:range><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-348

(7) Item description of ErrorSecond element
Table 5-357 Item Description Specifications of ErrorSecond Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

ASSIGN

12.

REF

13.

COMMENT

Description Details
Write "ErrorSecond".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Select and write one of the following: unsigned integer type, BCD integer type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of ErrorSecond element<p:commandArgumentMember label="ErrorSecond"><p:label2><p:item>ErrorSecond</p:item></p:label2><p:name><p:item>Error Occurrence Date and Time (Second)</p:item></p:name><p:datatype><p:item>UINT8</p:item></p:datatype><p:range><p:item>[0,59]</p:item></p:range><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-349

(8) Item description of ErrorDayOfWeek element
Table 5-358 Item Description Specifications of ErrorDayOfWeek Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

ASSIGN

12.

REF

13.

COMMENT

Description Details
Write "ErrorDayOfWeek".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Select and write one of the following: unsigned integer type, BCD integer type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of ErrorDayOfWeek element<p:commandArgumentMember label="ErrorDayOfWeek"><p:label2><p:item>ErrorDayOfWeek</p:item></p:label2><p:name><p:item>Error Occurrence Date and Time (Day of Week)</p:item></p:name><p:datatype><p:item>UINT8</p:item></p:datatype><p:range><p:enumRefItem>EnumDayOfWeek</p:enumRefItem></p:range><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-350

(9) Item description of ErrorDetail** element
Table 5-359 Item Description Specifications of ErrorDetail** Element
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

ASSIGN

12.

REF

13.

COMMENT

Description Details
Write "ErrorDetail**".
Write any string in the area marked by the asterisks (**).
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of ErrorDeteil1 element<p:commandArgumentMember label="ErrorDetail1"><p:label2><p:item>ErrorDetail1</p:item></p:label2><p:name><p:item>Error History Detailed Information 1</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-351

5.5.4

Method Specifications for conducting error checks of equipment
CC-Link and CC-Link IE Field Network define specifications related to METHOD that checks errors ofthe machine.

5.5.4.1 Overview
Judges whether or not there are errors in the equipment, and if a METHOD is written in order toacquire the error code when an error does occur in the equipment, write this as in Table 5-360. Evenon devices for which an error code cannot be acquired, it is possible to write a METHOD that indicates
information for the error judgment only. See Table 5-363 for the difference in the description by theacquisition propriety.
LABEL2 and NAME are recommended specifications, and other strings can be written.
COMM_IF Section

BLOCK Section

METHOD part

BLOCK_COMMAND part
GetErrorInfo** element

P_GetErrorInfo1 element
P_GetErrorInfo2 element
P_GetErrorInfo3 element

COMM_IF_COMMAND part
GetErrorInfo** element

Figure 5-44 Structural image when conducting error check of the equipment
Elements written in METHOD parts are indicated in Table 5-360. See section 5.5.4.2 for details of
description specifications of elements.
Table 5-360 List of elements written in METHOD partNo. Element Name
1. P_GetErrorInfo*

Description Details
Writes the method for conducting error check of equipment.

Required/Optional
Required

Elements written in COMM_IF_COMMAND parts are indicated in Table 5-361. See section 5.5.4.3 fordetails of description specifications of elements.
Table 5-361 List of elements written in COMM_IF_COMMAND partNo. Element Name
1. (Name Optional)

Description Details
Writes a command for conducting error check of equipment.

Required/Optional
Required

Table 5-362 List of elements written in BLOCK_COMMAND partNo. Element Name
1. (Name Optional)

CLPA

Description Details
Writes a command for conducting error check of equipment.

Required/Optional
Required

BAP-C2008ENG-001-K
1-352

5.5.4.2 Description details of elements written in METHOD part(1) Item description of P_GetErrorInfo+X elements (if error code can be acquired)
Table 5-363 METHOD Specifications for conducting error check of equipment(if error code can be acquired)
No.
1.

2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.

Item Name

Description Details"P_GetErrorInfo"+X*X is empty, or write numerical values in order from 1. (max 99) *1
LABEL
[Ex]
P_GetErrorInfo1,
P_GetErrorInfo2, …
"P_GetErrorInfo"+X*X is the same as LABELLABEL2Using a description that can read 4 digit western calendar years is
recommended [Recommended Specifications]
Not prescribed.
CATEGORY
Write the same as normal METHOD part.
NAME
Write "Get Error Info" [Recommended Specifications]Writes the label name of COMM_IF_COMMAND prescribed in Table 5-364
TARGETfor getting error info. *2
METHOD_TYPE
Writes "OTHER" or "COMMAND".
WRITE_REGISTER
Write prohibited.
WRITE_DATA
Write prohibited.
WRITE_DATATYPE
Write prohibited.
Write an address for error code acquisition. Either write the address directly,
READ_REGISTERor reference the ASSIGN element of COMMAND_ARGUMENT referenced
through TARGET. *3
References the VALUE element of COMMAND_ARGUMENT referenced
READ_DATA
through TARGET. *3
Writes the data type of the error code. Either write the data type directly or
READ_DATATYPE
reference the DATATYPE element of COMMAND_ARGUMENT referenced
through TARGET.
INTERLOCK
Write the error judgment conditions.
REQ_FLAG
Write prohibited.
END_CONDITION
Write prohibited.
ERR_CONDITION
Write prohibited.
ERR_REGISTER
Write prohibited.
ERR_CODE_RANGE Write prohibited.
RELATED_METHOD Write prohibited.
COMMENT
Write prohibited.
*1 If there are multiple error judgment conditions or means of acquiring error codes, by entering
different numerical values in X, it is possible to write multiple METHODs. The values of X
indicate priority, and if there is an upper limit to the number of error informations that can bedisplayed with engineering tools, it displays information in favor of that which was acquired withsmaller X value.
*2 In the case of equipment for which an error code can be acquired, the error code acquisitionargument is defined with the COMMAND_ARGUMENT referenced from the item ARGUMENTof BLOCK_COMMAND referenced by COMM_IF_COMMAND. When writing the error code’s
meaning (NAME) and comment (COMMENT), ENUM is defined, and they are referenced fromthe item RANGE of the error code acquisition argument.
*3 Multiple descriptions are not possible. When multiple error codes can be acquired, write themin another P_GetErrorInfoX.

CLPA

BAP-C2008ENG-001-K
1-353

(a) Example item description of P_GetErrorInfo+X element<p:methodMember label=" P_GetErrorInfo1"><p:label2><p:item>P_GetErrorInfo1</p:item></p:label2><p:name><p:item>Get Error Info1</p:item></p:name><p:target><p:item> CCLinkCommand.GetErrorInfo</p:item></p:target><p:methodType><p:item>OTHER</p:item></p:methodType><p:interlock><p:item>RX1A==ON</p:item></p:interlock><p:readRegister><p:item>RWr2</p:item></p:readRegister><p:readData><p:item> $(ARGUMENT.ErrorCode.VALUE)</p:item></p:readData><p:readDatatype><p:item> $(ARGUMENT.ErrorCode.DATATYPE)</p:item></p:readDatatype></p:methodMember>(2) Example item description of P_GetErrorInfo+X element (when error code cannot be acquired)
Table 5-364 METHOD Specifications for conducting error check of equipment(when error code cannot be acquired)
No.
1.

2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.

Item Name

Description Details"P_GetErrorInfo"+X*X is empty, or write numerical values in order from 1. (max 99) *1
LABEL
[Ex]
P_GetErrorInfo1,
P_GetErrorInfo2, …
"P_GetErrorInfo"+X*X is the same as LABELLABEL2Using a description that can read 4 digit western calendar years is
recommended [Recommended Specifications]
Not prescribed.
CATEGORY
Write the same as normal METHOD part.
NAME
Write "Get Error Info" [Recommended Specifications]Writes the label name of COMM_IF_COMMAND prescribed in Table 5-365
TARGETfor getting error info. *2
METHOD_TYPE
Writes "OTHER" or "COMMAND".
WRITE_REGISTER
Write prohibited.
WRITE_DATA
Write prohibited.
WRITE_DATATYPE
Write prohibited.
READ_REGISTER
Write prohibited.
READ_DATA
Write prohibited.
READ_DATATYPE
Write prohibited.
INTERLOCK
Write the error judgment conditions.
REQ_FLAG
Write prohibited.
END_CONDITION
Write prohibited.
ERR_CONDITION
Write prohibited.
ERR_REGISTER
Write prohibited.
ERR_CODE_RANGE Write prohibited.
RELATED_METHOD Write prohibited.
COMMENT
Write prohibited.
*1 If there are multiple error judgment conditions or means of acquiring error codes, by entering
different numerical values in X, it is possible to write multiple METHODs. The values of X
indicate priority, and if there is an upper limit to the number of error informations that can bedisplayed with engineering tools, it displays information in favor of that which was acquired withsmaller X value.
*2 In the case of equipment for which an error code can be acquired, the error code acquisitionargument is defined with the COMMAND_ARGUMENT referenced from the item ARGUMENTof BLOCK_COMMAND referenced by COMM_IF_COMMAND. When writing the error code’s
meaning (NAME) and comment (COMMENT), ENUM is defined, and they are referenced fromthe item RANGE of the error code acquisition argument.

CLPA

BAP-C2008ENG-001-K
1-354

5.5.4.3 Example of description of elements written in COMM_IF_COMMAND partNot prescribed.
Write the same as normal COMM_IF_COMMAND. An example description is shown below.
Table 5-365 Example item description of elements of COMM_IF_COMMAND part
No.
1.
2.
3.
4.
5.
6.
7.

Item NameLABELLABEL2
CATEGORYNAME
ARGUMENTREF
COMMENT

Description Details"GetErrorCode" is written.
Not written because it may be omitted.
Not written because it may be omitted.
"Get Error Info Command" is written.
Not written because it may be omitted.
"BlockSec.BlockCommand.GetErrorInfo" is written.
Not written because it may be omitted.

(a) Example of item description of GetErrorInfo element<p:commIfCommandMember label="GetErrorInfo"><p:name><p:item>Get Error Info Command</p:item></p:name><p:ref><p:item>BlockSec.BlockCommand.GetErrorInfo</p:item></p:ref ></p:commIfCommandMember >5.5.4.4 Description details of element written in BLOCK_COMMAND part(1) Item description of BLOCK_COMMAND element
Table 5-366 Item Description Specifications of BLOCK_COMMAND Element
No.
Item Name
1. LABEL
2. LABEL2
3. CATEGORY
4.

NAME

5.

ARGUMENT

6.

COMMENT

Description Details"GetErrorInfo1" is written.
Not written because it may be omitted.
Not written because it may be omitted.
Not prescribed.
Write the same as normal BLOCK_COMMAND parts.
Writes a reference to the COMMAND_ARGUMENT in which the elements
prescribed in Table 5-362 are written.
Not written because it may be omitted.

(a) Item description example of GetErrorLogCommand element<p:blockCommandMember label="GetErrorLogCommand"><p:name><p:item>Get Error Info Command</p:item></p:name><p:argument><p:item>ErrorInfoArgument</p:item></p:argument></p:blockCommandMember>

CLPA

BAP-C2008ENG-001-K
1-355

5.5.4.5 Description details of elements written in COMMAND_ARGUMENT part(1) Item description of ErrorCode elements
Table 5-367 Item description example of ErrorCode element
No.
Item Name
1. LABEL
2. LABEL2
3. CATEGORY
4.

NAME

5.
6.
7.
8.
9.
10.
11.
12.
13.

DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESSASSIGNREF
COMMENT

Description Details"ErrorCode" is written.
Not written because it may be omitted.
Not written because it may be omitted.
Not prescribed.
Write the same as normal COMMAND_ARGUMENT parts.
WORD is written.
Not written because it may be omitted.
"ENUM EnumErrorCode" is written.
Not written because it may be omitted.
Not written because it may be omitted.
"R" is written.
Not written because it may be omitted.
Not written because it may be omitted.
Not written because it may be omitted.

(a) Item description example of ErrorCode element<p:commandArgumentMember label="ErrorCode"><p:name><p:item>Error Code</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:range><p:enumRefItem>ENUM EnumErrorCode</p:enumRefItem></p:range><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

METHOD

COMM_IF_COMMAND (LABEL=CCLinkCommand)

BLOCK_COMMAND (LABEL=BlockCommand)

COMMAND_ARGUMENT (LABEL=ErrorInfoArgument)

ENUM (LABEL=EnumErrorCode)

Figure 5-45 Examples of METHOD & COMMAND that perform error check of equipment(some unwritable or optional items omitted)

CLPA

BAP-C2008ENG-001-K
1-356

5.5.5

Parts and elements that indicated parameters for safety communication function
The safety compatible devices of CC-Link IE Field Network define specifications related to parameters
for the safety communication function.
This section describes specifications of parts and elements for writing the parameters of safety
communication functions.

5.5.5.1 Overview
Write safety communication function parameters in COMM_IF_PARAMETER parts and
BLOCK_PARAMETER parts.
COMM_IF Section
BLOCK Section
COMM_IF_PARAMETER parts

BLOCK_PARAMETER parts

P_TransIntervalMonitorTime element

P_TransIntervalMonitorTime element

Figure 5-46 Structural image in when writing parameters of safety communication functions
Elements written in COMM_IF_PARAMETER parts are indicated in Table 5-368. See Section 5.5.5.2
for details of description specifications of elements.
Table 5-368 Example of item description in the case of ErrorCode elements
No.

Element Name

1.

P_TransIntervalMonitorTime

Description Details
Describes the transmission interval monitoringtime of safety communication function.

Required/Optional
Required

Elements written in BLOCK_PARAMETER parts are indicated inTable 5-369. See Section 5.5.5.2 fordetails of description specifications of elements.
Table 5-369 List of elements written in BLOCK_PARAMETER parts
No.

Element Name

1.

P_TransIntervalMonitorTime

CLPA

Description Details
Describes the transmission interval monitoringtime of safety communication function.

Required/Optional
Required

BAP-C2008ENG-001-K
1-357

5.5.5.2 Description details of elements written in COMM_IF_PARAMETER parts and
BLOCK_PARAMETER parts(1) Item description of elements of P_TransIntervalMonitorTime of COMM_IF_PARAMETER parts
Table 5-370 Item Description Specifications of P_TransIntervalMonitorTime Element of
COMM_IF_PARAMETER Part
No.
Item Name
1. LABEL
2. LABEL2
3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

WRITE_ORDER

12.

ASSIGN13.

UI_ATTRIBUTE

14.

REF

15.

COMMENT

Description Details
Write "P_TransIntervalMonitorTime".
Write "P_TransIntervalMonitorTime".
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Write "Transmission Interval Monitoring Time".
May be omitted because this case uses the value of the reference source of
REF item.
When writing, "UINT16" is written.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
May be omitted because this case uses the value of the reference source of
REF item.
When writing, " [2,65535] " is written.
Write prohibited.
May be omitted because this case uses the value of the reference source of
REF item.
When writing, "ms" is written.
May be omitted because this case uses the value of the reference source of
REF item.
When writing, "W" is written.
Write prohibited.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Write a reference to the "P_TransIntervalMonitorTime" of
BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.

(a) Example of item description of elements<p:commIfParameterMember label="P_TransIntervalMonitorTime"><p:label2><p:item>P_TransIntervalMonitorTime</p:item></p:label2><p:name><p:item>Transmission Interval Monitoring Time</p:item></p:name><p:ref><p:item>BlockSec.BlockParameter.P_TransIntervalMonitorTime</p:item></p:ref></p:commIfParameterMember>

CLPA

BAP-C2008ENG-001-K
1-358

(2) Item description of P_TransIntervalMonitorTime elements of BLOCK_PARAMETER parts
Table 5-371 Item Description Specifications of P_TransIntervalMonitorTime Element of
BLOCK_PARAMETER Part
No.
1.
2.

Item NameLABELLABEL2

3.

CATEGORY

4.
5.

NAME
DATATYPE

6.

DEFAULT

7.

RANGE

8.
9.
10.
11.

MIN_INC
ENG_UNITACCESS
WRITE_ORDER

12.

UI_ATTRIBUTE

13.

COMMENT

Description Details
Write "P_TransIntervalMonitorTime".
Write "P_TransIntervalMonitorTime".
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Write "Transmission Interval Monitoring Time".
Write "UINT16".
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
However, because communication interval monitoring time is 16 bit in 128μs
units in protocol specifications, values above 128×65535÷1000≒8388ms
cannot be specified.
Write prohibited.
Write "ms".
Write "W" or "RW".
Write prohibited.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.

(a) Examples of item description of elements<p:blockParameterMember label="P_TransIntervalMonitorTime"><p:label2><p:item>P_TransIntervalMonitorTime</p:item></p:label2><p:name><p:item>Transmission Interval Monitoring Time</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:range><p:item>[10,2000]</p:item></p:range><p:engUnit><p:item>ms</p:item></p:engUnit><p:access><p:item>RW</p:item></p:access></p:blockParameterMember>

CLPA

BAP-C2008ENG-001-K
1-359

5.5.6MESSAGE Specifications for parameter writing of safety communication functions
The safety compatible devices of CC-Link IE Field Network define specifications related to parameter
writing of the safety communication function.

5.5.6.1 Overview
When writing a MESSAGE to write parameters in safety equipment, write it according to thespecifications prescribed in this section. However, because LABEL2 and NAME are recommended
specifications, other strings may be written.
Also, when reading CRC32 values, it writes the strings indicated in Table 5-372 in REQUEST_DATA
and RESPONSE_DATA. Parameters of safety communication functions (See Section 5.5.5) are also
written using messages shown in this section.
COMM_IF Section

BLOCK Section

MESSAGE Part
SLMP_P_Safety_ParameterWrite element

COMM_IF_PARAMETER parts

BLOCK_PARAMETER parts

Parameter 1

Parameter 1

Parameter 2・••Parameter 2・••Parameter x

Parameter x

Figure 5-47 Structural image when describing parameter writing of safety communication functions
COMM_IF Section

BLOCK Section

MESSAGE Part
SLMP_P_Safety_EnableParameter element

COMM_IF_COMMAND parts

BLOCK_COMMAND parts

Command 1

Command 1

Figure 5-48 Structural image when describing enabling parameters of safety communication functions
Table 5-372 Reserved words that indicated read/write of CRC32 values
Name
Reserved
CRC32 value prescribed in CC-Link IE Safety$(CRC32_F1922815)
Communication Function *1
CRC32 value prescribed in IEEE802.3. *1$(CRC32_04C11DB7)

CLPA

BAP-C2008ENG-001-K
1-360

*1 Utility software calculates CRC32 according to the following specifications.
･When running a MESSAGE element including reserved words indicating CRC32, CRC32 is
calculated from the VALUE of all elements of COMM_IF_PARAMETER(BLOCK_PARAMETER) referenced by the TARGET of that MESSAGE element.
･When running multiple MESSAGE elements sequentially with RELATED_MESSAGE (in thecase that it includes reserved words indicating CRC32 in at least one of those elements),
CRC32 is calculated from the VALUE of all elements of COMM_IF_PARAMETER(BLOCK_PARAMETER) referenced by the TARGET of all MESSAGE elements referenced
by RELATED_MESSAGE.
When reserved words indicating the value of CRC32 are written in REQUEST_DATA, utility software
calculates CRC32 when MESSAGE is executed, and stores it in a request message. If it is written in
RESPONSE_DATA, the utility software reads the value of CRC32 from the place where the reply
message reserved word is written.
When parameter writing of safety communication functions is described with multiple consolidated
MESSAGES, elements prescribed in this section (SLMP_P_Safety_ParameterWrite) it is attached to a
MESSAGE representing a series of operations. The elements of the MESSAGE consolidated fromthere are optional.
A maximum of 1 reserved word of Table 5-372 can be written in each REQUEST_DATA orRESPONSE_DATA.
Elements written in MESSAGE parts are indicated in Table 5-373. See Section 5.5.6.2 for details of
description specifications of elements.
Table 5-373 List of elements written in MESSAGE parts
No.

Element Name

1.

SLMP_P_Safety_ParameterWrite

2.

SLMP_P_Safety_EnableParameter

Description Details
Writes the message used in parameter
writing of safety communication functions.
Writes the enabling information used inparameter writing of safety
communication functions.

Required/Optional
Optional
Optional(1) Elements of parameters referenced by SLMP_P_Safety_ParameterWrite elements
Elements written in COMM_IF_PARAMETER parts are indicated in Table 5-374. See Section 5.5.6.2
for details of description specifications of elements.
Table 5-374 List of elements written in COM_IF_PARAMETER parts
No.
1.

Element Name
(Name Optional)

Description Details
Writes the parameters of safety
communication functions.

Required/Optional
Optional

Elements written in BLOCK_PARAMETER parts are indicated in Table 5-375. See Section 5.5.6.2 fordetails of description specifications of elements.
Table 5-375 List of elements written in BLOCK_PARAMETER parts
No.
1.

Element Name
(Name Optional)

Description Details
Writes the parameters of safety
communication functions.

Required/Optional
Optional(2) Elements of commands referenced by SLMP_P_Safety_EnableParameter elements
Elements written in COMM_IF_COMMAND parts are indicated in Table 5-376. See Section 5.5.6.2 fordetails of description specifications of elements.
Table 5-376 List of elements written in BLOCK_PARAMETER parts
No.

Description Details
Required/Optional
Writes the parameters of safety
1. (Name Optional)
Optional
communication functions.
Elements written in BLOCK_COMMAND parts are indicated in Table 5-377. See Section 5.5.6.2 fordetails of description specifications of elements.

CLPA

Element NameBAP-C2008ENG-001-K
1-361

Table 5-377 List of elements written in BLOCK_PARAMETER parts
No.
1.

Element Name
(Name Optional)

Description Details
Writes the parameters of safety
communication functions.

Required/Optional
Optional

5.5.6.2 MESSAGE specifications for parameter writing of safety communication functions
MESSAGEs are prescribed for parameter writing, but not for reading. MESSAGEs for reading can be
written freely according to CSP+ specifications.
(1) Item description of SLMP_P_Safety_ParameterWrite elements
Table 5-378 Item Description Specifications of SLMP_P_Safety_ParameterWrite Element
No.
Item Name
1. LABEL
2. LABEL2
3.

CATEGORY

4.

NAME

5.

TARGET

6.

MESSAGE_TYPE

7.

REQUEST_TYPE

8.

REQUEST_DATA

9.

REQUEST_DATATYPE10.

RESPONSE_TYPE

11.

RESPONSE_DATA

12.

RESPONSE_DATATYPE

13.

ERR_TYPE

14.

ERR_CODERANGE

15.

RELATED_MESSAGE

16.

COMMENT

Description Details
Write "SLMP_P_Safety_ParameterWrite".
Write "SLMP_P_Safety_ParameterWrite". [Recommended Specification]
Not prescribed.
Write the same as normal MESSAGE parts.
Write "Parameter Writing". [Recommended Specification]
Write the reference to the COMM_IF_PARAMETER written in safety
communication function parameters.
Write "PARAMETER".
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.

(a) Item description example of SLMP_P_Safety_ParameterWrite element<p:messageMember label="SLMP_P_Safety_ParameterWrite"><p:label2><p:item>SLMP_P_Safety_ParameterWrite</p:item></p:label2><p:name><p:item>Parameter Writing</p:item></p:name><p:target><p:item>SEQ TARGET</p:item></p:target><p:messageType><p:item>PARAMETER</p:item></p:messageType><p:relatedMessage><p:item>&lt;SEQ SLMPStartWritePramArea&gt;&lt;SEQ SLMPStationWritePrm&gt;&lt;SEQ
SLMPWriteCRC32&gt;&lt;SEQ SLMPReflectPrm&gt;&lt;SEQ SLMPStartReadPramArea&gt;&lt;SEQ
SLMPReadCRC32&gt;</p:item></p:relatedMessage></p:messageMember>

CLPA

BAP-C2008ENG-001-K
1-362

(2) Item description of SLMP_P_Safety_EnableParameter elements
Table 5-379 Item Description Specifications of SLMP_P_Safety_EnableParameter Element
No.
Item Name
1. LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

TARGET

6.

MESSAGE_TYPE

7.

REQUEST_TYPE

8.

REQUEST_DATA

9.

REQUEST_DATATYPE10.

RESPONSE_TYPE

11.

RESPONSE_DATA

12.

RESPONSE_DATATYPE

13.

ERR_TYPE

14.

ERR_CODERANGE

15.

RELATED_MESSAGE

16.

COMMENT

Description Details
Write "SLMP_P_Safety_EnableParameter".
Write "SLMP_P_Safety_EnableParameter". [Recommended
Specification]
Not prescribed.
Write the same as normal MESSAGE parts.
Write "Enabling Parameter". [Recommended Specification]
Write the reference to the COMM_IF_COMMAND written in safety
communication function parameters.
Write "COMMAND".
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.
Not prescribed.
Write the same as normal MESSAGE parts.

(a) Item description example of SLMP_P_Safety_EnableParameter element<p:messageMember label="SLMP_P_Safety_EnableParameter"><p:label2><p:item>SLMP_P_Safety_EnableParameter</p:item></p:label2><p:name><p:item>Enabling Parameter</p:item></p:name><p:target><p:item>CommCommand.Safety_EnableParameter</p:item></p:target><p:messageType><p:item>COMMAND</p:item></p:messageType><p:requestType><p:item>wrReqMT_Binary</p:item></p:requestType><p:requestData><p:item>&lt;0x1613&gt;&lt;0x0000&gt;&lt;0x0000FFFF&gt;&lt;0x0001&gt;&lt;0xFFFE&gt;</p:item></p:requestData><p:requestDatatype><p:item>&lt;WORD&gt;&lt;WORD&gt;&lt;DWORD&gt;&lt;WORD&gt; &lt;WORD&gt;</p:item></p:requestDatatype><p:responseType><p:item>wrResMT_Binary</p:item></p:responseType></p:messageMember>

Figure 5-49 shows examples of MESSAGE for parameter writing of safety communication functions.

CLPA

BAP-C2008ENG-001-K
1-363

Figure 5-49 Example of MESSAGE for parameter writing of safety communication functions

CLPA

BAP-C2008ENG-001-K
1-364

5.5.7

Conventions of read/write capable parameters using parameter IDs
SLMP defines specifications related to parameters that can be written using parameter IDs.

5.5.7.1 Overview
This section shows conventions of parameters which can read and write using SLMP and parameter
IDs.
This convention, in the current version, can only be written in CSP+ for the Ethernet connection unit.
A structural image of the parameters using this convention are shown in Figure 5-50.
COMM_IF Section

BLOCK Section

COMM_IF_PARAMETER parts
LABEL: P_ParamIDInfo*

BLOCK_PARAMETER parts

Parameter 1

Parameter 1

Parameter 2•••

Parameter 2•••

Parameter x

Parameter x

Figure 5-50 Structural image of read/write capable parameters using parameter IDs
Parameters written with this convention are written in COMM_IF_PARAMETER parts with the prefix"P_ParamIDInfo" in its LABEL. In this convention, description by MESSAGE parts is not used.
Reading of parameters written with this convention are conducted using the GetParameter commandof SLMP, while writing is done in a series of steps using SetParameter related commands of SLMP.
(1) Conventions of COMM_IF_PARAMETER parts
Conventions of COMM_IF_PARAMETER parts are shown in Table 5-380.
Table 5-380 Conventions of COMM_IF_PARAMETER parts
No.
1.

Part Name
P_ParamIDInfo*

Description Details
Writes parameters that perform read/write usingparameter ID.

Required/Optional
Optional

With COM_IF_PARAMETER parts written with this convention, as the value of labels which are an
attribute XML elements indicating parts, any strings starting with "P_ParamIDInfo" are written.
(2) Elements of parameters written in P_ParamIDInfo* parts
Elements written in COMM_IF_PARAMETER parts are indicated in Table 5-381. See Section 5.5.7.2
for details of description specifications of elements.
Table 5-381 List of elements written in P_ParamIDInfo*
No.
1.

Element Name
(Name Optional)

Description Details
Writes parameters that perform read/write usingparameter ID.

Required/Optional
Optional

Elements written in BLOCK_PARAMETER parts are indicated in Table 5-382. See Section 5.5.7.2 fordetails of description specifications of elements.
Table 5-382 List of elements written in BLOCK_PARAMETER parts
No.

CLPA

Element Name

Description Details

Required/Optional
BAP-C2008ENG-001-K

1-365

1.

(Name Optional)

Writes parameters that perform read/write usingparameter ID.

Optional

5.5.7.2 Description specifications of parameters which perform read/write using parameter ID
Conventions of parameters which perform read/write using parameter ID are shown here.
(1) Item descriptions of elements of COMM_IF_PARAMETER
Item description specifications of elements written in COMM_IF_PARAMETER parts are indicated inTable 5-383.
Table 5-383 Item description specifications of COMM_IF_PARAMETER elements
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

WRITE_ORDER

12.

ASSIGN13.

UI_ATTRIBUTE

14.

REF

15.

COMMENT

Description Details
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
When word data (byte data) which one parameter ID is assigned to isdivided and assigned a different meaning for each bit, it writes a reference
to STRUCT parts. Otherwise it is recommended that this be omitted.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Writes parameter ID in hexadecimal numbers. Does not write "0x" toindicated hexadecimal numbers.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.
Writes a reference to elements of BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal COMM_IF_PARAMETER parts.

(a) Item description example of COMM_IF_PARAMETER part element<p:commIfParameter label="P_ParamIDInfo 1"><p:commIfParameterMember label="Param1"><p:label2><p:item>Parameter 1</p:item></p:label2><p:name><p:item>Parameter 1</p:item></p:name><p:assign><p:item>0070</p:item></p:assign><p:ref><p:item>BlockSec.BlockParameter.Param1</p:item></p:ref></p:commIfParameterMember></p:commIfParameter>

CLPA

BAP-C2008ENG-001-K
1-366

(2) Item description of elements of BLOCK_PARAMETER parts
Item description specifications of elements written in COMM_IF_PARAMETER parts are shown in
Table 5-384.
Table 5-384 Item description specifications of elements of BLOCK_PARAMETER parts
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

WRITE_ORDER

12.

UI_ATTRIBUTE

13.

COMMENT

Description Details
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
When word data (byte data) which one parameter ID is assigned to isdivided and assigned a different meaning for each bit, it writes a reference
to STRUCT parts. Otherwise it is recommended that this be omitted.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.
Not prescribed.
Write the same as normal BLOCK_PARAMETER parts.

(a) Item description example of BLOCK_PARAMETER part element<p:blockParameterMember label="Param1"><p:label2><p:item>Parameter 1</p:item></p:label2><p:name><p:item>Parameter 1</p:item></p:name><p:default><p:item>0</p:item></p:default><p:range><p:item>[0,65535]</p:item></p:range><p:access><p:item>RW</p:item></p:access></p:blockParameterMember>

CLPA

BAP-C2008ENG-001-K
1-367

5.5.8

Parts and elements related to the acquisition of energy management information

5.5.8.1 Overview
The acquisition of energy management information is described in the METHOD part or MESSAGE
part, COMM_IF_COMMAND part, BLOCK_COMMAND part, and COMMAND_ARGUMENT part.
Energy management information is sometimes managed on the module main body side andsometimes on the communication module side, depending on the module mode and specifications.
The parts that are described, therefore, differ accordingly (parts can be described based on theconcept of the COMM_IF section and BLOCK section). Figure 5-51 and Figure 5-52 show images ofthe structure when the acquisition of energy management information is described.
COMM_IF section

BLOCK section

METHOD part or MESSAGE part

BLOCK_COMMAND part

P_GetEnergyInfo** element

GetEnergyInfoCommand** element

COMMAND_ARGUMENT part

COMM_IF_COMMAND part

P_AverageCurrent element

GetEnergyInfoCommand** element

P_AverageVoltage element
P_ElectricPower element
P_ElectricEnergy element
P_PowerDistributionTime element

P_RunningTime element

Figure 5-51 Image of Structure When Acquisition of Energy Management Information Is Described(When Energy Management Information Is Managed on Module Main Body Side)
COMM_IF section
METHOD part or MESSAGE part

COMMAND_ARGUMENT part

P_GetEnergyInfo** element

P_AverageCurrent element
P_AverageVoltage element
P_ElectricPower element

COMM_IF_COMMAND part

P_ElectricEnergy element

GetEnergyInfoCommand** element

P_PowerDistributionTime element

P_RunningTime element

Figure 5-52 Image of Structure When Acquisition of Energy Management Information Is Described(When Energy Management Information Is Managed on Communication Module Side)CLPA

BAP-C2008ENG-001-K
1-368

Table 5-385 shows a list of elements described in the METHOD part. For details of the description
specifications of the elements, see Section 5.5.8.3. Any element is not described when the MESSAGE
part is used. Either the METHOD part or MESSAGE part is used.
Table 5-385 List of Elements Described in METHOD PartNo.
1.

Element Name

Description Details
Required/Optional
Describes the method used to acquire the energy
P_GetEnergyInfo**
management information.
Required*1
For "**", see detailed description specifications.
*1: Required only when the METHOD part is used. Optional when the METHOD part is not used.
Table 5-386 lists the elements described in the MESSAGE part. For details of the description
specifications of the elements, see Section 5.5.8.3. Any element is not described when the METHOD
part is used. Either the METHOD part or MESSAGE part is used.
Table 5-386 List of Elements Described in MESSAGE PartNo.
1.

Element Name

Description Details
Required/Optional
Describes the message used to acquire the energy
P_GetEnergyInfo**
management information.
Required*2
For "**", see detailed description specifications.
*2: Required only when the MESSAGE part is used. Optional when the MESSAGE part is not
used.
Table 5-387 lists the elements described in the COMM_IF_COMMAND part. For details of thedescription specifications of the elements, see Section 5.5.8.4.
Table 5-387 List of Elements Described in COMM_IF_COMMAND PartNo.

Element Name

1.

GetEnergyInfoCommand**Description Details
Describes the command information used to acquire
the energy management information.
For "**", see detailed description specifications.

Required/Optional
Required

Table 5-388 lists the elements described in the BLOCK_COMMAND part. For details of the description
specifications of the elements, see Section 5.5.8.5.
Table 5-388 List of Elements Described in BLOCK_COMMAND Part
No.
1.

CLPA

Element Name

Description Details
Required/Optional
Describes the command information used to acquire
GetEnergyInfoCommand** the energy management information.
Required*3
For "**", see detailed description specifications.
*3: Required only when the BLOCK_COMMAND part is used. Optional when the
BLOCK_COMMAND part is not used.

BAP-C2008ENG-001-K
1-369

Table 5-389 lists the elements described in the COMMAND_ARGUMENT part (specifications common
to COMM_IF and BLOCK sections). We recommend writing "GetEnergyInfoArgument" for the label
name of the COMMAND_ARGUMENT part. While all elements are optionally described, at least one
element must be described (A description of only the COMMAND_ARGUMENT part in which theseelements are not described is not permitted). For details of the description specifications of theelements, see Section 5.5.8.6.
Table 5-389 List of Elements Described in COMMAND_ARGUMENT PartNo.
Element Name
1. P_AverageCurrent
2. P_AverageVoltage
3. P_ElectricPower
4. P_ElectricEnergy
5. P_PowerDistributionTime
6. P_RunningTime
7. P_1_PhaseCurrent
8. P_2_PhaseCurrent
9. P_3_PhaseCurrent
10. P_1_2lineVoltage
11. P_2_3lineVoltage
12. P_3_1lineVoltage
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.

P_1_PhaseCurrentDemand
P_2_PhaseCurrentDemand
P_3_PhaseCurrentDemand
P_ElectricPowerDemand
P_PowerFactor
P_Frequency
P_ReactiveEnergy
P_1_0PhaseVoltage
P_2_0PhaseVoltage
P_3_0PhaseVoltage

Description Details
Total current
Total line voltage
Electric power
Electric energy
Integrated energization time
Actual operating time
One-phase current
Two-phase current
Three-phase current
Line voltage between the first phaseand the second phase
Line voltage between the second
phase and the third phase
Line voltage between the third phaseand the first phase
One-phase demand current
Two-phase demand current
Three-phase demand current
Demand electric power
Power factor
Frequency
Reactive power
One-phase voltage
Two-phase voltage
Three-phase voltage

Required/Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional

Note that while multiple parts are used to describe the acquisition of energy management information,
there are no regulations regarding the label name of any part other than the COMMAND_ARGUMENT
part. (The CSP+ file creator can freely assign label names.)

CLPA

BAP-C2008ENG-001-K
1-370

5.5.8.2 Description details of elements described in METHOD part(1) Item description of P_GetEnergyInfo** element
Table 5-390 Item Description Specifications of P_GetEnergyInfo** Element
No.

Item Name

1. LABEL
2. LABEL2
3. CATEGORY
4. NAME
5. TARGET
6. METHOD_TYPE
7. WRITE_REGISTER
8. WRITE_DATA
9. WRITE_DATATYPE
10. READ_REGISTER
11. READ_DATA
12. READ_DATATYPE
13. INTERLOCK
14. REQ_FLAG
15. END_CONDITION
16. ERR_CONDITION
17. ERR_REGISTER
18. ERR_CODE_RANGE
19. RELATED_METHOD
20. COMMENT

CLPA

Description Details
Write "P_GetEnergyInfo**".
Write any string, including spaces, in the area marked by the asterisks (**).
(Example: P_GetEnergyInfoMethod)
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Write a reference to the elements of the COMM_IF_COMMAND part
specified by Section 5.5.8.4.
Write "COMMAND".
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.
Not specified.
Write a value in the same manner as the regular METHOD part.

BAP-C2008ENG-001-K
1-371

(a) Item description example of P_GetEnergyInfoMethod element<p:methodMember label="P_GetEnergyInfoMethod"><p:label2><p:item>GetEnergyInfo</p:item></p:label2><p:name><p:item>Get Energy Information</p:item></p:name><p:target><p:item>GetEnergyInfoCommand</p:item></p:target><p:methodType><p:item>COMMAND</p:item></p:methodType><p:writeRegister><p:item>&lt;RWw2&gt;&lt;RWw3&gt;</p:item></p:writeRegister><p:writeData><p:item>&lt;$(ARGUMENT.P_ElectricPower.ASSIGN)&gt;&lt;$(ARGUME
NT.P_ElectricEnergy.ASSIGN)&gt;</p:item></p:writeData><p:writeDatatype><p:item>&lt;WORD&gt;&lt;WORD&gt;</p:item></p:writeDatatype><p:readRegister><p:item>&lt;RWr2&gt;&lt;RWr3&gt;</p:item></p:readRegister ><p:readData><p:item>&lt;$(ARGUMENT.P_ElectricPower.VALUE)&gt;&lt;$(ARGUMENT.P_ElectricEnergy.VALUE)&gt;</p:item></p:readData><p:readDatatype><p:item>&lt;$(ARGUMENT.P_ElectricPower.DATATYPE)&gt;&lt;$(ARGUMENT.P_ElectricEnergy.DATATYPE)</p:item></p:readDatatype><p:interlock><p:item>RXF==OFF&amp;&amp;RYF==OFF</p:item></p:interlock><p:reqFlag><p:item>RYF==ON</p:item></p:reqFlag><p:endCondition><p:item>RXF==ON</p:item></p:endCondition><p:comment>Get Electric Power and Electric Energy</p:comment></p:methodMember>

CLPA

BAP-C2008ENG-001-K
1-372

5.5.8.3 Description details of elements described in MESSAGE part(1) Item description of P_GetEnergyInfo** element
Table 5-391 Item Description Specifications of P_GetEnergyInfo** Element
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.

CLPA

Item Name

Description Details

Write "P_GetEnergyInfo**".
Write any string, including spaces, in the area marked by the asterisks (**).
(Example: P_GetEnergyInfoMessage)
Not specified.
LABEL2
Write a value in the same manner as the regular MESSAGE part.
Not specified.
CATEGORY
Write a value in the same manner as the regular MESSAGE part.
Not specified.
NAME
Write a value in the same manner as the regular MESSAGE part.
Write a reference to the COMM_IF_COMMAND part specified by Section
TARGET
5.5.8.4.
MESSAGE_TYPE
Write "COMMAND".
Not specified.
REQUEST_TYPE
Write a value in the same manner as the regular MESSAGE part.
Not specified.
REQUEST_DATA
Write a value in the same manner as the regular MESSAGE part.
Not specified.
REQUEST_DATATYPE
Write a value in the same manner as the regular MESSAGE part.
Not specified.
RESPONSE_TYPE
Write a value in the same manner as the regular MESSAGE part.
Not specified.
RESPONSE_DATA
Write a value in the same manner as the regular MESSAGE part.
Not specified.
RESPONSE_DATATYPE
Write a value in the same manner as the regular MESSAGE part.
Not specified.
ERR_TYPE
Write a value in the same manner as the regular MESSAGE part.
Not specified.
ERR_CODE_RANGE
Write a value in the same manner as the regular MESSAGE part.
Not specified.
RELATED_MESSAGE
Write a value in the same manner as the regular MESSAGE part.
Not specified.
COMMENT
Write a value in the same manner as the regular MESSAGE part.
LABEL

BAP-C2008ENG-001-K
1-373

(a) Item description example of P_GetEnergyInfoMessage element<p:messageMember label="P_GetEnergyInfoMessage"><p:label2><p:item>GetEnergyInfo</p:item></p:label2><p:name><p:item>Get Energy Information</p:item></p:name><p:target><p:item>GetEnergyInfoCommand</p:item></p:target><p:messageType><p:item>COMMAND</p:item></p:messageType><p:requestType><p:item>rdReqST_Binary</p:item></p:requestType><p:requestData><p:item>&lt;0x0613&gt;&lt;0x0000&gt;&lt;0x00000102&gt;&lt;$0x0002&gt;</p:item></p:requestData><p:requestDatatype><p:item>&lt;WORD&gt;&lt;WORD&gt;&lt;DWORD&gt;&lt;WORD&gt;</p:item></p:requestDatatype><p:responseType><p:item>rdResST_Binary</p:item></p:responseType><p:responseData><p:item>&lt;$(ARGUMENT.P_ElectricPower.VALUE)&gt;&lt;$(ARGU
MENT.P_ElectricEnergy.VALUE)&gt;</p:item></p:responseData><p:responseDatatype><p:item>&lt;$(ARGUMENT.P_ElectricPower.DATATYPE)&gt;&lt;$(ARGUMENT.P_ElectricEnergy.DATATYPE)&gt;</p:item></p:responseDatatype><p:comment>Get Electric Power and Electric Energy</p:comment></p:messageMember>

CLPA

BAP-C2008ENG-001-K
1-374

5.5.8.4 Description details of elements described in COMM_IF_COMMAND part(1) Item description of GetEnergyInfoCommand** element
Table 5-392 Item Description of GetEnergyInfoCommand Element
No.

Item Name

1. LABEL
2. LABEL2
3. CATEGORY
4. NAME

5. ARGUMENT

6. REF

7. COMMENT

Description Details
Write "GetEnergyInfoCommand**".
Write any string, including spaces, in the area marked by the asterisks (**).
(Example: GetEnergyInfoCommand1)
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
[When energy management information is managed on module main body side]
Write prohibited.
[When energy management information is managed on communication module
side]
Write a reference to the COMMAND_ARGUMENT part specified by Table 5-389.
[When energy management information is managed on module main body side]
Write a reference to the elements of the BLOCK_COMMAND part specified by
Section 5.5.8.5.
[When energy management information is managed on communication module
side]
Write prohibited.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.

(a) Item description example of GetEnergyInfoCommand** element<p:commIfCommandMember label="GetEnergyInfoCommand"><p:label2><p:item>GetEnergyInfo</p:item></p:label2><p:name><p:item>Get Energy Information</p:item></p:name><p:ref><p:item>BlockSec.BlockCommand.GetEnergyInfoCommand</p:item></p:ref></p:commIfCommandMember>

CLPA

BAP-C2008ENG-001-K
1-375

5.5.8.5 Description details of elements described in BLOCK_COMMAND part(1) Item description of GetEnergyInfoCommand** element
Table 5-393 Item Description Specifications of GetEnergyInfoCommand** Element
No.

Item Name

1. LABEL
2. LABEL2
3. CATEGORY
4. NAME
5. ARGUMENT
6. COMMENT

Description Details
Write "GetEnergyInfoCommand**".
Write any string, including spaces, in the area marked by the asterisks (**).
(Example: GetEnergyInfoCommand1)
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Write a reference to the COMMAND_ARGUMENT part specified in Table 5-389.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.

(a) Item description example of GetEnergyInfoCommand** element<p:blockCommandMember label="GetEnergyInfoCommand"><p:label2><p:item>GetEnergyInfo</p:item></p:label2><p:name><p:item>Get Energy Information</p:item></p:name><p:argument><p:item>GetEnergyInfoArgument</p:item></p:argument></p:blockCommandMember>

CLPA

BAP-C2008ENG-001-K
1-376

5.5.8.6 Description details of elements described in COMMAND_ARGUMENT part(1) Item description of P_AverageCurrent element
Table 5-394 Item Description Specifications of P_AverageCurrent Element
No.
Item Name
1. LABEL
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_AverageCurrent".
Write "P_AverageCurrent" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Total Current" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_AverageCurrent element<p:commandArgumentMember label="P_AverageCurrent"><p:label2><p:item>P_AverageCurrent</p:item></p:label2><p:name><p:item>Total current</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-377

(2) Item description of P_AverageVoltage element
Table 5-395 Item Description Specifications of P_AverageVoltage Element
No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_AverageVoltage".
Write "P_Average Voltage" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Total Line Voltage" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_AverageVoltage element<p:commandArgumentMember label="P_AverageVoltage"><p:label2><p:item>P_AverageVoltage</p:item></p:label2><p:name><p:item>Total Line Voltage</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-378

(3) Item description of P_ElectricPower element
Table 5-396 Item Description Specifications of P_ElectricPower Element
No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_ElectricPower".
Write "P_ElectricPower" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Electric Power" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_ElectricPower element<p:commandArgumentMember label="P_ElectricPower"><p:label2><p:item>P_ElectricPower</p:item></p:label2><p:name><p:item>Electric Power</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-379

(4) Item description of P_ElectricEnergy element
Table 5-397 Item Description Specifications of P_ElectricEnergy Element
No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_ElectricEnergy".
Write "P_ElectricEnergy" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Electric Energy" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_ElectricEnergy element<p:commandArgumentMember label="P_ElectricEnergy"><p:label2><p:item>P_ElectricEnergy</p:item></p:label2><p:name><p:item>Electric Energy</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-380

(5) Item description of P_PowerDistrubutionTime element
Table 5-398 Item Description Specifications of P_PowerDistributionTime Element
No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_PowerDistributionTime".
Write "P_PowerDistributionTime" in the case of English CSP+ files.
[Recommended specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Integrated Energization Time" in the case of English CSP+ files.
[Recommended specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_PowerDistributionTime element<p:commandArgumentMember label="P_PowerDistributionTime"><p:label2><p:item>P_PowerDistributionTime</p:item></p:label2><p:name><p:item>Integrated Energization Time</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-381

(6) Item description of P_RunningTime element
Table 5-399 Item Description Specifications of P_RunningTime Element
No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_RunningTime".
Write "P_RunningTime" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Actual Operating Time" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_RunningTime element<p:commandArgumentMember label="P_RunningTime"><p:label2><p:item>P_RunningTime</p:item></p:label2><p:name><p:item>Actual Operating Time</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-382

(7) Item description of P_1_PhaseCurrent element
Table 5-400 Item Description Specifications of P_1_PhaseCurrent Element
No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_1_PhaseCurrent".
Write "P_1_PhaseCurrent" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "One-Phase Current" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_1_PhaseCurrent element<p:commandArgumentMember label="P_1_PhaseCurrent"><p:label2><p:item>P_1_PhaseCurrent</p:item></p:label2><p:name><p:item>One-Phase Current</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-383

(8) Item description of P_2_PhaseCurrent element
Table 5-401 Item Description Specifications of P_2_PhaseCurrent Element
No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_2_PhaseCurrent".
Write "P_2_PhaseCurrent" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Two-Phase Current" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_2_PhaseCurrent element<p:commandArgumentMember label="P_2_PhaseCurrent"><p:label2><p:item>P_2_PhaseCurrent</p:item></p:label2><p:name><p:item>Two-PhaseCurrent</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-384

(9) Item description of P_3_PhaseCurrent element
Table 5-402 Item Description Specifications of P_3_PhaseCurrent Element
No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_3_PhaseCurrent".
Write "P_3_PhaseCurrent" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Three-Phase Current" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_3_PhaseCurrent element<p:commandArgumentMember label="P_3_PhaseCurrent"><p:label2><p:item>P_3_PhaseCurrent</p:item></p:label2><p:name><p:item>Three-Phase Current</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-385

(10)

Item description of P_1_2lineVoltage element
Table 5-403 Item Description Specifications of P_1_2lineVoltage Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_1_2lineVoltage".
Write "P_1_2lineVoltage" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "1-2 Line Voltage" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_1_2lineVoltage element<p:commandArgumentMember label="P_1_2lineVoltage"><p:label2><p:item>P_1_2lineVoltage</p:item></p:label2><p:name><p:item>1-2 Line Voltage</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-386

(11)

Item description of P_2_3lineVoltage element
Table 5-404 Item Description Specifications of P_2_3lineVoltage Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_2_3lineVoltage".
Write "P_2_3lineVoltage" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "2-3 Line Voltage" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_2_3lineVoltage element<p:commandArgumentMember label="P_2_3lineVoltage"><p:label2><p:item>P_2_3lineVoltage</p:item></p:label2><p:name><p:item>2-3 Line Voltage</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-387

(12)

Item description of P_3_1lineVoltage element
Table 5-405 Item Description Specifications of P_3_1lineVoltage Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_3_1lineVoltage".
Write "P_3_1lineVoltage" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "3-1 Line Voltage" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_3_1lineVoltage element<p:commandArgumentMember label="P_3_1lineVoltage"><p:label2><p:item>P_3_1lineVoltage</p:item></p:label2><p:name><p:item>3-1 Line Voltage</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-388

(13)

Item description of P_1_PhaseCurrentDemand element
Table 5-406 Item Description Specifications of P_1_PhaseCurrentDemand Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_1_PhaseCurrentDemand".
Write "P_1_PhaseCurrentDemand" in the case of English CSP+ files.
[Recommended specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "One-Phase Demand Current" in the case of English CSP+ files.
[Recommended specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_1_PhaseCurrentDemand element<p:commandArgumentMember label="P_1_PhaseCurrentDemand"><p:label2><p:item>P_1_PhaseCurrentDemand</p:item></p:label2><p:name><p:item>One-Phase Demand Current</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-389

(14)

Item description of P_2_PhaseCurrentDemand element
Table 5-407 Item Description Specifications of P_2_PhaseCurrentDemand Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_2_PhaseCurrentDemand".
Write "P_2_PhaseCurrentDemand" in the case of English CSP+ files.
[Recommended specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Two-Phase Demand Current" in the case of English CSP+ files.
[Recommended specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_2_PhaseCurrentDemand element<p:commandArgumentMember label="P_2_PhaseCurrentDemand"><p:label2><p:item>P_2_PhaseCurrentDemand</p:item></p:label2><p:name><p:item>Two-Phase Demand Current</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-390

(15)

Item description of P_3_PhaseCurrentDemand element
Table 5-408 Item Description Specifications of P_3_PhaseCurrentDemand Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_3_PhaseCurrentDemand".
Write "P_3_PhaseCurrentDemand" in the case of English CSP+ files.
[Recommended specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Three-Phase Demand Current" in the case of English CSP+ files.
[Recommended specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_3_PhaseCurrentDemand element<p:commandArgumentMember label="P_3_PhaseCurrentDemand"><p:label2><p:item>P_3_PhaseCurrentDemand</p:item></p:label2><p:name><p:item>Three-Phase Demand Current</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-391

(16)

Item description of P_ElectricPowerDemand element
Table 5-409 Item Description Specifications of P_ElectricPowerDemand Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_ElectricPowerDemand".
Write "P_ElectricPowerDemand" in the case of English CSP+ files.
[Recommended specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Demand Electric Power" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_ElectricPowerDemand element<p:commandArgumentMember label="P_ElectricPowerDemand"><p:label2><p:item>P_ElectricPowerDemand</p:item></p:label2><p:name><p:item>Demand Electric Power</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-392

(17)

Item description of P_PowerFactor element
Table 5-410 Item Description Specifications of P_PowerFactor Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_PowerFactor".
Write "P_PowerFactor" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Power Factor" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_PowerFactor element<p:commandArgumentMember label="P_PowerFactor"><p:label2><p:item>P_PowerFactor</p:item></p:label2><p:name><p:item>Power Factor</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-393

(18)

Item description of P_Frequency element
Table 5-411 Item Description Specifications of P_Frequency Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_Frequency".
Write "P_Frequency" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Frequency" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_Frequency element<p:commandArgumentMember label="P_Frequency"><p:label2><p:item>P_Frequency</p:item></p:label2><p:name><p:item>Frequency</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-394

(19)

Item description of P_ReactiveEnergy element
Table 5-412 Item Description Specifications of P_ReactiveEnergy Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_ReactiveEnergy".
Write "P_ReactiveEnergy" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "Reactive Energy" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_ReactiveEnergy element<p:commandArgumentMember label="P_ReactiveEnergy"><p:label2><p:item>P_ReactiveEnergy</p:item></p:label2><p:name><p:item>Reactive Energy</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-395

(20)

Item description of P_1_0PhaseVoltage element
Table 5-413 Item Description Specifications of P_1_0PhaseVoltage Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_1_0PhaseVoltage".
Write "P_1_0PhaseVoltage" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "1-0 Phase Voltage" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_1_0PhaseVoltage element<p:commandArgumentMember label="P_1_0PhaseVoltage"><p:label2><p:item>P_1_0PhaseVoltage</p:item></p:label2><p:name><p:item>One-Phase Voltage</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-396

(21)

Item description of P_2_0PhaseVoltage element
Table 5-414 Item Description Specifications of P_2_0PhaseVoltage Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_2_0PhaseVoltage".
Write "P_2_0PhaseVoltage" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "2-0 Phase Voltage" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_2_0PhaseVoltage element<p:commandArgumentMember label="P_2_0PhaseVoltage"><p:label2><p:item>P_2_0PhaseVoltage</p:item></p:label2><p:name><p:item>Two-Phase Voltage</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-397

(22)

Item description of P_3_0PhaseVoltage element
Table 5-415 Item Description Specifications of P_3_0PhaseVoltage Element

No.
Item Name
LABEL
1.
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Write "P_3_0PhaseVoltage".
Write "P_3_0PhaseVoltage" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "3-0 Phase Voltage" in the case of English CSP+ files. [Recommended
specifications]
Select and write one of the following: unsigned integer type, real number type.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Normally, write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of P_3_0PhaseVoltage element<p:commandArgumentMember label="P_3_0PhaseVoltage"><p:label2><p:item>P_3_0PhaseVoltage</p:item></p:label2><p:name><p:item>Three-Phase Voltage</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-398

5.5.9Convention for acquiring status codes
SLMP defines specifications related to status code acquisition.

5.5.9.1 Overview
This section shows the convention for acquiring status codes from a module using SLMP to display
the meaning of the status codes, corrective actions for them, and more. This convention, in the current
version, can only be written in CSP+ for the Ethernet connection unit. Figure 5-53 shows an image ofthe structure when the acquisition of the status code is described.
COMM_IF section

BLOCK section

COMM_IF_COMMAND part

BLOCK_COMMAND part
Command 1

P_GetStatusCommand element

COMMAND_ARGUMENT part
Argument 1
ENUM part
Status code 1
Status code 2
Status code 3

Figure 5-53 Image of Structure When Acquisition of Status Information Is Described
One element is described in each of the COMM_IF_COMMAND part, BLOCK_COMMAND part, andCOMMAND_ARGUMENT part.
A status code is acquired with use of the GetStatus command of SLMP.
Table 5-416 lists the elements described in the COMM_IF_COMMAND part. For details of thedescription specifications of the elements, see Section 5.5.9.2.
Table 5-416 List of Elements Described in COMM_IF_COMMAND PartNo.
1.

Element Name
P_GetStatusCommand

Description Details
Describes the command information used toacquire the status code.

Required/Optional
Required

Table 5-417 lists the elements described in the BLOCK_COMMAND part. For details of the description
specifications of the elements, see Section 5.5.9.3.
Table 5-417 List of Elements Described in BLOCK_COMMAND PartNo.
1.

Element Name
(Name Optional)

Description Details
Describes the command information used to acquire
the status code.

Required/Optional
Required*1

Table 5-418 lists the elements described in the COMMAND_ARGUMENT part. For details of thedescription specifications of the elements, see Section 5.5.9.4.

CLPA

BAP-C2008ENG-001-K
1-399

Table 5-418 List of Elements Described in COMMAND_ARGUMENT PartNo.
1.

Element Name
(Name Optional)

Description Details
Describes the argument of the status codeacquisition command (status code).

Required/Optional
Required

Table 5-419 lists the elements described in the ENUM part. For details of the description specificationsof the elements, see Section 5.5.9.4.
Table 5-419 List of Elements Described in ENUM PartNo.
1.

Element Name
(Name Optional)

Description Details
Describes a status code value, its meaning, and acorrective action.

Required/Optional
Required

Note that while multiple parts are used to describe the acquisition of status codes, there are no
regulations regarding the label name of any part. (The CSP+ file creator can freely assign labelnames.)CLPA

BAP-C2008ENG-001-K
1-400

5.5.9.2 Description details of elements described in COMM_IF_COMMAND part(1) Item description of P_GetStatusCommand element
Table 5-420 Item Description of P_GetStatusCommand Element
No.
Item Name
1. LABEL
2. LABEL2
3. CATEGORY
4. NAME
5. ARGUMENT
6. REF
7. COMMENT

Description Details
Write "P_GetStatusCommand".
Write "P_GetStatusCommand" in the case of English CSP+ files. [Recommended
specifications]
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
Write "Status Code Acquisition Command" in the case of English CSP+ files.
[Recommended specifications]Write prohibited.
Write a reference to the BLOCK_COMMAND part specified by Section 5.5.9.3.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.

(a) Item description example of P_GetStatusCommand element<p:commIfCommandMember label="P_GetStatusCommand"><p:label2><p:item>P_GetStatusCommand</p:item></p:label2><p:name><p:item>Status Code Acquisition Command</p:item></p:name><p:ref><p:item>BlockSec.BlockCommand.GetStatusCommand</p:item></p:ref></p:commIfCommandMember>

5.5.9.3 Description details of elements described in BLOCK_COMMAND part(1) Item description of BLOCK_COMMAND part element
Table 5-421 Item Description Specifications of Element
No.

Item Name

1. LABEL
2. LABEL2
3. CATEGORY
4. NAME
5. ARGUMENT
6. COMMENT

Description Details
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Write a reference to the COMMAND_ARGUMENT part specified by Section
5.5.9.4.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.

(a) Item description example of element<p:blockCommandMember label="GetStatusCommand"><p:label2><p:item>P_GetStatusCommand</p:item></p:label2><p:name><p:item>Status Code Acquisition Command</p:item></p:name><p:argument><p:item>StatusArgument</p:item></p:argument></p:blockCommandMember>

CLPA

BAP-C2008ENG-001-K
1-401

5.5.9.4 Description details of elements described in COMMAND_ARGUMENT part(1) Item description of COMMAND_ARGUMENT part element
Table 5-422 Item Description Specifications of Element
No.

Item Name

1. LABEL
2. LABEL2
3. CATEGORY
4. NAME
5. DATATYPE
6. DEFAULT
7. RANGE
8. MIN_INC
9. ENG_UNIT
10. ACCESS
11. ASSIGN
12. REF
13. COMMENT

Description Details
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "WORD".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write a reference to the COMMAND_ARGUMENT part specified by RANGE.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write "R".
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of ErrorCode element<p:commandArgumentMember label="StatusCode"><p:label2><p:item>StatusCode</p:item></p:label2><p:name><p:item>Status Code</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:range><p:enumRefItem>EnumStatusCode</p:enumRefItem></p:range><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-402

5.5.9.5 Description details of elements described in ENUM part(1) Item description of ENUM part element
Table 5-423 Item Description Specifications of ENUM Part Element
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.
5.
6.

NAME
CODE
COMMENT

Description Details
Not specified.
Write a value in the same manner as the regular ENUM part.
Not specified.
Write a value in the same manner as the regular ENUM part.
Not specified.
Write a value in the same manner as the regular ENUM part.
Describes the name of a status code value.
Describes a status code value.
Describes the meaning, a corrective action, and more of the status code.

(a) Item description example of ENUM part element<p:enum label="EnumStatusCode "><p:enumMember label="enum1"><p:name><p:item>Hardware Error</p:item></p:name><p:code><p:item>1</p:item></p:code><p:comment><p:item>Turn off the power once, and turn on the power again.
</p:item></p:comment></p:enumMember><p:enumMember label="enum2"><p:name><p:item>User Range Read Error</p:item></p:name><p:code><p:item>2</p:item></p:code><p:comment><p:item>This item turns on when an error is present in theuser range read from a flash memory. Turning on the error reset request
flag can reset (turn off) this flag. </p:item></p:comment></p:enumMember><p:enumMember label="enum3"><p:name><p:item>Flash Memory Write Error</p:item></p:name><p:code><p:item>3</p:item></p:code><p:comment><p:item>This item turns on when writing to a flash memory
failed. When this flag turns on, reset cannot be performed using theerror reset request flag because of a failure of the module itself.
</p:item></p:comment></p:enumMember></p:enum>

CLPA

BAP-C2008ENG-001-K
1-403

5.5.10Specifications related to CC-Link IE TSN

5.5.10.1 Parts and elements related to error related information
The module has a function that records the information of any errors that occur during module
operation, and acquires that error information as related information via SNMP from an externalsource. This section describes the specifications of parts and elements when writing error related
information acquisition processing.
5.5.10.1.1.
Overview
Write error related information acquisition in the MESSAGE, COMM_IF_COMMAND,BLOCK_COMMAND, COMMAND_ARGUMENT, and ENUM parts. Figure 5-54 shows an image ofthe structure when describing the error related information acquisition. (The specifications are only
for CC-Link IE TSN since the RELATED_ELE item of the ENUM part is used.)
LABEL2 and NAME are recommended specifications, and other strings can be written.
In the case of devices for which station mode can be changed (profiles have multiple COMM_IF
sections), matching descriptions of each COMM_IF section is required. For details, see thedescription methods of each part.

COMM_IF section

BLOCK section

MESSAGE part

BLOCK_COMMAND part

P_GetDiagCodeInfo element

GetDiagCodeCommand element

COMM_IF_COMMAND part

COMMAND_ARGUMENT part

GetDiagCodeInfoCommand element

ErrorCode element

ENUM part

COMM_IF section

Error code 1

MESSAGE part

Error code 2

P_GetDiagCodeInfo element

COMM_IF_COMMAND part
COMMAND_ARGUMENT part

GetDiagCodeInfoCommand element

Structure data of error details

STRUCT part
Value of error detail information

Figure 5-54 Image of Structure When Describing Error Related Information Acquisition

CLPA

BAP-C2008ENG-001-K
1-404

Table 5-424 shows a list of elements described in the MESSAGE part. For details of the description
specifications of each element, see Section 5.5.10.1.2.
When a MESSAGE part has been written to one COMM_IF section of the profile which has multiple
COMM_IF sections, the MESSAGE part should be written to all the COMM_IF sections.
Table 5-424 List of Elements Written in MESSAGE PartNo.
Element Name
1.
P_GetDiagCodeInfo

Description Details
Required/Optional
Write the information used for diagnostics code Required
information acquisition.

Table 5-425 shows a list of elements described in the COMM_IF_COMMAND part. For details of thedescription specifications of each element, see Section 5.5.10.1.3.
When the profile has multiple sections, refer to the same BLOCK_COMMAND part element for theerror information acquisition from COMM_IF_COMMAND parts for error information acquisition of all
the COMM_IF sections.
Table 5-425 List of Elements Written in COMM_IF_COMMAND PartNo.
Element Name
1.
GetDiagCodeInfoCommand

Description Details
Write the command information used for diagnostics
code information acquisition.

Required/Optional
Required

Table 5-426 shows a list of elements described in the BLOCK_COMMAND part. For details of thedescription specifications of each element, see Section 5.5.10.1.4.
A single element of BLOCK_COMMAND part for the error related information acquisition can be
written in a profile.
Table 5-426 List of Elements Written in BLOCK_COMMAND PartNo.
Element Name
1.
GetDiagCodeCommand

Description Details
Write the command information used for diagnostics
code information acquisition.

Required/Optional
Required

Table 5-427 shows a list of elements described in the COMMAND_ARGUMENT part. For details of
the description specifications of each element, see Section 5.5.10.1.5.
Table 5-427 List of Elements Written in COMMAND_ARGUMENT PartNo.
Element Name
1.
ErrorCodeDescription Details
Write the error code information.

Required/Optional
Required

Table 5-428 shows a list of elements described in the ENUM part. For details of the description
specifications of each element, see Section 5.5.10.1.6.
Table 5-428 List of Elements Written in ENUM PartNo.
Element Name
1.
(Any name)

Description Details
Write the error detailed information.

Required/Optional
Required

Table 5-429 shows a list of elements described in the COMMAND_ARGUMENT part for the detailed
information structure definition. Describe the data structure for the detailed information according to
the following specifications.
[1] From the error code to the error details size are not described.
[2] Describe the elements of COMMAND_ARGUMENT in order so that the order of the data from theerror details size is indicated.
[3] To divide one word so that multiple information is held, express the information with a STRUCT
type. Please note that data larger than one word cannot be expressed with one STRUCT. (Use ispossible for only the division of one word.)[4] The STRING(x) type can be used as the DATATYPE item. The following shows the precautions on
the specifications of the error detailed data returned by a device when using STRING(x).
CLPA

BAP-C2008ENG-001-K
1-405

• Control characters excluding null characters cannot be inserted in the error details data.
• An error detailed data area for the number of characters specified in DATATYPE must be
allocated. For example, when STRING(16) is used, an error detailed data area for 8 words must be
allocated even for the case when 5 characters (3 words) are returned (do not use the 3 words atthe end for other error details data).
[5] For the specifiable data specifications (data size and others) as detailed information, refer to "CCLink IE TSN Specifications (Overview) (BAP-C2011ENG-001).
Describing the element is optional. For details of the description specifications of each element, see
Section 5.5.10.1.7.
Table 5-429 List of Elements Written in COMMAND_ARGUMENT Part for Detailed Information
Structure Definition
No.
Element Name
1.
(Any name)

Description Details
Write the structure of the error detailed information.

Required/Optional
Optional

Table 5-430 shows a list of elements described in the STRUCT part. For details of the description
specifications of each element, see Section 5.5.10.1.8.
Table 5-430 List of Elements Written in STRUCT PartNo.
Element Name
1.
(Any name)5.5.10.1.2.

Description Details
Write the structure for dividing the error details
information.

Required/Optional
Optional

Description details of elements written in MESSAGE part(1) Item description of P_GetDiagCodeInfo element
Table 5-431 Item Description Specifications of P_GetDiagCodeInfo Element
No.
1.
2.
3.
4.

Item NameLABELLABEL2
CATEGORYNAME

5.

TARGET

6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.

MESSAGE_TYPE
REQUEST_TYPE
REQUEST_DATAREQUEST_DATATYPERESPONSE_TYPERESPONSE_DATARESPONSE_DATATYPEERR_TYPEERR_CODE_RANGE
RELATED_MESSAGE
COMMENT

Description Details
Write "P_GetDiagCodeInfo".
Write "P_GetDiagCodeInfo". [Recommended specifications]Write prohibited.
Write "Diagnostics Code Information". [Recommended specifications]Write a reference to the COMM_IF_COMMAND part that you will write in Section
5.5.10.1.3.
Write "OTHER".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.

(a) Item description example of P_GetDiagCodeInfo element<p:messageMember label="P_GetDiagCodeInfo"><p:label2><p:item>P_GetDiagCodeInfo</p:item></p:label2><p:name><p:item>Diagnostics Code Information</p:item></p:name><p:target><p:item>CommandSec.GetDiagCodeInfoCommand</p:item></p:target><p:messageType><p:item>OTHER</p:item></p:messageType></p:messageMember>

CLPA

BAP-C2008ENG-001-K
1-406

Description details of elements written in COMM_IF_COMMAND part5.5.10.1.3.
(1)Item description of GetDiagCodeInfoCommand element
Table 5-432 Item Description Specifications of GetDiagCodeInfoCommand Element

No.
1.
2.
3.
4.
5.
6.
7.

Item NameLABELLABEL2
CATEGORYNAME
ARGUMENTREF
COMMENT

Description Details
Write "GetDiagCodeInfoCommand".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write a reference to the BLOCK_COMMAND part that you will write in Section 5.5.10.1.4.
Write prohibited.

(a) Item description example of GetDiagCodeInfoCommand element<p:commIfCommandMember label="GetDiagCodeInfoCommand"><p:ref><p:item>BlockSec.CommandSec.GetDiagCodeCommand</p:item></p:ref></p:commIfCommandMember>

Description details of elements written in BLOCK_COMMAND part5.5.10.1.4.
(1)Item description of GetDiagCodeCommand element
Table 5-433 Item Description Specifications of GetDiagCodeCommand Element

No.
Item Name
1.
LABEL
2.
LABEL2
3.
CATEGORY
4.

NAME

5.

ARGUMENT

6.

COMMENT

Description Details
Write "GetDiagCodeCommand".
Write prohibited.
Write prohibited.
Write "Diagnostics Code Information Acquisition Command". [Recommended
specifications]Write a reference to the COMMAND_ARGUMENT part that you will write in Section
5.5.10.1.5.
Write prohibited.

(a) Item description example of GetErrorLogCommand element<p:blockCommandMember label="GetErrorLogCommand"><p:label2><p:item>GetErrorLogCommand</p:item></p:label2><p:name><p:item>Diagnostics Code Information Acquisition
Command</p:item></p:name><p:argument><p:item>Command_Arg</p:item></p:argument></p:blockCommandMember>

CLPA

BAP-C2008ENG-001-K
1-407

5.5.10.1.5.
(1)

Description details of elements written in COMMAND_ARGUMENT part
Item description of ErrorCode element
Table 5-434 Item Description Specifications of ErrorCode Element

No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPEDEFAULTRANGE
MIN_INC
ENG_UNITACCESSASSIGNREF
COMMENT

Description Details
Write "ErrorCode".
Write prohibited.
Write prohibited.
Write "Error Code". [Recommended specifications]Write "WORD".
Write prohibited.
Write a reference to the ENUM part that you will write in Section 5.5.10.1.6.
Write prohibited.
Write prohibited.
Write "R".
Write prohibited.
Write prohibited.
Write prohibited.

(a) Item description example of ErrorCode element<p:commandArgumentMember label="ErrorCode"><p:label2><p:item>ErrorCode</p:item></p:label2><p:name><p:item>Error Code</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:range><p:enumRefItem>ErrorCodeList</p:enumRefItem></p:range><p:access><p:item>R</p:item></p:access></p:commandArgumentMember>

CLPA

BAP-C2008ENG-001-K
1-408

Description details of elements written in ENUM part5.5.10.1.6.
(1)Item description of ENUM part element
Table 5-435 Item Description Specifications of Elements of ENUM Part

No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.
5.

NAME
CODE

6.

RELATED_ELE

7.
8.

COMMENT1COMMENT2

Description Details
Not specified.
Write a value in the same manner as the regular ENUM part.
Not specified.
Write a value in the same manner as the regular ENUM part.
Not specified.
Write a value in the same manner as the regular ENUM part.
Write the name (overview) of the error code.
Write the error code (hexadecimal).
In the case of an error that has error details information, write the reference for thecorresponding detailed information structure definition part (COMMAND_ARGUMENT).
This can be omitted if the error does not have error details information.
Write the error cause.
Write the remedy.

(a) Item description example of ENUM part element<p:enum label="ErrorCodeList"><p:enumMember label="enum1"><p:name><p:item>Hardware Code</p:item></p:name><p:code><p:item>0x10</p:item></p:code><p:comment index="1"><p:item>Hardware Error of Module</p:item></p:comment><p:comment index="2"><p:item>Turn off and on the module power.
</p:item></p:comment></p:enumMember><p:enumMember label="enum2"><p:name><p:item>Error Outside Input Value Range</p:item></p:name><p:code><p:item>0x105</p:item></p:code><p:relatedEle><p:item>InputError</p:item></p:relatedEle><p:comment index="1"><p:item>A value larger than the maximum value set forthe parameter has been input.</p:item></p:comment><p:comment index="2"><p:item>Review the input or review the parametersetting. </p:item></p:comment></p:enumMember><p:enumMember label="enum3"><p:name><p:item>Remote Buffer Memory Access Error</p:item></p:name><p:code><p:item>0x150</p:item></p:code><p:comment index="1"><p:item>Outside the range of the remote buffer memoryis accessed by the REMFR/REMTO command. </p:item></p:comment><p:comment index="2"><p:item>Correct the setting data of the REMFR/REMTO
command so that access is performed within the range of the remote buffer
memory. </p:item></p:comment></p:enumMember></p:enum>

CLPA

BAP-C2008ENG-001-K
1-409

5.5.10.1.7.

Description details of elements written in COMMAND_ARGUMENT part for detailed
information structure definition(1) Item description of COMMAND_ARGUMENT part element for detailed information structure
definition
Table 5-436 Item Description Specifications of COMMAND_ARGUMENT Part Element for Detailed
Information Structure Definition
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

ASSIGN

12.

REF

13.

COMMENT

Description Details
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Write the name of the data structure definition of the detailed information.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.
Not specified.
Write a value in the same manner as the regular COMMAND_ARGUMENT part.

(a) Item description example of COMMAND_ARGUMENT part element<p:commandArgument label="InputError"><p:commandArgumentMember label="ele1"><p:name><p:item>Axis Number</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype></p:commandArgumentMember><p:commandArgumentMember label="ele2"><p:name><p:item>Input Value information</p:item></p:name><p:datatype><p:item>STRUCT InputInfo</p:item></p:datatype></p:commandArgumentMember></p:commandArgument>

CLPA

BAP-C2008ENG-001-K
1-410

5.5.10.1.8.
(1)

Description details of elements written in STRUCT part
Item description of STRUCT part element
Table 5-437 Item Description Specifications of STRUCT Part Element

No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

OFFSET

11.

REF

12.

COMMENT

Description Details
Not specified.
Write a value in the same manner as the regular STRUCT part.
Not specified.
Write a value in the same manner as the regular STRUCT part.
Not specified.
Write a value in the same manner as the regular STRUCT part.
Not specified.
Write a value in the same manner as the regular STRUCT part.
Not specified.
Write a value in the same manner as the regular STRUCT part.
Not specified.
Write a value in the same manner as the regular STRUCT part.
Not specified.
Write a value in the same manner as the regular STRUCT part.
Not specified.
Write a value in the same manner as the regular STRUCT part.
Not specified.
Write a value in the same manner as the regular STRUCT part.
Not specified.
Write a value in the same manner as the regular STRUCT part.
Not specified.
Write a value in the same manner as the regular STRUCT part.
Not specified.
Write a value in the same manner as the regular STRUCT part.

(a) Item description example of ErrorCode element<p:struct label="InputInfo"><p:structMember label="ele1"><p:name><p:item>Current Value</p:item></p:name><p:datatype><p:item>INT8</p:item></p:datatype><p:offset><p:item>0.0</p:item></p:offset></p:structMember><p:structMember label="ele2"><p:name><p:item>Maximum Value</p:item></p:name><p:datatype><p:item>INT8</p:item></p:datatype><p:offset><p:item>0.8</p:item></p:offset></p:structMember></p:struct>

Figure 5-55 shows examples of parts and elements of the error related information.

CLPA

BAP-C2008ENG-001-K
1-411

MESSAGE
P_GetDiagCodeInfo Diagnostics Code In

COMM_IF_COMMAND (LABEL=CommandSec)

BLOCK_COMMAND (LABEL=CommandSec)
Diagnostics Code Information A

COMMAND_ARGUMENT (LABEL=Command_Arg)
Error CodeENUM (LABEL=ErrorCodeList)
Turn off and on the module power.
If the error occurs again, the module may be damaged.

Hardware Error

Hardware Error of Module

Error Outside Input Value Range

A value larger than the maximum value set for the parameter has been input. Review the input or review the parameter setting.
Correct the setting data of the REMFR/REMTO
Outside the range of the remote buffer memory is accessed by thecommand so that access is performed within the range
REMFR/REMTO command.
of the remote buffer memory.

Remote Buffer Memory Access
Error

COMMAND_ARGUMENT (LABEL=InputError)
Axis Number
Input Value in

STRUCT (LABEL=InputInfo)
Current V
MaximuFigure 5-55 Description Example of Parts and Elements Related to Error Related Information

CLPA

BAP-C2008ENG-001-K
1-412

5.5.10.2 Convention related to MESSAGE for slave station parameter automatic settingWith CC-Link IE TSN, the parameters are written automatically when a slave station is reconnected or
introduced by turning on its power or online exchange. This section describes how to write slave
station parameter automatic setting.

5.5.10.2.1.
Overview
Slave station parameter automatic setting is written in the MESSAGE part. The following two
conventions are available as description methods.
[1] Method to indicate automatic setting using only one element (method to indicate using No. 1 ofTable 5-438)
All of the parameters exist in consecutive address areas, and description with this method is
possible when batch automatic setting is possible.
[2] Method to write "SEQ_TARGET" in TARGET to indicate automatic setting using multiple
elements (method to refer to multiple No. 3 elements from No. 2 of Table 5-438)
When the parameters exist in non-consecutive address areas, write the No. 3 element of Table
5-438 for the automatic setting process of every area.
Only any one element can be written for one COMM_IF section. Figure 5-56 shows an image of thestructure of slave station parameter automatic setting.

COMM_IF section
When describing with only one element
MESSAGE part

COMM_IF_PARAMETER part

Refer to parameters.

When the "SEQ_TARGET" element is described in TARGETMESSAGE part
Refer to the message with SEQ
MESSAGE part

COMM_IF_PARAMETER part

Refer to parameters.

Figure 5-56 Image of Structure When Describing MESSAGE for Slave Station Parameter Automatic
Setting
Table 5-438 shows a list of elements described in the MESSAGE part. For details of the description
specifications of each element, see Section 5.5.10.2.2.
Table 5-438 List of Elements Written in MESSAGE Part

CLPA

No.

Element Name

1.

(Any name)2.

(Any name)3.

(Any name)

Description Details
Write a message in which only one element (reference of
COMM_IF_PARAMETER part to TARGET) is written.
Write a message in which "SEQ_TARGET" is written in
TARGET.
Write a message of an element referred to from
SEQ_TARGET of No. 2.

Required/Optional
Required
Required
Required

BAP-C2008ENG-001-K
1-413

Table 5-439 shows a list of elements described in the COMM_IF_PARAMETER part. For details of
the description specifications of each element, see Section 5.5.10.2.3.

Table 5-439 List of Elements Written in COMM_IF_PARAMETER PartNo.

Element Name

1.

(Any name)5.5.10.2.2.
(1)

Description Details
Write the parameter information to set in slave station
parameter automatic setting.

Required/Optional
Required

Description details of elements written in MESSAGE part
Item description of element to write using only one element

Table 5-440 Item Description Specifications of Element Written Using Only One Element
No.
1.

2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.

CLPA

Item Name

Description Details
Not specified.
Write a value in the same manner as the regular MESSAGE part.
LABEL
The prefix cannot be set to "SLMP" because this is not an SLMP-based
MESSAGE.
Not specified.
LABEL2
Write a value in the same manner as the regular MESSAGE part.
Not specified.
CATEGORY
Write a value in the same manner as the regular MESSAGE part.
Not specified.
NAME
Write a value in the same manner as the regular MESSAGE part.
Write the reference to the COMM_IF_PARAMETER part that you will write in
TARGET
Section 5.5.10.2.3 in the format of "'Part Name'.*". *1
MESSAGE_TYPE
Write "AUTO_PARAMETER".
REQUEST_TYPE
Write prohibited.
Write the three items of the parameter starting address (hexadecimal), target
REQUEST_DATA
parameter size (hexadecimal), and "$(*.VALUE)" using the <> convention.
REQUEST_DATATYPE<DWORD><WORD><$(*.DATATYPE)>RESPONSE_TYPE
Write prohibited.
RESPONSE_DATA
Write prohibited.
RESPONSE_DATATYPE Write prohibited.
ERR_TYPE
Write prohibited.
ERR_CODE_RANGE
Write prohibited.
RELATED_MESSAGE
Write prohibited.
Not specified.
COMMENT
Write a value in the same manner as the regular MESSAGE part.
*1: All elements of COMM_IF_PARAMETER (all elements specified as TARGET of MESSAGE for theprocess in which TARGET is written with PARAMETER) that are the parameter writing targets need
to be written so that they become the targets of parameter automatic setting. However, elements
whose DATATYPE is constant (CONST) are out of this restriction. Therefore, some of the elements
can be written only in either part.

BAP-C2008ENG-001-K
1-414

(a) Item description example of element<p:messageMember label="P_WriteParam"><p:label2><p:item>P_WriteParam</p:item></p:label2><p:name><p:item>Parameter Batch Write</p:item></p:name><p:target><p:item>WriteParam.*</p:item></p:target><p:messageType><p:item>AUTO_PARAMETER</p:item></p:messageType><p:requestData><p:item>item>&lt;0x0401&gt;&lt;0x0000&gt;&lt;0x00000000&gt;&lt;$0x0006&gt;</
p:item></p:requestData><p:requestDatatype><p:item>&lt;WORD&gt;&lt;WORD&gt;&lt;DWORD&gt;&lt;WORD&gt;</p:item></p:requestDatatype></p:messageMember>(2)

Item description of element to write "SEQ_TARGET" to TARGET

Table 5-441 Item Description Specifications of Element to Write "SEQ_TARGET" to TARGET
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.

TARGETMESSAGE_TYPE
REQUEST_TYPE
REQUEST_DATAREQUEST_DATATYPERESPONSE_TYPERESPONSE_DATARESPONSE_DATATYPEERR_TYPEERR_CODE_RANGE
RELATED_MESSAGE

16.

COMMENT

Description Details
Not specified.
Write a value in the same manner as the regular MESSAGE part.
The prefix cannot be set to "SLMP" because this is not an SLMPbased MESSAGE.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Write "SEQ_TARGET".
Write "AUTO_PARAMETER".
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Write prohibited.
Refer to related elements from "SEQ".
Not specified.
Write a value in the same manner as the regular MESSAGE part.

(a) Item description example of element<p:messageMember label="P_SEQMessage"><p:label2><p:item>P_SEQMessage</p:item></p:label2><p:name><p:item>SEQ Batch Write</p:item></p:name><p:target><p:item>SEQ_TARGET</p:item></p:target><p:messageType><p:item>AUTO_PARAMETER</p:item></p:messageType><p:relatedMessage><p:item>&lt;SEQ MessageA&gt;&lt;SEQ MessageB&gt;</p:item></p:relatedMessage></p:messageMember>

CLPA

BAP-C2008ENG-001-K
1-415

(3)

Item description of elements referenced from the elements of "SEQ_TARGET"

Table 5-442 Item Description Specifications of Elements Referenced from "SEQ_TARGET" Element
No.

Item Name

Description Details

Not specified.
Write a value in the same manner as the regular MESSAGE part.
1.
LABEL
The prefix cannot be set to "SLMP" because this is not an SLMP-based
MESSAGE.
Not specified.
2.
LABEL2
Write a value in the same manner as the regular MESSAGE part.
Not specified.
3.
CATEGORY
Write a value in the same manner as the regular MESSAGE part.
Not specified.
4.
NAME
Write a value in the same manner as the regular MESSAGE part.
Write the reference to the COMM_IF_PARAMETER part that you will write in
5.
TARGET
Section 5.5.10.2.3 in the format of "'Part Name'.*". *1
6.
MESSAGE_TYPE
Write "OTHER".
7.
REQUEST_TYPE
Write prohibited.
Write the three items of the parameter starting address (hexadecimal), target
8.
REQUEST_DATA
parameter size (hexadecimal), and "$(*.VALUE)" using the <> convention.
9.
REQUEST_DATATYPE<DWORD><WORD><$(*.DATATYPE)>
10. RESPONSE_TYPE
Write prohibited.
11. RESPONSE_DATA
Write prohibited.
12. RESPONSE_DATATYPE
Write prohibited.
13. ERR_TYPE
Write prohibited.
14. ERR_CODE_RANGE
Write prohibited.
15. RELATED_MESSAGE
Write prohibited.
Not specified.
16. COMMENT
Write a value in the same manner as the regular MESSAGE part.
*1: All elements of COMM_IF_PARAMETER (all elements specified as TARGET of MESSAGE for
the process in which TARGET is written with PARAMETER) that are the parameter writing targets
need to be written so that they become the targets of parameter automatic setting. However,elements whose DATATYPE is constant (CONST) are out of this restriction. Therefore, some ofthe elements can be written only in either part.
(a) Item description example of element<p:messageMember label="MessageA"><p:label2><p:item>MessageA</p:item></p:label2><p:name><p:item>Message A</p:item></p:name><p:target><p:item>WriteParam.*</p:item></p:target><p:messageType><p:item>OTHER</p:item></p:messageType><p:requestData><p:item>item>&lt;0x0401&gt;&lt;0x0000&gt;&lt;0x00000000&gt;&lt;$0x0006&gt;</
p:item></p:requestData><p:requestDatatype><p:item>&lt;WORD&gt;&lt;WORD&gt;&lt;DWORD&gt;&lt;WORD&gt;</p:item></p:requestDatatype></p:messageMember>

CLPA

BAP-C2008ENG-001-K
1-416

Description details of elements written in COMM_IF_PARAMETER part5.5.10.2.3.
(1)Item description of COMM_IF_PARAMETER part element
Table 5-443 Item Description Specifications of COMM_IF_PARAMETER Part Element

No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

WRITE_ORDER

12.

ASSIGN13.

UI_ATTRIBUTE

14.

REF

15.

COMMENT

Description Details
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER part.

(a) Item description example of element<p:commIfParameterMember label="WriteParam"><p:label2><p:item>WriteParam</p:item></p:label2><p:name><p:item>Write Parameter 1</p:item></p:name><p:assign><p:item>RW</p:item></p:assign><p:assign><p:item>RWw9</p:item></p:assign><p:ref><p:item>BlockSec.BlockParam.WriteParam</p:item></p:ref></p:commIfParameterMember>

CLPA

BAP-C2008ENG-001-K
1-417

5.5.10.3 Parts and elements indicating parameters for safety communication function
This section describes the specifications of parts and elements when writing the parameters of thesafety communication function of CC-Link IE TSN.

5.5.10.3.1.
Overview
When writing the parameters specified in the safety specifications, write them in accordance with thespecifications shown in this section. However, LABEL2 and NAME are recommended specifications,and other strings can be written. Furthermore, the items that are not described are optional. The
parameters of the safety communication function are written in the COMM_IF_PARAMETER and
BLOCK_PARAMETER parts.

COMM_IF section

BLOCK section

COMM_IF_PARAMETER part

BLOCK_PARAMETER part

P_TransIntervalMonitorTime element

P_TransIntervalMonitorTime element

P_SafetyCertCode element

P_SafetyCertCode element

Figure 5-57 Image of Structure When Describing Safety Communication Function Parameters
Table 5-444 shows a list of elements described in the COMM_IF_PARAMETER part. For details of
the description specifications of each element, see Section 5.5.10.3.2.

Table 5-444 List of Elements Written in COMM_IF_PARAMETER PartNo.

Element Name

1.

P_TransIntervalMonitorTime

2.

P_SafetyCertCode

Description Details
Write the transmission interval monitoring time ofthe safety communication function.
Write the safety certification code of the safety
communication function.

Required/Optional
Required
Required

Table 5-445 shows a list of elements described in the BLOCK_PARAMETER part. For details of thedescription specifications of each element, see Section 5.5.10.3.3.

Table 5-445 List of Elements Written in BLOCK_PARAMETER PartNo.

Element Name

1.

P_TransIntervalMonitorTime

2.

P_SafetyCertCode

CLPA

Description Details
Write the transmission interval monitoring time ofthe safety communication function.
Write the safety certification code of the safety
communication function.

Required/Optional
Required
Required

BAP-C2008ENG-001-K
1-418

Description details of elements written in COMM_IF_PARAMETER part5.5.10.3.2.
(1)

Item description of P_TransIntervalMonitorTime element in COMM_IF_PARAMETER part
Table 5-446 Item Description Specifications of P_TransIntervalMonitorTime Element in
COMM_IF_PARAMETER Part

Item Name

No.
1.
2.

LABEL
LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

WRITE_ORDER

12.

ASSIGN13.

UI_ATTRIBUTE

14.

REF

15.

COMMENT

Description Details
Write "P_TransIntervalMonitorTime".
Write "P_TransIntervalMonitorTime".
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Write "Transmission Interval Monitoring Time",
May be omitted because this case uses the value of the reference source of the
REF item.
When writing, write "UINT16".
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
May be omitted because this case uses the value of the reference source of the
REF item.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Write prohibited.
May be omitted because this case uses the value of the reference source of the
REF item.
When writing, write "ms".
May be omitted because this case uses the value of the reference source of the
REF item.
When writing, write "W" or "RW".
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Describe the reference to the "P_TransIntervalMonitorTime" element of the
BLOCK_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.

(a) Item description example of element<p:commIfParameterMember label="P_TransIntervalMonitorTime"><p:label2><p:item>P_TransIntervalMonitorTime</p:item></p:label2><p:name><p:item>Transmission Interval Monitoring Time</p:item></p:name><p:ref><p:item>BlockSec.BlockParameter.P_TransIntervalMonitorTime</p:item></p:ref></p:commIfParameterMember>

CLPA

BAP-C2008ENG-001-K
1-419

(2)

Item description of P_SafetyCertCode element in COMM_IF_PARAMETER part

Table 5-447 Item Description Specifications of P_SafetyCertCode Element in COMM_IF_PARAMETERPart

Item Name

No.
1.
2.

LABEL
LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.
9.

MIN_INC
ENG_UNIT10.

ACCESS

11.

WRITE_ORDER

12.

ASSIGN13.

UI_ATTRIBUTE

14.

REF

15.

COMMENT

Description Details
Write "P_SafetyCertCode".
Write "P_SafetyCertCode".
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Write "Safety Certification Code".
May be omitted because this case uses the value of the reference source of the
REF item.
When writing, write "DWORD".
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
May be omitted because this case uses the value of the reference source of the
REF item.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Write prohibited.
Write prohibited.
May be omitted because this case uses the value of the reference source of the
REF item.
When writing, write "RW".
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Describe the reference to the "P_SafetyCertCode" element of the
BLOCK_PARAMETER part.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.

(a) Item description example of element<p:commIfParameterMember label="P_SafetyCertCode"><p:label2><p:item>P_SafetyCertCode</p:item></p:label2><p:name><p:item>Safety Certification Code</p:item></p:name><p:ref><p:item>BlockSec.BlockParameter.P_SafetyCertCode</p:item></p:ref></p:commIfParameterMember>

CLPA

BAP-C2008ENG-001-K
1-420

5.5.10.3.3.
(1)

Description details of elements written in BLOCK_PARAMETER part
Item description of P_TransIntervalMonitorTime element in BLOCK_PARAMETER part

Table 5-448 Item Description Specifications of P_TransIntervalMonitorTime Element in
BLOCK_PARAMETER Part

Item Name

No.
1.
2.

LABEL
LABEL2

3.

CATEGORY

4.
5.

NAME
DATATYPE

6.

DEFAULT

7.

RANGE

8.
9.
10.

MIN_INC
ENG_UNITACCESS

11.

WRITE_ORDER

12.

UI_ATTRIBUTE

13.

COMMENT

Description Details
Write "P_TransIntervalMonitorTime".
Write "P_TransIntervalMonitorTime".
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Write "Transmission Interval Monitoring Time",
Write "UINT16".
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Write prohibited.
Write "ms".
Write "W" or "RW".
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.

(a) Item description example of element<p:blockParameterMember label="P_TransIntervalMonitorTime"><p:label2><p:item>P_TransIntervalMonitorTime</p:item></p:label2><p:name><p:item>Transmission Interval Monitoring Time</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:engUnit><p:item>ms</p:item></p:engUnit><p:access><p:item>RW</p:item></p:access></p:blockParameterMember>

CLPA

BAP-C2008ENG-001-K
1-421

(2)

Item description of P_SafetyCertCode element in BLOCK_PARAMETER part

Table 5-449 Item Description Specifications of P_SafetyCertCode Element in BLOCK_PARAMETERPart

Item Name

No.
1.
2.

LABEL
LABEL2

3.

CATEGORY

4.
5.

NAME
DATATYPE

6.

DEFAULT

7.

RANGE

8.
9.
10.

MIN_INC
ENG_UNITACCESS

11.

WRITE_ORDER

12.

UI_ATTRIBUTE

13.

COMMENT

Description Details
Write "P_SafetyCertCode".
Write "P_SafetyCertCode".
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Write "Safety Certification Code".
Write "DWORD".
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Write prohibited.
Write prohibited.
Write "RW".
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.

(a) Item description example of element<p:blockParameterMember label="P_SafetyCertCode"><p:label2><p:item>P_SafetyCertCode</p:item></p:label2><p:name><p:item>Safety Certification Code</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:access><p:item>RW</p:item></p:access></p:blockParameterMember>

CLPA

BAP-C2008ENG-001-K
1-422

5.5.10.4 MESSAGE specifications for writing the safety communication function parameter
5.5.10.4.1.
Overview
When writing MESSAGE for writing parameters to a safety compatible device, write them inaccordance with the specifications specified in this section. However, LABEL2 and NAME arerecommended specifications, and other strings can be written.
Furthermore, when reading and writing the CRC32 value, write the string indicated in Table 5-450 in
REQUEST_DATA and RESPONSE_DATA. The parameters of the safety communication function(see Section 5.5.10.3) are also written using the messages shown in this section.
COMM_IF section

BLOCK section

MESSAGE part
SLMP_P_Safety_ParameterWrite element

COMM_IF_PARAMETER part

BLOCK_PARAMETER partParameter 1

Parameter 1

Parameter 2

Parameter 2

・
・
・

・
・
・

Parameter x

Parameter x

Figure 5-58 Image of Structure When Describing Parameter Writing of Safety Communication
Function

COMM_IF section

BLOCK section

MESSAGE part
SLMP_P_Safety_ParameterWrite element

COMM_IF_COMMAND part

BLOCK_COMMAND part

Command 1

Command 1

Figure 5-59 Image of Structure When Describing Enabling of Safety Communication Function
Parameters

Table 5-450 Reserved Words to Indicate Reading and Writing CRC32 Value
Meaning
CRC32 value specified in CC-Link IE safety communication
function *1
CRC32 value specified in IEEE802.3 *1

CLPA

Reserved Word$(CRC32_F1922815)$(CRC32_04C11DB7)

BAP-C2008ENG-001-K
1-423

*1:

Utility software calculates CRC32 according to the following specifications.
CRC32 is calculated from the VALUE of all elements of COMM_IF_PARAMETER(BLOCK_PARAMETER) referenced by the TARGET of the parameter writing for the safetycompliant devices (SLMP_P_Safety_ParameterWrite).
･ When running multiple MESSAGE elements sequentially with RELATED_MESSAGE,
CRC32 is calculated from the VALUE of all elements of COMM_IF_PARAMETER(BLOCK_PARAMETER) referenced by the TARGET of all MESSAGE elements referenced
by RELATED_MESSAGE.
･

When reserved words indicating the value of CRC32 are written in REQUEST_DATA, utility software
calculates CRC32 when MESSAGE is executed, and stores it in a request message. If it is written in
RESPONSE_DATA, the utility software reads the value of CRC32 from the place where theresponse message reserved word is written.
When parameter writing of the safety communication function is described with multiple consolidated
MESSAGEs, the element names specified in this section (SLMP_P_Safety_ParameterWrite) areattached to a MESSAGE representing a series of operations. The element names of the MESSAGE
consolidated from there are optional.
A single reserved word of Table 5-450 can be written in each REQUEST_DATA orRESPONSE_DATA.
Table 5-451 shows a list of elements described in the MESSAGE part. For details of the description
specifications of each element, see Section 5.5.10.4.2.

Table 5-451 List of Elements Described in MESSAGE PartNo.

Description Details
Required/Optional
Write the message used for writing parameter1.
SLMP_P_Safety_ParameterWrite
Optionalof the safety compatible device.
Write the parameter enabling information of2.
SLMP_P_Safety_EnableParameter
Optional
the safety compatible device.
Reserved words indicating CRC32 (refer to Table 5-444) must be written to RESPONSE_DATA by theabove elements or at least one element among the elements referred by RELATED_MESSAGE.
(1)

Element Name

Elements of parameters referenced by parameter writing of safety communication function
Table 5-452 shows a list of elements described in the COMM_IF_PARAMETER part. For details of
the description specifications of each element, see Section 5.5.10.4.2.

Table 5-452 List of Elements Described in COMM_IF_PARAMETER PartNo.
1.

Element Name
(Any name)

Description Details
Write the parameters of the safety
communication function.

Required/Optional
Optional

Table 5-453 shows a list of elements described in the BLOCK_PARAMETER part. For details of thedescription specifications of each element, see Section 5.5.10.4.2.

Table 5-453 List of Elements Described in BLOCK_PARAMETER Part
No.
1.

CLPA

Element Name
(Any name)

Description Details
Write the parameters of the safety
communication function.

Required/Optional
Optional

BAP-C2008ENG-001-K
1-424

(2) Elements of commands referenced by parameter enabling of safety communication function
Table 5-454 shows a list of elements described in the COMM_IF_COMMAND part. For details of thedescription specifications of each element, see Section 5.5.10.4.3.
Table 5-454 List of Elements Described in COMM_IF_COMMAND PartNo.
1.

Element Name
(Any name)

Description Details
Write the parameter enabling command of
the safety communication function.

Required/Optional
Optional

Table 5-455 shows a list of elements described in the BLOCK_COMMAND part. For details of thedescription specifications of each element, see Section 5.5.10.4.3.
Table 5-455 List of Elements Described in BLOCK_COMMAND PartNo.
1.

Element Name
(Any name)

Description Details
Write the parameter enabling command of
the safety communication function.

Required/Optional
Optional

5.5.10.4.2.
MESSAGE specifications for writing the safety communication function parameter
MESSAGEs are specified for parameter writing, but not for reading. MESSAGEs for reading can be
written freely according to CSP+ specifications.
(1)

Item description of SLMP_P_Safety_ParameterWrite element
Table 5-456 Item Description Specifications of SLMP_P_Safety_ParameterWrite Element

No.
1.
2.

Item NameLABELLABEL2

3.

CATEGORY

4.

NAME

5.

TARGET

6.

MESSAGE_TYPE

7.

REQUEST_TYPE

8.

REQUEST_DATA

9.

REQUEST_DATATYPE10.

RESPONSE_TYPE

11.

RESPONSE_DATA

12.

RESPONSE_DATATYPE

13.

ERR_TYPE

14.

ERR_CODE_RANGE

15.

RELATED_MESSAGE

16.

COMMENT

CLPA

Description Details
Write "SLMP_P_Safety_ParameterWrite".
Write "SLMP_P_Safety_ParameterWrite". [Recommended specifications]
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Write "Parameter Write". [Recommended specifications]Write the reference to the COMM_IF_PARAMETER part in which the parametersof the safety communication function are written.
Write "PARAMETER".
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.

BAP-C2008ENG-001-K
1-425

(a) Item description example of SLMP_P_Safety_ParameterWrite element<p:messageMember label="SLMP_P_Safety_ParameterWrite"><p:label2><p:item>SLMP_P_Safety_ParameterWrite</p:item></p:label2><p:name><p:item>Parameter Write</p:item></p:name><p:target><p:item>SEQ TARGET</p:item></p:target><p:messageType><p:item>PARAMETER</p:item></p:messageType><p:relatedMessage><p:item>&lt;SEQ SLMPStartWritePramArea&gt;&lt;SEQ
SLMPStationWritePrm&gt;&lt;SEQ SLMPWriteCRC32&gt;&lt;SEQ
SLMPReflectPrm&gt;&lt;SEQ SLMPStartReadPramArea&gt;&lt;SEQ
SLMPReadCRC32&gt;</p:item></p:relatedMessage></p:messageMember>(2)

Item description of COMM_IF_PARAMETER part element
Table 5-457 Item Description Specifications of COMM_IF_PARAMETER Part Element
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

WRITE_ORDER

12.

ASSIGN13.

UI_ATTRIBUTE

14.

REF

15.

COMMENT

Description Details
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.
Not specified.
Write a value in the same manner as the regular COMM_IF_PARAMETER.

(a) Item description example of element<p:commIfParameterMember label="Parameter1"><p:label2><p:item>Parameter1</p:item></p:label2><p:name><p:item>Parameter 1</p:item></p:name><p:access><p:item>RW</p:item></p:access><p:assign><p:item>RWr1</p:item></p:name><p:ref><p:item>BlockSec.BlockParameter.Parameter1</p:item></p:ref></p:commIfParameterMember>

CLPA

BAP-C2008ENG-001-K
1-426

(3)

Item description of BLOCK_PARAMETER part element
Table 5-458 Item Description Specifications of BLOCK_PARAMETER Part Element
No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DEFAULT

7.

RANGE

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

WRITE_ORDER

12.

UI_ATTRIBUTE

13.

COMMENT

Description Details
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.
Not specified.
Write a value in the same manner as the regular BLOCK_PARAMETER.

(a) Item description example of element<p:blockParameterMember label="Parameter1"><p:label2><p:item>Parameter1</p:item></p:label2><p:name><p:item>Parameter 1</p:item></p:name><p:datatype><p:item>INT16</p:item></p:datatype><p:range><p:item>[0,200]</p:item></p:range><p:engUnit><p:item>ms</p:item></p:engUnit><p:access><p:item>RW</p:item></p:access></p:blockParameterMember>

CLPA

BAP-C2008ENG-001-K
1-427

5.5.10.4.3.
(1)

MESSAGE specifications for parameter enabling of safety communication function
Item description of SLMP_P_Safety_EnableParameter element

Table 5-459 Item Description Specifications of SLMP_P_Safety_EnableParameter Element
No.
1.
2.

Item NameLABELLABEL2

3.

CATEGORY

4.

NAME

5.

TARGET

6.

MESSAGE_TYPE

7.

REQUEST_TYPE

8.

REQUEST_DATA

9.

REQUEST_DATATYPE10.

RESPONSE_TYPE

11.

RESPONSE_DATA

12.

RESPONSE_DATATYPE

13.

ERR_TYPE

14.

ERR_CODE_RANGE

15.

RELATED_MESSAGE

16.

COMMENT

Description Details
Write "SLMP_P_Safety_EnableParameter".
Write "SLMP_P_Safety_EnableParameter". [Recommended specifications]
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Write "Enable Parameter". [Recommended specifications]Write the reference to the COMM_IF_COMMAND part in which the commandsof the safety communication function are written.
Write "COMMAND".
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.
Not specified.
Write a value in the same manner as the regular MESSAGE part.

(a) Item description example of SLMP_P_Safety_EnableParameter element<p:messageMember label="SLMP_P_Safety_EnableParameter"><p:label2><p:item>EnableParameter</p:item></p:label2><p:name><p:item>Enable Parameter</p:item></p:name><p:target><p:item>SEQ TARGET</p:item></p:target><p:messageType><p:item>COMMAND</p:item></p:messageType><p:relatedMessage><p:item>&lt;SEQ SLMPWriteCRC32&gt;&lt;SEQ
SLMPCheckCRC32&gt;&lt;SEQ SLMPReadCRC32&gt;&lt;SEQ
SLMPSafetyEnableParameter&gt;</p:item></p:relatedMessage></p:messageMember>

CLPA

BAP-C2008ENG-001-K
1-428

(2)

Item description of COMM_IF_COMMAND part element
Table 5-460 Item Description Specifications of COMM_IF_COMMAND Part Element

No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

ARGUMENT

6.

REF

7.

COMMENT

Description Details
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.
Not specified.
Write a value in the same manner as the regular COMM_IF_COMMAND part.

(a) Item description example of P_GetStatusCommand element<p:commIfCommandMember label="Safety_EnableCommand"><p:label2><p:item>Safety_EnableCommand</p:item></p:label2><p:name><p:item>Safety Communication Command</p:item></p:name><p:ref><p:item>BlockSec.BlockCommand.Safety_EnableCommand</p:item></p:ref></p:commIfCommandMember>(3)

Item description of BLOCK_COMMAND part element
Table 5-461 Item Description Specifications of BLOCK_COMMAND Part Element

No.

Item Name

1.

LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

ARGUMENT

6.

COMMENT

Description Details
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.
Not specified.
Write a value in the same manner as the regular BLOCK_COMMAND part.

(a) Item description example of element<p:blockCommandMember label="Safety_EnableCommand"><p:label2><p:item>Safety_EnableCommand</p:item></p:label2><p:name><p:item>Safety Communication Command</p:item></p:name></p:blockCommandMember>

CLPA

BAP-C2008ENG-001-K
1-429

5.5.10.5 Parts and elements related to the main module and extension modules
5.5.10.5.1.
Overview
This section describes the description specifications of the CSP+ files for the main module andextension modules. Information of the items described in this section cannot be written to CSP+ files
for the modules other than the main module and extension modules.
5.5.10.5.2.
Main moduleThis section describes the description specifications of the CSP+ file for the main module. Information,such as input/output areas, of the connected extension modules is defined so that the utility software
can access the extension modules via the main module. Information showing which extension module
uses which area must be defined as well.
5.5.10.5.2.1
Description details of DEVICE_INFO part
Information about extension modules is described in the DEVICE_INFO part. The following table lists
the described elements.
Table 5-462 List of Elements Written in DEVICE_INFO PartNo.

Element

1.

EXTExtensionIFTypeID

2.

EXTExtensionMax

3.

EXTExtensionModuleType

4.

EXTCyclicPDUExtensionFlg

CLPA

Description Details
Write the type of extension modules to be connected.
Write the maximum number of extension modules tobe connected.
Write the type of extension modules to be connected.
Write if extension modules supporting cyclic
transmission PDUs can be connected.

Required/
Optional
Required
Required
Optional
Required

BAP-C2008ENG-001-K
1-430

(1) Item description of EXTExtensionIFTypeID element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "EXTExtensionIFTypeID".
Write "EXTExtensionIFTypeID" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Extension Network Type ID" in the case of English CSP+ files. [Recommended
specifications]Write "STRING(32)".
Write "V" + "Vendor Code" + "Any String".
Only extension modules having the same value in DATA of the CommIFTypeID element
can be connected.
Different strings need to be set in order to describe whether if extension modules
manufactured by the same vendor can be connected or not.
(Example) When the vendor code is xxxx, write "VxxxxRemote".
* xxxx is a four-digit natural number.

(a) Item description example of EXTExtensionIFTypeID element<p:deviceInfoMember label="EXTExtensionIFTypeID"><p:label2><p:item>EXTExtensionIFTypeID</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Extension Network Type ID</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>VxxxxRemote</p:item></p:data></p:deviceInfoMember>(2) Item description of EXTExtensionMax element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "EXTExtensionMax".
Write "EXTExtensionMax" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Maximum Number of Extension Modules" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the maximum number of extension modules to be connected.

(a) Item description example of EXTExtensionMax element<p:deviceInfoMember label="EXTExtensionMax"><p:label2><p:item>EXTExtensionMax</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Maximum Number of Extension Modules</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>4</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-431

(3) Item description of EXTExtensionModuleType element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "EXTExtensionModuleType".
Write "EXTExtensionModuleType" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Connectable Extension Module Type" in the case of English CSP+ files.
[Recommended specifications]Write "STRING(32)".
When EXTExtensionIFTypeID of the main module matches with CommIFTypeID of theextension module, write the string that indicates the module type to add the extension
module.
The description of EXTExtensionModuleType of the extension module determines if
extension modules can be added.
• Extension modules with the description of EXTExtensionModuleType omitted
These extension modules can be connected to the main module.
• Extension modules with the description of EXTExtensionModuleType
Extension modules having the same string as that written in
EXTExtensionModuleType of the main module can be connected to the main module.
Note that when the description of EXTExtensionModuleType of the main module isomitted, extension modules with the description of EXTExtensionModuleType cannot be
connected.

(a) Item description example of EXTExtensionModuleType element<p:deviceInfoMember label="EXTExtensionModuleType"><p:label2><p:item>EXTExtensionModuleType</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Connectable Extension Module Type</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>UNITTYPE_100</p:item></p:data></p:deviceInfoMember>(4) Item description of EXTCyclicPDUExtensionFlg element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "EXTCyclicPDUExtensionFlg".
Write "EXTCyclicPDUExtensionFlg" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Cyclic Transmission PDU Extension Module Availability Flag" in the case of English
CSP+ files. [Recommended specifications]Write "BOOL".
0: Cannot be connected.
1: For future expansion(a) Item description example of EXTCyclicPDUExtensionFlg element<p:deviceInfoMember label="EXTCyclicPDUExtensionFlg"><p:label2><p:item>EXTCyclicPDUExtensionFlg</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Cyclic Transmission PDU Extension Module Availability Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:deviceInfoMember>
CLPA

BAP-C2008ENG-001-K
1-432

5.5.10.5.2.2

Description details of COMM_IF_INPUT, COMM_IF_OUTPUT, BLOCK_OUTPUT, and
BLOCK_INPUT parts
The extension module input/output areas are described. To define the extension module input/output
areas, the descriptions of all items in this section are required. The descriptions of the main module
input/output areas are the same as those of a single module.
The refresh areas need to be sequentially assigned to the same extension module.
(Example) The areas, RX10, RX11, and RX20, cannot be assigned as the input area of the 1st extension
module.
However, the areas, RX10 and RX11, can be assigned as the input area of the 1st extension
module, and the area RX20 can be assigned to the 2nd extension module.
(1) Common items of COMM_IF_INPUT, COMM_IF_OUTPUT, BLOCK_OUTPUT, and
BLOCK_INPUT parts
No.

Item Name

1.

LABEL

Description Details
Write prefix "EXTx_" + "Any String".
For x of the prefix, write the value that indicates which extension module is used.
(Example: For the input area of the 1st extension module in the COMM_IF_INPUT part,write "EXT1_InputA".)(2) Common items of COMM_IF_INPUT and COMM_IF_OUTPUT parts

CLPA

No.
1.

Item NameACCESS2.

ASSIGN

3.

REF

Description Details
Write "RF".
Write the elements, such as the remote input/output and remote register, to extension
modules.
Write a reference to the element of the BLOCK_OUTPUT part having the same prefix"EXTx_" for the COMM_IF_INPUT part.
Write a reference to the element of the BLOCK_INPUT part having the same prefix"EXTx_" for the COMM_IF_OUTPUT part.

BAP-C2008ENG-001-K
1-433

The following is the description example when input areas used by extension modules are defined in
the COMM_IF_INPUT and the BLOCK_OUTPUT.
1st extension module: RX10, RX11
2nd extension module: RX20
<p:commIfInput label="CommIfInput"><p:commIfInputMember label="EXT1_RX10"><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX10</p:item></p:assign><p:ref><p:item>BlockSection.BlockOutput.EXT1_RX10</p:item></p:ref></p:commIfInputMember><p:commIfInputMember label="EXT1_RX11"><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX11</p:item></p:assign><p:ref><p:item>BlockSection.BlockOutput.EXT1_RX11</p:item></p:ref></p:commIfInputMember><p:commIfInputMember label="EXT2_RX20"><p:access><p:item>RF</p:item></p:access><p:assign><p:item>RX20</p:item></p:assign><p:ref><p:item>BlockSection.BlockOutput.EXT2_RX20</p:item></p:ref></p:commIfInputMember></p:commIfInput><p:blockOutput label="BlockOutput"><p:blockOutputMember label="EXT1_RX10"><p:label2><p:item>EXT1_RX10</p:item></p:label2><p:name><p:item>1st Extension Module input Area 1</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype></p:blockOutputMember><p:blockOutputMember label="EXT1_RX11"><p:label2><p:item>EXT1_RX11</p:item></p:label2><p:name><p:item>2nd Extension Module Input Area 2</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype></p:blockOutputMember><p:blockOutputMember label="EXT2_RX20"><p:label2><p:item>EXT2_RX20</p:item></p:label2><p:name><p:item>2nd Extension Module input Area 1</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype></p:blockOutputMember></p:blockOutput>

CLPA

BAP-C2008ENG-001-K
1-434

5.5.10.5.3.
Extension modules
This section describes the description specifications of the CSP+ files for extension modules.
FILE_INFO
The descriptions of FILE_INFO of extension modules are the same as those of a single module. See
Section 5.1.1 "FILE_INFO part".

CLPA

BAP-C2008ENG-001-K
1-435

Description details of DEVICE_INFO part
Information about extension modules is described in the DEVICE_INFO part. The following table lists
the described elements.
Table 5-463 List of Elements Written in DEVICE_INFO PartNo.

Element1.

VendorName

2.

VendorCode3.

DeviceModel

4.

ProductID

5.

DeviceTypeID

6.

DeviceTypeDetail

7.

Version8.

VersionDisplayFlg

9.

VersionPolicyType

10.

DisplayVersionValue

11.

VersionComment

12.

DeviceConfigurationID

13.

DeviceConfigurationComment

14.

ReferenceURL

15.

URLInfo

16.

Outline17.

Feature18.

SpecList

19.

PowerSupplyVoltage

CLPA

Description Details
Write the name of the vendor that
manufactured the module.
Write the code of vendor that
manufactured the module.
The fifth to eighth digits of themembership number of the CC-Link
Partner Association are written.
Write the model of the module.
Write the product ID of the module.
The ID managed by the vendor that
manufactured the module is written.
Write the ID of the module type.
Write the specific device type.
Write the device version of themodule.
Write whether to show/hide the device
version to/from the user.
Write the policy of the relationshipbetween the actual device version andthe device version described in the
CSP+ file when the actual device isaccessed using the CSP+ file.
Write the value of the device version
to be displayed when the value(Version) of the device version
acquired from the actual device differsfrom the value of the version displayed
to the user on the utility software.
Write a comment related to the device
version.
Write a device configuration ID.
Write a device configuration comment.
Write a URL if the module information
is disclosed on the website.
Write the information indicated by thereference URL.
Write the general specifications of themodule.
Write the features of the module.
Write the module specifications using
a set of strings.
Write the power supply voltage involts (V).

Required/
Optional
Required

Description
Specifications
See Section
5.2.1.3.
See Section
5.2.1.3.

Required

Required
Required*1*1Required
Required

See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.

Required

See Section
5.2.1.3.
Optional

Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional

See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.

BAP-C2008ENG-001-K
1-436

No.

Element

20.

ConsumptionCurrent

21.

IconFileName

22.

GraphicsFileName

23.

Height

24.

Width

25.

Depth

26.

Weight27.

Price

Description Details
Write the current consumption in
milliamperes (mA).
Write the icon file name with theextension (.ico) when displaying themodule as an icon on the utility
software.
Write the graphic file name withthe extension (.bmp, .png, .jpg,
or .gif) when displaying themodule on the utility software.
Write the height of the external
dimensions with a unit.
Write the width of the external
dimensions with a unit.
Write the depth of the external
dimensions with a unit.
Write the weight with a unit.
Write the price with a unit.

Required/
Optional
Optional

Optional

Optional

Optional
Optional
Optional
Optional
Optional

Description
Specifications
See Section
5.2.1.3.
See Section
5.2.1.3.

See Section
5.2.1.3.

See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.

Write the name of the Window to be
specified in UI_ATTRIBUTE.
Optional
The Window number is written in "**".
Write the cyclic transmission PDU
See (1).
29.
CyclicPDUFlg
Requiredavailability.
*1: Write either of the DeviceTypeID element or the DeviceTypeDetail element. When both of theelements are written, the DeviceTypeDetail element takes precedence.
28.

CLPA

UI_ATTRIBUTE_Window**

BAP-C2008ENG-001-K
1-437

(1) Item description of CyclicPDUFlg element
No.
1.
2.
3.

Item NameLABELLABEL2
CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CyclicPDUFlg".
Write "CyclicPDUFlg" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_ExType".
Write "Cyclic Transmission PDU Availability" in the case of English CSP+ files.
[Recommended specifications]Write "BOOL".
0: Cannot be used
1: For future expansion(a) Item description example of CyclicPDUFlg element<p:deviceInfoMember label="CyclicPDUFlg"><p:label2><p:item>CyclicPDUFlg</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Cyclic Transmission PDU Availability</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>0</p:item></p:data></p:deviceInfoMember>(2) Unusable elements
Elements related to the dedicated tool cannot be described in the DEVICE_INFO part of extension
modules.

CLPA

BAP-C2008ENG-001-K
1-438

Description details of COMM_IF_INFO part
Information about extension modules is described in the COMM_IF_INFO part. The following table lists
the described elements.
Table 5-464 List of Elements Written in COMM_IF_INFO PartNo.
1.

Element
VendorName
VenderCode

2.

3.

VersionCommIFTypeID

4.

5.

EXTExtensionModule
Priority
EXTExtensionModule
Type

6.

7.
8.
9.
10.

CLPA

EXTBasicModuleCommIFTypeID
ModelCodeAutoSettingHeaderType
AutoSettingType

Description Details
Write the name of the vendor that
manufactured the module.
Write the code of vendor that manufactured themodule.
The fifth to eighth digits of the membershipnumber of the CC-Link Partner Association are
written.
Write the firmware version using a string.
Write the ID of the extension module type using
a string.
Extension modules can be connected when
EXTExtensionIFTypeID of the main module
matches with CommIFTypeID of the extension
module.
Write the priority of the extension module.
Lower-priority extension modules can only beconnected to higher-priority extension modules.
Write the extension module type.
The descriptions of EXTExtensionModuleTypeof the main module and the descriptions of
EXTExtensionModuleType of the extension
module determine if the extension module canbe connected. For details, see 5.5.10.5.2.1(3).
Write the communication interface type of themain module. The same information as that
described in CommIFTypeID of the main
module connected is written.
Write the model code.
Write the header type number of the slave
station parameter automatic setting.
Write the type of the slave station
parameter automatic setting.

Required/
Optional
Required

Description
Specifications
See Section
5.4.1.3.
See Section
5.4.1.3.

Required

Required

See Section
5.4.1.3.
See (1).

RequiredSee (2).
Optional
See (3).
Optional

See (4).
Required
Optional
Optional
Optional

See (5).
See (6).
See (7).

BAP-C2008ENG-001-K
1-439

(1) Item description of CommIFTypeID element
No.
1.
2.
3.

Item NameLABELLABEL2
CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CommIFTypeID".
Write "CommIFTypeID" in the case of English CSP+ files. [Recommended specifications]Write "COMMON".
Write "Communication Interface Type ID" in the case of English CSP+ files.
[Recommended specifications]Write "STRING(32)".
Write the ID of the extension module type.
Write the same value in DATA as that in EXTExtensionIFTypeID of the connectable main
module.
(Example) When the vendor code is xxxx, write "VxxxxRemote".
* xxxx is a four-digit natural number.

(a) Item description example of CommIFTypeID element<p:commIfInfoMember label="CommIFTypeID"><p:label2><p:item>CommIFTypeID</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Communication Interface Type ID</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>VxxxxRemote</p:item></p:data></p:commIfInfoMember>(2) Item description of EXTExtensionModulePriority element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "EXTExtensionModulePriority".
Write "EXTExtensionModulePriority" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Extension Module Priority" in the case of English CSP+ files. [Recommended
specifications]Write "INT8".
Write the priority of the extension module using the values between -128 and 127.
Extension modules with larger values can be connected closer to the main module.
If this item is omitted, it will be regarded as "0".

(a) Item description example of EXTExtensionModulePriority element<p:deviceInfoMember label="EXTExtensionModulePriority"><p:label2><p:item>EXTExtensionModulePriority</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Extension Module Priority</p:item></p:name><p:datatype><p:item>INT8</p:item></p:datatype><p:data><p:item>10</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-440

(3) Item description of EXTExtensionModuleType element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "EXTExtensionModuleType".
Write "EXTExtensionModuleType" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Extension Module Type" in the case of English CSP+ files. [Recommended
specifications]Write "STRING(32)".
Write the extension module type using any string.

(a) Item description example of EXTExtensionModuleType element<p:deviceInfoMember label="EXTExtensionModuleType"><p:label2><p:item>EXTExtensionModuleType</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Extension Module Type</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>UNITTYPE_100</p:item></p:data></p:deviceInfoMember>(4) Item description of EXTBasicModuleCommIFTypeID element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "EXTBasicModuleCommIFTypeID".
Write "EXTBasicModuleCommIFTypeID" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_ExType".
Write "Main Module Communication Interface ID" in the case of English CSP+ files.
[Recommended specifications]Write "STRING(32)".
Write "CCLinkIETSN".

(a) Item description example of EXTBasicModuleCommIFTypeID element<p:deviceInfoMember label="EXTBasicModuleCommIFTypeID"><p:label2><p:item>EXTBasicModuleCommIFTypeID</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Main Module Communication Interface ID</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>CCLinkIETSN</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-441

(5) Item description of ModuleCode element
No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPE
DATA

Description Details
Write "ModuleCode".
Write "ModuleCode" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_ExType".
Write "Model Code" in the case of English CSP+ files. [Recommended specifications]Write "UINT32".
Write any model code.

(a) Item description example of ModuleType element<p:deviceInfoMember label="ModuleCode"><p:label2><p:item>ModuleCode</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Model Code</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>1234</p:item></p:data></p:deviceInfoMember>(6) Item description of AutoSettingHeaderType element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "AutoSettingHeaderType".
Write "AutoSettingHeaderType" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Automatic Setting Header Type" in the case of English CSP+ files. [Recommended
specifications]Write "BYTE".
Write the header type number (0x00 to 0xFF).
For the header type number, see the description about the parameter automatic setting
file format in the "CC-Link IE TSN Specifications (Application Layer Protocol)" (BAPC2011ENG-004).
If this item is omitted, it will be regarded as "0x00".

(a) Item description example of AutoSettingHeaderType element<p:commIfInfoMember label="AutoSettingHeaderType"><p:label2><p:item>AutoSettingHeaderType</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Automatic Setting Header Type</p:item></p:name><p:datatype><p:item>BYTE</p:item></p:datatype><p:data><p:item>0x00</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-442

(7) Item description of AutoSettingType element
No.
1.
2.
3.

Item NameLABELLABEL2
CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "AutoSettingType".
Write "AutoSettingType" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_ExType".
Write "Auto Setting Type" in the case of English CSP+ files. [Recommended
specifications]Write "WORD".
Write the automatic setting type.
0x0000: Function not available (default)
0x0001: Settable for individual parameters only
0x0002: Settable for batch parameters only
If this item is omitted, it will be regarded as "0x0000".
When 0x0001 is set, always write MESSAGE for parameter auto setting.
When 0x0002 is set, parameter related information (values of METHOD_TYPE item and
MESSAGE_TYPE item are elements of PARAMETER and AUTO_PARAMETER) is notsupported.
For individual parameters and batch parameters, see Section 5.5.8.3 "Slave station
parameter automatic setting" in the "CC-Link IE TSN Specifications (Overview)" (BAPC2011ENG-001).
When the extension module is connected to the main module where AutoSettingType isset to 0x0000, it will be regarded as "0x0000".

(a) Item description example of AutoSettingType element<p:commIfInfoMember label="AutoSettingType"><p:label2><p:item>AutoSettingType</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Auto Setting Type</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:data><p:item>0x0001</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-443

Description details of COMM_IF_INPUT, COMM_IF_OUTPUT, BLOCK_OUTPUT, and
BLOCK_INPUT parts
The extension module input/output areas, which are used to refresh data with the main module, aredescribed. When the definition of the n-th extension module input/output area size defined in the main
module and that of the n-th extension module input/output area size are different, the definition of smaller
size is applied.
(1) Common items of COMM_IF_INPUT and COMM_IF_OUTPUT parts
Description Details

Required/
Optional

Description
Specifications
See Section
4.3.1.19.

No.

Item Name

1.

LABEL

Write the label for identifying the element.

Required2.

LABEL2

Write the label for identifying the element.
(Used when the utility software supports anotherlanguage.)

Optional

See Section
4.3.1.20.

3.

CATEGORY

Write the category for grouping the elements.

Optional

See Section
4.3.1.4.

4.

NAME

Write the name of the element.
Used when the name and contents are displayed withthe utility software.

Optional

See Section
4.3.1.24.

5.

DATATYPE

Write the data type of the element.

Optional

6.

DEFAULT

Write the default value set for the element.

Optional

7.

RANGE

Write the setting range of the element.

Optional

8.

MIN_INC

9.

ENG_UNIT10.

ACCESS

11.

ASSIGN12.

UI_ATTRIBUT
E

13.

REF

14.

COMMENT

Write the minimum increment applied to the value ofthe element.
Write the engineering unit applied to the value of theelement.
Write "RF".
Write "EXT_" + "Address Type of Main Module to be
Refreshed" + "Address Number of Extension Module".
(Example: For the start of the remote input in the
COMM_IF_INPUT part, write "EXT_RX0".
Write the display method when the element isdisplayed on utility software.
Write a reference to the element of the
BLOCK_OUTPUT part for the COMM_IF_INPUT
part.
Write a reference to the element of the
BLOCK_INPUT part for the COMM_IF_OUTPUT
part.
Write the meaning of the element and usage
precautions.

Optional

See Section
4.3.1.10.
See Section
4.3.1.11.
See Section
4.3.1.26.
See Section
4.3.1.23.
See Section
4.3.1.13.
-

Optional-

Optional

See Section
4.3.1.43.

Optional

See Section
4.3.1.30.

Optional

See Section
4.3.1.6.

Optional
Optional(2) BLOCK_INPUT part, BLOCK_OUTPUT partThe descriptions are the same as those of a single module. See Section 5.4.2 "BLOCK_INPUT part"and Section 5.4.3 "BLOCK_OUTPUT part".

CLPA

BAP-C2008ENG-001-K
1-444

The following is the description example when an input area is defined in the COMM_IF_INPUT partand the BLOCK_OUTPUT.
<p:commIfInput label="CommIfInput"><p:commIfInputMember label="EXT_RX0"><p:access><p:item>RF</p:item></p:access><p:assign><p:item>EXT_RX0</p:item></p:assign><p:ref><p:item>BlockSection.BlockOutput.EXT_RX0</p:item></p:ref></p:commIfInputMember><p:commIfInputMember label="EXT_RX1"><p:access><p:item>RF</p:item></p:access><p:assign><p:item>EXT_RX1</p:item></p:assign><p:ref><p:item>BlockSection.BlockOutput.EXT_RX1</p:item></p:ref></p:commIfInputMember></p:commIfInput><p:blockOutput label="BlockOutput"><p:blockOutputMember label="EXT_RX0"><p:label2><p:item>EXT_RX0</p:item></p:label2><p:name><p:item>Extension Module Input Area RX0</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype></p:blockOutputMember><p:blockOutputMember label="EXT_RX1"><p:label2><p:item>EXT_RX1</p:item></p:label2><p:name><p:item>Extension Module Input Area RX1</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype></p:blockOutputMember></p:blockOutput>

CLPA

BAP-C2008ENG-001-K
1-445

COMM_IF_COMMAND, BLOCK_COMMAND
The descriptions of the COMM_IF_COMMAND part and the BLOCK_COMMAND part of theextension modules are the same as those of a single module. See Section 5.5.10.1.3 "Description
details of elements written in COMM_IF_COMMAND part" and Section 5.5.10.1.4 "Description detailsof elements written in BLOCK_COMMAND part".
COMM_IF_PARAMETER, BLOCK_PARAMETER
The descriptions of the COMM_IF_PARAMETER part and the BLOCK_PARAMETER part of theextension modules are the same as those of a single module. See Section 5.3.4"COMM_IF_PARAMETER part" and Section 5.4.4 "BLOCK_PARAMETER part".
MESSAGEThe error related information and the slave station parameter automatic setting are described in the
MESSAGE part. The descriptions are the same as those of a single module except the descriptions
below. See Section 5.3.7 "MESSAGE part", Section 5.5.10.1 "Parts and elements related to error related
information", and Section 5.5.10.2 "Convention related to MESSAGE for slave station parameter
automatic setting".
• REQUEST_DATA, REQUEST_DATATYPE
To write a value to set which module is the target module as viewed from the extension module,$(P_EXTNUM0) is described in REQUEST_DATA.
*: In the utility software with CSP+ files installed, when the SLMP command is transferred to theextension module that is directly connected to the main module, the REQUEST_DATA item where$(P_EXTNUM0) is described is regarded as 0, and therefore the SLMP communications are performed.
The item for subsequent extension modules is regarded as 1, 2, … so that the SLMP communications
are performed.
*: The end of the string is 0 (numeric character), not O (alphabet).
• MESSAGE_TYPE
COMMAND cannot be described. The descriptions are the same as those of a single module except thedescription of COMMAND.

CLPA

BAP-C2008ENG-001-K
1-446

5.5.10.6 Parts and elements related to the integrated main/extension module unit
5.5.10.6.1.
Overview
This section describes the description specifications of the CSP+ files for the main module section andextension module section in the integrated main/extension module unit. Information of the items
described in this section cannot be written to CSP+ files for the modules other than the integrated
main/extension module unit.
5.5.10.6.2.
Main module section
This section describes the description specifications of the CSP+ file for the main module section in the
integrated main/extension module unit.

For elements other than those shown in "Table 5-465 List of Elements Written in DEVICE_INFO Part",
write the information in accordance with Section 5.2.1 "DEVICE_INFO part".
Furthermore, write the elements listed in "Table 5-465 List of Elements Written in DEVICE_INFO Part"as the common information of the main module section in the integrated main/extension module unit.
Table 5-465 List of Elements Written in DEVICE_INFO Part
Element
1. EXTExtensionIFTypeID

Description Details
Write the type of extension modules to be connected.
Write the maximum number of extension modules to be
2. EXTExtensionMax
connected.
Write the extension type or the integrated main/extension
3. EXTBuiltInType
module unit.
Write if extension modules supporting cyclic transmission
4. EXTCyclicPDUExtensionFlg
PDUs can be connected.

CLPA

Required/Optional
Required
Required
Optional
Required

BAP-C2008ENG-001-K
1-447

(1) Item description of EXTExtensionIFTypeID element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "EXTExtensionIFTypeID".
Write "EXTExtensionIFTypeID" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Extension Network Type ID" in the case of English CSP+ files. [Recommended
specifications]Write "STRING(32)".
Write "V" + "Vendor Code" + "Any String".
This indicates that the devices in which the same ID is written to COMM_IF_INFO in theextension module section are always integrated.
(Example) When the vendor code is xxxx, write "VxxxxBuiltIn".
* xxxx is a four-digit natural number.

(a) Item description example of EXTExtensionIFTypeID element<p:deviceInfoMember label="EXTExtensionIFTypeID"><p:label2><p:item>EXTExtensionIFTypeID</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Extension Network Type ID</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>VxxxxBuiltIn</p:item></p:data></p:deviceInfoMember>(2) Item description of EXTExtensionMax element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "EXTExtensionMax".
Write "EXTExtensionMax" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Maximum Number of Extension Modules" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the number of extension module sections to be integrated.

(a) Item description example of EXTExtensionMax element<p:deviceInfoMember label="EXTExtensionMax"><p:label2><p:item>EXTExtensionMax</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Maximum Number of Extension Modules</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>3</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-448

(3) Item description of EXTBuiltInType element
No.
1.
2.
3.
4.
5.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPE

6.

DATA

Description Details
Write "EXTBuiltInType".
Write "EXTBuiltInType" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_ExType".
Write "Built-in Type" in the case of English CSP+ files. [Recommended specifications]Write "BOOL".
0: Not built-in type (Extension type)
1: Built-in type
For the integrated main/extension module unit, write "1".
If this element is omitted, it will be regarded as "0".

(a) Item description example of EXTBuiltInType element<p:deviceInfoMember label="EXTBuiltInType"><p:label2><p:item>EXTBuiltInType</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Built-in Type</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:deviceInfoMember>(4) Item description of EXTCyclicPDUExtensionFlg element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "EXTCyclicPDUExtensionFlg".
Write "EXTCyclicPDUExtensionFlg" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Cyclic Transmission PDU Extension Module Availability Flag" in the case of English
CSP+ files. [Recommended specifications]Write "BOOL".
1: Built-in type(a) Item description example of EXTCyclicPDUExtensionFlg element<p:deviceInfoMember label="EXTCyclicPDUExtensionFlg"><p:label2><p:item>EXTCyclicPDUExtensionFlg</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Cyclic Transmission PDU Extension Module Availability Flag</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-449

Basically, write the information in accordance with Section 5.3.1 "COMM_IF_INFO part".
Furthermore, write the elements listed in "Table 5-466 List of Elements Written in COMM_IF_INFO Part"
for the main module section in the integrated main/extension module unit.
Table 5-466 List of Elements Written in COMM_IF_INFO Part
No.
1.
2.

Element"EXTx_"+"RPDOConfigMemoryAddre
ss""EXTx_"+"TPDOConfigMemoryAddre
ss"

Required/
Optional

Description Details
RPDO memory address for extension module
section x
TPDO memory address for extension module
section x

Optional
Optional(1) Item description of EXTx_RPDOConfigMemoryAddress element
No. Item Name
Description Details
1.
LABEL
Write "EXTx_"+"RPDOConfigMemoryAddress".*1
Write "EXTx_"+"RPDOConfigMemoryAddress" in the case of English CSP+ files.
2.
LABEL2[Recommended specifications]*1
3.
CATEGORY Write "COMMON_ExType".
Write "RPDO Configuration Memory Address for Extension Module Section x" in the case of
4.
NAME
English CSP+ files.
[Recommended specifications]*1
5.
DATATYPE Write "DWORD".
Write the memory address of the sub-payload to be used for RPDO communication for the6.
DATA
extension module section x.*1
*1: x indicates the extension module section number.
(a) Item description example of EXT1_RPDOConfigMemoryAddress element<p:commIfInfoMember label="EXT1_RPDOConfigMemoryAddress"><p:label2><p:item>EXT1_RPDOConfigMemoryAddress</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>RPDO Configuration Memory Address for Extension Module Section
1</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00001000</p:item></p:data></p:commIfInfoMember>(2) Item description of EXTx_TPDOConfigMemoryAddress element
No. Item Name
Description Details
1.
LABEL
Write "EXTx_"+"TPDOConfigMemoryAddress".*1
Write "EXTx_"+"TPDOConfigMemoryAddress" in the case of English CSP+ files.
2.
LABEL2[Recommended specifications]*1
3.
CATEGORY Write "COMMON_ExType".
Write "TPDO Configuration Memory Address for Extension Module Section x" in the case of
4.
NAME
English CSP+ files.
[Recommended specifications]*1
5.
DATATYPE Write "DWORD".
Write the memory address of the sub-payload to be used for TPDO communication for the6.
DATA
extension module section x.*1
*1: x indicates the extension module section number.
(a) Item description example of EXT1_TPDOConfigMemoryAddress element<p:commIfInfoMember label="EXT1_TPDOConfigMemoryAddress"><p:label2><p:item>EXT1_TPDOConfigMemoryAddress</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category>
CLPA

BAP-C2008ENG-001-K
1-450

<p:name><p:item>TPDO Configuration Memory Address for Extension Module Section
1</p:item></p:name><p:datatype><p:item>DWORD</p:item></p:datatype><p:data><p:item>0x00002000</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-451

As described in Section 4.2.11 "CSP+ file structure of the integrated main/extension module unit over
CC-Link IE TSN", the INPUT and OUTPUT description specifications are not used for the main module
section in the integrated main/extension module unit.

As described in Section 4.2.11 "CSP+ file structure of the integrated main/extension module unit over
CC-Link IE TSN", the PARAMETER description specifications are not used for the main module sectionin the integrated main/extension module unit.

As described in Section 4.2.11 "CSP+ file structure of the integrated main/extension module unit over
CC-Link IE TSN", the METHOD description specifications are not used for the main module section in the
integrated main/extension module unit.

Write error related information of the entire integrated main/extension module unit. The descriptions are
the same as those of a single module. For details, see Section 5.3.5 "COMM_IF_COMMAND part" andSection 5.5.10.1 "Parts and elements related to error related information".

Write error related information of the entire integrated main/extension module unit. The descriptions are
the same as those of a single module. For details, see Section 5.3.7 "MESSAGE part" and Section
5.5.10.1 "Parts and elements related to error related information".

CLPA

BAP-C2008ENG-001-K
1-452

5.5.10.6.3.
Extension module section
This section describes the description specifications of the CSP+ file for the extension module sectionin the integrated main/extension module unit.

The descriptions of FILE_INFO of extension module section are the same as those of a single module.
See Section 5.1.1 "FILE_INFO part".

CLPA

BAP-C2008ENG-001-K
1-453

Information about extension module sections is described in the DEVICE_INFO part. The following tablelists the described elements.
Table 5-467 List of Elements Written in DEVICE_INFO PartNo.

Element1.

VendorName

2.

VendorCode3.

DeviceModel

4.

ProductID

5.

DeviceTypeID

6.

DeviceTypeDetail

7.

VersionDescription Details
Write the name of the vendor that manufactured themodule.
Write the code of vendor that manufactured themodule.
The fifth to eighth digits of the membership number of
the CC-Link Partner Association are written.
Write the model of the module.
Write the product ID of the module.
The ID managed by the vendor that manufactured themodule is written.
Write the ID of the module type.
Write the specific device type.
Write the device version of the module.

Write whether to show/hide the device version to/fromthe user.
Write the policy of the relationship between the actual
device version and the device version described in the9.
VersionPolicyType
CSP+ file when the actual device is accessed using
the CSP+ file.
Write the value of the device version to be displayedwhen the value (Version) of the device version
10. DisplayVersionValue acquired from the actual device differs from the valueof the version displayed to the user on the utility
software.
Write a comment related to the device version.
11. VersionComment
8.

VersionDisplayFlg

DeviceConfigurationI Write a device configuration ID.
D
DeviceConfiguration Write a device configuration comment.
13.
Comment
Write a URL if the module information is disclosed on
14. ReferenceURL
the website.
Write the information indicated by the reference URL.
15. URLInfo
12.

16. Outline
17. Feature
18. SpecList
19. PowerSupplyVoltage
20. ConsumptionCurrent
21. IconFileName
CLPA

Write the general specifications of the module.
Write the features of the module.
Write the module specifications using a set of strings.
Write the power supply voltage in volts (V).
Write the current consumption in milliamperes (mA).

Required/
Optional
Required

Required

Required
Required*1*1Required
Required

Required

Description
Specifications
See Section
5.2.1.3.
See Section
5.2.1.3.

See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.

See Section
5.2.1.3.
Optional

Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional

Write the icon file name with the extension (.ico) when
Optional
displaying the module as an icon on the utility software.

See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.

BAP-C2008ENG-001-K
1-454

No.

Element

22. GraphicsFileName
23. Height
24. Width
25. Depth
26. Weight
27. Price

Description Details
Write the graphic file name with the extension(.bmp, .png, .jpg, or .gif) when displaying themodule on the utility software.
Write the height of the external dimensions with a unit.
Write the width of the external dimensions with a unit.
Write the depth of the external dimensions with a unit.
Write the weight with a unit.
Write the price with a unit.

Required/
Optional
Optional
Optional
Optional
Optional
Optional
Optional

Description
Specifications
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.
See Section
5.2.1.3.

Write the name of the Window to be specified in
UI_ATTRIBUTE_Win
UI_ATTRIBUTE.
Optional
dow**
The Window number is written in "**".
29. CyclicPDUFlg
Write the cyclic transmission PDU availability.
RequiredSee (1).
*1: Write either of the DeviceTypeID element or the DeviceTypeDetail element. When both of theelements are written, the DeviceTypeDetail element takes precedence.
28.

CLPA

BAP-C2008ENG-001-K
1-455

(1) Item description of CyclicPDUFlg element
No. Item Name
1.
LABEL
2.
3.
4.
5.
6.

Description Details
Write "CyclicPDUFlg".
Write "CyclicPDUFlg" in the case of English CSP+ files. [Recommended
LABEL2
specifications]
CATEGORY Write "COMMON_ExType".
Write "Cyclic Transmission PDU Availability" in the case of English CSP+ files.
NAME[Recommended specifications]
DATATYPE Write "BOOL".
0: Cannot be used
1: Can be used
DATA
For the extension module section in the integrated main/extension module unit, only
"1" can be written.

(a) Item description example of CyclicPDUFlg element<p:deviceInfoMember label="CyclicPDUFlg"><p:label2><p:item>CyclicPDUFlg</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Cyclic Transmission PDU Availability</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:deviceInfoMember>(2) Unusable elements
Elements related to the dedicated tool cannot be described in the DEVICE_INFO part of extension
module section in the integrated main/extension module unit.

CLPA

BAP-C2008ENG-001-K
1-456

Information about extension module sections is described in the COMM_IF_INFO part. The following
table lists the described elements.
Table 5-468 List of Elements Written in COMM_IF_INFO Part
Required/ Description
Optional Specifications
VendorName
Write the name of the vendor that manufactured the
See Section
1.
Requiredmodule.
5.4.1.3.
VenderCode
Write the code of vendor that manufactured themodule.
2.
Required
The fifth to eighth digits of the membership number of
the CC-Link Partner Association are written.
3. Version
Write the firmware version using a string.
Required
CommIFTypeID
Write the ID of the extension module section type in
See (1).
the integrated main/extension module unit using astring.
4.
Extension modules can be connected when
Required
EXTExtensionIFTypeID of the main module section
matches with CommIFTypeID of the extension
module section.
EXTExtensionModulePrio Write the priority of the extension module section.
See (2).
rity
Lower-priority extension module sections can only be
5.
Optional
connected to higher-priority extension module
sections.
EXTBuiltinType
Write the extension type or the integrated
See (3).
6.
Optional
main/extension module unit.
Write the communication interface ID of the mainSee (4).
EXTBasicModuleCommI module section. The same information as that
7.
Required
FTypeID
described in CommIFTypeID of the main module
section connected is written.
8. ModelCode
Write the model code.
Optional
See (5).
9. CanProfileNum
Write the supported CiA standard number.
Required See (6).
ObjectDictionaryFileNam Write the object dictionary file name.
See (7).
10.
Requirede
11. S_W_DefaultSize
Write the default size of the word data to be sent.
Required See (8).
12. R_W_DefaultSize
Write the default size of the word data to be received. Required See (9).
13. S_W_MaxSize
Write the maximum size of the word data to be sent. Required See (10).
Write the maximum size of the word data to be
See (11).
14. R_W_MaxSize
Requiredreceived.
15. S_W_MinSize
Write the minimum size of the word data to be sent. Optional
See (12).
Write the minimum size of the word data to be
See (13).
16. R_W_MinSize
Optional
received.
PDOConfigIndex+X
Write the index of the PDO configuration.
See (14).
17.
Required*1
PDOConfigPDOType+X Write the PDO type.
See (15).
18.
Required*1
PDOConfigPossibleMapp Write the index of the PDO mapping object as an
See (16).
19. ing+X
array in the priority order.
Required
*1

No.

CLPA

Element

Description Details

BAP-C2008ENG-001-K
1-457

*1: For elements where X is to be replaced with a number, apply the following conditions.
• Elements with the same X value should be written in the order listed in the table and also on aconsecutive basis. Nesting an element whose value X is different is prohibited.
PDOConfigIndex1
PDOConfigPDOType1
PDOConfigPossibleMapping1
PDOConfigIndex2
PDOConfigPossibleMapping2
PDOConfigPDOType2

PDOConfigIndex1
PDOConfigIndex2
PDOConfigPDOType1
PDOConfigPossibleMapping1
PDOConfigPDOType2
PDOConfigPossibleMapping2

The sortingorder iscorrect.

The sortingorder isreversed.

An element with adifferent value isnested.

• X needs to be a sequential number and omission of the number is prohibited.
PDOConfigIndex1
PDOConfigPDOType1
2 is skipped.
PDOConfigPossibleMapping1
PDOConfigIndex3
PDOConfigPDOType3
PDOConfigPossibleMapping3• Write the numbers in ascending order of the elements.
PDOConfigIndex2
Elements are not in
PDOConfigPDOType2
ascending order.
PDOConfigPossibleMapping2
PDOConfigIndex1
PDOConfigPDOType1
PDOConfigPossibleMapping1

CLPA

BAP-C2008ENG-001-K
1-458

(1) Item description of CommIFTypeID element
No.
Item Name
1.
LABEL
2.
LABEL2
3.
CATEGORY
4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CommIFTypeID".
Write "CommIFTypeID" in the case of English CSP+ files. [Recommended specifications]Write "COMMON".
Write "Communication Interface Type ID" in the case of English CSP+ files.
[Recommended specifications]Write "STRING(32)".
Write the ID of the extension module section type.
Write the same value in DATA as that in EXTExtensionIFTypeID of the main module
section.
(Example) When the vendor code is xxxx, write "VxxxxBuiltIn".
* xxxx is a four-digit natural number.

(a) Item description example of CommIFTypeID element<p:commIfInfoMember label="CommIFTypeID"><p:label2><p:item>CommIFTypeID</p:item></p:label2><p:category><p:item>COMMON</p:item></p:category><p:name><p:item>Communication Interface Type ID</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>VxxxxBuiltIn</p:item></p:data></p:commIfInfoMember>(2) Item description of EXTExtensionModulePriority element
No. Item Name
1.
LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "EXTExtensionModulePriority".
Write "EXTExtensionModulePriority" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Extension Module Priority" in the case of English CSP+ files. [Recommended
specifications]Write "INT8".
Write the priority of the extension module section in the range between -128 and 127.
Extension module sections with larger values can be connected closer to the main module
section.
If this element is omitted, it will be regarded as "0".

(a) Item description example of EXTExtensionModulePriority element<p:deviceInfoMember label="EXTExtensionModulePriority"><p:label2><p:item>EXTExtensionModulePriority</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Extension Module Priority</p:item></p:name><p:datatype><p:item>INT8</p:item></p:datatype><p:data><p:item>10</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-459

(3) Item description of EXTBuiltInType element
No.
1.
2.
3.
4.
5.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPE

6.

DATA

Description Details
Write "EXTBuiltInType".
Write "EXTBuiltInType" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_ExType".
Write "Built-in Type" in the case of English CSP+ files. [Recommended specifications]Write "BOOL".
Write an extension module or an extension module section in the integrated main/extension
module unit.
0: Not built-in type (Extension type)
1: Built-in type
For the integrated main/extension module unit, write "1".
If this element is omitted, it will be regarded as "0".

(a) Item description example of EXTBuiltInType element<p:deviceInfoMember label="EXTBuiltInType"><p:label2><p:item>EXTBuiltInType</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Built-in Type</p:item></p:name><p:datatype><p:item>BOOL</p:item></p:datatype><p:data><p:item>1</p:item></p:data></p:deviceInfoMember>(4) Item description of EXTBasicModuleCommIFTypeID element
No. Item Name
1.
LABEL
2.

LABEL2

3.

CATEGORY

4.

NAME

5.
6.

DATATYPE
DATA

Description Details
Write "EXTBasicModuleCommIFTypeID".
Write "MEXTBasicModuleCommIFTypeID" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_ExType".
Write "Main Module Communication Interface ID" in the case of English CSP+ files.
[Recommended specifications]Write "STRING(32)".
Write "CCLinkIETSN".

(a) Item description example of EXTBasicModuleCommIFTypeID element<p:deviceInfoMember label="EXTBasicModuleCommIFTypeID"><p:label2><p:item>EXTBasicModuleCommIFTypeID</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Main Module Communication Interface ID</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>CCLinkIETSN</p:item></p:data></p:deviceInfoMember>

CLPA

BAP-C2008ENG-001-K
1-460

(5) Item description of ModuleCode element
No.
1.
2.
3.
4.
5.
6.

Item NameLABELLABEL2
CATEGORYNAME
DATATYPE
DATA

Description Details
Write "ModuleCode".
Write "ModuleCode" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_ExType".
Write "Model Code" in the case of English CSP+ files. [Recommended specifications]Write "UINT32".
Write any model code.

(a) Item description example of ModuleCode element<p:deviceInfoMember label="ModuleCode"><p:label2><p:item>ModuleCode</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Model Code</p:item></p:name><p:datatype><p:item>UINT32</p:item></p:datatype><p:data><p:item>1234</p:item></p:data></p:deviceInfoMember>(6) Item description of CanProfileNum element
No.
1.
2.
3.

Item NameLABELLABEL2
CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "CanProfileNum".
Write "CanProfileNum" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_ExType".
Write "Supported CiA Standard Number" in the case of English CSP+ files.
[Recommended specifications]Write "STRING(32)".
Write the CiA standard number supported by the extension module section.
• 401: The CiA401 standard is supported.
• 402: The CiA402 standard is supported.

(a) Item description example of CanProfileNum element<p:commIfInfoMember label="CanProfileNum"><p:label2><p:item>CanProfileNum</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Supported CiA Standard Number</p:item></p:name><p:datatype><p:item>STRING(32)</p:item></p:datatype><p:data><p:item>401</p:item></p:data></p:commIfInfoMember>

CLPA

BAP-C2008ENG-001-K
1-461

(7) Item description of ObjectDictionaryFileName element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "ObjectDictionaryFileName".
Write "ObjectDictionaryFileName" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Object Dictionary File Name" in the case of English CSP+ files. [Recommended
specifications]Write "STRING(52)".
Write the object dictionary file name with the extension (.csv).
For a file name, only one-byte alphanumerical characters and symbols are usable.

(a) Item description example of ObjectDictionalyFileName element<p:commIfInfoMember label="ObjectDictionalyFileName"><p:label2><p:item>ObjectDictionalyFileName</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Object Dictionary File Name</p:item></p:name><p:datatype><p:item>STRING(52)</p:item></p:datatype><p:data><p:item>CiA401_ObjectDictionaly.csv</p:item></p:data></p:commIfInfoMember>(8) Item description of S_W_DefaultSize element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_W_DefaultSize".
Write "S_W_DefaultSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Send Word Data Default Size" in the case of English CSP+ files. [Recommended
specifications]Write "UINT16".
Write the default size of send word data (TPDO) in the number of words. The size must
be written with a numerical value equal to or larger than 0.
Set the value within the range S_W_MinSize ≤ S_W_DefaultSize ≤ S_W_MaxSize.

(a) Item description example of S_W_DefaultSize element<p:commIFInfoMember label="S_W_DefaultSize"><p:label2><p:item>S_W_DefaultSize</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Send Word Data Default Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>32</p:item></p:data></p:commIFInfoMember>

CLPA

BAP-C2008ENG-001-K
1-462

(9) Item description of R_W_DefaultSize element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "R_W_DefaultSize".
Write "R_W_DefaultSize" in the case of English CSP+ files. [Recommended
specifications]Write "COMMON_ExType".
Write "Receive Word Data Default Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the default size of receive word data (RPDO) in the number of words. The size must
be written with a numerical value equal to or larger than 0.
Set the value within the range R_W_MinSize ≤ R_W_DefaultSize ≤ R_W_MaxSize.

(a) Item description example of R_W_DefaultSize element<p:commIFInfoMember label="R_W_DefaultSize"><p:label2><p:item>R_W_DefaultSize</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Receive Word Data Default Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>32</p:item></p:data></p:commIFInfoMember>(10) Item description of S_W_MaxSize element
No.
1.
2.
3.

Item NameLABELLABEL2
CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_W_MaxSize".
Write "S_W_MaxSize" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_ExType".
Write "Send Word Data Maximum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the maximum size of send word data (TPDO) in the number of words. The sizemust be written with a numerical value equal to or larger than 0.
Set the value within the range S_W_MinSize ≤ S_W_DefaultSize ≤ S_W_MaxSize.

(a) Item description example of S_W_MaxSize element<p:commIFInfoMember label="S_W_MaxSize"><p:label2><p:item>S_W_MaxSize</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Send Word Data Maximum Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>64</p:item></p:data></p:commIFInfoMember>

CLPA

BAP-C2008ENG-001-K
1-463

(11) Item description of R_W_MaxSize element
No.
1.
2.
3.

Item NameLABELLABEL2
CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "R_W_MaxSize".
Write "R_W_MaxSize" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_ExType".
Write "Receive Word Data Maximum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the maximum size of receive word data (RPDO) in the number of words. The sizemust be written with a numerical value equal to or larger than 0.
Set the value within the range R_W_MinSize ≤ R_W_DefaultSize ≤ R_W_MaxSize.

(a) Item description example of R_W_MaxSize element<p:commIFInfoMember label="R_W_MaxSize"><p:label2><p:item>R_W_MaxSize</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Receive Word Data Maximum Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>64</p:item></p:data></p:commIFInfoMember>(12) Item description of S_W_MinSize element
No.
1.
2.
3.

Item NameLABELLABEL2
CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "S_W_MinSize".
Write "S_W_MinSize" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_ExType".
Write "Send Word Data Minimum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINT16".
Write the minimum size of send word data (TPDO) in the number of words. The size must
be written with a numerical value equal to or larger than 0.
Set the value within the range S_W_MinSize ≤ S_W_DefaultSize ≤ S_W_MaxSize.
If this element is omitted, it will be regarded as "0".

(a) Item description example of S_W_MinSize element<p:commIFInfoMember label="S_W_MinSize"><p:label2><p:item>S_W_MinSize</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Send Word Data Minimum Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>16</p:item></p:data></p:commIFInfoMember>

CLPA

BAP-C2008ENG-001-K
1-464

(13) Item description of R_W_MinSize element
No.
1.
2.
3.

Item NameLABELLABEL2
CATEGORY

4.

NAME

5.

DATATYPE

6.

DATA

Description Details
Write "R_W_MinSize".
Write "R_W_MinSize" in the case of English CSP+ files. [Recommended specifications]Write "COMMON_ExType".
Write "Receive Word Data Minimum Size" in the case of English CSP+ files.
[Recommended specifications]Write "UINIT16".
Write the minimum size of receive word data (RPDO) in the number of words. The sizemust be written with a numerical value equal to or larger than 0.
Set the value within the range R_W_MinSize ≤ R_W_DefaultSize ≤ R_W_MaxSize.
If this element is omitted, it will be regarded as "0".

(a) Item description example of R_W_MinSize element<p:commIFInfoMember label="R_W_MinSize"><p:label2><p:item>R_W_MinSize</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>Receive Word Data Minimum Size</p:item></p:name><p:datatype><p:item>UINT16</p:item></p:datatype><p:data><p:item>16</p:item></p:data></p:commIFInfoMember>(14) Item description of PDOConfigIndex+X element
No.
1.

Item Name
LABEL

Description Details
Write "PDOConfigIndex+X".
Write "PDOConfigIndex+X" in the case of English CSP+ files. [Recommended
2.
LABEL2
specifications]
3.
CATEGORY
Write "COMMON_ExType".
Write "PDO Configuration Index +X" in the case of English CSP+ files. [Recommended
4.
NAME
specifications]
5.
DATATYPE
Write "WORD".
Write the index of PDO configuration in the range between 0x1C00 and 0x1CFF.
6.
DATA
For details, see "D.2 PDO Config" in the CC-Link IE TSN Specifications (Overview) BAPC2011ENG-001.
*1: X indicates the extension module section number.
(a) Item description example of PDOConfigIndex+X element<p:commIFInfoMember label="PDOConfigIndex1"><p:label2><p:item>PDOConfigIndex1</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>PDO Configuration Index 1</p:item></p:name><p:datatype><p:item>WORD</p:item></p:datatype><p:data><p:item>0x1C00</p:item></p:data></p:commIFInfoMember>

CLPA

BAP-C2008ENG-001-K
1-465

(15) Item description of PDOConfigPDOType+X element
No.
1.

Item Name
LABEL

Description Details

Write "PDOConfigPDOType+X".
Write "PDOConfigPDOType+X" in the case of English CSP+ files. [Recommended
2.
LABEL2
specifications]
3.
CATEGORY
Write "COMMON_ExType".
Write "PDO Configuration PDO Type +X" in the case of English CSP+ files.
4.
NAME[Recommended specifications]
5.
DATATYPE
Write "BYTE".
Write the PDO type.
6.
DATA
0x00: RPDO
0X01: TPDO
*1: X indicates the extension module section number.
(a) Item description example of PDOConfigPDOType+X element<p:commIFInfoMember label=PDOConfigPDOType1><p:label2><p:item>PDOConfigPDOType1</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>PDO Configuration PDO Type 1</p:item></p:name><p:datatype><p:item>BYTE</p:item></p:datatype><p:data><p:item>0x01</p:item></p:data></p:commIFInfoMember>(16) Item description of PDOConfigPossibleMapping+X element
No.
1.

Item Name
LABEL

2.

LABEL2

3.

CATEGORY

4.

NAME

5.

DATATYPE

Description Details
Write "PDOConfigPossibleMapping+X".*1
Write "PDOConfigPossibleMapping+X" in the case of English CSP+ files.
[Recommended specifications]Write "COMMON_ExType".
Write "PDO Configuration Mapping Candidate +X" in the case of English CSP+ files.
[Recommended specifications]Write "WORD[x]".*2
Write the index of the PDO mapping object that can be set in the subindex 0x01: PDO
Assignment of PDO configuration, as an array in priority order (ascending order).
The first element in the array is the default value.

6.

DATA

[Note]The mapping selection window of the configuration tool displays the value of the Name
item in which the subindex of the PDO mapping object is set to the 0x00 entry. Therefore,
set the Name item of the subindex 0x00 entry with a name by which the content andmeaning of the corresponding mapping object can be identified.
*1: X indicates the extension module section number.
*2: x indicates the number of elements. x = 1 to 512(a) Item description example of PDOConfigPossibleMapping+X element<p:commIFInfoMember label=PDOConfigPossibleMapping1><p:label2><p:item>PDOConfigPossibleMapping1</p:item></p:label2><p:category><p:item>COMMON_ExType</p:item></p:category><p:name><p:item>PDO Configuration Mapping Candidate 1</p:item></p:name><p:datatype><p:item>WORD[2]</p:item></p:datatype><p:data><p:item>0x1600</p:item><p:item>0x1601</p:item></p:data></p:commIFInfoMember>

CLPA

BAP-C2008ENG-001-K
1-466

Write error related information to be output by the extension module section. The descriptions are thesame as those of a single module. For details, see Section 5.3.5 "COMM_IF_COMMAND part" andSection 5.5.10.1 "Parts and elements related to error related information".

Write error related information to be output by the extension module section. The descriptions are thesame as those of a single module. For details, see Section 5.3.7 "MESSAGE part" and Section 5.5.10.1"Parts and elements related to error related information".

CLPA

BAP-C2008ENG-001-K
1-467

6.

CSP+ Description Method

6.1

CSP+ Version Management Method
Figure 6-1 shows an example of updating the profile description for one device. The following
describes the rules for updating the profile description and managing the updated file.
(1) When you create a CSP+ file in which the device version has been updated, manage the file asindicated below in accordance with the value of the VersionPolicyType element [see Section
5.2.1.3(9)].
[When the VersionPolicyType element is 0 (When only the latest CSP+ file is managed)]
Update and manage only the CSP+ file of the latest device version [Recommended
specifications].
[When the VersionPolicyType element is a value other than 0 (When a CSP+ file is managed foreach device version)]Manage the CSP+ file of the old device version and the CSP+ file of the new device version inparallel [Required]. Then, update the CSP+ file of the old device version as required[Recommended specifications].
* The utility software uses the mass production device in accordance with the device version
described in the CSP+ file. As a result, the old CSP+ file needs to be managed as well.
(2) When you create a CSP+ file in which the minor version of the CSP+ specification version is
updated, manage only the CSP+ file of the new version.
* For details on the major version and minor version of the CSP+ specification version, see
Section 5.1.1.3(6).
(3) When you create a CSP+ file in which the major version of the CSP+ specification version is
updated, you need to manage the old CSP+ file as well.
* Note, however, that in a case where the file does not need to be used with utility software that
does not support the new major version, there is no need to manage the old CSP+ file.
(4) CSP+ files for the same device version need to be managed so that there are no duplicate fileversions [Required].
(5) For CSP+ files in which only the language-dependent information differs while all otherinformation is the same, make the major numbers of the file versions the same [Required].
* For details on the major version and minor version of the file version, see Section 5.1.1.3(7).
*Utility software that supports other languages determines the target CSP+ file by the device
version and major version of the file version only.

*

For example, in a case where only a Japanese portion of a Japanese version CSP+ file needs
to be corrected and the CSP+ files of other languages do not, increase the minor number ofthe file version of the Japanese version CSP+ file and leave the major version as is.

(6) For CSP+ files in which the device versions are the same and the major versions of the CSP+
specification versions are the same, the CSP+ file with the higher file version is regarded asnewer and used with priority by the utility software [Required].
* The priority order between CSP+ files having different major versions is determined by the fileversion alone.
(7) When a device version is increased, set the the file version as 1.
[Recommended specifications].

CLPA

BAP-C2008ENG-001-K
1-468

(1) Manage CSP+ files for each device version.
(4) Manage CSP+ files for the same device version so that there are no duplicate
file versions.
(7) When you update the device version, set the file version to one.

Device version A(2) When you create a
CSP+ file in which theminor version of the
CSP+ specification
version is updated, you
do not need to manage
the old CSP+ file.
(6) If the device versions
and the major versionsof the CSP+
specification versions
are the same, the
CSP+ file with thehigher file version isnewer.

Device version: A
CSP+ specification
version:1.0
File version:1

Device version: A
CSP+ specification
version:1.1
File version:2

Device version: A
CSP+ specification
version:2.0
File version:3

Device version B

Device version C

Device version: B
CSP+ specification
version:2.0
File version:1

Device version: C
CSP+ specification
version:2.2
File version:1

Device version: B
CSP+ specification
version:2.1
File version:2

Device version: C
CSP+ specification
version:2.2
File version:2

Device version: B
CSP+ specification
version:2.2
File version:3(3) When you update the major versionof the CSP+ specification version, it
is preferred that you manage the
new CSP+ file and the old CSP+ filein parallel for utilities that do notsupport the new major version.
Device version: A
CSP+ specification
version:2.1
File version:4

Device version: B
CSP+ specification
version:2.3
File version:4[Otherlanguage version]
Device version: C
CSP+ specification
version:2.2
File version:2*The device
versions and the
major versions of
the file versions are
the same, so thewritten contents are
regarded as thesame.

Device version: C
CSP+ specification
version:2.2
File version:2.1(5) If you make a change that does not affect the
CSP+ files of other languages, increase theminor version of the file version.
 An underline indicates that thevalue is updated.

 For CSP+ files with the same device versions, manage only the newest
file. (When a lower CSP+ file in the figure is created, there is no need to
update the above CSP+ file.) For CSP+ files of each device version, manage the old CSP+ files aswell. (When a CSP+ file on the right side in the figure is created, youneed to update the CSP+ file on the left side as well.)Figure 6-1 Version Update Example

6.2

Other Language Management
When you want to support a CSP+ file in another language for a device of the same model, change
only the items below. Do not change any other item. [Recommended specifications]
LABEL2NAME
CATEGORYDATACOMMENTENG_UNIT* While substantially all units do not need to be changed, change is required for those units written
using double-byte characters, not alphanumeric characters, such as "Ω".
In addition, as indicated in this section, for CSP+ files that simply have different language-dependent
information with all other information being the same, write the same major version [see Section
5.1.1.3(7)] in the file version for the CSP+ files.

CLPA

BAP-C2008ENG-001-K
1-469

CSP+ File Management

6.3

The utility software uses the following seven types of information when identifying a CSP+ file:[1] Model[2] Vendor code
[3] Supported language information[4] Device version[5] CSP+ specification version[6] File version[7] Device configuration ID
Table 6-1 describes each identifier as well as the methods used by the utility software for managing
CSP+ files having different identifiers. The CSP+ file creator and manager need to create a profile
description so that the utility software can execute management as shown in Table 6-1. In particular,
caution is required during device version management since the CSP+ files of older version also
require management.
Table 6-1 Information for Identifying CSP+ File and Management Method by Utility Software
No.
1.
2.
3.

4.

5.
6.
7.

CLPA

Type of Identifier
Model(See DeviceModel of
DEVICE_INFO in Section 5.2.1.3.)
Vendor code
(See VendorCode of
DEVICE_INFO in Section 5.2.1.3.)
Supported language information(See Language of FILE_INFO of
Section 5.1.1.3.)
Device version(See Version of DEVICE_INFO of
Section 5.2.1.3.)
CSP+ specification version(See CCLinkFamilyProfileVersionof FILE_INFO of Section 5.1.1.3.)
File version(See FileVersion of FILE_INFO of
Section 5.1.1.3.)
Device configuration ID(See DeviceConfigurationID of
DEVICE_INFO of Section 5.2.1.3.)

Management Method by Utility Software
Manage the CSP+ files of all models separately(recommended).
Manage the CSP+ files of all vendor codes separately(recommended).
Manage the CSP+ files of all language information separately(recommended).
Manage the CSP+ files of all device versions separately(recommended). However, in a case of a device in which a
CSP+ file of the latest device version can be used [a device inwhich the VersionPolicyType (See Section 5.2.1.3(9) is 0),
manage only the profile of the newest device version.
Manage the CSP+ file having the highest version among all of
the versions of CSP+ specifications supported by the utility
software (recommended).
Manage only the newest CSP+ file (recommended).
Manage CSP+ files with/without information and with content
differences separately (recommended).

BAP-C2008ENG-001-K
1-470

7.

Control & Communication System Profile XML Scheme

7.1

XML Schema
The following describes the XML schema for CSP+.

<?xml version="1.0" encoding="utf-8"?><xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"targetNamespace="http://cc-link.org/cspplus/ver3/"
xmlns:p="http://cc-link.org/cspplus/ver3/"><!--******************************************--><!--[Overall Structure]--><!--******************************************--><?xml version="1.0" encoding="utf-8"?><xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"targetNamespace="http://cc-link.org/cspplus/ver2/"
xmlns:p="http://cc-link.org/cspplus/ver2/"><!--******************************************--><!—[Overall Structure] --><!--******************************************--><xsd:element name="profile"><xsd:complexType><xsd:sequence><xsd:element ref="p:file" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:device" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:block" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:commIf" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType></xsd:element><!--******************************************--><!—[Structure of each section] --><!--******************************************--><!-- Sections --><xsd:element name="file"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:fileInfo" minOccurs="1" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="device"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:deviceInfo" minOccurs="1" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="block"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:blockInfo" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:blockInput" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:blockOutput" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:blockParameter" minOccurs="0" maxOccurs="unbounded"/>

CLPA

BAP-C2008ENG-001-K
1-471

<xsd:element ref="p:blockCommand" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:struct" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:enum" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:commandArgument" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:condition" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="commIf"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:commIfInfo" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:commIfInput" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:commIfOutput" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:commIfParameter" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:commIfCommand" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:method" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:message" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:struct" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:enum" minOccurs="0" maxOccurs="unbounded"/><xsd:element ref="p:commandArgument" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><!--******************************************--><!—[Structure of various parts] --><!--******************************************--><!—Defines the Member structure of parts for INFO--><xsd:complexType name="InfoTableMemberType"><xsd:sequence><xsd:element ref="p:label2" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:category" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:name" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:datatype" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:data" minOccurs="1" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType><!—Defines structure of FILE_INFO part--><xsd:element name="fileInfo"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:fileInfoMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="fileInfoMember" type="p:InfoTableMemberType"/><!--Defines structure of DEVICE_INFO part--><xsd:element name="deviceInfo"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:deviceInfoMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element>

CLPA

BAP-C2008ENG-001-K
1-472

<xsd:element name="deviceInfoMember" type="p:InfoTableMemberType"/><!--Defines structure of BLOCK_INFO part--><xsd:element name="blockInfo"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:blockInfoMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="blockInfoMember" type="p:InfoTableMemberType"/><!--Defines structure of COMM_IF_INFO part--><xsd:element name="commIfInfo"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:commIfInfoMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="commIfInfoMember" type="p:InfoTableMemberType"/><!-- Defines Member structure of BLOCK_INPUT, BLOCK_OUTPUT parts --><xsd:complexType name="BlockTableMemberType"><xsd:sequence><xsd:element ref="p:label2" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:category" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:name" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:datatype" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:default" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:range" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:minInc" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:engUnit" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:access" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:uiAttribute" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType><!—Defines structure of BLOCK_INPUT parts--><xsd:element name="blockInput"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:blockInputMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="blockInputMember" type="p:BlockTableMemberType"/><!—Defines structure of BLOCK_OUTPUT parts--><xsd:element name="blockOutput"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:blockOutputMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element>

CLPA

BAP-C2008ENG-001-K
1-473

<xsd:element name="blockOutputMember" type="p:BlockTableMemberType"/><!-- Defines structure of BLOCK_PARAMETER part--><xsd:element name="blockParameter"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element
ref="p:blockParameterMember"
maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element>

minOccurs="1"<xsd:element name="blockParameterMember"><xsd:complexType><xsd:sequence><xsd:element ref="p:label2" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:category" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:name" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:datatype" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:default" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:range" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:minInc" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:engUnit" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:access" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:writeOrder" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:uiAttribute" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><!--Defines structure of BLOCK_COMMAND part--><xsd:element name="blockCommand"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:blockCommandMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="blockCommandMember"><xsd:complexType><xsd:sequence><xsd:element ref="p:label2" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:category" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:name" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:argument" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><!-- Defines structure of COMM_IF_INPUT, COMM_IF_OUTPUT parts --><xsd:complexType name="CommIfTableMemberType"><xsd:sequence><xsd:element ref="p:label2" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:category" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:name" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:datatype" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:default" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:range" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:minInc" minOccurs="0" maxOccurs="1"/>

CLPA

BAP-C2008ENG-001-K
1-474

<xsd:element ref="p:engUnit" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:access" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:assign" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:uiAttribute" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:ref" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType><!-- Defines structure of COMM_IF_INPUT part --><xsd:element name="commIfInput"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:commIfInputMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="commIfInputMember" type="p:CommIfTableMemberType"/><!-- Describes structure of COMM_IF_OUTPUT part --><xsd:element name="commIfOutput"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:commIfOutputMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="commIfOutputMember" type="p:CommIfTableMemberType"/><!-- Defines structure of COMM_IF_PARAMETER part --><xsd:element name="commIfParameter"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:commIfParameterMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="commIfParameterMember"><xsd:complexType><xsd:sequence><xsd:element ref="p:label2" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:category" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:name" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:datatype" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:default" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:range" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:minInc" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:engUnit" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:access" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:writeOrder" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:assign" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:uiAttribute" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:ref" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element>

CLPA

BAP-C2008ENG-001-K
1-475

<!—Defines structure of COMM_IF_COMMAND part --><xsd:element name="commIfCommand"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:commIfCommandMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="commIfCommandMember"><xsd:complexType><xsd:sequence><xsd:element ref="p:label2" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:category" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:name" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:argument" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:ref" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><!—Defines structure of METHOD part--><xsd:element name="method"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:methodMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="methodMember"><xsd:complexType><xsd:sequence><xsd:element ref="p:label2" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:category" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:name" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:target" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:methodType" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:writeRegister" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:writeData" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:writeDatatype" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:readRegister" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:readData" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:readDatatype" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:interlock" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:reqFlag" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:endCondition" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:errCondition" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:errRegister" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:errCodeRange" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:relatedMethod" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><!—Defines structure of MESSAGE part--><xsd:element name="message"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:messageMember" minOccurs="1" maxOccurs="unbounded"/>

CLPA

BAP-C2008ENG-001-K
1-476

</xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="messageMember"><xsd:complexType><xsd:sequence><xsd:element ref="p:label2" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:category" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:name" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:target" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:messageType" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:requestType" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:requestData" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:requestDatatype" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:responseType" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:responseData" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:responseDatatype" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:errType" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:errCodeRange" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:relatedMessage" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><!-- Common information --><!—Defines structure of STRUCT part--><xsd:element name="struct"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:structMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="structMember"><xsd:complexType><xsd:sequence><xsd:element ref="p:label2" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:category" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:name" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:datatype" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:default" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:range" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:minInc" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:engUnit" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:offset" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:ref" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><!—Defines structure of ENUM part —><xsd:element name="enum"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:enumMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element>

CLPA

BAP-C2008ENG-001-K
1-477

<xsd:element name="enumMember"><xsd:complexType><xsd:sequence><xsd:element ref="p:label2" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:category" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:name" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:code" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:relatedEle" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:comment" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><!—Defines structure of COMMAND_ARGUMENT part--><xsd:element name="commandArgument"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:commandArgumentMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><xsd:element name="commandArgumentMember"><xsd:complexType><xsd:sequence><xsd:element ref="p:label2" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:category" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:name" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:datatype" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:default" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:range" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:minInc" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:engUnit" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:access" minOccurs="1" maxOccurs="1"/><xsd:element ref="p:assign" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:ref" minOccurs="0" maxOccurs="1"/><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/></xsd:sequence><xsd:attribute name="label" type="p:LabelType" use="required"/></xsd:complexType></xsd:element><!—Defines structure of CONDITION part--><xsd:element name="condition"><xsd:complexType><xsd:sequence><xsd:element ref="p:comment" minOccurs="0" maxOccurs="1"/><!--Describes reference information to labels used for expressions--><xsd:element ref="p:conditionVariable" minOccurs="1" maxOccurs="1"/><!--Writes values used for conditional judgment--><xsd:element ref="p:conditionMember" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="label" type="xsd:string" use="required"/><xsd:attribute name="conditionNumber" type="xsd:positiveInteger" use="required"/><xsd:attribute name="resultNumber" type="xsd:positiveInteger" use="required"/></xsd:complexType></xsd:element><xsd:element name="conditionVariable"><xsd:complexType><xsd:sequence><xsd:element ref="p:conditionXVariable" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType></xsd:element>

CLPA

BAP-C2008ENG-001-K
1-478

<xsd:element name="conditionMember"><xsd:complexType><xsd:sequence><xsd:element ref="p:conditionX" minOccurs="1" maxOccurs="unbounded"/><xsd:element ref="p:resultX" minOccurs="0" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType></xsd:element><!--******************************************--><!—[Item type declaration] --><!--******************************************--><xsd:element name="label2" type="p:ItemLabel2Type"/><xsd:element name="category" type="p:ItemType"/><xsd:element name="name" type="p:ItemType"/><xsd:element name="datatype" type="p:ItemOrStructType"/><xsd:element name="default" type="p:ItemType"/><xsd:element name="range" type="p:ItemListOrEnumOrConditionType"/><xsd:element name="minInc" type="p:ItemOrConditionType"/><xsd:element name="engUnit" type="p:ItemOrConditionType"/><xsd:element name="assign" type="p:ItemType"/><xsd:element name="access" type="p:ItemOrConditionType"/><xsd:element name="ref" type="p:ItemFLabelListType"/><xsd:element name="comment" type="p:IndexedItemType"/><xsd:element name="uiAttribute" type="p:ItemListType"/><xsd:element name="writeOrder" type="p:ItemType"/><xsd:element name="data" type="p:ItemListType"/><xsd:element name="argument" type="p:ItemType"/><!—Items for Method --><xsd:element name="target" type="p:ItemListType"/><xsd:element name="methodType" type="p:ItemListType"/><xsd:element name="writeRegister" type="p:ItemType"/><xsd:element name="writeData" type="p:ItemType"/><xsd:element name="writeDatatype" type="p:ItemType"/><xsd:element name="readRegister" type="p:ItemType"/><xsd:element name="readData" type="p:ItemType"/><xsd:element name="readDatatype" type="p:ItemType"/><xsd:element name="interlock" type="p:ItemType"/><xsd:element name="reqFlag" type="p:ItemListType"/><xsd:element name="endCondition" type="p:ItemListType"/><xsd:element name="errCondition" type="p:ItemType"/><xsd:element name="errRegister" type="p:ItemType"/><xsd:element name="errCodeRange" type="p:ItemListOrEnumType"/><xsd:element name="relatedMethod" type="p:ItemListType"/><!—Items for Message--><xsd:element name="messageType" type="p:ItemListType"/><xsd:element name="requestType" type="p:ItemType"/><xsd:element name="requestData" type="p:ItemType"/><xsd:element name="requestDatatype" type="p:ItemType"/><xsd:element name="responseType" type="p:ItemType"/><xsd:element name="responseData" type="p:ItemType"/><xsd:element name="responseDatatype" type="p:ItemType"/><xsd:element name="errType" type="p:ItemType"/><xsd:element name="relatedMessage" type="p:ItemListType"/><!—Items for common information--><xsd:element name="offset" type="p:ItemType"/><xsd:element name="code" type="p:ItemType"/><xsd:element name="relatedEle" type="p:ItemType"/><xsd:element name="conditionXVariable" type="p:IndexedItemType"/><xsd:element name="conditionX" type="p:IndexedItemListType"/><xsd:element name="resultX" type="p:IndexedItemListOrEnumType"/><!--******************************************--><!—[Type Definition] --><!--******************************************--><!--Type for items that only describe “item”-->

CLPA

BAP-C2008ENG-001-K
1-479

<xsd:complexType name="ItemType"><xsd:sequence><xsd:element ref="p:item" minOccurs="1" maxOccurs="1"/></xsd:sequence></xsd:complexType><!--Type for items that can describe multiple “items”--><xsd:complexType name="ItemListType"><xsd:sequence><xsd:element ref="p:item" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType><!--Type definition for items that can write references to “item” or STRUCT--><xsd:complexType name="ItemOrStructType"><xsd:choice><xsd:element ref="p:item"/><xsd:element ref="p:structRefItem"/></xsd:choice></xsd:complexType><!--Type definition for items that can write references to “item” or CONDITION--><xsd:complexType name="ItemOrConditionType"><xsd:choice><xsd:element ref="p:item"/><xsd:element ref="p:conditionRefItem"/></xsd:choice></xsd:complexType><!--Item definition that can write references to multiple description of “item” or
ENUM or references to CONDITION--><xsd:complexType name="ItemListOrEnumType"><xsd:choice><xsd:element ref="p:item" minOccurs="1" maxOccurs="unbounded"/><xsd:element ref="p:enumRefItem"/></xsd:choice></xsd:complexType><!--Item definition that can write multiple description of “item” or references to
ENUM or references to CONDITION--><xsd:complexType name="ItemListOrEnumOrConditionType"><xsd:choice><xsd:element ref="p:item" minOccurs="1" maxOccurs="unbounded"/><xsd:element ref="p:enumRefItem"/><xsd:element ref="p:conditionRefItem"/></xsd:choice></xsd:complexType><!--Type for items that describe only “item” for LABEL--><xsd:complexType name="ItemLabel2Type"><xsd:sequence><xsd:element name="item" type="p:Label2Type" minOccurs="1" maxOccurs="1"/></xsd:sequence></xsd:complexType><!--Type that can describe multiple reference “items” with LABEL--><xsd:complexType name="ItemFLabelListType"><xsd:sequence><xsd:element name="item" type="p:FLabelType" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence></xsd:complexType><!--Type for items that have “index” and can only use “item”—><xsd:complexType name="IndexedItemType"><xsd:sequence><xsd:element ref="p:item" minOccurs="1" maxOccurs="1"/></xsd:sequence><xsd:attribute name="index" type="xsd:positiveInteger" default="1" /></xsd:complexType>CLPA

BAP-C2008ENG-001-K
1-480

<!--Type for items that have “index” and define multiple “items”--><xsd:complexType name="IndexedItemListType"><xsd:sequence><xsd:element ref="p:item" minOccurs="1" maxOccurs="unbounded"/></xsd:sequence><xsd:attribute name="index" type="xsd:positiveInteger" default="1" /></xsd:complexType><!--Type for items that have “index” and can describe multiple “items” or can write
reference to Enum-->
sd:complexType name="IndexedItemListOrEnumType"><xsd:choice><xsd:element ref="p:item" minOccurs="1" maxOccurs="unbounded"/><xsd:element ref="p:enumRefItem"/></xsd:choice><xsd:attribute name="index" type="xsd:positiveInteger" default="1" /></xsd:complexType><xsd:element name="item"><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:minLength value="1"/></xsd:restriction></xsd:simpleType></xsd:element><xsd:element name="structRefItem" type="p:FLabelType"/><xsd:element name="enumRefItem" type="p:FLabelType"/><xsd:element name="conditionRefItem" type="p:FLabelType"/><xsd:simpleType name="LabelType"><xsd:restriction base="xsd:string"><xsd:pattern value="[a-zA-Z][a-zA-Z0-9_]{0,31}"/></xsd:restriction></xsd:simpleType><xsd:simpleType name="FLabelType"><xsd:restriction base="xsd:string"><xsd:pattern value="[a-zA-Z][a-zA-Z0-9_]*(¥.[a-zA-Z][a-zA-Z0-9_]*)*"/></xsd:restriction></xsd:simpleType><xsd:simpleType name="Label2Type"><xsd:restriction base="xsd:string"><xsd:pattern value="[^0-9_!&quot;#$%&amp;'()*+,¥-¥./:;&lt;=&gt;?@¥[¥¥¥]^`{|}~][^!&quot;#$%&amp;'()*+,¥-¥./:;&lt;=&gt;?@¥[¥¥¥]^`{|}~ ]{0,31}"/></xsd:restriction></xsd:simpleType></xsd:schema>

CLPA

BAP-C2008ENG-001-K
1-481

8. Description Specifications of Object Dictionary File
CSV File Format

8.1

Table 8-1 shows the format of the CSV file to write the object dictionary.
Table 8-1 CSV File Format
No.

Line No.

Details

1.

1st line

Header part2.

2nd line or
later

Data part

Description
Write the item name of each column.
Each of the item names are shown in the Item Name columnof Table 8-2 Item List.
Write one entry information per line. Write the items in thecolumn order that they are shown in the header part.

The following shows the precautions on creating a CSV file.
• Do not information other than that shown in Table 8-1 in the CSV file.
• When changing the CSV file, change the descriptions of the elements for the device version andfirmware version of the CSP+ file as necessary.
• Use Unicode (with UTF-16 little endian BOM) for the file format.
• Use a comma (,) for the delimiter between items.
• If a comma (,) or a double quotation mark (") is included in an item (which can be used only for acomment in Table 8-2 Item List), the item is enclosed double quotation marks and the double
quotation mark (") in the item is represented by two double quotation marks ("").
• Set a line feed (line feed code: CR+LF) at the end of a line.
Figure 8-1 CSV File Output Example shows an output example of a CSV file. The descriptions of some
objects (entries) are omitted in this example.

Figure 8-1 CSV File Output Example

CLPA

BAP-C2008ENG-001-K
1-482

Description Specifications for Each Item

8.2

Table 8-2 Item List lists the items of objects written in the CSV file.
Table 8-2 Item List
No.

Item Name

1.

Index

2.

SubIndex

3.

ObjectCode

4.

DataType

5.

BitLength6.

Access7.

Mapping

8.

UnitType

9.

DefaultValue

10.

MinValue

11.

MaxValue

12.

Name

CLPA

Required/
Optional

Description Details
Write the address (index) for accessing the object in a 2-byte
numerical value (hexadecimal).
Write the address (subindex) for accessing the entry in a 1-byte
numerical value (hexadecimal).
Write the structure (object code) of the entry in a 1-byte numericalvalue (hexadecimal).
0x05: DEFTYPE
0x07: VAR
0x08: ARRAY
0x09: RECORD
Write the data type of the entry in a 2-byte numerical value(hexadecimal).
0x0002: INTEGER80x0003: INTEGER160x0004: INTEGER32
0x0005: UNSIGNED80x0006: UNSIGNED160x0007: UNSIGNED32
0x0009: VISIBLE_STRING
Write the bit length of the entry in a 2-byte numerical value(hexadecimal).
Write the access attribute of the entry in a string.
R: Only reading is possible.
W: Only writing is possible.
RW: Both reading and writing are possible.
NA: Access is not possible.
Write the mapping availability in a 2-byte numerical value(hexadecimal).
Specify the mapping availability with the following bits.
Bit 0 to 5: Reserved (fixed to 0)
Bit 6: RPDO mapping availability (0: Unavailable, 1: Available)
Bit 7: TPDO mapping availability (0: Unavailable, 1: Available)
Bit 8 to 15: Reserved (fixed to 0)
Write the entry unit in a 4-byte numerical value (hexadecimal).
For details on how to represent units, see "CiA 303-2:2012,
CANopen recommendation - Part 2: Representation of SI units andprefixes".
Write the default value of the entry. The value to be written as thedefault value needs to follow DataType set for the entry. However, if
it follows DataType, a value that is outside the range set by
MinValue and MaxValue can be written.
Write the minimum value of the entry. The value to be written as theminimum value needs to follow DataType set for the entry. If theminimum value to be set is equal to the minimum value determinedby DataType, this can be omitted.
Write the maximum value of the entry. The value to be written as
the maximum value needs to follow DataType set for the entry. If
the maximum value to be set is equal to the maximum value
determined by DataType, this can be omitted.
Write the name of the entry. Write the name of the object when thevalue of SubIndex is "0x00" and write the name of the entry using
an arbitrary string when the value of SubIndex is other than "0x00".
Use of a comma (,) and double-quotation mark (") is prohibited.

Required
Required

Required

Required

Required

Required

Required

Optional

Optional

Optional

Optional

Required

BAP-C2008ENG-001-K
1-483

No.

Item Name

13.

LabelName

14.

Comment

CLPA

Required/
Optional

Description Details
Write a string using up to 32 characters for the label name of theentry. The characters that are not permitted are shown in"Characters Not Permitted in LABEL Item" of Table 4-13. Write aentry label name so that it does not duplicate another one.
Write entry descriptions and precautions on use using an arbitrary
string.

Optional
Optional

BAP-C2008ENG-001-K
1-484

9.

Additional specifications for CSP+ Specifications Version 1.1 or later
Conventions added in version 1.1 or later are shown here.
If using the following description, then CSP+ specification version (See Section 5.1.1.3 (6)) must be
described in a version that supports those descriptions.

9.1

Additional specifications for CSP+ Specifications Version 1.1
If CSP+ specification version is written in 1.0, the following conventions cannot be described.
(1) Consecutive execution of multiple methods or messages using reserved word SEQ
Consecutive execution of multiple methods or messages using reserved word SEQ cannot be
described in version 1.0. Specifications relating to this convention are mainly written in thefollowing places.
4.3.1.32. RELATED_MESSAGE conventions
4.3.1.33. RELATED_METHOD conventions
4.3.1.42. TARGET conventions
Consecutive execution of multiple methods or messages using reserved word PRE can be
described in version 1.0.

9.2

Additional specifications for CSP+ Specifications Version 2.0
If CSP+ specification version is written in 1.1 or earlier, description of the following conventions andspecifications cannot be performed.
(1) Conventions of expression by CONDITION parts
Conventions using CONDITION parts to change values of parameter items (RANGE, MIN_INC,
ENG_UNIT, ACCESS) according to values of other parameter cannot be used in version 1.1 or
earlier. For details, refer to the following.
4.3.1.7. CONDITIONx conventions
4.3.1.8. CONDITIONXVARIABLE conventions
4.3.1.41. RESULTx conventions
5.4.9. CONDITION parts(2) Conventions for max value and min value of RANGE items by reference to values
Conventions that reference values of other parameters as max value or min value of RANGE
items cannot be described in version 1.1 or earlier. For details, refer to the following.
4.3.1.26 RANGE conventions (8)(3) Description specifications for the safety communication function support unit
Conventions relating to the safety communication function support unit of the CC-Link IE Field
Network cannot be described in version 1.1 or earlier. For details, refer to the following.
5.3.1.3 COMM_IF_INFO parts description(31) SafetyProtocolVersion element description - (35) SupportSafetyCommService element
item description
5.5.5 Parts and elements showing parameters for safety communication function support
5.5.6 MESSAGE specifications for parameter writing of safety communication function support(4) Description specifications for the Ethernet connection unit
Descriptions relating to the Ethernet connection unit cannot be described in version 1.1 or earlier.
For details, refer to the following.
5.3.1.3 COMM_IF_INFO parts description(36) SupportIPAddressSize element item description - (48) SupportFlg_ReadStatus2 element
item description
5.5.7 Conventions of parameters which can read and write using parameter IDs

CLPA

BAP-C2008ENG-001-K
1-485

9.3

Additional specifications for CSP+ specifications Version 2.1
If CSP+ specification version is written in 2.0 or earlier, description of the following conventions andspecifications cannot be performed.
(1) Description specifications for the CC-Link IE Field Network Basic connection unit
Conventions relating to the CC-Link IE Field Network Basic connection unit cannot be describedin version 2.0 or earlier. For details, refer to the following.
4.2.7 CSP+ file structure of Ethernet connection unit
5.3.1.3 Description details of COMM_IF_INFO part
 Convention of the COMM_IF_INFO part when the communication interface is Ethernet(49) DevModel element description
to (52) EthernetCommFunction element item description(2) Description specifications for acquiring energy management information
Conventions for acquiring energy management information cannot be described in version 2.0 or
earlier. For details, refer to the following.
5.5.8 Parts and elements related to the acquisition of energy management information(3) Description specifications for acquiring status
Conventions for acquiring the status code and displaying detailed information of the Ethernet
connection unit cannot be described in version 2.0 or earlier. For details, refer to the following.
5.5.9 Convention for acquiring status codes

9.4

Additional specifications for CSP+ specifications Version 2.2
If CSP+ specification version is written in 2.1 or earlier, description of the following conventions andspecifications cannot be performed.
(1) Description specifications for acquiring maintenance information
Conventions for acquiring maintenance information cannot be described in version 2.1 or earlier.
For details, refer to the following.
4.3.1.21. MESSAGE_TYPE conventions
Addition of the type value "MAINTENANCE" and the detailed operating specifications of"MONITOR"
4.3.1.22. METHOD_TYPE conventions
Addition of the type value "MAINTENANCE" and the detailed operating specifications of"MONITOR"
4.3.1.32. RELATED_MESSAGE conventions
Addition of the keyword "POST"
4.3.1.33. RELATED_METHOD conventions
Addition of the keyword "POST"

CLPA

BAP-C2008ENG-001-K
1-486

9.5

Additional specifications for CSP+ Specifications Version 3.0
If CSP+ specification version is written in 2.2 or earlier, description of the following conventions andspecifications cannot be performed.
For a network connection device other than CC-Link IE TSN, use the CSP+ specifications with version
2.2 or earlier.
(1) Description specifications related to CC-Link IE TSN connection unit
• Description specifications for the CC-Link IE TSN connection unit
Conventions relating to the CC-Link IE TSN connection unit and CC-Link IE TSN safety
communication function support unit cannot be described in version 2.2 or earlier. For details, referto the following.
4.1.1 CSP+ file name4.1.2 Data configuration with compression management
4.2.8 CSP+ file structure of the CC-Link IE TSN connection unit
4.3.1.3 ASSIGN conventions
4.3.1.6 COMMENT conventions
4.3.1.21 MESSAGE_TYPE conventions
4.3.1.31 RELATED_ELE conventions
5.2.1 DEVICE_INFO part5.3.1.1 Overview
5.3.1.3 Description of COMM_IF_INFO part(53) Item description of StationMode element to (106) Item description of R_General_Addresselement
5.5.1 Elements related to system area
5.5.10.1 Parts and elements related to error related information
5.5.10.2 Convention related to MESSAGE for slave station parameter automatic setting
8 Description Specifications of Object Dictionary File
• Description specifications related to CC-Link IE TSN safety communication support unit
4.2.9 In the case of the CC-Link IE TSN safety communication function support unit
5.3.1.3 Description of COMM_IF_INFO part
(107) Item description of SafetyProtocolVersion element to (118) Item description of
R_Safe_Address element
5.5.10.3 Parts and elements indicating parameters for safety communication function
5.5.10.4 MESSAGE specifications for writing the safety communication function parameter

CLPA

BAP-C2008ENG-001-K
1-487

9.6

Additional specifications for CSP+ Specifications Version 4.0
If CSP+ specification version is written in 3.0 or earlier, description of the following conventions andspecifications cannot be performed.
(1) Description specifications related to CC-Link IE TSN connection unit
• Description specifications for the main module and extension module
Conventions relating to the main module and extension module cannot be described in version 3.0
or earlier. For details, refer to the following.
4.2.10 CSP+ file structure of the main module and extension modules over CC-Link IE TSN
5.5.10.5 Parts and elements related to the main module and extension modules

9.7

Additional specifications for CSP+ Specifications Version 4.1
If CSP+ specification version is written in 4.0 or earlier, description of the following conventions andspecifications cannot be performed.
(1) Description specifications related to CC-Link IE TSN connection unit
• Description specifications for the integrated main/extension module unit
Conventions relating to the integrated main/extension module unit cannot be described in version
4.0 or earlier. For details, refer to the following.
4.2.11 CSP+ file structure of the integrated main/extension module unit over CC-Link IE TSN
5.5.10.6 Parts and elements related to the integrated main/extension module unit

9.8

Additional specifications for CSP+ Specifications Version 4.2
If CSP+ specification version is written in 4.1 or earlier, description of the following conventions andspecifications cannot be performed.
(1) Description specifications related to CC-Link IE TSN connection unit
Of the elements described in the COMM_IF_INFO part, description of the
SupportFlg_IPAddressSet element and the SupportFlg_NodeIndication element cannot be
performed. For details, refer to the following.
5.3.1.3 Description of COMM_IF_INFO part(76) Item description of SupportFlg_IPAddressSet element and (77) Item description of
SupportFlg_NodeIndication element

9.9

Additional specifications for CSP+ Specifications Version 4.3
If CSP+ specification version is written in 4.2 or earlier, description of the following conventions andspecifications cannot be performed.
(1) Description specifications related to CC-Link IE TSN connection unit
Of the elements described in the COMM_IF_INFO part, description of theConnectionPortCableType element and the ConnectionPortNum element cannot be performed.
For details, refer to the following.
5.3.1.3 Description of COMM_IF_INFO part(61) Item description of ConnectionPortCableType element and (62) Item description ofConnectionPortNum element

CLPA

BAP-C2008ENG-001-K
1-488

10. Related Specification Documents
[1]
[2]
[3]
[4]
[5]
[6]
[7]

CC-Link Specification (Overview, Protocol) BAP-C2001-001
CC-Link IE CC-Link Field Network Specification (Physical Layer and Data Link Layer) BAP-C2005-002
CC-Link IE CC-Link Field Network Specification (Application Layer Service) BAP-C2005-003
CC-Link IE CC-Link Field Network Specification (Application Layer Protocol) BAP-C2005-004
CC-Link IE CC-Link Field Network Specification (Communication Profile) BAP-C2005-005
CC-Link IE CC-Link Field Network Specification (Device Profile)BAP-C2005-007
CC-Link IE Safety Communication Function Specification (Application Layer Service and Protocol) BAPC2007ENG-002[8] CC-Link IE Safety Communication Function Specification (Communication profile) BAP-C2007ENG-003[9] SLMP (Seamless Message Protocol) Specification (Overview) BAP-C2006ENG-001[10] SLMP (Seamless Message Protocol) Specification (Protocol) BAP-C2006ENG-003[11] CC-Link IE Field Network Basic Specification BAP-C2010ENG-004[12] CC-Link IE TSN Specifications (Overview) BAP-C2011ENG-001[13] CC-Link IE TSN Specifications (Application Layer Protocol) BAP-C2011ENG-004[14] CC-Link IE Safety Communication Function Specification (Overview) BAP-C2007ENG-001

CLPA

BAP-C2008ENG-001-K
1-489

CC-Link Family System Profile
Specification

CSP+ Ver.1.0

Prepared in October, 2023