Anybus AB6714 User guide

Brand: Anybus

Model: AB6714

Type: User guide

This manual is also suitable for

Anybus® CompactCom™ 40 - CC-Link IE TSN

NETWORK GUIDE

SCM-1202-212

Version 1.2

Publicaon date 2023-02-03

ENGLISH

Important User Informaon

Disclaimer

The informaon in this document is for informaonal purposes only. Please inform HMS Networks of any

inaccuracies or omissions found in this document. HMS Networks disclaims any responsibility or liability for

any errors that may appear in this document.

HMS Networks reserves the right to modify its products in line with its policy of connuous product

development. The informaon in this document shall therefore not be construed as a commitment on the

part of HMS Networks and is subject to change without noce. HMS Networks makes no commitment to

update or keep current the informaon in this document.

The data, examples and illustraons found in this document are included for illustrave purposes and

are only intended to help improve understanding of the funconality and handling of the product. In

view of the wide range of possible applicaons of the product, and because of the many variables and

requirements associated with any parcular implementaon, HMS Networks cannot assume responsibility

or liability for actual use based on the data, examples or illustraons included in this document nor for

any damages incurred during installaon of the product. Those responsible for the use of the product

must acquire sucient knowledge in order to ensure that the product is used correctly in their specic

applicaon and that the applicaon meets all performance and safety requirements including any applicable

laws, regulaons, codes and standards. Further, HMS Networks will under no circumstances assume liability

or responsibility for any problems that may arise as a result from the use of undocumented features or

funconal side eects found outside the documented scope of the product. The eects caused by any direct

or indirect use of such aspects of the product are undened and may include e.g. compability issues and

stability issues.

Contact Informaon

Postal address:

Box 4126

300 04 Halmstad, Sweden

E-Mail: inf[email protected]

Table of Contents

1. Preface .................................................................................................................................. 1

1.1. About this document ........................................................................................................ 1

1.2. Related Documents ........................................................................................................... 1

1.3. Document History ............................................................................................................ 1

1.4. Document Convenons ..................................................................................................... 2

1.5. Terminology .................................................................................................................... 3

1.6. Trademark Informaon ...................................................................................................... 3

2. About the Anybus Compact 40 CC-Link IE TSN .............................................................................. 4

2.1. General .......................................................................................................................... 4

2.2. Features ......................................................................................................................... 4

3. Basic Operaon ....................................................................................................................... 5

3.1. General Informaon ......................................................................................................... 5

3.1.1. Soware Requirements .............................................................................................. 5

3.2. Data Exchange ................................................................................................................. 5

3.2.1. Bit Area vs. Word Area ............................................................................................... 5

3.3. Network Identy .............................................................................................................. 6

3.4. Communicaon Sengs .................................................................................................... 6

4. CSP+ File Customizaon ............................................................................................................ 7

5. CC-Link IE TSN Implementaon Details ....................................................................................... 9

5.1. Process Data Mapping ....................................................................................................... 9

5.1.1. Default CC-Link Buer Memory Map ............................................................................ 9

5.1.2. Mapping ................................................................................................................. 9

5.2. Diagnoscs ..................................................................................................................... 12

6. Anybus State Machine ............................................................................................................. 13

7. SNMP Agent .......................................................................................................................... 14

7.1. General ......................................................................................................................... 14

7.2. Management Informaon (MIB) ......................................................................................... 14

7.2.1. Detailed Device Informaon ...................................................................................... 14

7.2.2. PTP Stascs ........................................................................................................... 16

7.2.3. CIET Stascs .......................................................................................................... 17

8. Anybus Module Objects .......................................................................................................... 18

8.1. Anybus Object (01h) ........................................................................................................ 19

8.1.1. Command Details: Reset ........................................................................................... 20

8.2. Diagnosc Object (02h) .................................................................................................... 21

8.3. Network Object (03h) ....................................................................................................... 22

8.4. Network Conguraon Object (04h) ................................................................................... 23

8.4.1. Command Details: Reset ........................................................................................... 27

9. Host Applicaon Objects ......................................................................................................... 28

9.1. General Informaon ........................................................................................................ 28

9.2. CC-Link IE TSN Host Object (E1h) ........................................................................................ 29

Appendix A. Categorizaon of Funconality ................................................................................... 30

1. Basic ................................................................................................................................ 30

