ISRA OPC UA Server Module - V2.1.4 - Eng

SMASH
Web Inspection System

ISRA OPC UA Server Module
Version 2.1.4
Original - May 2018,

Language: English
Copyright
© Copyright ISRA VISION GMBH, Darmstadt, Germany, including all affiliated
companies.
All rights reserved.
The system described in this documentation and its software, drawings,
electrical documentation and schematics are the intellectual property of
ISRA VISION GMBH and all subject to copyright and other intellectual property
protection. The objects of this documentation may not be copied or otherwise
communicated or used for commercial use or distribution, either in part or in
their entirety, nor may these objects be modified without the express written
consent of ISRA VISION GMBH.
This documentation is only intended for the use of the operating authority and
its personnel.
We have taken the greatest of care in the preparation of this document.

ISRA VISION GMBH accepts neither liability nor any form of legal responsibility
for erroneous information or its consequences. Should you identify any errors,
we would nevertheless be grateful if you were to inform us of them immediately.
Reading and using this document imply cognizance of the above conditions and
stipulations.
ISRA VISION – Part of Atlas Copco Group
Manufacturer
Product SMASH
Title of Documentation SMASH

Version of Dokumentation 2.1.4
Last Change 28September2023
Created by ES
2 SMASH – ISRA OPC UA Server Module

Table of Contents
Copyright ............................................................................................... 2
Table of Contents.................................................................................. 3
1 Introduction ..................................................................................... 6
1.1 Overview ...................................................................................................... 6
2 Program Options ............................................................................. 7
2.1 Data Monitor ................................................................................................. 7
2.2 System Settings Tab .................................................................................... 9
2.2.1 Central Connection .......................................................................... 9
2.2.2 Password ......................................................................................... 9
2.2.3 Tag Group Enables........................................................................ 10
2.3 Options Tab ................................................................................................ 10
2.3.1 Defect Tag Options ........................................................................ 10
2.3.2 Parameter Control Options ............................................................ 11
2.3.3 Flag Tag Options ........................................................................... 11
2.3.4 Position Synchronization ............................................................... 12
3 OPC Configuration ........................................................................ 13
3.1 Running the Program ................................................................................. 13
3.2 Running the Program as a Service ............................................................. 13
3.3 Changing the Default Port .......................................................................... 13
3.4 Example Client Connection ........................................................................ 14
3.5 Certificate Usage ........................................................................................ 15
3.5.1 Enabling Certificate Creation ......................................................... 15
3.5.2 Creating a Certificate ..................................................................... 15
3.5.3 Using the Certificate ...................................................................... 16
4 OPC Data items.............................................................................. 17
4.1 Alarm Statistics Data .................................................................................. 17
4.2 App Data .................................................................................................... 17
4.3 Bank Info Data............................................................................................ 18
4.3.1 Bank Video Statistics Data............................................................. 18
4.3.2 Camera Video Statistics Data ........................................................ 18
4.4 Classifier Data ............................................................................................ 20
4.4.1 Logic flow ....................................................................................... 20
4.4.2 Current Classifier Fields ................................................................ 20
4.4.3 Next Run Classifier Fields ............................................................. 21
4.4.4 Class Constraints Indices Table .................................................... 23
4.5 Control Data ............................................................................................... 24
4.6 Defect Data ................................................................................................ 25
4.7 Defect Control ............................................................................................ 27
SMASH – ISRA OPC UA Server Module 3

4.8 Defect JSON Format .................................................................................. 28

4.9 Edge Analyzer Data.................................................................................... 29
4.10 External Data .............................................................................................. 30
4.11 External Event Data .................................................................................... 30
4.12 Flag Data .................................................................................................... 31
4.13 Image Export Data...................................................................................... 33
4.14 Inspection Settings Data ............................................................................. 34
4.15 IO Data ....................................................................................................... 36
4.16 Lane Data ................................................................................................... 37
4.17 LED Data .................................................................................................... 39
4.18 Metal Detector Data .................................................................................... 40
4.19 Production Data .......................................................................................... 41
4.19.1 This Run Product Fields ................................................................. 41
4.19.2 Next Run Product Fields ................................................................ 43
4.19.3 Last Run Product Fields ................................................................. 44
4.19.4 Change Product Fields .................................................................. 45
4.20 Reclassify ................................................................................................... 46
4.20.1 Processing flow .............................................................................. 46
4.21 RunData Data ............................................................................................. 47
4.22 Segment Data............................................................................................. 48
4.22.1 Segment.Last Data ........................................................................ 48
4.22.2 Segment.Current Data ................................................................... 49
4.23 Segment Table Data ................................................................................... 50
4.24 Statistics Data............................................................................................. 51
4.24.1 Class Statistics Data ...................................................................... 51
4.24.2 Lane Statistics Data ....................................................................... 52
4.25 Sync Data ................................................................................................... 53
4.25.1 Synchronization input configuration ............................................... 53
4.25.2 OPC Sync Settings ........................................................................ 53
4.25.3 Synchronization Logic .................................................................... 54
4.26 System Data ............................................................................................... 54
4.27 System Parameters .................................................................................... 54
4.28 System Recipe CRC’s ................................................................................ 56
4.29 System Configuration Information .............................................................. 56
4.30 Trend Graph Data....................................................................................... 57
4.30.1 Last Trend Data ............................................................................. 57
4.30.1 Current Trend Data ........................................................................ 58
4.30.2 EOR Trend Data ............................................................................ 58
4.31 Video Analysis Data ................................................................................... 59
4.32 Winder Data................................................................................................ 59
5 Metal Detector Option .................................................................... 61

5.1 Detector Layouts ........................................................................................ 61

5.1.1 Single detector row ........................................................................ 61
5.1.2 Dual detector row - ½ Overlap ....................................................... 61
5.1.3 Dual detector row - ⅓ Overlap ....................................................... 62
5.2 Metal Defect Tags ...................................................................................... 63
5.2.1 Data Exchange Sequence with Handshaking ................................ 63
5.3 Metal Detector Options Tab........................................................................ 64

1 Introduction
1.1 Overview
The OPC UA Server module allows a client program to communicate with the
Main Inspection system via an OPC connection. The Client can send
parameters and can send messages to control the inspection of the system.
Data can also be transmitted to the Client.
Figure 1-1 Overview

2 Program Options
2.1 Data Monitor
OPC server tags can be added to the Data Monitor to allow the user to check
tag values.
Data Monitor Notes:
1. OPC Tags do not need to be added to the data monitor to be accessible by an
OPC client.
2. The value of an OPC tag can be monitored even if there are no OPC Clients
accessing the tag.
Figure 2-1 Data Monitor
The system is placed into Configuration mode by clicking the Setup Data
Monitor checkbox at the bottom of the Data Values page.
The configuration buttons allow the user to add/delete items or arrange the
order the items are displayed. The user can access the properties of each of the
items on the main screen by double clicking the item.

Tag Properties
Figure 2-2 Tag properties
 Description – this should describe the tags usage.

 OPC Server tag identifier - This is the Tag name in the OPC server. The
Browse button will show all available OPC server tags.
Browse dialog
 The browse dialog will show all the available tags. The group filter will show
tags from the selected group. The Search field will show only those tags
matching the characters that have been typed in. The wildcard * character
can be used to find any string that contains the contents of the search string.
For Ex: Search for “*Roll Number” and the list will show all tags containing
the text “Roll Number”.
Figure 2-3 Browse dialog

2.2 System Settings Tab
Figure 2-4 System Settings
2.2.1 Central Connection

Typically, the OPC server runs on the inspection PC and the OPC Client runs on a
customer PC. The OPC Server can be installed on the customer PC and the
Inspection PC’s name or IP address can be set.
Note
The OPC Server communicates to the Inspection Program through port 13000.
Note
If the OPC Server is configured to run on the customer PC, then that Customer
PC can only support 1 inspection system. This is because the OPC Server can
only make 1 connection to 1 Inspection PC.
2.2.2 Password
 The password will protect the OPC Server configuration options.

2.2.3 Tag Group Enables

The user can enable/disable groups of tags. This can be used to tune the
performance of the OPC Server. For example, if the OPC Client does not need
defect data, then it does not make sense to support the defect data fields. This
will keep the Inspection Program from sending defect data to the OPC server so
that it can post the values.
2.3 Options Tab
Figure 2-5 Settings
2.3.1 Defect Tag Options

 Defect data transfer mode – The defect control is used to set the mode of
transferring defects to a client. The transfer rate controls how fast defects
will be sent. If the client is busy and does not retrieve the defect data, then it
is overwritten and the defect is not read by the client. For systems where all
defects need to be processed a handshaking approach can be enabled. See
the Defect Control section for additional information.
 Post defect if criteria – this option can be used to only post those defects
that match a specific feature range or value. Defects that do not meet the
criteria will not be posted.

 Limit defect queue size to – this option will limit the number of defect
queued up for transfer. Once the queue size is exceeded older defects will
be removed from the queue to bring the queue under the limit. This can be
used to control the queue during periods of high defect rates.
 Transfer Rate – This is the rate that defects will be transmitted when the
transfer mode is set to Continuous mode.
 Handshake timeout – The handshaking Defect Ready flag will be reset
automatically and the next defect sent if the client side does not reset it
within the handshake timeout time.
 Transfer up to n defects per JSON output – This option is available if the
defect data transfer mode is set to JSON format. The JSON format sends
multiple defects at one time as a JSON string and this setting controls the
maximum number to be sent at one time.
2.3.2 Parameter Control Options

 Update lane states every n seconds – This is the rate that the system will
post the values for the Stats.Current.Lane x.State tags.
 Lane control mode - This option controls how the lane data is handled.
o None – lane data can be set by Central and the OPC module.
o Central controls the lanes – in this mode the lane data is set from Central
and is available via OPC. If the OPC module attempts to set the lane
values, then they will automatically be set back to the values from
Central.
o OPC controls the lanes - in this mode the lane data is set from the OPC
module. If the user attempts to set the lane values in the Lane setup
dialog they will be warned and the settings will automatically be set back
to the values contained in the OPC module.
 Class mode - This option controls how the classifier data tags are handled.
o None – class data can be set by Central and the OPC module.
o OPC controls the class data - in this mode the class data is set from the
OPC module. If the user attempts to set the class values in the classifier
setup dialog the settings will automatically be set back to the values
contained in the OPC module.
2.3.3 Flag Tag Options

 Defect Flagger mode - This option controls the usage of the defect flagger
tags.
o Support flag data – flagger information will be posted to the flag tags.
o Support flag tags with external flag data – as a defect flag is
generated the tag flags will be populated with the flag information. The
customer can then send information to be associated with the tag and
the tag will be updated with the customer supplied data. A typical usage
for this feature is the inspection program alarming on a defect which
applies a barcode to the product and then a barcode scanner reads the
barcode on the product and sends the data to the inspection program via

OPC. In this case the flag event from the alarm will be assigned the
barcode data that was read.
o Support external data only – this option can be used to receive
external data. The data is sent to the inspection program and can be
associated with a defect and/or create a flag event. A typical usage for
this feature is using a barcode scanner to read a barcode that was
already applied to the product and sending the data to the inspection
program via OPC.
 External flag data transfer timeout – In the “Support flag tags with
external flag data” mode the server will set the flag tag data to “NA” if the
customer does not send the external data within this MD distance.
 Hold distance – In the “Support external data only” mode the data can be
assigned to a defect. The inspection program will hold the external data for
this period of time and each defect will use the data value that is closest to it
based on the MD position.
 Store external data in - this will set the external feature for each defect
based on the external data that has been read. Each defect will use the
external data value that is closest to it based on the MD position.
 Create flag data in inspection program – this option will create a flag data
for each external value read and this data can be shown on the roll map and
other data displays.
2.3.4 Position Synchronization

Position synchronization will adjust the inspection system position based on a position
sent from the production line. The production line will assert a discrete input on the
inspection system when the production line position is given so that the two positions
are captured at the same point in time. See the Sync Data tags section for additional
information on position synchronization.

