6F2S1904 (Rev. 1.

21)

GR200 series basic manual

Programmable Logic Controller

and PLC editor

 6F2S1904 (Rev. 1.21)

Safety Precautions
Before using the equipment, please read this chapter carefully.
This chapter describes the safety precautions recommended when using GR equipment.
Before installing and using the equipment, this chapter must be thoroughly read and
understood.
Explanation of symbols used
Signal words such as DANGER, WARNING, and CAUTION, will be followed by
important safety information that must be carefully reviewed.

DANGER Indicates an imminently hazardous situation which will result in

death or serious injury if you do not follow the instructions.
Indicates a potentially hazardous situation which could result in
WARNING
death or serious injury if you do not follow the instructions.
CAUTION Indicates a potentially hazardous situation which if not avoided,
may result in minor injury or moderate injury or property damage.

CAUTION

•Disclaimer of liability
We have checked the description of this manual against the hardware and software
described, but we cannot guarantee that all deviations have been eliminated from the
description completely; hence, no liability can be accepted for any errors or omissions
contained in the information given. We review the information in this manual regularly
and there will be some corrections in subsequent editions. We reserve the right to make
technical improvements without notice.
•Copyright
Copyright © Toshiba Energy Systems and Solutions Corporation, 2019.
All rights reserved.
•Registered Trademarks
Product/Equipment names (mentioned herein) may be trademarks of their respective
companies.

ii
 6F2S1904 (Rev. 1.21)

Content
1 Overview.................................................................................................................................................. 1
PLC software................................................................................................................................... 2
Required environments .................................................................................................................. 2
Function Block (FB), Function ID, Signal number (Data ID) ..................................................... 2
2 Installation and preparation ................................................................................................................. 4
Installation of MULTIPROG ......................................................................................................... 5
Installation of PPCE....................................................................................................................... 7
Installation of ARM ........................................................................................................................ 9
Installation of .NET Framework ................................................................................................. 11
Software customization ................................................................................................................ 12
Setting PC language environment .............................................................................................. 16
Software registration code ........................................................................................................... 17
Preparation of firmware library .................................................................................................. 18
Preparation of user library .......................................................................................................... 21
Update of PLC software ............................................................................................................... 24
3 Connection and project setting ............................................................................................................ 25
How to make the connection between PC and IED.................................................................... 26
PLC project file to create.............................................................................................................. 29
Editing PLC project file................................................................................................................ 31
Build .............................................................................................................................................. 38
PLC data download to IED .......................................................................................................... 39
How to upload PLC data for the PC ............................................................................................ 43
How to save PLC project file ........................................................................................................ 44
4 Debug of PLC data................................................................................................................................ 45
Debug of PLC project file data ..................................................................................................... 46
PLC data error information ......................................................................................................... 47
5 Information of firmware functions ...................................................................................................... 48
About PLC editor .......................................................................................................................... 49
Elementary data type ................................................................................................................... 50
Numeric literals ............................................................................................................................ 51
Flip flop, edge detector, counter and timer function blocks....................................................... 52
Basic functions .............................................................................................................................. 53
Bit operation functions ................................................................................................................. 54
6 How to operate PLC editor................................................................................................................... 55
Worksheet operation..................................................................................................................... 56
Function blocks of Firmware library to be set............................................................................ 68

iii
 6F2S1904 (Rev. 1.21)

User’s logic to be created by PLC ................................................................................................ 75

Extended project export/import ................................................................................................... 78
Setting of Timer function blocks.................................................................................................. 83
Appendix A Firmware libraries ................................................................................................................ 87
Appendix B User libraries......................................................................................................................... 89
App. B.1-1 G2 user library files .......................................................................................................... 91
App. B.2-1 MV user library files ....................................................................................................... 101
Appendix C Libraries folders .................................................................................................................. 105

iv
 6F2S1904 (Rev. 1.21)

1 Overview
Contents Pages
Program logic controller (PLC) 2
PLC screen 2
PLC software (MULTIPROG®) 2
Required memory capacity 2

——————————————————————————————————————————————
†PLC main feature is discussed in Chapter PLC function of each GR200 series IED manual.
‡See also the instruction manual “Operation manual GR-TIMES (6F2M1082)” separately.

PLC editor
- 1 -
 6F2S1904 (Rev. 1.21)

PLC software
Programmable logic controller (PLC) provides the user to program binary inputs/outputs (I/Os),
alarms and indications (LEDs), and recording functions in GR200 series IEDs. The PLC
function are made of “timers”, “flip-flops”, “AND, OR, XOR, NOT” gates. The user is required
to install the PLC software (MULTIPROG®) in the PC. Figure 1.1-1 shows an example of a PC
screen.

Project tree
window

Edit Wizard
Work sheet screen screen

Figure 1.1-1 Screen provided by MULTIPROG®

Required environments
A PC requires memory (4G bytes or more) to run the PLC software (MULTIPROG®), if anther
software, such as GR-TIMES‡, should run together with in a PC, because the PLC software
requires some memory capacity (i.e., 3G bytes) in the PC.

Function Block (FB), Function ID, Signal number (Data ID)

(i) Signal symbols
Function Block (FB) is the software module and GR-series IED implements FBs for protections,
controls and communications. The function ID is unique ID described by six digits in
hexadecimal; each function ID represents each FB. Signal number (or Data ID) is the logical
address of the input and output data of the FB. The signal number (Data ID) consists of a
function ID and an element ID. The function ID is common within the FB; accordingly the
element ID will be shown to make description simple. The element ID is 10 hexadecimal and
it has the element ID name for easy to read. Figure 1.3-1 exemplifies the symbols, the function

PLC editor
- 2 -
 6F2S1904 (Rev. 1.21)

ID, and the element ID. The table below shows the structure of the signal.

Function ID Element ID Note

Format (Hex) FFFFFF XXXXXXXXXX Content

Signal example 123456 80000xxxx0 XX relay in phase-A is operated.
Element ID

FB (Function ID=123456)
80000xxxx0 8000xxxxxx
A & ≥1 XX1_OPT
81000xxxx1
XX1 B &
82000xxxx2
C
&
Element ID Signal name
&
8000011xxx0 XX_BLOCK 1

3. PLC connection point† 1. Relay element 2. Signal monitoring point

Figure 1.3-1 Example of symbols and others
†Note that a PLC connection point can be shown with the function ID (123456) plus
element ID (8000011xxx0) expressed in 16 delights in hexadecimal, in some scheme
logics. The ‘PLC connection point’ could be found to search the letter ‘E’ of element ID
(i.e., ‘8000011Exx0’).

(ii) Data length (bit length of Data ID)

