Anybus CompactCom 40 Modbus-TCP Installation and maintenance instructions

Anybus
®CompactCom™40
CC-Link IE Field
NETWORK GUIDE
HMSI-27-338 1.2 ENGLISH

Important User Information
Liability
Every care has been taken in the preparation of this document. Please inform HMS Industrial Networks AB of any
inaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS Industrial
Networks AB, reserve the right to modify our products in line with our policy of continuous product development.
The information in this document is subject to change without notice and should not be considered as a commit-
ment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errors that
may appear in this document.
There are many applications of this product. Those responsible for the use of this device must ensure that all the
necessary steps have been taken to verify that the applications meet all performance and safety requirements in-
cluding any applicable laws, regulations, codes, and standards.
HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that
may arise as a result from the use of undocumented features, timing, or functional side effects found outside the
documented scope of this product. The effects caused by any direct or indirect use of such aspects of the product
are undefined, and may include e.g. compatibility issues and stability issues.
The examples and illustrations in this document are included solely for illustrative purposes. Because of the many
variables and requirements associated with any particular implementation, HMS Industrial Networks AB cannot as-
sume responsibility for actual use based on these examples and illustrations.
Intellectual Property Rights
HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product de-
scribed in this document. These intellectual property rights may include patents and pending patent applications in
the USA and other countries.
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2
Table of Contents Page
1 Preface ............................................................................................................................... 3
1.1 About this document ......................................................................................................3
1.2 Related Documents .......................................................................................................3
1.3 Document History ..........................................................................................................3
1.4 Document Conventions ..................................................................................................4
1.5 Terminology...................................................................................................................4
1.6 Trademark Information ...................................................................................................4
2 About the Anybus CompactCom 40 CC-Link IE Field ........................................... 6
2.1 General.........................................................................................................................6
2.2 Features .......................................................................................................................6
3 Basic Operation............................................................................................................... 7
3.1 General Information .......................................................................................................7
3.2 Data Exchange..............................................................................................................8
4 CC-Link IE Field Implementation Details ................................................................ 13
4.1 Process Data Mapping .................................................................................................13
4.2 Diagnostics .................................................................................................................16
4.3 SLMP (Seamless Message Protocol) ............................................................................17
5 Anybus Module Objects .............................................................................................. 23
5.1 General Information .....................................................................................................23
5.2 Anybus Object (01h) ....................................................................................................24
5.3 Diagnostic Object (02h) ................................................................................................25
5.4 Network Object (03h) ...................................................................................................26
5.5 Network Configuration Object (04h)...............................................................................27
5.6 Anybus File System Interface Object (0Ah) ....................................................................30
5.7 Network CC-Link IE Field Object (12h) ..........................................................................31
6 Host Application Objects ............................................................................................ 33
6.1 General Information .....................................................................................................33
6.2 CC-Link IE Field Network Host Object (E6h) ..................................................................34
6.3 Ethernet Object (F9h)...................................................................................................39
A Categorization of Functionality ................................................................................. 41
A.1 Basic...........................................................................................................................41
A.2 Extended.....................................................................................................................41

Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2
Table of Contents
B Implementation Details................................................................................................ 42
B.1 SUP-Bit Definition ........................................................................................................42
B.2 Anybus State Machine .................................................................................................42
B.3 Application Watchdog Timeout Handling........................................................................42
C Certification Information ............................................................................................. 43
C.1 Basics.........................................................................................................................43
C.2 Model Type..................................................................................................................43
C.3 Other ..........................................................................................................................43
C.4 CSP+ File Customization..............................................................................................44
D Technical Specification ............................................................................................... 46
D.1 Front View...................................................................................................................46
D.2 Functional Earth (FE) Requirements.............................................................................. 47
D.3 Power Supply ..............................................................................................................47
D.4 Environmental Specification..........................................................................................48
D.5 EMC Compliance.........................................................................................................48
D.6 1000BASE-T Compliance.............................................................................................48
E Timing & Performance ................................................................................................. 49
E.1 General Information .....................................................................................................49
E.2 Internal Timing.............................................................................................................49