3 OPC Configuration
3.1 Running the Program
The OPCUAServer.exe program is located in the folder D:\OPCUAServer\.
Once the program is started an OPC UA Client can connect to it and configure
its tags.
On starting the program, the server will make a connection to the Central
Inspection Program and start sending/receiving information. This will happen
even if there are no OPC clients attached to the server.
3.2 Running the Program as a Service

Batch files are located in the D:\OPCUAServer\ folder to support running the
program as a service.
1. Service Install.bat – will add the program to Windows services.
2. Service Start.bat – will start the service and set the service to startup mode to
Automatic. In this mode the OPCUAServer program will automatically start on each
PC startup.
3. Service Stop.bat – will set the service start mode to manual. In this mode it will not
startup automatically on each PC startup.
4. Service Remove.bat – will remove the program from Windows services.
Note:
Only one instance of the program is allowed to run at a time.
3.3 Changing the Default Port

The default port for ISRA OPC UA is 48010.
The port is specified in the file D:\OPCUAServer\ini\ServerConfig.xml. To
change the default port value open the file in notepad and search for 48010 and
change all occurrences of it to the desired port.

3.4 Example Client Connection

This example test client will discover servers residing on the PC at this IP
address. The default port for ISRA OPC UA is 48010 and must be specified.
Figure 3-1 Enter URL
Upon connection the test server shows the available tags
Figure 3-2 Available tags
The server will accept an anonymous authentication, a valid windows user and
password, or a certificate. The default user is isra with password vision.

3.5 Certificate Usage

To use a certificate, the server needs to generate the certificate files that the
OPC UA client will need.
3.5.1 Enabling Certificate Creation

The ability to create a certificate is normally disabled and should only be
enabled during configuration and the disabled again. Otherwise if someone
were to inadvertently create a new certificate the existing client would then
have an invalid certificate and would be unable to connect.
In the settings file D:\OPCUAServer\ini\OPCUAServer.ini set the enabled key to

1 and restart the OPCUAServer. When enabled there will be a “Create
Certificate” button on the settings page.
[StoreConfig]
Enabled=1
Note: If this is an older version being updated then some values in the file
D:\OPCUAServer\ini\ServerConfig.xml need to be modified.
Open the file in notepad and search for the word UaSdkCppBundleEval and
replace it with ISRAOPCUaServer. There will probably be 8 to 10 places it
needs to be changed.
3.5.2 Creating a Certificate

Click the “Create Certificate” button. The program will prompt the user to create
a new certificate.
Click “Yes” and the certificate will be created. The program will show this dialog
confirming that it was created and will make a copy for customer use in the
D:\OPCUAServer\Certificate\ folder.

3.5.3 Using the Certificate

In this client test program the authentication was set to certificate and the two
files created are set.
The first time encountering this new certificate the test client will prompt the
user to accept the trust the server certificate. Once that is done the client will
connect to the server using the certificate.

4 OPC Data items

4.1 Alarm Statistics Data
The alarm statistics contain the data from alarms that are configured as counter
alarms or trend alarms. The system supports the data from the first 50 alarms
and only for the first 20 lanes for each alarm.
Item Item String Type RW Usage
1 Alarm.Alarm x Name String R The name of the alarm.

x is from 1 to 50
2 Alarm.Alarm x Overall Float R Overall count of defects for the alarm.
x is from 1 to 50
3 Alarm.Alarm x Lane n Float R Count of defects for each lane for the
alarm.
x is from 1 to 50; n is from 1 to 20
4 Alarm.Last Alarm x Overall Float R Overall count of defects for the alarm
for the last roll.
x is from 1 to 50
5 Alarm.Last Alarm x Lane n Float R Count of defects for each lane for the
alarm for the last roll.
x is from 1 to 50; n is from 1 to 20
4.2 App Data

The AppData fields are used to contain data that is not related to the inspection
system. This data is usually set from another program or source and is used as
a mechanism to pass data to the customer OPC UA instance.
1 AppData.Fieldx String RW x is from 1 to 10

4.3 Bank Info Data

The Bank Info data contains information about the video statistics for the bank and
each camera in the bank. The video statistics are calculated periodically. Options for
video statistics can be found in the Inspection Settings dialog in the menu option
Setup | Video Statistics.
4.3.1 Bank Video Statistics Data

1 BankInfo.Bank x.Shaded Float R Average shaded video intensity of
Mean Intensity bank x
2 BankInfo.Bank x.Unshaded Float R Average unshaded video intensity of
Mean Intensity bank x
3 BankInfo.Bank x.Shaded Float R Average shaded video standard
Mean StdDev deviation of bank x
4 BankInfo.Bank x.Unshaded Float R Average unshaded video standard
Mean StdDev deviation of bank x
5 BankInfo.Bank x.Defect Rate Int32 R Defects/second being read by the system
for the bank. This includes defects that are
being discarded
6 BankInfo.Bank x.Defect Count Int32 R Defects that were processed by the system
for the bank.
7 BankInfo.Bank x.Defect Int32 R Number of overflows for the bank for the
Overflows current production run.
8 BankInfo.Bank x.Ignored Int32 R Number of ignored defects from the
threshold ignores
9 BankInfo.Bank x.MD Float R The MD resolution of the bank.
Resolution
4.3.2 Camera Video Statistics Data

1 BankInfo.Bank x.Camera y. Float R Average shaded video intensity for
Shaded Mean Intensity bank x camera y
2 BankInfo.Bank x.Camera y. Float R Standard deviation of shaded video
Shaded StdDev for bank x camera y
3 BankInfo.Bank x.Camera y. Float R Average unshaded video intensity
Unshaded Mean Intensity for bank x camera y
4 BankInfo.Bank x.Camera y. Float R Standard deviation of unshaded
Unshaded StdDev video for bank x camera y
5 BankInfo.Bank x.Camera y. Integer R Video statistics check for each
Unshaded Video State camera.
0x1=OK
0x2=Avg low
0x4=Avg high
0x8=SD low
0x10=SD high

6 BankInfo.Bank x.Camera Int32 R Defects/second being read by the system

Y.Defect Rate for the bank x camera y. This includes
defects that are being discarded
7 BankInfo.Bank x.Camera Int32 R Defects that were processed by the system
Y.Defect Count for the bank x camera y.
8 BankInfo.Bank x.Camera Int32 R Number of overflows for bank x camera y
Y.Defect Overflows for the current production run.
9 BankInfo.Bank x.Camera Int32 R Number of ignored defects from the
Y.Ignored threshold ignores for bank x camera y
10 BankInfo.Bank x.Camera Float R The CD resolution for bank x camera y
Y.CD Resolution
11 BankInfo.Bank x.Camera Float R The percent CPU usage for bank x camera
Y.CPU Load y
12 BankInfo.Bank x.Camera Float R The percent memory used for bank x
Y.Memory Load camera y
13 BankInfo.Bank x.Camera Float R The temperature of the processing
Y.Temperature 1 hardware for bank x camera y
14 BankInfo.Bank x.Camera Float R The temperature at the camera sensor for
Y.Temperature 2 bank x camera y

4.4 Classifier Data

To allow setting of class values via the OPC connection The tags support 50
class constraints which allows the caller to change the class properties for up to
50 classes at a time. Note that these 50 do not correspond do the class index in
the Central classifier class list. The class that will be changed from one of the
50 class constraints is selected by matching the className in the constraint
data to the Centrals class list.
Ex: Set Class.Current.Constraint 1 to this and the class “Edge Defect” will be
changed to the values sent. “Edge Defect” may be the 5th class down the class
list and will be selected using the Name in the tag – “Edge Defect”.
Edge Defect,1,0,2.211,0,2,0,23,0,3,0,24,0,4,0,25,0,5,0,26,0,6,0,27,0,7,0,28,0,8,0,29,0,9,0,30,0,0,0,28
4.4.1 Logic flow

1. The following OPC tags are set by caller.
Class.Current.Start to 1
a.
Class.Current.Caller ID is set.
b.
Class.Current.Constraint 1 to n are set.
c.
Class.Current.Complete to 1
d.
2. On Complete being set to 1 OPC will
a. Transmit Class.Current.Constraint values to inspection system
b. If processing is successful, set the following OPC tags.
i. Class.Current.Error to 0
ii. Class.Current.Response ID equal to Class.Current.Caller ID.
c. If process is unsuccessful, set the following OPC tags.
i. Class.Current.Error to 1
ii. Class.Current.Response ID equal to Class.Current.Caller ID.
3. The following OPC tags are set by caller.
a. Class.Current.Start to 0
b. Class.Current.Complete to 0
4.4.2 Current Classifier Fields
1 Class.Current.Ready Int R ISRA will set this item to 1 if changes are

allowed.
2 Class.Current.Start Int RW The caller will set this item to 1 before setting
other OPC values. On the start being set, the
OPC Server will clear the Error and Response
ID values.
3 Class.Current.Caller ID String RW The caller will set this item. It is a unique
identifier for the request.
4 Class.Current.Constraint # String RW # is 1 to 50
The string value has the following
format:

ClassName,
ConstraintIndex1,Logic1,Value1,AndLogic2,
ConstraintIndex7,Logic7,Value7, And Logic 8,
ConstraintIndex9,Logic9,Value9, And Logic 10
ConstraintIndex10,Logic10,Value10
Note: All 40 values must be sent in the string or
the transfer will not happen and the Error value
will be set to 1.
ClassName (String) – Name of the class.

ConstraintIndex (Int) – Numerical
representation of constraint. Set to 0 for “NO”
constraint. See constraint table for complete
list of constraint usages.
Logic# (Int) – 0 is <=; 1 is >=.
AndLogic# (Int) – 0 is And; 1 is Or.
Value# (Float) – The value to check for
respective constraint.
5 Class.Current.Complete Int R The caller will set this item to 1 when ALL
constraints have been set to desired value.
The class data will be sent to the inspection
system at this time. The caller should set this
item back to 0.
6 Class.Current.Error Int R 0 = Class data set OK
1 =Class data format error
2 = Class not found. The class name in the
constraint tag is not defined in Central.
7 Class.Current.Response String RW On completion of sending data ISRA will echo
ID ‘Class.Current.Caller ID’.
8 Class.Current.Cancel Int RW Set to 1 to cancel all classifier changes that
were set. Cancel must be done before the
Complete value is set.
4.4.3 Next Run Classifier Fields

The next classifier values will be set after the next roll reset.
1 Class.Next.Ready Int R ISRA will set this item to 1 if changes are

allowed.
2 Class.Next.Start Int RW The caller will set this item to 1 before setting
other OPC values. On the start being set, the


OPC Server will clear the Error and Response
ID values.
3 Class.Next.Caller ID String RW The caller will set this item. It is a unique
identifier for the request.
4 Class.Next.Constraint # String RW # is 1 to 50
The string value has the following
format:
ClassName,
ConstraintIndex9,Logic9,Value9, And Logic 10
ConstraintIndex10,Logic10,Value10
Note: All 40 values must be sent in the string or
the transfer will not happen and the Error value
will be set to 1.
ClassName (String) – Name of the class.

ConstraintIndex (Int) – Numerical
representation of constraint. Set to 0 for “NO”
constraint. See constraint table for complete
list of constraint usages.
Logic# (Int) – 0 is <=; 1 is >=.
AndLogic# (Int) – 0 is And; 1 is Or.
Value# (Float) – The value to check for
respective constraint.
5 Class.Next.Complete Int R The caller will set this item to 1 when ALL
constraints have been set to desired value.
The class data will be sent to the inspection
system at this time. The caller should set this
item back to 0.
6 Class.Next.Error Int R 0 = Class data set OK
1 =Class data format error
2 = Class not found. The class name in the
constraint tag is not defined in Central.
7 Class.Next.Response ID String RW On completion of sending data ISRA will echo
‘Class.Next.Caller ID’.
8 Class.Next.Cancel Int RW Set to 1 to cancel all classifier changes that
were set. Cancel must be done before the
Complete value is set.

