Renesas R-IN32 Series, R-IN32M4-CL2, R-IN32M3-EC, R-IN32M3-CL User Manual

Renesas Electronics

All information of mention is things at the time of this document publication, and Renesas

R-IN32 Series User’s Manual

)

・・・

Userʼs Manual

(CC-Link Remote dev ice stati on

R-IN32M3-EC R-IN32M3-CL R-IN32M4-CL2

Electronics may change the product or specifications that are listed in this document without a notice. Please confirm the latest information such as shown by website of Renesas

Document number: R18UZ0056EJ0102 Issue date: Dec. 28, 2018

www.renesas.com

Notice

1. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples. You are fully responsible for the incorporation of these circuits, software, and information in the design of your equipment. Renesas Electronics assumes no responsibility for any losses incurred by you or third parties arising from the use of these circuits, software, or information.

2. Renesas Electronics has used reasonable care in preparing the information included in this document, but Renesas Electronics does not warrant that such information is error free. Renesas Electronics assumes no liability whatsoev er for any damages incurred by you resulting from errors in or omissions from the information included herein.

3. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others.

4. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. Renesas Electronics assumes no responsibility for any losses incurred by you or third parties arising from such alteration, modification, copy or otherwise misappropriation of Renesas Electronics product.

5. Renesas Electronics products are classified according to the following two quality grades: "Standard" and "High Quality". The recommended applications for each Renesas Electronics product depends on the product's quality grade, as indicated below.

"Standard": Computers; office equipment; communications equipment; test and measurement equipment; audio

and visual equipment; home electronic appliances; machine tools; personal electronic equipment; and industrial robots etc.

"High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control systems; anti-disaster

systems; anti-crime systems; and safety equipment et c.

Renesas Electronics products are neither intended nor authorized for use in products or systems that may pose a direct threat to human life or bodily injury (artificial life support devices or systems, surgical implantations etc.), or may cause serious property damages (nuclear reactor control systems, milit ar y equip ment etc. ). Y ou must check the qua lity grade of each Renesas Electronics product before using it in a particular application. You may not use any Renesas Electronics product for any application for which it is not intended. Renesas Electronics shall not be in any way liable for any damages or losses incurred by you or third parties arising from the use of any Renesas Electronics product for which the product is not intended by Renesas Electro ni cs.

6. You should use the Renesas Electronics products described in this document within the range specified by Renesas Electronics, especially with respect to the maximum rating, operating supply voltage range, movement power voltage range, heat radiation characteristics, installation and other product characteristics. Renesas Electronics shall have no liability for malfunctions or damages arising out of the use of Renesas Electronics products beyond such specified ranges.

7. Although Renesas Electronics endeavors to improve the quality and reliability of its products, semiconductor products have specific characteristics such as the occurrence of failure at a certain rate and malfunctions under certain use conditions. Further, Renesas Electronics products are not subject to radiation resistance design. Please be sure to implement safety measures to guard them against the possibility of physical injury, and injury or damage caused by fire in the event of the failure of a Renesas Electronics product, such as safety design for hardware and software including but not limited to redundancy, fire control and malfunction prevention, appropriate treatment for aging degradation or any other appropriate measures. Because the evaluation of microcomputer software alone is very difficult, please evaluate the safety of the final products or systems manufactured by you.

8. Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility of each Renesas Electronics product. Please use Renesas Electronics products in compliance with all applicable laws and regulations that regulate the inclusion or use of controlled substances, including without limitation, the EU RoHS Directive. Renesas Electronics assumes no liability for damages or losses occurring as a result of your noncompliance with applicable laws and regulations.

9. Renesas Electronics products and technology may not be used for or incorporated into any products or systems whose manufacture, use, or sale is prohibited under any applicable domestic or foreign law s or regulations. You should not use Renesas Electronics products or technology described in this document for any purpose relating to military applications or use by the military, including but not limited to the development of weapons of mass destruction. When exporting the Renesas Electronics products or technology described in this document, you should comply with the applicable export control laws and regulations and follow the procedures required by such laws and regulations.

10. It is the responsibility of the buyer or distributor of Renesas Electronics products, who distributes, disposes of, or otherwise places the product with a third party, to notify such third party in advance of the contents and conditions set forth in this document, Renesas Electronics assumes no responsibility for any losses incurred by you or third parties as a result of unauthorized use of Renesas Electronics products.

11. This document may not be reproduced or duplicated in any form, in whole or in part, without prior written consent of Renesas Electronics.

12. Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this document or Renesas Electronics products, or if you have any other inquiries.

(Note 1) "Renesas Electronics" as used in this document means Renesas Electronics Corporation and also includes its

majority-owned subsidiaries.

(Note 2) "Renesas Electronics product(s)" means any product developed or manufactured by or for Renesas Electronics.

stable. When switching

Arm® and Cortex® are registered trademarks of Arm Limited (or its subsidiaries) in the EU and/or elsewhere.

Instructions for the use of product

In this section, the precautions are described for over whole of CMOS device. Please refer to this manual about individual precaution.

When there i s a mention unlike the text of this manual, a mention of the text takes first pr iority

1.1 Handling of Unused Pins

Handle unused pins in accord with the directions given under Handling of Unused Pins in the manual.

-The input pins of CMOS products are generally in the high-impedance state. In operation with an unused pin in the open-circuit state, extra electromagnetic noise is induced in the vicinity of LSI, associat ed shoo t-t hro ugh current flows internally, and malfunctions occur due to the false recognition of the pin state as an input signal become possible. Unused pins should be handled as described under Handling of Unused Pins in the manual.

2.Processing at Power-on The state of the product is undefined at the moment when power is supplied.

-The states of internal circuits in the LSI are indeterminate and the states of register settings and pins are undefined

at the moment when power is supplied. In a finished product where the reset signal is applied to the external reset pin, the states of pins are not guaranteed from the moment when power is supplied until the reset process is compl e ted. In a similar way, the states of pins in a product that is reset by an on-chip power-on reset function are not guaranteed from the moment when power is supplied until the power reaches the level at which resetting has been specified.

3.Prohibition of Access to Reserved Addresses Access to reserved addresses is prohibited.

-The reserved addresses are provided for the possible future expansion of functions. Do not access these

addresses; the correct operation of LSI is not guaranteed if they are accessed.

4.Clock Signals After applying a reset, only release the reset line after the operating clock signal has become the clock signal during program execution, wait until the target clock signal has stabiliz ed.

-When the clock signal is generated with an external resonator (or from an external oscillator) during a reset, ensure

that the reset line is only released after full stabilization of the clock signal. Moreover, when switching to a clock signal produced with an external resonator (or by an external oscillator) while program execution is in progress, wait until the target clock signal is stable.

・

・Ethernet is a registered trademark of Fuji Xerox Co., Ltd. ・IEEE is a registered trademark of the Institute of Electrical and Electronics Engineers Inc. ・CC-Link and CC-Link IE Field are registered trademarks of the CC-Link Partner Association (CLPA).

・Additionally all product names and service names in this document are a trademark or a registered trademark

which belongs to the respective owners.

within the body of the text, at the end of each section, and in the Usage Notes section.

point in this document.

document from our web site and r e fer to it.

Document Name

Document Number

R-IN32M3 series Datasheet

R18DS0008EJ****

R-IN32M3-EC User’s Manual

R18UZ0003EJ****

R-IN32M3-CL User’s Manual

R18UZ0005EJ****

R-IN32M3 series User’s Manual (Peripheral function)

R18UZ0007EJ****

R-IN32M3 Series Programming Manual (OS edition)

R18UZ0011EJ****

R-IN32M3 Series Programming Manual (Driver edition)

R18UZ0009EJ****

R-IN32M4-CL2 User’s Manual

R18UZ0032EJ****

R-IN32M4-CL2 User’s Manual (Peripheral Modules)

R18UZ0034EJ****

R-IN32M4-CL2 User’s Manual (Gigabit Ethernet PHY edition)

R18UZ0044EJ****

R-IN32M4-CL2 Programming Manual (Driver edition)

R18UZ0036EJ****

R-IN32M4-CL2 Programming Manual (OS edition)

R18UZ0040EJ****

R-IN32M4-CL2 User’s Manual (B oard des ign edit ion)

R18UZ0046EJ****

R-IN32 Series User’s Manual (CC-Link Remote device station edition)

This Manual

How to use this manual

This manual is intended for users who wish to understand the functions of “R-IN32 Series” CC-Link Remote device station for designing application of it. The functio n of CC-Link re mote device stations is represented as "CCS" in this document.

Particular attention should be paid to the precautionary notes when using the manual. These notes occur

The revision history summarizes the locations of revisions and additions. It does not list all revisions. Refer to the text of the manual for details. The mark "<R>" means the updated point in this revision. The mark "<R>" let users search for the updated

Literature

Literature may be preliminary versions. Note, however, that the following descriptions do not indicate "Preliminary". S ome documents on cores were created when they were planned or still under development. So, they may be directed to specific customers. Last four digits of document number (described as ****) indicate version information of each document. Please download the latest

The document related to R-IN32 Series

2. Notation of Numbers and Symbols

Weight in data notation: Left is high-order column, right is low-order column Active low notation: xxxZ (capital letter Z after pin name or signal name) or xxx_N (capital letter _N after pin name or signal name) or xxnx (pin name or signa l name contains small letter n) Note: explanation of (Note) in the text Caution: Item deserving extra attention Remark: Supplementary explanation to the text Numeric notation: Binary … xxxx , xxxxB or n’bxxxx (n bit s ) Decimal … xxxx Hexadecimal … xxxxH or n’hxxxx (n bits)

Prefixes representing powers of 2 (address space, memory capacity):

10

K (kilo)… 2 M (mega)… 2 G (giga)… 2

= 1024

20

= 10242

30

= 10243 Data Type: Double word … 32 bits Word … 16 bits Byte … 8 bits

Contents

1.

Introduction .................................................................................................................................................... 1

1.1 Related materials ................................................................................................................................................ 1

1.2 Generic Terms and Abbreviations ...................................................................................................................... 1

1.3 CC-Link Partner Association .............................................................................................................................. 1

1.4 Cyclic Data Capacity .......................................................................................................................................... 2

2. Function List .................................................................................................................................................. 3

3. Specified Parts and Recommended Parts .................................................................................................... 4

3.1 Recommended Parts ........................................................................................................................................... 4

4. R-IN32 Series Initialization ............................................................................................................................ 5

5. CC-Link Remote Device Station Pins ............................................................................................................ 6

6. Setting Details ............................................................................................................................................... 9

6.1 Setting the Number of Occupied Stations ........................................................................................................... 9

6.2 Setting the Station Number and Baud Rate ...................................................................................................... 10

6.3 Transmission Monitor Section Terminals (for LED) ........................................................................................ 11

7. Monitor Output of Reception Frame Information ......................................................................................... 13

8. Memory Map ................................................................................................................................................ 14

8.1 Memory Map List ............................................................................................................................................. 14

8.2 Memory Map Details ........................................................................................................................................ 18

8.2.1 Send Data Write Enable Information (CCS_MWRENL_RCEX) ........................................................... 18

8.2.2 Station Number Switch Information, Number of Occupied Stations Information and Baud Rate Switch

Information (CCS_M3STNO_BSW_KYOKU) ...................................................................................... 19

8.2.3 Error Information (CCS_M3ERR1_ERR2) ............................................................................................. 20

8.2.4 M → R Status Information (CCS_M3MRST1_ST2) .............................................................................. 21

8.2.5 RY Reception Buffer (CCS_M3MRRY00_0F) ....................................................................................... 23

8.2.6 RWwn Register (CCS_M3MRRWWn) ................................................................................................... 23

8.2.7 Send Data Write Complete Flag and Receive Data Read Request (CCS_M3SDOK_RDRQ) ................ 24

8.2.8 Vendor Code (CCS_M3VENDORCODE) .............................................................................................. 25

8.2.9 Model Code and Version (CCS_M3MODELCODE_VERSION) .......................................................... 25

Contents-1

8.2.10

SDLED Illumination Time Setting and Ti meout T ime Setting (CCS_M3SDLED_TOVER) ................. 26

8.2.11 Cyclic Communication (CCS_M3RMST1_ST2) .................................................................................... 28

8.2.12 RX Update Buffer (CCS_M3RMRXn0_nF) ........................................................................................... 29

8.2.13 RWr Regi st er (CCS_M3RM RWRn) ....................................................................................................... 29

8.2.14 HOLD/C LR Register (CCS_M3HOLDC LR) .......................................................................................... 30

9. Sample Flowchart for CC-Link Version 1 .................................................................................................... 31

9.1 Initial Setting .................................................................................................................................................... 31

9.2 Main Processing ................................................................................................................................................ 32

9.2.1 Synchronous Read Met hod / Async hronous Write Method ..................................................................... 32

9.2.2 Asynchronous Read Me thod / Asynchronous Wr ite Method .................................................................. 34

9.3 Reception and Transmission Processing ........................................................................................................... 35

9.3.1 Synchronous Read Met hod (Interrupt Processing) .................................................................................. 35

9.3.2 Asynchronous Read Me thod .................................................................................................................... 36

9.3.3 Asynchronous Write Me thod ................................................................................................................... 37

9.4 Timeout Time Setting C hange .......................................................................................................................... 38

9.4.1 Initial Setting Time → Normal Setting Time .......................................................................................... 38

9.4.2 Normal Setting Time → Initial Setting Time .......................................................................................... 39

10. Remote Device Station Common Specification........................................................................................... 40

10.1 Cyclic Transmission S ignals ............................................................................................................................. 40

10.1.1 Cyclic Transmission Signal Definitions .................................................................................................. 40

10.1.2 System Area Details................................................................................................................................. 41

10.2 Remote Register ................................................................................................................................................ 44

11. Overview of CC-Link Ver. 2 ......................................................................................................................... 45

11.1 Characteristics of CC-Link Ver. 2 .................................................................................................................... 46

11.1.1 Extended Cyclic ....................................................................................................................................... 46

11.1.2 Less Occupied Stations ............................................................................................................................ 47

11.2 Overview of Protocol ........................................................................................................................................ 48

11.2.1 Overview of Extended Cyclic Communication ....................................................................................... 48

11.2.2 Transmission of O wn S tatio n Informatio n ............................................................................................... 49

11.2.3 Extended Cyclic Header Information ...................................................................................................... 51

11.3 Relationship between SQ Value s and RX/RY, RW r/RWw .............................................................................. 55

12. Sample Flowchart for CC-Link Version 2 .................................................................................................... 56

12.1 List of Modules and Variables .......................................................................................................................... 56

12.2 Initial Setting INT_CCV20 ............................................................................................................................... 58

12.3 Transmission/Reception Processing ................................................................................................................. 59

Contents-2

12.3.1

Example Using an Interrupt (CCS_REFSTB Si gnal) .............................................................................. 59

12.3.2 Example of Polling .................................................................................................................................. 60

12.4 Transmission/Reception Processing Module (ICCV20) ................................................................................... 61

12.5 Application Work Area Transfer Processing Module CHK20DONE .............................................................. 65

13. Notes on Developing with CC-Link Version 2 ............................................................................................. 66

13.1 Hardware .......................................................................................................................................................... 66

13.2 Software (Firmware) ......................................................................................................................................... 67

13.3 Write Timing at Transmission .......................................................................................................................... 68

13.4 Handling CC-Link Version 2 Work Area ......................................................................................................... 70

14. Questions & Answers .................................................................................................................................. 71

14.1 Circuit De s ign in General ................................................................................................................................. 71

14.2 Software ............................................................................................................................................................ 73

14.3 Protocol and Others .......................................................................................................................................... 81

Contents-3

Contents of Figures

Figure 4.1

Figure 5.1 R-IN32M3 Series CC-Link Remote Device Station Peripheral Architecture ....................................... 7

Figure 5.2 R-IN32M4-CL2 CC-Link Remote Device Station Peripheral Architecture ......................................... 8

Figure 6.1 Condition of RUN light on .................................................................................................................. 11

Figure 9.1 Initial Processing ................................................................................................................................. 31

Figure 9.2 Synchronous Read Method / Asynchronous Write Method ................................................................ 33

Figure 9.3 Asynchronous Read Method / Asynchrono us Write Method .............................................................. 34

Figure 9.4 Synchronous Read Method ................................................................................................................. 35

Figure 9.5 Asynchronous Read Method ............................................................................................................... 36

Figure 9.6 Asynchronous Writ e Method .............................................................................................................. 37

Figure 9.7 Initial Setting Time → Normal Setting Time ...................................................................................... 38

Figure9.8 Normal Setting Time → Initial Setting Time ...................................................................................... 39

Figure 10.1 RXsB (Remote Ready) ........................................................................................................................ 41

Figure 10.2 RXs9/RYs9 (Initial Data Processing Reque st / Processing Complete Flag) ....................................... 41

Figure 10.3 RXs9/RYs9 (Initial Data Setting Complete / Setting Request Flag) ................................................... 42

Figure 10.4 When Both RXs8/RYs8 and RXs9/RYs9 are Implemented ............................................................... 42

Figure 10.5 RXsA/RYsA (Error Status / Reset Request Flag) ............................................................................... 43

Figure 11.1 With 2 Occupied Stations and Extended Cyclic 2 × Setting ............................................................ 48

Figure 11.2 Extended Cyclic Header Information .................................................................................................. 51

Figure 11.3 Details of SQ V a lue (M → R Data) .................................................................................................... 52

Figure 11.4 Details of SQ Value (R → M Data) .................................................................................................... 53

Figure 11.5 Details of SQ Value (Loopback) ......................................................................................................... 54

Figure 12.1 Initial Set ting INT_CCV20 ................................................................................................................. 58

Figure 12.2 Transmission/Reception Processing Using Interrupt (CCS_REFSTB Signal) ................................... 59

Figure 12.3 Transmission/Reception Using Polling ............................................................................................... 60

Figure 12.4 Transmission/Reception Processing Module (ICCV20) ..................................................................... 61

Figure 12.5 Transmission/Reception Processing Module ICCV20 (Continued 1) ................................................. 62

Figure 12.6 Transmission/Reception Processing Module ICCV20 (Continued 2) ................................................. 63

Figure 12.7 Transmission/Reception Processing Module ICCV20 (Continued 3) ................................................. 64

Figure 12.8 Application Work Area Transfer Processing Module CHK20DONE ................................................. 65

Figure 13.1 Link Scan Ti me and CCS_REFSTB Signal Change ........................................................................... 69

Figure 13.2 Example of 4x Setting ......................................................................................................................... 70

How to R-IN32 Series Initialization ..................................................................................................... 5

Contents-4

Contents of Tables

Table 1.1

Table 1.2 Generic Terms and Abbreviations ............................................................................................................ 1

Table 1.3 Version 1 Cyclic Data Capacity ................................................................................................................ 2

Table 1.4 Version 2 Cyclic Data Capacity ................................................................................................................ 2

Table 2.1 Functio n Li st ............................................................................................................................................. 3

Table 3.1 Recommended Parts <R>.......................................................................................................................... 4

Table 5.1 Correspondence between CC-Link Remote Device Station Pins and R-IN32M3 Series Pins <R> .......... 6

Table 5.2 Correspondence between CC-Link Remote Device Station Pins and R-IN32M4-CL2 Pi ns <R> ............ 8

Table 6.1 Occupied stations setting .......................................................................................................................... 9

Table 6.2 Setting the station number and baud rate ................................................................................................ 10

Table 6.3 Light ON/OFF/BLINK c onditions .......................................................................................................... 12

Table 7.1 Monitor output of reception frame information ...................................................................................... 13

Table 8.1 When the Number of Occupied Stations is Set to 1 ................................................................................ 14

Table 8.2 When the Number of Occupied Stations is Set to 2 ................................................................................ 15

Table 8.3 When the Number of Occupied Stations is Set to 3 ................................................................................ 16

Table 8.4 When the Number of Occupied Stations is Set to 4 ................................................................................ 17

Table 9.1 Normal Setting T ime (Set ting After First Reception Completion) ......................................................... 38

Table 9.2 Initial Setting Time (Setting after Timeout) ............................................................................................ 39

Table 10.1 Remote Registers ................................................................................................................................ 44

Table 11.1 Extended Cyclic .................................................................................................................................. 46

Table 11.2 Relationship between the number of occupied stations and extended cyclic setting in CC-Link

Table 11.3 Relationship between number of occupied stations and number of connected modules ..................... 47

Table 11.4 Version 1 and Version 2 No. of Occupied Stations / Amt. of Cyclic Data ......................................... 47

Table 11.5 Details of ST1 and ST2 in Version 2 .................................................................................................. 49

Table 11.6 Details of RV in Version 2 .................................................................................................................. 50

Table 11.7 Relationship between SQ Value s and RX/RY, RW r/RWw ................................................................ 55

Reference materials ................................................................................................................................... 1

Version 2 ............................................................................................................................................................ 46

Contents-5

Reference Name

Reference Number

"CC-Link Specification (Overview, Protocol)"

Reference code: BAP-05026

"CC-Link Specification (Installation Sp ecification)"

Reference code: BAP-05027

"CC-Link Specification (Profile)"

Reference code: BAP-05028

For document requests, c ontact:

CC-Link Partner Association (CLPA)

TEL:052-919-1588 / FAX: 052-916-8655

Email: info@cc-link.org

Generic Terms and Abbreviations

Description

Link Version 1.10, may

be stated simply "Version 1".

Ver.2

CC-Link Version 2 may be stated simply "Version 2".

Home page address: http://ww w.cc-link.org/

R18UZ0056EJ0102 R-IN32 Series CC-Link Remote device station Dec. 28, 2018

1. Introduction

This document is the specification for developing CC-Link remote device stations using the R-IN32 Series. The functio n of CC-Link remote device stations is r epresented as "CCS" in this document.

1.1 Related materials

The materials related to this product are indicated below. Refe r to Table 1.1, and request any materials by contacting the CC-Link Partner Association as necessary. Please see the "CC-Link Specification" publ i s hed by the C C-Link Partner Association for a detailed description of CC-Link.

Table 1.1 Reference materials

1.2 Generic Terms and Ab br eviations

Unless otherwise stated, this manual uses the terms and abbreviations below to describe the CC-Link remote device station funct io ns CC S .

Table 1.2 Generic Terms and Abbreviations

Ver.1 CC-Link Version 1, including CC-Link Version 1.00 and CC-

1.3 CC-Link Partner Association

The product developed based on this manual must pass a conformance test conducted by the CC-Link Partner Association. For details of the conformance te st, cont act the C C-Link Partner Association.

R18UZ0056EJ0102 Page 1 of 83 Dec. 28, 2018

No. of Occupied Stations

1 Occupied Station

2 Occupied Stations

3 Occupied Stations

4 Occupied Stations

RWr/RWw

4 words each

8 words each

12 words each

16 words each

Cyclic Setting

No. of Occupied Stations

1 Occupied Station

2 Occupied Stations

3 Occupied Stations

4 Occupied Stations

RWr/RWw

4 words each

8 words each

12 words each

16 words each

RWr/RWw

8 words each

16 words each

24 words each

32 words each

RWr/RWw

16 words each

32 words each

48 words each

64 words each

RWr/RWw

32 words each

64 words each

96 words each

128 words each

Remarks 1.

The latter 16 bits of remote I/O (RX/RY) are reserved by the system.

2.

The cyclic data capacity with an extended cyclic setting of data capacity of Version 1.

R-IN32 Series CC-Link Remote device station 1. Introduction

1.4 Cyclic Data Capacity

The data amount of up to 128 bits for RX/RY and 16 words for RWr/RWw can be handled using Version 1 cyclic by selecting the number of occupied stations (between one and four).

In addition, the data amount of up to 896 bits for RX/RY and 128 words for RWr/RWw can be handled by specifying the extended cyclic transmission setting in Version 2 .

(1) Version 1 Cyclic Data Capacity

Table 1.3 Version 1 Cyclic Data Capacity

Type

RX/RY

32 bits each

(2) Version 2 Cyclic Data Capacity

Table 1.4 Version 2 Cyclic Data Capacity

Extended

Single RX/RY

Double RX/RY

Quadruple RX/RY

Octuple RX/RY

Type

32 bits each

64 bits each

128 bits each

64 bits each

96 bits each

192 bits each

384 bits each

96 bits each

160 bits each

320 bits each

640 bits each

"single" is the same as the cyclic

128 bits each

224 bits each

448 bits each

896 bits each

R18UZ0056EJ0102 Page 2 of 83 Dec. 28, 2018

Name

Description

Amount of data:4 to 128 words, setting possible

after startup (normal setting time).

station.

function

once to the transmission buffer, thereby preventing send data separation.

prevention function

once to the RY and RWw areas, thereby preventing receive data separation.

status monitoring function

be monitored.

module status has returned to normal.

software setting. (See section 8, Memory Map)

Baud rate setting function

10M / 5M / 2.5M / 625k / 156kbps settings available

error detection function

be detected.

the error flag.

R-IN32 Series CC-Link Remote device station 2. Function List

2. Function List

Table 2.1 Function List

Setting the number of occupied stations

Setting timeout (transmission path switching) time

Fuse blown detection function When a device is equipped with a fuse, send the status of the fuse to the master

Send data separation prevention

Receive data separation

Programmable controller CPU

Network return function This function automatically connects to the data link a module that has been

Transmission status display function

Based on the terminal setting. For Version 1:No. of I/O points:32 to 128 bits Amount of data:4 to 16 words, setting possible For Version 2:No. of I/O points:32 to 896 bits

The timeout time is determined by the communication baud rate. Taking into consideration transmission inconsistencies at the time of network startup, two types of time settings are available: at software startup (initial setting time) and

The data to be sent is written to the RX and RWr areas and then transferred all at

The received data are stored in the reception buffer and then transferred all at

Run/stop and normal/abnormal statuses of the programmable controller CPU can

disconnected from the data link due to an event such as power OFF after the

The monitor terminal enables the LED display. Because an SDLED has a short lighting duration, adjustments can be made by

Baud rate/station number setting

Baud rate/station number change detection function

By referencing error flags, abnormal settings for baud rate and station number can

If the communication baud rate or the station num ber setting value is changed to a value that is different from the value at startup, it can be detected by referencing

R18UZ0056EJ0102 Page 3 of 83 Dec. 28, 2018

Product Name

Model Name

Manufacturer

Filter

MCT7050-A401

Sinka Japan Co., ltd.

RS485 transceiver

SN75ALS181NS

Texas Instruments Japan, Inc.

RD6.2Z

Renesas Electronics.

STZU6.2NT146

ROHM Co., Ltd.

Product Name

Model Name

Manufacturer

HCPL-7720-500E

HCPL-0720-500E

HCPL-2611-500E

HCPL-M611-500E

PS9117A

Renesas Electronics.

.

For CC-Link interface circuit recommended parts and model names, direct your inquiries to the CC-Link Partner Association.

2.

Specify option 060 when the insulation characteristics of VIORM = 630VPEAK are required.

3.

Specify option 060 when the insulation characteristics of VIORM = 560VPEAK are required.

R-IN32 Series CC-Link Remote device station 3. Specified Parts and Recommended Parts

3. Specified Parts and Recommended Parts

3.1 Recommended Parts

The following lists the parts recommended by the CC-Link P artner Association for use in the design of CC -Link interface circuits.

For detailed part specifications, direct your inquiries to the co rresponding manufacturer.

Table 3.1 Recommended Parts <R>

Note1

Zener diode

When the communication system is isolated

Note1

Photocoupler A

Photocoupler B

Note2 Note3 Note2

Note3

Avago Technologies, Inc.

Notes 1

R18UZ0056EJ0102 Page 4 of 83 Dec. 28, 2018

Port Setting

Set multiplexed pins.

Note1

Pxx, PMxx, PMCxx, PMFCxx, PMFCExx RPxx, RPMxx, RPMCxx, RPMFCxx, RPMFCExx

Bridge Setting

Set CC-Link bus bridge registers.

Note2

CCBSC (CC-Link bus size control register) ：0x0000_5575 CCSMC1 (CC-Link bus bridge control register0) ：0x0000_1131

Protection Release

Protection release the write-protected registers.

Note2

SYSPCMD (System Protect Command Register) ：0x0000_00A5 SYSPCMD (System Protect Command Register) ：0x0000_0001 SYSPCMD (System Protect Command Register) ：0x0000_FFFE SYSPCMD (System Protect Command Register) ：0x0000_0001

Pin Setting

CC-Link remote device station pins.

Note2

CCSMD （CC-Link remote device operating mode setting register)