2. Extended .......................................................................................................................... 30

Anybus® CompactCom™ 40 - CC-Link IE TSN

SCM-1202-212 Version 1.2

Appendix B. Implementaon Details ............................................................................................. 31

1. Applicaon Watchdog Timeout Handling ................................................................................ 31

Appendix C. Cercaon Informaon ........................................................................................... 32

1. Model Type ....................................................................................................................... 32

Appendix D. Technical Specicaon .............................................................................................. 33

1. Front View ........................................................................................................................ 33

1.1. Status LEDs ............................................................................................................... 33

1.2. Link LEDs .................................................................................................................. 33

2. Funconal Earth (FE) Requirements ....................................................................................... 34

2.1. Cables, shielding connecons ....................................................................................... 34

3. Power Supply .................................................................................................................... 34

3.1. Supply Voltage ........................................................................................................... 34

3.2. Power Consumpon ................................................................................................... 34

4. Environmental Specicaon ................................................................................................. 34

5. EMC Compliance ................................................................................................................ 35

Appendix E. Timing & Performance ............................................................................................... 36

1. General Informaon ........................................................................................................... 36

2. Internal Timing .................................................................................................................. 36

2.1. Startup Delay ............................................................................................................. 36

2.2. NW_INIT Handling ...................................................................................................... 36

2.3. Anybus Read Process Data Delay ................................................................................... 37

2.4. Anybus Write Process Data Delay .................................................................................. 38

2.5. Event Based WrMsg Busy Time ..................................................................................... 38

Appendix F. Licensing Informaon ................................................................................................ 39

Anybus® CompactCom™ 40 - CC-Link IE TSN

SCM-1202-212 Version 1.2

1. Preface

1.1. About this document

This document is intended to provide a good understanding of the funconality oered by the Anybus

CompactCom 40 CC-Link IE TSN. The document describes the features that are specic to Anybus CompactCom

40 CC-Link IE TSN. For general informaon regarding Anybus CompactCom 40, consult the Anybus CompactCom

40 design guides.

The reader of this document is expected to be familiar with high level soware design and communicaon

systems in general. The informaon in this network guide should normally be sucient to implement a design.

However if advanced CC-Link IE TSN specic funconality is to be used, in-depth knowledge of CC-Link IE TSN

networking internals and/or informaon from the ocial CC-Link IE TSN specicaons may be required. In such

cases, the persons responsible for the implementaon of this product should either obtain the CC-Link IE TSN

specicaon to gain sucient knowledge or limit their implementaon in such a way that this is not necessary.

For addional related documentaon and le downloads, please visit the support website at www.anybus.com/

support.

1.2. Related Documents

Document Author Document ID

Anybus CompactCom 40 Soware 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 Applicaon Implementaon Guide HMS HMSI-27-334

CC-Link IE TSN Conformance Test Specicaons Remote Staon Version (Twisted Pair Cable) CLPA BAP-C0401ENG

CC-Link IE TSN Specicaon (Overview) CLPA BAP-C2011ENG

Control & Communicaon System Prole Specicaon CLPA BAP-C2008ENG

1.3. Document History

Version Date Descripon

1.0 2022-11-30 First release

1.1 2023-01-02 Added chapter SNMP Agent

Added chapter Timing & Performance

1.2 2023-02-03 Added CIET Stascs

Minor updates

Preface Anybus® CompactCom™ 40 - CC-Link IE TSN

SCM-1202-212 Version 1.2 Page 1 of 42

1.4. Document Convenons

Lists

Numbered lists indicate tasks that should be carried out in sequence:

1. First do this

2. Then do this

Bulleted lists are used for:

• Tasks that can be carried out in any order

• Itemized informaon

User Interacon Elements

User interacon elements (buons etc.) are indicated with bold text.

Program Code and Scripts

Program code and script examples

Cross-References and Links

Cross-reference within this document: Document Convenons (page 2)

External link (URL): www.anybus.com

Safety Symbols

DANGER

Instrucons that must be followed to avoid an imminently hazardous situaon which, if not avoided,

will result in death or serious injury.

WARNING

Instrucons that must be followed to avoid a potenal hazardous situaon that, if not avoided, could

result in death or serious injury.

CAUTION

Instrucon that must be followed to avoid a potenal hazardous situaon that, if not avoided, could

