Contents

Mitsubishi C64 Numerical Control Network Manual PDF

1 of 208
1 of 208

Summary of Content for Mitsubishi C64 Numerical Control Network Manual PDF

CNC C6/C64

NETWORK MANUAL

BNP-B2373B(ENG)

MELDAS and MELSEC are registered trademarks of Mitsubishi Electric Corporation. Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corp. in the United States and/or other countries. Other company and product names that appear in this manual are trademarks or registered trademarks of the respective company.

Introduction

This manual explains the interfaces and functions related to the MELDAS C6/C64 network connection. Always read this manual before starting use. To ensure safe use of the MELDAS C6/C64, always read the "Precautions for Safety" given on the next page. Details described in this manual

CAUTION

For items described as "Restrictions" or "Usable State" in this manual, the instruction manual issued by the machine maker takes precedence over this manual.

Items not described in this manual must be interpreted as "not possible".

This manual is written on the assumption that all option functions are added. Confirm with the specifications issued by the machine maker before starting use.

The screens and functions may differ or be disabled depending on the NC system version.

General precautions Refer to the following documents.

(1) MELDAS C6/C64/C64T Operation Manual ....................................................... BNP-B2259 (2) MELDAS C6/C64/C64T Parameter Manual ...................................................... BNP-B2267 (3) MELDAS C6/C64/C64T PLC I/F Manual ........................................................... BNP-B2261 (4) MELDAS C6/C64 PLC Programming Manual ......................................... BNP-B2309 (Ladder Section with MELSEC Tool) (5) MELDAS C6/C64 Connection and Maintenance Manual........................ BNP-B2255

Precautions for Safety

Always read the specifications issued by the machine maker, this manual, related manuals and attached documents before installation, operation, programming, maintenance or inspection to ensure correct use. Understand this numerical controller, safety items and cautions before using the unit. This manual ranks the safety precautions into "DANGER", "WARNING" and "CAUTION".

DANGER When the user may be subject to imminent fatalities or major

injuries if handling is mistaken.

WARNING

When the user may be subject to fatalities or major injuries if handling is mistaken.

CAUTION

When the user may be subject to bodily injury or when physical damage may occur if handling is mistaken.

Note that even items ranked as "

CAUTION", may lead to major results depending on the situation. In any case, important information that must always be observed is described.

DANGER

Not applicable in this manual.

WARNING

1. Items related to prevention of electric shocks Do not operate the switches with wet hands. Failure to observe this could lead

to electric shocks. Do not damage, apply forcible stress, place heavy things on, or catch the

cables. Failure to observe this could lead to electric shocks.

2. Items related to program development Do not set any of the touch keys on the GOT as a start switch for the C6/C64.

If a communication error (including cable disconnection) occurs between the GOT and C6/C64, the communication will be cut off and the GOT operation will be disabled. Even if the start switch is released, it will not be recognized that the start signal has been cut off, so the operation will continue. This could result in serious accidents.

CAUTION

1. Items related to product and manual

For items described as "Restrictions" or "Usable State" in this manual, the instruction manual issued by the machine maker takes precedence over this manual.

Items not described in this manual must be interpreted as "not possible".

This manual is written on the assumption that all option functions are added. Confirm with the specifications issued by the machine maker before starting use.

The screens and functions may differ or be disabled depending on the NC system version.

Do not turn "Use prohibited" signal ON. Failure to observe this could result in malfunction in units.

2. Items related to installation and assembly

Always ground the signal cable to ensure stable operation of the system. Use a one-point ground so that the control unit body, power distribution panel and machine are at the same potential.

3. Items related to maintenance

Do not connect or disconnect the cables connected between each unit while the power is ON.

Do not mount or remove each PCB while the power is ON.

Do not pull the cables when connecting/disconnecting them.

- i -

Contents I. MELSECNET/10 1. Outline .......................................................................................................................................1 2. Performance Specifications.......................................................................................................1 3. Available Functions ...................................................................................................................2 4. Cyclic Transmission ..................................................................................................................3

4.1 Flow of Network Data .......................................................................................................3 4.2 Flow of Data Transmitting/Receiving ................................................................................4

5. Parameter Setting .....................................................................................................................5 5.1 Control Station Parameter ................................................................................................5 5.2 Normal Station Parameter ................................................................................................5

6. Other Functions.........................................................................................................................6 6.1 Refresh of SB and SW......................................................................................................6 6.2 Devices Possible to Refresh.............................................................................................6

7. Transient Transmission .............................................................................................................7 7.1 Dedicated Command ........................................................................................................7 7.2 Access to Other Stations ..................................................................................................7

8. Setting and Display ...................................................................................................................8 9. Name and Setting of Each Part of MELSECNET/10 Card ........................................................9 10. Others....................................................................................................................................12

10.1 Backup of MELSECNET/10 Related Parameters .........................................................12 10.2 Replacement of MELSECNET/10 Card ........................................................................12

II. DeviceNet Interface 1. Outline .......................................................................................................................................1

1.1 Features............................................................................................................................1 1.2 Restrictions .......................................................................................................................1

2. Detailed Explanations................................................................................................................2 2.1 General Configuration.......................................................................................................2 2.2 Setting the Configuration Parameters...............................................................................2

2.2.1 Configurator .............................................................................................................2 2.2.2 Parameter Setting Function .....................................................................................3

3. Communication Data.................................................................................................................4 3.1 Assigning the Input Data...................................................................................................4

3.1.1 Setting with SyCon2.................................................................................................4 3.1.2 Setting with the PLC Program..................................................................................5

3.2 Assigning the Output Data................................................................................................6 3.2.1 Setting with SyCon2.................................................................................................6 3.2.2 Setting with the PLC Program..................................................................................6

3.3 Message Communication .................................................................................................7 3.3.1 Message Communication Commands .....................................................................7 3.3.2 Message Communication Results ...........................................................................8 3.3.3 Message Communication Data................................................................................9

4. Interface with Communication Card (HR871)..........................................................................12 4.1 Outline of Interface Signals.............................................................................................13 4.2 Details of Interface Signals .............................................................................................14

4.2.1 Refresh Request, Refreshing.................................................................................14 4.2.2 Message Communication Request, Message Communication Completion,

Message Communication Error .............................................................................14 4.2.3 Error Reset Request, Error Set..............................................................................15 4.2.4 Slave Down............................................................................................................16

- ii -

4.2.5 Parameter Set Request, Setting Parameters, Parameter Setting Completion.............................................................................................................16

4.2.6 System Ready........................................................................................................17 4.3 Details of Word Data.......................................................................................................18

4.3.1 Mounted Card Information .....................................................................................18 4.3.2 Master Communication Status...............................................................................18 4.3.3 Error Information ....................................................................................................19 4.3.4 Parameter Set Head Register No. .........................................................................19 4.3.5 No. of Set Parameters ...........................................................................................20 4.3.6 Down Station Detection Prohibit Setting ................................................................20

5. Diagnosis Information..............................................................................................................21 5.1 Details of Diagnosis Information .....................................................................................21

5.1.1 Master Communication Status...............................................................................21 5.1.2 Error Information ....................................................................................................21 5.1.3 Bus Error Counter ..................................................................................................22 5.1.4 Bus OFF Counter...................................................................................................22 5.1.5 Each Station's Configuration Status ......................................................................22 5.1.6 Each Stations Communication Status...................................................................23 5.1.7 Each Station's Trouble Status................................................................................23

6. Setting the Communication Parameters..................................................................................24 6.1 Setting the Parameters with Configurator .......................................................................24

6.1.1 Setting the Configuration .......................................................................................24 6.1.2 Setting the Master Station Parameters ..................................................................24 6.1.3 Setting the Bus Parameters ...................................................................................24 6.1.4 Setting the Slave Station Parameters ....................................................................25

6.2 Setting the Parameters with the PLC Program...............................................................26 6.2.1 Example of Circuit Creation ...................................................................................27

7. Error Displays..........................................................................................................................29 7.1 Communication Error Codes ..........................................................................................29 7.2 Message Communication Execution Error Codes ..........................................................32

8. Details on Expected Packet Rate and Production Inhibit Time ...............................................34 III. CC-Link Master/Local Unit 1. Outline .......................................................................................................................................1 2. Performance Specifications.......................................................................................................1 3. Usable Functions.......................................................................................................................2 4. Input/output Signals...................................................................................................................3 5. Flow of Communication Data ....................................................................................................5

5.1 Automatic Refresh ............................................................................................................6 6. Transient Function.....................................................................................................................7

6.1 Outline ..............................................................................................................................7 6.2 Transient Command (READ/SREAD/WRITE/SWRITE) Format.......................................7 6.3 Transient Command (RIRD/RIWT) Format.......................................................................8 6.4 Precautions.......................................................................................................................8

7. Names and Settings of Each CC-Link Card Section .................................................................9 8. Miscellaneous..........................................................................................................................13

8.1 Backing Up CC-Link Related Parameters ......................................................................13 8.2 Replacing the CC-Link Card ...........................................................................................13

IV. Setting the Ethernet IP Address 1. Outline .......................................................................................................................................1 2. Explanation of function ..............................................................................................................1

2.1 Confirming the IP Address................................................................................................1 2.2 Initializing the IP Address .................................................................................................1

- iii -

2.3 Setting the IP Address ......................................................................................................1 3. Operation Procedure .................................................................................................................2

3.1 Confirming the Address ....................................................................................................2 3.2 Initializing the IP Address .................................................................................................3 3.3 Setting the IP Address ......................................................................................................4

V. Ethernet 2-channel Connection 1. Outline .......................................................................................................................................1 2. Hardware Configuration ............................................................................................................1

2.1 Unit No..............................................................................................................................1 2.2 Correspondence with Unit Numbers.................................................................................2

3. Setting the Parameters..............................................................................................................2 4. Precautions ...............................................................................................................................2 5. Supplement ...............................................................................................................................3

5.1 Setting the Gateway Address ...........................................................................................3 5.2 EXT3 Compatible Version ................................................................................................3

VI. Ethernet Interface Communication Function

(MELSEC Communication Protocol Section) 1. Outline .......................................................................................................................................1 2. Functions for Accessing the PLC CPU with MC Protocol .........................................................1 3. Example of Connection Configuration.......................................................................................3

3.1 Example of Connecting Peripheral Devices on Single Network .......................................3 3.2 Example of Connecting Peripheral Devices to a Multilevel Network ................................3 3.3 Example of Connecting MELSEC CPU and C6/C64 to a Multilevel Network ...................4

4. Setting the Parameters..............................................................................................................5 4.1 Setting the NC Side ..........................................................................................................5 4.2 Setting the GX Developer Side.........................................................................................5

4.2.1 Setting the Network Parameters ..............................................................................5 4.2.2 Setting the GX Developer Connection Destination ..................................................6

5. Comparison of Functions ..........................................................................................................6 6. Performance Specifications.......................................................................................................7 VII. Ethernet Interface Communication Function Using PLC

(Client Function Section) 1. Outline .......................................................................................................................................1 2. Detailed Explanation .................................................................................................................1

2.1 Connection No. in Connecting with Client Device ............................................................1 2.2 Control Signals .................................................................................................................2 2.3 Response Monitor Timer ..................................................................................................2 2.4 Transmission Control Method...........................................................................................3 2.5 Reception Control Method ................................................................................................4

3. Data Format ..............................................................................................................................5 3.1 Header ..............................................................................................................................5 3.2 Application Data................................................................................................................5

4. Details of Dedicated Commands...............................................................................................7 4.1 OPEN Command ..............................................................................................................7 4.2 CLOSE Command ............................................................................................................8 4.3 BUFSND Command..........................................................................................................9 4.4 BUFRCV Command........................................................................................................10 4.5 Details of Error Codes ....................................................................................................11 4.6 Precautions for Programming .........................................................................................11

5. Example of Data Communication Program .............................................................................12

- iv -

VIII. I/O/Intelligent Function Unit Connection Function 1. Outline .......................................................................................................................................1 2. Basic Specification ....................................................................................................................1 3. Detailed Explanation .................................................................................................................3

3.1 Connection........................................................................................................................3 3.2 Allocation of I/O I/F (Interface)..........................................................................................3 3.3 Access to Intelligent Function Units..................................................................................6

3.3.1 Reading Buffer Memory (by FROM command)........................................................6 3.3.2 Writing in Buffer Memory (by TO command) ...........................................................7 3.3.3 Restrictions in Using FROM/TO Commands ...........................................................8 3.3.4 Access to I/O of Intelligent Function Units ...............................................................9

4. Other Notices ..........................................................................................................................10 4.1 Notices in Connecting Remote I/O Unit ..........................................................................10 4.2 Built-in PLCs Scan Time ................................................................................................12 4.3 Buffer Memory Address ..................................................................................................12

5. Alarm List ................................................................................................................................13 6. Supplement (Example of built-in PLC when FL-net unit is used) ............................................14

6.1 Input/Output Signal List ..................................................................................................15 6.2 Initial Setting ...................................................................................................................16 6.3 Cyclic Transmission........................................................................................................18 6.4 Message Transmission...................................................................................................19

6.4.1 Outline of Message Transmission..........................................................................19 6.4.2 Transaction Code...................................................................................................20 6.4.3 Support Message List ............................................................................................21 6.4.4 Support Message Details.......................................................................................22

6.5 Checking various status of other nodes..........................................................................36 6.6 Reference .......................................................................................................................38

IX. Connection Function with GOT 1. Outline .......................................................................................................................................1 2. Available Function .....................................................................................................................2 3. Connection Mode ......................................................................................................................3

3.1 CPU Direct Connection.....................................................................................................4 3.2 CC-Link Connection..........................................................................................................5 3.3 Ethernet Connection .........................................................................................................6

3.3.1 Initial setting of Ethernet Connection .......................................................................7 4. Device Range Referenced on the GOT ..................................................................................14 5. Related Documents.................................................................................................................15

X. GOT Window Function 1. Outline .......................................................................................................................................1 2. Displaying the NC data..............................................................................................................2 3. Displaying the NC data (Method 2): GOT window function.......................................................3 4. Designating the window area ....................................................................................................4 5. Retrieving window data .............................................................................................................6 6. Data change request and complete signals ..............................................................................7

6.1 Data change request signal (GOT NC)...........................................................................7 6.2 Data change complete signal (NC GOT) ........................................................................8

7. Window commands/responses .................................................................................................9 7.1 List of command codes .......................................................................................................9 7.2 Command area....................................................................................................................9 7.3 Response area ..................................................................................................................10

8 Details of commands................................................................................................................11 8.1 melGetCurrentPrgPack .....................................................................................................11

- v -

8.2 melGetGmodalPack ..........................................................................................................12 8.3 melGetAxisPosition ...........................................................................................................14 8.4 melGetCurrentAlarmMsg2.................................................................................................18 8.5 mmelGetAlarmHistory .......................................................................................................23

XI. Remote Monitor Tool 1. Outline .......................................................................................................................................1 2. System Configuration ................................................................................................................1

2.1 System Requirements ......................................................................................................1 2.2 Contents of Software Package .........................................................................................1

3. Installation of Remote Monitor Tool...........................................................................................2 4. Uninstalling th Remote Monitor Tool .........................................................................................4 5. How to Start and Operate..........................................................................................................5

5.1 Starting Remote Monitor Tool .........................................................................................5 5.2 Screen Makeup of Remote Monitor Tool ..........................................................................6 5.3 Basic Operation of Remote Monitor Tool..........................................................................6

5.3.1 Title Bar....................................................................................................................6 5.3.2 Menu Bar .................................................................................................................7 5.3.3 Connect with Machine Tools (NC) ...........................................................................7 5.3.4 Send and Receive a Parameter File ........................................................................8 5.3.5 Send and Receive the Program...............................................................................9 5.3.6 Receiving a Maintenance Data ..............................................................................10 5.3.7 Refer to NC Information .........................................................................................10 5.3.8 Search the Topics ..................................................................................................11 5.3.9 Confirm the Remote Monitor Tool Version.............................................................11 5.3.10 Using a Tool Bar ..................................................................................................12 5.3.11 Using a Status Bar ...............................................................................................12

6. Setting NC Parameters ...........................................................................................................13 7. Error Message and Its Remedy...............................................................................................14 8. Supplement .............................................................................................................................15

I. MELSECNET/10

I. MELSECNET 10 1. Outline

I - 1

1. Outline As a control station or normal station of MELSECNET/10, MELDAS C6/C64 can be directly connected to the network. To connect, insert the MELSECNET/10 communication unit into extension slots. The maximum number of communication units possible to insert is 2.

2. Performance Specifications Item Optical loop system (HR879) Coaxial bus system (HR878)

LX/LY 8192 points LB 8192 points

Max. link points per network

LW 8192 points

