EFKA Industry 4

®

EFKA Industry 4.0

USER MANUAL

© 2019 BIASYS Systempartner GmbH

2

EFKA Industry 4.0 © 2019 BIASYS Systempartner GmbH

Table of Contents

1. Introduction 4

2. Biasys I4 Frontend 7

2.1 Frontend Login .................................................................................................................... 8

2.2 Frontend Application ........................................................................................................ 10

Management ............................................................................................................... 102.2.1User .................................................................................................................................................................. 122.2.1.1

Machine .......................................................................................................................................................... 132.2.1.2

Service Call ID ................................................................................................................................................ 142.2.1.3

Sewing Machine Group ................................................................................................................................ 162.2.1.4

Add or Remove Machine ........................................................................................................................ 192.2.1.4.1

Get Parameter File from DB ................................................................................................................... 202.2.1.4.2

Production ................................................................................................................... 212.2.2Machine Status .............................................................................................................................................. 222.2.2.1

Machine Detail ........................................................................................................................................ 252.2.2.1.1

Machine Status Log ................................................................................................................................. 262.2.2.1.2

Service ....................................................................................................................................................... 272.2.2.1.3

Single Parameter <= Machine ....................................................................................................... 292.2.2.1.3.1

Selected Parameter by File <= Machine ...................................................................................... 302.2.2.1.3.2

Selected Parameter <= Machine ................................................................................................... 322.2.2.1.3.3

All Parameter <= Machine ............................................................................................................. 342.2.2.1.3.4

Single Parameter => Machine ....................................................................................................... 352.2.2.1.3.5

Selected Parameter by File => Machine ...................................................................................... 372.2.2.1.3.6

All Parameter => Machine ............................................................................................................. 382.2.2.1.3.7

Parameter File <=> Database ........................................................................................................ 402.2.2.1.3.8

Set Piece Counter ............................................................................................................................. 432.2.2.1.3.9

Set Service Counter .......................................................................................................................... 432.2.2.1.3.10

Save Parameter File ........................................................................................................................ 442.2.2.1.3.11

All Active Service Calls ........................................................................................................................... 452.2.2.1.4

Statistic ........................................................................................................................................................... 462.2.2.2

Service Call Log .............................................................................................................................................. 482.2.2.3

Settings ........................................................................................................................ 502.2.3Window Configuration ................................................................................................................................ 512.2.3.1

Setup ................................................................................................................................................................ 522.2.3.2

Language Setup ........................................................................................................................................ 522.2.3.2.1

Communication Server Setup ................................................................................................................ 522.2.3.2.2

Frontend Server Setup ............................................................................................................................ 532.2.3.2.3

House Keeping ......................................................................................................................................... 562.2.3.2.4

Archive Data ..................................................................................................................................... 582.2.3.2.4.1

Touch Mode Setup ................................................................................................................................... 602.2.3.2.5

3. EFKA Communication Server 62

3.1 Efka Communication Server Login ................................................................................... 63

3


Table of Contents

3.2 Efka Com Server Application ............................................................................................ 65

4. Log From DB 66

5. Log Viewer 69

6. Database 73

6.1 i4_management ................................................................................................................. 74

User - Table ................................................................................................................. 756.1.1

Machine - Table .......................................................................................................... 776.1.2

Other - Table ............................................................................................................... 796.1.3

6.2 i4_production .................................................................................................................... 82

DailyStatistic - Table ................................................................................................... 846.2.1

MachineStatus - Table ................................................................................................ 856.2.2

Other - Tables ............................................................................................................. 876.2.3

Tables for pass-through command / responses to sewing machine control box and vice versa ..... 916.2.4

Index 0

Introduction

5


Introduction

1 Introduction

This document is the user manual for the EFKA Industry 4.0 Software Solution (also called as Efka

BigData).

Efka I4 solution inter connects the sewing machines equipped with Efka Control Boxes

(e.g.ABxxxxx). It acquires the 'sewing data' as specified below from the connected Control Boxes:

· The detailed sewing information

· Service calls generated by the control box itself or by the operator on the sewing machine or

by the sensors connected to the machine

Efka I4 solution stores the acquired 'sewing data' to the database. It computes the statistics based

on the acquired 'sewing data' and maintains the sewing 'parameter data sets' in the database.

'parameter data sets' are the parameters related to the product to be produced on the machines.

Upload/download of 'parameter data sets' from/to the sewing machine control boxes are

possible from this Efka solution. It maintains a machine database and user database for the

sewing machine operators and the sewing machine service technicians.

Efka I4 solution provides data logging, which is a process of storing data over a period of time in

order to analyze application mechanism during the application information or errors. This log data

can be analyzed by reading the log files by the log viewer software as shown in Log Viewer

The solution mainly consists of the following software components:

· Server

Server is equipped with specific software application programs. Server is enabled to provide

services to the program called clients on its network. Server program accepts and responds to

the request made by the client on its network. The main function of a server is to store, retrieve

and manage all the application data in the database. Efka software solution contains server

application called 'EFKA Communication Server' also called as 'Com Server' as shown in Efka

communication server . Com server application provides service by responding to the

request made by the clients on the specific network IP Address.

· Client

Client is a device or software that access a service or resources shared by a server. The clients in

Efka software solution are as follows:

- Control Boxes

70

63

6


Introduction

- Frontend application as described in Biasys I4 Frontend

These control boxes and the frontend application are connected to the com server on a specific

network IP Address and port number. The data communication like sending and receiving

message between server and client application is recorded by the software in MySql database.

8

Biasys I4 Frontend

8


Biasys I4 Frontend

2 Biasys I4 Frontend

Introduction

Frontend is a Graphical User Interface (GUI) application, to manage the sewing machine data in

the database. The data acquired by the com server application during the production is stored in

the database, this particular data is read by the frontend application.

Frontend maintains the detail view of all the connected control boxes to the com server

application. User has the permission to insert or update the data values to the specific data

tables. It enables the grouping of sewing machines and to set the parameter from file based on

sewing machine groups. The service calls generated from the machine or the operator can be

handled using frontend. The performance of the sewing machine or the sewing machine user are

evaluated by the software. It also monitors the time taken by the mechanic to service the sewing

machine during the service call. It provides the data backup and cleanup functionality to maintain

old data during the specific time period. In general, frontend application reads the complete

sewing data from the database where user can access this data or insert the new data into the

database.

Remark: When frontend application is starting for the first time, it must be started as an

administrator twice because of application license.

2.1 Frontend Login

Introduction

On the start of the frontend application, the frontend login window pops up. The user must login

with the database server credentials in this window. The frontend application mechanism is

logged, in case of any errors or information.

9


Biasys I4 Frontend

Frontend Login Window

Description

Frontend login window contains the MySQL database server credentials which must be filled by

the operator to access the frontend application. The operator must make sure about the database

server host and the user details, where the Efka I4 production data is present in the MySQL

workbench.

· Database server host: Database server name to which the frontend application must be

connected to retrieve the data

· User Name: User name which is specified in the database user accounts in the 'Users and

Privileges' section of MySQL workbench

· Password: Password specified for the respective user name in the database

- If the password does not exist for the particular user, this field can be empty

Once the database server host, user name and password entered, the database connection can be

verified by clicking Check button. If the database connection is successful for the entered

credentials, the following window is displayed:

If the database connection does not exists for the entered credentials, the following window is

displayed

10


Biasys I4 Frontend

· Application Logging: Frontend application logging information stores the frontend application

information or application errors. The frontend application information is logged based on the

option selected as follows:

- Log All: Logs all the frontend application data

- Only Errors: Logs only the error messages

- Errors and Last Infos: Logs only errors and the last information

- No Logging: No logging of any data in the frontend application

When all the required fields are entered, click Login button to start the frontend application

Button Description

Checks the database connection for the entered values and display the result

Login· Applies the database credentials entered

· Starts the frontend application if the database connection was successful or elsedisplay the error window

Cancel Exits the complete program

2.2 Frontend Application

Front End application has three main sections:

· Management

· Production

· Settings

2.2.1 Management

Introduction

11


Biasys I4 Frontend

Management section contains the primary data related to the sewing machine and the sewing

machine user. The data in this section is inserted or modified by the com server application or by

the frontend operator.

Industry4 Front End (Management Section)

Description

The four main forms of the Management section are:

· Users

· Machine

· Service Call ID

· Sewing Machine Group

12


Biasys I4 Frontend

2.2.1.1 User

Introduction

The User form is the list of sewing machine user information. The sewing machine user could be

either an operator or a mechanic, explained as follows:

- Operator: The one who operates the sewing machine to perform the sewing task

- Mechanic: The one who services the sewing machine during the service calls

The administrator of the system must enter all the user data in the user table before any user can

login to the sewing machine. This form permits the user to add, delete or update data to the

database.

Management - User Form

Description

· RFID: ID from the RFID chip or the value entered in the efka variocontrol device during the

user login

- The RFID value must always be a 10 digit value

- Example: If the value entered in Efka variocontrol = 1234

- The RFID value in the user table will be = 0000001234

- The RFID field is formatted automatically to the 10 digit value once the mouse is clicked

out of the RFID field

· Real User Name: Full name of the sewing machine user

· Short User Name: Short unique user name, this is the name displayed in the EFKA variocontrol

(must be a unique value)

· Description: Enter the description for the particular user entered (The field value can also be

empty)

13


Biasys I4 Frontend

· EFKA User Group: Select if the user is an Operator or Mechanic from the drop down box

appeared

Click the save button to save the user data entered in the table. The user can also edit the old