result in minor or moderate injury.

IMPORTANT

Instrucon that must be followed to avoid a risk of reduced funconality and/or damage to the

equipment, or to avoid a network security risk.

Anybus® CompactCom™ 40 - CC-Link IE TSN Document Convenons

Page 2 of 42 SCM-1202-212 Version 1.2

Informaon Symbols

NOTE

Addional informaon which may facilitate installaon and/or operaon.

TIP

Helpful advice and suggesons.

1.5. Terminology

• The terms “Anybus” or “module” refers to the Anybus CompactCom module.

• The terms “host” or “host applicaon” refer to the device that hosts the Anybus.

• Hexadecimal values are wrien in the format NNNNh or 0xNNNN, where NNNN is the hexadecimal value.

• A byte always consists of 8 bits.

• The terms “basic” and “extended” are used to classify objects, instances and aributes.

1.6. Trademark Informaon

Anybus® is a registered trademark of HMS Industrial Networks.

All other trademarks are the property of their respecve holders.

Terminology Anybus® CompactCom™ 40 - CC-Link IE TSN

SCM-1202-212 Version 1.2 Page 3 of 42

2. About the Anybus Compact 40 CC-Link IE TSN

2.1. General

The Anybus CompactCom 40 CC-Link IE TSN communicaon module provides instant CC-Link IE TSN slave

funconality via the patented Anybus CompactCom host interface. Any device that supports this standard can

take advantage of the features oered by the module, allowing seamless network integraon regardless of

network type.

This product conforms to all aspects of the host interface dened in the Anybus CompactCom 40 Hardware-

and Soware Design Guides, making it fully interchangeable with any other device following that specicaon.

Generally, no addional network related soware support is needed, however in order to take advantage of

advanced network specic funconality, a certain degree of dedicated soware support may be necessary.

2.2. Features

• CC-Link IE TSN class B remote staon

• Sample conguraon le (CSP+) provided by HMS Industrial Networks (requires adaptaons)

• Possibility to customize Vendor Code, Model Code, Vendor Name, Model Type/Device Type, Model Name and

Version via applicaon interface

• Max. read process data: 1420 bytes

• Max. write process data: 1420 bytes

• Max. process data (read + write, in bytes): 2840 bytes

Please note that Anybus CompactCom 40 modular device funconalies are not supported in Anybus

CompactCom 40 CC-Link IE TSN.

Anybus® CompactCom™ 40 - CC-Link IE TSN About the Anybus Compact 40 CC-Link IE TSN

Page 4 of 42 SCM-1202-212 Version 1.2

3. Basic Operaon

3.1. General Informaon

IMPORTANT

Currently the suggested Cyclic Transmission Time in GX Works is insucient. In order for the Anybus

CompactCom module to funcon correctly the Cyclic Transmission Time needs to be extended

by a minimum of 13 μs when using 1 Gb/s communicaon, and 125 μs when using 100 Mb/s

communicaon.

3.1.1. Soware Requirements

No addional network support code needs to be wrien in order to support the Anybus CompactCom 40 CC-Link

IE TSN, however due to the nature of the CC-Link IE TSN networking system, certain restricons must be taken

into account:

• ADIs must be mapped as Process Data, in accordance with the Anybus CompactCom 40 CC-Link IE TSN

mapping scheme, in order to be correctly represented on the network.

• ADI Names, types and similar aributes cannot be accessed from the network.

• One diagnosc instance can be created by the host applicaon during normal operaon. One addional (2nd)

instance may be created in event of a major fault.

For in depth informaon regarding the Anybus CompactCom soware interface, consult the Anybus

CompactCom 40 Soware Design Guide.

3.2. Data Exchange

3.2.1. Bit Area vs. Word Area

On CC-Link IE TSN, 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.

Direcon Bit Area Points (hex) Word Area Points (dec)

Slave —> Master 0-11360 points, e.g. RX00 .... RX2C5F 0-710 points, e.g. RWr0... RWr709

Master —> Slave 0-11360 points, e.g.RY00 .... RY2C5F 0-710 points, e.g. RWw0... RWw709

Due to restricons in the module, the maximum total amount of I/O data in each direcon is 1420 bytes.

NOTE

Bit data will be allocated to the Bit Area unl the rst word is mapped. Any bit data mapped aer

this will be allocated to the Word Area.