Reset Release

Release CC-Link remote device station from the reset state.

Note2

Set up time (76.76us) requires before reset released. CCSRES（CC-Link Reset Register）：0x0000_0001 In case of reading the transmission speed by software. It’s should Be read after 51.2us from resetting

Protect Setting

Protect set the write-protected registers.

Note2

SYSPCMD (System Protect Command Register) ：0x0000_0000

・・・

1.

For details on multipl exed pins and po

R-IN32M4-CL2 User’s Manual

2.

For detail function)" or "R-IN32M4-CL2 User’s Manual (Peripheral function)".

R-IN32 Series CC-Link Remote device station 4. R-IN32 Series Initialization

4. R-IN32 Series Initialization

Figure 4.1 s h ows how to R-IN3 2 Series initialization for CC-Link remote device station. Procedure for setting CC-Link remote device station, see section 9, Sample Flowchart for CC-Link Version 1.

Figure 4.1 How to R-IN32 Series Initialization

Notes

R-IN32M3-EC User’s Manual R-IN32M3-CL User’s Manual

rt-related registers, see following manuals.

s on register specifications, see "R-IN32M3 series User’s Manual (Peripheral

R18UZ0056EJ0102 Page 5 of 83 Dec. 28, 2018

CC-Link Pin Name

R-IN32M3 Pin Name

Shared Port

Description

SD

CCS_SD

P54

Communications circuit data transmission pin

RD1

CCS_RD

P53

Communications circuit data reception pin

control pin

RUN (CCS_LNKRUNZ) = "L RUN "

ERRL(CCS_ERRZ) = "L ERR"

SDLED(CCS_SDLEDZ) = "SD"

RDLED( CCS_RDLEDZ) = "RD"

IOTENSU

CCS_IOTENSU

P22

Initial setting pin (Low fixed)

SENYU0

CCS_SENYU0

P23

Initial setting pin

SENYU1

CCS_SENYU1

P24

Initial setting pin

BS1, 2, 4, 8

CCS_BS1, 2, 4, 8

RP02-RP05

Baud rate setting switch input pin

SW1, 2, 4, 8, 10, 20, 40, 80

CCS_STATION_NO_0-7

P70-P77

Station no. setting switch input pins

REFSTB

CCS_REFSTB

P10

Interrupt signal

WDTZ

CCS_WDTZ

P13

Please connect when alarm is necessary

If there is no external fuse, input High

R-IN32 Series CC-Link Remote device station 5. CC-Link Remote Device Station Pins

5. CC-Link Remote Device Station Pins

Table 5.1 shows correspondence between CC-Lin k remote device station pins and R-IN32M3 series pins, Figure 5.1 shows R-IN32M3 Series CC-Link Remote Device Station Peripheral Architecture.

Table 5.1 Correspondence between CC -Link Remote Device Station Pins and R-IN32M3 Series Pins <R>

SDGATEON CCS_SDGATEON P52 Communications circuit transmit data & gate

RUN CCS_LNKRUNZ P50 Link RUN LED control output

ERRL CCS_ERRZ P25 Operation check LED

SDLED CCS_SDLEDZ RP00 Operation check LED

RDLED CCS_RDLEDZ P51 Receive data LED control output

FUSEZ CCS_FUSEZ P36 Please connect when external fuse is

necessary.

R18UZ0056EJ0102 Page 6 of 83 Dec. 28, 2018

R-IN32M3 Series

Cortex-M3

Control Register

CCRES

AHB Bus

Bridge

CCBSC

CCSMC0 CCSMC1

CC-Link

Remote Device

Station

CC-Link

Intelligent Device

Station

CCSMD

CCS_SD, CCS_RD, CCS_SDGATEON

CCS_REFSTB

Note

CCS_LNKRUN, CCS_ERRZ, CCS_SDLEDZ, CCS_RDLEDZ

CCS_STATION_NO7-0

CCS_IOTENSU, CCS_SENYU1-0, CCS_BS1,2,4,8

.

It is necessary to connect a CCS_REFSTB pin to a port pin with the external interrupt function (INTPZ).

R-IN32 Series CC-Link Remote device station 5. CC-Link Remote Device Station Pins

Figure 5.1 R-IN32M3 Series CC-Link Remote Device Station Peripheral Architecture

Note

R18UZ0056EJ0102 Page 7 of 83 Dec. 28, 2018

CC-Link Pin Name

R-IN32M4-CL2 Pin Name

Shared Port

Description

SD

CCS_SD

P56

Communications circuit data transmission pin

RD1

CCS_RD

P54

Communications circuit data reception pin

control pin

RUN

CCS_LNKRUNZ

P32

Link RUN LED control output

ERRL

CCS_ERRZ

P25

Operation check LED

SDLED

CCS_SDLEDZ

RP00

Operation check LED

RDLED

CCS_RDLEDZ

P33

Receive data LED control output

IOTENSU

CCS_IOTENSU

P22

Initial setting pin (Low fixed)

SENYU0

CCS_SENYU0

P23

Initial setting pin

SENYU1

CCS_SENYU1

P24

Initial setting pin

BS1, 2, 4, 8

CCS_BS1, 2, 4, 8

RP02-RP05

Baud rate setting switch input pin

SW1, 2, 4, 8, 10, 20, 40, 80

CCS_STATION_NO_0-7

P70-P77

Station no. setting switch input pins

REFSTB

CCS_REFSTB

P50

Interrupt signal

R-IN32M4-CL2

Cortex-M4F

Control Register

CCRES

AHB Bus

Bridge

CCBSC

CCSMC0

CCSMC1

CC

-Link

Remote Device

Station

CC

-Link

Intelligent Device

Station

CCSMD

CCS_SD, CCS_RD, CCS_SDGATEON

CCS_LNKRUN, CCS_ERRZ, CCS_SDLEDZ, CCS_RDLEDZ

CCS_STATION_NO7-0

CCS_IOTENSU, CCS_SENYU1-0, CCS_BS1,2,4,8

R-IN32 Series CC-Link Remote device station 5. CC-Link Remote Device Station Pins

Table 5.2 shows correspondence bet ween CC-Link remote device station pins and R-IN32M4-CL2 pins, Figure 5.2 shows R-IN32M4-CL2 CC-Li nk Remote Device Station Peripheral Architecture.

Table 5.2 Correspondence between CC -Link Remote Device Station Pins and R-IN32M4-CL2 Pins <R>

SDGATEON CCS_SDGATEON P51 Communications circuit transmit data & gate

Figure 5.2 R-IN32M4-CL2 CC-Link Remote Device Station Peripheral Architecture

R18UZ0056EJ0102 Page 8 of 83 Dec. 28, 2018

Terminal

SENYU0

L H L H SENYU1

L L H

H

Caution

:

Fix the IOTENSU pin to the low level. Setting the pi n to the high level is prohibited. <R>

R-IN32 Series CC-Link Remote device station 6. Setting Details

6. Setting Details

6.1 Setting the Number of Occupied Stations

Based on the combination listed below, the number of occupied stations can be set from 1 to 4.With one communication, 32 I/O bits and 4 words of data can be used per station.

Table 6.1 Occupied stations setting

Number of occupied stations

1 2 3 4

When the number of occupied stations is set to "2":

With one communication, 64 I/O bits and 8 words of data can be used.

R18UZ0056EJ0102 Page 9 of 83 Dec. 28, 2018

Terminal

SW80

H H H H H H H H L L SW40

H H H H L L L L H H SW20

H H L L H H L L H H SW10

H L H L H L H L H

L

Terminal

SW8

H H H H H H H H L L SW4

H H H H L L L L H H SW2

H H L L H H L L H H SW1

H L H L H L H L H

L

Terminal

kbps

Mbps

BS8 H H H H H H H H L L

BS4 H H H H L L L L H H

BS2 H H L L H H L L H H

BS1 H L H L H L H L H L

1.

The settings result in error. Station number setting value 0 or 65 and over: Results in a station number switch setting error. The L ERR. LED turns on.

2.

Baud rate setting value Results in a baud rate switch setting error. The L ERR. LED turns on.

R-IN32 Series CC-Link Remote device station 6. Setting Details

6.2 Setting the Station Number and Baud Rate

Table 6.2 Setting the station number and baud rate

Station No. (Tens Place)

00 10 20 30 40 50 60 70

Note1 80Note1

Station No. (Ones Place)

0 1 2 3 4 5 6 7 8 9

90

Note1

Notes

Baud Rate

156

625

2.5

5

10

1 to 64: Station number (normal)

:

5

Note2

6

Note2

7

Note2

8

Note2

9

Note2

R18UZ0056EJ0102 Page 10 of 83 Dec. 28, 2018

LED name

Status

Condition

normally received after network entry. (see Figure 6.1)

4. During hardware reset

Blinking

-

higher)

2. During hardware reset

blinking)

ON

During transmission or +0.41ms × 2

after transmission (n = 1 to 8)

2. During hardware reset

Blinking

-

ON

During channel carrier detectio n

2. During hardware reset

Blinking

-

M R

R M

Turn the power on Cancel reset

Communication

with other station

Test and test polling

Test

polling

Test

response

Refresh and

polling

Refresh

Polling

response

(*1) Network entry

RUN on

Unable to detect carrier for

channel

3.28ms( 10M)

Timeout (refresh or refresh & polling not received)

104.8576ms ( 10M)

RUN off

R-IN32 Series CC-Link Remote device station 6. Setting Details

6.3 Transmission Monitor Section Terminals (for LED)

(1) Light ON/OFF/BLINK conditions

Each LEDs are automatically set ON/OFF/BLANK under the following conditions

Table 6.2 Light ON/OFF/BLINK conditions

L RUN (ON: "L" output)

L ERR. (ON: "L" output)

SD (ON: "L" output)

RD (ON: "L" output)

ON When the refresh signal or the refresh signal and polling signal are

OFF 1. Before network entry (see Figure 6.1)

2. Channel carrier detection failed

3. Timeout

ON 1. CRC error

2. Station number switch setting error at reset release (0 or 65 stations or more including the number of occupied stations)