Preface 3 (52)
1 Preface
1.1 About this document
This document is intended to provide a good understanding of the functionality offered by the
Anybus CompactCom 40 CC-Link IE Field. The document describes the features that are spe-
cific to Anybus CompactCom 40 CC-Link IE Field. For general information regarding Anybus
CompactCom 40, consult the Anybus CompactCom 40 design guides.
The reader of this document is expected to be familiar with high level software design and com-
munication systems in general. The information in this network guide should normally be suffi-
cient to implement a design. However if advanced CC-Link IE Field specific functionality is to be
used, in-depth knowledge of CC-Link IE Field networking internals and/or information from the
official CC-Link IE Field specifications may be required. In such cases, the persons responsible
for the implementation of this product should either obtain the CC-Link IE Field specification to
gain sufficient knowledge or limit their implementation in such a way that this is not necessary.
For additional related documentation and file downloads, please visit the support website at
www.anybus.com/support.
1.2 Related Documents
Document Author Document ID
Anybus CompactCom 40 Software Design Guide HMS HMSI-216-125
Anybus CompactCom M40 Hardware Design Guide HMS HMSI-216-126
Anybus CompactCom B40 Design Guide HMS HMSI-27-230
Anybus CompactCom Host Application Implementation
Guide
HMS HMSI-27-334
CC-Link Specification (Device Profile) CLPA BAP-C2005-007 (E)
CC-Link Conformance Test Specifications CLPA BAP-C0401-037-D)
CC-Link Family System Profile (CSP+) Creation Guidelines CLPA BCN89000-0756-A
Control & Communication System Profile Specification
(CSP+)
CLPA BAP-C2008-001
SLMP (Seamless Message Protocol) specification
(Overview)
CLPA BAP-C2006ENG-001-
D
SLMP (Seamless Message Protocol) Conformance Test
Specification (for Server)
CLPA BAP-C0401-040-E
1.3 Document History
Version Date Description
1.0 2016-08-30 First version
1.1 2017-04-10 Support for SLMP added
1.2 2017-07-11 SLMP updated
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

Preface 4 (52)
1.4 Document Conventions
Ordered lists are used for instructions that must be carried out in sequence:
1. First do this
2. Then do this
Unordered (bulleted) lists are used for:
• Itemized information
• Instructions that can be carried out in any order
...and for action-result type instructions:
► This action...
➨leads to this result
Bold typeface indicates interactive parts such as connectors and switches on the hardware, or
menus and buttons in a graphical user interface.
Monospaced text is used to indicate program code and other
kinds of data input/output such as configuration scripts.
This is a cross-reference within this document: Document Conventions, p. 4
This is an external link (URL): www.hms-networks.com
This is additional information which may facilitate installation and/or operation.
This instruction must be followed to avoid a risk of reduced functionality and/or
damage to the equipment, or to avoid a network security risk.
Caution
This instruction must be followed to avoid a risk of personal injury.
WARNING
This instruction must be followed to avoid a risk of death or serious injury.
1.5 Terminology
• The terms “Anybus” or “module” refers to the Anybus CompactCom module.
• The terms “host” or “host application” refer to the device that hosts the Anybus.
• Hexadecimal values are written in the format NNNNh or 0xNNNN, where NNNN is the hex-
adecimal value.
• A byte always consists of 8 bits.
• The terms “basic” and “extended” are used to classify objects, instances and attributes.
1.6 Trademark Information
Anybus®is a registered trademark of HMS Industrial Networks AB.
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

Preface 5 (52)
All other trademarks are the property of their respective holders.
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