Basic Operaon Anybus® CompactCom™ 40 - CC-Link IE TSN

SCM-1202-212 Version 1.2 Page 5 of 42

3.3. Network Identy

By default, the module uses the following identy sengs:

Vendor ID: 0212h (HMS Industrial Networks)

Device Type: 007Fh (Generic Device)

Product Code: 00000003h (CompactCom 40 CIET)

Product Name: "CompactCom 40 CIET"

NOTE

In the CC-Link IE TSN Host Object, Product Code and Product Name is represented by Model Code

and Model Name respecvely.

Oponally, it is possible to customize the identy of the module by implemenng the corresponding instance

aributes in the CC-Link IE TSN Host Object. See CC-Link IE TSN Host Object (E1h) (page 29).

IMPORTANT

In order to pass conformance tesng certain values must be changed. For more informaon, see

CC-Link IE TSN Conformance Test Specicaons Remote Staon Version (Twisted Pair Cable).

3.4. Communicaon Sengs

Network related communicaon sengs are grouped in the Network Conguraon Object (04h), and includes:

IP Sengs These sengs must be set properly in order for the module to be able to parcipate on the network.

NOTE

The module's IP address must match the IP address in the conguraon tool. It is not possible for the

conguraon tool to set the IP address of the module.

Physical Link

Sengs

By default, the module uses auto negoaon to establish the physical link sengs, however it is possible to force a specic

seng if necessary.

See also...

•Network Conguraon Object (04h) (page 23)

Anybus® CompactCom™ 40 - CC-Link IE TSN Network Identy

Page 6 of 42 SCM-1202-212 Version 1.2

4. CSP+ File Customizaon

Each device on CC-Link can be associated with a CC-Link Family System Prole (CSP+) le, which holds a

descripon of the device and its funcons.

HMS Industrial Networks supplies a generic CSP+ le which can serve as a basis for new implementaons.

A tool for modifying the le, as well as guidelines for creang CSP+ les, is available at the CLPA web page

(www.cc-link.org, membership is required). The entries in the le that shall be changed are listed in the following

secons.

File Informaon

The following entries shall be changed in the File Secon of the CSP+ File.

Entry Descripon

ModDate Date when the last modicaon of CSP+ le was done.

ModTime Time when the last modicaon of CSP+ le was done.

Device Informaon

The following entries shall be changed in the Device Secon of the CSP+ File.

Entry Descripon Notes

Vendor Name The vendor name. If the vendor name in CC-Link IE TSN Host Object

(instance 1, aribute 2) is implemented this entry shall

match the sengs in the CC-Link IE TSN Host Object.

Vendor Code The vendor code assigned by CLPA. If the vendor code in CC-Link IE TSN Host Object

(instance 1, aribute 1) is implemented this label shall

match the sengs in the CC-Link IE TSN Host Object.

Device Model The device model name (managed by each vendor). If the device model name in the CC-Link IE TSN Host

Object (instance 1, aribute 5) is implemented this label

shall match the sengs in the CC-Link IE TSN Host

Object.

Device Type ID The ID that indicates the device type of the host. The IDs

are managed by CLPA.

If the device type ID in the CC-Link IE TSN Host Object

(instance 1, aribute 6) is implemented this label shall

match the sengs in the CC-Link IE TSN Host Object.

Version The device version. If the version in the CC-Link IE TSN Host Object (instance

1, aribute 7) is implemented this label shall match the

sengs in the CC-Link IE TSN Host Object.

CSP+ File Customizaon Anybus® CompactCom™ 40 - CC-Link IE TSN

SCM-1202-212 Version 1.2 Page 7 of 42

CommIf Informaon

The following entries shall be changed in the CommIf Secon of the CSP+ File.

Label Descripon Notes

Vendor Name The vendor name. See Vendor Name in Device Informaon (page 7).

Vendor Code The vendor code assigned by CLPA. See Vendor Code in Device Informaon (page 7).

Version The device version. See Version in Device Informaon (page 7).

Model Code The model code. If the model code in the CC-Link IE TSN Host Object

(instance 1, aribute 3) is implemented this label shall

match the sengs in the CC-Link IE TSN Host Object.

Dev Model The device model name (managed by each vendor). See Device Model in Device Informaon (page 7).

S B Default Size The default size of the send bit data (RX) in number of

bits.

