PX Developer Version 1 Operating Manual (Monitor Tool)

2 SYSTEM CONFIGURATION

MELSOFT


2.1 System Configuration

This section deals with system configuration of monitor tools.

2.1.1 Supported CPU

Process CPU: Q02PHCPU, Q06PHCPU, Q12PHCPU, Q25PHCPU

Redundant CPU: Q12PRHCPU, Q25PRHCPU

2.1.2 Communication route

(1) Connecting to Process CPU

QnPHCPU +

Serial communication module

QnPHCPU

MELSECNET/H Remote I/Omodule

RS-232 cable

MELSECNET/10(H)

(RemoteI/O network)

QnPHCPU

QnPHCPU + CC-Link module

RS-232 cable

1)-3

RS-232 cable

USB cable

1)-1

G4 module

1)-4

RS-422 conversion cable

PX

Developer

1)-2

QnPHCPU +

CC-Link IE Controller Network,

MELSECNET/H module


MELSECNET/10(H) board

2) 3) 4) 5)

CC-Link IE

Controller Network,

MELSECNET/10(H)

(PLC network)

Twisted pair cable

7) 8) 6)

CC-Link board

Commercially available Ethernetboard

QnPHCPU + Ethernet module

Twisted pair cable

USB cable

RS-232 cable

GOT

Ethernet

QnPHCPU

2

2-1 2-1


MELSOFT

2

Supported route when using Process CPU

When Process CPU is applied for normal operations as operator station, configuring the system that can receive the event notification is required. For details, refer to Appendix 1.2.

No. Connection method Precautions for connection

1)-1 CPU module

Applicable only for adjusting the CPU.

If applied for performing normal operations of the CPU as operator station, the performance cannot be guaranteed. *

1

One CPU module can be connected from one personal computer by USB cable. *

2

1)-3

Serial/USB connection

MELSECNET/10(H) remote



1

Use the type of AJ65BT-G4-S3.

2)

3)

5)

8)

MELSECNET/10 connection

(When using the MESECNET/

10 board)


(When using the MESECNET/ H board)

CC-Link IE Controller Network connection

GOT transparent connection*

6


1

The PLC must be set to the MELSECNET/10 compatible mode.

When connecting a PLC using different types of networks in single network connection or connecting in coexistence network connection, the performance as an operator station in normal operation is not guaranteed. *

1

The MELSECNET board and PLC must be set to the MELSECNET/10 compatible mode.


1


1

CC-Link IE Controller Network compatible version of Process CPU is required.*

3

The driver for CC-Link IE Controller Network board which supports the event notification function is required.*

4

Applicable only for adjusting the CPU when connecting a PLC using different types of networks in single network connection or connecting in coexistence network connection.


1

The performance as an operator station in normal operation is not guaranteed under the following conditions. *

1

• The IP addresses of the Ethernet module and personal computer are not in the same segment.

• When a wireless LAN adapter (NZ2WL) *

5

is applied for communication route.

• Single network connection in which a PLC is connected using different types of networks or in coexistence network connection.



1

CC-Link Ver.1 and Ver.2 boards cannot be used together.

Connection method via GOT is the same as that of GX application.

Note that, GOT transparent function via GOT 2000 is not supported by GX

Developer.



1

2-2 2-2


MELSOFT

*1: This happens as the monitor tool cannot receive event notification. For the system configuration that can receive event notification, refer to Appendix 1.2.

*2: Refer to POINT in Section 2.1.3 .

*3: The Process CPU whose first five digits of serial number is 10042 or later is required.

*4: The driver for CC-Link IE Controller Network board (SW1DNC-MNETG-B) version 1.08J or later is required.

*5: Use a wireless LAN adapter corresponding to national standards where it is used. For details, refer to the manuals of wireless LAN adapter.

*6: For details of GOT transparent function, refer to the following manuals:

• GOT2000 Series Connection Manual (Mitsubishi Product) For GT Works3 Version1

• GOT1000 Series Connection Manual (Mitsubishi Products) for GT Works3

• GOT-A900 Series User's Manual (Connection System Manual)

• GOT-F900 SERIES HARDWARE MANUAL [Connection]

2-3 2-3


