Manual Smart Robotic 300003099 E 2012 12 22
Manual Smart Robotic 300003099 E 2012 12 22
Manual Smart Robotic 300003099 E 2012 12 22
smart-robotic
Operating Instructions
BYK-Gardner GmbH
Table of Contents
1 Introduction.................................................................................................................................................. 7
1.1 Copyright............................................................................................................................................... 7
1.2 Prerequisites........................................................................................................................................... 8
1.3 Requirements......................................................................................................................................... 8
1.3.1 Hardware .................................................................................................................................... 8
1.3.2 Software ..................................................................................................................................... 8
5 OPC................................................................................................................................................................ 29
5.1 OPC Signal Basics................................................................................................................................... 29
5.2 OPC Server Settings ............................................................................................................................... 30
5.3 Common Control Signals ....................................................................................................................... 32
5.4 Common Job Signals.............................................................................................................................. 32
6 Devices.......................................................................................................................................................... 35
6.1 7036 - BYK-mac i ROBOTIC.................................................................................................................... 36
6.1.1 Connection Settings .................................................................................................................... 37
6.1.2 Device Configuration................................................................................................................... 38
6.1.3 OPC Control Signals .................................................................................................................... 39
6.1.4 OPC Point Signals........................................................................................................................ 40
6.1.5 Device Calibration ....................................................................................................................... 42
11 Appendix ......................................................................................................................................................155
11.1 Abbreviations......................................................................................................................................... 155
11.2 Error Handling........................................................................................................................................ 155
11.2.1 Error Code Transmission.............................................................................................................. 155
11.2.2 Usage of OPC Signals .................................................................................................................. 156
11.2.2.1 System-wide Error Messages........................................................................................ 156
11.2.2.2 Instrument-specific Error Messages .............................................................................. 156
11.3 Troubleshooting..................................................................................................................................... 157
11.4 XML Input File PELT................................................................................................................................ 158
11.4.1 Job Information........................................................................................................................... 158
11.4.2 Multiple Measurements............................................................................................................... 158
11.4.2.1 Measurement 1 ........................................................................................................... 158
11.4.2.1.1 Layer 1.......................................................................................................159
11.4.2.1.2 Layer 2.......................................................................................................159
11.4.2.1.3 Layer 3.......................................................................................................159
11.4.2.1.4 Layer 4.......................................................................................................159
11.4.2.2 Measurement 2 ........................................................................................................... 160
11.4.2.2.1 Layer 1.......................................................................................................160
11.4.2.2.2 Layer 2.......................................................................................................160
11.4.2.2.3 Layer 3.......................................................................................................161
11.4.2.2.4 Layer 4.......................................................................................................161
1 Introduction
Dear customer,
thank you for having decided for a BYK-Gardner product. BYK-Gardner is commit-
ted to providing you with quality products and services. We offer complete system
solutions to solve your problems in areas of color, appearance and physical proper-
ties. As the basis of our worldwide business, we strongly believe in total customer
satisfaction. Therefore, in addition to our products, we offer VALUE-ADDED ser-
vices:
• Technical Sales Force
• Technical & Application Support
• Application and Technical Seminars
• Repair & Certification Service
BYK-Gardner is part of the Altana Group and a direct subsidiary of BYK, the world-
wide leader of additives for coatings and plastics. Together we offer complete and
unique solutions for you, our customer.
Thank you for your trust and confidence. If there is anything we can do better to
serve your needs, do not hesitate to let us know.
Your BYK-Gardner Team
www.byk-instruments.com
1.1 Copyright
Specific properties and structural characteristics of the instrument are intellectual
property of BYK-Gardner. The copyright of this manual remains with BYK-Gardner.
This document must not be reproduced fully or in party, published or used for any
other competitive purposes, no matter whether against payment or not, without
prior written authorization from BYK-Gardner.
BYK-Gardner reserves the right to update the instrument, software and written
documentation without prior notice.
1.2 Prerequisites
In order to operate the software basic understanding of following topics is re-
quired:
• Products from BYK-Gardner:
– Instrument BYK-mac i ROBOTIC to measure effect colors
– Instrument wave-scan ROBOTIC and wave-scan 3 ROBOTIC to measure
appearance (orange peel)
– Software smart-process to monitor the measurement results
• Third-party products:
– Instruments for measuring the thickness
– OPC server for the control of the robot
– Pre-positioning system for robot moves
NOTICE
The software smart-process is a variant of the software smart-chart. After a trial
period of 30 days the software smart-chart has to be registered. During registra-
tion the variant smart-process has to be selected.
1.3 Requirements
1.3.1 Hardware
• Hardware: Intel Core-i3 2.5 GHz; Core-i7 recommended, or equivalent
• Memory: 8 GB RAM, 16 GB recommended
• Hard-disk capacity: 4 GB during installation
• Monitor resolution: 1920 x 1080 pixel or higher
• Interface: LAN port and free USB port
1.3.2 Software
• Operating system: Windows® 10 1607 or later
• Software smart-chart V7.1 or later
• Runtime: .NET core 3.1.0 or later
2 System Description
The software smart-robotic is the interface software for the BYK-Gardner robotic
color and appearance measurement instruments and for compatible thickness
measurement systems.
It provides all necessary modules for system configuration and monitoring for the
BYK-Gardner robotic instruments and for storing the measurement results:
1. Monitoring [} 27]: Check the logging of events such as errors, warnings,
debug events and info.
2. OPC [} 29]: Configure and test connection to the server hosting the interface
to the robot.
3. Devices [} 35]: Configure and test the physical robotic measurement instru-
ments.
4. Results Management:
– Without smart-chart: Generate Output Files [} 67] as CSV / XML.
– With smart-chart: Store results via smart-chart link [} 77] in the DB.
5. Robot Simulator [} 139]: Test the existing configuration and the physical in-
struments without the need of a robot.
2.1 Overview
The software can control following robotic measuring instruments:
• Color meter for effect colors: BYK-Gardner BYK-mac i ROBOTIC
• Appearance measurement:
– BYK-Gardner wave-scan ROBOTIC
– BYK-Gardner wave-scan 3 ROBOTIC
• Thickness measurement: Fisher or PELT
2.2 Mounting
The measurement instruments and a pre-positioning system are mounted to a ro-
bot arm. Via the pre-positioning system the target position is reached. The robot
arm rotates to bring the required instrument into measurement position. After-
wards the measurement is started. The measurement data are transferred immedi-
ately to smart-robotic and evaluated there.
3
4
Illustration 3: BYK-Gardner instruments mounted to robot arm
2.3 Integration
Following figure shows the basic integration principle of smart-robotic.
The products connected with blue arrows are delivered by BYK-Gardner. The prod-
ucts connected with white arrows are delivered by third parties.
NOTICE
The thickness measuring instruments are not controlled by smart-robotic. The
supported instruments create XML files (in a predefined format) which can be read
by smart-robotic and processed in smart-chart. Details see Thickness Measure-
ment [} 106] and PELT Measurement [} 121].
3 System Installation
Install and configure following components:
1. OPC Server (3rd Party) [} 13]
2. Software smart-chart [} 17]
3. Robotic Instruments [} 22]
NOTICE
The suggested refresh rate for each signal on the server is 10 ms.
ALL_CTRL.IN_ERR_ACK // Section #1
ALL_CTRL.IN_HEARTBEAT
ALL_CTRL.IN_JOB_START
ALL_CTRL.IN_JOB_STOP
ALL_CTRL.IN_REQU_CAL
ALL_CTRL.IN_REQU_DAILY_CHECK
ALL_CTRL.IN_REQU_MAST
ALL_CTRL.OUT_ERR_NO
ALL_CTRL.OUT_ERR_STROBE
ALL_CTRL.OUT_HEARTBEAT
ALL_CTRL.OUT_JOB_RUN
ALL_CTRL.OUT_JOB_SUCCESS
ALL_JOB.DATA_COLOR // Section #2
ALL_JOB.DATA_COMMENT
ALL_JOB.DATA_MODEL
ALL_JOB.DATA_PAINTLINE
ALL_JOB.DATA_VID
MAC1_CTRL.IN_CURVATURE
MAC1_CTRL.IN_ENABLE // Section #3
MAC1_CTRL.IN_POINT_POS
MAC1_CTRL.IN_SYS_ERR_ACK
MAC1_CTRL.OUT_CAL_OK
MAC1_CTRL.OUT_CORR_K
MAC1_CTRL.OUT_CORR_Q
MAC1_CTRL.OUT_CORR_VAL
MAC1_CTRL.OUT_CORR_Z
MAC1_CTRL.OUT_ERR_NO
MAC1_CTRL.OUT_ERR_STROBE
MAC1_CTRL.OUT_POINT_READY
MAC1_CTRL.OUT_POINT_RESULT
MAC1_CTRL.OUT_SYS_ERR
MAC1_POINT.IN_CHECKZONE
MAC1_POINT.IN_POINTNR
MAC2_CTRL.IN_CURVATURE
MAC2_CTRL.IN_ENABLE // Section #4
MAC2_CTRL.IN_POINT_POS
MAC2_CTRL.IN_SYS_ERR_ACK
MAC2_CTRL.OUT_CAL_OK
MAC2_CTRL.OUT_CORR_K
MAC2_CTRL.OUT_CORR_Q
MAC2_CTRL.OUT_CORR_VAL
MAC2_CTRL.OUT_CORR_Z
MAC2_CTRL.OUT_ERR_NO
MAC2_CTRL.OUT_ERR_STROBE
MAC2_CTRL.OUT_POINT_READY
MAC2_CTRL.OUT_POINT_RESULT
MAC2_CTRL.OUT_SYS_ERR
MAC2_POINT.IN_CHECKZONE
MAC2_POINT.IN_POINTNR
WAVE1_CTRL.IN_ENABLE // Section #5
WAVE1_CTRL.IN_POINT_POS
WAVE1_CTRL.IN_SYS_ERR_ACK
WAVE1_CTRL.OUT_ERR_NO
WAVE1_CTRL.OUT_ERR_STROBE
WAVE1_CTRL.OUT_POINT_READY
WAVE1_CTRL.OUT_POINT_RESULT
WAVE1_CTRL.OUT_SYS_ERR
WAVE1_POINT.IN_CHECKZONE
WAVE1_POINT.IN_POINTNR
WAVE2_CTRL.IN_ENABLE // Section #6
WAVE2_CTRL.IN_POINT_POS
WAVE2_CTRL.IN_SYS_ERR_ACK
WAVE2_CTRL.OUT_ERR_NO
WAVE2_CTRL.OUT_ERR_STROBE
WAVE2_CTRL.OUT_POINT_READY
WAVE2_CTRL.OUT_POINT_RESULT
WAVE2_CTRL.OUT_SYS_ERR
WAVE2_POINT.IN_CHECKZONE
WAVE2_POINT.IN_POINTNR
WAVE3_CTRL.IN_ENABLE // Section #7
WAVE3_CTRL.IN_POINT_POS
WAVE3_CTRL.IN_SYS_ERR_ACK
WAVE3_CTRL.OUT_ERR_NO
WAVE3_CTRL.OUT_ERR_STROBE
WAVE3_CTRL.OUT_POINT_READY
WAVE3_CTRL.OUT_POINT_RESULT
WAVE3_CTRL.OUT_SYS_ERR
WAVE3_POINT.IN_CHECKZONE
WAVE3_POINT.IN_POINTNR
RESULT_CTRL.IN_ACK // Section #8
RESULT_CTRL.OUT_READY
RESULT_DATA.OUT_COLOR
RESULT_DATA.OUT_COMMENT
RESULT_DATA.OUT_DATETIME
RESULT_DATA.OUT_INSTRUMENT
RESULT_DATA.OUT_MODEL
RESULT_DATA.OUT_PAINTLINE
RESULT_DATA.OUT_STATUS
RESULT_DATA.OUT_VID
NOTICE
1 This example list is required to describe the corresponding items in the configu-
ration of smart-robotic.
2 The signals listed above are examples only – you always HAVE to adapt the sig-
nals according to YOUR configuration(!).
NOTICE
Do not forget to adapt the list of OPC signals according to your required configu-
ration.
The software package also includes the necessary drivers for the BYK-Gardner ro-
botic instruments.
3.2.1 Download
The software package for BYK-mac i ROBOTIC and wave-scan ROBOTIC is the
same. To download the package go to following web-site:
• www.byk-instruments.com/byk-maci or
• www.byk-instruments.com/wave-scan
Via these links you can easily open and view the software package with your pre-
ferred browser application.
Illustration 5: Download-Software-Package
It is recommended to save the package on the hard drive of your PC before extrac-
tion or installation.
NOTICE
During beta phase an alternatively download link may be provided. In this case use
the alternative link. It will take some time until the latest software package has
been placed on our website.
3.2.2 Installation
NOTICE
You need administrator privilege on the PC in order to install the software pack-
age.
Illustration 6: Installed-Software-Package
After download and installation the software package can be used for 30 days
free trial. Thereafter, you need to register your software package. The standard de-
livery includes two PC licenses for the selected software package.
NOTICE
During registration you have to decide for smart-process. Afterwards the section
smart-lab will not be available anymore.
NOTICE
For a productive smart-robotic system the option SQL Server Connections >
Link existing database is recommended, see Integration [} 11].
3.2.3 Robotic
The software smart-robotic is installed along with smart-chart. For smart-robotic
following information is relevant:
• Program files: “C:\Program Files (x86)\BykWare\smart-robotic”
• Configuration files: “C:\ProgramData\BYK\smart-robotic”
To start the software open the file “SmartRobotic.exe”.
3.2.4 Runtime
Both smart-chart and smart-robotic are written in C# (C-Sharp). In order to run
the program the runtime .NET core is required.
3.2.5 Upgrade
The installer for smart-chart will uninstall an existing installation prior to the in-
stallation of a newer software version.
In case of fallback to an older version (downgrade) deinstall the older version man-
ually using the Windows functions.
In both scenarios the information stored in “C:\ProgramData\BYK\smart-chart”
and “C:\ProgramData\BYK\smart-robotic” remains unchanged.
WARNING
To avoid instrument damage, only use the cables which are part of the delivery for
connecting the instruments!
4 System Basics
It is recommended to perform all steps in a test environment in a first phase and to
bring the final configuration to the productive system in a second phase.
4.1 Startup
To startup the system perform following steps:
1. Start the OPC server.
2. Connect power supply to the instruments.
3. Connect the data cable to the instruments.
4. Start smart-robotic.
NOTICE
The complete configuration of the system - including connection testing and in-
strument testing - takes place in smart-robotic; no other software is needed.
4.2 Shutdown
The shutdown procedure is the startup procedure in reverse order. Perform follow-
ing steps:
1. Close smart-robotic with Alt + F4 or with the X symbol in the upper right
corner.
2. Disconnect the data cables from the instruments, if required.
3. Disconnect the power supply from the instruments, if required.
4. Close the OPC server.
The configuration done in smart-robotic is stored in an XML file. The file is placed
in the folder “C:\ProgramData\BYK\Robotic”. The name of the file is “Configura-
tion.xml_<Timestamp>.xml”.
Every day a new file is created. It is read when smart-robotic is started and writ-
ten when smart-robotic is closed. Backup these files in regular intervals.
NOTICE
If you have unsaved changes in the configuration, a confirmation message is dis-
played. You can close and save, close without saving or abort the program shut-
down.
4.3 Monitoring
On the Monitoring tab all important system messages are displayed. This tab is
used to check the logging of events such as errors, warnings, debug events and
info.
The log files are placed in the folder “C:\ProgramData\BYK\smart-robotic\Logs”.
Every day a separate file is written. Backup these files in regular intervals.
NOTICE
For more details on the error messages see Error Handling [} 46].
4.4 Operation
When all configuration and testing has finished in the test system the final config-
uration can be delivered to the productive system. Perform following steps:
1. Setup the productive system.
2. Copy the XML configuration file for smart-robotic.
3. Place it in the program folder for the productive system.
4. Start smart-robotic it in the productive system.
5. Make all necessary adaptations and save.
6. Restart smart-robotic.
The application is now listening to OPC signals coming from the OPC server. When
the signals arrive, the measurements are started according to the operation modes
described in Run Procedure [} 145].
5 OPC
On the tab OPC the connection to the OPC server and the communication be-
tween OPC server and smart-robotic is configured.
This communication is based on “OPC signals”. In general an OPC signal is defined
by its type and by its content / data. Different types of signals are supported.
Following information is provided:
1. OPC Signal Basics [} 29]
2. OPC Server Settings [} 30]
3. Common Control Signals [} 32]
4. Common Job Signals [} 32]
Signal Types
In smart-robotic different types of OPC signals are used for communication:
• Control Signals
• Job Data
• Point Data
Control Signals
Control data is needed for the operation of the measuring head. They represent a
so called handshake to the PLC. Here information is handed over such as start
measurement, measurement finished or errors. Control data is handed over for a
complete measuring instrument group and separately for each BYK-mac i RO-
BOTIC or wave-scan ROBOTIC.
Example: IN_JOB_START = Start a new measurement series on a car body.
Job Data
General data for a job. A job is e.g. a vehicle or a component and can consist of
many measuring points. These data are valid for all measuring instruments used in
a group.
Example: TYPE = Denotes the model of the measured car body, e.g. “SUV”.
Point Data
General data for a measuring point, for example measuring point coordinates or
point numbers. These data are handed over separately for each measuring instru-
ment.
Example: PART = Denotes the measured part on the car body, e.g. “Roof”.
5. Legacy BYKlink Error Handling: Check this option to activate the global er-
ror handling. Uncheck this option to activate instrument-specific error han-
dling. For more details see Error Handling [} 155] in the appendix.
NOTICE
1 In earlier versions of smart-robotic the “OPC signals” were referenced as “OPC
items”.
2 The list of signals must match on OPC server and in smart-robotic.
3 “BYKlink” was the predecessor of the software smart-robotic.
• Paintline
• Comment
• Vehicle ID
Perform following steps:
1. Click the tab Common Job Signals.
2. Add a new entry by clicking on the button Add.
3. Modify an existing entry by clicking on the button Edit.
4. Delete an existing entry (without confirmation) by clicking on the button Re-
move.
5. Check if the connection status for all signals is Connected.
6. If status is Not found, check / edit the signals in the OPC server and restart
smart-robotic.
2. Alias: A free value. Under this name the parameter can be used for outputting
the measurement result files and for naming the files.
3. Type: Defines the parameter type used.
– Boolean
– Double
– Float
– Integer
– String
NOTICE
For Name and Alias the value can be entered manually or via copy / paste func-
tion.
4 System Basics
It is recommended to perform all steps in a test environment in a first phase and to
bring the final configuration to the productive system in a second phase.
4.1 Startup
To startup the system perform following steps:
1. Start the OPC server.
2. Connect power supply to the instruments.
3. Connect the data cable to the instruments.
4. Start smart-robotic.
NOTICE
The complete configuration of the system - including connection testing and in-
strument testing - takes place in smart-robotic; no other software is needed.
NOTICE
If necessary, restart smart-robotic in order to take changes made to the configura-
tion into effect.
NOTICE
These configurations options are known from smart-chart. For the hand-held in-
struments, these configurations are covered by the smart-chart items Standard and
Organizer Management.
3
1
2 4
NOTICE
1 Checks are recommended daily.
2 Calibration is recommended monthly.
3 New certificate is recommended yearly.
3 2 1
NOTICE
1 It is recommended to mount the tiles vertically. This avoids collection of dust on
the tiles, which could falsify the calibration and test process.
2 Make sure the four rubber buffers on the feet of each standard are in place and
in good condition. Order spare parts if necessary.
NOTICE
For more details on calibration and check see Device Test [} 47].
NOTICE
1 Some entries are always system errors and can not be deactivated.
2 Some entries are never system errors and can not be activated.
NOTICE
Make sure the standard values given in the certificate for your instrument have
been stored in smart-robotic, see Data in Certificate [} 42]. Otherwise the device
test will not finish successfully.
6.1.7.1 Initialize
To initialize the device test perform following steps:
1. Make sure the instrument is connected – see Connection Settings [} 37].
2. Remove the dust protection from one of the standards.
3. Remove protective cap from the instrument.
4. Place the instrument on the standard.
5. Click the button Initialize.
This function prepares the instrument for measuring and calibration / testing.
Illustration 41: BYK-mac-Device-Test-Initialize
The systems responses with Preparing OK.
6.1.7.2 Measure
Click the button Measure to take a measurement.
Illustration 42: BYK-mac-Device-Test-Measure
The measured data is stored in the instrument memory.
Illustration 43: BYK-mac-Device-Test-Reading
Scroll up and down to see all data.
1 2
3 4
Illustration 45: BYK-mac-Calibration-Pins
Place the instrument on the white calibration standard.
Illustration 47: BYK-mac-Device-Test-Calibrate-Message
If the positioning was not performed correctly, the message “Robotic calibration
switch not pressed” will be displayed. Repeat the procedure.
Illustration 48: BYK-mac-Device-Test-Calibrate-Failed
If the positioning was performed correctly the instrument performs following steps
– see Data in Certificate [} 42]:
1. Pin calibration
2. White calibration
3. Camera / effect calibration
4. Measurement
The progress is displayed in the screen.
Illustration 49: BYK-mac-Device-Test-Calibrate-OK
NOTICE
The re-calibration and the issue of a new certificate is recommended once a year.
Illustration 50: BYK-mac-Device-Test-Color
The results of the color check - in the L*a*b* color system - are shown on the
screen.
Illustration 51: BYK-mac-Device-Test-Effect
The results of the effect check - amount of sparkle under different angles - are
shown on the screen.
NOTICE
Information, warnings and errors will be logged in the log file and displayed in the
Monitoring [} 27] screen.
8.1.4 Organizers
The module Organizer is used to configure the check points / zones to be mea-
sured. The organizer management comprises following steps:
• Model [} 83]
• Standards [} 84]
• Paint line [} 85]
• Instruments [} 86]
• Check zones [} 87]
NOTICE
It is recommended to program the robot with an offset scan length for the acceler-
ation ramp.
• Available Scales: The measurement results can be calculated according the var-
ious scales available. All these scales are customer-specific.
• Basic Scales (Always included): The calculation according to these scales takes
place always.
• Selected Scales (User defined): Select required scales by clicking the arrow but-
ton in the Available Scales list. They appear under Selected Scales and can be
removed from here using the X button.
NOTICE
With the hand-held instruments, these configurations are covered by the smart-
chart Standard and Organizer Management or via the measurement parameters in
the device configuration.
2
1
3
In the test setup shown above the probe is fix installed. Thus only the dullness can
be measured – all other values are zero. In order to get all data included wave-
length details you have two options:
• Slowly move the sample or
• slowly move the instrument.
The example file shown above contains meta data including time stamp, car
model, color and check points / zones as well as measurement data of the wave-
scan ROBOTIC. In order to process this data with the corresponding organizer and
standard in smart-chart, the data must be mapped.
NOTICE
Below the example device wave-scan ROBOTIC is shown. The configuration for
the BYK-mac i ROBOTIC is analogue.
NOTICE
The wave-scan 3 ROBOTIC is much more powerful than its predecessor wave-scan
ROBOTIC. The new device has a modern processor and sufficient memory to calcu-
late ALL scales immediately. Thus the configuration of the scales can be omitted
here – all this data will be available always.
7 Output Files
In the Output files tab, additional user-defined output files can be defined for fol-
lowing instruments:
• BYK-Gardner BYK-mac i ROBOTIC
• BYK-Gardner wave-scan ROBOTIC
• Compatible thickness measurement instruments
This is optional and does not influence the measurement data stored in the smart-
chart database.
Illustration 67: Output-Files-Main-Window
In order to create such an additional output file, select an instrument and click the
button Add Storage to add a new output file for configuration.
Illustration 68: Output-Files-Add-Menu
Depending on the instrument, different options appear in the context menu to
generate different output files:
• Normal measurement
• Calibration
• Daily check
Illustration 69: Output-Files-Add-Details
Complete configurations get a green icon; incomplete a red icon. To complete en-
ter following details:
1. Output Directory [} 69]
2. Output Filename [} 70]
3. Template File [} 71]
4. Quality Status [} 74]
5. Active Devices [} 76]
These tasks are described below.
NOTICE
1 If multiple output files have been defined, multiple output files will be gener-
ated.
2 In the example shown above three configurations exist for “Measurement”.
3 So for each measurement job these three files will be generated.
Illustration 70: Output-Files-Directory-Set
In the example shown above following directories will be used:
• C:\ProgramData\BYK\Robotic\TemplateFiles
Following sub-directories will also be created in the given location:
• ..\TemplateFiles\BykMacJob
• ..\TemplateFiles\WavescanJob
NOTICE
The application allows copy and paste for most input options. This way you can ex-
change existing information between different configurations or external editors.
Illustration 71: Output-Files-Filename-Set
The button Define opens an editor to configure the file name using predefined
items of measurement metadata - e.g. timestamp, color or vehicle ID – and free
text – e.g. separators and file extension.
NOTICE
1 After adding all required fields use Drag & Drop to bring a field into correct posi-
tion.
2 Do not forget to append the file name with an appropriate file type like “.csv”
or “.xml”.
3 The extension is to be entered in the Definition designer – not in the Output file
definition(!).
Illustration 72: Output-Files-Template-Editor
Perform following steps:
1. Choose a File Name for the template.
2. Add the Predefined Items in the Header box.
3. Add the Predefined Items in the Measurement Data box.
4. Add appropriate text in the Footer box.
Following rules apply:
• The section Header will appear once at the top.
• The section Measurement data will appear for every check zone.
• The section Footer will appear once at the end of the file.
Write free text to structure the data with XML tags or CSV column names.
NOTICE
Follow conventions such as “;” separator for CSV files for structuring text and pre-
defined items.
Header
<?xml version="1.0"?>
<wave-scan-robotic>
<jobdata>
<timestamp>$TIMESTAMP§</timestamp>
<jobquality>$QUALITY§</jobquality>
<carmodel>$Car-Model§</carmodel>
<carcolor>$Car-Color§</carcolor>
<paintline>$Paint-Line§</paintline>
<comment>$Free-Comment§</comment>
<vehicleid>$Vehicle-ID§</vehicleid>
</jobdata>
<points count="$MEAS_COUNT§">
Measurement data
<point>
<time>$TIME§</time>
<serialnr>$Serial number§</serialnr>
<catalognr>$Catalogue nr.§</catalognr>
<status>$STATUS§</status>
<zoneid>$Checkzone-Index§</zoneid>
<zone>$Checkzone-Name§</zone>
<scale Id="01 LW" value="$LW§" />
<scale Id="02 SW" value="$SW§" />
<scale Id="19 We" value="$We§" />
<scale Id="20 Wd" value="$Wd§" />
<scale Id="21 Wc" value="$Wc§" />
<scale Id="22 Wb" value="$Wb§" />
<scale Id="23 Wa" value="$Wa§" />
<scale Id="24 Du" value="$du§" />
</point>
Footer
</points count>
</wave-scan-robotic>
With the example template shown above the following output XML file will be
created after a measurement.
<?xml version="1.0"?>
<wave-scan-robotic>
<jobdata>
<timestamp>2020-10-06T17:38:33</timestamp>
<jobquality>Green</jobquality>
<carmodel>Combi</carmodel>
<carcolor>Pearl</carcolor>
<paintline>PL1</paintline>
<comment>Created with simulator.</comment>
<vehicleid>123456</vehicleid>
</jobdata>
<points count="1">
<point>
<time>2020-10-06T17:38:38</time>
<serialnr>1213324</serialnr>
<catalognr>4822</catalognr>
<status>None</status>
<zoneid>4</zoneid>
<zone>rear bumper</zone>
<scale Id="01 LW" value="0" />
<scale Id="02 SW" value="0" />
<scale Id="19 We" value="0" />
<scale Id="20 Wd" value="0" />
<scale Id="21 Wc" value="0" />
<scale Id="22 Wb" value="0" />
<scale Id="23 Wa" value="0" />
<scale Id="24 Du" value="12,1" />
</point>
</points count>
</wave-scan-robotic>
NOTICE
The template files will be stored with extension “.btmp” in the sub-folders for the
BYK-mac and the wave-scan.
Illustration 73: Output-Files-Quality-Status
If you want to use traffic light status for pass / fail indication you can enter for ex-
ample:
• Within tolerances: Green
• In warning area: Yellow
• Out of tolerances: Red
If you want to use just OK / NOK for pass / fail indication only can enter for exam-
ple:
• Within tolerances: OK
• In warning area: OK or NOK (depending on your requirements)
• Out of tolerances: NOK
The defined text will appear in the Filename if the QUALITY item is inserted.
Illustration 74: Output-Files-Quality-Field
With the example configuration shown above the following file will be created.
2020-10-06T17_38_33-Combi-Pearl-Green.xml
Th status will also appear in the content of the output file if it is part of the tem-
plate, see example template file above.
<jobquality>$QUALITY§</jobquality>
…
<status>$STATUS§</status>
<jobquality>Green</jobquality>
…
<status>None</status>
NOTICE
In an output file with multiple measurement points (check zones) the status will be
inserted separately within each single point.
Illustration 75: Output-Files-Device-Select
The output file configuration for the other instrument types is analogue.
NOTICE
The output files will be generated when performing measurements with the ro-
botic instruments. The configuration can be tested with the Robot Simulator
[} 139].
8 smart-chart link
When using the software smart-chart for data analysis and tolerance settings, the
tab smart-chart link manages the connection between measurement devices,
OPC server and smart-chart. With the configuration of smart-chart link follow-
ing operations are supported:
• The information in the standard and organizer database is retrieved for pass /
fail check.
• The measurement results are stored in the measurement database according
to existing standards and organizers.
NOTICE
The generation of Output Files [} 67] can be used in addition to the storage in
the smart-chart database.
CAUTION
Do not use the module Instrument Management. It is not required for the inter-
action with smart-robotic and it is not possible to access the instrument from
smart-chart and smart-robotic at the same time. If you have used the module,
restart smart-chart without using it again.
See also
2 Installation [} 19]
8.1.1 Database
In smart-chart following databases are used:
• Standard Database [} 77]
• Measurement Database [} 78]
NOTICE
For the creation of this documentation a compact database file was used. Alter-
natively an SQL server connection can be used. This is the preferred option in a
production environment, see also Installation [} 19] of smart-chart.
8.1.2 Catalog
In the Catalog configuration the various parameters for identification of the mea-
sured objects are selected.
NOTICE
The Catalog for parameter 2 can not be configured here. It is always mapped to
the catalog “Color”.
8.1.3 Standards
The module Standard Management is used to configure the settings for the vari-
ous color standards. These standards can then be added the check zone organizers
later on. The configuration of color standards comprises following steps:
• Standard Family [} 79]
• Standard [} 81]
Measurement data
<point>
<time>$TIME§</time>
<SerialNo>None - PELT is OEM product.</SerialNo>
<CatalogNo>None - PELT is OEM product.</CatalogNo>
<Status>$STATUS§</Status>
<Checkzone>$CHECKZONE§</Checkzone>
<scale Id = "1 Elec. coat" - value ="$EC1 mic§"></scale>
<scale Id = "2 Prime coat" - value ="$PR1 mic§"></scale>
<scale Id = "3 Basis coat" - value ="$BC1 mic§"></scale>
<scale Id = "4 Clear coat" - value ="$CC1 mic§"></scale>
<!-- Sum calculated by smart-robotic ----- -->
<scale Id = "T Total coat" - value ="$total mic§"></scale>
</point>
Footer
</points>
</byklink_service_pelt>
With this step the configuration in smart-robotic is complete for PELT thickness
measurement.
NOTICE
Thickness measurement instruments of type PELT don’t have a “Serial Number” or
a “Catalog Number” – these parameters can be skipped in the output files.
8.1.3.2 Standard
For the creation of this documentation the standard “Silver – Moondust” was cre-
ated.
Example
Below following pass / fail tolerances were configured in this standard for the scale
“Dullness (du)”:
• Below 10 = Red: Measured value = Not in tolerance.
• 10 … 20 = Yellow: Measured value = In warning area.
• 20 … 30 = Green: Measured value = In tolerance.
• 30 … 40 = Yellow: Measured value = In warning area.
• Above 40 = Red: Measured value = Not in tolerance.
These values have been entered for Horizontal check points / zones only. The en-
tries Horizontal and Vertical are relevant later on for the check zones, see below.
NOTICE
All changes are stored via the Save button in the top level button row.
8.1.4 Organizers
The module Organizer is used to configure the check points / zones to be mea-
sured. The organizer management comprises following steps:
• Model [} 83]
• Standards [} 84]
• Paint line [} 85]
• Instruments [} 86]
• Check zones [} 87]
NOTICE
The combo box with selected entry “Model” appears only, if this entry has been
created in the Catalog [} 79] before.
8.1.4.5.1 Settings
On the tab Settings the parameters are available for selection which can be con-
figured in the handheld device. These parameters are not relevant for smart-ro-
botic.
NOTICE
The configuration in smart-chart is read by smart-robotic during program start.
After each change in standards and organizers the program smart-robotic has to
be restarted.
Model
Color
Paint Line
Vehicle ID
The example file shown above contains meta data including time stamp, car
model, color and check points / zones as well as measurement data of the wave-
scan ROBOTIC. In order to process this data with the corresponding organizer and
standard in smart-chart, the data must be mapped.
NOTICE
Below the example device wave-scan ROBOTIC is shown. The configuration for
the BYK-mac i ROBOTIC is analogue.
NOTICE
The Predefined Items are coming from the OPC [} 29] settings > section Com-
mon Job Signals [} 32]. These signals are common to all devices - they have to be
created once in the system.
NOTICE
The Predefined Items for the wave-scan are coming from the device 4822 -
wave-scan ROBOTIC [} 55] > section OPC Point Signals [} 58] - and from all
other devices(!). These signals have to be created separately for each device in the
system.
The signal mapping connects the OPC signals containing standard and organizer
information with the objects in the smart-chart database.
NOTICE
The names of the check zones in the PLC domain are case-sensitive.
Illustration 99: Smart-Robotic-Color-Standards
The mapping is analogue to the mapping of the Check Zones [} 96]. In the exam-
ple shown above the value “Silver” in smart-robotic is linked to the value “Silver -
Moondust” in smart-chart.
NOTICE
It is up to the PLC domain to evaluate these triggers and to communicate the
alarm situation.
NOTICE
1 Make sure the color standard has been added to the organizer, see Standard
Selection [} 84].
2 Create an additional output file with the quality status as part of the Output
Filename [} 70].
NOTICE
In the following examples the tolerance settings in smart-chart will be changed.
Remember to restart smart-robotic after each change in smart-chart in order to
read the changed values in the database.
<?xml version="1.0"?>
<wave-scan-robotic>
<jobdata>
<timestamp>2020-10-22T14:20:19</timestamp>
<jobquality>Green</jobquality>
<carmodel>Compact</carmodel>
<carcolor>Silver</carcolor>
<paintline>Paintline 1</paintline>
<comment>Created with simulator.</comment>
<vehicleid>123456</vehicleid>
</jobdata>
<points count="1">
<point>
<time>2020-10-22T14:20:23</time>
<serialnr>1213324</serialnr>
<catalognr>4822</catalognr>
<status>None</status>
<zoneid>1</zoneid>
<zone>Front</zone>
<scale Id="01 LW" value="0" />
<scale Id="02 SW" value="0" />
<scale Id="19 We" value="0" />
…
<scale Id="23 Wa" value="0" />
<scale Id="24 Du" value="38,8" />
</point>
</points count>
</wave-scan-robotic>
Check the measurement value for the scale “Dullness (du)”, here: “38,8”. In the
following examples this value will be used as base for the modification of the toler-
ance settings.
<?xml version="1.0"?>
<wave-scan-robotic>
<jobdata>
<timestamp>2020-10-22T14:07:09</timestamp>
<jobquality>Red</jobquality>
<carmodel>Compact</carmodel>
<carcolor>Silver</carcolor>
<paintline>Paintline 1</paintline>
<comment>Created with simulator.</comment>
<vehicleid>123456</vehicleid>
</jobdata>
<points count="1">
<point>
<time>2020-10-22T14:07:13</time>
<serialnr>1213324</serialnr>
<catalognr>4822</catalognr>
<status>Red</status>
<zoneid>1</zoneid>
<zone>Front</zone>
<scale Id="01 LW" value="0" />
<scale Id="02 SW" value="0" />
<scale Id="19 We" value="0" />
…
<scale Id="23 Wa" value="0" />
<scale Id="24 Du" value="38,8" />
</point>
</points count>
</wave-scan-robotic>
<?xml version="1.0"?>
<wave-scan-robotic>
<jobdata>
<timestamp>2020-10-22T14:04:25</timestamp>
<jobquality>Yellow</jobquality>
<carmodel>Compact</carmodel>
<carcolor>Silver</carcolor>
<paintline>Paintline 1</paintline>
<comment>Created with simulator.</comment>
<vehicleid>123456</vehicleid>
</jobdata>
<points count="1">
<point>
<time>2020-10-22T14:04:29</time>
<serialnr>1213324</serialnr>
<catalognr>4822</catalognr>
<status>Yellow</status>
<zoneid>1</zoneid>
<zone>Front</zone>
<scale Id="01 LW" value="0" />
<scale Id="02 SW" value="0" />
<scale Id="19 We" value="0" />
…
<scale Id="23 Wa" value="0" />
<scale Id="24 Du" value="38,8" />
</point>
</points count>
</wave-scan-robotic>
<?xml version="1.0"?>
<wave-scan-robotic>
<jobdata>
<timestamp>2020-10-22T14:11:37</timestamp>
<jobquality>Green</jobquality>
<carmodel>Compact</carmodel>
<carcolor>Silver</carcolor>
<paintline>Paintline 1</paintline>
<comment>Created with simulator.</comment>
<vehicleid>123456</vehicleid>
</jobdata>
<points count="1">
<point>
<time>2020-10-22T14:11:41</time>
<serialnr>1213324</serialnr>
<catalognr>4822</catalognr>
<status>Green</status>
<zoneid>1</zoneid>
<zone>Front</zone>
<scale Id="01 LW" value="0" />
<scale Id="02 SW" value="0" />
<scale Id="19 We" value="0" />
…
<scale Id="23 Wa" value="0" />
<scale Id="24 Du" value="38,8" />
</point>
</points count>
</wave-scan-robotic>
NOTICE
The XML files are required in a specific structure to be processed by smart-ro-
botic. Details see below.
8.4.1 Prerequisites
Understanding of following topics is required:
• Configuration of Output Files [} 67]
• Configuration in smart-chart [} 77]
• Configuration in smart-robotic [} 90]
These topics are about the BYK-Gardner ROBOTIC instruments. In the following
the differences are described.
<?xml version="1.0"?>
<byklink_service_thickness>
<jobdata>
<timestamp>2020-10-30T11:16:00</timestamp>
<Comment>This is a comment.</Comment>
<Paintline>X</Paintline>
<Model>Compact</Model>
<VID>Vehicle 12458</VID>
<Color>White</Color>
<Body_type>4DR</Body_type>
</jobdata>
<points count="2">
<point>
<deviceid>1210833</deviceid>
<timestamp>2020-10-30T11:16:00</timestamp>
<Checkzone>Front</Checkzone>
<PartNo>01</PartNo >
<PointNo>08</PointNo >
<Name>SAMPLE 01</Name>
<scale Id ="112 (mic/µm)" value ="302"></scale>
</point>
<point>
<deviceid>1210833</deviceid>
<timestamp>2020-10-30T11:16:00</timestamp>
<Checkzone>Top</Checkzone>
<PartNo>02</PartNo >
<PointNo>09</PointNo >
<Name>SAMPLE 02</Name>
<scale Id ="112 (mic/µm)" value ="259"></scale>
</point>
</points>
</byklink_service_thickness>
With this information smart-robotic can search for the corresponding standard in
the smart-chart standard database and save the measured values in the results
database – including pass / fail indication.
NOTICE
Refer also to Allow Missed [} 137] for more information on color standards.
NOTICE
Remember that valid parameters are highlighted in cyan color. Check this for all
parameters to be replaced with current values. The syntax check is performed
when opening the template for editing.
Header
<?xml version="1.0"?>
<byklink_service_thickness>
<jobdata>
<timestamp>$TIMESTAMP§</timestamp>
<jobquality>$QUALITY§</jobquality>
<carmodel>$MODEL§</carmodel>
<carcolor>$COLOR§</carcolor>
<paintline>$PAINTLINE§</paintline>
<comment>$COMMENT§</comment>
<vehicleid>$VEHICLE_ID§</vehicleid>
</jobdata>
<points count="$MEAS_COUNT§">
Measurement data
<point>
<time>$TIME§</time>
<SerialNo>$Serial No.§</SerialNo>
<CatalogNo>None - Fisher is OEM product.</CatalogNo>
<Status>$STATUS§</Status>
<Checkzone>$CHECKZONE§</Checkzone>
<scale Id = "102" value ="$mic§"></scale>
<scale Id = "103" value ="$mil§"></scale>
</point>
Footer
</points>
</byklink_service_thickness>
With this step the configuration in smart-robotic is complete for Fisher thickness
measurement.
NOTICE
Thickness measurement instruments of type Fisher can have a “Serial Number” -
but they don’t have a “Catalog Number”, which is specific to BYK-Gardner prod-
ucts.
<?xml version="1.0"?>
<byklink_service_thickness>
<jobdata>
<timestamp>2020-12-04T09:00:00</timestamp>
<jobquality>Green</jobquality>
<carmodel>Compact</carmodel>
<carcolor>White - Glacier</carcolor>
<paintline>PL 1</paintline>
<comment>This is a comment.</comment>
<vehicleid>Vehicle 123456</vehicleid>
</jobdata>
<points count="2">
<point>
<time>2020-12-04T09:00:00</time>
<SerialNo>1210833</SerialNo>
<CatalogNo>None - Fisher is OEM product.</CatalogNo>
<Status>Green</Status>
<Checkzone>Hood</Checkzone>
<scale Id = "102" value ="222"></scale>
<scale Id = "103" value ="UNDEFINED"></scale>
</point>
<point>
<time>2020-12-04T09:00:00</time>
<SerialNo>1210833</SerialNo>
<CatalogNo>None - Fisher is OEM product.</CatalogNo>
<Status>Green</Status>
<Checkzone>Roof</Checkzone>
<scale Id = "102" value ="265"></scale>
<scale Id = "103" value ="UNDEFINED"></scale>
</point>
</points>
</byklink_service_thickness>
NOTICE
Do not forget to clean-up the file system in regular intervals. This applies to both
input and output files.
NOTICE
The XML files are required in a specific structure to be processed by smart-ro-
botic. Details see below.
8.5.1 Prerequisites
Understanding of following topics is required:
• Configuration of Output Files [} 67]
• Configuration in smart-chart [} 77]
• Configuration in smart-robotic [} 90]
• Thickness Measurement [} 106] (Fisher)
In the following the differences to these topics are described.
Each layer can have a different tolerance, thus multiple tolerances are usually de-
fined in smart-chart, see Color Standard [} 123].
…
<Id>00000098020041</Id>
<StyleNumber>Compact</StyleNumber>
<Booth>B</Booth>
<BaseColor>Petrol</BaseColor>
<ClearColor>HE05</ClearColor>
<MeasurementUnits>Microns</MeasurementUnits>
…
NOTICE
The PELT input XML files used to create this documentation are large – they in-
clude multiple measurements. An example file has been added to the appendix –
see XML Input File PELT [} 158].
In the scale μm for each layer the tolerance value(s) for the pass / fail indication
have to be entered. This can be once done for all colors in the family or separately
for each color, see Color Standard [} 109].
In the example shown above for the complete standard family “BYK Solid Colors -
Multilayer” following tolerances have been set:
• < 50 = Red
• 50..90 = Yellow
• 90..100 = Green
• > 100 = Red
These tolerances will be used in the description below.
NOTICE
It is recommend to create separate color standard families for Fisher (single-layer)
and for PELT (multi-layer) thickness measurements and to add required scales only.
NOTICE
Remember that valid parameters are highlighted in cyan color. Check this for all
parameters to be replaced with current values. The syntax check is performed
when opening the template for editing.
Header
<?xml version="1.0"?>
<byklink_service_thickness_pelt>
<jobdata>
<timestamp>$TIMESTAMP§</timestamp>
<jobquality>$QUALITY§</jobquality>
<carmodel>$MODEL§</carmodel>
<carcolor>$COLOR§</carcolor>
<paintline>$PAINTLINE§</paintline>
<comment>Units: $COMMENT§ (Mics)</comment>
<vehicleid>$VEHICLE_ID§</vehicleid>
</jobdata>
<points count="$MEAS_COUNT§">
Measurement data
<point>
<time>$TIME§</time>
<SerialNo>None - PELT is OEM product.</SerialNo>
<CatalogNo>None - PELT is OEM product.</CatalogNo>
<Status>$STATUS§</Status>
<Checkzone>$CHECKZONE§</Checkzone>
<scale Id = "1 Elec. coat" - value ="$EC1 mic§"></scale>
<scale Id = "2 Prime coat" - value ="$PR1 mic§"></scale>
<scale Id = "3 Basis coat" - value ="$BC1 mic§"></scale>
<scale Id = "4 Clear coat" - value ="$CC1 mic§"></scale>
<!-- Sum calculated by smart-robotic ----- -->
<scale Id = "T Total coat" - value ="$total mic§"></scale>
</point>
Footer
</points>
</byklink_service_pelt>
With this step the configuration in smart-robotic is complete for PELT thickness
measurement.
NOTICE
Thickness measurement instruments of type PELT don’t have a “Serial Number” or
a “Catalog Number” – these parameters can be skipped in the output files.
<?xml version="1.0"?>
<byklink_service_thickness_pelt>
<jobdata>
<timestamp>2020-12-14T14:26:13</timestamp>
<jobquality>Middle</jobquality>
<carmodel>Compact</carmodel>
<carcolor>Petrol-Multi</carcolor>
<paintline>PL 2</paintline>
<comment>Units: Microns (Mics)</comment>
<vehicleid>00000098020041</vehicleid>
</jobdata>
<points count="1">
<point>
<time>2020-12-14T14:26:13</time>
<SerialNo>None - PELT is OEM product.</SerialNo>
<CatalogNo>None - PELT is OEM product.</CatalogNo>
<Status>Middle</Status>
<Checkzone>Hood</Checkzone>
<scale Id = "1 Elec. coat" - value ="24,94"></scale>
<scale Id = "2 Prime coat" - value ="22,66"></scale>
<scale Id = "3 Basis coat" - value ="27,18"></scale>
<scale Id = "4 Clear coat" - value ="24,46"></scale>
<!-- Sum calculated by smart-robotic ----- -->
<scale Id = "T Total coat" - value ="99,24"></scale>
</point>
</points>
</byklink_service_thickness_pelt>
NOTICE
Do not forget to clean-up the file system in regular intervals. This applies to both
input and output files.
<LayerNumber>4</LayerNumber>
<Thickness> 24.94</Thickness>
<LayerTooThin>0</LayerTooThin>
<Confidence> 44.0</Confidence>
<Indirect>0</Indirect>
The threshold for the Confidence Level can be entered on the tab Scales, see
also Multi-Layer Scales [} 128].
The resulting output file may look like the following example.
<?xml version="1.0"?>
<byklink_service_thickness_pelt>
<jobdata>
<timestamp>2020-12-15T14:26:13</timestamp>
<jobquality>Good</jobquality>
<carmodel>Compact</carmodel>
<carcolor>Petrol-Multi</carcolor>
<paintline>PL 2</paintline>
<comment>Units: Microns (Mics)</comment>
<vehicleid>00000098020041</vehicleid>
</jobdata>
<points count="1">
<point>
<time>2020-12-15T14:26:13</time>
<SerialNo>None - PELT is OEM product.</SerialNo>
<CatalogNo>None - PELT is OEM product.</CatalogNo>
<Status>None</Status>
<Checkzone>Hood</Checkzone>
<scale Id = "1 Elec. coat" - value ="UNDEFINED"></scale>
<scale Id = "2 Prime coat" - value ="22,66"></scale>
<scale Id = "3 Basis coat" - value ="UNDEFINED"></scale>
<scale Id = "4 Clear coat" - value ="24,46"></scale>
<!-- Sum calculated by smart-robotic ----- -->
<scale Id = "T Total coat" - value ="UNDEFINED"></scale>
</point>
</points>
</byklink_service_thickness_pelt>
Illustration 150: PELT-Allow-Missed
The two fields Allow Missed indicate how many tests for this scale may be out of
tolerance over the whole job before the status of the test series changes.
In the example shown above the threshold is 50 percent. This will result in the fol-
lowing output file.
<?xml version="1.0"?>
<byklink_service_thickness_pelt>
<jobdata>
<timestamp>2020-12-15T14:26:13</timestamp>
<jobquality>Good</jobquality>
<carmodel>Compact</carmodel>
<carcolor>Petrol-Multi</carcolor>
<paintline>PL 2</paintline>
<comment>Units: Microns (Mics)</comment>
<vehicleid>00000098020041</vehicleid>
</jobdata>
<points count="2">
<point>
<time>2020-12-15T14:26:13</time>
<SerialNo>None - PELT is OEM product.</SerialNo>
<CatalogNo>None - PELT is OEM product.</CatalogNo>
<Status>Middle</Status>
<Checkzone>Hood</Checkzone>
<scale Id = "1 Elec. coat" - value ="24,94"></scale>
<scale Id = "2 Prime coat" - value ="22,66"></scale>
<scale Id = "3 Basis coat" - value ="27,18"></scale>
<scale Id = "4 Clear coat" - value ="24,46"></scale>
<!-- Sum calculated by smart-robotic ----- -->
<scale Id = "T Total coat" - value ="99,24"></scale>
</point>
<point>
<time>2020-12-15T14:27:13</time>
<SerialNo>None - PELT is OEM product.</SerialNo>
<CatalogNo>None - PELT is OEM product.</CatalogNo>
<Status>Good</Status>
<Checkzone>Roof</Checkzone>
<scale Id = "1 Elec. coat" - value ="21,01"></scale>
<scale Id = "2 Prime coat" - value ="29,79"></scale>
<scale Id = "3 Basis coat" - value ="10,53"></scale>
<scale Id = "4 Clear coat" - value ="22,86"></scale>
<!-- Sum calculated by smart-robotic ----- -->
<scale Id = "T Total coat" - value ="84,19"></scale>
</point>
</points>
</byklink_service_thickness_pelt>
The overall status is “Good”, although one of the two measurements was only
“Middle”.
9 Robot Simulator
The simulation allows testing of software configuration and physical instruments
without the need of a robot.
Instead of sending the OPC signals to the PLC the signals are sent to the simula-
tion. The simulation fills in all data.
The results of each operation can be checked directly in the smart-robotic appli-
cation.
Perform following steps:
1. Prepare Simulation [} 139]
2. Activate Simulation [} 140]
3. Configure Instrument [} 141]
4. Control Simulation [} 142]
5. Monitor Simulation [} 143]
6. Check Results [} 144]
These steps are described below. For the examples given below the device wave-
scan ROBOTIC is used. The usage of the simulation with the BYK-mac i RO-
BOTIC or wave-scan 3 ROBOTIC is analogue.
NOTICE
The button will be displayed again after restarting smart-robotic.
NOTICE
To change an existing configuration which is already in status Enabled first click
the button Disable.
6. Job Data Values: In the productive system these data are transferred from the
PLC. Here in the simulation all entries have to be created using the Add but-
ton. Remove an entry using the X symbol to the right of the entry.
– Car-Model: Create for example “Limousine”, “Convertible”, “Station
Wagon” and “SUV”.
– Car-Color: Create for example “Black”, “Pearl”, “Red” and “White”.
– Paint-Line: Create for example “PL1”, “PL2”, and “PL3”.
– Free-Comment: Create for example “Created with Simulator”.
– Vehicle-ID: Create for example “123456” and “654321”.
7. Log: Here all events for the simulation are displayed.
When configuration is finished click the button Start to proceed.
NOTICE
1 To calculate the number of measurements: If the quantity for the Device is for
example “4” and for the Control it is for example “5” the robot simulation will
make “20” measurements.
2 If Job Quantity is “1” it will use the 1st data value for the 1st run, the 2nd data
value for the 2nd run (etc.) If the quantity is higher it will use one data value after
the other within one run.
<?xml version="1.0"?>
<wave-scan-robotic>
<jobdata>
<timestamp>2020-10-06T17:38:33</timestamp>
<jobquality>Green</jobquality>
<carmodel>Combi</carmodel>
<carcolor>Pearl</carcolor>
<paintline>PL1</paintline>
<comment>Created with simulator.</comment>
<vehicleid>123456</vehicleid>
</jobdata>
<points count="1">
<point>
<time>2020-10-06T17:38:38</time>
<serialnr>1213324</serialnr>
<catalognr>4822</catalognr>
<status>None</status>
<zoneid>4</zoneid>
<zone>rear bumper</zone>
<scale Id="01 LW" value="0" />
<scale Id="02 SW" value="0" />
<scale Id="19 We" value="0" />
<scale Id="20 Wd" value="0" />
<scale Id="21 Wc" value="0" />
<scale Id="22 Wb" value="0" />
<scale Id="23 Wa" value="0" />
<scale Id="24 Du" value="12,1" />
</point>
</points count>
</wave-scan-robotic>
Now you can modify the various settings in the tabs for the Devices and in the
Control tab and restart the simulation as often as you need to check the results.
10 Run Procedure
With BYK-mac i ROBOTIC the measurements can be accomplished in three differ-
ent operation modes. In addition the appropriate bit for the operation mode must
be set by the PLC. The wave-scan ROBOTIC has only one measurement mode. Fol-
lowing operation modes are to be programed on the PLC side:
1. Measurement Mode - BYK-mac [} 145]
2. Calibration Mode - BYK-mac [} 150]
3. Masterpanel Mode - BYK-mac [} 150]
4. Measurement Mode - wave scan [} 152]
10.1.1 General
The operation mode “Normal Measurement” is reached by not setting one of the
signals IN_REQU_MAST, IN_REQU_CAL, IN_REQU_MODE4-9.
A new measuring group is started by the handshake IN_JOB_START. A normal
measurement can be divided into four partial sequences:
1. Start job
2. Fine position correction
3. Points end
4. Terminate job
Since a job can contain more than one point, the procedure jumps from partial se-
quence 3 to 2 at the next measuring point. Only with receipt of the signal
IN_JOB_STOP smart-robotic is instructed to regard the job as terminated and
passes all data out.
NOTICE
The signal IN_JOB_STOP always causes a complete end of measurement. Up to
then measured data are passed out as result data. In the operating mode “Normal
Measurement“ this signal can be used as reset.
If the fine positioning (point 3) was not successful it is repeated several times. If it
should not be successful nevertheless, the point is not measured. For the robot,
handshake ends however normal (point 4) with the signal OUT_POINT_READY.
The signal OUT_POINT_RESULT indicates the result of the measurement at the time
OUT_POINT_READY:
• 0 = NOK
• 1 = OK
After a point is reached (IN_POINT_POS), BYK-mac i ROBOTIC evaluates the 4 posi-
tioning pins. If the equipment is too near at the surface or too far, errors x99200
or x99201 are announced in connection with OUT_POINT_READY/ and
OUT_POINT_RESULT=0.
If a calculation of the correction values is possible, the necessary correction values
are handed over via OUT_CORR-Z/K/Q to the PLC and are indicated with
OUT_CORR_VAL.
The robot must thereupon correct the position and indicate it in IN_POINT_POS
again.
If the position according to the handed over curvature is in the permitted toler-
ances, a measurement is deployed, subsequently OUT_POINT_READY and
OUT_POINT_RESULT is set.
10.1.2 Sequence
No. Description PLC smart-robotic
10 If defined, job data must be available. Job data..↑..
11 New job is started. IN_JOB_START..↑.. Internal start of a new job,
takeover of the job data on the
agenda.
12 ..↑..OUT_JOB_RUN Feedback to PLC that job runs.
..↑..OUT_JOB_SUCCESS Retraction of the job success sig-
nal.
13 Retraction of the job start signal. IN_JOB_START..↓..
14 Job data do not need to be valid any Job data..↓..
longer.
20 Robot hit point. If defined, point data Point data..↑.. New point hit or correction exe-
must be on the agenda. IN_CURVATURE..↑.. cuted.
A curvature must be reported.
21 Robot reports that a matching position is IN_POINT_POS..↑..
hit.
BYK-mac calculates correction values
BYK-mac reports back a correction value
(continue at 22).
BYK-mac reports that measurement was OUT_POINT_RESULT=1
successful (continue at 32).
BYK-mac reports error, abort (continue at OUT_POINT_RESULT=0
32).
10.1.3 Diagram
Illustration 156: BYK-mac-Time-Diagram-PLC
Illustration 157: BYK-mac-Time-Diagram-SR
10.1.4 Workflow
Illustration 158: BYK-mac-Flow-Diagram-Part1
Illustration 159: BYK-mac-Flow-Diagram-Part2
Start tile:
10 Robot is at the first calibration tile IN_POINT_POS..↑..
Start measurement
Tile O.K.:
11 Report at robot that point is finished. ..↑..OUT_POINT_READY
12 Robot reports that point is left. ..↓..IN_POINT_POS
13 Retraction of the handshake. ..↓..OUT_POINT_READY
If further tile is measured, continue at 10.
End Job:
40 Robot reports that the job is finished. IN_JOB_STOP..↑..
41 FL finishes the job and generates measur- ..↓..OUT_JOB_RUN
ing file.
42 Retraction of the handshake. ..↓..IN_JOB_STOP
If control measurements are avail-
able, output file is generated.
The sequence given below is nearly the same as in shown in Measurement Mode
- BYK-mac [} 145]. Except the positions 1 and 14 differ from the normal measure-
ment mode.
20 Robot hit point. If defined, point data Point data..↑.. New point hit or correction exe-
must be on the agenda. IN_CURVATURE..↑.. cuted.
A curvature must be reported.
21 Robot reports that a matching position is IN_POINT_POS..↑..
hit.
BYK-mac calculates correction values
BYK-mac reports back a correction value
(continue at 22).
BYK-mac reports that measurement was OUT_POINT_RESULT=1
successful (continue at 32).
BYK-mac reports error, abort (continue at OUT_POINT_RESULT=0
32).
10.4.1 Sequence
No. Description PLC smart-robotic
10 If defined, job data must be available. Job data..↑..
11 New job is started. IN_JOB_START..↑.. Internal start of a new job,
takeover of the job data on the
agenda.
12 ..↑..OUT_JOB_RUN Feedback to PLC that job runs.
..↑..OUT_JOB_SUCCESS Retraction of the job success sig-
nal.
13 Retraction of the job start signal. IN_JOB_START..↓..
14 Job data do not need to be valid any Job data..↓..
longer.
20 Robot hit point. If defined, point data Point data..↑.. New point hit or correction exe-
must be on the agenda. cuted.
21 Robot reports that a matching position is IN_POINT_POS..↑..
hit.
The wave-scan reports that measurement OUT_POINT_RESULT=1
was successful (continue at 32).
The wave-scan reports error, abort (con- OUT_POINT_RESULT=0
tinue at 32).
10.4.2 Diagram
Illustration 160: Wave-Scan-Time-Diagram-PLC
Illustration 161: Wave-Scan-Time-Diagram-SR
10.4.3 Workflow
Illustration 162: Wave-Scan-Flow-Diagram
11 Appendix
11.1 Abbreviations
The following abbreviations are used in this documentation.
BMi BYK-Gardner BYK-mac i (handheld instrument)
BMi-R BYK-Gardner BYK-mac i ROBOTIC
CSV Comma Separated Values
DB Database
FTDI Future Technology Devices International
IP Internet Protocol
LAN Local Area Network
PLC Programmable Logic Controller
OEM Original Equipment Manufacturer
OPC Open Platform Communications
SC BYK-Gardner smart-chart
SR BYK-Gardner smart-robotic
USB Universal Serial Bus
WS BYK-Gardner wave-scan (handheld instrument)
WS-R BYK-Gardner wave-scan ROBOTIC
WS3 BYK-Gardner wave-scan 3 (handheld instrument)
WS3-R BYK-Gardner wave-scan 3 ROBOTIC
XML Extensible Markup Language
11.3 Troubleshooting
Module Problem Solution
Main Configuration is yet not possible or can Restart smart-robotic.
program not be reached.
Main There is a problem with smart-robotic. Check log file in “C:\ProgramData\BYK\smart-ro-
program botic\Logs\ SmartRobotic.log”.
Main Adding data is not possible on a configu- Add the data input value first. Click the Add button
program ration. second.
Main There are too many XML files in the pro- Backup all files, for example in a ZIP archive.
program gram data directory.
Main There are too many log files in the log di- Backup all files, for example in a ZIP archive.
program rectory.
OPC OPC control signal in status “Not con- Check / correct configuration on OPC server. Restart
config nected”. OPC server.
OPC OPC point signal in status “Not con- 1 Check / correct configuration on OPC server.
config nected”. Restart OPC server.
2 Check / correct configuration in smart-robotic.
Restart smart-robotic.
Device COM port can not be assigned, it is occu- 1 Assign a free COM port.
connect pied by other device. 2 If not possible, delete the other device.
Device Device initialization failed with “Error at 1 Click the button De-Initialize first.
test Initialize”. 2 Reconnect USB cable and repeat with new con-
nection.
3 Reconnect power cable and repeat after new in-
strument start.
Output Output files have no or unknown file ex- Append the correct extension in the file name defi-
files tension. nition designer.
Output Output file is not written after measure- Activate the device used during measurement for
files ment. this type of storage.
smart-chart link Simulation hangs during a measurement. 1 Close smart-robotic.
2 Restart OPC server.
3 Restart smart-robotic.
4 Reactivate device and simulator.
5 Restart measurement.
smart-chart link Expected quality status is not achieved A Save last modification in smart-chart and restart
during measurement. smart-robotic.
B Check if matching car model AND color standard
is used in smart-robotic.
Robot Robot simulator can not be started. Enable a measurement device first.
simulator
Robot There is a problem with the robot simula- Check log file in “C:\ProgramData\BYK\ smart-ro-
simulator tor. botic\Logs\ RobotSimulator.log”.
Robot There are too many log files in the log di- Backup all files, for example in a ZIP archive.
simulator rectory.
11.4.2.1 Measurement 1
<Measurement>
<PanelName>R01 X01 0:1</PanelName>
<PanelNumber>0</PanelNumber>
<PanelLocation>1</PanelLocation>
<Location>1</Location>
<Robot>1</Robot>
<Sensor>1</Sensor>
<Placement>1</Placement>
<GroupCode>T</GroupCode>
<KD_KOORD_X>0</KD_KOORD_X>
<KD_KOORD_Y>0</KD_KOORD_Y>
<KD_KOORD_Z>0</KD_KOORD_Z>
<LayerCount>4</LayerCount>
<Temperature> 18.0</Temperature>
<Timestamp>2020-12-14T14:26:13</Timestamp>
<Layers>
11.4.2.1.1 Layer 1
<Layer>
<LayerNumber>1</LayerNumber>
<Thickness> 34.46</Thickness>
<LayerTooThin>0</LayerTooThin>
<Confidence> 59.0</Confidence>
<Indirect>0</Indirect>
<TemperatureScaleValue>1.0000</TemperatureScaleValue>
<TOF>33.50</TOF>
<LayerName>Clear_T</LayerName>
<LayerCode>CC</LayerCode>
<LayerVendor>VW</LayerVendor>
</Layer>
11.4.2.1.2 Layer 2
<Layer>
<LayerNumber>2</LayerNumber>
<Thickness> 17.18</Thickness>
<LayerTooThin>0</LayerTooThin>
<Confidence> 59.0</Confidence>
<Indirect>0</Indirect>
<TemperatureScaleValue>1.0000</TemperatureScaleValue>
<TOF>16.50</TOF>
<LayerName>TP Color_T</LayerName>
<LayerCode>BC</LayerCode>
<LayerVendor>VW</LayerVendor>
</Layer>
11.4.2.1.3 Layer 3
<Layer>
<LayerNumber>3</LayerNumber>
<Thickness> 22.66</Thickness>
<LayerTooThin>0</LayerTooThin>
<Confidence> 83.0</Confidence>
<Indirect>0</Indirect>
<TemperatureScaleValue>1.0000</TemperatureScaleValue>
<TOF>21.50</TOF>
<LayerName>Prime_T</LayerName>
<LayerCode>PR</LayerCode>
<LayerVendor>VW</LayerVendor>
</Layer>
11.4.2.1.4 Layer 4
<Layer>
<LayerNumber>4</LayerNumber>
<Thickness> 14.94</Thickness>
<LayerTooThin>0</LayerTooThin>
<Confidence> 84.0</Confidence>
<Indirect>0</Indirect>
<TemperatureScaleValue>1.0000</TemperatureScaleValue>
<TOF>14.00</TOF>
<LayerName>E-Coat_T</LayerName>
<LayerCode>EC</LayerCode>
<LayerVendor>VW</LayerVendor>
</Layer>
11.4.2.2 Measurement 2
<Measurement>
<PanelName>R01 X01 1:21</PanelName>
<PanelNumber>1</PanelNumber>
<PanelLocation>21</PanelLocation>
<Location>2</Location>
<Robot>1</Robot>
<Sensor>1</Sensor>
<Placement>2</Placement>
<GroupCode>S</GroupCode>
<KD_KOORD_X>0</KD_KOORD_X>
<KD_KOORD_Y>0</KD_KOORD_Y>
<KD_KOORD_Z>0</KD_KOORD_Z>
<LayerCount>4</LayerCount>
<Temperature> 19.0</Temperature>
<Timestamp>2020-12-14T14:27:13</Timestamp>
<Layers>
11.4.2.2.1 Layer 1
<Layer>
<LayerNumber>1</LayerNumber>
<Thickness> 42.86</Thickness>
<LayerTooThin>0</LayerTooThin>
<Confidence> 48.0</Confidence>
<Indirect>0</Indirect>
<TemperatureScaleValue>1.0000</TemperatureScaleValue>
<TOF>41.50</TOF>
<LayerName>2K Clearcoat</LayerName>
<LayerCode>ALD 096050/ALZ</LayerCode>
<LayerVendor>Axalta</LayerVendor>
</Layer>
11.4.2.2.2 Layer 2
<Layer>
<LayerNumber>2</LayerNumber>
<Thickness> 10.53</Thickness>
<LayerTooThin>0</LayerTooThin>
<Confidence> 48.0</Confidence>
<Indirect>0</Indirect>
<TemperatureScaleValue>1.0000</TemperatureScaleValue>
<TOF> 9.00</TOF>
<LayerName>Deepblack Per_5</LayerName>
<LayerCode>2T2T</LayerCode>
<LayerVendor>Axalta</LayerVendor>
</Layer>
11.4.2.2.3 Layer 3
<Layer>
<LayerNumber>3</LayerNumber>
<Thickness> 29.79</Thickness>
<LayerTooThin>0</LayerTooThin>
<Confidence> 95.0</Confidence>
<Indirect>0</Indirect>
<TemperatureScaleValue>1.0000</TemperatureScaleValue>
<TOF>20.50</TOF>
<LayerName>Anthrazit Prime</LayerName>
<LayerCode>ALG 670008</LayerCode>
<LayerVendor>Hemmelra</LayerVendor>
</Layer>
11.4.2.2.4 Layer 4
<Layer>
<LayerNumber>4</LayerNumber>
<Thickness> 21.01</Thickness>
<LayerTooThin>0</LayerTooThin>
<Confidence> 95.0</Confidence>
<Indirect>0</Indirect>
<TemperatureScaleValue>1.0000</TemperatureScaleValue>
<TOF>15.00</TOF>
<LayerName>CathoGuard 800</LayerName>
<LayerCode>ALE 074507</LayerCode>
<LayerVendor>BASF</LayerVendor>
</Layer>
NOTICE
The value for the “Multi-Layer Total Thickness” is not present in the file. It is calcu-
lated by smart-robotic from the values of the different layers belonging to the
same check zone.