This value shall match the total amount of bits in the

send bit area mapped in the host applicaon.

S W Default Size The default size of the send word data (RWr) in number

of words.

This value shall match the total amount of words in the

send word area mapped in the host applicaon.

R B Default Size The default size of the receive bit data (RY) in number of

bits.

This value shall match the total amount of bits in the

receive bit area mapped in the host applicaon.

R W Default Size The default size of the receive word data (RWw) in

number of words.

This value shall match the total amount of words in the

receive word area mapped in the host applicaon.

S B Max Size The maximum size of the send bit data (RX) in number of

bits.

This value shall match the value of S B Default SIze.

S W Max Size The maximum size of the send word data (RWr) in

number of words.

This value shall match the value of S W Default SIze.

R B Max Size The maximum size of the receive bit data (RY) in the

number of bits.

This value shall match the value of R B Default SIze.

R W Max Size The maximum size of the receive word data (RWw) in

the number of words.

This value shall match the value of R W Default SIze.

S B Address The start address used for send bit data (RX)

communicaon.

This value shall be set to 0.

S W Address The start address used for send word data (RWr)

communicaon.

This value shall match the amount of data in S B Default

SIze, but be wrien in bytes.

R B Address The start address used for receive bit data (RY)

communicaon.

This value shall be set to 0.

R W Address The start address used for receive word data (RWw)

communicaon.

This value shall match the amount of data in R B Default

SIze, but be wrien in bytes.

Under the COMM_IF secon, there are two parts that can be added, COMM_IF_INPUT and COMM_IF_OUTPUT.

The COMM_IF_INPUT part describes informaon related to the input informaon in the communicaon

interface. The COMM_IF_OUTPUT part describes informaon related to the output informaon in the

communicaon interface. For more informaon, see Control & Communicaon System Prole Specicaon.

Block Informaon

The following entries shall be changed in the Block Secon of the CSP+ File.

Label Descripon Notes

Vendor Name The vendor name. See Vendor Name in Device Informaon (page 7).

Vendor Code The vendor code assigned by CLPA. See Vendor Code in Device Informaon (page 7).

Version The device version. See Version in Device Informaon (page 7).

If COMM_IF_INPUT and/or COMM_IF_OUTPUT are added under the COMM_IF secon, BLOCK INPUT part

and/or BLOCK_OUTPUT part shall be added under BLOCK secon. For more informaon, see Control &

Communicaon System Prole Specicaon.

Anybus® CompactCom™ 40 - CC-Link IE TSN CommIf Informaon

Page 8 of 42 SCM-1202-212 Version 1.2

5. CC-Link IE TSN Implementaon Details

5.1. Process Data Mapping

5.1.1. Default CC-Link Buer Memory Map

The default prole for Anybus CompactCom 40 CC-Link IE TSN is “Generic Device”. The applicaon realizes the

implementaon, including the mapping of ADIs to the corresponding memory. This makes it possible to comply

with any prole buer data layout.

5.1.2. Mapping

This scheme is used when the host applicaon 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 consecuve locaons in the respecve areas in the same order as the mapping commands

are issued.

• All bit data types (BITSx, BITx, PADx or BOOL1) are mapped to the CC-Link IE TSN bit area as long as no

previous mapping command with a non bit data type has been received. Aer that, for any following mapping

command with a bit data type, the data will be mapped in the CC-Link IE TSN word area, see the examples on

the following pages.

• 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.

• If no byte alignment is used during mapping, the Anybus CompactCom returns an error message.

• The Map_ADI_Write_Ext_Area and Map_ADI_Read_Ext_Area commands are in bit granularity and can be used

for all data types.

• Not all elements in an ARRAY or STRUCT ADI need to be mapped.

See example in secon Mapping Example with Extended Mapping Command (page 11).

•Implementaon of CC-Link IE TSN proles might require that the applicaon uses some padding in the

mapping to get the memory buer layout as the prole requires.

• The Anybus CompactCom does not perform any implicit padding of the process data, except for at the very

end of the process data map up to byte alignment, since the process data needs to be of byte size.

• Bit padding is done either through available ADI elements of PADx type, or through the use of ADI 0, which is

assumed to be an array with 255 elements of type PAD1.

• Word padding can be achieved by using dummy ADIs of the required padding size.

• A faulty mapping will generate a NAK (negave acknowledgment).