3. Baud rate switch setting error at reset release (a setting of 5 or

OFF 1. Normal communication

Blinking The switch setting changed from the setting at reset release. (0.4s

(n-1)

OFF 1. Other than the above

OFF 1. Channel carrier detection failed

(2) Details of RUN light on

Figure 6.1 Condition of RUN light on

R18UZ0056EJ0102 Page 11 of 83 Dec. 28, 2018

L RUN

L ERR.

SD

RD

Operation

☼ ☼

noise.

☼ ☼

and is different from the value at startup L ERR. is lit at intervals of 0.4 s.

☼

- (Impossible operation status)

☼

○

Unable to respond because the received data caus ed a CRC error.

☼

●

- (Impossible operation status)

●

☼

Normal communication

●

☼

- (Impossible operation status)

● ● ○

No data for the own station

● ● ●

- (Impossible operation status)

☼

Responds to polling signal, but the refresh rec eption caused a CRC error.

☼

- (Impossible operation status)

☼

○

Data for the own station caused a CRC error.

☼

●

- (Impossible operation status)

●

☼

Link startup has not been conducted.

●

☼

- (Impossible operation status)

due to noise.

Power off or hardware being set.

○ ● ○

Baud rate and/or station number setting error

Note:

A blinking L ERR. light warns the operator that there has been a change in the baud rate or station number setting. The setting will be established at the next reset.

R-IN32 Series CC-Link Remote device station 6. Setting Details

(3) Light ON/OFF/BLINK conditions

Table 6.3 Light ON/OFF/BLINK conditions

○

○ ○ ○ ○ ○ ○ ○

●

● ● ● ○ Either no data for the own station or unable to receive the data for own station

● ● ● ● Unable to receive data due to w ire breakage, etc.

○ Communicating normally, but CRC errors have often been detected due to

○ The communication baud rate or the station number setting value has changed

Note

●

● ○

●

○

●

● ○

●

○: ON ●: OFF ☼: BLINK

R18UZ0056EJ0102 Page 12 of 83 Dec. 28, 2018

MON7, 6

: Monitor terminals for internal signals. The signals to be monitored are not specified.

MON5

: Set to high when RWw information (bit data) of the own station is being received.

MON4

: Set to high when RY information (bit data) of the own station is being received.

MON3

: Set to high when a communication frame (bit data) other than a flag pattern is being received.

MON2 to 0

: Display the type of frame being received according to the table below.

MON2

MON1

MON0

Frame type

H H L

Receiving polling and refresh data

H L H

Receiving polling data

H L L

Receiving test polling and test data

L H H

Receiving test polling

L H L

Receiving refresh cycle complete

L L L

Initial state

R-IN32 Series CC-Link Remote device station 7. Monitor Output of Reception Frame Information

7. Monitor Output of Reception Frame Information

Table 7.1 Monitor output of reception frame information

R18UZ0056EJ0102 Page 13 of 83 Dec. 28, 2018

Address

(hexadecimal)

Address

(hexadecimal)

Data width

16 8

16

8

(Lower)

00

Send data write enable information

Allowed

Not allowed

(Lower)

80

Send data write completed

Allowed

(Upper)

01

Receive data update information

Allowed

Not allowed

(Upper)

81

Receive data read request

Allowed

(Lower)

02

Station number switch information

Allowed

Not allowed

(Lower)

82

Vendor code (Lower)

Allowed

stations information

(Lower)

04

Error information 1

Allowed

Not allowed

(Lower)

84

Model code

Allowed

(Upper)

05

Error information 2

Allowed

Not allowed

(Upper)

85

Version

Allowed

(Lower)

06

(Not used)

Not allowed

(Lower)

86

SDLED illumination time setting

Allowed

(Upper)

07

(Not used)

Not allowed

(Upper)

87

Timeout time setting

Allowed

(Lower)

08

M→R ST1

Allowed

Not allowed

(Lower)

88

R→M ST1

Allowed

(Upper)

09

M→R ST2

Allowed

Not allowed

(Upper)

89

R→M ST2

Allowed

(Lower)

0A

M→R RY00-07

Allowed

Not allowed

(Lower)

8A

R→M RX00-07

Allowed

(Upper)

0B

M→R RY08-0F

Allowed

Not allowed

(Upper)

8B

R→M RX08-0F

Allowed

(Lower)

0C

M→R RY10-17

Allowed

Not allowed

(Lower)

8C

R→M RX10-17

Allowed

(Upper)

0D

M→R RY18-1F

Allowed

Not allowed

(Upper)

8D

R→M RX18-1F

Allowed

(Lower)

0E

(Not used)

Not allowed

(Lower)

8E

(Not used)

Not allowed

(Upper)

0F

(Not used)

Not allowed

(Upper)

8F

(Not used)

Not allowed

(Lower)

10

(Not used)

Not allowed

(Lower)

90

(Not used)

Not allowed

(Upper)

11

(Not used)

Not allowed

(Upper)

91

(Not used)

Not allowed

(Lower)

12

(Not used)

Not allowed

(Lower)

92

(Not used)

Not allowed

(Upper)

13

(Not used)

Not allowed

(Upper)

93

(Not used)

Not allowed

(Lower)

14

(Not used)

Not allowed

(Lower)

94

(Not used)

Not allowed

(Upper)

15

(Not used)

Not allowed

(Upper)

95

(Not used)

Not allowed

(Lower)

16

(Not used)

Not allowed

(Lower)

96

(Not used)

Not allowed

(Upper)

17

(Not used)

Not allowed

(Upper)

97

(Not used)

Not allowed

(Lower)

18

(Not used)

Not allowed

(Lower)

98

(Not used)

Not allowed

(Upper)

19

(Not used)

Not allowed

(Upper)

99

(Not used)

Not allowed

(Lower)

1A

M→R RWw0(L)

Allowed

Not allowed

(Lower)

9A

R→M RWr0(L)

Allowed

(Upper)

1B

M→R RWw0(H)

Allowed

Not allowed

(Upper)

9B

R→M RWr0(H)

Allowed

(Lower)

1C

M→R RWw1(L)

Allowed

Not allowed

(Lower)

9C

R→M RWr1(L)

Allowed

(Upper)

1D

M→R RWw1(H)

Allowed

Not allowed

(Upper)

9D

R→M RWr1(H)

Allowed

(Lower)

1E

M→R RWw2(L)

Allowed

Not allowed

(Lower)

9E

R→M RWr2(L)

Allowed

(Upper)

1F

M→R RWw2(H)

Allowed

Not allowed

(Upper)

9F

R→M RWr2(H)

Allowed

(Lower)

20

M→R RWw3(L)

Allowed

Not allowed

(Lower)

A0

R→M RWr3(L)

Allowed

(Upper)

21

M→R RWw3(H)

Allowed

Not allowed

(Upper)

A1

R→M RWr3(H)

Allowed

(Lower)

22

(Not used)

Not allowed

(Lower)

A2

(Not used)

Not allowed

(Upper)

23

(Not used)

Not allowed

(Upper)

A3

(Not used)

Not allowed

(Lower)

36

(Not used)

Not allowed

(Lower)

B6

(Not used)

Not allowed

(Upper)

37

(Not used)

Not allowed

(Upper)

B7

(Not used)

Not allowed

(Lower)

38

(Not used)

Not allowed

(Lower)

B8

(Not used)

Not allowed

(Upper)

39

(Not used)

Not allowed

(Upper)

B9

(Not used)

Not allowed

3A 3A

(Lower)

BA

Setting HOLD/CLR information

Allowed

(Upper)

BB

(Not used)

Not allowed

BC

3E 3F

BF

R-IN32 Series CC-Link Remote device station 8. Memory Map

8. Memory Map

Memory must be written in wor d unit in R-IN32 Series.

8.1 Memory Map List

Table 8.1 When the Number of Occupied Stations is Set to 1

00

02

(Upper) 03

04

06

08

0A

0C

0E

10

12

14

16

18

1A

1C

1E

Description Read Write

Baud rate switch/number of occupied

Reception buffer

80

Allowed Not allowed (Upper) 83 Vendor code (Upper) Allowed Allowed

82

84

86

88

8A

8C

8E

90

92

94

96

98

9A

9C

9E

Update buffer

Description Read Write

20

22

36

38

(Not used) Not allowed Not allowed

A0

A2

B6

B8

BA

BC BE

(Not used) Not allowed Not allowed

R18UZ0056EJ0102 Page 14 of 83 Dec. 28, 2018

Address

(hexadecimal)

Address

(hexadecimal)

Data width

16

8 16

8

(Lower)

00

Send data write enable information

Allowed

Not allowed

80

(Lower)

80

Send data write completed

Allowed

(Upper)

01

Receive data update information

Allowed

Not allowed

(Upper)

81

Receive data read request

Allowed

(Lower)

02

Station number switch information

Allowed

Not allowed

82

(Lower)

82

Vendor code (Lower)

Allowed

stations information

(Lower)

04

Error information 1

Allowed

Not allowed

84

(Lower)

84

Model code

Allowed

(Upper)

05

Error information 2

Allowed

Not allowed

(Upper)

85

Version

Allowed

(Lower)

06

(Not used)

Not allowed

86

(Lower)

86

SDLED illumination time setting

Allowed

(Upper)

07

(Not used)

Not allowed

(Upper)

87

Timeout time setting

Allowed

(Lower)

08

Reception buffer

M→R ST1

Allowed

Not allowed

88

(Lower)

88

Update buffer

R→M ST1

Allowed

(Upper)

09

M→R ST2

Allowed

Not allowed

(Upper)

89

R→M ST2

Allowed

(Lower)

0A

M→R RY00-07

Allowed

Not allowed

8A

(Lower)

8A

R→M RX00-07

Allowed

(Upper)

0B

M→R RY08-0F

Allowed

Not allowed

(Upper)

8B

R→M RX08-0F

Allowed

(Lower)

0C

M→R RY10-17

Allowed

Not allowed

8C

(Lower)

8C

R→M RX10-17

Allowed

(Upper)

0D

M→R RY18-1F

Allowed

Not allowed

(Upper)

8D

R→M RX18-1F

Allowed

(Lower)

0E

M→R RY20-27

Allowed

Not allowed

8E

(Lower)

8E

R→M RX20-27

Allowed

(Upper)

0F

M→R RY28-2F

Allowed

Not allowed

(Upper)

8F

R→M RX28-2F

Allowed

(Lower)

10

M→R RY30-37

Allowed

Not allowed

90

(Lower)

90

R→M RX30-37

Allowed

(Upper)

11

M→R RY38-3F

Allowed

Not allowed

(Upper)

91

R→M RX38-3F

Allowed

(Lower)

12

(Not used)

Not allowed

92

(Lower)

92

(Not used)

Not allowed

(Upper)

13

(Not used)

Not allowed

(Upper)

93

(Not used)

Not allowed

(Lower)

14

(Not used)

Not allowed

94

(Lower)

94

(Not used)

Not allowed

(Upper)

15

(Not used)

Not allowed

(Upper)

95

(Not used)

Not allowed

(Lower)

16

(Not used)

Not allowed

96

(Lower)

96

(Not used)

Not allowed

(Upper)

17

(Not used)

Not allowed

(Upper)

97

(Not used)

Not allowed

(Lower)

18

(Not used)

Not allowed

98

(Lower)

98

(Not used)

Not allowed

(Upper)

19

(Not used)

Not allowed

(Upper)

99

(Not used)

Not allowed

(Lower)

1A

M→R RWw0(L)

Allowed

Not allowed

9A

(Lower)

9A

R→M RWr0(L)

Allowed

(Upper)

1B

M→R RWw0(H)

Allowed

Not allowed

(Upper)

9B

R→M RWr0(H)

Allowed

(Lower)

1C

M→R RWw1(L)

Allowed

Not allowed

9C

(Lower)

9C

R→M RWr1(L)

Allowed

(Upper)

1D

M→R RWw1(H)

Allowed

Not allowed

(Upper)

9D

R→M RWr1(H)

Allowed

(Lower)

1E

M→R RWw2(L)

Allowed

Not allowed

9E

(Lower)

9E

R→M RWr2(L)

Allowed

(Upper)

1F

M→R RWw2(H)

Allowed

Not allowed

(Upper)

9F

R→M RWr2(H)

Allowed

(Lower)

20

M→R RWw3(L)

Allowed

Not allowed

A0

(Lower)

A0

R→M RWr3(L)

Allowed

(Upper)

21

M→R RWw3(H)

Allowed

Not allowed

(Upper)

A1

R→M RWr3(H)

Allowed

(Lower)

22

M→R RWw4(L)

Allowed

Not allowed

A2

(Lower)

A2

R→M RWr4(L)

Allowed

(Upper)

23

M→R RWw4(H)

Allowed

Not allowed

(Upper)

A3

R→M RWr4(H)

Allowed

(Lower)

24

M→R RWw5(L)

Allowed

Not allowed

A4

(Lower)

A4

R→M RWr5(L)

Allowed

(Upper)

25

M→R RWw5(H)

Allowed

Not allowed

(Upper)

A5

R→M RWr5(H)

Allowed

(Lower)

26

M→R RWw6(L)

Allowed

Not allowed

A6

(Lower)

A6

R→M RWr6(L)

Allowed

(Upper)

27

M→R RWw6(H)

Allowed

Not allowed

(Upper)

A7

R→M RWr6(H)

Allowed

(Lower)

28

M→R RWw7(L)

Allowed

Not allowed

A8

(Lower)

A8

R→M RWr7(L)

Allowed

(Upper)

29

M→R RWw7(H)

Allowed

Not allowed

(Upper)

A9

R→M RWr7(H)

Allowed

(Lower)

2A

(Not used)

Not allowed

A

(Lower)

AA

(Not used)

Not allowed

(Upper)

2B

(Not used)

Not allowed

(Upper)

AB

(Not used)

Not allowed

(Lower)

2C

(Not used)

Not allowed

AC

(Lower)

AC

(Not used)

Not allowed

(Upper)

2D

(Not used)

Not allowed

(Upper)

AD

(Not used)

Not allowed

(Lower)

2E

(Not used)

Not allowed

AE

(Lower)

AE

(Not used)

Not allowed

(Upper)

2F

(Not used)

Not allowed

(Upper)

AF

(Not used)

Not allowed

(Lower)

30

(Not used)

Not allowed

B0

(Lower)

B0

(Not used)

Not allowed

(Upper)

31

(Not used)

Not allowed

(Upper)

B1

(Not used)

Not allowed

(Lower)

32

(Not used)

Not allowed

B2

(Lower)

B2

(Not used)

Not allowed

(Upper)

33

(Not used)

Not allowed

(Upper)

B3

(Not used)

Not allowed

(Lower)

34

(Not used)

Not allowed

B4

(Lower)

B4

(Not used)

Not allowed

(Upper)

35

(Not used)

Not allowed

(Upper)

B5

(Not used)

Not allowed

(Lower)

36

(Not used)

Not allowed

B6

(Lower)

B6

(Not used)

Not allowed

(Upper)

37

(Not used)

Not allowed

(Upper)

B7

(Not used)

Not allowed

(Lower)

38

(Not used)

Not allowed

B8

(Lower)

B8

(Not used)

Not allowed

(Upper)

39

(Not used)

Not allowed

(Upper)

B9

(Not used)

Not allowed

3A 3A

BA

(Lower)

BA

Setting HOLD/CLR information

Allowed

(Upper)

BB

(Not used)

Not allowed

(Not used)

Not allowed

BC BC

3E

3F

BE BF

R-IN32 Series CC-Link Remote device station 8. Memory Map

Table 8.2 When the Number of Occupied Stations is Set to 2

00

02

04

06

08

0A

0C

0E

10

12

14

16

18

1A

1C

(Upper) 03

Description Read Write

Baud rate switch/number of occupied

Allowed Not allowed

Description Read Write

(Upper) 83 Vendor code (Upper) Allowed Allowed

1E

20

22

24

26

28

2A

2C

2E

30

32

34

36

38

A

(Not used) Not allowed Not allowed

R18UZ0056EJ0102 Page 15 of 83 Dec. 28, 2018

Address

(hexadecimal)

Address

(hexadecimal)

Data width

16 8

16

8

(Lower)

00

Send data write enable information

Allowed

Not allowed

(Lower)

80

Send data write completed

Allowed

(Upper)

01

Receive data update information

Allowed

Not allowed

(Upper)

81

Receive data read request

Allowed

(Lower)

02

Station number switch information

Allowed

Not allowed

(Lower)

82

Vendor code (Lower)

Allowed

information

(Lower)

04

Error information 1

Allowed

Not allowed

(Lower)

84

Model code

Allowed

(Upper)

05

Error information 2

Allowed

Not allowed

(Upper)

85

Version

Allowed

(Lower)

06

(Not used)

Not allowed

(Lower)

86

SDLED illumination time setting

Allowed

(Upper)

07

(Not used)

Not allowed

(Upper)

87

Timeout time setting

Allowed

(Lower)

08

Reception buffer

M→R ST1

Allowed

Not allowed

(Lower)

88

Update buffer

R→M ST1

Allowed

(Upper)

09

M→R ST2

Allowed

Not allowed

(Upper)

89

R→M ST2

Allowed

(Lower)

0A

M→R RY00-07

Allowed

Not allowed

(Lower)

8A

R→M RX00-07

Allowed

(Upper)

0B

M→R RY08-0F

Allowed

Not allowed

(Upper)

8B

R→M RX08-0F

Allowed

(Lower)

0C

M→R RY10-17

Allowed

Not allowed

(Lower)

8C

R→M RX10-17

Allowed

(Upper)

0D

M→R RY18-1F

Allowed

Not allowed

(Upper)

8D

R→M RX18-1F

Allowed

(Lower)

0E

M→R RY20-27

Allowed

Not allowed

(Lower)

8E

R→M RX20-27

Allowed

(Upper)

0F

M→R RY28-2F

Allowed

Not allowed

(Upper)

8F

R→M RX28-2F

Allowed

(Lower)

10

M→R RY30-37

Allowed

Not allowed

(Lower)

90

R→M RX30-37

Allowed

(Upper)

11

M→R RY38-3F

Allowed

Not allowed

(Upper)

91

R→M RX38-3F

Allowed

(Lower)

12

M→R RY40-47

Allowed

Not allowed

(Lower)

92

R→M RX40-47

Allowed

(Upper)

13

M→R RY48-4F

Allowed

Not allowed

(Upper)

93

R→M RX48-4F

Allowed

(Lower)

14

M→R RY50-57

Allowed

Not allowed

(Lower)

94

R→M RX50-57

Allowed

(Upper)

15

M→R RY58-5F

Allowed

Not allowed

(Upper)

95

R→M RX58-5F

Allowed

(Lower)

16

(Not used)

Not allowed

(Lower)

96

(Not used)

Not allowed

(Upper)

17

(Not used)

Not allowed

(Upper)

97

(Not used)

Not allowed

(Lower)

18

(Not used)

Not allowed

(Lower)

98

(Not used)

Not allowed

(Upper)

19

(Not used)

Not allowed

(Upper)

99

(Not used)

Not allowed

(Lower)

1A

M→R RWw0(L)

Allowed

Not allowed

(Lower)

9A

R→M RWr0(L)

Allowed

(Upper)

1B

M→R RWw0(H)

Allowed

Not allowed

(Upper)

9B

R→M RWr0(H)

Allowed

(Lower)

1C

M→R RWw1(L)

Allowed

Not allowed

(Lower)

9C

R→M RWr1(L)

Allowed

(Upper)

1D

M→R RWw1(H)

Allowed

Not allowed

(Upper)

9D

R→M RWr1(H)

Allowed

(Lower)

1E

M→R RWw2(L)

Allowed

Not allowed

(Lower)

9E

R→M RWr2(L)

Allowed

(Upper)

1F

M→R RWw2(H)

Allowed

Not allowed

(Upper)

9F

R→M RWr2(H)

Allowed

(Lower)

20

M→R RWw3(L)

Allowed

Not allowed

(Lower)

A0

R→M RWr3(L)

Allowed

(Upper)

21

M→R RWw3(H)

Allowed

Not allowed

(Upper)

A1

R→M RWr3(H)

Allowed

(Lower)

22

M→R RWw4(L)

Allowed

Not allowed

(Lower)

A2

R→M RWr4(L)

Allowed

(Upper)

23

M→R RWw4(H)

Allowed

Not allowed

(Upper)

A3

R→M RWr4(H)

Allowed

(Lower)

24

M→R RWw5(L)

Allowed

Not allowed

(Lower)

A4

R→M RWr5(L)

Allowed

(Upper)

25

M→R RWw5(H)

Allowed

Not allowed

(Upper)

A5

R→M RWr5(H)

Allowed

(Lower)

26

M→R RWw6(L)

Allowed

Not allowed

(Lower)

A6

R→M RWr6(L)

Allowed

(Upper)

27

M→R RWw6(H)

Allowed

Not allowed

(Upper)

A7

R→M RWr6(H)

Allowed

(Lower)

28

M→R RWw7(L)

Allowed

Not allowed

(Lower)

A8

R→M RWr7(L)

Allowed

(Upper)

29

M→R RWw7(H)

Allowed

Not allowed

(Upper)

A9

R→M RWr7(H)

Allowed

(Lower)

2A

M→R RWw8(L)

Allowed

Not allowed

(Lower)

AA

R→M RWr8(L)

Allowed

(Upper)

2B

M→R RWw8(H)

Allowed

Not allowed

(Upper)

AB

R→M RWr8(H)

Allowed

(Lower)

2C

M→R RWw9(L)

Allowed

Not allowed

(Lower)

AC

R→M RWr9(L)

Allowed

(Upper)

2D

M→R RWw9(H)

Allowed

Not allowed

(Upper)

AD

R→M RWr9(H)

Allowed

(Lower)

2E

M→R RWw10(L)

Allowed

Not allowed

(Lower)

AE

R→M RWr10(L)

Allowed

(Upper)

2F

M→R RWw10(H)

Allowed

Not allowed

(Upper)

AF

R→M RWr10(H)

Allowed

(Lower)

30

M→R RWw11(L)

Allowed

Not allowed

(Lower)

B0

R→M RWr11(L)

Allowed

(Upper)

31

M→R RWw11(H)

Allowed

Not allowed

(Upper)

B1

R→M RWr11(H)

Allowed

(Lower)

32

(Not used)

Not allowed

(Lower)

B2

(Not used)

Not allowed

(Upper)

33

(Not used)

Not allowed

(Upper)

B3

(Not used)

Not allowed

(Lower)

34

(Not used)

Not allowed

(Lower)

B4

(Not used)

Not allowed

(Upper)

35

(Not used)

Not allowed

(Upper)

B5

(Not used)

Not allowed

(Lower)

36

(Not used)

Not allowed

(Lower)

B6

(Not used)

Not allowed

(Upper)

37

(Not used)

Not allowed

(Upper)

B7

(Not used)

Not allowed

38

(Lower)

38

(Not used)

Not allowed

(Lower)

B8

(Not used)

Not allowed

(Upper)

39

(Not used)

Not allowed

(Upper)

B9

(Not used)

Not allowed

3A 3A

(Lower)

BA

Setting HOLD/CLR information

Allowed

(Upper)

BB

(Not used)

Not allowed

(Not used)

Not allowed

BC BC

3E

3F

BE BF

R-IN32 Series CC-Link Remote device station 8. Memory Map

Table 8.3 When the Number of Occupied Stations is Set to 3

00

02

04

06

08

0A

0C

0E

10

12

14

16

18

1A

1C

(Upper) 03

Description Read Write

Baud rate switch/number of occupied stations

Description Read Write

80

Allowed Not allowed (Upper) 83 Vendor code (Upper) Allowed Allowed

82

84

86

88

8A

8C

8E

90

92

94

96

98

9A

9C

1E

20

22

24

26

28

2A

2C

2E

30

32

34

36

9E

A0

A2

A4

A6

A8

AA

AC

AE

B0

(Not used) Not allowed Not allowed

B2

B4

B6

B8

BA

R18UZ0056EJ0102 Page 16 of 83 Dec. 28, 2018

Address

(hexadecimal)

Address

(hexadecimal)

Data width

16 8

16

8

00

(Lower)

00

Send data write enable information

Allowed

Not allowed

(Lower)

80

Send data write completed

Allowed

(Upper)

01

Receive data update information

Allowed

Not allowed

(Upper)

81

Receive data read request

Allowed

0

(Lower)

02

Station number switch information

Allowed

Not allowed

(Lower)

82

Vendor code (Lower)

Allowed

information

0

(Lower)

04

Error information 1

Allowed

Not allowed

(Lower)

84

Model code

Allowed

(Upper)

05

Error information 2

Allowed

Not allowed

(Upper)

85

Version

Allowed

0

(Lower)

06

(Not used)

Not allowed

(Lower)

86

SDLED illumination time setting

Allowed

(Upper)

07

(Not used)

Not allowed

(Upper)

87

Timeout time setting

Allowed

0

(Lower)

08

Reception buffer

M→R ST1

Allowed

Not allowed

(Lower)

88

Update buffer

R→M ST1

Allowed

(Upper)

09

M→R ST2

Allowed

Not allowed

(Upper)

89

R→M ST2

Allowed

0

(Lower)

0A

M→R RY00-07

Allowed

Not allowed

(Lower)

8A

R→M RX00-07

Allowed

(Upper)

0B

M→R RY08-0F

Allowed

Not allowed

(Upper)

8B

R→M RX08-0F

Allowed

0C

(Lower)

0C

M→R RY10-17

Allowed

Not allowed

(Lower)

8C

R→M RX10-17

Allowed

(Upper)

0D

M→R RY18-1F

Allowed

Not allowed

(Upper)

8D

R→M RX18-1F

Allowed

0E

(Lower)

0E

M→R RY20-27

Allowed

Not allowed

(Lower)

8E

R→M RX20-27

Allowed

(Upper)

0F

M→R RY28-2F

Allowed

Not allowed

(Upper)

8F

R→M RX28-2F

Allowed

A0

(Lower)

10

M→R RY30-37

Allowed

Not allowed

(Lower)

90

R→M RX30-37

Allowed

(Upper)

11

M→R RY38-3F

Allowed

Not allowed

(Upper)

91

R→M RX38-3F

Allowed

12

(Lower)

12

M→R RY40-47

Allowed

Not allowed

(Lower)

92

R→M RX40-47

Allowed

(Upper)

13

M→R RY48-4F

Allowed

Not allowed

(Upper)

93

R→M RX48-4F

Allowed

14

(Lower)

14

M→R RY50-57

Allowed

Not allowed

(Lower)

94

R→M RX50-57

Allowed

(Upper)

15

M→R RY58-5F

Allowed

Not allowed

(Upper)

95

R→M RX58-5F

Allowed

16

(Lower)

16

M→R RY60-67

Allowed

Not allowed

(Lower)

96

R→M RX60-67

Allowed

(Upper)

17

M→R RY68-6F

Allowed

Not allowed

(Upper)

97

R→M RX68-6F

Allowed

18

(Lower)

18

M→R RY70-77

Allowed

Not allowed

(Lower)

98

R→M RX70-77

Allowed

(Upper)

19

M→R RY78-7F

Allowed

Not allowed

(Upper)

99

R→M RX78-7F

Allowed

1A

(Lower)

1A

M→R RWw0(L)

Allowed

Not allowed

(Lower)

9A

R→M RWr0(L)

Allowed

(Upper)

1B

M→R RWw0(H)

Allowed

Not allowed

(Upper)

9B

R→M RWr0(H)

Allowed

1C

(Lower)

1C

M→R RWw1(L)

Allowed

Not allowed

(Lower)

9C

R→M RWr1(L)

Allowed

(Upper)

1D

M→R RWw1(H)

Allowed

Not allowed

(Upper)

9D

R→M RWr1(H)

Allowed

1E

(Lower)

1E

M→R RWw2(L)

Allowed

Not allowed

(Lower)

9E

R→M RWr2(L)

Allowed

(Upper)

1F

M→R RWw2(H)

Allowed

Not allowed

(Upper)

9F

R→M RWr2(H)

Allowed

20

(Lower)

20

M→R RWw3(L)

Allowed

Not allowed

(Lower)

A0

R→M RWr3(L)

Allowed

(Upper)

21

M→R RWw3(H)

Allowed

Not allowed

(Upper)

A1

R→M RWr3(H)

Allowed

22

(Lower)

22

M→R RWw4(L)

Allowed

Not allowed

(Lower)

A2

R→M RWr4(L)

Allowed

(Upper)

23

M→R RWw4(H)

Allowed

Not allowed

(Upper)

A3

R→M RWr4(H)

Allowed

24

(Lower)

24

M→R RWw5(L)

Allowed

Not allowed

(Lower)

A4

R→M RWr5(L)

Allowed

(Upper)

25

M→R RWw5(H)

Allowed

Not allowed

(Upper)

A5

R→M RWr5(H)

Allowed

26

(Lower)

26

M→R RWw6(L)

Allowed

Not allowed

(Lower)

A6

R→M RWr6(L)

Allowed

(Upper)

27

M→R RWw6(H)

Allowed

Not allowed

(Upper)

A7

R→M RWr6(H)

Allowed

28

(Lower)

28

M→R RWw7(L)

Allowed

Not allowed

(Lower)

A8

R→M RWr7(L)

Allowed

(Upper)

29

M→R RWw7(H)

Allowed

Not allowed

(Upper)

A9

R→M RWr7(H)

Allowed

2A

(Lower)

2A

M→R RWw8(L)

Allowed

Not allowed

(Lower)

AA

R→M RWr8(L)

Allowed

(Upper)

2B

M→R RWw8(H)

Allowed

Not allowed

(Upper)

AB

R→M RWr8(H)

Allowed

2C

(Lower)

2C

M→R RWw9(L)

Allowed

Not allowed

(Lower)

AC

R→M RWr9(L)

Allowed

(Upper)

2D

M→R RWw9(H)

Allowed

Not allowed

(Upper)

AD

R→M RWr9(H)

Allowed

2E

(Lower)

2E

M→R RWw10(L)

Allowed

Not allowed

(Lower)

AE

R→M RWr10(L)

Allowed

(Upper)

2F

M→R RWw10(H)

Allowed

Not allowed

(Upper)

AF

R→M RWr10(H)

Allowed

30

(Lower)

30

M→R RWw11(L)

Allowed

Not allowed

(Lower)

B0

R→M RWr11(L)

Allowed

(Upper)

31

M→R RWw11(H)

Allowed

Not allowed

(Upper)

B1

R→M RWr11(H)

Allowed

32

(Lower)

32

M→R RWw12(L)

Allowed

Not allowed

(Lower)

B2

R→M RWr12(L)

Allowed

(Upper)

33

M→R RWw12(H)

Allowed

Not allowed

(Upper)

B3

R→M RWr12(H)

Allowed

34

(Lower)

34

M→R RWw13(L)

Allowed

Not allowed

(Lower)

B4

R→M RWr13(L)

Allowed

(Upper)

35

M→R RWw13(H)

Allowed

Not allowed

(Upper)

B5

R→M RWr13(H)

Allowed

36

(Lower)

36

M→R RWw14(L)

Allowed

Not allowed

(Lower)

B6

R→M RWr14(L)

Allowed

(Upper)

37

M→R RWw14(H)

Allowed

Not allowed

(Upper)

B7

R→M RWr14(H)

Allowed

38

(Lower)

38

M→R RWw15(L)

Allowed

Not allowed

(Lower)

B8

R→M RWr15(L)

Allowed

(Upper)

39

M→R RWw15(H)

Allowed

Not allowed

(Upper)

B9

R→M RWr15(H)

Allowed

3A 3A

(Lower)

BA

Setting HOLD/CLR information

Allowed

(Upper)

BB

(Not used)

Not allowed

(Not used)

Not allowed

BC BC

3E

3F

BE BF

R-IN32 Series CC-Link Remote device station 8. Memory Map

Table 8.4 When the Number of Occupied Stations is Set to 4

2

(Upper) 03

4

6

8

A

Description Read Write

Baud rate switch/number of occupied stations

Description Read Write

80

Allowed Not allowed (Upper) 83 Vendor code (Upper) Allowed Allowed

82

84

86

88

8A

8C

8E

90

92

94

96

98

9A

9C

(Not used) Not allowed Not allowed

9E

A0

A2

A4

A6

A8

AA

AC

AE

B0

B2

B4

B6

B8

BA

R18UZ0056EJ0102 Page 17 of 83 Dec. 28, 2018

MWR

When the transfer completes, the status is set to enable.

R-IN32 Series CC-Link Remote device station 8. Memory Map

8.2 Memory Map Details

8.2.1 Send Data Write Enable Information (CCS_MWRENL_RCEX)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

CCS_MWR

ENL_RCEX

R/W

Bit Position Bit Name Function 8 DCHANG

0 0 0 0 0 0 0

0 0 0 0 0 0 0 R 0 0 0 0 0 0 0 R

Receive data update information

DCH

0 0 0 0 0 0 0

ANG

ENL

0：No update

Receive buffer (byte address 08h - 39h, word address 08h - 38h) contains the same data as the previously read data. (Received new data during the previous read, or the read interval is shorter

than the refresh cycle.) 1：Update Newly received data is stored in the receive buffer .

(Even if the updated data is the same as the previously read d ata, if the receiv e buffer has been updated this bit becomes "1".)

For an asynchronous read, ensure that this bit is set to "1" before reading the

receive data.

0 MWRENL

Send data write enable information

0：Enable

Confirms that this bit is set to "0" and writes the send data into the update buffer.

1：Disable

Writing to the update buffer is disabled when this bit is set to "1" because the data is being transferred from the update buffer to the send buffer.

When the send data write completion flag (80h) is set to "1", the data transfer from the update buffer to the send buffer starts and the status is set to disable.

Address Initial

Value

400F B000H 0000H

R18UZ0056EJ0102 Page 18 of 83 Dec. 28, 2018

KYOKU1

KYOKU0

Number of Occupied Stations

0 0 1station

0 1 2 stations

1 0 3 stations

1 1 4 stations

BSW8

BSW4

BSW2

BSW1

Switch Setting

0 0 0 0 156 kbps

0 0 0 1 625 kbps

0 0 1 0 2.5 Mbps

0 0 1 1 5 Mbps

0 1 0 0 10 Mbps

hardware converts the 2-digit switch value from BCD to binary.

R-IN32 Series CC-Link Remote device station 8. Memory Map

8.2.2 Station Number Switch Information, Number of Occupied Stations Information and Baud Rate Switch Information (CCS_M3STNO_BSW_KYOKU)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

CCS_M3ST

NO_BSW_

KYOKU

R/W

Bit Position Bit Name Function 13-12 KYOKU1-

0 0

0 0 R R R R R R R R R R R R R R

KYOKU0

KYO

KU1

KYO

BSW

KU0

8

4

2

S7 S6 S5 S4 S3 S2 S2 S0 400F B002H

1

Number of occupied stations informatio n

Address Initial

Value

Undefined

11-8 BSW8-BSW1

7-0 S7-S0

Baud rate switch information

Station number switch information The station number setting switch value will be stored as binary code upon power up or the completion of the reset cycle.

Note that any value in the range from 0 to 99 (00h to 63h) is valid, because the

R18UZ0056EJ0102 Page 19 of 83 Dec. 28, 2018

1: CRC error

1: Timeout error

1: CRC error

1: Error (The setting has been changed from the settin g at power on.)

1: Setting error (Value other than 0 to 4 has been set)

1: Setting error (Value 0, 65 or greater has been set)

Remark

The error is cancelled when it returns to its normal condition.

R-IN32 Series CC-Link Remote device station 8. Memory Map

8.2.3 Error Information (CCS_M3ERR1_ERR2)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

CCS_M3ER

R1_ERR2

R/W

Bit Position Bit Name Function 10 ERR22

0 0 0 0 1

0 0 0 0 1 R R R 0 0 R R 0 0 R R

ERR

22

CRC error

21

ERR

20

0 0

BSE

RR

SSE

RR

0 0

BERR STE

0: Normal

Address Initial

400F B004H

RR

Value

Undefined

9 ERR21

8 ERR20

5 BSERR

4 SSERR

1 BERR

0 STERR

Timeout error 0: Normal

CRC error 0: Normal

Baud rate switch change error information 0: Normal

Station number setting switch change error information 0: Normal

Baud rate switch setting error information 0: Normal

Station number switch setting error information 0: Normal

R18UZ0056EJ0102 Page 20 of 83 Dec. 28, 2018

Transmission Words

0 0 0 0 0 word

0 0 0 1 32 words (64 bytes)

0 0 1 0 64 words (128 bytes)

0 0 1 1 96 words (192 bytes)

0 1 0 0 128 words (256 bytes)

0 1 0 1 160 words (320 bytes)

0 1 1 0 192 words (384 bytes)

0 1 1 1 224 words (448 bytes)

1 0 0 0 256 words (512 bytes)

Transmission Bits

0 0 0 0 0 bit 0 0 0 1

256 bits (32 bytes)

0 0 1 0 512 bits (64 bytes)

0 0 1 1 768 bits (96 bytes)

0 1 0 0 1024 bits (128 bytes)

0 1 0 1 1280 bits (160 bytes)

0 1 1 0 1536 bits (192 bytes)

0 1 1 1 1792 bits (224 bytes)

1 0 0 0 2048 bits (256 bytes)

1: Standby master station

1: Ver.2.**

1: Disable

R-IN32 Series CC-Link Remote device station 8. Memory Map

8.2.4 M → R Status Information (CCS_M3MRST1_ST2)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

CCS_M3M

RST1_ST2

R/W

Bit Position Bit Name Function 15-12 MST27-MST24

MST

27

26

25

24

23

22

21

R R R R R R R R R 0 R R R R R R

20

MST

17

MST

0

15

14

13

12

MST

11

MST27 MST26 MST25 MST24

Number of RWw

MST

Address Initial

400F B008H

10

Value

Undefined

11-8 MST23-MST20

7 MST17

5 MST15

4 MST14

MST23 MST22 MST21 MST20 Number of RY Information

0: Main master station

Protocol Version 0: Ver.1.**

Transient reception 0: Enable

R18UZ0056EJ0102 Page 21 of 83 Dec. 28, 2018

1: Yes

1: Abnormal

1: RUN

R-IN32 Series CC-Link Remote device station 8. Memory Map

Bit Position Bit Name Function

3 MST13 Transient

0: No

2 MST12 Refresh

0: No

1 MST11 Master station program

0: Normal

0 MST10 Master station program

0: STOP

R18UZ0056EJ0102 Page 22 of 83 Dec. 28, 2018

Remark

n = 0-7

Remark:

n = 0-15

R-IN32 Series CC-Link Remote device station 8. Memory Map

8.2.5 RY Reception Buffer (CCS_M3MRRY00_0F)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

CCS_M3M RRY00_0F

R/W

Bit Position Bit Name Function 15-0 Yn15-Yn0

YnE YnD YnC YnB YnA Yn9 Yn8 Yn7 Yn6 Yn5 Yn4 Yn3 Yn2 Yn1 Yn0

YnF

R R R R R R R R R R R R R R R R

RY reception buffer

Address Initial

400F B00AH

+2nH

Undefined

Value

8.2.6 RWwn Register (CCS_M3MRRWWn)

CCS_M3MR

RWWn

R/W

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

bnF bnE bnD bnC bnB bnA bn9 bn8 bn7 bn6 bn5 bn4 bn3 bn2 bn1 bn0

R R R R R R R R R R R R R R R R

Address Initial

400F B01AH

+2nH

Undefined

Value

Bit Position

15-0 Bn15-bn0

Bit Name Function

RWw (RWwn15-RWwn0)

R18UZ0056EJ0102 Page 23 of 83 Dec. 28, 2018

REQ

completed.

R-IN32 Series CC-Link Remote device station 8. Memory Map

8.2.7 Send Data Write Complete Flag and Receive Data Read Request (CCS_M3SDOK_RDRQ)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

CCS_M3SD

OK_RDRQ

R/W

Bit Position Bit Name Function 8 DRDREQ

0 0 0 0 0 0 0

0 0 0 0 0 0 0 R/W 0 0 0 0 0 0 0 R/W

<Write>

DRD

0 0 0 0 0 0 0

WPF

LG

Address Initial

Value

400F B080H

Upon reading the receive data, set this bit to "1", and upon completing the read, set it to "0". <Read>

The data written will be read.

Initial setting: 00H After initial setting: Writes 01h when starting to read reception data and writes 00h when reading is

0 WPFLG

<Write> Set the flag to "write" after completing data write to the update buffer. ( Write "01" as the data value.) When the flag becomes "write", the data transfer from the update buffer to the send buffer starts. (Caution 1) After writing all the data to be sent to th e update buffer at one time, set the flag to "write". (Caution 2) Setting this flag to "w rite" star ts sending and rec eiv ing. Ensure to set the flag to "write" after writing the initial dat a. <Read>

The flag becomes "1" as the "write" operation begins. When the data transfer to the send buffer completes, the flag becomes "0". Initial setting: Writes 01h when initial data setting has been completed during initial processing. (The communication will not start unless this operation is performed.) After initial setting: Writes 01h after transmission data is written to the CCS during transmission processing.

00H

R18UZ0056EJ0102 Page 24 of 83 Dec. 28, 2018

:

four digits consisti ng of the fifth to the eighth digits from the

If the ID number is 123-456-7890, the vendor code is 5678.

SFTV

1: Ver.2.**

:

corresponding code, contact the CC-Link Partner Association (CLPA).

R-IN32 Series CC-Link Remote device station 8. Memory Map

8.2.8 Vendor Code (CCS_M3VENDORCODE)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

CCS_M3VE

NDORCOD

R/W

Bit Position Bit Name Function

15-0 VENDOR15-0

VEN

DOR

15

14

13

E

R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W

12

DOR

11

10

Write the lower portion of the vendor code.

DOR

9

VEN

DOR

8

VEN

DOR

7

VEN DOR

6

VEN

DOR

5

VEN DOR

4

VEN

DOR

3

VEN

DOR

2

VEN

DOR0 400F B082H

DOR

1

Address Initial

Caution

The vendor code is obta ined from the ID number issued when a vendor joins the CC-Link Partner Association (CLPA). The beginning of the ID number constitute the vendor code. [Example]

8.2.9 Model Code and Version (CCS_M3MODELCODE_VERSION)

CCS_M3MO

DELCODE_V

ERSION

R/W

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

PRO

0

VER

ER5

ER4

ER3

ER2

0

0 R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W

ER1

ER0

MCO

DE7

MCO

DE 6

MCO DE 5

MCO

DE 4

MCO DE 3

MCO DE 2

MCO DE 1

MCO DE 0

Address Initial

400F B084H

Value

0000H

Value

0000H

Bit Position Bit Name Function 14 PROVER0

13-8

7-0 MODE7-

SFTVER5－ SFTVER0

MODE0

Protocol version 0: Ver.1.**

Software version information Initial setting：00 0001B

Model code Initial setting：For each model code, contact the CC-Link Partner Association.

Caution

The model code is defined by the CC-Link Partner Association (CLPA).

Write the model code specified in the "CC-Link Specification (Profile)". If there is no

R18UZ0056EJ0102 Page 25 of 83 Dec. 28, 2018

Baud Rate

TIM3

TIM2

TIM1

TIM0

First Time

10M

0→1→0

1 0 1

1677.7216ms

5M

0→1→0

1 0 1

1677.7216ms

2.5M

0→1→0

0 1 1

1677.7216ms

625k

0→1→0

0 0 1

1677.7216ms

156k

0→1→0

1 1 1

3355.4432ms

Baud Rate

TIM3

TIM2

TIM1

TIM0

First Time

10M

0→1→0

1 1 0

104.8576ms

5M

0→1→0

1 0 1

104.8576ms

2.5M

0→1→0

1 0 1

209.7152ms

625k

0→1→0

1 0 1

838.8608ms

156k

0→1→0

1 0 0

1677.7216ms

rate.

SLED3

SLED2

SLED1

SLED0

SDLED Illumination Time

0 - - - During transmission period

1 0 0 0 0.05 to 0.1ms

1 0 0 1 0.1 to 0.2ms

1 0 1 0 0.4 to 0.8ms

1 0 1 1 0.8 to 1.6ms

1 1 0 0 3.3 to 6.6ms

1 1 0 1 13.1 to 26.2ms

1 1 1 0 52.4 to 104.8ms

1 1 1 1 209.7 to 419.5ms

Initial setting：1111 (SDLED ON time: 209.7 to 419.5ms)

R-IN32 Series CC-Link Remote device station 8. Memory Map

8.2.10 SDLED Illumination Time Setting and Timeout Time Setting (CCS_M3SDLED_TOVER)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

CCS_M3SDL

ED_TOVER

R/W

Bit Position Bit Name Function 15-12 TIM3-TIM0

TIM3 TIM2 TIM1 TIM0 0 0 0 0

R/W R/W R/W R/W 0 0 0 0 R/W R/W R/W R/W 0 0 0 0

The time-over settings for the time up to first reception completion and the time after first reception completion need to be changed. 〈Initial setting time〉 Setting value until reception complete is set to ON for the first time after reset release or power ON

SLE

D3

SLE

D2

SLE

D1

SLE

0 0 0 0 400F B086H

D0

Address Initial

Value

0000H

7-4 SLED3-SLED0

〈Normal setting time〉 This is the timeout time setting value after completion of the initial data reception

Initial setting：The default time setting value is set to a value corresponding to the baud

R18UZ0056EJ0102 Page 26 of 83 Dec. 28, 2018

Caution1.

In the above figure, the setting value is written after "0" is written to bit 7 (SLED3).

2.

The timeout time is set using TIM0 to 2. The set value is confirmed at the TIM3 rising edge (0 →

Section 9.4, Timeout Time Setting Change.

R-IN32 Series CC-Link Remote device station 8. Memory Map

1). After the setting is set, change TIM3 back to 0. For setting procedure details, see

R18UZ0056EJ0102 Page 27 of 83 Dec. 28, 2018

M3R

21

M3R

20

M3R

Initial setting：00H

Caution

This bit is used in Version 2 only. For details of use, INT_CCV20 With Version 1, set the setting to "Fixed to 0".

R-IN32 Series CC-Link Remote device station 8. Memory Map

8.2.11 Cyclic Communication (CCS_M3RMST1_ST2)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

CCS_M3R

MST1_ST2

R/W

Bit Position Bit Name Function 15,14 M3RMST21,

MST

0 0 0 0 0 0 0 0

R/W R/W 0 0 0 0 0 0 0 0 R/W 0 0 0 0 0

MST1 0 0 0 0 0 400F B088H

Extended cyclic setting (setting of multiple)

M3RMST20

00: 1x setting

Address Initial

Value

00H

01: 2x setting 10: 4x setting 11: 8x setting

5 M3RMST1

Cyclic Communication 0: Cyclic communication enable 1: Cyclic communication disable

see Section 12.2, Initial Setting

and Section 12.4 Transmission/Reception Processing Module (ICCV20).

R18UZ0056EJ0102 Page 28 of 83 Dec. 28, 2018

Remark:

n = 0-7

Remark:

n = 0-15

R-IN32 Series CC-Link Remote device station 8. Memory Map

8.2.12 RX Update Buffer (CCS_M3RMRXn0_nF)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

CCS_M3R

MRXn0_nF

R/W

Bit Position Bit Name Function

15-0 Xn15-Xn0

XnF XnE XnD XnC XnB XnA Xn9 Xn8 Xn7 Xn6 Xn5 Xn4 Xn3 Xn2 Xn1 Xn0

W W W W W W W W W W W W W W W W

RX update buffer

Address Initial

400F B08AH

+2nH

Undefined

8.2.13 RWr Register (CCS_M3RMRWRn)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

CCS_M3R

MRWRn

R/W

Bit Position Bit Name Function

15-0 Xn15-Xn0

XnF XnE XnD XnC XnB XnA Xn9 Xn8 Xn7 Xn6 Xn5 Xn4 Xn3 Xn2 Xn1 Xn0

W W W W W W W W W W W W W W W W

RWr

Address Initial

400F B09AH

+2nH

Undefined

Value

R18UZ0056EJ0102 Page 29 of 83 Dec. 28, 2018

HOL

0h: CLR

Caution

:

The HOLD/CLR process holds or clears data received from the master station when an error, STOP, or timeout occurs on the master station application (master station controller). Determine the hold or clear process in accordance with device specifications, and execute the process using firmware.

R-IN32 Series CC-Link Remote device station 8. Memory Map

8.2.14 HOLD/CLR Register (CCS_M3HOLDCLR)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

CCS_M3H

OLDCLR

R/W

Bit Position Bit Name Function

0 HOLDCLR

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 R/W

HOLD/CLR Information Setting

DCLR 400F B0BA 0000H

Address Initial

Value

This bit notifies the master station of the HOLD or CLR setting of the HOLD/CLR process performed by firm ware. Set the information to be notified to the master station when an error, STOP, or time-over occurs on the master station application (master station controller), i.e., whether the device is to HOLD or CLR the data received from the master stati on. 1h: HOLD

R18UZ0056EJ0102 Page 30 of 83 Dec. 28, 2018

Initial setting

[1] Transmission speed [2] Station number [3] Vendor code [4] Model code [5] Version [6] SDLED ON time [7] Timeout time [8] RX area initialization [9] RWr area initialization

Send data write complete

Ready for reception

Initial setting

· Set [1] only when they are set by software.

· For setting [6], write "0" to SLED3 of CCS_M3SDLED_TOVER (SDLED ON time setting) and then write the "SD LED ON time".

· For setting [7], set the "initial setting time" that corresponds to the transmission speed to CCS_M3SDLED_TOVER（TIM3TOM0）, and write "0" to the lower 4 bits.

· Settings [8] and [9]: Clear the RX area and RWr area to 0.

Complete

· Transmission is enabled when "1" is written to CCS_M3SDOK_RDRQ(WPFLG bit) (send data write complete flag).

· Set the RS485 transceiver reception enable terminal

(RDENL) to "L" to enable reception.

R-IN32 Series CC-Link Remote device station 9. Sample Flowchart for CC-Link Version 1

9. Sample Flowchart for CC-Link Version 1

9.1 Initial Setting

After the initial setting process, execute Section 9.2, Main Processing.

Figure 9.1 Initial Processing

R18UZ0056EJ0102 Page 31 of 83 Dec. 28, 2018

R-IN32 Series CC-Link Remote device station 9. Sample Flowchart for CC-Link Version 1

9.2 Main Processing

When the reception processing is completed within 1 ms, execute the main processing as described in Section 9.2.1, Synchronous Read Met hod / Async hronous Write Method . When the reception processing is no t c ompleted within 1 ms, execute the main processing as described in Section 9.2.2, Asynchronous Read Method / Asynchronous Write Method.

9.2.1 Synchronous Read Method / Asynchronous Write Method

The following indicates an example of the main processing performed when the synchronous read method (see Section

9.3.1, Synchronous Read Method (Interrupt Pr ocessing)) is used during reception processing and the asynchronous write method (see Section 9.3.3, Asynchronous Write Method) is used duri ng transmiss ion proces s ing.

Perform rec eption processing b y connectin g the CCS_REFSTB o ut put of CCS to t he interr upt input of the microcomputer and using a rising edge interrupt.

Perform transmission processing based on timing of your own discretion.

When a timeout occurs, assess conditions based on the timeout error of CCS_M3ERR1_ERR2. ERR21 (error information).

R18UZ0056EJ0102 Page 32 of 83 Dec. 28, 2018

Main processing

Has a timeout occurred?

Reception processing

(see Section 9.3.1, Synchronous Read Method

(

Interrupt Processing

))

Hold/Clear processing of device

(see Section 8.2.14, HOLD/CLR register (CCS_M3HOLDCLR))

Timeout time setting change (see Section 9.4.2, Normal Setting Time → Initial Setting Time)

Device main processing

Transmission processing

(see Section 9.3.3, Asynchronous Write Method)

Yes

No

Interrupt

R-IN32 Series CC-Link Remote device station 9. Sample Flowchart for CC-Link Version 1

Figure 9.2 Synchronous Read Method / Asynchronous Write Method

R18UZ0056EJ0102 Page 33 of 83 Dec. 28, 2018

Main processing

Has a timeout occurred?

Reception processing

(see Section 9.3.2, Asynchronous Read Method)

Hold/Clear processing of device

(see Section 8.2.14, HOLD/CLR register (CCS_M3HOLDCLR))

Timeout time setting change (see Section 9.4.2, Normal Setting Time → Initial Setting Time)

Device main processing

Transmission processing

(see Section 9.3.3, Asynchronous Write Method)

Yes

No

R-IN32 Series CC-Link Remote device station 9. Sample Flowchart for CC-Link Version 1

9.2.2 Asynchronous Read Method / Asynchronous Write Method

The following indicates an example of the main processing performed when the asynchronous read method (see Section 9.3.2, Asynchronous Read Method) is used during reception processing and the as ynchronous write method (see Section 9.3.3, Asynchronous Writ e Method) is used during transmission processing.

When a timeout occurs, assess conditions based on the timeout error of CCS_M3ERR1_ERR2.ERR21 (error information).

Figure 9.3 Asynchronous Read Method / Asynchronous Write Method

R18UZ0056EJ0102 Page 34 of 83 Dec. 28, 2018

Synchronous read

method

Timeout time setting change (see Section 9.4.1, Initial Setting Time → Normal Setting Time)

Refresh data (RY and RWw)

error information and status

information read

· Read byte address 04h, 05h (error information 1, 2).

· For devices that check the status information (master station program status, etc.), read

CCS_M3MRST1_ST2 resister

(M → R status information ST1) as well. Execute HOLD/CLR processing based on the status content.

· Read: Read data in the order of RY → RWw.

· Because the timeout time before the link is established is different from that after the link is established, check whether or not reception is being completed for the first time and change the setting time the first time only.

Complete

Is this the

first time reception has been

completed?

No

Yes

R-IN32 Series CC-Link Remote device station 9. Sample Flowchart for CC-Link Version 1

9.3 Reception and Transmission Processing

When the read process is to be completed within 1ms, use the methods described in Section 9.3.1, Synchronous Read Method (Interrupt Processing) and Section 9.3.3, Asynchronous Write Method. When the read process is not to be completed within 1ms, use the methods described in Section 9.3.2, Asynchronous Read Method and Section 9.3.3, Asynchronous Write Me thod.

9.3.1 Synchronous Read Method (Interrupt Processing)

Connect the CCS_REFS TB output of CCS to the microcomputer interrupt input, and execute the read process using a rising-edge interrupt.

The write process can be executed in asynchronous write mode based on arbitrary timing.

Figure 9.4 Synchronous Read Method

The processing of an "interrupt" to "completion" has to be done within 1 ms.

(The next in terrupt might be ignored if processing does not finish within 1 ms.)

R18UZ0056EJ0102 Page 35 of 83 Dec. 28, 2018

· Confirm whether or not there is update data by reading CCS_M3SDOK_RDRQ.DRDREQ (receive data update presence information).

Asynchronous read

method

Is this the

first time reception has been

completed?

Timeout time setting change

(see Section 9.4.1, Initial Setting Time → Normal Setting Time)

Receive data read request set

Refresh data (RY and RWw)

error information and status

information

Receive data read request

reset

· Be sure to write "01" to byte address 81h (receive data read request) before reading the data.

· Read CCS_M3ERR1_ERR2

·

For devices that check status information (master station program status, etc.) , read CCS_M3MRST1_ST2 (M R status information ST1) as well. Execute HOLD/CLR processing based on the status content.

·

Read: Read data in the order of RY RWw.

· Be sure to write "0" to CCS_M3SDOK_RDRQ.DRDREQ (receive data read request) after the data has been read.

Complete

Is there update data?

Yes

No

R-IN32 Series CC-Link Remote device station 9. Sample Flowchart for CC-Link Version 1

9.3.2 Asynchronous Read Method

Figure 9.5 Asynchronous Read Method

R18UZ0056EJ0102 Page 36 of 83 Dec. 28, 2018

Asynchronous write

method

MWRENL

(Byte address 00h)

Data (RWr/RX) write

Send data write complete

0: Enable

1: Disable

· Check whether or not write is enabled by reading CCS_MWRENL_RCEX( MWRENL (MWRENL: send data write enable information).

· (0: Enable, 1: Disable)

· Collect and write the data to be sent in one communication process .

· Write: Write data in the order of RWr RX.

· After the data is written, write "1" to CCS_M3SDOK_RDRQ (WPFLG: send data write complete flag).

Complete

Caution

:

Whe During this period, CCS_MWRENL_RCEX.MWRENL does not become enabled.

R-IN32 Series CC-Link Remote device station 9. Sample Flowchart for CC-Link Version 1

9.3.3 Asynchronous Write Method

The written data is transmitted by the ne xt polling from the master.

Figure 9.6 Asynchronous Write Method

n the baud rate is 156Kbps, a maximum of 3.08ms is required for send processing.

R18UZ0056EJ0102 Page 37 of 83 Dec. 28, 2018

Timeout time setting

change

Complete

TIM3 TIM2～0

0 Baud rate

TIM3

TIM2～0

TIM3 TIM2～0

0

1

The value of TIM2 to TIM0 is set at the rising edge of TIM3.

・Return TIM3 to "0."

When you want to switch the timeout time to

"normal setting time," finish at the "Amount of Time until Timeout Time Is Set after First Reception" in the following table.

Baud rate

For the "normal setting time," set TIM0 to TIM2 in accordance with the transmission rate (baud rate) in the table below. Write "0" to TIM3. Write "0" to the lower 4 bits).

First Reception

10M

0→1→0

1 1 0

104.8576 ms

51 ms or less

5M

0→1→0

1 0 1

104.8576 ms

103 ms or less

2.5M

0→1→0

1 0 1

209.715 2ms

49 ms or less

625k

0→1→0

1 0 1

838.8608 ms

39 ms or less

156k

0→1→0

1 0 0

1677.7216 ms

13,000 ms or less

R-IN32 Series CC-Link Remote device station 9. Sample Flowchart for CC-Link Version 1

9.4 Timeout Time Setting Change

9.4.1 Initial Setting Time → Normal Setting Time

After the first data reception has been completed, change the timeout time setting from "initial setting time" to "normal

setting time" following the procedure below.

The following cases apply to "the first data reception" (i.e., the first time refresh data is received after power ON, reset

or timeout recovery):

(Synchronous read)

- When the first reception complete interrupt occurs as a result of CCS_REFSTB output (Asynchronous read)

- When "receive data update presence information" changes to "present" for the first time

Figure 9.7 Initial Setting Time → Normal Setting Time

Table 9.1 Normal Setting Time (Setting After First Reception Completion)

Baud Rate TIM3 TIM2 TIM1 TIM0 Timeout Time Amount of Time until Timeout Time is Set after

R18UZ0056EJ0102 Page 38 of 83 Dec. 28, 2018

Timeout time setting

change

Complete

TIM3 TIM2 to TIM0

0 Baud rate

TIM3 TIM2 to TIM0

0

1

The value of TIM2 to TIM0 is set at the rising edge of TIM3.

Return TIM3 to "0".

Baud rate

For the "normal setting time", set TIM0 to TIM2 in accordance with

the transmission rate (baud rate) in the table below.

Write "0" to TIM3.

Baud Rate

TIM3

TIM2

TIM1

TIM0

Timeout Time

10M

0→1→0

1 0 1

1677.7216 ms

5M

0→1→0

1 0 1

1677.7216 ms

2.5M

0→1→0

0 1 1

1677.7216 ms

625k

0→1→0

0 0 1

1677.7216 ms

156k

0→1→0

1 1 1

3355.4432 ms

R-IN32 Series CC-Link Remote device station 9. Sample Flowchart for CC-Link Version 1

9.4.2 Normal Setting Time → Initial Setting Time

After a timeout occurs, change the setting from "normal setting time" to "initial setting time". Set TIM0 to TIM3 to the

data (TIM3 = 1) corresponding to the transmission speed in the table below.

Figure9.8 Normal Setting Time → Initial Setting Time

Table 9.2 Initial Setting Time (Setting after Timeout)

R18UZ0056EJ0102 Page 39 of 83 Dec. 28, 2018

Link Input

Signal Name

Link Output

Signal Name

RXm0

RYm0

:

RXs0

RYs0

RXs1

RYs1

RXs2

RYs2

RXs3

RYs3

RXs4

RYs4

RXs5

RYs5

RXs6

RYs6

RXs7

RYs7

RXs8

Initial data processing request flag

RYs8

Initial processing complete flag

RXs9

Initial data setting complete flag

RYs9

Initial setting request flag

RXsA

Error status flag

RYsA

Error set request flag

RXsB

Remote ready (required)

RYsB

RXsC

RYsC

RXsD

RYsD

RXsE

RYsE

RXsF

RYsF

Remark

:

m s: Indicates the RX/RY system area occupied by the slave station.

R-IN32 Series CC-Link Remote device station 10. Remote Device Station Common Specification

10. Remote Device Station Common Specification

10.1 Cyclic Transmission Signals

10.1.1 Cyclic Transmission Signal Definit ions

The I/O points of the remote device station are divided into a user area and a system area. The final 16 bits of RX and RY are reserved as system areas.

The following lists the number of user area points according to the number of occupied stations. 1 occupied station: 16 bits 2 occupied stations: 48 bits 3 occupied stations: 80 bits 4 occupied stations: 112 bits

User area

: : :

System area

User area

Reserved

User area : : :

Reserved

: A number derived from the station number setting.

R18UZ0056EJ0102 Page 40 of 83 Dec. 28, 2018

Caution

:

This signal turns OFF when master station data transmission/reception with the user program is not possible due to an error.

RXsB

Enabled from this point

Power ON

Caution

:

Remote ready (RXsB) is turned ON after initial data processing is completed.

RXs

8

RYs8

RXsB

Enabled from this point

Initial data processing

R-IN32 Series CC-Link Remote device station 10. Remote Device Station Common Specification

10.1.2 System Area Details

(1) RXsB (Remote Ready)

Indicates that data transmission/reception is possible between the master station and user program of the remote device

station.

Turn this signal ON after power ON or hardware reset. Be sure to implement this signal.

Figure 10.1 RXsB (Remote Ready)

(2) RXs8/RYs8 (Initial Data Processing Request / Processing Complete Flag)

Used when the remote device station requests the user program to execute initial data processing after remote device

power ON or hardware reset.

Figure 10.2 RXs9/RYs9 (Initial Data Processing Request / Processing Complete Flag)

R18UZ0056EJ0102 Page 41 of 83 Dec. 28, 2018

Caution

:

RXs9/RYs9 (initial data setting complete / setting request flag)

RYs9

RXs9

RXsB

Enabled from this point

Initial data setting

RXs8

RYs8

RXsB

RYs9

RXs9

Initial data processing

Initial data setting

Enabled from this point

R-IN32 Series CC-Link Remote device station 10. Remote Device Station Common Specification

(3) RXs9/RYs9 (Initial Data Setting Complete / Setting Request Flag)

Used when the master station user program requests the remote device station to execute initial data setting.

Figure 10.3 RXs9/RYs9 (Initial Data Setting Complete / Setting Request Flag)

(4) When Both RXs8/RYs8 and RXs9/RYs9 are Implemented

When both RXs8/RYs8 and RXs9/RYs9 are implemented, turn RYsB (remote ready) ON after both initial d a ta

processing and initial data setting are completed.

Figure 10.4 When Both RXs8/RYs8 and RXs9/RYs9 are Implemented

R18UZ0056EJ0102 Page 42 of 83 Dec. 28, 2018

:

An error reset request clears the error as well as the error code storage area. Note, however, that the device number of the error code storage area is co Remote ready (RXsB) is turned OFF from error occurrence to error reset.

RXsA

RYsA

Disabled from this point (error occurrence)

RXsB

Enabled from this point

Error clearance in progress

Error occurrence notification

Error cleared

R-IN32 Series CC-Link Remote device station 10. Remote Device Station Common Specification

(5) RXsA/RYsA (Error Status / Reset Request Flag)

Used for error notification/clear ing when an error other than a watch dog timer error occurs in the remote device

station.

Caution

ntrolled by the remote device.

Figure 10.5 RXsA/RYsA (Error Status / Reset Request Flag)

R18UZ0056EJ0102 Page 43 of 83 Dec. 28, 2018

Link Register

Signal Name

Link Register

Signal Name

RWrm0

User-defined area

RWwm0

User-defined area

RWrm1

RWwm1

RWrm2

RWwm2

RWrm3

1 station occupied

RWwm3

1 station occupied

RWrm4

RWwm4

RWrm5

RWwm5

RWrm6

RWwm6

RWrm7

2 stations occupied

RWwm7

2 stations occupied

RWrm8

RWwm8

RWrm9

RWwm9

RWrm10

RWwm10

RWrm11

3 stations occupied

RWwm11

3 stations occupied

RWrm12

RWwm12

RWrm13

RWwm13

RWrm14

RWwm14

RWrm15

4 stations occupied

RWwm15

4 stations occupied

R-IN32 Series CC-Link Remote device station 10. Remote Device Station Common Specification

10.2 Remote Register

The all areas of the remote registers of a remote device station are user-defined areas. Note that m is a register number assigned to each remote station.

Table 10.1 Remote Registers

R18UZ0056EJ0102 Page 44 of 83 Dec. 28, 2018

R-IN32 Series CC-Link Remote device station 11. Overview of CC-Link Ver. 2

11. Overview of CC-Link Ver. 2

This chapter explains the specifications necessary to design CC-Link remote device stations compatible with CC-Link

Version 2.

This chapter describes only the contents related to Version 2 development. For detailed specifications regarding the

CCS, see the other chapters.

[Hardware] Since the hardware structure for CC-Link Version 2 is basically identical to that of Version 1, this document contains

only the notes for development of CC-Link Ver s ion 2-compatible remote device stations.

[Software (Firmware)] Protocol related to CC-Link Version 2 must be constructed in software (fir mware). This document contains notes as

well as sample flowcharts for developing CC-Link Version 2-compatible remote device stations.

R18UZ0056EJ0102 Page 45 of 83 Dec. 28, 2018

Version 2

Version 1

RWw/RWr: 2048 words

RWw/RWr: 256 words

RWw/RWr: 8 to 32 words

RWw/RWr: 4 words

RWw/RWr: 16 to 64 words

RWw/RWr: 8 words

RWw/RWr: 24 to 96 words

RWw/RWr: 12 words

RWw/RWr: 32 to 128 words

RWw/RWr: 16 words

Number of occupied stations per machine

1 to 4

Extended cyclic setting

1×, 2×, 4×, 8× (1

)

None

:

When 1 and Then, don’t use 1 setting of Ver.2, use Ver.1 communication mode.

RWw/RWr: 4 words

RWw/RWr: 8 words

RWw/RWr: 12 words

RWw/RWr: 16 words

RWw/RWr: 8 words

RWw/RWr: 16 words

RWw/RWr: 24 words

RWw/RWr: 32 words

RWw/RWr: 16 words

RWw/RWr: 32 words

RWw/RWr: 48 words

RWw/RWr: 64 words

RWw/RWr: 32 words

RWw/RWr: 64 words

RWw/RWr: 96 words

RWw/RWr: 128 words

R-IN32 Series CC-Link Remote device station 11. Overview of CC-Link Ver. 2

11.1 Characteristics of CC-Link Ver. 2

11.1.1 Extended Cyclic

The capacity of cyclic data per station can be increased by using extended cyclic.

Table 11.1 Extended Cyclic

Maximum number of links (Data volume) RX/RY: 8192 bits

Number of links per machine (Data volume)

1 station occupied RX/RY: 32 to 128 bits

2 stations occupied RX/RY: 96 to 384 bits

3 stations occupied RX/RY: 160 to 640 bits

4 stations occupied RX/RY: 224 to 896 bits

×

Note

RX/RY: 2048 bits

RX/RY: 32 bits

RX/RY: 64 bits

RX/RY: 96 bits

RX/RY: 128 bits

Note

setting is set in Version 2, the header information for extended cyclic does not exist,

frame and data amount are identical to Version 1.

Table 11.2 Relationship between the number of occupied stations and extended cyclic setting in CC-Link

Version 2

Stations 1 Station Occupied 2 Stations Occupied 3 Stations Occupied 4 Stations Occupied

1× Setting RX/RY: 32 bits

2× Setting RX/RY: 32 bits

4× Setting RX/RY: 64 bits

8× Setting RX/RY: 128 bits

RX/RY: 64 bits

RX/RY: 96 bits

RX/RY: 192 bits

RX/RY: 384 bits

R18UZ0056EJ0102 Page 46 of 83 Dec. 28, 2018

RX/RY: 96 bits

RX/RY: 160 bits

RX/RY: 320 bits

RX/RY: 640 bits

RX/RY: 128 bits

RX/RY:224 bits

RX/RY:448 bits

RX/RY: 896 bits

:

When the number of remote device stations connected is the same as the number of occupied stations.

No. of Occupied Stations

Amt. of Cyclic Data

RWw/RWr: 16 words

RWw/RWr: 32 words

RWw/RWr: 16 words

R-IN32 Series CC-Link Remote device station 11. Overview of CC-Link Ver. 2

11.1.2 Less Occupied Stations

Table 11.3 Relationship between number of occupied stations and number of connected modules

No. of Occupied Stations

No. of connected modules of remote device station per master

Note

1 Station Occupied 2 Stations Occupi ed 3 Stations Occupied 4 Stations Occupied

42 modules 32 modules 21 modules 16 modules

Note

Table 11.4 Version 1 and Version 2 No. of Occupied Stations / Amt. of Cyclic Data

CC-Link Version 2 1 occupied station, quadruple setting RX/RY: 64 bits

1 occupied station, octuple setting RX/RY: 128 bits

CC-Link Version 1 4 occupied stations RX/RY: 128 bits

When the extended cyclic setting of a Version 2 system with 1 oc c upie d station is "quadruple", the number of bit data points hand led is the same as that of a CC-Link Version 1 system with four occupied stations. When the setting is "octuple", the amount of word data handled is the same as that of a CC-Link Version 1 system wit h four occupied stations.

It is therefore possible to realize the same amount of data using a lesser number of occupied stations and, consequently, increase the number of remote sta tions controlled by a single master station.

R18UZ0056EJ0102 Page 47 of 83 Dec. 28, 2018

First division

[Transmission]

[Reception]

RWw8~ B

RWw0~ 3 RWw4~ 7

RWw

RY30~ 3F

RY00~ 0F

ST3

SQ

RY

RY30~ 3F

RY00~ 0F

RY

RY10~ 1F RY20~ 2F

RY40~ 4F RY50~ 5F

RWw

RWwC~ F

RWr8~ B

RWr0~ 3 RWr4~ 7

RWr

RX30~ 3F

RX00~ 0F

ST3

SQ

RX RX

RX10~ 1F RX20~ 2F

RX40~ 4F RX50~ 5F

RWr

RWrC~ F

Master station data Slave station dataData area on frame

RWw8~ B

RWw0~ 3 RWw4~ 7

RWwC~ F

RX30~ 3F

RX00~ 0F RX10~ 1F RX20~ 2F

RX40~ 4F RX50~ 5F

RWr8~ B

RWr0~ 3 RWr4~ 7

RWrC~ F

Second division

[Transmission]

[Reception]

~ 3

~ B ~ F

~ 3

~ B ~ F

~ 0F

~ 3F

ST3 SQ

RY

~ 0F

~ 3F

RY ~ 4F ~ 5F

~ 4F ~ 5F

~ 1F ~ 2F

~ 7

~ 3

~ B

~ F

~ 3

~ B

~ F

~ 0F

~ 3F

ST3

SQ

RX

~ 0F

~ 3F

RX ~ 4F ~ 5F

~ 4F ~ 5F

~ 1F ~ 2F

RWr

~ 7

Master station

data

Slave station

data

Data area on

frame

Polling & refresh

Response

....

Master station

Transmission

Reception

Polling & refresh

Response

....

RWw0

RWw8 RWwC

RY00

RY30 RY40 RY50

RY10 RY20

RWw4

RWr0

RWr8 RWrC

RX00

RX30 RX40 RX50

RX10 RX20

RWr4

RWw0

RWw8

RWwC

RY00

RY30 RY40 RY50

RY10 RY20

RWw4

RWr0

RWr8 RWrC

RX00

RX30 RX40 RX50

RX10 RX20

RWr4

RWw RWw

RWr

R-IN32 Series CC-Link Remote device station 11. Overview of CC-Link Ver. 2

11.2 Overview of Protocol

11.2.1 Overview of Extended Cyclic Communicati on

"Extended Cyclic" to be added in Version 2 splits refresh data (RY, RWw) and response data (RX, RWr) into multiple

link scans, and sends/receives data. The following shows a general description of the communication.

Figure 11.1 With 2 Occupied Stations and Extended Cyclic 2 × Setting

R18UZ0056EJ0102 Page 48 of 83 Dec. 28, 2018

F

A 1

A

2

S T 1

S

T 2

DATA

C R C

F

Basic Frame Format

Master station → Slave station

Slave station → Master station

b7

b0

Master station user 0: stop Application 1: run Master station user 0: Normal Application 1: Error Refresh 0: Stop

1: Start

Transient 0: Absent

1: Present

Transient reception 0: Disable

1: Enable

Protocol version 00: Ver.1.**

01: Ver.2.** 10: Ver.3.**

(For future use)

11: Ver.4.**

(For future use)

Data link* running 0: Master station station 1: Standby master station

* Valid only between the master station and the standby master station

b7 b0

Fuse blown

0: No error

1: Error Unit error/invalid points 0: Absent 1: Present Refresh not received 0: Received 1: Not received Parameter not

0: Received

received

1: Not received Switch change 0: No change detected 1: Changed Cyclic communication

0: Enable

1: Disable

Invalid if a version error occurred

Reserved

WDT error 0: Not detected 1: Detected

No changes since Version 1

b7 b0

RY information transmission points

0000:

0

bits

0001:

256

bits

0010:

512 bits

1000:

2048 bits

1001 ~ 1111:

Reserved

RWw information transmission points

0000:

0 bits

0001:

32 bits

0010:

64 bits

1000:

256 bits

1001 ~ 1111:

Reserved

No changes since Version 1

b7 b0

Transient data 0: Absent

1: Present

Transient reception 0: Disable

1: Enable

Transient type 0: 1:n

1: n:n

Reserved

Transmission route 0: No error status 1: Error Reserved 1: Fixed

Extended cyclic setting 00: 1 x setting *

(Version 2) 01: 2 x setting

10: 4 x setting 11: 8 x setting

* Version 1 specification (without extended cyclic function)

R-IN32 Series CC-Link Remote device station 11. Overview of CC-Link Ver. 2

11.2.2 Transmission of Own Station Information

CC-Link Vers ion 2 uses bits ST1 and S T2 in the transmission fr ame, which were reserved in Vers ion 1, to transmit protocol version information (master station → slave station) and extended cyclic setting information (slave station → master station).

Also, in the slave station test loopback data, highest 2 bits in the RV area are used for protocol version information (slave station → master station).

Table 11.5 Details of ST1 and ST2 in Version 2

ST1

ST2

R18UZ0056EJ0102 Page 49 of 83 Dec. 28, 2018

TP

R V

F F

F

A1A

2

S T 1

S

T 2

VD

Loopback

test data

(4 bytes)

C R C

F F F

Slave station test loopback data

Slave station → Master station

b7

b0

Software version

Protocol version

0000:: VVeerr..11..**** 0011:: VVeerr..22..**** 1100:: VVeerr..33..**** ((FFoorr ffuuttuurree uussee)) 1111:: VVeerr..44..**** ((FFoorr ffuuttuurree uussee)

)

R-IN32 Series CC-Link Remote device station 11. Overview of CC-Link Ver. 2

Table 11.6 Details of RV in Version 2

RV

R18UZ0056EJ0102 Page 50 of 83 Dec. 28, 2018

Polling &

refresh

....

Cycle adjustment

RY

(Ver.1)

RY

Station 1 Station 2

Station 3 Station 4

......

RY

RWw

Station 64 Station 1

......

S T 3

S Q

RYST

3

S Q

RY

....

Response

....

S T 3

S Q

RX RWr

A 1

A 2

S T 1

S T2RY Area RWw Area

CR

C

A 1

A 2

S T 1

S T2RX Area RWr Area

CR

C

Master station

Transmission

Reception

Cyclic data section

Header

information

Header

information

R-IN32 Series CC-Link Remote device station 11. Overview of CC-Link Ver. 2

11.2.3 Extended Cyclic Header Information

In Version 2 , header in formation provides for the hands haking between the master and slave statio ns for the divided data. The header information uses the first 16 bits of the data area in the transmission frame. This corresponds to the section in the frame used as RY00-0F and RX00-0F in Version 1. This frame section is now referred to as header information in Version 2, containing "ST3" and "SQ", each of which consists of 8 bits. ST3 is reserved for future expansion and is not used in Version 2.

Figure 11.2 Extended Cyclic Header Information

R18UZ0056EJ0102 Page 51 of 83 Dec. 28, 2018

ST1 ST2

RY

(4 bytes when 1 occupied station)

RWw

(8 bytes when 1 occupied station)

ST3 SQ

RY

(2 bytes when 1

occupied station)

RWw

(8 bytes when 1 occupied station)

Version 1 or earlier

Ver. 2

Same as Version 1 ST1, ST2

Not used

LoopbackSQReception

SQ

Upper 4

bits

Lower 4

bits

M R data (reception data) frame

One data set is completed by 2 to 8 data receptions.

Checks this Reception SQ value, and performs reception operation.

This area is divided into 2 to 8 parts and received

With 1 occupied station 4 mode, X/Y: 16 4 = 64 bits,

RWr/w: 4 4 = 16 words

R-IN32 Series CC-Link Remote device station 11. Overview of CC-Link Ver. 2

(1) Details of SQ Value

(a) M → R DATA

"Reception SQ": This indicates the order of data transmitted from the master station.

"Loopback SQ": This is loopback information containing the SQ value tr a nsmitted in the previous Remote s ta tion to Master station transmission. The reception status of the master station can be monitored by checking the continuity of this data.

If a reception error by the master station is detected, it is possible to resend the data again from the first packet. (The resending of data from the first pac ket f unction is optional and is not required. )

Figure 11.3 Details of SQ Value (M → R Data)

R18UZ0056EJ0102 Page 52 of 83 Dec. 28, 2018

ST1

ST2

RX

(4 bytes when 1 occupied station)

RWr

(8 bytes when 1 occupied station)

Version 1 or earlier

ST3

SQ

RX

(2 bytes when 1

occupied station)

Ver. 2

This area is divided into 2 to 8 parts and transmitted

RWr

(8 bytes when 1 occupied station)

Same as Version 1 ST1, ST2

Not used

Loopback

SQ

Transmission

SQ

Upper 4

bits

Lower 4

bits

R → M data (reception data) frame

One data set is completed by 2 to 8 data receptions.

R-IN32 Series CC-Link Remote device station 11. Overview of CC-Link Ver. 2

(b) R → M DATA

"Transmission SQ": This indic ate s the o rder of data transmitted to the master station.

"Loopback SQ": This is loopback information containing the SQ value received in the previous Master station to Remote station transmission. The master station monitors this d a ta a s the remote station’s recep tion status. If the continuity of this loopback SQ value i s lost, the master station decides that the remote station is not receiving data correctly, and retransmits data star ting from SQ (Number of divisio ns – 1). Since the master station checks the loopback SQ value for remote station reception continuity, this SQ loopback function is mandatory on remote stations.

Figure 11.4 Details of SQ Value (R → M Data)

R18UZ0056EJ0102 Page 53 of 83 Dec. 28, 2018

3

*

Split in 4

......

*

3

* 2

3 2

3 1

2 1

2 0

1

0

1 3

3

2

Decrement 1

1

0

3

0 2

3 2

3 1

Transmission

Reception

SQ number

Loopback

SQ

Transmission SQ

R-IN32 Series CC-Link Remote device station 11. Overview of CC-Link Ver. 2

Split transmission:Tr a nsmission starts with the [(Trans mission SQ number of Divisions) –1], and is decremented until it becomes 0. This indicates the end of split transmission. The loopback SQ number will contain the received and acknowledged Transmission SQ number.

Split reception:The split reception data is recombined when the transmission SQ number equals zero. Continuity of the SQ numbers is checked. (Redundant receptions are discarded.)

Figure 11.5 Details of SQ Value (Loopback)

R18UZ0056EJ0102 Page 54 of 83 Dec. 28, 2018

RWw+18

RWr+18

RWw+19

RWr+19

RWw+1A

RWr+1A

RWw+1B

RWr+1B

RWw+1C

RWr+1C

RWw+1D

RWr+1D

RWw+1E

RWr+1E

RWw+1F

RWr+1F

RWw+10

RWr+10

RWw+11

RWr+11

RWw+12

RWr+12

RWw+13

RWr+13

RWw+14

RWr+14

RWw+15

RWr+15

RWw+16

RWr+16

RWw+17

RWr+17

RWw+8

RWr+8

RWw+9

RWr+9

RWw+A

RWr+A

RWw+B

RWr+B

RWw+C

RWr+C

RWw+D

RWr+D

RWw+E

RWr+E

RWw+F

RWr+F

RWw+0

RWr+0

RWw+1

RWr+1

RWw+2

RWr+2

RWw+3

RWr+3

RWw+4

RWr+4

RWw+5

RWr+5

RWw+6

RWr+6

RWw+7

RWr+7

R-IN32 Series CC-Link Remote device station 11. Overview of CC-Link Ver. 2

11.3 Relationship between SQ Values and RX/RY, RWr/RWw

The relationship between SQ values and RX/RY or RWr/RWw is shown below.

[Example with 2 occupied stations at 4× setting]

The SQ values are transmitted and received in the descending order. Furthermore, the transmitted/received message content (RX/RY and RWr/RWw) is stored in the descending order.

Table 11.7 Relationship between SQ Values and RX/RY, RWr/RWw

Reception

SQ = 3

Reception

SQ = 2

Reception

SQ = 1

RY90 to RYBF

RY60 to RY8F

RY30 to RY5F

Transmission

SQ = 3

Transmission

SQ = 2

Transmission

SQ = 1

RX90 to RXBF

RX60 to RX8F

RX30 to RX5F

Reception

SQ = 0

RY0 to RY2F

Transmission

SQ = 0

RX0 to RX2F

R18UZ0056EJ0102 Page 55 of 83 Dec. 28, 2018

Variable Name

Application

CC20_RECEIVE

Indicates that reception is complete

CC20R_DONE

Indicates that a single data reception is complete

CC20S_DONE

Indicates that a single data transmission is complete

R_ZEN_SQ

Previously received Reception SQ value

R_NOW_SQ

Currently received Reception SQ value

S_ORI_SQ

Loopback SQ value to be tra n smi tted next

S_NOW_SQ

Transmission SQ value to be transmitted next

R_ZOR_SQ

Previously received loopback SQ value

CCS Register/Port

Application

CCS_M3SDOK_RDRQ

CCS offset address 80h (Send data write complete flag)

RDENL

Reception ready flag

Variable Name

Application

CC20_RECEIVE

Indicates that reception is complete

CCS Register/Port

Application

CCS_M3SDOK_RDRQ

Send data write complete flag (400F B080H)

Variable Name

Application

CC20_RECEIVE

Indicates that reception is complete

CCS Register/Port

Application

CCS_M3SDOK_RDRQ

end data write complete flag (400F B080H)

CCS_REFSTB

CCS_REFSTB signal for the CCS

R-IN32 Series CC-Link Remote device station 12. Sample Flowchart for CC-Link Version 2

12. Sample Flowchart for CC-Link Version 2

12.1 List of Modules and Variables

(1) INT_CCV2: Initial Processing

(2) CCS_REFSTB: Interrupt Processing

(3) ITIM:1ms Interrupt Processing

R18UZ0056EJ0102 Page 56 of 83 Dec. 28, 2018

Variable Name

Application

CC20_RECEIVE

Indicates that reception is complete

CC20R_DONE

Indicates that a single data reception is complete

CC20S_DONE

Indicates that a single data transmission is complete

R_ZEN_SQ

Previously received Reception SQ value

R_NOW_SQ

Currently received Reception SQ value

S_ORI_SQ

Loopback SQ value to be transmitted next

S_NOW_SQ

Transmission SQ value to be transmitted next

R_ZOR_SQ

Previously received loopback SQ value

CCS Register/Port

Application

CCS_M3SDOK_RDRQ

Send data write complete flag (400F B080H)

CCS_M3MRST1_ST2

M→R status information (400F B008H)

M3RM_SSQ

CCS offset address 8Bh (R → M SQ) (400F B08BH)

M3MR_SSQ

CCS offset address 0Bh (M → R SQ) (400F B00BH)

CCS_MWRENL_RCEX

Receive data update information (400F B000H)

Variable Name

Application

CC20R_DONE

Indicates that a single data reception is complete

CC20S_DONE

Indicates that a single data transmission is complete

R-IN32 Series CC-Link Remote device station 12. Sample Flowchart for CC-Link Version 2

(4) ICCV20: Transmission/Reception Processing

(5) CHK20DONE: (Application Work Area Transfer Processing Module)

R18UZ0056EJ0102 Page 57 of 83 Dec. 28, 2018

R-IN32 Series CC-Link Remote device station 12. Sample Flowchart for CC-Link Version 2

12.2 Initial Setting INT_CCV20

After initial setting completion, execute Section 12.3, Transmission/Reception Processing.

Figure 12.1 Initial Setting INT_CCV20

R18UZ0056EJ0102 Page 58 of 83 Dec. 28, 2018

R-IN32 Series CC-Link Remote device station 12. Sample Flowchart for CC-Link Version 2

12.3 Transmission/Reception Processing

12.3.1 Example Using an Interrupt (CCS_REFSTB Signal)

The following shows an example of transmission/reception processing in CC-Link Version 2 that utilizes an interrupt at the rising/falling of t he CCS_REFS TB signal of the CCS.µ

Figure 12.2 Transmission/Reception Processing Using Interrupt (CCS_REFSTB Signal)

R18UZ0056EJ0102 Page 59 of 83 Dec. 28, 2018

100

s

or less

ITIM

(

1

ms interrupt

)

Save registers

,

etc

.

Unit internal processing for 1ms interrupt (

Application processing)

ICCV

20

Transmission

/

Reception processing

(

Refer to Section

12

.

4

.)

After recovering the

registers, IRET

ICCV

20

Transmission

/

Reception processing

(

Refer to Section

12.

4

.)

CHK

20DONE

Application work area transfer

processing

(

see Section

12

.

5

.)

CHK20DONE

Application work area transfer

processing (see Section

12.5.)

CCS

_

MWRENL

_

RCEX

.

DCHANG

!=

0

CC-Link update?

Yes

No

Yes

No

M3RCEX & 0x01 != 0

CC-Link update?

Reception complete flag ON

CC20_RECEIVE ← 1

CCS_REFSTB falling

detected?

Has the receive

data been read?

CC20_RECEIVE != 0

Yes

No

CCS transmission complete flag ON CCS_M3SDOK_RDRQ.WPFLAG ← 1 (Data written into CCS becomes ready

for transmission)

Reception complete flag OFF

CC20_RECEIVE ← 0

CCS_REFSTB falling detection flag

OFF

Yes

Reception complete flag ON

CC20_RECEIVE ← 1

CCS_REFSTB

falling detected?

Has the receive

data been read?

CC20_RECEIVE != 0

Yes

No

CCS transmission complete flag ON CCS_M3SDOK_RDRQ.WPFLAG ← 1 (Data written into CCS becomes ready

for transmission)

Reception complete flag OFF

CC20_RECEIVE ← 0

CCS_REFSTB falling detection flag

OFF

No

Yes

No

Execution time 400 to 750 s

100 s or less

R-IN32 Series CC-Link Remote device station 12. Sample Flowchart for CC-Link Version 2

12.3.2 Example of Polling

The following shows an example of transmissio n/re c e ption processing in CC-Link Version 2 that performs polling processing at an interval of 1ms or less using a timer. The processing in the two areas enclosed by dotted lines are identical. In this example, "t rans mi ss io n SQ" and "loopback SQ" can be transmitted/re c e ived without fail by polling before and after the pol ling interval, assuming that the processing time within the unit is constant .

Polling condition:

When using polling, execute the processing so that incompletion does not occur even with the shortest link scan time.

The shortest link scan time is the time required for one remote device station (1 occupied station) to be connected to the master station (transmission spe e d 10Mbps). Since the fastest link scan time at this point is approx. 1.1ms, polling must be done at intervals of 1ms or less.

Figure 12.3 Transmission/Reception Using Polling

R18UZ0056EJ0102 Page 60 of 83 Dec. 28, 2018

ICCV20

CCS_M3MRST1_ST2.

MST15=0?

(Master station version =1)

Yes

CCS_M3MRST1_ST2.

MST1 ← 1

Set cyclic transmission

to ENABLE.

No

return

Warning output OFF

Warning output ON (If version discrepancy is detected, some warning is output)

CCS_M3MRST1_ST2.

MST1 ? 1

Set cyclic transmission

to DISABLE.

If invalid, set all RX and RWr to 0

Set Transmission SQ value to 0

M3RM_SSQ←0

Transmission complete flag ON

CCS_M3SDOK_RDRQ.WPFLG? 1

Reception data request OFF

CCS_M3SDOK_RDRQ.DRD

RQ? 0

Other initialization

such as work area

initialization

A ←M3MR_SSQ B ←A & 0fh (Retrieve lower 4 bits) R_NOW_SQ ←B (Store current SQ value) S_ORI_SQ ←B (Store loopback SQ value) R_ORI_SQ ← (A >> 4) & (divisions - 1) (Get upper 4 bits)

Is this the

first time reception has been

completed?

No

Yes

B

Timeout time

setting change

... see Section 8.2.4

... see Section

8.4.1.

R-IN32 Series CC-Link Remote device station 12. Sample Flowchart for CC-Link Version 2

12.4 Transmission/Reception Processing Module (ICCV20)

The following indicates the pr ocessing called during interrup t or polling based transmission/recep tion processing.

Figure 12.4 Transmission/Reception Processing Module (ICCV20)

R18UZ0056EJ0102 Page 61 of 83 Dec. 28, 2018

No

R_

NOW

_SQ > divisions -1?

If the SQ value skipped and the previous SQ value was set, the fact that SQ value skipped may be lost if, for instance, SQ = 3 did not arrive and then same SQ is repeated, such as 2 2. In other words, 3 is lost and 2 2 1 0 or 3 and 2 are lost and 1 1 0 will both be perceived as correct values.

Yes

(Same received data

as the previous one)

Previous SQ value

= (current SQ value +1)

(R_ZEN_SQ=R_NOW_SQ +1)

No

(not matched)

Previous Reception

SQ value = current Reception SQ

value?

R_ZEＮ_SQ==R_NOW_SQ?

No

(Skipped data

or data lost)

Is current

Reception SQ value 0?

(Completed a data set?)

R_NOW_SQ==0?

No

(Middle of

a data set)

Previous Reception SQ value

current Reception SQ value R_ZEN_SQ R_NOW_SQ

Yes

(1 data set completed)

To

transmission

processing

Discard the received data as is (No transfer from MFP3N)

CC20R_DONE 1 (Reception data complete. The transmission flag is set ON. This flag is checked and cleared at CHK20DONE)

Current SQ value = (divisions -1)?

R_NOW_SQ == divisions -1?

No

Always receive the first time data

Previous Reception SQ value

current Reception SQ value R_ZEN_SQ R_NOW_SQ

Previous SQ value updating processing

Previous Reception

SQ value 0

R_ZEN_SQ 0

Current SQ

value is (divisions -1) or less?

R_NOW_SQ < divisions -1?

Yes

Receive first time data and store in CC-Link Version 2.0 work area

Receive the second data and subsequent, and store it in CC-Link Version 2.0 work area

Although the master station sends the same ST1 and ST2 for SQ = 3 to 0, the remote station side reads constantly to ensure timeliness in case of an error

B

Please note that when an SQ value far greater than expected was received, if the value is not checked at this point, comparison against the previous SQ value may set to the proper value due to subsequent processing.

YES

Yes

(matched)

R-IN32 Series CC-Link Remote device station 12. Sample Flowchart for CC-Link Version 2

Figure 12.5 Transmission/Reception Processing Module ICCV20 (Continued 1)

R18UZ0056EJ0102 Page 62 of 83 Dec. 28, 2018

To

transmission

processing

return

Deduct the transmission SQ value by 1

S_NOW_SQ S_NOW_SQ-1

Yes

No

Set the Transmission SQ value to (divisions - 1) S_NOW_SQ (divisions - 1)

Switch to new data

Transmission SQ value = 0?

S_NOW_SQ==0?

(Upper 4 bits: Loopbacks the received SQ value Lower 4 bits: Stores the SQ value to be transmitted by a remote station)

To avoid transmitting incomplete data, write the transmission SQ value at the very end.

Transfer data according to the SQ value from the CC-Link Version 2.0 work area to CCS buffer

Transfer RX and RWr that correspond to the transmission SQ to CCS as the transmission data

Is transmission SQ value 0?

S_NOW_SQ==0?

CC20S_DONE 1 (Indicate that transmission of one data set is complete, and prepare the next data in CHK20DONE) (This work area is checked and cleared in CHK20DONE)

Yes

No

Loopback check *1

*1 If a Loopback check is to be performed, add the flowchart for loopback check on the next page.

Fail

R-IN32 Series CC-Link Remote device station 12. Sample Flowchart for CC-Link Version 2

Figure 12.6 Transmission/Reception Processing Module ICCV20 (Continued 2)

R18UZ0056EJ0102 Page 63 of 83 Dec. 28, 2018

Point

[Loopback check]

the expanded cyclic setting is 4x or less.)

Yes

work3 R_ORI_SQ+1 work3 = work3 & (divisions -1)

work3=R_ZOR_SQ?

(work3 = previous transmission

loopback SQ?)

Although there is no way of detecting a missed packet and retransmitting it, unnecessary link scans can be avoided during normal communication

No

R_ORI_SQ = R_ZOR_SQ?

(Loopback SQ = previous Loopback SQ?)

Missing data is detected only after 2 link scans; therefore, new data transmission does not start at the first and second data transfer.

Yes

(Transfer new data)

Previous Loopback

SQ = 0

R_ZOR_SQ 0

Previous loopback SQ value =

Loopback SQ value

R_ZOR_SQ R_ORI_SQ

R_ORI_SQ == divisions - 1?

(Loopback SQ = divisions - 1?)

Yes

No

In the case of "divisions - 1" (which is 7 in 8x mode), this must always be accepted since data may be retransmitted by the local station.

If the value is identical to the previous Loopback SQ value, there is a possibility that the processing on the counterpart side did not make it on time, which means the correct Loopback may be received in the next communication. Therefore, this is OK.

S_NOW_SQ<=6

No

Loopback

check

To OK

transmission

processing

To Fail

transmission

processing

No

R-IN32 Series CC-Link Remote device station 12. Sample Flowchart for CC-Link Version 2

Transmission/Reception Processing Module ICCV20 (Continued 3) This processing chec ks the loopback SQ and decides whether or not retransmission is to be performed.

Implement this processing in the 8x expanded c yclic setting mode. (The process does not need to be implemented when

Figure 12.7 Transmission/Reception Processing Module ICCV20 (Continued 3)

R18UZ0056EJ0102 Page 64 of 83 Dec. 28, 2018

Accumulated received

data for one whole frame?

CC20R_DONE!=0?

Transfer from CC-Link Version

2.0 buffer to application buffer

Yes

RET

CHK20DONE

CC20R_DONE 0

Already transmitted

the transmission data for

one whole frame?

CC20S_DONE!=0?

Transfer from application buffer to CC-Link Version 2.0 buffer

Yes

No

CC20S_DONE 0

No

R-IN32 Series CC-Link Remote device station 12. Sample Flowchart for CC-Link Version 2

12.5 Application Work Area Transfer Processing Module CHK20DONE

Figure 12.8 Application Work Area Transfer Processing Module CHK20DONE

R18UZ0056EJ0102 Page 65 of 83 Dec. 28, 2018

R-IN32 Series CC-Link Remote device station 13. Notes on Developing with CC-Link Version 2

13. Notes on Developing with CC-Link Version 2

13.1 Hardware

Basically, hardware structures for Versions 2 and 1 are the same. Nonetheless, please note on the following points.

(1) Version 2 Work Area

When in the Extended Cyclic setting (nx), data is transmitted/received by dividing it into n packets. Therefore, it is necessary to store the data for n packets in a memory buffer and read/write all the data together. To avoid losing part or all of the data, design the buffer in a way that all data packets for n transmissions/receptions can be read or written in one operation.

(2) Switching

Though thi s i s unnecessary for Version 2-dedicated remote device stations, if both Version 2 and Version 1 protocols are to be supported, a switch may be required in order to toggle between Version 2 and Version 1.

(3) Polling Processing

To avoid missing a Transmission SQ from the master station, polling processing must be performed at an interval less than 1ms. T o achieve thi s , the CCS_REFSTB interrupt signal can be used, or an interrupt can be initiated by a timer, etc.

For details, see Section 12.3, Transmission/Reception Processing.

(4) Transmission Processing

In Version 1, writing to CCS transmission buffer could be done at any time, but in Version 2, the timing of writing to the transmission buffer is critical. All of the polling processing described above needs processing to validate the data written after turning ON the CCS transmission data write complete (offset address 0080h: M3SDOK) after triggered by the falling of the CCS_REFSTB signal. Therefore, design the hardware so that it can positively detect the falling of the CCS_REFSTB signal. For example, use an MP U that can handle interrupt triggers or embed the falling of t he CCS_REFSTB signal into an interrupt using external logic.

For details, see Section 13.3, Write Timing at Transmission.

R18UZ0056EJ0102 Page 66 of 83 Dec. 28, 2018

R-IN32 Series CC-Link Remote device station 13. Notes on Developing with CC-Link Version 2

13.2 Software (Firmware)

Since the CCS does not i nclude any protocol related to Version 2, such protocol must be written into the software (firmware). The following describes the items to be developed.

(1) Master Station Version Checking

At the time of normal reception, check bits 5, 6 "Protocol Version" of CCS_M3MRST1_ST2 register.

If the protocol version is Version 1, set M3RMST1 bit "Cyclic communication" of CCS_M3RMST1_ST2 register to disable.

(2) Reception Processing

The timing of RY/RWw data read is the same as that of Version 1.

For example, when the e xt ended cyclic setting is quadruple, the SQ values are received four times in the order of 3 → 2 → 1 → 0.

The four segments of RY/RWw data are treated as one set of data.

(3) Loopback Che c king at Recept ion (Optional)

If the loopback SQ values are monitored and continuity is broken, new data is transmitted from the beginning. Except for 8× setting, transmitting new data from the remote side is less effective (transmission delay time actually becomes greater), so exercise caution during implementation.

(4) Loopback Processing at Transmission

Loop back the SQ values received from the master station at the time of transmission.

The master st ation checks the co ntinuity of the looped back SQ val ues, and if the continuity is broken, assesses that the data was not transmitted normally, aborts the current data transmission and se nds new data.

At the time of transmission, normal data will not be sent from the master station unless the SQ values have been processed. Be sure to loop back all reception SQ values without fail.

R18UZ0056EJ0102 Page 67 of 83 Dec. 28, 2018

refresh data is received during refresh & single station polling.)

next polling.

:

System configuration with the shortest link scan time

・

(For the system configuration described above, the link scan time is about 1.1 ms).

R-IN32 Series CC-Link Remote device station 13. Notes on Developing with CC-Link Version 2

13.3 Write Timing at Transmission

Completing the processes (1) and (2) described below in a period of time between the rising of a CCS_REFSTB s i gnal and the risi ng of a next CCS_REFSTB signal serves to maintain the co nt inuity of the looped back SQ value s .

If the continuit y o f the looped back SQ values is broken, the master station will assess that the slave station has not correctly received the data and then send data in packets from the beginning again. Therefore, be sure to complete the processes (1) and (2) within the time between the rising of a CCS_REFSTB signal and the rising of a next CCS_REFSTB signal.

(1) After confirming the completion of rec eption processing by the rise of a CCS_REFSTB signal, set the

received SQ from the master station as a loopback SQ and then writes the send data (from [fraction number – 1] to 0) to the update buffer sequentially. (The CCS_REFSTB signals should rise when

(2) After completing the process (1), check the falling of a CCS_REFSTB signal and then turn ON the

send data write complete (CCS_M3SDOK_RDRQ). (CCS_REFSTB signals should fall after a refresh cycle has been completed). With the process (2) above, what is stored in the CCS update buffer will be transferred to the send buffer to be used for transmission and then sent to the master station in the

Note

Transmission rate: 10 Mbps Slave station: A single remote device station (the number of stations occupied: 1)

In summary, the transmission rate of looped back SQ val ues should satisfy the following t hree conditions:

・Process (1) + Process (2) ≤ Shortest link scan time (about 1.1 ms)

・Process (1) should take place after the rising of a CCS_REFSTB signal.

・Process (2) should take place after Process (1) has been completed and after the falling of the CCS_REFSTB signal.

R18UZ0056EJ0102 Page 68 of 83 Dec. 28, 2018

Dummy signal

1

station polling

&

refresh

2

stations

polling

1 station

response

2 stations response

...

Refresh

cycle end

(2) After completing Process (1),

turn ON the send data write complete

flag (M3SDOK) during this time.

Monitor the interrupt request signal of MPU using polling.

Monitor CCS reception buffer

update flag using polling

CCS update

buffer

Write

transmission

data from

MPU

CCS

transmission

buffer

Transmit to the master station during the next

frame circle

Link scan time

(1) Create data to be sent next and transfer the data to CCS update buf fer during this time.

M3SDOK ON

1 station polling &

refresh

CCS_REFSTB

Master station

transmission

Remote station

transmission

R-IN32 Series CC-Link Remote device station 13. Notes on Developing with CC-Link Version 2

Figure 13.1 Link Scan Time and CCS_REFSTB Signal Change

R18UZ0056EJ0102 Page 69 of 83 Dec. 28, 2018

master station to the Version 2 work area in n segments.

CCS every n link scans.

scans.

n link scans.

RY/RWw

application work

area

CCS

Master station

RX/RWr

Version

2 work

area

Transfer every

4 link scans

For every link scan

RX/RWr

application work

area

RY/RW

w

Version

2 work

area

Transfer every

4 link scans

For every link scan

Microcomputer RAM area

Application

work area

Area where the application can asynchronously read/write

Exclusive control is necessary to avoid colliding with the transferring that takes place every 4 link scans

Version 2

work area

Area where only the CC-Link Version 2 processes can access For each link scan, corresponding SQ values are transmitted and received

SQ = 3 area SQ = 2 area SQ = 1 area SQ = 0 area

For every link scan

Remote device station

CASE2

CASE1

CASE3

CASE4

R-IN32 Series CC-Link Remote device station 13. Notes on Developing with CC-Link Version 2

13.4 Handling CC-Link Version 2 Work Area

When the extended cyclic setting is the multiple n, ensure that data is transmitted and received between the Version 2 work area and CCS every link scan. The data communicated between CCS and the master station must be updated every link scan.

(1) Write application work area data (RX/RWr) to be transmitted from the remote device station to the

(2) When writing data from the Version 2 work area to CCS, be sure to divide and transfer the data to

(3) When reading the data (RY/RWw) to be received from CCS to the Version 2 work area, from the

master station to the remote device station, be sure to divide and transfer the data to CCS every n link

(4) When transferring data from the Versi on 2 work area to the application work area, hold the data of the

To guarantee data integrity between the master station and remote device stations, make sure the hardware design follows the structure below. (A memory size that supports the multiple n extension is required.)

Figure 13.2 Example of 4x Setting

R18UZ0056EJ0102 Page 70 of 83 Dec. 28, 2018

Question

Answer

Can they be substituted with other parts

with the same specifications?

packaging. There is thus no problem in using RD6.2Z-T1B.

Question

Answer

other LEDs.

two LEDs (RUN and ERRL)?

panels?

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

14. Questions & Answers

14.1 Circuit Design in General

(1) Questions and Answers Related to Specified Parts

1 Is it mandatory to use CC-Link specified

parts?

2 While it is specified to use the RD6.2Z-T2B

Zener diodes, can we use -T1B rather than

-T2B?

The specified parts are essential to maintaining the performance of CC-Link; please use the specified parts.

The RD6.2Z-T1B can also be used. The RD6.2Z-T2B and -T1B Zener diodes are, in fact, the same Zener diode products; the only difference is the direction of the device taping of the mold

(2) Questions and Answers Related to LEDs

1 Are any colors specified (or recommended) for

the transmission monitor LEDs?

2 In the circuit example, four LEDs (RUN,

ERRL, SDLED, and RDLED) are used for displaying the status. Is it all right to use only

3 Are there any limitations on the size of

characters printed on LED displays and

There is no special specification. We use red LEDs for our units. With the products by other manufacturers, the most frequently used colors seem to be red for the ERR LED only and green for

It is recommended to use four LEDs whenever possible to monitor the link status. However, if this is not possible due to the mounting conditions, etc., it is all right not to use them.

There are no limitations on the size of characters printed on the LED displays and panels.

R18UZ0056EJ0102 Page 71 of 83 Dec. 28, 2018

Question

Answer

bottom surface of the station.

specification pose any problems?

should be released.

possible to insert and remove the connector.)

S-3011A switches made by Copal.)

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