4.4.4 Class Constraints Indices Table

These indices are used in setting the class fields that set the classes constraint.
0=None 41=MD segment relative 81=Net width from merges
1=Length 42=MD Distance to Nearest segment 82=Length 1
2=Width 43=Boundary defect 83=Length 2
3=Area 44=Merge Count 84=Length 3
4=Average intensity 45=Circumference 85=Length 4
5=Maximum intensity 46=Blob Roughness 86=Length 5
6=Minimum intensity 47=Area Dark [1] 87=Length 6
7=Aspect ratio 48=Area Dark [2] 88=Width 1
8=Percent fill 49=Area Dark [3] 89=Width 2
9=Crossweb 50=Area Dark [4] 90=Width 3
10=Compactness 51=Area Dark [5] 91=Width 4
11=Roundness 52=Area Dark [6] 92=Width 5
12=Diagonal 53=Area Bright [1] 93=Width 6
13=Diameter 54=Area Bright [2] 94=Average Red (Color only)
14=Contrast 55=Area Bright [3] 95=Average Green (Color only)
15=Defect Std dev 56=Area Bright [4] 96=Average Blue (Color only)
16=Background intensity 57=Area Bright [5] 97=Average H (Color only)
17=Background std dev 58=Area Bright [6] 98=Average S (Color only)
18=Bounding box area 59=Area Dark Ratio1 [1] 99=Average I (Color only)
19=Channel 0 60=Area Dark Ratio1 [2] 100=Core Area Ratio
20=channel 1 61=Area Dark Ratio1 [3] 101=Sharpness mean 1
21=channel 2 62=Area Dark Ratio1 [4] 102=Sharpness Std 1
22=channel 3 63=Area Dark Ratio1 [5] 103=Sharpness mean 2
23=CD Adjusted 64=Area Dark Ratio1 [6] 104=Sharpness Std 2
24=Inertia Axis Dir 65=Area Bright Ratio1 [1] 105=Blob mean area ratio
25=Large main moment 66=Area Bright Ratio1 [2] 106=Blob max area ratio
26=Small main moment 67=Area Bright Ratio1 [3] 107=Core area
27=Moment relationship 68=Area Bright Ratio1 [4] 108=Bright Area
28=G Min 69=Area Bright Ratio1 [5] 109=Dark Area
29=G Max 70=Area Bright Ratio1 [6] 110=Bright length
30=Downweb 71=Dark Sum Area Ratio1 111=Dark length
31=Distance from left edge 72=Bright Sum Area Ratio1 112=Bright width
32=Distance from right edge 73=Grey Tiles [1] 113=Dark width
33=Core mean intensity 74=Grey Tiles [2] 114=G Diff Min
34=Core min intensity 75=Grey Tiles [3] 115=G Diff Max
35=Core max intensity 76=Grey Tiles [4] 116=Merge B2B area ratio
36=Core to defect contrast 77=Grey Tiles [5] 117=External feature 1
37=Core to background contrast 78=Grey Tiles [6] 118=External feature 2
38=Core num pixels 79=Grey Tiles [7] 119=External feature 3
39=CD lane relative 80=Net length from merges 120=External feature 4
40=CD Distance to Nearest
Lane

4.5 Control Data

1 Control.Inspect Mode Int32 RW 1= Inspect; 0=standby

2 Control.Inhibit Defects Int32 RW 1= Inhibit defects; 0=allow defects
This allows the defects to be ignored without actually
putting the system in standby mode.
3 Control.Inhibit Defects2 Int32 RW 1= Inhibit defects; 0=allow defects
This allows the defects to be ignored without actually
putting the system in standby mode.
This version causes the system to count the position
while inhibited
4 Control.Web Break mode Int32 RW 1= Web break; 0=not web break
5 Control.Roll Reset Int32 W 1 will do a roll reset.
6 Control.Alarm Clear Int32 RW Clear the alarms
7 Control.System Status Int32 R Contains a bit encoded system status error code.
0x1 - Connection issue to hardware
0x2 – Product not found
0x4 – Error writing a file
0x8 – Encoder frequency to high
0x10 – Interconnect cable not detected
0x20 – Edge tracking error
0x40 – Rolls being produced with 0 length
0x200 – Reset signal from camera missing
0x400 – Camera reset signal pulsed during run
0x800 – Camera signals are missing
0x1000 – Camera signals are intermittent
0x4000 – Inspection PC health issue
0x10000 – Camera driver error
0x20000 – Camera memory low
0x40000 – Camera voltage low
0x80000 – Hardware temperature high
0x400000 – Connection to hardware dropped
0x800000 – Camera FPGA error
0x2000000 – Camera acquisition error

4.6 Defect Data

1 Defect.Number Int32 R
2 Defect.ID Int32 R Unique defect ID
3 Defect.Class String R Defect class as text
4 Defect. Numeric Class Int32 R Defect class as a number
5 Defect.MD Float R Defect downweb position
6 Defect.MDRel Float R Defect downweb position winder relative
7 Defect.CD Float R Defect crossweb position
8 Defect.CD0 Float R Defect crossweb position relative to 0
9 Defect.CDEdge Float R Defect crossweb position relative to product
edge
10 Defect.CDRel Float R Defect crossweb position winder relative
11 Defect.CDStretched Float R Defect crossweb position stretched
12 Defect.CDEnd Float R Defect crossweb ending position
13 Defect.Length Float R Defect length
14 Defect.Width Float R Defect width
15 Defect.Area Float R Defect area
16 Defect.Diameter Position Float R Position of the defect by roll diameter
17 Defect.Start Lane Int32 R Defect starting lane index
18 Defect.End Lane Int32 R Defect Ending lane index
19 Defect.Bank Int32 R Bank index the defect belongs to. 0=Bank 1
20 Defect.Bank Name String R Bank name the defect belongs to.
21 Defect.Camera String R Camera that reported the defect
22 Defect.Time String R Time in ISRA encoded format
23 Defect.Alarm Level String R Alarm that this defect asserted
24 Defect.Average Intensity Int32 R Average defect intensity
25 Defect.Minimum Intensity Int32 R Minimum defect intensity
26 Defect.Maximum Intensity Int32 R Maximum defect intensity
27 Defect.Merge Count Int32 R Number of times this defect merged
28 Defect.CD 2 Float R CD relative to a 2nd coordinate system
29 Defect.QuickTeach Id String R Quickteach class identifier
30 Defect.Aspect Ratio Float R Aspect ratio = L/W
31 Defect.Percent Fill Float R Percent fill = A/(LxW)
32 Defect.Severity Factor Float R User defined severity rating for defect class
33 Defect.Symbol String R Defect class symbol
34 Defect.Bright Threshold Int32 R Bright detection threshold
35 Defect.Dark Threshold Int32 R Dark detection threshold
36 Defect.Bright Area Threshold Int32 R Bright area threshold
37 Defect.Dark Area Threshold Int32 R Dark area threshold
38 Defect.Bright-dark type Int32 R Defect contains bright and dark parts

39 Defect.Image Name String R Name of the image

40 Defect.Image Path String R Folder location
41 Defect.Time Stamp String R Yyyymmddhhmmss
42 Defect.Drawing Shape Int32 R 1=Rectangle, 2=Square, 3=Circle,
4=Oval,5=Triangle;6=Diamond
43 Defect.Ext Feat X Float R External features – X is from 1 to 10
441 Defect.EvalData.Bright.Area Array R The bright evaluation threshold areas
Array Float[6]
451 Defect.EvalData.Bright.Area Array R The bright evaluation threshold area ratios
Ratio 1 Array Float[6] 1. Eval area[x]/total area
461 Defect.EvalData.Bright.Area Array R The bright evaluation threshold area ratios
Ratio 2 Array Float[6] 2. Eval area[x]/dark area
471 Defect.EvalData.Bright.Area Array R The bright evaluation threshold bin area –
Bin Array Float[6] area between adjacent threshold levels
481 Defect.EvalData.Bright.Area Array R The bright evaluation threshold bin ratios –
Bin Ratio Array Float[6] bin area[x]/total area
491 Defect.EvalData.Bright.Sum Float R Sum of the bright ratio 1’s
Area Ratio 1
501 Defect.EvalData.Bright.Sum Float R Sum of the bright ratio 2’s
Area Ratio 2
511 Defect.EvalData.Dark.Area Array R The dark evaluation threshold areas
Array Float[6]
521 Defect.EvalData.Dark.Area Array R The dark evaluation threshold area ratios 1.
Ratio 1 Array Float[6] Eval area[x]/total area
531 Defect.EvalData.Dark.Area Array R The dark evaluation threshold area ratios 2.
Ratio 2 Array Float[6] Eval area[x]/dark area
541 Defect.EvalData.Dark.Area Bin Array R The dark evaluation threshold bin area –
Array Float[6] area between adjacent threshold levels
551 Defect.EvalData.Dark.Area Bin Array R The dark evaluation threshold bin ratios –
Ratio Array Float[6] bin area[x]/total area
561 Defect.EvalData.Dark.Sum Float R Sum of the dark ratio 1’s
Area Ratio 1
571 Defect.EvalData.Dark.Sum Float R Sum of the dark ratio 2’s
Area Ratio 2
581 Defect.EvalData.Length Array Array R The defect lengths from the eval thresholds.
Float[6]
591 Defect.EvalData.Width Array Array R The defect widths from the eval thresholds.
Float[6]
60 Defect.Roll Number String R The roll number that the defect is on.
61 Defect.Lot Id String R The Lot Id that the defect is on.
62 Defect.Order Id String R The Order Id that the defect is on.
632 Defect.Defect JSON String R JSON string with multiple defects and
selected features. Max length is 20000
characters.
1 – If the INI key DefectTagMode is set to 1 then a subset of the features is supported and these features will not be available.
2 – This is only available if the transfer mode is set to JSON Format. In this mode the individual defect features are not available. See
section 4.8 for information on setting the features to include in the JSON string.

4.7 Defect Control

The defect control is used to set the mode of transferring defects to a client. The continuous
mode will send a defect every transfer rate number of milliseconds. If the client is busy and
does not retrieve the defect data, then it is overwritten and the defect is not read by the client.
The customer side can control the defect data flow by enabling on of the handskaing modes.
There are two handshaking modes.
1. Handshake mode 1- (One flag) – This method uses the defect ready tag.
A. ISRA OPC UA sets the defect data tags in section 4.6
B. ISRA OPC UA sets the Defect.Defect Ready to 1
C. Customer OPC UA reads the defect data on the Defect.Defect Ready tag going to 1
D. Customer OPC UA clears the Defect.Defect Ready to 0
E. ISRA OPC UA reads the Defect.Defect Ready tag and if 0 goes back to step A
F. If the timeout duration of time elapses and the Defect.Defect Ready tag has not been
set back to 0, then ISRA OPC UA will clear it and continue sending.
2. Handshake mode 2- (Two flags) – This method uses the defect ready and the defect
ReadyAck tags.
A. ISRA OPC UA sets the defect data tags in section 4.6
D. Customer OPC UA Sets the Defect.Defect Ready Ack to 1
E. ISRA OPC UA reads the Defect.Defect Ready Ack and if 1 clears both tags back to 0
and goes back to step A
F. If the timeout duration of time elapses and the Defect.Defect Ready Ack tag has not
been set to 1, then ISRA OPC UA will clear both tags back to 0 and continue sending.
3. JSON Format – This method sends multiple defects in a JSON string. The defect JSON
string will be posted every update rate milliseconds with the last defects. The defect ready
and the defect ReadyAck tags can be used to verify that the data is being received and
processed.
A. ISRA OPC UA sets the defect JSON data tag.
D. Customer OPC UA Sets the Defect.Defect Ready Ack to 1
E. ISRA OPC UA reads the Defect.Defect Ready Ack and if 1 clears both tags back to 0
and goes back to step A
F. If the ½ the transfer rate time elapses and the Defect.Defect Ready Ack tag has not
been set to 1, then ISRA OPC UA will clear both tags back to 0.
G. The next JSON defect data will be posted when the transfer rate time has elapsed
regardless of the handshaking state.
1 Defect.Transfer Mode Int32 R 0: Continuous defect sending. A defect will be

