GPG database structure training.

mp4

[ 00:00:03 ] the recording. Now, the structure of the objects, as we were saying, is
available for any given object. As you can see for the text, we have the text structure plus
all the common related HMI parameters. Maybe I can, I'm not sure if we have in our
system an analog value, but if not, we can create one. For the analog values, whenever
we create an analog value, we also have the point where it is coming from, the ID or the
analog signal. We can associate a set point, so writing command to associate it to this
analog value. So when the operator clicks on it, it can actually enter the analog value and
send this order to the ID or to the PLC. The scale, the different limits for the analog
values, et cetera, plus all the standard tooltips.

[ 00:01:08 ] So we can see for any given object, the location of the object and all
theparametersoftheobjectarestandardforeachtypeofobjectandwehaveallthese type of
parameters. Another thing that we will discuss directly from the database perspective is
the interlocking. Any command can be blocked from the operator being able to execute
the command by associating this command to different interlocks. The interlocks are
digital points within the database that are going to block your command execution. When
we see the command object, you will see that for any given device, let's say a G60, we
want to add a new interlock. We will create this table where we select which is the
command that we are going to Let's say this one, for example.

[ 00:02:06 ] I mean, we can use any. Which is the interlocking name? Breaker open.
Okay, for example. And which is the point that it's going to block this command? The
point can come from the same ID, from the same G60 where the command is, or it can
come from the PLC, which is the level two, or from any other device. You can see that we
can select any device with any status and even the status that it's going to block this
command. So for example, when this digital point is on, I'm going to block the command.
Okay? Or when it is off, it's going to block the command. And we can create additional
interlocking conditions. So if I select the same command, I can use a second point.

[ 00:03:05 ] that it's going to block this given command. We can add multiple interlocks to
the same command. Now, this task, as you can see, is very time- consuming to do
directly from the configurator. It is good for customers to use to make a quick change in
the system. It is easy, it is structured. You can select the different IDs. It is easy for
anyone to use to make minor changes. But if you want to configure all the interlockings
for all the relays, for all the commands, you can spend a lifetime configuring this table
through this interface, let's say. Doing this task directly from the database, it's going to be
way faster. I mean, a 100 times faster.

[ 00:04:01 ] I'm going to save a few interlocks so we can see them in the database itself.
Last but not least, the PLC. The PLC is extremely tricky to configure directly from the I
recommend always to do so directly from this interface. You know that you can add your
own logic boxes you can create. I'm going to create a very simple logic so you can see
how itworks from the database perspective. You can create your logic using your
graphical configuration and all this logic and graphical configuration which is taking points
as inputs from the level two table and creating outputs. All this PLC is also stored in the
database so you can see and modify and even create your own logics from the database.

[ 00:04:59 ] But you will see later on that it is a let's say a complex task to do or to
perform and anyway I will show you how it is done but I would recommend always to
make the PLC modifications and creating your own PLC directly from the editor itself. Let
me just assign a few outputs. I'm going to select andconfigure the inputs so you can see
that for the digital input in the PLC we need to select as which digital input it is. Let's say
it's coming from the G60 or for the new one status number one when it is active and the
digital point number two we are going to assign from the G60 for example and the first
point in the G60.

[ 00:05:54 ] So when one or the other is active I'm going to activate my output. Now the
output if we check the properties there's nothing to configure. There's only the size, the
text that is available here, the location where it is placed within the canvas which in within
this graphical area where we can configure the system but I don't need to configure
anything. Why is this? Because the output digital output of the PLC is actually a new
point a new level two point that we are creating. It's a new point let's say manufactured
by the PLC which is which is going to behave not by reading something from the relays.
It's going to behave according to the inputs and the logics that you are creating in the
database.

[ 00:06:46 ] take note of this name digital output one that I'm creating right now in the in
the PLC. Once I save my PLC you will see that this new point is created in the level two
table. So if I check my status points in my level two table I have all the points from the
relays but also the level two points which come from the PLC itself and also some
internal conditions such as the substation is in local remote, there's any alarms which are
active, the system is busy executing a command but as well it includes the PLC points.
You can see a new point which is digital output one which we can change the name, we
can create an alarm on it and this is everything coming from the PLC itself.

[ 00:07:37 ] We will see how to use these points from the database. So very basically you
do understand the structure that it's being used from the configurator level one, level two
points. All the level two points are used both for the graphical configurator from the PLC
and of course I missed the level three communication. We can create a level three link
and we can assign, sorry the database is not compatible with this system, but we can
create the same data points coming from the level two table to any level three what we
call level three or any master communication protocol or server communication protocol
and it follows the same structure as the level one. We have general tabs, we have status
points, analog points and command points and you will see that from the let's say status
point we can assign any point within the database because again we are looking at the
level two table. So all the points in the database regardless if they are coming from the
PLC, from the IDs, no matter what protocol, we have them all listed here and we can
create our own tables. We can configure the groups, the information, anything that we
want, okay.

