1. USING H1 WITH TI505 CONTROLLERS
OBJECT:
To read and write data to a TI505 controller from Wonderware Intouch using H1.
EQUIPMENT:
Simatic TI555 Controller - Part number 555-1101
TI Power Supply - Part number 505-6660
Sinec H1 Communication Processor - 505-CP1434TF
Ethernet 10Base-T Hub - Addtron UTP8
2 Ethernet 10Base-T Cables
2 Ethernet 10Base-T Transceivers - Allied Telesis CentreCOM 210TS
PC - AST 486, 25Mhz, 4MB RAM
Intel PC H1 card - Part Number PCL2ANIA
Microsoft Windows version 3.1
Wonderware Intouch version 5.1
TISOFT version 5.0
Intouch H1 Server version 5.1a
505-CP1434TF Configuation Software
PCL2A Configuration Software version 3.1 (can be obtained from H1Server)
SETUP:
The CP1434TF module is placed in the rack of the PLC. A transceiver is placed in the H1 port of the module from which a 10Base-T cable goes from the transceiver into the hub. Another 10Base-T cable then goes from the hub into the second transceiver which is placed in the port on the PCL2ANIA card in the PC.
CONFIGURING THE PLC CPU:
Using Tisoft, we can configure the I/O map of the controller and verify controller to H1 module communications. It is extremely important to configure the I/O in the PLC as even though the H1 module may appear to be working correctly, it does not communicate with the PLC unless it is configured in the I/O map. Basically what we need to do is apply power to the base and follow these steps:
1. Ensure the H1 module successfully completes power up initialization.
2. In TISOFT, access the Configure I/O function menu.
3. Select the appropriate channel and base number.
4. Execute the Read Base function. The H1 module should appear as 4WX and 4WY with the next slot containing all zeros (this is because it is a double wide module).
5. Assign the appropriate I/O addresses and write the completed I/O configuration to the PLC memory using the Write PLC function. You can then write a ladder logic program in the PLC.
CONFIGURING THE PCL2ANIA CARD:
Before inserting the card in the PC, it is important to check the jumper settings on the card. The default settings are:
I/O Port Address : 360
Interface : V2/IEEE 802.3
IPL Source : Local
Interrupt Setting : IRQ2 or 5
It is claimed by Intel that Interrupts 2,3,4 and 5 can all be used by the card. I would still only recommend that interrupts 2 or 5 be used. After inserting the card, follow these basic steps:
1. Install the configuration software, PCL2A, into the computer.
2. Go into the PCL2A directory and type Netbios. This command runs the card driver and will give us important information about the PCL2ANIA card . By running Netbios we can get the actual adapter ethernet address of the card which we require for the setup. Be prepared for the computer to ìlock-upî; this is because the card is not configured yet and you will have to re-boot the computer. If the computer locks up at Primary Adapter Detected, you probably have an IRQ error. If it locks up at Adapter Ethernet Address, you have probably selected the wrong Communication Load File Name in the settings (see below).
3. Go into the PCL2A directory and type Admin. This runs the configuration software.
4. Enter 1 - Modify Network Adapter Configuration Parameters. You will then be asked for the following parameters:
NIA Base Port : 360 (jumper setting on the card)
NIA Base Address : CC (See below)
NIA Interrupt Level (2/5) : 5 (jumper setting on the card)
Maximum Number of Netbios Commands : 32 (default if using wonderware)
Maximum Number of Netbios Sessions : 32
Communication Load File Path : C:\PCL2A\
Communication Load File Name : INAR31.MEM or INAR31A.MEM
For the NIA Base Address, whatever address we pick must be excluded in the CONFIG.SYS. For example, if you select CC, then your CONFIG.SYS should have a line looking something like this:
DEVICE=C:\DOS\EMM386.EXE NOEMS X=C000-CFFF
5. Next we have to configure the nodes on the system.
Go back to the main menu and enter 2 - Manage Spokesman System.
Then enter 1 - Add a new Node to the Spokesman.
You will then be asked for the following parameters:
Node Name: PLC1 (any name)
Host ID: 00 AA 00 07 BE E1
This is the actual ethernet address of the PCL2ANIA card (eg 00 AA 00 07 BE E1)
TSAP ID: 5757
This is a selectable ID number for the card (eg. 0801). For this example I am using Wonderware Intouch so I will make the TSAP ID = 5757 (ASCII =WW)
iNA Rel. No. (1,2,3): 2
6. After entering these values, hit the esc key and then enter 4 - List Nodes on Spokesman. The node you just entered should be listed on the screen. We can then exit out of the configuration software and run netbios; if we get Local Node Information Added, the card is installed and configured correctly.
CONFIGURING THE H1 CP1434TF CARD:
Install the H1 configurator software onto the PC and double click on the H1 Configurator icon. Using the TI programming cable, ensure that the PC is online with the H1 module (RS232 port).
After opening a new file, we must select the type of communication service we require; the choice is Peer Data Transfer services or Technology Function Services. Peer Services are based on ISO Layer 4 (transport layer) and are typically used for the fast and efficient exchange of data. Technology Function Services (TF) are based on layer 7 (application layer) and are generally used between a supervisory system and the PLC nodes from which it is gathering or writing data. When a node communicates in the Peer Services mode, it can function as either the client (the active or initiating partner) or the server (the passive partner). With TF Services the node can only function as the server. Generally, for this type of application, peer services are used, and that is what is being used in this example.
To set up the parameters for the CP1434TF card, do the following:
1. Open a new file. On the first screen of this file, you will be asked for a local ethernet address (this will be the ethernet address of the H1 CP1434TF card and must be unique to that card) and the type of services you wish to use. The ethernet address is 12 characters long and the default is 080006010000. The first eight characters are the Siemens standard and they must be left the same. For this example, the number I use is 080006010001.
2. Next, click on the box under Peer Services and then click on the Insert button. At the second screen enter a job labelled FETCH.
3. For the transport profile, select TPROF_0505_SPS (see manual for descriptions of these)
4. In the Local (local being the PLC) box, select the following:
TSAP Length: 4 Hex: 46464646 ASCII: FFFF
(The TSAP length can be a maximum of eight characters long)
5. In the Remote (remote being the PC) box, select the following:
Ethernet Address: 00 AA 00 07 BE E1 (actual address of PCL2ANIA card - see above)
TSAP Length: 2 Hex: 5757 ASCII: WW
6. Next, click on the job button. For the job definition, select Read Passive. This is the only entry required for this screen unless an active type of job is selected. A passive job does not need any logic to be programmed in the controller whereas an active job does (hence the 4WX and 4WY in the I/O configuration of the PLC). For an active job, we require a start bit (from the 4WY), what and how much data we are to transfer, an error location (V memory) and what the remote node is. We also get a job in process bit (from the 4WX). See the manual for more details.
7. After entering the FETCH job, we enter another job in Peer Services. This one is called the RECEIVE job.
8. For the RECEIVE job, enter the following:
Transport Profile: TPROF_0505_SPS
Local (the PLC):
TSAP Length: 4 Hex: 52525252 ASCII: RRRR
Remote (the PC):
Ethernet Address: 00 AA 00 07 BE E1 (actual address of the PCL2ANIA card)
TSAP Length: 2 Hex: 5757 ASCII: WW
9. Click on the job button. This time the job definition is Write Passive.
10. Save the file and download it to the H1 module with the transfer command.
11. We have now set up the PLC with two jobs; Read Passive and Write Passive. This means that we can both read and write values from/to the PLC from Wonderware. It also means that because they are passive we do not have to write any code in the PLC to start the transfer. In Peer Services it is possible to define up to 40 connections from the PLC. It should be noted that each PLC/PC should have a unique ethernet address and TSAP ID.
CONFIGURING THE WONDERWARE H1 SERVER:
Next we have to configure the Wonderware server. Double click on the server to run it, and then click on the Configure heading. The options Adapter Card Settings and DDE Server Settings can be left alone. The option of importance to us is Topic Definition.
Click on Topic Definition and select new. Then enter the following:
Topic Name : PLC1
Ethernet Address : 080006010001 (ethernet address of PLC)
Local TSAP : 5757 ASCII: WW (address of PC)
Remote FETCH TSAP : 46464646 ASCII: FFFF (job in PLC)
Remote RECEIVE TSAP : 52525252 ASCII: RRRR (job in PLC)
PLC/Item name : TI
The update interval should also be changed to around 100ms
When running the application, the H1 server should be started before WindowViewer.
2. USING H1 WITH S5 CONTROLLERS:
OBJECT:
To read and write data to an S5 controller from Wonderware Intouch using H1.
EQUIPMENT:
CC 135U/155U Central Controller with Power Supply
135U CPU 928B - Part Number 6ES5 928 3UB12
CP143TF Communications Processor - Part Number 6GK1143-0AB01
Powered Programming Cable
Ethernet 10Base-T Hub - Addtron UTP8
2 Ethernet 10Base-T cables
2 Ethernet 10Base-T Transceivers - Allied Telesis CentreCOM 210TS
PC - AST 486, 25 Mhz, 4MB RAM
Intel PC H1 card - Part Number PCL2ANIA
Microsoft Windows version 3.1
Wonderware Intouch version 5.1
Step5 version 6.5
COM 143 TF Configuration Software version 1.1
Intouch H1 Server version 5.1a
PCL2A cConfiguration Software version 3.1 (can be obtained from H1 server)
SETUP:
The CP143TF module is placed in the rack of the PLC. A transceiver is placed in the H1 port of the module from which a 10Base-T cable goes from the transceiver into the hub. Another 10Base-T cable then goes from the hub into the second transceiver which is placed in the port on the PCL2ANIA card in the PC.
CONFIGURING THE PCL2ANIA CARD:
Before inserting the card in the PC, it is important to check the jumper settings on the card. The default settings are:
I/O Port Address : 360
Interface : V2/IEEE 802.3
IPL Source : Local
Interrupt Setting : IRQ2 or 5
It is claimed by Intel that Interrupts 2,3,4 and 5 can all be used by the card. I would still only recommend that interrupts 2 or 5 be used. After inserting the card, follow these basic steps:
1. Install the configuration software, PCL2A, into the computer.
2. Go into the PCL2A directory and type Netbios. This command runs the card driver and will give us important information about the PCL2ANIA card . By running Netbios we can get the actual adapter ethernet address of the card which we require for the setup. Be prepared for the computer to ìlock-upî; this is because the card is not configured yet and you will have to re-boot the computer. If the computer locks up at Primary Adapter Detected, you probably have an IRQ error. If it locks up at Adapter Ethernet Address, you have probably selected the wrong Communication Load File Name in the settings (see below).
3. Go into the PCL2A directory and type Admin. This runs the configuration software.
4. Enter 1 - Modify Network Adapter Configuration Parameters. You will then be asked for the following parameters:
NIA Base Port : 360 (jumper setting on the card)
NIA Base Address : CC (See below)
NIA Interrupt Level (2/5) : 5 (jumper setting on the card)
Maximum Number of Netbios Commands : 32 (default if using wonderware)
Maximum Number of Netbios Sessions : 32
Communication Load File Path : C:\PCL2A\
Communication Load File Name :INAR31.MEM or INAR31A.MEM
For the NIA Base Address, whatever address we pick must be excluded in the CONFIG.SYS. For example, if you select CC, then your CONFIG.SYS should have a line looking something like this:
DEVICE=C:\DOS\EMM386.EXE NOEMS X=C000-CFFF
5. Next we have to configure the nodes on the system.
Go back to the main menu and enter 2 - Manage Spokesman System.
Then enter 1 - Add a new Node to the Spokesman.
You will then be asked for the following parameters:
Node Name: PLC1 (any name)
Host ID: 00 AA 00 07 BE E1
This is the actual ethernet address of the PCL2ANIA card (eg 00 AA 00 07 BE E1)
TSAP ID: 5757
This is a selectable ID number for the card (eg. 0801). For this example I am using Wonderware Intouch so I will make the TSAP ID = 5757 (ASCII =WW)
iNA Rel. No. (1,2,3): 2
6. After entering these values, hit the esc key and then enter 4 - List Nodes on Spokesman. The node you just entered should be listed on the screen. We can then exit out of the configuration software and run netbios; if we get Local Node Information Added, the card is installed and configured correctly.
CONFIGURING THE PLC CPU:
Set up a new file in the Step5 software and make sure you are online with the 928B cpu. To set up the CPU, we have to ensure that the Send-All Block (FB126) and the Receive-All Block (FB127) are called to trigger sending and receiving once per scan. The PLC should basically be set up as follows:
1. Set up DB10 as the Read-Write register. This should be set up as 250 Data Words long.
2. Program OB20, OB21 and OB22 with the following:
:JU FB11 (where FB11 is the STARTUP block)
3. Program OB1 with:
:JU PB10
4. Program PB10 with the following:
:C DB10
:JU FB126
Name:Send-A
SSNR:KY 0,x (where x=SSNR of card - dependent on jumper settings)
ANR:KY 0,0
ANZW:DW1
PAFE:FY200
:JU FB127
Name:Recv-A
SSNR:KY 0,x (where x=SSNR of card - dependent on jumper settings)
ANR:KY 0,0
ANZW:DW3
PAFE:FY201
The SSNR setting depends on the jumper settings in the CP143 card. In this example, the card is set up with the SSNR address 0.
5. Program FB11 with following:
FB11 - STARTUP
:JU FB125
Name:SYNCHRON
SSNR:KY 0,x (where x=SSNR of card - dependent on jumper settings)
BLGR:0,6
PAFE:FY199
CONFIGURING THE H1 CP143TF CARD:
Important:
When programming the CP143TF card, it is very important that a externally powered programming cable is used.
Install COM143 onto your PC and run Step5. When in Step5, select the Change (then Further) menu. Here you can run COM143. Initially you will be asked whether you wish to program the CP143TF card online or offline.
When at the main menu, select F1: Create or Change (Edit)
If you are working offline, the device will say FD (otherwise CP). Enter a name for the file at Module File (this will always begin with P) eg. PTEST.143 ; after this, hit F1 (Block).
Select F1 : System Identifier of Memory Card
CP Type: CP143
Base SSNR: x (where x=the SSNR address of the card; see jumper settings)
In this example the SSNR = 0
Memory Type: EPROM or RAM depending on what type of module is in the CP143 card
Memory Length: Again this is dependent on the type of module in the CP card
Ethernet Address: Assigned address - in this example 080006010001
Then hit F7: Okay
No changes need to be made under F2: CP143 Initialization.
Select F3: Communication Link
At the Data Link block, we configure the Jobs. In this example we shall set up two jobs:
One FETCH and one RECEIVE. It should be noted that there are two screens per job to configure.
Job 1, Screen 1:
SSNR : x (x = SSNR of card; in this example SSNR = 0)
ANR : 1 (job number)
Job Type : FETCH
Active/Passive : P
Leave the rest of this screen blank as we have no remote PLC (the ethernet address should read all zeros)
Hit F5: Next Screen Form
Job 1, Screen 2:
Read/Write : Y (or J in German)
Local TSAP ID: Length : 4 Hex : 46464646 ASCII : FFFF
Remote TSAP ID: Length : 2 Hex : 5757 ASCII: WW
Remote NSAP ID: Length : 12 ASCII : PLC1
(Anything that is not configured above, can be left as it is)
Job 2, Screen 1:
SSNR : x (x = SSNR of card; in this example SSNR = 0)
ANR : 2 (job number)
Job Type : RECEIVE
Active/Passive : P
Leave the rest of this screen blank as we have no remote PLC (the ethernet address should read all zeros)
Hit F5: Next Screen Form
Job 2, Screen 2:
Read/Write : Y (or J in German)
Local TSAP ID: Length : 4 Hex : 52525252 ASCII : RRRR
Remote TSAP ID: Length : 2 Hex : 5757 ASCII: WW
Remote NSAP ID: Length : 12 ASCII : PLC1
(Anything that is not configured above, can be left as it is)
CONFIGURING THE WONDERWARE H1 SERVER:
Next we have to configure the wonderware server. Double click on the server to run it, and then click on the Configure heading. The options Adapter Card Settings and DDE Server Settings can be left alone. The option of importance to us is Topic Definition.
Click on Topic Definition and select new. Then enter the following:
Topic Name : PLC1
Ethernet Address : 080006010001 (ethernet address of PLC)
Local TSAP : 5757 ASCII: WW (address of PC)
Remote FETCH TSAP : 46464646 ASCII: FFFF (job in PLC)
Remote RECEIVE TSAP : 52525252 ASCII: RRRR (job in PLC)
PLC/Item name : SIEMENS
The update interval should also be changed to around 100ms
When running the application, the H1 server should be started before WindowViewer.
3. RESULTS OF H1 SPEED TEST:
OBJECT:
To test the speed of a H1 network for optimum performance on two different computers.
For this experiment, I used the equipment listed in number 2 above (Using H1 with S5 Controllers). The two different computers used are:
1. AST 486, 25MHz, 4MB RAM
2. Siemens SICOMP IPC RI 40, 486DX, 90MHz Pentium
The same test was carried out in both PCís to see what effect each computer has on the speed of the network.
REPORT:
The network was set up as described in number 2 above, using a 135U, cpu 928B (see Using H1 with S5 Controllers). A program was written in the PLC using DO-Loops to constantly transfer values into Data Words, Timers, Counters, and Flag Words. In all, the program consisted of 7 active data blocks (each with 250 data words), 10 counters, 10 timers and 10 flagwords. The updating of all of this data was monitored in Intouch via the H1 network, and the time taken for the updates was noted for each PC.
The Intouch application consisted of 10 screens, each with varying amounts of tags. In all, 212 tagnames were used. Each screen consisted of a different amount of data blocks (each covering 250 data words); starting with 1 data block to a maximum of 6. There were also different combinations of timers, counters and flagwords. The updates were timed over 10 second periods so it should be noted that the results shown below are estimates. This test covered each screen being active one at a time, then all screens active at once.
RESULTS:
1. AST 486:
1 Data Block : 26 tags --------------------------------- 2.6 updates per second
2 Data Blocks : 52 tags --------------------------------- 1.5 updates per second
3 Data Blocks : 78 tags --------------------------------- 1.1 updates per second
4 Data Blocks : 104 tags --------------------------------- 0.8 updates per second
5 Data Blocks : 130 tags --------------------------------- 0.6 updates per second
6 Data Blocks : 156 tags --------------------------------- 0.5 updates per second
4 Data Blocks,10 timers, 10 counters, 10 flags---------- 0.6 updates per second
All tags (10 screens, 212 tags)--------------------------------- 0.8 updates per second
2. Siemens IPC RI40:
1 Data Block : 26 tags --------------------------------- 2.6 updates per second
2 Data Blocks : 52 tags --------------------------------- 2.5 updates per second
3 Data Blocks : 78 tags --------------------------------- 2.2 updates per second
4 Data Blocks : 104 tags --------------------------------- 1.7 updates per second
5 Data Blocks : 130 tags --------------------------------- 1.4 updates per second
6 Data Blocks : 156 tags --------------------------------- 1.2 updates per second
4 Data Blocks, 10 timers, 10 counters, 10 flags--------- 1.4 updates per second
All tags (10 screens, 212 tags)--------------------------------- 1.0 updates per second
CONCLUSION:
These results show us what impact the speed of the PC has on the speed of the network. We can see that when updating one Data Block (one screen, 26 tagnames), we get the same amount of updates per second for both PCís. This changes radically though when the number of tagnames is increased. For example, to obtain one or more updates per second, the AST can only support a maximum of three data blocks whereas the RI40 can support over six. It should also be noted that the update interval in the H1 server was set at 10ms for these results.
4. USING H1 ALONGSIDE TCP/IP IN THE SAME COMPUTER
OBJECT:
To get H1 working on the same PC as TCP/IP. That is, two ethernet cards in one PC running different protocols.
EQUIPMENT:
Simatic TI555 Controller - Part number 555-1101
TI Power Supply - Part number 505-6660
Sinec H1 Communication Processor - 505-CP1434TF
Ethernet 10Base-T Hub - Addtron UTP8
4 Ethernet 10Base-T Cables
2 Ethernet 10Base-T Transceivers - Allied Telesis CentreCOM 210TS
2 PCís - AST 486, 25Mhz, 4MB RAM
Intel PC H1 card - Part Number PCL2ANIA
2 PC TCP/IP cards - Etherlink III (3C509B-TP0)
Microsoft Windows for Workgroups version 3.11
Wonderware Intouch version 5.1
Wonderware NetDDE
Newt Configuration Software (Windows TCP/IP Stack)
Tisoft version 5.0
Intouch H1 Server version 5.1a
505-CP1434TF Configuation Software
PCL2A Configuration Software version 3.1 (can be obtained from H1Server)
SETUP:
The CP1434TF module is placed next to the TI555 controller in the PLC rack. A transceiver is placed in the H1 port of the CP1434TF module from which a 10Base-T cable goes to the hub. Another 10Base-T cable goes from the hub into the second transceiver which is placed in the port of the PCL2ANIA card in the first PC (Computer 1). An Etherlink III card is placed in Computer 1 next to the PCL2ANIA card. Another 10Base-T cable goes from the Etherlink III card to the hub. The last 10Base_T cable then goes from the hub into the second Etherlink III card in the second PC (Computer 2).
To show this application working, a program was written in the PLC which was monitored from Intouch in Computer 1. The same Intouch application was placed in Computer 2, monitoring the PLC - hence showing TCP/IP working in the same PC as H1.
For the setup instructions on the PLC, PCL2ANIA card, CP1434TF card and Wonderware H1 server, refer to ìUsing H1 with TI505 Controllersî above.
CONFIGURING COMPUTER 1 (AND COMPUTER 2):
Install Windows for Workgroups, Wonderware Intouch, NetDDE and Newt configuration software onto the computer.
In the System Editor, the following changes need to be made (only in Computer 1):
PROTOCOL.INI
lana 0 should be changed to lana 1
lana 1 should be changed to lana 2
[NETBEUI]
lanabase = 1
SYSTEM.INI
[386ENH]
V86ModeLANAs = 0
[NETWORK]
Exclude = 0
If the above lines do not exist in the System.ini, they should be added.
The following steps have to be configured on both computers:
Assign a name and workgroup to the computer. This is done in the windows Control Panels - Network Control Panel.
In this example the computer name is Computer 1 (for the second computer: Computer 2). We then go into the Network Setup (in the windows group Network). Here we have to allow the files to be shared with others. Also (under Drivers; Add Adapter), the 3Com Etherlink III network adapter has to be installed.
Next, open File Manager; under the Disk heading, click on ìShare Asî. Here the access type should be full.
Under the Disk heading, click on ìConnect Network Driveî; here we can Show Shared Directories on Computer 2 (if in Computer 2 we Show Shared Directories on Computer 1).
CONFIGURING NEWT - TCP/IP APPLICATIONS FOR WINDOWS:
The Newt configuration software is set up as below for Computer 1:
Interface : Ethernet0
Type : Ethernet
Physical Address : 00 A0 24 23 30 5D (actual address of card)
IP Address : 204.145.245.201 (actual internet address - Class C)
(For Computer 2 the IP Address is 204.145.245.202)
Subnet Mask : 255.255.255.0
Host Name : Computer 1
Under Services - Host Table:
Name : Host
Internet Address of Remote : 204.145.245.202
Aliases : Computer 2
(For Computer 2, the Internet Address of Remote is 204.145.245.201 and Aliases is Computer 1)
CONFIGURING NETDDE:
NetDDE for Computer 1 is set up as below:
Local Node Name : Computer 1
Interfaces : TCP/IP, Winsock 1.1
Node Name : Computer 1
Preferences : Default Route: Computer 2
Connection Names : Computer 1
Network : wwinsock
Port : Any
Network Node Name : Computer 1
(All of these names will be opposite for Computer 2)
CONFIGURING INTOUCH DDE ACCESS NAMES:
In Intouch, go into DDE Access Names (under the Special heading).
In Computer 1, it should be set up as below:
Access Name : PLC1
Application Name : H1Server
Topic Name : PLC1
In Computer 2, the DDE access name is set up as follows:
Access Name : PLC1
Application Name : \\Computer 1\H1Server
Topic Name : PLC1
No comments:
Post a Comment