posted every transfer rate number of milliseconds.
1: Handshaking enabled
2 Defect.Defect Ready Int32 RW See above description.
3 Defect.Defect Ready Ack Int32 RW This tag is ONLY used if the Transfer Mode is set
handshake mode 2 or 3.
See above description.

4.8 Defect JSON Format

The JSON data contains selected features of multiple defects. The number of
defects in a single JSON output can be set in the Options dialog.
Example JSON string containing two defects:
{"Defects":{"1":[23,"Hole",7757.96,1.452,0.0199,0.115,11.152,1,1,0,244,135,255,1,2.082,62.476,0.0],"2":[2
4,"Thin Spot",7760.445,2.763,0.012,0.0419,2.668,1,1,0,243,161,255,1,3.45,68.86,0.0]}}
JSON String as shown in a JSON viewer.
The features that the JSON string contains is set in the programs setting INI file.
D:\Central\INI\ OPCUAClient.ini
The INI file contains a section [DEFECT JSON MAPPING] with comments and
variables. Each defect feature maps to a specific feature index and the indices
for the desired features in the JSON output are set in the JsonDefectFeaturex
variables.
[DEFECT JSON MAPPING]
;1-Defect Number
;2-Defect Numeric Class
;3-Defect Class
;4-Defect MD
;5-Defect MDRel
;6-Defect CD
………
JsonDefectFeature1=1
………

4.9 Edge Analyzer Data

The Edge Analyzer is used to locate internal product edges and perform checks on
their position or the distance between 2 edges. This option is often used in
applications that are slitting the product before inspection and the system needs to
locate each slit for the purpose of disabling defect inspection at the slit boundaries
and/or to measure the final width of each slit. The Edge analyzer can also calculate
average video intensity in a user defined region to check for proper video levels. The
system supports up to 100 measurement results.
1 EAMeas.Data Ready Integer RW Set to a 1 when new measurement data

has been posted. The OPC Client
should set this back to a 0 after reading
the data.
2 EAMeas.MeasDateTime String R Time stamp that the last measure data
was posted - Yyyymmddhhmmss
3 EAMeas.Meas X Name String R This is the name of the measurement.
x is from 1 to 100
4 EAMeas.Meas X Current Float R This is the current value for the
measurement. If the measurement
could not be taken because edges are
missing, then this will be set to -1.
x is from 1 to 100
5 EAMeas.Meas X Average Float R This is the average value for the
measurement.
x is from 1 to 100
6 EAMeas.Meas X Minimum Float R This is the minimum value for the
measurement.
x is from 1 to 100
7 EAMeas.Meas X Maximum Float R This is the maximum value for the
measurement.
x is from 1 to 100
8 EAMeas.Meas X State Integer R This is the state for the measurement.
1=pass; 0=fail; 2=Missing edges
x is from 1 to 100

4.10 External Data

The External data tags are used to send up to 20 process values to the inspection
system. These values can be included with each defect using the custom features
option. And the values can be added to a trend graph that is configured to trend
system variables.
1 ExternalData.Value n Float RW These are the values that will be sent to
the inspection system. n is from 1 to 20.
2 ExternalData.Data Set Integer RW This will trigger the inspection system to
process the new external data values.
Note that the inspection system will
automatically process the new data if
the “Data Set” value has not been set
within 1 second.
4.11 External Event Data

An external event can generate a defect through the alarm module of the inspection
system.
1 External Event.Alarm ID Integer RW Set to the alarm ID that will be used to
create the external event.
2 External Event.MD Float RW The position of the event can be set. If
set to 0, the system will use the current
position.
3 External Event.MD Offset Float RW This can be used to set the position of
the event so that it is an offset distance
away from the current position.
4 External Event.CD Float RW The CD position of the event can be
set.
5 External Event.Event Mode Integer RW 1=one shot event-This will create the
alarm defect with the length specified
in the alarm properties.
2=Start event–This will create an
alarm defect where the length will
grow as the product moves. The caller
must give a Stop event to end the
event.
3=Stop event-This will stop the defect
that was growing from the start event.
6 External Event.Fire Event Integer RW Setting this to a 1 will fire the event and
cause the alarm to perform its function
based on the Event mode. It is the
caller’s responsibility to clear this value
to 0.

4.12 Flag Data

Flag data is generated when a defect asserts an output that has be associated with
the flagger. The Flagger options in the I/O setup dialog need to be configured in
Central to support the flag processing. The inspection system records the output
events for up to two flaggers and the data and options are handled independently.
Options are available in the Settings tab to control how the OPC Server will handle the
flag data.
Note that some of these tags are not used based on the defect flagger mode setting.
These tags are for the first flagger’s output events.
1 FlagData.Flag ID Integer R The flag ID is a unique number for each
flag.
2 FlagData.Flag MD Float R The MD position of the flag event.
3 FlagData.Flag Text String R The text that is associated with the flag
as set by Central.
4 FlagData.Defect ID Integer R The defect ID is a unique ID number of
the defect the caused the flag event.
5 FlagData.Defect MD Float R The MD position of the defect that
caused the flag event.
6 FlagData.External Flag Text String RW In the Support flag data with external
data mode this data will be supplied by
the customer and will be associated
with the current flag being processed.
Or in Support external data only mode
this will be the data associated with a
defect and/or used to create the flag
event.
A common usage for this is some
customers use a flag with barcode data
on them and a barcode scanner is used
to read back the flag data. The flag data
is then recorded by the flag in Central
via this OPC tag.
7 FlagData.External Data Distance Float RW If external flag data is not recorded
Timeout within this distance then the flag data is
set to “NA”. This distance can be set in
the settings tab.
These tags are for the second flagger’s output events in the Support flag data with
external data mode.
1 FlagData.Flag ID 2 Integer R The flag ID is a unique number for each
flag.
2 FlagData.Flag MD 2 Float R The MD position of the flag event.

3 FlagData.Flag Text 2 String R The text that is associated with the flag
as set by Central.
4 FlagData.Defect ID 2 Integer R The defect ID is a unique ID number of
the defect the caused the flag event.
5 FlagData.Defect MD 2 Float R The MD position of the defect that
caused the flag event.
6 FlagData.External Flag Text 2 String RW This data will be supplied by the
customer and will be associated with
the current flag being processed from
the second flagger’s output. A common
usage for this is some customers use a
flag with barcode data on them and a
barcode scanner is used to read back
the flag data. The flag data is then
recorded by the flag in Central via this
OPC tag.

4.13 Image Export Data

The image sampling option will save an image from each camera at a defined rate for
customer offline processing. Multiple image jobs can be defined to provide custom
sampling on a per camera or per bank basis. The option is accessed from the Camera
bank setup dialog with the Image sampling button.
The Image Export Tags are used to set the image sampling options and to trigger an
image sample.
1 ImageExport.Enable Int32 RW Enables/disables the image job

2 ImageExport.Sample Interval Int32 RW Sets the sample interval,
3 ImageExport.Image.PositionX Int32 RW X position in pixels to start the acquisition
4 ImageExport.Image.SizeX Int32 RW The width of the image in pixels to
acquire
5 ImageExport.Image.SizeY Int32 RW The height of the image in lines of video
6 ImageExport.Image.ScaleX Int32 RW Scales the image in the X direction.
0=1x, 1=2x, 2=4x, 3=8x, 4=16x
7 ImageExport.Image.ScaleY Int32 RW Scales the image in the X direction.
0=1x, 1=2x, 2=4x, 3=8x, 4=16x
8 ImageExport.Image.Source Int32 RW 0=Shaded video; 1=Raw video
9 ImageExport.Sample Path String RW Image archive path. This path is common
to all image jobs
10 ImageExport.Sample Trigger String RW Acquires an image
11 ImageExport.Job Set Data Index String RW The Set Data index is used to control the
image index that the above parameters
and trigger tags will affect. 1 is the first
image job. If the Set Data index is -1 then
all image jobs are affected.
12 ImageExport.Job Get Data Index String RW The Get Data index is used to request the
parameters for a specific job and will set
the parameter tags above. 1 is the first
image job.

4.14 Inspection Settings Data

The inspection settings data contains the parameters that control how the
system detects defects. Extreme care should be used when setting these
values as they will affect the ability of the system to inspect the product. The
settings take affect immediately upon being set.

1 Inspection Params.Bank Integer RW Channel n high threshold enabled
x.Chn High Threshold Enable
2 Inspection Params.Bank Integer RW Channel n high threshold
x.Chn High Threshold
3 Inspection Params.Bank Float RW Channel n high threshold min
x.Chn High Threshold Min width constraint
Width Filter
x.Chn High Threshold Min length constraint
Length Filter
x.Chn High Threshold Min area constraint
Area Filter
6 Inspection Params.Bank Float RW Channel n high threshold max
x.Chn High Threshold Max width constraint
Width Filter
x.Chn High Threshold Min length constraint
Length Filter
x.Chn High Threshold Min area constraint
Area Filter
9 Inspection Params.Bank Integer RW Channel n low threshold enabled
x.Chn Low Threshold Enable
10 Inspection Params.Bank Integer RW Channel n low threshold
x.Chn Low Threshold
11 Inspection Params.Bank Float RW Channel n low threshold min width
x.Chn Low Threshold Min constraint
Width Filter
12 Inspection Params.Bank Float RW Channel n low threshold min
x.Chn Low Threshold Min length constraint
Length Filter
13 Inspection Params.Bank Float RW Channel n low threshold min area

Area Filter
14 Inspection Params.Bank Float RW Channel n low threshold max
x.Chn Low Threshold Max width constraint


Width Filter
15 Inspection Params.Bank Float RW Channel n low threshold max
x.Chn Low Threshold Min length constraint
Length Filter
16 Inspection Params.Bank Float RW Channel n low threshold max area
Area Filter
17 Inspection Params.Bank Integer RW Channel n low threshold enabled
x.Chn Low Threshold Enable
18 Inspection Params.Bank Integer RW 0 = Fixed edges; 1= Track Edges;
x.Edge Track Mode 2 = use edges from another bank
19 Inspection Params.Bank Float RW Left edge when in fixed edges
x.Left Fixed Edge mode
20 Inspection Params.Bank Float RW Right edge when in fixed edges
x.Right Fixed Edge mode
21 Inspection Params.Bank Float RW Left edge safety
x.Left Edge Safety
22 Inspection Params.Bank Float RW Right edge safety
x.Right Edge Safety
23 Inspection Params.Bank Float RW Start of edge search window for
x.Left Track Search Start left edge when in Track Edges
mode.
24 Inspection Params.Bank Float RW End of edge search window for
x.Left Track Search End left edge when in Track Edges
mode.
23 Inspection Params.Bank Float RW Start of edge search window for
x.Right Track Search Start right edge when in Track Edges
mode.
24 Inspection Params.Bank Float RW End of edge search window for
x.Right Track Search End right edge when in Track Edges
mode.
25 Inspection Params.Bank Float RW Left default edge that will be used
x.Left Default Edge if edges are not detected when in
Track Edges mode.
26 Inspection Params.Bank Float RW Right default edge that will be

x.Right Default Edge used if edges are not detected
when in Track Edges mode.
27 Inspection Params.Bank Float RW Gain used to amplify the edge
x.Edge Gradient Gain gradient
28 Inspection Params.Bank Integer RW Edge threshold
x.Edge Threshold
29 Inspection Params.Bank Integer RW Exposure time
x.Exposure Time


30 Inspection Params.Bank Float RW Trigger divisor
x.Trigger Divisor
31 Inspection Params.Bank Integer RW Shading target value
x.Shading Target
32 Inspection Params.Bank Float RW Dynamic shade rate
x.Dynamic Shade Rate
33 Inspection Params.Bank x.Do Integer RW Set to 1 to shade the video
Shade Video
The Video Level Auto Adjustment option will set the camera gains, LED
intensity, and/or exposure time to drive the video to a target video value. These
tags allow the OPC UA to adjust the video and receive feedback regarding the
results. The settings for this option are accessed from Central in the Inspection
Settings dialog under the menu option - Setup | Automatic Settings Options.