[ 00:09:12 ] Compatible. I didn't update the table. We did it with the version 1. 113 and
this is the configurator for 1. 2. 0. Anyway, I'll show you now how all this configuration is
available in the database itself, how it is interconnected and which are all the
interrelations between the different tables in order for you to make all necessary
modifications, okay. Now let me not save it. I'm going to open the database. Where is the
database first of all? database, all your projects are stored in CGPowerProjects. In my
case, the database that we used in our first session was called TestSite and where is
TestSite?

[ 00:10:16 ] TestSite, okay. This is the database that we were working on right now. Just
save, okay. As you will see, the database is in CFG format and the first thing that you
access is the database. So, you will need to have in your computer Microsoft Access
installed in order to open the database and the complete configuration. Which version,
sorry David, which version we have to use? I use 2016 but the database is in 2010
format. So, anything above 2010 will work. Okay, good. So, to open the database it's just
very simple. You just open Access, File, Open and that's it. Let me just change it here so
you can see how it So, when I double click, it opens Access and it asks for a password,
okay. The database are all encrypted, okay.

[ 00:11:26 ] For cyber security purposes, they all come encrypted and once you create
your project, you can change the database password. By default, it is 7169 is G in
hexadecimal format but it's 7169. Once you enter the password, you have full access to
all the different tables your configuration, okay. And everything that you configure in the
configurator software going to be stored here. So, anything that you can do in the
configurator software, you will see in the database, okay. Now, it is very important to
understand therisks of modifying the database from scratch, right. From the configurator
software, the configurator software displays all the information that the user can actually
change and it provides criterias to prevent the user from entering values that are not
supported by the system, right.

[ 00:12:41 ] So, some values cannot be negative, some values cannot be above a
number, some values are only on off. All these type of limitations are or restrictions are
available in the configurator software because we want the configurator software to be
used by customers or anyone. But, these limitations are not applicable in the database,
okay. There's lots of interrelationships between the different tables. This is not created,
this is created automatically from the configuration software but it is not created
automatically from the database, of course. If you make any manual change in
thedatabase this is not going to relate to the different tables. So, this is why only we
allow, Imean we should allow ourselves as engineers for this kind of system, which we
are developing the complete project and we are experts on the system, to have access to
the database, okay.

[ 00:13:40 ] This is the first point. I do not recommend and this is something that you
should never do, give the passwords and the access to the database to customers
because any minor change, I mean, it can be a space that you tap on the database can
screw your complete configuration, okay. And this is a point that not only happens to
customers but also happens to us. So, anytime that we are changing, this is something
that I haven't done, anytime that you want to modify the database from database itself,
make a backup. So, copy and paste the database that is enough to create a backup,
okay. I have my backup of the database. This is extremely important because any
mistake that you make in the database, the database will not run.

[ 00:14:34 ] You will not be able to open it in the configurator, it will not run in the
concentrator or whatever, okay. So, remember to make a Now, moving again to the
configurator software, let's start with a good part. First of all, let's talk, there are many
tables, I'm not going to cover all the tables, this we can have in a separate session, but
I'm going to show you the main tables that you would configure in the system. So, first
thing that we did in the configurator was configure a level one protocol, okay, how I
communicate with the IDs. In this case, we communicated in 61850. So, you will see that
we have L1, which is level one, and followed by the protocol name. We have ICs 101,
103, 104, 61850.

[ 00:15:25 ] This is 61850, it's both edition one and edition two, you don't need toselect
either one or the other, it's both of them are supported simultaneously, okay. So, Modbus
RTU, Modbus TCP, all the communication protocols are available here in the and they all
follow the same format, as you can see. We have a general table, which includes generic
information and protocol specific information, digitals, analogs, commands, and set
points, exactly the same thing that we, the structure that we saw in the protocols. If we go
to the 61850 table, okay, so, level one, 61850, okay, where's the general tab? Okay, you
will see that we have an identifier, which is the number, an identifier column, which is
available in all the tables across the, across the okay, and this identifier is a unique
number within the table that will help us interrelate the points from one table to the other,
okay.

[ 00:16:40 ] So, when we make a reference to any given table, we're always making
reference to this number here, okay, the identifier. Identifier origin and identifier ID, this is
something that you don't see in the configurator software, and you don't need to
configure, you just leave with your standard default values. We have given default values
to all the, you can see here at the very bottom, the default value. If you keep your value,
that is okay, okay, that means that it's a value that is supported by the, by the system,
and it's the standard default value that is created by the, by the configurator itself. If the
link is active or not, we can select here, select or unselect, this is equivalent from the
database.