data in the table.

Button Description

Refreshes the User data tableReverts any unsaved changes made to the table

Saves the changes made in the User table to the database

Exports the User data in the table to Excel file

2.2.1.2 Machine

Introduction

Machine table is the list of sewing machines connected to the com server application. Machine

table contains the detailed information regarding all the sewing machines that are connected to

the com server application. The data in this table is entered by the communication server (com

server) application when the new machine is connected.

Management - Machine Form

Description

· Machine ID: Sewing machine ID - Must be entered to the Efka control box by 799

· Server ID (Non-Editable): IP Address of the connected communication server

· Circuit Board No (Non-Editable): Sewing machine Circuit Board Number

· Serial No (Non-Editable): Efka control box Serial Number

· IP Address (Non-Editable): IP Address of the sewing machine control box connected to the com

server application

14


Biasys I4 Frontend

All the above values are inserted by the com server application when the connection is

established between the com server and the sewing machine client control box.

· Description (Editable): This is the only field editable by the user in Machine table and can save

the changes to the database

- The default value of this field is 'NEW RECORD' which is entered by the software

- Any particular description for the specific machine can be entered and saved

Button Description

Refreshes the Machine data tableReverts any unsaved changes made to the table

Saves the changes made in the Machine table to the database

Exports the Machine table data to Excel file

2.2.1.3 Service Call ID

Introduction

Service Call ID table is the list of detailed information of the complete service call. The service

calls are generated either by the sewing machine or by the sewing machine operator or by the

sensors connected to the machine. Each service call have a unique ID mentioned in this table.

Example: The following are the service calls generated from the operator during:

· Broken needle

· Broken Bobbin

· Broken knife

· Refill oil

· Broken thread

15


Biasys I4 Frontend

Management - Service Call ID Form

Description

· Service call ID (Non-Editable): Each service call event is identified by this unique ID

- Service call ID is the service call number attached to a service call message

· Service call Event (Editable): Each respective ID has a unique event, which specifies what each

service call means

- This field can be modified and saved to the database

· Source (Non-Editable): Specifies the owner of the service call who can send the particular

service call event

· Category (Editable): Specifies the priority level of each service call event, which are categorized

as follows:

16


Biasys I4 Frontend

- High Priority

- Middle Priority

- Low Priority

This priority can be configured based on the customer requirements. This field can be modified in

this table.

Button Description

Refreshes the Service Call ID data tableReverts any unsaved changes made to the table

Saves the changes made in the Service Call ID table to the database

Exports Service Call ID table data to Excel file

2.2.1.4 Sewing Machine Group

Introduction

Sewing Machine Group table is the list of sewing machine group and its corresponding list of

machines in the particular sewing machine group. This form contains sewing machine group table

and a detail table as follows:

· Sewing machine group table contains the sewing machine group based on the specific

requirements

· Detail table contains the list of machines present in the particular sewing machine group

These grouped machines are used to set the parameters from file. Setting parameter for the

particular group is possible once the parameter files are attached to the list of machines in the

particular group.

17


Biasys I4 Frontend

Management - Sewing Machine Group Form

Description

User can create a new sewing machine group with unique 'Group Name' and specific 'Description'.

Step by step procedure to add the sewing machine to the particular group and to add the

parameter file for the respective sewing machine are as follows:

To add the sewing machine to the selected group

· Select the particular sewing machine group and click button to add the sewing machine to

the selected group

- By clicking on Add or Delete Machine button will open the form with the list of sewing

machines as shown in Add or Remove Machine

To add the parameter file to the selected machine

· Select the machine rows (to select multiple machine use 'ctrl' or 'shift' button) in the group

- Click Add Parameter File button to select the parameter file for selected machine

19

18


Biasys I4 Frontend

- Add Parameter File button will open the form with list of parameter files from the

database as shown in Get Parameter File from DB

- Same parameter file can be attached to one or many machines in the group

· After adding parameter files to all the machines in the group, click Save button and click

Set Parameter button which displays the confirm window as shown below

- Click 'Yes' to continue to set parameter for the selected group of machines or else click 'No'

· If 'Yes' button is clicked, the progress window will arrive as shown below

- The window specifies the machine ID of currently processing sewing machine

- Once the process is completed the following window is closed

- The whole set parameter process can be canceled at any time by clicking 'Cancel' button

- If the cancel button is clicked, the set parameter process stops for the particular sewing

machine group and the following window is closed

While setting parameter, the 'Progress' column of the machine detail table display the progress

set parameter process

· The count displayed in the 'Progress' column is the set parameter count for the respective

machine and the parameter file

· The 'Progress' column display one of the status as shown below, once the set parameter

process is executed for the particular sewing machine group

- Completed: The set parameter process is set successfully

- No Parameter File: The parameter file is not added for the particular machine

20

19


Biasys I4 Frontend

- Canceled: The set parameter process is canceled by the user

- Failed: The set parameter process failed

Sewing Machine Group Form: Set Parameter Process

Button Description

Refreshes Sewing Machine Group data table Reverts any unsaved changes made to the table

Saves the changes made in the Sewing Machine Group table to thedatabase

Exports Sewing Machine Group data in the table to Excel file

Add or Delete Machines from the Selected Group

Add Parameter file for the selected Machine

Sets parameter for all the machine in the selected group

2.2.1.4.1 Add or Remove Machine

Introduction

20


Biasys I4 Frontend

Add or Remove Machine table is the list of all sewing machines connected to the com server

application. It provides the detail information of the sewing machine. In this form user has the

option to insert or remove the sewing machine from the particular sewing machine group.

Description

· To add the machine to the selected group, click on the 'Selection' field (tick mark means

selected) and click OK button

· To remove the machine from the selected group, click on the 'Selection' field (click on the tick

mark to remove) of particular machine to be removed and click OK button

· If 'Cancel' button is clicked, this form is closed without any modifications to the selected sewing

machine group

Add Machine or Remove Machine

2.2.1.4.2 Get Parameter File from DB

Introduction

Get Parameter File from DB table is the list of parameter files in the database. Only one

parameter file can be selected from this table. The selected parameter file data is retrieved to

the selected sewing machine.

Description

21


Biasys I4 Frontend

· Click on the parameter file to view the data of that particular file in the field below the

parameter file list

· The selected file name is displayed in the region below the parameter file list

· Select one parameter file in the list, and click this button

· The data from the selected parameter is retrieved for all the selected machine

· Or double click on the particular parameter file row to get the file data to the selected machine

Get Parameter File from Database

2.2.2 Production

Introduction

Production section contains the current production data of all the sewing machines connected to

the com server. It provides an overview of complete sewing data stored in the database. The data

in the production section cannot be modified. It monitors the status of the connected machines.

22


Biasys I4 Frontend

The data are categorized based on the user or machine. It provides statistics based on sewing

machine or sewing machine user. It maintains the service call information of the sewing machine.

Description

The three main formulas of Production section are:

· Machine Status

· Statistic

· Service Call Log

Industry4 Front End (Production Section)

2.2.2.1 Machine Status

Introduction

Machine Status table is the list of sewing machines and its current status. The list of sewing

machines are the sewing machines which are connected to the com server. The table contains the

detailed information of the connected sewing machines.

23


Biasys I4 Frontend

Machine status form contains four sub forms which gives a detailed description of the data in the

machine status table. Each machine detail can be viewed independently. It maintains the

machine statistics of each sewing machine. It provides specific service functionality for each

sewing machine. It determines the active service call of the machine and provides the permission

to acknowledge the active service call.

Production - Machine Status Form

Description

· State: Specifies the current status of the machine as following

- On: If the sewing machine is switched on - Blue Color

- LoggedIn: If the user has logged-in to the specific machine - Green Color

- Service: If the mechanic has logged-in to the specific machine for servicing the machine - Red

Color

- Off: If the machine is switched off - Grey Color

If the user logout of the machine, the 'State' field value will be 'On' for that particular machine

· Machine ID: Specifies the machine ID of the particular machine

· Real User Name: Specifies the logged-in user name, if the user has an entry in the user table

with the respective RFID

- If the logged-in user does not have an entry in the user table, the real user name is 'Unknown'

· Short User Name: The unique user name entered while logging-in to the control box as

explained in User

· Login Time: User logged-in date time

- This field contains value only if the user login to particular sewing machine

· Logout Time: User log-out date time

12

12

24


Biasys I4 Frontend

- This field contains value only when the user logout of particular sewing machine

· Power On Time: Sewing Machine switched on date time

· Power Off Time: Sewing Machine switched off date time

· Total MotorRunTime [ms]: Each sewing info message contains motor run time of that particular

sewing task

- Total motor run time is a sum of all the motor run time obtained by particular sewing machine

between power On and power Off of the machine in milliseconds

· Seams: Total number of sewing info message received from the control box before the piece

counter message

· Pieces: Total number of pieces

· Service Call Category: Displays the active service call of the respective Machine

- This field contains button to send the service call acknowledge message for the

respective machine

- When the service call is active and is not acknowledged, the alert window is displayed

- The alert window as shown below, disappear once the service call is acknowledged

- This field display 'Active' until the mechanic service the particular machine

· Update Time: Last time the machine status table was updated

· Last Message: Last message received by the com server from the control box

When the sewing machine is switched on the Motor Run Time, Seams and Pieces column is set to

value zero.

Machine Status Tool Bar

Button Description

Refreshes Machine Status data table

Exports Machine Status table to Excel file

Hides the detail view of Machine Status table window

Opens Machine Detail window (Machine Detail ) 25

25