1 Inspection Params.Bank x Integer RW Set to 1 to set the video level.
Auto Set.Do Set Video Level
2 Inspection Params.Bank x Integer RW -1 = the option is disabled on
Auto Set.Set Video Level Central.
Result 0 = the video was set successfully
3 Inspection Params.Bank x Float RW The average video after the
Auto Set.Set Video Level adjustment has been made.
Result Average Video
4.15 IO Data
The input data will show the state of the digital inputs used by the system.
1..80 IO.Inputs.Input x State Boolean R State of the input. Input index is 1 to 80

as listed in the input configuration
dialog on Central.
1..48 IO.Outputs.Output x State Boolean R State of the output. Output index is 1 to
48 as listed in the output configuration
dialog on Central.

4.16 Lane Data

Most systems only use one lane configuration. But, on a system with multiple banks some
systems will inspect two separate web paths. Each web path can be slit into lanes or daughter
rolls and the dual lane support allows each web path to have a unique lane configuration.
Thus, there is a second set of lane tags that can be enabled to support this second set of
lanes. The second set of lane tags start with the root tag name of “Lane 2”.
The lane information can be configured using one the following methods:
1. Uniform width method – This method is used when all lanes have the same dimension.
The caller sets the number of lanes, the start position of the first lane, and the uniform
width value.
2. Specifying the range for each lane – This method is used when the lanes are
specified based on a starting and ending coordinate. Send the number of lanes
and the left and right coordinates of each lane.
3. Specifying the width for each lane – This method is used when the lanes are
specified based on a starting position and the width of each lane. Send the number
of lanes, the starting lane value, and the width of each lane.
1 Lane.Number Lanes Int32 RW Number of defined lanes in the Inspection

system
2 Lane.Uniform Width Float RW The lane width of all lanes when the lane setup
is in Fixed width mode.
3 Lane.StartLane Float RW The starting position of the first lane.
4 Lane.Lane Left 1..100 Float RW This is the left most coordinate of each lane.
5 Lane.Lane Right 1..100 Float RW This is the right most coordinate of each lane.
6 Lane.Lane Width 1..100 Float RW This is the width of each lane.
7 Lane.AutoCalc Float RW This is the starting lane value for the Auto Calc
StartLane lane mode.
8 Lane.AutoCalc Float RW This is the ending lane value for the Auto Calc
EndLane lane mode.
9 Lane.AutoCalc Float RW This is the lane width for the Auto Calc lane
LaneWidth mode. Depending on the auto calc mode, this
value may not be used.
10 Lane.Apply Changes Int32 RW Set this to 1 to make the system take the
current lane values now. If this tag is not used,
the lane changes will still take affect but will be
delayed by 2 or 3 seconds.
11 Lane.Next Number Int32 RW This value will be applied at the start of the
Lanes next roll. Number of defined lanes in the
Inspection system
12 Lane.Next Uniform Float RW This value will be applied at the start of the
Width next roll.
Number of defined lanes in the Inspection
system
13 Lane.Next Start Lane Float RW This value will be applied at the start of the
next roll.


The starting position of the first lane.
14 Lane.Next Lane Left Float RW This value will be applied at the start of the
1..100 next roll.
This is the left most coordinate of each lane.
15 Lane.Next Lane Right Float RW This value will be applied at the start of the
1..100 next roll.
This is the right most coordinate of each lane.
16 Lane.Next Lane Width Float RW This value will be applied at the start of the
1..100 next roll.
This is the width of each lane.
17 Lane.Next AutoCalc Float RW This is the starting lane value for the Auto Calc
StartLane lane mode for the next roll.
18 Lane.Next AutoCalc Float RW This is the ending lane value for the Auto Calc
EndLane lane mode for the next roll.
19 Lane.Next AutoCalc Float RW This is the lane width for the Auto Calc lane
LaneWidth mode for the next roll. Depending on the auto
calc mode, this value may not be used.
20 Lane.Enable Save Int32 RW The default behavior is any lane changes
Changes made via OPC are not saved to the lane
settings file for the product. Setting this value
to 1 will cause subsequent lane changes made
via OPC to be saved to the file. Note that
changes made when using the Lane.Next Roll
Lane values will not be saved until the next roll
starts.

4.17 LED Data

1 LED.LED Intensity Off Integer W 1 will set all LED banks to 0%
intensity
2 LED.LED Intensity On Integer W 1 will set all LED banks to the
intensity levels set for the product
style.
3 LED.LED n.Intensity Integer RW This is the percent intensity for LED
Bank n. n is 1 to 6.
4 LED.LED n.Current Float R This is the current temperature of
Temperature LED bank n. n is 1 to 6.
5 LED.LED n.Minimum Float R This is the minimum temperature of
Temperature LED bank n since LEDInterface
started. n is 1 to 6.
6 LED.LED n.Maximum Float R This is the maximum temperature
Temperature of LED bank n since LEDInterface
started. n is 1 to 6.

4.18 Metal Detector Data

A metal detector can send metal event data to the program which will create
metal defects in the inspection program and/or set metal data for a normally
detected defect so it can be classified as a metal defect. See the section on the
metal detector for a complete description for this option.
1 Metal Detector.ISRA MD Position Float R Current web position

2 Metal Detector.ISRA Velocity Float R Production line speed
3 Metal Detector.ISRA Row 1 Data Integer RW This tag is set when the metal data is
Read Ack read by the OPC. This tag should
cleared by customer.
4 Metal Detector.ISRA Row 1 Data Integer RW When this tag goes high ISRA will read
Ready the metal defect information that was
posted by the metal detector.
5 Metal Detector.ISRA Row 1 Data Integer RW Section that detected the metal defect
Section
6 Metal Detector.ISRA Row 1 Data Float RW The amplitude or strength of the metal
Amplitude detection.
7 Metal Detector.ISRA Row 2 Data Integer RW This tag is set when the metal data is
Read Ack read by the OPC. This tag should
cleared by customer.
8 Metal Detector.ISRA Row 2 Data Integer RW When this tag goes high ISRA will read
Ready the metal defect information that was
posted by the metal detector.
Section

4.19 Production Data

Production data can be set for this production run or the next production run. There are also
fields available that contain the last production runs fields.
4.19.1 This Run Product Fields

1 Prod.This Product Style String RW Set the product style
2 Prod.This Product Table Code Int32 RW Set the product based on a numerical value
that looks up the product in the product table
3 Prod.This Roll Number String RW Set current roll number
4 Prod.This Lot Id String RW Sets the Lot Id field
5 Prod.This Order Id String RW Sets the Order Id field
6 Prod.This Shift Id String RW Sets the Shift Id field
7 Prod.This Operator Name String RW Sets the Operator name field
8 Prod.This Customer Name String RW Sets the Customer name field
9 Prod.This Customer Id String RW Sets the Customer Id field
10 Prod.This Machine Name String RW Sets the Machine name field
11 Prod.This User Defined 1 String RW Sets the User defined field 1 field
21 Prod.This Nominal Width Float RW Sets the nominal width
22 Prod.This Width UL Float RW Sets the width upper limit
23 Prod.This Width LL Float RW Sets the width lower limit
24 Prod.This Thickness Float RW Sets the product thickness
25 Prod.This Density Float RW Sets the product density
26 Prod.This gsm Float RW Sets the product weight in gsm
27 Prod.This Status LED 1 value String R This is the current value of Status Led 1
33 Prod.This Calc x value String R Contains the current calculation value. X is
the calculations index – 1 to 30.
These tags can be dependent on the

classifier and/or graph setup. If the
setup is changed or a product is loaded that
has different configuration files, then the
values that these tags represent can change.
To use the tags without issue it is best to
configure all products to use the same
classifier and graph file.
34 Prod.This Target Length Float RW Sets the target length

35 Prod.This Target Length Short By Float RW Sets the target length short by value. Used to
determine a short roll.
36 Prod.This Target Length Long By Float RW Sets the target length long by value. Used to
determine a long roll.
37 Prod.This Blank Length String RW Sets the products blank length. Used to
calculate how many blanks a defect covers.
38 Prod.This Start TimeStamp String R Timestamp of when this production run
started. Time stamp – Yyyymmddhhmmss
39 Prod.Class List Array R The class names for the current product. This
String[n] is an array of n strings where n is the number
of defined classes.
40 Prod.This Sub Roll x String R A sub roll is a lane based or segment based
roll from a mother roll. Normally the sub roll
field is set to <mother roll #>-<index>. These
tags will override the standard naming
convention. Note this only sets the sub roll
production field and does not change the
filename the sub roll is saved into.
41 Prod.This Sub Roll Customer String R A sub roll is a lane based or segment based
Name x roll from a mother roll. This allows for each
sub roll to have a unique customer name.
42 Prod.This Process Step String RW Set the process step

4.19.2 Next Run Product Fields

1 Prod.Next Product Style String RW Set the next product style
2 Prod.Next Product Table Code Int32 RW Set the next product based on a numerical
value that looks up the product in the product
table
3 Prod.Next Roll Number String RW Set next roll number
4 Prod.Next Lot Id String RW Sets the next Lot Id field
5 Prod.Next Order Id String RW Sets the next Order Id field
6 Prod.Next Shift Id String RW Sets the next Shift Id field
7 Prod.Next Operator Name String RW Sets the next Operator name field
8 Prod.Next Customer Name String RW Sets the next Customer name field
9 Prod.Next Customer Id String RW Sets the next Customer Id field
10 Prod.Next Machine Name String RW Sets the next Machine name field
11 Prod.Next User Defined 1 String RW Sets the next User defined field 1 field
21 Prod.Next Nominal Width Float RW Sets the next nominal width
22 Prod.Next Width UL Float RW Sets the next width upper limit
23 Prod.Next Width LL Float RW Sets the next width lower limit
24 Prod.Next Thickness Float RW Sets the next product thickness
25 Prod.Next Density Float RW Sets the next product density
26 Prod.Next gsm Float RW Sets the next product weight in gsm
27 Prod.Next Target Length Float RW Sets the next target length
28 Prod.Next Blank Length String RW Sets the products blank length. Used to
calculate how many blanks a defect covers.
29 Prod.Next Process Step String RW Sets the next rolls process step

4.19.3 Last Run Product Fields

1 Prod.Last Product Style String R Contains the last rolls product style
2 Prod.Last Roll Number String R Contains the last rolls roll number
3 Prod.Last Lot Id String R Contains the last rolls Lot Id field
4 Prod.Last Order Id String R Contains the last rolls Order Id field
5 Prod.Last Shift Id String R Contains the last rolls Shift Id field
6 Prod.Last Operator Name String R Contains the last rolls Operator name field
7 Prod.Last Customer Name String R Contains the last rolls Customer name field
8 Prod.Last Customer Id String R Contains the last rolls Customer Id field
9 Prod.Last Machine Name String R Contains the last rolls Machine name field
10 Prod.Last User Defined 1 String R Contains the last rolls User defined field 1 field
20 Prod.Last Status LED 1 value String R Contains the last rolls value of Status Led 1
26 Prod.Last Calc x value String R Contains the last calculation value. X is the
calculations index – 1 to 30.
These tags can be dependent on the

classifier and/or graph setup. If the
setup is changed or a product is loaded that has
different configuration files, then the values that
these tags represent can change. To use the
tags without issue it is best to configure all
products to use the same classifier and graph
file.
27 Prod.Last Start TimeStamp String R Timestamp of when this production run started.
Time stamp – Yyyymmddhhmmss
28 Prod.Last End TimeStamp String R Timestamp of when this production run ended.
Time stamp – Yyyymmddhhmmss
29 Prod.Last Sub Roll x String R A sub roll is a lane based or segment based
roll from a mother roll. Normally the sub roll
field is set to <mother roll #>-<index>. These
tags contain the sub roll values that were set
in the Prod.This Sub Roll tags on the last roll.
30 Prod.Last Process Step String R Contains the last rolls process step