CC-Link IE TSN Implementaon Details Anybus® CompactCom™ 40 - CC-Link IE TSN

SCM-1202-212 Version 1.2 Page 9 of 42

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 resulng RY mapping in the bit area:

Point Contents (Command[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 resulng RWw mapping in the word area:

Contents (Command[Element]:(word/byte/bit)

Point Contents (LSB) Contents (MSB)

RWw #0 C[0]:(byte) D[0]:(byte)

RWw #1 E[0]:(LSB) E[0]:(MSB)

RWw #2 F[0]:(byte) F[1]:(byte)

RWw #3 G[0]:(7,6,5,4,3,2,1,0) G[0]:(15,14,13,12,11,10,9,8)

RWw #4 G[0]:(23,22,21,20,19,18,17,16) G[0]:(31,30,29,28,27,26,25,24)

RWw #5 H[0]:(7,6,5,4,3,2,1,0) H[0]:(15,14,13,12,11,10,9,8)

RWw #6 I[0]:(LSW:LSB) I[0]:(LSW:MSB)

RWw #7 I[0]:(MSW:LSB) I[0]:(MSW:MSB)

Anybus® CompactCom™ 40 - CC-Link IE TSN Process Data Mapping

Page 10 of 42 SCM-1202-212 Version 1.2

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 dened by the

sengs of “Index rst element” and “Nbr of consecuve elements”

Command # mapping

items

ADI # Total Nbr of

elements

Index rst

element

Nbr of consecuve

elements

Nbr of type

descriptors

Data type speciers

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 resulng RX mapping in the bit area.

Point Command[mapping Item]:ADI[IndexElement]:(bit/byte/word)

RX #7...

A[1]:10[0]:(6) A[1]:10[0]:(5) A[1]:10[0]:(4) A[1]:10[0]:(3) A[1]:10[0]:(2) A[1]:10[0]:(1) A[1]:10[0]:(0) A[0]:3[0]:(0)

RX #15...

A[1]:10[0]:

(14)

A[1]:10[0]:

(13)

A[1]:10[0]:

(12)

A[1]:10[0]:

(11)

A[1]:10[0]:

(10)

A[1]:10[0]:(9) A[1]:10[0]:(8) A[1]:10[0]:(7)

RX #23...

B[0]:20[1]:(0) B[0]:20[1]:(0) B[0]:20[0]:(5) B[0]:20[0]:(4) B[0]:20[0]:(3) B[0]:20[0]:(2) B[0]:20[0]:(1) B[0]:20[0]:(0)

RX #31...

B[0]:20[3]:(7) B[0]:20[3]:(6) B[0]:20[3]:(5) B[0]:20[3]:(4) B[0]:20[3]:(3) B[0]:20[3]:(2) B[0]:20[3]:(1) B[0]:20[3]:(0)

This is the resulng 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]:(7,6,5,4,3,2,1,0) C[0]:7[2]:(15,14,13,12,11,10,9,8)

RWr #2 C[0]:7[3]:(byte) -

Process Data Mapping Anybus® CompactCom™ 40 - CC-Link IE TSN

SCM-1202-212 Version 1.2 Page 11 of 42

5.2. Diagnoscs

The module supports one diagnosc entry during normal condions, plus an addional second entry in case of a

major unrecoverable event.

Latching event funconality is not supported.

Severity of Event Result on the network

Minor recoverable Triggers a minor applicaon error in the StsWa. status informaon.

Also triggers an applicaon error in the Status informaon in the Detailed Device Informaon MIB accessible via SNMP.Minor unrecoverable

Major recoverable Triggers a major applicaon error in the StsWa. status informaon.

Also triggers an applicaon error in the Status informaon in the Detailed Device Informaon MIB accessible via SNMP.

Major unrecoverable Triggers the module to go to EXCEPTION state and shut down the CC-Link IE TSN network.

It will sll be possible to see that an applicaon error has occured in the Status informaon in the Detailed Device

Informaon MIB accessible via SNMP.

a.StsW is the cyclic status data sent from the module to the master each network cycle.

Anybus AB6714 User guide

Brand: Anybus

Model: AB6714

Type: User guide

This manual is also suitable for

Download PDF

report

Anybus AB6714 User guide

This manual is also suitable for

Anybus AB6714 User guide

Related papers

Other documents