Biasys I4 Frontend

Opens Machine Status Log window (Machine Status Log )

Opens Service window (Service )

Opens All Active Service Calls window (All Active Service Calls )

Send Service Call Acknowledge message to selected Machine

2.2.2.1.1 Machine Detail

Introduction

Machine Detail form contains the detailed information for the selected sewing machine in the

machine status table. It describes the particular machine data precisely. Each machine in the

machine status table has a detail view. The detail view is based on the machine, user and

production information. If the particular machine has any active service call, the acknowledge can

also be sent from this segment.

Machine Status - Machine Detail

Description

The selected sewing machine ID is displayed in the top field of the Machine Detail window.

Machine Detail window display the following information section for each sewing machine:

- Machine Info

- User Info

- Production Info

26

27

45

26


Biasys I4 Frontend

The 'Service Call Active' field in the 'Production Info' region, display whether any service call is

active for the selected machine which provides:

- If service call is active, service call acknowledge message can be sent to the respective

machine by clicking on button

- The text displayed in this field, mentions the priority of the service call received as shown in

Service Call ID

2.2.2.1.2 Machine Status Log

Introduction

Machine status log table is the list of currently generated sewing data by the selected sewing

machine in the machine status table. The sewing information is recorded each time the sewing

info message is received by the com server from the sewing machine control box. This recorded

sewing data is displayed in the Machine Status Log table. The sewing data displayed is with

respect to the selected machine. Maximum of 10 recent records are displayed in the machine

status log table based on the latest update time.

Machine Status - Machine Status Log

Description

· Seam Number: Serial number of the seam

- Seam number increments each time when the sewing info message is received

14

27


Biasys I4 Frontend

- Seam number is initialized to '0' on every Power On or Power Off of the particular sewing

machine

· Update Time: Date time of the sewing info message received

· Total Sewing Time [ms]: Total time taken for sewing in milliseconds

· Motor Run Time [ms]: Total run time of the motor for each sewing info message in milliseconds

· Stops: Number of Stops during sewing

· Average Speed [rpm]: Average Speed in rpm

· Stop Time [ms]: Stop time in milliseconds

· Stitches: Total number of stitches for whole sewing seam


- When the 'Piece Counter Ready' message is received by the com server, the number of pieces

are incremented by one

· Delta Time [ms]: Time between previous seam end and seam start in milliseconds

· Work Ratio [%]: Work ratio of each sewing message is a percentage value, which is calculated as

follows:

- Work Ratio = ((TotalSewingTime - StopTime) / TotalSewingTime * 100)

2.2.2.1.3 Service

Introduction

Service contains various service functionality for the sewing machine. Servicing a sewing machine

means, setting sewing 'parameter data sets' to the operator specific value. The main functionality

present in this form are:

- Get/Set specific 'parameter data sets' of the sewing machine control box

- Get/Set 'parameter data set' files from/to the database

- To set piece counter

- To set service counter

28


Biasys I4 Frontend

Machine Status - Service

· Single Parameter <= Machine

· Selected Parameter by File <= Machine

· Selected Parameter <= Machine

· All Parameter <= Machine

· Single Parameter => Machine

· Selected Parameter by File => Machine

· All Parameter => Machine

· Parameter File <=> Database

· Set Piece Counter

· Set Service Counter

29

30

30

34

35

37

38

40

43

43

29


Biasys I4 Frontend

2.2.2.1.3.1 Single Parameter <= Machine

Introduction

This section contains the 'Get Parameter' function for single parameter. Get parameter will read

parameter value from the control box. This form will read a single parameter value from the

selected sewing machine control box.

Service Window – Get Single Parameter From Machine

Description

Gets single parameter value from the selected machine in the Machine Status table. The step by

step procedure to get the parameter value from the control box in this section are as follows:

· Parameter Number: Parameter number for which parameter value must be read from the

control box

Click this Get Parameter button to send get parameter message to the control box. If the

parameter value is received from the control box then the value is displayed in the 'Parameter

Value' field and the message window is displayed as shown below.

30


Biasys I4 Frontend

If the selected machine is not switched on then the following error window appears.

If the get parameter value was not successful, then the following error window appears.

2.2.2.1.3.2 Selected Parameter by File <= Machine

Introduction

This section gets the parameter value for the parameters in the specified parameter file from the

control box. And writes the obtained parameter value to the parameter file specified.

31


Biasys I4 Frontend

Service Window – Get Selected Parameter by File From Machine

Description

This section gets the parameter value for all the parameters in the file selected in the field called

'File with list of selected parameter'. This selected parameter file acts an input file and the

parameters from this input file are send to the control box. The received parameter value from

the control box is saved to the file selected in the field called 'Save parameter file to'. This

selected parameter file acts as an output file, where the received parameter value from the

control box is saved into this output file. The step by step procedure to get the parameter value

from the control box in this section are as follows:

· File with list of selected parameter: Select a '.par' file which has a list of all parameters to get

the parameter value from the sewing machine control box by clicking on this button

· Save parameter file to: Click this button which opens a dialog box as shown in Save

Parameter File , to select or create new parameter file (.par file)

Once this button is clicked, this opens the 'Sewing Machine Setup Action' window as shown

below.

· 'Sewing Machine Setup Action' window displays the details regarding which process is going on

for which particular machine and the progress bar ensures the progress of the get parameter

The process of get parameter can be canceled by clicking the cancel button. If the selected

machine is not connected, an error message is displayed as shown below.

44

32


Biasys I4 Frontend

If the setup action window closes without any error window then the parameter value is saved to

the file selected in this 'Save parameter file to' field.

2.2.2.1.3.3 Selected Parameter <= Machine

Introduction

This section contains get parameter function for a range of parameter numbers specified.

Parameter value for the particular range of parameter number can be obtained. The received

parameter value is saved in the user selected parameter file.

Service Window – Get Selected Parameter by File From Machine

Description

This section gets parameter values for the set of parameter numbers mentioned in the 'From'

field to 'To' field. The received parameter values are saved to the file selected in the field 'Save

parameter file to'. The step by step procedure to get the parameter value from the control box in

this section are as follows:

· From: Starting number of the get parameter range

33


Biasys I4 Frontend

· To: Ending number of the get parameter range, must be greater than the parameter number

entered in the 'From' field

- If the parameter number entered in the field 'To' is greater than the parameter number

entered in the 'From' field, the following error window is displayed by the software

· Save parameter file to: Click button which opens a file dialog as shown in SaveParameter File , to select parameter file (.par file) to save received parameter value

Click 'Get Parameter' button, this opens the 'Sewing Machine Setup Action' window as

shown below.

'Sewing Machine Setup Action' window displays the detail of which process is going on for which

particular machine. The progress bar ensures the progress of the get parameter. The process can

be canceled by clicking cancel button to stop sending the get parameter message. If the selected

machine is not connected, an error message is displayed as shown below.

If the setup action window closes without any error window then the get parameter is successful

and the parameter value is saved in the selected file.

44

34


Biasys I4 Frontend

2.2.2.1.3.4 All Parameter <= Machine

Introduction

The complete parameter value for the parameters present in the selected sewing machine is

obtained in this form. The user must select only the output file to save the received parameter

value from the sewing machine control box. The received parameter file can be viewed in the

notepad program.

Service Window - Get All Parameter From Machine

Description

The complete parameter value from the control box is received to the selected parameter file in

the field 'Save parameter dump to file'. The step by step procedure to get the parameter value

from the control box in this section are as follows:

· Save parameter dump to file: Click this button which opens a dialog box as shown in Save

Parameter File , to select or create new parameter file (.par file)

When clicked this 'Get Parameter Dump' button, the below Setup Action Window is opened.

44

35


Biasys I4 Frontend

The above 'Sewing Machine Setup Action' window displays the detail of undergoing process for

which particular sewing machine. The processing takes place until the complete parameter dump

is received from the selected machine. The below result window displayed at the end of the

process, shows whether the get parameter dump was successfully or not.

If the selected machine is not connected then the below error window is displayed.

Once the process is complete, the received parameter value stored in the parameter dump file

can be viewed in the notepad by clicking button. This button is enabled only when the

parameter dump value is successfully saved to the file.

2.2.2.1.3.5 Single Parameter => Machine

Introduction

This section contains the 'Set Parameter' function for single parameter. Set parameter message

will write the parameter value of the particular parameter to the control box.

36


Biasys I4 Frontend

Service Window - Set Single Parameter to Machine

Description

This section will set a single parameter value to the selected control box. The step by step

procedure to set the parameter value to the control box in this section are as follows:

· Parameter Number: Enter the parameter number for which the value must be set

· Parameter Value: Enter parameter value for the respective parameter number

Click 'Set Parameter' button to send set parameter message to the selected machine control

box. A dialog box is displayed, showing the result of the set parameter operation, whether it was

successful or not as shown below.

37


Biasys I4 Frontend

If the connection from the com server to the sewing machine control box is not established then

the below error window is displayed.

2.2.2.1.3.6 Selected Parameter by File => Machine

Introduction

This section contains a function to set selected parameter from file to the particular machine. Sets

parameter value for all the parameters in the selected file to the selected sewing machine.

Service Window - Set Selected Parameter by File to Machine

Description

Sets parameter value for all the parameters in the file selected in the field 'File with list of all

parameter' to the selected sewing machine control box. The step by step procedure to set the

parameter value to the control box in this section are as follows:

· File with list of all parameter: Select a ".par" file which has a list of selected parameters and it's

respective values by clicking on this button