(3) Questions and Answers Related to Switches, Connectors, and Terminal Blocks

1 Does it pose any problems if we place the

switches for setting the station number and the baud rate (rotary switch) in a place other than on the panel surface? We are planning to place the station number setting switch on the rear surface (installation surface) and the baud rate setting switch on the

2 Regarding the setting of the station number

We are planning to fix the station number instead of using a rotary s witch. Does this

3

Could the station number be set by software? There is no register to set the station number directly.

<R>

There are no restrictio ns on th e sw itch layout . If it is difficult to plac e a group of the setting switches at one place, place them in different locations.

According to the CC-link standard, the station number should be freely configurable. <R>

Station number is set by pin setting of "station number setting switch input terminal (CCS_STATION_NO_0-CCS_STATION_NO_7)". When no switch is mounted, it is possible to set the station number by connecting the pins of "station number sett ing switch input terminal" to any general-purpose ports and setting the station number from the general-purpose port by softwar e . After setting the station number, the reset of CC-Link block

4 We want to install a communication connector

(RS485) on the bottom surface of the station. Does this pose any problems? (We will make it

5 There is no specification for the external form.

Can we decide the following as we like? [1] The shape, layout, color, and size of the LEDs [2] The type of connectors (we are considering the use of Conbicon connectors made by Phoenix.) [3] The size and type of rotary and dip s witches (we are considering the use of

It is all right to layout the connector as you like.

There is no specification for parts except the specified parts. [1] Any design can be used for the LEDs. [2] Use 2-piece connectors. If 2-piece connectors cannot be used, please specify in your manual that this product cannot be replaced in the link operation status (without shutting down the entire link). (Online connection and disconnection are not possible.) [3] Any design can be used for the switches.

R18UZ0056EJ0102 Page 72 of 83 Dec. 28, 2018

Question Answer

initialization?

thinking so?)

being processed)