Max. link points per station 2000)2(

8 +

+ WYB

bytes

B 8192 points Max. link device in NC W 8192 points

Communication speed 10MBPS (equivalent to 20MBPS for multiple transmission) 10MBPS

Communication method Token ring Token bus Synchronization method Frame synchronization Encoding method NRZI (Non Return to Zero Inverted) Manchester encoding Transmission route format Duplex loop Simplex bus

Transmission format Conform to HDLC (frame format) Max. number of networks 255 Max. number of groups 9 Number of stations for connection per network

64 stations (Control station: 1, Normal station: 63)

32 stations (Control station: 1, Normal station: 31)

3C-2V 5C-2V Total extension distance per network 30Km (Station to station 500m) 300m

(Station to station 300m)

500m (Station to station

500m) Error control method Retry with CRC (X16+X12+X5+1) and overtime

RAS function

Loop back function with error detection and cable disconnection (only for optical loop systems) Host link line check diagnosis function System fault prevention due to control station migration Error detection using special relay or register Network monitor, various types of diagnosis functions

Transient transmission N: N communication (such as monitoring or program upload/download) ZNRD/ZNWR (N: N)

Connection cable SI-200/250 3C-2V or 5C-2V equivalent product

Connector 2-core optical connector plug CA7003 BNC-P-3-Ni-CAU, BNC-P-5-Ni-CAU (DDK) equivalent products

Cable transmission loss 12db/Km max. Conform to JIS C 3501 standard

I. MELSECNET 10 3. Available Functions

I - 2

3. Available Functions Among the functions of MELSECNET/10 network, available functions with MELDAS C6/C64 are as follows.

Function MELSEC MELDAS C6/C64 Control station function Available Available Control station transfer function Available Available

Communication by B/W (1: N) Available Available Communication by X/Y (1: 1) Available Available Constant link scan function Available Available Stopping/Restarting data link Available Available Inter data link transmission Available Available

Cyclic transmission

Station specific parameter Available Not available N: N communication Available Available Routing function Available Available Transient

transmission Group function Available Not available Automatic recovery function Available Available Loop back function Available Available Station detachment function Available Available RAS function Data link status detection function Available Available

Remote I/O net Available Not available Multiplex transmission function Available

(Optical loop only) Available

(Optical loop only)

N et

w or

k fu

nc tio

n

Reserve station function Available Available

LED diagnosis function 22 point display 4 point (coaxial)

7 point (optical loop) display

Network No. setting Group No. setting Station No. setting Condition setting

Setting switch on the card

Mode setting switch Switch on the front of the card S

et tin

g an

d di

sp la

y

Display changeover switch

Switch on the front of the unit

Not available Hardware testing Available Not available Internal self-loop back testing Available Not available Self-loop back testing Available Not available Station to station testing Available Not available Forward loop / Reverse loop testing Available

(Optical loop only) Not available

Loop testing Available Not available Setting switch check Available Not available Station order check testing Available Not available Line monitoring Available Not available Status monitoring Available Not available Error history monitoring Available Not available

S el

f d ia

gn os

is fu

nc tio

n

Network nesting Available Not available

READ/SREAD Available Available

D ed

ic at

ed

co m

m an

d

WRITE/SWRITE Available Available

I. MELSECNET 10 4. Cyclic Transmission

I - 3

4. Cyclic Transmission The cyclic transmission function is for periodical data transfer between the stations in the network. (The transfer period is in proportional to the size of the entire data in the network.)

4.1 Flow of Network Data Data that can be transmitted within the MELSECNET/10 network is as follows.

Device Unit The max. number of points per 1 network

Link relay (B) 1 bit 8192 points Link register (W) 1 word 8192 points Link input (X) 1 bit 8192 points Link output (Y) 1 bit 8192 points

All stations data is transmitted into the network. Each station outputs its data to the network, and takes the other stations data in. So each station can refer to all the other stations output information. However, it is not possible to output to the data allocated for the other stations. Each stations size of data can be set by a parameter.

Station 4

Link device

Station 1 (Control station)

Link device

Station 1 Station 2 Station 3 Station 4

Station 2

Link device

Station 1 Station 2 Station 3 Station 4

Station 1 Station 2 Station 3 Station 4

Station 3

Link device

Station 1 Station 2 Station 3 Station 4

I. MELSECNET 10 4. Cyclic Transmission

I - 4

4.2 Flow of Data Transmitting/Receiving Data transfer (link refresh) between the network card and PLC device in the NC is executed automatically. The size of data to transmit and the device to which the data is transmitted can be set by parameters.

Slot #2 MELSECNET/10 cardPLC device in C6/C64

B, R

W, R

X

LB

LW

LX

LY

SB

SW

LB

LW

LX

LY

SB

SW

Slot #1 MELSECNET/10 card

LB

LW

LX

LY

SB

SW

LB

LW

LX

LY

SB

SW

Link scan

Scan refreshScan refresh

Link scan

Link refresh

SB

SW

MELSECNET/10 network (Optical/Coaxial)

Y

I. MELSECNET 10 5. Parameter Setting

I - 5

5. Parameter Setting Set parameters related to MELSECNET/10 with MELSECs peripheral devices in the same way as parameter setting of MELSEC CPU, and write them on C64 by PC. However, in the case of using the default parameters or not requiring separate settings due to normal stations, it is not necessary to set the network parameters.

5.1 Control Station Parameter If you wish to place the control station in C64 and set the common parameters, set the network parameters by peripheral device and write them on C64. An example of parameter setting by GPPW is as follows. Set the first I/O No. as follows according to the expansion slot to which the unit is inserted.

Slot First I/O No.

EXT1 (Bottom) 0200 EXT2 (Top) 0280

Set essential settings. Set other parameters if necessary.

5.2 Normal Station Parameter As for normal stations, it is not necessary to set parameters unless separate settings are required. The refresh parameters are set and written as required. In this case, the parameter setting of the first I/O No. is the same as in the case of the control station.

I. MELSECNET 10 6. Other Functions

I - 6

6. Other Functions This section introduces functions whose specifications are different from MELSEC.

6.1 Refresh of SB and SW SB and SW devices are automatically refreshed according to the allocation below depending on the slot.

Slot Refresh range of SB Refresh range of SW

EXT1 SB0000 to SB00FF SW0000 to SW00FF EXT2 SB0100 to SB01FF SW0100 to SW01FF

6.2 Devices Possible to Refresh The refresh parameters have extended setting. By the extended setting, various devices can be set as devices to be refreshed. In the case of C64, the range of devices is as follows.

Devices possible

to refresh Unit Range possible to use

B 1 bit B0 to B1FFF X 1 bit X0 to X1FF (Avoid overlapping with the range for real I/O) Y 1 bit Y0 to Y1FF (Avoid overlapping with the range for real I/O) M 1 bit M0 to M8191 L 1 bit L0 to L255 W 16 bit W0 to W1FFF R 16 bit R0 to R8191 (Avoid overlapping with the range for NC I/F) D 16 bit D0 to D8191 (Note 1) T 16 bit T0 to T255 C 16 bit C0 to C127

(Note 1) D0 to D8191 can be used with software version D0 and above.

I. MELSECNET 10 7. Transient Transmission

I - 7

7. Transient Transmission The transient transmission function is used to communicate only when a station requests communication to another. In the transient transmission, it is possible to read and write devices of the other stations.

7.1 Dedicated Command If C64 is set as either of the command execution station or the target station among the dedicated commands of transient transmission of MELSECNET/10, only the commands below can be used.

Dedicated command

possible to use Outline of the command

READ The host reads the word device data from the specified station.

SREAD The host reads the word device data from the specified station (with the target station completion).

WRITE The host writes data in the word device data of the specified station.

SWRITE The host writes data in the word device data of the specified station (with the target station completion).

7.2 Access to Other Stations By setting the access to other stations valid for peripheral device connected to a station in the MELSECNET/10 network, operation of the peripheral device targeting the other stations in the network becomes possible. The PLC in C64 is also targeted. It is also possible to access the other stations via the peripheral device connected to C64.

I. MELSECNET 10 8. Setting and Display

I - 8

8. Setting and Display

Set network settings by MELSECs peripheral devices. Available functions are shown in the table below.

Setting and display Availability with C64

Number of unit settings Available Common parameter Available Network refresh parameter Available Station specific parameter - Transfer parameters for data link Available

S et

tin g

Routing parameter Available Line monitor Not available Detailed line monitor Not available Line monitor

Line monitor (other stations) Not available Status monitor Not available Detailed status monitor Not available Status monitor Test monitor Not available Error history monitor Not available Loop switching data display Not available

M on

ito r d

is pl

ay

Error history monitor

Transient transmission error Not available

I. MELSECNET 10 9. Name and Setting of Each Part of MELSECNET/10 Card

I - 9

9. Name and Setting of Each Part of MELSECNET/10 Card Name and setting of each part of HR879 for the optical loop system and HR878 for the coaxial bus system are as follows.

1

2

3 4

6 7

5

6

7

HR878 Coaxial bus system HR879 Optical loop system

I. MELSECNET 10 9. Name and Setting of Each Part of MELSECNET/10 Card

I - 10

No. Name Description

Set the operation condition.

SW Description OFF ON

1 Network type Inter-PC net (PC) Remote I/O net

2 Station type Normal station (N.ST) Control station (MNG)

3 Used parameter Common parameters (PRM) Default parameter (D.PRM)

4 OFF ON OFF ON

5

Number of stations (Valid when SW3 is ON) OFF

8 sta- tions OFF

16 sta- tions ON

32 sta- tions ON

64 sta- tions

6 OFF ON OFF ON

7

B/W total points (Valid when SW3 is ON)

OFF

2K points OFF

4K points ON

6K points ON

8K points

(1)

Condition setting switch

8 Not used Always OFF Setting switch of station No., group No. and network No.

Station number setting 1 to 64: Station number Other than 1 to 64: Setting error

Group number setting Not used, fixed to 0 (2)

Network number setting 1 to 255: Network number Other than 1 to 255: Setting error

Sets the mode. Mode Name Description

0 Online (with auto recovery) Data link with auto recovery 1 Cannot be used 2 Offline 3 Test mode 1 Loop test (Forward loop) 4 Test mode 2 Loop test (Reverse loop) 5 Test mode 3 Station to station test (Master station) 6 Test mode 4 Station to station test (Slave station) 7 Test mode 5 Self loop back test 8 Test mode 6 Internal self loop back test 9 Test mode 7 H/W test A - Cannot be used B - Cannot be used C - Cannot be used D Test mode 8 Network No. check E Test mode 9 Group No. check

(3)

Mode setting switch

F Test mode 10 Station No. check

1

8 7 6 5 4 3 2

ON

I. MELSECNET 10 9. Name and Setting of Each Part of MELSECNET/10 Card

I - 11

No. Name Description

Name Status Description

ON Unit normal RUN

OFF WDT error occurred

ERR ON Hardware error

SD Sending data

(4)

LED (Coaxial bus system)

RD

ON in dim light

Receiving data

ON Unit normal RUN

OFF WDT error occurred

F.ERR ON Forward loop Hardware error

R.ERR ON Reverse loop Hardware error

F.SD Forward loop Sending data

F.RD Forward loop Receiving data

R.SD Reverse loop Sending data

(5)

LED (Optical loop system)

R.RD

ON in dim light

Reverse loop Receiving data

(6)

Connector Connect coaxial cable (F shape connector).

1

Forward (F) loop RD

2 Reverse (R) loop SD

3 Reverse (R) loop RD

4 Forward (F) loop SD

(7)

Connector Connect optical fiber cable.

4 3

2 1

I. MELSECNET 10 10. Others

I - 12

10. Others 10.1 Backup of MELSECNET/10 Related Parameters

The parameters related to MELSECNET/10 are only the network parameters written from MELSECs peripheral device. Their storage area is different from that of usual NC parameters, and the parameters are stored in the Ladder program area in the NC. In order to backup the network parameters out of the NC, it is necessary to output and save the data as follows.

No. Data output operation Devices to use

1 Read the data by selecting the PC read parameter by MELSECs peripheral device, and store it as a file in the PC. In writing, execute PC writing as above.

MELSEC peripheral devices GPPQ, GPPW, etc.

2 Output the PLC program area in the NC data output screen. Output by #(99) DATA ( ALL2). In inputting, use the data input screen.

External storage unit (PC, etc.)

10.2 Replacement of MELSECNET/10 Card Even if the MELSECNET/10 card inserted in the NC is faulty and the cards are replaced, data recovery is not necessary as no parameters are stored in the card.

II. DeviceNet Interface

II. DeviceNet Interface 1. Outline

II - 1

1. Outline This function is used to connect MELDAS C6/C64 to DeviceNet as the master station. The dedicated interface card HR871 is required to use this function.

1.1 Features This function has the following features. (1) Compliant with DeviceNet Standards Revision 2.0. (2) Operates as a DeviceNet group 2 dedicated client, and communicates with a Group 2 dedicated server. (3) Can input and output 256 bytes (2048 points) each using I/O communication.

1.2 Restrictions (1) This MELDAS C6/C64 operates as a Group 2 dedicated client using the HR871, but cannot

communicate with the other masters. In other words, neither communication to the configurator on the network nor dynamic establishment of the connection is supported.

(2) A Hilsher (hereinafter, Company H) communication PCB is used, so when the network analyzer is installed, it will appear as a Company H product. (This is because the Company H vender ID is recognized.)

(3) The DeviceNet communication parameters must be set (configured) with the Windows based SYNERGETIC Configurator SyCon Ver. 2.0 or with the built-in PLC program.

II. DeviceNet Interface 2. Detailed Explanations

II - 2

2. Detailed Explanations 2.1 General Configuration

The general configuration when using the C64 as the master station is shown below.

RS-232C

C64

Network power (24VDC)

HR871

Masters + slaves: total 64 units

Windows personal computer for setting parameters + SYNERGETIC SynCon2

TapTerminator

Terminator

2.2 Setting the Configuration Parameters 2.2.1 Configurator

The parameters can be set in the HR871 using the SYNERGETIC (hereinafter Company S) Configurator SyCon Ver. 2.0 (hereinafter SynCon2). Connect HR871 and SyCon2 with a RS-232C cross cable. The SyCon2 system requirements are as follows.

Item System Requirements CPU Intel 486 processor or more OS Windows95, WindowsNT3.51, WindowsNT4.0 Open disk space 10MB or more RAM 16MB or more Display resolution 800 600 dots or more External memory CD-ROM drive (for installation)

II. DeviceNet Interface 2. Detailed Explanations

II - 3

Connect the cross cable as shown below. The connections shown with dotted lines are not required, but may be connected without problem to eliminate the cable orientation.

C64 (HR871)

PC/AT compatible unit

Signal name

Pin No. Pin No. Signal name

1 1

RXD 2 2 RXD

TXD 3 3 TXD

DTR 4 4 DTR

GND 5 5 GND

6 6 DSR

RTS 7 7 RTS

CTS 8 8 CTS

9 9

Dsub 9-pin connector [female] Dsub 9-pin connector [female]

RS-232C cross cable connection diagram

(Note) The details set with SyCon2 are written into the flash ROM on the communication PCB mounted on HR871. This data cannot be read or written from the NC main system (it can only be erased). Back up the setting data with the personal computer.

2.2.2 Parameter Setting Function

The configuration parameters can be set with the PLC program.

(Note) The details set with the PLC program are written into the EEPROM on the HR871's base PCB. When the parameters are written, the data in the flash ROM set with the SyCon2 will be erased. Always invalidate the EEPROM parameters when writing the parameters with SyCon2 again.

The relation of the flash ROM and EEPROM parameters is as follows.

Flash ROM Parameters not set Parameters set

Invalid Local station MAC ID is FFFF

Communication does not start.

Communicates with the flash ROM parameters. EEPROM

Valid Communicates with the EEPROM parameters.

(Note) The EEPROM can be invalidated by setting the local station's station No. (MAC ID) to FFFF.

Refer to section "6.2 Setting the parameters with the PLC program" for details on setting the station No., etc.

II. DeviceNet Interface 3. Communication Data

II - 4

3. Communication Data The communication data is assigned to device B (or device W). The device assignments are as shown below.

HR871 mounting slot Input/output data Extension slot 1 Extension slot 2

Input data 2048 points B0000 to B07FF B1000 to B17FF Output data 2048 points B0800 to B0FFF B1800 to B1FFF

HR871 mounting slot Message communication

Extension slot 1 Extension slot 2 Message communication command (16word, W) W0000 to W000F W1000 to W100F Message communication results (16word, R) W0010 to W001F W1010 to W101F Message communication data (120word, R/W) W0020 to W0097 W1020 to W1097

(Note) Programming and monitor of the device B (or device W) are currently not supported with onboard. These are possible only with GPP until supported.

3.1 Assigning the Input Data

The input data arrangement follows the parameter settings. 3.1.1 Setting with SyCon2

The assignment of the input data for each station is indicated with SyCon2's "Customized I/O data" "I. Addr". This value follows the address mode set with another SyCon2 screen (Master Settings screen). (1) Byte addressing mode

If the address mode is byte address, the devices and I. Addr correspond as shown below. Device I. Addr

B0007-B0000 0 B000F-B0008 1 B0017-B0010 2 B001F-B0018 3 B0027-B0020 4 B002F-B0028 5

(2) Word addressing mode If the address mode is word address, the devices and I. Addr correspond as shown below.

Device I. Addr B0007-B0000 B000F-B0008 0

B0017-B0010 B001F-B0018 1

B0027-B0020 B002F-B0028 2

II. DeviceNet Interface 3. Communication Data

II - 5

3.1.2 Setting with the PLC Program

When the data is set with the PLC program, the settings are the same as the word addressing mode. Note that the byte modules, word modules and double-word modules must be grouped per each slave station in the order as previously indicated. (Layout example)

Device Module B000F to B0000 Byte module 2 Byte module 1 B001F to B0010 (Open due to alignment) Byte module 3 B002F to B0020 Word module 1 B003F to B0030 Word module 2 B004F to B0040 Double-word module 1 (low-order) B005F to B0050 Double-word module 1 (high-order)

Input data for 1st station

B006F to B0060 Byte module 2 Byte module 1 B007F to B0070 Byte module 4 Byte module 3

Input data for 2nd station

II. DeviceNet Interface 3. Communication Data

II - 6

3.2 Assigning the Output Data

The output data arrangement follows the parameter settings. 3.2.1 Setting with SyCon2

The assignment of the output data for each station is indicated with SyCon2's "Customized I/O data" "0. Addr". This value follows the address mode set with another SyCon2 screen (Master Settings screen). (1) Byte addressing mode

If the address mode is byte address, the devices and O. Addr correspond as shown below. Device O. Addr

B0807-B0800 0 B080F-B0808 1 B0817-B0810 2 B081F-B0818 3 B0827-B0820 4 B082F-B0828 5

(2) Word addressing mode If the address mode is word address, the devices and O. Addr correspond as shown below.

Device O. Addr B0007-B0000 B000F-B0008 0

B0017-B0010 B001F-B0018 1

B0027-B0020 B002F-B0028 2

3.2.2 Setting with the PLC Program

When the data is set with the PLC program, the settings are the same as the word addressing mode. Note that the byte modules, word modules and double-word modules must be grouped per each slave station in the order as previously indicated. (Layout example)

Device Module B080F to B0800 Byte module 2 Byte module 1 B081F to B0810 (Open due to alignment) Byte module 3 B082F to B0820 Word module 1 B083F to B0830 Word module 2 B084F to B0840 Double-word module 1 (low-order) B085F to B0850 Double-word module 1 (high-order)

Output data for 1st station

B086F to B0860 Byte module 2 Byte module 1 B087F to B0870 Byte module 4 Byte module 3

Output data for 2nd station

II. DeviceNet Interface 3. Communication Data

II - 7

3.3 Message Communication 3.3.1 Message Communication Commands

The following information can be handled with Message Communication. Reading of error information for the slave in which error occurred Getting/Setting of the slave attribute data Resetting of objects (1) Reading the communication error information

Device No. Item Details W0000 W1000 Command No. 0001H Communication error information read W0001 W1001 High-order byte Not used (always 0)

Slave station No. (Slave MAC ID) Low-order byte Number of the slave station from which error

information is read

(2) Getting the attribute data (Get Attribute)

Device No. Item Details W0000 W1000 Command No. 0101H Attribute get W0001 W1001 High-order byte Class ID of the object from which attribute are

gotten

Slave station No./ class ID

Low-order byte No. of the slave station (MAC ID) from which attributes are gotten

W0002 W1002 Instance ID Instance ID of the object from which attributes are gotten

W0003 W1003 High-order byte Not used (always 0)

Attribute ID Low-order byte Attribute ID of the object from which attributes

are gotten (3) Setting the attribute data (Set Attribute)

Device No. Item Details W0000 W1000 Command No. 0102H Attribute set W0001 W1001 High-order byte Class ID of the object to which attributes are set

Slave station No./ class ID Low-order byte No. of the slave station (MAC ID) to which

attributes are set W0002 W1002 Instance ID Instance ID of the object to which attributes are

set W0003 W1003 High-order byte Byte length of the attribute data to be set (1 to

240)

Attribute ID / Data length

Low-order byte Attribute ID of the object to which attributes are set

(4) Resetting

Device No. Item Details W0000 W1000 Command No. 0201H Reset W0001 W1001 High-order byte Class ID of the object to be reset

Slave station No./ class ID Low-order byte Slave Station No. containing target object

W0002 W1002 Instance ID Instance ID of the object to be reset

II. DeviceNet Interface 3. Communication Data

II - 8

3.3.2 Message Communication Results

When the "message communication command" process results are set, "Message completion" signal (Y202/Y282) turns ON. The PLC program must confirm that "Message completion" signal is ON before reading the data. Refer to section "7.2 Message communication execution error codes" for details on the execution error codes.

(1) Reading the communication error information

Device No. Item Details W0010 W1010 Command No. 0001H Communication error information read W0011 W1011 0000H Normal end

Execution error code Other than 0000H Error end (execution error code)

(2) Getting the attribute data (Get Attribute)

Device No. Item Details W0010 W1010 Command No. 0101H Attribute get W0011 W1011 0000H Normal end

Execution error code Other than 0000H Error end (execution error code)

W0012 W1012 High-order byte Class ID of the object from which attributes were gotten

Slave station No./ class ID

Low-order byte No. of the slave station (MAC ID) from which attributes were gotten

W0013 W1013 Instance ID Instance ID of the object from which attributes were gotten

W0014 W1014 High-order byte Byte length of the gotten attribute data (1 to 240)

Attribute ID/data length

Low-order byte Attribute ID of the object from which attributes were gotten

(3) Setting the attribute data (Set Attribute)

Device No. Item Details W0010 W1010 Command No. 0102H Attribute set W0011 W1011 0000H Normal end

Execution error code Other than 0000H Error end (execution error code)

W0012 W1012 High-order byte Class ID of the object to which attributes were set

Slave station No./ class ID

Low-order byte No. of the slave station (MAC ID) to which attributes were set

W0013 W1013 Instance ID Instance ID of the object to which attributes were set

W0014 W1014 High-order byte Byte length of the set attribute data (1 to 240)

Attribute ID / Data length

Low-order byte Attribute ID of the object to which attributes were set

II. DeviceNet Interface 3. Communication Data

II - 9

(4) Resetting

Device No. Item Details W0010 W1010 Command No. 0201H Reset W0011 W1011 0000H Normal end

Execution error code Other than 0000H Error end (execution error code)

W0012 W1012 High-order byte Class ID of the reset object

Slave station No./ class ID Low-order byte Slave Station No. containing the target

object W0013 W1013 Instance ID Instance ID of the reset object

3.3.3 Message Communication Data

(1) Reading the communication error information

Device No. Item Details W0020 W1020 Slave status Indicates whether the slave is set in the parameters, and

whether the slave responded or not. Refer to the explanation (a) below.

W0021 W1021 (Not used) W0022 W1022 Communication error The error code is stored.

Refer to section "7.1 Communication error codes" for details on the error codes.

W0023 W1023 General error codes General error codes sent from the slave station. This is valid only when the communication error code is 35 (0023H). The general meanings stipulated with DeviceNet are shown in (b) below. Refer to the manual for each slave for details on the actual trouble and countermeasures.

W0024 W1024 Additional error code Additional error codes sent from the slave station. Refer to the manual for the slave for the meaning of each error code.

W0025 W1025 No. of heartbeat timeouts

No. of times the slave station was asked whether it was down. A higher value indicates that the network state is poor.

(Note) Refer to each slave station manual for details on the general error codes and additional error

codes.

(a) Slave status Problems in the slave station are notified by the ON/OFF state of each bit.

Parameters are set for a reserved station

The slave rejected writing of the attributes

The size of the input/output data set in the parameters differs from the actual size

Occurrence of a problem is notified by the corresponding bit turned ON.

The slave did not respond

Bit 6 F to 8 7 45 23 01

II. DeviceNet Interface 3. Communication Data

II - 10

(b) General DeviceNet error codes Error code

Hexa- decimal Decimal

Name Meaning

0000 0 This is reserved by DeviceNet. 0001 1 This is reserved by DeviceNet. 0002 2 Resource unavailable The requested service could not be executed because the

required resources were not found. 0003 to

0007 3 to 7 This is reserved by DeviceNet.

0008 8 Service not supported The requested service is not supported, or is not defined with this object class/instance.

0009 9 Invalid attribute value The attribute data is incorrect. 000A 10 This is reserved by DeviceNet. 000B 11 Already in requested mode/state The object is already in the mode/status requested by the

server. 000C 12 Object settable The object cannot execute the requested service in the

current mode/status. 000D 13 This is reserved by DeviceNet. 000E 14 Attribute not settable Attributes that cannot be changed were changed. 000F 15 Prevelege violation Access rights are not available. 0010 16 Device state conflict The requested service cannot be executed in the current

device state. 0011 17 Reply data too large The response data length is longer than the buffer. 0012 18 This is reserved by DeviceNet. 0013 19 Not enough data Enough data to execute the designated operation has not

been provided. 0014 20 Attribute not supported The designated attribute is not supported. 0015 21 Too much data Invalid data was found. 0016 22 Object does not exist The designated object does not exist in the slave. 0017 23 This is reserved by DeviceNet. 0018 24 No stored attribute data The designated object's attribute data was not saved before

the service was requested. 0019 25 Store operation failure The attribute data could not be saved because a problem

occurred during the save process. 001A to

001E 26 to 30 This is reserved by DeviceNet.

001F 31 Vender specific error A vender specific error occurred. The details are shown in the additional error code area (W0024/W1024). Refer to the slave station manual for details on the vender specific error.

0020 32 Invalid parameter The parameters for the requested service are incorrect. 0021 to

0027 33 to 39 Future extensions This is reserved by DeviceNet.

0028 40 Invalid Member ID The requested member ID designated a class, instance or attribute that is not mounted.

0029 41 Member not settable The requested setting service designated a write disabled member.

002A to 00CF

42 to 204

This is reserved by DeviceNet.

00D0 to 00FF

207 to 225

Reserved for Object Class and service errors

An object class specific error was indicated. The details may be displayed in the additional error code area (W0024/S1024). Refer to the slave station manual for details.

II. DeviceNet Interface 3. Communication Data

II - 11

(2) Getting the attribute data (Get Attribute) The gotten attribute data is stored as a byte string. (3) Setting the attribute data (Set Attribute) Set the attribute data to be set as a byte string. (4) Reset There is no message communication data.

II. DeviceNet Interface 4. Interface with Communication Card (HR871)

II - 12

4. Interface with Communication Card (HR871)

The interface assignments for the communication card and main system are shown below. The assignment will change according to the interface card mounted in this area.

HR871 mounting slot Slot's local information Extension slot 1 Extension slot 2

Bit data HR871 Main (256 points) X200 to X27F X280 to X2FF Main HR871 (256 points) Y200 to Y27F Y280 to Y2FF Word data (10 words) R60 to R69 R70 to R79

(Note) This interface assignment differs according to the communication card to be used. Thus, when

using the PLC program with another interface card, each mounted communication card must be identified.

(Example of circuit creation)

= H871 R60 MC N0 M2000

X202

X201 N0

When sharing the ladder program with another system that uses the same slot for another network card, program the circuit including the DeviceNet card (MR871) local area contact and coil in this section.

Y201

Y202

MCR N0

II. DeviceNet Interface 4. Interface with Communication Card (HR871)

II - 13

4.1 Outline of Interface Signals

Bit data (HR871 Main)

Slot 1 Slot 2 Details Slot 1 Slot 2 Details X200 X280 (Not used) X208 X288 (Not used) X201 X281 Refreshing X209 X289 (Not used)

X202 X282 Message communication completion X20A X28A (Not used)

X203 X283 Error set X20B X28B (Not used) X204 X284 Slave down X20C X28C (Not used)

X205 X285 Message communication error X20D X28D (Not used)

X206 X286 Setting parameters X20E X28E (Not used)

X207 X287 Parameter setting completion X20F X28F System ready

Bit data (Main HR871)

Slot 1 Slot 2 Details Slot 1 Slot 2 Details Y200 Y280 (Not used) Y208 Y288 (Not used) Y201 Y281 Refresh request Y209 Y289 (Not used)

Y202 Y282 Message communication request Y20A Y28A (Not used)

Y203 Y283 Error reset request Y20B Y28B (Not used) Y204 Y284 (Not used) Y20C Y28C (Not used) Y205 Y285 (Not used) Y20D Y28D (Not used) Y206 Y286 (Not used) Y20E Y28E (Not used) Y207 Y287 Parameter set request Y20F Y28F (Not used)

Word data

Slot 1 Slot 2 Details Slot 1 Slot 2 Details

R60 R70 Mounted card information (0871H) R65 R75 No. of set parameters

R61 R71 Master communication status R66 R76

R62 R72 Error information R67 R77 R63 R73 (Not used) R68 R78

R64 R74 Parameter set Head register No. R69 R79

Down station detection prohibit setting

II. DeviceNet Interface 4. Interface with Communication Card (HR871)

II - 14

4.2 Details of Interface Signals 4.2.1 Refresh Request, Refreshing

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Refresh request PC

Y201 Y281

This signal turns ON when the details of device B are refreshed on the network. Refreshing starts when the master communication state is "operating". Refreshing will not start if the communication status is "stop" or "clear". Turn this signal OFF to stop refreshing. 0 (or OFF) will be sent forcibly to the network when refreshing stops.

B

contact Signal name Abbre- viation Slot 1 Slot 2 Applicable

type Refreshing

PC X201 X281

This signal turns ON when refreshing has started followed by "Refresh request" signal (Y201/Y281) turned ON, and the master communication status being "operating". This signal turns OFF when refreshing stops.

Stop OperatingClear Master communication state (R61/R71)

Refreshing (X201/X281)

Refresh request (Y201/Y281)

4.2.2 Message Communication Request, Message Communication Completion, Message

Communication Error

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Message communication request PC

Y202 Y282

This signal turns ON during message communication. The signal turns ON after the data (command) is set in the message communication area. This signal turns OFF after the message communication results are received. "Message communication completion" signal (or "Message communication error" signal) turns OFF when this signal turns OFF.

B

contact Signal name Abbre- viation Slot 1 Slot 2 Applicable

type Message communication completion

PC X202 X282

This signal turns ON when the message communication for "Message communication request" signal (Y202/Y282) has ended, and the results have been written into the message communication area. If an error occurs during the message communication, "Message communication error" signal will also turn ON. When the message communication request signal turns OFF, this signal will also turn OFF.

II. DeviceNet Interface 4. Interface with Communication Card (HR871)

II - 15

B

contact Signal name Abbre- viation Slot 1 Slot 2 Applicable

type Message communication error

PC X205 X285

This signal turns ON if an error occurs during message communication. When "Message communication request" signal turns OFF, this signal will also turn OFF.

No error Error occurrence

PLC program

Message communication error (X205/X285)

Message communication completion (X202/X282)

Message communication request (Y202/Y282)

Message communication command write

(mov)

(Only during data transmission)

Message communication

data write (mov)

Message communication

results read (mov)

(Only during data reception)

Message communication

data read (mov)

4.2.3 Error Reset Request, Error Set

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Error reset request PC

Y203 Y283

"Error set" signal and error code reset are executed when this signal is issued.

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Error set PC

X203 X283

This signal turns ON when an error occurs and the error code is set in the file register's error information area. This signal automatically turns OFF when the cause of the error is eliminated.

Error set (X203/X283)

Error reset request (Y203/Y283)

PLC program Error code

read (mov)

II. DeviceNet Interface 4. Interface with Communication Card (HR871)

II - 16

4.2.4 Slave Down

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Slave down PC

X204 X284

This signal turns ON if there is a slave with inactive communication status. The signal will turn OFF when the slave with inactive communication status is recovered. The communication status of each slave station is indicated with "each station communication status (from SD56/from SD88)". To disable the slave down detection for any slave, designate the slave with the "down station detection prohibit setting (from R66/from R76)".

4.2.5 Parameter Set Request, Setting Parameters, Parameter Setting Completion

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Parameter set request PC

Y207 Y287

Use this signal to set the parameters with the PLC program. This signal turns ON after the data is prepared in the parameter send area. The data is written into the EEPROM when this signal turns ON. The data (set with SyCon2) in the flash ROM is cleared at this time. "Refreshing" signal (X201/X281) must be OFF to set the parameters. (Note) If this signal turns ON when "Refreshing" signal (X201/X281) is ON, it will be ignored. In this case,

confirm that "Refreshing" signal (X201/X281) is OFF, and then turn this signal ON again.

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Setting parameters PC

X206 X286

When "Parameter set request" signal is received and the parameter analysis is completed, the parameter write process will start. This signal turns ON during the parameter write process. Communication is stopped during the parameter write process.

II. DeviceNet Interface 4. Interface with Communication Card (HR871)

II - 17

B

contact Signal name Abbre- viation Slot 1 Slot 2 Applicable

type Parameter setting completion

PC X207 X287

This signal turns ON when the parameter write process is completed.

PLC program

Parameter setting completion (X207/X287)

Setting parameters (X206/X286)

Parameter set request (Y207/Y287)

Parameter write

Refreshing (X201/X281)

Refresh request (Y201/Y281)

4.2.6 System Ready

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

System ready PC

X20F X28F

This signal turns ON when initialization of the module for DeviceNet communication has been completed, and data can be received. This signal must be ON as a condition for the program related to DeviceNet.

II. DeviceNet Interface 4. Interface with Communication Card (HR871)

II - 18

4.3 Details of Word Data 4.3.1 Mounted Card Information

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Mounted card information PC

R60 R70

Information on the card mounted in the expansion slot is set in this signal. When using the DeviceNet master station card (HR871), 0871 (hexadecimal) is set. This is used in the PLC program to determine that the DeviceNet master station card (HR871) is mounted. (Note) The card information may not be set depending on the mounted card.

4.3.2 Master Communication Status

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Master communication status PC

R61 R71

[High-order byte] The I/O communication status is indicated. The status values are as follow. Use this information to confirm that the communication status is "operating" before starting message communication.

Value Name Operation 00H Offline Initializing 40H Stop I/O communication stopped 80H Clear Resetting each slave's output data by transmitting 0 data C0H Operating In I/O communication

Each communication status shifts in the following order.

Operating

Clear

Stop

Offline

II. DeviceNet Interface 4. Interface with Communication Card (HR871)

II - 19

[Low-order byte] Problems in the master are notified with the ON/OFF state of each bit.

Always OFF

Bit 67 4 5 23 01

A serious problem occurred in the network. Communication cannot be continued.

An error occurred in the communication with one slave, so communication with all slaves was stopped.

There is a station with a communication error.

Parameter error

4.3.3 Error Information

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Error information PC

R62 R72

This signal indicates information on the problem, such as a parameter error, which occurred during unit initialization or communication. When a valid error is set in the register, "Error set" signal (X203/X283) turns ON. Even if the error information is eliminated, and "Error set" signal is automatically turned OFF, the error information is held. "Error reset request" signal (Y203/Y283) must be turned ON to clear the error information.

[High-order byte]

The error code is indicated. (Refer to section "7.1 Communication error code" for details.)

[Low-order byte] Station No. (MAC ID) of the station in which problem was detected

Data Details Related NC error FF Local station (type 1) L10 FE Local station (type 2) L11

0 to 3F (63) Station No. (MAC ID) of the station in which problem was detected L12

4.3.4 Parameter Set Head Register No.

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Parameter set head register No. PC

R64 R74

When setting the configuration parameters with the PLC program, set the head No. of the file register (random) in which the data is stored. For example, if the parameters are set from R4000, set "4000". This data must be set before "Parameter set request" signal is turned ON.

II. DeviceNet Interface 4. Interface with Communication Card (HR871)

II - 20

4.3.5 No. of Set Parameters

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

No. of set parameters PC

R65 R75

When setting the configuration parameters with the PLC program, set the number of file registers (random) in which the data is stored. For example, if the parameters are set from R4000 to R4019, set "20". This data must be set before "Parameter set request" signal is turned ON.

4.3.6 Down Station Detection Prohibit Setting

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Down station detection prohibit setting PC

R66 to R69 R76 to R79

Set whether to reflect the down information for each slave station onto "Slave down" signal (X204/X284). When corresponding bit is ON : "Slave down" signal does not turn ON even if the station is down. When corresponding bit is OFF : "Slave down" signal turns ON when the station is down. If the slave station is set as a reserved station with the configuration, set the corresponding bit ON. If the bit is not ON, the reserved station will be recognized as a down station, and "Slave down" signal (X204/X284) will turn ON.

Slave station corresponding to each bit Slot 1/Slot 2 Bit 15 Bit 14 Bit 1 Bit 0

R66/R76 15 14 1 0 R67/R77 31 30 17 16 R68/R78 47 46 33 32 R69/R79 63 62 49 48

II. DeviceNet Interface 5. Diagnosis Information

II - 21

5. Diagnosis Information

The diagnosis information is indicated in the special register SD. The details of the diagnosis information are held even when the power is turned OFF. Slot 1 Slot 2 Details Slot 1 Slot 2 Details

SD48 SD80 Master communication status SD56 SD88

SD49 SD81 Error information SD57 SD89 SD50 SD82 Bus error counter SD58 SD90 SD51 SD83 Bus OFF counter SD59 SD91

Each station's communication status

SD52 SD84 SD60 SD92 SD53 SD85 SD61 SD93 SD54 SD86 SD62 SD94 SD55 SD87

Each station's configuration status

SD63 SD95

Each station's trouble status

Slot 1 Slot 2 Details Slot 1 Slot 2 Details SD64 SD96 (Not used) SD72 SD104 SD65 SD97 (Not used) SD73 SD105 SD66 SD98 (Not used) SD74 SD106 SD67 SD99 (Not used) SD75 SD107 SD68 SD100 (Not used) SD76 SD108 SD69 SD101 (Not used) SD77 SD109 SD70 SD102 (Not used) SD78 SD110 SD71 SD103 (Not used) SD79 SD111

Communication PCB version information (ASCII)

5.1 Details of Diagnosis Information 5.1.1 Master Communication Status

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Master communication status PC

SD48 SD80

Refer to section "4.3.2 Master communication status".

5.1.2 Error Information

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Error information PC

SD49 SD81

Refer to section "4.3.3 Error information". The R62/R72 error information is cleared with "Error reset request" signal (Y203/Y283), but the details of this register are held.

II. DeviceNet Interface 5. Diagnosis Information

II - 22

5.1.3 Bus Error Counter

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Bus error counter PC

SD50 SD82

The number of times the illegal frame counter for the communication chip (CAN chip) exceeded the limit value (96) is indicated.

5.1.4 Bus OFF Counter

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Bus OFF counter PC

SD51 SD83

The number of times that bus OFF (communication error) was detected is indicated.

5.1.5 Each Station's Configuration Status

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Each station's configuration status PC

SD52 to SD55

SD84 to SD87

The status of each slave station's configuration (communication parameter settings) is indicated. When corresponding bit is ON : Parameters for that station are set. When corresponding bit is OFF : Parameters for that station are not set.

Slave station corresponding to each bit Slot 1/Slot 2 Bit 15 Bit 14 Bit 1 Bit 0 SD52/SD84 15 14 1 0 SD53/SD85 31 30 17 16 SD54/SD86 47 46 33 32 SD55/SD87 63 62 49 48

II. DeviceNet Interface 5. Diagnosis Information

II - 23

5.1.6 Each Station's Communication Status

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Each station's communication status PC

SD56 to SD59

SD88 to SD91

The I/O communication status of each slave station is indicated. When corresponding bit is ON : I/O communication with that station is taking place normally. When corresponding bit is OFF : I/O communication with that station is not taking place normally.

Slave station corresponding to each bit Slot 1/Slot 2 Bit 15 Bit 14 Bit 1 Bit 0 SD56/SD88 15 14 1 0 SD57/SD89 31 30 17 16 SD58/SD90 47 46 33 32 SD59/SD91 63 62 49 48

5.1.7 Each Station's Trouble Status

B contact Signal name Abbre-

viation Slot 1 Slot 2 Applicable type

Each station's trouble status PC

SD60 to SD63

SD92 to SD95

The status of any communication trouble occurring during communication with each slave station are indicated. When corresponding bit is ON : Communication trouble information found. When corresponding bit is OFF : Communication trouble information not found. The communication error information for the corresponding slave station must be read out with the message communication function in order to turn the corresponding bit OFF.

Slave station corresponding to each bit Slot 1/Slot 2 Bit 15 Bit 14 Bit 1 Bit 0 SD60/SD92 15 14 1 0 SD61/SD93 31 30 17 16 SD62/SD94 47 46 33 32 SD63/SD95 63 62 49 48

II. DeviceNet Interface 6. Setting the Communication Parameters

II - 24

6. Setting the Communication Parameters 6.1 Setting the Parameters with Configurator

Configuration using SyCon2 is carried out in the following manner.

(1) Setting the configuration (2) Setting the master station parameters (3) Setting the bus parameters (4) Setting the slave station parameters

Refer to the SyCon2 manual for details on using SyCon2.

6.1.1 Setting the Configuration

Write the configuration of the network to be configured into the file. Select the master station and slave station device name from the list. If the applicable device is not listed, the EDS file for that device must be read in. The EDS file can be downloaded from the ODVA website.

http://web.kyoto-inet.or.jp/org/odva-j/ 6.1.2 Setting the Master Station Parameters

Set the following items on the Master Settings screen. (1) Startup behavior after system initialization Always select "Controlled release of the communication by the application program". (2) User program monitoring For Watchdog time, set the time (ms unit) to monitor whether the carrier PCB OS is running properly.

For C64, set a value of 56ms or higher. (3) Addressing mode Set whether to assign the I/O data with a byte unit or word unit.

(Refer to section "3. Communication data".) (4) Storage format (word module) Always select "Little Endian". (5) Handshake of the process data Always select "Buffered, device controlled". (6) Hardware parameter Always select "8 kB dual-port memory".

6.1.3 Setting the Bus Parameters

Set the following items on the Bus Parameter screen

(1) Baudrate Set the baud rate. (2) MAC ID Master C64 station No. (MAC ID) (3) Heartbeat timeout Set the interval to recognize the slave existence. (ms) (4) Auto Clear mode on

Select this to turn the output from all stations OFF when there is a communication error in any station.

II. DeviceNet Interface 6. Setting the Communication Parameters

II - 25

6.1.4 Setting the Slave Station Parameters

Set the following items on the Device Configuration screen. (1) MAC ID Set the slave station No. (2) Description Set the slave name. (3) Activate device in actual configuration

Set whether the station actually communicates, or if it is a reserved station. Checking this item will activate the station. (4) Actual chosen IO connection Select the I/O data communication methods. (5) UCMM Check This system is a Group 2 only system, so this cannot be selected. (6) Fragmented Timeout Designate the time to wait for confirming the reception from the slave when carrying out split

transmission/reception of messages. (7) Expected packet rate Set the expected packet rate. (Refer to section "8. Details on expected packet rate and production

inhibit time".) (8) Production inhibit time Set the production inhibit time. (Refer to section "8. Details on expected packet rate and production

inhibit time".) (9) Watchdog timeout action Set the action taken at watchdog timeout.

Details Timeout Timeout : The connection times out.

The communication is manually halted, and is not recovered until manually restarted.

Auto delete Auto delete : The connection is automatically deleted. The communication is halted, and automatically restarted. The output is cleared to 0 once.

Auto reset Auto reset : Communication continues while holding the connection.

(10) Configured I/O connection data and its offset address Designate the I/O module configuration. Designate the method for assigning the input/output data for

that I/O module with I.Addr and O.Addr.

II. DeviceNet Interface 6. Setting the Communication Parameters

II - 26

6.2 Setting the Parameters with the PLC Program

To set the communication parameters with the PLC program, set the data in a random file register (R register). The set file register's head No. and number (offset) are set in R64 (R74) and R65 (R75) respectively. The setting item "1st station" and "2nd station" are not the station No. (MAC ID). If three slave stations are connected, set the data in the parameter areas for the 1st station to the 3rd station. Offset Item Details

0 Local station No. (Local station MAC ID)

C64 (master) station No. 0000H to 003FH (0 to 63) If FFFFH is set and the parameters are set, the EEPROM data will be invalidated.

1 Baud rate Select the baud rate. 1 : 500Kbps, 2 : 250Kbps, 3 : 125Kbps

2 (Reserved for future use) Fixed to 0 3 (Reserved for future use) Fixed to 0 4 1st station's slave station No. Low-order byte : Station No. (MAC ID) for 1st station's slave 0 to 63

High-order byte : 1st station's slave type 01H : Actual communicating station 80H : Reserved station

5 1st station's slave connection type

Select the I/O communication connection type. 0001H: Poling 0002H: Bit strobe 0004H: Change of state 0008H: Cyclic

6 No. of byte module points for 1st station's slave

Low-order byte : No. of input byte modules High-order byte : No. of output byte modules (The bit module is calculated as 8 points equaling to 1 byte module.)

7 No. of word module points for 1st station's slave

Low-order byte : No. of input word modules High-order byte : No. of output word modules

8 No. of double-word module points for 1st station's slave

Low-order byte : No. of input double-word modules High-order byte : No. of output double-word modules

9 Expected packet rate for 1st station (EXPECTED PACKETRATE)

Set the expected packet rate for the 1st stations slave. (Note) 0000H : 500ms (default value) Other than 0000H : Watchdog timer value ... Setting value -1 (ms)

10 Watchdog timeout action for 1st station (WATCHDOG TIMEOUT ACTION)

Select the action taken when a watchdog timeout occurs in the slave. 0000H : (Default value) Same as following timeout. 0001H : Timeout... The connection times out.

The communication is manually halted, and is not recovered until manually restarted.

0002H : Auto delete ... The connection is automatically deleted. The communication is halted, and automatically restarted. The output is cleared to 0 once.

0003H : Auto reset ... Communication continues while holding the connection. The output is not cleared to 0.

11 Production inhibit time for 1st station's slave (PRODUCTION INHIBIT TIME)

Set the production inhibit time for the 1st station's slave. (Note) 0000H : 10ms (default value) Other than 0000H : Production inhibit time ... Setting value -1 (ms)

12 to 19 Settings for 2nd station's slave 20 to 27 Settings for 3rd station's slave

: : 500 to

507 Settings for 63rd station's slave

(Note) Refer to section "8. Details on expected packet rate and production inhibit time" for details on the expected

packet rate and production inhibit time.

II. DeviceNet Interface 6. Setting the Communication Parameters

II - 27

6.2.1 Example of Circuit Creation

An example of creating the circuit when connecting two slave stations is shown below. Since the parameters are written into the EEPROM, they are saved even when the power is turned OFF. Once the program is executed, it does not need to be executed again.

MOV K1 R4000

X201 X207

System ready

Param. set request

Param. setting complet

Refresh- ing

Param. set command

X20F Y207

MOV K1 R4001

MOV H0104 R4004

MOV H0002 R4005

MOV H0204 R4006

MOV H0000 R4007

MOV H0000 R4008

MOV K0 R4009

MOV H0000 R4010

MOV K0 R4011

MOV H0103 R4012

MOV H0001 R4013

MOV H0204 R4014

MOV H0000 R4015

MOV H0000 R4016

MOV K501 R4017

MOV H0002 R4018

MOV K21 R4019

X201 X207 X20F Y207

Set local station No. to 1 Set baud rate to 500kbps Set 1st station's station No. to 4 Set 1st station's connection to bit strobe Input byte modules : 4 modules Output byte modules : 2 modules Input word modules : 0 modules Output word modules : 0 modules Input double-word modules : 0 modules Output double-word modules : 0 modules

Expected packet rate: Default (500ms) Watchdog timeout action: Default (timeout) Production inhibit time: Default (10ms) Set 2nd station's station No. to 4 Set 2nd station connection to poling

Input byte modules : 4 modules Output byte modules : 2 modules Input word modules : 0 modules Output word modules : 0 modules Input double-word modules : 0 modules Output double-word modules : 0 modules

Expected packet rate: (500ms) Watchdog timeout action: Auto delete Production inhibit time: 20ms

(Continued on next page)

Param. set command

II. DeviceNet Interface 6. Setting the Communication Parameters

II - 28

(Continued from previous page)

MOV K4000 R64

X201 X207 X20F Y207

MOV K20 R65

SET Y207

X207 Y207

RST Y207

RST

Param. set command

Parameter set Set register's head No. Parameter set Set number of data items Parameter set request ON Parameter set request OFF

Param. set command

II. DeviceNet Interface 7. Error Displays

II - 29

7. Error Displays 7.1 Communication Error Codes

Display Screen L10 DN initialization error 1

7- segment

Error detected when initializing DeviceNet unit (Type 1: Configuring with SyCon2)

Error No. Details Countermeasures

0035 The baud rate setting is not within the valid range.

Correctly set the baud rate.

0036 The local station No. (MAC ID) value is not within the valid range.

Set the local station No. between 0 and 63.

0039 There are two or more stations with the same station No. (MAC ID) in the network.

Set the station numbers so that they are not duplicated.

00D2 The parameters are not set in the communication PCB's flash ROM.

This is not particularly a problem when using the EEPROM parameters.

Display

Screen L11 DN initialization error 2 7-

segment

Error detected when initializing DeviceNet unit (Type 2: Configuring with PLC program)

Error No. Details Countermeasures

0001 The local station No. (MAC ID) value is not within the range.

Set the local station No. within 0000H to 003FH, or to FFFFH.

0002 The baud rate is not within the valid range.

Set a value between 1 and 3.

0003 The slave station No.'s low-order byte is not within the valid range.

Set a value between 0 and 63.

0004 The slave station No.'s high-order byte is not within the valid range.

Set 01H or 80H.

0005 The connection type is not within the valid range.

Set 0001H, 0002H, 0004H or 0008H.

0006 A slave station with the same station No. as the local station No. is already set.

Set the slave station numbers so that they are not duplicated within all stations.

0007 No slave station is set. Set at least one slave station.

0008 The total input data length for all slave stations is too long.

The total length must be 256 bytes or less for all slave stations.

0009 The total output data length for all slave stations is too long.

The total length must be 256 bytes or less for all slave stations.

000A The parameter watchdog timeout action value is illegal.

Set 0000H, 0001H, 0002H or 0003H.

000B The expected packet rate value is smaller than the production inhibit time value.

Set so that the expected packet rate value is greater than or equal to the production inhibit time value.

000C EEPROM check sum error Write the parameters again.

Do not turn the power OFF or reset the system while writing the parameters.

II. DeviceNet Interface 7. Error Displays

II - 30

Display

Screen L12 DN link error

Error No. Error detected station No.

7- segment (Station

No.)

Error detected during DeviceNet communication process

Error No. Details Countermeasures

0001 Network trouble was detected after communication started.

Check that the cable is connected correctly.

001E

The slave did not respond. Comprehensively check the state of the network and slave, and check that the MAC ID and baud rate are correct, that the slave is not down, and that the terminator is not disconnected, etc.

0020 The slave responded with an unspecified error.

Read the communication error information, read the error information, and take appropriate measures for that error.

0023 The slave responded with an error when establishing the connection.

Read the communication error information, read the error information, and take appropriate measures for that error.

0024 The parameter input data size and actual slave size do not match.

Check the slave manual and set the correct input data size.

0025 The parameter output data size and actual slave size do not match.

Check the slave manual and set the correct output data size.

0026

Response data for a function not supported by the HR871 card was received.

Check the slave manual, and set so that functions not supported by HR871 are not sent.

Comprehensively check the state of the network and slave, and confirm that the terminator is not disconnected, etc.

0027 The connection is already in the designated mode.

Comprehensively check the state of the network and slave, and confirm that the terminator is not disconnected, etc.

0028 Unpredicted illegal data was received when establishing the connection.

Comprehensively check the state of the network and slave, and confirm that the terminator is not disconnected, etc.

0029 A connection is already established with that slave.

Observe the state for a while, and if the connection cannot be established, reset the slave.

002A

The poling response data length differs from the data length read from the slave when the connection was established.

Comprehensively check the state of the network and slave, and confirm that the terminator is not disconnected, etc.

002B When receiving a split poling response, the first split data was received twice.

Comprehensively check the state of the network and slave, and confirm that the terminator is not disconnected, etc.

002C When receiving a split poling response, the received split data No. differed from the one available.

Comprehensively check the state of the network and slave, and confirm that the terminator is not disconnected, etc.

002D

When receiving a split poling response, the middle data or final data was received before receiving the first split data.

Comprehensively check the state of the network and slave, and confirm that the terminator is not disconnected, etc.

II. DeviceNet Interface 7. Error Displays

II - 31

Error No. Details Countermeasures

003B

The same station No. (MAC ID) was detected two or more times in the parameters.

There are two or more slaves with the same station No. in the parameters. Correct the station numbers.

A slave with the same station No. as the local station No. was found in the parameters.

0045 O.Addr in the parameters exceeds 255.

Set O.Addr to 255 or less.

0046 I.Addr in the parameters exceeds 255.

Set I.Addr to 255 or less.

0047 An illegal connection type was designated.

Confirm that the connection type value is correct.

0049 The expected packet rate value is smaller than the production inhibit time value.

Set the expected packet rate value higher than the production inhibit time value.

II. DeviceNet Interface 7. Error Displays

II - 32

7.2 Message Communication Execution Error Codes

Display

Screen L13 DN message communication error

Error No. 7-

segment

Error detected while executing message communication

Error No. Details Countermeasures

0002 The resources required for executing the required service could not be used.

Referring to the slave manual, check the conditions for the slave to notify this error, and remedy accordingly.

0008

The requested service is not mounted or is not defined for this object class or instance.

Check that the designated MAC ID, class ID, instance ID and attribute ID are correct.

Referring to the slave manual, check the conditions for the slave to notify this error, and remedy accordingly.

0009

Invalid attribute data was detected. Check that the designated MAC ID, class ID, instance ID and attribute ID are correct.

Referring to the slave manual, check the conditions for the slave to notify this error, and remedy accordingly.

000B

The object is already in the mode or state requested by the service.

Check that the designated MAC ID, class ID, instance ID and attribute ID are correct.

Check the current status using attribute get. Referring to the slave manual, check the

conditions for the slave to notify this error, and remedy accordingly.

000C

The object cannot execute the requested service in the current mode or state.

Check that the designated MAC ID, class ID, instance ID and attribute ID are correct.

Check the current status using attribute get. Referring to the slave manual, check the

conditions for the slave to notify this error, and remedy accordingly.

000E

A request to change a change prohibited attribute was received.

Check that the designated MAC ID, class ID, instance ID and attribute ID are correct.

Referring to the slave manual, check the conditions for the slave to notify this error, and remedy accordingly.

000F

The enable/special rights check failed.

Check that the designated MAC ID, class ID, instance ID and attribute ID are correct.

Referring to the slave manual, check the conditions for the slave to notify this error, and remedy accordingly.

0010

The requested service cannot be executed in the current device state.

Check that the designated MAC ID, class ID, instance ID and attribute ID are correct.

Referring to the slave manual, check the conditions for the slave to notify this error, and remedy accordingly.

0011 The slave did not respond. Comprehensively check the state of the network

and slave, and check that the slave is not down, and that the terminator is not disconnected, etc.

II. DeviceNet Interface 7. Error Displays

II - 33

Error No. Details Countermeasures

0013

Sufficient data to execute the designated operation has not been provided.

Check that the designated MAC ID, class ID, instance ID and attribute ID are correct.

When executing attribute set, check that the designated data is not insufficient, and that the data length is correct.

Referring to the slave manual, check the conditions for the slave to notify this error, and remedy accordingly.

0014

The designated attributes are not supported.

Check that the designated MAC ID, class ID, instance ID and attribute ID are correct.

Referring to the slave manual, check the conditions for the slave to notify this error, and remedy accordingly.

0015 The service provided with an unexpected volume of data.

The data returned by the slave must be 240 bytes or less.

0016

The designated object does not exist in the slave.

Check that the designated MAC ID, class ID, instance ID and attribute ID are correct.

Referring to the slave manual, check the conditions for the slave to notify this error, and remedy accordingly.

0032 The response data format is illegal. Comprehensively check the state of the network

and slave, and confirm that the terminator is not disconnected, etc.

0037 The designated slave station No. is not within 0 to 63.

Designate a value between 0 and 63.

0039 The split response order is illegal. Comprehensively check the state of the network

and slave, and confirm that the terminator is not disconnected, etc.

00C8 The parameters are not set for the designated slave.

Designate a slave with which the parameters have been set.

0101 The set data length exceeds 241. The data length must be 240 or less.

0102 An illegal value was set for the command No. in the message communication command area.

Set 0001H, 0101H, 0102H or 0201H for the command No.

II. DeviceNet Interface 8. Details on Expected Packet Rate and Production Inhibit Time

II - 34

8. Details on Expected Packet Rate and Production Inhibit Time

Expected packet rate Production inhibit time (1) The communication watchdog timer value

for the slave is set. If communication is cut off at the set time, the slave will carry out the action designated with the watchdog timeout action.

(1) Slave's minimum transmission cycle = Set the minimum time in which the slave can prepare the send data. The master sends the poling request to the slave at this time cycle.

(2) If the expected packet rate setting value is 1, meaning if the expected packet rate 0ms, then the expected packet rate the production inhibit time must be observed.

Poling

(3) If 1 is set, meaning if the expected packet rate is 0ms, the watchdog timer monitor function is invalid.

(3) The production inhibit time 3ms, or in other words, the setting value 4 must be observed..

(1) The communication watchdog timer value for the slave is set. If the communication between the master and slave is cut off at the set time, the slave will carry out the action designated with the watchdog timeout action.

(1) Slave's minimum transmission cycle = Set the minimum time in which the slave can prepare the send data. The master sends the poling request to the slave at this time cycle.

(2) If the expected packet rate setting value is 1, meaning if the expected packet rate 0ms, then the expected packet rate the production inhibit time must be observed.

(3) If 1 is set, meaning if the expected packet rate is 0ms, the watchdog timer monitor function is invalid.

(3) The production inhibit time 3ms, or in other words, the setting value 4 must be observed.

Bit strobe

(4) This value must be the same for all bit strobe connections.

Change of state

(1) 1 must always be set. In other words, the expected packet rate must be set to 0ms.

(1) 1 must always be set. In other words, the production inhibit time must be set to 0ms.

(1) Designate the cycle to send the data from the slave to the master.

(1) Designate the cycle to send the data from the master to the slave.

(2) If the expected packet rate setting value is 1, meaning if the expected packet rate 0ms, then the expected packet rate the production inhibit time must be observed. Cyclic

(3) The expected packet rate 3ms, or in other words, the setting value 4 must be observed.

(3) The production inhibit time 3ms, or in other words, the setting value 4 must be observed.

III. CC-Link Master/Local Unit

III. CC-LINK Master/Local Unit 1. Outline

III - 1

1. Outline

The MELDAS C6/C64 can be directly connected to the network as a MELSEC CC-Link master/local station. The CC-Link master/local unit (HR865) must be mounted in the expansion slot to use this connection. Up to two communication units can be mounted.

2. Performance Specifications

Item CC-Link master/local unit (HR865) Transmission speed 156kbps; 625kbps; 2.5Mbps; 5Mbps; 10Mbps selective Maximum transmission distance

1200m; 600m; 200m; 150m/110m; 100m/80m/50m depending on the transmission speed selected above

Maximum number of connected units

64 units Note that the following conditions must be satisfied: {(1 a) + (2 b) + (3 c) + (4 d)} 64

a : Number of units that occupies 1 station b : Number of units that occupies 2 stations c : Number of units that occupies 3 stations d : Number of units that occupies 4 stations

{(16 A) + (54 B) + (88 C)} 2304

A : Number of remote I/O stations (not more than 64 units) B : Number of remote device stations (not more than 42 units) C : Number of local stations, standby master stations and intelligent

device stations (not more than 26 units) Number of occupied stations (Number of local stations)

1 to 4 stations (change with DIP switch)

Maximum number of link points per system (Note 1)

Remote input/output (RX, RY) : 2048 points each for input/output Remote register (RWw) : 256 points (master station remote/local station) Remote register (RWr) : 256 points (remote/local station master station)

Number of link points per remote station/local station

Remote input/output (RX, RY) : 32 points (30 points for local station) Remote register (RWw) : 4 points (master station remote/local station) Remote register (Rwr) : 4 points (remote/local station master station)

Communication method Poling method Synchronization method Frame synchronization method Coding method NRZI method Transmission path format Bus (RS-485) Transmission format HDLC complaint Error control method CRC (X16 + X12 + X5 + 1) Connection cable Twisted pair cable with shield RAS function Automatic online return function

Slave station cutoff function Error detection with link special relay/register

Number of occupied input/ output points

32 points

(Note 1) When the CC-Link master station is mounted on the C64, the maximum number of remote input/output points may drop slightly depending on the number of device points that can be secured on the C64 side.

III. CC-LINK Master/Local Unit 3. Usable Functions

III - 2

3. Usable Functions

The following CC-Link functions can be used with the MELDAS C6/C64.

Function item MELSEC MELDAS C6/C64 Ver.1

Method Ver.2 Communication with remote I/O station Communication with remote device station Communication with local station Communication with mixed system Reserved station function Error invalid station function Data link status setting at master station CPU error Parameter registration in EEPROM Input data status setting from data link error station Unit reset by sequence program Data link stop/restart Parameter registration function Automatic refresh function

Synchronous mode

Master functions

Scan synchronization function Asynchronous mode

Local station

LED diagnosis function 16-point display (A1SJ61QBT11) 16-point display

Station No. setting Baud rate setting

Setting switch on card

Mode setting switch

Setting and display functions

Condition setting

Switches on the front of unit Switch on the front

of card

Automatic online return function Slave station cutoff function

Data link status confirmation (SB/SW)

Automatic refresh- ing to SB/SW

Offline test Online test Monitor diagnosis Standby master function

RAS function

Temporary error invalid station designation function READ command, SREAD command WRITE command, SWRITE command Dedicated

commands RIRD command, RIWT command (Note 1)

(Note 1) Transient execution using this command is applicable only to the software Version D and above.

III. CC-LINK Master/Local Unit 4. Input/output Signals

III - 3

4. Input/output Signals

The input/output signal device numbers used to control the CC-Link card mounted in the C64 expansion slot with the built-in PLC are determined according to the slot in which the card is inserted.

Slot Input device number Output device number

EXT1 (bottom) X200 to X21F Y200 to Y21F EXT2 (top) X280 to X29F Y280 to Y29F

Signal direction: Built-in PLC master/local card Signal direction: Built-in PLC master/local card

Usability Usability Input No. Signal name Master

station Local

station

Output No. Signal name Master

station Local

station X2n0 Unit error Y2n0 Refresh command

X2n1 Data link status at host station Y2n1

X2n2 Parameter setting status Y2n2

X2n3 Data link status at other stations Y2n3

(Prohibited to use)

X2n4 Unit reset acceptance complete Y2n4 Unit reset request

X2n5 (Prohibited to use) Y2n5 (Prohibited to use)

X2n6 Data link startup normal completion Y2n6 Data link startup request

X2n7 Data link startup error completion Y2n7 (Prohibited to use)

X2n8 Data link startup by EEPROM parameter normal completion

Y2n8 Data link startup request from the EEPROM parameters

X2n9 Data link startup by EEPROM parameter error completion

Y2n9 (Prohibited to use)

X2nA Parameter registration to EEPROM normal completion

Y2nA Parameter registration request to EEPROM

X2nB Parameter registration to EEPROM error completion Y2nB

X2nC Y2nC X2nD Y2nD X2nE

(Prohibited to use) Y2nE

X2nF Unit ready Y2nF

(Prohibited to use)

III. CC-LINK Master/Local Unit 4. Input/output Signals

III - 4

Signal direction: Built-in PLC master/local card Signal direction: Built-in PLC master/local card

Usability Usability Input No. Signal name Master

station Local

station Output No. Signal name Master

station Local

station X2 (n+1) 0 Y2 (n+1) 0 X2 (n+1) 1 Y2 (n+1) 1 X2 (n+1) 2 Y2 (n+1) 2 X2 (n+1) 3 Y2 (n+1) 3 X2 (n+1) 4 Y2 (n+1) 4 X2 (n+1) 5 Y2 (n+1) 5 X2 (n+1) 6 Y2 (n+1) 6 X2 (n+1) 7 Y2 (n+1) 7 X2 (n+1) 8 Y2 (n+1) 8 X2 (n+1) 9 Y2 (n+1) 9 X2 (n+1) A Y2 (n+1) A X2 (n+1) B Y2 (n+1) B X2 (n+1) C Y2 (n+1) C X2 (n+1) D Y2 (n+1) D X2 (n+1) E Y2 (n+1) E X2 (n+1) F

(Prohibited to use)

Y2 (n+1) F

(Prohibited to use)

: Usable : Not usable

(Note 1) n is either 0 or 8 according to the slot. (Note 2) Refer to the MELSEC "CC-Link System Master/Local Unit User's Manual" for details on the

input/output signals. Normally only "Refresh command (Y2n0)" signal and "Data link start (Y2n6)" signal with the buffer memory parameters are turned ON.

III. CC-LINK Master/Local Unit 5. Flow of Communication Data

III - 5

5. Flow of Communication Data

The flow of data communicated with the CC-Link scan is as shown below.

C64 built-in PLC

Device group

Master station

RX

RY

RWr

RWw

Local station

RWr

RWw

C64 built-in PLC

Device group

RX

RY

Remote I/O station

X

Remote device station

RX

RY

RWw

RWr

Link scan

Automatic refresh Automatic refresh

(Note 1)

(Note 1) Both master stations and local stations can be used by using the MELSEC CPU.

III. CC-LINK Master/Local Unit 5. Flow of Communication Data

III - 6

5.1 Automatic Refresh

Data is automatically sent between the CC-Link card and the NC built-in PLC device. The transmission size and the transmission destination device are set with the parameters using the MELSEC peripheral device. An example for setting this with the GX Developer is given below. The parameters cannot be set with the PLC program, and the system cannot be started with the EEPROM parameters. When setting the parameters, the network parameters must also be set for the master station.

Set the number designated for each slot as the head I/O No.

The setting is invalid. The data will be refreshed automatically to the SB and SW devices.

The devices that can be set as the transmission destination for automatic refresh are as follow. Device name Device range RX, RY RWr, RWw

X X0 to X1FF (Must not be duplicated with actual I/O) Only RX Y Y0 to Y1FF (Must not be duplicated with actual I/O) Only RY M M0 to M8191 L L0 to L255 B B0 to B1FFF D D0 to D8191 (Note 1) R R4000 to R4499, R6400 to R7199 W W0 to W1FFF

(Note 1) D0 to D8191 can be used in the software version D0 and above.

SB and SW are automatically refreshed to the internal devices SB and SW. The setting is invalid. SB refresh range SW refresh range

Slot Output (C64 CC-Link)

Input (CC-Link C64)

Output (C64 CC-Link)

Input (CC-Link C64)

EXT1 SB0000 to SB002F SB0030 to SB00FF SW0000 to SW003F SW0040 to SW00FF EXT2 SB0100 to SB012F SB0130 to SB01FF SW0100 to SW013F SW0140 to SW01FF

III. CC-LINK Master/Local Unit 6. Transient Function

III - 7

6. Transient Function 6.1 Outline

The transient function does not constantly send data. Instead, the data is written and read to and from arbitrary stations when necessary. The client station must be compatible with the transient function. The C6/C64 is compatible with the READ(SREAD)/WRITE(SWRITE) and RIRD/RIWT commands.

6.2 Transient Command (READ/SREAD/WRITE/SWRITE) Format

Usable devices Bit device Word device Constant Pointer

X Y M L F B SB T SM T C D R W SW Z SD K H P Index Digit

designation

S1 S2 D1 D2 D3

READ/WRITE

SREAD/SWRITE

GP.READ Un S1 S2 D1 D2

G.SREAD Un S1 S2 D1 D2 D3

SREAD/SWRITE GP.SREAD Un S1 S2 D1 D2 D3

READ/WRITE G.READ Un S1 S2 D1 D2

6 steps

12 steps

7 steps

13 steps (Note) The station targeted for this command is either QnCPU, QnACPU or MELDASs master/local station.

READ/SREAD Setting data Details

Un Local station head input/output No. S1 Head device of local station storing the control data S2 Head device of target station storing the data to be read D1 Head device of local station where the read data is to be stored D2 Local station device that turns 1 scan ON at completion of command D3 Target station device that turns 1 scan ON at completion of command

WRITE/SWRITE

Setting data Details Un Local station head input/output No. S1 Head device of local station storing the control data S2 Head device of local station storing the data to be written D1 Head device of target station where the written data is to be stored D2 Local station device that turns 1 scan ON at completion of command D3 Target station device that turns 1 scan ON at completion of command

(Note) Designate the Un value as U20 for the EXT1 card, and as U28 for the EXT2 card.

III. CC-LINK Master/Local Unit 6. Transient Function

III - 8

6.3 Transient Command (RIRD/RIWT) Format Usable devices

Bit device Word device Constant Pointer X Y M L F B SB T SM T C D R W SW Z SD K H P

Index Digit designation

S D1 D2

RIRD/RIWT GP.RIRD Un S1 D1 D2

RIRD/RIWT G.RIRD Un S1 D1 D2

5 steps

11 steps

(Note) The station targeted for this command is either the QnCPU, QnACPU, ACPU or MELDASs master/local station.

RIRD command Setting data Details

Un Local station head input/output No. S1 Head device of local station storing the control data D1 Head No. of device storing read data

D2 Device that turns 1 scan ON at completion of read. (D2)+1 device also turns ON at error completion.

RIWT command

Setting data Details Un Local station head input/output No. S1 Head device of local station storing the control data D1 Head No. of device storing write data

D2 Device that turns 1 scan ON at completion of write. (D2)+1 device also turns ON at error completion.

(Note) Designate the Un value as U20 for the EXT1 card, and as U28 for the EXT2 card. 6.4 Precautions

(1) If the target station is MELDAS, only the device memory can be designated in the access code. The buffer memory in the CC-Link unit cannot be designated.

(2) This command is usable only with the FCU6-HR865 unit card version B and above. A timeout error will occur with earlier card versions.

III. CC-LINK Master/Local Unit 7. Names and Settings of Each CC-Link Card Section

III - 9

7. Names and Settings of Each CC-Link Card Section

The names and settings of each section on the HR865 are explained in this section.

HR865 CC-Link system

(1)

(3)

(4)

(5)

(2)

(4)

(2)

(1)

(5)

III. CC-LINK Master/Local Unit 7. Names and Settings of Each CC-Link Card Section

III - 10

No. Name Description

This switch sets the operation conditions. Switch status Setting validity

No. Setting details OFF ON

Master station

(Standby master station)

Local station

(Standby master station)

SW1 Station type Master

station/local station

Standby master station

(Valid) (Valid)

SW2 (Not used) Always OFF SW3 (Not used) Always OFF

SW4 Data link error station input data status Clear Hold Valid Valid

No. of occupied stations

SW5 SW6

1 station OFF OFF 2 stations OFF ON 3 stations ON ON

SW5 SW6

Number of occupied stations

4 stations ON OFF

Invalid Valid

SW7 (Not used) Always OFF

(1) Condition setting switch

8 7 6 5 4 3 2 1

ON

SW8 (Not used) Always OFF (2) Mode switch This switch sets the unit operation status.

Settability

No. Name Details Master

station Local

station

0 Automatic online return provided when data link is enabled

Yes Yes

1

Online Link with remote I/O net mode Yes No

2 Offline Data link offline state Yes Yes 3 Line test 1 Line test 1 in offline state Yes No 4 Line test 2 Line test 2 in offline state Yes No

5 Parameter confirmation test

Checks the parameter details Yes No

6 Hardware test Test of isolated HR865 card Yes Yes

7 (Not usable) Used internally; cannot be set.

8 (Not usable) Used internally; cannot be set.

9 (Not usable) Used internally; cannot be set.

A (Not usable) Setting error ("SW" LED lights)

B (Not usable) Setting error ("SW" LED lights)

C (Not usable) Setting error ("SW" LED lights)

D (Not usable) Setting error ("SW" LED lights)

E (Not usable) Setting error ("SW" LED lights)

F (Not usable) Setting error ("SW" LED lights)

III. CC-LINK Master/Local Unit 7. Names and Settings of Each CC-Link Card Section

III - 11

No. Name Description (3) This switch sets the unit transmission speed.

No. Details 0 156 kbps 1 625 kbps 2 2.5 Mbps 3 5 Mbps 4 10 Mbps 5 Setting error ("SW" "L.ERR" LED lights) 6 Setting error ("SW" "L.ERR" LED lights) 7 Setting error ("SW" "L.ERR" LED lights) 8 Setting error ("SW" "L.ERR" LED lights)

Transmission speed setting switch

9 Setting error ("SW" "L.ERR" LED lights) (4) Station No. setting switch

This switch sets the unit station No.

Master station : 0 Local station : 1 to 64 Standby master station : 1 to 64

If a value other than 0 to 64 is set, the "SW" and "L.ERR." LED will turn ON.

(5) Connector A twisted pair cable is connected here to establish the data link. Pin Signal name 1 DA 2 DB 3 DG 4 SLD

1 2 3 4 5

5 FG

III. CC-LINK Master/Local Unit 7. Names and Settings of Each CC-Link Card Section

III - 12

No. Name Description

LED display status Master station

(Standby master station)

Local station (Standby master

station) No. LED

name Details

Normal Error Normal Error ON Unit is in normal stateLED1 RUN OFF Watchdog timer error

ON OFF ON OFF

Indicates the status of communication with the station set in parameters ON Communication with

all stations error LED2 ERR.

Flicker Station with error communication found

OFF ON or flicker OFF ON or

flicker

LED3 MST ON Set to master station ON OFF LED4 S.MST ON set to standby master ON ON LED5 LOCAL ON Set to local station OFF ON

LED6 CPU R/W ON Communicating with PLC CPU ON OFF ON OFF

LED7 L RUN ON Executing data link ON OFF ON OFF ON communication error

(local station) LED8 L ERR. Flicker Switches 1 to 3

changed during power ON

OFF ON or flicker OFF ON or

flicker

LED9 SW ON Switch setting is incorrect OFF ON OFF ON

LED10 M/S ON Master station already exists in same line OFF ON

LED11 PRM ON Error in parameter details OFF ON

(6) LED display

1

8

2 3 4 5 6 7

ON

LED1 LED9

LED8

LED12 TIME ON Data link monitor timer

activated (All stations error)

OFF ON

LED13 LINE ON Cable is disconnected

Transmission path is affected by noise, etc.

OFF ON OFF ON

LED14 (Not used) LED15 SD ON Sending data ON OFF ON OFF LED16 RD ON Receiving data ON OFF ON OFF

III. CC-LINK Master/Local Unit 8. Miscellaneous

III - 13

8. Miscellaneous 8.1 Backing Up CC-Link Related Parameters

The CC-Link related parameters are only network parameters written into from the MELSEC peripheral devices. These parameters are usually stored in a different area than the NC parameters, and are stored in the ladder program area of the NC. To store these network parameters externally, the data must be output and saved with the following methods.

No. Data output operation Usable devices

1

Select PC read, then parameters with the MELSEC peripheral device, read the parameters and store them as a file in the personal computer. To write the parameters, carry out PC write in the same manner.

MELSEC peripheral device GPPQ, GPPW, etc.

2

Output the PLC program area with the NC Data Out screen. Output by setting #(99 ) DATA ( ALL2). The data is input with the Data In screen.

External storage device (personal computer, etc.)

8.2 Replacing the CC-Link Card

If any defect is found in the CC-Link card mounted in the NC, the card must be replaced. There are no such parameters on the card which must be saved, so the data does not need to be recovered.

IV. Setting the Ethernet IP Address

IV. Setting the Ethernet IP Address 1. Outline

IV - 1

1. Outline

With this function, the communication parameters can be confirmed and set using the 7-segment LED display and rotary switches mounted on the C6/C64. These parameters, such as the IP address, are required for establishing Ethernet communication with the personal computer to monitor the C6/C64 and carry out setting operations.

2. Explanation of function 2.1 Confirming the IP Address

The IP address, gateway address, subnet mask and port No. set in the parameter area can be confirmed with the 7-segment LED display mounted on the C6/C64. Set communication parameters confirmed above in the application setting file in the personal computer used to monitor the C6/C64 and carry out settings. When the application is started up, Ethernet communication will start between the C6/C64 and personal computer.

2.2 Initializing the IP Address

The IP address, gateway address, subnet mask and port No. can be initialized using the rotary switches mounted on the C6/C64. The default values are shown below.

IP address : 192. 168. 1. 2 Gateway address : 0. 0. 0. 0 Subnet mask : 255. 255. 255. 0 Port No. : 64758

After initializing the parameters with this function, reboot C6/C64. Ethernet communication will be enabled with the default values. Set the above default values in the application setting file in the personal computer used to monitor the C6/C64 and carry out settings. When the application is started up, Ethernet communication will start between the C6/C64 and personal computer.

2.3 Setting the IP Address

Once Ethernet communication is established between the C6/C64 and personal computer with the above method, the communication parameters, such as the IP address, can be set on the Parameter Setting screen of the application used for C6/C64 monitoring and setting operations. After setting the communication parameters, such as the IP address, on the Parameter Setting screen, turn the C6/C64 power OFF once. When the power is turned ON again, Ethernet communication with the new parameter setting values will be possible. Set the parameters set above in the application setting file in the personal computer used to monitor the C6/C64 and carry out settings. When the application is started up, Ethernet communication will start between the C6/C64 and personal computer using the new parameter setting values. The IP address, gateway address, subnet mask and port No. can be set using the 7-segment LED display and rotary switches mounted on the C6/C64.

IV. Setting the Ethernet IP Address 3. Operation Procedure

IV - 2

3. Operation Procedure 3.1 Confirming the Address

(Example) Display when parameters are set as follows

IP address : 192. 255. 11. 3 Gateway address : 192. 255. 11. 254 Subnet mask : 255. 255. 255. 0 Port No. : 64758

Turn the C6/C64 power OFF.

Select the IP address confirmation mode by setting the slide switch SW1 on the C6/C64 (shown on the right) to "ON" and the rotary switch CS1 to "8".

Turn the C6/C64 power ON.

A 6

D

B C4

F 1 0 E2

97

3

5

OFF

ON

LED2 BAT

S W

1 C

S 2

C S

1

LED1

8 A6

D

B C4

8

F 1 0 E2

97

3 5

The IP address, gateway address, subnet mask and port No. will appear on the 7-segment LED display as shown below.

(Note) The IP address is normally indicated as a decimal, but is displayed as a hexadecimal on the

7-segment LED. 3 (0x03) 11 255 192 I

0 (0x00) 255 255 255 M

254 (0xFE) 11 255 192 G

64758 (0xFCF6) P

IV. Setting the Ethernet IP Address 3. Operation Procedure

IV - 3

3.2 Initializing the IP Address

Turn the C6/C64 power OFF.

Turn the C6/C64 power ON.

Select the IP address initialization mode by setting the slide switch SW1 on the C6/C64 (shown on the right) to "ON" and the rotary switch CS1 to "A".

The IP address initialization mode is ready, and the following will appear on the 7-segment LED display.

With the power ON, change the rotary switch CS1 from "A" to "9".

A

D

B C4

F 1 0 E 2

97

3

5

OFF

ON

LED2 BAT

S W

1 C

S 2

C S

1

LED1

8 A6

D B C4

8

F 1 0 E2

97

3

5

The 7-segment LED display will change as follows.

The following will appear on the 7-segment LED display. The communication parameters, such as the IP address and subnet mask, will be initialized.

(Note) The settings are not initialized until the above display appears. If the power is turned OFF, etc., during the operation, start again from the beginning.

Turn the rotary switch CS1 back to "A" from "9".

A6

D

B C4

F 1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5 A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

A6

D B C4

F 1 0 E2

97

3

5

8

CS1 CS2

E2 D 3

4 C

8

F 1 0

A6 97 B 5 A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

Turn the C6/C64 power ON.

Turn the C6/C64 power OFF, set the slide switch SW1 to "OFF", and turn the rotary switch CS1 back to "0".

Ethernet communication is possible with the default communication parameters.

IV. Setting the Ethernet IP Address 3. Operation Procedure

IV - 4

3.3 Setting the IP Address

The methods for setting the IP address, gateway address, subnet mask and port No. using the 7-segment LED display and rotary switches mounted on the C6/C64 are explained in this section.

Turn the C6/C64 power OFF.

Turn the C6/C64 power ON.

Select the IP address initialization mode by setting the slide switch SW1 on the C6/C64 (shown on the right) to "ON" and the rotary switch CS1 to "8".

C

OFF

ON

LED2 BAT

S W

1 C

S 2

C S

1

LED1

A 6

D

B 4

F 1 0 E 2

97

3

5

8 A 6

D

B C4

8

F 1 0 E 2

97

3

5

The IP address, gateway address, subnet mask and port No. will appear on the 7-segment LED display.

This indicates that the IP address will be set.

The IP address setting mode is ready, and the setting parameter name will appear on the 7-segment LED display as shown below.

With the power ON, change the rotary switch CS1 from "8" to "9".

The lit dot LED indicates the settable digit. In this example, the "C" section can be set.

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

D E2

3 4 C

8

F 1 0

A6 97 B5

The first IP address will appear on the 7-segment LED display.

Change the rotary switch CS1 from "9" to "8".

A6

D

B C4

F 1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5 A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

(Example) If the IP address is "C0. FF. 0B. 03", the first "C0" will appear.

(Continued on next page)

IV. Setting the Ethernet IP Address 3. Operation Procedure

IV - 5

Previous CS2 setting

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1

E2 D3

4 C

8

F 1 0

A6 97 B5 A6

D

B C4

F1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

The settable section will change, and the dot LED will move.

As CS2 is changed, the settable section will flicker and change.

Change the setting with rotary switch CS2. (Example: To change "0" to "A")

In the above case, the rotary switch CS2 was already set to "0", so the setting was changed to "1" once, and then changed to "0" again.

If the rotary switch CS2 is already set to the required value (example: "0") as shown above, change the switch to another value once, and then reset it to the required value.

As CS2 is changed, the settable section will flicker and change.

Change the setting with rotary switch CS2. (Example: To change "C" to "0")

Indicates that the right section can be set.

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

Change the rotary switch from "8" to "9", and change the settable section.

A6

D

B C4

F 1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

A6

D

B C4

F1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

D E2

3 4 C

8

F 1 0

A6 97 B5

(Continued on next page)

(Continued from previous page)

IV. Setting the Ethernet IP Address 3. Operation Procedure

IV - 6

IP address C0. FF, 0B. 03

The settable section will change, and the dot LED will move.

As CS2 is changed, the settable section will flicker and change.

Change the rotary switch CS1 from "8" to "9", and change the settable section.

Change the setting with rotary switch CS2. (Example: To change "F" to "C")

Indicates that the right section can be set.

The settable section will change, and the second IP address delimited with "." will appear.

As CS2 is changed, the settable section will flicker and change.

Change the rotary switch CS1 from "9" to "8", and change the settable section.

Change the setting with rotary switch CS2. (Example: To change "F" to "0")

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

B

E2 D3

4 C

8

F 1 0

A6 97 5 A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

Indicates that the left section can be set.

Previous CS2 setting

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1

E2 D3

4 C

8

F 1 0

A6 97 B5 A6

D

B C4

F1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

5 A 6

D

B C4

F 1 0 E 2

97

3

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

Previous CS2 setting

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1

E2 D3

4 C

8

F 1 0

A6 97 B5 A6

D

B C4

F1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

(Continued on next page)

(Continued from previous page)

IV. Setting the Ethernet IP Address 3. Operation Procedure

IV - 7

IP address C0. FF. 0B. 03

As CS2 is changed, the settable section will flicker and change.

Change the setting with rotary switch CS2. (Example: To change "B" to "D")

Indicates that the right section can be set.

The settable section will change, and the dot LED will move.

Change the rotary switch CS1 from "8" to "9", and change the settable section.

The settable section will change, and the third IP address delimited with "." will appear

As CS2 is changed, the settable section will flicker and change.

Change the rotary switch CS1 from "9" to "8", and change the settable section.

Change the setting with rotary switch CS2. (Example: To change "0" to "1")

Indicates that the left section can be set.

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5 A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

Previous CS2 setting

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1

E2 D3

4 C

8

F 1 0

A6 97 B5 A6

D

B C4

F1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

Previous CS2 setting

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1

E2 D3

4 C

8

F 1 0

A6 97 B5 A6

D

B C4

F1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

(Continued on next page)

(Continued from previous page)

IV. Setting the Ethernet IP Address 3. Operation Procedure

IV - 8

IP address C0. FF. 0B. 03

The settable section will change, and the dot LED will move.

As CS2 is changed, the settable section will flicker and change.

Change the rotary switch CS1 from "8" to "9", and change the settable section.

Change the setting with rotary switch CS2. (Example: To change "3" to "6")

Indicates that the right section can be set.

The settable section will change, and the fourth IP address delimited with "." will appear.

As CS2 is changed, the settable section will flicker and change.

Change the rotary switch CS1 from "9" to "8", and change the settable section.

Change the setting with rotary switch CS2. (Example: To change "0" to "3")

Indicates that the left section can be set.

A6

D

B C4

F 1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

C A6

D

B 4

F 1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

Previous CS2 setting

A6

D

B C4

F 1 0 E2

97

3

5

8

CS1

E2 D3

4 C

8

F 1 0

A6 97 B5 A6

D

B C4

F1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

A6

D

B C4

F 1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

Previous CS2 setting

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1

E2 D3

4 C

8

F 1 0

A6 97 B5 A6

D

B C4

F1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

A6

D

B C4

F 1 0 E2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

(Continued on next page)

(Continued from previous page)

IV. Setting the Ethernet IP Address 3. Operation Procedure

IV - 9

Gateway address C0. FF. 0B. FE

The lit dot LED indicates the settable digit. In this example, the "C" section can be set.

The display above indicates the gateway address setting.

The first gateway address will appear on the 7-segment LED display.

Change the rotary switch CS1 from "8" to "9".

The 7-segment LED display will change as shown below, and all of the IP address settings set above will be validated.

Change the rotary switch CS1 from "9" to "8", and change the settable section.

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5 A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

(Continued from previous page)

Using the same methods as setting the IP address, select the digit to be set with rotary switch CS1, and change the setting with rotary switch CS2.

The settable section will change as rotary switch CS1 is operated, and the settable section on the 7-segment LED display will flicker and change as the rotary switch CS2 is operated.

(Continued on next page)

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

D

A 6 B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5

The 7-segment LED display will appear as shown below. All of the gateway addresses set above will be validated.

Change the rotary switch CS1 from "8" to "9", and change the settable section.

The display above indicates the subnet mask setting.

IV. Setting the Ethernet IP Address 3. Operation Procedure

IV - 10

Subnet mask FF. FF. FF. 00

The two high-order digits of the port No. will appear on the 7-segment LED display.

The settable section will change as rotary switch CS1 is operated, and the settable section on the 7-segment LED display will flicker and change as the rotary switch CS2 is operated. When the port No. has been set to the last digit, the 7-segment LED display will appear as shown below. All of the port No. settings made above will be validated.

Change the rotary switch CS1 from "8" to "9".

Using the same methods as setting the IP address, select the digit to be set with rotary switch CS1, and change the setting with rotary switch CS2.

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5 A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

Turn the C6/C64 power ON.

Turn the C6/C64 power OFF, set the slide switch SW1 to "OFF", and turn the rotary switch CS1 back to "0".

Ethernet communication using the IP address, gateway address, subnet mask and port No. set with the above operations will be possible.

Port No. F C F 6.

The first subnet mask setting value will appear on the 7-segment LED display.

The settable section will change as rotary switch CS1 is operated, and the settable section on the 7-segment LED display will flicker and change as the rotary switch CS2 is operated. When the subnet mask has been set to the last digit, the 7-segment LED display will appear as shown below. All of the subnet mask settings set above will be validated.

Change the rotary switch CS1 from "9" to "8".

Using the same methods as setting the IP address, select the digit to be set with rotary switch CS1, and change the setting with rotary switch CS2.

A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F 1 0

A6 97 B5 A 6

D

B C4

F 1 0 E 2

97

3

5

8

CS1 CS2

E2 D3

4 C

8

F1 0

A6 97 B5

The display above indicates the port No. setting.

(Continued from previous page)

V. Ethernet 2-channel Connection

V. Ethernet 2-channel Connection 1. Outline

V - 1

1. Outline

When two Ethernet I/F cards HR876 are mounted in the C6/C64 (hereinafter, C64), two network channels can be connected with Ethernet.

2. Hardware Configuration

The Ethernet I/F card HR876 can be mounted in the C64's internal expansion slot (EXT1, EXT2) and the external expansion slot (EXT3).

2.1 Unit No.

When two Ethernet I/F cards are mounted, unit numbers are assigned to each card to identify the I/F card. The I/F cards mounting state and the unit numbers correspond as shown below.

When mounted in EXT1 and EXT2

EXT2

EXT1 unit 2

EXT2

EXT1

unit 2

EXT2

EXT1

unit 2

EXT3 EXT3 EXT3

EXT1

EXT2 EXT3

EXT1

EXT2EXT3 EXT3

unit 1 unit 1

unit 1

When mounted in EXT1 and EXT3

unit 1

When mounted in EXT1 only When mounted in EXT2 only When mounted in EXT3 only

When mounted in EXT2 and EXT3

EXT1

EXT2

unit 1 unit 1

V. Ethernet 2-channel Connection 2. Hardware Configuration

V - 2

2.2 Correspondence with Unit Numbers

The operation of the Ethernet I/F card corresponds to each unit No. as indicated below.

Operation Unit 1 Unit 2 Recommended connection HMI (Human Machine Interface) Information network Corresponding IP address setting #1926 IP address #1931 IP address (2)

Corresponding Subnet mask setting #1927 Subnet mask #1932 Subnet mask (2)

Corresponding port number setting #1929 Port number #1933 Port number (2)

Processing priority High Low Others IP address setting available off-line

3. Setting the Parameters

Set the parameters for each Ethernet I/F card on the BASIC SPECIFICATION PARAMETER screen. You can set the parameters from #1926 to #1929 in the off-line mode. (Refer to "Chapter IV. Setting the IP Address" in this manual.)

(Note 1) If "#1926 IP address" is not set, "192.168.1.2" will be set as the initial setting. (Note 2) If you set or change the Ethernet parameters, reboot C64.

4. Precautions

(1) When two Ethernet cards are mounted, do not use the IP address in the same net ID as correct transmission may be inhibited. The same net ID refers to when the masked (valid) section is duplicated by the subnet mask.

[BASIC SPECIFICATION PARAMETER] SETUP PARAM 1.18/21 # 1925 1926 IP address 192. 168. 1. 2 1927 Subnet mask 255. 255. 255. 0 1928 Gateway address 0. 0. 0. 0 1929 Port number 64758 1930 Speed 10M/auto 0 1931 IP address (2) 192. 168. 2. 2 1932 Subnet mask (2) 255. 255. 255. 0 1933 Port number (2) 64758 1934 Speed (2) 10M/auto 1 1935 1936 #( ) DATA ( . . . ) EMG STOP

AXIS SERVO SPINDLE MENU CHANGE BASIC

V. Ethernet 2-channel Connection 5. Supplement

V - 3

5. Supplement 5.1 Setting the Gateway Address

Routing is not used with the WEP compatible specifications, so the gateway address does not need to be set. To use routing, set "#1927 Gateway address". Routing will be validated for unit 1.

Setting example

10.97.12.254

10.97.46.254

Host 2

10.97.46.50

192.168.1.2

C64

10.97.12.1

Host 1

192.168.1.1

GOT

Unit0

Unit1

#1927 Gateway address 10.97.46.254

5.2 EXT3 Compatible Version

The HR876 Ethernet I/F card can be mounted in the EXT3 with the software version D and above.

VI. Ethernet Interface Communication Function (MELSEC Communication Protocol Section)

VI. Ethernet Interface Communication Function (MELSEC Communication Protocol Section) 1. Outline

VI - 1

1. Outline

This section explains the methods of communication using MELSEC communication protocol (hereinafter, MC protocol) which is one of the Ethernet interface card communication functions. MC protocol is a MELSEC communication method used to read and write, etc., the data in the MELSEC CPU. The sequence programs and data in the C6/C64 can be accessed from a MELSEC peripheral device connected by Ethernet using this protocol. This section generically labels the C6/C64 and MELSEC CPU as the "PLC CPU".

2. Functions for Accessing the PLC CPU with MC Protocol

The main functions for accessing the PLC CPU with MC protocol are explained here. On the PLC side, the Ethernet unit sends and receives data based on the commands from the client device. Thus, a sequence program for data communication is not required on the PLC CPU side.

GX Developer Connect to C6, C64, MELSEC 1, or 2

MELSEC 1

C6 Connect to C64, MELSEC 1, or 2

MELSEC 2

MELSEC NET/10

C64

Connect to C6, C64, or MELSEC 2

Connect to C6, C64, or MELSEC 1

Connect to C6, MELSEC 1 or 2

Ethernet

VI. Ethernet Interface Communication Function (MELSEC Communication Protocol Section) 2. Functions for Accessing the PLC CPU with MC Protocol

VI - 2

(1) Reading and writing data This function reads and writes data to and from the device memory of the PLC CPU in the local station or other station on MELSECNET/10, and to and from the intelligent function unit's buffer memory. By reading and writing the data, the PLC CPU's operation can be monitored, data can be analyzed, and production can be controlled with the client device. In addition, production commands, etc., can be issued from the client device.

(2) Reading and writing files

This function reads and writes the files, such as the sequence programs and parameters, stored in the PLC CPU. By reading and writing the files, the PLC CPU files can be controlled with the client device. The execution programs, etc., can be changed (interchanged) from the client device.

(3) PLC CPU remote control

This function executes remote RUN/STOP. Remote operation of the PLC CPU from the client device is possible using the PLC CPU remote control function.

(4) Accessing other stations' PLC using data link command

The PLC CPU can exchange data with PLC CPUs in the following stations using the data link commands. Note that the only data link commands supported by C6/C64 are READ, SREAD/WRITE and SWRITE.

Other station's PLC CPU on same Ethernet Other Ethernet via MELSECNET/H or MELSECNET/10, or PLC CPU on MELSECNET/H or

MELSECNET/10 (Use MELSECNET/H or MELSECNET/10 relay communication function)

(Note) The MELSECNET/H cannot be connected directly to C6/C64.

VI. Ethernet Interface Communication Function (MELSEC Communication Protocol Section) 3. Example of Connection Configuration

VI - 3

3. Example of Connection Configuration

An example of the actual connection configuration is shown below. 3.1 Example of Connecting Peripheral Devices on Single Network

This is the most simple configuration for connecting peripheral devices with Ethernet.

GX Developer Network No.: 1, station No.: 1 (192.168.1.1)

Basic specification parameter settings #1926 IP address 192.168.1.2 #1927 Subnet Mask 255.255.255.0 #1928 Gateway address 0.0.0.0 #1929 Port number 64758

Connection destination designation

Personal computer I/F Ethernet selection Network No.: 1, Station No.: 1

PLC I/F

Network No.: 1, station No.: 1, IP address 192.168.1.2 Routing method: Automatic conversion method

Set both IP addresses for the connection destination setting

Ethernet

Set local IP address

C6/C64 Network No.: 1, station No.: 2 (192.168.1.2)

3.2 Example of Connecting Peripheral Devices to a Multilevel Network

This configuration connects peripheral devices to a multilevel network consisting of Ethernet and MELSECNET /10. The communication settings for other stations are set on the peripheral device side in this case.

MNET/10 routing parameter setting

Transmission destination network No. 1 Relay destination network No. 2 Relay destination station No. 1

C6/C64

MELSEC NET/10 MELSEC

MELSEC

GX Developer

Connection destination designation Personal computer I/F : Serial selection PLC I/F : CPU unit selection Other station designation : Designate each station

Network No.: 1 Station No.: 1

Network No.: 1 Station No.: 2 Network No.: 2

Station No.: 1 (192.168.1.1)

Network No.: 2 Station No.: 2 (192.168.1.2)

Ethernet

Network parameter setting Network type MELSECNET/10 Network No. 1 Station No. 1

Basic specification parameter settings #1926 IP address 192.168.1.2 #1927 Subnet Mask 255.255.255.0 #1928 Gateway address 0.0.0.0 #1929 Port number 64758

MNET/10 routing parameter setting Transmission destination network No. 2 Relay destination network No. 1 Relay destination station No. 2

Network parameter setting Network type Ethernet MELSECNET/10 Network No. 2 1 Station No. 1 2 IP address 192.168.1.1

VI. Ethernet Interface Communication Function (MELSEC Communication Protocol Section) 3. Example of Connection Configuration

VI - 4

3.3 Example of Connecting MELSEC CPU and C6/C64 to a Multilevel Network

This configuration connects the MELSEC CPU and C6/C64 to a multilevel network consisting of Ethernet and MELSECNET /10. Each can access (read/write) each other's devices.

MNET/10 routing parameter setting

Transmission destination network No. 1 Relay destination network No. 2 Relay destination station No. 1

C6/C64

MELSEC NET/10

MELSEC 1

MELSEC 2

Ethernet

To access C6/C64, execute READ/WRITE command to network No. 2, station No. 2

Network No.: 2 Station No.: 1 (192.168.1.1)

Network No.: 1 Station No.: 2

Network No.: 1 Station No.: 1

To access MELSEC1, execute READ/WRITE command to network No. 1, station No. 2

Network parameter setting Network type MELSECNET/10 Network No. 1 1 Station No. 1 1

Basic specification parameter settings #1926 IP address 192.168.1.2 #1927 Subnet Mask 255.255.255.0 #1928 Gateway address 0.0.0.0 #1929 Port number 64758

MNET/10 routing parameter setting Transmission destination network No. 2 Relay destination network No. 1 Relay destination station No. 2

Network parameter setting Network type Ethernet MELSECNET/10 Network No. 2 1 Station No. 1 2 IP address 192.168.1.1

Network No.: 2 Station No.: 2 (192.168.1.2)

VI. Ethernet Interface Communication Function (MELSEC Communication Protocol Section) 4. Setting the Parameters

VI - 5

4. Setting the Parameters 4.1 Setting the NC Side

The local station's IP address is set with the NC. The IP address set here is shared with the other Ethernet communication functions (GOT connection, etc.).

Parameter No. Parameter name Setting example

#1926 IP address 192. 182. 1. 2 #1927 Subnet mask 255. 255. 255. 0 #1928 Gateway address 192. 182. 1. 254 #1929 Port number 64758

4.2 Setting the GX Developer Side 4.2.1 Setting the Network Parameters

The network parameters set with the GX Developer are included in the parameter files. The parameter files set here are written into the target C6/C64. These settings include the MELSECNET/10 routing parameters. Set the following value for the head I/O No. according to the slot in which the Ethernet unit is inserted.

Inserted slot Head I/O No.

EXT1 (bottom) 200 EXT2 (top) 280

(Note) When C6/C64 is set, the NC parameter setting is validated for the IP address, and the IP

address set with this network parameter is invalidated.

VI. Ethernet Interface Communication Function (MELSEC Communication Protocol Section) 4. Setting the Parameters

VI - 6

4.2.2 Setting the GX Developer Connection Destination

These parameters set the GX Developer connection method. These parameters are included in the GX Developer project data.

5. Comparison of Functions

A comparison of the functions with the Ethernet unit mounted in the MELSEC CPU is given below.

Function C6/C64 MELSEC (Note 2)

Communication with MC protocol Communication with fixed buffers Communication with random access buffer Sending/receiving by e-mail Communication with data link buffer (data link command) (Note 1) File transmission (FTP server function) Communication with Web function

Automatic response method IP address calculation method Table conversion method

MELSECNET/H, MELSECNET/10 relay communication

Combined method Router relay communication (router relay function) (Note 3) Client device existence check Communication with pairing open Communication with automatic open UDP port Simultaneous broadcast communication Compliance with QCPU remote password function Multi-CPU system compliance Ethernet parameter setting using GX Developer Access to QCPU using GX Developer (TCP/IP or UDP/IP)

(Note 1) Only the READ, SREAD, WRITE, and SWRITE commands are supported. (Note 2) Compliance with each MELSEC function depends on the CPU model. (Note 3) If the network is configured with only one router installed for each network, the units can

communicate with each other across routers even without the router relay function.

VI. Ethernet Interface Communication Function (MELSEC Communication Protocol Section) 6. Performance Specifications

VI - 7

6. Performance Specifications

The Ethernet unit (FCU6-EX875) performance specifications are as shown below.

Item Specifications Interface 10BASE-T (RJ-45) Transmission method Base band Maximum segment length 100 m Transmission specifications

Maximum number of nodes/connection

Up to four levels with cascade connection

Number of simultaneously opened connections 8 connections

Fixed buffer Random access buffer

Transmission/reception data storage memory

e-mail

VII. Ethernet Interface Communication Function Using PLC (Client Function Section)

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 1. Outline

VII - 1

1. Outline

Using the built-in PLC dedicated commands, this function sends and receives the PLC device data to and from the devices (host computer, etc.) connected with Ethernet. The communication method (protocol) can be selected from TCP/IP or UDP/IP for each connection.

The following four dedicated commands are used with this function.

Dedicated command Function

OPEN Establishes (opens) a connection with the client device with which data is to be communicated.

BUFSND Sends data to the client device. BUFRCV Reads data received from the client device.

CLOSE Ends (closes) the connection with the client device with which data is being communicated.

The following two communication procedures (protocol) are available for communicating with the client device. These can be selected for each connection.

Protocol type Communication procedure

Procedural Data is communicated while establishing a handshake with the client device. A response must be made to the communication request. The maximum send data size is 1017 words.

Non-procedural No response is made in respect to the data reception. The maximum send data size is 2046 bytes.

2. Detailed Explanation 2.1 Connection No. in Connecting with Client Device

The client device with which data is communicated is connected with a connection port identified with a connection No. Up to eight connections, with connection No. 1 to 8, can be opened simultaneously. One connection only allows to be connected for either sending or receiving data. Thus, two connection numbers are required when sending and receiving data to and from the client device. Once the connection is closed, it can be switched to another client device.

Receive

C64

Connection 1

Connection 2

Connection 3

Connection 8

Client device A

Client device B Connection 4

Send

Receive

:

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 2. Detailed Explanation

VII - 2

2.2 Control Signals

Control signals are assigned to control the Ethernet I/F card from the built-in PLC. These control signal devices' are automatically assigned as shown below according to the slot in which the Ethernet I/F card is mounted. When two Ethernet I/F cards are mounted, the control signals are assigned to the devices with the smaller number.

Ethernet I/F card mounting position Devices to which control signals are assigned

EXT1 (bottom built-in slot) From X200/From Y200 EXT2 (top built-in slot) From X280/From Y280 EXT3 (left external slot) From X300/From Y300

Device No. Details Device No. Details

X200 /X280 /X300

Initialization normal completion

Y200 to Y20F /Y280 to Y28F /Y300 to Y30F

Blank

X210 to X217 /X290 to X297 /X310 to X317

Connections 1 to 8 Open completion

Y210 to Y21F /Y290 to Y29F /Y310 to Y31F

Blank

X220 to X227 /X2A0 to X2A7 /X320 to X327

Connections 1 to 8 Data reception status

Y220 to Y22F /Y2A0 to Y2AF /Y320 to Y32F

Blank

2.3 Response Monitor Timer

When the send connection is opened with "procedural", once the data is sent, the Ethernet I/F card will wait for a response from the client device to which the data was sent. The maximum value for this wait time is set as the response monitor timer value. If a response is not received within the set timer value time, the BUFSND command will end as an error. (The control data completion status will become C022H.) The response monitor timer is set in the following file register.

File register No. Details Setting range Default value Setting unit

R123 Response monitor timer 2 to 32767 60 500 ms

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 2. Detailed Explanation

VII - 3

2.4 Transmission Control Method

The method of control when sending data from the Ethernet I/F card to the client device is explained below using connection 1 as an example.

Command

"U20" K1 D0

M100 M101

M101

"U20" K1 D0

Process at normal completion

Process at error completion

M102 M103

M103

W0

X200 X210

Send Command

M100

Set open information in D0~

ZP.OPEN

Process at error completion

Process at normal completion

Set send data in W0~

M102

Set send information in D0~

ZP.BUFSND

Initialization Open process Data transmission

Response reception Power ON

Initialization normal completion (X200)

Open completion (X210)

OPEN command complete device M100

OPEN command

Open command complete device +1 M101

BUFSND command complete device +1 M103

BUFSND command

BUFSND command complete device M102

D at

a tra

ns -

m is

si on

R es

po ns

e

ACK (Only TCP)

ACK (Only TCP)

ON only when error occurs

The response is received only when "Procedural" is selected. The ACK response is made only when TCP/IP is selected.

1 scan

1 scan

OPEN

BUFSND

ON only when error occurs

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 2. Detailed Explanation

VII - 4

2.5 Reception Control Method

The method of control when receiving data from the client device is explained below using connection 1 as an example.

Command

Set open information in D0~

"U20" K1 D0 M100

Process at normal completion

Process at error completion

M100 M101

M101

Set control data in D0~

ZP.BUFRCV "U20" K1 D0

Process at normal completion

Process at error completion

M102 M103

M103

W0

X220 X200 X210

ZP.OPEN

M102

BUFRCV

OPEN

Initialization Open process Data reception Response transmission Power ON

Initialization normal completion (X200)

Open completion (X210)

OPEN command complete device M100

OPEN command

Open command complete device +1 M101

BUFRCV command complete device +1 M103

BUFRCV command

BUFRCV command complete device M102

D at

a re

ce pt

io n

R es

po ns

e ACK (Only TCP)

ACK (Only TCP)

ON only when error occurs

The response is sent only when "Procedural" is selected. The ACK response is made only when TCP/IP is selected.

1 scan

1 scan

ON only when error occurs Data reception status (X220)

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 3. Data Format

VII - 5

3. Data Format

The data format used when communicating data between the Ethernet I/F card and client device is explained in this section. The communication data consists of the "header" and "application data" as shown below.

Header Application data

Max. 2040 bytes (procedural) Max. 2046 bytes (non-procedural)

3.1 Header

The header is for TCP/IP and UDP/IP. The header is automatically added and deleted within the Ethernet I/F card, and does not need to be set in the program.

3.2 Application Data

The application data format differs according to the procedure setting.

(1) For procedural When procedural is selected, the format is as shown below.

Sub-header

Application data section

Application data section (Response)

Text (command)

L H L H

Data length setting section

2 bytes 2 bytes Max. 1017 words

Communica- tion request source side

Communication request receiving side

Sub-header End code

1 byte 1 byte

(a) Sub-header The sub-header format is shown below. The sub-header is automatically added and deleted within the Ethernet I/F card, and does not need to be set in the program.

Data type Set to state shown in figure (60H).

Command/response flag At command 0 At response 1

0 0 0 0 0 1 1 0 0 0 0 0 0 0 0

b0b1b2 b3 b4 b5 b6 b8 b9 b10 b11b12b13b14b15b7

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 3. Data Format

VII - 6

(b) Data length setting section

The data capacity of the text (command) section is indicated. (Indicate in number of words.)

(c) Text This is the text section actually to be sent.

(d) End code When the client device normally receives the data, the end code indicates 00H. If an error occurs, a corresponding error code is entered. The following end codes are used.

End code Details

00H Normal completion 50H Command/response type in sub-header is not specified code.

(2) For non-procedural When non-procedural is selected, all of the data is handled as valid text.

Text (command)

Application data section Max. 2046 bytes

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 4. Details of Dedicated Commands

VII - 7

4. Details of Dedicated Commands 4.1 OPEN Command

Usable devices Bit device Word device Constant Pointer

X Y M L F B SB T SM T C D R W SW Z SD K H P Index Digit

designation

S1 S2 D1

OPEN ZP.OPEN S1 S2 D1 "Un

[Command symbol] [Execution condition] Command

12 steps

Setting data

Setting data Details Data type "Un" Head input/output No. for Ethernet I/F card BIN16 bit S1 Connection No. (1 to 8) BIN16 bit S2 Head device of local station storing control data BIN16 bit

D1 Local device that turns 1 scan ON at completion of command. (D1)+1 device also turns ON at error completion.

Bit

Control data

Device Item Setting data Setting range Setting side (S2) + 0 Execution type/

completion type Fix to a setting not used by GX Developer. 8000H User

(S2) + 1 Completion status The status at completion is stored. 0000H : Normal completion Other than 0000H : Error completion

(error code)

System

(S2) + 2 Application Designate the connection application. (Indicated on User setting area b15 b9 b8 b1 b0 the left) (5) (4) (1) (1) Buffer application (bit 0)

0 : Transmission 1 : Reception

(4) Communication method (bit 8) 0 : TCP/IP 1 : UDP/IP

(5) Communication procedure (bit 9) 0 : Procedural 1 : Non-procedural

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 4. Details of Dedicated Commands

VII - 8

Device Item Setting data Setting range Setting side

(S2) + 3 Blank 0 (S2) + 4 to (S2) + 5

Client device IP address

Designate the client device's IP address. (Set 0A8C00101 for IP = 168.192.1.1)

1H to FFFFFFFFH

User

(S2) + 6 Client device port No.

Designate the port No. for the client device. 1025 to 65535 User

(S2) + 7 to (S2) + 9

Blank 0

4.2 CLOSE Command

Usable devices Bit device Word device Constant Pointer

X Y M L F B SB T SM T C D R W SW Z SD K H P Index Digit

designation

S1 S2 D1

[Command symbol] [Execution condition] Command

12 steps

CLOSE ZP.CLOSE Un S1 S2 D1 U

Setting data

Setting data Details Data type "Un" Head input/output No. for Ethernet I/F card BIN16 bit S1 Connection No. (1 to 8) BIN16 bit S2 Head device of local station storing control data BIN16 bit

D1 Local device that turns 1 scan ON at completion of command. (D1)+1 device also turns ON at error completion.

Bit

Control data

Device Item Setting data Setting range Setting side (S2) + 0 System area (S2) + 1 Completion status The status at completion is stored.

0000H : Normal completion Other than 0000H : Error completion

(error code)

System

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 4. Details of Dedicated Commands

VII - 9

4.3 BUFSND Command

Usable devices Bit device Word device Constant Pointer

X Y M L F B SB T SM T C D R W SW Z SD K H P Index Digit

designation

S1 S2 S3 D1

BUFSND ZP.BUFSND S1 S2 D1S3 Un

[Command symbol] [Execution condition] Command

13 steps

Setting data

Setting data Details Data type "Un" Head input/output No. for Ethernet I/F card BIN16 bit S1 Connection No. (1 to 8) BIN16 bit S2 Head device of local station storing control data BIN16 bit S3 Head No. of device to store the data to be sent BIN16 bit

D1 Local device that turns 1 scan ON at completion of command. (D1)+1 device also turns ON at error completion.

Bit

Control data

Device Item Setting data Setting range Setting side (S2) + 0 System area (S2) + 1 Completion status The status at completion is stored.

0000H : Normal completion Other than 0000H : Error completion

(error code)

System

Send data

Device Item Setting data Setting range Setting side (S3) + 0 Send data length Designate the send data length.

Designate the data length according to the communication procedure.

User

Procedural : No. of words 1 to 1017 Non-procedural : No. of bytes 1 to 2046

(S3) + 1 to (S3) + n

Send data Designate the send data. User

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 4. Details of Dedicated Commands

VII - 10

4.4 BUFRCV Command

Usable devices Bit device Word device Constant Pointer

X Y M L F B SB T SM T C D R W SW Z SD K H P Index Digit

designation

S1 S2 D1 D2

BUFRCV ZP.BUFRCV S1 S2 D1 Un D2

[Command symbol] [Execution condition] Command

13 steps

Setting data

Setting data Details Data type "Un" Head input/output No. for Ethernet I/F card BIN16 bit S1 Connection No. (1 to 8) BIN16 bit S2 Head device of local station storing control data BIN16 bit D1 Head No. of device to store the received data BIN16 bit

D2 Local device that turns 1 scan ON at completion of command (D1)+1 device also turns ON at error completion.

Bit

Control data

Device Item Setting data Setting range Setting side (S2) + 0 System area (S2) + 1 Completion status The status at completion is stored.

0000H : Normal completion Other than 0000H : Error completion

(error code)

System

Received data

Device Item Setting data Setting range Setting side (D1) + 0 Received data

length Designate the received data length. Designate the data length according to the communication procedure.

System

Procedural : No. of words 1 to 1017 Non-procedural : No. of bytes 1 to 2046

(D1) + 1 to (D1) + n

Received data Designate the received data. System

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 4. Details of Dedicated Commands

VII - 11

4.5 Details of Error Codes

The errors that occur when each dedicated command is executed, along with the error codes, are as shown below.

Error code Details OPEN BUFSND BUFRCV CLOSE

2111H The input/output No. is not 20, 28, or 30. The head character of the input/output No. is not "U". The Ethernet I/F card is not mounted in the designated slot.

4100H The device designation in the command is illegal. C014H The initialization process or open process is not

completed.

C017H An error occurred when opening the TCP connection. C020H The data length exceeds the tolerable range. C021H An error completion response was received. C022H The response was not received within the response

monitor timer value.

C030H A transmission error occurred. C033H A client device with the set IP address does not exist. C1A6H BUFSND was executed in a connection opened for

reception. BUFRCV was executed in a connection opened for transmission. An opened connection was tried to be opened again. The connection No. is not within the specified range.

4.6 Precautions for Programming

(1) Even if the dedicated commands (OPEN, CLOSE, BUFSND, BUFRCV) are executed with the high-speed PLC, the actual operation will take place at the same timing as the medium-speed PLC. Thus, the dedicated command should be executed with the medium-speed PLC.

(2) Do not update the BUFSND command transmission buffer until the command is completed. Failure to observe this could result in malfunctions.

(3) Refer to the BUFRCV command reception buffer after the command is completed. Failure to observe this could result in malfunctions.

(4) Open transmission using TCP after the client device's reception has been opened. If transmission is opened before reception is opened, an error completion (completion status C033) will occur. If transmission is opened for a client device with a nonexistent IP address, an error completion (completion status C033) will occur after one minute.

(5) If a connection opened with TCP is closed, and is tried to be opened again within a minute, an error completion (completion status C017) will occur. Wait a while before opening the connection again.

(6) If the connection No. is not within the specified range, an error completion (completion status C1A6) will occur, but the completion device and completion device +1 will not turn ON.

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 5. Example of Data Communication Program

VII - 12

5. Example of Data Communication Program

The following is an example of the program that executes sending (BUFSND) and receiving (BUFRCV). UDP/IP, non-procedural type are used for both commands. The send destination IP address is 192.168.1.3, and the applicable port No. is 6000. Connection 5 is used. In the actual program, the send data is set in R500 and above. For the reception, the port No. is 6001, and connection 1 is used.

Snd OPEN executn start pulse

Snd OPEN command applica- tion set

Snd OPEN command clnt dev port No.

Snd OPEN command error complet.

Snd OPEN command executn type

Snd OPEN command clnt dev IP addrs

Snd OPEN command complete

Snd OPEN command normal complet.

BUFSND control data

BUFSND complete status

BUFSND normal complet. pulse

Send start pulse

Transmi- ssion buffer

BUFSND error complet. status

CLOSE command control data

Snd OPEN command executn type

Snd OPEN command complete

Snd OPEN command normal complet.

BUFSND complete status

CLOSE command normal complet.

Snd OPEN command normal complet.

BUFSND normal complet. pulse

VII. Ethernet Interface Communication Function Using PLC (Client Function Section) 5. Example of Data Communication Program

VII - 13

Receptn OPEN executn st pulse

Receptn OPENcmnd clnt dev port No.

Receptn at conn- ection 1

BUFRCV error complet. status

Receptn OPENcmnd executn type

Receptn OPEN complete status

BUFRCV control data

BUFRCV normal complet. pulse

Receptn OPENcmnd applica- tion set

Receptn OPENcmnd error complet.

BUFRCV receptn buffer

CLSEcmnd normal complet. status

Receptn OPENcmnd clnt dev IP addrs

Receptn OPENcmnd normal complet.

BUFRCV complete status

Reception OPEN complete status

Receptn OPENcmnd normal complet.

BUFRCV complete status

BUFRCV normal complet. pulse

CLOSE command control data

Receptn OPENcmnd executn type

Receptn OPENcmnd normal complet.

VIII. MELSEC Q Series I/O/Intelligent Function Unit Connection Function

VIII. I/O/Intelligent Function Unit Connection Function 1. Outline

VIII - 1

1. Outline This function is for connecting an I/O unit / intelligent function unit of MELSEC-Q series to the NC (MELDAS C6/C64).

2. Basic Specification By adding a Q bus bridge card HR863, connection with the following specifications becomes possible. Only one Q bus bridge card can be mounted, but the maximum 4 extension base units can be mounted on the Q bus bridge card. The maximum number of slots (No. of units) is 24. MELSEC I/O connection basic specification

Item Basic specification The numbers of I/O points The maximum number of input points: 512 points

The maximum number of output points: 512 points Access to buffer memory of intelligent unit

The accessible size of MELSEC intelligent units buffer memory per scan is up to 12k words with FROM/TO command from the built-in PLC of C6/C64.

Connectable MELSEC units

Product Model Description QX10 100-120VAC/7-8mA, 16 points, response time: 20ms, terminal block AC QX28 240VAC, 8 points, terminal block

QX40 24VDC/4mA, positive common, 16 points, response time: 1/5/10/20/70ms, terminal block

QX40-S1 24VDC, 16 positive common input points, terminal block for high-speed input (Possible to set the response time to 0.1ms.)

QX41 24VDC/4mA, positive common, 32 points, response time: 1/5/10/20/70ms, connector QX42 24VDC/4mA, positive common, 64 points, response time: 1/5/10/20/70ms, connector

QX80 24VDC/4mA, negative common, 16 points, response time: 1/5/10/20/70ms, terminal block

Input unit

DC

QX81 24VDC/4mA, negative common, 32 points, response time: 1/5/10/20/70ms, connector

QY10 240VAC/24VDC, 2A/point, 8A/common, 16 points (16 points/common), output delay:12ms, without fuse, terminal block Contact

QY18A 240VAC/24VDC 2A, 8 independent output points, terminal block, without fuse AC triac QY22 240VAC, 0.6A, 16 points, terminal block, without fuse

QY40P 12/24VDC, 0.1A/point, 1.6A/common, 16 points (16 points/common), output delay:1ms, terminal block, with short protection function

QY41P 12/24VDC, 0.1A/point, 2A/common, 32 points (32 points/common), output delay:1ms, connector, with short protection function

QY42P 12/24VDC, 0.1A/point, 2A/common, 64 points (32 points/common), output delay:1ms, connector, with short protection function

Transistor (Sink)

QY50 12/24VDC, 0.5A/point, 4A/common, 16 points (16 points/common), output delay:1ms, with fuse, terminal block

Transistor QY68A 5-24VDC, 2A/point, 8A/unit, 8 points, all points independent, sink/source, terminal

block, without fuse

QY70 5/12VDC, 16mA/point, 16 points (16 points/common), output delay:0.3ms, with fuse, terminal block TTL

CMOS (Sink) QY71 5/12VDC, 16mA/point, 32 points (32 points/common), output delay:0.3ms, with fuse,

connector

QY80 12/24VDC, 0.5A/point, 4A/common, 16 points (16 points/common), output delay:1ms, with fuse, terminal block

Output unit

Transistor (Source)

QY81P 12/24VDC, 0.1A/point, 2A/common, 32 points (32 points/common), output delay:1ms, connector, with short protection function

VIII. I/O/Intelligent Function Unit Connection Function 2. Basic Specification

VIII - 2

Intelligent unit Product Model Description

QJ71FL71-T-F01 QJ71FL71-B5-F01 FL-net (OPCN-2) unit QJ71FL71-B2-F01

AS-i master unit QJ71AS92 Supports AS-i Standard Ver.2.11 Others

Product Model Description Q63B Power supply + 3 I/O slots, for mounting on Q series unit Q65B Power supply + 5 I/O slots, for mounting on Q series unit Q68B Power supply + 8 I/O slots, for mounting on Q series unit

Extension base unit

Q612B Power supply + 12 I/O slots, for mounting on Q series unit Q61P-A1 100-120VAC input/5VDC 6A output Q61P-A2 200-240VAC input/5VDC 6A output Q62P 100-240VAC input/5VDC 3A, 24VDC/0.6A output Q63P 24VDC input/5VDC 6A output

Power supply unit

Q64P 100-120/200-240VAC input, 5VDC 8.5A output

(Note 1) Maximum 4 extension base units can be mounted. (Note 2) Extension base unit without power supply cannot be used.

VIII. I/O/Intelligent Function Unit Connection Function 3. Detailed Explanation

VIII - 3

3. Detailed Explanation 3.1 Connection

Connect the NC and the MELSEC units as shown below. MELSEC unit connection

3.2 Allocation of I/O I/F (Interface) The I/O I/F between C6/C64 and MELSEC unit is 512 points (X000 to X1FF) for input and 512 points (Y000 to Y1FF) for output. By using the following devices in the built-in PLC of C6/C64, you can access to the I/O of the MELSEC units. The device number to each unit is determined by the I/O number of each unit. The I/O No. of each unit is expressed in HEX. The left end slot, which is the closest to the power supply unit, of the first extension base unit is 0H. To find the I/O No. of the next unit (the one on the right hand of the first unit), add the number of I/O points of the first unit (the one on the left hand) and express it in HEX. (A slot without a unit also occupies 16 points.) Refer to the next page for calculation examples.

QC B extension cable

C6/C64

Q bus bridge card HR863

Extension base

Extension base

The maximum number of mountable extension base units: 4 The maximum number of slots (No. of units): 24 (Including empty slot)

X000 to X1FF

Y000 to Y1FF

C6/C64 device

Extension base

Extension base

MELSEC unit

VIII. I/O/Intelligent Function Unit Connection Function 3. Detailed Explanation

VIII - 4

(1) Example of calculation of I/O numbers and device numbers

I/O No.

Device No.

Head I/O No. 0

QX41 32 input points

E m

pty

E m

pty

As 80 points (32*2+16) are occupied by Slots 0 to 2, the I/O No. of QX10 (mounted in Slot 3) is 80=50 Hex, 50H.

As 224 points (32*2+16*2+16+32*2+16*2+16) are occupied by Slots 0 to 9, the I/O No. of QY10 (mounted in Slot 10) is 224=E0 Hex, E0H.

As the I/O No. is 50H, and the unit is QX10 (input unit), the device No.s are X50 to 5F.

As the I/O No. is E0H, and the unit is QY10 (output unit), the device No.s are YE0 to YEF.

Slot No. 0 1 2 3

QX10 16 input points

QY41P 32 output points

QY10 16 output points

4 5 6 7 8 9 10 11

20 40 50 60 70 90 B0 C0 D0 E0 F0

VIII. I/O/Intelligent Function Unit Connection Function 3. Detailed Explanation

VIII - 5

(2) MELSEC I/O unit connection and access devices from C6/C64 The followings are examples of device correspondence of C6/C64.

(E.g. 1) When only I/O units are mounted

Point (E.g. 2) When intelligent function units and I/O units are mounted

Point

QX10 (16 input points)*6

QX41 (32 input points)*5 QY10 (16 output points)*6

QY41P (32 output points)*5

X000X00F X010X01F X020X02F X030X03F X040X04F X050X05F

Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable

X0C0X0DF X0E0X0FF X100X11F X120X13F X140X15F

Unavailable Unavailable Unavailable Unavailable Unavailable

Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable

Y060Y06F Y070Y07F Y080Y08F Y090Y09F Y0A0Y0AF Y0B0Y0BF

Unavailable Unavailable Unavailable Unavailable Unavailable

Y160Y17F Y180Y19F Y1A0Y1BF Y1C0Y1DF Y1E0Y1FF

Input Output C6/C64 device

As in the figure on the right, when an input unit is mounted, output devices with the same I/O No.s cannot be used. On the other hand, when an output unit is mounted, input devices with the same I/O No.s cannot be used.

QX10 (16 input points)*4

QX41 (32 input points)*5

QY10 (16 output points)*6

QY41P (32 output points)*5

X060X06F X070X07F

Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable

X160X17F Unavailable Unavailable Unavailable

Unavailable Unavailable Unavailable Unavailable

Y0C0Y0CF Y0D0Y0DF

Unavailable Unavailable Unavailable Unavailable

Input Output

C6/C64 device

Each FL-net unit and AS-i master unit occupies 32 I/O points. The I/O devices occupied by the FL-net unit and AS-i master unit cannot be used for general I/O.

FL-net unit AS-i master unit

Unavailable

X000X00F X010X01F X020X02F X030X03F X040X04F X050X05F

Y000Y00F Y010Y01F Y020Y02F Y030Y03F

Y080Y08F Y090Y09F Y0A0Y0AF Y0B0Y0BF

X0E0X0FF X120X13F X140X15F

Y180Y19F Y1A0Y1BF Y1C0Y1DF Y1E0Y1FF

VIII. I/O/Intelligent Function Unit Connection Function 3. Detailed Explanation

VIII - 6

3.3 Access to Intelligent Function Units This section explains how to access to a MELSEC intelligent function unit from the built-in PLC of C6/C64.

3.3.1 Reading Buffer Memory (by FROM command) To read the buffer memory of the MELSEC intelligent function unit by the built-in PLC in C6/C64, use an FROM command.

Usable device

Bit device Word device

C on

st an

t

Po in

te r

X Y M L F B SB T SM V T C D R W SW Z SD K H P D ig

it sp

ec ifi

ca tio

n

In de

x

Th e

nu m

be r o

f st

ep s

n1 n2 Dn n3

5

(Note) As for bit device, the only available unit for designation is 16 bits.

(E.g.) To read 32 words of data in Area 2 of the FL-net unit (buffer memory address 2000H) and write them into D0 to D31 of data register in the configuration above. (The I/O number of FL-net unit in the configuration above is 000.)

FROM n1 n2 Dn n3

Execution condition

n1: Head I/O No. (Designate the first two digits of the 3-digit I/O No. allocated to the intelligent function unit.)

n2: Head address of the buffer memory in which the data to read is stored. Dn: Head No. of the PLC register of C6/C64 which will store the read data. n3: The number of words of the data to read.

FROM H0 H2000 D0 K32

Execution condition

C6/C64

Q bus bridge card HR863

FL-net unit AS-i master unit

VIII. I/O/Intelligent Function Unit Connection Function 3. Detailed Explanation

VIII - 7

3.3.2 Writing in Buffer Memory (by TO command)

To write data into the buffer memory of the MELSEC intelligent function unit from the built-in PLC in C6/C64, use a TO command.

Usable device

Bit device Word device

C on

st an

t

Po in

te r

X Y M L F B SB T SM V T C D R W SW Z SD K H P D ig

it de

si gn

at io

n

In de

x

Th e

nu m

be r o

f st

ep s

n1 n2 Dn n3

5

(Note) As for bit device, the only available unit for designation is 16 bits. (E.g.) To write 32 words of data in data register D1000 to D1031 into the buffer memory addresses 2040H

to 205FH of FL-net units Area 2. (The I/O number of FL-net unit in the configuration above is 000.)

TO

Execution condition

n1 n2 Dn n3

n1: Head I/O No. (Designate the first two digits of the 3-digit I/O No. allocated to the intelligent function unit.)

n2: Head address of the buffer memory in which the data to write is stored. Dn: Head No. of the PLC register of C6/C64 which will store the written

data. n3: The number of words of the data to write.

Execution condition

TO H0 H2040 D1000 K32

VIII. I/O/Intelligent Function Unit Connection Function 3. Detailed Explanation

VIII - 8

3.3.3 Restrictions in Using FROM/TO Commands

Using FROM/TO command by the built-in PLC in C6/C64 has the restrictions below. (1) The number of FROM and TO commands that can be used in one scan (including multiple program) is

50 each. Using more than 50 will cause the alarm "Q01 EMERGENCY STOP LAD 0005", and will stop the built-in PLC.

(2) The accessible size of buffer memory in one scan (including multiple program) by FROM/TO command

is up to 12k words. Exceeding 12k words will cause the alarm "Q01 EMERGENCY STOP LAD 0006", and will stop the built-in PLC.

(3) Actual transfer from the buffer memory to read devices by FROM command, and transfer from write

devices to the buffer memory by TO command are done at the execution of END command. (In multiple programs, at the execution of END command at the end of all the programs.) Thus, device data renewal will be delayed by 1 scan.

Token p-

articip- at. sta- tus sig.

Head of node 01 area 1 readdata

(4) FROM/TO commands cannot be used in high-speed program processing.

If FROM/TO command is executed in high-speed program processing, the alarm "Q01 EMERGENCY STOP LAD 0007" will occur and the built-in PLC will stop.

(5) If bit device is used for FROM/TO command, the only available unit for designation is 16 bits. If bit device is not designated in the unit of 16 bits, the alarm "Q01 EMERGENCY STOP LAD 0008" will occur and the built-in PLC will stop. Correct example : FROM H0 H1C00 K4B20 K32 TO H0 H1C80 K4M64 K32 Incorrect example : FROM H0 H1C00 K4B28 K32 "Q01 EMERGENCY STOP LAD 0008" TO H0 H1C80 K4M100 K32 "Q01 EMERGENCY STOP LAD 0008"

Other n- ode area 1 data ref dev.

Local n- ode area 1 output device

Head of node 03 area 1 wrt data

Other n- ode area 1 data ref dev.

Local n- ode area 1 output device

Actual writing in the devices B0 to B5F from the buffer memory by the FROM command is executed at this point.

The device B0 used here is in the state of the previous scan.

At this point, a transfer command to B0 to B5F is issued by the FROM command, however, the transfer will not actually be executed at this point.

VIII. I/O/Intelligent Function Unit Connection Function 3. Detailed Explanation

VIII - 9

3.3.4 Access to I/O of Intelligent Function Units

MELSEC intelligent function unit occupies I/O as I/O units do, and the I/O controls the unit itself or judges the status. In an access from C6/C64s built-in PLC to I/O of an intelligent function unit, use X000 to X1FF and Y000 to Y1FF (the I/O I/F). Device numbers are determined by I/O numbers allocated to the intelligent function unit. Each device number will be "I/O number + 00 to 1F".

The I/O devices of each intelligent unit in the case that the units are mounted as shown in the figure above are as follows.

Intelligent unit Input devices Output devices

FL-net unit 1 X000 to X01F Y000 to Y01F AS-i master unit X020 to X03F Y020 to Y03F

C6/C64

Q bus bridge card HR863

FL-net unit AS-i master unit

16-point I/O units

I/O No. 00 20 40 50 60 70 80 90 A0 B0 C0 D0

VIII. I/O/Intelligent Function Unit Connection Function 4. Other Notices

VIII - 10

4. Other Notices 4.1 Notices in Connecting Remote I/O Unit

(1)When a remote I/O unit is connected, the priority is on the input signals from the remote I/O unit.

If a remote I/O unit that occupies 32 points is connected to Channel 1 for remote I/O as shown in the figure below, the I/O signals from MELSEC (X000 to X01F) will be ignored, and the I/O signals from the remote I/O unit will be validated. As for output signals, the same signals are output to the remote I/O unit and MELSEC.

X00F.X000 X01F.X010

X02F.X020 X00F.X030 X01F.X040 X02F.X050 : : : : X01F.X070 X1FF.X1F0

Input from MELSEC unit (512 points)

Input from remote I/O (32 points)

QC B extension cable

C6/C64

Q bus bridge card HR863

Extension base unit

Extension base unit

Remote I/O unit

VIII. I/O/Intelligent Function Unit Connection Function 4. Other Notices

VIII - 11

(2) When intelligent function unit and remote I/O unit are connected When an intelligent function unit is used, access to the units buffer memory needs to be controlled by I/O signals from the unit, so access to the unit may not be done properly if I/O signals from the remote I/O unit lap over. To use an intelligent function unit and remote I/O unit together, connect the remote I/O unit to Channel 2, so that their I/O signals will not lap over.

X00F.X000 X01F.X010

: : X0EFX0E0 X0FFX0F0 X10F.X100 X11F.X110 : : X1EFX1E0 X1FFX1F0

I/O signals from the remote I/O (Ch 2) (Allocated to X100 to X1FF)

Input from FL-net unit (32 points)

FL-net unit

C6/C64

Ch 2 for remote I/O (RIO M/S connector)

Remote I/O unit (Within 8 channels)

Ch 2

VIII. I/O/Intelligent Function Unit Connection Function 4. Other Notices

VIII - 12

4.2 Built-in PLCs Scan Time As mentioned in the section of restrictions, up to 50 FROM/TO commands are available in one scan, and the maximum size of access to the buffer memory by FROM/TO command is 12k words. However, as FROM/TO command takes longer for processing compared with other commands, it greatly affects on the scan time of the built-in PLC. Keep the number of FROM/TO commands as low as possible. Reference: FROM/TO command processing time

Command Command base processing time Data transfer time

FROM command 115s 1.29s/word TO command 110s 1.29s/word

Example of processing time calculation: FROM H0 H2000 D1000 K64 (Read 64 words of the address 2000H of the buffer memory and write them in D1000)

Command processing time=Command base processing time + Data transfer time =115 +1.29*64 =197.56s

4.3 Buffer Memory Address

Trying to access to an illegal address (that doesnt exist in terms of MELSEC intelligent units spec) with the intelligent units buffer memory access by FROM/TO command will cause the alarm "Q01 EMERGENCY STOP LAD 0009", and will stop the built-in PLC.

VIII. I/O/Intelligent Function Unit Connection Function 5. Alarm List

VIII - 13

5. Alarm List Descriptions and remedies for the alarms that may occur during using this function.

Message Description Remedy

Q01 EMERGENCY STOP LAD 0002

FROM/TO command was issued without mounting a Q bus bridge card HR863.

Mount a Q bus bridge card HR863.

Q01 EMERGENCY STOP LAD 0003

In FROM/TO command, a minus value was set as the head I/O number.

Correct the head I/O number.

Q01 EMERGENCY STOP LAD 0004

In FROM/TO command, a minus value was set as the transfer size.

Correct the transfer size.

Q01 EMERGENCY STOP LAD 0005

There are more than 50 FROM/TO commands in one scan.

Review the built-in PLCs program so that the number of each FROM command and TO command does not exceed 50.

Q01 EMERGENCY STOP LAD 0006

The size of access to the buffer memory by FROM/TO command in one scan exceeded 12k words.

Review the built-in PLCs program.

Q01 EMERGENCY STOP LAD 0007

FROM/TO command was used in high-speed program processing.

As FROM/TO command is not available in high-speed program processing, delete the command.

Q01 EMERGENCY STOP LAD 0008

The unit when designating bit device in FROM/TO command is not 16 bits.

Change the unit of bit device number to 16 bits.

Q01 EMERGENCY STOP LAD 0009

In access to MELSEC intelligent units buffer memory by FROM/TO command, an illegal address (that doesnt exist in terms of the units spec) was accessed.

Of the built-in PLCs FROM/TO command, review the part that designates the buffer memory address.

Q01 EMERGENCY STOP LAD 000A

An alarm occurred in the MELSEC unit mounted on an extension base unit.

Check the MELSEC unit that is mounted on an extension base unit.

The head I/O No. designated by FROM/TO command and the actual position of the mounted intelligent function unit (the units I/O No.) dont match.

Check if the head I/O No. and the units mounted position are correct. If wrong, correct the head I/O No. of the FROM/TO command.

Q01 EMERGENCY STOP LAD 000B

The head address designated by FROM/TO command is out of the range of the intelligent function units buffer memory address.

Check the head address of the FROM/TO command. If its wrong, correct the head address.

(Note) To release the alarm, reboot the NC after completing the remedy.

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 14

6. Supplement (Example of built-in PLC when FL-net unit is used) The following is an example of built-in PLC when MELSEC FL-net unit is connected as below.

This example is on the assumption that FL-net is used when its common memory Area 1 and 2 are allocated to each node as shown in the left of the figure below, and the C64s built-in PLC (node 3) allocates devices as shown in the right of the figure below.

Node 01 (Size: 4 words)

Area 1 (Bit area)

Node 02 (Size: 2 words)

Node 03 (Size: 4 words)

Node 04 (Size: 2 words)

Node 05 (Size: 4 words)

1C00

1C04

1C06

1C0A

1C0C

Node 01 (Size: 64 words)

Area 2 (Word area) 2000

Node 02 (Size: 64 words)

2040

Node 03 (Size: 32 words)

Node 04 (Size: 32 words)

Node 05 (Size: 64 words)

2080

20A0

20C0

Node 01 (Size: 64 words)

Node 02 (Size: 64 words)

Node 03 (Size: 32 words)

Node 04 (Size: 32 words)

Node 05 (Size: 64 words)

W0000

W0040

W0080

W00A0

W1000

Node 01 (Size: 4 words)

Node 02 (Size: 2 words)

Node 04 (Size: 2 words)

Node 05 (Size: 4 words)

B0000

B0040

B0060

B0080

Node 03 (Size: 4 words)

B1000

FL-net unit buffer memory

FROM

FROM

FROM

FROM

FROM

FROM

FROM

FROM

TO

TO

Built-in PLCs device of C64

Node 01

FL-net (OPCN-2) Node 02 Node 03 Node 04 Node 05

IP address: 192.168.250.3

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 15

6.1 Input/Output Signal List FL-net units input/output signals are explained in this section. The input/output signal assignment is performed on the assumption that the FL-net unit is mounted in the slot on an extended base unit. Note that device X indicates the input signal from FL-net unit to NC, and device Y indicates the output signal from NC to FL-net unit.

Signal direction: NC FL-net unit Signal direction: NC FL-net unit

Input No. Signal name Output No. Signal name

X00 Message send normal completion ON: Normal completion OFF: - Y00 Message send request

ON: Request OFF: -

X01 Message send error completion ON: Error completion ending OFF: - Y01 Use prohibited

X02 Message being received ON: Being received OFF: Not received Y02 Message reception completion

ON: Request OFF: - X03 to

X0F Use prohibited

Y03 to

Y0F Use prohibited

X10 Network parameter write completion ON: Completed OFF: - Y10 Network parameter write request

ON: Request OFF: -

X11 Network parameter read completion ON: Completed OFF: - Y11 Network parameter read request

ON: Request OFF: - X12 Use prohibited Y12 Use prohibited

X13 Device profile read completion ON: Completed OFF: - Y13 Device profile read request

ON: Request OFF: -

X14 Log data clear completion ON: Completed OFF: - Y14 Log data clear request

ON: Request OFF: -

X15 Log data read completion ON: Completed OFF: - Y15 Log data read request

ON: Request OFF: - X16 Use prohibited X17 Use prohibited

X18 Parameter setting status ON: Error OFF: Normal

X19 Token participation status ON: Participation OFF: Released

X1A Use prohibited X1B Use prohibited

X1C Unit ready

ON: Preparation completed OFF: In initialization

X1D Use prohibited X1E Use prohibited

X1F Watchdog timer error detection ON: Detected OFF: Not detected

Y16

to

Y1F

Use prohibited

CAUTION

Do not turn "Use prohibited" signal ON among the signals output to FL-net unit (Y00 to Y1F). Failure to observe this could result in malfunction the device mounted on the extension base unit.

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 16

6.2 Initial Setting The following is an example of initial processing of FL-net unit. (The local node number is Node 03.)

Node name setting temp. 2

At completion of initial setting, go to P10.

Set the node name (equipment name) in initial setting temporary (optional).

Set the lower part (250.3) of IP address (192.168.250.3) in initial setting temporary.

Set the higher part (192.168) of IP address (192.168.250.3) in initial setting temporary.

Set the head address of Area 1 in initial setting temporary.

Set the size of Area 1 in initial setting temporary.

Set the head address of Area 2 in initial setting temporary. Set the size of Area 2 in initial setting temporary. Set the token monitoring timeout time in initial setting temporary.

Set the minimum permissible frame interval in initial setting temporary.

Initial. complete flag

Node name setting temp. 1

IP addr. (Low) setting temp. 1

Spare

Area 1 head addr set temp.

Area 1 size set temp.

Token monitor timeout set temp

Min per- missible interval set temp

Node name setting temp. 3

Node name setting temp. 4

Node name setting temp. 5

IP addr. (High) setting temp. 1

Area 2 head addr set temp.

Area 2 size set temp.

Initial. complete flag

H4740

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 17

(Note) Automatic refresh cannot be set. Execute refresh by programming with FROM/TO commands.

Data and description of parameter setting errors (List of error data in D100 and its description) D100s data Description of error Remedy

C021H Wrong IP address (network address) setting Correct the IP address and perform initial process again.

C022H Wrong IP address (host address) setting Correct the IP address and perform initial process again.

C023H Wrong setting value for common memory area 1 head address

Correct setting value for common memory area 1 head address and perform initial process again.

C024H Wrong setting value for common memory area 1 size

Correct setting value for common memory area 1 size and perform initial process again.

C025H Setting value for common memory area 1 head address or size is outside permissible range.

Correct setting value for common memory area 1 head address and size and perform initial process again.

C026H Wrong setting value for common memory area 2 head address

Correct setting value for common memory area 2 head address and perform initial process again.

C027H Wrong setting value for common memory area 2 size

Correct setting value for common memory area 2 size and perform initial process again.

C028H Setting value for common memory area 2 head address or size is outside permissible range.

Correct setting value for common memory area 2 head address and size and perform initial process again.

C029H Wrong setting value for token monitoring timeout time

Correct setting value for token monitoring timeout time and perform initial process again.

C02AH Wrong setting value for minimum permissible frame interval

Correct setting value for minimum permissible frame interval and perform initial process again.

C02CH Setting for common memory area overlaps other node setting range

Correct setting value for common memory and perform initial processing.

Unit ready signal

Node name setting temp.1

Network param. write request

Network para.wrt complete signal

Param. write error info.

Network param. write request

Para set status: error

Initial. complete flag

Param. setting error info.

Network para. write request

Para set status: normal

Write the initial setting temporary in the local node parameter area on the buffer memory of FL-net. Parameter writing request ON.

Parameter writing request OFF.

Set parameter writing status.

Initialization completion flag ON.

Parameter writing request OFF. Read parameter setting error information.

Initialization completed. Cyclic transmission processing (Next page) P10 53

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 18

6.3 Cyclic Transmission The following is an example of communication processing by cyclic transmission of FL-net unit.

Head of node 03 area 1 wrt data

Local n- ode area 1 output device

Express transmission data in Area 1 of the other nodes as Bit device of C64.

Create and process the cyclic transmission data of the local node based on the cyclic transmission data from the other nodes.

Read the data in Area 2 of Node 01 and 02 and write it in W100 to W17F.

Read the data in Area 2 of Node 04 and 05 and write it in W180 to W1DF. Write output word data in Area 2 of the local node.

Read the data in Area 1 of Node 01 and 02 and write it in W000 to W005.

Read the data in Area 1 of Node 04 and 05 and write it in W006 to W00B. Write output bit data in Area 1 of the local node.

Head of node 01 area 1 readdata

Other n- ode area 1 data ref dev.

Token p- articip- at. sta- tus sig.

W80

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 19

6.4 Message Transmission 6.4.1 Outline of Message Transmission

Message transmission is the function supporting the asynchronous data exchange generated among nodes. (1) When a node receives a token, it sends up to one (message) frame before transmitting cyclic frames. (2) Data volume that can be transmitted in a frame is equal to or less than 1024 bytes (512 words). (3) Algorithm is provided so as not to exceed allowable refresh cycle time for cyclic transmission. (4) Both "1:1 transmission" transmitting to a specific destination node and "1:n broadcast transmission"

transmitting to all nodes are provided. (5) Delivery acknowledgement function is provided to confirm successful delivery of data to the destination

node on the "1:1 transmission".

Node 01 Node 02 Node 03

Request

Response

1:1 Transmission

Request

Receive Receive

1:n Broadcast transmission

Node 01 Node 02 Node 03

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 20

6.4.2 Transaction Code Each message has a header with a transaction code for requesting or responding, which is used for identifying the message frame.

Transaction code

Decimal Hex Application

0 to 59999 0000H to EA5FH Transparent type message 60000 to 64999 EA60H to FDE7H Reserved 65000 FDE8H Cyclic header (with token) 65001 FDE9H Cyclic header (without token) 65002 FDEAH Participation request frame header 65003 FDEBH Byte block data read (request) 65004 FDECH Byte block data write (request) 65005 FDEDH Word block data read (request) 65006 FDEEH Word block data write (request) 65007 FDEFH Network parameter read (request) 65008 FDF0H Network parameter write (request) 65009 FDF1H Stop command (request) 65010 FDF2H Operate command (request) 65011 FDF3H Profile read (request) 65012 FDF4H Trigger header 65013 FDF5H Log read (request) 65014 FDF6H Log clear (request) 65015 FDF7H For message return test (request) 65016 to 65202 FDF8H to FEB2H Reserved 65203 FEB3H Byte block data read (response) 65204 FEB4H Byte block data write (response) 65205 FEB5H Word block data read (response) 65206 FEB6H Word block data write (response) 65207 FEB7H Network parameter read (response) 65208 FEB8H Network parameter write (response) 65209 FEB9H Stop command (response) 65210 FEBAH Operate command (response) 65211 FEBBH Profile read (response) 65212 FEBCH Reserved 65213 FEBDH Log read (response) 65214 FEBEH Log clear (response) 65215 FEBFH For message return test (response) 65216 to 65399 FEC0H to FF77H Reserved 65400 to 65535 FF78H to FFFFH Reserved

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 21

6.4.3 Support Message List This section explains available message transmissions from C64s user PLC.

(1) Transparent type message transmission

Message data (up to 512 words) can be sent and received to and from the message area of a specified node. Possible to use arbitrary transaction codes (0 to 59999).

(2) Return data response

It is possible to return the received data as-is whenever a return command is received.

(3) Reading of the parameters It is possible to read the network parameters (such as vendor name, token monitoring time, etc.) for each node.

(4) Reading and clearing of log data

It is possible to read and clear the communication log data held by each node.

(5) Reading of device profile It is possible to read the device profile data held by each node.

Support message list

Client function (*2)

No. Message 1:1 1:n Server function (*1)

Transparent type message

transmission (*3) 1 Byte block read (*4) 2 Byte block write (*4) 3 Word block read (*4) 4 Word block write (*4) 5 Network parameter read 6 Network parameter write 7 Operate/stop command 8 Profile read 9 Log data read 10 Log data clear 11 Message return 12 PING

13 Transparent type message transmission

*1: Server function ....... Functions that create a response frame for the request message that has been received and send it.

*2: Client function......... Functions that send the request message and receive the response frame. *3: Realized by the transparent type message transmission. Refer to the next page for the transparent

type message transmission procedures. *4: If this message is received not in the transparent type message, the device data which can be

read/written is not of C6/C64.

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 22

6.4.4 Support Message Details This section explains details of message transmission available from C64s user PLC.

(1) Transparent type message transmission

This function writes messages to the corresponding nodes received message area from the network. Arbitrary transaction codes (0 to 59999) are available. By arranging transaction codes with the destination node, various messages can be transmitted. As FL-net unit itself doesnt return response messages, if response messages are necessary, response message creation process has to be carried out with the user PLC program.

Item Request Response Transaction code 0 to 59999 -

Parameter Object node number Data size (Word unit) -

User data Data (512 word space) -

Node 01 (To send)

FL-net (OPCN-2)

Node 02 (To receive)

Object node No.:02 Transaction code Send data size

Send data area

(512 words)

D2000

Set message data in message send device (e.g.: from D2000

C64 User PLC

When Message send completion signal (X00/X01) is turned ON, turn Message send request signal (Y00) OFF.

Message send request signal (Y00) ON.

Send source node No.:02 Transaction code Receive data size Receive data area

(512 words)

6400H C64 User PLC

When Message being received signal (X02) turns OFF, turn Message reception completion signal (Y02) OFF.

Message reception completion signal (Y02) ON.

By TO command, the message send data is transferred to the message data send area.

Object node No.:02 Transaction code Send data size

Send data area

(512 words)

6000H

Execute processing according to the transaction code of the received message.

Send source node No.:02 Transaction code Receive data size

Receive data area

(512 words)

D3000

When Message being received signal (X02) turns ON, the message is transferred from the message data receive area to the receive devices (e.g.: from D3000) by FROM command.

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 23

[Example of user PLC program]

(a) Message send

Mesg. snd normal complet. signal

Message snd err. complet. signal

Mesg snd normal complet. signal

Message send complete memo

Message send request signal

Message send request signal

Message send start signal

Token partici- pat. st- atus sig.

Transpa- rent typ mesg snd results

Mesg. snd error complet. signal

Token participation Request Response

Object node

Transaction code

Send data size

Set send data in message data send area.

Message send request.

Message send completion.

Message send normal completion.

Mesg. send error completion Write diag. data into D101.

Set the send data in D2003 to D2514. Set send data.

S en

d

R es

po ns

e

A

B

C

Token participation status (X19)

Set send message

Message send request (Y00)

Message send normal completion (X00)

Message send error completion (X01)

Data setting & Y00 ON

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 24

A : Check if FL-net units "Token participation status" signal (X19) is ON. B : After setting data below in message send devices, transfer the message to the message data send area,

then turn "Message send request" signal (Y00) ON. Object node number Transaction code Send data size Send data

C : Check the completion of the message send.

"Message send normal completion" signal (X00): ON "Message send error completion" signal (X01): OFF

"Message send normal completion" signal (X00): OFF "Message send error completion" signal (X01): ON

At an error completion, refer to the diagnosis data in D101 (see the table below) and correct the FL-net parameters or user PLC, then reboot C6/C64.

After confirming that "Message send normal completion" signal (X00) or "Message send error completion" signal (X01) is ON, turn "Message send request" signal (Y00) OFF.

Data and description of message transmission errors (List of error data in D101 and its description)

D101s data Description of error Remedy

C321H Setting value for object node number is outside permissible range.

Correct setting value for object node number.

C322H Object node does not exist. Correct setting value for object node number. Check operation of corresponding equipment.

C323H No response from object node for 10 seconds or more.

Correct setting value for object node number. Check operation of corresponding equipment.

C324H Error in send data. Correct send data.

C325H The transaction code includes the process that is not supported by FL-net unit.

Correct transaction code.

C326H No empty capacity in object node buffer.

Re-execute after waiting for a while.

C328H Not participating in token. Check the status of the PLC and wires. Review the settings for the initial process.

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 25

(b) Message receive

MsgRcpt: send so- urce node No.

Msg rec- eption: received data

Msg rec- eption: rcvd d- ata size

Msg rec- eption: transac- tn code

Unsuppo- rted message

Other error

Receiv- ing message signal

Response message type

Normal reception

Error message response

Receive processing

Response processing

Error processing

Normal receive

Error receive

Error receive

Error receive

Normal data receive determination

Read receive data.

Request receive determination

Message receive completion.

Read the response message type.

Message send: object node No.

Request receptn

Message send: transac- tn code

Message receptn complete signal

MsgRcpt: send so- urce node No.

MsgRcpt: transac- tn code

Response message type

Response message type

Response message type

Unsuppo- rted message

Normal reception

Error message response

Receiv- ing message signal

Normal recept- ion

Receiv- ing message signal

Normal recept- ion

Request recept- ion

Request recept- ion

Other error

Error message response

Message receptn complete signal

Unsuppo- rted message

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 26

Receive Response

A : After the received message data is set in message receive device, turn "Message being received"

signal (X02) ON.

B : After transferring (writing) the message data to device, turn "Message reception completion" signal (Y02) ON.

C : After confirming that "Message being received" signal (X02) is OFF, turn "Message reception completion" signal (Y02) OFF.

(Note) If response is necessary at receiving message data, create a sequence program for responding.

(2) Message return

This function returns the received message. The message return is performed automatically within the FL-net unit. Thus, there is no necessity for C6/C64s user PLC to perform processing.

Item Request Response

Transaction code 65015 65215 Parameter Object node number - User data Test data (512 words space) Test data (512 words space)

FL-net (OPCN-2) Request message

Object node number

Response message

R es

po ns

e

R ec

ei ve

A

B

C

Received data is stored in message receive device Message being received (X02)

Received message data processing and Y02 turns ON

Message reception completion (Y02)

Data storage

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 27

(3) Read network parameters This function reads network parameters (such as vendor name, token monitoring time, etc.) for each node.

Item Request Response Transaction code 65007 65207

Parameter Object node number - User data - Node number

Vendor name Manufacturers model Node name (equipment name) Address and size of common memory Token monitoring timeout time Refresh cycle time Refresh cycle time (Actual value) Permissible minimum frame interval Upper layer status FL-net (OPCN-2) status Protocol version

Network parameter Node number Vendor name Manufacturers model Node name (equipment name) Area 1 head address Area 1 size Area 2 head address Area 2 size Token monitoring timeout time Permissible minimum frame interval FL-net (OPCN-2) status Protocol version Upper layer status Refresh cycle permissible time RCT setting value Refresh cycle measurement value (Current) Refresh cycle measurement value (Maximum) Refresh cycle measurement value (Minimum)

FL-net (OPCN-2)

Request message

Object node number

Response message

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 28

Example of user PLC program

Token participation Request Response A : Check if "Token participation status" signal (X19) of FL-net unit is ON. B : After setting the parameter reading object node number in the message send device D2000 (node

number setting device), set the number in the buffer memory by "TO" command, then turn "Network parameter read request" signal (Y11) ON.

C : FL-net unit stores the object nodes parameter data in the buffer memory (address: 1200H to 121bH). After stored, the parameter data is transferred to the message reception device D3003 and later.

D : Check the completion of the parameter reading. "Network parameter read completion" signal (X11): ON Parameter reading result (D103): 0

"Network parameter read completion" signal (X11): ON Parameter reading result (D103): Other than 0

Error completion processing

Set the object node number.

Parameter reading request

Parameter reading completion

Read normal completion parameter data.

Error completion

Read parameter reading result.

Set the parameter reading object node No. in buffer memory.

Param. read results

Message recptn: Rcvd data

Message send: object node No.

Param. read request

Message send start signal

Token p- articip- at. sta- tus sig.

Message send: object node No.

Param. read request

Param. read results

Param. read results

Node No. setting

R eq

ue st

R es

po ns

e

A

B

C

Token participation status (X19)

Network parameter read request (Y11)

Read data setting

Network parameter read completion (X11)

Read object node No. setting

D

Data setting

Param. read complete signal

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 29

At an error completion, refer to the diagnosis data in D103 (see the table below) and correct the FL-net parameters or user PLC, then reboot C6/C64.

After confirming "Network parameter read completion" signal (X11) is ON, turn "Network parameter read request" signal (Y11) OFF.

Data and description of parameter reading result errors (List of error data in D103 and its description)

D103s data Description of error Remedy

C321H Setting value for object node number outside permissible range.

Correct setting value for object node number.

C322H Object node does not exist. Correct setting value for object node number. Check operation of corresponding equipment.

C323H No response from object node for 10 seconds or more.

Correct setting value for object node number. Check operation of corresponding equipment.

C324H Error in send data. Correct send data.

C326H No empty capacity in object node buffer.

Re-execute after waiting for a while.

C328H Not participating in token Check the status of the PLC and wires. Review the settings for the initial process.

(4) Log data read

Message function for reading corresponding node log data from the network. Item Request Response

Transaction code 65013 65213 Parameter Object node number - User data - Send and receive log

Frame log Cyclic transmission error log Message transmission error log ACK error log Token error log Status data Participation node list

FL-net (OPCN-2) Request message

Object node number

Response message

For details of log data, refer to MELSEC Q Series FL-net (OPCN-2) Interface Module Users Manual (QJFL71-F01-U-SY-J/E), section 3.2.5 (3) Details of buffer memory, item (f) Log data acquisition area.

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 30

Example of user PLC program

Token participation Request Response A : Check if FL-net units "Token participation status" signal (X19) is ON. B : After setting the log data read object node No. in message send device D2000 (node No. setting device),

set the data in the buffer memory by "TO" command, and turn "Log data read request" (Y15) ON. C : FL-net unit stores the log data of the object node in the buffer memory (address: from 1600H).

After stored, the log data is transferred to the message reception device D3003 and later. D : Check the log data read completion.

"Log data read completion" signal (X15): ON Log data reading result (D104): 0

"Log data read completion" signal (X15): ON Log data reading result (D104): Other than 0

Error completion processing

Set object node No.

Log data read request

Log data read completion

Normal completion

Error completion

Set log data reading object node No. in buffer memory.

Read log data reading result.

Message send: object node No.

Message send start signal

Token p- articip- at. sta- tus sig.

Message send: object node No.

Log data read results

Message send: send data

Log info read request

Log info read complete data

Log data read results

Log data read results

Log info read request

A

B

C

Node No. setting

R eq

ue st

R es

po ns

e

Token participation status (X19)

Log data read request (Y15)

Log data read completion (X15)

Read data setting

Read object node No. setting

Data setting

D

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 31

At an error completion, refer to the diagnosis data of D104 (see the table below) and correct the FL-net parameters or user PLC, then reboot C6/C64.

After confirming that "Log data read completion" signal (X15) is ON, turn "Log data read request" signal (Y15) OFF.

Data and description of log data reading result errors (List of error data in D104 and its description)

D104s data Description of error Remedy

C321H Setting value for object node number is outside permissible range.

Correct setting value for object node number.

C322H Object node does not exist. Correct setting value for object node number. Check operation of corresponding equipment.

C323H No response from object node for 10 seconds or more.

Correct setting value for object node number. Check operation of corresponding equipment.

C324H Error in send data. Correct send data.

C326H No empty capacity in object node buffer.

Re-execute after waiting for a while.

C328H Not participating in token. Check the status of the PLC and wires. Review the settings for the initial process.

(5) Log data clear

Message function for clearing corresponding node log data from the network.

Item Request Response Transaction code 65014 65214

Parameter Object node number - User data - -

FL-net (OPCN-2) Request message

Object node number

Response message

Log data clear

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 32

Example of user PLC program

Token participation Request Response A : Check if FL-net units "Token participation status" signal (X19) is ON. B : After setting the log data clear object node number is set in message send device D2000 (node number

setting device), set the data in the buffer memory by "TO" command, and turn "Log data clear request" signal (Y14) ON.

C : Check the log data clear completion. "Log data clear completion" signal (X14): ON Log data clear result (D105): 0

"Log data clear completion" signal (X14): ON Log data clear result (D105): Other than 0

At an error completion, refer to the diagnosis data in D105 (see the table below) and correct the FL-net parameters or user PLC, then reboot C6/C64.

Error completion processing Error completion

Set object node No.

Log data clear request

Log data clear completion

Set log data clear object node No. in buffer memory.

Read log clear result.

A

B

C

Node No. setting

R eq

ue st

R es

po ns

e

Token participation status (X19)

Log data clear request (Y14)

Log data clear completion (X14)

Clear object node No. setting

Message send: object node No.

Message send start signal

Token p- articip- at. sta- tus sig.

Log data clear results

Log info clear request

Log info clear complete signal

Message send: object node No.

Log info clear request

Log data clear results

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 33

After confirming that "Log data clear completion" signal (X14) is ON, turn "Log data clear request" signal (Y14) OFF.

Data and description of log data clear result errors (List of error data in D105 and its description)

D105s data Description of error Remedy

C321H Setting value for object node number outside permissible range.

Correct setting value for object node number.

C322H Object node does not exist. Correct setting value for object node number. Check operation of corresponding equipment.

C323H No response from object node for 10 seconds or more.

Correct setting value for object node number. Check operation of corresponding equipment.

C324H Error in send data. Correct send data.

C326H No empty capacity in object node buffer.

Re-execute after waiting for a while.

C328H Not participating in token. Check the status of the PLC and wires. Review the settings for the initial process.

(6) Device profile read

This function reads the device profile data that is the data for the corresponding node from the network. The data format for the device profile data is based on ASN1.1 (Abstract Syntax Notation One) conversion rules for transmission encoding as stipulated in ASN1.1 Basic Encoding Rule (ISO/IEC 8825).

Item Request Response Transaction code 65011 65211

Parameter Object node number - User data - System parameter

System parameter

Common specifications version Identifier character string Revision number Revision date Device classification Vendor name Product model

FL-net (OPCN-2) Request message

Object node number

Response message

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 34

Example of user PLC program

Token participation Request Response A : Check if FL-net units "Token participation status" signal (X19) is ON. B : After setting the device profile reading object node number in message send device D2000 (node

number setting device), set the data in the buffer memory by "TO" command, and turn "Device profile read request" signal (Y13) ON.

C : FL-net unit stores the device profile data of the object node in the buffer memory (address: from 1400H). After stored, the parameter data is transferred to the message reception device D3003 and later.

D : Check device profile reading completion. "Device profile read completion" signal (X13): ON Device profile read result (D106): 0

"Device profile read completion" signal (X13): ON Device profile read result (D106): Other than 0

Error completion processing

Set object node No.

Device profile reading request

Device profile reading completion

Normal completion

Error completion

Set device profile.read object node No. in buffer memory

Read device profile reading result.

Message send start signal

Token p- articip- at. sta- tus sig.

Message send: send data

Message send: object node No.

Message send: object node No.

Device profile read results

Device profile read request

Dev. pro- file re- ad cmplt signal

Device profile read request

Device profile read result

Device profile read result

R eq

ue st

R es

po ns

e

Read object node No. setting

A

B

C

Token participation status (X19)

Device profile read request (Y13)

Read data setting

Device profile read completion (X13) D

Node No. setting

Data setting

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 35

At an error completion, refer to the diagnosis data of D106 (see the table below) and correct the FL-net parameters or user PLC, then reboot C6/C64.

After confirming that "Device profile read completion" signal (X13) is ON, turn "Device profile read request" signal (Y13) OFF.

Data and description of device profile read result errors (List of error data in D106 and its description)

D106 data Description of error Remedy

C321H Setting value for object node number outside permissible range.

Correct setting value for object node number.

C322H Object node does not exist. Correct setting value for object node number. Check operation of corresponding equipment.

C323H No response from object node for 10 seconds or more.

Correct setting value for object node number. Check operation of corresponding equipment.

C324H Error in send data. Correct send data.

C326H No empty capacity in object node buffer.

Re-execute after waiting for a while.

C328H Not participating in token. Check the status of the PLC and wires. Review the settings for the initial process.

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 36

6.5 Checking various status of other nodes

The information on the other nodes can be obtained by referring to the information area of the other nodes as shown in the table below.

Buffer memory address

Name Description

Reference to other

nodes from C64 user

PLC

Reference to C64 side from other

nodes

9E0H to

9EFH

Participation node list

Indicates the token participation status at the other node in bits.

b15 b0 9E0H

Node 15 Node 1

b15 b0 9E1H

Node 31 Node 16

0: Participation 1: Release

Possible Possible

9F0H to

9FFH

Other node parameter setting status

Indicates the parameter setting status at the other nodes in bits. *1

b15 b0 9F0H

Node 15 Node 1

b15 b0 9F1H

Node 31 Node 16

0: Setting 1: No setting

Possible Possible

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 37

Buffer memory address

Name Description

Reference to other

nodes from C64 user

PLC

Reference to C64 side from other

nodes

A00H to

A0FH

Other node CPU execution status

Indicates the execution status of QnCPU, etc. at the other node in bits. *1

b15 b0 A00H

Node 15 Node 1

b15 b0 A01H

Node 31 Node 16

0: RUN status (RUN,STEP_RUN) 1: STOP status (STOP,PAUSE)

Possible Not possible (Note)

A10H to

A1FH

Other node CPU operation status (Low level error) *2

Indicates the results of self-diagnosis of QnCPU, etc. at the other node in bits. *1

b15 b0 A10H

Node 15 Node 1

b15 b0 A11H

Node 31 Node 16

0: Normal 1: Warning

Possible Not possible (Note)

A20H to

A2FH

Other node CPU operation status (Medium, high level errors) *3

Indicates the results of self-diagnosis of QnCPU, etc. at the other node in bits. *1 b15 b0

A20H Node 15 Node 1 b15 b0

A21H Node 31 Node 6

0: Normal 1: Alarm

Possible Not possible (Note)

VIII. I/O/Intelligent Function Unit Connection Function 6. Supplement

VIII - 38

*1: For the participation nodes only. *2: CPU unit's operation continues when the low level error occurs. *3: CPU unit's operation stops when the medium to high level error occurs. [Note] Because C64 is not provided with QnCPU, CPU status, such as CPU execution status or operation status of C64, cannot be referred to from the other nodes. When C64 PLC execution status or PLC operation status needs to be checked from the other nodes, alternatively check the heart beat signal in the common area that has been written by the C64 side user PLC with TO commands.

6.6 Reference For the specifications or other programming methods of FL-net, refer to the document of MELSEC Q series below.

FL-net (OPCN-2) Interface Module Users Manual (QJ71FL71-F01-U-SY-J/E)

IX. Connection Function with GOT

IX. Connection Function with GOT 1. Outline

IX - 1

1. Outline This function is to connect Mitsubishi Graphic Operation Terminal (GOT) with MELDAS C6/C64 and use the GOT as a machine operation panel or a NC operation panel. You can display not only overall PLC devices but various monitored information of CNC C6/C64 on the GOT. Setting display dedicated for CNC C6/C64 (CNC monitor), and ladder monitor display are also available. The contents of this manual are supporting C6/C64 software Ver. D0.

CAUTION

Do not set any of the touch keys on the GOT as a start switch for the C6/C64. If a communication error (including cable disconnection) occurs between the GOT and C6/C64, the communication will be cut off and the GOT operation will be disabled. Even if the start switch is released, it will not be recognized that the start signal has been cut off, so the operation will continue. This could result in serious accidents.

IX. Connection Function with GOT 2. Available Function

IX - 2

2. Available Function The table below shows the available functions of GOT when the GOT is connected with CNC C6/C64. This table is extracted from GOT-A900 Series Operating Manual (GT Works2 Version1/GT Designer2 Version1 compatible Extended/Option Functions Manual). : Available : Partly restricted : Unavailable

C6/C64

CC-Link connection Function Ref. Section Bus

connection CPU direct connection

Computer link

connection

MELSEC NET

connection BT13 BT15 G4 Ethernet

connection

Utility function Sec. 4 *1

Ladder monitor

Monitoring of sequence programs with ladder signals

Sec. 6.3.1

Displaying of word device values in decimal and hexadecimal numbers Display

switching Displaying of device comments

Sec. 6.3.3

Device changing Changing of device values Sec.

6.3.4

Ladder monitor function

Print-out Printing of ladder Sec. 6.3.5

Entry monitor

Monitoring of current values by pre-registering monitor devices Sec. 9.2 *2

Batch monitor

Monitoring of n points of current values subsequent to the designated device

Sec. 9.3 *2

T/C monitor

Monitoring of m points of current values, setting values, contacts and coils subsequent to the designated device

Sec. 9.4

BM monitor

Monitoring of x points of current values subsequent to the designated buffer memory of the designated special unit

Sec. 9.5

Setting/resetting of bit devices

Changing of current values for the buffer memory of word device

Changing of current value for T/C (can be used while monitoring T/C)

Data editing by using test operation

Changing of setting value for T/ C (can be used while monitoring T/C)

Sec. 9.6

Quick test Changing of device value by using quick test

Sec. 9.6.2

Displaying of device comment

System monitor function

Display switching

Displaying of word device value and buffer memory value in decimal and hexadecimal numbers

Sec. 9.1.2

Special unit monitor function

Monitoring of special units buffer memory on the dedicated screen Ch. 11

Network monitor function

Monitoring of the network status of MELSECNET/B, (II), and /10 Ch. 15

List editing function List editing of sequence programs Ch. 19

Servo monitor

Monitoring of servo-related items, such as current values and positioning errors on various monitor screens

Motion monitor function Parame-

ter setting Changing of servo parameter setting values

Ch. 22

Servo drive unit monitor function

Monitoring of servo drive unit, changing of servo parameter settings and test operation

Ch. 25 This function is available regardless of the connection mode, as RS-232C interface of the GOT is used. (Refer to Sec. 3.7.3 for the precautions for servo drive unit monitor function.)

CNC monitor function

Monitoring of C6/C64 and changing of the parameters Ch. 28

BT13 : A8GT-J61BT13 is used (intelligent device station). BT15 : A8GT-J61BT15 is used (remote device station). G4 : A9GT-RS4 or A9GT-50WRS4 is used (via G4).

*1 Clock setting is not available. *2 Link devices can be monitored only when they are allocated to the GOT.

CNC monitor function is available only with A985GOT (-V), which also requires the memory board. For more details, refer to GOT-A900 Series Operating Manual (GT Works2 Version1/GT Designer2 Version1 compatible Extended/Option Functions Manual).

IX. Connection Function with GOT 3. Connection Mode

IX - 3

3. Connection Mode The table below shows the connectability of GOT by connection mode.

MELSEC NET connection

Network system

Data link system

CC-Link connection Connection

mode

Bus con-

nection

CPU direct

connec- tion

Computer link

connec- tion

H 10 B, (II) Intelligent

device station

Remote device station

Via G4

Ethernet connection

Connectable X X X X X *1 X

*1 Compatible with the software version of CC-Link communication unit A8GT-J61BT13 is X or later.

Each unit requires the communication units in every communication mode. But the additional unit on C6/C64 side is not necessary when in CPU direct connection mode.

IX. Connection Function with GOT 3. Connection Mode

IX - 4

3.1 CPU Direct Connection GOT can be connected with CNC C6/C64 via RS-422 and RS-232C cables, and this connection is the most economical way. When you use RS-422 cable, you connect this cable with the GPP connector of the F311 cable which is connected to the SIO connector on CNC C64 control unit. When you use RS-232C cable, you connect this cable with TERMINAL connector on CNC C64 control unit.

< Cable specification > (1) RS-422 cable

Cable for GOT (MELSEC) AC30R4-25P (3.0m), AC100R4-25P (10.0m), AC300R4-25P (30.0m)

(2) RS-232C cable CNC C6/C64 side (20-pin half-pitch)

GOT side (9-pin D-SUB)

Signal name Pin No.

Cable connection and direction of signal Pin No. Signal

name GND 1 1 CD

2 RD (RXD) SD 6 3 SD (TXD) RD 16 4 DTR (ER)

ER (DTR) 18 5 SG (GND) 6 DSR (DR) 7 RS (RTS) 8 CS (CTS)

GND 11

9 -

[CNC connector (recommended)] Connector : 10120-3000VE (manufactured by Sumitomo 3M Ltd.) Connector cover : 10320-52F0-008 (manufactured by Sumitomo 3M Ltd.)

[GOT connector] The following type of connector is used as GOT connector. You should use the matching connector.

D-sub 9-pin (male) inch thread type 17LE-23090-27 (D3CC) (manufactured by DDK Ltd.)

(Note) For more details of GOT, refer to GOT-A900 Series User's Manual (GT Works2 Version1/GT

Designer2 Version1 compatible Connection System Manual) and other relevant documents.

Cabinet side wall

TERMINAL

RS-422 cable GOT

SIO

RS-232C/RS-422 (for GPP) relaying

F311 cable

General-purpose RS-232C device connection connector

RS-232C cable

Alternative

GOT

Control unit

IX. Connection Function with GOT 3. Connection Mode

IX - 5

3.2 CC-Link Connection Remote control can be realized via network since CNC C6/C64 functions as an intelligent device station or remote device station in CC-Link system. In order to be connected via CC-Link, a CC-Link unit (FCU6-HR865) needs to be mounted on the expansion slot on the control unit. You need to use CC-Link dedicated cable. Connect the cable to CC-Link system unit (FCU6-HR865) terminal. And make sure to attach the terminating resistor (attachment) to the end station unit.

With regard to CC-Link specification with CNC C6/C64, refer to "III. CC-LINK Master/Local Unit" in this

MANUAL. For details of connection instruction, refer to "MELDAS C6/C64 CONNECTION AND MAINTENANCE

MANUAL" (BNP-B2255). For more details of GOT, refer to "GOT-A900 Series User's Manual (GT Works2 Version1/GT Designer2

Version1 compatible Connection System Manual)" and other relevant documents.

GOT Control unit

CC-Link

(Note 4)

FG cable for CC-Link (Note 3)

(Note 1) We cannot assure the performance when you use any cables other than CC-Link dedicated cable in CC-Link system. For specifications of CC-Link dedicated cables and inquiries, please access the Web page of CC-Link Partner Association (http://www.cc-link.org/). (Provided in "Contact List of CPLA Members")

(Note 2) You need to use the attached terminating resistor. The values of the resistors vary depending on the cables to be used. The value is 110 for CC-Link dedicated cable, 130 for CC-Link dedicated high-performance cable.

(Note 3) Connect FG cable from the FG terminal of CC-Link terminal block to the FG terminal at the lower part on C64 control unit.

(Note 4) In order to adjust the rotary switches for station number setting and for baud rate setting on C64 control unit, pull the CC-Link unit out from the control unit.

IX. Connection Function with GOT 3. Connection Mode

IX - 6

3.3 Ethernet Connection After installed in Ethernet system, GOT can operate CNC C6/C64 remotely via network. In order to be connected via Ethernet, an Ethernet unit (FCU6-EX875) needs to be mounted on the expansion slot of the control unit. Connect an Ethernet cable (10BASE-T cable) to the modular jack on the Ethernet unit. Ethernet cable is so susceptible to noise that you should wire power cables and electric supply cables separately. And you need to attach a ferrite core (attachment) on the control unit side. If you use this function under particularly adverse conditions, or need EMC compatibility, we recommend you to use the shielded cables.

Control unit

1 turn

(Note 1)

Ferrite core

Ethernet

FG cable for Ethernet (Note 2)

Ferrite core (Note 3)

GOT

(Note 1) Follow the procedure below to attach ferrite cores. (1) Wind the cable around the ferrite core once. (2) Fasten the catch as firmly as it can snap. (3) Tighten it by a binding band to avoid displacement.

(Note 2) If you use a shielded cable, you will need an additional FG cable to connect it with FG. Shielded cable is usually connected to FG terminal on the control unit. If earth plate is near it, however, you should connect it directly.

(Note 3) IF you need EMC compatibility, a ferrite core may need to be attached on GOT side, too.

IX. Connection Function with GOT 3. Connection Mode

IX - 7

3.3.1 Initial setting of Ethernet Connection The initial setting in the case of the following system configuration is described below.

(1) Setting on NC Perform the settings of Host IP address on NC side. The IP address to be set here will be shared with the other Ethernet communication function (including GX Developer connection). Up to 2 Ethernet units (FCU6-EX875) can be mounted on C6/C64, so it has 2 channels of Ethernet connection. There are three expansion slots in total: two internal expansion slots (EXT1, EXT2) and one external expansion slot (EXT3). When you mount 2 Ethernet units, each unit will be controlled by being numbered for identification (as "Unit 1" and "Unit 2"). The mounted status and unit numbers of Ethernet units are as follows.

Ethernet (192.168.1.xx)

[Communication with GOT] N/W No. :239 PLC No. :1 IP address :192.168.1.2

N/W No. : 239 PLC No. : 2 IP address : 192.168.1.3

N/W No. : 1 PLC No. : 1 IP address : 192.168.1.1

[Communication with Host] N/W No. : - PC No. : - IP address :192.168.2.2

Ethernet (192.168.2.xx) IP address :192.168.2.1

[When mounted on EXT1 and EXT2]

EXT 2

EXT 1

Unit 1

Unit 2

EXT 1

EXT 2 EXT 3

Unit 1 Unit 2

[When mounted on EXT2 and EXT3]

EXT 1

[When mounted on EXT1 only]

Unit 1

EXT 2

[When mounted on EXT2 only]

EXT 3

[When mounted on EXT3 only]

Unit 1

[When mounted on EXT1 and EXT3]

EXT 3

Unit 1 Unit 2

Unit 1

IX. Connection Function with GOT 3. Connection Mode

IX - 8

The following table shows the settings relating to Ethernet in accordance with each unit number. Item Unit 1 Unit 2

Recommended connection GOT Information network Assigned IP address setting #1926 IP address #1931 IP address (2)

Assigned Subnet mask setting #1927 Subnet mask #1932 Subnet mask (2)

Assigned port number setting #1929 Port number #1933 Port number (2)

Assigned communication speed setting #1930 Speed 10M/auto #1934 Speed (2) 10M/auto

Processing priority High Low

Others IP address setting available at off-line

You will set Ethernet parameters on Basic specification parameter screen. You can set the parameters from #1926 to #1929 in off-line mode. (Refer to "IV. Setting the IP Address" in this manual.)

Parameter number Parameter name Setting example #1926 IP address 192.168.1.2 #1927 Subnet mask 255.255.255.0 #1929 Port number 64758 #1930 Speed 10M/auto 0

(Note 1) If #1926 IP address is not set, the initial setting will be "192.168.1.2". (Note 2) If you set or change the Ethernet parameters, you need to reboot C64. (Note 3) Always set Port number to "64758". (Note 4) Always set #1930 Speed 10M/auto to 0 (10Mbps) during GOT connection.

The following table shows meaning of #1930 Speed 10M/auto and #1934 Speed (2) 10M/auto. Setting value 0 1

Communication speed Speed 10M/auto

The communication speed is fixed to 10Mbps.

The communication speed is set after 10Mbps or 100Mbps is automatically recognized

[BASIC SPECIFICATION PARAMETER] SETUP PARAM 1.18/21 # 1925 1926 IP address 192. 168. 1. 2 1927 Subnet mask 255. 255. 255. 0 1928 Gateway address 0. 0. 0. 0 1929 Port number 64758 1930 Speed 10M/auto 0 1931 IP address (2) 192. 168. 2. 2 1932 Subnet mask (2) 255. 255. 255. 0 1933 Port number (2) 64758 1934 Speed (2) 10M/auto 0. 0. 0. 0 1935 1936 #( ) DATA ( . . . ) EMG STOP

AXIS SERVO SPINDLE MENU CHANGE BASIC

IX. Connection Function with GOT 3. Connection Mode

IX - 9

(2) Setting on GT Designer2 Perform the settings of C6/C64 to be monitored in "Ethernet setting" of GT Designer2.

Item Detail Host "*" mark will be shown when you click "Set to Host" button.

N/W No. Set the network number of the MELDAS C6/C64. If you use the CNC monitor function, set it to "239".

PLC No. Set the PLC number (station number) of the CNC C6/C64. Model Select "AJ71QE71".

IP address Set the IP address of the MELDAS C6/C64. Set the IP address that is assigned to the connected C6/C64.

Port No. Set it to "5001".

Communication type

Fixed to UDP/IP. However, communication is made via TCP/IP during the CNC monitoring, and via UDP/IP during the normal monitoring.

IX. Connection Function with GOT 3. Connection Mode

IX - 10

(3) Setting on GOT Perform the Ethernet settings on GOT unit. Use Setup of the GOT units utility function to perform Ethernet settings.

Item Detail Factory setting

GOT NET No. Set the network number of the GOT. 1 GOT PC No. Set the station number of the GOT. Do not set the same number as

the PC numbers of the Ethernet unit and C6/C64 to be monitored. 1

GOT IP ADDRESS Set the IP address of the GOT. 000.000.000.000 GOT PORT No. Set the port number of the GOT.

When connected with C6/C64, set it to "5001". 5001

ROUTER ADDRESS

If the system is connected with the other network by a router, set the router address of the network where the GOT is connected.

000.000.000.000

SUBNET MASK When the GOT is connected to the Ethernet network controlled by the subnet, set the subnet mask that is commonly set in the network. Without subnet, operation will be conducted with the default value.

255.255.255.000

SEND MESSAGE WAIT

Set the send message wait time in order to reduce loads on the network and the subjected PLC.

0

SEND MESSAGE TIME

Set the timeout interval. 3

START UP TIME Set how many seconds after GOTs power-on the communication with C6/C64 will be started. Set it to "10".

3

(Note) For more details about settings on GT Designer2 and GOT, refer to "GOT-A900 Series User's Manual (GT Works2 Version1/GT Designer2 Version1 compatible Connection System Manual)" and other relevant documents.

SET UP GOT NET No. 001 (1~239) GOT PC No. 01 (1~64) GOT IP ADDRESS 000.000.000.000 GOT PORT No. 05001(1024 to 65534) ROUTER ADDRESS 000.000.000.000 SUBNET MASK 255.255.255.000 SEND MESSAGE WAIT 00010ms (0~300) SEND MESSAGE TIME 03 sec (3~90) STARTUP TIME 003 sec (0~255)

Page 3/3 SELECT/CHANGE

IX. Connection Function with GOT 3. Connection Mode

IX - 11

(4) Initial setting procedure example The followings show the setting procedure to conduct CNC monitoring with the GOT. The setup procedure of the configuration below is used as an example. The procedure of connecting with the default value before changing the IP address in order to set the IP address of C6/C64 is explained here.

[C6/C64 parameter setting (factory setting)] [GOT parameter setting (factory setting)]

Parameter No.

Parameter name

Factory setting

#1926 IP address 192.168.1.2 #1927 Subnet mask 0.0.0.0 #1929 Port number 64758 #1930 Speed 10M/auto 0

Ethernet

N/W No. : 239 PLC No. : 1 IP address : 192.168.10.2

N/W No. : 1 PLC No. : 1 IP address : 192.168.10.1

Connecting with the default values to set the IP address of

C6/C64. (Step (1)~(2))

Changing the IP address of C6/C64 on the CNC monitor.

(Step (3))

Changing the IP address of the GOT. (Step (4)~(6))

END

[Setting procedure]

START

Parameter name Factory setting GOT NET No. 1 GOT PC No. 1

GOT IP ADDRFESS 000.000.000.000 GOT PORT No. 5001

ROUTER ADDRESS 000.000.000.000 SUBNET MASK 255.255.255.000

TRANSMISSION WAIT TIME 0 TRANSMISSION TIMEOUT 3

START UP TIME 3

IX. Connection Function with GOT 3. Connection Mode

IX - 12

Step (1): Set the following settings in "Ethernet setting" of GT Designer2, and transmit them to the GOT.

Item Setting value Remarks Host *

N/W No. 239 When conducting CNC monitoring, set it to "239". PLC No. 1 Model AJ71QE71

IP address 192.168.1.2 Set the default IP address of C6/C64. Port No. 5001

Communication type UDP

Step (2): Set the following settings on the GOT unit.

Step (3): With the CNC monitor displayed, change the IP address of C6/C64. The changed IP address will be validated after rebooting.

SET UP GOT NET No. 001 (1~239) GOT PC No. 01 (1~64) GOT IP ADDRESS 192.168.001.001 GOT PORT No. 05001(1024~65534) ROUTER ADDRESS 000.000.000.000 SUBNET MASK 255.255.255.000 SEND MESSAGE WAIT 00010ms (0~300) SEND MESSAGE TIME 03 sec (3~90) STARTUP TIME 010 sec (0~255)

Page 3/3 SELECT/CHANGE

[BASIC SPECIFICATION PARAMETER] SETUP PARAM 1.18/21 # 1925 1926 IP address 192. 168. 1. 2 1927 Subnet mask 255. 255. 255. 0 1928 Gateway address 0. 0. 0. 0 1929 Port number 64758 1930 Speed 10M/auto 0. 0. 0. 0 1931 IP address (2) 0. 0. 0. 0 1932 Subnet mask (2) 0. 0. 0. 0 1933 Port number (2) 0 1934 Speed (2) 10M/auto 0. 0. 0. 0 1935 1936 #( ) DATA ( . . . ) EMG STOP

AXIS SERVO SPINDLE MENU CHANGE BASIC

IX. Connection Function with GOT 3. Connection Mode

IX - 13

Step (4): Set the formal settings in "Ethernet setting" of GT Designer2, and then transmit them to the GOT.

Step (5): Set the formal settings on the GOT unit.

Step (6): Reboot C6/C64 and GOT.

Now, the initial setting is completed.

SET UP GOT NET No. 001 (1~239) GOT PC No. 01 (1~64) GOT IP ADDRESS 192.168.010.001 GOT PORT No. 05001(1024~65534) ROUTER ADDRESS 000.000.000.000 SUBNET MASK 255.255.255.000 SEND MESSAGE WAIT 00010ms (0~300) SEND MESSAGE TIME 03 sec (3~90) STARTUP TIME 010 sec (0~255)

Page 3/3 SELECT/CHANGE

IX. Connection Function with GOT 4. Device Range Referenced on the GOT

IX - 14

4. Device Range Referenced on the GOT The following table shows the types and ranges of the devices in the C6/C64 that can be referenced on the GOT.

Application Device Range Point Input X0 to XAFF 2816 points Output Y0 to YE7F 3712 points Internal relay M0 to M8191 8192 points Internal relay (Annunciator) F0 to F127 128 points Latch relay L0 to L255 256 points Special relay SM0 to SM127 128 points Link relay B0 to B1FFF 8192 points Special link relay SB0 to SB1FF 512 points Special register SD0 to SD127 128 points Link register W0 to W1FFF 8192 points Special link register SW0 to SW1FF 512 points

10ms T0 to T15 16 points 100ms T16 to T95 80 points 100ms integration T96 to T103 8 points 10ms (Fixed timer) T104 to T143 40 points 100ms (Fixed timer) T144 to T239 96 points

Timer

100ms integration (Fixed timer) T240 to T255 16 points Counter C0 to C127 128 points Data register D0 to D8191

(Note 1) 8192 points

File register R0 to R8191 8192 points

(Note 1) D1024 to D8191 can be used with the software version D0 and above.

IX. Connection Function with GOT 5. Related Documents

IX - 15

5. Related Documents [Documents relating to MELDAS C6/C64]

MELDAS C6/C64 CONNECTION AND MAINTENANCE MANUAL ............................. BNP-B2255 MELDAS C6/C64 PLC PROGRAMMING MANUAL ..................................................... BNP-B2309 (Ladder Section with MELSEC Tool)

[Documents relating to GOT] GOT-A900 Series User's Manual (GT Works2 Version1/GT Designer2 Version1 Compatible Connection System Manual)....................................................................................... SH (NA)-080255 GOT-A900 Series Operating Manual (GT Works2 Version1/GT Designer2 Version1 Compatible Extended/Option Functions Manual) ......................................................................... SH (NA)-080253

X. GOT Window Function

X. GOT Window Function 1. Outline

X - 1

1. Outline

This function is an interface used to display various data on the GOT (A900 Series) connected to the MELDAS C6/C64. The currently running machining program No., the currently running machining program and the coordinates, etc., are read from the GOT with the device read commands. Commands for the NC are set from the GOT, and the data corresponding to the commands is created on the NC side. The command area and response area are designated in R7756 to R7760. When the GOT designates the NC data to be gotten in the command area, the NC stores the designated data in the response area. That data can be sequentially read and displayed with the GOT. Up to ten areas can be set as window areas, and up to ten types of commands can be set simultaneously.

NC system

R register

GOT

R0

Window process Command

issuance and device

reading

R8191

R7756 ~

R7760

Once the data change is requested, the NC system continuously creates the data corresponding to the designated command until the next data change request is received.

The area used as the command and response area by the GOT or built-in ladder is set in R7756 to R7760. The command is set in the command area and the data is read from the response area.

Command 10

Response 10

Command and response area

designation

Designate the user area in R register, D register or W register as command area.

Designate the user area in R register, D register or W register as response area.

X. GOT Window Function 2. Displaying the NC data

X - 2

2. Displaying the NC data

The NC internal data can be displayed and set with three methods. Method 2 is explained in this manual. The NC screen conventionally displayed on the communication terminal, etc., is displayed on the GOT using the GOT's NC monitor function. This is a fixed screen which cannot be customized by the user. Only the A985GOT(-V) NC monitor function can be used. The data periodically output to the NC's built-in PLC register by the NC system software is displayed on the GOT. The types and amount of data periodically output by the NC system software are limited. Data is prepared (DDB commands) in the register by the NC's built-in PLC, and the GOT reads and writes the NC register. The degree of freedom is high, but the NC internal data must always be gotten with a ladder.

C6/C64(NC) GOT

NC screen Display character code

Key code

Ladder

O:123 N:456 X100.00 Y150.00

NC counter, modal, execution program, etc.

Lamps, operation results, etc. Switches and buttons

NC keyboard

Size Design

Fixed

Variable

Method 1

Method 2

Method 3

NC system

software Fixed

Register

Variable

Variable Variable

Register

X. GOT Window Function 3. Displaying the NC data (Method 2): GOT window function

X - 3

3. Displaying the NC data (Method 2): GOT window function

This function displays the NC internal data prepared in a special register by the NC system.

1

GOT

N100G91G28X0.Y0.Z0.; N110G00X-150.Y-200.; N120G00Z-500.; N130G01Z-50.F500.; N140G00Z50.; N150G00X50.Y50.; N160G00-Z50.F500.;

100

Currently running program

Machine value

X 110.000

120.000

130.000

Y

Z

X 110.000

120.000

130.000

Y

Z

O N

Spindle tool 01 02 S 6000 500 F

1 100 O N

Main program

T 5

Subprogram

Remaining distance

Standby tool

Display data Getting method Main/sub O, N No. Get with melGetGmodalPack (Command code: 0x0F02) Currently running program Get with melGetCurrentPrgPack (Command code: 0x0F01) Machine value Get with melGetAxisPosition (Command code: 0x0F03) Remaining distance Get with melGetAxisPosition (Command code: 0x0F03) F command (modal) Get with melGetGmodalPack (Command code: 0x0F02) S command (modal) Get with melGetGmodalPack (Command code: 0x0F02) T command (modal) Get with melGetGmodalPack (Command code: 0x0F02)

X. GOT Window Function 4. Designating the window area

X - 4

4. Designating the window area

Set the window area in R7756 to R7760 with the GOT (or built-in PLC). Set commands in the set window command area.

The user area is used as the command and response areas. [User area]

R4000~R4499 R6400~R7199 D0~D8191 W0~W1FFF

(Example) To designate R6400 as the response head device No.

: Set 6400 as a decimal.

R register

R7757

R7758

R7756 Window validity & device type

R8191

Status

R7759

Command head device No.

Response head device No.

R7760

Window quantity (1 to 10)

(1)

(2)

(3)

(4)

(1) Window validity and device type designation (Designate with R7756)

bit Details Explanation 0 Window validity 1 2 3 4 5 6 7

Turn bit0 ON to use the window function. The data in the response area will not be updated when this bit is OFF. Turn the validity bit ON after setting all of the other data.

8 R register usage 9 D register usage For command A W register usage B C R register usage D D register usage For response E W register usage

Designate the device type used with the window function. Turn 1 bit ON. If multiple bits are ON or if they are all OFF, the R register will be used.

F

X. GOT Window Function 4. Designating the window area

X - 5

(2) Window command area (Designate with R7757)

Data change request

Command area 1

64 words

Up to ten (64 words x 10) continuous areas

+0

+1

+2

+66

Spare

Command area 2

(3) Window response area (Designate with R7758)

Clear the complete signal before turning the window validity bit ON.

Response area 1

128 words

+0

+1

+2

+130 Response area

2

Data change complete

Spare

Up to ten (128 words x 10) continuous areas

(4) Status (Designate with R7760) bit Details 0 Window quantity error 1 Command area Device range error 2 Response area Device range error 3 4 5 6 7 8 9 A B C D E F

The error status from the NC is stored in the status area. An error will occur if the designated device is not within the user area range, or if the window quantity is not between 1 and 10. The "response area device range error" will occur if the command area and response area overlap.

Precautions for designating the window area

(1) Turn the window validity bit ON after setting the window quantity, command head device No. and response head device No.

The window validity bit can be turned ON simultaneously with the device type without problem.

(2) After changing the window area, turn the window validity bit OFF once and then set the device No., etc.

(3) After an error such as a window quantity error or device range error occurs, turn the window validity bit OFF once, and make a correct setting.

(4) The command head device No. and response head device No. must always be an even number (so that 4 bytes is the boundary).

X. GOT Window Function 5. Getting window data

X - 6

5. Getting window data The window area must be designated before the GOT can get the NC data. Next, set the required commands, and turn the data change request ON. The NC side receives the data change request, and when the data has been changed, the data change complete signal turns ON. Once the data change request turns ON, the NC will continue to create data until the next data change request turns ON. There are ten data change request signals corresponding to windows 1 to 10.

After writing the command (API designation) and argument into the command area from the GOT or built-in ladder, the data change request signal turns ON.

The GOT reads the response area device.

After the NC receives the data change request and the response area update is completed, the data change complete signal turns ON.

The GOT receives the data change complete signal and turns the data change request signal OFF.

The NC continually creates data in respect to the designated command, and stores it in the response area.

Designate the window area. (Window quantity, command/response device area, device type designation, window validity bit)

(1)

(2)

(3)

(4)

(5)

(6)

(2)

(3)

(4)

(6)

(1)

Command setting (GOT->NC)

Data change request (GOT->NC)

Data change complete (NC->GOT)

Data getting (GOT process)

Window setting (GOT->NC)

Precautions for getting the window data (1) The script function is used to write the commands from the GOT. (2) To prevent transient data from being displayed, do not get the data while the data change request is ON. (3) If data is to be constantly gotten without changing the command, turn the data change request ON only

once. The response area will be constantly updated after that.

X. GOT Window Function 6. Data change request and complete signals

X - 7

6. Data change request and complete signals 6.1 Data change request signal (GOT NC)

Offset Details Remarks Command head device +0 Data change request signal Turns ON when the command data is

changed.

Details of bits bit Details 0 Window 1 data change request 1 Window 2 data change request 2 Window 3 data change request 3 Window 4 data change request 4 Window 5 data change request 5 Window 6 data change request 6 Window 7 data change request 7 Window 8 data change request 8 Window 9 data change request 9 Window 10 data change request A B C D E F

X. GOT Window Function 6. Data change request and complete signals

X - 8

6.2 Data change complete signal (NC GOT)

Offset Details Remarks Response head device +0 Data change complete

signal Turns ON when the data change is completed, and turns OFF when the data change request signal turns OFF.

Details of bits bit Details 0 Window 1 data change complete 1 Window 2 data change complete 2 Window 3 data change complete 3 Window 4 data change complete 4 Window 5 data change complete 5 Window 6 data change complete 6 Window 7 data change complete 7 Window 8 data change complete 8 Window 9 data change complete 9 Window 10 data change complete A B C D E F

X. GOT Window Function 7. Window commands/responses

X - 9

7. Window commands/responses 7.1 List of command codes

Command name Details Command code melGetCurrentPrgPack Designate and get type of currently running program 0xF01 melGetGmodalPack Get modal information in batch 0xF02 melGetAxisPosition Get coordinate values for all axes in batch 0xF03 melGetCurrentAlarmMsg2 Get currently occurring alarm message 0xF04 melGetAlarmHistory Get alarm history information 0xF05

7.2 Command area

Up to ten window command areas can be used.

Window Offset Details Remarks - +0 Data change request signal - +1 Spare

+2 Data size Number of bytes from command code to end of argument

+3 Spare +4 Command code Command code used +5 Spare

Window 1

+6 ~ +65

Argument 1 to argument 30 The argument configuration differs according to the command

+66 Data size Number of bytes from command code to end of argument

+67 Spare +68 Command code Command code used +69 Spare

Window 2

+70 ~ +129

Argument 1 to argument 30 The argument configuration differs according to the command

: : : : +578 Data size Number of bytes from command code to

end of argument +579 Spare +580 Command code Command code used +581 Spare

Window 10

+582 ~ +641

Argument 1 to argument 30 The argument configuration differs according to the command

The offset is indicated in word units.

X. GOT Window Function 7. Window commands/responses

X - 10

7.3 Response area

Up to ten window response areas can be used.

Window Offset Details Remarks - +0 Data change complete

signal

- +1 Spare +2 Data size Number of bytes from command code to

end of response +3 Spare +4 Command code Command code issued +5 Spare +6 +7

Error code 0 : No error Other than 0 : Error occurring

Window 1

+8 ~ +129

Response (122 words) The response configuration differs according to the command

+130 Data size Number of bytes from command code to end of response

+131 Spare +132 Command code Command code issued +133 Spare +134 +135

Error code 0 : No error Other than 0 : Error occurring

Window 2

+136 ~ +257

Response (122 words) The response configuration differs according to the command

: : : : +1154 Data size Number of bytes from command code to

end of response +1155 Spare +1156 Command code Command code issued +1157 Spare +1158 +1159

Error code 0 : No error Other than 0 : Error occurring

Window 10

+1160 ~ +1281

Response (122 words) The response configuration differs according to the command

The offset is indicated in word units.

X. GOT Window Function 8. Details of commands

X - 11

8. Details of commands 8.1 melGetCurrentPrgPack

melGetCurrentPrgPack Designates and gets the type of currently running program.

Usage example

Command Offset Details Setting example Remarks 0 Data size 16 1 Spare 0 2 Command code 0x0F01 Designate

melGetCurrentPrgPack 3 Spare 0 4 5

Argument 1: Designate part system No.

1 1: 1st part system 2: 2nd part system

6 7

Argument 2: Designate number of blocks to get

3 Setting range: 1 to 10

8 9

Argument 3: Designate number of characters in one block

16 Setting range: 1 to 240

The offset is indicated in word units. Designate so that the number of blocks x number of characters in one block is within 240 characters.

Response Offset Details Response example Remarks 0 Data size 60 1 Spare 0 2 Command code 0x0F01 Designate

melGetCurrentPrgPack 3 Spare 0 4 5

Error code 0 0 : No error Other than 0 : Error occurring

6 7

Status 1 0: Not running 1: Running

8~15 "NO1G90G28X0.Y0.;" 16~23 "NO2G00X-123.456;" 24~31

Currently running program

"NO003;" The offset is indicated in word units. The currently running block is always output to the 2nd block. NULL is output for empty blocks. Thus, if the program is not running, the NULL code is output to the above two blocks.

X. GOT Window Function 8. Details of commands

X - 12

8.2 melGetGmodalPack

melGetGmodalPack Gets various modal information in a batch.

Usage example

Command Offset Details Setting example Remarks 0 Data size 16 1 Spare 0 2 Command code 0x0F02 Designate melGetGmodalPack 3 Spare 0 4 5

Argument 1: Designate part system No.

1 1: 1st part system 2: 2nd part system

The offset is indicated in word units.

X. GOT Window Function 8. Details of commands

X - 13

Response

Offset Details Response example Remarks 0 Data size 190 Number of bytes 1 Spare 0 2 Command code 0x0F02 Command code issued 3 Spare 0 4 5

Error code 0 0 : No error Other than 0 : Error occurring

6~9 S1 modal "1200" 8-digit S1 modal (ASCII) S1 is output regardless of the part system

10~13 T modal "13" 8-digit T modal (ASCII) 14~18 (Note1)

F modal "1200.00" 10-digit FA modal (ASCII)

19~48 G modal "01 17 91 94" "21 40 49 80" "98 54 64 67" "97 50.143.1"

G modal for each group (ASCII) One group is output with four characters

49 NC status 1 0 0: No alarm message 1: Alarm message found

50~68 NC status 2 "LSK mm INC G40 G54"

When there is no alarm message: ST1 to ST8 are output with ASCII

When there is an alarm message: The message is output with up to 33 characters

69~72 Main program No. "100" 8-digit main program No. (ASCII) 73~76 Main sequence No. "110" 8-digit main program sequence No.

(ASCII) 77~80 Subprogram No. "9990" 8-digit subprogram No. (ASCII) 81~84 Subprogram sequence No. "200" 8-digit subprogram sequence No.

(ASCII) 85~88 S2 modal "2000" 8-digit S2 modal (ASCII)

S2 is output regardless of the part system

89~92 Current program No. "9990" 8-digit current program No. (ASCII) 93~96 Currently running program's

sequence No. "200" 8-digit sequence No. of currently

running program (ASCII) The offset is indicated in word units. (Note 1) The F modal value is a value on which override is not applied.

X. GOT Window Function 8. Details of commands

X - 14

8.3 melGetAxisPosition

melGetAxisPosition Gets the coordinate values for all axes in a batch.

Example of use when getting the machine value (When getting as a character string)

Command Offset Details Setting example Remarks 0 Data size 20 1 Spare 0 2 Command code 0x0F03 Designate melGetAxisPosition 3 Spare 0 4 5

Argument 1: Designate part system No.

1 1: 1st part system 2: 2nd part system

6

7

Argument 2: Designate the axis to get

3 bit0: 1st axis bit1: 2nd axis ... If the axis is not designated, the values for all axes will be gotten.

8

9

Argument 3: Designate the type of coordinate value

0 0: Machine value 1: Current value 2: Workpiece coordinate value 3: Remaining command 4: Next command

10 11

Argument 4: Data type 1 0: Interpolation unit (Note 1) 1: Character string type (ASCII)

The offset is indicated in word units. (Note 1) When the command unit is 1m, the interpolation unit is 0.5m. When the command unit is 0.1m, the interpolation unit is 0.05m. (Note 2) Only the NC axes are the target axes. The coordinate values for the PLC axes cannot be gotten. (Note 3) When using the character string type, the diameter designated axis will be displayed as a

diameter. (Note 4) When using the character string type, if the coordinate value exceeds 8 digits, * will be displayed.

(ex.) ******.*** (Note 5) If the number of axes to be gotten exceeds the number of axes actually mounted on the NC, an

error will be returned, and the coordinate values, including those for the mounted axes, will not be stored.

X. GOT Window Function 8. Details of commands

X - 15

Response Offset Details Response example Remarks 0 Data size 44 Number of bytes 1 Spare 0 2 Command code 0x0F03 Command code issued 3 Spare 0 4 5

Error code 0 0 : No error Other than 0 : Error occurring

6~11 1st axis coordinate value "-12345.678" 8-digit S1 modal (ASCII) S1 is output regardless of the part system

12~17 2nd axis coordinate value "12345.678" 8-digit T modal (ASCII) 18~23 3rd axis coordinate value " " 10-digit FA modal (ASCII)

The offset is indicated in word units.

Example of storing "-123.456" in register bit15 bit8 bit7 bit0

+0 " " " " +1 "-" " " +2 "2" "1" +3 "." "3" +4 "5" "4" +5 " " "6"

X. GOT Window Function 8. Details of commands

X - 16

Example of use when getting the machine value (When getting as a binary)

Command Offset Details Setting example Remarks 0 Data size 20 1 Spare 0 2 Command code 0x0F03 Designate melGetAxisPosition 3 Spare 0 4 5

Argument 1: Designate part system No.

1 1: 1st part system 2: 2nd part system

6

7

Argument 2: Designate the axis to get

7 bit0: 1st axis bit1: 2nd axis ... If the axis is not designated, the values for all axes will be gotten.

8

9

Argument 3: Designate the type of coordinate value

0 0: Machine value 1: Current value 2: Workpiece coordinate value 3: Remaining command 4: Next command

10 11

Argument 4: Data type 0 0: Interpolation unit (Note 1) 1: Character string type (ASCII)

The offset is indicated in word units. (Note 1) When the command unit is 1m, the interpolation unit is 0.5m. When the command unit is 0.1m, the interpolation unit is 0.05m. (Note 2) Only the NC axes are the target axes. The coordinate values for the PLC axes cannot be gotten. (Note 3) If the number of axes to be gotten exceeds the number of axes actually mounted on the NC, an

error will be returned, and the coordinate values, including those for the mounted axes, will not be stored.

X. GOT Window Function 8. Details of commands

X - 17

Response Offset Details Response example Remarks 0 Data size 20 Number of bytes 1 Spare 0 2 Command code 0x0F03 Command code issued 3 Spare 0 4 5

Error code 0 0 : No error Other than 0 : Error occurring

6 7

1st axis coordinate value 20000 (0x4E20)

20000-2000=10.000mm

8 9

2nd axis coordinate value -24690 (0xFFFF9F8E)

-24690/2000=-12.345mm

10 11

3rd axis coordinate value 1000 (0x3E8)

1000/2000=0.500mm

The offset is indicated in word units.

Example of storing 0xFFFF9F8E (-24690) in register +0 9F8E +1 FFFF

X. GOT Window Function 8. Details of commands

X - 18

8.4 melGetCurrentAlarmMsg2

melGetCurrentAlarmMsg2 Gets the currently occurring alarm message.

The designated number of up to five currently occurring messages can be gotten in order of priority. The NC alarm/stop code language follows NC parameter "#1043 lang". Example of use

Command Offset Details Setting example Remarks 0 Data size 16 1 Spare 0 2 Command code 0x0F04 Designate melGetCurrentAlarmMsg2 3 Spare 0 4

5

Argument 1: Designate part system No.

0 0: All part systems 1: 1st part system 2: 2nd part system ...

6 7

Argument 2: Number of messages to get

5 1~5

8

9

Argument 3: Type of alarm to get 0x7 bit0: NC alarm bit1: Stop code bit2: PLC alarm message The alarm messages for which the corresponding bit is ON are gotten.

The offset is indicated in word units.

X. GOT Window Function 8. Details of commands

X - 19

Response Offset Details Response example Remarks

0 Data size 252 Number of bytes 1 Spare 0 2 Command code 0x0F04 Command code issued 3 Spare 0 4 5

Error code 0 0 : No error Other than 0 : Error occurring

6~7 Number of gotten messages

2 The number of gotten messages (number of occurring alarms) is set.

8~10 Alarm code (1) 0x003300520700 Refer to the Alarm code table 11~31 Alarm message (1) "S03 Servo error 0052 XYZ

$1" The message is returned with left justified. A space (0x20) is set in empty areas.

32~34 Alarm code (2) 0x000100000000 35~55 Alarm message (2) "EMG Emergency stop

EXIN $1"

56~58 Alarm code (3) 0x000000000000 0 is set if there is no alarm. 59~79 Alarm message (3) NULL NULL(0) is set if there is no alarm. 80~82 Alarm code (4) 0x000000000000 83~103 Alarm message (4) NULL 104~106 Alarm code (5) 0x000000000000 107~127 Alarm message (5) NULL

Message format The NC alarms, stop codes and PLC alarm messages use the following format. Each message has a fixed length of 21 words (42 characters). (1) NC alarm/stop code Message (20 characters) + sp + error No. 1 (4 characters) + sp + error No. 2 (8 characters) + sp + $1 (2

characters) (Note 2) + sp (5 characters) (2) PLC alarm message Message (32 characters) + sp + sp + class No. (5 characters) + sp (3 characters)

(Note 1) sp: Space (0x20) (Note 2) Only when all part systems are designated. When 1st part system or 2nd part system, etc., is

designated, this will be sp + sp.

X. GOT Window Function 8. Details of commands

X - 20

Alarm code The NC alarms, stop code and PLC alarm messages displayed on the NC screen are coded with three words. (Example) When servo alarm S03 occurs

S03 SERVO ALARM 0052 XZ

Axis name Alarm No. Alarm message Alarm type

00000000 00110011 00000000 01010010 00000101 00000000

bit

7 6 5 4 3 2 1 0

1st axis 0 0 0 0 0 0 0 1 2nd axis 0 0 0 0 0 0 1 0 3rd axis 0 0 0 0 0 1 0 0 4th axis 0 0 0 0 1 0 0 0 5th axis 0 0 0 1 0 0 0 0 6th axis 0 0 1 0 0 0 0 0 7th axis 0 1 0 0 0 0 0 0 8th axis 1 0 0 0 0 0 0 0

The bit corresponding to the axis No. at which the alarm occurs turned ON for the servo axis name, spindle axis name and PLC axis name. If several alarms occur simultaneously, several bits will turn ON.

PLC axis name Alarm type Alarm number Spindle nameServo axis name

Alarm code table The alarm types and alarm Nos. follow the next table. The alarm with priority 1 has the highest priority.

Alarm Details Alarm type

Presence of axis name Priority

NC alarm Operation error M01 OPERATION ERROR 0x11 Some are

added. 8

S01 SERVO ALARM:PR 0x31 Added. 2 S02 INIT PARAM ERR 0x32 S03 SERVO ALARM:NR 0x33 S04 SERVO ALARM:AR 0x36 S51 PARAMETER ERROR 0x34 Added. 6

Servo/spindle alarm

S52 SERVO WARNING 0x35 Y02 SYSTEM ALARM 0x41 Not added. 3 Y03 AMP. UNEQUIPPED 0x42 Y51 PARAMETER ERROR 0x45

MCP alarm

Y90 SP. NON SIGNAL 0x47 Z52 BATTERY FAULT 0x52 Not added. 7 Z53 TEMP. OVER 0x53 Z55 RIO NOT CONNECT 0x54 Z59 TIME CONSTANT 0x59 Z70 ABS. ILLEGAL 0x55 Added. 1 Z71 DETECTOR ERROR 0x56 Z72 COMPARE ERROR 0x57 Z73 ABS. WARNING 0x58

System alarm

P990 PREPRO S/W ERR 0x61 Not added. 5

X. GOT Window Function 8. Details of commands

X - 21

Alarm Details Alarm type

Presence of axis name Priority

NC alarm (continued) Program error P*** Program error 0x71 Not added. 5 M00 AUX OPER.ALM 0x81 Added. 8 M01 AUX OPER.ALM 0x82 S01 AUX SERVO ALM 0x83 Added. 2 S02 AUX SERVO ALM 0x84 S03 AUX SERVO ALM 0x85 S52 AUX SERVO WRN 0x86 Y02 AUX SYSTEM ALM 0x87 Some are 3 Y03 AUX AMP UNEQU. 0x88 added. EMG AUX EMERGENCY 0x89 Z70 AUX POS. ERR 0x8A Added. 1 Z71 AUX DETEC. ERR 0x8B

Auxiliary axis (MR-J2-CT) alarm (Note 1)

Z73 AUX SYSTEM WRN 0x8C Emergency stop EMG EMERGENC 0x01 Not added. 4 Stop code T01 CAN'T CYCLE ST 0x21 Not added. 9 T02 FEED HOLD 0x22 T03 BLOCK STOP 0x23 T04 COLLATION STOP 0x24

Stop code

T10 FIN WAIT 0x26 PLC alarm message (Arbitrary character string) 0x91 Not added. 10

(Note 1) If multiple alarms occur simultaneously, only the alarm with the highest order of priority in the code table will be output. Note that the auxiliary axis name is output to the servo axis name area.

The messages for emergency stop are coded as shown below.

Alarm Details Alarm number

EMG emergency EXIN External emergency stop 0x0000 stop PLC User PLC emergency stop 0x0001 SRV Servo drive unit not ready 0x0002 STOP User PLC not running 0x0003 SPIN Spindle drive unit not ready 0x0004 PC_H PLC high-speed process error 0x0005 PARA Door open II fixed device setting illegal 0x0006 LINK No communication with external PLC 0x0007 WAIT Waiting for external PLC communication 0x0008 XTEN External PLC emergency stop 0x0009 LAD User PLC illegal code 0x0010

X. GOT Window Function 8. Details of commands

X - 22

The PLC alarm messages are coded as shown below. Alarm Details Alarm number

PLC alarm message (Arbitrary character string) + contents of registered D register

For corresponding F device (ex) F64: 64, or When contents of corresponding R register (ex) R118 are the target, and contents of R118 are 64: 64

There are two interfaces for displaying the PLC alarm messages on the NC screen, the "F method" that makes a display request with the temporary memory F, and the "R method" that makes a display request with the file register (R). The method can be selected with the parameters. Up to four PLC alarm messages can be displayed at once on the Alarm Diagnosis screen. (1) F method interface

The 128 points from F0 to F127 in the temporary memory are the target. The priority of the F0 to F127 signals starts with F0. Starting from F0, the messages corresponding to the Fn which is set to 1 are gotten from the message table and displayed.

(2) R method interface The file registers R118, R119, R120 and R121 are the target. The values (binary) set in these R registers are the values that indicate which number message in the message table to display. The messages are cleared by setting the R register contents to 0. The messages are displayed in order from the message corresponding to R118. Since the display is cleared when the contents of the R register are set to 0, No. 0 in the message table cannot be used when using the R method.

(3) Parameter for switching between F method and R method Switch between the methods with the PLC parameter #6450/bit1. bit1=0: F method bit1=1: R method

X. GOT Window Function 8. Details of commands

X - 23

8.5 mmelGetAlarmHistory

melGetAlarmHistory Gets the alarm history information.

Details of alarm history The alarm history information saved in the NC is gotten. The NC alarm history information is gotten from the history data displayed on the NC "Operation History"

screen. The history is sorted in order of latest data and is gotten. The history for up to 168 alarms can be stored in the NC. When 168 alarms are exceeded, the history will be deleted in order from the oldest alarms. The stop codes and PLC alarm messages are not stored in the operation history. The following NC alarms are not stored in the operation history.

M01 Operation error 0004 (External interlock axis found) M01 Operation error 0005 (Internal interlock axis found) M01 Operation error 0109 (Block start interlock) M01 Operation error 0110 (Cutting block start interlock)

Alarm history message format

The length of one message is fixed to a total of 60 characters as shown below. The blank spaces of the message are filled in with space codes. 03/01/01

Year/month/date Hour:minute:second Message

8 characters 1 character 8 characters 1 character 42 characters

sp 13:59:02 P153 LF ERROR sp sp $ 1 sp sp spsp

(Note 1) The part system No. ($1, $2, etc.) is indicated at the 38th and 39th characters of the message. For the 1st part system, the part system No. is indicated as sp+sp.

X. GOT Window Function 8. Details of commands

X - 24

Due to limitations to the response area size, M alarms are gotten from the history for the latest Nth alarms. Up to four alarm histories can be gotten at once. Thus, to get the entire alarm history in the NC, up to 42 retrievals must be used. Example of use

Command Offset Details Setting example Remarks 0 Data size 12 1 Spare 0 2 Command code 0x0F05 Designate melGetAlarmHistory 3 Spare 0 4

5

Argument 1: Head history number of history data to be retrieved

10 0: Retrieve from latest history data 1: Retrieve from previous history data 2: Retrieve from second to previous history data

6 7

Argument 2: Number of histories to retrieve

4 1~4

The offset is indicated in word units.

Response Offset Details Response example Remarks

0 Data size 252 Number of bytes 1 Spare 0 2 Command code 0x0F05 Command code issued 3 Spare 0 4 5

Error code 0 0 : No error Other than 0 : Error occurring

6~7 Number of retrieved histories

3 The number of retrieved histories is set.

8~37 Alarm history (1) "03/01/01 15:20:26 EMG EMERGENCY EXIN $3 "

-24690/2000=-12.345mm

38~67 Alarm history (2) "03/01/01 15:20:26 EMG EMERGENCY EXIN $2 "

1000/2000=0.500mm

68~97 Alarm history (3) "03/01/01 15:20:26 EMG EMERGENCY EXIN $1 "

98~127 Alarm history (4) " "

A space is set if there is no alarm history.

XI. Remote Monitor Tool

XI. Remote Monitor Tool 1. Outline

XI - 1

1. Outline The C64 series remote monitor tool is the software capable of the following functions. Remotely monitoring NC screens by using intranet Inputting and outputting parameters / machining programs

2. System Configuration

2.1 System Requirements

Remote monitor tool works on the following system requirements.

Items Details

Processor Pentium 100MHz or faster RAM 64MB or more Hard disk space 50MB or more (apart from the capacity required for OS) OS Microsoft Windows95/98 or Microsoft WindowsNT4.0 Interface 10/100M Ethernet Monitor Resolution 800 x 600 or more, 256 colors or more Restriction on the number of Remote Monitor Tools connected

Maximum 8 NC screens per 1 NC can be connected. (Including setup/maintenance tool)

Connectable NC MELDAS C6/C64/C64T Ver. C or later versions. (Ethernet option card must be mounted in this case.)

2.2 Contents of Software Package

The software package consists of the following items. C64 series Remote monitor tool installation disk Software license agreement

XI. Remote Monitor Tool 3. Installation of Remote Monitor Tool

XI - 2

3. Installation of Remote Monitor Tool

(1) Insert an installation disk into a CD-ROM drive. After a while, the setup program of Remote monitor tool starts. (In the case of the personal computer with which reading of CD-ROM is not automatically performed, double-click Setup.exe in a setup disk.) Choose the language used by installation and click "OK" button.

(2) The screen of "Welcome!" is displayed. Click a "Next" button according to the dialogue in a screen.

XI. Remote Monitor Tool 3. Installation of Remote Monitor Tool

XI - 3

(3) Next, the "License Agreement" screen is displayed. When you read the contents well and agree with the license agreement, click "Yes". Click "NO" to cancel installation. If clicked "Back", it will return to the screen of "Welcome".

(4) Next, the "Choose Destination Location" screen is displayed. Here, the directory which installs Remote monitor tool can be chosen. When you install in other directories, click "Browse" and choose a directory. Click "Next", if selection is made, then installation of Remote monitor tool is started.

XI. Remote Monitor Tool 4. Uninstalling the Remote Monitor Tool

XI - 4

4. Uninstalling the Remote Monitor Tool

Uninstall the remote monitor tool with following steps. (1) Quit the remote monitor tool.

(2) Click [Start] [Setting] [Control panel].

(3) Double-click on [Add/Remove Program].

(4) Click on "Remote monitor tool".

(5) Click on "Add/Remove".

(6) Follow the onscreen instructions.

XI. Remote Monitor Tool 5. How to Start and Operate

XI - 5

5. How to Start and Operate How to start and operate the remote monitor tool software is explained in this section.

5.1 Starting Remote Monitor Tool

Click on [Start] [Program] [MELDAS C64] [Remote monitor tool]. Multiple windows of the remote monitor tool can be opened, so the 1st and 2nd NC can be monitored simultaneously.

XI. Remote Monitor Tool 5. How to Start and Operate

XI - 6

5.2 Screen Makeup of Remote Monitor Tool The window of Remote monitor tool consists of a title bar, menu bar, status bar and NC information display etc.

5.3 Basic Operation of Remote Monitor Tool

5.3.1 Title Bar

Title bar shows the tool name "ReC64Monitor"

Tool name

Iconify the tool

Exit from the tool

IP address of the connected NC

Item Details

Tool name The tool name is displayed. The tool name is used for being identified in Windows.

IP address of the connected NC

When the tool is in online mode, the IP address of connected NC is displayed.

Iconification of tool Click this button to minimize the window of Remote monitor tool to the size of an icon and to be contained in the task bar.

Exit Click this button to exit from Remote monitor tool.

Menu bar Title bar

Tool bar NC information

Status bar

XI. Remote Monitor Tool 5. How to Start and Operate

XI - 7

5.3.2 Menu Bar Each function including connection destination designation is able to be selected from the menu bar.

(1) File menu

The commands for the basic operation of the tool are allocated on the [File (F)] menu.

Sub menu Details Connect This connects with the designated NC. When selecting this menu, the

dialogue box to designate connection destination shows up. Translate This is used when sending and receiving the parameters, machining

programs and maintenance data to and from NC. By selecting each menu item, file transferring tool will be activated.

Online This is used for selecting online (connecting) mode or offline (disconnecting) mode.

Exit This exits from Remote monitor tool.

(2) Help menu An explanation about the operation etc. is allocated on the [Help] menu.

Sub menu Details Help topics This displays the explanation of how to treat Remote monitor tool. About Remote monitoring tool

This shows the software version of Remote monitor tool.

5.3.3 Connect with Machine Tools (NC) Select [File] [Connect] from the menu bar and display the [Connection] dialogue box. Input the IP address of the NC to connect with and press the button [Connect]. If the communication is started normally, a screen of the connected NC will be displayed. (The screen of the connected NC is displayed only when "Base specification parameters #21034" is set to "0"). If any communication error occurs, [Communication Error] will be displayed on the status bar. By describing NC list in the Hosts File in advance, the NC to connect with can be selected from the list. Refer to "8. Supplement" of this chapter for creating the host files.

XI. Remote Monitor Tool 5. How to Start and Operate

XI - 8

5.3.4 Send and Receive a Parameter File Select [File] [Translate] [Parameter] [Text] from the menu bar. Or, select [Binary] and display the [ParameterText] dialogue box or the [ParameterBinary] dialogue box. Receiving a parameter file

When receiving a parameter file from NC, select "ALL.PRM" (text format) or "PARAMET.BIN" (binary format) and press the [Receive] button.

Sending a parameter file When sending a parameter file to NC, press [Send] button, designate the directory to store the file and a file name of the sending file and then press the [Open] button.

(Note) The parameters can be sent when sending is validated with "ReC64Monitor.ini".

Refer to "8. Supplement" of this chapter for details on setting this parameter.

Designate the applicable parameter file.

Save/send file name designation

Save/send file directory designation

XI. Remote Monitor Tool 5. How to Start and Operate

XI - 9

5.3.5 Send and Receive the Program Select [File] [Translate] [Program] [Text] from the menu bar. Or, select [Binary] and display the [ProgramText] dialogue box or the [ProgramBinary] dialogue box. Receiving a machining program file

When receiving a machining program file from NC, select the program from the list, designate directory to store the file and the file name and then press the [Receive] button. When selecting a machining program file, plural files can be selected by clicking the file names displayed in the list while pressing Ctrl key.

Sending a machining program file When sending a machining program file to NC, press the [Send] button, select the sending program from the list and press the [Open] button.

(Note) The parameters can be sent when sending is validated with "ReC64Monitor.ini".

Refer to "8. Supplement" of this chapter for details on setting this parameter.

Designate the applicable program file.

Save/send file name designation

Save/send file directory designation

XI. Remote Monitor Tool 5. How to Start and Operate

XI - 10

5.3.6 Receiving a Maintenance Data

Select [File] [Translate] [Maintenance] from the menu bar, and display [Maintenance] dialogue box.

The maintenance data is used for protecting the users data or for investigating the cause of the problem. When receiving a maintenance file from NC, select "SRAM.BIN" in the displayed list, designate the directory to store the data and the file name and then press the [Receive] button.

5.3.7 Refer to NC Information

Press the keyboard or click the buttons on the screen with a mouse to work on the NC information The keyboard keys used for NC information reference are as shown below.

Keyboard keys Buttons to be clicked F1 Menu 1 F2 Menu 2 F3 Menu 3 F4 Menu 4 F5 Menu / Operation F6 Position display F7 Alarm diagnosis F8 Tool offset / Param. F9 Program , , , Cursor Page up, Page Dn Back / Next Home C+B/CAN Insert Add Delete Delete Back space Delete Tab, Shift + Tab Tab / Shift + Tab ; EOB Enter INPUT 0 ~ 9 0 ~ 9 !, #, $, (, ), =, , +, [, ], *, / !, #, $, (, ), =, , +, [, ], *, / ,. ,. SPACE Space

XI. Remote Monitor Tool 5. How to Start and Operate

XI - 11

5.3.8 Search the Topics Select [Help] [Help Topics] from the menu bar, and display the help screen. On the "table-of-contents" page, the help system consists of a format of a volume and a page.

5.3.9 Confirm the Remote Monitor Tool Version Select [Help] [About Remote monitoring tool] from the menu bar, and display the [Version] dialogue box for version information.

XI. Remote Monitor Tool 5. How to Start and Operate

XI - 12

5.3.10 Using a Tool Bar

Designation of the NC to connect with or other functions can be used without selecting from the menu. Besides, the outline of the function is displayed by placing the cursor on the tool bar.

5.3.11 Using a Status Bar

The status of Remote monitor tool including communication status is displayed on the status bar.

No. Display Details 1 ONLINE This means the status in which Remote monitor tool is communicating

with the designated NC. Select the [START / STOP] button on the tool bar or select [Offline] in the menu to change the status to the offline mode.

2 OFFLINE This means the status in which Remote Monitor Tool is not communicating with the designated NC. Select the [START / STOP] button on the tool bar or select [Online] in the menu to change the status to the online mode.

3 COMMUNICATION ERROR

This means that the communication error between Remote monitor tool and the connected NC has occurred.

4 DISPLAY INVALID This means the status in which the NC screen cannot be displayed by Remote monitor tool due to the incorrect NC parameter settings. NC screen can be displayed by setting "Base specification parameters #21034"to "0".

5 READY This status is displayed when the connected NC is ready to start operating.

XI. Remote Monitor Tool 6. Setting NC Parameters

XI - 13

6. Setting NC Parameters By setting Base specification parameters in NC, the key operation and the display can be restricted.

# Item Detail Setting range

Standard setting value

21033 KeyCtrlLmt Restriction on the right to operate the keys

Restrict the right to operate the keys. 0: The keys on other display units can

operate all the screens. 1: The keys on other display units are

disabled while a program screen is displayed.

2: The keys on other display units cannot operate any screen.

0 to 2 0

21034 ReMonDisp Display restriction

Restrict to display with Remote monitor tool. 0: No restriction on the display with

Remote monitor tool. 1: No information about display is

sent to Remote monitor tool. (Note) Do not set the parameter with

Remote monitor tool, or nothing will be displayed immediately after the setting has been done.

0 to 1

0

XI. Remote Monitor Tool 7. Error Message and Its Remedy

XI - 14

7. Error Message and Its Remedy The details of the errors that would occur while Remote monitor tool is running and the remedies are listed below.

No. Message Details Remedy

1 Communication error

Communication error is occurring between Remote monitor tool and the designated NC.

Confirm the following items and retry. Confirm: that the designated IP address is correct. that there is no problem with a connecting cable. that the ping command in the designated IP address is normal. that the communication traffic is not crowded.

2 Duplication error More than 1 dialogue boxes for transferring files are opened.

If more than 1 dialogue boxes for transferring files are opened, close them leaving only 1 dialogue box.

3 Directory open error

The directory information was not acquired successfully in the file transferring dialogue.

Confirm the following items and retry. Confirm: that there is no problem in the file system of the connected NC. that no communication error is occurring.

4 Directory search error

The directory information was not searched successfully in the file transferring dialogue.

Confirm the following items and retry. Confirm: that there is no problem in the file system of the connected NC. that no communication error is occurring.

5 Reserved word

"COM1 to COM9, LPT1 to LPT9, AUXCON, PRN, NUL, CLOCK" has already reserved in the system.

Use words other than "COM1 to COM9, LPT1 to LPT9, AUXCON, PRN, NUL, CLOCK"

6 Incorrect file name "/,;,:,*?"<>|\" or Tab is used for the file name. Do not use "/,;,:,*?"<>|\" nor Tab when naming the title of the file.

7 Select file name The file to send or receive is not selected. Retry after selecting the file to send or receive.

8 File reception error

Error has occurred while receiving a parameter file, machining program file or maintenance data.

Confirm the following items and retry. Confirm: that there is no problem in the file system of the connected NC. that no communication error is occurring.

9 File sending error Error has occurred while sending a parameter file or machining program file.

Confirm the following items and retry. Confirm: that there is no problem in the file system of the connected NC. that no communication error is occurring. that the connected NC is not in the data protect mode. that the connected NC is running.

10 File designation error

The designated file does not exist. Confirm that the designated file exists and retry.

11 File deletion error

When overwriting a sending or receiving a file, the file was not deleted successfully.

When overwriting a file on PC side, confirm that the property of the file is not set to "read only". When overwriting a file on NC side, confirm the following items and retry. Confirm: that there is no problem in the file system of the connected NC. that no communication error is occurring. that the connected NC is not in the data protect mode. that the connected NC is running.

XI. Remote Monitor Tool 8. Supplement

XI - 15

8. Supplement (1) Key operation rights

To operate a screen when another display (NC dedicated display or adjustment and maintenance tool) is connected, press the F5 key or "Key operation rights" button to retrieve the screen operation rights.

(2) Number of simultaneous connections

Up to eight "remote monitor tool + operation panel (adjustment and maintenance tool)" sets can be connected at once. A communication error message will appear if more are connected.

(3) Creating the hosts file By saving the Hosts file with the following format under the name "C64Hosts" in the C:\Program files\MELDAS C64\Remote monitor tool (default installation directory), a list of the connection destinations can be displayed. Set the name of the connection destination with up to 20 characters, excluding spaces and tabs.

# = Comment IP address [space] connection destination name

Description example

#C64 connection destination list # 192.168.1.2 SP117 192.168.1.3 SP118 192.168.1.4 SP119 192.168.1.5 SP120 192.168.1.6 SP121

(4) Setting the parameter/machining program file transmission validity

To validate transmission of parameter files or machining program files, add the line "DOWNLOAD=1" to the "ReC64Monitor.ini" file located in the "C:\Program files\MELDAS C64\Remote monitor tool (default installation directory)". [Setting example]

[COMMUNICATION]

DOWNLOAD=1

Revision History

Date of revision Manual No. Revision details

Sep. 2003 BNP-B2373* First edition created.

Apr. 2004 BNP-B2373A The following changes were made to comply with the software version D. (1) The following chapters were added. "V Ethernet 2-channel Connection" "VII Ethernet Interface Communication Function Using PLC

(Client Function Section)" "VIII I/O/Intelligent Function Unit Connection Function"

(2) The following chapter was deleted. "VIII FL-net interface" "IX Appendix" (Moved to Chapter II and Chapter X.)

(3) The number of steps was changed in "III CC-Link Master/local Unit". (4) The contents of "IX GOT Connection Function" (previous Chapter VII)

were totally reviewed. (5) Mistakes, etc., were corrected.

Dec. 2004 BNP-B2373B (1) "X. GOT Window Function" was added. (2) The following chapters' explanations were added. "VIII MELSEC Q Series I/O/Intelligent Function Unit Connection Function" "IX. Connection Function with GOT"

Notice

Every effort has been made to keep up with software and hardware revisions in the contents described in this manual. However, please understand that in some unavoidable cases simultaneous revision is not possible. Please contact your Mitsubishi Electric dealer with any questions or comments regarding the use of this product.

Duplication Prohibited This instruction manual may not be reproduced in any form, in part or in whole, without written permission from Mitsubishi Electric Corporation.

2003-2004 MITSUBISHI ELECTRIC CORPORATION ALL RIGHTS RESERVED

Manualsnet FAQs

If you want to find out how the C64 Mitsubishi works, you can view and download the Mitsubishi C64 Numerical Control Network Manual on the Manualsnet website.

Yes, we have the Network Manual for Mitsubishi C64 as well as other Mitsubishi manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The Network Manual should include all the details that are needed to use a Mitsubishi C64. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Mitsubishi C64 Numerical Control Network Manual is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Mitsubishi C64 Numerical Control Network Manual consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Mitsubishi C64 Numerical Control Network Manual free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Mitsubishi C64 Numerical Control Network Manual, simply download the document to your computer. Once downloaded, open the PDF file and print the Mitsubishi C64 Numerical Control Network Manual as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.