Geda Manual Eng
Geda Manual Eng
USER’S MANUAL
1.2 SYMBOLISM
Before installing and configuring GEDA, it is necessary to program the stations installed along the
process lines in order to have them ready to communicate to the network. For a proper set up of
the different stations, refer to the specific documentation of each machine or software (for
example RecDATA TJ or TJ V) which composes the stations.
GEDA network stations may be composed by:
GEDA communicates with the new Galileo TP “K” series machines through an Ethernet network,
through an owner protocol based on the standard TCP/IP protocol.
Also the communication with RecDATA TJ and TJ V is performed through Ethernet, while the
connection with the old Galileo TP machines is performed through a RS485 serial line.
The Ethernet flexibility allows to choose between two possible architectures to connect GEDA to
the Galileo TP stations: one solution, easier but less performing, foresees the connection directly
through the company LAN, while the second solution, more difficult but definitely safer and more
performing, foresees an independent Ethernet subnet.
Should the LAN network be accessible inside the factory where the process lines are, one should
only connect the stations to the Ethernet plugs using the appropriate cables. Obviously, also the
PC where the GEDA will be installed, will have to be connected in the same LAN network.
Once a device is connected to an Ethernet network, it is important to select the appropriate policy
for assignment of the IP address to this device. The choice is between the static type or the
dynamic one; generally, inside a company LAN, the IP addresses are normally dynamic.
This choice, which is the most appropriate for “office” contexts, is not used by the GEDA network,
which only uses static addresses, more appropriate for “industrial” contexts.
Picture 1 shows the scheme of a GEDA network structure installed inside a company LAN. As you
may see, the IP addresses assigned to the PC with the GEDA, belong to the same domain of the
LAN addresses. In Picture 1 the addresses 192.168.0.X are used only as an example.
As the different network hubs are directly connected to the company network, the performances of
the GEDA network will strictly depend on the LAN general performances. Besides, eventual
malfunctionings or any service break down of the company LAN will inevitably affect also the GEDA
network.
192.168.0.X
Station “K”
series 1
192.168.0.X
Station “K”
192.168.0.X
Company
Switch
series 2 LAN
ETH
Station x 192.168.0.X
RS485
Station y GEDA
series n
“K” n
Picture 1 – Example of a GEDA network configuration through a company LAN. Station “x” e “y” are two
not “K” series machines connected through a RS485 serial line.
In order to grant the optimal performances and, at the same time, to provide a connection which
could better support the malfuctionings, the best solution is to realize an Ethernet subnet which is
independent from the company LAN. One possible solution would be to install the GEDA on a PC
equipped with a double network board (the PC minimum requirements are specified at paragraph
3.1). A network board will be used to make visible the PC inside the company LAN, while the other
network board will be used for the connection to the stations placed on the process lines.
This architecture prevents that eventual malfuctionings of the company LAN may affect the GEDA
network, which, on the contrary, will go on working regularly. Besides, the connection will result to
be more efficient and safe as the packets which are transmitted on the GEDA network will be
confined inside the network itself.
As the PC where the GEDA is installed is visualized inside the company LAN, this allows to share
the data stored in the GEDA database.
Picture 2 shows a sample of this connection structure. Also in this example GEDA network contains
two not “K” series machines connected through a RS485 serial line.
series 1 192.168.0.X
ETH
10.0.0.254
Station x
Network
Board 2
RS485
Station y GEDA
192.168.0.X
Network
10.0.0.n Board 1
Station “K”
series n
Picture 2 – Configuration example of an independent GEDA network. Station “x” e “y” are two not “K”
series machines connected through a RS485 serial line.
In this kind of architecture the GEDA network can be implemented by different topologies, as for
example star, ring or a mixed solution between these two types. The most proper type will be
decided case by case according to the specific factory characteristics.
For a correct system functioning, it is necessary to configure the IP address of the two network
boards present on the PC with the GEDA.
As far as the network board used to be interfaced with the company LAN (“Network board 1” in
Picture 2) is concerned, its IP address can be assigned according to the normal IP addresses policy
used inside to company LAN; regarding the “Network board 2” (ref. to Picture 2) its IP address has
to be static and it has to belong to the same domain of the addresses configured on the stations.
For example, if the different stations have an IP address like 10.0.0.X, the “Network board 2” of
Picture 2 will have the same type of address, for ex. 10.0.0.254.
Refer to the technical documentation of the used operative system for the correct procedure
regarding the assignment of the static IP address to the second network board.
Once the GEDA network has been correctly installed and configured, one may proceed with the
software installation. Before proceeding, be sure that the PC complies with the software and
hardware minimum requirements listed below. Some of the software requirements are included
with the GEDA installation package.
Before making GEDA installation, make sure you have updated firmware
and/or software of all stations installed on the production lines.
The GEDA installation procedure is very simple as all the necessary operations are completed
automated. It will take a few minutes to complete the installation as most of the time is used to
install and configure the Microsoft SQL Server and Microsoft .NET .
The GEDA installation package is composed by two executable files:
1. GedaSqlServer.exe
For a correct installation, it is necessary to execute first GedaSqlServer.exe: this application will
install and configure the database managing system and it will install the empty GEDA database.
Should the installation package include an USB key, it will be only necessary to insert the key,
make double click with the mouse on the file.
Once the installation and configuration of Microsoft SQL Server is terminated, execute at the
same way the file InstallGeda.exe: at first, this application will check that Microsoft .NET 4.0 is
installed inside the system; shouldn’t it be present, it will be installed.
The third installation files, SSCERuntime-ITA.msi, installs the “SQL Server Compact” runtime, the
libraries needed to read and write the database files of the machines. This database file must be
stored on a USB key (not all GTP machines can perform this kind of operation).
Afterwards, it will be automatically started the GEDA installation.
For the system correct functioning, it is mandatory not to modify neither the
structure of the folders created during the installation process, nor the
content of the files stored inside.
To start the program, make double click on the Desktop icon or execute the application from
Windows “Start” menu.
To uninstall the programme enter the normal function offered by Windows systems and select
GEDA from the list of the installed programs. The uninstalling will only regard GEDA, while if you
need to uninstall Microsoft SQL Server or Microsoft .NET , they will have to be uninstalled
separately.
Before starting GEDA, be sure you have correctly inserted the hardware USB
key supplied with the application.
Have the PC with the GEDA working in front of you in order to easily understand this paragraph.
GEDA has distributed with its USB HW key. Without inserting USB key into the PC where you
installed GEDA, the following operations will be denied:
Once GEDA is started for the first time, the process lines configuration window is shown. The user
shall enter all the requested information to configure the lines and the stations which are part of
the different lines.
In order to configure the Ethernet connection properly, it is necessary to select the type of
connection:
LAN Subnet: it is the connection type explained in paragraph 2.2.1. The user needs to
enter the first three octets composing the company LAN subnet, for example 192.168.0.
GEDA Subnet: it is the connection type explained in paragraph 2.2.2. In this case the
subnet to be enter is 10.0.0.
In case of connection with not “K” series machines, it is necessary to enter the serial port number
(COM) to be used.
As far as the process lines are concerned, the user needs to enter the following information:
1. Type: indicates the type of process line, to be selected between Production, Repair,
and Service. The choice will be guided by a windows menu.
2. Description: Description of line type, for example “Line 1”.
1. Name: it is the station name. The choice will be guided by a windows menu.
2. ID Line: it is the line number. The related windows menu will contain the ID of the
lines added in the previous section.
3. Description: it is the description of the machine, for ex. “Charge 1”.
4. Serial number: it is the machine serial number or software which composes the
station. The correct communication with the station depends on the input value,
which has to be the same value stored in the machine firmware (this is true only for
“K” series machine).
5. Address: station IP address. In case of serial communication the physical address
has to be inserted.
6. Is Final: this flag needs to be selected if the related station is the last one,
according to the process order, inside the line. This information is requested for
some processing, as for ex. the calculation of the pieces produced by the production
line.
Real time monitoring of the stations: the process lines and the stations input during the
configuration phase, are represented in a graphic mode in the window central part. The
stations are represented by buttons which could have different colors according to the
current status:
o Green: the station is in STAND BY or WORK status.
o Blue: the station is in PROGRAMMING.
o Orange: the station has communication problems (NO COMM status).
o Grey: the station was disabled by the user (OFFLINE status), GEDA will not
receive data from this station until it will be enabled again through the
specific function (refer to paragraph 4.3).
By pressing the stations buttons, one may enter the window “Management” related to the
specific station (refer to paragraph 4.3).
Visualization of the end cycle report: once a station completes a working cycle, it sends to
GEDA the resuming table with all the cycle parameters. This table is normally called Report.
The window right side is dedicated to the visualization of the Report list which will be
received in real time: by mouse double clicking a particular Report, it will be shown the
complete table referred to the selected Report.
Accessories functions: on the top window left side it is present the menu with different
functions. They will be explained in details in paragraph 4.4.
On the main window left side it is shown the tree structure of the process lines and of their own
stations, as they were input in the configuration window during the first start.
When a station on the main screen has a status of "NO COMM" (Orange
color), you may lose data if you do not resolve the possible problem, before
the machine is out of memory responsible of storage of "packets" to be sent.
In case of a shutdown of one or more machines for prolonged periods, it is
recommended to place the corresponding station in the OFFLINE state from
the main screen of GEDA, to avoid delays in the transmission line.
It is possible to enter the managing window both through the buttons placed on the center main
window and by clicking on the tree structure nodes placed on the main window left side. The
managing window is characterized by three modalities:
1. Station
2. Line
3. Factory (this terms indicates the union of all process lines present inside the factory)
Each modality is characterized by its own functions. The managing window is shown like a table
where the different sections are structured like a tree. Picture 3 shows the structure of the
managing window in Station mode.
The shown functionalities are referred to “K” series machine. For the not “K” series machine the
Programing section is not available, as well as for RecDATA TJ and TJ V. Furthermore, for a
certain kind of machines could be other difference concerning the set of available functionalities,
for example in PK Vacuum Codes programing is not available.
1. (Info) general information visualization: window where the main information are resumed
related to a Station, Line or the whole Factory. Through the Info window it is also possible
to put in the OFFLINE status the station, the line or all the lines.
2. (Programing) Management of the Programing data: through this function it is possible to
manage the station programing, i.e.:
a. Working cycles.
b. Global parameters.
c. Codes.
3. (Query) Management and Analysis of the Working data: this GEDA section is dedicated to
the analysis of the Reports sent by the stations at the end of each working cycle. With
these data, it is possible to make three types of analysis: Production, Maintenance e
Quality. This section is composed by a research section by which it is possible to create a
Query by inserting different research criteria, which will be combined together with a type
AND operator; this means that the higher will be the number of the inserted criteria, the
less will be the quantity of the data shown in the next results window. Below a brief
description of the three types of analysis:
a. Production: it is the simplest analysis and our aim is to know the number of the
processed units (“Station” mode) or products (“Line” or “Factory” mode). This kind
of query is particularly suitable for traceability, and in “Factory” modality, It is
possible to retrieve Reports related to a station or a line deleted from Configuration
window. It is also possible to see the statistic of the rejected units, generated by
one Station or on a Line. Furthermore, the operations of printing reports and export
data in standard text format “CSV” are available.
b. Maintenance: this analysis allows to monitor the functioning of a particular
machine through the visualization of the value of all parameters which compose the
Report, including the eventual Alarms. For each analyzed Report, it is also possible
Code: 8.003.7.027_rev.07 pag. 12/18
to see immediately, in the same window, all the parameter values related to the
working cycle and the global parameters which are active on the machine during
the work cycle execution (this functionality is not available in not series “K”
machine). Furthermore, the export data operation in standard text format “CSV” is
available.
c. Quality: it is analyzed the “produced unit”. The window is divided into two parts: in
the left side are visualized all the processed units and, for each unit, it is possible to
see the list of all processes performed on stations along the process line; on the
right side are shown the production statistics and the statistic related to the Alarms
activated on the all stations object of the Query. Through the table of the
production statistics, it is also possible to enter the Alarm analysis window: this
window allows to execute a detailed analysis to understand the reasons which
activated the alarms on the station.
4. (USB Key) Import/Export of data in USB Key: only for GTP machines that allow this
operation, it is possible to perform a data transfer through an USB key. The “Import”
operation allows to read the following data:
a. Work Cycles
b. Codes
c. Report
The “Export” operation allows to transfer to the machine the following data:
a. Work Cycles
b. Codes
In order to perform a transfer operation by the USB Key, it is necessary to set the station in
OFFLINE state.
If the symbol “ ” appears while going with the mouse on any graphic
interface component, GEDA advises the user that additional functions are
available; they can be entered by a double click of the mouse or by pressing
the mouse right button and by selecting the desired operation from the
menu.
In Production and Quality function is possible to perform the query by specifying the “model”
through the Barcode mask, inserting the fixed character of the Barcode. Picture 4 shows an
example.
Picture 4 – Barcode mask example. The inserted characters (‘123’ and ‘ABCD’) identify the fix part of the
barcode.
The same mask can be defined also in programing Codes section, in which you have to create an
association between a model and a particular working cycle. The mask will have a maximum
length of 32 characters, while the read barcode will have a maximum of 40 characters, so the
mask represent the 32 most significant digit of barcodes.
From the main window it is possible to enter the GEDA accessories functions. This paragraph
describes in general all the functions which can be entered from the main window. Picture 4 shows
the functions list as they are shown on the main window.
A B C D E F G H
In order to put quickly all the stations in the OFFLINE status, enter the
Management window by pressing the button “Factory” on the main window
and , in the section “Info” select the flag “Set communication OFF”.
In case of deletion of a station or a whole line, the associated working data (the Reports) are not
deleted from Database, so they are still available for traceability, but only in Production query
and in “Factory” modality (see par. 4.3).
1. Hourly.
2. Daily (Default).
3. Weekly.
4. Manual.
Another parameter to be set is the time in which the backup has to be performed, so it must be
set a time in which your PC is turned on.
With the manual option the user is totally responsible for making the backup, through the
appropriate button present on the window.
Another important parameter is the path and/or the device where the backup needs to be
physically written. The backups are not “destructive” types; the data of the working database will
remain there even after the backup.
GEDA continuously monitors the size of the Database, and if its size risks of exceeding the set limit
(this limit cannot be changed by the user), GEDA will shows a message saying that user should
perform the operation of "cleaning", in which the user can select the oldest data for deletion.
As default set up GEDA writes the backup in the folder “C:\GEDA_DB\Backup”.
When the database will contain an excessive amount of data, GEDA will ask you to perform a
"clean" operation that can be performed using the appropriate window.
Through the backup management window it is also possible to use the function Restore, in order
to restore a previous GEDA status. By using the restore function, the most recent data will be lost;
it is therefore advisable to make a Backup before using this function.
The GEDA database is accessible by anyone through an account with read-only permissions. To
access the database you need to make a connection to the SQL Server instance installed on the
same PC where installed GEDA. Access can be made with the following credentials:
Username: GedaReader
Password: GTP000
In order to access GEDA database from external program, the following string connection must to
be used:
The database name is “GEDA”. The instance of SQL Server used by GEDA cannot be used for
management of other databases. In case you need to install other databases on the same PC
where GEDA is installed, these databases will necessarily have to be installed on a new instance of
SQL Server.
For installation and configuration of SQL Server, refer to the appropriate Microsoft documentation.
The instance of SQL Server used by GEDA cannot be used for management of
other databases. If you need to install other databases on GEDA PC, you have
to install and configure another instance of SQL Server. Changing the
configuration of the SQL Server used by GEDA may cause malfunction of the
entire system.
GEDA is a software for monitoring and acquiring data from process lines, and as such it must be
installed close to the production lines, but if the need arises to be able to monitor the status of
individual stations or to perform queries and analysis from different locations other than
production, then on any PC within the same Ethernet company LAN GEDA Client can be installed.
GEDA Client is a GEDA plugin that connected to GEDA and its database, allows you to take
advantage of the following features:
GEDA Client necessarily needs GEDA to work. To better understand this fact, below there is a
diagram showing the global system architecture composed by GEDA and GEDA Client.
Company LAN
GEDA
GEDA Database
Production lines