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. So, let's just call this how about test tag for now, there's an optional description here. 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 that points to the location in the program. 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 if I head back to my gateway here, I'm going to add a row. Auxiliary bit area would be AR or A, there's a float so we'll put down the data type at offset 723. 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. Next step would be the offsets, and then optionally the bit if we need to. Now this part is optional, but it's probably a good idea for us to go ahead and specify this. But then does have some angle braces inside of it. We see that the next part here is the data type, which does have a set of curly braces around it. Then I scroll down a little bit more back to that example there. As well as the notation that we'll need to use to access them. But basically the various areas inside of the device. 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. So in the very least willing to start with the area. And by more or less I mean, some of these items are actually optional. So when you're filling out that addresses page on the gateway here, we more or less follow this example here. Where we can see it has some syntax examples and then it gives you some more flashed out examples. But, I did want to head over to the examples area here. And the page may change over time depending on when you watched this video.
#Omron cx programmer upload comments driver#
So I'm going to switch over to our user manual here, we do have an Omron FINS driver page here. Now, to really understand how this works, we need to know a thing or two about syntax and this particular driver. And these nodes can be assigned addresses, from inside of the devices programming. So what this does is, it allows us to effectively create nodes inside of our OPC UA server that are then browsable. And then we see this piece of user interface right here. 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. 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. Now this is an Omron FINS TCP connection.
Instead, I'm going to show you the addresses page here on this device connection. It's kind of a slow method to do so I'm not even going to bother showing you. So going to the designer and creating an OPC tag. There are a couple of ways to do this, one option which I'm not going to show you, is manually creating OPC tags. And I want to access some values inside of this device connection. We can see here I have a device connection already configured. Be civil: do not insult no all-caps, no excessive "!" and "?", please.In this lesson, we'll take a look at creating tags for Omron FINS device connections.Job announcements (oustide the monthly job thread).Single Board computers: r/Raspberry_pi, r/Arduino, r/linux_devices, r/linuxboards.Hardware design that does not include a PLC for electronic circuits: /r/AskElectronics.PLC internship, employment and education questions.Homework help but make it clear it's homework.This sub is dedicated to discussion and questions about Programmable Logic Controllers (PLCs): "an industrial digital computer that has been ruggedized and adapted for the control of manufacturing processes, such as assembly lines, robotic devices, or any activity that requires high reliability, ease of programming, and process fault diagnosis." On topic subjects