The user can read data length of a Data ID by seeing the seventh and eighth number of the
Data ID. Table 1.3-1 shows examples of 1~32-bits data.
Table 1.3-1 How to identify a Data length by seeing Element ID
Data Example Example
Identifier texts Note
length Function ID Element ID
1-bit 400001 8000001B6F 8 (the beginning # of Element ID)
8-bits 400001 2000001B6F 20 (First and second # of Element ID)
8-bits 400001 3000001B6F 30 (First and second # of Element ID)
16-bits 400001 2100001B6F 21 (First and second # of Element ID)
16-bits 400001 3100001B6F 31 (First and second # of Element ID)
32-bits 400001 2200001B6F 22 (First and second # of Element ID)
32-bits 400001 3200001B6F 32 (First and second # of Element ID)
32-bits 400001 4200001B6F 42 (First and second # of Element ID) Float 32
64-bits 400001 2300001B6F 23 (First and second # of Element ID)
64-bits 400001 3300001B6F 33 (First and second # of Element ID)
64-bits 400001 4300001B6F 43 (First and second # of Element ID) Float 64

PLC editor
- 3 -
 6F2S1904 (Rev. 1.21)

2 Installation and preparation

Contents Pages Pages
G2EclrNatveFW 19 Software registration code 17

Installation - Update of PLC software 24

-MULTIPROG® 5
-PPCE software 7
-ARM software 9
-.NET Framework (3.5) 11
-.NET Framework (4.0) 11

Language environment 16

Library build -
-User library 21
-Firmware library 18

——————————————————————————————————————————————
Administrators can only install MULTIPROG® software in a PC; hence, the users has to start
up the PC with administrator’s login ID. The followings describe how to install the
MULTIPROG® and the other in the PC.

Note: If the PC is not running in “English” operating system, the user has to change the
language to “English” on the MULTIPROG software. To change the language
environment, see page 16.

PLC editor
- 4 -
 6F2S1904 (Rev. 1.21)

Installation of MULTIPROG
The software (MULTIPROG®) is provided for the user with a CD-ROM. There are folders on
the CD-ROM, and the user needs to execute “[Link]” in “1_MULTIPROG535_Buildxxx†”
folder on the CD-ROM. After that, installation screens are displayed on the PC. The user
should take the below steps in the screens:
 Click “Next” in Setup Wizard window (Figure 2.1-1).
 Confirm license agreement (Figure 2.1-2)
 Select a destination folder in the PC for the MULTIPROG (Figure 2.1-3)
 Start an installation (Figure 2.1-4)
 Check the installation processes (Figure 2.1-5)
 If succeeded, click “Finish” (Figure 2.1-6)

Revision number

Figure 2.1-1 MULTIPROG® Setup Wizard and installed folders

†Note:The folder name includes a software revision number. For example, a revision
number (574) is attached to its folder name.

Note: The user has to erase the old MULTIPROG5.35 one, when the new one has to be
installed in the PC. That is, if the user wishes to have the new (i.e., new Rev. 575)
in the PC, Uninstall the old one (i.e., old Rev. 574). For uninstalling, jump to
section 2.10.

PLC editor
- 5 -
 6F2S1904 (Rev. 1.21)

Check an agreement and click “Next”. The below screen appears during the
installation. It will take a few minutes.

Figure 2.1-2 License confirmation

Select a destination and click “Next” Figure 2.1-5 Installation progress screen

If being successful, the following screen

will appear, after that click “Finish”.

Figure 2.1-3 Selection of destination folder

Click “Install”

Figure 2.1-6 Installation completion screen

Figure 2.1-4 Commence of installation

PLC editor
- 6 -
 6F2S1904 (Rev. 1.21)

Installation of PPCE
The user has to install the software of PPCE in the PC. The user can find it in folder
“2_PPCE300_BE_PPC_eCLR”.

PPCE folder

Figure 2.2-1 PPCE folder on the CD-ROM

Run “PPCE300_BE_PPC_eCLR_3.[Link]”. The user has to take the below steps:

 Select “Accept”, and then click “Next”. (Figure 2.2-3)
 Determine a folder; and click “Next”. (Figure 2.2-4)
 Click a check box “Install Visual Studio / Visual C# Express Support”, and then click
“Next”. (Figure 2.2-5)
 Click “Install”†. It will take few minutes to complete. (Figure 2.2-6)
 If the installation is successful, a screen will appear; and then click “Finish”. (Figure
2.2-7)

Figure 2.2-2 Startup of PPCE installation

PLC editor
- 7 -
 6F2S1904 (Rev. 1.21)

Select “Accept”, and then click “Next”. Click “Install”. (It will take few minutes
for the installation to complete)

Figure 2.2-3 PPCE license agreement

Browse a folder; and click “Next”. Figure 2.2-6 Ready to install PPCE

The following screen will appear, and

then click “Finish”.

Figure 2.2-4 PPCE destination folder

Click a check box, and then click “Next”.

Figure 2.2-7 PPCE installation completed

Figure 2.2-5 Visual Studio for PPCE

PLC editor
- 8 -
 6F2S1904 (Rev. 1.21)

Installation of ARM
After the software of PPCE is installed in the PC, the user has to install the software of ARM
in the PC.

PPCE folder

Figure 2.3-1 ARM folder in the CD-ROM

Run “ARM_LE_GCC3_eCLR_3.[Link]” in folder “3_ARM_LE_GCC3_eCLR”.

 Select “Accept”, and then click “Next”. (Figure 2.3-3)
 Determine a folder; and click “Next”. (Figure 2.3-4)
 Click a check box “Install Visual Studio / Visual C# Express Support”, and then click
“Next”. (Figure 2.3-5)
 Click “Install”. It will take few minutes to complete. (Figure 2.3-6)
 If the installation is successful, a screen will appear; and then click “Finish”. (Figure
2.3-7)

Figure 2.3-2 Startup of ARM installation

PLC editor
- 9 -
 6F2S1904 (Rev. 1.21)

Select “Accept”, and then click “Next”. Click “Install”. (It will take few minutes
for the installation to complete)

Figure 2.3-3 ARM license agreement

Browse a folder; and click “Next”. Figure 2.3-6 Ready to install ARM

The following screen will appear, and

then click “Finish”.

Figure 2.3-4 ARM destination folder

Click a check box, and then click “Next”.

Figure 2.3-7 ARM installation completed

Figure 2.3-5 Visual Studio for ARM

PLC editor
- 10 -
 6F2S1904 (Rev. 1.21)

Installation of .NET Framework

If .NET Framework has not been installed in the PC, error messages (Figure 2.4-1) may
appear; hence, the user has to install “Microsoft .NET Framework3.5/4.0®” in the PC.

Figure 2.4-1 Error message of .NET Framework

The user can find it on the CD-ROM.

Figure 2.4-2 .NET Framework folders on the CD-ROM

To install it, run execute files for .NET Framework. Click a check box “I have read and accept
the license terms”; then click “Install”.

Figure 2.4-3 License terms of .NET Framework®

Note: If problems occurs during the installation of .NET Framework, contact user’s I.T.
system administrator.

PLC editor
- 11 -
 6F2S1904 (Rev. 1.21)

Software customization
The software (MULTIPROG®) has to be customized depending on the PC environment; hence,
the user has to execute “setup_patch_for_G2_x_x_x_x.exe”†, which is placed in “4_TOSHIBA”
folder on the CD-ROM.

PPCE folder

Figure 2.5-1 Toshiba folder in the CD-ROM

†Note: The CD-ROM revision number can be identified with “X_X_X_X” number of the
execute file name.

Revision number

Figure 2.5-2 How to identify CD-ROM revision number

Data of libraries and firmware is transferred to PC’s folders from the CD-ROM through
customization processes.
(i) Execution of Patch
Click “Next” and “Finish” (Figure 2.5-3 and Figure 2.5-4)
(ii) Installation of PLC software
Click “Next” and “Install” (Figure 2.5-5 to Figure 2.5-7)
(iii) Installation of firmware libraries
Click “Next” and “Install” (Figure 2.5-8 to Figure 2.5-10)
(iv) Installation of tools
Click “Next” and “Install” (Figure 2.5-11 to Figure 2.5-13)
(v) Installation of user libraries
Click “Next” and “Install” (Figure 2.5-14 to Figure 2.5-16)

PLC editor
- 12 -
 6F2S1904 (Rev. 1.21)

Click “Install” Click “Next”

Figure 2.5-3 Patch stated Figure 2.5-5 Installation of eCLR software

Click “Finish” Click “Install”

Figure 2.5-6 Progress of installer

Figure 2.5-4 End of Patch screened after the Click “Next”
end of Figure 2.5-16

Figure 2.5-7 End of eCLR installation

PLC editor
- 13 -
 6F2S1904 (Rev. 1.21)

Click “next” Click “Next”

Figure 2.5-8 Installation of firmware libraries Figure 2.5-11 Installation of tools

Click “Install” Click “Install”

Figure 2.5-12 Tools installation started

Figure 2.5-9 Firmware libraries installation Click “Install”
Click “Finish”

Figure 2.5-13 End of tools installation

Figure 2.5-10 End of firmware installed

PLC editor
- 14 -
 6F2S1904 (Rev. 1.21)

Click “Next”

Figure 2.5-14 Installation of user libraries

Click “Install”

Figure 2.5-15 User libraries installations

Click “Finish”

Figure 2.5-16 End of user libraries installation

PLC editor
- 15 -
 6F2S1904 (Rev. 1.21)

Setting PC language environment

If a PC is not running in “English” environment, the user should change the software language
to “English” environment. To change, go to “Options… ”→ “Extras drop down list.

Figure 2.6-1 MULTIPROG® startup screen

Figure 2.6-2 Language selection menu

Select “English” among language drop down lists, under the “General” tab.

Figure 2.6-3 Language selection from Option menu

PLC editor
- 16 -
 6F2S1904 (Rev. 1.21)

Software registration code

If the license waring is screened on the PC, the user shall enter the registration code, which is
printed on the license sheet that the user bought.

Figure 2.7-1 Warning about MULTIPROG® license

Figure 2.7-2 Keying registration code

Enter the registration code, and click “OK”.

Figure 2.7-3 Screen for registration code

PLC editor
- 17 -
 6F2S1904 (Rev. 1.21)

Preparation of firmware library

Samples of project file include the firmware library “G2EclrNatveFW”. The user can select a
sample when the user creates new project.

The samples are provided for respective IED models. Accordingly,

the user has to select it depending an IED model. To identify it, see
Chapter Connection and project setting: How to make the
connection between PC and IED (→p.26).

Project G2_sample MV_sample

Wizard

Template for Template for Template for

eCLREasySim IPC_40 eCLR

Template for Template for Template for

ProConOS DE ProConOS INT ProConOS ARM
CE

Firmware library provided from

Toshiba

Icon to view the libraries provide

in user’s project file

Figure 2.8-1 Firmware libraries included in sample files

PLC editor
- 18 -
 6F2S1904 (Rev. 1.21)

The user can select a function block (FB) of the firmware libraries.

Select “G2EclrNatveFW” with Edit Wizard

Figure 2.8-2 FB lists in G2EclrNatveFW

PLC editor
- 19 -
 6F2S1904 (Rev. 1.21)

If the user lost firmware libraries or requires other libraries† in a user’s project file, import
them by “Include”.
 Go to “Project Tree Window”, select “Libraries”; right click at “Insert”.
 Select “Firmware Library”.
 Select a library†.

Provided by Toshiba

Figure 2.8-3 Insert another firmware libraries for users’ project file

†Note:Figure 2.8-3 is one of examples. The BIT_UTIL or other libraries can be provided
from the MULTIPROG®. For the information about libraries, see its help menus.

Tip: See Appendix: Firmware libraries in order that the ones are imported properly
(seep. 87).

PLC editor
- 20 -
 6F2S1904 (Rev. 1.21)

Preparation of user library

The sample project file—that has been selected in response to an IED model for new project—
also includes user libraries. The user can view them in the project tree.

For example, the G2_sample was selected (see Figure 2.8-1).

Project G2_sample MV_sample

Wizard

Template for Template for Template for

eCLREasySim IPC_40 eCLR

Template for Template for Template for

ProConOS DE ProConOS INT ProConOS ARM
CE

G2 series’ User libraries are provided

by Toshiba

Click to see user libraries in user’s

project file

Figure 2.9-1 User libraries in the project tree

Note: Another MV_sample also include User libraries. They are different depending the
selected IED model. For more detail about the libraries, see Appendix: User
libraries (p. 89)

PLC editor
- 21 -
 6F2S1904 (Rev. 1.21)

The user can select a function block (FB) of the user libraries.

Select “G2lib______” with Edit Wizard

Figure 2.9-2 List of FBs of G2lib_240001 [Keyinput]

PLC editor
- 22 -
 6F2S1904 (Rev. 1.21)

If the user lost user the user library in the user’s project file, import them by “Include”.
 Go to “Project Tree Window”, select “Libraries”; right click at “Insert”.
 Select “User Library”.
 Select file “G2lib_200B01(BIO_slot1)” or others.

Figure 2.9-3 Insert User libraries for project file

PLC editor
- 23 -
 6F2S1904 (Rev. 1.21)

Update of PLC software

The user should remove the software (MULTIPROG5.35) from a PC when the user wishes to
update that of new version. Use ‘Uninstall a program” through the Window setting screen (i.e.,
Control panel) to erase the software. After that, the user is able to reinstall the new one in the
PC (see Chapter 2.1)

PLC editor
- 24 -
 6F2S1904 (Rev. 1.21)

3 Connection and project setting

Contents Pages Pages
Build settings for project file 34 CPU and PLC settings 31
-eCLR (Core 3.0.6) setting 35 -Set of CPU type 32
-eCLR (Core 3.0.2) setting 35 -Set of IP address 35
-Task setting 36 -Set of PLC 31
-Event and priority

Download of project data to IED 39 How to connect between PC and IED 26

-Download option 39 -Connection for IED (G2) 26
-Download operation 40 -Connection for IED (MV) 26
-Start to PLC after the download 42 -IED connection tool 27
-Stopping PLC before the download 39 -TPC_SERIAL_IF.exe 27
-USB speed setting 28
Upload of project data to PC 43
-Type of project file uploaded 43 Save project file 44
-Upload operation 43

PLC editor
- 25 -
 6F2S1904 (Rev. 1.21)

How to make the connection between PC and IED

The user can connect a PC with an IED for the PLC. There are two methods for the connection:
LAN or USB. Information is described in separate GR200 series instruction manual. See
Chapter Technical description: Signal processing and communication module.

(i) Connection with G2 model

Figure 3.1-1 shows the connection with a G2 IED via USB cable or LAN cable.

IED

LAN Cable

Personal Computer

USB Cable

Figure 3.1-1 USB or LAN cable connection for G2 model

(ii) Connection with MV model

Figure 3.1-2 shows the connection with a MV model using a USB or LAN cable.

IED

LAN Cable
Personal Computer

USB Cable

Figure 3.1-2 USB or LAN cable connection for MV model

PLC editor
- 26 -
 6F2S1904 (Rev. 1.21)

(iii) USB connection tool

Software “TPC_SERIAL_IF” provides serial USB connection tool for the PC. The tool provides
“Activity window (Figure 3.1-3)”, so that the user can watch the USB communication state.
The PLC software can run, after the “TPC_SERIAL_IF.exe” is executed.

Table 3.1-1 Folder for “TPC_SERIAL_IF.exe”

Windows
(iv) Destination
OS

8.1,10 C:¥Program Files(x86)¥KW-Software¥MULTIPROG 5.35 Build xxx¥G2_tool

Note: The number “xxx” is MULTIPROG® software revision number (→p. 5).

Figure 3.1-3 USB state (Waiting is shown in the left image)

Note: When the USB is applied, the user has to set an IP address of USB port number in
a PLC project file. In order to identify, open the Device manager (Figure 3.1-4). In
the figure (example), COM5 (USB port) is added in the PC so the user has to set
"[Link]" in the PLC project (see Figure 3.3-5).

USB port is COM5.

Figure 3.1-4 USB shown in Device manager (Example. PC windows screen)

PLC editor
- 27 -
 6F2S1904 (Rev. 1.21)

(v) USB speed setting

The user can set a communication speed either 115.2kbps or 921.6kbp†. Figure 3.1-5 shows a
menu for the speed choice. The user has to check to set the same speed in the IED‡ and the
PC.

Figure 3.1-5 Set of communication speed for the USB

†Note:The user can select either when an IED model is running with ARM CPU. The
user can check if the ARM CPU is mounted in the IED with the CPU code (see
Figure 3.1-6).
If an IED model is running with PowerPC CPU (e300), it is fixed in 115kbps.

Positions
--
7 S G T E F U 9 V
CPU code: (IED model)
- _ _ ? _ - _ _ _ - _ _ 1: PowerPC e300 (G2)
2: PowerPC e300 (G2)
3: ARM (G2)
5: ARM (MV)

GR_200- --

GR_200
TOSHIBA ENERGY SYSTEMS & SOLUTIONS CORPORATION

--

Figure 3.1-6 How to identify ARM or PowerPC using CPU code (and IED model)

PLC editor
- 28 -
 6F2S1904 (Rev. 1.21)

PLC project file to create

A project file is required if the user wishes to customized PLC functions. To create a PLC project
file, click “New project” with File menu bar (Figure 3.2-1).

Figure 3.2-1 New project selected in the menu

(i) To create a project

Select “File”, and click “New Project”. After that, click a sample project. (Figure 3.2-2)

Project G2_sample MV_sample

Wizard

Template for Template for Template for

eCLREasySim IPC_40 eCLR

Template for Template for Template for

ProConOS DE ProConOS INT ProConOS ARM
The user has to select either
CE depending the IED model. For example,
select “G2_sample”, if required. Figure 2.8-1 illustrates which has
to be selected.

Figure 3.2-2 Screen for New Project

Note: Samples (templates) are provided for new projects; hence, the user should create
the new one using the sample (template).

PLC editor
- 29 -
 6F2S1904 (Rev. 1.21)

(ii) To open the project to have been saved in PC

To open the project in the PC, select “File”, and click “Open Project / Unzip Project…” and select
it (Figure 3.2-3).

Figure 3.2-3 Selection of “Open Project/Unzip Project”

Tip: Icon operation

The user can also open it by clicking an icon “Open Project / Unzip Project”
with the Icon on Tool bar (Figure 3.2-4); following which, the user can see it
on the PC.

Figure 3.2-4 Open Project / Unzip Project button

PLC editor
- 30 -
 6F2S1904 (Rev. 1.21)

Editing PLC project file

When creating a PLC project, the user can do by editing the project file. The project file includes
an IP address to connect with the IED.

(i) PLC type to set

The user has to set a PLC type in the PLC project.
1) Jump to “Project Tree Window”.
2) Move to “Physical Hardware” (a root of a tree)
3) Go to the level 2 of the Physical Hardware tree, and right click it.
4) Right click “Properties”.
5) Select a PLC type1.

Project tree window

Physical Hardware tree (root)

Level 2 of Physical Hardware tree

Properties

PLC type

Figure 3.3-1 Set of PLC type

1Note: The PLC type can be found by seeing the ordering code. See Figure 3.3-3.

PLC editor
- 31 -
 6F2S1904 (Rev. 1.21)

(ii) Processor type to set

The user has to set a processor type in the PLC project.
1) Jump to “Project Tree Window”.
2) Move to “Physical Hardware” (a root of a tree).
3) Go to the level 3 of the Project Hardware tree, and right click it.
4) Right click “Properties”.
5) Select a Processor Type1 using the drop down list.

Project tree window

Physical Hardware tree (root)

Level 3 of Physical Hardware tree

Properties

Processor type

Figure 3.3-2 Set of processor

1Note: The Processor type can be found by seeing the ordering code. See Figure 3.3-3.

PLC editor
- 32 -
 6F2S1904 (Rev. 1.21)

Positions
--
7 S G T E F U 9 V
PLC type (IED model)
- _ _ ? _ - _ _ _ - _ _ 1: eCLR(Core 3.0.2) (G2)
2: eCLR(Core 3.0.2) (G2)
3: eCLR(Core 3.0.6) (G2)
5: eCLR(Core 3.0.6) (MV)

Processer (IED model)

1: PPCE300_BE_PPC (G2)
2: PPCE300_BE_PPC (G2)
3: ARM_LE_GCC3 (G2)
GR_200- -- 5: ARM_LE_GCC3 (MV)

GR_200
TOSHIBA ENERGY SYSTEMS & SOLUTIONS CORPORATION

--

Figure 3.3-3 PLC type and processer identifier

PLC editor
- 33 -
 6F2S1904 (Rev. 1.21)

(iii) Resource setting

The user has to set resources (IP address and PLC type) in the PLC project.
1) Jump to “Project Tree Window”.
2) Move to “Physical Hardware tree (root)”
3) Go to Level 3 of the Project Hardware tree, and right click it.
4) Right click “Properties”.