[ 00:17:28 ] If I check my 61850 configuration, I can create, if the link is active or not, this
is the same, active or not active, that we see here in the configuration. The thread, this is
an important point. The thread is, which is the communication thread that actually the
concentrator is going to be using. All the communication protocols, and when we create,
when, if you remember, when we create a communication protocol, you first need to
create a which is configured for a specific protocol, okay, so whenever we create a new
protocol, let's say I want a Modbus TCP, this is going to create a new entry, a new group,
this is a new thread in which I can add many different devices, new, new, I can add
multiple devices to a singlethreadsingle thread.

[ 00:18:23 ] Internally, this is the communication path that it's, the communication link
actually the different devices, and all the devices within that thread are going to let's say,
in series, if it's a Modbus, it's first going to send a query to the first device, then to the
second, to the third, within the same thread. Different threads are running in They are
completely independent thread and communication threads to the ID. That's why
mentioned in our first discussion that whenever we are creating the communication
groups, it is good to not to have more than, let's say, 10 devices or 15 devices, especially
when we are communicating with, in a Modbus protocol, for example, which is a serial
protocol that you always need to send query, answer, query, answer.

[ 00:19:21 ] Extremely important, the threads are also extremely important for serial
protocols because the threads is a single communication link that we can assign to a
specific port, right? A communication port in your hardware, in the GPG, we have lots of
serial ports. We want a specific thread to be wired to a specific port. This is where we
configure the thread parameters or the communication port parameters in the database.
So, this thread actually makes reference to a table, which is called threads, easy to
remember, which includes all the communication links that this database has, including
the internal threads, so the PLC cycles, the system which is checking the master slave,
the sister internal system, which is checking when an alarm is active, when it is not
active, and creating all these acknowledged, not acknowledged systems.

[ 00:20:26 ] These are, by default, all active, okay? You cannot even deactivate from the
configurator. From the database itself, we can see that they exist, and whenever we
create new protocols, you will see that new entries apply. So, when I created my first
61850 protocol, okay? When I created this new 61850 protocol that is called new, okay?
This created a new thread called new, which is thread 19, and we can see in the 61850
table that the thread that was created is thread 19, okay? So, this is the first interlink
between the thread table, and again, I said before that all the threads, how can I open the
all the tables are interrelated by the identifier number. So, you can see in the threads
table, the identifier number 19 is what I'm going to use
[ 00:21:35 ] Generic table to identify the thread, thread 19. Now, there are many different
parameters, ID, comps, level 2, for every single thread that we have, for every single ID
that we create. We are going to be identifying when we have a level 2 point, which
identifies if the system is communicating or not. We have communication offline, online
for any given ID. This is a point that it's created. It's a level 2 point that it's created
automatically by the system whenever we import a new device, available for every single
protocol and every single device. This level 2 point, point 15, is actually the level 2 point
related to this 61850 device. If we go to the level 2 tables, level 2 digital table, we will see
that point number 15 is level 1 communication failure created for this specific device.

[ 00:22:53 ] As you will see, communication failure is the point which is created here.
Mnemonics, something that you don't need to worry about. The out- of- service, you can
actually create or put the device out- of- service, any given ID. You can just right- click
from the HMI and put it out- of- service. That means that you block all the
communications to this There is a level 2 point that you can actually read to see if this
device is out- of- service or not. This is point 17 of the digital tables. If we check the
digital tables, point 17 is out- of- service for this specific device. So on and so on. The
text of the Let me just follow. I know I'm taking a lot of time, but this is important because
it's going to be the same for all the protocols.

[ 00:23:55 ] So once you understand one, you understand them all. Level 2 ID point is
whenever we create a new ID in any given protocol, this creates an instance as well in
the level 2 tables. You can see that the level 2 tables also follow the same format. We
have the IDs for each device, the digitals, the analogs, the commands, and the set
points. So in the level 2 IDs, we have all the list of IDs that we have in our database,
regardless the protocol that they are communicating on. You can see that the ID number
1 is our G60, which is the point that we created. So we see, going back to the 61850
information, the ID that we have just created from 61850 table, it's ID number 1 in the
level 2 table.

[ 00:24:58 ] So let's say that I have a lot of devices and I want to change the text. Let's
start with something simple. Creating a complete database is something that will take
time and you will need to play a lot with the system to create automatically your own
configurations. We have many customers, actually, many partners doing this type of But
something that any engineer will do is change the text, how the device is called. So I
don't want to call it G60, I want to call it G60 number 2. If we have to complete, we have
100 61850 devices doing this way. Just changing the text directly, copying and pasting
from an Excel file is also possible. You can copy and paste the complete names, tags of
your devices directly into this field.

