How to create dummy tags of boolean and string for Yokogawa GX Ethernet

[WL_10521300]

Hi there,

I am trying to create a dummy tags. One for Boolean and one for string with the Yokogawa GX Ethernet driver & OPC-UA and I got this idea from this post but the addresses B0001 and S0001 are not the same for this driver. My question is how do I make a Boolean dummy tag and String dummy tag for Yokogawa GX Ethernet driver so it works on AMU

Previous Post: 

https://community.ptc.com/t5/ThingWorx-Developers/How-AMU-attribute-logging-works/m-p/930097#M65531)

[rajskumar]

Hello Wendy,

As we are working on this with an internal case submitted by you, I will update our resolution to benefit the broader community. Alternatively, you can update the solution once you achieve the requirement to benefit the broader community.

Thanks

[mstarnaud · Accepted solution]

Hi

I'm not a Kepware expert, but I'll explain how I create dummy tags and you can feel free to try it and see if it's good enough for you.

- Under Project, right-click on the Connectivity folder and create a Channel of type Simulator (this is where you probably chose Yokogawa). In the following popups I keep the default settings. 

- Right-click on the Channel that was just created and create a new Device. Again I keep the default settings in the following popups.

- Right-click on the Device that was just created and create a new Tag Group.

- Now in the Tag Group we can create new tags. As an example, one with address S0001 and type String.

I believe the Channel type Simulator is the big difference that enables addresses like S0001 to work for dummy tags. I have other Channels with other types and Kepware won't let me add tag addresses like S0001 in them, I'm guessing that's the problem you're having. And Simulator also allows me to use functions as addresses for my testing, like RAMP (value increases, good for quantity tags) and USER (go through a specific list of values, good for status & name tags). For example, address RAMP(1000, 0, 100, 1) will go from 0 to 100, increasing by 1 every 1000ms.

Let us know if this solves your issue.

[rajskumar]

As the issue has been resolved and the internal case has been closed, I am posting the summary for the wider community audience.

As our colleague suggested in the post below, how this can be achieved using the simulation driver. However, just to add:

Since the simulation driver is not a licensed aspect of KEPServer, it is not supported. Its functionality or any unexpected behavior will not be addressed by Technical Support, and any potential defects will not be addressed by Development. The Memory Based driver is the supported solution within Kepware Products.

Thanks