Project tree window

Physical Hardware tree (root)

Level 3 of Physical Hardware tree

Properties

Resource settings

Figure 3.3-4 Set of resources

PLC editor
- 34 -
 6F2S1904 (Rev. 1.21)

Resource settings

IP address1

PLC type version2

Figure 3.3-5 How to set Build version

1Note: The user has to enter the IP network which to be set in the IED. If the PLC editor
is connected with the IED through a USB cable (see Figure 3.1-1), the user has to
enter the IP network addres which to be assigned for the USB port of the PC. For
example, if the PC has a USB with COM5, enter "127.0.1. 5" in the PLC project.
The "[Link] " is defined by the manufacture. The USB port (e.g., COM5) can
be found in the Device manager (Figure 3.1-4).
2Note: The PLC type version can be found by seeing the IED ordering code. See Figure
3.3-3.

PLC editor
- 35 -
 6F2S1904 (Rev. 1.21)

(iv) Task setting

A PLC project has task types, and one of types was set for the PLC project. Normally, “EVENT
(default)” is used in the PLC project, but the user can change it if required (see Figure 3.3-6).
Table 3.3-1 shows types of the PLC project task.

Project tree window

Physical Hardware tree (root)

Task “EVENTS” at Level5

Properties

Task type setting

Figure 3.3-6 Set of task

Table 3.3-1 Types of tasks

Types Usages Meanings
EVENT Normal Conventional task (Default setting)
Cyclic execution task, which is managed by “eCLR”. The smallest
CYCLE Not used
cycle should be equal to a special sampling period (SSP).
DEFAULT Not used Execution task runs during idle time.
SYSTEM Not used System event task runs during outage, data-download, etc.

PLC editor
- 36 -
 6F2S1904 (Rev. 1.21)

In case of the “Event”, the user can select a kind of that, as shown in Table 3.3-2.
Table 3.3-2 Event kinds and meanings
Processor priority values‡
Kinds Meanings
ARM_LE_GCC3 PPCE300_BE_PPC
Main1† 0 0 An event is triggered before SSP task
Main2† 0 0 An event is triggered after SSP task
Main3† 0 0 An event is triggered after SSP task
5ms 1 1 An event is triggered every periodic task (every 5ms).
10ms 2 1 An event is triggered every periodic task (every 10ms).
100ms 3 1 An event is triggered every periodic task (every 100ms).
200ms 4 1 An event is triggered every periodic task (every 200ms).
†Note: The processor requires more computation times when “Main1”, “Main2” or
“Main3” is set. Thus, these selections are not recommend.
‡Note:Priority value “0” is set when “Main*” is set. A greater value is set when except
“Main” is selected. The user can check it using the Task setting screen (→ p.64).

PLC editor
- 37 -
 6F2S1904 (Rev. 1.21)

Build
The libraries have to be built in the PLC editor. In order to include those in the PLC editor,
compile those using “Build menu”, as shown in Figure 3.4-1.

Figure 3.4-1 Compile libraries with “Build” menu (or press F9 key)

When libraries are compiled, the message are shown on the “Build” tab.

Figure 3.4-2 Message for library build

PLC editor
- 38 -
 6F2S1904 (Rev. 1.21)

PLC data download to IED

First, the user has to stop the PLC project running in the IED, and then select download
options in the PLC editor. After that, the user can download the PLC data in the IED.

(i) How to download data

In order to download a PLC data, the user shall stop the PLC project running in the IED.
Figure 3.5-1 illustrates how to stop the PLC project in the IED.

1. Select Project control

2. Click “Stop” button

Figure 3.5-1 How to stop the PLC project before the download

PLC editor
- 39 -
 6F2S1904 (Rev. 1.21)

When the IED has stopped, push “More” button to set options. At a later date, the user can
retrieve the PLC project file from the IED, and the user can edit it on the PC.

Note: the user might as well tick all boxes.

If the user cannot tick boxes in The user shall tick both boxes “Permanent as Bootproject” and

“Download Option”, see Figure “Include Sources” in “Download Options”; consequently, PLC

3.5-4. data (IMG file) is later. The PLC data to be recorded in the

IED are uploaded to the PC (see Chapter 3.6).

Figure 3.5-2 Check boxes for Include source

Push “Download” button, and then PLC data is going to be downloaded in the IED. Note that
long time might be required, if the options are included. This is because; PLC source code will
be also downloaded for the IED (i.e., “Include soured” was set in Figure 3.5-2).

Figure 3.5-3 Download button

PLC editor
- 40 -
 6F2S1904 (Rev. 1.21)

Figure 3.5-4 shows the options’ menu for Debugging. Figure 3.5-2 can be screened if the tick of
“Use master setting…” is .removed.

Figure 3.5-4 Checkbox “Use muster settings of download options”

PLC editor
- 41 -
 6F2S1904 (Rev. 1.21)

(ii) How to start the PLC project with the downloaded data
In order to start the PLC with the downloaded data, select a start type† from the type lists,
and then start the PLC in the IED.

Figure 3.5-5 Start button

Table 3.5-1 Start-up types in PLC function

PLC start-up type Description
Cold (Cold Start) The user can start the PLC function from the initial process.
Warm (Warm Start) The user can start the PLC function without the initial process.
The user can start the PLC function from the point where the PLC
Hot (Hot Start)
function has stopped before.
Reset the PLC function. Note that the PLC function cannot restart
Reset
if the PLC data is not downloaded again.
†Note:The user is recommended to select “Cold (Cold Start)”.

PLC editor
- 42 -
 6F2S1904 (Rev. 1.21)

How to upload PLC data for the PC

Follow the below steps when the user wishes to get a PLC project file in the IED.
1. Click “Cold”.
2. Click “Upload”
3. Click “Project Source”.
4. Select a folder to save the project file data in the PC.

1. Cold

2. Upload
3. Upload

Figure 3.6-1 Upload and Source buttons

Note: The size of the project file influences the PC operation time for saving the file in
the PC. Thus, the user can select either compressed or uncompressed type for
that, as shown in Table 3.6-1.
Table 3.6-1 Types of project file
File type filename extension File structure Remark
“****.mwt” to be stored in
Normal .mwt
“****/” folder
It is a compressed file; it will
Compressed .zwt “****.zwt” be uncompressed when the
project file is viewed.

PLC editor
- 43 -
 6F2S1904 (Rev. 1.21)

How to save PLC project file

The user can save a project file in the PC. Select “File” with Menu bar, and click “Save Project
As / Zip project as…”

Selection of save

Selection of file type

Zip options

Do not place marks (✔) in

Zip option boxes.

Figure 3.7-1 Save project As / Zip Project As

Note: Figure 3.7-1 shows that either file types to be saved in the PC. The user has to
select either normal (*.mwt) or compressed (*.zwt) type.

PLC editor
- 44 -
 6F2S1904 (Rev. 1.21)

4 Debug of PLC data

Contents Pages Pages
Debug of PLC project file data 46 PLC data error information 47

——————————————————————————————————————————————
The user can debug a PLC project file data with PLC debugger. The IED has automatic
supervision function†; hence PLC errors can be detected by the supervision function.

†Note: The IED can reports PLC error information on the LCD. See the IED instruction
manual separately. See Chapter Automatic supervision: Supervision of data in
PLC function.

PLC editor
- 45 -
 6F2S1904 (Rev. 1.21)

Debug of PLC project file data

The user can execute the debug monitor function in the PLC editor, so the user can monitor
and examine the data in the PLC project file when the PLC is running in the IED.

Figure 4.1-1 Icon of PLC debug monitor function

Note: The user is not able to fix or modify the data of PLC project file when the debugger
is running. In order to edit or change the PLC data, stop the debugger to edit.
After editing or changing the PLC data, click “Debug” button again.

PLC editor
- 46 -
 6F2S1904 (Rev. 1.21)

PLC data error information

The automatic supervision function can report error information when an error occurs in the
PLC function. The diagnostic is provided on the LCD screen (see Figure 4.2-1), and several
error codes and detailed contents are given (see Table 4.2-1). When a PLC error is detected,
the error information is screened at the first row and column. If errors are detected in the IED
at the same time, those information are given with one code; it is a united code. That is, if two
errors (e.g., 0x00000002 and 0x00000004) occur at the same time, the sum value “0x00000006”
will be given for the diagnostic.

Table 4.2-1 Error code and its information

Error code Content of the error code
0x00000001 No PLC data exists in the IED.
0x00000002 Error in input data (DIN function)1
0x00000004 Error in output data (DOUT function) 2
0x00000008 Time over because of the excess task priority (→p. 37)
0x00000010 PLC is stopping by the operation of PLC editor (→ p.39)
…. …..

PLC data error 1/1

10:48
[Minor error]

[00000006] [00000000]
[00000000] [00000000]
[00000000] [00000000]

PLC error code‡

Figure 4.2-1 Error code at 1st row and 1st column on the monitoring sub-menu
1Note: It is mentioning that the PLC function fails to input the data from IED memories.
2Note: It is mentioning that the PLC function fails to output the data to IED memories

PLC editor
- 47 -
 6F2S1904 (Rev. 1.21)

5 Information of firmware functions

Contents Pages Pages
Basic functions 53 Help menus 49
-Bitwise Boolean 53
-Bit-string 53
-Arithmetic 53 Numeric literals 51
-Numerical 53 -Integer literals 51
-Selection 53 -Integer literals with fixed data type 51
-Comparison 53 -Real literals 51
-Type conversion 53 -Real literals with exponent 51
-Bitwise Boolean 53 -Long Real literals 51
-Long Real literals with exponent 51
-Base 2 literals 51
Bit operation functions 54 -Base 8 literals 51
-Test of a bit 54 -Base 16 literals 51
-Get of a character 54 -Boolean “FALSE and TRUE” 51
-Get of LSB 54 -Boolean “0 and 1” 51
-Get of MSB 54
-Invert of a bit 54
-Check of parities 54
-Reset of a bit 54

Elementary data types 50

-BOOL 50
-SINT 50
-INT 50
-DINT 50
-USINT 50
-UINT 50
-UDINT 50
-REAL 50
-LREAL 50
-TIME 50

Function blocks 52
-Flip Flop 52
-Edge detector 52
-Counter 52
-Timer 52

PLC editor
- 48 -
 6F2S1904 (Rev. 1.21)

About PLC editor

Information of the PLC function can be found on PLC help menus. Jump to the PLC help
menus to check detailed information.

Figure 5.1-1 Help menu in PLC software

Figure 5.1-2 About Function blocks

PLC editor
- 49 -
 6F2S1904 (Rev. 1.21)

Elementary data type

Table 5.2-1 shows elementary data types of the PLC firmware.
Table 5.2-1 Data types and descriptions
Default
Data type Description Size Range
and initial
BOOL Boolean 1 Either 0 or 1 0
SINT Short integer 8 −128 to 127 0
INT Integer 16 −32,768 to 32,767 0
DINT Double integer 32 −2,147,483,648 up to 2,147,483,647 0
Unsigned
USINT 8 0 up to 255 0
short integer
Unsigned
UINT 16 0 up to 65,535 0
integer
Unsigned
UDINT 32 0 up to 4,294,967,295 0
double integer
−3.402823466 E+38 (50pprox.. 7 digits) up
to
−1.175494351 E−38 (50pprox.. 7 digits)