[ 00:25:51 ] The ID, this is the domain from the 61850 parameter. This is exactly the
domain when we check in the 61850 configuration, the physical device name and logical
device name. You will see that the domain, it's exactly what it's written into this
parameter. The four different IPs that the device can have, they are also configured here.
The main IPs that you see that you could configure here, you can configure directly from
the database. The ICD file, this is just the text. Once you import your ICD file, you can
see this parameter here, the ICD file name. This is stored just for reference, but it's
stored in this field. Reconnection delay, digital intervals, etc, which are specific for the
protocol. The digital intervals are the integrity period that we want to use.

[ 00:26:51 ] The reconnection delay is if we lose the communication, how many seconds
we want to wait until trying to reconnect with the device. All this is stored in this table, in
the level 2 ID table. If we want local time, if we have the general interrogation trigger
option active, all this which is available from the local time checkbox, or the general
interrogation option, all this available in the level 1 generic table. Now, let's see all the list
of parameters. You can check that everything which is available in the configurator, it's
available here. One very important thing to once you are modifying your database in
Access only saves or only asks you if you want to save changes to the structure.

[ 00:27:57 ] So if I move the size of a if I reorder the field, if I make a filter of my database
Access, I mean, of my Access is going to ask me if I want to save or not. But be careful,
because any changes in the values of the so let's say instead of 12, I write 13, this is
already saved. It will not ask me if I want to save it or not. Any change in the database is
automatically or in any field is automatically saved. So be careful just when you are
modifying the system, the structure should never be saved. Whenever Access ask you,
do you want to save the configuration, you just click no. You don't want any filters or
changes in the structure to be saved because it doesn't make any sense.

[ 00:28:53 ] If you make a filter, for example, you will not be able to read it from the
concentrator itself. So whenever Access asks you if you want to save, you just click no.
Any change that you do in the database, copying and pasting parameters, this is
automatically saved. So don't worry when you are clicking no to save, because it's
instinctively. I mean, we all do it. We are used to Word, Excel, Access, I mean, Word, all
the other systems where you always click when you close, you save. Here, you don't
have to save. So all the parameters from the IDs are available here. Do you want to
save? No. You always click no if you want to save. That's just a change that we need to
get used to. I'm not saving anything.

[ 00:29:39 ] Just let me close the other. From the level 1, who we're discussing about the
61850, the level 1 digitals, we have a lot of points. Every single point that we are
importing from the ICD file, we are going to have here. We can see the text. We can see
where the point is coming from. What is the 61850 point and what is the text? The text,
we can change here. So we can see that very easily. Status 1, status 2. We can very
easily change here. While doing it in the configurator, it will take a lot of time. Of course,
we can always open. This is something that I do. For example, we can open an Excel file
and just create a bunch of points. This, we can copy and paste into our database.

[ 00:30:49 ] This very easily can allow you to change all the text values, even if you're
using multiple names. I mean, it's easy to do, something that it will be difficult. Sorry,
Marco, do you have a Okay. Anyway, just keep in mind that the level 1 text is just for
reference. All the texts and data that we use, remember, it's always used from the level 2
tables. You will see that any given point, as we did for the ID, we have a related point in
our level 2 table. This specific point, which is the GGIOST indication number 1, is going
to create an entry in my level 2 table, which is entry 22. If I go to my level 2 table,
Digitals, I will see that entry 22 is this new point that we are referring to.

[ 00:32:02 ] The text, we can modify here, and if we have dual language, we can modify
here. You can copy- paste. I already have my copy- paste from the level 2 table. We can
also copy- paste from Excel and modify our text in the level 2 table. Do you see a level 2
and a It's all braided. When you do a maneuver in a you remember the and then you go
to all the 12- digit tables and you use that ID to make the same modification. I would
never do that. Okay, okay. Sorry, sorry, please continue. No, that's good, that'sgood
Internal clarifications means that at least someone is understanding what I'm saying, so
I'm happy to hear this. This creates all the different points in the database.

[ 00:33:01 ] Every single point that we import from the ICD file, it creates an entry in my
level 1, 61, 850, Digitals, and I can see all the points from all the devices. Now, this table
includes all the points from 61, 850, from all the devices in 61, 850. You will see that we
have an ID general field, which will tell us which device this point is coming from. We only
have one device, so it's only showing zero. This is because in the 61, 850 generic table,
identifier zero is this specific ID. If I was to create, for example, in Modbus TCP in our
database, we have two different devices. We created this table. Actually, we have a lot of
different devices, even in different threads.

