Feb 12 2009
TCP Protocol between Wonderware ArchestrA 3.0 and SLC500
On this chapter I will show you how to configure Wonderware ArchestrA 3.0 to control and monitor 2 or more PLC SLC500 via TCP protocol. Before that, you should have already install :
- Microsoft XP Professional Service Pack 2 – minimum operating system
- Microsoft SQL Server 2005 Service Pack 2 – repository database when running ArchestrA application
- Wonderware Intouch 10 – main template to insert ArchestrA symbol libraries
- TCP Driver Communication – setting IP address SLC500 and mapping address between tagname HMI and memory address PLC (on this case I use DAServer : DASABTCP 1.1 SP2)
Please select the ArchestrA IDE shortcut on Start Menu so you could create a galaxy database to save all of ArchestrA symbol libraries. On this case, I will create an ArchestrA Stand Alone HMI (local supervisory monitoring) by selecting the galaxy type : Base_InTouch.cab. After you have successful create a galaxy database, you could use this galaxy to connect ArchestrA IDE environment.
If you have any problem when creating a galaxy database, please check your antivirus and firewall configuration. Some of antivirus or firewall block this application because of security reason.
On the ArchestrA IDE environment, you should create an Intouch template where will used to connect Wonderware Intouch. There are two methods : Create new Intouch application or Import existing Intouch application. After you have successful create new Intouch template, then Intouch – WindowMaker application will opened at the end of step. Until this step, you have successful configure Wonderware Intouch base ArchestrA symbol libraries. This configuration allow you to insert default ArchestrA symbol libraries into Intouch – WindowMaker by click the Embed ArchestrA Graphic icon on Intouch – WindowMaker.
If you need to modify or create new ArchestrA symbol, you could click View -> Graphic Toolbox (Ctrl+Shift+P). On the Graphic Toolbox menu, you could create new Graphic Toolset to save all of your ArchestrA symbols. Double click the new symbol so you could enter ArchestrA Symbol Editor Window. On here, you could insert ArchestrA default symbol then modify or embed it with other symbol so could match with your HMI design. To maximize your symbol design, you could insert 3 dimension image, check box, calender, list box, etc.
ArchestrA Symbol Editor could provide you with the complete menu for graphical design and inserting script code for each or overall symbols. This facilities will help you to create an animation or editing display value on each symbol. ArchestrA symbol libraries provide the most of graphical symbol for anything HMI developement.
On the ArchestrA Symbol Editor, defining the new variable on your script not counted as new tagname. Its mean, you could maximize your tagname usage so could cost down the budget to paid more tagname licence. Its different with Wonderware Intouch, where each of new variable definition will counting as new tagname. Actually, on the Intouch there is function so your new variable that not counted as new tagname, which is :
DIM <new variable> AS <variable type>
But Intouch has limited space to save more script compared with Wonderware ArchestrA. If you insert many script into Intouch menu (Application, Condition, Data Change), you will have more problem potential when running HMI Intouch, example : delaying data transfer, blank HMI page, etc.
On this ArchestrA chapter, I inserting Toggle Button and Light Indicator into symbol SLC500_a, and Slider and Analog Indicator into symbol SLC_500_b. Then on each Intouch window, I embed symbol SLC500_a into Intouch window SLC500_a, and symbol SLC500_b into Intouch window SLC500_b. This is the detail configuration for Intouch – WindowMaker :
Window SLC500_a
Access Name : SLC500_a, Node Name : <blank>, Application Name : DASABTCP, Topic Name : SLC500_a, Protocol : SuitLink
- Tagname Button and Light are I/O Discrete with Access Name : SLC500_a, Check Box : Use Tagname as Item Name
Window SLC500_b
- Access Name : SLC500_b, Node Name : <blank>, Application Name : DASABTCP, Topic Name : SLC500_a, Protocol : SuitLink
- Tagname Slider and Analog are I/O Real with Access Name : SLC500_b, Check Box : Use Tagname as Item Name
Please download my example project on here.
Each of Access Name will connect to specific IP address of SLC500 via DAServer. For SLC500 you should install DASABTCP DAServer in the System Management Console (SMC). The SMC menu allow you to configure IP Address, Connection Timeout, Topic Name, Mapping Address tagname HMI and memory address PLC, etc. This screeshoot showing the DAServer configuration for SLC500.
The bellow screenshot is the runtime HMI Intouch base on ArchestrA symbol libraries. As you can see on bellow, there are full improvement on graphical symbol libraries when you create HMI Intouch base ArchestrA symbol libraries.
After that, you could backup your ArchestrA project into file format *.aaPKG, backup your tagname usage into file format *.csv, or publish your ArchestrA project into Intouch application. After you publish an ArchestrA project into Intouch application, you just could use the ArchestrA symbols and can’t modify its.
I hope, the short review of HMI Intouch base ArchestrA symbol libraries could help you to perform the HMI development. If you have any questions or need more technical support about Wonderware I could help you. Don’t hesitate to contact me please.
No responses yet
Print This Post
Related Posts