Click this 'Set Parameter' button, this will open the Setup Action window as shown below.

38


Biasys I4 Frontend

The above 'Sewing Machine Setup Action' window displays the detail of undergoing process for

which particular sewing machine and the progress bar display the status of the on going set

parameter process. If the selected machine is not connected, an error message is displayed as

shown below.

If the setup action window closes without any error window then the set parameter process is

successful by setting the value to the selected sewing machine.

2.2.2.1.3.7 All Parameter => Machine

Introduction

This section contains the function to set all parameters from file to the selected sewing machine.

Service Window - Set Selected Parameter by File to Machine

39


Biasys I4 Frontend

Description

Sets parameter value for all the parameters in the file selected in the field 'File with list of all

parameter' to the selected sewing machine control box. The set parameter dump message is sent

for the collection of parameters in the selected file.

· File with list of all parameter: Select a ".par" file which has a list of all parameters and it's

respective values by clicking on this button

Click this 'Set Parameter Dump' button which open the Setup Action window as shown

below.

The processing takes place until the complete set parameter dump is set to the selected machine.

The below result window is displayed at the end of the set parameter process, which confirms

whether all the parameter value was successfully set or not.

If the selected machine is not connected, an error window is displayed as shown below.

40


Biasys I4 Frontend

2.2.2.1.3.8 Parameter File <=> Database

Introduction

This section contains functions for writing and reading parameter file to or from the database

respectively. The two main functions are:

· New parameter file can be inserted into the database

· Can fetch parameter file data from the database

Service Window - Get or Set Parameter File to Database

Description

The (.par) parameter file can be saved to the database or can get the (.par) parameter file from

the database from this particular section.

· Copy File from Database to: Click this button to select or create new parameter file (.par

file) or else just copy the file path along with the file name to the text box as shown in the

above window

- When Clicked on this button a dialog box is opened as shown in Save Parameter File

Click this 'Copy Parameter File from Database' button, which display the window as shown

below.

44

41


Biasys I4 Frontend

Get Sewing Machine ParamFile from DB Window

Select the parameter file as shown in 'Get Sewing Machine ParamFile from DB Window' from the

list and click on this button. Or else double click on the parameter file name to get the file

data from the database to the file selected in this 'Copy File from Database to' field. Once this

button is clicked, the 'Get Sewing Machine ParamFile from DB' window is closed and the file

data from the selected file in DB is written to the local file selected.

· Copy Parameter File to Database: Select a parameter (.par) file which must be saved into the

database by clicking on this button

Click 'Copy Parameter File to database' button, which display the window as shown below.

42


Biasys I4 Frontend

Update Sewing Machine Parameter File to DB Window

The 'Update Sewing Machine Parameter File to DB' window opens the list of all the parameter

files stored in the database with the 'File Name' and 'Description' column in the first half section

of the window. In the second half section of 'Update Sewing Machine Parameter File to DB'

window contains two tabs namely:

· The First tab always reads the file data of the selected file from the parameter file list

· The second tab always reads the data from the file selected in the field 'Copy Parameter File

to Database'

If the file name selected locally by the user already exists in the database, the software opens

'Update Sewing Machine Parameter File to DB' window pointing to that row in the parameter file

list. Save button is clicked to save the file to the database.

Button Description

Refreshes the list of parameter file table

43


Biasys I4 Frontend

Reverts any unsaved changes made to the table

Saves changes made to the list of parameter files to the database

Exports Sewing Machine Parameter File table to Excel file

2.2.2.1.3.9 Set Piece Counter

Introduction

This section contains the set piece counter function. Set piece counter for the selected sewing

machine from the machine status table.

Service Window - Set Piece Counter

Description

Set piece counter for selected sewing machine based on the specified trimming count.

· Trimming Count: Enter desired trimming count value

Click 'Set Piece Counter' button to set the value to the selected sewing machine.

2.2.2.1.3.10 Set Service Counter

Introduction

This section contains the set service counter function. Setup service counter for the selected

sewing machine from the machine status table.

44


Biasys I4 Frontend

Service Window - Set Service Counter

Description

Set service counter for the selected sewing machine by assigning the values in the field and click

'Set Service Counter' button.

· Counter/Timer ID: It is possible to setup 5 service count down value

· Counter/Timer Mode: Counter means stitch counter value

· Start Value: If the the mode is 'Timer' then the start value is in hours

- If value = 0, the counter or timer is deactivated

2.2.2.1.3.11 Save Parameter File

The window as shown below is the file dialog, which permits the user to select the existing

parameter file or to create a new empty parameter file. The step by step procedure to select

parameter file are as follows:

· Select an existing .par file or just type a new parameter file name in the 'File name' field and

click Open button

45


Biasys I4 Frontend

· Example: Select 'paramdump.par' file in the file dialog to overwrite the data in the existing file

by the new parameter values and click on Open button

· Or else type any new file name example 'dump' in the field 'File name' and click on Open

button

- Example: New parameter file called 'dump.par' will be created and the received value from

the control box will be saved to this file

Save Parameter File Dialog Box

2.2.2.1.4 All Active Service Calls

Introduction

All active service call table is the list of active service calls for all the sewing machines in the

machine status table. Active service calls are the service calls which are waiting for the service by

a mechanic. All these active service calls from all the connected sewing machines are displayed in

this table.

46


Biasys I4 Frontend

Machine Status - All Active Service Calls

Description

All Active Service Calls window display if there is any active service call present in any machines

of Machine Status table. The data in this table specifies the particular machine data and the

service call details. The following are the column description of the all active service calls table:

· Machine ID: ID of the machine which received service call

· Service Call Category, Source, Operator Name, Service Call ID, Event : Describes the service call

functionality (Service Call ID )

· Update Time: Time when the service call was received

· Acknowledge Time: Time when service call acknowledge message is sent

Once the particular machine is serviced by a mechanic, the respective machine data entry in 'All

Active Service Calls' table is removed.

2.2.2.2 Statistic

Introduction

Statistic table is the list of statistic data based on user or machine. The performance efficiency

based on user and machine can be analyzed in this table. The data entry of this table is based on

the sewing information received during the course of time. Based on the time interval selected

the statistics data can be reviewed. The records to be viewed can be limited to the desired value

count. Determines the total and the average data value of the particular user or machine

selected.

14

47


Biasys I4 Frontend

Production - Statistic Form

Description

The detailed description of the form are as follows:

Selection

Select 'User' or 'Machine' based on which the statistics data must be viewed.

· User: Select the individual user name from the combo box or select '%' to view all the user

statistics data

· Machine: Select the individual machine ID from the combo box or select '%' to view all the

machine statistics data

· From date: Start date of the data to be viewed

· To date: End date of the data to be viewed

· max. records in the table: Mention total number of records to be viewed in the table

- In this table, the maximum of 2000 records can be viewed

Once all the above data are entered, click refresh button to view the data based on the

requirements entered.

Results

· The 'Results' section displays the total and the average value of the sewing data, based on the

selection

- Total number of seams, stops, stitches and pieces: Sum of respective column values

48


Biasys I4 Frontend

- Average of 'Motor Run Time', 'Average Speed' and 'Work Ratio': Average value obtained from

the respective column values

- Total downtime: Calculated based on the customer requirements

The table column values are explained in Machine Status Log .

Image Description

Refreshes Statistic data table

Exports Statistic table to Excel file

Gets previous sewing records based on maximum records in table and timeinterval

Gets next sewing records based on maximum records in table and timeinterval

2.2.2.3 Service Call Log

Introduction

Service call log table is the list of all service calls generated by/for the list of sewing machines in

the machine status table. This table gives a detail information of the machine, service call and its

servicing. Same machine may have received one or more service calls, which is listed in this table.

This table contains all the service calls whether if it is currently active or not. The service call

event is filtered with respect to user or machine based on the time interval selected and the

maximum records.

Production - Service Call Log Form

Description

The detailed description of the form are as follows:

Selection

26

49


Biasys I4 Frontend

Select 'User' or 'Machine' based on which the statistics data must be viewed.

· User: Select the individual user name from the combo box or select '%' to view all the user

statistics data

· Machine: Select the individual machine ID from the combo box or select '%' to view all the

machine statistics data

· From date: Start date of the data to be viewed

· To date: End date of the data to be viewed

· max. records in the table: Mention total number of records to be viewed in the table

- In this table, the maximum of 2000 records can be viewed

· Source: Select whether the source must be an 'Operator' or 'Mechanic' or '%' to view both data

Once all the above data are entered, click refresh button to view the data based on the

requirements entered

· Operator Name: User name while service call was received

· Update Time: Time when service call was received

· Message Buffer ID: Internal message ID, which is unique for each message

· Source, Service Call ID, Event, Service Call Category : Described in Service Call ID

· Acknowledge Time: Time when service call is acknowledged

· Mechanic Name: Name of the mechanic for servicing that particular machine

- If the field is empty then the mechanic has not logged-in to that particular machine for

servicing

· Service Time: Calculated based on the customer requirements [Seconds]

- This field value is 0 if the service call is active

- Service time is calculated as: Service time = (MechanicLogoutTime - MechanicLoginTime)

· Machine ID: ID of the sewing machine

Image Description

Refreshes Service call log data table

Exports Service call log table to Excel file

Gets previous service call records based on maximum records in table andtime interval

Gets next service call records based on maximum records in table and timeinterval

14

50


Biasys I4 Frontend

2.2.3 Settings

Introduction

This section provides the operator to modify the frontend application to the desired

requirements. The modified operations can be saved for the further usage. The frontend