REAL Real numbers 32 and 0.0

+1.175494351 E−38 (50pprox.. 7 digits) up

to
+3.402823466 E+38 (50pprox.. 7 digits)
−1.798 E+308 (50pprox.. 15 digits) up to
−2.225 E−308 (50pprox.. 15 digits)
Long real
LREAL 64 and 0.0
numbers
+2.225 E−308 (50pprox.. 15 digits) up to
+1.798 E+308 (50pprox.. 15 digits)
TIME Duration 32 0 up to 4,294,967,295 t#0s
Bit string of 0 up to 255
BYTE 8 0
length 8 (16#00 ... 16#FF)
Bit string of 0 up to 65,535
WORD 16 0
length 16 (16#00...16#FFFF)
Bit string of 0 up to 4,294,967,295
DWORD 32 0
length 32 (16#00....16#FFFFFFFF)

PLC editor
- 50 -
 6F2S1904 (Rev. 1.21)

Numeric literals
Table 5.3-1 shows the literal types for numerical data.
Table 5.3-1 Numerical literals and ranges
Type Examples
Integer literals -12 0 123_456 +986
Integer literals with fixed data type [Data Type]#[base]#Number
Real literals -12.0 0.0 0.4560 3.14159_26
Real literals with exponent -1.34E-12 -1.34e-12 1.0E+6
Long Real literals LREAL#-12.0
Long Real literals with exponent LREAL#2.3E-89
Base 2 literals INT#2#1111_1111
Base 8 literals INT#8#377
Base 16 literals INT#16#FF SINT#16#ff
Boolean FALSE and TRUE FALSE TRUE
Boolean 0 and 1 0,1
Time TIME#100ms

PLC editor
- 51 -
 6F2S1904 (Rev. 1.21)

Flip flop, edge detector, counter and timer function blocks

Table 5.4-1 shows function blocks in the PLC firmware FBs.
Table 5.4-1 Function blocks
Function Function block Short description
SR Set dominant
Flip Flop
RS Reset dominant
F_TRIG Falling edge detector
Edge detector
R_TRIG Rising edge detector
CTU Up-counter
Counter CTD Down-counter
CTUD Up-down-counter
TP Pulse
Timer TON On-delay timer
TOF Off-delay timer

PLC editor
- 52 -
 6F2S1904 (Rev. 1.21)

Basic functions
Table 5.5-1 shows basic functions in PLC firmware functions.
Table 5.5-1 Basic function
Function Function Short description
AND AND connection
NOT Complement
Bitwise Boolean functions
OR OR connection
XOR XOR connection
ROL Rotate left
ROR Rotate right
Bit-string functions
SHL Shift left
SHR Shift right
ADD Addition of ANY_NUM
DIV Divisor of ANY_NUM
EXPT Exponentiation
MOD Modulo division
Arithmetic functions
MOVE Assignment
MUL Multiplier for ANY_NUM
NEG Double complement
SUB Subtractor of ANY_NUM
ABS Absolute value
ACOS Arc cosine
ASIN Arc sine
ATAN Arc tangent
COS Cosine
Numerical functions EXP Exponent
LN Natural logarithm
LOG Logarithm to the base of 10
SIN Sine
SQRT Square root
TAN Tangent
LIMIT Limitation
MAX Maximum
Selection functions
MIN Minimum
SEL Binary selection
EQ Comparison: =
GE Comparison: >=
GT Comparison: >
Comparison functions
LE Comparison: <=
LT Comparison: <
NE Comparison: <>
Type conversion functions *_TO_** Type conversion from * to **

PLC editor
- 53 -
 6F2S1904 (Rev. 1.21)

Bit operation functions

Table 5.6-1 shows the function of bit operation.
Table 5.6-1 Bit operation function
Function Short description
BIT_TEST reads the value of a single bit in a bit string
GET_CHAR extracts one character out of a string
GET_LSB reads the value of the least significant BYTE of a bit string
GET_MSB reads the value of the most significant BYTE of a bit string
I_BIT_IN_* inverts a single bit in a bit string
PARITY_* checks if the number of set bits is even or odd
R_BIT_IN_* resets a single bit in a bit string
S_BIT_IN_* sets a single bit in a bit string
SET_LSB writes a value on the least significant BYTE of a bit string
SET_MSB writes a value on the most significant BYTE of a bit string
SWAP exchanges the most and the least significant BYTE of a bit string
*Note: To execute this function, the user should install the “BIT_UTIL” library (→p. 20).

PLC editor
- 54 -
 6F2S1904 (Rev. 1.21)

6 How to operate PLC editor

Contents Pages Pages
Add a logic 62 Open a worksheet 56
Add new task 63
Add a variable value in the worksheet 59 PLC driver setting 72

Connect a value with function block 60 Timer setting 83

Connect a function with another one 61
Worksheet operation 56
DIN**** setting 68
DOUT**** setting 70

Exporting projects 78

Importing projects 80
Insert function blocks 57

PLC editor
- 55 -
 6F2S1904 (Rev. 1.21)

Worksheet operation
(i) How to open a worksheet
Follow the steps below to open a worksheet:
1. Click “Logical POUs” in the “Project Tree Window”; then, select a “POU.
2. Right click the “POU*”; click “Open Worksheet”. Default ADD function will be inserted
as shown in Figure 6.1-2. The user can delete it if unrequired.

Worksheet area

Right click

Default ADD Function

Figure 6.1-1 Open the worksheet screen

PLC editor
- 56 -
 6F2S1904 (Rev. 1.21)

Default ADD function added

Figure 6.1-2 Default ADD inserted

(ii) How to insert function blocks (FB) or functions on Worksheet

Click “View” on the “Menu bar”; and select “Edit Wizard”. The “Edit Wizard” appears on the
right as shown in Figure 6.1-3.

Figure 6.1-3 Edit Wizard screened

Select a required function on “Favorites” group (Figure 6.1-4); then, drag and drop the required
one on the worksheet for preferred location.

PLC editor
- 57 -
 6F2S1904 (Rev. 1.21)

Drag

Drop

Figure 6.1-4 FB inserted on the worksheet

PLC editor
- 58 -
 6F2S1904 (Rev. 1.21)

The “Group” is made of user libraries. The user can use any libraries. The appendix for the
user libraries. A sample project file includes libraries (→p. 29).
Tips: See Appendix B User libraries (→p. 89)

For example, when the user wishes to use a binary input circuit (BI1) at slot #1 (Table B.1-2),
the user can use it by selecting “S1_BI1” from the user library.

(iii) How to add a variable

Select “Variable” (or press F5) to add a variable on the worksheet. The user can set a value
(with Name, Data Type, Usage and so on) for it using “Variable Properties”, as shown in Figure
6.1-6. Table 6.1-1 shows data types for the variable.

Right click

Figure 6.1-5 Adding a variable on the worksheet

PLC editor
- 59 -
 6F2S1904 (Rev. 1.21)

Table 6.1-1 Data type

Data type Data type name Data type name in the PLC
0x00 Boolean UDINT
0x20 Signed int8 SINT
0x21 Signed int16 INT
0x22 Signed int32 DINT
0x30 Unsigned int8 USINT
0x31 Unsigned int16 UINT
0x32 Unsigned int32 UDINT
0x42 Real32 REAL
0x43 Real64 LREAL
0x8X† Bit BOOL
†Note: When Bit type is used, its 16-bit area is reserved in the IED memory. The user
can set it in Bit type (X：0x0 to 0xF); “X” is used to designate its offset.

Figure 6.1-6 Variable Properties window

(iv) How to link a variable with a function

Left click and hold the mouse button on a variable terminal point and drag to a function block
at the terminal point to connect the both, as shown in Figure 6.1-7.

PLC editor
- 60 -
 6F2S1904 (Rev. 1.21)

Figure 6.1-7 Connection between a variable and a function

(v) How to connect a function to another function

Functions are connected using FBD toolbar, as shown in Figure 6.1-8.

FBD Toolbar

Figure 6.1-8 Connecting function blocks

“Objects” drop down list allows that the user can insert a comment, connector, label /
jump, return, edit variable, duplicate FP and toggle negation of FP are done using on the menu
bar or using the icons available on the FBD toolbar.

PLC editor
- 61 -
 6F2S1904 (Rev. 1.21)

(vi) How to add a logic

To add a logic in Logical POUs, follow the steps as below:
1. Right click “logical POUs” in the project tree window, and select “Insert->Program”.
2. Enter a Name of the worksheet in “Insert” window; then, click “OK”.
3. A logic element is added in the project tree.

Figure 6.1-9 “PROG2” logic added in Logical POUs

PLC editor
- 62 -
 6F2S1904 (Rev. 1.21)

(vii) How to add new task

To add a task (for example, named “Task2”) for Physical Hardware tree, the user should follow
the steps as shown in Figure 6.1-11.
1. Jump to the Project Tree Window.
2. Go to Physical Hardware (root of a tree).
3. Click “Tasks” (at the level 4 of the Physical Hardware tree).
4. Click “Insert” to add a new Task.
5. Enter a task name; then, select a type1. After that, click “OK”.
6. Select an event type and a priority.
7. After that, the “Task2” is ready (Figure 6.1-10).

1Note: For the information about a task, a type, a kind, and

a priority, see Table 3.3-1 (→p. 37).
2Note: Table 3.3-2 shows the value of the task priority.

Figure 6.1-10 “Task2 (example)” added at Physical Hardware tree

PLC editor
- 63 -
 6F2S1904 (Rev. 1.21)

 
 (e.g., Task2)


 1 

Figure 6.1-11 Adding new Task

PLC editor
- 64 -
 6F2S1904 (Rev. 1.21)

Adding a logic in the “Task2” task

1. Right click on the “Task2”, for which a logic will be added. (Figure 6.1-13).
2. Select “InsertProgram”.
3. Enter a name “logic2 (for example)” at “Program instance” in Insert window, and set a
program type” for the “logic2”.
4. The logic (e.g., name “logic2”, PROG2 type) is added in the Task2.
5. To add another login in the Task2, repeat the above steps (). After that, “logic3”
is added on the Task2.
6. Drag and drop the Logic element to change the execution sequence. Figure 6.1-12 shows
an example where the “logic2” is dragged, after which it is dropped over the “logic3”.

Drag logic2 and

Drop it

Figure 6.1-12 Positions of “logic2” and “logic3” changed by Drag and drop

PLC editor
- 65 -
 6F2S1904 (Rev. 1.21)

Figure 6.1-13 How to insert logics on the “Task2”

PLC editor
- 66 -
 6F2S1904 (Rev. 1.21)

Move a logic to another task

The user can move a logic into another task as shown in Figure 6.1-14 and Figure 6.1-15.

Drag logic 2 and

drop it

Figure 6.1-14 Moving logic to another task

Figure 6.1-15 Logic moved

PLC editor
- 67 -
 6F2S1904 (Rev. 1.21)

Function blocks of Firmware library to be set

The firmware library includes DIN and DOUT function blocks (FBs) in order to import and
export signals in the PLC. Those FBs have some features and properties. The user has to
include them in the PLC project (→p. 18).

(i) “DIN_****” setting

Import/export of FB “DIN_****” data
FBs “DIN_****” are used to import a signal in the PLC. For example, a FB “DIN_BOOL” can
import the information of the 1-bit type signal.
Table 6.2-1 FB “DIN_****” import properties†
FB name Input property
DIN_BOOL Input data of 1-bit type
DIN_DINT Input data of integer 32-bits type
DIN_INT Input data of integer 16-bits type
DIN_SINT Input data of integer 8-bits type
DIN_UDINT Input data of unsigned integer 32-bits type
DIN_UINT Input data of unsigned integer 16-bits type
DIN_USINT Input data of unsigned integer 8-bits type
DIN_LREAL Input data of double floating-point 64-bits type
DIN_REAL Input data of floating-point32-bits type
†Note:Table 6.1-1 shows the data types of DIN_**** FBs.

Import of FB “DIN_****” attribution

Figure 6.2-1 shows that the “DIN_BOOL” works with a signal including several parameters.
It will an output (1-bit type data) if the signal is inputted in the DIN_BOOL. The DIN_BOOL
has several attributes—FID, DTYPE, DID, DO, ST, and allows to works in accordance with
the attributes (see Table 6.2-2).

Figure 6.2-1 Signal importation by FB “DIN_BOOL”

Table 6.2-2 PLC parameters and others in FBs “DIN_****”

Parameter Attribute Data type Contents
FID IN UDINT Function ID (16-bits) with instance number (8bits)
DTYPE IN DINT Data type (8-bits) of the element ID
Group ID (16-bits) and Attribute type (16-bits) of the element
DID IN UDINT
ID
DO OUT ANY_TYPE depends on _****
True: Data ID is valid
ST OUT BOOL
False: Data ID is invalid

PLC editor
- 68 -
 6F2S1904 (Rev. 1.21)

Check of FB “DIN_*****” configuration

The user can check a DIN FB configuration.
1 Run the PLC, which the user has configured.
2 Execute the PLC debugging function (→p. 46).
3 Check the ST value in the DIN FB. When “1” is yielded at ST, the DIN FB
configuration has been checked successfully (Figure 6.2-2). When “0” is yielded, it has
not been checked successfully (Figure 6.2-3).

Figure 6.2-2 When True (1) is observed at ST, the DIN FB is configured successfully

Figure 6.2-3 When False (0) is observed at ST, the DIN FB is configured unsuccessfully

PLC editor
- 69 -
 6F2S1904 (Rev. 1.21)

(ii) “DOUT_****” setting

FBs “DOUT_****” are provided to check a PLC signal.

Export in “DOUT_****” data

PLC data is inputted in FB “DOUT_****”, and the FB “DOUT_****” outputs its PLC data. The
output destination (i.e., connecting point) is also set in the FB “DOUT_****”. Accordingly, the
PLC data is outputted for that connecting point. If a connecting point has been set in the FB
“DOUT_****”, that connecting point shall not be used in the other FBs at the same time.

For example, FB “DOUT_BOOL” has an input signal, and generates an output 1-bit signal:
“True(1)” or “False(0)” state. Table 6.2-3 lists “DOUT_****” FBs.
Table 6.2-3 Data export in FBs “DOUT_****”
FB name Output property
DOUT_BOOL Data export in bit type
DOUT_DINT Integer data export in 32 bits type
DOUT_INT Integer data export in 16 bits type
DOUT_SINT Integer data export in 8 bits type
DOUT_UDINT Unsigned integer data export in 32 bits type
DOUT_UINT Unsigned integer data export in 16 bits type
DOUT_USINT Unsigned integer data export in 8 bits type
DOUT_LREAL Double floating-point data export
DOUT_REAL Floating-point data export
†Note: The “DOUT_****” data type is shown in Table 6.1-1.

Import of in FB “DOUT_****” attribute

Figure 6.2-4 shows that a FB “DOUT_BOOL” can obtain a signal including several attributes.
The FB “DOUT_BOOL” will generate a check output at ST (BOOL type). Figure 6.2-4 shows
its parameters and attributes.

Figure 6.2-4 Data export in FB “DOUT_BOOL” (e.g. DataID: 200B05-31-020e-e11d)

Table 6.2-4 Parameters and others in FBs “DOUT_****”

Parameter Attribute Data type Contents
FID IN UDINT Function ID (16-bits) with instance number (8bits)
DTYPE IN DINT Data type (8-bits) of the element ID
Group ID (16-bits) and Attribute type (16-bits) of the element
DID IN UDINT
ID
DI IN ANY_TYPE depends on _****
True: Data ID is valid
ST OUT BOOL
False: Data ID is invalid

PLC editor
- 70 -
 6F2S1904 (Rev. 1.21)

Check of FB “DOUT_****” configuration

The user can check the configuration of the DOUT FB by following the steps below:
1 Run the PLC, which the user has configured.
2 Execute the PLC debugging function (→p. 46).
3 Check the ST value in the DOUT FB. When “1” is yielded at ST, the DOUT
configuration has been checked successfully (Figure 6.3-5). When “0” is yielded, it has
not been checked successfully (Figure 6.3-6).

Figure 6.2-5 When True (1) is observed at ST, the DIN FB is configured successfully

Figure 6.2-6 When False (0) is observed at ST, the DIN FB is configured unsuccessfully.

PLC editor
- 71 -
 6F2S1904 (Rev. 1.21)

(iii) Assigning a variable to a PLC driver

The user can assign a variable to a PLC driver1 to initiate the PLC. Several variables are used
for the PLC outputs. Table 6.3-5 shows data types to be available for the PLC drivers. They
can generate output signals for the user.
Table 6.2-5 Data types in PLC driver
Types Signal name3 Number of contents Comments
BIT BIT_xx_y 128 xx: byte offset; y: bit offset
USINT U08_xx 32 xx: serial numbers
UINT U16_xx 32 xx: serial numbers
UDINT U32_xx 32 xx: serial numbers
SINT S08_xx 32 xx: serial numbers
INT S16_xx 32 xx: serial numbers
DINT S32_xx 32 xx: serial numbers
REAL R32_xx 32 xx: serial numbers
LREAL R64_xx 32 xx: serial numbers
BIT2 [Link].y (Equal to BIT_xx_y) xx: byte offset; y: bit offset
1Note: PLC drivers are provided by PLC_DRVs (Function ID: 230301 or 230302). For
example, 128 of the PLC drivers are made in 1-bit type. They includes points to
monitor the driver output signals (see each IED instruction manual). The lists are
provided with FunctionID and ElementIDs.
2Note: PMX3 and BIT drivers are provided in 1-bit type. The both are identical, but they
do not operate in the same manner. For the PMX3, users should use its data type
by seeing the example. Note PMX3 is only available in the PLC_DRV (Function ID
230301).
3Note: The signals are called with their names. They are listed with numbers (Data IDs).

How to use types “BIT”, “U08”, “U16” and other data types
 Open “Work sheet”, click “Variable” icon on “FBD Tool bar” (alternatively press the [F5]
key); the “Variable Properties” window will appear. (Step 1)
 Select a definition scope “Global”. Remove the mark of “Show all variables of worksheets”
(Step2).
 Choose a data type among “Global Variable Groups”. (Step 3)
 Select an object signal from “Name” drop-down list (Step 4). Object signals are shown as
“M_signal names”.

PLC editor
- 72 -
 6F2S1904 (Rev. 1.21)

Step1

Step2
Step4

Step3

Step2

Figure 6.2-7 “Variable Properties” window

How to use data type “PMX3” of PLC_DRV (FunctionID 230301)

The variable “ViewPoint” is provided in the PLC, as shown in Figure 6.2-8. For example, if the
user requires such that a “ViewPoint” has to be connected to PLC driver2 “PMX3_15_7”, the
below steps should be proceeded:

Figure 6.2-8 Variable “ViewPoint” in PLC

2Note: The PLC driver “PMX3_15_7” can be identified with Function ID (230301) and
Element ID (8710071BBF).

The “Variable Properties” window appears when a variable is added in the PLC, as discussed
in Chapter 6.1(iii). The user should key its name for “I/O address”, as shown in Figure 6.2-9.

PLC editor
- 73 -
 6F2S1904 (Rev. 1.21)

Figure 6.2-9 I/O address in screen “Variable Properties”

The user has to change the name of a PLC driver in accordance with the PLC format, as shown
in Table 6.2-6.

Table 6.2-6 Example of name change between Signal list and PLC editor
Expression PLC driver name3 Data ID(Function ID–Element ID)
Signal list expression PMX3_15_7 230301 – 8710071BBF
PLC expression %MX3.15.7 230301 – 8710071BBF
3Note: The user should change letters “P” to “%” to express a signal name in the PLC
editor. Likewise, change “_” to “.”.S

PLC editor
- 74 -
 6F2S1904 (Rev. 1.21)

User’s logic to be created by PLC

(i) User I/O logic (Example1 for G2 model)
Figure 6.3-3 shows a sample EF logic, and the user can create an own logic by the PLC and its
libraries (see Figure 2.8-1). In the figure, the EF logic has an input “EF_BLOCK” and an output
“EF1-OPT” so that the EF scheme logic can be controlled when its input and output is
controlled by the user own logic.

Figure 6.3-1 Sample EF scheme logic

Table 6.3-1 lists the sample signals of the EF scheme logic; the input and output are provided
with “EF1_BLOCK(input)” and “EF1-OPT(output)”.

Table 6.3-1 EF signal points for the PLC sample

 Signal monitoring point
EF(Function ID: 441001)
Element ID Name Description
8000011C23 EF1 EF1 relay element operated

8000011C27 EF1PU EF1 relay operation level pick up

8000011B60 EF1-OPT EF1 protection operated

 Connection point on PLC logic

EF(Function ID: 440001)
Element ID Name Description
800001EBB0 EF1_BLOCK EF1 protection block command

Note: The data length of the signal can be read using the 1st and 2nd number of
Element ID. To know that, jump to section 1.3. It also shows how to read the logic
(→see p. 2).

PLC editor
- 75 -
 6F2S1904 (Rev. 1.21)

Input PLC logic

A “G2lib_200B01” library is provided for user’s input PLC logic. “S1_BI1_1” input function block
is selected for the binary input circuit (BI1) at IO#1. That function block is connected with
function block “DOUT_BOOL_1” in the user’s input PLC logic.

BI1

IO#1: Binary input1 circuit

“G2lib_200B01” library (S1_BI1_1)

→see Table B.1-2 (p. 92)

Figure 6.3-2 Input PLC logic for EF function

The “DOUT_BOOL_1” one is added in Figure 6.3-2. It can check the status of the signal, and
generates a Boolean output. The function ID of this EF sample logic is 45A401, and the first
and second number of “800001EBB0” is “80”. Accordingly, in the EF1_BLOCK, the DTYPE is
80 and the DID is 0010EBB0.

Output PLC logic

Similarly, the user’s output PLC logic can be created with

BO1

IO#1: Binary output1 circuit

“G2lib_200B01” library (S1_BO1_1)

→see Table B.1-2 (p. 92)

Figure 6.3-3 Output PLC logic for EF function

PLC editor
- 76 -
 6F2S1904 (Rev. 1.21)

(ii) Key input logic (Example2 for G2 model)

The “G2lib_240001 (keyinput)” one is provided in the libraries. The user can create an own
‘key’ operation logic with the PLC. “KEYIN_CLOSE_1” and “KEYIN_OPEN_1” function
features are available in that library (→p.100). Figure 6.3-4 shows that a variable—“V000” in
BOOL—is mapped at an IO address.

Figure 6.3-4 PLC key logic (sample)

PLC editor
- 77 -
 6F2S1904 (Rev. 1.21)

Extended project export/import

The extended project export and import allows the user to export and import individual objects
and program parts; hence, the user can restore previously exported project versions by
importing them again or use parts of other projects. The following shows that objects are
exported/imported, when a particular node is selected in the project tree and the 'Export' or
'Import' command is invoked:

(i) How to export a project object

The user can export objects in the PC in either XML or IEC 61131-3 types.

1. Select a project object in the project tree window (Figure 6.4-1).

2. Select “File->+Export” from the menu bar.
3. Select “Export PLC open XML file” or “Extended IEC 61131-3 Export” from the
following window. The user can export a project in XLM or IEC in the PC.

PLC editor
- 78 -
 6F2S1904 (Rev. 1.21)

Select a project

Select “Export”

XLM type

IEC 61131-3 type

Figure 6.4-1 Selected a project to export in the PC

PLC editor
- 79 -
 6F2S1904 (Rev. 1.21)

(ii) How to Import a project object

The user can import project objects in the PC. To import them, the user needs to create new
project tree; the creation of the new one is discussed previously (→p.29).

1. Move to a project tree; or create a new Project with a sample project file.
2. Selecting the tree on the project tree window.
3. Choose “File->Import” with “XLM” or “Extended-IEC61131-3”.

Create a new project

Select the new one for import

Select “Import”

XLM type

IEC61131-3 type

Figure 6.4-2 Selection of Import in XML or Extended-IEC61131-3

PLC editor
- 80 -
 6F2S1904 (Rev. 1.21)

Import of POU in extended IEC61131-3

When IEC61131-3 type is selected, the user has to select “POU” and click “OK”. Select an object,
which was exported in the PC; then, it will be imported in the project tree. If a confirmation
message to overwrite is displayed, click “OK” for the importation. Figure 6.4-3 illustrates cyclic
operations for importing POU items in the PC.

Select “Import”

Select IEC61131-3 type

Select POU

Select a POU object in the PC

Figure 6.4-3 Importing POU objects

PLC editor
- 81 -
 6F2S1904 (Rev. 1.21)

To import the items about “Physical Hardware”, takes the steps shown in Figure 6.4-4.

Select “Import”

Select IEC61131-3 type

Select Phy. Hard

Select an object in the PC

Figure 6.4-4 Importing Physical hardware object

When importing objects is complete, the user can save them with “File->Save Project As / Zip
Project As” using the menu bar.

PLC editor
- 82 -
 6F2S1904 (Rev. 1.21)

Setting of Timer function blocks

In order to delay the signal operation or to generate a pulse signal, timer function blocks (FBs)
is provided for the user. Figure 6.5-1 shows a constant value can be set in the users PLC logic
by the PLC editor, but it can be changed later by the LCD/GR-TIMES menu† though [UTMxx]
settings by a variable, which is realized by the global variable in the IED memory.
IED memory PLC function

PLC editor

Timer FB
Constant value set
Fixed PLC = 500ms

A timer value inputted

PLC driver FB ( 500 [ms] or 200 [ms] )
Function ID: 230302
Variable value set
Setting [UTMxx] = 200 ms
= 5000ms

User PLC logic

Figure 6.5-1 User PLC logic including a time delay FB (example)

PLC timer settings: [UTM1]~ [UTM24]

PLC Timer
10:48 1/24
UTM1 +
0 ms
UTM2 +
0 ms
UTM3 +
0 ms

UTM24 +
0 ms

GR-TIEMS Setting screen LCD screen

Figure 6.5-2 [UTMxx] timer setting menu (GR-TIMES or LCD†)

†Note:The setting menu position and structure about the PLC timer is shown on the GR-
TIEMS or LCD, but the operation of settings [UTMxx] are dependent on respective
GR200 series’ models. Some models do not support that. To find the menu positon
and structure, see respective IED instruction manuals (see Capture User
interface).

PLC editor
- 83 -
 6F2S1904 (Rev. 1.21)

(i) Kinds of Timer FBs

Three function blocks (FBs) are provided in the PLC: TP, TON, and TOF. Table 6.5-1 illustrates
the symbols and operations about TP, TON, TOP. Table 6.5-2 shows the FBs have four
parameters for their input and output operations.

Table 6.5-1 Timer FBs

Kinds Short descriptions Function operation Symbols

An input signal is outputted to be

TOF Delayed drop off timer
dropped off slowly.

An input signal is outputted to be

TON Delayed pick up timer
picked up slowly.

An input signal creates a shot

TP One shot timer
pulse output.

Table 6.5-2 Parameters and Data types

Data
Parameters Descriptions
types
IN BOOL If the FB detects an input signal to be fallen, the timer can start.

PT TIME A delay time value is set beforehand for the timer.

TRUE:
If an input signal is logically true (i.e., IN=TURE), and when
the ET value is smaller than the PT value (i.e., ET < PT), the
FB can output the TRUE signal.
Q BOOL
FALSE:
If an input one is not logically true (i.e., IN≠TURE), and when
the ET value is not smaller than the PT one (i.e., ET ≥ PT), the
FB outputs the FALSE signal.
ET TIME Elapsed time interval.

PLC editor
- 84 -
 6F2S1904 (Rev. 1.21)

(ii) How to set a constant in Timer FB

When the user sets a constant value by the PLC editor, the time value will be fixed in the timer
FB. Figure 6.5-3 illustrates how to set a value (200ms, constant one) when it is the TON FB.

Step 2

Step 1

Step 3

Figure 6.5-3 Constant (200ms) is set in the FB of the PLC worksheet (example)

Step1: Double clicks at the PT in the TON1 FB, and then the Variable properties is
screened.
Step2: Enter the name of the TOP FB in the screen. In the PLC, the time value is
expressed in “TIME#xxxms” format. Thus, the user has to enter “TIME#200ms”
when the constant (200 ms) is required to set.
Step3: After clicking OK button, the constant one is set in the FB.

Note: The format of TIME is defined in the PLC (→p. 51). The user has to set the value
in accordance with the format.

PLC editor
- 85 -
 6F2S1904 (Rev. 1.21)

(iii) How to set a variable in Timer FB

When the user wishes to use a variable value in the timer FB, it will be changed with the
setting menu of the IED. This feature is realized with the PLC driver, so the user has to set
the PLC driver in the TON FB.

Step 4 Step 2

Step 1

Step 3
Step 5

Step 2

Figure 6.5-4 Driver (for variable UTM1) is set in the FB of the PLC worksheet (example)

The variable value is exchanged through the global variable and the PLC driver. The global
value is defined already in a template (such as, G2_sampleIED→p. 18).

Step1: Double clicks at the PT in the TON1 FB, and then the Variable properties is
screened.
Step2: Select Global, and then remove Select all variable of worksheet.
Step3: Choice user timer in the Global Variable Groups.
Step4: Select a name among the drop down list. Remember that its name is identical
to both the variable value and the variable signal name.
Step5: After clicking OK button, the valuable constant is set in the FB.

Note: For more information about settings [UTM1]~[UTM24], see Chapter PLC function
of each GR200 series IED manual, separately.
The variable settings are not supported in some GR200 series’ models. To find the
IED has them, see respective IED instruction manuals (see Capture PLC
function).

PLC editor
- 86 -
 6F2S1904 (Rev. 1.21)

Appendix A Firmware libraries

“Firmware libraries” are provided for the PLC function. These are the common libraries for
whole IEDs.

Table A-1 Folder name for Firmware libraries

Windows OS Destination
C:¥ProgramData¥KW-
Software¥MULTIPROG®¥5_35_xxx¥plc¥FW_LIB¥G2EclrNativeFW

8.1,10

Note: The number “xxx” depends on the MULTIPROG software revision number.

PLC editor
- 87 -
 6F2S1904 (Rev. 1.21)

To import the libraries, select “Libraries” on “Project Tree Window”; then, right click at “Insert”;
select “Firmware Library”.

Figure A-1 Insertion of Firmware library

When inserted, they are shown in drop down lists. See Chapter 5 for details.

Figure A-2 FBs list

PLC editor
- 88 -
 6F2S1904 (Rev. 1.21)

Appendix B User libraries

The User libraries are provided for the respective IED models, so that required ones are
dependent on the IED model (Table B.1-1 etc. or Table B.2-1 etc.). The user libraries are saved
in the PC folder by the installation of user libraries (→ p. 12). Table B-1 shows the libraries
are saved in the PC folder “Libraries”.

Table B-1 Folder name for user libraries

Windows OS Destination
C:¥Users¥Public¥Documents¥MULTIPROG¥Libraries

8.1, 10

PLC editor
- 89 -
 6F2S1904 (Rev. 1.21)

To import the user libraries, select “Libraries” on “Project Tree Window”; then, right click at
“Insert”; select “User Library”.

Figure B-1 Inserting User Library

When inserted, FBs are listed in the drop down list.

Figure B-2 Function blocks in file “G2lib_240001 (keyinput).mwt”

PLC editor
- 90 -
 6F2S1904 (Rev. 1.21)

App. B.1-1 G2 user library files

Table B.1-1 G2 model2: User libraries and their function names

File names1 Contents of User Library
G2lib_200B01(BIO_slot1).mwt User library for BI or BO circuits at IO#1.
G2lib_200B02(BIO_slot2).mwt User library for BI or BO circuits at IO#2.
G2lib_200B03(BIO_slot3).mwt User library for BI or BO circuits at IO#3.
G2lib_200B04(BIO_slot4).mwt User library for BI or BO circuits at IO#4.
G2lib_200B05(BIO_slot5).mwt User library for BI or BO circuits at IO#5.
G2lib_200B06(BIO_slot6).mwt User library for BI or BO circuits at IO#6.
G2lib_200B07(BIO_slot7).mwt User library for BI or BO circuits at IO#7.
G2lib_200B08(BIO_slot8).mwt User library for BI or BO circuits at IO#8.
G2lib_240001(keyinput).mwt User library for key button on IED front panel
1Note: The above files are stored in the folder shown in Table B-1.
2Note: To identify the model, see Figure 3.1-1 and Figure 3.1-6 of Chapter Connection
and project setting (→p.26).

PLC editor
- 91 -
 6F2S1904 (Rev. 1.21)

Table B.1-2 G2 model: G2lib_200B01 library for IO#1 slot

Function items Binary input circuits Function items Binary output circuits

S1_BI1 BI1 at IO#1 S1_BO1 BO1 at IO#1

S1_BI2 BI2 at IO#1 S1_BO2 BO2 at IO#1
S1_BI3 BI3 at IO#1 S1_BO3 BO3 at IO#1
S1_BI4 BI4 at IO#1 S1_BO4 BO4 at IO#1
S1_BI5 BI5 at IO#1 S1_BO5 BO5 at IO#1
S1_BI6 BI6 at IO#1 S1_BO6 BO6 at IO#1
S1_BI7 BI7 at IO#1 S1_BO7 BO7 at IO#1
S1_BI8 BI8 at IO#1 S1_BO8 BO8 at IO#1
S1_BI9 BI9 at IO#1 S1_BO9 BO9 at IO#1
S1_BI10 BI10 at IO#1 S1_BO10 BO10 at IO#1
S1_BI11 BI11 at IO#1 S1_BO11 BO11 at IO#1
S1_BI12 BI12 at IO#1 S1_BO12 BO12 at IO#1
S1_BI13 BI13 at IO#1 S1_BO13 BO13 at IO#1
S1_BI14 BI14 at IO#1 S1_BO14 BO14 at IO#1
S1_BI15 BI15 at IO#1 S1_BO15 BO15 at IO#1
S1_BI16 BI16 at IO#1 S1_BO16 BO16 at IO#1
S1_BI17 BI17 at IO#1 S1_BO17 BO17 at IO#1
S1_BI18 BI18 at IO#1 S1_BO18 BO18 at IO#1
S1_BI19 BI19 at IO#1
S1_BI20 BI20 at IO#1
S1_BI21 BI21 at IO#1
S1_BI22 BI22 at IO#1
S1_BI23 BI23 at IO#1
S1_BI24 BI24 at IO#1
S1_BI25 BI25 at IO#1
S1_BI26 BI26 at IO#1
S1_BI27 BI27 at IO#1
S1_BI28 BI28 at IO#1
S1_BI29 BI29 at IO#1
S1_BI30 BI30 at IO#1
S1_BI31 BI31 at IO#1
S1_BI32 BI32 at IO#1

PLC editor
- 92 -
 6F2S1904 (Rev. 1.21)

Table B.1-3 G2 model: G2lib_200B02 library for IO#2 slot

Function items Binary input circuits Function items Binary output circuits

S2_BI1 BI1 at IO#2 S2_BO1 BO1 at IO#2

S2_BI2 BI2 at IO#2 S2_BO2 BO2 at IO#2
S2_BI3 BI3 at IO#2 S2_BO3 BO3 at IO#2
S2_BI4 BI4 at IO#2 S2_BO4 BO4 at IO#2
S2_BI5 BI5 at IO#2 S2_BO5 BO5 at IO#2
S2_BI6 BI6 at IO#2 S2_BO6 BO6 at IO#2
S2_BI7 BI7 at IO#2 S2_BO7 BO7 at IO#2
S2_BI8 BI8 at IO#2 S2_BO8 BO8 at IO#2
S2_BI9 BI9 at IO#2 S2_BO9 BO9 at IO#2
S2_BI10 BI10 at IO#2 S2_BO10 BO10 at IO#2
S2_BI11 BI11 at IO#2 S2_BO11 BO11 at IO#2
S2_BI12 BI12 at IO#2 S2_BO12 BO12 at IO#2
S2_BI13 BI13 at IO#2 S2_BO13 BO13 at IO#2
S2_BI14 BI14 at IO#2 S2_BO14 BO14 at IO#2
S2_BI15 BI15 at IO#2 S2_BO15 BO15 at IO#2
S2_BI16 BI16 at IO#2 S2_BO16 BO16 at IO#2
S2_BI17 BI17 at IO#2 S2_BO17 BO17 at IO#2
S2_BI18 BI18 at IO#2 S2_BO18 BO18 at IO#2
S2_BI19 BI19 at IO#2
S2_BI20 BI20 at IO#2
S2_BI21 BI21 at IO#2
S2_BI22 BI22 at IO#2
S2_BI23 BI23 at IO#2
S2_BI24 BI24 at IO#2
S2_BI25 BI25 at IO#2
S2_BI26 BI26 at IO#2
S2_BI27 BI27 at IO#2
S2_BI28 BI28 at IO#2
S2_BI29 BI29 at IO#2
S2_BI30 BI30 at IO#2
S2_BI31 BI31 at IO#2
S2_BI32 BI32 at IO#2

PLC editor
- 93 -
 6F2S1904 (Rev. 1.21)

Table B.1-4 G2 model: G2lib_200B03 library for IO#3 slot

Function items Binary input circuits Function items Binary output circuits

S3_BI1 BI1 at IO#3 S3_BO1 BO1 at IO#3

S3_BI2 BI2 at IO#3 S3_BO2 BO2 at IO#3
S3_BI3 BI3 at IO#3 S3_BO3 BO3 at IO#3
S3_BI4 BI4 at IO#3 S3_BO4 BO4 at IO#3
S3_BI5 BI5 at IO#3 S3_BO5 BO5 at IO#3
S3_BI6 BI6 at IO#3 S3_BO6 BO6 at IO#3
S3_BI7 BI7 at IO#3 S3_BO7 BO7 at IO#3
S3_BI8 BI8 at IO#3 S3_BO8 BO8 at IO#3
S3_BI9 BI9 at IO#3 S3_BO9 BO9 at IO#3
S3_BI10 BI10 at IO#3 S3_BO10 BO10 at IO#3
S3_BI11 BI11 at IO#3 S3_BO11 BO11 at IO#3
S3_BI12 BI12 at IO#3 S3_BO12 BO12 at IO#3
S3_BI13 BI13 at IO#3 S3_BO13 BO13 at IO#3
S3_BI14 BI14 at IO#3 S3_BO14 BO14 at IO#3
S3_BI15 BI15 at IO#3 S3_BO15 BO15 at IO#3
S3_BI16 BI16 at IO#3 S3_BO16 BO16 at IO#3
S3_BI17 BI17 at IO#3 S3_BO17 BO17 at IO#3
S3_BI18 BI18 at IO#3 S3_BO18 BO18 at IO#3
S3_BI19 BI19 at IO#3
S3_BI20 BI20 at IO#3
S3_BI21 BI21 at IO#3
S3_BI22 BI22 at IO#3
S3_BI23 BI23 at IO#3
S3_BI24 BI24 at IO#3
S3_BI25 BI25 at IO#3
S3_BI26 BI26 at IO#3
S3_BI27 BI27 at IO#3
S3_BI28 BI28 at IO#3
S3_BI29 BI29 at IO#3
S3_BI30 BI30 at IO#3
S3_BI31 BI31 at IO#3
S3_BI32 BI32 at IO#3

PLC editor
- 94 -
 6F2S1904 (Rev. 1.21)

Table B.1-5 G2 model: G2lib_200B04 library for IO#4 slot

Function items Binary input circuits Function items Binary output circuits

S4_BI1 BI1 at IO#4 S4_BO1 BO1 at IO#4

S4_BI2 BI2 at IO#4 S4_BO2 BO2 at IO#4
S4_BI3 BI3 at IO#4 S4_BO3 BO3 at IO#4
S4_BI4 BI4 at IO#4 S4_BO4 BO4 at IO#4
S4_BI5 BI5 at IO#4 S4_BO5 BO5 at IO#4
S4_BI6 BI6 at IO#4 S4_BO6 BO6 at IO#4
S4_BI7 BI7 at IO#4 S4_BO7 BO7 at IO#4
S4_BI8 BI8 at IO#4 S4_BO8 BO8 at IO#4
S4_BI9 BI9 at IO#4 S4_BO9 BO9 at IO#4
S4_BI10 BI10 at IO#4 S4_BO10 BO10 at IO#4
S4_BI11 BI11 at IO#4 S4_BO11 BO11 at IO#4
S4_BI12 BI12 at IO#4 S4_BO12 BO12 at IO#4
S4_BI13 BI13 at IO#4 S4_BO13 BO13 at IO#4
S4_BI14 BI14 at IO#4 S4_BO14 BO14 at IO#4
S4_BI15 BI15 at IO#4 S4_BO15 BO15 at IO#4
S4_BI16 BI16 at IO#4 S4_BO16 BO16 at IO#4
S4_BI17 BI17 at IO#4 S4_BO17 BO17 at IO#4
S4_BI18 BI18 at IO#4 S4_BO18 BO18 at IO#4
S4_BI19 BI19 at IO#4
S4_BI20 BI20 at IO#4
S4_BI21 BI21 at IO#4
S4_BI22 BI22 at IO#4
S4_BI23 BI23 at IO#4
S4_BI24 BI24 at IO#4
S4_BI25 BI25 at IO#4
S4_BI26 BI26 at IO#4
S4_BI27 BI27 at IO#4
S4_BI28 BI28 at IO#4
S4_BI29 BI29 at IO#4
S4_BI30 BI30 at IO#4
S4_BI31 BI31 at IO#4
S4_BI32 BI32 at IO#4

PLC editor
- 95 -
 6F2S1904 (Rev. 1.21)

Table B.1-6 G2 model: G2lib_200B05 library for IO#5 slot

Function items Binary input circuits Function items Binary output circuits

S5_BI1 BI1 at IO#5 S5_BO1 BO1 at IO#5

S5_BI2 BI2 at IO#5 S5_BO2 BO2 at IO#5
S5_BI3 BI3 at IO#5 S5_BO3 BO3 at IO#5
S5_BI4 BI4 at IO#5 S5_BO4 BO4 at IO#5
S5_BI5 BI5 at IO#5 S5_BO5 BO5 at IO#5
S5_BI6 BI6 at IO#5 S5_BO6 BO6 at IO#5
S5_BI7 BI7 at IO#5 S5_BO7 BO7 at IO#5
S5_BI8 BI8 at IO#5 S5_BO8 BO8 at IO#5
S5_BI9 BI9 at IO#5 S5_BO9 BO9 at IO#5
S5_BI10 BI10 at IO#5 S5_BO10 BO10 at IO#5
S5_BI11 BI11 at IO#5 S5_BO11 BO11 at IO#5
S5_BI12 BI12 at IO#5 S5_BO12 BO12 at IO#5
S5_BI13 BI13 at IO#5 S5_BO13 BO13 at IO#5
S5_BI14 BI14 at IO#5 S5_BO14 BO14 at IO#5
S5_BI15 BI15 at IO#5 S5_BO15 BO15 at IO#5
S5_BI16 BI16 at IO#5 S5_BO16 BO16 at IO#5
S5_BI17 BI17 at IO#5 S5_BO17 BO17 at IO#5
S5_BI18 BI18 at IO#5 S5_BO18 BO18 at IO#5
S5_BI19 BI19 at IO#5
S5_BI20 BI20 at IO#5
S5_BI21 BI21 at IO#5
S5_BI22 BI22 at IO#5
S5_BI23 BI23 at IO#5
S5_BI24 BI24 at IO#5
S5_BI25 BI25 at IO#5
S5_BI26 BI26 at IO#5
S5_BI27 BI27 at IO#5
S5_BI28 BI28 at IO#5
S5_BI29 BI29 at IO#5
S5_BI30 BI30 at IO#5
S5_BI31 BI31 at IO#5
S5_BI32 BI32 at IO#5

PLC editor
- 96 -
 6F2S1904 (Rev. 1.21)

Table B.1-7 G2 model: G2lib_200B06 library for IO#6 slot

Function items Binary input circuits Function items Binary output circuits

S6_BI1 BI1 at IO#6 S6_BO1 BO1 at IO#6

S6_BI2 BI2 at IO#6 S6_BO2 BO2 at IO#6
S6_BI3 BI3 at IO#6 S6_BO3 BO3 at IO#6
S6_BI4 BI4 at IO#6 S6_BO4 BO4 at IO#6
S6_BI5 BI5 at IO#6 S6_BO5 BO5 at IO#6
S6_BI6 BI6 at IO#6 S6_BO6 BO6 at IO#6
S6_BI7 BI7 at IO#6 S6_BO7 BO7 at IO#6
S6_BI8 BI8 at IO#6 S6_BO8 BO8 at IO#6
S6_BI9 BI9 at IO#6 S6_BO9 BO9 at IO#6
S6_BI10 BI10 at IO#6 S6_BO10 BO10 at IO#6
S6_BI11 BI11 at IO#6 S6_BO11 BO11 at IO#6
S6_BI12 BI12 at IO#6 S6_BO12 BO12 at IO#6
S6_BI13 BI13 at IO#6 S6_BO13 BO13 at IO#6
S6_BI14 BI14 at IO#6 S6_BO14 BO14 at IO#6
S6_BI15 BI15 at IO#6 S6_BO15 BO15 at IO#6
S6_BI16 BI16 at IO#6 S6_BO16 BO16 at IO#6
S6_BI17 BI17 at IO#6 S6_BO17 BO17 at IO#6
S6_BI18 BI18 at IO#6 S6_BO18 BO18 at IO#6
S6_BI19 BI19 at IO#6
S6_BI20 BI20 at IO#6
S6_BI21 BI21 at IO#6
S6_BI22 BI22 at IO#6
S6_BI23 BI23 at IO#6
S6_BI24 BI24 at IO#6
S6_BI25 BI25 at IO#6
S6_BI26 BI26 at IO#6
S6_BI27 BI27 at IO#6
S6_BI28 BI28 at IO#6
S6_BI29 BI29 at IO#6
S6_BI30 BI30 at IO#6
S6_BI31 BI31 at IO#6
S6_BI32 BI32 at IO#6

PLC editor
- 97 -
 6F2S1904 (Rev. 1.21)

Table B.1-8 G2 model: G2lib_200B07 library for IO#7 slot

Function items Binary input circuits Function items Binary output circuits

S7_BI1 BI1 at IO#7 S7_BO1 BO1 at IO#7

S7_BI2 BI2 at IO#7 S7_BO2 BO2 at IO#7
S7_BI3 BI3 at IO#7 S7_BO3 BO3 at IO#7
S7_BI4 BI4 at IO#7 S7_BO4 BO4 at IO#7
S7_BI5 BI5 at IO#7 S7_BO5 BO5 at IO#7
S7_BI6 BI6 at IO#7 S7_BO6 BO6 at IO#7
S7_BI7 BI7 at IO#7 S7_BO7 BO7 at IO#7
S7_BI8 BI8 at IO#7 S7_BO8 BO8 at IO#7
S7_BI9 BI9 at IO#7 S7_BO9 BO9 at IO#7
S7_BI10 BI10 at IO#7 S7_BO10 BO10 at IO#7
S7_BI11 BI11 at IO#7 S7_BO11 BO11 at IO#7
S7_BI12 BI12 at IO#7 S7_BO12 BO12 at IO#7
S7_BI13 BI13 at IO#7 S7_BO13 BO13 at IO#7
S7_BI14 BI14 at IO#7 S7_BO14 BO14 at IO#7
S7_BI15 BI15 at IO#7 S7_BO15 BO15 at IO#7
S7_BI16 BI16 at IO#7 S7_BO16 BO16 at IO#7
S7_BI17 BI17 at IO#7 S7_BO17 BO17 at IO#7
S7_BI18 BI18 at IO#7 S7_BO18 BO18 at IO#7
S7_BI19 BI19 at IO#7
S7_BI20 BI20 at IO#7
S7_BI21 BI21 at IO#7
S7_BI22 BI22 at IO#7
S7_BI23 BI23 at IO#7
S7_BI24 BI24 at IO#7
S7_BI25 BI25 at IO#7
S7_BI26 BI26 at IO#7
S7_BI27 BI27 at IO#7
S7_BI28 BI28 at IO#7
S7_BI29 BI29 at IO#7
S7_BI30 BI30 at IO#7
S7_BI31 BI31 at IO#7
S7_BI32 BI32 at IO#7

PLC editor
- 98 -
 6F2S1904 (Rev. 1.21)

Table B.1-9 G2 model: G2lib_200B08 library for IO#8 slot

Function items Binary input circuits Function items Binary output circuits

S8_BI1 BI1 at IO#8 S8_BO1 BO1 at IO#8

S8_BI2 BI2 at IO#8 S8_BO2 BO2 at IO#8
S8_BI3 BI3 at IO#8 S8_BO3 BO3 at IO#8
S8_BI4 BI4 at IO#8 S8_BO4 BO4 at IO#8
S8_BI5 BI5 at IO#8 S8_BO5 BO5 at IO#8
S8_BI6 BI6 at IO#8 S8_BO6 BO6 at IO#8
S8_BI7 BI7 at IO#8 S8_BO7 BO7 at IO#8
S8_BI8 BI8 at IO#8 S8_BO8 BO8 at IO#8
S8_BI9 BI9 at IO#8 S8_BO9 BO9 at IO#8
S8_BI10 BI10 at IO#8 S8_BO10 BO10 at IO#8
S8_BI11 BI11 at IO#8 S8_BO11 BO11 at IO#8
S8_BI12 BI12 at IO#8 S8_BO12 BO12 at IO#8
S8_BI13 BI13 at IO#8 S8_BO13 BO13 at IO#8
S8_BI14 BI14 at IO#8 S8_BO14 BO14 at IO#8
S8_BI15 BI15 at IO#8 S8_BO15 BO15 at IO#8
S8_BI16 BI16 at IO#8 S8_BO16 BO16 at IO#8
S8_BI17 BI17 at IO#8 S8_BO17 BO17 at IO#8
S8_BI18 BI18 at IO#8 S8_BO18 BO18 at IO#8
S8_BI19 BI19 at IO#8
S8_BI20 BI20 at IO#8
S8_BI21 BI21 at IO#8
S8_BI22 BI22 at IO#8
S8_BI23 BI23 at IO#8
S8_BI24 BI24 at IO#8
S8_BI25 BI25 at IO#8
S8_BI26 BI26 at IO#8
S8_BI27 BI27 at IO#8
S8_BI28 BI28 at IO#8
S8_BI29 BI29 at IO#8
S8_BI30 BI30 at IO#8
S8_BI31 BI31 at IO#8
S8_BI32 BI32 at IO#8

PLC editor
- 99 -
 6F2S1904 (Rev. 1.21)

Table B.1-10 G2 model: G2lib_240001 library for Key inputs

Function items Key buttons

KEYIN_LOCRMT [L/R] Key input for Local/Remote operation

KEYIN_F1 [F1] Function key input
KEYIN_F2 [F2] Function key input
KEYIN_F3 [F3] Function key input
KEYIN_F4 [F4] Function key input
KEYIN_F5 [F5] Function key input
KEYIN_F6 [F6] Function key input
KEYIN_F7 [F7] Function key input
KEYIN_OPEN [O] Key input for OPEN control
KEYIN_CLOSE [I] Key input for CLOSE control
KEYIN_CANCEL [CANCEL] Operation key input
KEYIN_CLEAR [CLEAR] Operation key input
KEYIN_ENTER [ENTER] Operation key input
KEYIN_MIMIC [MIMIC] Operation key input
KEYIN_HELP [HELP] Operation key input
KEYIN_UP [▲] Operation input for cursor up
KEYIN_DOWN [▼] Operation input for cursor down
KEYIN_RIGHT [►] Operation input for cursor move right
KEYIN_LEFT [◄] Operation input for cursor move left

PLC editor
- 100 -
 6F2S1904 (Rev. 1.21)

App. B.2-1 MV user library files

Table B.2-1 MV model2: User library and function of User library

File names1 Contents of User Library
MVlib_200B41(BIO_slot1).mwt User library for a BI/BO circuit at IO#1-1/2.
MVlib_200B42(BIO_slot2).mwt User library for a BI/BO circuit at IO#2.
MVlib_200B43(BIO_slot3).mwt User library for a BI/BO circuit at IO#2.
MVlib_240001(keyinput).mwt User library for a key button on HMI
1Note: The above files are stored in the folder shown in Table B-1.
2Note: To identify the model, see Figure 3.1-2 and Figure 3.1-6 of Chapter Connection
and project setting (→p.26).

PLC editor
- 101 -
 6F2S1904 (Rev. 1.21)

Table B.2-2 MV model: MVlib_200B41 library for IO#1-1 slot

Function items Binary input circuits

S1_BI1 BI1 at IO#1-1

S1_BI2 BI2 at IO#1-1
S1_BI3 BI3 at IO#1-1
S1_BI4 BI4 at IO#1-1
S1_BI5 BI5 at IO#1-1
S1_BI6 BI6 at IO#1-1
S1_BI7 BI7 at IO#1-1
S1_BI8 BI8 at IO#1-1
S1_BI9 BI9 at IO#1-1
S1_BI10 BI10 at IO#1-1
S1_BI11 BI11 at IO#1-1
S1_BI12 BI12 at IO#1-1
S1_BI13 BI13 at IO#1-1
S1_BI14 BI14 at IO#1-1
S1_BI15 BI15 at IO#1-1

Table B.2-3 MV model: MVlib_200B41 library for IO#1-2 slot

Function items Binary input circuits

S1_BI1 BI1 at IO#1-2

S1_BI2 BI2 at IO#1-2
S1_BI3 BI3 at IO#1-2
S1_BI4 BI4 at IO#1-2
S1_BI5 BI5 at IO#1-2
S1_BI6 BI6 at IO#1-2
S1_BI7 BI7 at IO#1-2
S1_BI8 BI8 at IO#1-2

PLC editor
- 102 -
 6F2S1904 (Rev. 1.21)

Table B.2-4 MV model: MVlib_200B42 library for IO#2 slot

Function items Binary input circuits Function items Binary output circuits

S2_BI1 BI1 at IO#2 S2_BO1 BO1 at IO#2

S2_BI2 BI2 at IO#2 S2_BO2 BO2 at IO#2
S2_BI3 BI3 at IO#2 S2_BO3 BO3 at IO#2
S2_BI4 BI4 at IO#2 S2_BO4 BO4 at IO#2
S2_BI5 BI5 at IO#2 S2_BO5 BO5 at IO#2
S2_BI6 BI6 at IO#2 S2_BO6 BO6 at IO#2
S2_BI7 BI7 at IO#2 S2_BO7 BO7 at IO#2
S2_BI8 BI8 at IO#2 S2_BO8 BO8 at IO#2
S2_BI9 BI9 at IO#2
S2_BI10 BI10 at IO#2
S2_BI11 BI11 at IO#2
S2_BI12 BI12 at IO#2
S2_BI13 BI13 at IO#2
S2_BI14 BI14 at IO#2
S2_BI15 BI15 at IO#2

Table B.2-5 MV model: MVlib_200B43 library for IO#3 slot

Function items Binary input circuits Function items Binary output circuits

S3_BI1 BI1 at IO#3 S3_BO1 BO1 at IO#3

S3_BI2 BI2 at IO#3 S3_BO2 BO2 at IO#3
S3_BI3 BI3 at IO#3 S3_BO3 BO3 at IO#3
S3_BI4 BI4 at IO#3 S3_BO4 BO4 at IO#3
S3_BI5 BI5 at IO#3 S3_BO5 BO5 at IO#3
S3_BI6 BI6 at IO#3 S3_BO6 BO6 at IO#3
S3_BI7 BI7 at IO#3 S3_BO7 BO7 at IO#3
S3_BI8 BI8 at IO#3 S3_BO8 BO8 at IO#3
S3_BI9 BI9 at IO#3
S3_BI10 BI10 at IO#3
S3_BI11 BI11 at IO#3
S3_BI12 BI12 at IO#3
S3_BI13 BI13 at IO#3
S3_BI14 BI14 at IO#3
S3_BI15 BI15 at IO#3

PLC editor
- 103 -
 6F2S1904 (Rev. 1.21)

Table B.2-6 MV model: MVlib_240001 library for Key inputs

Function items Key buttons

KEYIN_LOCRMT [L/R] Key input for Local/Remote operation

KEYIN_F1 [F1] Function key input
KEYIN_F2 [F2] Function key input
KEYIN_F3 [F3] Function key input
KEYIN_F4 [F4] Function key input
KEYIN_F5 [F5] Function key input
KEYIN_OPEN [O] Key input for OPEN control
KEYIN_CLOSE [I] Key input for CLOSE control
KEYIN_CANCEL [CANCEL] Operation key input
KEYIN_CLEAR [CLEAR] Operation key input
KEYIN_ENTER [ENTER] Operation key input
KEYIN_UP [▲] Operation input for cursor up
KEYIN_DOWN [▼] Operation input for cursor down
KEYIN_RIGHT [►] Operation input for cursor move right
KEYIN_LEFT [◄] Operation input for cursor move left

PLC editor
- 104 -
 6F2S1904 (Rev. 1.21)

Appendix C Libraries folders

“G2 User libraries” is copied to the folder, shown in Table C-1.
Table C-1 Folder for G2 User libraries
Windows
Copied libraries Destination
OS
C:¥Users¥Public¥Documents¥MUL
8.1,10 custom¥document¥Libraries
TIPLOG

“G2EclrNativeFW” is copied to the folders, shown in Table C-2.

Table C-2 Folder for Library G2EclrNativeFW
Windows
Copied libraries Destination
OS
C:¥Documents and Settings¥All
custom¥appdata¥ Users¥Application Data¥KW-
8.1,10
G2EclrNativeFW Software¥MULTIPROG¥5_35_xxx¥pl
c¥FW_LIB
Note: The number “xxx” depends on the software revision number.

“DLL “G2Sharedmemory” of” custom¥program” folder is copied in the folders shown in Table
C-3.
Table C-3 Folder for G2Sharedmemory and others
Windows
Copied DLL Destination
OS
G2SharedMemory.dll1
C:¥Program Files4¥KW-
8.1,10 eCLRDeviceProfiles.xml2 Software¥MULTIPROG 5.35 Build
xxx¥plc¥eCLR¥PPCE300_BE_PPC
src.st13
1Note: This file is copied into a new folder.
2Note: This file is overwritten onto existing “[Link]”.
3Note: This file is overwritten onto existing “src.st1” to correct Event messages.
4Note: If 64bit OS is running, it will be copied to “C:¥Program Files(x86)¥....”
5Note: The number “xxx” depends on a software revision number.

PLC editor
- 105 -
 Rev. and Section Approved Checked by Prepared
Change place and contents
Date (page) by by
-- -- Tentative edition T. Kaneko
-- --
Oct. 26 2013 Oct. 26
0.1 -- First issue N. Iizuka N. Iizuka T. Kaneko
Jan. 16,2014 Jan. 16 Jan. 16 Jan.15
1.2.1 Added the save operation of project file
0.2 N. Iizuka N. Iizuka T. Kaneko
1.5.2 Added the confirmation procedure of DIN and DOUT FB
Feb. 20,2014 Feb. 20 Feb. 20 Feb. 19
1.5.3 Added the operation of import/export
0.21 1.2.1 (ix) The selection of Zip option is forbidden. N. Iizuka N. Iizuka T. Kaneko
Mar. 27,2014 Mar. 27 Mar. 27 Mar. 26
0.3 1.2.3 Connection means added. N. Iizuka N. Iizuka T. Kaneko
Jul. 10, 2014 Deleted the installation for Windows XP Jul. 10 Jul. 10 Jul. 9
0.4 1.5.2(iii) New PLC drivers added N. Iizuka N. Iizuka T. Kaneko
July 24,2014 1.5.3(iv) Libraries added Jul. 10 Jul. 10 Jul. 9
0.5 2.1(v) Chapter number revised; the new explanation for N. Iizuka N. Iizuka T. Kaneko
Aug. 4, 2014 installation software was added. Aug. 4 Aug. 4 Aug. 3
0.6 3.2 and 3.3 Revised data download procedures N. Iizuka N. Iizuka T. Kaneko
Oct 20, 2014 Oct. 20 Oct. 20 Oct. 19
0.61 3.3 Added the notice for downloading data F. Kawano N. Iizuka T. Kaneko
Oct 28, 2014 Oct. 20 Oct. 20 Oct. 20
0.71 3.2 Added the notice for selection of “Priority” F. Kawano N. Iizuka T. Kaneko
Nov 4, 2014 3.3 Altered the explanation for the download Nov. 4 Nov. 4 Oct. 28
0.8 4 Added the information corresponding to the error code F. Kawano N. Iizuka T. Kaneko
Dec 22, 2014 Dec. 22 Dec. 22 Dec. 17
0.81 2.7 Added the information of software update F. Kawano N. Iizuka T. Kaneko
Dec 25, 2014 4.2 Revised the information of the error-codes Dec. 24 Dec. 24 Dec. 23
0.82 2.1 Added the notice of software update F. Kawano N. Iizuka T. Kaneko
Jan 6, 2015 Jan. 6 Jan. 6 Jan. 6
0.83 Table 6.3-5 Added missing signal names N. Iizuka N. Iizuka T. Kaneko
Jan 21, 2015 Jan. 21 Jan. 21 Jan. 21
1.00 All sections Renovate the readability N. Iizuka N. Iizuka T. Kaneko
Apr 23, 2015 1.2 Required PC physical memories Apr. 23 Apr. 23 Apr. 20
2.1 Added the installation of the software for the ARM
1.10 3.1 Added the speed setting for the USB-connection N. Iizuka N. Iizuka T. Kaneko
Aug 25, 2015 3.2 Added the meaning as for the ARM in Table 3.3-4 Aug. 25 Aug. 25 Aug. 25
6.4 Added the notice that a single is available for a logic
1.11 3.2 Revised Fig. 3.1-2 and Fig. 3.2-6 N. Iizuka N. Iizuka T. Kaneko
Oct 26, 2015 6.4 Revised the description in Note in Sec. 6.4 (iii) and (iv) Oct. 26 Oct. 26 Oct. 26
1.12 3.3 (iii) Revised the selection of Download options N. Iizuka N. Iizuka T. Kaneko
Nov 17, 2015 Added the notice for download operation if impossible Nov. 17 Nov. 17 Nov. 17
1.13 3.3 (iii) Modified typos N. Iizuka N. Iizuka T. Kaneko
Nov 19, 2015 Nov. 19 Nov. 19 Nov. 19
2.1 Revised the file holder names during the installation N. Iizuka [Link] T. Kaneko
(ii),(iii),(iv),(v) Added the tips to check the software revision number May. 30 May. 11 Apr. 27
2.1 Deleted the contents “User libraries G2EclrNativeFW”; N. Iizuka [Link] T. Kaneko
1.14 added new contents “Folder for G2 User libraries” May. 30 May. 11 Apr. 27
May 31,2017 2.2 (i) Modified the contents to open new project or existing N. Iizuka [Link] T. Kaneko
project May. 30 May. 11 Apr. 27
7 Added trouble shooting list N. Iizuka [Link] T. Kaneko
May. 30 May. 11 Apr. 27
1.15 -- Republished under the spin-off company K. Oohashi K. Oohashi T. Kaneko
Oct. 2, 2017 Sep. 28 Sep. 28 Sep. 28
1.20 -- Revised whole contents in order to meet new GRE200 H. Amoh N. Iizuka T. Kaneko
Dec. 6, 2019 relay specifications Dec. 7 Dec. 2 Nov. 24
1.21 -- Changed a term “GRE200” model to “MV” model H. Amoh N. Iizuka T. Kaneko
Dec.12, 2019 Dec. 7 Dec. 2 Nov. 24