[00:00] In this lesson, we'll demonstrate how to manually create tags in Ignition using an existing Mitsubishi device connection. We'll also demonstrate the use of some basic addressing syntax for the Mitsubishi driver. We'll start out here in our Ignition gateway on the Device Connections page. In a prior lesson, we showed how to set up a Mitsubishi device connection. We're going to need that device connection name for coming steps, so we note that it will be: mitsubishi_device. Next, in order to manually create tags in the Tag Browser, using this device connection, we'll first need to know about the addressing syntax for Mitsubishi devices. This diagram visually summarizes many key things about Mitsubishi device addressing. Let's consider this diagram in a bit more detail. Broadly speaking, Mitsubishi device addressing consists of two required components and several other optional ones.

[01:03] The first required component is a device keyword for the various possible logical areas of the device, such as inputs, outputs, relays, registers, and so forth. For example, a D designator stands for a data register. For a full listing of all available device area names and mnemonics, please refer to the User Manual. Just for the sake of simplicity, this example diagram is confined to data registers, so each addressing syntax expression here will start with a letter D. The other required component is a numerical offset within that device area. Each device area has its own range of offsets. This is shown along the left side from top to bottom. So here the offsets for the D or data register area begin at 0 at the top, and increment downward on the diagram. Because each data register item is natively a 16 bit word, this word size is shown across the top by individual bits left to right from the most significant bit 15, or MSB, to the least significant bit 0, or LSB.

[02:09] Let's now implement some tags using some of these examples. Next, we'll head over to our Designer, specifically to the Tag Browser. Since the Tag Browser will be where we'll manually create some tags using Mitsubishi device addressing syntax, we will resize this window such that we can see the Tag Browser side by side with our device addressing diagram. To create one individual tag, let's start with the simplest addressing syntax. In our Tag Browser, we'll click on Add > New Standard Tag > OPC Tag. This takes us to our Tag Editor, where we'll specify the following parameters. For the name, we'll specify DReg0 For the value source, we'll leave this as OPC. We'll leave the data type as its default integer. For the OPC Server we'll select our one option, the Ignition OPC UA Server. Then for the OPC Item Path, this is where our addressing syntax will come into play. To start, we'll need to specify the name of our device in square brackets.

[03:15] We saw from our device connections page that this will be mitsubishi _device. Now we can specify the intended addressing syntax. We'll use the first one in our diagram, a data register with offset 0, so D0. That's all we need, so we'll click OK, and we see that our name tag DReg0 with a device address D0, has been created and shows the current value from the device. Now that we've seen how to manually create one tag, the steps will be mostly identical for other tags, apart from the specific addressing syntax used. In fact, let's save ourselves a few steps by copy pasting this original tag into some new ones. Let's create a bit address tag next by doing copy, paste.

[04:05] Then we'll open up this copied tag in the Tag Editor and adjust its parameters, For the name. We'll change it to DReg0 _Bit0. The Value Source, Data Type and OPC Server retain their existing values now, but now our addressing syntax will differ a bit from our diagram. That's because now we want to extract the LSB of the existing D0 tag we created in the prior example, so that we can toggle it later. So we'll specify D0.0 instead of D2.0, which is the 0th bit of the D0 address. That's all we need, so we'll click OK, and we see that our name tag is created. Note that it has a correct bit 0 value of 0 since D0 is an even number. Finally, let's create one more tag, this time for a double sized word. Here the angle brackets for int32 represent an optional data type attribute that can be used to specify a double word size using two adjacent memory addresses as shown. So similar to before, we'll do copy, paste, then we'll open up this copied tag in the Tag Editor and adjust its parameters.

[05:28] For the name, we'll call this one Big Tag. The Value Source, Data Type, and OPC Server retain their existing values. Then for the Item Path, this time we'll specify D<int 32>5, which is the 32 bit double word, starting at offset 5. That's all we need, so we'll click OK, and we see that our Big Tag is created. Finally, as a simple check on our tags, we can do the following. Let's give our Big Tag some other very large value that clearly exceeds 16 bits. How about 1 2 3 4 5 6 7 8 9.

[06:13] And for our DReg0 tag, let's set it to any odd value such as 2005, and we see that its 0 bit in the other tag toggles to a 1. So in this lesson, we've demonstrated how to manually create some tags in the Tag Browser, using an existing Mitsubishi device connection, and how to make use of several available types of Mitsubishi addressing.