application text can be changed based on the language options provided. Server setup can be

made based on the required specifications. Data backup can be made automatically during the

course of time.

Setting Section

Description

Settings section contain three parts

· Skins: User can select the look and feel of the frontend application window by selecting

anyone of the options in this section

· Window Configuration

51


Biasys I4 Frontend

- Open Window Configuration: Loads the selected configuration file to the frontend and

saved as a default configuration. 'Open Window Configuration' button will open the

window with list of saved configuration files as shown below. The saved configuration file

are in '.layout.xml' format in the base directory (frontend application startup path) of the

frontend application. Operator can select the configuration file and click Ok button. The

selected configuration is applied for the frontend application when Ok button is clicked

and saved as default configuration of the frontend.

Select Window

- Save Window Configuration: Saves the current configuration of the frontend as a default

config file and writes the configuration to the new config file or overwrites the selected

config file. This form saves the window configuration in '.layout.xml' file format in the

base directory (frontend application startup path) of the frontend application. 'Save

Window Configuration' button will open the window as shown below. Provide the

configuration file name in the field (example: 'VisualStudioBlue') as shown below to save

the configuration into new file and click OK button. Or else click button which

provides the list of saved configuration file names, select file name to which the current

configurations must be overwritten and click Ok button. The configuration is saved as a

default configuration of the frontend application.

Save Window Configuration Window

- Delete Window Configuration: Deletes the window configuration file from the base

directory. 'Delete Window Configuration' button will open the list of configuration file

window as shown below. Select the configuration file name from the list and click Ok

button.

Delete Window Configuration Window

· Setup: Contains all the setting property of the frontend application as described in Setup

2.2.3.1 Window Configuration

Enter topic text here.

52

52


Biasys I4 Frontend

2.2.3.2 Setup

Setup section contains formulas of the following:

· Language Setup

· Communication Server Setup

· Frontend Server Setup

· House Keeping

2.2.3.2.1 Language Setup

Introduction

The frontend application text can be switched to the desired language provided. This form

provides the multiple language options to choose. The selected language is saved as a default

language of the frontend application.

Description

The complete form text can be changed based on the selected language in the combo box.

· Select Language: Select language from the given option

· Set language of the frontend form based on the selection

· Refresh the language files when the language files are modified

Once the language is selected, click Set language button to switch to the selected language.

Setting - Language Setup Form

2.2.3.2.2 Communication Server Setup

Introduction

Communication server setup is the list of com servers initialized. Com server application insert

this table entry when the com server application is initialized with the new 'Server IP Address'.

This server ip address of the com server is inserted as a server id. The frontend operator can add,

delete or modify the data entry into this table.

53


Biasys I4 Frontend

Description

The detail information of the communication server is listed in this table. The data values in this

table can be edited or a new row entry can be inserted. The columns description are as follows:

· Server ID: IP Address of the communication server application, for the case if two servers

running on same system

· Computer Name: Name of the computer in which the communication server application is

initialized

· Description: Description for the particular row entry, initially it is described as 'NEW RECORD'

when the new entry is added to the table

· Com Server API Port: Port number of the communication server application through which the

frontend application is connected

Setting - Communication Server Setup Form

Button Description

Refreshes the communication server setup data tableReverts any unsaved changes made to the table

Saves the changes made in the table to the database

2.2.3.2.3 Frontend Server Setup

Introduction

The frontend application is connected to the following:

· Database: To extract data and display in it in the frontend application tables

· Com server application: To communicate with the sewing machine control box

This form provides access to modify both database and the com server connection configuration

of the frontend application.

54


Biasys I4 Frontend

Setting - Frontend Server Setup Form

Description

The Frontend Server Setup is used to set the database and com server connection configuration of

the frontend application. The list of three configurations are provided, so that the frontend

operator can modify each list entry and use it. The modified configurations can be changed and

must restart the frontend application to apply the changes. The first section of the window

display the current configurations that the frontend is running on. The second section contains

the three main configurations of the frontend application that can be modified.

· DB Server Host: Database server host name or IP address to which the frontend application

must be connected

· Com Server API Port: The communication server port on which the communication server is

running

- Enter the com server port to which the frontend application must be connected

· Com Server API Host: The communication server host name or IP address to which the frontend

application must be connected

Click on the test button to check the connection to the host, if the test is successful the result

window is displayed as below.

55


Biasys I4 Frontend

If the Test failed the result window is displayed as below.

The list of three entries with DBHost, ComServerPort and ComServerHost are displayed in the list

box of Frontend Server Setup window. The fields are updated based on the list selected. Click on

any one of the list, this selected list value is displayed in the respective fields. Operator can edit

these fields and save the changes. When the 'Change' button is clicked, the selected list value is

changed based on the respective field. Once 'Apply' button is clicked, the default configuration of

the frontend application is changed to the respective values and the following information

window is displayed.

Restarting the frontend application is a must, to implement the new configurations applied. Click

on 'Restart' button to restart the frontend application. The frontend application will restart with

new configurations entered.

Button Description

Test Test the connection to the respective host

Change Selected list value is modified based on the entered value in the field

ApplySet the default configuration of the frontend Saves the respective value to the selected list

Restart Restart the frontend application

56


Biasys I4 Frontend

2.2.3.2.4 House Keeping

Introduction

This form provides the operator to manage the data backup and cleanup of the database during

the prescribed time interval. Handles the data backup of the complete production data. The

backup is done automatically by the com server application in the background. Data backup is

executed on the scheduled backup date time. Archive data table is the list of all the old archived

data (Backup data). This archived data can be loaded into the frontend application for reference.

Setting - House Keeping Form

Description

House Keeping has two main functionality as follows:

· Helps to modify the database backup configuration

· Permits the frontend operator to change the database of the frontend application from the

production database (current working database) to the archive database

The first section of the House keeping are the current data backup setting as shown below:

First section of the House Keeping Form

57


Biasys I4 Frontend

The above backup setting values in the table can be modified in the fields as shown below:

First section of the House Keeping Form

· MySql Tool Path: Specify the tool path where the program 'sql.exe' and 'sqldump.exe' are

located in the system

· Backup Location Path: Create a backup directory, where the backup data files must be stored

- Copy this directory path to this field

· Backup Time: Backup time, when the backup will be executed

- Enter the desired backup time in this field

· Backup Interval: The time interval when the backup will be executed

- Select the backup interval from the list of values from the field, which are as follows

o Deactivate: Data backup will not be executed

o Daily: Data backup will be executed every day on the selected backup time

o Weekly: Data backup will be executed every week of the selected week day on theselected time

o Monthly: Data backup will be executed every first day of the month on the selected backuptime

· Week Day For Weekly Backup: Select the day of the week for the data backup when theselected Backup Interval is 'Weekly'

· Next Scheduled Backup Date: Specifies the backup time interval based on the selection made inthe 'Backup Time', 'Backup Interval' and 'Week Day For Weekly Backup' field

- The value of this field can be modified individually for any desired date time of the databackup

· Delete detailed sewing recorded data after X-days: Specify that the sewing records older than Xdays are deleted from the production database after the execution of a database backup

- If this field value is 0 then no sewing records are deleted from the database

58


Biasys I4 Frontend

· Last Executed Backup Date (Read Only): Date and time of the last executed backup

· Last Executed Backup Status (Read Only): Status of the last executed data backup

- It can have SUCCESS or ERROR as a status

· Last Executed Backup Info (Read Only): Information regarding the last backup execution

Image Description

Refreshes all the data backup fields Reverts any unsaved changes made to the table fields

Saves the changes made in the data backup fields to the database

Opens or loads Archive Database to the frontend applicationCloses all the opened tabs in the frontend application

Opens or loads Production Database to the frontend applicationCloses all the opened tabs in the frontend application

2.2.3.2.4.1 Archive Data

Introduction

Archive data table is the list of all the information of the backup data (archive data) folders. The

executed data backups are saved in the backup folders locally. This backup folders contain

production data which can be loaded into the frontend application. Backup folders can be

removed permanently from the local directory and from the database by the frontend operator.

Description

List of all the backup data folders are listed in the Archive Data table as shown below:

Second section of the House Keeping Form

· Archive Path: Backup location or folder name where the backup files are stored which is

specified by the first section of the House Keeping From in 'backuplocationpath' field

· Archive Execution Date: The date and time of the backup execution

· Backup Location Path: Backup directory path, where the backup folders are present

· Load Request Pending: Set by the frontend application if the archive shall be loaded; reset if

archive is loaded or load failed

59


Biasys I4 Frontend

- The status of this field specifies whether the loading of archive data is in progress or not

o Idle: Archive load data is not in progress

o In Progress: Archive load data is in progress

· Delete Request Pending: Set by frontend application if the archive shall be deleted

- This will remove the archive folder from the local directory and also from the database table

- Once the archive is deleted, particular data entry is removed from this archive table

- The status of this field specifies whether the deleting of archive data folder is in progress or

not

o Idle: Delete archive data folder is not in progress

o In Progress: Delete archive data folder is in progress

· Archive Begin DateTime: Date time of the first record based on the update time of the message

in that particular backup data folder

· Archive End DateTime: Date time of the last record based on the update time of the message in

that particular backup data folder

· Load: Loads the specific archive data into the frontend application

· Delete: Deletes the specific archive data folder from the database and also from the local

system backup directory

Step by step procedure to load or delete archive data

· To view the particular archive data in the frontend application, click 'Load' button on the

particular archive folder row

· As soon as 'Load' button is clicked the status of the 'Load Request Pending' field switches

from status 'Idle' to 'In Progress'