About the Anybus CompactCom 40 CC-Link IE Field 6 (52)
2 About the Anybus CompactCom 40 CC-Link IE
Field
2.1 General
The Anybus CompactCom 40 CC-Link IE Field communication module provides instant CC-
Link IE Field slave functionality via the patented Anybus CompactCom host interface. Any de-
vice that supports this standard can take advantage of the features offered by the module, al-
lowing seamless network integration regardless of network type.
This product conforms to all aspects of the host interface defined in the Anybus CompactCom
40 Hardware- and Software Design Guides, making it fully interchangeable with any other de-
vice following that specification. Generally, no additional network related software support is
needed, however in order to take advantage of advanced network specific functionality, a cer-
tain degree of dedicated software support may be necessary.
2.2 Features
• CC-Link IE Field Network intelligent device station
• Sample configuration file (CSP+) provided by HMS Industrial Networks AB (requires
adaptations).
• Possibility to customize Vendor Code, Model Code, Vendor Name, Model Type/Device
Type, Model Name and Version via application interface
• Fixed 1 Gbit/s Baud Rate
• Network Number and Station Number configuration via application interface
• Seamless Message Protocol (SLMP) server supported
• Galvanically isolated bus
• I/O: up to 1536 bytes in total
• Transient server functionality supported.
Please note that Anybus CompactCom 40 modular device and sync functionalities are not sup-
ported in Anybus CompactCom 40 CC-Link IE Field
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

Basic Operation 7 (52)
3 Basic Operation
3.1 General Information
3.1.1 Software Requirements
No additional network support code needs to be written in order to support the Anybus Com-
pactCom 40 CC-Link IE Field, however due to the nature of the CC-Link IE Field networking
system, certain restrictions must be taken into account:
• ADIs must be mapped as Process Data, in accordance with the Anybus CompactCom 40
CC-Link IE Field mapping scheme, in order to be correctly represented on the network.
• ADI Names, types and similar attributes cannot be accessed from the network.
• No support for network reset requests.
• One diagnostic instance can be created by the host application during normal operation.
One additional (2nd) instance many be created in event of a major fault.
For in depth information regarding the Anybus CompactCom software interface, consult the
Anybus CompactCom 40 Software Design Guide.
3.1.2 CC-Link Family System Profile (CSP+) File
Each device on CC-Link can be associated with a CC-Link Family System Profile (CSP+) file,
which holds a description of the device and its functions.
HMS Industrial Networks supplies a generic CSP+ file which can serve as a basis for new im-
plementations. A tool for modifying the file is available at the CLPA web page (www.cc-link.org,
membership is required).
If the product is not going to be certified there is no need for a CSP+ file. If the product is going
to be certified, the generic CSP+ file has to be adapted to the application in order to pass certifi-
cation tests. For more information see Certification Information, p. 43.
3.1.3 Communication Settings
Network related communication settings, which can accessed by the end user, are grouped in
the Network Configuration Object (04h).
In the case of CC-Link IE Field, this includes:
Station Number On CC-Link IE Field, each device on the network must be assigned a unique
Station Number.
Network Number The network can be segmented into several parts, each with a unique network
number, that is used for addressing.
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

Basic Operation 8 (52)
3.2 Data Exchange
3.2.1 Bit Area vs. Word Area
On CC-Link IE Field, data is divided into two categories as follows:
Bit Area Data is accessed on a bit-by-bit basis. Data is commonly referred to as RX #nn
(Slave->Master) and RY #nn (Master->Slave) where nn represents an
addressable point (i.e. a single bit) in the Bit Area.
Word Area Data is accessed as 16-bit words. Data is commonly referred to as RWr #nn
(Slave->Master) and RWw #nn (Master->Slave) where nn represents an
addressable point (i.e. a word) in the Word Area.
Direction Bit Area Points (hex) Word Area Points (dec)
Slave —> Master RX00 .... RX7FF 768 points, e.g. RWr0... RWr767
Master —> Slave RY00 .... RY7FF 768 points, e.g. RWw0... RWw767
Due to restrictions in the module, the maximum total amount of IO/Data in each direction is
1536 bytes
3.2.2 Acyclic Data Exchange
Transient/acyclic data exchange in server mode is supported by the Anybus CompactCom 40
CC-Link IE Field.
• Statistic Information acquisition
• Detailed Node Information acquisition
• Memory Read
• Memory Write
The Anybus CompactCom 40 CC-Link IE Field supports ADI #1 to 65535 and all ADI data types.
The data is handled in 16–bit granularity.
Transient Server Memory Read and Memory Write
To access ADI data from the CC-Link IE Field network there are two dedicated functions that
can be used by a CC-Link IE Field towards an intelligent device station:
Function Description Attribute Code Access Code
RIRD Reading Data from
the target station
05h - Word access
(external informa-
tion). Other values
reserved.
Reserved, set to 0h.
RIWT Writing Data in target
stations
The module will only handle access on the complete ADI data value. The length given in the
function “Number of write/read points” (S1 + 4) and (S + 4) is verified by the module on a byte
granularity against ADI data size. The minimum returned value size is also in a byte granularity
and the returned value is in a Little Endian word format.
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