(2) Connecting to Redundant CPU of redundant system

(backup mode/separate mode)

QnPRHCPU redundant configuration

MELSOFT


Tracking cable

Tracking cable

Redundant type extension base unit

+ serial communication module


MELSECNET/10(H)

(remote I/O network)

RS-232 cable

USB cable

RS-232 cable

Tracking cable

QnPRHCPU+CC-Link IE

Controller Ne twork, MELSECNET/H module redundant configuration

MELSECNET/H remote I/O module or serial communication module

RS-232 cable

1)-2,3

1)-2 1)-1

PX

Developer

CC-Link IE Co ntroller Network,

MELSECNET/H board

2) 3) 4)

CC-Link IE

Controller Network,

MELSECNET/10(H)

(PLC network)

QnPRHCPU +

CC-Link module redundant configuration

Tracking cable

Tracking cable

G4 module

1)-4


Twisted pair cable

6) 7) 5)

CC-Link board

Commercially available

Ethernet board

QnPRHCPU +

Ethernet module redundant configuration

Twisted pair cable


Tracking cable

Ethernet


Tracking cable


+ CC-Link module

Twisted pair cable

USB cable

RS-232 cable

GOT

Tracking cable


+ Ethernet module


Tracking cable

2-4 2-4


MELSOFT

Supported route when using Redundant CPU (redundant configuration)



1)-1

Serial/USB connection

1)-3

2)

4)

CPU module


MELSECNET/10 connection*

4





1

Connect a cable to the CPU module in either of system A or system B.

(The communication is performed with the CPU module of another system via tracking cable.)


2

When connecting via the serial communication module mounted to the redundant type extension base unit, the version of Redundant CPU needs to be compatible with the redundant type extension base unit. *

3



1



1



1


The driver for MELSECNET/H interface board and the MELSECNET/H module whose versions support Redundant CPU are required. *

5

When connecting PLCs using different types of networks in single network connection or connecting in coexistence network connection, the performance as an operator station in normal operation is not guaranteed. *

1


5

When connecting PLCs using different types of networks in single network connection or connecting in coexistence network connection, the performance as an operator station in normal operation is not guaranteed. *

1

CC-Link IE Controller Network compatible version of Redundant CPU is required.

*

6

The CC-Link IE Controller Network module whose version supports Redundant

CPU is required.*

7


8



1

2-5 2-5


MELSOFT

No.

7)

Connection method


11

Precautions for connection

The Ethernet module of function version D or later is required to support the

Redundant CPU.

When connecting via the Ethernet module mounted to the redundant type extension base unit, the version of Redundant CPU needs to be compatible with the redundant type extension base unit. *

3


1



9



• Connection via the Ethernet module mounted to a redundant type extension base unit.

• When using monitor tool with Windows Vista R or later, the IP addresses of

Ethernet modules of both system A and system B are not on the same segment.

The driver for CC-Link Ver.1 board and CC-Link module whose versions support

Redundant CPU are required. *

10



1


When connecting via the CC-Link module mounted to the redundant type extension base unit, the version of Redundant CPU needs to be compatible with the redundant type extension base unit. *

3




Developer.


1


*2: Refer to POINT in Section 2.1.3.

*3: The Redundant CPU whose first five digits of serial number is 09012 or later is required.

*4: The MELSECNET/10 board is inapplicable, as the driver (SW DNF-MNET10) is incompatible with the Redundant

CPU.

*5: For MELSECNET/H interface board, refer to Section 2.1.4 (1). For MELSECNET/H interface module, the function version D or later is required.


*7: The CC-Link IE Controller Network module whose first five digits of serial number is 10041 or later is required.



*10: For CC-Link Ver.1 board, refer to Section 2.1.4 (3). For CC-Link module, the QJ61BT11N whose first five digits is

06052 or later is required.






2-6 2-6


MELSOFT

(3) Connecting to Redundant CPU of single configuration (debug mode)

QnPRHCPU single CPU configuration


+ serial communication module



MELSECNET/10(H)

(remote I/O network)

RS-232 cable

USB cable

RS-232 cable

MELSECNET/H remote I/O module or serial communication module

RS-232 cable

1)-2,3

1)-2

PX

Developer

1)-1