[ 00:34:02 ] If we check the level 1 Modbus TCP table, you will see in general that we
have multiple entries. We have entry number zero and entry number one. If we check the
digital points, we have status one from device zero and status one from device one. You
see that all the points from a given protocol are all in the same table. It is easy to make
changes actually to all the devices which are from the same type directly from the
database itself. I'm telling you, and probably this is scary. To start with, don't make
changes to level 1. Importing files, XMLs, etc. is very easy from the configurator. You
don't need at first to modify the level 1 tables. The first thing that it's probably interesting
for you to do is tomodify the level 2 tables that I will show you later on.

[ 00:35:06 ] The same application for every single digital point, all the parameters are
available here from the commands. Well, we didn't import any command. Analog values.
Sorry, this is Modbus TCP. Analog values we imported from the relay are also available
here. Again, same parameters that you see in the configurator are going to be present
here. If you want to see analog value, this given point, any analog value, we will see that
there is a reference to the level 2 table. Level 2 analog value, this specific point is stored
in the row number 3. If we check this GGI01 SD health status, if we check the level 2
analog values, number 3 is the same.
[ 00:36:08 ] So this is how the level one tables are created. Everything that you import is
available in the database in the level one tables. It creates an entry in the level two
tables. This is very important. Even if we want to create our own configuration
automatically, we would need to create the entry in the level one table and create and
populate all the references in the level two table, okay? This is only going to be useful if
you're using scripts. We have customers creating its own scripts through Visual Basic or
any other programming language that populates automatically the database with this
information. If you're going to do it manually, it doesn't make sense. It's easier to do from
the configurator itself. Now, the same thing happens for the level one Modbus tables.

[ 00:36:59 ] We see the Modbus TCP general tables. see the two IDs that we have
created where we have an entry. The thread for the Modbus, it's thread 20. So if we
check in the threads table, we will see that we have a Modbus thread, which is called
new. Actually, I didn't change the name in the database in the configurator. It's again, this
thread is going to have all these devices. This is the thread I'm referring to, okay? This is
Modbus TCP, which is called new. And that's exactly the same structure. There's no
difference between the 61 and 50 and the Modbus TCP. It follows the same structure. A
general table with all the default values, IP address and timeouts and all this stuff
available in the generic table. All the digital points where we have the status, the address,
Modbus address and the level two reference, okay, where these are created, the level
two reference for everything, digitals, analogs, commands and set points.

[ 00:38:25 ] Do you want to save? No, just remember that we don't save anything. All the
other protocols are exactly the So it doesn't make sense to follow the different protocols.
Now, a little hint when we're creating all the level two and let's start with the level two
tables. All entries within level one, the devices in a specific protocols are going to create
an entry in the level two. let's start with the level two IDs. The level two IDs includes all
the devices that we have in the system, okay? And this is important because you will see
it creates a new entry for every single device where you can actually change the name of
the devices in dual language. So both the standard name and the extended name or dual
language name, you can change here. The bay where it is in or not. And you can change
the, Imean this is just related to 61850 and the influx database. So this is something that
you don't need to change. If you want to check which parameters to change, it's very
easy. Just open your, for some reason, I closed my configurator software.

[ 00:39:57 ] Test site. OK, so all the parameters that you can see here level 2. It is. These
parameters. You can modify directly in the database. This is a good way to know. Which
parameters should be left by default? And which parameters you should change and
modify? OK, so just check at the very beginning when you're first learning about all this,
just check. Oh, here I can check. Change the text, the auxiliary text and the So here I
have my text, my auxiliary text and my Bay. OK, and I can make all the changes directly
in the in the database. Now if we check at the level 2digitals2 digitals. This is. Very
interesting, you have an entry for every single digital point that you can use and that you
have in your database.

[ 00:40:57 ] OK, these are all double points. Where we have the identifier. This is again a
unique number. It's starting here and it adds one for every entry, so you just do the same
thing. The index it's something that it's not actually used for much. It's just need to be a
number which is sequentially increasing. It doesn't need too much with the identifier, but
it does. It's not related to. I mean, it's not used for the interrelations between between
tables. So if you're going to modify this and create it on your own, just. Give the same
number as the identifier that will do OK. The mnemonic. It's something that it's. smart.
Uh, think that we have in the in the database that you should know how it is working. The
mnemonic is used.

[ 00:41:57 ] Uh, to configure all the points. To the HMI objects. OK, instead of using a
unique identifier. We use a reference to the point which takes into account. The device
that this point is coming from. The device is shown in the level 2 ID. OK, so we give. The
identifier of the device. That this point is coming from. And then a generic text. That you
can see it's built automatically. How do we build this mnemonic? This is automatically
done by the configurator, but if you understand it, it's really, really clever. It adds the
name of the protocol level 161850. The same thing that we did for our level 161850. So
let's let's look at the 161850 points. Level 161850. This is just the name of the of the table
and then it adds the 161850. Point. Uh, of the I mean within the ICD file so you can see.
In your level 2 table.