Basic Operation 9 (52)
Translation of RIWT
The RIWT function will be converted by the module to a Set_Attribute command to the Applica-
tion Data object (FEh), Attribute # 5 (value).
RIWT data
(master
function)
Description Value Data
Type
ABCC Cmd
field
ABCC Resp
field
Jn Own network No. (1 to 239) 16-bit NA NA
Un Start I/O number of master
(Not relevant for the module)
0 to FE 16-bit NA NA
(S1+0) Completion status (see error
code below)
0: Normal, no error.
-16-bit NA No Error/Error
Response (Error
bit and data[0])
(S1+1) Target station number 1-120 16-bit NA NA
(S1+2) Access code (hi byte)/Attrib-
ute code (low byte)
The attribute code should al-
ways be set to 05h by the
user to indicate word access
(external information.
0x00xx 16-bit Always gen-
erate a Set_
Attribute
Set_Attribute
(S1+3) Device number (start
number)
1-65535 16-bit ADI number
(Instance)
CmdExt[0],
Attribute = 5
(value)
ADI number
(Instance)
CmdExt[0], At-
tribute = 5
(value)
(S1+4) Number of write points.
(must be in same granularity
as the data type, see access
code in previous section)
1-480 16-bit Data field
size (bytes)
and in Data
[0-n]
NA
S2 Start device of the own sta-
tion (in PLC) where data to
be written is stored (Source)
-16-bit NA NA
D2 Device of the own station
turned ON for 1 scan upon
completion of the instruction
(D)+1 is turned ON as well
when the instruction fails.
-Bit NA NA
Data Transfer from Network to Application
When writing to an ADI with an odd (2*n+1) number of bytes, the number of points in the re-
quest should be n + 1, i.e. one extra byte should be padded in. The copying of data from the
transient frame to the ADI is transparent. This means that because the transient write/read
memory data is little endian on the network, the padded byte should be the high byte of the (n +
1):th word in the write request data.
Example with 3 byte ADI
Data layout in master
1122h 3344h
Data on network
22 11 44 33
Resulting ADI data
22 11 44
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

Basic Operation 10 (52)
Translation of RIRD
The RIRD function will be converted by the module to a Get_Attribute command to the Applica-
tion Data object FEh Attribute #5 (value).
RIRD data
(master
function)
Description Value Data
Type
ABCC Cmd
field
ABCC Resp
field
Jn Own network No. (1 to 239) 16-bit NA NA
Un Start I/O number of master
(Not relevant for the module)
0 to FE 16-bit NA NA
(S+0) Completion status (see error
code below)
0: Normal, no error.
-16-bit NA No Error/Error
Response (Error
bit and data[0])
(S+1) Target station number 1-120 16-bit NA NA
(S+2) Access code (hi byte)/attrib-
ute code (low byte)
The attribute code should al-
ways be set t 05h by the user
to indicate word access (ex-
ternal information.
0x00xx 16-bit Always gen-
erate a Get_
Attribute
NA
(S+3) Device number (start
number)
1-65535 16-bit ADI number
(Instance)
CmdExt[0],
Attribute = 5
(value)
NA
(S+4) Number of read points
(must be in same granularity
as the data type, see access
code in previous section)
1-480 16-bit NA Validated against
Data field size
(bytes) in
response.
(S+4) * 2 = Data
field size.
D1 Start device of the own sta-
tion (in PLC) where read data
is stored (Destination)
-16-bit NA NA
D2 Device of the own station
turned ON for 1 scan upon
completion of the instruction
(D2)+1 is turned ON as well
when the instruction fails.
-Bit NA NA
Data Transfer from Application to Network
When reading from an ADI with an odd number of bytes, the high byte of the (n + 1):th word in
the received read request data is padded and should be ignored on the master side.
Example
RIRD (transient2 read memory)
Data layout in ADI
11 22 33
Data on network
11 22 33 XX
Resulting data in the master
2211h XX33h
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

Basic Operation 11 (52)
Error Codes/Completion Status
In case of error, the following error codes are transferred to CC-Link IE Field network in the
Transient response frames. The error code is returned according to the following table
Item name Bit # CC-Link IE Field
Description
Detail Usage
Error Code/
Completion
Status
15-12 Vendor definition Free error range to assign for
vendor.
0xExxx is used as error
base value.
11-8 Error location Grouped by each network hi-
erarchy: Data Link layer, Ap-
plication layer.
0000b = Application
generated
0001b = Module
generated
0010b = Internal applica-
tion generated
0011b-1111b = reserved
7 Error critically 0 = Warning, 1 = Major Set to 0 for all errors.
6-0 Error code Vendor specific. Error codes, see tables
below, giving error code
ranges and error code
translations.
Error Code Range Error codes
E0xxh Application generated error codes
E1xxh Module generated error codes
E2xxh Internal application error codes
Error Code Translation
The low byte of the error code is translated as given in this table.
Number Meaning Description CFN Error
code
CFN Description
00h Reserved -0000h No error
01h Reserved -XX01h -
02h Invalid message
format
Command and error bit set XX02h Invalid Message Set
03h Unsupported object Object not registered XX03h Unsupported object
04h Unsupported
instance
The requested instance
doesn’t exist
XX04h Application data
unsupported
05h Unsupported
command
The target doesn’t support
the command
XX05h Unsupported
command
06h Invalid CmdExt[0] Invalid value of CmdExt[0]or
invalid combination of
CmdExt[0] and CmdExt[1]
XX06h Invalid CmdExt[0]
07h Invalid CmdExt[1] Invalid value of CmdExt[1] XX07h Invalid CmdExt[0]
08h Attribute not set-
able
The requested attribute is not
set-able
XX08h Application data not
set-able
09h Attribute not get-
able
The requested attribute is not
get-able
XX09h Application data not
get-able
0Ah Too much data Too much data in message
data field
XX0Ah Too much data
0Bh Not enough data Not enough data in message
data field
XX0Bh Not enough data
0Ch Out of range The data is out of range
Use this code only when
code 11h or 12h cannot be
used.
XX0Ch Out of range
0Dh Invalid state The command is not sup-
ported in the current state
XX0Dh Application in invalid
state
0Eh Out of resources The target object cannot exe-
cute the command due to lim-
ited resources
XX0Eh Out of resources
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

Basic Operation 12 (52)
Number Meaning Description CFN Error
code
CFN Description
0Fh Segmentation
failure
Invalid handling of the seg-
mentation protocol
XX0Fh Segmentation failure
10h Segmentation buffer
overflow
Too much data received for
the segmentation buffer
XX10h Segmentation buffer
overflow
11h Value too high Written data value is too high
(extension to 0Ch (Out of
range))
XX11h Value too high
12h Value too low Written data value is too low
(extension to 0Ch (Out of
range))
XX12h Value too low
13h Attribute controlled
from another
channel.
Used to NAK writes to “read
process data” mapped
attributes.
XX13h Application data con-
trolled from another
channel
14h Message channel
too small
The message read/write area
in use by the host application
does not support a message
channel with large enough
data field to fit the response
data.
XX14h Application message
channel too small
15h General error An error not matching any of
the other existing error codes
has occurred.
XX15h Application general
error
21h Illegal Access code Illegal value XX21h Illegal Access code
22h Illegal Attribute code Illegal value XX22h Illegal Attribute code
23h Not addressed to
node
The module received a re-
quest that was not addressed
to itself (wrong node number/
network number).
XX23h Not addressed to
node
24h Unsupported
service
The module received an un-
supported transient2 request,
i.e. other than Read memory/
Write memory.
XX24h Unsupported service
25h Wrong quantity The module only supports
batch access, not random
access.
XX25h Wrong quantity
26h Data size too big The number of points times
the data type size exceeds
the maximum transient2 data
size (480 words)
XX26h Data size too big
7Fh Object specific error
(Not possible to rep-
resent due to 7 bits
toward CFN)
The object returned an object
specific error code
XX7Fh Object specific error
Timeout Considerations
If a timeout is detected for a RIRD or RIWT function, please consult the CC-Link IE Field net-
work master manual for timeout settings and retry factors.
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

CC-Link IE Field Implementation Details 13 (52)
4 CC-Link IE Field Implementation Details
4.1 Process Data Mapping
4.1.1 Default CC-Link Buffer Memory Map
The default profile for Anybus CompactCom 40 CC-Link IE Field is “Generic Device”. The appli-
cation realizes the implementation, including the mapping of ADIs to the corresponding memory.
This makes it possible to comply with any profile buffer data layout.
If no mapping is done by the application, the Anybus CompactCom 40 CC-Link IE Field auto-
matically generates the minimum CC-Link IE Field network configuration (16 bit points/4 word
points), but with no connection/mapping towards the application. The module will be available
on the network and can be used for parameter data exchange.
4.1.2 Mapping
This scheme is used when the host application uses the mapping commands:
• Map_ADI_Write_Area and Map_ADI_Write_Ext_Area map data to the RX (bit) and RWr
(word) areas.
• Map_ADI_Read_Area and Map_ADI_Read_Ext_Area map data from the RY (bit) and
RWw (word) areas.
• ADIs are mapped to consecutive locations in the respective areas in the same order as the
mapping commands are issued.
• All bit data types (BITSx, BITx or PADx) are mapped to the CC-Link IE Field bit area as long
as no previous mapping command with a non bit data type has been received. After that,
for any following mapping command with a bit data type, the data will be mapped in the
CC-Link IE Field word area, see the examples on the following pages.
• By default no padding is performed. Any padding or alignment demand to reach the profile
layout is the responsibility of the application.
• The Map_ADI_Write_Area and Map_ADI_Read_Area commands are in byte granularity
and can only be used for data types of 8, 16, 32 or 64 bit length.
• Byte alignment during mapping will be enforced when using this command.
• The use of e.g. the data type BIT3 will generate a NAK (negative acknowledgment) mes-
sage in answer to the request.
• The host application may need to perform padding, e.g. if word alignment is needed.
See example in section .
• The Map_ADI_Write_Ext_Area and Map_ADI_Read_Ext_Area commands are in bit granu-
larity and can be used for all data types.
• Bit data will be mapped consecutively in the bit area as long as BITSx, BITx or PADx data
types are used.
• Once a command with any other data type has been received, all data will be mapped in
the word area. This may disrupt the byte alignment, that is a condition. It is the responsibil-
ity of the host application to perform all padding to avoid error messages due to unaligned
data mapping.
• Not all elements in an ARRAY or STRUCT ADI need to be mapped.
See example in section .
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

CC-Link IE Field Implementation Details 14 (52)
• ADIs with data type structure are put in the CC-Link IE Field word area as a complete
chunk/blob, unless covered by any of the rules above.
Implementation of CC-Link IE Field profiles might require that the application uses some pad-
ding in the mapping to get the memory buffer layout as the profile requires. This can be done by
using ADI # 0 or PADx for padding in the map directed to the CC-Link IE Field bit areas and us-
ing ADI# xx (dummy byte) for padding in the CC-Link IE Field word areas. These areas should
be marked as reserved in the buffer memory description (towards the CC-Link IE Field network).
A faulty mapping will generate a NAK (negative acknowledgment).
Mapping Example with Standard Command
This is an example of nine (A-I) Read mapping commands using the Map_ADI_Read_Area
command.
Command Data Type No. of Elements
A BITS8 3
B BITS16 1
C BOOL 1
D UINT8 1
E UINT16 1
F BOOL 2
G BITS32 1
H BITS16 1
I UINT32 1
This is the resulting RY mapping in the bit area:
Point Contents (Command number[Element:bit])
RY #7... 0 A[0:7] A[0:6] A[0:5] A[0:4] A[0:3] A[0:2] A[0:1] A[0:0]
RY #15... 8 A[1:7] A[1:6] A[1:5] A[1:4] A[1:3] A[1:2] A[1:1] A[1:0]
RY #23... 16 A[2:7] A[2:6] A[2:5] A[2:4] A[2:3] A[2:2] A[2:1] A[2:0]
RY #31... 24 B[0:7] B[0:6] B[0:5] B[0:4] B[0:3] B[0:2] B[0:1] B[0:0]
RY #39... 32 B[0:15] B[0:14] B[0:13] B[0:12] B[0:11] B[0:10] B[0:9] B[0:8]
This is the resulting RWw mapping in the word area:
Contents (Command number[bit/byte/word])
Point Contents (LSB) Contents (MSB)
RWw #0 C D
RWw #1 E[0] E[1]
RWw #2 F[0] F[1]
RWw #3 G[LSW] G[LSW]
RWw #4 G[MSW] G[MSW]
RWw #5 H[7], H[6] , H[5], H[4], H[3], H[2], H[1] , H[0] H[15], H[14], H[13], H[12], H[11], H[10], H[9], H[8]
RWw #6 I[LSW] I[LSW]
RWw #7 I[MSW] I[MSW]
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

CC-Link IE Field Implementation Details 15 (52)
Mapping Example with Extended Mapping Command
This is an example of three (A-C) Write mapping commands using the Map_ADI_Write_Ext_
Area command. Please note that not all elements in an ADI need to be mapped. The elements
to be mapped, are defined by the settings of “Index first element” and “Nbr of consecutive
elements”
Com-
mand
# map-
ping
items
ADI # Total Nbr
of
elements
Index first
elementa
Nbr of con-
secutive
elements
Nbr of
type de-
scriptors
Data type
specifiers
A 2 3 1 0 1 1 65(BIT1)
-10 1 0 1 1 47(PAD15)
B 1 20 5 0 3 5 70(BIT6)34
(PAD2)9
(BITS8)36
(PAD4)68
(BIT4)
C 1 7 4 1 3 4 9(BITS8)5
(UINT16)10
(BITS16)0
(BOOL)
This is the resulting RX mapping in the bit area.
Point Command[mapping Item]:ADI[IndexElement]:(bit/byte/word)
RX #7... 0 A[1]:10
[0]:(b6)
A[1]:10
[0]:(b5)
A[1]:10
[0]:(b4)
A[1]:10
[0]:(b3)
A[1]:10
[0]:(b2)
A[1]:10
[0]:(b1)
A[1]:10
[0]:(b0)
A[0]:3[0]:
(b0)
RX #15... 8 A[1]:10
[0]:(b14)
A[1]:10
[0]:(b13)
A[1]:10
[0]:(b12)
A[1]:10
[0]:(b11)
A[1]:10
[0]:(b10)
A[1]:10
[0]:(b9)
A[1]:10
[0]:(b8)
A[1]:10
[0]:(b7)
RX #23... 16 B[0]:20
[1]:(b1)
B[0]:20
[1]:(b0)
B[0]:20
[0]:(b5)
B[0]:20
[0]:(b4)
B[0]:20
[0]:(b3)
B[0]:20
[0]:(b2)
B[0]:20
[0]:(b1)
B[0]:20
[0]:(b0)
RX #31... 24 B[0]:20
[2]:(b7)
B[0]:20
[2]:(b6)
B[0]:20
[2]:(b5)
B[0]:20
[2]:(b4)
B[0]:20
[2]:(b3)
B[0]:20
[2]:(b2)
B[0]:20
[2]:(b1)
B[0]:20
[2]:(b0)
This is the resulting RWr mapping in the word area.
Command[mapping Item]:ADI[IndexElement]:(bit/byte/word)
Point LSB MSB
RWr #0 C[0]:7[1]:(LSB) C[0]:7[1]:(MSB)
RWr #1 C[0]:7[2]:(b7]
C[0]:7[2]:(b6)
C[0]:7[2]:(b5)
C[0]:7[2]:(b4)
C[0]:7[2]:(b3)
C[0]:7[2]:(b2)
C[0]:7[2]:(b1)
C[0]:7[2]:(b0)
C[0]:7[2]:(b15)
C[0]:7[2]:(b14)
C[0]:7[2]:(b13)
C[0]:7[2]:(b12)
C[0]:7[2]:(b11)
C[0]:7[2]:(b10)
C[0]:7[2]:(b9)
C[0]:7[2]:(b8)
RWr #2 C[0]:7[3]:(byte) -
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

CC-Link IE Field Implementation Details 16 (52)
4.2 Diagnostics
The module supports one diagnostic entry during normal conditions, plus an additional second
entry in case of a major unrecoverable event.
Information on the actual cause and the severity of a diagnostic event is forwarded to the
network.
Latching event functionality is not supported.
Diagnostic object command from application Event displayed in master (Diagnostics)
Create,
CmdExt[0], Bit 4-6: Severity
0x00 – Minor, recoverable
0x10 – Minor, unrecoverable
“Continue error in progress”
0x20 – Major, recoverable “STOP PAUSE ERROR”
“Stop error in process”
0x30 – Major, unrecoverable
(EXCEPTION state)
“Baton pas error”
“Data link error”
Delete Deleted severity 0x00, 0x10:
“Continue error cancellation”
Delete severity 0x20:
“RUN or STEP RUN”
“Stop error cancellation”
Anybus®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

CC-Link IE Field Implementation Details 17 (52)
4.3 SLMP (Seamless Message Protocol)
SLMP is a feature of CC-Link IE Field that makes it possible to seamlessly connect field sys-
tems to information systems. If SLMP is implemented in a standard Ethernet device, the device
can be accessed and also exchange data across the network.
The Anybus CompactCom 40 CC-Link IE Field supports SLMP server functionality in the config-
urations shown in the figures below.
PC - SLMP Client
PLC
CC-Link IE Field
Network
Anybus CompactCom
Intelligent device
- SLMP Server
Fig. 1
PLC
- SLMP Client
CC-Link IE Field
Network
Anybus CompactCom
Intelligent device
- SLMP Server
Fig. 2
Anybus
®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2

CC-Link IE Field Implementation Details 18 (52)
SLMP is enabled by default in the device, but can be disabled by setting attribute #7 (Enable
SLMP) in the CC-Link IE Field Network Host Object (E6h). The Anybus CompactCom 40 CC-
Link IE Field supports a limited set of SLMP commands by default. If attribute #8 (Enable SLMP
forwarding) is enabled, the application can choose to handle SLMP requests, both implement-
ing the commands, supported by the Anybus CompactCom 40, and implementing additional
support for functions not supported by the device.
Fig. 3
Anybus
®CompactCom™40 CC-Link IE Field Network Guide HMSI-27-338 1.2