VMI VVS OL82 - Page 25

VMI_OPCSERVER_WRAPPER.INI definitions
No. Legend Description
1 Comment lines
All lines starting with a semicolon (;) are interpreted as comment (non active
program lines). These lines can be deleted without consequences.
2 General section
In the general section the IDs of the OPC Server and the configuration file are
defined.
OPC_SERVER_
NAME
Specifies the OPC Server name.
OPC_SERVER_
CONFIG_FILE
Specifies the OPC Server configuration file name.
3 Product sections
In a wrapper file there are 6 product sections with the following titles:
● [BREAKER1]
● [BREAKER2]
● [BREAKER3]
● [BREAKER4]
● [CARCASS]
● [TREAD]
The product sections define the addressing of the PLC. The channel and device
name must be valid in all product sections.
For each PLC type there is a command, parameter, and status address line.
For more information, refer to the paragraph OPC Server wrapper address
definition on page 3 ‑ 8.
COMMAND_
ADDRESS
Specifies the command address line.
PARAMETER_
ADDRESS
Specifies the parameter address line.
STATUS_
ADDRESS
Specifies the status address line.
The ACTIVE statements tell VVSX what components (conveyors) are part of
the system and what (parts of the) sections have to be read. When the ACTIVE
statement is set to 1, the component tag must be read by VVSX.
COMMAND_
ACTIVE
Always 1.
PARAMETER_
ACTIVE
0 if you use the parameter handshake (command buffer bit 8).
1 if you do not use the parameter handshake (currently
standard)
STATUS_ACTIVE Always 0.
Status information is always send from VVSX to PLC, so this
bit is always 0 (false).
Check the Active statements of all components.
INSTALLATION AND CONFIGURATION
Configuration
3
THINKING FORWARD
VMI Vision System VVS (OL82) VVSX 13.0.12.0, VVSU 3.0.6 / 4 / 2016-07-11 / pd#175592
3-7