FA-M3 Programming Tool WideField3 (Introduction and Troubleshooting)
FA-M3 Programming Tool WideField3 (Introduction and Troubleshooting)
Manual
FA-M3 Programming Tool
WideField3
(Introduction and Troubleshooting)
IM 34M06Q16-01E
IM 34M06Q16-01E
Yokogawa Electric Corporation 8th Edition
Blank Page
i
Applicable Product:
Range-free Multi-controller FA-M3
- Model Name: SF630-MCW
- FA-M3 Programming Tool WideField3
The document number and document model code for this manual are given below.
Refer to the document number in all communications; also refer to the document
number or the document model code when purchasing additional copies of this manual.
Media No. IM 34M06Q16-01E (CD) 7th Edition: May 2017(YHQ) IM 34M06Q16-01E 7th Edition: May 31, 2017-00
All Rights Reserved Copyright 2012, Yokogawa Electric Corporation
ii
Important
About This Manual
- This Manual should be passed on to the end user.
- This manual is an essential part of the product; keep it in a safe place for future
reference.
- This product is designed to be used by a person with specialized knowledge.
- Before using the product, read this manual thoroughly to have a clear understanding
of the product.
- This manual explains the functions of this product, but there is no guarantee that
they will suit the particular purpose of the user.
- Under absolutely no circumstances may the contents of this manual be transcribed
or copied, in part or in whole, without permission.
- The contents of this manual are subject to change without prior notice.
- Every effort has been made to ensure accuracy in the preparation of this manual.
However, should any errors or omissions come to the attention of the user, please
contact the nearest Yokogawa Electric representative or sales office.
Safety Symbols
- Danger. This symbol on the product indicates that the operator must follow the
instructions laid out in this user's manual to avoid the risk of personnel injuries,
fatalities, or damage to the instrument. Where indicated by this symbol, the manual
describes what special care the operator must exercise to prevent electrical shock
or other dangers that may result in injury or the loss of life.
WARNING
- Indicates a “Warning”.
Draws attention to information essential to prevent hardware damage, software
damage or system failure.
CAUTION
- Indicates a “Caution”
Draws attention to information essential to the understanding of operation and
functions.
TIP
- Indicates a “TIP”
Gives information that complements the present topic.
SEE ALSO
- Indicates a “SEE ALSO” reference.
Identifies a source to which to refer.
Authorized Representative:
- The Authorized Representative for this product in the EEA is:
Yokogawa Europe B. V.
Euroweg 2, 3825 HD Amersfoort, The Netherlands
Do not touch components in the unit:
- Do not remove the back cover of the unit. Doing so may cause a failure.
Product Category
With reference to the equipment types in the WEEE directive, this product is classified
as a “Monitoring and Control instruments”.
When disposing of products in the EU, contact your local Yokogawa Europe B. V. office.
Do not dispose of this product in domestic household waste.
How to dispose the batteries
This is an explanation about the new EU Battery Directive. This directive is only valid in
the EU.
Batteries are included in some modules of this product. The procedure is different when
the user can remove or cannot remove.
Note: With reference to Annex II of the new EU Battery Directive, the above symbol
indicates obligatory separate collection.
Introduction
About This Manual
The WideField3 manual set consists of the following four volumes.
Table 1 Manual List
Volume Document No.
Introduction and Troubleshooting IM 34M06Q16-01E
Offline IM 34M06Q16-02E
Online IM 34M06Q16-03E
Script IM 34M06Q16-04E
Trace Function IM 34M06Q50-21E
This manual is the operation manual, Introduction and Troubleshooting, for the Range-
free Multi-controller FA-M3 Programming Tool (known as WideField3 in this manual).
B2. Updating Programs after a Change in the I/O Module Slot Position
Describes how to easily update a program when an I/O module is moved to a different
installed slot position.
C3. Troubleshooting
Describes common errors when using WideField3 and how to perform troubleshooting.
Notation
Notation for Windows Screens and Operation
- Items in initial caps denote symbols, names and window names.
Example: WideField3, Program Monitor dialog
- Bracketed items denote menu bar items, dialog box fields, commands, and buttons.
Example: Select [File]–[New] from the menu bar.
Click [OK].
For individual sequence CPU modules, please refer to the relevant user's manuals.
F3SP71, 76
- Sequence CPU Instruction Manual - Functions (for F3SP71-4N/4S, F3SP76-7N/7S)
(IM 34M06P15-01E)
- Sequence CPU – Network Functions (for F3SP71-4N/4S, F3SP76-7N/7S) (IM
34M06P15-02E)
- Sequence CPU Instruction Manual – Instructions (IM 34M06P12-03E)
F3SP66, 67
- Sequence CPU – Functions (for F3SP66-4S, F3SP67-6S) (IM 34M06P14-01E)
- Sequence CPU – Network Functions (for F3SP66-4S, F3SP67-6S) (IM 34M06P14-
02E)
- Sequence CPU Instruction Manual – Instructions (IM 34M06P12-03E)
FA Link Functions
- FA Link H Module, Fiber-optic FA Link H Module (IM 34M06H43-01E)
Trademarks
The trade names and company names referred to in this manual are either trademarks
or registered trademarks of their respective companies.
FA-M3
Programming Tool
WideField3 Introduction and Troubleshooting
IM 34M06Q16-01E 8th Edition
CONTENTS
Applicable Product: ...................................................................................i
Important ...................................................................................................ii
Introduction ...............................................................................................x
Copyrights and Trademarks ..................................................................xv
The startup manual describes basic specifications of WideField3 as well as setup and
startup procedures.
A1. Overview
This chapter gives an overview of the FA-M3 programming tool WideField3, and
describes its difference from its predecessor, the WideField2 (SF620) software.
Personal
Computer
-2 or
C
32
RS SB
U
Ethernet
/FLnet
A01_01.VSD
TIP
To confirm the software version in WideField3 R1, select [Help]–[Version Information] from the menu
bar. A dialog box as shown in Figure A1.2 appears. Verify that the software version is displayed as
“R1.xx”.
A01_02_R101.VSD
TIP
There is correspondence between CPU types as shown below. For description of F3SPV-, check
the following list and refer to the explanation of the corresponding CPU.
- F3SPV3-4H: Equivalent to F3SP53-4H
- F3SPV8-6H: Equivalent to F3SP58-6H
- F3SPV3-4S: Equivalent to F3SP53-4S
- F3SPV8-6S: Equivalent to F3SP58-6S
SEE ALSO
For details of devices, see "Sequence CPU – Functions."
SEE ALSO
For details of individual differences, see sections given in the “SEE ALSO” column in Table A1.6.
TIP
To confirm the software version in WideField3 R2, select [Help]–[Version Information] from the menu
bar. A dialog box as shown in Figure A1.3 appears. Verify that the software version is displayed as
“R2.xx”.
A01_02_R201.VSD
Figure A1.3 WideField3 R2 Version Information
TIP
There is correspondence between CPU types as shown below. For description of F3SPV-, check
the following list and refer to the explanation of the corresponding CPU.
- F3SPV3-4H: Equivalent to F3SP53-4H
- F3SPV8-6H: Equivalent to F3SP58-6H
- F3SPV3-4S: Equivalent to F3SP53-4S
- F3SPV8-6S: Equivalent to F3SP58-6S
- F3SPV9-7S: Device capacities and instructions are equivalent to F3SP76-7S
Script Monitoring The script monitor can be G5.4 Monitoring in the R2.03
hidden. Script Pane
CAUTION
TIP
To identify the type and Rev number of the CPU connected from WideField3, check the information
displayed on Status Bar.
SEE ALSO
For details on Status Bar, see Section A3.1, "Screen Layout."
SEE ALSO
For details of individual differences, see sections given in the “SEE ALSO” column in Table A1.8.
TIP
To confirm the software version in WideField3 R3, select [Help]–[Version Information] from the menu
bar. A dialog box as shown in Figure A1.3 appears. Verify that the software version is displayed as
“R3.xx”.
TIP
There is correspondence between CPU types as shown below. For description of F3SPV-, check
the following list and refer to the explanation of the corresponding CPU.
- F3SPV3-4H: Equivalent to F3SP53-4H
- F3SPV8-6H: Equivalent to F3SP58-6H
- F3SPV3-4S: Equivalent to F3SP53-4S
- F3SPV8-6S: Equivalent to F3SP58-6S
- F3SPV9-7S: Device capacities and instructions are equivalent to F3SP76-7S
CAUTION
Once a project is opened in WideField3 R3 and is converted to WideField3 R3 format,
the project can no longer be used in WideField3 R2. A project created in WideField3 R3
must be converted to a lower format so that it can be used in WideField3 R2 if
necessary.
TIP
To identify the type and Rev number of the CPU connected from WideField3, check the information
displayed on Status Bar.
SEE ALSO
For details on Status Bar, see Section A3.1, "Screen Layout."
Ladder Program Created with Any Circuit Column Count Other Than 11
The ladder program edit screen of WideField3 R3.02 or earlier shows a circuit with 11
columns. Therefore, except for a circuit with 11 columns in WideField3 R3.03 or later, a
circuit displayed in a single line is converted to a continuation circuit when displayed in
WideField3 R3.02 or earlier.
In addition, regardless of the column count of a circuit, block/macro files saved on
WideField3 R3.03 or later with a conversion error cannot be used with WideField3 R3.02
or earlier. When you try to open such a block/macro file, the error message appears as
shown below. To use in WideField3R3.02 or earlier, you must correct the conversion
error with WideField3 R3.03 or later.
A01_03.vsd
├── ││──────────○┤
├── ││─|
├── ││─| Circuit exceeding 25 lines
:
├── ││─|
├── ││─|
LD
OR
OR
Mnemonics display
:
OR
OR
OUT
SEE ALSO
- For details on the column count of a circuit, see Section E1.8, "Column Count in Circuit" (Offline).
- For details on the limitations on circuits, see Section E1.1.1, "Limitations on Editing Ladder
Program" (Offline).
- For details on mnemonic editing, see Section E1.2.44, "Mnemonic Editing Function" (Offline).
SEE ALSO
For details of individual functional differences, see the sections given in the “SEE ALSO” column in
Table A1.8.2.
TIP
To confirm the software version of WideField3 R4, select [Help]-[About WideField3] from the menu bar.
A dialog box as shown in Figure A1.6 appears. Verify that the version is displayed as “R4.xx”.
TIP
There is correspondence between CPU types as shown below. For a description of F3SPV-,
check the following list and refer to the explanation of the corresponding CPU.
- F3SPV3-4H: Equivalent to F3SP53-4H
- F3SPV8-6H: Equivalent to F3SP58-6H
- F3SPV3-4S: Equivalent to F3SP53-4S
- F3SPV8-6S: Equivalent to F3SP58-6S
- F3SPV9-7S: Device capacities and instructions are equivalent to F3SP76-7S
CAUTION
Projects in WideField3 R4 use the same format as WideField3 R3. A project created in
WideField3 R4 can also be used in WideField3 R3. Therefore, you do not have to
convert a project in WideField3 R4 format into one in WideField3 R3.
SEE ALSO
For details on Virtual-M3, see “FA-M3 Simulation Software Virtual-M3” (IM 34M06Q50-22E).
SEE ALSO
- For details on syntax check, see Section D3.2.1, "Checking Programs." Also, for details on the
program syntax check, see Section D1.2.6, "Program Syntax Check Setup."
- For details on protection, see Section D4.4, "Editing Local Devices and Properties of Blocks and
Macros" (Offline).
CAUTION
TIP
The in-CPU names file saves the corresponding relationship between a project file name, block file
names, and macro file names recognized by the personal computer and an executable program name,
block names, and macro names stored in the CPU.
CAUTION
Project configuration files are added when a project created in WideField is opened in
WideField3. The following table shows the files to be added.
Table A1.13 List of Files to be Added
Item to be Added File Name
In-CPU names file LONGNAME.TXT
Screen resume file Resumeinfo.USR
CAUTION
If a project that is opened and then downloaded to a sequence CPU using WideField3 is
uploaded using WideField or WideField2, the project may sometimes fail to be
generated properly. If this happens, perform [File]–[Save Project in Other Formats]–
[Downgrade and Save] in WideField3 for the project saved on the personal computer
before using it in WideField or WideField2.
CAUTION
CAUTION
Some operating environments may not display the font you choose on WideField3.
Start it by choosing the font which can be displayed.
CAUTION
Do not run the WideField3 software and the WideField (SF610) or WideField2 (SF620)
software concurrently.
TIP
- Use a USB1.1/2.0-compliant generic USB cable (up to 5m long).
- Depending on the chipset used by the PC running the WideField3 software, reliable USB
connection is not always guaranteed.
- A USB connection may become unreliable or even disconnected due to noise. If this happens,
remove and re-attach the USB cable to the PC.
- Connecting to the PC
Connect the cable to the serial port of the PC. The serial port is located at the back
for most PCs but located in front for some PCs.
- Connecting to the sequence CPU module
Connect the cable to the PROGRAMMER or SIO port of the sequence CPU module.
Remove the protective cover from the sequence CPU module to be accessed or
configured from WideField3, and connect the cable securely.
SEE ALSO
When using a USB cable for connection, you may need to configure the serial port on the PC.
For more information on the USB-Serial converter cable, see “USB-Serial Converter”
(IM34M06C91-01E).
SEE ALSO
For details on Ethernet connection, see “Ethernet Interface Module” (IM 34M06H24-01E, IM
34M06H24-04E).
SEE ALSO
For details, see “Sequence CPU – Network Functions (for F3SP66-4S, F3SP67-6S)” (IM34M06P14-
02E) and “Sequence CPU – Network Functions (for F3SP71-4N/4S, F3SP76-7N/7S)” (IM34M06P15-
02E).
CAUTION
SEE ALSO
For details on FL-net connection, see “FL-net (OPCN-2) Interface Module” (IM34M06H32-□□E)
A03_01.VSD
Title Bar
The title bar displays the file name of the open project, the name of the active window
and the name of the block or macro file being edited.
Project file name
Menu Bar
The menu bar displays names of menus which are available in WideField3. You can
select a menu from the menu bar. The menus displayed in the menu bar are dependant
on the function that is currently active e.g. online or tag name definition function.
Toolbar
The toolbar displays icons of the most frequently used menus from the menu bar. You
can select a menu from the menu bar or the toolbar.
To register a menu to the toolbar, use the Set up Environment dialog box.
To switch between showing and hiding the tool bar, use [View]–[Toolbar].
A03_04.VSD
Figure A3.4 Layout of Toolbar (The figure shows the single row of icons divided into two.)
Instruction Palette
The instruction palette displays icons for instructions and comments. You can create a
circuit by selecting instructions from the instruction palette.
To switch between showing and hiding the instruction palette, use [View]–[Instruction
Palette].
A03_05.VSD
Find Bar
The find bar displays an area for entering devices for search conditions and icons to
specify for performing searches. You can also select devices for search conditions from
past history.
To switch between showing and hiding the find bar, use [View]–[Find Bar].
A03_06.VSD
A03_07.VSD
Status Bar
The status bar displays various status information of the WideField3 software.
To switch between showing or hiding the status bar, use [View]–[Status Bar].
Displays Overwrite/
Describes the menu item under the Displays the type and Rev
mouse cursor. Insert mode.
number of the CPU connected.
Displays Communication
medium. Displays the number of lines
and steps in the block and
The status of the FA-M3 command macro.
connection is displayed here.
A03_08.VSD
Select [Copy File] from the popup Copies a project block with a different
menu. name.
Select [Insert File] from the popup Adds a block file to the project.
menu.
Select [Rename File] from the popup Changes the file name of the specified
menu. block in the project.
Select [Delete File] from the popup Deletes a block file in the project.
menu.
Select [Copy File] from the popup Copies a project macro with a different
menu. name.
Select [Rename File] from the popup Changes the file name of the specified
menu. macro in the project.
Select [Delete File] from the popup Deletes a macro file in the project.
menu.
Select [Extract Macro] from the popup Adds a macro file to the project.
menu.
Macro under Select [Compare] from the popup Compares macro programs.
the Macro List menu.
Select [Block Tag Name Definition] Opens the Macro Tag Name Definition
from the popup menu. window.
Select [Local Device/Properties] from Opens the Local Device/Properties dialog
the popup menu. box.
Select [Copy File] from the popup Copies a project block with a different
menu. name.
Select [Rename File] from the popup Changes the macro file name.
menu.
Select [Delete File] from the popup Deletes the macro.
menu.
Select [Register Macro] from the Registers a macro in the macro folder.
popup menu.
Double-click, or Opens the Edit Macro window.
select [Open] from the popup menu.
Displays the CPU type for the Double-click to open windows for
connection destination. each log type.
Double-click to open the Display
CPU Program Information dialog
box. Double-click to open the Common
Tag Name Definition monitor
Double-click to open the Alarm
window.
display window.
Output Window
The output window is an auxiliary window that facilitates WideField3 functions.
Tab name of the output window
A03_12.VSD
SEE ALSO
For details of the balloon list window, see Section E1.2.40, "Creating and Deleting Balloon Comments"
(Offline).
Search Window
The search window allows simple viewing of project cross references.
A03_14.VSD
SEE ALSO
For details on the search window and cross references, see Chapter E6, "Cross Reference" (Offline).
CAUTION
User program files in WideField3 are managed as version 5 files in WideField series.
User Log File .YULG Stores user logs. K3.3 User Log
Operation Log .YCLG
Stores operation logs. K3.4 Operation Log
File .YOLG
Sampling
.YTST2
Trace Setup Stores sampling trace settings. K4 Sampling Trace Tool
File .YTSC
Sampling .YTRC2
Trace Results .CSV Stores sampling trace results. K4 Sampling Trace Tool
File .YTRS
Device .YDVF Stores device data. H8 Device Manager
Management Stores device data in the format H8 Device Manager
File .YMDV suitable for the email functions. H10.4 Remote OME by Email
CPU Property Download this file to set up the
File .YPRP CPU.
D2 Overview of Projects
FA Link Setup Stores FA link configuration H7.1 Station Assignment and
File .FAI information. Monitoring of FA Links
Balloon
Comment File .YBLC Stores balloon comments. D2 Overview of Projects
Stores the corresponding
relationship between on-PC
names, such as a project file
In-CPU names
file .TXT name and block file names, and D2 Overview of Projects
in-CPU names such as an
executable program name and
block names.
Operation
Stores operation protection
Protection .YODF H11.2 Operation Protection
settings.
Settings File
Print Setup
File .YPRN Stores print settings. D2 Overview of Projects
Screen
Resume File .YUSR Stores screen states. D2 Overview of Projects
*1: File names with these extensions are "on-PC names."
For details on on-PC names, see Section A5.2, "Naming Rules."
Access Keys
Access keys are letters assigned to menu items to allow a user to select a menu using
the keyboard. Access keys are displayed as underlined letters on a menu.
For example, pressing the [ALT] key, followed by the [T] key opens the [Tools] menu.
Pressing the [E] key in this state selects the [Set up Environment] menu item.
A03_16.VSD
Windows
Windows can be enlarged or reduced. Multi-window operations are supported.
You can open up to 16 online windows concurrently.
To close a window, select [File]–[Close] from the menu bar.
To close all windows that are currently displayed, select [File]–[Close All].
To close all the windows except for the currently active window, select [File]-[Close All
Except Frontmost Window].
TIP
If you open a new window when the maximum number of windows are already open, the window at the
back (the rearmost window of the window stack) automatically closes. If the window at the back is an
Edit Block window being edited or is under online editing, a message box appears to check if you want
to save or apply any changes made.
Modeless Dialogs
Menu operations sometimes move control to a modeless dialog. To close a modeless
dialog, click on the corresponding button displayed on the dialog. Commands from
menus have no effect on a modeless dialog.
SEE ALSO
For Explaining about installation/uninstallaion of WideField3, refer to “FA-M3 Programming Tool
WideField3 Readme First (IM34M06Q16-11E)”.
Procedure
(1) On the [Start] menu, select [All
Programs]–[FA-M3 Application]–
[WideField3].
The start screen of WideField3 is
displayed.
TIP
You can also use the WideField3 shortcut
icon on the desktop to start the software.
CAUTION
Do not install the WideField3 software and the WideField (SF610) or WideField2
(SF620) software on the same PC.
The following restrictions apply if you have multiple WideField3 applications running
concurrently:
- You cannot open project files with the same name concurrently.
- Only one WideField3 application can connect online to a single FA-M3.
- You can change the environment setup in each WideField3 application. Each
WideField3 application will operate according to its respective environment setup
until you exit from the application. When you initiate a new WideField3 application, it
uses the environment setup of the WideField3 application most recently terminated.
Procedure
(1) On the menu bar, click [File]–[Exit].
WideField3 exits.
CAUTION
If you attempt to exit from WideField3 with an extended tool (I/O module setup, device
manager, sampling trace tool, FA-M3 Defender) running, WideField3 will display the
following dialog box and abort exit processing.
You must exit from all extended tools before exiting from WideField3.
SEE ALSO
For details on the naming rules for in-CPU names and on-PC names, see Section A5.2,
"Naming Rules."
Table A5.1 CPU Modules That Support On-PC Names Different from In-CPU Names
CPU Type Limitations SEE ALSO
F3SP22-0S, On-PC names different from in-CPU names can be used. -
F3SP28-3S,
F3SP38-6S,
F3SP53-4S,
F3SP58-6S,
F3SP59-7S
F3SP66-4S, On-PC names different from in-CPU names can be used. -
F3SP67-6S
F3SP71-4N, On-PC names different from in-CPU names can be used. -
F3SP76-7N
F3SP71-4S, On-PC names different from in-CPU names can be used. -
F3SP76-7S
F3SPV3-4S, On-PC names must be the same as in-CPU names. -
F3SPV8-6S,
F3SPV9-7S
CAUTION
If on-PC names different from in-CPU names are used for a CPU module that
does not support using such names, an error occurs during syntax checking.
In such a case, specify the same names as in-CPU names for the on-PC names.
TIP
You can specify the same name as an in-CPU name for the corresponding on-PC name.
When you use file formats supported in WideField3 R2.04 and earlier, use the same names
between "in-CPU names" and "on-PC names".
SEE ALSO
Block/macro names used for instruction parameters must be on-CPU names.
For details on instruction parameters, see E1.2.18, "Entering Escape Sequences, Block/Macro
Names, and Label Names" (Offline).
Figure A5.2 File Names on a Personal Computer and the Corresponding Names in a
CPU
SEE ALSO
Some file names used on a personal computer must be the same as the project names. For
details, see A3.3, "List of Generated Files."
● Names in a CPU
The following file names are used in a CPU.
SEE ALSO
For details on other files that compose a project, see A3.3, "List of Generated Files."
Table A5.2 Naming Rules for On-PC Names and In-CPU Names
Name Type Rule Type Naming Rules
On-PC name File name A name of up to 80 characters
(excluding its file extension)
Available special The following characters can be used:
characters - "-" (hyphen)
- "_" (underscore)
- "@" (at sign)
- "( )" (parentheses)
- "#" (number sign)
- " " (space character, which cannot be used at the
beginning and end of a file name)
* All lowercase characters are converted
to uppercase characters.
In-CPU name File name An alphanumeric string of up to eight characters
beginning with two alphabets
(excluding its file extension)
Available special The following characters can be used:
characters - "-" (hyphen)
- "_" (underscore)
CAUTION
WideField3 reserves block names that begin with "WF3SYS."
If a block file with a block name that begins with "WF3SYS" is registered in a
component definition, an error occurs during syntax checking.
SEE ALSO
For details on language setup, see D1.3, "Language Setup" (Offline).
Table A5.3 Example of a Block File Name Duplicated with the Block Name of Another
Block
Block File Name Block Name Behavior
BLOCK_01 BLOCK01
BLOCK_02 BLOCK02
BLOCK01 BLOCK03 An error occurs during syntax checking because the
block file name "BLOCK01" is already used as an
existing block name.
Table A5.4 Example of a Block Name Duplicated with the Block Name of Another
Block
Block File Name Block Name Behavior
BLOCK_01 BLOCK01
BLOCK_02 BLOCK02
BLOCK_03 BLOCK01 An error occurs during syntax checking because the
block name "BLOCK01" is already used as an existing
block name.
Table A5.5 Example of a Macro Name Duplicated with the Macro Name of Another
Macro
Macro File Name Macro Name Behavior
MACRO_01 MACRO01
MACRO_02 MACRO02
MACRO_03 MACRO01 The macro name "MACRO01" is already used as an
existing macro name.
When a macro with this macro name is downloaded,
WideField3 downloads the macro found first.
Figure A5.3 On-PC Name of a File and Full Path to the File
- A Project folder
Up to 80 characters in length
- B On-PC name
Up to 80 characters in length (excluding the file extension)
- C Full path
Up to 255 characters in length (including the file extension)
SEE ALSO
- For details on the naming rules of on-PC names, see Section A5.2, "Naming Rules."
- For details on creating a new project, see D2.2.1, "Creating a New Project" (Offline).
TIP
When a project is created, various files related to the project are created in a folder with a
folder name that is the same as the project name.
In WideField3 R3 and later, even if this folder is copied by using Windows Explorer or the
folder name is changed, the project in the new folder can be opened.
- [File Name]
Specify an on-PC name for the block or macro according to the naming
rules for on-PC names. As in the case of WideField3 R2 and earlier, you
can specify the same name as the in-CPU name.
- [Block/Macro Name]
Specify a block name or macro name that is used in a CPU, according to
the naming rules for in-CPU names.
SEE ALSO
- For details on the naming rules of on-PC names, see Section A5.2, "Naming Rules."
- For details on creating a new block or macro, see D4.1, "Creating New Block and Macro
Files" (Offline).
TIP
The in-CPU names file stores the corresponding relationship between on-PC names, such as
a project file name and block file names, and in-CPU names such as an executable program
name and block names that are used when these files are stored in a CPU.
Figure A5.8 System Block Displayed in the Execution Block Components Screen
This manual describes useful functions that will help the user take full advantage of
WideField3.
Other CPU types that are not listed in the above table do not support stored
comments. Even for CPU types that support stored comments, comments will not
be stored to the CPU if programs are downloaded with the stored comments
option disabled.
WideField3 always uses I/O comment data stored with the tag name definition in
the project file created on the personal computer regardless of whether I/O
comment data is stored in the CPU. If circuit comment and subcomment data is
stored in the CPU, WideField3 uses the data for reconstruction on the PC. If not,
WideFiled3 uses the circuit comment and subcomment data saved in the project
file for reconstruction (see the figures below).
This chapter describes the various states of stored comment data (the concept of
reference for comment integration) and how modified comments are handled in
online operations.
If tag name definition and I/O comment data is stored in the CPU, a user may add
to or modify the data in the CPU online edit. The program monitor function,
however, makes such changes only to the project file and thus the changes are
not reflected in the tag name definition and I/O comment data in the CPU.
In addition, on a PC without the project file, tag name definition and I/O comments
are not displayed in the program monitor (the information cannot be
reconstructed in the program monitor) unless the program monitor is executed
after an upload operation.
It can be seen from this description that if comment data is edited from multiple
PCs, data may become inconsistent so it is necessary to keep information in the
CPU always up-to-date by downloading or consolidate and use the latest project
data.
If circuit comment and subcomment data is stored in the CPU, data can only be
modified or deleted. Addition is not possible. These online edited changes are
written immediately to the CPU. In addition, by reflecting the changes to the
project file, data integrity can be secured and ensured even if data is being
updated from multiple PCs.
If circuit comment and subcomment data is not stored in the CPU, the data is
combined with project data and reconstructed so comment data cannot be
reconstructed on a PC with no project file.
TIP
- The top tree name on the [online] tab of the [Balloon Comment List] window shows whether online
balloon comment and monitor data refers to the CPU or the data at the time of program download.
- If the CPU does not store balloons, offline balloon comment and monitor data at the time of the
download is referred to immediately after the program is downloaded. If the reference is "(When
Downloaded)", online balloon information is updated when the connection is disconnected.
Therefore, for the second and subsequent connections, the program monitor shows the online
balloon comment and monitor data at the time when the last connection was disconnected.
- If the CPU is not set to store balloon comment and monitor data, online balloon comment and
monitor data is not applied to the CPU even when online editing is done.
Regardless of whether balloon comment data is stored in the CPU, data can be
modified, deleted and added. However, to write balloon comments to the CPU,
online editing or downloading of balloons is required.
In addition, by uploading the changes within the CPU to the offline project file,
data integrity between the project file and the CPU can be secured.
If balloon comment and monitor data is not stored in the CPU, balloon comments
at the time of the program download are referred to. Therefore, balloon comments
cannot be reconstructed on the program monitor on a PC with no project data.
B01_13.VSD
The flowchart below shows the measures to be taken under various situations.
As shown in the above figure, if comment data is stored in the CPU, it can be
reconstructed by uploading but tag name definition and I/O comment data will be
current only as of the most recent download. If tag name definition or I/O
comment has been modified only on another PC, those changes cannot be
reconstructed by uploading as they were not updated in the CPU.
If comment data is not stored in the CPU, comment data can still be combined and
displayed on another PC by making use of data of the project file stored in the
Dwnload folder at the time of download. The procedure for restoring comment
data from data in the Dwnload folder is described on the next page.
Comment data can be reconstructed by copying block files, macro files (with
filename extensions of ".yblk" and ".ymcr"), tag name definition files (with
filename extensions of ".ycmn", ".ysig" and ".ymcs"), and balloon comment files
(with the filename extension of ".yblc") to the PC where monitoring is to be
performed.
Proc
cedure
(1) Create a new projec
ct on person
nal
computeer 'B'.
TIP
Specify the same projectp file name and
executable program name betweenn personal
computerrs 'A' and 'B'.
TIP
- In ste
ep (2) above, you
y can also rrestore comment data by up ploading the pprogram to pro
oject “AAA” on
n
perso onal computerr ‘B’. To resto re tag name I/OI comments s, you can alsso copy tag na
ame definition
n
files (filename
( exte
ension '.ysig') d
directly to the project after uploading.
u
- To up pload the project to person
nal computer ‘A’ into a diffferent project,, say “CCC”, create a neww
projeect “CCC” and perform stepp (2), substituting “personal computer B” w with “persona
al computer A””
in the
e instructions. The commen ts will be resto
ored after uplo
oading.
SEE AL
LSO
For detaails on how to
o store comm ents in a CPU, see Chaptter H2, "Downnloading" and
d Chapter H9,,
"Storing Comments an nd Tag Name Definitions" (O
Online).
IM 34M06Q
Q16-01E 6th Editio
on: Mar. 13, 2017-00
0
B2-1
CAUTION
- The Change I/O Installation Position function is not applicable to constant names
specifying slot numbers in READ/WRITE and HRD/HWR instructions. In this case,
modify the relevant constant specification in the constant definition, or change
instruction parameters directly.
- The Change I/O Module Installation Position function is not applicable to blocks
referring the common library or another project.
The Change I/O Installation Position function changes not only instruction
parameters in ladder programs but also tag name definition data.
When tag names are used in a ladder program and actual addresses are defined
in the tag name definition, you do not need to update the ladder program to
correspond to a change in the I/O slot position. It is only necessary to change the
actual addresses in the tag name definition.
TIP
Selecting [Project]–[Change I/O Installation Position] from the menu bar does not change I/O
installation positions for any blocks that refer to the common library or another project.
1 2 3 4 5 6
X X Y
D D D
Main unit 3 6 3
2 4 2
X X Y
D D D
Sub unit 1 3 6 3
2 4 2
B02_01.VSD
Procedure
(1) Select [Project]–[Change I/O
Installation Position] from the menu
bar.
The Change I/O Installation Position
dialog box opens.
(2) Enter the old slot number and the new
slot number, and click [OK].
TIP
To relocate more than one I/O module, specify
a range for the old and new slot numbers.
1 2 3 4 5 6 7
X X X Y
D D D D
3 6 6 3
2 4 4 2
B02_04.VSD
Procedure
(1) Select [Project]–[Change I/O
Installation Position] from the menu
bar.
The Change I/O Installation Position
dialog box opens.
(2) Enter the old slot number, the new
slot number and the number of slots
to be shifted, and click [OK].
The "Change I/O Installation Position -
Progress" dialog is displayed, followed by
another dialog box that notifies the
completion of slot replacement.
Procedure
(1) Select [Project]–[Change I/O
Installation Position] from the menu
bar.
The Change I/O Installation Position
dialog box opens.
(2) Turn on the [Specified Block] option
button in the [Replacement Range]
group box, and click [Browse].
TIP
The [Specified Block] option button is also
available when I/O modules are relocated or a
new I/O module is added.
TIP
Blocks referring the common library or other
projects cannot be selected. Such blocks are Step (3) B02_08.VSD
B02_09.VSD
Step (4)
To do this, use the [Circuit Display/Input] tab of the Set up Environment dialog
box.
There are two settings related to entering instructions and parameters.
- Instruction/Instruction Parameter Completion
- Parameter Direct Change Input Settings
Procedure ◆
(1) Select [Tools]-[Set up Environment]
from the menu bar.
The Set up Environment dialog opens.
B0301_01.VSD
Table B3.1 Input Options Available in [Parameter Direct Change Input Settings]
[Parameter Direct Change
Radio Button Input Operation
Input Settings] Checkbox
Command Use keys on the keyboard to enter instructions.
change has
priority
ON
Parameter The keyboard is used for input operation.
change has The cursor position determines whether the instruction or
priority the instruction parameter is modified.
Input operation is performed by selection on the
OFF — instruction palette, double-clicking an instruction, or
selection by the [Enter] key.
As a guideline, turn on the checkbox when the keyboard is mainly used to enter and
modify instruction/instruction parameters.
Use the following procedure to customize what input method is selected in the program
edit screen when using alphanumeric keys on the keyboard.
Procedure ◆
(1) Select [Tools]-[Set up Environment]
from the menu bar.
The Set up Environment dialog opens.
B0301_02.VSD
Procedure ◆
(1) Place the cursor over the position
where an instruction is to be entered.
SEE ALSO
For details of mnemonics, see "Sequence CPU – Instructions."
B0302_03.VSD B0302_04.VSD
B0302_05.VSD
B0302_06.VSD
To edit connection lines, use the function keys and special keys as connection lines has
no mnemonics. The following function keys are available for editing connection lines.
SEE ALSO
For details on how to set up the input completion function, see Section B3.1.1, "Setting up
Instruction/Instruction Parameter Completion."
Procedure ◆
(1) Move the position cursor to where an
instruction is to be inserted.
SEE ALSO
After the first character is entered, you can
press the [] key to display a list of
instructions.
SEE ALSO
For details on how to set up the input completion function, see Section B3.1.1, "Setting up
Instruction/Instruction Parameter Completion."
Procedure
(1) Enter an instruction, or select an
instruction of which the parameter is
to be changed, to display the Enter
Instruction or instruction parameter
setup dialog.
Step (1) B0302_09.VSD
SEE ALSO
When entering an instruction parameter, you
can select to use the [] key, instead of
entering any character, to display tag
names/address and select one of them.
B0303_01.VSD
Place the cursor over the instruction to be modified and enter a new mnemonic.
In the Enter Instruction dialog, you have to enter the mnemonic. Then press the [Enter]
key.
B0303_02.VSD
B0303_03.VSD
TIP
There is no special key for inverting the double-long-word instruction.
SEE ALSO
For details on how to set up the direct parameter modification input function, see Section B3.1.2,
"Setting up Parameter Direct Change Input."
Procedure
(1) Place the cursor over the instruction
parameter to be modified.
Step (1) B0304_01.VSD
SEE ALSO
For details on how to set up the direct parameter modification input function, see Section B3.1.2,
"Setting up Parameter Direct Change Input."
Procedure
(1) Place the cursor over the instruction
parameter to be modified.
Step (1) B0304_04.VSD
TIP
If you have set multiple message dialogs to be hidden, selecting [Display Hidden Message Dialog
Boxes] affects all the messages, allowing them to appear again.
The method for creation and invocation is the same for both macro types. To
create a macro, select [File]–[New] from the menu bar, select [Macro] in the
displayed New dialog box and edit the macro in the same way as editing a block.
To call a macro, use the MCALL instruction.
Macros can be shared among users, but should not use devices that are used by
other blocks or macros. We describe below how to use devices effectively in
macros.
B05_01.VSD
Figure B5.1 Distribution of Devices between Blocks (upper) and Macros (lower)
B05_02.VSD
Figure B5.2 Distribution of Devices between Macro 1 (upper) and Macro 2 (lower)
CAUTION
When using local devices in function macros, note the following precautions. If the same
macro must be used in multiple locations, change the name of the macro. As local
devices are allocated on a macro basis, calling the same macro in multiple locations
causes device overlaps during execution.
B05_03.VSD
Figure B5.3 Example of Improper Use of the Same Macro at Multiple Locations
B05_04.VSD
Figure B5.4 Example of Proper Use of the Same Macro at Multiple Locations
B05_05.VSD
Figure B5.5 Invoking Macros (lower) from Blocks (upper) by Specifying Pointers as
Beginnings of Devices
CAUTION
If another personal computer downloads a program to the same CPU that is connected
online to WideField3 on your personal computer, WideField3 may no longer operate
normally. In this case, disconnect your WideField3 from the CPU by selecting [Online]–
[Disconnect], and then reconnect to the CPU by selecting [Online]–[Connect] from the
menu bar.
- A
List data items to be shared among blocks. Classify the devices into global
and local areas according to the number of such data items.
Allocate addresses of global devices (e.g., D00001) to data items to be shared
among blocks.
Use local devices (e.g., /D00001) for data items that are to be used only within
a block.
D00001
Block 1 Block 2
Global area
Local Local
data data
Global data
Local Local
data data
D32768
B06_01.VSD
- B
Create a new common project for all blocks. Perform common setup that
applies to all blocks, including project setup/configuration, common tag name
definition, constant definition, user log messages. In the project
setup/configuration, set up the global and local areas as determined in step A
above.
Overall project
Project setup/configuration
Common tag name definition
Constant definition
User log message
Project setup/configuration
Copy
Common tag name definition
Constant definition
User log message
Block A
Project setup/configuration
Copy
Common tag name definition
Constant definition
User log message
Block B
B06_02.VSD
Figure B6.2 Common Project and Block-specific Projects for Each Developer
- D
Each developer creates blocks assigned to him and creates dummy interface
blocks to test and debug interfaces with other blocks.
- E
Each developer transfers his blocks to the FA-M3 and debugs them. After
finishing debugging of a block, he writes it to the common project created in
step B by selecting [Project]–[Insert File] from the menu bar, or using the
Windows Explorer function.
- F
Combine all debugged blocks in the common project, and transfer the project
to the FA-M3. Perform integration tests to debug the entire project.
- G
During the integration test, multiple developers may perform debugging, as
well as perform online-editing on the same CPU concurrently.
CAUTION
To transfer the online-edited data to the CPU, first convert the program by selecting
[Edit]–[Convert] from the menu bar, and then exit online editing by selecting
[Debug/Maintenance]–[End Online Editing] from the menu bar.
While a developer is transferring his online-edited data to the CPU, other developers
cannot convert their programs, or exit online editing in WideField3.
When multiple developers are online-editing a program concurrently, it is important to
know that once a developer transfers his online-edited changes to the CPU, the existing
program in the CPU will no longer be the same as the programs currently edited by the
other developers.
When multiple developers are online-editing a program concurrently, only the first
developer who stores balloons in the CPU can continue to do so. Note that for the other
developers to store balloons later, they must first reload balloons from the CPU.
Block AA
Project D
Refer Block AA
Refer
Register
Refer Project C
Project A
Block AA
Block AA
Project B
Block AA
B0701_01.VSD
SEE ALSO
For details on the common library folder settings, see Section D1.2.2, "Folder Setup" (Offline).
Procedure ◆
(1) In the Project Settings/Configuration
window, select [Executable Program
Settings]-[Execution Block
Components] in the tree.
SEE ALSO
For details on how to open the Project
Settings/Configuration window, see Section
D3.1, "Building a Project" (Offline).
TIP
If a block file with the same name is already
present in the common library, a warning B0701_03.VSD
Step (3)
message is displayed. To overwrite the block,
click [OK]. To cancel the operation, click
[Cancel].
Procedure ◆
(1) In the Project Settings/Configuration
window, select [Executable Program
Settings]-[Execution Block
Components] in the tree.
SEE ALSO
For details on how to open the Project
Settings/Configuration window, see Section
D3.1, "Building a Project" (Offline).
TIP
An "*" in the [Ref] column indicates the block
is referred to by another project.
TIP
The same procedure applies when registering
blocks in reference folders.
Procedure ◆
(1) In the Project Settings/Configuration
window, select [Execution Block
Components] in the tree.
SEE ALSO
For details on how to open the Project
Settings/Configuration window, see Section
D3.1, "Building a Project" (Offline).
B0701_06.VSD
Steps (2) and (3)
Procedure ◆
(1) In the Project Settings/Configuration
window, select [Protection Settings] in
the tree.
SEE ALSO
For details on how to open the Project
Settings/Configuration window, see Section
D3.1, "Building a Project" (Offline).
B0702_02.VSD
CAUTION
TIP
To cancel protection, clear both [New Password] and [Confirm Password] boxes in the Set up
Password dialog (i.e., leave the boxes blank), and click [OK].
Procedure ◆
(1) In the Project Settings/Configuration
window, select Common Tag Name
Definitions/Local Device in the tree.
SEE ALSO
For details on how to open the Project
Settings/Configuration window, see Section
D3.1, "Building a Project" (Offline).
SEE ALSO
For details on how to change maximum
number of common tag name definitions, see
Section E2.6, "Changing Maximum Number of
Common Tag Name Definitions and Storing to
CPU" (Offline).
Procedure ◆
(1) In the Project Settings/Configuration
window, select Common Tag Name
Definitions/Local Device in the tree.
SEE ALSO
For details on how to open the Project
Settings/Configuration window, see Section
D3.1, "Building a Project" (Offline).
This manual describes how to solve problems that might occur in WideField3.
C01_01.VSD
C01_02.VSD
CAUTION
C01_03.VSD
Figure C1.3 SCB Uses Slot 2, and Normal Blocks Use Slots 3 to 5 on Unit 0
SEE ALSO
- For details on multi-CPU systems, see "Sequence CPU – Functions."
- For details on the project settings/configuration, see Section D3.1, "Building a Project" (Offline).
- For details on the procedure for referring to the I/O settings of other CPUs, see Section D3.1.13,
"Inter-CPU Shared Memory Setup" (Offline).
C02_01.VSD
If you wish to continue the connection, you can check the cable and/or switch off
and then switch on the FA-M3, and click [Yes] on the error message dialog box.
This recovery measure may remove the cause of the error and allow you to
continue operation (this measure will not work if the CPU communications mode
before power off is changed after power on).
It is recommended that you click [No] to disconnect (all monitor windows will
close automatically), check the communications cable, and reconnect online
again by selecting [Online]–[Connect] from the menu bar.
If the power supply to the FA-M3 is inadvertently turned off during Ethernet
communications, always click [No] to disconnect. If you click [Yes] in this case, a
communications error will again be generated due to connection processing
between the personal computer and the Ethernet interface module.
In the case of USB communications, the USB driver recognized by the PC may
enter into an unknown state. If connection cannot continue, check the USB cable
and/or switch off and then switch on the FA-M3, or disable and then enable the
FA-M3 USB driver using Windows device manager.
TIP
When you select [Edit]–[Convert] from the menu bar to convert a program during online-editing, and
then select [Debug/Maintenance]–[End Online Editing] from the menu bar to terminate online editing,
online connection is terminated only after the converted program is successfully transferred (the CPU
is notified of the program transfer status).
If WideField3 is forced to terminate, or the FA-M3 is switched off, or the communications cable is
disconnected during the conversion or transfer, you must switch off and then switch on the FA-M3.
Try to ensure that the above events do not occur during conversion or transfer.
If protection is enabled for the connected CPU, operation cannot continue even if you select [Yes] on
the communications error message dialog box even though reconnection may seem to be successful.
You should disconnect by selecting [No] on the communications error message dialog box and then try
to reconnect.
C3. Troubleshooting
This chapter describes some common problems that you may encounter when
using WideField3, and how to perform troubleshooting.
This chapter suggests some standard measures to troubleshoot various problems but
these remedial measures may not always work.
Communications Failure
Others
CPU error after download
What happened?
Error at download
Reset CPU
Check CPU properties
No problem
Errors
Upload CPU properties from amended
CPU and edit again
No
OK?
Yes
END
C03_03.VSD
C03_04.VSD
Figure C3.4 Windows Security Alert
C03_05.VSD
2. Select and open Windows Firewall from the Windows Security Center screen.
C03_06.VSD
C03_07.VSD
4. Click the Exceptions tab and perform setup as shown in the following screen.
C03_08.VSD
Figure C3.8 Windows Firewall
C03_09.VSD
C03_10.VSD
CAUTION
The Mailer program to be invoked is defined in the [E-mail] field on the Programs tab of
the Internet Options dialog box of the Internet Explorer software.
C04_01.VSD
TIP
To display the Internet Options dialog box, select [Internet Options] from the Internet Explorer software
or Windows control panel.
Procedure
(1) Select [Tools]–[E-mail to Technical
Support] from the menu bar.
The mailer program is started and a
screen for creating a new E-mail is
displayed.
TIP
The E-mail address of Yokogawa’s Technical
Support Center is displayed in the destination
address field by default.
If any of these problems occur, you can probably resolve them by editing the
antivirus security software settings. We recommend that you consult the
information security administrator in your organization to arrange for this.
You can avoid this problem by excluding the folders and files used with WideField3 from
the targets of real-time scanning.
TIP
Depending on the antivirus security software you are using, real-time scanning may be called real-time
inspection, real-time scan, or on-access scan instead.
The "exception" settings may also be called "exclusion" settings instead. For details, check the
antivirus security software you are using.
We recommend that you specify the following folders and files as the exception settings
for real-time scanning.
Table C5.1 Folders that should be specified as the exception settings for real-time scanning
Type Folder name
Program folder C:\Program Files\WideField3
Share folder C:\Program Files\Common Files\Yokogawa\FAM3
Project folder C:\Users\Public\Documents\Yokogawa\FA-M3\Fam3pjt
Work folder C:\Users\Public\Documents\Yokogawa\FA-M3\Fam3tmp
Shared data folder C:\Users\Public\Documents\Yokogawa\FA-M3\Fam3com
Macro folder C:\Users\Public\Documents\Yokogawa\FA-M3\Fam3mac
Library folder C:\Users\Public\Documents\Yokogawa\FA-M3\Fam3lib
Table C5.2 Files that should be specified as the exception settings for real-time scanning
Type Folder name
WideField3 program C:\Program Files\WideField3\WideField3.exe
C:\Program Files\Common Files\Yokogawa\FAM3\mcomsrvex.exe
Applications for FA-M3 C:\Program Files\Common Files\Yokogawa\FAM3\McomSetup.exe
communication C:\Program Files\Common Files\Yokogawa\FAM3\McomSetupMng.exe
C:\Program Files\Common Files\Yokogawa\FAM3\McomSetupDisp.exe
TIP
Replace the folder name specified as "C:\Program Files" above with the name of the actual folder used
in the environment in which WideField3 is installed.
- If you have installed the folder or file under a disk drive other than the C drive:
Replace "C:\Program Files" with "D:\Program Files".
- If you have installed the folder or file in a 64-bit operating system (OS):
Replace "C:\Program Files" with "C:\Program Files (x86)".
- If you have installed the folder or file by specifying a folder other than the default folder:
Replace "C:\Program Files" with the name of the specified folder.
FA-M3
Programming Tool WideField3
Introduction and Troubleshooting
IM 34M06Q16-01E 7th Edition
T
tag name ........................ A3-20,D3-65,D3-66,D3-67,
D3-78,E1-12,E1-43,E1-94,E1-98,E2-29,
J2-27,J2-28,J4-3
tag name definition ...... A1-6,A1-7,A1-8,A1-9,A3-20,
D3-78,E1-95,E2-1,E2-6,E2-24,E8-47,F4-18,
H2-10,H3-8,H9-3,J2-28,J4-1,K2-21
Tag Name Definition Monitor .............................. J4-1
Temporarily change communication speed ........ J1-7
Tile…................................................................ A3-17
title….. .................................. A3-20,D2-9,D3-5,D4-11
toolbar ............................................ A3-2,D1-26,H8-3
U
Undo… .................................................. A3-13,E1-69
upload ......................... D3-81,H1-2,H3-3,H3-6,H3-8,
H5-4,H5-11,H8-4,H9-9,H13-5
USB… .................................... A2-2,A4-9,D1-12,H1-3
Used Device ...................................................... E5-9
user authentication ........................................ H11-28
user log message ............. A3-15,A3-18,D2-8,D3-29,
K3-15
Revision Information
Title : FA-M3 Programming Tool WideField3 - Introduction and Troubleshooting User's Manual
Document No. : IM 34M06Q16-01E