[ 00:43:20 ] your level 2 table you have the 61850 path and you would say and why is this
clever because if you look at the structure level 161850 and the point this does not
include the physical device name and logical device name this point is going to be
common for all the devices of the same type let's say we have 10 feeders 10 feeders
which are exactly the same same 61850 configuration 10 feeders are going to have this
point because all of them communicate in 61850 they all have ggio1 uh uh indication
number one which means that our digital objects that we're going to be using in the hmi
we can build objects that refer to multiple ids to the same point from multiple ids this is
what we call template so when we create a breaker we can assign the breaker point
which is xcbr uh indication uh estival uh xcbr uh whatever

[ 00:44:34 ] this same breaker and same screen can be assigned to multiple ids by using
this mnemonic point because the point associated to this uh to this digital uh value is
always the same so the hmi is actually going to search for this mnemonic in different ids
which ids the ones that we define so in this case this point is coming from id number zero
i mean we only have uh sorry the id number one if we check in the level two table we will
see that id number one is the g60 okay the only 61850 device but if we have a hundred
of them we can assign this digital i mean this uh hmi object digital object to device
number one number two number three number four and it's always going to search for
the same uh mnemonic point so that's why it is uh let's say relatively easy uh and uh uh
to create screens for multiple uh ids what we call template screens
[ 00:45:41 ] by referring to this uh this uh mnemonic uh name so mnemonics for 61850
are created with the name of the protocol and the 61850 structure okay uh the slash zero
is created automatically and this is uh included by default because certain points
especially for the commands the same 61850 point you can write it to one which is one
command or you can write it to zero which is a separate command so you can have the
same 61850 point with either one or zero in digital points it doesn't make sense but we
include a zero by default so it's one specific instance of this uh of this uh 61850 point so
this is how we create uh the mnemonics for 61850 if we look at a Modbus point okay this
is for example a Modbus TCP point we have to follow the same structure the name of the
protocol underscore the group the address and the point value that we have so if we
check in the 61850 in the level one

[ 00:47:02 ] level one sorry in the Modbus TCP digital points we will see that we have uh
sorry it's the function code we will see that we have one point that is status number one
function code number one address zero zero one and uh and uh sorry and the and the
mask right so these three parameters is what we use to build the mnemonic we write the
function code the address and the mask and if we check in the level one table actually
we can see that this point which is in the table uh level two table 155 we can see in the
level two table that the point that we are referring to is 155 okay the mnemonic is built in
this way so all the devices we have ethernet switches we have Modbus generally motors

[ 00:48:09 ] in the uh mm300s for example for motor protection relays we have hundreds
of them in the installation they are all going to have the same Modbus map so they are all
going to have the same Modbus address okay this is how the mnemonics are uh created
and we will see how they are used when we talk about the digital objects um okay so
looking at the at the parameters that we can configure from the level two digital points the
text copy paste text extremely easy to do with the with the with the access if you're not
familiar with access you can just copy a table imeancopy acompletefieldor
acompletetablepasteitintoexcelandmake all the modifications that you want search
formulas whatever you want and then paste it back this is something that i

[ 00:49:03 ] used uh that i use a lot for this kind of uh of configurations uh if the text is on
and off what text we should show in the hmi so we can modify here text on text off for the
error and undefined as well if the point is an alarm or not so you can see it's exactly the
same structure that we find in the in the so this is showing that the database is not
compatible all the different points that you have here is what you would have available to
configure in the database okay so all these parameters or every single device and every
single point you can directly modify in the database okay same if it's an alarm if it's not
alarm the groups even the groups if you want to group them you can just i mean copy all
the different groups from uh from this uh from this table itself so very powerful tool at
least let's say as an entry level to modify

[ 00:50:12 ] database you would be interested in modifying your text your text for on off
error undefined or whatever even if the structures if they are alarm or not and uh and the
groups and the group level all this you can do very easily from the from the database
itself any questions no okay same thing for the analog values so the analog values follow
the same structure identifier the mnemonic which is the protocol name and the 61850 uh
tag or if we are talking about modbus it is the function code and the modbus address
okay for the text auxiliary text etc exactly the same as we had before commands exactly
the same and set points exactly the same