QnPRHCPU+CC-Link IE

Controller Network, MELSECNET/H module single CPU configuration


MELSECNET/H board

2) 3) 4)

CC-Link IE

Controller Network,

MELSECNET/10(H)

(PLC network)

QnPRHCPU + CC-Link module single CPU configuration

G4 module

1)-4


6)

Twisted pair cable

5)

Commercially available

Ethernet board

QnPRHCPU + Ethernet module single CPU configuration


CC-Link board

Ethernet


Twisted pair cable

7)

USB cable

RS-232 cable


+ CC-Link module

GOT


+ Ethernet module

QnPRHCPU

Single CPU configuration

2-7

POINT

When monitoring the Redundant CPU in the debug mode, power off the other

Redundant CPU or disconnect the CPU from network. Otherwise, a communication error may occur or PX Developer may not normally monitor.

2-7


MELSOFT

Supported route when using Redundant CPU (single CPU configuration)



1)-1

1)-3

2)

4) connection

CPU module


MELSECNET/10 connection*

4





1


2

When connecting via the serial communication module mounted to the redundant type extension base unit, the version of Redundant CPU needs to be compatible with the redundant type extension base unit. *

3



1



1



1



5


1


5


1

CC-Link IE Controller Network compatible version of Redundant CPU is required.*

6

The CC-Link IE Controller Network module whose version supports Redundant

CPU is required. *

7


8



1

The Ethernet module of function version D or later is required to support the

Redundant CPU.

When connecting via the Ethernet module mounted to the redundant type extension base unit, the version of Redundant CPU needs to be compatible with the redundant type extension base unit. *

3


1



9



• Connection via the Ethernet module mounted to a redundant type extension base unit.

2-8 2-8


MELSOFT

No.

7)

Connection method


11

Precautions for connection

The driver for CC-Link Ver.1 board and CC-Link module whose versions support

Redundant CPU are required. *

10



1


When connecting via the CC-Link module mounted to the redundant type extension base unit, the version of Redundant CPU needs to be compatible with the redundant type extension base unit. *

3




Developer.


1


*2: Refer to POINT in Section 2.1.3.


*4: The MELSECNET/10 board is inapplicable, as the driver (SW DNF-MNET10) is incompatible with the Redundant

CPU.

*5: For MELSECNET/H interface board, refer to Section 2.1.4 (1). For MELSECNET/H interface module, the function version D or later is required.


*7: The CC-Link IE Controller Network module whose first five digits of serial number is 10041 or later is required.



*10: For CC-Link Ver.1 board, refer to Section 2.1.4 (3). For CC-Link module, the QJ61BT11N whose first five digits is







2-9 2-9


MELSOFT

(4) Using the PC CPU module

MELSECNET/H

(Remote I/O network)

QnPHCPU/

QnPRHCPU

Serial communication module

MELSECNET/H

(Remote I/O network)

MELSECNET/H remote I/O module

QnPHCPU/QnPRHCPU

+CC-Link module

Twisted pair cable

G4 module

QnPHCPU +Serial communication module QnPRHCPU

RS-232 cable

MELSECNET/H board

RS-232 cable

USB cable

QnPHCPU/

QnPRHCPU

RS422 cable

QCPU

1)-4 1)-3 1)-2

Serial/USB

PC CPU module

1)-1 4)

Ethernet

QnPHCPU/QnPRHCPU

+Ethernet module

MELSEC

NET/H module

CC-Link module

QnPHCPU/QnPRHCPU

+MELSECNET/H module

2) 3)

MELSECNET/H

(PLC network)

PX Developer

5)

QnPHCPU/QnPRHCPU

+CC-Link module

BUS I/F driver

MELSECNET/H

CC-Link

Main base module (Q series bus)

Supported route when using PC CPU module



1)-1 CPU module

1)-3 connection

MELSECNET/H remote

Same with the precautions for Serial/USB connection of (1) to (3).

2)

4)


(When using the MESECNET/

H module)

Same with the precautions for MELSECNET/10 connection of (1) to (3). *

2

However, applicable only for adjusting the CPU.


1

Same with the precautions for MELSECNET/H connection of (1) to (3). *

However, applicable only for adjusting the CPU.