4.19.4 Change Product Fields

These tags will change the roll information on the last roll that finished.
1 Prod.Change Roll Number String W Used to change the roll number on a previous
production run.
2 Prod.Change Lot Id String W Used to change the lot id on a previous
production run.
3 Prod.Change Order Id String W Used to change the order id on a previous
production run.
4 Prod.Change Shift Id String W Used to change the shift id on a previous
production run.
5 Prod.Change Operator Name String W Used to change the operator name on a
previous production run.
6 Prod.Change Customer Name String W Used to change the customer name on a
7 Prod.Change Customer Id String W Used to change the customer id on a previous
production run.
8 Prod.Change Machine Name String W Used to change the machine name on a
9 Prod.Change User Defined 1 String W Used to change the user defined field 1 on a

4.20 Reclassify
These tags are used to reclassify defects. Multiple defects can be transmitted at
one time for reclassification. The defects to be classified are identified by the
defect ID which is a unique ID for each defect. The Tag defect.ID contains each
defects unique ID value.
Ex Reclassify.DefectList data that changes the class for 3 defects to Bad Edge.
The Class Bad Edge must be defined in the classigier.
519260,Bad edge,519263,Bad edge,519272,Bad edge
4.20.1 Processing flow

1. OPC Sets ISRAStatus =1; Central is ready to receive new data
2. Client sets the DefectList tag
Ex: ID,class,ID,class…ID,class
3. Client sets SenderReady to 1 to process the DefectList
4. OPC Sets ISRAStatus =0. Data is being processed
5. OPC Sets RtnErrorCode with result
6. OPC Sets ISRAStatus =1
7. Client sets SenderReady to 0

1 Reclassify.DefectList String RW Comma delimited list of defect ID’s
and class names for each.
2 Reclassify.SenderReady Integer RW Set to 1 when the defect list is set
3 Reclassify.ISRAStatus Integer R 1 = ISRA ready to receive new data
4 Reclassify.RtnErrorCode Integer R 0=Processed OK
1=Defect ID not found
2=Class name not found

4.21 RunData Data

1 RunData.Footage Float R Current web position
2 RunData.Velocity Float R Production line speed
3 RunData.Roll Diameter Float R Current diameter of the roll
4 RunData.Bx Product Width Float R Current product width from bank x
5 RunData.Bx Product Finished Width Float R Current product width minus edge
safeties or edge trim from bank x
6 RunData.Bx Maximum Width Float R Maximum product width for this
production run from bank x
7 RunData.Bx Minimum Width Float R Minimum product width for this
production run from bank x
8 RunData.Bx Left Edge Float R Left product edge position from bank x
9 RunData.Bx Right Edge Float R Right product edge position from bank
x
10 RunData.Left Edge Wander State Int32 R 0 = OK; 1=wander
11 RunData.Right Edge Wander State Int32 R 0 = OK; 1=wander
12 RunData.Product Area Float R Sqr area of product inspected
13 RunData.Total Defects Int32 R Total defects on the roll
14 RunData.Total Bright Defects Int32 R Total bright defects on the roll
15 RunData.Total Dark Defects Int32 R Total dark defects on the roll
16 RunData.Total BD Defects Int32 R Total Bright/dark defects on the roll
17 RunData.Heartbeat Int32 R The inspection PC’s system timer
value. The value is updated every 2
seconds.
18 RunData.Mass Float R Calculated mass of product inspected
19 RunData.Weight kg Float R Calculated weight of product inspected
in kilograms
20 RunData.Weight t Float R Calculated weight of product inspected
in metric tons
21 RunData.Overflows Int32 R Number of overflows detected by the
system.
22 RunData.Defect Rate Float R Defects/second being read by the
system. This includes defects that are
being discarded

4.22 Segment Data

If the segment option is configured for segments by lanes, then multiple
segments of data need to be posted to the segment tags. The multiple sets of
segment data will post to the tags for a segment and set the data Ready tag.
The ID or Index data tags can be used to know which product segment the data
belongs to. The data will stay set for some amount of milliseconds and then
change to next segments data. The amount of time the data is held can be
changed in the UpdateSegmentTime_ms variable located in OPCUAServer.ini.
The default value is 500ms.
4.22.1 Segment.Last Data

The Segment.Last tags are from the last finished segment.
1 Segment.Last.Data Ready Integer RW Set to a 1 when new segment data has
been posted. The OPC Client should
set this back to a 0 after reading the
data.
2 Segment.Last.DateTime String R Time stamp – yyyymmddhhmmss
3 Segment.Last.Index Integer R This is the segments index. The first
segment is 0.
4 Segment.Last.ID String R This is the segments ID. The ID can
start at a non-zero value based on
segment options.
5 Segment.Last.Set ID String R This is used when doing segments by
lanes. This is the set that this segment
is in
6 Segment.Last.MD Start Float R Segment starting position
7 Segment.Last.MD End Float R Segment ending position
8 Segment.Last.CD Float R Segment crossweb position
9 Segment.Last.Width Float R Segment width
10 Segment.Last.Length Float R Segment length
11 Segment.Last.Lane Float R Lane that this segment is in.
12 Segment.Last.Area Float R Segment area
13 Segment.Last.Label String R Label assigned to the segment that is
shown in the inspection program
14 Segment.Last.State Integer R The segment state
0=Pass
1=Warn
2=Fail
3=Not inspected
15 Segment Last.Result Value X Float R Each segment can have 50 values
assigned to it by processing routines
that operate on the segment. This is
the current value for the data values. x
is from 1 to 50
16 Segment.Last.Result State X Integer R Each segment can have 50 values
assigned to it by processing routines
that operate on the segment. This is
the current State of each of the values
x is from 1 to 50
0x1=Value is used

0x2=Value was set

0x4=Value failed
17 Segment.Last.Class X Count Integer R This is the count of each class type
that is on the segment. The class index
is the order that the classes are shown
in the classifier dialog. Products need
to use a consistent class layout
otherwise a class can be at a different
indie based on the product style
loaded. x is from 1 to100
4.22.2 Segment.Current Data

The Segment.Current tags are from the segment that is currently being
inspected and not finished yet.
1 Segment.Current.Data Ready Integer RW Set to a 1 when new segment data has
data.
2 Segment.Current.DateTime String R Time stamp – yyyymmddhhmmss
3 Segment.Current.Index Integer R This is the segments index. The first
segment is 0.
4 Segment.Current.ID String R This is the segments ID. The ID can
start at a non-zero value based on
segment options.
5 Segment.Current.MD Start Float R Segment starting position
6 Segment.Current.MD End Float R Segment ending position
7 Segment.Current.CD Float R Segment crossweb position
8 Segment.Current.Width Float R Segment width
9 Segment.Current.Length Float R Segment length
10 Segment.Current.Lane Float R Lane that this segment is in.
11 Segment.Current.Area Float R Segment area
12 Segment.Current.Class X Count Integer R This is the count of each class type
that is on the segment. The class index
is the order that the classes are shown
in the classifier dialog. Products need
to use a consistent class layout
otherwise a class can be at a different
indie based on the product style
loaded. x is from 1 to100

4.23 Segment Table Data

Central supports up to 5 tables that show data about each segment inspected.
These data items will only contain data if the segment option is enabled and the
system is not configured for segments by lanes.
The ”Current” items are updated approximately once per second and
correspond to the segment that is being inspected and is not finished yet.
The ”Last” items are updated when the current segment being inspected is
finished.
1 SegmentTable.Table n.Header.Number Integer RW Number of columns in the table.
Columns
2 SegmentTable.Table n.Header.Column x String R Each columns header text from the
table. The number of columns (x) is
depends on the table configuration.
3 SegmentTable.Table n.Current.Column x Integer R Value of the current row in the table
that is being updated by the current
segment that Is being inspected. The
number of columns (x) is depends on
the table configuration.
4 SegmentTable.Table n.Current.DateTime String R Time stamp – yyyymmddhhmmss
5 SegmentTable.Table n.Current.Date String R Date using date format on Central
production header.
6 SegmentTable.Table n.Current. Time String R Time using time format on Central
production header.
7 SegmentTable.Table n.Current.Data String R Set to a 1 when new segment data
Ready has been posted. The OPC Client
should set this back to a 0 after
reading the data.
8 SegmentTable.Table n.Last.Column x Integer R Value of the last row in the table that
just finished which corresponds to the
segment that just finished. The
number of columns (x) is depends on
the table configuration.
9 SegmentTable.Table n.Last.DateTime String R Time stamp – yyyymmddhhmmss
10 SegmentTable.Table n.Last.Date String R Date using date format on Central
production header.
11 SegmentTable.Table n.Last. Time String R Time using time format on Central
production header.
12 SegmentTable.Table n.Last.Data Ready String R Set to a 1 when the segment data has
data.

4.24 Statistics Data

4.24.1 Class Statistics Data
The Statistics data contains the following statistical values for each defect class and the total
defect counts.
Item Statistic Type RW Usage
1 Count Int32 R Defect count
2 Area Float R Sum of the area of the defects
3 Count div Prod length Float R Defect count/product length
4 Count div Prod area Float R Defect count/product area
5 Count div Prod mass Float R Defect count/product mass
6 Count div weight in kg Float R Defect count/weight in kg
7 Count div weight in t Float R Defect count/weight in t
8 Area div Prod area Float R Defect area sum /product area
9 Area div Prod mass Float R Defect area sum /product mass
10 Area div weight in kg Float R Defect area sum /weight in kg
11 Area div weight in t Float R Defect area sum /weight in t
12 PPM Float R Defect area in mm²/product area in
mm² * 1000000
13 Class name String R Name of the class for this statistic
14 Score Float R Defect sum/product area * class
normalize value
The current and last rolls statistics are collected for each class and the total counts. The EOR
or last roll data is updated at the roll reset. And, the current values are cleared at the end of
the roll in preparation for the next roll.
1 Stats.Current.Total ___ __ Statistic Values for total defects on the current
Defects.<statistic> roll.
2 Stats.Current.Bright ___ __ Statistic Values for total bright defects on the
Defects.<statistic> current roll.
3 Stats.Current.Dark ___ __ Statistic Values for total dark defects on the
Defects.<statistic> current roll
4 Stats.Current.BD.<statistic> ___ __ Statistic Values for total bright/dark defects on the
current roll
5 Stats.Current.Class ___ __ Statistic Values for class x on the current roll. x
x.<statistic> can be from 1 to 100 corresponding to the first
100 defect classes.
6 Stats.Current.Footage Float R Current roll footage
7 Stats.Current.Roll Diameter Float R Current diameter of the roll
8 Stats.Current.Product Area Float R Current product area
9 Stats.Current.Velocity Float R Current velocity
10 Stats.Current.Mass Float R Current mass
11 Stats.Current.Weight KG Float R Current weight in kg
12 Stats.Current.Weight T Float R Current weight in metric tons
13 Stats.Current.Roll Number String R Current roll number
14 Stats.Current.Lot Id String R Current lot Id
15 Stats.Current.Order Id String R Current order Id
16 Stats.Current.Data Ready Integer RW This is set to 1 when the data is updated. Can be
cleared by client or the tag will be cleared
automatically after about 1 second.
17 Stats.EOR.Total ___ __ Statistic Values for total defects on the last roll.

Defects.<statistic> Set at the end of the roll (EOR).

