• 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

• Wonderware Application Server 3.0 – develop the 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.

The change of resistance value when RTD sensing the physical temperature will interpreted and collected by ADAM-4015. Then the RTD acquisition will redistribute on unique Modbus address (4xxxx) and convert the resistance value into unsigned integer (0 – 65535) data.  Each ADAM-4015 could configure separately using ADAM 4000-5000 Utility Software (support for all of ADAM 4000 s/d 5000 series). This software could configure the Modbus (hexadecimal standard) address, baud rate, modbus type, scaling of temperature range on each ADAM-4015. Beside that, its also could monitor the actual change of resistance value of RTD into hexadecimal data view when ADAM-4015 connected with PC via serial/RS-232 port. Because ADAM-4015 only support Modbus 485, you will need converter RS-232 to RS-485 to perform the ADAM-4015 configuration. You may use ADAM 4520 to configure ADAM-4015 using your laptop or PC.

ADAM-4015 communicate with other device using Modbus 485 Master/Slave. This standar industrial protocol have more advantage, like support high speed data transfer until 10 Mbps (bit per second) for long distance (theoritically 1200 meter or 4000 feet)  on base EIA (Electronics Industry Association) standard and could receive resistance  from RS-485 cable up to 12 k ohm. As theoritically, Modbus 485 could have 247 unique node address. Its mean that in one Modbus 485 network, we could have 247 ADAM-4015 that collect data from 1482 RTD. As you know RS-485 cable are 2-wire, half-duplex, multi-drop system. For comparation, imagine how long analog cable that needed when we use analog cable for 1482 of 2 or 3 wire RTD into analog module of SLC500.

On this system, protocol Modbus 485 Master/Slave are used for communication between ADAM-4015 and PROLINK-5201/5202-MNET-MCM(4). When we talk about Modbus Master/Slave network, we have active device that request and collect data from slave device (called by Master Device – PROLINK-5201/5202-MNET-MCM(4)) and passive device that just follow the request from master device (called by Slave Device – ADAM-4015). We could have many slave device for one master device.

After we have finish ADAM-4015 configuration, we should configure the PROLINK-5201/5202-MNET-MCM(4) as the master device. The configuration could perform by Prosoft Configuration Builder (PCB) Software. In my configuration, I set port 0 for Modbus 485 communication with ADAM-4015.  You could download my example configuration by click this link : 2nodetoprolink020908success.ppf.

As the information, PROLINK-5201/5202-MNET-MCM(4) have 4 available input port that support with Modbus 485/422/232 protocol where each port could configure separately.  If we talk about temperature data acquisition from RTD via ADAM-4015, PROLINK could collect a wide amount of data, approximately : 247 x 6 x 4 = 5928 temperature data from RTD. On PCB software we also should write a request command per Modbus address so data acquisition from each ADAM-4015 could collected into PROLINK and save temporary. You could see my configuration on upper screenshot.

Data that have saved temporary on PROLINK-5201/5202-MNET-MCM(4) will sent to PROSOFT-MVI56-MCM using Modbus TCP/IP protocol.  Its mean that each device should have IP, Netmask and Client/Server status configuration. All of configuration could performed by PCB software. Because all of data from ADAM-4015 collected and save temporary with active command in PROLINK-5201/5202-MNET-MCM(4), this device has Server status. PROSOFT-MVI56-MCM just receive data that was sent by PROLINK, so this device has Client status. This is the example configuration of PROSOFT-MVI56-MCM : 1nodetoprosoft020908success.ppf.

As note: PROLINK-5201/5202-MNET-MCM(4) using signed integer (-32768 s/d 32367) and ADAM-4015 using unsigned integer (0 s/d 65535) standard data. The different standard data does not matter on data exchange between ADAM-4015 to SLC500, but we should add scalling function in ladder programming on SLC500. On RSLogix PLC Software available Scale with Paramater function. If you have any questions or more technical support please don’t hesitate to contact me.