the operation manual in such cases.

order of RWr → RX as well?

enable signal of RX and RWr information initial settings during initializatio n?

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

14.2 Software

(1) Questions and Answers Related to Initial Processing

1 We have a question about the initial setting in

the sample flowchart . Should the RS485 reception enable signal be set to H only at

Set it to "H" at initialization, and keep it high afterwards.

2 We perform the following softwar e processing

for the initial processing. Word address (1) CCS_M3VENDORCODE = 0x0119 (2) CCS_M3MODELCODE_VERSION = 0x0120 (3) CCS_M3SDLED_TOVER = 0xf200 (4) CCS_M3SDLED_TOVER = 0xf2f0 (5) CCS_M3SDOK_RDRQ = 0x0101 However, in step 5 above, SDLED is not lit even though the WRFLG bit is set to 1 (there is no output from the SD terminal of the CCS, either. It maintains the H level). If CCS_M3SDOK_RDRQ register is read after this, the value 0x0100 has been stored. This means that the transfer to the send buffer must have been completed. (Are we correct in

3 Which takes priority, an ini tial proc essing

request or error status request? (Assuming a request is generated while another request is

When the CCS_M3SDOK_RDRQ.WPFLG bit is set to 1, data is transferred between the double buffers for transmission (send buffer and update buffer). During the transfer, the MWRENL send data write enable informati on of CCS_MWRENL_RCEX.MWRENL is set to 1. CCS_M3SDOK_RDRQ.WRFLG and CCS_MWRENL_RCEX.MWRENL are set to 0 when the transfer from the send buffer to the update buffer is completed. No data is transmitted from the CCS (causing SDLED to be lit) unless polling data from the master station is received. If data was read after the CCS_M3SDOK_RDRQ.WRFLG bit was set to "1" and the bit is changed to "0", the data transfer from the send buffer to the update buffer has been completed.

As a general rule, priori ty should be given to error status requests. However, this rule does not apply if it would cause deadlock in the operation of the developed device. Please specify the operation in

4 The specifications indicate that initialization of

initial settings occurs in the order of RX information followed by RWr information. In the asynchronous write method flowchart, however, the specifications indicate that the settings are to be written in the order of RWr

RX. Can initialization be performed in the

→

5 Do we need to verify the transmission data

R18UZ0056EJ0102 Page 73 of 83 Dec. 28, 2018

During initialization, RX and RWr information may be initialized in either order.

The data link is not established during RX and RWr information initialization; there is no need to verify the signal.

Question

Answer

any operations necessary for the CCS?

are no operations necessary for the CCS.

note, such as timing?

is not necessary to disconnect it, we would lik e

do not connect the MPU port output to GND.

Question

Answer

Note that your company must take care of the version control.

3rd byte: Model type

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

(2) Questions and Answers Related to Reception Enable

1 What does reception enable mean? Are there

2 The specifications describe a precaution on

RS485 transceiver reception as "the receive enable pin of the RS485 transceiver is controlled". Are there any particular points to

3 The MPU port output is connected to the

RDENL line connected to the RS485 transceiver. Under what circumsta nc es mig ht the communication input be disconnected? If it

to connect the MPU port output to GND.

Reception enable means allowing RS485 to receive data. There

Enable the transceiver reception after enabling transmission during the initial settings. It can be kept enabled afterwards.

Data reception from the master station should be disabled until the initial processing is completed (the communication input is disconnected). The reception should then be enabled after the initial processing is completed. After that, it is not necessary to disable the reception. Since it is necessary to disable the reception before the initial processing is performed, make sure to use the MPU port output;

(3) Questions and Answers Related to Version and Model Code

1 Which version should be written to byte

address 85h of the CCS? Is it the version on the user side?

CCS_M3MODELCODE_VERSION is an area where the version information of your product (i.e., the CC-Link product you develop) should be written. Write 01h for version "A" and 02h for version "B", and update the contents every time you upgrade the product.

2 Regarding the model code at initialization

processing Does the model code consist of the following three bytes? 1st byte: Station information 2nd byte: Unit information

R18UZ0056EJ0102 Page 74 of 83 Dec. 28, 2018

The 3-byte model data is transmitted via the transmission path. However, the data of the 1st and 2nd bytes are supplied by the CCS. It is only the data of the 3rd byte that your company must specify.

Question

Answer

after resetting?

SLED3 are set to "1111" in our products.

itten to byte address 86h SDLED

also be rewritten. Does this pose any problems?

wait time required?

performed?

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

(4) Questions and Answers Related to SD LED

1 Doesn't SDLED turn on unless the SDLED

lighting time is written to byte address 86h? Does it turn on even if the period remains 00h

2 The specifications indicate that 0 must be written

to the 7th bit, and the SDLED lighting time must then be written in order to set the SDLED lighting time. If data is wr lighting time setting using 16 bits, however, the data in byte address 87h initial setting time must

3 The specifications indicate that the SDLED time

setting is to be set after writing "0" to bit 7, but is a

4 If there is no change in the SDLED time setting

from the initial value (Fh), does the process of writing "1111" after writing "0" need to be

If 00h is stored after resetting, the SDLED turns on only during the "transmission period". With this setting, the SDLED can scarcely be seen to light up in practice. By default, SLED0 to

Rewriting does not pose any problems.

The time setting can be written immediately after writing "0" to bit 7. A wait time is not particularly required.

If there has been no change from the initial value, the process of writing "1111" after writing "0" is not required.

R18UZ0056EJ0102 Page 75 of 83 Dec. 28, 2018

Question

Answer

products.

bit is canceled? Are other bits also canceled?

g error) and BERR (baud rate

error information cannot be communicated to the master station.

the master station is shut down.

transmission path or CCS is reset.

is not started, so timeout errors will not occur.

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

(5) Questions and Answers Related to Errors

1 Are there any processing flowcharts that can

be used as a reference when handling errors? Are there any standard charts?

2 The explanation of the BSERR bit of

CCS_M3ERR1_ERR2 of the CCS states that "the error is canceled when it returns to normal". Does this mean that only the BSERR

3 Should errors also be generated in SSERR

and STERR of CCS_M3ERR1_ERR2?

4 What does the ERR21 timeout error of

CCS_M3ERR1_ERR2 mean?

Errors must be handled for each device as required. It is not possible to determine standard processing; p lea se hand le errors according to the specification and communication status of your

The STERR and BERR must be restarted after setting the station number and baud rate within the valid range. The SSERR and BSERR become normal by returning their settings to the original settings when the power was turned on.

It is not necessary to generate device errors when SSERR (baud rate switch change error information) and STERR (station number setting switch change error information) are turned on. In the case of SSERR and BSERR, it is not necessary to generate errors as data is linked normally with the status before change. (The ERR LED flashes on remote stations only.) Moreover, in the case of STERR (station number switch settin switch setting error), data cannot be linked normally; thus, the

It turns on if refresh data cannot be received w ithin the tim eo ut time specified by the baud rate when the line is disconnected or

5 What is the meaning of ERR22 channel carrier

detection of CCS_M3ERR1_ERR2?

6 Can timeout errors occur if the power to the

master station is not turned on?

A carrier refers to a change in signal level on a transmission path of CC-Link communication. The carrier is used to detect whether or not communication has been normally performed between the master station and remote device station. When a carrier is not detected on the transmission path within the carrier monitoring time (3.28ms for 10Mbps), an error occurs. The status changes to normal when either a carrier is detected on the

Timeout is checked for the period from the time polling data is received to the time the next polling data is received. This means that polling data has not been received at all if the master station

R18UZ0056EJ0102 Page 76 of 83 Dec. 28, 2018

Question

Answer

should be written after reading is completed.

Is it possible to read multiple bytes (words)?

synchronous read?

(in the same ways as CCS_REFSTB)?

CCS_REFSTB.

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

(6) Questions and Answers Related to Reception Data read Processing

1 When reading data, do we just need to set 01

in CCS_M3SDOK_RDRQ (write 01 to CCS_M3SDOK_RDRQ)? Must we set it back to 0 after reading the data?

2 The specification indicates, upon reading the

reception data, that the DRDREQ bit of CCS_M3SDOK_RDRQ should be set to 1; and upon completing the read operation, it should be reset to 0. Is this operation necessary when reading one byte (half word)?

3 Is it necessary to turn on DRDREQ (reception

data read request) of byte address 81h at

4 Is it correct that the DCHANG bit of

CCS_MWRENL_RCEX notifies that data has been updated? Currently the software on the device side is halted, the programmable controller CPU is in the STOP status, the RD and RUN LEDs are lit, and the SD LED flashes. In this status, DCHANG is set to 1. At this point, we set DRDEQ to 1 (at this point DCHANG changes to 0) in order to read the receive buffer and return DCHANG to 0. Then DCHANG immediately changes to 1. Why does this happen, even though the progr ammabl e controller CPU is in the STOP status? Is DCHANG updated regardless of the operation of the programmable controller CPU

CCS_M3SDOK_RDRQ , reception data read requ est, is used to secure data consistency by preventing the link data from being overwritten by the master station while reading the receive buffer. As described in the flowchart in the specificat io ns, the val ue 1 should be written to this address before reading data, and 0

The number of data points read can be any number of bytes. The DRDREQ bit is a flag used in the reception data s eparation prevention processing. Data transfer between the double receive buffers within the CCS is prevented when it is set to 1.

It is not necessary. Synchronous reading, however, must be completed within 1 ms.

The DCHANG signal receives new refresh data and notifies that it is stored in the receive buffer by being set to "1" (it is also set to "1" when the same data is refreshed). Normally, refresh data is received successively while the link is active. Therefore, "1" is continuously written to bit 0 of CCS_MWRENL_RCEX (the DCHANG signa l) as well. The CC-Link master station continues to perform the link refresh operation when the link is started even if the programmable controller CPU is in the STOP status (RY, however, becomes 0).

5 The explanation of the DCHANG bit of

CCS_MWRENL_RCEX says "for an asynchronous read, ensure that this bit is set to '1' before reading the receive data". We think reading should be performed upon checking that the DCHANG register is set to 1 even when an interrupt is received via

R18UZ0056EJ0102 Page 77 of 83 Dec. 28, 2018

We do not intend to limit the usage, but it is not necessary to check DCHANG at a synchronous read using CCS_REFSTB, i.e., pin 40 of the CCS. It is acceptable to check DCHANG at a CCS_REFSTB interrupt, but make sure to keep the processing time within 1 ms.

Question

Answer

completed?

Question

Answer

failure?

(first time reception) → (normal setup time)?

always be detectable during normal periods.

set. Specifically, what is this process?

that baud rate.

switch is changed?

time.

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

6 When a link is established after the initial

processing is completed, the reception data update information is always set to on, even when the programmable controller CPU is in the STOP status. Since interrupts are always received as well, it is not possible to perform normal processing. How can we know that data writing is

(7) Timeout Processing

1 The timeout time setting switches based on

whether it is (the first time), but: (1) Please clarify the definition of (the first time). (2) Is (the first time) when recovery occurs after communication was attempted but regarded as not possible due to some type of

The reception data update information indicates that data is written to the buffer and turns on at every link scan. It has nothing to do with whether or not the actual data has c hanged. Perform handshaking with the master station using a separate remote input/output (RX and RY). In the case of devices that do no require reading programmable controller's data all the time, you should not use interrupts, but use the asynchronous read method instead.

(1) The first time is when initialization processing is performed after power ON or reset cancel or after recovery from communication discontinuity. (2) The first time is as described above; it does not occur in a case where a failure other than communication discontinuity, such as a data packet error, occurs.

2 Why is the processing in which the software

writes to TIM0-3 with reference to the baud rate switches BS1-8 during timeout time setup performed for (initialization write operation) →

3 The specifications indicate that the timeout

time setting should be set in accordance with the baud rate when the initialization time is

4 Do we always need to monitor the value of the

baud rate switch for the timeout time setting? Should we always update the timeout time setting in accordance with the baud rate if the

The reason is as follows: Until normal reception occurs for the first time, a longer time than usual is required. If the timeout time is set to a short time, "timeout" will always occur the first time. Conversely, if the timeout time is remains long, timeout may not

When setting the initiali zation time of timeout time settings, read the value of the baud rate switch of the byte address 03H after power ON or reset, and set the timeout time in accordance with

You do not need to always monitor the baud rate switch value for the timeout time setting. If the baud rate switch is chan ged d uring Link-Run, the setting is assessed for the first time at the rise after reset or power OFF/ON. Change the timeout time setting at that

R18UZ0056EJ0102 Page 78 of 83 Dec. 28, 2018

Question

Answer

processing is performed in each device.

transferred to the send buffer?

station side?

access to the same port and register?

processing necessary?)

memory map?

handler?

possible to read from them but not to write to them .

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

(8) Others

1 Could you tell us the processing flow of

existing products (i.e., software processing procedure)?

2 Is the latest data always transmitted if the data

update period is shorter than the response period during an asynchronous write operation? Or does it depend on the timing at which data written to the update buffer is

3 Does the CCS send a remote station refresh

response data frame asynchronously with the refresh data update interval on the remote

4 Are there any restrictions on continuous

5 There is a description regarding

CCS_M3SDOK_RDRQ of the CCS, stating to write a collection of data to be sent simultaneously in a single communication to the update buffer and then write the data. What is the upper limit of the transmission amount? Also, does writing to the update buffer mean writing data to any address (wherever you want to store the data)? (Is any other

The basic processing is as described in the sample flowchart. In the event that the master station user application stops, generates an error, or pauses to refresh, the HOLD/CLR output

The latest data is always transmitted.

Yes, it is asynchronous.

There are no special restrictions.

Data must be written to byte addresses 82h to 87h (vendor code, model code, version, etc.) and BAh (HOLD/CLR information setting) at the initial processing and CCS_M3RMRXn0_nF (RX) and CCS_M3RMRWRn (RWr) at normal data transmission. Data is written to the areas above as necessary at data transmission. The range varies depending on the number of occupied stations (the upper limit is the occupied data).

6 Is it possible to obtain the status equivalent to

the "RUN" signal of pin 62 of the CCS ? For example, is it possible to obtain the same status for the "SQSTOPL" signal on the

7 In the sample applicati on flowchart, data is

read within the interrupt handler via pin 40 of the CCS_REFSTB. Are there any problems in using it to read data outside the interrupt

8 Is it true that ST1 and ST2 of

CCS_M3RMST1_ST2 are identical to those of CCS_M3MRST1_ST2?

There are no signals that are completely synchronized. If a link is started at normal operation, DCHANG of CCS_M3SDOK_RDRQ turns on at each link scan; please substitute with this.

There will be no problems as far as data is read within 1 ms.

They are different. CCS_M3RMST1_ST2 represent the status of the master station. CCS_M3MRST1_ST2 represent the status of remote stations, and data is stored in them by the CCS. It is

R18UZ0056EJ0102 Page 79 of 83 Dec. 28, 2018

Question

Answer

is not necessary

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

9 Can you explain about CCS_M3MRST1_ST2

of the CCS?

MST10 indicates the RUN/STOP status of the master station user application, MST11 indicates the normal/abnormal status of the master station user application, and MST12 indicates the information of the link refresh status. Perform the HOLD/CLR processing of outputs on the device side according to this information. MST13 and MST14 contain information about the transient transmission. MST15 and MST16 contain the protocol version of the master station. MST17 contains informati on about the standby master station; use

R18UZ0056EJ0102 Page 80 of 83 Dec. 28, 2018

Question

Answer

restarted automatically when problems are solved.

"disconnection" state?

exceeds the specified value.

displaying the information before the shutdown.

the entire network but there is no information for each station.

RX(m+n)A is ON?

continues.

request RY(m+n)A?

operation at this time in the user's manual.

R-IN32 Series CC-Link Remote device station 14. Questions & Ans wers

14.3 Protocol and Others

(1) Questions and Answers Related to Errors

1 What is the exact definition of

"disconnection"?

2 On what should we base our assessment of a

3 We know that there are timeout errors, but

what is the definition of the timeout error?

4 What is the definition of "temporary error

invalid stations"?

It means that a data link error occurs and a station is disconnected from the data link. Automatic return means that the data link is

A timeout error.

It occurs when the time from the completion of refresh normal reception to the time of normal reception of the next refresh

By specifying some of the link status special relays (SB) and link special registers (SW) of the master station as temporary error invalid stations, it is possible to exclude the stations specified as temporary error invalid stations from being detected as stations in the error status, even if they are down. By using this function, it is possible to replace modules without causing link errors (the power to the modules to be replaced must be turned off). The specification of temporary error invalid stations does not require parameters; it can be changed online. If any temporary error invalid stations are down (the power is turned off), the outputs from the master station are turned off while the inputs are maintained; it is possible to replace them while

5 Is the log of each station saved when a

communication error occurs? How about the number of retri es?

6 Is it possible to receive the next request

(command) when the error s tatus flag

7 What happens if the error reset request flag

RY(m+n)A is turned on when an error state continuously occurs?

8 When an error state continues or multiple

errors occur, can we set remote station READY RX(m+n)B to ON using the error reset

The information log of each station is not saved when a communication error occurs. The real time information of each station is written to the link special register (SW), but it simply indicates the bit status and is cleared when the error is canceled and the station recovers and returns to the system. To leave the information in the log, it is necessary to save it with a program on the master station side every time the status changes. The number of retries is saved for

Yes, it is possible. Execute the request (command).

The error reset request flag is always executable. When executed in such a state, the error status flag turns OFF, but then turns ON again since the request (command) to generate an error

Turn remote station Ready ON after clearing all error conditions (states), unless a deadlock is to occur for the operation convenience of the developed device. Clearly describe the

R18UZ0056EJ0102 Page 81 of 83 Dec. 28, 2018

Question

Answer

we do not set RX(m+n)A to "1"?

transmission is not possible.

indicated in the manual.

Is the terminating resistor disconnected?

Question

Answer

Is it mandatory to set RX(m+n)9?

controller during step (a)?

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

9 What is the relationship between the

RX(m+n)A error status flag and the various CCS errors? In an CCS error state, is it OK if

10 When an error occurs, must remote station

Ready RX(m+n)B be set to OFF until reset is requested, regardless of the error contents?

11 The master station and slave station L RUN

light will not turn on, and a data link cannot be established. What should I check?

Set RX(m+n)A to "1" when the device itself is in an error state. When there is an CCS error (switch setting error, transmission status error), data cannot be transmitted and, thus, RX

Yes, it is determined so by CC-Link specifications. However, if an error exists that makes it inconvenient to set remote ready to OFF, it is acceptable to not set remote ready to OFF, as clearly

Check the following items:

·Is the initial processing completed?

·Is "REH" still set to "H"?

·Is the CC-Link cable disconn ecte d, or is there a wiring err or ?

·Is the CC-Link cable disconn ecte d?

·

(2) Questions and Answers Related to Initial Processing (Specifications Common to Remote

Devices)

1 The initial data processing request flags are as

follows: RX(m+n)8: Initial processing c ompl ete flag RY(m+n)8: Initial setting request flag RY(m+n)9: Initial data setting complete flag

It is not mandatory to us e these signals if this processing is not necessary. Note, however, that these signals cannot be used for other purposes.

2 The CC-Link master module is initial iz ed with

a programmable controller program according to the following procedure: (a) Initialize other circuit boards (will take several seconds) (b) Initialize the CC-Link In this case, what kinds of data are output from the master module to the slaves and programmable

The master module outputs test polling data to the slaves, as described in the specifications. This data is repeatedly output until the completion of the initial communicati on. The mast er mod ule outputs I/O signals (either Xn0: unit error or XnF: unit ready) to the programmable controller CPU, after the power to both the programmable controller and the master module is turned on.

R18UZ0056EJ0102 Page 82 of 83 Dec. 28, 2018

Question

Answer

will the data be in conflict with each other?

conflict.

programmable controller run.

station is not received.

device does not need to know them.

number switch in a simple manner?

switch is changed.

be, more precisely, 156.25k (625k/4)?

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

(3) Others

1 If both the master station and the device

station start sending data at the same time,

2 When we cancel reset on the device side,

initialize and enable reception (software is halted), and then turn on the power to the programmable controller (stop status), the LED displays become as follows: RUN: Off ERR: Off RD: On SD: Flashes (at approximately 1 second intervals) This status is described as "impossible" in the CCS specifications. Could you give us more information? At this time, update can be performed normally by making the

3 In what way is "No data for the own station"

different from "Unable to receive the data for the own station", precisely?

The device station does not start transmission unless it receives polling data from the master station; thus, data will never be in

If any Mitsubishi programmable controller i s used as the master station, the link to the CC-Link master station is not started if the power is turned on while the programmable contr ol ler CPU is in the STOP status; test scans will be repeated. This means that SD and RD should flash and RUN and ERR should be turned off.

"No data for the own station" is a status in which data is not refreshed and a timeout error has occurred. "Unable to receive the data for the own station" is a status in which data is refreshed but polling data addressed to the own

4 Is the FE (polling frame) data in the polling

data expressed in hexadecimal?

5 Are there any methods to conduct hardware

tests for the baud rate switch and the station

6 Regarding the CC-Link bit rate, are we correct

to interpret the value 156k in specifications to

Yes, the FE data is expressed in hexadecimal. Note, however, that the corresponding address information and related information is automatically set by the CCS; the software of your

Monitor the switches with CCS_M3STNO_BSW_KYOKU. Please note that it is necessary to turn the power on again every time the

Yes, the value is more precisely 156.25k (625k/4).

R18UZ0056EJ0102 Page 83 of 83 Dec. 28, 2018

Revision History

R-IN32 Series CC-Link remote device station

Description

Page

Summary

1.00

2013.7.26

-

First edition issued

Document Number changed.

Target product changed to R-IN32 series from R-IN32M3 series.

R-IN32M4-CL2 documents added. (Complement)

Newly added. (Complement)

L RUN signal output value, modified. (Errors corrected)

Register name changed. (Errors corrected)

Add description for speed setting by software.

Add description for each function

Modify from "setting number" to "baud rate"

11

Add explanation for T able 6.3 Light ON/OFF/BLINK conditions

Modify from "setting number" to "baud rate"

32

Figure 9.1 Initial Processing modify software setting item.

Delete the undescribed annotation "note3"

Delete the unnecessary words.

Modify mistakes from "one byte (half word)" to "byte (half word)"

One Zener diode, added

The function of the IOTENSU pin, Low fixed, was added

Caution on the IOTENSU pin, modified

R-IN32 Series CC-Link Remote device station Revision History

Rev. Date

1.00 2016.6.17 - First edition issued for R-IN32 Series common edition.

- Document Name changed.

- How to use this manual

5 4. R-IN32 Series Initialization

6 to 7 5. CC-Link Remote Device Station Pins

10 6.3(1) Light ON/OFF/BLINK conditions

29 8.2.14 HOLD/CLR register (CCS_M3HOLDCLR)

1.01 2017.2.28 5 Figure 4.1 How to R-IN32 Series Initialization

6 Table 5.1 Correspondence between CC-Link Remote Device Station Pins and

R-IN32M3 Series Pins

9 6.2 Setting the Station Number and Baud Rate

18 8.2.2 Station number switch i nformation, Number of occupied stations information

and Baud rate switch information (CCS_M3STNO_BSW_KYOKU)

74 14.2 software (1)Questions and ans wers related to initial processing

75 14.2 software (2)Questions and answers related to reception enable

78 14.2 software (6)Questions and answers related to reception data read processing

1.02 2018.12.28 4 Table 3.1 Recommended Parts

6 Table 5.1 Correspondence between CC-Link Remote Device Station Pins and

R-IN32M3 Series Pins

8 Table 5.2 Correspondence between CC-Link Remote Device Station Pins and

R-IN32M4-CL2 Pins

9 6.1 Setting the Number of Occupied Stations

C-1

Description

Page

Summary

Answer updated and items added

R-IN32 Series CC-Link Remote device station Revision History

Rev. Date

1.02 2018.12.28 72 14.1 (3) Questions and Answers Related to Switches, Connectors, and Terminal Blocks

C-2

R-IN32 Series CC-Link Remote device station Revision History

[Memo]

C-3

R-IN32 Series User’s Manual

CC-Link Remote device station

http://www.renesas.com

Refer to "http://www.renesas.com/" for the latest and detailed information.

Renesas Electronics America Inc.

1001 Murphy Ranch Road, Milpitas, CA 95035, U.S.A. Tel: +1-408-432-8888, Fax: +1-408-434-5351

Renesas Electronics Canada Limited

9251 Yonge Street, Suite 8309 Richmond Hill, Ontario Canada L4C 9T3 Tel: +1-905-237-2004

Renesas Electronics Europe Limited

Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.K Tel: +44-1628-651-700, Fax: +44-1628-651-804

Renesas Electronics Europe GmbH

Arcadiastrasse 10, 40472 Düsseldorf, Germany Tel: +49-211-6503-0, Fax: +49-211-6503-1327

Renesas Electronics (China) Co., Ltd.

Room 1709 Quantum Plaza, No.27 ZhichunLu, Haidian District, Beijing, 100191 P. R. China Tel: +86-10-8235-1155, Fax: +86-10-8235-7679

Renesas Electronics (Shanghai) Co., Ltd.

Unit 301, Tower A, Central Towers, 555 Langao Road, Putuo District, Shanghai, 200333 P. R. China Tel: +86-21-2226-0888, Fax: +86-21-2226-0999

Renesas Electronics Hong Kong Limited

Unit 1601-1611, 16/F., Tower 2, Grand Century Place, 193 Prince Edward Road West, Mongkok, Kowloon, Hong Kong Tel: +852-2265-6688, Fax: +852 2886-9022

Renesas Electronics Taiwan Co., Ltd.

13F, No. 363, Fu Shing North Road, Taipei 10543, Taiwan Tel: +886-2-8175-9600, Fax: +886 2-8175-9670

Renesas Electronics Singapore Pte. Ltd.

80 Bendemeer Road, Unit #06-02 Hyflux Innovation Centre, Singapore 339949 Tel: +65-6213-0200, Fax: +65-6213-0300

Renesas Electronics Malaysia Sdn.Bhd.

Unit 1207, Block B, Menara Amcorp, Amcorp Trade Centre, No. 18, Jln Persiaran Barat, 46050 Petaling Jaya, Selangor Darul Ehsan, Malaysia Tel: +60-3-7955-9390, Fax: +60-3-7955-9510

Renesas Electronics India Pvt. Ltd.

No.777C, 100 Feet Road, HAL 2nd Stage, Indiranagar, Bangalore 560 038, India Tel: +91-80-67208700, Fax: +91-80-67208777

Renesas Electronics Korea Co., Ltd.

17F, KAMCO Yangjae Tower, 262, Gangnam-daero, Gangnam-gu, Seoul, 06265 Korea Tel: +82-2-558-3737, Fax: +82-2-558-5338

SALES OFFICES

Colophon 5.0

Renesas R-IN32 Series, R-IN32M4-CL2, R-IN32M3-EC, R-IN32M3-CL User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

1. Introduction

1.1 Related materials

1.2 Generic Terms and Ab br eviations

1.3 CC-Link Partner Association

1.4 Cyclic Data Capacity

R-IN32 Series CC-Link Remote device station 2. Function List

R-IN32 Series CC-Link Remote device station 3. Specified Parts and Recommended Parts

3.1 Recommended Parts

R-IN32 Series CC-Link Remote device station 4. R-IN32 Series Initialization

R-IN32 Series CC-Link Remote device station 5. CC-Link Remote Device Station Pins

R-IN32 Series CC-Link Remote device station 6. Setting Details

6.1 Setting the Number of Occupied Stations

6.2 Setting the Station Number and Baud Rate

6.3 Transmission Monitor Section Terminals (for LED)

R-IN32 Series CC-Link Remote device station 7. Monitor Output of Reception Frame Information

R-IN32 Series CC-Link Remote device station 8. Memory Map

8.1 Memory Map List

8.2 Memory Map Details

8.2.1 Send Data Write Enable Information (CCS_MWRENL_RCEX)

8.2.2 Station Number Switch Information, Number of Occupied Stations Information and Baud Rate Switch Information (CCS_M3STNO_BSW_KYOKU)

8.2.3 Error Information (CCS_M3ERR1_ERR2)

8.2.4 M → R Status Information (CCS_M3MRST1_ST2)

8.2.5 RY Reception Buffer (CCS_M3MRRY00_0F)

8.2.6 RWwn Register (CCS_M3MRRWWn)

8.2.7 Send Data Write Complete Flag and Receive Data Read Request (CCS_M3SDOK_RDRQ)

8.2.8 Vendor Code (CCS_M3VENDORCODE)

8.2.9 Model Code and Version (CCS_M3MODELCODE_VERSION)

8.2.10 SDLED Illumination Time Setting and Timeout Time Setting (CCS_M3SDLED_TOVER)

8.2.11 Cyclic Communication (CCS_M3RMST1_ST2)

8.2.12 RX Update Buffer (CCS_M3RMRXn0_nF)

8.2.13 RWr Register (CCS_M3RMRWRn)

8.2.14 HOLD/CLR Register (CCS_M3HOLDCLR)

R-IN32 Series CC-Link Remote device station 9. Sample Flowchart for CC-Link Version 1

9.1 Initial Setting

9.2 Main Processing

9.2.1 Synchronous Read Method / Asynchronous Write Method

9.2.2 Asynchronous Read Method / Asynchronous Write Method

9.3 Reception and Transmission Processing

9.3.1 Synchronous Read Method (Interrupt Processing)

9.3.2 Asynchronous Read Method

9.3.3 Asynchronous Write Method

9.4 Timeout Time Setting Change

9.4.1 Initial Setting Time → Normal Setting Time

9.4.2 Normal Setting Time → Initial Setting Time

R-IN32 Series CC-Link Remote device station 10. Remote Device Station Common Specification

10.1 Cyclic Transmission Signals

10.1.1 Cyclic Transmission Signal Definit ions

10.1.2 System Area Details

10.2 Remote Register

R-IN32 Series CC-Link Remote device station 11. Overview of CC-Link Ver. 2

11.1 Characteristics of CC-Link Ver. 2

11.1.1 Extended Cyclic

11.1.2 Less Occupied Stations

11.2 Overview of Protocol

11.2.1 Overview of Extended Cyclic Communicati on

11.2.2 Transmission of Own Station Information

11.2.3 Extended Cyclic Header Information

11.3 Relationship between SQ Values and RX/RY, RWr/RWw

R-IN32 Series CC-Link Remote device station 12. Sample Flowchart for CC-Link Version 2

12.1 List of Modules and Variables

12.2 Initial Setting INT_CCV20

12.3 Transmission/Reception Processing

12.3.1 Example Using an Interrupt (CCS_REFSTB Signal)

12.3.2 Example of Polling

12.4 Transmission/Reception Processing Module (ICCV20)

12.5 Application Work Area Transfer Processing Module CHK20DONE

R-IN32 Series CC-Link Remote device station 13. Notes on Developing with CC-Link Version 2

13.1 Hardware

13.2 Software (Firmware)

13.3 Write Timing at Transmission

13.4 Handling CC-Link Version 2 Work Area

R-IN32 Series CC-Link Remote device station 14. Questions & Answers

14.1 Circuit Design in General

14.2 Software

14.3 Protocol and Others