18 Stats. EOR.Bright ___ __ Statistic Values for total bright defects on the last
Defects.<statistic> roll. Set at the end of the roll (EOR).
19 Stats. EOR.Dark ___ __ Statistic Values for total dark defects on the last
Defects.<statistic> roll. Set at the end of the roll (EOR).
20 Stats. EOR.BD.<statistic> ___ __ Statistic Values for total bright/dark defects on the
last roll. Set at the end of the roll (EOR).
21 Stats. EOR.Class x.<statistic> ___ __ Statistic Values for class x on the last roll. x can
be from 1 to 100 corresponding to the first 100
defect classes. Set at the end of the roll (EOR).
22 Stats.EOR.Footage Float R End of roll footage
23 Stats.EOR.Roll Diameter Float R End of roll diameter of the roll
24 Stats.EOR.Product Area Float R End of roll product area
25 Stats.EOR.Velocity Float R End of roll velocity
26 Stats.EOR.Mass Float R End of roll mass
27 Stats.EOR.Weight KG Float R End of roll weight in kg
28 Stats.EOR.Weight T Float R End of roll weight in metric tons
29 Stats.EOR.Roll Number String R End of roll roll number
30 Stats.EOR.Lot Id String R End of roll lot Id
31 Stats.EOR.Order Id String R End of roll order Id
32 Stats.EOR.Data Ready Integer RW This is set to 1 when the data is updated. Can be
cleared by client or the tag will be cleared
automatically after about 1 second.
4.24.2 Lane Statistics Data

Lane statistics contain the lane state based on the alarms that have been asserted for the
lane.
Item Item String Usage
1 Stats.Current.Lane x.State This is the worst case state for the last n seconds of
production as set by the alarms for the lane. The time
between data updates can be set in the program
options.
1=OK; 2=Warn; 2=Fail
2 Stats.Current.Lane x.MaxState This is the worst case state for the current production
roll as set by the alarms for the lane.
1=OK; 2=Warn; 2=Fail
3 Stats.Current.Lane x.Roll Num This is the sub roll number that was set in the
Prod.This Sub Roll fields for the lane.
4 Stats.EOR.Lane x.State This is the worst case state for the roll as set by the
alarms for the lane. 1=OK; 2=Warn; 2=Fail
5 Stats.EOR.Lane x.Roll Num This is the sub roll number that was set in the
Prod.This Sub Roll fields for the lane.

4.25 Sync Data

The Sync data is used to synchronize the inspection system position to the production line
position.

1 Sync.Sync To Position Float RW Production line position when the
sync pulse is set.
2 Sync.Sync ISRA Position Float R The inspection system position when
the sync pulse is received from the
production line.
3 Sync.Delta Float R The position difference between the
production line and the inspection
system.
4.25.1 Synchronization input configuration

An input needs to be configured in the inspection system to receive the Sync pulse from the
production line.
4.25.2 OPC Sync Settings

In the OPC settings dialog the sync method and sync input need to be set.

4.25.3 Synchronization Logic

1. The Sync pulse is set by the production line
2. OPC tag “Sync.Sync To Position” is set by the production line corresponding to the
position when the Sync pulse was set.
3. Inspection system receives the input and the position at which it occurred.
4. The inputs position and “Sync.Sync To position” are used to calculate an MD adjustment
value and the inspection system is adjusted.
5. OPC writes the sync pulse position to the “Sync.Sync ISRA position”.
6. OPC writes the difference between the production and inspection positions in “Sync.Delta”.
Note: Often the inspection 0 reference is not at the same position as the production line 0
reference which is usually at the cutter which will end the roll. The inspection system has an
option to move the meters of product between the inspection system and the cutter to the next
roll. The “Sync To Position” set by the production line should be relative to the production line
0 reference and the OPC sync logic will take into account the distance that has been set to
move to the next roll when synchronizing the two positions. In this case the inspection system
position should always be ahead of the production line position by the distance that is between
the two. At the roll reset the meters of product between the two will be moved to the next roll
and the final roll footage recorded by ISRA will be reduced by the distance between the two
and will then match the production line distance.
4.26 System Data

1 System.CentralIP String R If connecting remotely, this will show the PC
name or IP address of the target Inspection
PC.
2 System.ConnectedToCentral Int32 R 0= not connected
1= connected
3 System.ISRAOPCUAVersion String R Program version
4 System.CentralVersion String R Program version of Central
5 System.SystemDriveFreeSpace Int32 R Percentage of free drive space on the
system drive (normally D drive).
6 System.DataDriveFreeSpace Int32 R Percentage of free drive space on the data
drive (normally E drive).
7 System.Mirror1DriveFreeSpace Int32 R Percentage of free drive space on the mirror
1 data drive.
8 System.Mirror2DriveFreeSpace Int32 R Percentage of free drive space on the mirror
2 data drive.
9 System. PercentMemoryUsed Int32 R Percentage of PC memory in use.
10 System.PercentCPUUsed Int32 R CPU Percent usage
4.27 System Parameters

1 System Parameter.Standby Float RW When the velocity drops below this

Velocity Threshold value, the inspection will be placed
into standby. Note: This setting only


takes affect if this option has been
enabled in the System Options
dialog.
2 System Parameter.Inspect Velocity Float RW When the velocity goes above this
Threshold value, the inspection will be placed
into inspection mode. Note: This
setting only takes affect if this option
has been enabled in the System
Options dialog and the system went
into standby due to low velocity.
3 System Parameter.At Reset Move Float RW This is the amount of product that will
Last Distance be moved to the next roll at a roll
reset. This setting only takes affect if
this ability has been enabled in the
System Options dialog.
4 System Parameter.At Reset Delete Float RW This is the amount of product that will
Last Distance be deleted from the end of the roll at
a roll reset. This setting only takes
affect if this ability has been enabled
in the System Options dialog.
5 System Parameter. Ignore Roll Min Float RW The production run data can be
Length ignored if the roll length is < than this
amount. This setting only takes affect
if this ability has been enabled in the
System Options dialog.
6 System Parameter.On Change String RW The roll number will be set to this
Roll Number value when another production field is
changed such as the lot Id. This
feature has to be enabled and
configured in the System Options
dialog.
7 System Parameter.Encoder Float RW This is the encoder resolution for the
Resolution encoder the system is using. Care
should be exercised when using this
value as it will affect system
performance.
8 System Parameter.Repeat Float RW This is the stretch factor that can be
Distance Stretch Factor applied to specific repeating
distances
9 System Parameter. Roll Segment Float RW This is the roll segment offset value.
Offset This setting only takes effect of the
roll segment ability is enable
10 System Parameter. Rtviewer Float W The roll map and image list on the
Distance Offset real time viewer have options to use
this to show the product relative to
the real time viewer’s position. The
value will be sent to all real time
viewers connected to the inspection
system.

4.28 System Recipe CRC’s

The CRC is a checksum of the parameters for a file. If parameters are changed
by the user or if a different recipe is loaded, then the CRC will change.
1 System.RecipeCRCs.Product File Int32 R Product file CRC
2 System.RecipeCRCs.Alarm File Int32 R Alarm file CRC
3 System.RecipeCRCs.Classifier File Int32 R Classifier file CRC
4 System.RecipeCRCs.Graph File Int32 R Graph file CRC
5 System.RecipeCRCs.Lane File Int32 R Lane file CRC
6 System.RecipeCRCs.Segement File Int32 R Segment file CRC
7 System.RecipeCRCs.Edge Analyzer File Int32 R Edge analyzer file CRC
8 System.RecipeCRCs.CInspection Settings File Int32 R Inspection settings file CRC
9 System.RecipeCRCs.IP File Int32 R IP file CRC
4.29 System Configuration Information

1 System.Configuration.Number Banks Int32 R Number of camera banks in the
system.
2 System.Configuration.Bank x.Number Cameras Int32 R Number of cameras for the bank x
is the bank index – from 1 to 6
3 System.Configuration.Bank x.Board Type String R Board type for bank x
4 System.Configuration.Bank x.Camera Type String R Camera type for bank x
5 System.Configuration.Config CRC Int32 R Configuration checksum
calculated from the above
configuration tag values.

4.30 Trend Graph Data

The Trend graph data contains trend information calculated by each trend graph
configured in the system. There can be up to 10 trend graphs and up to 10 data
series shown on each graph.
These tags are dependent on the graph setup. If the setup is changed or
a product is loaded that has a different graph configuration, then the
values that these tags represent can change. To use the tags without issue
it is best to configure all products to use the same graph settings.
The target and limits are write only data tags. This is done to prevent
ISRA from altering limits on the customer’s equipment. The INI key
TrendGraphDataLimitsTagsReadWrite can be set to 1 to change this tag to
RW.
1 Trend.Graph x.Graph Name String R The name of graph x.
x is the graph index from 1 to 10.
2 Trend.Graph x.Upper limit Float W This is the upper limit setting for the graph. Note
that the limits can be set as an absolute value or
relative to the target value as set by an option in
the trend graph.
3 Trend.Graph x.Upper warn Float W This is the upper warning limit setting for the
limit graph. Note that the limits can be set as an
absolute value or relative to the target value as
set by an option in the trend graph.
4 Trend.Graph x.Target value Float W This is the idea target value for the trend data.
5 Trend.Graph x.Lower warn Float W This is the lower warning limit setting for the
limit graph. Note that the limits can be set as an
absolute value or relative to the target value as
set by an option in the trend graph.
6 Trend.Graph x.Lower limit Float W This is the lower limit setting for the graph. Note
that the limits can be set as an absolute value or
relative to the target value as set by an option in
the trend graph.
7 Trend.Graph x.Position Float R Position of the last point updated.
8 Trend.Graph x.Area Float R Area of the last trend interval.
9 Trend.Graph x.Mass Float R Mass of the last trend interval.
10 Trend.Graph x.Weight kg Float R Weight in kg of the last trend interval.
11 Trend.Graph x.Weight t Float R Weight in metric tons of the last trend interval.
4.30.1 Last Trend Data

This is the last data point that finished on the graph. For graphs that update with
completed finished data these values will be the same as the current data
values.
1 Trend.Graph x.Series Float R Value of the last data point added for series n of
n.Last.Value graph x.
2 Trend.Graph x.Series n. Float R Average data value for series n of graph x.
Last.Average
3 Trend.Graph x.Series n. Float R Standard deviation of the data value for series n
Last.Stddev of graph x.

4 Trend.Graph x.Series n. Float R Minimum data value for series n of graph x.

Last.Minimum
5 Trend.Graph x.Series Float R Maximum data value for series n of graph x.
n.Last.Maximum
6 Trend.Graph x.Series Float R Sum of the data value for series n of graph x.
n.Last.Sum
7 Trend.Graph x.Series Int32 RW Set to a 1 when the last trend data has been
n.Last.Data Ready posted. The OPC Client should set this back to a
0 after reading the data.
4.30.1 Current Trend Data

This is the current data point that is accumulating data on the graph. Note that
some trend graph modes only show new data when the data is completely
done. In this case the current data will be the same as the last data tags.
1 Trend.Graph x.Series Float R Value of the last data point added for series n of
n.Current.Value graph x.
2 Trend.Graph x.Series n. Float R Average data value for series n of graph x.
Current.Average
3 Trend.Graph x.Series n. Float R Standard deviation of the data value for series n
Current.Stddev of graph x.
4 Trend.Graph x.Series n. Float R Minimum data value for series n of graph x.
Current.Minimum
5 Trend.Graph x.Series Float R Maximum data value for series n of graph x.
n.Current Maximum
6 Trend.Graph x.Series n. Float R Sum of the data value for series n of graph x.
Current.Sum
n.Last.Data Ready posted. The OPC Client should set this back to a
4.30.2 EOR Trend Data

These tags are the end of roll statistics from the trend points collected during
the run.
1 Trend.Graph x.Series Float R End of roll average data value for series n of
n.EOR.Average graph x. Set at the end of the roll.
2 Trend.Graph x.Series Float R End of roll standard deviation of the data value
n.EOR.Stddev for series n of graph x. Set at the end of the roll.
3 Trend.Graph x.Series Float R End of roll minimum data value for series n of
n.EOR.Minimum graph x. Set at the end of the roll.
4 Trend.Graph x.Series Float R End of roll maximum data value for series n of
n.EOR.Maximum graph x. Set at the end of the roll.
5 Trend.Graph x.Series Float R End of roll sum of the data value for series n of
n.EOR.Sum graph x. Set at the end of the roll.
n.EOR.Data Ready posted. The OPC Client should set this back to a