2


1

Ethernet connection Same with the precautions for Ethernet connection of (1) to (3).

5) CC-Link connection Same with the precautions for CC-Link connection of (1) to (3). *

2


*2: If accessing other station via MELSECNET/H module and CC-Link module, the PC CPU must be set to control the network modules.

2-10 2-10


MELSOFT

2.1.3 Serial/USB connection

(1) Connection cables for serial/USB connection

The connection method of serial/USB connection cable is the same when they are connected to GX application. For the applicable cables, refer to the following manuals:

 GX Works2 Version 1 Operating Manual (Common)

 GX Developer Version 8 Operating Manual

POINT

The USB cable connection is not applicable in the following connection structure.

Only one personal computer and one CPU module can be connected by USB cable.

<Structures cannot be constructed>

One personal computer installed with several USB ports is connected to multiple CPU modules.

CPU module

USB cable

USB ca ble

CPU module

One personal computer is connected to multiple CPU modules through USB hub.

CPU module

USB cable

USB hub

USB cable

USB c able

CPU module

REMARK

By connecting a tracking cable to the Redundant

CPU in either of system A or system B,

QnPRHCPU in both systems can be monitored.

(The communication is performed with the CPU module of another system via tracking cable.)

QnPRHCPU

Tracking cable

RS-232 cable (QC30R2) or USB cable

PX

Developer

2-11 2-11


MELSOFT

(2) Precautions on USB connection

1) A communication error may occur when the personal computer communicates with the CPU module after setting the resume function, suspend setting, power-saving function or standby mode.

Do not set any of the above functions for communication with the CPU module.

2) A communication error may occur and normal operation may not be recovered if connecting and disconnecting a USB cable, resetting the CPU module or turning the power ON/OFF is performed frequently during communication with the CPU module.

When a communication error occurs and normal operation is not recovered, remove a USB cable from the CPU module, and then reconnect it after more than five seconds.

(Even after this operation, an error may occur at the initial communication.

Communication, however, will be performed normally at the second time and later.)

2-12 2-12


MELSOFT

2.1.4 Network board

The following describes the applicable network boards to PX Developer Monitor Tool.

For details of corresponding operating systems of network boards, refer to the each network board manual.

(1) MELSECNET/10, MELSECNET/H, CC-Link IE Controller Network board

Network Board

MELSECNET/10

MELSECNET/10 *

MELSECNET/H

CC-Link IE

3

Controller Network

A70BD-J71QLP23 (For PC/AT, optical)

A70BD-J71QBR13 (For PC/AT, coaxial)

Q81BD-J71LP21-25 (For PC/AT, optical) *

4

Q80BD-J71LP21-25 (For PC/AT, optical) *

4

Q80BD-J71LP21S-25 (For PC/AT, optical)

(With external power supply) *

4

Q80BD-J71LP21G (For PC/AT, optical) *

4

Q80BD-J71BR11 (For PC/AT, coaxial) *

4

Q81BD-J71GP21-SX (For PC/AT, coaxial) *

9,

*

10

Q81BD-J71GP21S-SX (For PC/AT, optical)


9,

*

10

Q80BD-J71GP21-SX (For PC/AT, optical) *

9,

*

10

Q80BD-J71GP21S-SX (For PC/AT, optical)


9,

*

10

Driver

SW3DNF-MNET10 (For PC/AT, optical) *

SW0DNC-MNETH(-B)

(For PC/AT, optical) *

5,

*

6,

*

7,

*

8,

SW1DNC-MNETG-B *

11,

*

12,

*

*

14

13,

*

15

1,

*

2

*1: MELSECNET/10 board is inapplicable to Redundant CPU.

*2: Can be used only for Microsoft

R

Windows

R

98 Operating System and Microsoft

R

Workstation Operating System Version 4.0

*3: Should be used in the MELSECNET/10 compatibility mode.

Windows NT

R

*4: The product whose first five digits of serial number are "06032" or later is required to connect to the

Redundant CPU.

*5: Cannot be used for Microsoft

R

Windows

R

Millennium Edition Operating System

*6: The driver (SW0DNC-MNETH(-B)) version 90K or later is required to connect to Redundant CPU.