· Loading of the archive data takes a while

· Click refresh button to check the status of 'Load Request Pending' field

- If the status has changed to 'Idle' then the archive database has been loaded or else wait for

some more time and click refresh button to check the status

· Once the data is loaded into archive database, click 'Open Archiv data' button to view the

archive data in the frontend application

60


Biasys I4 Frontend

- If the archive data has been loaded into frontend application, the user can only view this

particular data but cannot edit any data values

· Click 'Open Production Data' button to return back to the current production database

· Click 'Delete' button to delete the archive data folder from both database and from the

backup location path

· As soon as 'Delete' button is clicked 'Delete Request Pending' field changes the status from

'Idle' to 'In Progress'

· Click 'Refresh' button to check if the status of 'Delete Request Pending' field changed back

to 'Idle'

- If the status is changed to 'Idle' then the backup folder is deleted or else wait for sometime

and click refresh button to check the status

2.2.3.2.5 Touch Mode Setup

Introduction

Frontend application also works on the touch-screen device. This form the touch mode feature to

access the frontend application on a touch screen device. User can turn On or Off the touch mode

of the frontend application in this particular form. Turning On the touch mode feature enables

the frontend to create more space between the controls and the buttons get enlarged, so that the

commands are easier to tap.

Setting - Touch Mode Setup Form

Description

Clicking on this button on the frontend Settings tool bar opens the form as shown above.

This form contains the switch to On or Off the touch mode of the frontend application. Initial

state of the switch defines the current state of the frontend application, whether the application

is in touch mode or not. If touch mode is On, then the frontend application is in touch mode. If

touch mode is Off, then the frontend application is not in touch mode. When the state of the

61


Biasys I4 Frontend

switch is changed, it closes all the currently opened tabs or forms in the frontend application to

apply the touch mode changes to the application.

EFKA Communication Server

63



3 EFKA Communication Server

Introduction

Efka communication server is a server application which establish a connection to one or more

sewing machine client control box. The connection established to each client control box is a TCP

IP connection. The main purpose of the connection is to record the data communication between

the client control boxes and the Efka communication server software. The data communication

between the com server application and the client control boxes are saved in the database. The

data backup is executed by the com server application in the background on the particular time

scheduled. The application process is logged, based on the configurations selected during the

start of the com server software.

3.1 Efka Communication Server Login

Introduction

Login window is displayed on the start of the com server application. Login is necessary to gain

access by the operator for the com server application. The login window must be entered with

the values appropriate to the data field as shown below. If login fails, the server application

cannot be initialized.

64



Efka Communication Server Login

Description

· Database Account Name: Name of the valid database user account

· Database Password: Password for the respective user account if existing

· Database Host: Valid database server host address which contains the entered user account and

valid data

· Server IP Address: IP Address of the server to start

· Test (Button): Is used to test the entered server IP address is valid or not

· Port Number: Communication server port number

· Extended Data Record Directory: Provide the local directory name, to save the message buffer

to the database file

- Sewing machine data obtained from the client control box are stored in the '.db' database

file

65



· Enable Extended Data Recording (CheckBox): Select this field if the data must be saved to

message buffer or else deselect this field

· Specify Application Logging: The complete software processing can be logged based on this

selection

- Application logging information can be selected during the login between the following

options

o Log All

o Only Errors

o Errors and Log Infos

o No Logging

· Login (Button): Performs application login operation

- If login successful the communication server application(Efka ComServer Application ) is

opened

- If login fails the error message is displayed

· Cancel (Button): Exist the complete application

3.2 Efka Com Server Application

Introduction

The communication server application will be accessible when the login is successful. Click start

button to start the com server application.

Efka Com Server Application Window

65

Log From DB

67


Log From DB

4 Log From DB

Introduction

This form is used to read the data from the selected 'MessageBuffer_Date.db' database file. The

data communication between sewing machine control box and com server application are stored

in the database (.db) file. The default directory of this 'MessageBuffer.db' file is selected by the

com server operator during the start of the com server application.

Log From DB Form

Description

· Misc: Select a ".db" file to be read which is located in the local folder by clicking on

button

- The directory of this database file is selected in the com server application in field

'Extended Data Record Directory'

Search Data: Specifies the search criteria to sort the message buffer data accordingly. Select one

of the following main search category:

- Newest Log Messages: Filters only the recently added records based on the 'Max. No Of

Records'

63

68


Log From DB

- From Date/Time: Filters the data from the date time specified in this field, based on the

'Max. No Of Records'

- From ID: Filters the data from the ID (First Column of the table, Message Buffer ID) which

is unique for each row in the table, based on the 'Max. No Of Records'

Select any of the following sub search category based on the table columns

- Machine ID

- RFID

- Message ID

- User Name

- Only Status 'Not OK': Select this field to filter the message with the status 'NOK'

· Max. No Of Records: Specify the maximum record count to view in the table

Click 'Refresh' button each time if the search categories are modified. These buttons

as shown in the above window are used to get previous or next set of

maximum records in the table. The button is used to display or hide the date

column in the log data table.

The second table to the right of the log data table is the detail table of the Message column, It

explains the message column with the detail Name, Value and Description.

Example: The below window displays the detail of the 'Power ON' message

Log Viewer

70


Log Viewer

5 Log Viewer

Introduction

This form is used to view the complete log data based on the application. Data logging is a process

of storing data over a period of time in order to analyze application mechanism during the

application information or errors. The logging mechanism is implemented for 'communication

server', 'frontend' and 'log from DB' applications. The data logging option can be chosen based on

the user requirements during the start of the both communication server and frontend

application.

Log From DB Form

Description

Log data from the specified file path is read into this form. The data displayed in the above form is

the application information followed by icon and application error followed by

icon.

· Path: Select the root log directory of the log files

- Click button which opens the window as shown below

71


Log Viewer

- Provide desired name in the field 'Alias'

- Provide the directory path where all the log files are stored as show below

- Click 'OK' button once the valid data entered in the field

· Program: Select program name to view the log data only from the selected program

- Or else select 'All Programs' to view the log data for all the program

- The current program names present in the log application are

o ComServer: Log data from the Com server application will be displayed

o GlobalDef: Log data from the database program will be displayed

o logFromDB: Log data from the 'Log From DB' application will be displayed

o FrontEnd: Log data from the frontend application will be displayed

· Timespan: Select the date to view the log data during the particular time interval

Gets the previous log records based on the timespan specified

Gets the next log records based on the timespan specified

· Refresh (F5): Click refresh button to view the log data based on the selected criteria

- Click refresh button each time the criteria is changed

· Choose File (Button): Click choose file button to select log collection (.LogCol) files to read

data from this particular file to the log viewer

· Filter

- Category: Filter based on the category name, select category in the combo box and click

filter button

o Each 'Program' name has unique categories

72


Log Viewer

- Message: Filter based on the alphabets, particular text or complete message and click

- Error: Select the filter button to filter only error messages

- Deselect the filter button in the Error field to view all log messages

· Save To File: Save the log messages

- Select: Save the selected messages to the log collection (.LogCol) file

- All Shown: Save all the messages shown in the log viewer to the log collection (.LogCol)

file

· Click 'F2' button on the keyboard to make the log viewer application to display as a topmost

application

· Click 'F3' which enables both automatic refresh and the application points to the newest log

entry received

· Click 'F4' which only points to the newest log entry received

Database

74


Database

6 Database

Introduction

Data communication between client control box and com server application is stored in the

MySQL database.

· The EFKA Industry 4.0 Software Solution database schema are as follows

- i4_management: Collection of data tables containing primary data of the sewing machine and

the sewing machine user

- i4_management_archiv: Archive database of the i4_management database. The data tables in

this schema are same as 'i4_management'

- i4_production: Collection of data tables containing production data of all the sewing

machines connected to the com server application

- i4_production_archiv: Archive database of the i4_production database. The data tables in this

schema are same as 'i4_production'

Remark: Do not change the database schema.

6.1 i4_management

Introduction

Collection of data tables containing primary data of the sewing machine and the sewing machine

user. The i4_management schema contains data tables as shown below in the diagram.

75


Database

Collection of data tables in i4_management schema

6.1.1 User - Table

1. user

This table contains data regarding sewing machine user. Data entry to this data table is done by

the system administrator before the user can login. User table has two foreign keys, namely:

76


Database

· EfkaUserGroupID (Foreign-Key): Referenced from 'efkausergroup' data table

· InterUserGroupID (Foreign-Key): Referenced from 'internalusergroup' data table

Columns:

· UserGUID (Primary-Key): Unique value for each user data entry in the table

· RealUserName: Full name of the user

· ShortUserName (Unique): Short name of the user

- Main purpose of this field is to distinguish between the user who has the same full name

in 'RealUserName' field

- All the values in this column must be distinct (Unique)

· RFID: Unique ID value from the RFID chip or the value entered in the Efka variocontrol during

user login

· EfkaUserGroupID (Not Null): Efka user group ID value, either 1 or 2

- It is a foreign key related to 'efkausergroup' datatable

- The value cannot be null

· InternalUserGroupID (Not Null): Internal user group ID value which can be either 1 or 2 or 3

- It is a foreign key related to 'internalusergroup' datatable

- The value cannot be null

· Description: Description for the particular row entry

· Spare: Spare column from 1-5 are the extra columns which can be used in future if necessary

2. internalusergroup

This table contains detail data of the internal user. Currently this table data is not used by the Efka

I4 solution software.

Remark: Do not change any data in this data table.

Columns:

· InternalUserGroupID (Primary-Key): Unique internal user ID

· InternalUserGroupName: Name of the internal user

· The data in this table is as follows:

77


Database

InternalUserGroupID InternalUserGroupName

1 Admin

2 Developer

3 User

3. efkausergroup

This table contains efka user data.


Columns:

· EfkaUserGroupID (Primary-Key): Unique efka user ID

· EfkaUserGroupName: Name of the efka user category

· The data in this table is as follows:

EfkaUserGroupID EfkaUserGroupName

1 Mechanic

2 Operator

6.1.2 Machine - Table

4. machine

This table is the list of sewing machines connected to the com server application. Contains

detailed information regarding sewing machine client control boxes connected to the com server

application. The data in this table is entered by the com server application when the new control

box is connected to the com server application.

Columns:

· MachineGUID (Primary-Key): Unique value for each machine data table entry

· MachineID: Sewing machine ID

· ServerID (Foreign-Key): IP address of the com server application, to which the sewing machine

control box is connected

- Foreign key referenced from 'communicationserver' data table

78


Database

· CircuitBoardNo: Sewing machine circuit board number

· SerialNo: Efka control box serial number

· IPAddress: IP Address of the sewing machine control box connected to the com server

application


· Spare: Spare column from 1-5 are the extra columns which can be used in future if necessary

5. communicationserver

This table is a list of com server applications initialized.

Columns:

· ServerID (Primary-Key): IP Address of the communication server application, for the case if

two servers running on the same system

· ComServerAPIPort: Port number of the communication server application through which the

frontend application is connected

· ComputerName: Name of the computer in which the communication server application is

initialized

· FillMessageBuffer: Condition to fill the message buffer with the data communication

between client and server

- Value = 0 (Message buffer is not filled by the com server application)

- Value = 1 (Message buffer is filled by the com server application)


6. sewingmachinegroup

This table is a list of sewing machine group, created in the frontend application. Each sewing

machine group can contains a list of sewing machines.

Columns:

· GroupGUID (Primary-Key): The unique value for each group entry

· GroupName: Name of the sewing machine group


79


Database

7. machine_sewingmachinegroup

Contains the list of sewing machines inserted into any sewing machine group.

Columns:

· GroupGUID (Primary-Key) (Foreign-Key): Referenced from the 'sewingmachinegroup' table

· MachineGUID (Primary-Key) (Foreign-Key): Referenced from the 'machine' table

· FileName (Foreign-Key): Referenced from the 'sewingmachineparameterfile' table

8. qrymachineofgroup

'qrymachineofgroup' is a database view which is defined from the 'machine' and the

'machine_sewingmachinegroup' table. A view is a virtual table that contains no physical data but

provides an alternative way to look at the data.

The view is created where the 'MachineGUID' of 'machine_sewingmachinegroup' and 'machine'

table are equal. It contains a list of sewing machine clients connected to the com server. It gives a

detail view of the machines in the particular sewing machine group.

9. sewingmachineparameterfile

Contains the list of parameter files. The data in this table can be modified by the frontend

application.

Columns:

· FileName (Primary-Key): Name of the parameter file

· FileData: Parameter file data


6.1.3 Other - Table

10.parameter

Contains the list of parameter value, which is referenced by the com server application.


Columns:

· ParameterName (Primary-Key): Name of the parameter

80


Database

· ParameterValue: Value of the parameter

11.servicecallid

Contains the list of detailed information of all the service calls that can be generated.

Columns:

· ServiceCallID (Primary-Key): Each service call event is identified by this unique ID

· Event: Each respective ID has a event

· Source: Specifies the owner of the service call who can sent the particular service call event

· Category: Specifies the priority level of each service call event

- 3: High Priority

- 2: Middle Priority

- 1: Low Priority

12.lasterrorid

Contains the list of error messages sent from the sewing machine control box to the com server.


Columns:

· ErrorID (Primary-Key): Unique ID of the error list

· Error: Error name

13.hk_backup

Contains data configuration regarding regular database backup and cleanup tasks.

Columns:

· hk_backupGUID (Primary-Key): Unique value for each data row entry

· backuplocationpath: Path where the backups are stored on the server

· backuptime: The time when the backup shall be executed

- Specified as DateTime, but only the time part is evaluated. e.g. 23:00, the time when the

production is not active

81


Database

· mySqlToolsPath: The path where the program 'sql.exe' and 'sqldump.exe' are located

· lastExecutedBackupDate: Date and time when the backup was executed the last time.

· backupInterval: This is an enumeration:

- backup deactivated = 0

- daily = 1

- weekly = 2

- monthly = 3

· lastExecutedBackupStatus: Its an enumeration

- 0 = NONE

- 1 = SUCCESS

- 2 = ERROR

· weekDayForWeeklyBackup: The weekday as set for the current culture information

· scheduledBackupDate: Date time when the data back is scheduled to be executed

· lastExecutedBackupInfo: Date and time of the last executed data backup

· CleanUpSewingRecordsOlderThanXdays: Sewing records older than X days are deleted from

the production database after the execution of a database backup

- A value of 0 indicates to not delete old records

14.hk_backup_archives

Contains list of all the data backup folders (Archive data Folders).

Columns:

· archiveGUID (Primary-Key): Unique value for each data row entry

· archivePath: Backup location or folder name where the backup files are stored under

'backuplocationpath' folder

· archiveExecutionDate: Date and time of the backup execution

· backuplocationpath: Path where the backups are stored on the server

· loadRequestPending: Set by frontend application if the archive shall be loaded; reset if

archive is loaded or load failed

- Value = 1 (set)

82


Database

- Value = 0 (Load action is not in process)

· deleteRequestPending: Set by frontend application if the archive shall be deleted

- Value = 1 (set)

- Value = 0 (Delete action is not process)

· archiveBeginDateTime: Date time of the first record based on the update time of the message

in that particular backup data folder

· archiveEndDateTime: Date time of the last record based on the update time of the message in

that particular backup data folder

6.2 i4_production

Introduction

This section contains production data of all the sewing machines connected to the com server.

The diagram shown below is the collection of data tables in the i4_production database.

83


Database

Collection of data tables in i4_production schema

84


Database

6.2.1 DailyStatistic - Table

1. dailystatisticuser

This table stores the sewing data statistic for the sewing machine user on a daily basis. The

statistic is computed by the com server application in the background.

Columns:

· UserGUID (Primary-Key): Unique ID created in the user table, refer 'user' table in User

Table

· UpdateTime (Primary-Key): Row updated date

· RealUserName: Full user name of the logged-in user to the sewing machine control box

· ShortUserName: Unique user name of the logged-in user to the sewing machine control box

· TotalPieces: Total number of sewing pieces, , incremented by one when the sewing

information message is received by the com server application

· TotalNoOfSeams: Total number of seams, incremented by one when the 'PieceCounterReady'

message is received by the com server application

· averageMotorRunTime: Average motor run time in milliseconds

· averageSpeed_rpm: Average motor speed in rpm

· AVG_WorkRatio: Average work ratio in percentage

· TotalStops: Total number of stops on that specific day

· TotalStitches: Total number of stitches on that specific day

· TotalDowntime: Total down time on that specific day in seconds

2. dailystatisticmachine

This table stores the sewing data statistic for sewing machines on a daily basis. The statistic is

computed by the com server application in the background.

· MachineGUID (Primary-Key): Unique ID, refer 'machine' table in Machine Table

· UpdateTime (Primary-Key): Row updated date

· All other columns except 'MachineGUID' are similar to 'dailysatisticuser'

75

77

85


Database

6.2.2 MachineStatus - Table

3. machinestatus

Contains list of sewing machines connected to the com server. Gives the detail information of the

connected machines.

Columns:

· MachineGUID (Primary-Key): Unique value created in the machine table, refer 'machine' table

in Machine Table

· UpdateTime: Date time of the recently received message

· MessageBufferID: Unique internal message ID value

· MachineID: Machine ID of the connected sewing machine control box

· CircuitBoardNo: Circuit board number of the connected sewing machine control box

· SerialNo: Serial number of the connected sewing machine control box

· IPAddress: IP address of the com server application connected by the sewing machine control

box

· RealUserName: Full user name of the logged-in user to the sewing machine control box

· ShortUserName: Unique user name of the logged-in user to the sewing machine control box

· EfkaUserGroupName: Efka user group name of the logged-in user, whether the user is

Mechanic or Operator

· InternalUserGroupName: Internal user group name of the logged-in user, whether the user is

Admin or Developer or User

· LoginTime: Date time of the user login to the sewing machine control box

· LogoutTime: Date time of the user logout to the sewing machine control box

· PowerOnTime: Date time of the sewing machine control box when switched on

· PowerOffTime: Date time of the sewing machine control box when switched off

· MotorRunTime: Total motor run time of all the motor run time obtained by particular sewing

machine between power On and power Off of the machine [milliseconds]

· Seams: Total number of sewing info message received from the control box before the piece

counter message


· Downtime: Time taken by the mechanic to service the sewing machine control box [seconds]

77

86


Database

- DownTime = (MechanicLogoutTime - MechanicLoginTime) in seconds

· LastMessage: Last message received by the com server application from the sewing machine

control box

· LastError: Last error message of the particular sewing machine control box

· SoftwareVersion: Software version of the sewing machine control box, received during the

'Power on' or 'Login' or 'Logout' message

· Description: Description of each message communication process

· ServiceCallActive: Specifes if the service call is active or not

- Value = 0 (Not active)

- Value = 1 (Active)

· Status: Specifies the current status of the efka control box as follows,

