EMDEP KSK SYSTEM

KSK CLIENT
Emdep KSK Client / User’s guide

Document history and versions

Ver. Date Author Change description
1.0 11/10/2017 Gerard Llort Initial version.
1.1 04/06/2018 Gerard Llort Added Cluster stations section.
1.2 21/06/2018 Gerard Llort Added Creating Wintestem™ processes in KSK stations section.
1.3 30/07/2018 Gerard Llort Added Validating a station in KSK project section.
Added Activating memory usage logs section.
1.4 06/08/2018 Gabriel Plana Added Validation station section.
Gerard Llort
1.5 24/08/2018 Gerard Llort Added Creating a dispatch station section.
1.6 05/09/2018 Gerard Llort Added Shared interfaces section.
Added User’s guide section for validation stations.
Added User’s guide section for rework stations.
1.7 11/10/2018 Gerard Llort Added Creating and configuring labels section.
1.8 11/10/2018 Gerard Llort Added Development Information section
3.1 05(02(2019 Gabriel Plana Added new configuration options for Dispatch and Validation
3.3 24/04/2019 Gabriel Plana Changed screens on Validation station section and Dispatch section,
after made 2019-PR4015: New features for PPAP
3.4 27/5/2019 Gabriel Plana Changed screen in Dispatch terminal settings. Now Auto Generate
Module Validation Report can be configured to generate a PDF
(2019-PR4075)
3.6 10/9/2019 Gabriel Plana Added a comment on “Module validation with PPAP stations”
subsection to explain conditional Validation(2019-PR4270)
3.8 24/10/2019 Gabriel Plana Added Spare Modules Validation Station (2019-PR4239)
Correcting some mistakes in PPAP section
3.10 29/11/2019 Gabriel Plana Added E-Level explanation (2019-PR4361)
3.13 10/03/2020 Gabriel Plana Added a paragraph in installation instructions explaining that visual
basic scripts (.vbs files) are not updated when upgrading the
version.
3.14 23/6/2020 Gabriel Plana Added Rework Clips Checker
3.15 16/10/2020 Gabriel Plana Added Light clients section (Raspberry clients)
3.16 01/12/2020 Gabriel Plana Changed updating instructions for KskWebService client.
3.17 01/12/2020 Gabriel Plana Adding installation instructions for Marriage Station.
3.18 29/12/2020 Gabriel Plana Adding RFID settings on Dispatch station
3.19 19/01/2021 Gabriel Plana Adding NOTE about RFID simulator mode.
3.20 05/02/2021 Gabriel Plana Adding micronorma raspberry client
3.21 16/03/2021 Gabriel Plana Adding section using rework terminal from Wintestem
3.22 17/03/2021 Gabriel Plana Adding how to update raspberry applications.
Improved explanation in section using rework terminal from
Wintestem
3.23 23/04/2021 Gabriel Plana Modify creating dispatch station section to add combined dispatch
tab.
Added combined dispatch station section.
3.24 26/04/2021 Gabriel Plana Modify combined dispatch station section to explain how to
reconfigure secondary dispatch station.
3.25 27/04/2021 Gabriel Plana Modify combined dispatch station section. Change order: first
explain that relationship between stations can be configured on KSK
Studio.
3.26 03/05/2021 Gabriel Plana Modify Introduction: add micronorma as station type. Separate
marriage.
Modify Installation and configuration of Marriage Client
Modify Creating a Dispatch station: adding link to combined
dispatch

© EMDEP 2024 Page 0

Emdep KSK Client / User’s guide

Adding section Thin Clients

3.27 16/06/2021 Gabriel Plana Adding new points and screenshots for MicroNorma application
3.28 18/06/2021 Gabriel Plana Adding troubleshooting section after updating raspberry apps
3.29 21/07/2021 Gabriel Plana Revised the documentation. Fixed some grammatical errors.
3.30 22/11/2021 Gabriel Plana Adding new Thin client application Assembly Guiding
3.31 14/12/2021 Gabriel Plana Adding new section Re-scanning connector barcodes
3.32 23/12/2021 Gabriel Plana Modifying section Re-scanning connector barcodes to explain the
yellow status
Changes in Warehouse To Rework to explain getting feedback from
SAP
3.33 18/01/2022 Gabriel Plana Modifying Visual Inspection station flow: now it shows missing
subassemblies.
Adding new section show missing subassemblies screen.
Adding new section partial matching station.
Adding new section final matching station.
Adding new section Installation and Configuration of Assembly
Guiding
Adding new section Installation and Configuration of Subassembly
Matching
3.34 18/02/2022 Gabriel Plana Adding feature share rework between several lines (but not all)
3.35 12/04/2022 Gabriel Plana Adding new application Moby-D Repacking
Adding explanation for Dispatch when order is 18 characters in
length
3.36 22/04/2022 Gabriel Plana Added extra parameters on Dispatch Terminal Settings screen:
- Added parameter Minimum Order Length to write
DMC_Code on RFID tab
- Added new tab “Behavior options”
3.37 28/04/2022 Gabriel Plana Allow to print ECB labels on dispatch station
3.40 10/06/2022 Gabriel Plana Changed section Installation and Configuration of Subassembly
Matching client: Explain SA Matching stations cannot have
substations (Subassembly Workstations)

3.41 17/06/2022 Gabriel Plana Changed section Settings screen of assembly Guiding
Application. Explaining how to configure the printer.

3.42 21/07/2022 Lalit Bhangale Allow to print Additional variables of harness in Electric test label at
KSK Dispatch client.

3.43 11/10/2022 Gerard Pasano Created a functionality to allow to move a harness to previous
station.
Added “SendHarnessToPreviousStation” on Methods.

Added new tags for Dispatch labels.

3.44 6/02/2023 Suvarna Mohite Adding new Thin Application SA Matching Client.

09/05/2023 Gerard Pasano Added the definition of concerns, alerts and other alerts in
Variables in Electrical test labels.

4.0 18/05/2023 Lalit Bhangale Add the VBS in KSK Client to get the assign line of the Order.

Gerard Pasano Rework Terminal - Not passed SA should be mandatory asked

© EMDEP 2024 Page 1

Emdep KSK Client / User’s guide

4.1 7/06/2023 Suvarna Mohite SA Matching Client: add functionality to allow multiple Final
Matching station in one line.

4.2 22/06/2023 Gerard Pasano Create manual for Rotary Line Led Navigation

4.3 30/06/2023 Lalit Bhangale - Change the Foaming Client flow same as Visual Control
like avoid the Serial port communication

- Add New option “Harness can be sent to Rework” in

Micronorma Leak setting file

- Add New Station Type as “Micronorma_SA”

4.4 04/08/2023 Gerard Pasano Add KSK_Rework_SendWithSpecificDefect.vbs on Generated process

files.

4.5 18/07/2023 Gerard Pasano Add on KskWebserviceClient the new option “Print label” in
Micronorma Leak setting file.
Modifications on the document:
• Configuration of KskWebServiceClient
• Printing label screen
• Settings Screen

4.6 21/07/2023 Lalit Bhangale Add New Form for Rework harness Report
In Setting file Add two new field :
• Allow rework comments
• Quality password to send to scrap

4.7 28/08/2023 Gerard Pasano The configuration window of the station has been modified. Instead of
explicitly defining the characters that refer to the "Harnes" code suffix,
now there is the option to define the number of characters that need
to be removed from the end of the code.

Changes on the manual:

• Configuration of KskWebServiceClient

4.8 14/09/2023 Lalit Bhangale Created functionality for Order Simulation with open and close
stage.

Added “OpenStage with Simulation” on Methods.

Added “CloseStage with Simulation” on Methods.

4.9 02/10/2023 Lalit Bhangale Add new Deserialization Client Application

5.0 23/10/2023 Arnau Added SaveHarnessDMC and CheckHarnessDmcExists in the KSK

Montañés Client Interface section.

5.1 12/12/2023 Gerard Pasano Added Rework In – Out.

Added Rework Dashboard application.

5.2 14/12/2023 Lalit Bhangale Added QA FireWall Client.

© EMDEP 2024 Page 2

Emdep KSK Client / User’s guide

5.3 11/01/2024 Gerard Pasano Updated Deserialization Client.

5.4 14/06/2024 Lalit Bhangale Added remove last n characters field in KSK SA Matching
client.

5.5 18/06/2024 Daniel Alexe Added Wire Pick-up for Eyelets

5.6 29/07/2024 Arnau Added Installation and Configuration of Eyelet Squeezing Client.
Montañés Added Eyelet Squeezing Client.

5.8 06/11/2024 Gerard Pasano Added on SharedInterfaces > KSK Client interface > Methods
Description of new function “GetHarnessHasBeenInReworks”

Disclaimer
The instructions in this document have been carefully checked for accuracy and are presumed
to be reliable. EMDEP and its writers assume no responsibility for inaccuracies and reserve the
right to modify and revise this document without notice.

If you discover a discrepancy in this document, please e-mail your comments to our Engineering
Support department ([email protected]).

© EMDEP 2024 Page 3

Emdep KSK Client / User’s guide

Contents
Introduction........................................................................................................................................... 2
Installing KSK Client ............................................................................................................................... 3
Client requirements ................................................................................................................................. 3
Station installation ................................................................................................................................... 3
Installing KskWebServiceClient .............................................................................................................. 6
Client Requirements ................................................................................................................................ 6
Hardware ............................................................................................................................................. 6
Software .............................................................................................................................................. 6
Station installation ................................................................................................................................... 6
Configuration of KskWebServiceClient .................................................................................................... 6
Installation and Configuration of Marriage client .................................................................................. 8
Installation and Configuration of Assembly Guiding application ............................................................ 9
Installation and Configuration of Subassembly Matching client ........................................................... 10
Installation and Configuration of Eyelet Squeezing Client .................................................................... 13
Updating process for raspberry applications ........................................................................................ 15
Troubleshooting .................................................................................................................................. 16
Error when starting raspberry application ............................................................................................. 16
Problem ............................................................................................................................................. 16
Solution .............................................................................................................................................. 16
Assembly/Test stations ........................................................................................................................ 18
Standard stations................................................................................................................................. 19
Creating a standard station .................................................................................................................... 19
Testing the station with Wintestem™ .................................................................................................... 21
Generated process files ......................................................................................................................... 22
Integrated stations .............................................................................................................................. 23
Creating an integrated station ............................................................................................................... 23
Testing the station with Wintestem™ .................................................................................................... 25
Generated process files ......................................................................................................................... 28
Cluster stations .................................................................................................................................... 28
MSSC Cluster Controller (server) ........................................................................................................... 29
Defining a cluster in MSSC server .......................................................................................................... 30
Defining the master station ................................................................................................................... 30
Defining the slave stations ..................................................................................................................... 31
Station settings .................................................................................................................................... 33
Assembly/test operations ...................................................................................................................... 33
Export Wintestem board data to KSK project ........................................................................................ 34
Order scanning options .......................................................................................................................... 35
Keyboard shortcuts ................................................................................................................................ 37
Rework options ...................................................................................................................................... 38
Backup .................................................................................................................................................... 38
Sending station board data to KSK project ........................................................................................... 39
Upload board data with Emdep KSK Board Exporter ............................................................................. 39
Error and warning messages .................................................................................................................. 41
Creating Wintestem™ processes in KSK stations .................................................................................. 41
Example 1: Perform an electrical test .................................................................................................... 41

© EMDEP 2024 Page 4

Emdep KSK Client / User’s guide

Example 2: Perform a double vision test ............................................................................................... 43

Re-scanning connector barcodes ......................................................................................................... 46
Dispatch station flow ........................................................................................................................... 50
Module validation .................................................................................................................................. 50
Module validation with PPAP stations ............................................................................................... 51
Module validation without PPAP ....................................................................................................... 51
Print Electrical label ............................................................................................................................... 51
Creating a dispatch station .................................................................................................................. 51
Variables in Electrical test labels ....................................................................................................... 56
Combined Dispatch Station .................................................................................................................. 63
Configuring Combined Dispatch Stations............................................................................................... 64
Configuring Behavior options................................................................................................................. 67
Flow of Primary Combined Dispatch Station ......................................................................................... 68
Flow of Moby-D device ........................................................................................................................ 71
Creating a Moby-D Repacking station .................................................................................................. 71
Configuration of Moby-D Repacking station ........................................................................................ 72
Operators guide ................................................................................................................................... 74
Creating a validation station ................................................................................................................ 81
Configure the Dispatch stations to send orders to validation ............................................................... 84
User’s guide ......................................................................................................................................... 85
Creating a spare module validation station ......................................................................................... 90
User’s guide ......................................................................................................................................... 93
Rework Stations................................................................................................................................... 97
Creating a rework station .................................................................................................................... 98
User’s guide ....................................................................................................................................... 101
Using Rework Terminal from Wintestem ........................................................................................... 105
What is a thin client? ......................................................................................................................... 111
Micronorma Leak ............................................................................................................................... 112
Micronorma Leak Flow ........................................................................................................................ 112
Login screen ......................................................................................................................................... 113
Scanning Order screen ......................................................................................................................... 114
Waiting for Micronorma reply screen .................................................................................................. 115
Printing label screen............................................................................................................................. 116
Sending to rework screen .................................................................................................................... 119
Settings Screen ..................................................................................................................................... 120
Visual Inspection................................................................................................................................ 122
Show missing subassemblies screen .................................................................................................... 123
Foaming ............................................................................................................................................. 124
Settings screen ..................................................................................................................................... 124
Login screen ......................................................................................................................................... 125
Scan Barcode Screen ............................................................................................................................ 126
Warehouse to rework ........................................................................................................................ 129
Marriage stations............................................................................................................................... 130
Assembly Guiding Application ........................................................................................................... 131
General flow ......................................................................................................................................... 131
Settings screen ..................................................................................................................................... 132

© EMDEP 2024 Page 5

Emdep KSK Client / User’s guide

Login screen ......................................................................................................................................... 134

Waiting screen ..................................................................................................................................... 135
Instructions screen ............................................................................................................................... 136
Connector Pictures in detail ................................................................................................................. 142
SA Matching Client Application .......................................................................................................... 143
General flow ......................................................................................................................................... 143
Settings screen ..................................................................................................................................... 144
Scan Barcode Screen ............................................................................................................................ 145
Scan User Code Screen......................................................................................................................... 146
Scan subassembly code screen ............................................................................................................ 147
Partial Matching station .................................................................................................................... 150
Configuration screen ............................................................................................................................ 150
Main screen.......................................................................................................................................... 152
Final Matching station.......................................................................................................................... 154
Missing subassemblies screen ............................................................................................................. 155
FM Matching Client............................................................................................................................ 156
Settings screen ..................................................................................................................................... 157
Login screen ......................................................................................................................................... 158
Scan Harness Screen ............................................................................................................................ 159
Conveyor Table Screen......................................................................................................................... 160
Functional Module Scan Screen ........................................................................................................... 161
Result Screen........................................................................................................................................ 162
Rotary Line Led Navigation ................................................................................................................ 163
Settings screen Raspberry Pi ................................................................................................................ 163
Scanning device configuration ......................................................................................................... 163
Panel device configuration .............................................................................................................. 165
How to use ........................................................................................................................................... 166
Possible problems ................................................................................................................................ 167
Wire Pick-up for Eyelets ..................................................................................................................... 169
Settings screen ..................................................................................................................................... 169
General Settings............................................................................................................................... 169
Add Wire Pipe .................................................................................................................................. 170
Edit Wire Pipe .................................................................................................................................. 171
Delete Wire Pipe .............................................................................................................................. 171
Test Selected Wire Pipes ................................................................................................................. 171
Test All Wire Pipes ........................................................................................................................... 171
Clear All Wire Pipes .......................................................................................................................... 172
Working Mode ................................................................................................................................. 172
Information On Screen .................................................................................................................... 172
GPIO Button ..................................................................................................................................... 172
Prefix ................................................................................................................................................ 172
Suffix ................................................................................................................................................ 172
Log Level .......................................................................................................................................... 173
Standard Operation Screen .................................................................................................................. 173
Scan Order Barcode ......................................................................................................................... 173
Order Screen .................................................................................................................................... 174

© EMDEP 2024 Page 6

Emdep KSK Client / User’s guide

Scan User Barcode ........................................................................................................................... 174

Power failure recovery system............................................................................................................. 175
Error codes ........................................................................................................................................... 175
Rework Dashboard ............................................................................................................................ 176
Settings screen ..................................................................................................................................... 176
How to use ........................................................................................................................................... 177
Deserialization Client ......................................................................................................................... 179
Setting Screen ...................................................................................................................................... 180
Scan Harness Screen ............................................................................................................................ 182
Print label Screen ................................................................................................................................. 183
Validation label Screen......................................................................................................................... 184
QA FireWall Client ............................................................................................................................. 185
Settings screen ..................................................................................................................................... 186
Login screen ......................................................................................................................................... 186
Scan Barcode Screen ............................................................................................................................ 187
If configuration is ok, the first step of the application is the scan order screen. Each user has a barcode
which identifies them. Scan this barcode to login to the system, or type the code using a keyboard and
press ENTER. ........................................................................................................................................ 187
Eyelet Squeezing Client ...................................................................................................................... 189
Login Screen ......................................................................................................................................... 189
Scan Order Screen ................................................................................................................................ 189
Maintenance Screen ............................................................................................................................ 190
Logout Screen ...................................................................................................................................... 191
Squeezing Screen ................................................................................................................................. 191
Reworking operations in test stations................................................................................................ 194
Adding defects to a harness ................................................................................................................. 194
Repairing defects ................................................................................................................................. 195
Rework Report Viewer ....................................................................................................................... 197
Creating and configuring labels .......................................................................................................... 198
Supported label printers and file formats ............................................................................................ 198
RAW printing languages .................................................................................................................. 198
Labels and order information TAGs ................................................................................................. 198
Creating a label .................................................................................................................................... 199
Supported label TAGs ........................................................................................................................... 201
General harness information ........................................................................................................... 201
Harness module list ......................................................................................................................... 201
Harness reported defects ................................................................................................................ 201
Validating a station in KSK project ..................................................................................................... 203
Logging and diagnostics ..................................................................................................................... 204
Activating logs ...................................................................................................................................... 204
Activating memory usage logs ............................................................................................................. 205
Diagnosing problems with libraries ...................................................................................................... 206
Shared interfaces ............................................................................................................................... 209
KSK Client interface .............................................................................................................................. 209
Properties ........................................................................................................................................ 209
Methods........................................................................................................................................... 209

© EMDEP 2024 Page 7

Emdep KSK Client / User’s guide

KSK Rework interface ........................................................................................................................... 219

Properties ........................................................................................................................................ 219
Methods........................................................................................................................................... 219
KSK Terminal interface ......................................................................................................................... 220
Properties ........................................................................................................................................ 220
Methods........................................................................................................................................... 220

© EMDEP 2024 Page 8

Emdep KSK Client / User’s guide

GETTING STARTED

© EMDEP 2024 Page 1

Emdep KSK Client / User’s guide

Introduction
The Emdep KSK Client package contains all client software to create any supported station in
production lines.

• Emdep KSK Rework Terminal

Application that implements a rework station.
• Emdep KSK Dispatch Terminal
Application that implements a standard dispatch station.
• Emdep KSK Validation Terminal
Application that implements a module validation (PPAP) station.
• Emdep KSK Spare Module Validation Terminal
Application that implements a spare module validation station.
• Emdep KSK Test Terminal
Application that allows visually configure a test station using Wintestem™.
• Emdep KSK Board Exporter
Utility to add/update the station board data into the KSK project.
• KSK system libraries
Libraries to allow stations interact with KSK system (flow control, test compilation, etc.).
• Tools and utilities
Common utilities used to check COM components, open MDB files, etc.
There is also another kind of KSK Clients, called KskWebServiceClient. These thin clients use Ksk
web service, meaning that they use low resources and can be executed over a raspberry
(although it can be also executed on a normal computer running Windows). Currently these
stations use this modality:
• Visual Inspection
• Warehouse to rework
• Micronorma
The stations mentioned above are included in KskWebServiceClient application. However, there
are another thin client applications:
• Marriage
• Eyelet Squeezing
Those applications are provided in a separate .exe with their own .lng files for dictionaries.
All those clients are not included in the setup of KSK Client. Each is inside a zip file and consist
only of few files (two at the moment of creating this guide: an exe file and a dictionary file).
This zip file can be unzipped in the root of a USB pen-drive. Then, connecting this pen-drive to a
raspberry device and restarting the raspberry will update the application. The initial system
image must be provided by Emdep in a special SD card.

© EMDEP 2024 Page 2

Emdep KSK Client / User’s guide

Installing KSK Client

Client requirements

Hardware

• 1GB RAM
• 100 MB of hard disk available space
• Network access to KSK server(s)

Software
• Microsoft Windows Vista, 7, 8, 8.1 or 10.
• Microsoft .NET Framework 2.0 (3.5 are also possible, since they support 2.0)
• Microsoft .NET Framework 4.0 (4.5 is also possible, since it supports 4.0).
• Microsoft .NET Framework 4.7.2 or above is needed for thin applications.

Station installation
All KSK station software is distributed in a single setup package in order to simplify the process
as much as possible.

In case that this installer is executed in a computer where an older version of this software was
already installed, it will be updated, however, scripts folder containing .vbs files will not be
updated to prevent the loss of the changes made inside the script to accommodate script to
client configuration, such as database name, postgresql port and wintestem variables.

To install Component Assembly Terminal

1. Execute the installation package provided for this software:

Emdep.KSK.Client.Setup.X.X.X.exe

2. Depending on the version of Microsoft Windows and/or the security policies, Windows
will show a confirmation dialogue. Press Yes button to start the installation.

© EMDEP 2024 Page 3

Emdep KSK Client / User’s guide

3. The first step is to choose the language for the installation process. Choose the preferred
language and press OK button.

4. Second step is basically a welcome page. Simply press Next > button to continue or
Cancel to cancel the installation.
5. The third step shows the Emdep License Agreement. Review the license terms and if the
license is accepted, press I agree button. If the license is declined, press Cancel button
to cancel the installation.

6. The fourth step allows to select the installation path and bring information related to
the space required and space available in the selected volume.

© EMDEP 2024 Page 4

Emdep KSK Client / User’s guide

Emdep recommends using the proposed path:

C:\Emdep-2\KSK\Client

7. Finally, to start the installation, press Install button. The installer will copy all files in the
specified folder and create a new folder into the Windows Start Menu.

© EMDEP 2024 Page 5

Emdep KSK Client / User’s guide

Installing KskWebServiceClient
Client Requirements

Hardware
• Raspberry 3B+
• 1GB RAM
• SD with at least 100MB of disk available space
• Network access to KSK Web Service

Software
• Linux with Mono or Microsoft Windows 7, 8, 8.1 or 10 (provided in SD image)
• Microsoft Net Framework 4.7.2 or above (provided in SD image)

Station installation
For the raspberries (Linux) an SD (Secure Digital) memory device will be provided with an image
containing the application. However, application can be updated connecting a pen-drive via USB
to raspberry device and restarting raspberry.

Configuration of KskWebServiceClient

These parameters must be configured by Emdep qualified staff

First time that application is started, configuration screen will appear:

© EMDEP 2024 Page 6

Emdep KSK Client / User’s guide

First field “Base URL” must be filled by the base URL where web service is running, followed by
/rest.

For example, if web-service is running at http://YRLB-APP03:8888 then this field must be filled
as http://YRLB-APP03:8888/rest

NOTE: Some times, depending on the DNS configuration, it might be necessary to add “.local”
after the host name (http://YRLB-APP03.local:8888/rest in the example).

When pressing “TEST URL” button, the rest of fields will be filled:

Checkboxes shown on the right are not editable and depends on the selected type of client
station. Fields on the left must be set according to the client that we are configuring.

This screen can be also accessed by pressing configuration button on the right-bottom corner in
order scanner screen, after having logged in as a user with superuser/supervisor role.

Client Station Type must be choosen. Currently, these client station types are supported:

- Micronorma Leak (since version 1.1.0)

- Visual Inspection
- Warehouse to rework

Please note that Station Type will define the behavior of this application, but it’s not connected
to the defined station types. It is responsibility from the engineer who make the startup to select
a proper Station that is suitable with the Client Station Type.

Development note: This client application uses processorder call from Emdep KSK Web-service
to perform open and close stage.

© EMDEP 2024 Page 7

Emdep KSK Client / User’s guide

Installation and Configuration of Marriage client

Marriage client is also a web service client application, so same steps described previously apply
to this client.

However, because of its nature, fields in settings screen are a little bit different:

Only production lines that contain marriage substations will be shown in Production Line
dropdown list.

Only marriage stations of selected production line will be shown in Station dropdown list.

Prefix for the harness is configured on web-service and it is not possible to edit it on client
application, because it is common for all marriage stations accessing the web-service.

Prefix and suffix of the subassembly should be configured per each station and they can be
different for each station. Configuring a prefix and suffix is mandatory.

The field “Time after matching OK” can be configured to make the system press automatically
the OK button after some seconds. The number of seconds is specified by this parameter. If it is
0, then the button is not pressed automatically and the screen will be shown until the operator
press the OK button:

Development note: This client application uses openStage and closeStage calls from Emdep
KSK web service, instead of using processOrder, as used by the rest of raspberry applications.

© EMDEP 2024 Page 8

Emdep KSK Client / User’s guide

Installation and Configuration of Assembly Guiding application

Assembly guiding application is another thin client application. This application is a simple
application to guide operator for making the assembly, showing some instructions and pictures
in the screen.

The installation and configuration of this application follows the same steps as any other thin
client application.

© EMDEP 2024 Page 9

Emdep KSK Client / User’s guide

Installation and Configuration of Subassembly Matching client

Subassembly matching client is another thin client application, and it is intended to perform the
partial subassembly matching and the final subassembly matching. Thus, configuring the
application will be similar than configuring other thin clients: defining parameters such as the
URL of the KSK web service.

Final subassembly matching is a type of station (called final matching). For partial matching,
subassembly station should be used as type of station. Both types must be substations of a
preassembly station.

Normally only one final matching station should be configured. In case there are more than one
configured, harness can be processed by any of them. When a harness is processed by a final
matching station, the whole step will be closed and the harness will advance to next step, no
matter if harness has been processed by partial matching stations or not.

No other type of substations (such as marriage stations) should be configured here.

IMPORTANT: When subassembly stations are being used with subassembly matching client,
those stations should not contain substations in it (i. e., they should not contain any subassembly
workstations defined inside).

© EMDEP 2024 Page 10

Emdep KSK Client / User’s guide

Additionally, in order to make final subassembly matching work properly, special flows of type
SC1 and SC2 should be configured. This can be performed in Layout Designer of KSK Studio:

Both SC1 and SC2 are special flows that send the harness to Rework when it arrives at Visual
Inspection, but SC1 passes by Schunk and SC2 skip Schunk.

Please note that the names SC1 and SC2 can be any other names. The important thing is the
type and also the defined steps, which should start with first desired step after Final Matching
station, and should finish with Rework.

© EMDEP 2024 Page 11

Emdep KSK Client / User’s guide

© EMDEP 2024 Page 12

Emdep KSK Client / User’s guide

Installation and Configuration of Eyelet Squeezing Client

The Eyelet Squeezing Client is another thin client application. However, unlike the previous
clients this has been updated to run on .NET Core. As its name suggests, the purpose of the
Eyelet Squeezing Client is to guide the users throughout the squeezing process of an eyelet.

You will see the following window the first time the application is launched:

Despite the UI looking a bit different, the configuration options are similar to the other KSK Web
service clients.

In the General section you will have to configure the Web service URL like in previous clients.
You will also have the option to change the language, but you must complete all configuration:
otherwise, the language change will not be saved. Language changes require restarting the
application after saving the configuration to take effect.

© EMDEP 2024 Page 13

Emdep KSK Client / User’s guide

Once the Web service URL has been specified and tested via the “TEST URL” button, the rest of
the options will become available and you will see all terminals and applicators in their
corresponding sections.

In the Station section you will be able to select the line and station to identify this particular
station. You will also be able to select if the Terminals and Applicators are connected to an
Arduino or IO Board device. The next option is a logout code or password for closing a session
in this station. And, finally, you have two optional fields: the prefix of the orders in this station
and the last characters to remove from the order.

It is important to note that only Squeezing Stations defined as such in KSK Studio will appear.

In the Terminals and Applicators sections you can configure the physical position of each
applicator and terminal on their respective racks. You can also configure their Arduino pins (if
the I/O Device is set to Arduino) or their cards and pins (if the I/O Device is set to EMDEP IO
Board v2012).

It is important to notice that the terminals and applicators displayed here are the terminals and
applicators configured in KSK Studio. All applicators must be configured in all stations, and if a
harness is started in a station and this station is missing applicators or terminals used in the
harness, you will be required to configure them before continuing.

© EMDEP 2024 Page 14

Emdep KSK Client / User’s guide

Updating process for raspberry applications

Installed application on raspberry can be updated just connecting a pen-drive via USB to
raspberry device and restarting raspberry. Content of this pen-drive will be provided by Emdep
and must have a folder called EmdepClient_Upgrade.

This EmdepClient_Upgrade folder must be on the root of the pen-drive, and its typical content
structure is like what it is shown in the following picture:

This updating process is useful not only to upgrade an EMDEP client application in raspberry,
but also to change the application that we want to run on that raspberry device. For example,
we can currently have a WarehouseToRework application in one raspberry and we can connect
the Upgrade for Marriage application. After performing that, Raspberry will contain Marriage
application instead of WarehouseToRework application.

© EMDEP 2024 Page 15

Emdep KSK Client / User’s guide

Troubleshooting
Error when starting raspberry application

Problem
When starting raspberry application, after having upgraded a version, this message appears:

Solution
Remove (or rename) the settings.xml file located on /home/emdep_pi. After doing this, settings
screen will appear when starting application. Set properly all the settings and save the
configuration.

© EMDEP 2024 Page 16

Emdep KSK Client / User’s guide

ASSEMBLY / TEST
STATIONS

© EMDEP 2024 Page 17

Emdep KSK Client / User’s guide

Assembly/Test stations
Assembly/Test stations are the common stations where an assembly or test operation is
performed for all orders. These kinds of stations can operate as a single station or in cluster (for
parallel multi-user operations). These stations need a license of Emdep Wintestem™, used to
perform the assembly / test operations. Each software works together through shared
components.

The following schema shows a basic flow for this kind of stations:

The assembly/test stations can be created using two different methods:

• Standard stations: Standard stations are the default type of stations used in KSK,
allowing complex assembly/test operations and bringing maximum of flexibility, but
more complicated and harder to maintain. This method is based to a couple of Visual
Basic scripts that should be called from Emdep Wintestem™ process.

• Integrated stations: The Integrated stations are simpler than the standard. The flow and
all screens are built-in and is easy to create and set-up, only the test(s) needs to be
configurated.

• Cluster stations: In certain situations, a multi-user operation is needed for a single

station. In that cases, one KSK station can be composed by two or more workplaces
acting as a single station. This kind of configuration is supported natively by all KSK
stations. This type of stations must be created using Integrated stations.

© EMDEP 2024 Page 18

Emdep KSK Client / User’s guide

Standard stations
Creating a standard station
Creating and configuring a basic assembly / test station is a simple task. Be sure that before to
follow these steps, the station has been created in the KSK project layout.

1. Install the Emdep KSK Client Station software as described in the previous sections.

2. In the Windows Start Menu, in the Emdep KSK folder, open the Client Station
application.

3. Set the KSK database Connection settings and press Test connection button.

4. Set the KSK station Identification settings (project, line and station name).

5. Select the Wintestem tab page.

6. In the WTT project tab page, specify the Wintestem project path used for the KSK
assembly / test operations.

© EMDEP 2024 Page 19

Emdep KSK Client / User’s guide

7. In the same tab page, in Processes group, press the Generate process files button from
the group Standard flow.

This action generates the necessary files (PRG process files and VBS scripts) to use the
station in the selected KSK project, in the Wintestem project path root folder (specified
in the step 6).

8. Select the tab page Station and then, select Repair / Rework tab page.

9. Check the box Allow repair defects in the station if repairing the registered defects is
allowed in the station. If not, uncheck and the station only allows the operators register
defects without repairing them.

If the line contains assembly & scanning station(s) and in the current station is allowed
to replace any scanned component, it is necessary to enable the Allow re-scan replaced
components in order to be able to replace and re-scan the damaged components.

The rework label can be printed automatically after the defects register and defects
repairing screens are shown. To print automatically the label, enable the Print specific
label for harness sent to rework checkbox and then, select the appropriate label. Learn

© EMDEP 2024 Page 20

Emdep KSK Client / User’s guide

how to create labels to print in Creating and configuring labels section. If this option
remains disabled, the label should be printed from Wintestem™ process.

10. Select the Logging tab page and enable the LOGs for the station in order to be able to
diagnose any problem that might appear. See a detailed explanation on how to set-up
the LOG in Logging and diagnostics section.

11. Finally, the base KSK station is ready. Press OK to close the configuration application and
save the current settings.

Testing the station with Wintestem™

After generating the Wintestem files, the station is ready to be tested for the KSK flow (without
any assembly or test operation). To test the station using Emdep Wintestem™ follow the
described steps.

Before to start, make sure you have a valid user and an order waiting for the station created.
Read Validating a station in KSK project section to know how to move orders to specific station.

1. Open Emdep Wintestem™.

2. Select Test Harness option. The Start program dialogue will be shown.

© EMDEP 2024 Page 21

Emdep KSK Client / User’s guide

3. Select the program KSK_Main_Std and press Accept button to put the station working.

This Wintestem™ process includes all needed to implement the KSK basic flow, including
the compilation of the selected tests and a basic test (all test should be checked and well
configured after this verification).

4. A Wintestem™ input LOGIN screen will be shown. Provide a valid user code (an account
with enough privileges to use the current station).

5. After a valid user code is provided, the ORDER screen will be shown. Scan or manually
type the order code.

Of course, the order should be waiting for the current station (or stage) in the current
line, otherwise, an error will be shown.

6. The TEST screen will be shown. Select 1 or 2 depending on the result desired to simulate
an assembly/test operation.

7. Depending on the selected option the flow closes the order as OK (option 1) and come
back to the order scanning screen, otherwise, the user can select to repeat the test or
add defects and send to rework.

Generated process files

When the station processes are created, it is possible to start processing orders without a real
assembly / test operation, just to test the KSK flow process.
File Type Comments
KSK_Main_Std.prg WTT Main station process.
Process
Sub_Test_Std.prg WTT Harness test process.
Process
KSK_Rework_Send.vbs VBScript Add defects to the current harness
and then, send the harness to a
rework station.
KSK_Rework_SendWithSpecificDefect.vbs VBScript Add custom description to the
deffect to the current harness and
then, send the harness to a rework
station.
KSK_Settings.vbs VBScript Variable initialization for KSK client.
KSK_Stage_Close_NOK.vbs VBScript Close current test stage as NOK.
KSK_Stage_Close_OK.vbs VBScript Close current test stage as OK.

© EMDEP 2024 Page 22

Emdep KSK Client / User’s guide

KSK_Stage_Open.vbs VBScript Open working stage for the current

harness.
KSK_Tests_Clean.vbs VBScript Clean all generated test files for the
current order.
KSK_Tests_Compile.vbs VBScript Generate (compile) all test files
needed for the selected tests (HNS,
CP, etc.).
KSK_User_IsValid.vbs VBScript Authenticate the current user.

The generated files are a couple of Emdep Wintestem™ processes (PRG files) and some VBS
scripts. These files are internally using Wintestem variables for the flow control.

Obviously, any of these variables can be used in the test process but considering that they should
only be used in reading mode. Any change in its value will affect the internal process of the
station and it would not behave correctly.
Variable Contents Comments
@INT01 VBS call result Used to store the internal process results after VBScript calls.
- NOK = 0 → Internal execution error
- OK = 1
@STR01 VBS call result Used to store the internal process result message (in case of any
error occurs).
@INT02 Test result Test process result.
- NOK = 0
- OK = 1
@STR08 HKSK folder Path to precompiled files (HKSK files).
@STR09 User code Current user code.
@STR10 Harness order Current order number.
@STR11 KSK project name
@STR12 Station line name
@STR13 Station name
@STR14 WTT project path Current WTT active project path (harness.mdb)
@STR15 Database host Server name or IP
@STR16 Database user Database access account login
@STR17 Database password Database access account password

As a rule, NEVER set the value for these variables, except the @INT02 that is used to specify
the test result before to leave the test process.

Integrated stations
Creating an integrated station
Creating and configuring a basic integrated assembly / test station is a simple task. Be sure that
before to follow these steps, the station has been created in the KSK project layout.

1. Install the Emdep KSK Client Station software as described in the previous sections.

© EMDEP 2024 Page 23

Emdep KSK Client / User’s guide

2. In the Windows Start Menu, in the Emdep KSK folder, open the Client Station
application.

3. Set the KSK database Connection settings and press Test connection button.

4. Set the KSK station Identification settings (project, line and station name).

5. Select the Wintestem tab page.

6. In the WTT project tab page, specify the Wintestem project path used for the KSK
assembly / test operations.

7. In the same tab page, in Processes group, press the Generate process files button from
the group Integrated flow.

This action generates the necessary files (PRG process files and VBS scripts) to use the
station in the selected KSK project, in the Wintestem project path root folder (specified
in the step 6).

© EMDEP 2024 Page 24

Emdep KSK Client / User’s guide

Optionally additional files can be generated to open the station settings dialogue from
Wintestem process or calling a VBS script. These additional files can be generated
enabling the Generate process to open station settings check box.

8. Select the tab page Station and then, select Repair / Rework tab page.

9. Check the box Allow repair defects in the station if repairing the registered defects is
allowed in the station. If not, uncheck and the station only allows the operators register
defects without repairing them.

If the line contains assembly & scanning station(s) and in the current station is allowed
to replace any scanned component, it is necessary to enable the Allow re-scan replaced
components in order to be able to replace and re-scan the damaged components.

The rework label can be printed automatically after the defects register and defects
repairing screens are shown. To print automatically the label, enable the Print specific
label for harness sent to rework checkbox and then, select the appropriate label. Learn
how to create labels to print in Creating and configuring labels section. If this option
remains disabled, the label the label will not be printed.

10. Select the Logging tab page and enable the LOGs for the station in order to be able to
diagnose any problem that might appear. See a detailed explanation on how to set-up
the LOG in Logging and diagnostics section.

11. Finally, the base KSK station is ready. Press OK to close the configuration application and
save the current settings.

All the station settings are centralized with a single XML settings file located in the installation
folder. The file always is called settings.xml.

Testing the station with Wintestem™

After generating the Wintestem files, the station is ready to be tested for the KSK flow (without
any assembly or test operation). To test the station using Emdep Wintestem™ follow the
described steps.

Before to start, make sure you have a valid user and an order waiting for the station created.
Read Validating a station in KSK project section to know how to move orders to specific station.

1. Open Emdep Wintestem™.

© EMDEP 2024 Page 25

Emdep KSK Client / User’s guide

2. Select Test Harness option. The Start program dialogue will be shown.

3. Select the program KSKProcess and press Accept button to put the station working.

4. The LOGIN screen will be shown. Provide a valid user code (an account with privileges
to use the current station).

© EMDEP 2024 Page 26

Emdep KSK Client / User’s guide

5. After a valid user code is provided, the ORDER screen will be shown. Scan or manually
type the order code.

Of course, the order should be waiting for the current station (or stage) in the current
line, otherwise, an error will be shown.

6. The TEST screen will be shown. Select 1 or 2 depending on the result desired to simulate
an assembly/test operation. Note that this screen is generated from Emdep
Wintestem™ process ( TestProcess.prg ).

7. After pressing OK (for example), the working stage is closed in the current station and
the result is shown in the screen.

© EMDEP 2024 Page 27

Emdep KSK Client / User’s guide

8. Finally, after some seconds the flow automatically goes to the order scanning screen
again (step 5).

Generated process files

When the station processes are created, it is possible to start processing orders without a real
assembly / test operation, just to test the KSK flow process.
File Type Comments
KSK_Main_Int.prg WTT Process Main station process.
Sub_Test_Int.prg WTT Process Harness test process.
KSK_Setup_Int.prg WTT Process Process to open the station settings
dialogue.
KSK.Terminal.Harness.Close.vbs VBScript Close the current harness session.
KSK.Terminal.Harness.Start.vbs VBScript Open a new harness session.
KSK.Terminal.Settings.vbs VBScript Open the settings dialogue.

The generated files are a couple of Emdep Wintestem™ processes (PRG files) and some VBS
scripts. These files are internally using Wintestem variables for the flow control.

Obviously, any of these variables can be used in the test process but considering that they should
only be used in reading mode. Any change in its value will affect the internal process of the
station and it would not behave correctly.
Variable Contents Comments
@INT01 Process result Used to store the internal process results.
- NOK = 0 → Internal execution error
- OK = 1
@STR01 Process result message Used to store the internal process result message (in case of any
error occurs).
@INT02 Test result Test process result.
- NOK = 0
- OK = 1
@STR09 User code Current user code.
@STR10 Harness order Current order number after scanning and transformation.

As a rule, NEVER set the value for these variables, except the @INT02 that is used to specify
the test result before to leave the test process.

Cluster stations
In certain situations, one station needs more than one computer to control the assembly / test
operation. A typical sample is a montage station showing three screens, each one with a
different fuse box and operated by different persons but working on same harness at same time
(in parallel). This scenario can be implemented easily by a cluster station. Each cluster must have
three main actors: server, master and slaves.

© EMDEP 2024 Page 28

Emdep KSK Client / User’s guide

MSSC Cluster Controller (server)

Each cluster require a server (Emdep MSSC Server) who orchestrate all required
communications between the involved computers. The cluster controller support multiple
clusters in same server and is responsible to orchestrate all communications between involved
physical computers using TCP/IP. One server support more than one cluster. Before to create
the cluster, an Emdep MSSC Server should be installed and configured.

Single mode
In this scenario, the MSSC server is installed in one of the computers involved in the cluster and
the server controls only the cluster itself.

Server mode
In this scenario, the MSSC server is installed in KSK server (or other server) and control all clusters
in the KSK project.

© EMDEP 2024 Page 29

Emdep KSK Client / User’s guide

Defining a cluster in MSSC server

When a MSSC server is installed, a clusters.xml file is created. This file contains all controlled
clusters. The format is:

<?xml version="1.0" encoding="utf-8"?>

<clusters version="1.0">
<cluster id="CL1" mode="ALL">
<station name="BT1 L1" master="YES" />
<station name="BT1 L11" />
<station name="BT1 L12" />
</cluster>
</clusters>

In the exposed sample, the server is controlling the cluster CL1 with three stations. As mentioned
in below sections, for the KSK system, all cluster stations are working as a single station. The
MASTER station will have the KSK station name (in the example, BT1 L1). The rest of stations
have the same name plus a number (ID), distinct for each station (BT1 L11, BT1 L12, etc.).

Defining the master station

All cluster must have one (and only one) master computer, and will be the linked computer to
KSK system, responsible to authenticate the operator, read and validate the orders and to
control the working stage (open/close).

1. In the Windows Start Menu, in the Emdep KSK folder, open the Client Station
application.

2. Select the Cluster tab page.

© EMDEP 2024 Page 30

Emdep KSK Client / User’s guide

3. In Working mode group, choose Cluster MASTER station option.

4. In Server properties (MSSC) group, specify the IP and port number for the installed
Emdep MSSC server. Also, a PING interval can be set (by default, this value is set to
500mSec).

5. In Client settings group, specify:

• Cluster identifier (CLID) → This value is defined in Emdep MSSC server, in file
clusters.xml .

• Slave identifier (CLID) → This value is not used by master stations.

• Test max. timeout → If this value is greater than 0, indicate the maximum
number of milliseconds to finish the current assembly/test operation. If this
time is exceeded the current operation will be finished as NOK.

6. Press OK to save the current settings or Cancel to discard all changes.

Defining the slave stations

A couple of slave computers can be added to each cluster. These computers only receive the
order number. Through Emdep KSK Client interfaces could read KSK project data if needed (to
know the list of modules, for example).

1. In the Windows Start Menu, in the Emdep KSK folder, open the Client Station
application.

2. Select the Cluster tab page.

© EMDEP 2024 Page 31

Emdep KSK Client / User’s guide

3. In Working mode group, choose Cluster SLAVE station option.

4. In Server properties (MSSC) group, specify the IP and port number for the installed
Emdep MSSC server. Also, a PING interval can be set (by default, this value is set to
500mSec).

5. In Client settings group, specify:

• Cluster identifier (CLID) → This value is defined in Emdep MSSC server, in file
clusters.xml .

• Slave identifier (CLID) → This value should be unique by all slaves in the cluster.

• Test max. timeout → If this value is greater than 0, indicate the maximum
number of milliseconds to finish the current assembly/test operation. If this
time is exceeded the current operation will be finished as NOK.

6. Press OK to save the current settings or Cancel to discard all changes.

© EMDEP 2024 Page 32

Emdep KSK Client / User’s guide

Station settings
All station settings can be set using the Test Terminal application (included in the Emdep KSK
Client installation package).

Assembly/test operations
The basic difference between a test directly performed from Emdep Wintestem™ and from a
KSK project is basically that in KSK the order composition change depending on the modules
contained, so a compilation is needed for each order (in Emdep Wintestem™ this feature is
performed by reference, not by order).

So, in a KSK station, a compilation should be performed for each order to generate the assembly
/ test files and delete all generated files at the end of the process (to avoid storage problems
due to the large number of generated files).

The assembly / test operations to perform during a work stage for each order should be specified
in the station configuration, and the Emdep KSK Client will generate the files before the
operation and then, when the stage is closed, the files will be removed automatically.

1. In the Windows Start Menu, in the Emdep KSK folder, open the Client Station
application.

2. Select the Emdep Wintestem™ tab page.

3. In the WTT project tab page, check the Wintestem project path used for the KSK
assembly / test operations. Should be the same used by the active Emdep Wintestem™
project.

4. In the Tests tab page, check all Wintestem tests needed to perform in the current station
for each order.

© EMDEP 2024 Page 33

Emdep KSK Client / User’s guide

All the test files will be generated in the Wintestem project path root folder (specified
in the step 6), but a different folder can be specified for each assembly / test type using
the path selection field.

Checking the Remove test files after harness working session check box, all KSK test
files will be deleted after the operation. If this option is disabled, all files will remain
in the station and after a long time working in the station, storage problems could be
appearing, so use this option only for testing purposes.

If an electrical test is enabled, the Precompiled files folder should be specified,

needed to compile the HKSK files generated by the Emdep KSK Precompiler Service.

5. Press OK to save the settings and close the application.

Export Wintestem board data to KSK project

The board data defined in Wintestem Board Edition should be imported to KSK project each
time the board is changed (or, of course, when it is finished for first time). Emdep KSK System
offer this importer directly through the station configuration utility but, of course, Emdep KSK
Board Exporter can be used to do this task.

1. In the Windows Start Menu, in the Emdep KSK folder, open the Client Station
application.

2. Select the Station tab page and then, Import board data tab page.

© EMDEP 2024 Page 34

Emdep KSK Client / User’s guide

3. Select the board type to import to KSK project using the drop-down list Board type.

4. In field File, select the appropriate file to import (MDB for electrical and vision test, CT
for clips, etc.).

5. Press Import to KSK project button to start the import process.

6. When the process is finished, to close the configuration tool press OK button if any
settings was changed or Cancel if no changes should be stored.

After a short time, the data will be available in KSK project and can be checked using Emdep KSK
Studio tools.

Order scanning options

In most cases, the scanned code is used as an order number to obtain the harness order in the
current KSK project. But in some cases, the scanned code should be transformed to obtain a
valid order. Emdep KSK Client offers several options to transform the scanned codes into a valid
order number.

1. In the Windows Start Menu, in the Emdep KSK folder, open the Client Station
application.

2. Select the Station tab page and then, select the Orders tab page.

© EMDEP 2024 Page 35

Emdep KSK Client / User’s guide

3. Choose the desired transformation for the scanned code:

a. Use the scanned code as an order number: no transformation will be applied to

the scanned code.

b. Use a part of the scanned code as an order number: Get a portion of the scanned
code. In this transformation, the starting character and a fixed length should be
specified.

c. Use a regular expression to transform the scanned code: Apply a regular

expression to get only a part of the scanned code. Using a regular expression,
all matching occurrences will be removed (replaced by an empty text).

4. Specify the option that must be applied after scanning the code:

a. Trim spaces and to upper case: Remove all spaces at the beginning and at the
end of the scanned code and then, transform the result into upper case text (all
alphabetic characters).

b. Accept rework labels: Enabling this option the station accepts both order codes
and rework codes (order number with prefix). By default, this option is disabled.

c. Remove first/last: Allow remove a fixed number of characters from the

beginning or from the end of the resultant order number.

After defining all transformations and options, is possible to test how the station
transform the scanned codes by using the Scanned codes tester (press Test codes to
open the tester).

© EMDEP 2024 Page 36

Emdep KSK Client / User’s guide

5. Press OK button to store the settings or Cancel to discard all changes and close the
configuration utility.

Keyboard shortcuts
For the test tables using an Emdep Keyboard it is possible to define some key to the basic
operations used by operators during the process. These are Exit (return to Wintestem), Change
operator (login) and Cancel current operation. Of course, not all screens support all operations,
it will depend on the screen. The available options are shown at the bottom of the test screen:

1. In the Windows Start Menu, in the Emdep KSK folder, open the Client Station
application.

2. Select the Station tab page and then, select the Shortcuts tab page.

3. Choose the key for each action. For the action that the shortcut is not used, select the
key None.

© EMDEP 2024 Page 37

Emdep KSK Client / User’s guide

4. Press OK button to store the settings or Cancel to discard all changes and close the
configuration utility.

Rework options
In case of a NOK test, the station will offer to operator a simple menu with two options:

• Retest: The current stage is closed as NOK and then, the station will show the order
scanning screen.
• Send to rework: In case that the harness has some defect(s), the station will show a
screen to add defects to the current harness and optionally let to repair in-station.

Backup
Both installation technicians and those responsible for the stations in the plants usually make
backup copies and restore the test stations. The KSK client configuration include a simple way
to create a backup of the station in a single ZIP file.

In addition, detailed information on installed components and versions is added with each
backup. This feature makes the backups interesting both for those responsible for the station in
the plant and for the EMDEP support service, which with a simple file can more easily diagnose
any issue that may arise.

1. In the Windows Start Menu, in the Emdep KSK folder, open the Client Station
application.

2. Select the Backup tab page.

3. To generate a backup, press Backup current station button. When the backup is
finished, the available backup list will be refreshed.

4. To open the folder where the backups are generated, press the Open backups folder
button.

5. To delete a backup, select the corresponding row and then, press Delete selected
backup button.

© EMDEP 2024 Page 38

Emdep KSK Client / User’s guide

In case that a station requires technical assistance from EMDEP support service, a backup
should be sent in order to speed-up the analysis of the issue. To send a backup file we
recommend using cloud services like Dropbox, Google Drive or Microsoft OneDrive.

Sending station board data to KSK project

When the programming of an assembly/test table in Emdep Wintestem is finished, the board
data should be sent to KSK project in order to maintain the KSK project up-to-date. Also, if any
change is performed in the station board (new connector added, more detections, etc.), the
board must be uploaded again.

This upload process, of course, must be performed during the preparation of the station, but
can be performed in production if any change affecting the board data is performed in the
station.

The process can be done using two different tools:

• From the station settings dialogue (described in Export Wintestem board data to KSK
project section).
• Using the Emdep KSK Board Exporter application (distributed with Emdep KSK Client
software).

Both methods use the same library to import the data, so both can be used indistinctly.
However, Emdep KSK Board Exporter don’t use the station settings (contained in settings.xml
file), so it is more flexible and portable.

Upload board data with Emdep KSK Board Exporter

1. From the Windows Start menu, select the application Emdep KSK → Utilities → Board
Exporter.

© EMDEP 2024 Page 39

Emdep KSK Client / User’s guide

The first time the application is run, the configuration dialog will open where you can
establish the connection to the KSK project database.

Fill all required data and check the connection. If the connection can be stablished, the
application could start, otherwise a message appears with the error detected during the
connection.
2. From the Station type group, select the type of station.
Each type of station is able to upload certain board data (not all). The following table
contains the supported board types by station type:
Board type
Tightening
Electrical

Eyelets
Relays
Vision

Clips

Station type
Electrical  
Vision   
Clips 
Tightening   

3. From the Station group, select the source station (usually the station from where the
data are being exported).
4. From the Data to export group, select the file to upload. Depending on the type of
station, the file will be the harness.mdb, CP file, etc.
5. Press Export data button to start exporting the board data. Depending on the size of the
board and the size of the KSK project, this process can take long time.

© EMDEP 2024 Page 40

Emdep KSK Client / User’s guide

6. If the export process finishes without any problem, a message box will appear
confirming the operation.

Error and warning messages

During the export process, Emdep KSK Board Exporter can show messages for warnings and
errors. Warnings can be omitted, but errors always cancel the process to avoid problems in KSK
project.

Message Description
[CON] / [WAY] >> Pins not defined (loading Check board in Wintestem (harness.mdb). Not
board ways) all pins are related to a connector.

Creating Wintestem™ processes in KSK stations

All assembly and/or test operations that must be performed in the station should be
programmed in Sub_Test_Int.prg file. Is better to maintain the rest of the auto-generated
files in its original version to avoid confusions.

In KSK stations, most operations needs a specific order compilation because the composition of
each order changes. The Emdep KSK Client will compile each order in the operations specified
(see the section Adding assembly/test operations). It means that just before to start executing
Sub_Test_Int.prg process, all compilations will be ready to be used (the compilations are
managed internally by Emdep KSK Client).

Example 1: Perform an electrical test

The following example shows how to configure the station and the processes to perform an
electrical test consisting in 2 steps. Remember that the steps are defined in the KSK rules (not in
the station or in Wintestem™).

1. Open the station settings and select the Wintestem tab page and then, select the Tests
tab page.

© EMDEP 2024 Page 41

Emdep KSK Client / User’s guide

2. Enable the Electrical test option. Leaving the path field empty we tell the compiler to
generate the files into the WTT project folder (usually MyKskProject).

3. Enable the Remove test files after harness working session option to remove all files
when the test is finished otherwise, and after a while in operation, the WTT project
folder would contain thousands of files.

4. As it is an electrical test, it is necessary to specify the folder that contains the pre-
compiled orders (HKSK files) in the field Precompiled files folder.

5. If the process files have not yet been generated, generate them by following the steps
described in Creating a base station.

6. Press OK to save the current settings.

7. Open Wintestem™ and then, open the TestProcess.prg file in Process Editor and then,
modify the test according to the following sample:

Program

'Load the first step HNS test file

Harness "@STR10_1"

'Start step 1 of electrical test

Test(Wir:Yes, Lock:No, Det:Yes, Hard:Yes, Multi:No(999), Induct:No, Cont:No, Iso:No, OnceOK:No)

'Check the test results

If (ErrTest = True)

'Set the test result as NOK

SetValue(@Num02 = 0)

'Goto exit label

Goto "EXIT"

© EMDEP 2024 Page 42

Emdep KSK Client / User’s guide

'Load the second step HNS test file

Harness "@STR10_2"

'Start step 2 of electrical test

Test(Wir:No, Lock:No, Det:Yes, Hard:Yes, Multi:Yes, Induct:No, Cont:No, Iso:No, OnceOK:No)

'Check the test results

If (ErrTest = True)

'Set the test result as NOK

SetValue(@Num02 = 0)

'Goto exit label

Goto "EXIT"

'Set the test result as OK

SetValue(@Num02 = 1)

'Finish the process with a blank screen shown for 100 mSec
 Show (X) ← Label EXIT

Emdep Wintestem™ process colored for a better comprension

8. Save the Sub_Test_Int.prg file and the station is ready to be tested.

As can be seen above, the process starts loading the first HNS automatically generated by KSK
compiler (and available in the WTT project folder as @STR10_1.hns) and then, the electrical test
starts. If the test finish as NOK (ErrTest is true), the test result variable @INT02 is set to 0 (NOK)
and the flow goes to the end of the process, otherwise the flow continues.

The next step is to load the second step of the electrical test (@STR10_2.hns automatically
generated by KSK client) and launch the second test. If the test finish as NOK, the @INT02 is set
to 0 and the flow goes to the end of the process.

Finally, if all tests are finished as OK, the test result variable @INT02 is set to 1 (OK) the flow goes
to the end of the process.

The last Show command clear the screen (blank string) and will be closed automatically after a
short time (10 or 100 milliseconds) just to be sure that the Wintestem™ test screen is empty.
This command is the last in the process and have associated the label EXIT.

Example 2: Perform a double vision test

The following example shows how to configure the station and the processes to perform an
electrical test consisting in 2 steps. Remember that the steps are defined in the KSK rules (not in
the station or in Wintestem™).

1. Open the station settings and select the Wintestem tab page and then, select the Tests
tab page.

© EMDEP 2024 Page 43

Emdep KSK Client / User’s guide

2. Enable the Vision test option. Leaving the path field empty we tell the compiler to
generate the files into the WTT project folder (usually MyKskProject).

3. Enable the Remove test files after harness working session option to remove all files
when the test is finished otherwise, and after a while in operation, the WTT project
folder would contain thousands of files.

4. If the process files have not yet been generated, generate them by following the steps
described in Creating a base station.

5. Press OK to save the current settings.

6. Open Wintestem™ and then, open the Sub_Test_Int.prg file in Process Editor. The
following code shows how to achieve the test:

Program
'Load the scanned harness
Harness "@STR10_1"
'Vision test: well insertion test
 Test(Box: C:\VisionProject_PDCR\, Hns: F152-2, 1) ← Label TEST_1
'Check the test results
If (ErrTest = True)
'Offer to operator to repeat the test
 Show (X) ← Label MENU_VISION_1
'Option 1 -> Repeat well insertion test
If (Key = "1")
Goto "TEST_1"
'Option 2 -> Test NOK
If (Key = "2")
'Set the test result as NOK
SetValue(@Num02 = 0)
'Goto exit label
Goto "EXIT"
Goto "MENU_VISION_1"

'Load the second step HNS test file

Harness "c:\VisionProject_COVER\MyProject\COVER"
'Start step 2 of electrical test ← Label TEST_2
 Test(Box: C:\VisionProject_COVER\, Hns: Cover, 0)
'Check the test results

© EMDEP 2024 Page 44

Emdep KSK Client / User’s guide

If (ErrTest = True)
'Offer to operator to repeat the test
 Show (X) ← Label MENU_VISION_2
'Option 1 -> Repeat well insertion test
If (Key = "1")
Goto "TEST_2"
'Option 2 -> Test NOK
If (Key = "2")
'Set the test result as NOK
SetValue(@Num02 = 0)
'Goto exit label
Goto "EXIT"
Goto "MENU_VISION_2"
'Set the test result as OK
SetValue(@Num02 = 1)
'Finish the process with a blank screen shown for 100 mSec
 Show (X) ← Label EXIT

Emdep Wintestem™ process colored for a better comprension

7. Save the Sub_Test_Int.prg file and the station is ready to be tested.

As can be seen above, the process starts loading the first HNS automatically generated by KSK
compiler (and available in the WTT project folder as @STR10.hns) and then, the vision test starts.
If the test finish as NOK (ErrTest is true), the test result variable @INT02 is set to 0 (NOK) and
the flow shows a menu to repeat the test or finish as NOK.

The next step is to load the second vision test (in that case is a fixed cover test, not depending
on the order). If the test finish as NOK, the @INT02 is set to 0 and the flow shows another menu
to repeat the test or finish as NOK.

Finally, if all tests are finished as OK, the test result variable @INT02 is set to 1 (OK) the flow goes
to the end of the process.

© EMDEP 2024 Page 45

Emdep KSK Client / User’s guide

Re-scanning connector barcodes

Since version 3.31.0, it is possible to re-scan the barcodes of the tightening boxes/connectors
(item barcodes) in a station (normally just before dispatch) in order to check that all those
boxes/connectors are still in the harness before the harness will be packed.

To accomplish this, a file named KSK_ReScanConnector.vbs is included in the installer.

Parameters that have to be passed to this script are self-commented inside.

Additionally, one wintestem process which uses this script is provided as an example. This
wintestem process is a file called ReScanConnector_test.prg included in folder prg_samples.

When calling properly to this script, the following screen will appear:

As it can be seen, in this example, order 6043590IM08 has 3 barcodes and all of them are
pending to be scanned.

Barcodes can be scanned in any order.

When scanning one of the codes, it will become green:

© EMDEP 2024 Page 46

Emdep KSK Client / User’s guide

When all codes are scanned, control will be returned to wintestem process, and a successful
code will be returned.

In case of scanning a barcode which is not in the list, then the station will be blocked until some
supervisor scans their code:

When a supervisor scans their code, 3 buttons will appear to choose between 3 actions:

Accept Barcode This button will accept the scanned barcode as correct, meaning
that one of the barcodes in the list will be replaced by this one.

Send Order to Rework This button will finish the re-scanning and will return a code
indicating that the wintestem process should send the harness to
rework. The harness will not be sent to rework by this script. It is
wintestem process’ responsibility to send it to rework.

Abort Scan and Exit This button will abort the re-scanning, returning an exit code to
wintestem process to indicate that user has aborted the operation.

© EMDEP 2024 Page 47

Emdep KSK Client / User’s guide

After a wrong barcode has been accepted, it will be added to a list in the left titled NEW
SCANNED BARCODES, and the code on the right that is from same pattern will appear in yellow:

When the number of new scanned barcodes plus the number of barcodes correctly scanned
equals the number of the items in scanned barcodes list, or in other words, when there are no
more barcodes pending to scan, or when all the scanned barcodes are in green or yellow, a
confirmation message will appear to confirm that this replacement should be made. Then yellow
barcodes on the right will be replaced by new scanned barcodes on the left.

If Send Order to Rework or Abort Scan and Exit button is pressed, or if replacement of barcodes
is not accepted, the process will be aborted. This means that when calling again this script for
this harness, the original list will appear and none of those items will be green, so all barcodes
will be expected to be scanned again.

© EMDEP 2024 Page 48

Emdep KSK Client / User’s guide

DISPATCH STATIONS

© EMDEP 2024 Page 49

Emdep KSK Client / User’s guide

Dispatch station flow

These stations are usually placed at the end of the production lines and are designed to inspect
and verify the finished goods before to send it to expedition.

Also, in these stations, the module verification is performed when a module never tested is
inspected for the first time in the station, unless there is a verification station.

The following schema shows a basic flow for this kind of stations:

The dispatch stations are implemented as a dedicated software, so the Emdep Wintestem™ is
not needed for the standard stations. In case that a different flow should be implemented, a
specific process can be created using Emdep Wintestem™ and interacting with different KSK
modules through scripts.

Module validation
When a harness is processed in dispatch station and contains modules not validated, the
behavior is different if the layout contains module validation station(s) defined (PPAP) or not.

© EMDEP 2024 Page 50

Emdep KSK Client / User’s guide

Module validation with PPAP stations

The harness will be automatically transferred to the validation station, closing the current stage
as NOK, unless a Conditional Validation rule has been defined for this QLevel and current line is
not included on any rule for this QLevel (see KSK-Studio Manual) .
Also, if a QLevel doesn’t start with letter Q, then it is not considered a QLevel, but an ELevel
instead. Modules that have ELevels instead of QLevels are considered to be a prototype and,
thus, it is not being sent to validation station, meaning that validation for these modules will be
skipped. This also includes the modules that has no QLevel (empty QLevel).
This mode uses the synchronization mechanism with production system (SAP or other) through
Emdep KSK Synchronization Service, do for each validated module (in PPAP station) a validation
signal will be sent to production system.

Module validation without PPAP

The harness composition (modules) will be shown in the screen, highlighting all non-validated
modules. When the harness is closed as OK in the dispatch station, all non-validated modules
will be set as validated.
This mode doesn’t use the synchronization mechanism with production system (SAP or other)
through Emdep KSK Synchronization Service.

Print Electrical label

Since version 3.37.0, it is possible to configure Dispatch Station to print electrical labels. If this is
the case, the label will be printed after user pressed OK button, and after having printed it, it
will be necessary to scan the label to check that printing was correct. The stage will not be closed
as OK until scanning the label has been successful.

Creating a dispatch station

To create a new dispatch station in an existing line, follow these steps:

1. Open the Layout designer from Emdep KSK Studio and create the dispatch station in the
desired line.

2. Once the station has been created in the KSK project, the Emdep KSK Client software
will be installed on the computer corresponding to the new validation station.

3. From the Windows Start menu, select Start → Emdep KSK → Utilities → Configure
dispatch terminal. The settings dialogue will be shown.

© EMDEP 2024 Page 51

Emdep KSK Client / User’s guide

4. Input all KSK connection settings and press Test connection button.

5. Specify the KSK station identification data (KSK project, line and station).

6. Select the user interface language for the operator’s screens (the settings dialogue is
only available in English).

7. Select the Configuration tab page.

If the computer has more than one screen, and a specific screen has to be used, check the “Use
specific screen” check box, and select the desired screen.

© EMDEP 2024 Page 52

Emdep KSK Client / User’s guide

8. Select the rework mode:

• Allow repair defects in the station before sending to rework: if this option is
selected, the operator could set reported defects as repaired before to send the
harness to a rework station. If all defects are set to repaired, the harness is not
sent to a rework station and the validation screen (with all modules pending to
be validated) will be shown again.

If this option is selected, the components re-scanning can be enabled to allow

the operators to scan the barcode of all replaced components.

• Send to rework without repair defects in current station: If this option is

selected, the operator is not able to set defects to repaired and the harness will
be sent to a rework station directly.

• Print specific label for rework station: If this option is selected, a label will
be printed when the harness is sent to rework from this station.

• Scan printed label: If this option is selected, the printed label will have to be
scanned after having printed it, to ensure it has been printed well.

• Print specific label with modules: If this option is selected, a label will be
printed when sending the harness to validation station. This label will contain
the modules to be validated, and maybe also the others. This can be
configured via Label settings.

• Auto Generate Module Validation Report: If this option is selected, a PDF

file will be generated with the list of modules and its status. This file will be
generated in the folder configured in Report Path field.

© EMDEP 2024 Page 53

Emdep KSK Client / User’s guide

9. Configure and select a rework label. The rework label is printed before to send the
harness to a rework station. Lear how to define a label in Creating and configuring labels
section.

10. Chose whether this dispatch station should use RFID tags

See Configuring RFID section for more details.

11. Since version 3.25.0. Combined Dispatch stations can be defined. Please see Combined
Dispatch section.

12. In the Logging tab page, the LOGs can be enabled. Detailed information is available in in
section Logging and diagnostics.

13. Press OK to save the current settings and start the application or Cancel to discard all
settings changed and stop executing the application.

© EMDEP 2024 Page 54

Emdep KSK Client / User’s guide

Configuring label settings

When clicking on “Label settings” button in “Order” or “Rework / Validation” tab, this screen
will appear:

On this screen, the list of configured labels appears. On the top there are three buttons to add
a new label configuration, to edit a current label configuration and to remove it.

When adding or editing a label configuration for rework or validation, this screen will appear:

© EMDEP 2024 Page 55

Emdep KSK Client / User’s guide

To create a label for sending the modules list to validation, check “Include module list in label” and also
“Distinguish between validated and non-validated modules”. A new “Modules” tab will appear:

Configure here the prefixes that the .prn file has for the part number (PN), revision (REV) and QLevel for
the validated, under validation, and non-validated modules, as shown in the picture above.

Variables in Electrical test labels

When adding or editing an electrical label configuration, the part to configure the variables will
not appear, but the following variables can be included in .PRN file:

@ORDER: This variable will contain the order without prefix. If a prefix is desired, just add it in
the PRN file. For example, if prefix A2B has to be added, write A2B@ORDER in the PRN file

@TESTTIME: Date/time when harness was closed at electrical station, in the format
yyyy/MM/dd HH:mm, e. g.: 2021/11/23 13:56.

© EMDEP 2024 Page 56

Emdep KSK Client / User’s guide

@MODULES: Will be replaced with the list of module part numbers, with no delimiter. IN case a
delimiter is desired, put it between claudators just after @MODULES. For example, if MODULES
have to be separated by a semi-colon, write @MODULES{;}

It is also possible to specify a space as a separator writing @MODULES{ } or adding several

characters as a separator, for example @MODULES{***}

@TESTOPERATOR: The code of the last operator who did the last test in ECB station.

Those parameters can appear also in Scan Electrical label format field in settings screen, to
specify what should be scanned. In the following example, the format of the label to be scanned
is specified to be “A@ORDERB @TESTTIME”, which means that the scanned code must contain
the order with an A prefix and a B suffix, then a space, and then the test time (the date and time
when harness has been tested, in format yyyy/MM/dd HH:mm):

Some Additional Fields are available to print in Electrical Label at Dispatch client station, these
are not include in setting form but user can configure in PRN file.

@PRODUCTHIERARCHY: This variable will contain the order product hierarchy

@SYDATUM: This variable will contain the order system date

@DRAWINGNO: This variable will contain the order drawing number

@DRAWINGINDEX This variable will contain the order drawing index

@TESTDATA: This variable will contain the order test data

@JINUM: This variable will contain the order JINUM

@POSID This variable will contain the order POSID.

@ALERT01, @ALERT02… This variable will contain the alerts concerning the modules related to
a harness. There are 3 types of alerts:

- Concern: A Harness may have one or no Concern. If there is an assigned concern it will
be shown in the @ALERT01, otherwise this variable will be empty. In the case of an
attempt to assign more than one Concern, an error appears in the QSSE file.
- Alert: The alerts are related to the concerns. They may or may not appear. If they do
appear, concern(alert) will be displayed in the @ALERT01 variable. In case the alert is
not defined, only the concern will be shown without the parenthesis.
- Other alerts: These are harness-related alerts independent of the concern. The script
"KSK_Alerts_Get.vbs" shows how to retrieve 9 such alerts.

@TESTTIME This variable will contain the date of the test.

it is allowed to print the partial part of any field declared above except @TESTOPERATOR,
@MODULES, @TESTOPERATOR,@ALERT01, @ALERT02, @ALERT03… For partial part printing
user need to just add starting position and number of characters delimited by ‘#’ in the PRN file.

© EMDEP 2024 Page 57

Emdep KSK Client / User’s guide

For example,
@ORDER#1#8 => if order is 12345678I123, only 12345678 will be printed
@SYDATUM#5#2 => if System Date is 20220608, only 06 will be printed
@SYDATUM#5 => if System Date is 20220608, all characters starting at position 5 will be printed (0608)

The @TESTTIME variable must be followed by the format in which the date is to be displayed.
@TESTTIME{yyyy/MM/dd HH:mm:ss}
Will return a date and time like this: 2022/10/04 07:14:49

Format specifier Description Examples

2009-06-01T13:45:30 -> 1
The day of the month, from 1 through 31.
"d"
2009-06-15T13:45:30 -> 15
The day of the month, from 01 through 31. 2009-06-01T13:45:30 -> 01
"dd"
2009-06-15T13:45:30 -> 15
2009-06-15T13:45:30 -> Mon (en-US)
The abbreviated name of the day of the week.
"ddd" 2009-06-15T13:45:30 -> Пн (ru-RU)

2009-06-15T13:45:30 -> lun. (fr-FR)

2009-06-15T13:45:30 -> Monday (en-US)

The full name of the day of the week.

"dddd" 2009-06-15T13:45:30 -> понедельник (ru-RU)

2009-06-15T13:45:30 -> lundi (fr-FR)

2009-06-15T01:45:30 -> 1
The hour, using a 12-hour clock from 1 to 12.
"h"
2009-06-15T13:45:30 -> 1
2009-06-15T01:45:30 -> 01
The hour, using a 12-hour clock from 01 to 12.
"hh"
2009-06-15T13:45:30 -> 01
2009-06-15T01:45:30 -> 1
The hour, using a 24-hour clock from 0 to 23.
"H"
2009-06-15T13:45:30 -> 13
2009-06-15T01:45:30 -> 01
The hour, using a 24-hour clock from 00 to 23.
"HH"
2009-06-15T13:45:30 -> 13
2009-06-15T01:09:30 -> 9
The minute, from 0 through 59.
"m"
2009-06-15T13:29:30 -> 29
2009-06-15T01:09:30 -> 09
The minute, from 00 through 59.
"mm"
2009-06-15T01:45:30 -> 45
The month, from 1 through 12.
"M" 2009-06-15T13:45:30 -> 6

The month, from 01 through 12.

"MM" 2009-06-15T13:45:30 -> 06

The abbreviated name of the month. 2009-06-15T13:45:30 -> Jun (en-US)

"MMM"
2009-06-15T13:45:30 -> juin (fr-FR)

© EMDEP 2024 Page 58

Emdep KSK Client / User’s guide

Format specifier Description Examples

2009-06-15T13:45:30 -> Jun (zu-ZA)

2009-06-15T13:45:30 -> June (en-US)
The full name of the month.
"MMMM" 2009-06-15T13:45:30 -> juni (da-DK)

2009-06-15T13:45:30 -> uJuni (zu-ZA)

The second, from 0 through 59.
"s" 2009-06-15T13:45:09 -> 9

The second, from 00 through 59.

"ss" 2009-06-15T13:45:09 -> 09

0001-01-01T00:00:00 -> 1

0900-01-01T00:00:00 -> 0
The year, from 0 to 99.
"y" 1900-01-01T00:00:00 -> 0

2009-06-15T13:45:30 -> 9

2019-06-15T13:45:30 -> 19
0001-01-01T00:00:00 -> 01

0900-01-01T00:00:00 -> 00
The year, from 00 to 99.
"yy"
1900-01-01T00:00:00 -> 00

2019-06-15T13:45:30 -> 19
0001-01-01T00:00:00 -> 001

The year, with a minimum of three digits. 0900-01-01T00:00:00 -> 900

"yyy"
1900-01-01T00:00:00 -> 1900

2009-06-15T13:45:30 -> 2009

0001-01-01T00:00:00 -> 0001

The year as a four-digit number. 0900-01-01T00:00:00 -> 0900

"yyyy"
1900-01-01T00:00:00 -> 1900

2009-06-15T13:45:30 -> 2009

The year as a five-digit number. 0001-01-01T00:00:00 -> 00001
"yyyyy"
2009-06-15T13:45:30 -> 02009
Defines the following character as a custom
format specifier.
% 2009-06-15T13:45:30 (%h) -> 1

© EMDEP 2024 Page 59

Emdep KSK Client / User’s guide

© EMDEP 2024 Page 60

Emdep KSK Client / User’s guide

Configuring RFID
Since version 3.18, Dispatch stations allow to detect and write information on RFID tags. From
this version on, a new tab RFID is available to configure several parameters:

• Use RFID tags: If this option is not checked, RFID tags will not be used on this station
and all the rest of RFID options become disabled.

• COM Port: Select the COM port where RFID reader/writer is connected to. All available
COM ports on the computer will appear on this list.

• Max write attempts: Select the maximum number of attempts to be made if writing a
RFID tag fails.

• Tags to remember: It is not possible to use a tag that has recently been dispatched
successfully on this station. This number indicates the number of tags to remember so
that if scanned tag is one of the last remembered tags, an error message will appear.

• RFID tag options: These options are intended to configure which information will be
stored on the RFID tag. An example is provided which changes automatically depending
on the settings.

© EMDEP 2024 Page 61

Emdep KSK Client / User’s guide

As it can be seen on the example, what is written in RFID tag is the order number followed by a
space, followed by supplier number + date (in yyyyMMdd format) + Factory + CarLine. However,
since version 3.35.0, if order number is 18 characters in length, instead of this format, only the
DMC_Code and POSID will be written on RFID tag.

• Minimum order length to write DMC code: Since version 3.36.0, the content to be
written on RFID tag can be different depending on the length of the order. If length of
the order is large enough (if it is minimum the value of this parameter), then DMC code
and POSID will be written in the tag, instead of writing the first digits of the order
followed by the defined static parameters.

o Setting this parameter to 0 will mean that system will always write DMC code
and POSID and never the order number followed by static parameters.

o Setting this parameter to a high value which is larger than any order, such as 99,
will mean that system will always write the order number followed by the
defined static parameters, i. e., a code as the one shown in the example will be
written.

o Setting this parameter to an intermediate value, such as 18, will mean that
system will write POSID code + POSID for any order which is 18 or more
characters in length will, but if order length is less than 18, then the code that
will be written in RFID tag will be as the one in the example.

NOTE: RFID can be configured to run without device, using the simulator mode. This mode is
only allowed for Emdep staff and more information can be found inside Manuals/RFID folder.

Configure the terminal from the command line

The Emdep KSK Dispatch Terminal executable file Emdep.KSK.Terminal.Dispatch.exe
accepts the parameter -setup to force to show the station settings before to start the
application:

> Emdep.KSK.Terminal.Dispatch.exe -setup

© EMDEP 2024 Page 62

Emdep KSK Client / User’s guide

Combined Dispatch Station

Since KSK Client 3.25.0, Dispatch stations can be combined. A combined dispatch station means
that dispatch station has a relationship with another dispatch station.

From this point of view, there are 3 types of dispatch station:

- Standalone Dispatch Station (or “normal” Dispatch Station)

This station is not related to any other station and works as dispatch stations
from previous versions to 3.25.0.

- Primary Combined Dispatch Station

This station has a dispatch station from another line. The station will ask not only
for the harness of current line, but also for a second harness that belongs to the
line where related secondary dispatch station belongs to.

- Secondary Combined Dispatch Station

This station is not a real station, meaning that it does not exist physically, but
must be added in the layout of the line to maintain the concept of the flow.
A relationship with another dispatch station is defined. That station will work as
primary station and will ask the harness from this secondary station.
Dispatch client application cannot be started for secondary Combined Dispatch
Station, except for configuring the relationship with the primary station.

© EMDEP 2024 Page 63

Emdep KSK Client / User’s guide

Configuring Combined Dispatch Stations

Since version 1.45.0 of KSK Studio, relationship between dispatch stations can be defined on KSK
Studio by editing dispatch station properties. Please see “Managing Stations” sections in KSK
Studio manual for more details. Configuring this relationship using KSK Studio is highly
recommended. That means that only parameters “length of line suffix” and “QR folder” will
remain to be configured for primary station.

When configuring settings for dispatch terminal, there is a tab Combined Dispatch to set
properties related to combined dispatch station:

When checkbox “Use combined Dispatch” is unchecked, all the rest of the options on this tab
will be disabled and this station will work as a non combined station (also called standalone
dispatch station or “normal” dispatch station).

When checkbox “Use combined Dispatch” is checked, this station is a combined station. It can
be Primary station (the one that will handle the two harnesses) or secondary station (the one
that does not exist physically).

As secondary stations are not a physical station, starting of a secondary station is not allowed.
If you try to start application using configuration of a secondary station, this message will
appear:

© EMDEP 2024 Page 64

Emdep KSK Client / User’s guide

If this is a mistake, please remove settings.xml file and run application again in order to force
the settings window to appear again and restart the station configuration.

To create a combined dispatch station, a relationship must be defined from secondary station
to primary station. This means that secondary station must be defined on first tab (KSK tab) and
then, in Combined Dispatch, “Secondary station” option has to be selected. After that, the
Related Primary Station has to be selected using the combo box. The following picture depicts
this situation:

After this change, the station that is selected on “Related Primary Station” becomes a primary
station. That means that when entering on the configuration for that station, a screen like this
will appear:

© EMDEP 2024 Page 65

Emdep KSK Client / User’s guide

Parameter length of suffix allows to configure which part of the order number must not be
considered when making the matching between the two harnesses scanned in the primary
combined dispatch station.

© EMDEP 2024 Page 66

Emdep KSK Client / User’s guide

Configuring Behavior options

Since version 3.36.0, a tab called Behavior options is also accessible:

As it can be seen, those options can be configured:

• Scan ECB labels: When this option is enabled, after montage plan has been scanned, the
ECB label will be requested. This label will contain only the KSK Order, with no prefix and
no suffix. In case the harness is combined, the ECB label for every harness that
compounds the combined harness will be requested. For example, if a combined
harness is compound by a main harness and an audio harness, both labels for main and
audio will be requested. If this is the case, those labels can be scanned in any order.

• Require SUPERVISOR PASSWORD when scanning non-combined harness on combined

line: When this parameter is enabled and line is combined and a montage plan of a
single (non-combined) order is scanned, the station is blocked until supervisor password
is scanned. RFID tag will not be written for those single harnesses.

• ACCEPT harnesses from Harness ATTACHMENT stations in other lines: Usually,

harnesses from another lines are not accepted. However, if this option is enabled,
harnesses that are prepared to be scanned in a station of type “Harness Attachment”
will be accepted.

© EMDEP 2024 Page 67

Emdep KSK Client / User’s guide

Flow of Primary Combined Dispatch Station

In a Primary combined dispatch station, two harnesses are scanned instead of one. First harness
is the harness that belongs to the line where this dispatch station belongs to. Second harness is
the one that belongs to the line where the related secondary station belongs to. These two
harnesses must contain the same order number (without taking into account the last characters
defined in parameter “Length of the suffix” in “Combined Dispatch” tab).

When using combined dispatch station, if something is wrong, station will be blocked until a
supervisor code is scanned.

When everything is ok, application will ask to operator if harnesses are both physically ok. If so,
then close stage will be performed for both harnesses and two QR codes will be shown in the
screen, if parameter “Show QR Codes” in settings screen is checked:

© EMDEP 2024 Page 68

Emdep KSK Client / User’s guide

This image will be also stored in the folder defined by “QR folder” parameter. The name of this
file will be <order_number>.png, where <order_number> is the order number of both
harnesses, without considering the line suffix.

© EMDEP 2024 Page 69

Emdep KSK Client / User’s guide

MOBY-D REPACKING
STATION

© EMDEP 2024 Page 70

Emdep KSK Client / User’s guide

Moby-D Repacking station is a kind of station that allows to read an RFID tag from a Moby-D
device, scan an order, check that a part of this data matches with data stored in TestData field,
and finally writes the order number on RFID tag in Moby-D device.

Flow of Moby-D device

Creating a Moby-D Repacking station

To create a new Moby-D Repacking station in an existing line, follow these steps:

1. Open the Layout designer from Emdep KSK Studio and create the Moby-D Repacking
station in the desired line.

2. Once the station has been created in the KSK project, the Emdep KSK Client software
will be installed on the computer corresponding to the new Moby-D Repacking station.

3. From the Windows Start menu, select Start → Emdep KSK → Configure Moby-D
Repacking terminal. The settings dialogue will be shown.

© EMDEP 2024 Page 71

Emdep KSK Client / User’s guide

Configuration of Moby-D Repacking station

Once starting Moby-D Repacking station for the first time, settings dialog will be shown. Another
way to start it is going to Start → Emdep KSK → Configure Moby-D Repacking terminal.

Settings screen contains 3 tabs: KSK, Configuration and Logging.

KSK and Logging contains same functionality as the rest of station types: KSK is meant to
configure the connection to database and the type of the station. Logging is meant to configure
options for logging on file and/or windows events system. Please refer to Dispatch configuration
to learn how to configure those parts.

In configuration tab, there are 3 subtabs: RFID, Matching and Others.

Configure RFID parameters: set the COM port in the computer where MobyD device is
connected to, and other parameters described also in Dispatch configuration guide.

© EMDEP 2024 Page 72

Emdep KSK Client / User’s guide

Use Matching tab to configure how matching should be performed. Matching is performed
between the RFID tag read from MobyD device, and between contents in TestData field for the
scanned order. This TestData field is filled by QSS1 Orders Importer service.

By default, all RFID tag and all TestData will be considered for the matching. However, it can be
defined to match only a part of them.

Use parameters in RFID Read Tag Options to define which characters on RFID tag read from
Moby-D device should be considered to make the matching. Those values will be 1-1024
meaning that all 1024 characters in Tag will be considered: from first character (character 1).

Use parameters in RFID Database Matching to configure which part of the TestData field in
database will be used to match with the RFID tag read (or the specified part of it). By default, all
100 characters of TestData field, starting by first one, will be considered, meaning all the content
is considered.

Parameter number of characters is synched with Ending position, meaning that when one of
them is modified, the other will be modified also automatically.

© EMDEP 2024 Page 73

Emdep KSK Client / User’s guide

Finally, the tab “Others” contains some other configurations such as on which screen should
application be run (in case that more than one screen is connected to the system.

Operators guide
Once inside application, after performing login, this screen will appear:

As it can be seen, the screen has a text box on the upper part to be able to scan an order,
however, scanning an order will not be possible until a tag in Moby-D device has been read.

In the central part, a list of the tasks that are being performed by the system appears. Currently,
the system is waiting to read a tag from Moby-D device.

Moby-D Tag is read automatically when a tag is on Moby-D device. The system will read its
contents and the following screen will appear:

© EMDEP 2024 Page 74

Emdep KSK Client / User’s guide

As it can be seen, now the Scan Order area has been enabled, and the system is waiting to scan
a harness order (or type it manually using the keyboard).

If an error occurs, the error message will appear on the tasks list. In this way, all the history of
the actions that application is performing will appear on the list in the central area.

Each task on the list appears with an icon and a text.

The text describes the action, while the icon describes if the action is in progress, if the action is
being performed, or if it is an error message:

Icon Meaning

The action described in the text is being performed (it is not done yet)

The action described in the text has been performed successfully

An error has occurred. The text contains the description of the error.

© EMDEP 2024 Page 75

Emdep KSK Client / User’s guide

In this example, a Moby-D tag has been read successfully. Then an order has been successfully
scanned, but while trying to open stage for that order, an error occurred because that order
has already been processed in this station.

On the bottom right area, there are two buttons: Logout button and cancel button. Pressing
cancel button will clear the list of tasks and will start again the process. Pressing the Logout
button will go back to login screen. When all the process is completed successfully, the cancel
button disappears and it appears an ok button instead:

Button Meaning

Logout button: Cancels current task, closes current screen and goes to Login
screen.

Cancel button: Cancels current tasks, clears the list of tasks and restart the
process, trying to read the tag in Moby-D, etc…

Ok button: Acknowledge of process completely successful. Clears the list and

starts the process, trying to read next tag in Moby-D, etc…

© EMDEP 2024 Page 76

Emdep KSK Client / User’s guide

In the following example, all tasks have been completed successfully:

© EMDEP 2024 Page 77

Emdep KSK Client / User’s guide

If code on RFID tag does not match with TestData field, then supervisor code will be required:

After having entered supervisor code, station will be unblocked and the process will be
restarted, meaning that a new RFID tag will be read, then a new order code to be scanned will
be requested, etc…

© EMDEP 2024 Page 78

Emdep KSK Client / User’s guide

MODULE VALIDATION
STATIONS (PPAP)

© EMDEP 2024 Page 79

Emdep KSK Client / User’s guide

The module validation stations (also called PPAP) are placed next to a dispatch station and are
designed to perform the module validation when a module was never tested for a specific
QLevel.

The following schema shows a basic flow for this kind of stations:

Validation stations are implemented as dedicated software, so the Emdep Wintestem™ is not
needed for this kind of stations.

When a harness is at Dispatch station, the system examines if any of their modules have to be
validated. A module has to be validated if it has not already been tested for the current
combination of part number, revision and Q-Level (so, if it is a new module).

If a harness has all their modules validated, it will continue the normal flow in dispatch station
(setting it to TESTED after being processed in dispatch station).

If a harness has some modules that are not still validated then the harness will be sent (queued)
to validation station, unless all these modules have been already sent to validation station by
other harness (so they are in the queue and they are already waiting to be validated).

If a harness has some modules that are not still validated but all these modules are on the queue
to be validated, then the harness will continue its flow normally (so it will be processed in
dispatch station as if their modules were all validated). This is an optimistic approach that
improves the production speed and involves no problems if the explained flow is followed.

When the harness is at validation station, it can finalize as OK or NOK. If it is OK, it returns to
dispatch. If it is NOK, then it goes to an available rework station.

© EMDEP 2024 Page 80

Emdep KSK Client / User’s guide

If a harness is sent to rework from validation, a CSV file will be generated and shown with all the
affected harnesses, because all those harnesses might well have to be discarded, even if they
passed dispatched step (but they can be discarded as they are still at the factory).

The CSV file contains all harnesses including the non-validated modules and the list is sorted
with the following premises:

1. Harnesses in TESTED status (finished)

2. Harnesses in INPROCESS status
3. Harnesses in WAITING status
4. The rest of affected harnesses

Creating a validation station

In validation terminal there is no button in the user interface to prevent operators from
accessing the configuration. There are multiple methods to access to the terminal settings:

• The first time the terminal is executed, the configuration dialog will appear directly.
• Accessing to Emdep KSK → Utilities → Configure validation terminal in the Windows
Start menu.
• From the command line, executing the application and adding the -setup parameter:
Emdep.KSK.Terminal.Validation.exe -setup

To configure a KSK validation station the following steps should be performed:

1. Open the Layout designer from Emdep KSK Studio and create the module validation
station in the desired line.

© EMDEP 2024 Page 81

Emdep KSK Client / User’s guide

Each validation station is assigned to a line, so it is not possible to share a single

validation station between multiple lines.

2. Once the station has been created in the KSK project, the Emdep KSK Client software
will be installed on the computer corresponding to the new validation station.

3. From the Windows Start menu, select Start → Emdep KSK → Utilities → Configure
validation terminal. The settings dialogue will be shown.

4. Input all KSK connection settings and press Test connection button.

5. Specify the KSK station identification data (KSK project, line and station).

6. Select the user interface language for the operator’s screens (the settings dialogue is
only available in English).

7. Select the Configuration tab page.

© EMDEP 2024 Page 82

Emdep KSK Client / User’s guide

8. Select the rework mode:

• Allow repair defects in the station before sending to rework: if this option is
selected, the operator could set reported defects as repaired before to send the
harness to a rework station. If all defects are set to repaired, the harness is not
sent to a rework station and the validation screen (with all modules pending to
be validated) will be shown again.

If this option is selected, the components re-scanning can be enabled to allow

the operators to scan the barcode of all replaced components.

• Send to rework without repairing defects in current station: If this option is

selected, the operator is not able to set defects to repaired and the harness will
be sent to a rework station directly.

9. Configure and select a rework label. The rework label is printed before to send the
harness to a rework station. Lear how to define labels in Creating and configuring labels
section.

10. Select the folder where the harnesses with modules pending to be validated report will
be generated. Also, the report base name will be provided.

To be able to automatically open the generated reports in the station, EMDEP

recommend installing LibreOffice Calc, Microsoft Excel or a similar software.

11. If the new station has installed an EMDEP keyboard, the associated actions Exit, Login
and Cancel can be assigned to a specific key. Select None to disable the key association.

12. In the Logging tab page, the LOGs can be enabled. Detailed information is available in in
section Logging and diagnostics.

© EMDEP 2024 Page 83

Emdep KSK Client / User’s guide

13. Press OK to save the current settings and start the application or Cancel to discard all
settings changed and stop executing the application.

Configure the Dispatch stations to send orders to validation

If the dispatch station in KSK project are using the Emdep KSK Dispatch Terminal software, this
step is not necessary, and no other task is needed. If the dispatch station is created using an
Emdep Wintestem™ process, it is necessary to check/modify this process to be sure that the
orders with modules non-validated will be sent to PPAP station.

The dispatch station processes should be checked to be sure that the

KSK_Modules_CheckPPAP.vbs script is called after the stage is opened (calling the
KSK_Stage_Open.vbs script). The following sample program shows a basic dispatch station
process (simplified for better understanding):

Program
'Initialize the KSK settings for the station
Run("C:\MyKSKProject\KSK_Settings.vbs")
'User code input
 Input(@Str09, Password:Yes, Keyboard) ← Label USR_SCAN
'Check user code
Run("C:\MyKSKProject\KSK_User_IsValid.vbs")
If (@Num01 <> 1)
'Show error
Show (X)
Goto "USR_SCAN"
'Order scanning
 Input(@Str10, Password:No, Scanner) ← Label HNS_SCAN
'Open the stage in current dispatch station
Run("C:\MyKSKProject\KSK_Stage_Open.vbs")
If (@Num01 <> 1)
'Show error
Show (X)
Goto "HNS_SCAN"
'Check if order should be validated or not
Run("C:\MyKSKProject\KSK_Modules_CheckPPAP.vbs")
If (@Num01 = 0)
'Show error in @Str01
Show (X)
Goto "HNS_SCAN"
If (@Num01 = 1)
'Inform operator that the harness has been sent to validation station
Show (X)
Goto "HNS_SCAN"
'-----------------------------------------------
' Current behaviour
'-----------------------------------------------
'Close the stage in current dispatch station as OK
Run("C:\MyKSKProject\KSK_Stage_Close_OK.vbs")
If (@Num01 <> 1)
'Show error
Show (X)
Goto "HNS_SCAN"
'Goto main menu
Goto "HNS_SCAN"

Emdep Wintestem™ process colored for a better comprension

© EMDEP 2024 Page 84

Emdep KSK Client / User’s guide

The script KSK_Modules_CheckPPAP.vbs returns the following values:

WTT Variable Value Description

The order has been sent to module validation station.
1 The current dispatch stage has been closed as NOK and the order is
now waiting in PPAP station.
@Num01
The order shouldn’t be validated.
2
The dispatch flow continues normally.
0 Error occurred. The description can be accessed from @Str01.

User’s guide
1. Start the application Validation terminal from the Windows Start menu. The Emdep KSK
Client software will create the Emdep KSK group in that menu.

If this is the first time the application is executed, the configuration dialogue will be
shown. See how to configure the station in Creating a validation station section.
2. After the application is started, the login screen will be shown.

Scan or type the user’s private code.

• To close the application, press the Login button in the bottom bar.
3. After the log-in operation, the scanning order dialogue will be shown.

© EMDEP 2024 Page 85

Emdep KSK Client / User’s guide

4. Scan or type the order number.

• To come back to log-in screen, press the Login button in the top bar.
• To close the application, press the Exit button in the bottom bar.
5. If the scanned order is queued into the validation station, the harness composition
screen will be shown with all modules contained. The non-validated modules will be
shown highlighted in red. Modules that are being under validation will be shown
highlighted in orange. Finally, Modules that are already validated will be shown
highlighted in green.

Check all highlighted modules in the scanned harness.

• If the modules are correct, press OK button from left panel.
After that, all modules will be set to validated and the harness is automatically sent
to the dispatch station again (same origin station).

© EMDEP 2024 Page 86

Emdep KSK Client / User’s guide

• If not all modules are correct, and the harness needs to be repaired/reworked, press
NOK button from left panel.
When the NOK button is pressed, a report is generated with all harnesses containing
one or more non-validated modules listed in the current order. After that, the
rework standard flow is called (the rework operation details can be found in
Reworking operations section).
• To cancel the current validation and back to the order scanning screen, press the
Cancel / Back button in the bottom bar.
6. After validation screen, the order scanning screen will be shown again (step 3).

© EMDEP 2024 Page 87

Emdep KSK Client / User’s guide

SPARE MODULE
VALIDATION STATION

© EMDEP 2024 Page 88

Emdep KSK Client / User’s guide

The spare modules validation station (also called PPAP client for spare module) goal is to validate
individual modules that are not in a mass production harness. These modules are intended for
having replacements or for making tests aside of production.

The following schema shows a basic flow for this kind of stations:

Spare Module Validation station software is implemented as a standalone software, meaning

that Emdep Wintestem™ is not used for this kind of stations.

After logged in to this station, the scanning screen appears.

The scanned barcode needs to contain the module Part Number, the index / revision and the
QLevel. These 3 barcode parts will be at fixed positions and will have a specific length, which will
be defined in settings screen.

If the scanned module exists, a special harness containing only this module will be created in
the database, unless this special harness already exists. The location for this harness will always
be at spare module validation station, meaning that this harness can only be on this station.

If the module is validated, a label will be printed.

© EMDEP 2024 Page 89

Emdep KSK Client / User’s guide

If the module is not validated, the validation screen appears. If user press OK button the module
will be validated and the label will be printed. If user press NOK button, application returns to
scanning screen to allow user to scan another spare module.

Creating a spare module validation station

In validation terminal there is no button in the user interface to prevent operators from
accessing the configuration. There are multiple methods to access to the terminal settings:

• The first time the terminal is executed, the configuration dialog will appear directly.
• Accessing to Emdep KSK → Utilities → Configure Spare Module terminal in the Windows
Start menu.
• From the command line, executing the application and adding the -setup parameter:
Emdep.KSK.Terminal.SpareModuleValidation.exe –setup

In the settings screen, follow these steps:

1. Input all KSK connection settings and press Test connection button.

2. Once database connection is correct, select the project

3. When selecting a project, if spare module station does not exist, it will be created
automatically in a special line called “out of line” which will be also created if it doesn’t
exist. This special line will not be shown in KSK Studio.

© EMDEP 2024 Page 90

Emdep KSK Client / User’s guide

4. Select the user interface language for the operator’s screens (the settings dialogue is
only available in English).

5. Select the Configuration tab page.

6. Select the starting and end positions in the barcode for module part number, QLevel
and revision.

These positions refer to the position in the scanned bar code, starting from 1. For
example, if you want to scan a barcode like this:

A177906052_Q003_01

You should define Part number from position 1 to position 10, QLevel from position 12
to position 15, and revision from position 17 to position 18.

7. Configure the separator character. This character will be used for the order of the special
harness associated with the spare module. This order will contain module part number,
QLevel and revision, separated by this character. Normally a hyphen will be used.

8. Configure and select a label to be printed. The label is printed whenever a validated
module is scanned or whenever a module is validated on this station. Learn how to
define labels in Creating and configuring labels section.

9. If computer has more than one screen and a specific screen must be used for this
application, check the “User specific screen” option and select the “Screen number”
accordingly.

10. If the new station has installed an EMDEP keyboard, the associated actions Exit, Login
and Cancel can be assigned to a specific key by using “Shortcuts” tab. Select None to
disable the key association.

© EMDEP 2024 Page 91

Emdep KSK Client / User’s guide

11. In the Logging tab page, the LOGs can be enabled. Detailed information is available in in
section Logging and diagnostics.

12. Press OK to save the current settings and start the application or Cancel to discard all
settings changed and stop executing the application.

© EMDEP 2024 Page 92

Emdep KSK Client / User’s guide

User’s guide
7. Start the application Spare Module Validation terminal.

If this is the first time the application is executed, the configuration dialogue will be
shown. See how to configure the station in Creating a spare module validation station
section.
8. After the application is started, the login screen will be shown.

Scan or type the user’s private code.

• To close the application, press the Login button in the bottom bar.

© EMDEP 2024 Page 93

Emdep KSK Client / User’s guide

9. After the log-in operation, the scanning order dialogue will be shown.

10. Scan or type the order number.

• To come back to log-in screen, press the Login button in the top bar.
• To close the application, press the Exit button in the bottom bar.

© EMDEP 2024 Page 94

Emdep KSK Client / User’s guide

11. If the scanned code matches a validated module, according to the defined positions in
settings to get the module fields, a label will be printed. The printing will take the
configured prn file and will replace the following variables to the following values:
@CUSTOMER_MATERIAL is replaced by the scanned part number
@QLEVEL is replaced by the scanned QLevel
@INDEX is replaced by the scanned revision
@YEAR is replaced by current year
@MONTH is replaced by current month
@DAY is replaced by current day
@HOUR is replaced by current hour
@MINUTE is replaced by current minute
@SECOND is replaced by current second

If the scanned code matches a module but this module is not validated, the validation
screen will appear:

• If the module is correct, press OK button from left panel.

After that, the module will be set to validated state and the label will be printed.
• If the module is not correct, press NOK button from left panel. Module will remain
on its non-validated state and scanning screen will appear to scan another module.
• To cancel the current validation and go back to the scanning screen, press the Cancel
/ Back button in the bottom bar.

© EMDEP 2024 Page 95

Emdep KSK Client / User’s guide

REWORK STATIONS

© EMDEP 2024 Page 96

Emdep KSK Client / User’s guide

Rework Stations
Rework stations are a special type of stations where all goods with detected defects can be
repaired (or discarded) out of the normal production line. The typical flow for this kind of
stations is shown in the next schema.

Since version 1.87.2, a new way of working is introduced, in addition to the standard one.
Starting from this version, you can also choose the "Rework In - Out" mode of operation. When
configuring the Rework station in this mode, it will be required to have at least two computers
physically present, one configured in "Rework In" mode and the other in "Rework Out" mode.
The difference is that the computer in "Rework In" mode will be responsible for performing the
"open stage" and allowing the printing of reports related to the rework. The computer
configured as "Rework Out" does not perform the "open stage" but allows operations related to
changes in the status of incidents and sending the harness to the line by performing the relevant
"close stage."

When selecting the "Rework In-Out" mode of operation, it is necessary to have physically one
computer in "Rework - In" mode and another in "Rework - Out" mode. Below are two diagrams
to illustrate the flow in this new mode.

© EMDEP 2024 Page 97

Emdep KSK Client / User’s guide

The following schema defines the behaviour of the Rework – In:

The following schema defines de behavior of the Rework – Out:

The Emdep KSK Test Station installation package include the rework station application, so it is
not necessary to install additional software to use it.

Creating a rework station

In rework terminal there is no button in the user interface to prevent operators from accessing
the configuration. There are multiple methods to access to the terminal settings:

• The first time the terminal is executed, the configuration dialog will appear directly.
• Accessing to Emdep KSK → Utilities → Configure rework terminal in the Windows Start
menu.

© EMDEP 2024 Page 98

Emdep KSK Client / User’s guide

• From the command line, executing the application and adding the -setup parameter:
Emdep.KSK.Terminal.Rework.exe -setup

To configure a KSK rework terminal the following steps should be performed:

1. Access to the configuration dialogue by choosing one of the described methods in

previous section.

2. Set the KSK database Connection settings and press Test connection button.

3. Set the KSK station Identification settings (project, line and station name).

4. Select the user interface language for the operator’s screens (the settings dialogue is
only available in English).

© EMDEP 2024 Page 99

Emdep KSK Client / User’s guide

5. Select the Configuration tab page.

6. In field Prefix for labels, specify the rework labels prefix used by the KSK project. If the
field is left empty, no check will be made after the scanning of an order.

7. If the selected KSK project requires scanning assembled components and in the rework
station these components can be replaced, check Allow re-scan replaced assembled
components option.

8. If checked Allow rework comment, then when operator click on set as repaired button
rework comment form will be appearing.

9. If Checked Quality password to sent to scrap., then wherever operate will scrap harness
before that quality password required.

10. Specify the keyboard keys associated to actions login (change user), exit (close
application) and cancel (current operation). Select None from the drop-down list to
disable the shortcut for the selected action.

11. If in the configuratin of the station is enabled the option “Use Rework In – Out”, the area
of “Rework In – Out” in the Configuration tab page will be enabled. It is mandatory to
select “Rework In” or “Rework Out”.

12. In the Logging tab page, the LOGs can be enabled (for detailed information, see the
Logging and diagnostics section)

13. Press OK button to store the settings.

14. Start the Emdep KSK Rework Terminal to check if all settings are correct and the
terminal is working.

© EMDEP 2024 Page 100

Emdep KSK Client / User’s guide

User’s guide
1. Start the application Rework terminal from the Windows Start menu. The Emdep KSK
Client software will create the Emdep KSK group in that menu.

If this is the first time the application is executed, the configuration dialogue will be
shown. See how to configure the station in Creating a rework station section.
2. After the application is started, the login screen will be shown.

Scan or type the user’s private code.

• To close the application, press the Login button in the bottom bar.

© EMDEP 2024 Page 101

Emdep KSK Client / User’s guide

3. After the log-in operation, the scanning order dialogue will be shown.

4. Scan or type the order number.

• To come back to log-in screen, press the Login button in the bottom bar.
• To close the application, press the Exit button in the bottom bar.
5. If the scanned order is not queued into this rework station, an error message will appear.
A harness is queued in a rework station if it has been sent to rework, and at least one of
those situations occurs:
a. This harness belongs to he line where this rework station belong to.
b. Rework station is configured as shared to all lines
c. Since KSK Client 3.33.0: This harness belongs to one of the lines that is in the
Accepted list in Rework Station properties in KSK Studio.
6. If the scanned order is queued into the rework station, the harness defects will be shown
in the screen.

© EMDEP 2024 Page 102

Emdep KSK Client / User’s guide

At this point, the user should select one by one the defects to repair (by clicking over
the defect) and repair them. Each time the user selects a defect, all related information
should appear in the bottom panel.
Since version 1.14.0, a third button called “Send Harness to Clip Checker” could appear.
This button appears only if a station of type “Rework Clips Checker” is present on the
line. When pressing this button, a screen to select the subassemblies and clips stations
that contains the clips that must be reworked will appear:

After selecting some of the subassembly or clip stations (or all of them), “Send To
Harness Rework Clips Checker” button can be pressed and Harness will be sent to this
special station to rework clips.
Since version 3.43.1, it is possible to choose the SA stations to be processed before the
selected step.

© EMDEP 2024 Page 103

Emdep KSK Client / User’s guide

7. Select the desired defect in the list.

If the selected defect has been successfully repaired (and harness has not been sent to
rework clips checker station), press Set as repaired button from left panel.
Automatically, the defect is set to repaired and now appear with green background to
easily identify the defects repaired and not repaired.
Repeat the step 6 for all defects pending to repair.
8. When all defects have been processed:
• If all defects have been repaired (all with green background), press Finish (return to
line) button.
Depending on the current layout definition and the harness status, the harness will
be sent back to the defined step or the user will be asked to select the returning
step in the current line.
• If not all defects have been repaired and the pending defects cannot be repaired,
press Unrepairable (send to scrap) button to discard the harness and send to scrap.
When a harness is sent to scrap, a signal is sent to production system (SAP, LEPS;
etc.) in order to inform that the harness cannot be finished and to take the
appropriate measures (re-send order, etc.).
• To cancel the current validation and back to the order scanning screen, press the
Cancel / Back button in the bottom bar. The current order still in same status and
remains in rework station.
9. After step 7 the order scanning screen will be shown again (step 3).

© EMDEP 2024 Page 104

Emdep KSK Client / User’s guide

Using Rework Terminal from Wintestem

Since version 3.22.0, Rework Terminal can be launched from a Wintestem process by using script
KSK_Launch_ReworkTerminal.vbs.

Calling Rework Terminal from Wintestem instead of using it as a standalone application could
be useful for example to have Rework Terminal and Rework Clip Checker on same computer.
However, from the logical point of view, they are still two different stations and must be defined
as different stations on Layout Designer.

When using Rework Terminal, no matter if it is called as a standalone application or if it is called

from Wintestem, a button to send harness to Rework Clip Checker will appear if a rework Clip
Checker station is defined and visible from current line1.

When this button is pressed, a new screen will appear to select which clips should be reworked.
However, instead of selecting the clips one by one, the list of subassembly and clips stations will
appear. Selecting a station of the list means selecting its clips. More than one station can be
selected before pressing button “Send Harness To Rework Clips Checker”. The clips included on
each station is defined in TestData -> Clips plugin inside KSK Studio.

1
A rework clip checker station is visible in a line if it belongs to that line or if it has not the option “only
for this line” checked.

© EMDEP 2024 Page 105

Emdep KSK Client / User’s guide

When calling Terminal Rework from Wintestem, the caption of the button can be personalized.
This can be accomplished editing file KSK_Launch_ReworkTerminal.vbs. This way, instead of text
“Send to clip checker” we can have another text such as “Start clip checker”.

Before using KSK_Launch_Rework.vbs, it is important to configure settings.xml file properly on

Wintestem folder (which by default is C:\Emdep-2\exec), using the name of the rework station.
This file is generated the first time that standalone rework application is run and can be copied
from KSK Client installation folder (which normally is C:\Emdep-2\KSK\Client).

This script will return on wintestem variable @NUM02 a value to indicate how terminal was
finished. In case its value is 2, it means that harness has been sent to rework clip checker and
that script KSK_ReworkClipChecker_ShowAid.vbs can be called.

© EMDEP 2024 Page 106

Emdep KSK Client / User’s guide

REWORK CLIPS CHECKER

STATION

© EMDEP 2024 Page 107

Emdep KSK Client / User’s guide

Rework clips checker is a special station that will have two boards:

• One with all clips which are at inline clip checker

• Second one with all clips from all sub-assembly stations

Both boards are managed by a single test equipment with Wintestem and Multiuser Clips.

Apart from open and close stage scripts, one special script will be called from wintestem process
just before starting the multiuser clips test.

This script is called KSK_ReworkClipChecker_ShowAid.vbs. It has some internal parameters

that can be configured such as:

- allowCancel: When this option is true, a cancel button will be shown. When pressing
this button, the script will return 0 on NUM02 wintestem variable to let wintestem
process know that test should be cancelled.
- allowSendToScrap: When this option is true, a “send to scrap” button will be shown so
that user can press it to send harness to scrap from rework clips checker station.
- clipsCheckerBoardOnLeft: Normally checker board is on the right and subassemblies
board is on the left, however, this parameter can be set to true if checker board is on
the left and subassemblies board is on the right.
- reworkPrefix: The prefix that has been added in the harness label for rework. This will
be part of the scanned code in rework clips checker station. Normally it will be an “R”,
but it can be configured.

When this script is executed a screen will be displayed in which it will be shown in which board
the operator will have to perform the clips test as well as which subassemblies or clips station
should be reworked.

© EMDEP 2024 Page 108

Emdep KSK Client / User’s guide

In this example, left board must be used and subassemblies SA1 and SA3 should be reworked.

Apart from returning on variable NUM01 if the script has been executed successfully, this script
returns also, using NUM02 variable, a code which indicates the option selected by user:

Code returned in NUM02 Description

1 User selected start test optio: wintestem process should call

Multiuser clips to start the test

0 User selected cancel test option: wintestem process should NOT

call Multiuser clips

-1 Harness has been sent to scrap

-9 An error has been produced. Wintestem variable STR02 will

contiain a message with details.

When closing stage as ok, harness will return to the line the same way as it happens when
closing stage on rework station.

If something is wrong, harness can be returned to Rework station adding some defects just by
calling script KSK_Rework_Send.vbs

© EMDEP 2024 Page 109

Emdep KSK Client / User’s guide

THIN CLIENTS

© EMDEP 2024 Page 110

Emdep KSK Client / User’s guide

What is a thin client?

Thin clients are stations that do not connect to database directly, and also do not contain any
(or almost any) business logic. They communicate via http to KSK web-service, which contains
all the logic and performs the data exchange with the database.

These clients are normally executed on a raspberry pi device, although they can also be executed
on Windows Systems. See installing KskWebServiceClient section for more details.

Currently, thin client applications exist for those type of stations:

• Micronorma Leak (since version 1.1.0)

• Visual Inspection
• Warehouse to rework
• Marriage stations (matching stations)
• Assembly Matching application
• Partial Matching station
• Final Matching station
• Eyelet Pickup
• Eyelet Squeezing

© EMDEP 2024 Page 111

Emdep KSK Client / User’s guide

Micronorma Leak
Micronorma is a special device for leak detections. This device accepts some commands via
serial port. Our micronorma Leak application is a thin application that communicates with this
device and also with KSK web-service.

Micronorma Leak Flow

The flow for micronorma leak application can be seen below:

© EMDEP 2024 Page 112

Emdep KSK Client / User’s guide

Login screen
When entering to Emdep Micronorma application (and also when entering to other Thin
applications), username will be asked:

If this is the first time when entering application, and settings.xml file was not created, then
the settings screen will appear to be able to configure the device, without having to enter any
user.

As an emergency measure, removing settings.xml file can be done to enter to settings screen
without having to login. Settings.xml file will normally be located on folder
/users/emdep_pi/settings.xml.

© EMDEP 2024 Page 113

Emdep KSK Client / User’s guide

Scanning Order screen

After login, next screen appears to scan an order:

The scanned code must include the harness prefix and the subassembly suffix.

Pressing button will logout current user and will return to login screen.

When logged with a superuser user, icon will appear on the bottom-right corner. We can
press this button to go to settings screen.

If scanned harness is not in proper state, an error screen will appear like this:

© EMDEP 2024 Page 114

Emdep KSK Client / User’s guide

Waiting for Micronorma reply screen

After scanning a correct code (prefix is correct, suffix is correct, and the order exists and it is in
proper status) then command will be sent to micronorma, and this screen will appear:

On the prior screenshot, Status code 500 has been returned by webservice and it means that
harness exists and it is in proper status. Order has been sent to MicroNorma device, and now
application is waiting for Micronorma reply.

If Micronorma device replies with OK, then this screen will appear:

If Micornorma device replies with NOK or ABORT, one of those screens will appear:

© EMDEP 2024 Page 115

Emdep KSK Client / User’s guide

Finally, if Micronorma device doesn’t reply, and a timeout different than 0 has been defined on
“Timeout for micronorma reply” field in configuration, this screen will appear:

Printing label screen

After clicking the "Close stage OK" button, depending on the "Print label" configuration
parameter, the label printing process will be triggered or not. If the parameter is enabled, the
following window will appear on the screen:

As it can be seen, this screen is asking user to scan the printed label. This is made to ensure that
printed label is ok.

On the right-bottom corner, there is a button to reprint the label. When pressing this button,
entering supervisor code will be needed before reprinting the label:

© EMDEP 2024 Page 116

Emdep KSK Client / User’s guide

© EMDEP 2024 Page 117

Emdep KSK Client / User’s guide

Adding defects screen

When closing stage as NOK, this screen will appear:

This screen allows to add defects before sending harness to rework. If no defects are added,
then harness will remain on current station.

Pressing button will add currently selected defect and send harness to rework.

Pressing button will add currently selected defect and will allow to add some extra defect
(application will be kept on same screen).

Pressing button will cancel the adding defects.

© EMDEP 2024 Page 118

Emdep KSK Client / User’s guide

Sending to rework screen

After pressing the button in adding defects screen, a new screen will appear to show the
list of defects added to harness:

Press button to send harness to rework with the list of defects shown on this screen.

Press button to add some extra defects.

Any defect can be deleted pressing the option besides the defect to be deleted.

© EMDEP 2024 Page 119

Emdep KSK Client / User’s guide

Settings Screen
When pressing settings button in scanning order screen, or when starting application if there is
no settings.xml file in application folder, settings screen will appear:

First thing is to configure the base URL of the rest service. After pressing TEST button, if web-
service connection can be made, the combo boxes of next 3 fields will be filled.

New Option provide As Harness Can be sent to Rework; in previous version all NOK harness will
sent to Rework station Now if Harness can be sent to Rework option is select then harness will
send to rework station otherwise it will close a stage.

Starting from version 1.7.0, there is the option of "Print label". In earlier versions, once the test was
performed and passed successfully, the label was automatically printed. With this checkbox, the user
is given the power to choose whether they want the label to be printed or not.

Also Add New Station Type as “Micronorma_SA” same as Micronorma Leak.

“The Print Label Scan Format” is a text that defines what will be included in the barcode in the
printed label. This text can include any of those variables:

- @HarnessPrefix: The harness prefix.

- @HarnessPN: The harness Part Number (Harness Order code)
- @Timestamp: The date and time at the moment of printing, in format
YYYYMMddHHmmss.

In the example, the barcode is expected to contain all 3 variables all together (with no spaces or
separators)

© EMDEP 2024 Page 120

Emdep KSK Client / User’s guide

When pressing the serial configuration, a new screen appears to configure serial port
configuration for both micronorma device and serial printer:

As it can be seen, in this screen 3 things are defined: the prn file, the settings for serial port
connected to device, and the settings for serial port connected to printer.

The prn file that contains the print template is defined. This file can include also any of the 3
variables explained in the “Print Label Scan Format”. The program will replace those variables
with its real value.

For each of the serial port, all parameters must be set with the proper configuration.

Printer button can be pressed to print a testing page using current configuration.

When everything is set, press the back button to return to main settings screen.

All changes will be saved in settings.xml file when pressing the ok button in main settings
screen.

© EMDEP 2024 Page 121

Emdep KSK Client / User’s guide

Visual Inspection
Visual inspection station is a station in which the operator visually examines the harness and
says if it is correct or not.

The flow for visual inspection is shown below.

Adding defects is not mandatory. If close stage is performed as NOK without having added steps,
the harness will remain in same station. If defects were added, the harness will be sent to
rework.

If harness is closed as OK it will advance to next station.

Since version 1.4.0, if there are some missing subassemblies that has not been scanned on Final
Subassembly Matching station, they will be shown before adding the defects.

© EMDEP 2024 Page 122

Emdep KSK Client / User’s guide

Show missing subassemblies screen

This screen is shown since version 1.4.0 if the harness has any pending subassembly.

The screen will be shown only if next planned station is rework and if there is any missing
subassembly (which belongs to current harness and has not been scanned in Partial SA Matching
or Final SA Matching).

This screen will show the list of missing subassemblies (W1 and W2 in the example).

This screen will be also accessible from screen where defects are added, just by pressing a
button.

© EMDEP 2024 Page 123

Emdep KSK Client / User’s guide

Foaming
Settings screen
The first time that application is started after having installed it from scratch, a settings screen
appears which allows to configure the parameters of the application, such as the base URL of
the web-service.

Settings screen will be also accessible from scan order screen.

Serial port setting screen opens for configuration details for printer to get the print.

© EMDEP 2024 Page 124

Emdep KSK Client / User’s guide

Login screen
If configuration is ok, the first step of the application is the login screen. Each user has a code
which identifies them. Scan this code to login to the system, or type the code using a keyboard
and press ENTER.

As it can be seen, some information appears on the footer of the screen. This information is:

- The station name (L09.Foaming in the example)

- The IP address or addresses that the station has. If there is more than one, they are
separated by a slash. In the example there are 2 IP addresses: 169.254.232.160
/192.168.96.1 / 10.13.10.36

Once user code is scanned, the system verifies that the user exists and has proper permissions
to access to this station and, if so, the system ask to scan the order.

© EMDEP 2024 Page 125

Emdep KSK Client / User’s guide

Scan Barcode Screen

If configuration is ok, the first step of the application is the scan order screen. Each user has a
barcode which identifies them. Scan this barcode to login to the system, or type the code using
a keyboard and press ENTER.

Once order barcode is scanned, the system verifies that the order is valid then it will check the
Prefix and suffix letter is valid or not, if so, the system will show the screen to close the stage as
OK or NOK button. If the order/harness is already scanned on this station then it will show the
message as harness has already scanned.

© EMDEP 2024 Page 126

Emdep KSK Client / User’s guide

After Version 4.2 there is no need to scan second barcode. Operator can decide “OK” or “NOK”
status of the current Harness.

If the user closes this stage with OK button, then it closes the stage and moves to next step. And
shows the KSK scan order screen again to scan another order.

If the user closes this stage with NOK button, then it sends the harness to the rework stage. After
clicking on NOK button it shows following screen:

© EMDEP 2024 Page 127

Emdep KSK Client / User’s guide

After clicking on this button it moves the order or harness to the rework stage.

If user again tries to scan this order without closing stage from rework stage it shows the error
screen.

After closing it from rework. User can close the order on foaming stage with OK.

© EMDEP 2024 Page 128

Emdep KSK Client / User’s guide

Warehouse to rework
When a harness is tested, it is stored in the warehouse area. In some plants, if a defect is
detected on the harness while it is on the warehouse, this station allows to send it from
warehouse to rework.

When sending a harness to rework from the warehouse, this application will change status of
current harness from Tested to in process2.

Application flow for Warehouse to rework is shown below.

In this case, adding defects is mandatory, and also it is not possible to make a close stage as OK.
That means that the only possible flow for the harness after being scanned in a warehouse to
rework station is to send it to rework.

2
Since version 1.3.0, the harness status is changed to an intermediate status called
WarehouseToProduction, and only when OK feedback is received from SAP, this status will be changed to
InProcess. If SAP feedback is NOK, then status will be changed back to Tested and the movement to
Rework is reverted.

© EMDEP 2024 Page 129

Emdep KSK Client / User’s guide

Marriage stations
A marriage station (also called matching stations) is intended to make the matching between
main harness and one of its subassemblies.

The scanned code for the harness must contain a prefix (for example an ‘M’). The scanned code
for the subassembly must contain a prefix (for example an ‘S’) and a suffix (for example “.01”).

All subassembly prefixes are configured in settings. Main harness prefix is received from web-
service.

The application flow for marriage client can be seen below.

© EMDEP 2024 Page 130

Emdep KSK Client / User’s guide

Assembly Guiding Application

Assembly guiding application is an application running in an embedded computer intended to
show the steps and instructions to operator to assemble wires and clips to connectors.

General flow
This is a simplified diagram of the application flow:

As it can be seen, after user logs in, the system checks if there is any available order for this
station. An order is available for a station if it has a production module assigned to that station.
If there is one, then the first production module that belongs to the order and that was assigned
to this station is shown in instructions screen. Then operator makes the assembly and presses
the OK button when he finishes to get next production module. A waiting screen appears if there
are no more production modules to be processed on this station, considering not only PMs
belonging to current harness but also to any harness.

© EMDEP 2024 Page 131

Emdep KSK Client / User’s guide

Settings screen
The first time that application is started after having installed it from scratch, a settings screen
appears which allows to configure the parameters of the application, such as the base URL of
the web-service.

Settings screen will be also accessible from Show Instructions screen and from Waiting screen if
currently logged user is a superuser.

When specifying Base URL of the webservice and pressing the TEST URL button, if URL is ok and
web-service is accessible, combo boxes of production line and station will be filled. Only stations
of type preassembly, subassembly or subassembly workplaces will be considered.

Waiting Timeout parameter allows to configure the number of seconds that waiting screen will
wait until making a new request to web-service to ask if there is now any pending production
module for current station.

During execution of application, ok or next button can be pressed to go to advance to next

production module or to advance to next page. This advancement can be done using the mouse
(or pressing over the button in the screen, if screen is a touch screen) or can be pressed using a
physical button. In case that a physical button should be used, it is connected to device using
GPIO. If this is the case, check the Use GPIO checkbox and select the GPIO number (from 1 to
27) which the button is connected to.

Connector Aid Folder option parameter is intended to specify the folder where connector
pictures will be stored locally. By default, the current working folder will appear, but it is
advisable to press the BROWSE button and create a new folder called Connector Aids or
something similar and select this new created folder.

© EMDEP 2024 Page 132

Emdep KSK Client / User’s guide

No. of Orders in Queue in user can enter no of order you want show to operator. If you set 3
then it will show 3 pending orders with its PM in List

Finally, it is possible to print a label when all production modules for a functional module have
been processed. If this option is desired, check the option Print File Label and press the
configuration button

After pressing this button, this screen appears to configure the printer parameters:

Press the back button to return to main configuration screen.

In Printing Mode having 3 options for

• Ethernet
• USB
• Serial Port

As per printer select any one out of above option & fill connection details as per printing mode.

And Set Correct path of print template.

On main settings screen:

Press ok button to save the changes made in settings screen.

Press the cancel button to exit settings screen without saving changes.

© EMDEP 2024 Page 133

Emdep KSK Client / User’s guide

Login screen
If configuration is ok, the first step of the application is the login screen. Each user has a barcode
which identifies them. Scan this barcode to login to the system, or type the code using a
keyboard and press ENTER.

As it can be seen, some information appears on the footer of the screen. This information is:

- The station name (PM3 in the example)

- The IP address or addresses that the station has. If there is more than one, they are
separated by a slash. In the example there are 2 IP addresses: 172.25.48.1, 10.13.10.44
- The currently user name (this information will only appear when user is logged in).

Once user code is scanned, the system verifies that the user exists and has proper permissions
to access to this station and, if so, the system will check what is the next pending production
module that has to be made on this station.

If there are no pending production modules to be processed, a waiting screen will appear.

If there is any, the instructions screen will appear with detailed information for that production
module.

© EMDEP 2024 Page 134

Emdep KSK Client / User’s guide

Waiting screen
If there are no production modules pending to be processed on current station, waiting screen
will appear.

This screen will be communicating regularly with web-service to check if there is any pending
production module and, if so, instructions screen will appear.

© EMDEP 2024 Page 135

Emdep KSK Client / User’s guide

Instructions screen
When there is a production module pending to be processed in current station, the instructions
screen appears:

Instructions screen contains a header:

In the header, apart from the name of the application and the current version (v1.0.8 in the
image above), the following information appears:

• Order: this is the order returned by the system which has some pending production
modules. In the previous example, the name of the order is 451.

• P. Module: The name of the production module that is being processed now in
current station. In the example this name is 000-AABA-48.

© EMDEP 2024 Page 136

Emdep KSK Client / User’s guide

The content of instructions screen is split in Three parts:

The upper part shows images of the used connectors and ways. For each image, the PartNumber
of the connector is overlapped on the bottom part, and the ways that are being used by the
steps shown below appear Enlighted. The color or colors of the wire that uses that way are
painted inside the way.

The lower part shows the steps that have to be followed. There are 3 types of steps:

Instructions to follow, such as taping some wires, etc.…. Instructions can

Instructions contain a material name, a part number and a text note.

Wire to be assembled. It contains the material name, PartNumber, Cross

Section (CS), Connector and Way in one end (From), Connector and Way
in the other end (To), and a text note.

For each connector/way, it can appear 3 things:

- Connector ID
Wire - Connector PartNumber (which is also shown in the picture)
- Name of the way

That information is separated by a slash (/).

Additionally, the icon appears if the connector has to be picked up.

Clip to be assembled. It contains the material name, PartNumber and a

Clip text note.

Only items assigned to currently Production Module will appear, and they will
appear in the order that has been specified in KSK Studio.

© EMDEP 2024 Page 137

Emdep KSK Client / User’s guide

If the number of items of the production module does not fit, results will be paginated. This
results in appearing a new button to go to next page instead of showing the ok button, which
will be shown only on the last page.

The image above shows first page. The image bellow shows second page.

© EMDEP 2024 Page 138

Emdep KSK Client / User’s guide

This Part will show List of Current Order with Its PM and List will show Pending Orders in Queue.

451 is my current Order & Right-side column will show production Module of Current order.
Current Order will be appeared in blue color & next order in queue will be appear in silver color.
Next Order in queue is 0451812075-7.

When Last Production Module come in Current Order the List of next order will be appear like
this. It will show next pending order in queue with its Production Module.

My Current Oder is 451 & its Last production module is 830-YEGA-12

© EMDEP 2024 Page 139

Emdep KSK Client / User’s guide

Those are the buttons that can appear at the bottom-right corner of the screen:

When there are more items than the amount that can be shown
on the screen (in a full HD screen, when there are more than 8
steps), items are paginated. When we are not in first page, this
Previous page button appears to allow to return to previous page.

When there are more items than the amount that can be shown
on the screen (in a full HD screen, when there are more than 8
steps), items are paginated. When we are not in last page, this
Next Page button appears to allow to go to next page.

This button only appears if all items fit in one page, or if we are in
the last page. Pressing this button validates the current production
module and it tries to get next production module to be processed
on this station (firstly, next production of current harness, but first
Ok production of next harness if there are no more PM for current
harness).

This button is only available if current user is a superuser. It allows

to open settings screen.

Settings

This button finishes currently logged user and It returns to login

screen.

Logout

© EMDEP 2024 Page 140

Emdep KSK Client / User’s guide

If Current Production Module not having any item, then below part of screen will be appear like
this & just complete this Production Module by clicking Ok button. Next Production Module will
come for testing.

© EMDEP 2024 Page 141

Emdep KSK Client / User’s guide

Connector Pictures in detail

Connector pictures that appear in Assembly Guiding application are defined using KSK Studio
Connector Visual Aid plugin. Each picture contains a PNG image, an XML file containing some
extra information to define the areas for the ways, and a SHA file containing hash codes for both
PNG and XML files. All this information is stored in database, and is got from Web-service,
however, once an image has been downloaded, it is kept in a local cache (images are being
stored in folder defined in settings screen).

When starting the application, there is a process which uses SHA256 hash codes to detect which
images (or related information) are obsolete and all those files that are outdated are deleted so
that this information will be requested again from web-service.

The following diagram shows this process to update the pictures and their information that is
out of date:

This means that, if any change has been done to connector pictures or to their ways definition,
information cannot be refreshed to the application until it is restarted.

© EMDEP 2024 Page 142

Emdep KSK Client / User’s guide

SA Matching Client Application

SA matching application is an application running in an embedded computer intended to show
workcenters related to each step.

General flow
This is a simplified diagram of the application flow:

As it can be seen, after user enters the line, station system checks the available order for this
station with prefix letter. If the order is available then it will ask for the user code and then it will
show the list workcenters assigned to that order for the selected substation. After all
workcenters scan for each station it will give message as harness has already scan on this station.

In this application there are two flows one is Partial matching flow and second is Final matching
flow. In the partial matching flow, we get screen showing only workcenters related to the
selected station. And in final matching flow we get screen showing all workcenters related to
the harness. After scanning all the workcenters it will show the screen of harness completed
successfully.

© EMDEP 2024 Page 143

Emdep KSK Client / User’s guide

Settings screen
The first time that application is started after having installed it from scratch, a settings screen
appears which allows to configure the parameters of the application, such as the base URL of
the web-service.

Settings screen will be also accessible from Show Instructions screen.

When specifying Base URL of the webservice and pressing the TEST URL button, if URL is ok and
web-service is accessible, combo boxes of production line and station will be filled. Only stations
of type preassembly, subassembly or subassembly workplaces will be considered.

Waiting Timeout parameter allows to configure the number of seconds that waiting screen will
wait until making a new request to web-service to ask if there is now any pending workcenter
for current station.

During execution of application, harness with workcenter name and pressing enter button will
scan the workcenter for this station successfully. And change the color for that workcenter to
green. Or if we are scanning another workcenter which not related to the selected station then
it will change the color to yellow after scanning successfully.

In this screen added “remove last n characters from the harness” label. It is used for KSK SA
Matching client to remove last characters from the harness order. And default value of this parameter is
0. It means that no character is removed from harness label. It is available for both Partial Matching and
Final matching stations

© EMDEP 2024 Page 144

Emdep KSK Client / User’s guide

Scan Barcode Screen

If configuration is ok, the first step of the application is the scan order screen. Each user has a
barcode which identifies them. Scan this barcode to login to the system, or type the code using
a keyboard and press ENTER.

As it can be seen, some information appears on the footer of the screen. This information is:

- The station name (L09.SA Matching1 in the example)

- The IP address or addresses that the station has. If there is more than one, they are
separated by a slash. In the example there are 2 IP addresses: 172.20.32.1, 10.0.9.75
- The currently user name (this information will only appear when user is logged in).

Once order barcode is scanned, the system verifies that the order is valid then it will check the
Prefix letter is valid or not and also it will check how many letters want to remove from order if
harness order character is less than the remove character then it will show error message , if
all details are correct then, the system will ask to enter the user code screen. If the
order/harness is already scanned on this station then it will show the message as harness has
already scanned.

© EMDEP 2024 Page 145

Emdep KSK Client / User’s guide

Scan User Code Screen

If the order barcode is valid then scan user code screen will appear. After entering the user code,
it checks if the user is valid or not. If yes then it will show the scan subassembly code screen.

When we have selected the partial matching flow in the setting file then screen will appear as:

When the final matching flow is selected in the setting file then this scan user code screen
appears as:

© EMDEP 2024 Page 146

Emdep KSK Client / User’s guide

Scan subassembly code screen

After entering the user code, it checks if the user is valid or not. If yes then it will show the scan
subassembly code screen. In these screens it displays the list of workcenters assigned to that
station for the harness. To scan this workcenter we have to scan the order barcode with
workcenter name and press the enter button.

If we have selected the partial matching flow then scan subassembly code screen appears as:

If we selected the final matching flow in the configuration file the scan subassembly code
screen appears as: the list of workcenter labels to scan will be initially colored in 3 colors:

•red: labels pending from Partial matching, independently if they are assigned for re-scan at
Final matching or not

•yellow: labels which are defined for re-scan at Final matching

•green: labels not necessary to scan.

© EMDEP 2024 Page 147

Emdep KSK Client / User’s guide

After scanning the code, it will change the background color for that workcenter as green.

After completing the all workcenters it will show the scan user barcode screen again.

If we send the harness to rework with or without Schunk by clicking on the button it will
display the screen as:

© EMDEP 2024 Page 148

Emdep KSK Client / User’s guide

When we click on the setting button it will display the screen which ask for the super user
code

© EMDEP 2024 Page 149

Emdep KSK Client / User’s guide

Partial Matching station

Partial Matching station is intended to attach some subassemblies to a harness. This is the flow
of the application:

Depending on a global parameter configured in KSK web service, operator code will be required
before scanning each subassembly instead of just scanning once after montage plan.

Configuration screen
When starting the application for first time, a screen will appear to configure the station.

After entering the base URL where Emdep KSK Web-service is installed, the rest to the field will
be filled. Select the production line and station. Only stations of type Subassembly and Final

© EMDEP 2024 Page 150

Emdep KSK Client / User’s guide

Matching will appear on the list. Select also the Matching flow to choose if this is a partial
matching station or final matching application.

On the bottom-right corner, those buttons appear:

Left and right buttons are to cancel and accept the changes made.

The button in the middle is intended to set the led configuration:

The numbers for Green, Red and Yellow are the pin number where those LEDs are connected
and must be different (meaning that the shown configuration 1-1-1 is not possible and should
be, for example, 1-2-3 or 3-2-1).

© EMDEP 2024 Page 151

Emdep KSK Client / User’s guide

Main screen

When Clicking on Setting button Station will be block & Supervisor code
required for Configuration settings.

Settings

This button finishes currently logged user and it returns to login screen.

Logout

© EMDEP 2024 Page 152

Emdep KSK Client / User’s guide

This button using for going to back to Order Scan Screen

Previous page

After entering supervisor code configuration setting page will be open.

© EMDEP 2024 Page 153

Emdep KSK Client / User’s guide

Final Matching station

Final matching station is intended to perform the final matching after all required partial
matchings. This is the flow of the application:

There will be 2 different NG buttons: one for skipping Schunk and one for performing Schunk. In
the following diagram this is represented by SC1 and SC2 special flows (red arrows):

© EMDEP 2024 Page 154

Emdep KSK Client / User’s guide

Missing subassemblies screen

When there are some missing subassemblies, the station will be blocked until a supervisor code
is scanned. After scanning supervisor code, this screen will appear until all missing subassemblies
are scanned or until one of the buttons on the bottom-right corner are pressed: for sending
harness to rework passing by Schunk and Visual Inspection, by sending harness to rework
passing by Visual Inspection but without passing by Schunk, or cancelling this action.

For Multiple Final Matching Station need to process all optional and subassembly station in
particular step. After that scan all required code from final matching station for particular step
and it will close the final matching station for current station’s step.

© EMDEP 2024 Page 155

Emdep KSK Client / User’s guide

FM Matching Client
FM Matching application is an application running in an embedded computer intended to
Complete FM in scan order.

As it can be seen, after user logs in, the system waits for Harness scan. After scan harness check
necessary things like prefix or Valid Harness etc. after that scan Conveyor table and that scan
functional Module In harness one by one all functional module completed. After Completing all
Functional module Harness completing in current station & passes to next plan station.

© EMDEP 2024 Page 156

Emdep KSK Client / User’s guide

Settings screen
The first time that application is started after having installed it from scratch, a settings screen
appears which allows to configure the parameters of the application, such as the base URL of
the web-service.

Settings screen will be also accessible from Show Harness screen.

When specifying Base URL of the webservice and pressing the TEST URL button, if URL is ok and
web-service is accessible, combo boxes of production line and station will be filled. Only stations
of type FM Matching workplaces will be considered.

Scanning Time of Harness parameter allow you to scan Functional Module in that time period
after time out Conveyor table screen open once again.

All other parameter is related to harness label to set prefix harness & length, also set conveyor
table length, set functional module prefix, length & start position of FM of FM label.

© EMDEP 2024 Page 157

Emdep KSK Client / User’s guide

Login screen
If configuration is ok, the first step of the application is the login screen. Each user has a barcode
which identifies them. Scan this barcode to login to the system, or type the code using a
keyboard and press ENTER.

As it can be seen, some information appears on the footer of the screen. This information is:

- The station name (FM_Matching_Demo_010 in the example)

- The IP address or addresses that the station has. If there is more than one, they are
separated by a slash. In the example there are 3 IP addresses: 169.254.116.184,
10.0.20.126 and 192.168.56.1.
- The currently user name (this information will only appear when user is logged in).

Once user code is scanned, the system verifies that the user exists and has proper permissions
to access to this station and, if so, the system will wait for harness scan.

© EMDEP 2024 Page 158

Emdep KSK Client / User’s guide

Scan Harness Screen

If User Log Correctly then this screen will open and waiting for scanning harness label

After scanning harness label by Operator, it will check harness prefix is correct or not. If harness
prefix not correct then giving warning message & Orange LED will blink. And operator scan once
again with correct prefix then check order valid or not.

If Order not valid then supervisor screen will open & Red LED blinking. Otherwise, Conveyor
Table scan screen will be open & green LED will blink.

This button is only available if current user is a superuser. It allows

to open settings screen.

Settings

This button finishes currently logged user and it returns to login

screen.

Logout

© EMDEP 2024 Page 159

Emdep KSK Client / User’s guide

Conveyor Table Screen

After Scanning Correct harness by operator Conveyor Table Screen will open.

In conveyor Table screen operator will scan conveyor table label after that system will check
length of scan label. If scan label length match, then green LED blink and Fm Scanning screen
will be open.

If Conveyor Table length not match then system will generate warning message to operator, the
Conveyor table length will not match & Orange LED will be blinking.

This button using for going to back to Harness screen

Previous page

© EMDEP 2024 Page 160

Emdep KSK Client / User’s guide

Functional Module Scan Screen

After scanning Correct Conveyor Table Scan this screen will be open

When Operator scan FM Label after that system will check prefix & length of label. If Label length
or prefix not correct then it will generate warning message for operator & orange LED will be
blinking.

When operator scan Correct FM Label system will check in Label Order is match with current
Order or not and also check Functional model Correct or not also system will check Current Fm
is Already matched or not if all above condition getting corrected then it will precoding next
step. Otherwise, it will generate error message for operator supervisor screen will be open. And
Red Led will Blink.

In Current Order Some FM Not Completed in that condition system will process current FM &
Show Message to operator to scan next FM. When all FM Completed in Current Order then
Result screen will be open. And Current Harness will close from current station & process that
harness to next plan station.

© EMDEP 2024 Page 161

Emdep KSK Client / User’s guide

Result Screen
In Result Screen will open after current Harness will completed.

After Pressing Ok Button once again scan Harness page will be generate.

© EMDEP 2024 Page 162

Emdep KSK Client / User’s guide

Rotary Line Led Navigation

The application is designed to control and manage the illumination of the LEDs based on the
specific configuration and status of the harness and its associated modules. This allows for
precise and synchronized control of the LEDs to provide visual feedback and information
corresponding to the assembly process or other relevant parameters.

The configuration of the LEDs is done in the KSK Studio.

Physically, we have 2 types of devices on the production line. The first is the "Scanning device"
and the other is the "Panel device".

In order to be able to switch on the desired LEDs, it is necessary to scan the Harness and then
the Panel where the wiring will go. If the Harness contains modules to which LEDs have been
assigned for that panel, they will light up.

Settings screen Raspberry Pi

The first time the application is started, the form to configure the device will appear.

Two types of devices must be configured. The Scanning device and the Panel device.

Scanning device configuration

First of all, let's configure the Scanning device. This device will be the one that the operator will
scan the Harness and the panel that corresponds to it. Also this device will be in charge of the
connection via wifi to the panels.

The first thing to do is to enter the address of the webservice in the "Base URL" field.

© EMDEP 2024 Page 163

Emdep KSK Client / User’s guide

Once this parameter has been entered, click on the "TEST URL" button. This button makes a
request to the webservice to obtain the configuration made in the different lines that have been
defined in the KSK Studio.

At this point you have to choose the "Product Line" to which the scanning device belongs.

Then choose the "Main station name" and the "Station" which must match.

Then, proceed to configure the "Serial scanner". In order to carry out this configuration, it is
necessary to click on the tab with this name.

The picture shows an example configuration for the "Serial scanner". Once this configuration
has been entered, the "Test serial scanner" button can be pressed to check that everything is
correct. If it is correct, after pressing this button and using the serial scanner to scan a barcode,
a window with the scanned text will be displayed on the screen.

We then proceed to configure the wifi that will act as a bridge between the panels and the
webservice.

When entering the "Hotspot" tab, the system provides the necessary information for the
configuration of the wifi access point for the panels.

At this point you must click on the "Generate Hotspot" button.

Once pressed, the application will restart several times to perform all the relevant
configurations.

The configuration is only allowed to be done on a Raspberry Pi device.

© EMDEP 2024 Page 164

Emdep KSK Client / User’s guide

It is important not to remove the installation usb until the screen indicates that it can be
removed.

Once the system has been configured, it will open asking for the credentials of the user who is
going to work in that station and in the lower left corner two IPs. The first IP is the one that
corresponds to the wired connection of the device on the company network. The other IP
corresponds to the wifi.

Now we are ready to proceed with the configuration of the panel that contains the LEDs.

Panel device configuration

Before turning on the panel device it is necessary to connect the same usb that we were using
for the scanning device configuration, a monitor and a mouse.

When the panel device is started, the configuration window appears directly. In this case, click
directly on the "TEST URL" button without setting any value.

Internally, we proceed to use the base configuration that has already been saved on the usb.

For the correct configuration, it is necessary to choose the same line as the scanning device and
the same "Main station name". In the "Station" field, the corresponding panel must be chosen.

© EMDEP 2024 Page 165

Emdep KSK Client / User’s guide

Then proceed to the "Hotspot" tab and click on the "Connect To Wifi" button.

The system will inform you that it is going to restart to make the relevant configurations.

The usb must be removed as soon as the system prompts you to do so.

If everything has gone correctly, the application will open and at the bottom, the IP assigned to
the device through the Wi-Fi generated by the scanning device will be displayed.

How to use
When starting the scanning device, it will prompt you to enter the credentials of the user who
will be using the station. You should enter the credentials as requested.

Afterward, you will be prompted to scan the harness. It should have the same prefix that you
have defined in the configuration.

© EMDEP 2024 Page 166

Emdep KSK Client / User’s guide

At this point, you should scan the panel where the harness will be placed. The barcode you
need to scan should have the prefix specified in the configuration, followed by the name of the
panel you have entered in KSK Studio.

If all the information is correct and the harness has modules associated with LEDs configured
for the scanned panel, a signal will be sent to turn on the LEDs.

Possible problems
If the LEDs do not turn on correctly, there could be various issues:

1. The Raspberry Pi of the panel is not powered on: Ensure that the Raspberry Pi
connected to the panel is powered on and running properly.
2. The Raspberry Pi of the panel has lost Wi-Fi connection with the scanning device:
Check the Wi-Fi connection between the Raspberry Pi and the scanning device. Ensure
that they are connected to the same network and that the Wi-Fi signal is stable.
3. There is a connection problem between the LEDs and the Raspberry Pi of the panel:
Verify the physical connections between the LEDs and the Raspberry Pi. Make sure
they are securely connected and that there are no loose or damaged cables.
Additionally, check the software configuration on KSK Studio to ensure it is properly
set up to control the LEDs.

In the configuration of the scanning device, there is a tab called "Test LEDs Panel." In this tab,
you can directly send the desired signal to the specific panel you want to test the different
LEDs. This allows you to verify the functionality of individual LEDs without going through the
entire scanning process.

© EMDEP 2024 Page 167

Emdep KSK Client / User’s guide

To perform a test in this form, you need to first click on the "Load" button. This action will load
the list of panels in the line you are working on.

Then, you can manually define the LEDs you want to turn on in the "LEDs to send" option.

If you want to turn off or turn on all the LEDs of the chosen panel, you can use the "Switch off
LEDs" or "Switch on all LEDs" buttons.

When you send a signal to the panel, below the "Operation result" text, you will see
information about the system's status. When you send the LEDs, it will display "Sent
information to panel XXXXXX". If the Wi-Fi connection is correct, the LEDs on the panel should
behave as desired.

If you have a display connected to the panel, you can see a similar message as shown in the
image below.

In this test case, the signal to turn on all the LEDs has been sent to the panel.

© EMDEP 2024 Page 168

Emdep KSK Client / User’s guide

Wire Pick-up for Eyelets

This application is designed to facilitate the process of picking up wires for eyelets by the
operator in order to prepare them for the squeezing operation of the eyelet. In order to do so
the application is connected to led bars that are mounted on the station thus providing a visual
cue to the operator of what wires it needs to pick up and their number by lighting up the leds.

Settings screen
The first time the application is started the settings screen will appear in order to make the
required changes in order to configure the application for your use case.

General Settings
The “Base URL” is the link to the KSK Web Service with whom the application will communicate
during standard operation. Pressing the button “TEST URL” will check the connection to the KSK
Web Service with the provided link and load the eligible data for “Production Line” and
“Station”.

The “Production Line” is a list of lines that contains steps with at least one station type
“EyeletWirePickUp” as they are set in KSK Studio.

The “Station” is the “EyeletWirePickUp” type of station that you desire to operate with the
application.

© EMDEP 2024 Page 169

Emdep KSK Client / User’s guide

The “Usb Rs485 Port” is the list of available serial ports where you select the one that will send
commands to the led bars.

The “Wire Pipes List” are the list of wire pipes as defined by your need where you specify the
wire material, led bar id, the start and end position that corresponds physically to where the led
bar is placed near the wire pipe.

Add Wire Pipe

In order to add a wire pipe, we press the button with the “plus sign” and a new window will
appear where we specify the required data.

The “Yazaki Wire Material” is the wire material name such as: SK04960721

The “LED Bar Id” is the id of the led controller that can be seen when you provide power to the
led bar.

The “Start LED” is the position starting with 1 of the led that corresponds with where the wire
pipe starts.

The “End LED” is the position of the led that corresponds with where the wire pipe ends.

Thus, if we provide 1 for “Start LED” and 5 for “End LED” then the leds 1, 2, 3, 4, 5 will be
allocated for that wire pipe.

Warning: Leds cannot be reused on the same led bar between multiple wire pipes.

© EMDEP 2024 Page 170

Emdep KSK Client / User’s guide

Edit Wire Pipe

In order to edit a wire pipe, we select the desired wire pipe from the list by clicking on it and we

press the button with the “pencil” and a new window will appear where we can edit the
data of the wire pipe.

Warning: Leds cannot be reused on the same led bar between multiple wire pipes.

Delete Wire Pipe

In order to delete a wire pipe, we select one or more desired wire pipes from the list by clicking

on them and we press the button with the “trashcan” .

Warning: Please be careful as the delete operation cannot be undone.

Test Selected Wire Pipes

In order to test if the provided data for a wire pipe corresponds to the physical wire pipe and
the led bar is working properly, we select one or more desired wire pipes from the list by clicking

on them and we press the button with the “star” . The wire pipes will start lighting up in the
order of Red, Green, Blue, White for each selected wire pipe in order to check that the full color
spectrum is working.

Test All Wire Pipes

In order to test all the provided data for the wire pipes list correspond to the physical wire pipes

and the led bars are working properly we press the button with the “double star” . The wire
pipes will start lighting up in the order of Red, Green, Blue, White for each wire pipe in the list
in order to check that the full color spectrum is working.

© EMDEP 2024 Page 171

Emdep KSK Client / User’s guide

Clear All Wire Pipes

In order to clear the led bars from the previous tests done we press the button with the “broom”

Working Mode
The application has 2 working mode options from which to choose:

The “All Eyelets At Once” option will light up all the wire pipes of the eyelets that are present in
the order.

The “Eyelet By Eyelet” option will sequentially light up the wire pipes of each eyelet. In order to
pass to the next eyelet, the operator will press on the gpio button.

Information On Screen
The application has 3 options for the displayed information on screen from which to choose:

The “Yazaki Wire Material” will show only the wire material for the eyelet content ex:
SK04960721.

The “Customer Wire Name” will show only the wire name for the eyelet content ex: 10001.

The “Yazaki Wire Material + Customer Wire Name” will show both the wire material and the
wire name for the eyelet content ex: SK04960721_10001.

GPIO Button
The “Button GPIO Port” field is the list of available GPIO ports from which you choose the one
where the physical button is connected. In order to be sure that the selected port is the proper
one we press the “TEST” button and then we try multiple times to press the physical button. If
the selected port is the proper one the text will change to OK, if not the text will change to NOK
and will allow you to check another port.

In case you have doubts regarding which port is the correct one you can mouse hover over the
text “Button GPIO Port” and an image will appear with the physical GPIO port configuration of
the device.

Prefix
The string to be removed from the begin of the order when it is sent to web service. Only
uppercase letters are allowed. If no string is to be removed the field can be left blank.

Suffix
The number of characters to be removed from the end of the order. If no characters are to be
removed the field can be set to 0.

© EMDEP 2024 Page 172

Emdep KSK Client / User’s guide

Log Level
The logging level of the application. The possible levels are the following:

• Debug
• Information
• Warning
• Error
• Fatal

Standard Operation Screen

After you have set up the application this is the screen where the operator will interact with in
order to pick up wires for eyelets. The led bars are prechecked and they will light up with the
boot of device color and duration as they are specified in KSK Studio, then the “Scan Order
Barcode” screen will appear.

In case you want to make changes to the configuration of the application, you can go to the

settings screen by pressing the “cog” button in the lower right side of the window. This will
make the “Scan User Barcode” window to appear in order to confirm that you have the required
permissions to make changes.

Scan Order Barcode

In order to start the wire pickup operation, you need to provide the order that has the
information regarding the required wires to be picked up. This is done by scanning the barcode
with the order using the usb barcode scanner.

© EMDEP 2024 Page 173

Emdep KSK Client / User’s guide

Order Screen
If the scanned order is eligible to be processed in the station then a new screen will appear with
the order information based on the configured working mode and information on screen
options.

If the led is light up then 1 wire needs to be picked up. If the led is blinking then 2 wires need to
be picked up. The blinking time interval is set in KSK Studio.

If the order is processed successfully then the led bars will light up with the configured color and
time of the “Order Finished” setting from KSK Studio.

Scan User Barcode

In the eventuality that you need to change the configuration of the station you need to confirm
entering the settings screen by scanning the user barcode of a user that has the permission to

make such settings. If you want to cancel the operation you can press the “x” button from
the bottom left corner.

© EMDEP 2024 Page 174

Emdep KSK Client / User’s guide

Power failure recovery system

In the case of a power failure, if the working mode is configured to “Eyelet By Eyelet” then if the
first scan of order is the previous one that was being processed when the power failure occurred
the operator will continue from the remaining eyelets from that order.

Error codes
In the unfortunate situation that an error occurs the application will try to display that error in
order to fix it if possible. The color and duration of the error is the one that is set from KSK
Studio.

If there are led bars available then the error code will be displayed on the led bars by the
combination of a repeating pattern of ON_OFF leds where the number of ON leds will indicate
the error code.

If for some reason there are no led bars available to display the error code then an error window
will appear on the screen with an error message that will reflect the description of the error
code.

Possible error codes and their number of ON leds:

1. A led bar error has occurred. One or more led bar may be disconnected;
2. The received eyelets contain a wire pipe that is not defined in the station configuration;
3. The configured wire pipes are not big enough for the received eyelets to be processed;
4. The close stage operation has timed out. The application will retry to send the close
stage operation;
5. The open stage operation failed;
6. The list of eyelets to be processed is empty;
7. The close stage operation failed;
8. An http error has occurred on contacting the KSK Web Service;
9. The received xml could not be decoded;
10. The received xml has the wrong content;
11. The received xml has an empty response instead of data;
12. The received xml has a response data that is unknown to this application;
13. A serial error occurred that is indicative of a possible duplicate led bar id.

© EMDEP 2024 Page 175

Emdep KSK Client / User’s guide

Rework Dashboard
The Rework Dashboard application has been created to run on a Raspberry Pi to display a
dashboard showing the harnesses scanned at Rework In but not finished at Rework Out.

Settings screen
The first time the application is started, the form to configure the device will appear.

In this screen only is allowed to add the Base URL. This parameters defines the adress of the ksk
webservice.

After entering the web service address and pressing the "TEST URL" button, if everything is
correct, the other parameters that cannot be edited in the configuration will display the values
configured in the KSK Studio.

© EMDEP 2024 Page 176

Emdep KSK Client / User’s guide

How to use
When starting the app, it will promt you to enter the credentials of the user who will be using
the statation. You must enter the credentials as requested.

Afterward, you will be promoted to the main screen of the Rework Dashboard.

In the previous image, you can see two main areas, one with a white background and the other
with a blue background.

The white area contains, in a grid format, the harnesses that have already passed through
Rework - In but have not yet gone through Rework - Out. It can also be observed that each
command has a different color: red, blue, and black.

- Red harness: The harness in red have exceeded the warning time (in hours) in pending
rework. All the harnesses that have been at Rework for more than the warning time will
be displayed in red at the beginning of the list.
- Blue harness: The harness has been set as urgent. Urgent harnesses will be displayed in
blue at the beginning of the list, just after the Orders which has been passed the warning
time.
- Black harness: The harnesses that have passed through Rework - In.

© EMDEP 2024 Page 177

Emdep KSK Client / User’s guide

In the blue area, two counters can be seen. The first one is labeled "IN," and the second one is
labeled "Total."

- The number next to "IN" refers to the total number of harnesses that have passed
through Rework-In.
- The number next to "Total" refers to the total number of harnesses pending to pass
through Rework-In.

© EMDEP 2024 Page 178

Emdep KSK Client / User’s guide

Deserialization Client
This application can handle a process of deserialization. The Deserialization process means
Sometimes, order number of harnesses manufactured at Yazaki or Nursan needs to be replaced
by a new order number at Ford warehouse. Then, a new label with new order number needs to
be printed, keeping data of original order in a process called deserialization.

First scan order & application send that order to deserialization server. Server check Order
present or not. If not then send show “no label to print”. If present then server will send new
order to the application with appropriate URL of database. After that Application send
information to appropriate URL for harness details. After receiving harness details, it will be print
by Application.

© EMDEP 2024 Page 179

Emdep KSK Client / User’s guide

Setting Screen
The first time that application is started after having installed it from scratch, a settings screen
appears which allows to configure the parameters of the application, such as the base URL of
the deserialization web-service.

Settings screen will be also accessible from Show Harness screen

When specifying Base URL of the webservice and pressing the TEST URL button, if URL is ok and
web-service is accessible, combo boxes of production line and station will be filled. Only stations
of type deserialization client workplaces will be considered.

Finally, it is possible to print a label when all production modules for a functional module have
been processed. If this option is desired, check the option Print File Label and press the
configuration button

After pressing this button, this screen appears to configure the printer parameters:

Press the back button to return to main configuration screen.

In Printing Mode having 3 options for

• Ethernet
• USB
• Serial Port

As per printer select any one out of above option & fill connection details as per printing mode.

And Set Correct path of print template.

© EMDEP 2024 Page 180

Emdep KSK Client / User’s guide

On main settings screen:

Press ok button to save the changes made in settings screen.

Press the cancel button to exit settings screen without saving changes.

© EMDEP 2024 Page 181

Emdep KSK Client / User’s guide

Scan Harness Screen

After saving setting “Scan harness barcode” page will be open & waiting for barcode scanning.

It allows to open settings screen.

Settings

It allows to close application.

Logout

After scan harness application send Application to deserialization webserver. Webserver

checking harness exist or not accordingly server will send result.

If harness not exist then no order screen will display show message come from webserver

© EMDEP 2024 Page 182

Emdep KSK Client / User’s guide

when you click on this ok button scan harness barcode form will be appear.

Print label Screen

When operator click on “OK” button as per printer setting harness data will be send
to printer & print it.

© EMDEP 2024 Page 183

Emdep KSK Client / User’s guide

Validation label Screen

In this screen, the user is prompted to scan the label that has just been printed. If the scanned
code contains the new nomenclature for the order, it will be considered valid; otherwise, it will
not.

Whether the label is valid or not, a close stage operation is performed. In the case where the
label is incorrect, it will be closed as "NG."

After performing this validation, it returns to the initial screen so that the user can scan
another order.

© EMDEP 2024 Page 184

Emdep KSK Client / User’s guide

QA FireWall Client
Fire Wall station is a station in which the operator visually examines the harness and says if it is
correct or not. Firewall client has the same functionality of Visual Inspection, but without being
affected by special flow rules.

the flow for Fire Wall station is shown below:

Adding defects is not mandatory. If close stage is performed as NOK without having added steps,
the harness will remain in same station. If defects were added, the harness will be sent to
rework.

If harness is closed as OK it will advance to next station.

© EMDEP 2024 Page 185

Emdep KSK Client / User’s guide

Settings screen
The first time that application is started after having installed it from scratch, a settings screen
appears which allows to configure the parameters of the application, such as the base URL of
the web-service.Settings screen will be also accessible from scan order screen.

Login screen
If configuration is ok, the first step of the application is the login screen. Each user has a code
which identifies them. Scan this code to login to the system, or type the code using a keyboard
and press ENTER.

© EMDEP 2024 Page 186

Emdep KSK Client / User’s guide

As it can be seen, some information appears on the footer of the screen. This information is:

- The station name (Fire Wall station in the example)

Once user code is scanned, the system verifies that the user exists and has proper permissions
to access to this station and, if so, the system asks to scan the order.

Scan Barcode Screen

If configuration is ok, the first step of the application is the scan order screen. Each
user has a barcode which identifies them. Scan this barcode to login to the system,
or type the code using a keyboard and press ENTER.

Once order barcode is scanned, the system verifies that the order is valid then it will check the
Prefix and suffix letter is valid or not, if so, the system will show the screen to close the stage as
OK or NOK button. If the order/harness is already scanned on this station then it will show the
message as harness has already scanned.

© EMDEP 2024 Page 187

Emdep KSK Client / User’s guide

If the user closes this stage with OK button, then it closes the stage and moves to next step. And
shows the KSK scan order screen again to scan another order.

If the user closes this stage with NOK button, then it sends the harness to the rework stage. After
clicking on NOK button it shows following screen:

After clicking on this button it moves the order or harness to the rework stage.

If user again tries to scan this order without closing stage from rework stage it shows the error
screen. After closing it from rework. User can close the order on firewall stage with OK.

© EMDEP 2024 Page 188

Emdep KSK Client / User’s guide

Eyelet Squeezing Client

The Eyelet Squeezing Client is used to guide the process of squeezing an eyelet by telling the
operator which terminal and applicator to use, and to perform measurements if needed.

The first time this client is opened you will be shown the Configuration screen. More information
for the initial configuration in the section can be found in Installation and Configuration of Eyelet
Squeezing Client.

In order to run this application past the initial configuration screen, you need to have the
configured I/O Device connected at all times.

Login Screen
The first screen is the login screen, where the user will scan a barcode with their user.

Scan Order Screen

In this screen the user will have to scan the harness barcode in order to begin the squeezing
process.

In addition, a user can plug in a mouse to access the following sections:

• To access the configuration screen, where a qualified operator can configure

everything related to the client, the station, the terminals and the applicators.

• To access the maintenance screen, where you can see the presence of the
applicators and open/release both terminals and applicators.

© EMDEP 2024 Page 189

Emdep KSK Client / User’s guide

• To log out of the current user.

Maintenance Screen
In this screen, you can see the configured terminals and applicators, and their positions in their
respective grids. You can also see if each applicator is currently present or not.

In a terminal, you can press the button to open the specified terminal. Before exiting
this window, all terminals must be closed by pressing the button.

© EMDEP 2024 Page 190

Emdep KSK Client / User’s guide

In an applicator, you can press the button to release the applicator. You can then press
the to activate the pin that locks the applicator in place (or prevents inserting it, If
the applicator is not present). Before exiting this screen, all applicators must be present.

Logout Screen
Very similar to the login screen, here you can input the code specified in the configuration
window to log out of the system.

Squeezing Screen
Once a valid order has been scanned in the Scan Order Screen, you will see the following screen:

On the left side you can see all eyelets that you must squeeze, with the one you are currently
assembling marked in yellow. The terminal you must use (marked in the same color) will be
opened and the applicator (also marked in the same color) will be released. On the right side
you have all wires that must be assembled in the current eyelet.

Once an eyelet is assembled and the applicator returned to its place, the process will continue
for the next eyelets until all are squeezed.

© EMDEP 2024 Page 191

Emdep KSK Client / User’s guide

Sometimes, however, the process will require that the operator measures an eyelet. In this
event, the screen will show a message and the operator will have to measure the assembled
eyelet.

Two measurements must be performed: Conduction and Insulation. If one measurement fails
outside the parameters, the user will be informed with the following message:

Should two consecutive measures be invalid, the process will block the station and show the
Superuser Screen. A superuser must enter their user code to unblock the station and will be able
to perform unlimited measurements.

The superuser will also have the option to activate a manual keyboard to manually input the
measurement.

Once the process is finished, the program will return to the Scan Order Screen.

© EMDEP 2024 Page 192

Emdep KSK Client / User’s guide

COMMON FEATURES

© EMDEP 2024 Page 193

Emdep KSK Client / User’s guide

Reworking operations in test stations

When a harness is being inspected, assembled and/or tested in a station, is possible to discover
some defects (visually or due a test operations). When a defect is discovered should be
registered in KSK system and, if is possible, repaired. For the defects that cannot be repaired
directly in the station, should be sent to a rework area to a deeply inspection and repairing.

Adding defects to a harness

As commented in previous section, when a defect is detected should be registered in KSK system
and this action can be done from any type of station (assembly/test, dispatch or rework). To
simplify the operation, all stations uses the same screens and options.

1. The defect registration screen is accessed from any type of station, usually when the
processing is finished as NOK and the operator decides to register defects. In that case,
the defects registration screen will be shown.

2. Select the group of the defects in the Group list. The available defect types in the
selected groups will be listed in the right list.
3. Select the type of detected defect in the Detected defect list.
4. In field Description, add a brief description of the detected defect.
5. To save the current defect and add a new one, press Save and add new button in the
left panel.
6. To save the current defect and finish registering defects, press Save and exit button in
the left panel.
7. To cancel the current defect registry (and back to previous screen) press Cancel button
in bottom part of screen. Also, this action can be done by pressing the shortcut key
associated to the Cancel action (see Keyboard shortcuts).

© EMDEP 2024 Page 194

Emdep KSK Client / User’s guide

All registered defects will be stored in the order and could be checked using Emdep KSK Studio
or other software.
The groups and types of defects shown in this screen are stored in the current KSK project and
can easily be maintained using Emdep KSK Studio. Also, is possible importing the categories
defined in other KSK projects or exporting the existing ones to other KSK projects.

Repairing defects
The repairing harness defects screen shows all detected defects in the current scanned order.
The defects pending to be repaired appears in first position and with a warning icon, and the
repaired defects in last position and with check icon and green background.

1. Select a defect from the list.

2. The details for the selected defect will be shown in the bottom panel. If the defect is not
repaired, the panel will be painted in red. To set the defect as repaired, press Set as
repaired button.
3. If a new defect is detected, press Add new defect button from the left panel. The defects
registration screen will be shown (see how to proceed in Adding defects to a harness
section).
4. When all defects are processed or when a defect cannot be repaired:
• If all defects are repaired, the harness is automatically returned to the production
line following these rules:
▪ If no return step is defined, the harness is sent to first step again.
▪ If only one return step is defined, the harness is automatically sent to this
step.
▪ If more than one return step is defined, a new screen will appear to select
the returning step (taking in consideration the previous steps completed by
the order).

© EMDEP 2024 Page 195

Emdep KSK Client / User’s guide

• If the harness cannot be repaired and must be sent to scrap, press Unrepairable
button from the left panel. The harness will be set to UNREPARABLE status and a
harness scarped signal will be sent to the production system (SAP, etc.). At this point,
the harness is out of the line and cannot be processed in any station.

© EMDEP 2024 Page 196

Emdep KSK Client / User’s guide

Rework Report Viewer

Allows you to get Rework harness information from an interval of dates. At this moment, 3
different reports can be generated:

- Harness Waiting for rework

- Harnesses already repaired in the rework station
- Harnesses already Completed in reworks station

After selecting the report criteria, that is, the date interval and the type of report and select
station, press the “Load Report” button and information will appear on the grid. Please be aware
that this can take a while depending on the amount of data requested.

When data is on grid, exporting data to a CSV file and or printing data is possible just pressing
these options on the ribbon. This option is useful for example to make an exporting of defect
codes in mass way.

© EMDEP 2024 Page 197

Emdep KSK Client / User’s guide

Creating and configuring labels

Emdep KSK Client is able to print the rework labels for the harnesses before to be sent to the
rework area. For dispatch and module validation stations terminals (also in test stations if they
are of integrated type), these labels are usually mandatory to be printed and attached to the
processed harness.

Supported label printers and file formats

Emdep KSK System doesn’t support any specific printer model or label format to avoid
distributing third party drivers and to use certain printer models or label formats.

As usual in industrial environments, the used printers support RAW printing. RAW printing is
sending a string of commands to a printer directly in its native language. Many printers that are
popular support this. RAW printing bypasses the printer's drivers, making it very fast and
reliable. It is perfect for printing receipts, barcodes and labels. So, Emdep KSK System is
compatible with all printers supporting raw printing.

RAW printing languages

There is a wide variety of RAW printing languages, so before you start be sure to check with your
manufacturer which ones your printer supports. For example, Zebra printers commonly support
EPL and/or ZPL. The following are some of the most commonly used languages:

• ZPL - Zebra Programming Language

Widely popular in shipping, barcoding and labeling.
• EPL - Eltron Programming Language
Widely popular in shipping, barcoding and labeling.
• ESC/P - Epson Standard Code for Printing
The defacto standard for point of sales.
• FGL - Friendly Ghost Language
Popular with ticket printing, especially for Boca printers.
• DPL - Datamax Programming Language
Programming commands used specifically for control of and label production in
Datamax - O’Neil™ printers and popular in shipping, barcoding and labeling.
• CPCL - Comtec Printer Control Language
Popular with Mobile Printing

Labels and order information TAGs

As seen above, the label information is a group of mixed printing commands and information
(text, barcodes, etc.) that should be sent to printer. Emdep KSK System allows to introduce some

© EMDEP 2024 Page 198

Emdep KSK Client / User’s guide

TAGs inside the label information. Before to send, all TAGs will be replaced with the harness
information (order, module list, defects, operator, etc.). These TAGs are customizable, but
Emdep recommends to use the Wintestem™ variable acronyms (@STR01, @DSTR13, @NUM21, etc.
to be compatible with existing processes).

Creating a label
1. Open the settings dialogue of the current station and find the label selection list (in the
sample image, the rework label).

2. If there are no labels defined, press Label settings button, otherwise jump to step
XX. The Label settings dialogue will be shown.
3. Select the Printers tab page to check if the printer is present in the printers list.

Be sure that the printer is listed. If not, install the printer using the standard Windows
methodology or, if a serial printer must be used (connected to a COM port directly or
through USB), press Add new serial printer to create a new printer.
Also using the buttons Printer properties and Remove printer is possible to show
the printer properties dialogue or remove printers (serial only, it is not possible to
remove system printers using this option).
Before proceeding with the next step, make sure that the printer is able to print (use
the Print Test Page option from Windows printer properties page).

© EMDEP 2024 Page 199

Emdep KSK Client / User’s guide

4. When the printer is present and ready to print, select the Labels tab page.
5. Press Add new label button to create a new label definition. The Label properties
dialogue will be shown.

6. Specify the name, select the printer and the label file to be used.
7. In the tabbed section, specify all TAGs and variable ranges used in the label. Learn how
to specify the TAGs in Supported label TAGs section.
8. Press OK button to save the label definition for the current station and come back to
Label settings dialogue.
9. Press Close button to close the Label settings dialogue and come back to the station
settings dialogue.
10. In Label drop-down list, select the desired label.

© EMDEP 2024 Page 200

Emdep KSK Client / User’s guide

Supported label TAGs

General harness information

Field Description Typical TAG / Value

Order no. Harness order number @STR10

Operator name Operator name @STR09 (for code only)

Station name Station name @STR13

Date/Time Timestamp in (dd/MM/yyyy HH:mm format) -

Harness module list

Field Description Typical TAG / Value

Tag prefix Prefix for TAGs including module information @DSTRXX

Start index of the list

Starting index 01
One index for each module

Maximum index Maximum index allowed 90

Include part number The PN is always included -

Include revision Allows to add the revision to each module -

Include Q-Level Allows to add the QLevel to each module -

Example:
The following sample includes a list of modules in a label for a harness composed by 36 modules
and the label show, for each module, the part number, revision and Q-Level.

@DSTR01 → A9800003546;01;003
@DSTR02 → A9800047521;05;003
@DSTR03 → A9800064765;03;002
@DSTR04 → A9800038963;01;003
…
@DSTR36 → A9800095442;08;002

Harness reported defects

Field Description Typical TAG / Value

Tag prefix Prefix for TAGs including defect information @STRXX

Start index of the list

Starting index 41
Multiple indexes for each defect

Maximum index Maximum index allowed 70

Number of defects Number of defects @STR40

Include defects code Include group and incident codes -

© EMDEP 2024 Page 201

Emdep KSK Client / User’s guide

Both codes are included in a single TAG

Include group
Allows to add the defect group description -
description
Include incident
Allows to add the defect incident description -
description
Include operator Allows to add the description provided by the
-
description operator

Example:
The following sample includes a list of all non-repaired defects in a rework label. There are 5
defects and the label should show the defect codes and also the operator’s description for each
one.

@STR40 → 5
@STR42 → AM AM10
@STR43 → FIL DE PLUS ET MANQUE FIL
@STR45 → BB BB39
@STR46 → Connecteur endomage
@STR45 → AW AW26
@STR46 → Manque fil

© EMDEP 2024 Page 202

Emdep KSK Client / User’s guide

Validating a station in KSK project

After installing Emdep KSK Client software and creating the station the best practice is to
validate the basic flow into the KSK project. To do this task the Emdep KSK Studio is needed.

1. Get some valid orders for testing (never use production orders without the consent of
the responsible personnel).
2. Open the Emdep KSK Studio software (better in a different computer than the station
computer), connected to the same KSK project as the station under test.
3. Open the Validation → Staging test plug-in and load the order, the line where the
station is placed and a user account with permissions in the station(s) we’re going to
check.
4. Press start to show the current status of the selected order in the selected line.

5. Move the order to the stage where the station is placed. To move the order, show the
contextual menu in the step (header) and select Set next step here.

6. In the station, open the Wintestem™ and start the generated process (PRG file).
7. Proceed with the following tests:

© EMDEP 2024 Page 203

Emdep KSK Client / User’s guide

a. Test OK
b. Test NOK → Repeat test
c. Test NOK → Defects detected → All defects repaired in the station
d. Test NOK → Defects detected → Send to rework
8. After each test, check in Emdep KSK Studio that the order is in the correct position and
status. To change from one test to another, repeat the step 6.
9. Perform the tests with almost 2 or 3 orders before validating the station.

In general, and if it is possible, check entire line(s) flow to validate the entire layout before to
put a project in production (without assembly/test operations). This is the best way to validate
all KSK software without interferences from other software.

Logging and diagnostics

Activating logs
In computing, a log file is a file that records certain events that occur in a software system and
keep this information in a log file. Event logs record events taking place in the execution of a
system to provide an audit trail that can be used to understand the activity of the system and to
diagnose problems.

Emdep KSK Client have a built-in logging system that can be enabled if it is necessary in a simple
and clear way.

1. In the Windows Start Menu, in the Emdep KSK folder, open the Client Station
application.

2. Select the Logging tab page.

3. Setting File logger:

© EMDEP 2024 Page 204

Emdep KSK Client / User’s guide

a. Check the File logger enabled option to activate the file logger.

b. Select the log level from the Level drop-down list.

c. By default, the log files will be generated in the installation folder. If you want
to use another location, you must specify it in the Path field.

4. Settings Windows logger:

a. Check the Windows logger enabled option to activate the Windows logger.

b. Select the log level from the Level drop-down list.

c. Set the name and the source for all log events recorded. The name is the main
group of events (for example, KSK System) and the source is a reference to the
software that is generating the record (for example, Test station).

5. Press OK button to store the settings.

6. Start the station (depending on the type of the station, from Wintestem™ or directly
from EXE file) and check if the software is registering logs by checking the generated file
and/or the generated Windows Event Viewer entries.

Activating memory usage logs

Another tools that can be useful to diagnose memory problems is the memory usage log. This
utility generates a file for each day adding a timestamp, an application/library name, a
section/method name and the CPU and memory usage (same information we have available in
Windows Task Manager). These files easily can be loaded using Microsoft Excel allowing filters,
charts, etc. The CSV files will be generated in a new folder METRICS, inside the installation folder.

1. In the Windows Start Menu, in the Emdep KSK folder, open the Client Station
application.

2. Select the Logging tab page.

© EMDEP 2024 Page 205

Emdep KSK Client / User’s guide

3. Check the option Generate CSV files with system metrics.

4. Press OK button to store the settings.

5. Start the station (depending on the type of the station, from Wintestem™ or directly
from EXE file) and check if the software is registering logs by checking the generated
files.

Diagnosing problems with libraries

The KSK software is usually working under Wintestem™ and combined with other software like
Vision Tools, Components Assembly, etc. When KSK software is installed (or updated) in an
assembly/test station, can appear issues usually related to incompatibility between libraries
from a huge variety of versions and platforms.

For this kind of problems, the Emdep KSK Client include a utility to get information related to all
installed, used and shared components. It can be useful to diagnose a problem caused when
other software load (or use) old libraries.

1. The diagnostic tools are integrated into the About dialogue and can be accessible
through two distinct ways:
• Clicking on the About this software link, in the configuration application.

• Clicking in the EMDEP logo on the assembly/test screens.

© EMDEP 2024 Page 206

Emdep KSK Client / User’s guide

After clicking the appropriate link or logo, the About this software will be shown.

2. In the Loaded .NET assemblies tab page, a list of loaded assemblies (DLL and EXE files
used by the application) can be checked.
3. In the Shared COM objects tab page all shared components can be checked. All shared
components must show a green icon, otherwise it indicates that some component is not
correctly registered and must be registered manually (or reinstalled with a newer
version of the Emdep KSK Client software).

4. Also, a report containing the list of the files included in the installation folder can be
generated by pressing the Generate component report button.

© EMDEP 2024 Page 207

Emdep KSK Client / User’s guide

DEVELOPER
INFORMATION

© EMDEP 2024 Page 208

Emdep KSK Client / User’s guide

Shared interfaces
The Emdep KSK Client software exposes some public interfaces as COM object to use it with
Emdep Wintestem™ processes through VBScript or other compatible technologies (such C# or
VB.NET).

Most interface methods have an associated VBScript file that can be used from Emdep
Wintestem™. These scripts are ready to use and are delivered as a part of Emdep KSK Client
(usually in folder C:\Emdep-2\KSK\Client\Scripts).

KSK Client interface

This interface provides a basic methods and properties to manage the orders flow into the
stations / lines and some methods to get basic KSK project data (order composition, etc.).

ProgID KSKClient.Engine
File KSKClient.dll
Format .NET framework

Properties
Name Type Accessors Description
ConnectionString String Set Sets the connection string used to connect to KSK
database.
ClientSAP String Set [OBSOLETE] Maintained for compatibility purposes.
ErrorMessage String Get Gets the last error message.
HarnessFields String Get Gets the information obtained calling the method
GetHarnessFields.
IndependentLines Boolean Set Sets a value indicating if the layout operating mode
should be set to independent lines.
LanguageCode String Get / Set Gets or sets the current language code for the
translated messages.
NeedsToValidate String Set [OBSOLETE] Maintained for compatibility purposes.
PasswordSAP String Set [OBSOLETE] Maintained for compatibility purposes.
ServerSAP String Set [OBSOLETE] Maintained for compatibility purposes.
UserSAP String Set [OBSOLETE] Maintained for compatibility purposes.

Methods

CloseStage

Close stage for a harness order in the specified station.

Parameters String Harness order.
String KSK project name.
String Line name.
String Station name.
Integer The result of the test:

© EMDEP 2024 Page 209

Emdep KSK Client / User’s guide

▪ 0 = NOK
▪ 1 = OK
String Language code for the messages.
Return Integer OK (1) if the call is executed without errors or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

CloseStage With Simulation

close stage for a harness order in the specified station without checking any condition.
It has same parameters like close stage. Just we need to add one prefix in Order which is predefine in
Database in Misc table with Key (harness.simulation.prefix).

CloseStageCluster

Close stage for a harness order in the specified cluster’s master station.
Parameters String Cluster ID.
String Harness order.
String KSK project name.
String Line name.
String Station name.
Integer The result of the test:
▪ 0 = NOK
▪ 1 = OK
String Language code for the messages.
Return Integer OK (1) if the call is executed without errors or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

GetHarnessFields

Gets a harness information from the specified record field or SQL expression.
Parameters String Harness order.
String Column name or SQL expression used in SELECT column.
String Language code for the messages.
Return Integer OK (1) if the call is executed without errors (the requested information
will be stored in property HarnessFields) or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

© EMDEP 2024 Page 210

Emdep KSK Client / User’s guide

GetHarnessHasBeenInReworks

Gets if a harness has previously been at rework.

Parameters String Harness order.
Return Integer 1 = Harness fas previously been at rework.
0 = Harness has not previously at rewirk.
String Case can not connect to datab
INTERNAL ERROR: Unable to connect to KSK database! Please check
connection settings, network connectivity or server status.

Incorrect harness:
Harness [providedHarness] not found in KSK system.

Correct harness without rework:

Harness has previously been at rework.

Correct harness with rework:

Harness has not previously been at rework.

GetMatchingKSK

Returns the first order number matching the specified pattern.

Parameters String Find pattern (compatible with standard SQL).
String Language code for the messages.
Return String The requested order number or an empty string if no order can be found.

GetNextStation [OBSOLETE]

NOT IMPLEMENTED. Maintained only for compatibility purposes.

Parameters String KSK project name.
String Order number.
Boolean A value indicating if the layout operating mode should be set to
independent lines.
String Language code for the messages.
Return String A string containing the name of the next planned station for the specified
order or an empty string if no planned station was registered for the
specified order.

© EMDEP 2024 Page 211

Emdep KSK Client / User’s guide

GetQLevel

Gets the Q Level information for a harness module.

Parameters String Harness order.
String Module part number.
String Module revision.
String Language code for the messages.
Return Integer OK (1) if the call is executed without errors (the requested information
will be stored in property HarnessFields) or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

GetUserName

Gets the user name from his private code.

Parameters String User private code.
String Language code for the messages.
Return String The requested user name or an empty string if the user cannot be found.

IsValidUser

Check if the specified user exists and have the specified role.
Parameters String Role name.
String User private code.
Return Integer OK (1) if the user exists and have the specified role or NOK (0) if there was
a problem. In that case, the property ErrorMessage will be set with a
description of the error.

ModulesToString

Gets a list of harness modules (part number) in a CSV list.

The format of list is: MODULE1;MODULE2;MODULE3
Parameters String Harness order.
String Language code for the messages.
Return String The requested CSV list of modules or an empty string if the order cannot
be found.

© EMDEP 2024 Page 212

Emdep KSK Client / User’s guide

ModulesWithRevisionToString

Gets a list of harness modules (part number and revision) in a CSV list.
The format of list is: MODULE1:REV1;MODULE2:REV2;MODULE3:REV3
Parameters String Harness order.
String Language code for the messages.
Return String The requested CSV list of modules or an empty string if the order cannot
be found.

ModulesWithRevisionAndQLevelToString

Gets a list of harness modules (part number, revision and Q-Level) in a CSV list.
The format of list is: MODULE1:REV1:QL1;MODULE2:REV2:QL2;MODULE3:REV3:QL3
Parameters String Harness order.
String Language code for the messages.
Return String The requested CSV list of modules or an empty string if the order cannot
be found.

NumberOfWires

Gets the number of the wires using a specified connector and way.
Parameters String Harness order.
String Connector name (ID).
String Connector part number.
String Connector way name.
String Language code for the messages.
Return Integer The requested number of wires.

NumReworksAfterElectric

Gets the number of harnesses in rework station after electrical test.

Parameters String Harness order.
String Language code for the messages.
Return Integer The requested number of harness orders.

© EMDEP 2024 Page 213

Emdep KSK Client / User’s guide

OpenStage

Open stage for a harness order in the specified station.

Parameters String Harness order.
String User private code.
String KSK project name.
String Line name.
String Station name.
Boolean A value indicating if the layout operating mode should be set to
independent lines.
String Language code for the messages.
Return Integer OK (1) if the call is executed without errors or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

OpenStage With Simulation

Open stage for a harness order in the specified station without checking any condition.
It has same parameters like open stage. Just we need to add one prefix in Order which is predefine in
Database in Misc table with Key (harness.simulation.prefix).

OpenStageCluster

Open stage for a harness order in the specified cluster’s master station.
Parameters String Cluster ID.
String Harness order.
String User private code.
String KSK project name.
String Line name.
String Station name.
Boolean A value indicating if the layout operating mode should be set to
independent lines.
String Language code for the messages.
Return Integer OK (1) if the call is executed without errors or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

© EMDEP 2024 Page 214

Emdep KSK Client / User’s guide

OrderNeedsToValidate

Check if the current order has modules non-validated. For order with non-validated modules, if there
are PPAP stations defined, the order is sent to PPAP station. If not, the method returns the list of non-
validated modules.
Parameters String Harness order.
String KSK project name.
String Line name.
String Station name.
String Language code for the messages.
Return Integer An integer indicating the result of the operation:
1 → The order contains non-validated modules
2 → All modules in the current order are validated
0 → An internal error occurred (property ErrorMessage will be updated
with the description).

SendHarnessToPreviousStation

Send a harness to a previous station.

This method automatically close as NOK the current opened step (if any), so it is not required to call
CloseStage method after calling it and send the harness to a selected previous station.
Parameters String Harness order.
String Language code for the messages.
String Source station name.
String Destination station name.
Return Integer OK (1) if the call is executed without errors or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

SendToRework

Send a harness to an available rework station.

This method automatically close as NOK the current opened step (if any), so it is not required to call
CloseStage method after calling it.
Parameters String Harness order.
String Language code for the messages.
String Station name.
Return Integer OK (1) if the call is executed without errors or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

© EMDEP 2024 Page 215

Emdep KSK Client / User’s guide

UserIsValid

Check if a specified user code is valid.

Parameters String User private code.
String Language code for the messages.
Return Integer OK (1) if the call is executed without errors or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

WireExists

Check if a wire is used in one or more modules of the specified order.

Parameters String Order number.
String Wire name.
String Language code for the messages.
Return Boolean A value indicating if the wire is included in the specified order or not.

The following list of methods are obsolete and only are maintained in the interface to ensure
backward compatibility. Please, don’t use these methods in production environments.

GetHarnessColumn [OBSOLETE]

Equivalent to GetHarnessFields.
Maintained only for compatibility purposes.
Parameters String Harness order.
String Column name or SQL expression used in SELECT column.
String Language code for the messages.
Return Integer OK (1) if the call is executed without errors (the requested information
will be stored in property HarnessFields) or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

GetHarnessInfo [OBSOLETE]

Gets the harness current QSS1/QSSE K0 segment information.

This method is currently not used because he clients cannot communicate directly with production
systems (SAP, etc.).
Parameters String Harness order.
String Language code for the messages.
Return String A string containing the requested order K0 segment or an empty string if
the order cannot be found.

© EMDEP 2024 Page 216

Emdep KSK Client / User’s guide

ReturnFromRwork [OBSOLETE]

Send back to the line a reworked harness.

This method is currently not used because the rework screens included in the client software move the
harness to the destination station automatically.
Parameters String KSK project name.
String Destination station name.
String Harness order.
String User private code.
String Language code for the messages.
Return Integer OK (1) if the call is executed without errors or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

ScanConnectorCodes [OBSOLETE]

NOT IMPLEMENTED.
This method is currently not used and will be removed in future versions. Maintained only for
compatibility purposes.
Parameters String Order number.
String Box connector name (ID).
String Station name.
String User private code.
Return Integer OK (1) if the call is executed without errors or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

SetHarnessTested [OBSOLETE]

Set the harness status to TESTED.

This method is currently not used and will be removed in future versions. The status is automatically
changed when a stage is closed in last station and all status are managed internally by KSK system.
Parameters String Harness order.
String Language code for the messages.
Return Integer OK (1) if the call is executed without errors or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

© EMDEP 2024 Page 217

Emdep KSK Client / User’s guide

SetUnrepairable [OBSOLETE]

Set the harness status to UNREPAIRABLE.

This method is currently not used and will be removed in future versions. The status is automatically
changed when a stage is closed in last station and all status are managed internally by KSK system.
Parameters String Harness order.
String Language code for the messages.
Return Integer OK (1) if the call is executed without errors or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

TestData [OBSOLETE]

Gets a test data from a harness order.

Equivalent to GetHarnessFields. Maintained only for compatibility purposes.
Parameters String Harness order.
String Language code for the messages.
Return String The requested TestData from the specified order or an empty string if
the order cannot be found.

UpdateHarnessSap [OBSOLETE]

NOT IMPLEMENTED.
This method is currently not used and will be removed in future versions. Maintained only for
compatibility purposes.
Parameters String Language code for the messages.
Return Integer OK (1) if the call is executed without errors or NOK (0) if there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

SaveHarnessDMC

Set a harness DMC Code. It is used in the script KSK_SaveHarnessDMC.vbs

Parameters String hnsOrder
String dmcCode
String language
Return Boolean True if the dmcCode could be saved successfully, false otherwise.

© EMDEP 2024 Page 218

Emdep KSK Client / User’s guide

CheckHarnessDmcExists

Checks if a DMC code exists in the database. You can include a list of positions that will be ignored in
the comparison. It is used in the script KSK_CheckIfExistsDMC.vbs
Parameters String dmcCode
Integer ignoredPositions
Array
Return Boolean True if there is a DMC code equivalent to the parameter, false otherwise.

KSK Rework interface

This interface provides an integrated functionality for the rework flow in test stations.

ProgID KSKRework.Engine
File Emdep.KSK.Terminal.Core.dll
Format .NET framework

Properties
Name Type Accessors Description
ConnectionString String Get, Set Gets or sets the connection string used to
connect to KSK database.
ErrorMessage String Get Gets the last error description.
MaxReworksAllowed Integer Set Sets a value indicating the maximum number of
rework tasks allowed for one harness.
PendingErrors String Get Gets a string containing all pending to repair
defects.

The format used by the property PendingErrors after ShowDefectsRework method is called is:

NumReworks=XX@#@GroupCode1;GroupDesc;IncidentCode;IncidentDesc;OperatorDesc@#@...

The separator used is the constant string @#@. In case of the harness doesn’t have pending
defects, this property will be set to:

NumReworks=XX

Methods

ShowDefectsRecorder

Open the harness defects recorder screen to allow an operator to add defects to the current harness.
Parameters String Harness order.
String Current user code.

© EMDEP 2024 Page 219

Emdep KSK Client / User’s guide

Return Boolean A value indicating if the call is executed without errors or there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

ShowDefectsRework

Open the harness defects repairing screen to allow an operator to inform about repaired defects for
the current harness.
After calling this method, the property PendingErrors will be set with all pending defects.
Parameters String Harness order.
String Current user code.
Return Boolean A value indicating if the call is executed without errors or there was a
problem. In that case, the property ErrorMessage will be set with a
description of the error.

KSK Terminal interface

This interface provides a couple of integrated screens and features and is basically used by the
stations created as an integrated station.

ProgID KSK.Terminal
File Emdep.KSK.Terminal.Core.dll
Format .NET framework

Properties
Name Type Accessors Description
CurrentHarnessOrder String Get Gets the current scanned order.
CurrentUserCode String Get Gets the current authenticated user code.
IsExitRequested Integer Get Gets a value indicating if the user has been
requested to exit the current process.
IsLoginRequested Integer Get Gets a value indicating if the user has been
requested to perform a logout (change
authenticated user).
LastErrorMessage String Get Gets the last error description.
LineName String Get Gets the name of the line where the station is
placed (from the settings.xml file).
ProjectName String Get Gets the name of KSK project (from the
settings.xml file).
StationName String Get Gets the name of the station (from the
settings.xml file).

Methods

EndSession

© EMDEP 2024 Page 220

Emdep KSK Client / User’s guide

Finish the active working session.

Parameters String Current user code.
String Harness order.
Boolean A value indicating if the test result was OK or NOK.
Return Boolean A value indicating if the call is executed without errors or there was a
problem. In that case, the property LastErrorMessage will be set with
a description of the error.

ProcessDefects

Start a defects processing process for the specified harness.

Parameters String Current user code.
String Harness order.
Return String A string with all the defects pending to be repaired or “Reworks=0” if all
defects are solved.

Settings

Open the settings dialogue for the current station.

Parameters - -
Return Boolean A value indicating if the call is executed without errors or there was a
problem. In that case, the property LastErrorMessage will be set with
a description of the error.

StartSession

Start a new working session.

Parameters String Current user code.
Return Boolean A value indicating if the call is executed without errors or there was a
problem. In that case, the property LastErrorMessage will be set with a
description of the error.

TestBuildFiles

Generate the test files using the current station configuration.

Parameters String Harness order.
Return Boolean A value indicating if the call is executed without errors or there was a
problem. In that case, the property LastErrorMessage will be set with a
description of the error.

TestCleanFiles

© EMDEP 2024 Page 221

Emdep KSK Client / User’s guide

Remove the generated test files for the specified harness.

Parameters String Harness order.
Return Boolean A value indicating if the call is executed without errors or there was a
problem. In that case, the property LastErrorMessage will be set with a
description of the error.

© EMDEP 2024 Page 222