*7: For Windows

R

7, the driver (SW0DNC-MNETH-B) version 21X or later is required.

*8: For Windows

R

8, the driver (SW0DNC-MNETH-B) version 26C or later is required.

*9: When connecting with the following CPUs, the CPU module whose first five digits is 10042 or later is required.

Q12PHCPU, Q25PHCPU, Q12PRHCPU, Q25PRHCPU

*10: When connecting with Redundant CPU, the CC-Link IE Controller Network module whose first five digits is


*11: To connect to Q02PHCPU or Q06PHCPU, the driver (SW1DNC-MNETG-B) version 1.03D or later is required. (When connecting to other Process CPU or Redundant CPU, the driver for QnHCPU can be used.)

*12: For Windows

*13: For Windows

R

R

7, the driver (SW1DNC-MNETG-B) version 1.11M or later is required.

8, the driver (SW1DNC-MNETG-B) version 1.16S or later is required.

*14: Cannot be used for Windows

*15: For Windows

R

R

8.1.

8.1, the driver (SW1DNC-MNETG-B) version 1.17T or later is required.

2-13 2-13


MELSOFT

The following table shows the Ethernet board/card whose operations are guaranteed by us.

Maker Model

3COM EthernetLink LAN PC Card

Allied Telesis

TDK

CentreCOM LA-PCM Ethernet PC Card LAN Adapter

RE2000 (ISA)

10BASE-T LAN card (Model: LAN-CD021BX)

If there are restrictions on Ethernet module to Ethernet board, follow the restrictions.

Network Board

CC-Link Ver.1

CC-Link Ver.1

CC-Link Ver.2

A80BDE-J61BT11 (Ver.1 Board) *

1

A80BDE-J61BT13 (Ver.1 Board) *

1

Q81BD-J61BT11 (Ver.2 Board) *

1

Q80BD-J61BT11N (Ver.2 Board) *

1

Driver

SW4DNF-CCLINK-B (for PC/AT) *

SW1DNC-CCBD2-B (for PC/AT) *

2,

4,

*

*

3

5,

*

6

*1: CC-Link Ver.1 and Ver.2 boards cannot be used together with the same PC.

*2: If connecting to a Redundant CPU, SW4DNF-CCLINK-B of version G or later is required.

*3: Cannot be used for Microsoft

R

XP

R

Windows

Home Edition, and Windows Vista

R

R

Millennium Edition Operating System, Microsoft

R or later.

*4: For Windows Vista

R

, the driver (SW1DNC-CCBD2-B) version 1.04E or later, for Windows

R

(SW1DNC-CCBD2-B) version 1.08J or later is required.

*5: For Windows

R

8, the driver (SW1DNC-CCBD2-B) version 1.13P or later is required.

*6: Cannot be used for Windows

R

8.1.

Windows

7, the driver

2.1.5 Printer

No limitation in this application.

Printer on personal computer can be used.

2-14 2-14


MELSOFT

2.1.6 Monitoring system configuration with Monitor Tool

(1) Server/client monitoring system configuration

In the server/client monitoring system, up to eighteen OPSs

*1

and up to sixteen

PLCs are connectable. In this case, clients access the monitoring data

*2 collected/managed by a server.

*1: One primary server, one secondary server, and up to sixteen clients, coming to eighteen in all, in the server/client configuration

*2: Clients can display the following kinds of the monitoring data collected by

Server.

 Setting data

 Tag data (Displayed on the control panel and pop-up windows)

 Trend data

 Alarm data

 Event data

18 OPSs

Monitor tool clients

Access the monitoring data collected/managed

by a server and display it.

PX

Developer

Monitor tool server (primary)

Communicates with PLCs in a batch

and collects/manages/displays the

monitoring data.

Personal computer

(primary server)

PX

Developer

PX

Developer

PX

Developer

Personal computers

(client)

Ethernet

PX

Developer

Monitor tool server (secondary)

Synchronizes the setting data with the primary server to provide against outages of the primary server.

Personal computer

(secondary server)

CC-Link IE Controller Network, MELSECNET/10(H), Ethernet

2-15

QnPHCPU QnPHCPU

Tracking cable

QnPRHCPU (redundant system)

Tracking cable