[ 00:51:12 ] okay so here we have in level 2 all the database all the points coming from
the plc from the ids all in a single day in a single table easy to filter to group uh and to
modify directly from the database changing the names all the names you can create your
own formulas i i generally use once i create the 61850 structure uh i do i search and
replace uh formulas uh for for given devices so this speeds up very significantly the
configuration time of your points okay now let's jump to the hmi application the hmi
application can also be uh configured directly from the from the database itself uh the hmi
application so we have level three protocols that we will discuss uh later on but for the
objects uh which are the hmi objects that we use we have all this set of objects they are
the same objects that we have in our configuration tool

[ 00:52:22 ] okay you see we have the alarm object the text object the presence object all
these have a related table so all these objects are these tables plus the list of tabs the
number of screens that we have in the system which is this table here so from the tab uh
screen we can create a new uh let's say screen in this case when we created this new
screen we created this uh tab which is called new tab we just gave it this name if we
check the properties of the tab you will see that the name new tab is here with the size uh
certain number of pixels wide certain number of pixels this in the database you will see
the name the background color the image that we are using the image that we are using
as a background

[ 00:53:23 ] this uh for this screen we used a single line diagram to to display the
properties so this is also uh in the database the type if it's a pop- up or a or a or a just
normal screen you can select here the size of the of the screen the colors labels
everything that you are configuring this menu even the size and color it's available in the
uh in this field okay in the tab field every single tab new screen that we create we will
have a new entry within this table now what about the objects all the objects that we
create within a tab okay remember that the going to tell us where which tab each object
is related to so if we want to check let's say a digital object object digital okay we've used
a few we can see a specific object

[ 00:54:33 ] where we are going to configure and let's open a digital object any digital
object this one it's coming from the g60 so first thing that we need to configure is the id it
is coming from and the point it is referring to so this uh we can see here which id it is
coming from id number one is id number one g60 we can check in the level two table ids
that id number one is g60 okay this is how they relate the object with id and the
mnemonic as we said before we are not using the identifier within the analog objects we
are adding the mnemonic so this is the structure the that we create not to use the
identifier but to use a common uh let's say name for all the devices uh which shared the
same configuration okay so you can see the demonic is referring to the same point that
we are seeing here in our configuration all the

[ 00:55:43 ] images that we are uh referring to all the um parameters that we have in the
object the size the location if it blinks if it doesn't blink everything is available here okay in
this in these uh tables applicable for every single device if we check the analog object the
analog well we didn't have any analog objects in the in the screen but uh we can create a
new analog object uh from from scratch from the screen let's say that we have this device
the device number one it's having so from device number one i'm going to take this point
this is the mnemonic uh and it have a specific format i mean the size

[ 00:56:36 ] the font i'm just going to leave it by default and this is how i can create and
i'm going to place it in 100 and 100 i have no idea where this is going to appear in which
tab am i going to set it i'm going to set tab number zero which is the only tab uh sorry
actually it's tab number one it's the only tab that i have in my system so i'm going to place
it in tab number one the size i'm going to leave it uh as uh whatever number of pixels uh i
want to have and that's uh and that's it so i have created directly an analog value that is
going to be represented within the the hmi system directly from the database itself okay
so you can see it's only a matter of configuring the the parameters on the on the on the
database

[ 00:57:42 ] Z number one. Okay, so I created a new entry. Same for the any other object,
presence object, you just check the features and the parameters that you have for any
given object and all this you can configure in the database. Now, to finalize, I would like
to mention how the system is configured from level 3 and this is probably extremely
important. Whenever we are maps to act as a gateway, and let's do it from the
configurator, I want to create a 104 link. I create my 104 link. I suggest to create the 104
link directly from the configurator because this creates the threads and creates the
structure of your 104 link automatically in the database. You will see that the
configuration, oh, I forgot it's not the same version.

[ 00:58:44 ] The configuration that we have here can all be set directly from the database
and the status points that we are going to be creating. These might be coming from many
different types of devices, right? So, generally, when we communicate upstream, we are
going to take points, a few points from every single place in the database, and we are
going to send them upstream. So, doing this here manually is taking a lot of time, okay?
You can do it. I've done it a million times, but once you learn how to take the points
directly from the this is going to save a very, very significant amount of time. So, let's see
how we can create points directly from the database to convert from one protocol to
another.
[ 00:59:37 ] We can see that we already created a 104 link. So, in our 104 generic level
three, IC104 generic table, we already have a link, a thread created, thread 21, which we
can see in threads that this was already created, and this is good because I did it through
the configurator. So, all these entries in the database, it's already done by the
configurator. I can change the IP address. I can change the specific parameters, the T1,
T2, K parameter, W, all the protocol- related parameters we can change here directly, or
we can do very easily from the configurator. So, this is already done. And now, I want to
create all the list of points. So, if we've seen the level three 104 points, this follows a very
basic structure.