- PowerON: When com server application receives power on message from the sewing

machine control box

- Login: When com server application receives login message from the sewing machine

control box

- Logout: When com server application receives logout message from the sewing machine

control box

- PowerOff: When com server application receives power off message from the sewing

machine control box

- Disconnected: When com server application receives disconnected message from the

sewing machine control box

· PieceIncremented: Specifies whether the piece counter is incremented or not

- Value = 0 (Not incremented), is set to '0' when 'SewInformation' message is sent by the


- Value = 1, Incremented, is set to '1' when 'PieceCounterReady' message is sent by the


· ServiceCallCategory: Specifies whether the received service call priority, refer 'servicecallid'

table in Other Table

- If the service call is not active then the ServiceCallCategory value = 0

· ServiceCallID: Specifies the unique service call ID number received by the service call message

- Refer 'servicecallid' table in Other Table

79

79

87


Database

- If the service call is not active then the ServiceCallID value = 0

· MachineState: Specifies the status of the machine as following

- 0: Off, If the sewing machine is switched off

- 1: On, If the machine is switched on

- 2: LoggedIn, If the user has logged-in to the specific machine

- 3: Service, If the mechanic has logged-in to the specific machine for servicing the machine

If the user logout of the machine, the 'MachineState' field value will be '1'

Deletion of data entry in this 'machinestatus' table is restricted if there is any child row existing

which is referring to 'MachineGUID' column.

4. machinestatuslog

Contains all the message data received from the control box. Each message sent from the sewing

machine to comserver, is entered as a new entry to this data table.


in Machine Table

- Foreign key referenced from 'machinestatus' 'MachineGUID' column

· UpdateTime (Primary-Key): Date time of each message received

· MessageBufferID (Primary-Key): Unique internal message ID value

The combination of above three value must be unique value for each data entry in this table

· The 'MachineGUID' is the foreign key to this 'machinestatuslog' table, referenced from

'machinestatus' 'MachineGUID' column

· The data table columns present in 'machinestatuslog' table is same as 'machinestatus' table

except 'UserGUID' field

- UserGUID: Unique ID created in the user table, refer 'user' table in User Table

- UserGUID value is null

o If the user has not logged-in

o If the logged-in user does not have an entry in the user table

6.2.3 Other - Tables

5. sewinginfolog

77

75

88


Database

Contains seam status information of sewing information message. The sewing information is

computed by the com server application when sewing information message is received from the

control box.

Columns:

· MachineGUID (Primary-Key) (Foreign-Key): Unique value created in the machine table, refer

'machine' table Machine Table


· UpdateTime (Primary-Key): Date time of the sewing message received


The combination of above three value must be unique value for each data entry in this table

· UserGUID: Unique group ID, refer 'user' table User Table

· TotalSewingTime_ms: Time for whole sewing seam in milliseconds

· TotalStitches: Total stitches for whole sewing seam

· AverageSpeed_rpm: Average speed in rpm

· RunTime_ms: Motor run time in milliseconds

· StopTime_ms: Stop time in milliseconds

· DeltaTimePrevSeamEnd2Start_ms: Time between previous seam end and seam start in

milliseconds

· Stops: Number of stops during sewing

· WorkRatio: Work ratio in percentage

- It is calculated as follows

- Work Ratio = ((TotalSewingTime - StopTime) / TotalSewingTime * 100)

6. sewinginfosectionlog

Section status information of sewing information message is inserted into this table. The section

information is computed by the com server application when sewing information message is

received.

Columns:

· MachineGUID (Primary-Key) (Foreign-Key): Unique value created in the machine table, refer

'machine' table in Machine Table

- Foreign key referenced from 'sewinginfolog' 'MachineGUID' column

77

75

77

89


Database

· UpdateTime (Primary-Key) (Foreign-Key): Date time of the received sewing information

message

- Foreign key referenced from 'sewinginfolog' 'UpdateTime' column

· SectionNo (Primary-Key): Serial number of each section


The combination of above four primary key value will be unique value for each data entry in this

table

· SewingTime_ms: Sewing time for section in milliseconds

· Stitches: Stitches for section

· AverageSpeed_rpm: Average time for section in rpm

· RunTime_ms: Motor run time in milliseconds

· StopTime_ms: Stop time in milliseconds

· Input: Input during section sewing

· Output: Output during section sewing

· StopInputSignal: During stop, Input signal

· StopOutputSignal: During stop, Output signal

7. serivecalllog

Stores generated service call message data of each connected sewing machine. The service

information is computed by the com server application during following scenarios:

- Service call message is received by the com server

- When acknowledge message is received by the com server

- When mechanic login and logout of the particular sewing machine

Columns:


in Machine Table




77

90


Database

· Source: Specifies the owner of the service call who can send the particular service call event

· OperatorName: User name while service call was received

· ServiceCallID: Each service call event is identified by this unique ID

- Service call ID is the service call number attached to a service call message

· Event: Each respective ID has a unique event, which specifies what each service call means

· AcknowledgeTime: Time when service call is acknowledged

· MechanicName: Name of the mechanic for servicing that particular machine

- If the field is empty then the mechanic has not logged-in to that particular machine for

servicing

· ServiceTime: Calculated based on the customer requirements [Seconds]

- Here service time is calculated as

- Service time = (MechanicLogoutTime - MechanicLoginTime)

· ServiceCallCategory: Specifies the priority level of each service call event

· MachineID: ID of the sewing machine

· Refer 'servicecallid' table in Other Table

8. lasterrorlog

Stores all the error messages received from the control box to com server application.

Columns:


in Machine Table




The combination of above three value will be unique value for each data entry in this table

· ErrorID: Unique error ID value

· Info: Error information sent from control box to com server application

79

77

91


Database

9. parameter

Stores parameter and its values, which are configured in the com server application. It is an

individual table without any relation to other data table.

Columns:

· ParameterName (Primary-Key): Unique name of the specific parameter, which is a primary

key

· ParameterValue: Value of the particular parameter

6.2.4 Tables for pass-through command / responses to sewing machine control boxand vice versa

Tables for pass-through command / responses to sewing machine control

box and vice versa

The pass-though command/messages are implemented since version 1.6.0.2 of the communication

server.

These tables store the messages exchanged between the communication server application an

the sewing machine control boxes for the

messages EXCMD, EXRES and EXREQ.

These messages are not evaluated by the communication server application in any way.

· Messages received from a sewing machine control box are just in inserted into the table

receivedmessagefromcontrolbox.

It is in the responsibility of the end user to evaluate and delete the received messages from

the table.

· Messages to be send to a sewing machine control box are read from the table

sendmessagetocontrolbox.

A customer frontend application can insert commands and responses into this table. The

communication server will just send the messages stored in the table to the sewing machine

control box. The communication server only checks, if the message has a correct checksum. If

the checksum is wrong the message is just deleted from the table.

Messages are only send to a control box, if the control box is connected and powered on.

92


Database

After sending a message the communication server deletes the message from the table.

The communication server checks every 100 milli seconds, if the are messages to be send.

An example of the processing of send/received messages is shown in the following figure.

93


Database

1) receivedmessagefromcontrolbox - table format

CREATE TABLE `receivedmessagefromcontrolbox` (

`MessageGuid` varchar(255) NOT NULL

COMMENT 'Primary key for a received EXCMD,EXRES, EXREQ message from a sewing

machine control box.

The key is generated by the comm server application on the reception of a message.',

`MachineGUID` varchar(255) DEFAULT NULL

COMMENT 'unique id for a sewing machine control box',

`UpdateTime` datetime(6) DEFAULT NULL

COMMENT 'date and time of message insertion ',

`MessageBufferID` int(11) DEFAULT NULL

COMMENT 'related key for the message buffer entry',

`MachineID` int(11) DEFAULT NULL

COMMENT 'id of the machine',

`CircuitBoardNo` varchar(255) DEFAULT NULL

COMMENT 'CircuitBoardNo of the control box',

`SerialNo` varchar(255) DEFAULT NULL

COMMENT 'SerialNo of the control box',

`IPAddress` varchar(255) DEFAULT NULL

COMMENT 'IPAddress of the control box from which the message was received',

`MessageHex` varchar(4096) DEFAULT NULL

COMMENT 'MessageHex - the message in ASCII/Hexadecimal format',

`MessageBin` blob

COMMENT 'MessageBin - message in binary format',

PRIMARY KEY (`MessageGuid`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8;

94


Database

2) sendmessagetocontrolbox - table format

CREATE TABLE `sendmessagetocontrolbox` (

`MessageGuid` varchar(255) NOT NULL

COMMENT 'primary key for message to be send to a control box.

The format shall be as for a ''Globally Unique Identifier'', but it can also be any

unique text value.',

`UpdateTime` datetime(6) DEFAULT NULL

COMMENT 'date / time value of message insertion.',

`IPAddress` varchar(255) DEFAULT NULL

COMMENT 'IP Address of the control box where the message shall be send to.',

`MessageHex` varchar(4096) DEFAULT NULL

COMMENT 'The message in ASCII/Hexadecimal format. The complete message from

<SOH> to >CRC>

Example: "01F1027B46324558434D443D312C302C313030302C03B9"

This field is only used, if the MessageBin field has a NULL value.',

`MessageBin` blob

COMMENT 'The message in binray format. The complete message from <SOH> to

>CRC>

If this field value is NULL the MessageHex field value is applied.',

PRIMARY KEY (`MessageGuid`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8;

EFKA Industry 4

Documents

Transcript of EFKA Industry 4