POINT

The CC-Link IE Controller Network or Ethernet connection is recommended if five or more PLCs are to be connected.

2-15


MELSOFT

<System configuration preparing for server outages>

1) Installing two servers (primary and secondary)

Preparing and running a backup server (secondary server) which uses the same setting data as a regular server (primary server) enables the server/client monitoring system configuration providing against server outages. However, the monitoring data is not equalized

*1

even though two servers are running.

Redundant servers enables automatic server switching in the event of a fault of the primary server. Afterward, the connection server can be manually switched after restoration of the primary server. Refer to Section 9.5 for the setting method,

Section 8.6.3 for switching server.

In the redundant server system, the setting data can be changed in the primary server. The secondary server starts up using the setting data of the primary server.

*1: The monitoring data equalization is a process that synchronizes the monitoring data, between the primary server and the secondary server.

(Normal)

Ethernet

PX

Developer

Communication

PX

Developer

PX

Developer

PX

Developer

Primary server

Clients


Secondary server

(Primary server fails)

Ethernet

PX

Developer

Down

PX

Developer

PX

Developer

Connecting to the secondary server automatically

Communication

PX

Developer

Primary server

Clients


Secondary server

2-16 2-16


MELSOFT

2) Installing one server

The server/client monitoring system that has one server (does not have a redundant server) can also be configured.

In the event of a server failure, a client can be connected to PLCs*

1

, and restarted as a substitute server that uses the same setting data*

2

as one used by an original server before the failure.

Change the connection server in the client side when starting a new server. For the setting method, refer to Section 9.5.

*1: To connect a client restarted as Server to PLCs via the same communication route as the failed server, mounting the same network board on a personal computer (client) as a personal computer (server) is necessary.

Also, for connecting a client to PLCs directly, change the PC transfer setting in the monitor target project setting ( Section 9.4).

*2: A client gets the setting data from a server and saves it in itself during executing. Therefore, when restarting as Server, a client can use the setting data gotten from a server immediately before.

(Normal)

Ethernet

PX

Developer

Communication

PX

Developer

PX

Developer

PX

Developer

Server

Clients


2-17

(Server fails)

Ethernet

PX

Developer

Down

Server

Communication

PX

Developer

Client

Standalone

Connecting to PLCs directly.


POINT

The monitoring data that had been collected by a failed server cannot be transferred to a substitute server.

After recovering, a regular server also cannot receive the monitoring data collected by a substitute server during the outage.

2-17

2-18


PX

Developer

MELSOFT

In the standalone monitoring system, one OPS and up to sixteen PLCs are connectable.

For the system configuration in normal operation, refer to Appendix 1.2.1.

Monitor tool

Communicates with PLCs and collects/manages/displays the monitoring data.


QnPHCPU QnPHCPU

Tracking cable


Tracking cable


Up to 16 PLCs

(3) Multiple CPU system with Process CPU

The multiple CPU system including Process CPU can be monitored when the following conditions are satisfied.

 A network module is controlled by each Process CPU, and each Process CPU communicates with control CPU via that network module.

 The whole network includes up to 16 CPUs, including Process CPU of multiple CPU system and CPU module of single CPU system. (In the following diagram, 3 QnPHCPUs are counted.)


Management

Management

QnPHCPU

QnPHCPU

Network module

Network module

QnPHCPU

Network module

Other CPU

Other CPU

<System configuration with multiple CPU system>

* The redundant system does not support the multiple CPU system.

POINT

The CC-Link IE Controller Network or Ethernet connection is recommended if five or more PLCs are to be connected.

2-18

PX Developer Version 1 Operating Manual (Monitor Tool)

Related manuals

Table of contents

PX Developer Version 1 Operating Manual (Monitor Tool)

Related manuals

Mitsubishi Electric

PX Developer Version 1

Mitsubishi Electric

MELSEC iQ-R

Mitsubishi Electric

MELSEC iQ-R

Mitsubishi Electric

MELSEC iQ-R

Mitsubishi Electric

PX Developer Version 1

Mitsubishi Electric

PX Developer Version 1

Mitsubishi Electric

PX Developer Version 1

Mitsubishi Electric

PX Developer Version 1

Table of contents