WWW.NNC.IR
Basic Knowledge For Macro Customize Functions
196
Vision System FH/FZ5 Series
User’s Manual (Z340)
Standard IO commands
When the same command name / command id of standard IO commands are used for customize IO
commands, customize IO command has the priority and the standard IO commands are not executed.
If you execute the standard IO commands after execution of customize IO commands, please add the line as
below.
In this case, standard IO commands is executed just after executing customize IO command.
Calling the procedure defined on the other commands
It is possible to call the procedure defined on the other commands during the command execution.
Each command has "Function name", and it is used to call the procedure.
Example: When command is defined as the table below and we intend to call procedure of CMD0 from CMD1,
the codes for CMD1 should be like this:
This case, the behavior of the command like BUSY depends on the caller (CMD1), and BUSY stays ON until
the end of the procedure.
Define the different procedure according to I/O module
The variable IoIdent$ stores the IO module identification name, which received the current I/O command.
When you define the different procedure for each I/O modules, please make branch by the value of IoIdent$.
Example: The command which receives "Serial" for serial command, and "Ethernet" for UDP normal
CommandExecute&=False
Command No. Command name Busy Function name
0 CMD0 False FUNC0
1 CMD1 True FUNC1
Gosub *FUNC0
Please be careful not to make the commands calling each other (In the case above, CMD0 also calls FUNC1), because
it makes infinite loop.
If IoIdent$ = "SerialNormal" Then
Response$ = "Serial"
Elseif IoIdent$ = "UdpNormal" Then
Response$ = "Ethernet"
Endif