4.31 Video Analysis Data

The video analysis data tags will contain data from the video analysis option or
the web statistics option. Both options divide the web into x lanes of area and
calculate video statistics on each lane. The OPC server supports up to 30 lanes
of analysis data.
1 Video Analysis.Bank n.Num Integer R This is the number of lanes that have
Lanes been configured for the analysis
module.
Note: This is not the same number of
lanes that is configured in the Lane
Setup dialog.
2 Video Analysis.Bank n.Lane x Avg Float R This is the average video intensity for
each lane. Only the lanes what have
been configured will have valid data.
3 Video Analysis.Bank n. Lane x SD Float R This is the standard deviation of the
video intensities for each lane. Only the
lanes what have been configured will
have valid data.
4 Video Analysis.Bank n.Lane x Roll Float R This is the roll average video intensity
Avg for each lane for all the samples taken
for a production run. Only the lanes
what have been configured will have
valid data.
5 Video Analysis.Bn Lane x Roll SD Float R This is the roll standard deviation of the
video intensities for each lane for all
the samples taken for a production run.
Only the lanes what have been
configured will have valid data.
4.32 Winder Data

1 Winder.Winder n.Footage Float R Current roll length for winder n.

n is 1 to 12.
2 Winder.Winder n.Sqr Area Float R Square area of product inspected for
winder n.
n is 1 to 12.
3 Winder.Winder n.Total Defects Integer R Total count of defects for winder n.
n is 1 to 12.
4 Winder.Winder n.This Roll String RW Set current winder roll number for
Number winder n.
n is 1 to 12.
5 Winder.Winder n.Next Roll String RW Set next winder roll number for winder
Number n.
n is 1 to 12.

6 Winder.Winder n.Winder Reset Integer RW 1 will do a winder reset for winder n

n is 1 to 12.
7 Winder.Winder n. Last Roll String RW This is the last winder roll number that
Number is finished for winder n.
1 will do a winder reset for winder n
n is 1 to 12.
8 Winder.Winder n. Change Roll String RW This will change the winder roll number
Number for the last finished roll on winder n.
1 will do a winder reset for winder n
n is 1 to 12.
9 Winder.Winder n.Online Integer RW This is the online state of the winder. 1
is the winder is online. 0 is the winder
is offline.

5 Metal Detector Option

5.1 Detector Layouts
5.1.1 Single detector row
The metal sections are one contiguous set of detectors.
5.1.2 Dual detector row - ½ Overlap

There are two rows of metal sections overlapped by 50% and the system
determines the logical metal section based on how the two detectors sense the
metal. For ex. If the section 1 of both rows sense metal, then the system will
report that metal was found in logical metal section 2 with a width of ½ a metal
section width. Note that if a row misses a metal event then the width output will
be the full section width. For ex: if row 1 section 3 senses metal but row2 does
not sense anything then the metal event will start at row 1’s section 3 position
and be the width of the complete section.

5.1.3 Dual detector row - ⅓ Overlap

There are two rows of metal sections overlapped by 33% and the system
determines the logical metal section based on how the two detectors sense the
metal. For ex. If the section 1 of row 2 sense metal, then the system will report
that metal was found in logical metal section 3 with a width of a ⅓ of a metal
section width. Because of this overlapping method the first and last logical
sections will produce metal events that are ⅔ of the width of a physical metal
section.

5.2 Metal Defect Tags

Use the Row 1 data tags for a metal detector with a single row of detectors.
For a metal detector with two rows both the row 1 tags and row 2 tags will be
used. The row 1 tags need to be the ones that start closer to the 0 position side
of the machine.
1 Metal Detector.ISRA Row 1 Data Integer RW This tag is set when the metal data is read
Read Ack by the OPC. This tag should be cleared by
customer.
Used if handshaking is enabled.
2 Metal Detector.ISRA Row 1 Data Integer RW When this tag goes high ISRA will read the
Ready metal defect information that was posted by
the metal detector.
Section
5 Metal Detector.ISRA Row 2 Data Integer RW This tag is set when the metal data is read
Read Ack by the OPC. This tag should be cleared by
customer.
6 Metal Detector.ISRA Row 2 Data Integer RW When this tag goes high ISRA will read the
Ready metal defect information that was posted by
the metal detector.
Section
5.2.1 Data Exchange Sequence with Handshaking
1. Customer sets section data

2. Customer sets data ready flag high
3. ISRA reads data ready flag high
4. ISRA reads metal defect information
5. ISRA sets acknowledge flag high
6. Customer lowers data ready flag
7. ISRA reads data ready flag as low
8. ISRA lowers acknowledge flag
Note: if the customer side doesn’t lower the data ready flag in step 6 then the ISRA
side will automatically clear the acknowledge and data ready flags after one second.
If handshaking is disabled, then the section data will be processed on receiving the
data.

5.3 Metal Detector Options Tab
Figure 5-1 Settings
Detector Settings
 Detector layout – The detector layout as defined in the previous section.
 Handshake – if set to enabled then the data will be handshakes. If disabled,
then the section data will be processed on receiving the data.
 Metal section width - This is the width of each of the metal detector sections.
 Number of metal sections Row 1 – The number of physical metal sections for
the single row method or for the first row in dual mode. This row should be the
one that starts closest to the 0 side of the machine.
 Metal section width - This is the width of each of the metal detector sections.
the single row method or for the first row in dual mode. This row should be the
one that starts closest to the 0 side of the machine.
the second row of detectors when in dual mode. The number of detectors in this
roll is normally the same as the first row but it can be one shorter.
 Dual detection timeout – in dual mode the system will buffer a detection from
one metal detector to give time for the other metal detector to report data. Once
both metal detectors have reported then the logical metal section will be

determined and a metal defect will be sent to the inspection system. If the other
detector doesn’t detect the metal event, then a metal defect will be created at
the section that did sense the metal and the metal defect width will be set to the
full section width.
 Metal 1 defect CD offset – the metal event CD position will be offset by this
amount.
 Metal 1 defect MD offset – the metal event MD position will be offset by this
amount.
 Metal 2 defect MD offset – the metal event MD position will be offset by this
amount.
Metal Defect Reporting

 Report Mode
o Assign to defect – This option will associate the metal detection to a
defect. If there are not any defects within the merge distance of the metal
event, then the metal event will be ignored.
o Create an alarm defect – This option will create an alarm defect using
the alarm Id. There is no attempt to associate the metal event with a
normal defect.
o Assign to defect or create alarm defect – This option will attempt to
associate the metal event to a defect. If there are not any defects within
the merge distance of the metal event, then the system will create an
alarm defect for the metal event.
o Assign to defect and create alarm defect - This option will attempt to
associate the metal data to a defect. It will also create an alarm defect
for the metal event regardless of it being associated with a defect or not.
o Create a class defect – This option will create a defect that will be
processed by the standard classifier list. Classes need to be added with
the class defect type set to Metal source. The various metal data such as
height data will be assigned to the defect and can be used in the
standard class logic.

Multiple classes can be configured to classify this defect type.
The metal level ability setting should be set to multi-level data and
it only needs one level as the classifier can support multiple defect
types in this mode.
 Metal defect length – The length of the metal particle is not known. Thus, the
length will be set to this value. For the defect to be displayed on the Inspection
system correctly, a defect must have a valid length.
 Store ISRA section in - this will set the external feature in the defect event to
store the ISRA section which is the logical metal section that detected the
metal.
 Store metal 1 section in - this will set the external feature in the defect event
to store the metal 1 physical section that detected the metal.
 Store metal 2 section in - this will set the external feature in the defect event
to store the metal 2 physical section that detected the metal.
 Store Metal amplitude in - this will set the external feature in the defect event
to store the amplitude value. This feature can be used in classification of the
defect.
 Reverse map the metal defects – this option will reverse the metal defect
positions. It is needed for cases where the metal detector 0 position is opposite
of the inspection system 0 position.
 Metal Level Ability
o None– This option will associate the metal detection to a defect. If there
are not any defects within the merge distance of the metal event, then
the metal event will be ignored.
o Multi-Level data – this option allows different alarm defects to be
created based on the metal amplitude sent from the metal detector. Each
level has a threshold and an alarm ID to control the alarm that will be
used at each level. If the report mode is set to “Create a class defect”
then only one level needs to be set and the alarm ID will be used in
creating the defect so an alarm needs to be created in Central with that
ID.
 Alarm ID– the alarm ID is used to create an alarm event when the metal level
ability is set to None.
o An alarm on the Inspection System should be configured as follows:
 The alarm method should be set to “External Alarm Event”.
 The alarm should be set to generate a defect when it is asserted.
 For the Multi-level data method an alarm should be created for
each alarm ID defined for each level.

Metal to Defect Merging

These settings are used to control how a metal event will merge with a defect from
the inspection system.
 X merge distance – the metal data will be assigned to the defect that is within
merge X distance to the metal event position.
 Y merge distance – the metal data will be assigned to the defect that is within
merge Y distance to the metal position.
 Hold defect distance – if the metal has not been assigned to a defect within
this distance, then it is either reported as an alarm defect or discarded based on
the report mode.
Metal Testing
These settings are used to generate metal test defects. The user can set the
section for each metal detector row and the amplitude for the detection. The metal
event is sent to the inspection system and can be used to verify the setup.

ISRA OPC UA Server Module - V2.1.4 - Eng

Uploaded by

Copyright:

Available Formats

ISRA OPC UA Server Module - V2.1.4 - Eng

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ISRA OPC UA Server Module - V2.1.4 - Eng

Uploaded by

Copyright:

Available Formats

SMASH

Web Inspection System

Original - May 2018,

We have taken the greatest of care in the preparation of this document.

Title of Documentation SMASH

Last Change 28September2023

2 SMASH – ISRA OPC UA Server Module

SMASH – ISRA OPC UA Server Module 3

4.8 Defect JSON Format .................................................................................. 28

4 SMASH – ISRA OPC UA Server Module

5.1 Detector Layouts ........................................................................................ 61

SMASH – ISRA OPC UA Server Module 5

Figure 1-1 Overview

6 SMASH – ISRA OPC UA Server Module

Figure 2-1 Data Monitor

SMASH – ISRA OPC UA Server Module 7

Figure 2-2 Tag properties

 Description – this should describe the tags usage.

Figure 2-3 Browse dialog

8 SMASH – ISRA OPC UA Server Module

2.2 System Settings Tab

Figure 2-4 System Settings

2.2.1 Central Connection

SMASH – ISRA OPC UA Server Module 9

2.2.3 Tag Group Enables

2.3 Options Tab

Figure 2-5 Settings

2.3.1 Defect Tag Options

10 SMASH – ISRA OPC UA Server Module

2.3.2 Parameter Control Options

2.3.3 Flag Tag Options

SMASH – ISRA OPC UA Server Module 11

2.3.4 Position Synchronization

12 SMASH – ISRA OPC UA Server Module

3.2 Running the Program as a Service

3.3 Changing the Default Port

SMASH – ISRA OPC UA Server Module 13

3.4 Example Client Connection

Figure 3-1 Enter URL

Upon connection the test server shows the available tags

Figure 3-2 Available tags

14 SMASH – ISRA OPC UA Server Module

3.5 Certificate Usage

3.5.1 Enabling Certificate Creation

In the settings file D:\OPCUAServer\ini\OPCUAServer.ini set the enabled key to

3.5.2 Creating a Certificate

SMASH – ISRA OPC UA Server Module 15

3.5.3 Using the Certificate

16 SMASH – ISRA OPC UA Server Module

4 OPC Data items

Item Item String Type RW Usage

1 Alarm.Alarm x Name String R The name of the alarm.

4.2 App Data

1 AppData.Fieldx String RW x is from 1 to 10

SMASH – ISRA OPC UA Server Module 17

4.3 Bank Info Data

4.3.1 Bank Video Statistics Data

4.3.2 Camera Video Statistics Data