[00:00] In this lesson, we'll take a look at creating tags for Omron FINS device connections. We can see here I have a device connection already configured. And I want to access some values inside of this device connection. There are a couple of ways to do this, one option which I'm not going to show you, is manually creating OPC tags. So going to the designer and creating an OPC tag. It's kind of a slow method to do so I'm not even going to bother showing you. Instead, I'm going to show you the addresses page here on this device connection. Now this is an Omron FINS TCP connection. What I'm going to show you here would work just as well on a UDP type connection, they both use the same addresses page. So what I'm going to do to start is, I'm going to click on the more drop down here and I'm going to click on addresses. And then we see this piece of user interface right here. So what this does is, it allows us to effectively create nodes inside of our OPC UA server that are then browsable. And these nodes can be assigned addresses, from inside of the devices programming. Now, to really understand how this works, we need to know a thing or two about syntax and this particular driver. So I'm going to switch over to our user manual here, we do have an Omron FINS driver page here. And the page may change over time depending on when you watched this video. But, I did want to head over to the examples area here. Where we can see it has some syntax examples and then it gives you some more flashed out examples. So when you're filling out that addresses page on the gateway here, we more or less follow this example here. And by more or less I mean, some of these items are actually optional. So in the very least willing to start with the area. Now if I scroll up just a little bit here, there is a table that basically spells out all the we call them data areas here, but I believe in the device they're called memory areas. But basically the various areas inside of the device. As well as the notation that we'll need to use to access them. Then I scroll down a little bit more back to that example there. We see that the next part here is the data type, which does have a set of curly braces around it. But then does have some angle braces inside of it. Now this part is optional, but it's probably a good idea for us to go ahead and specify this. Next step would be the offsets, and then optionally the bit if we need to. Now for this example here, my colleague that's handling the programming for this device I'm connected to is telling me that in the auxiliary bit area, so if I scroll up here. Auxiliary bit area would be AR or A, there's a float so we'll put down the data type at offset 723. So if I head back to my gateway here, I'm going to add a row. So an auxiliary bit would be AR, we're going to do the angle brackets so I'm going to type float and then the offset so 723. So that points to the location in the program. I need to enter at least a tag path, so the tag path here represents the node that we're going to be browsing for inside of our OPC UA server. So, let's just call this how about test tag for now, there's an optional description here. You really don't see this on the tag as you're browsing for it, it's really more or less for this page here as well as if you create an export file it'll contain the description, which is nice when you have a lot of rows here. But to start with let's go ahead and save the configuration and we can take a look at the quick client, but I'm actually going to switch over to the designer. So, I'm going to bring my designer over here and have a designer open, doesn't really matter how you get here, but you definitely want to take a look at the tag browser. I don't have any tags inside of my tag provider here we see that it's empty. I'm going to click the OPC browser button. I'm going to go down into ignitions OPC UA server. Go down to devices we do see our FINS TCP device connection. I'll go into the tags folder and hey, there's that test tag we created a moment ago. So, if I drag this over into the text folder here it should create a float OPC tag with a value of 3.14. We'll wait for it to come through and there we are. Now if I were to double click on this tag here, just to show you the OPC data path you'll notice, that part of the path here looks pretty familiar the AR float 723. Of course, we have the device name and the namespace that all of our drivers use. Now, I'm going to close this here and I'm going to come back to this. So I'm actually going to just dock this to the side for right now. If I go back into that addresses page, so I'll click more again, we'll go back to addresses. And for the test tag here, I didn't mention it earlier but this can actually be a path. So, if you just add a say a folder name right, so folder1/ how about folder2/, right. We'll go ahead and we'll save. I'll head on back to my designer. Now, adding those folders to the tag path doesn't really impact our existing tag. This is using the address from that item we created so we can freely add folders after the fact if we need to. What it did change is, we need to refresh on our OPC browser since it's not polling. Let's go back in we'll go to device, we go to FINS TCP back to tags. And now we got folder one, folder two and now our test tag, right. So if you wanted to add a little bit of structure inside of the OPC browser, you can do that with the tag path. Now the last thing I wanted to show you, which is a nice time saver, let's go back to that addresses page here. Now if you fill this out, you had a bunch of rows you can export the configuration and then move it to, a different device connection or a different gateway or what have you. And then of course, you can load in with the load configuration file button here. But what I wanted to show you, I'm going to go ahead and browse real quick. I have this TSV file here, which I'm going to open real quick just to show you before I import it in. Now my same colleague that's been programming this device, created this file for me. So they are using the CX programmer software to program the device. And they actually just created this export for me, directly from that software. So our driver can take this export here and just create a whole bunch of entries in this addresses table. So I'm going to select that file, I'll click open. I'll click load here, I can also append to the current configuration so if I wanted to maintain that test tag here, we'll just add the entries in this configuration file after. So I'll click Load now and you can see, it went ahead and added a whole bunch of entries here which I'm just going to scroll down here. I'm going to save and of course, if we go back to our designer. We'll just refresh the OPC browser, head on back down and just like that, we got a whole bunch of extra entries here. So that should give you enough information to get started with creating tags here. Again, you just going to want to lean pretty heavily on the user manual page just because it has all the various, data types and notation that you're going to want to use, when creating tags from this device connection.