WWW.NNC.IR
Basic Knowledge For Macro Customize Functions
250
Vision System FH/FZ5 Series
User’s Manual (Z340)
Troubleshooting during regular operation
Problems that are commonly encountered when using the macro customize functions in regular operation are
described below, along with the actions to take.
A specific program line does not
execute
It is possible that a statement
and a comment are written on
the same line.
A statement is sometimes not executed correctly when
written on the same line as a comment.
Write the comment on a separate line.
It is possible that release mode
is specified in the Debug
function.
When release mode is specified in the Debug function,
functions such as the Stop function and DebugPrint
function are not enabled.
Execute the Debug function to change from release
mode to debug mode.
Reference:
How to Use the Debug Function (p.235)
Problem
Cause
Action
An error message appears in the
system status console window
An error occurred when the
program was executed.
Check the error message and correct the error.
Reference:
If it is difficult to identify the error, use Debug to
determine the cause and correct the error.
Reference:
How to Use the Debug Function (p.235)
A standard communication
command does not execute
The name of a command
created with the communication
command macro may be the
same as the name of the
standard communication
command.
If the name of a command created with the
communication command macro function is the same
as the name of a standard communication command,
the command created with the communication
command macro is given priority.
Change the command name to a name that is different
from the standard communication command.
Communication command
macro settings cannot be
applied to another sensor
controller
It is possible that only backup
data (.bkd) is loaded in the other
sensor controller.
Communication command macro settings cannot be
saved in backup data (.bkd). Load the settings file
(.mcr) that was saved by executing [Save] in the setting
screen of the communication command macro tool into
the other sensor controller separately from the backup
data (.bkd).
To load the settings file (.mcr) in the other sensor
controller, execute [Load] in the setting screen of the
communication command macro tool of that sensor
controller.
The communication command
macro settings cannot be saved.
You may be attempting to save
the settings with [Save to file].
The communication command macro settings are not
saved in the backup data (.bkd). Consider one of the
following methods:
• Execute [Data save].
• Execute [Export] in the setting screen of the
communication command macro tool.
Measurement flow settings that
were saved are cleared after
restart
It is possible that the *SaveProc
subroutine is written in the scene
control macro program.
When the *SaveProc subroutine is written, only the
process written in the *SaveProc subroutine is
executed when [Data save] is executed or scene data is
saved. For this reason, overall scene data changes are
not saved in the way they are when regular [Data save]
or [Save to file] is executed.
Delete the *SaveProc subroutine.
Problem
Cause
Action
Summary of Contents for fh-1 series
Page 8: ...WWW NNC IR 6 Vision System FH FZ5 Series User s Manual Z340...
Page 14: ...WWW NNC IR 12 Vision System FH FZ5 Series User s Manual Z340 MEMO...
Page 22: ...WWW NNC IR 20 Vision System FH FZ5 Series User s Manual Z340 MEMO...
Page 48: ...WWW NNC IR Initializing the Controller 46 Vision System FH FZ5 Series User s Manual Z340 MEMO...
Page 68: ...WWW NNC IR Editing Scene Groups 66 Vision System FH FZ5 Series User s Manual Z340 MEMO...
Page 881: ...WWW NNC IR...