[ 01:00:34 ] We have an identifier, which is from one, two, three, four. It's just a
consecutive number. ID, general, which is which link, 104 link this point is related to. You
have to think that we can create multiple 104 points. We have multiple masters. So, each
master is going to have its own 104 points. This will create multiple entries in our 104
general tab, I mean, table, point entry number zero, number one, number two, and each
of the points, digital points that I'm going to create needs to be related to this, to which, I
mean, to understand to which master I need to send the point to, okay? So, this zero
makes reference to the generic entry zero, which is this specific client that I'm going to be
communicating to.

[ 01:01:28 ] The group, the status text, this is just the text for your reference. You can put
whatever you want. Normally, I copy the text from level two. I paste it in this text
parameter. The groups you can create here, if it's a double, I mean, the address, if it's a
double point or not, here you have the digital point that you are going to bereferring to.
So, point 29 means that from the level two digitals, I'm going to take point 29, okay? So,
point 29 is this point coming from this G60, and that's pretty much it. It's not constructed,
and it's not, so it's not a constructed point. Let me show you what constructed means.
Constructed is when you want to build a double point coming from two single points,
okay? So, if you check in the 104 configuration, you can build

[ 01:02:45 ] you can select the point. This is the same thing as selecting which is the
database level two point that we are referring to, and you can build or not a constructed
point. You can select a second point to build a constructed point. In this case, I'm not
interested in doing this, and you can build your own parameters. Now, this is extremely
good because I can copy- paste and I can build my own complete 104 mapping straight
from the database. What I do normally, I create a for example, any point from the
configurator. I copy the table, paste it into Excel, and I have all my groups, my names, my
status points, etc. So I want 10 points. I want 10 points, I create 10 points. This, I know it
needs to be consecutive.

[ 01:03:49 ] They are all assigned to group number 0. I want them all to be in group
number 1. This is consecutive, so 101. I just give the consecutive addresses. They are all
single points. None of them are going to be This, it's not constructed. I'm going to be
using for point number 1, number 2, a set of level 2 points. Which level 2 points? I don't
know. We can just pick, open the level 2 table. I want from 29 to 43. You can pick random
points. I mean, random points. They don't need to be consecutive. It's any point will do.

[ 01:04:47 ] The only thing that you need to take into account when you are building this,
is that you need to include for any field which is It does not allow, and this is just a thing
with access. It needs an empty string to be included in the system. How do you include
an empty string, just nothing within your database? You need to include open question
marks, close question mark, sorry, speech marks. You just copy the speech marks, and
no field is empty. You can see that no field is empty. I can copy my 104 mapping, and this
is coming from any device. I just go to my 104 table, level 3, 104 digitals. I paste it, and
now I have my 104 mapping. Imagine doing this from the configurator. It takes a million
times more than doing this directly through an Excel file. Now, if I close all this,

[ 01:06:07 ] and I open the configurator. Hopefully I didn't screw anything while doing the
changes, but we should see.

[ 01:06:25 ] So if we check the level four configuration, which is anyway not compatible,
but it should show something, ah, it's not. I need to create it with a new database. But
this is just because the database is not updated. But you will have the status points
directly configured here. And you can modify them directly from the configurator. Maybe
the HMI point, it will be able to open it. we created a HMI point directly, ah, an analog
point directly from the database. And we can see it here. The location of the point is
exactly what we created. Okay. The size, the configuration, et It's, ah, it's directly showing
up here in the, in the, the page.

[ 01:07:18 ] So I believe that this is enough information for one day. don't, ah, I don't
expect you to, ah, to be experts on the database configuration. It's just for you to
understand that everything that we do from the configurator is available in the, in the
database itself. The database start doing minor changes, such as the text, changing the
text of the different points. It's very easy to do in the, in the database. The next step
probably it's creating your own level three mapping points, such as I did right now. With
the level three mapping points, it's something relatively easy. And then if you have, ah,
someone that it's very, very motivated, ah, you can build your own standard solutions,
populating the complete database, ah, from, without using the configurator at all.

[ 01:08:18 ] So just for you to know, we have a partner, for example, in the UK, which is
building substations for national grid, and they build everything in an Excel file. They put
how many bays, how many transformer bays, how many incomers. They click a button
and all the configuration is done. 61850 configuration, HMI mapping, absolutely
everything is, ah, is populated, ah, by default. So it's something that, ah, that you can
explore, but just step by step. Okay. Thank you. Thank you. Thank you. Thank you.
Maybe we have these, ah, registration, ah, for, ah, to review your steps, because I
brought something down, but it is useful to, to see what are your changes in this
example. Absolutely. I know that Teams, ah, gives the record online. let me stop, ah, the
recording.