op09_rsopcgateway

OP09 – RSOPC Gateway

Presenter: Christopher RogersOperate

¡Error! Estilo no definido.RSTechED 2005 § Rockwell Software 3 of 42

OP09 RSOPC Gateway

Contents

Before you begin.......................................................................................................................4

About this lab ..............................................................................................................................4

Tools & prerequisites...................................................................................................................4

Create a FactoryTalk Application containing an RSLinx Enterprise server ...........................5

Configure RSLinx Enterprise to communicate with the SoftLogix Controller........................9

Add an RSView SE server to the application .........................................................................12

Configure the RSOPC Gateway ..............................................................................................17

Test the OPC connection with the OPC Test Client...............................................................20

Serve 10,000 ControlLogix Data Points a second and keep the data server CPU utilizationlow............................................................................................................................................24

Making Online Changes..........................................................................................................26

Viewing RSLinx Enterprise Diagnostics ................................................................................31

Troubleshooting......................................................................................................................33

When some of the tags do not update and have a bad quality.................................................... 33

Data not updating; Tags have bad quality or OPC clients can’t browse for tags.......................... 34

Appendix .................................................................................................................................36

¡Error! Estilo no definido.4 of 42 RSTechED 2005 § Rockwell Software

Before you begin

About this lab

RSOPC Gateway gives OPC clients access to RSLinx Enterprise and RSView SE data.Additionally, RSView SE alarm and derived tags can be collected within OPC clients.

This lab will explore configuring, collecting data from, and troubleshooting RSOPC Gateway indistributed application.

In this lab we will:

• Create a FactoryTalk application and add an RSLinx Enterprise and an RSView SEserver to that application

• Configure and test the RSOPC Gateway connection to the FactoryTalk application

• Put 10,000 tags on scan and observer the low data server CPU utilization

• Perform changes to the ControlLogix program while OPC clients are collecting data. OPCclients do not need to be shut down and restarted.

• Go through some troubleshooting and diagnostics steps.

Tools & prerequisites§ SoftLogix and RSLogix 5000 (version 13)

§ CPR 7 versions of the FactoryTalk Automation Platform, RSLinx Enterprise and RSView SE


Create a FactoryTalk Application containing an RSLinxEnterprise server

RSOPC Gateway is a component of a FactoryTalk application. The first thing we need to do is tocreate a FactoryTalk application.

1. Start the FactoryTalk Administration Consol. This consol is used to create and modifyFactorTalky applications including RSLinx Enterprise servers.

From the Start menu, select Programs > Rockwell Software > FactoryTalk AdministrationConsol.

2. Select the FactoryTalk application type. There are two types of applications that can be used.

• Local - Everything is on one computer. If RSView SE is used then it must be RSView SEstation. If you have a Local FactoryTalk application then you need to use RSOPCGateway Station.

• Network – RSLinx Enterprise and RSView SE distributed can be located on anycomputer relative to RSOPC Gateway. Also, OPC clients can collect data from multipleRSLinx Enterprise and RSView SE servers. If you have a Network FactoryTalkapplication then you need to use RSOPC Gateway Distributed.

For this lab we will be using Network.

3. You will be prompted to log on to FatoryTalk. Username = administrator; password = rockwell


4. No we create the network FatcoyTalk application by right mouse clicking on “Network” withinthe FactoryTalk application consol and selecting “New Application”.

5. Name the application “Monitoring System”.

6. Add an area by right moue clicking on the Monitoring System application and selecting NewArea.


7. Name the area “ProductA”. An area is a used to logically organize RSLinx Enteprise andRSView SE servers in a distributed system.

8. Now add an RSLinx Enterprise server to the ProductA area. Right mouse click on the areaProductA and select add New Data Server -> RSLinx Enterprise Data Server


9. Select OK to the dialog that specifies the logical name of the RSLinx Enteprise server andwhich machine it resides on. Leave the Defaults.


Configure RSLinx Enterprise to communicate with the SoftLogixController

Now we have to configure RSLinx Enterprise to communicate with the local SoftLogix 5860Controller. RSLinx Enterprise can be configured with the FactoryTalk Administration Consol orwith RSView Studio. We’ll use the FactoryTalk Administration Consol. Also, no driverconfiguration is required since we are using a Softlogix. All that needs to be done to configureRSLinx Enterprise is to browse the virtual network for the device and to create a shortcut thatreferences that controller.

1. Select Communication setup to that we can create a shortcut and referrence SoftLogix and

2. From the communication setup screen right mouse click on the 1789-A17 (Virtual Backplane)and select “Start Browsing”.


3. RSLinx Enterprise will browse and find devices on the virtual backplane. We want to create ashortcut referencing the softlogix “ProductA” controller in slot 2. Select the processor in theRSWho tree and click “Add” on the bottom of the communication setup dialog.


4. Name the shortcut “CLX_A”

5. Select Yes.

RSLinx Enterprise is now configured with a shortcut called CLX_A that points to the Softlogixcontroller.


Add an RSView SE server to the application

Were going to add an RSView SE server to the FactoryTalk application so that we can show howRSOPC Gateway can allow data access to RSView SE direct references, Alarm tags, andderived tags.

1. Start the RSView Studio.

From the Start menu, select Programs > Rockwell Software > RSView Enterprise->RSView Studio.

2. Select “SE Distributed” since we are adding an RSView SE server to a network application.


3. Now we need to select the FactoryTalk application “Monitoring System” and open it. Make surethat you select a language (English (United States), en-US)

4. RSView Studio has now loaded the Monitoring System application. Remember that we createdthis application along with the area “ProductA” and the RSLinx Enterprise server in theFactoryTalk Administration Console. These components can be created and viewed inRSView Studio as well. We are using RSView Studio now because we need to add anRSView SE server.

We will add it to the area “ProductA”. Right mouse click on “ProductA” and select “New HMIServer”.


5. Select “Import a project” since we are going to import an already existing HMI serverproject.


6. Select “RSView Supervisory Edition Project” and click on the ellipsis button to the right

7. Click on the ellipsis button and browse to C:\OP09\HMIServerToImport. This HMI servercontains two alarm tags and one other tag that can be used as a derived tag.

8. Name the HMI Server “HMIServerProductA” and click finish.


9. Keep RSView Studio open. You can minimize if it if you like.


Configure the RSOPC Gateway

In this section we are going to configure the RSOPC Gateway to reference our FactoryTalkapplication. The RSOPC Gateway will point to the root level of the Monitoring System application.RSOPC Gateway has to point to a specific FactoryTalk application or an area within aFactoryTalk application.

1. Start the RSOPC Gateway Configuration Tool.

From the Start menu, select Programs > Rockwell Software > RSOPC Gateway->RSOPCGateway Configuration.

2. Stop the service. RSOPC Gateway is not configured yet for a FactoryTalk directory scope.Note the error “Parameter is incorrect” under selected scope.

3. When you stop the RSOPC Gateway service a message will pop up warning you that stoppingthe OPC server will disconnect OPC clients. Select Yes.


4. Select configure. This will allow us to point to a FactoryTalk application.

5. Select Network since we are going to connect to our network scoped FactoryTalk application.

6. If you are prompted to log on to FatoryTalk. Username = administrator; password = rockwell

7. Choose “ProductA” for the scope and then select OK. Note that ProductA is an Area that wecreated.


8. Select Yes.

9. Start the service.


Test the OPC connection with the OPC Test Client

Now we are going to use the OPC test client that ships with the RSOPC Gateway to test our OPCconnection.

1. Start the OPC Test Client. From the Start menu, select Programs > Rockwell Software >RSLinx->Tools->OPC Test Client.

2. Select Server > Connect

3. Choose RSOPC Gateway. An OPC client will find the available OPC servers on a machine. Ifyou are using an OPC client that’s remote to an RSOPC Gateway then you need to install theremote client setup utility that is included on the product CD. For this lab we do not need toinstall it since everything is on the same box.


4. Add a Group. This is a collection of tags with the same update rate.

5. Give the group name “BunchOTags” and make the update rate = 1msec.

6. Add an Item. This will open the Browse window so we can browse for the available tags. Fromthe OPC test client window go to Item>Add Item


7. Go to the root of the RSOPC Gateway (RSOPC Gateway (Node:<Local>). When weconfigured the RSOPC Gateway we configured it to point to the area ProductA. So here wesee the list of RSView SE server tags. Alrarm1_RSViewSE, Alarm2_RSViewSE, andUsedCLXMemory The “system” folder contains native RSView SE server tags


8. Now select ProductA, expand it and then select CLX_A. We are pointing to the SoftLogixController. There are diagnostic counters in the Diagnostic Items folder and the Online foldercontains the controller tags.

Click on Online and browse to UDT1.INT1

9. Click on OK to add the tag and to start collecting data from UDT1.INT1.


Serve 10,000 ControlLogix Data Points a second and keep thedata server CPU utilization low.

We are going to put 10,000 ControlLogix tags on scan via the OPC test client. All of the tagnames and relative path with the FactoryTalk application are stored in a csv file located inC:\OP09. The update rate is 1000ms so we collecting updates from 10,000 tags once a second.

1. Start the OPC Test Client. From the Start menu, select Programs > Rockwell Software >RSLinx->Tools->OPC Test Client.

2. Select Open.

3. Browse to C:\OP09 and select 10000 OPC Data Items.csv


4. Verify that the quality is good and that the data beings to update. The ControlLogix processorshould be in run mode so all of the data is changing. Keep this OPC test client open, as wewill need this in the next section of the lab.

Right mouse click in the system tray (close to the clock in Windows) and select task manager.Look at the CPU utilization for both RSLinx Enterprise and RSOPC Gateway. Note that theyare pretty low. ~3%-4% each. The overall CPU utilization is high since softlogix is running inthis computer and consuming most of the CPU. Data collection of these 10,000 is taking upno more than 6%-8% of the total system CPU.


Making Online Changes

In this section we are going to edit a ControlLogix program by removing a data member of aUser-Defined data type, adding a member, and then downloading while an OPC client still hastags on scan.

1. Make sure that the OPC test client is still running from the previous section of the lab.

2. Double click on the “ProductA.ACD’ file on your desktop. This will open up the RSLogixprogram for our

3. Open the INTStructure user-defined data type definition. We are going to make edits to themembers of this data type. The OPC Client is currently serving data of this data type.


3. Scroll Down to the bottom of the data type editor and remove the member “INT222”. Rightmouse click on the row containing “INT222” and select delete.

4. Add a data member named “INTXXX” to the INTStructure data type.

5. Click OK in the data type editor and then save the RSLogix 5000 file.

6. Download this program to the Softlogix controller. In RSLogix 5000 select Communications->Who Active from the menu. Browse to slot 2 of the AB_VBP-1 driver and select Download.


7. Go back to the OPC test client and notice that the all of the tags have a bad quality. After thedownload is complete the quality of the tags will go back to good and start to update again. Ifthe data is not changing then make sure that the processor is in run mode.

8. In the OPC test client scroll down to see UDT1.INT222. Note that the quality is bad since thetag no longer exists in the processor. You can verify this for the other UDT instances (UDT2,UDT3…) The other tags not effected still have a good quality.

9. We need to do an extra step here until we resolve an issue with RSLinx Enterprise. From theStart menu, select Settings > Control Panel > Administrative Tools > Services and stopand then restart the RSLinx Enterprise service.

10. Now we are going to collect the UDT data member that we added. In the OPC test client go toGroup->Add Group. Select OK to accept the defaults of the “add new group” dialog that popsup. We’re adding another group here so we don’t have to scroll through 10,000 tags when weadd the tag.


10. Go to Item->Add Item. Scroll down to CLX_A and expand the online folder.

11. Expand one of the UDT data types and search for the member “INTXXX” on the right handside of the tag browser.


11. Click OK to add the tag. You should now see the tag in the OPC test client with a value ofzero and a good quality.


Viewing RSLinx Enterprise Diagnostics

RSLinx Enterprise now has a diagnostics counter display. For the lab you can launch it from theDesktop. This diagnostic screen can be launched from the desktop when CP7 ships. See theappendix for a description of the counters related to ControlLogix based processors. Thesecounters are designed for hardware and not SoftLogix controllers.

Remember that you can use this stand-alone display and you can use these counter directly inyour application via OPC tags if you have RSOPC Gateway.

1. Make sure that you still have the OPC test client still open and collecting data. Go to theDesktop and launch the CounterMonitor.

CounterMonitor.exe.lnk

2. Click the add workstation button. You can add several machine names containing RSLinxEnterprise servers.


3. Find the hostname of the computer that you are on.

4. For each shortcut there is a list of diagnostic counters available. These can be used directly inyour applications like an RSView SE display or in a derived tag. See the appendix for adescription of the diagnostic counters.


Troubleshooting

When some of the tags do not update and have a bad quality

1. Lets go back to the first group (_Group0) that we created with 10,000 tags. Note again that allof the tags containing UDTX.222 have a bad quality.

2. Lets check out the FactoryTalk Diagnostics and see what events have occurred related to this.Start the OPC Test Client. From the Start menu, select Settings > Control Panel >Administrative Tools>Event Viewer. Check out the FactoryTalk Diagnostics log.

3. Look though the log and notice that several tags have a warning message

CLXDP) Item 'UDTX.INT222' does not exist in the processor on route RSI-LINXHMIS.Backplane.ProductA.

So now we know that we would need to clean up our OPC client to stop asking for tags that don’texist in the processor.

4. Keep scrolling down the FactoryTalk Diagnostics events notice that you come across twoevents.

§ (CLXDP) CLX Processor download finished on route RSI-LINXHMIS.Backplane.ProductA.

§ (CLXDP) CLX Processor download started on route RSI-LINXHMIS.Backplane.ProductA.

The download that we performed got captured in FactoryTalk Diagnostics. We can see the historyof what changes were made to the system.


Data not updating; Tags have bad quality or OPC clients can tbrowse for tags

We are not going to simulate this problem in the lab but here are the steps to follow whentroubleshooting.

A. Check the RSLinx Enterprise configuration

1. Go to the FactoryTalk Administration console or to RSView Studio.

2. Drill down to the RSLinx Enterprise server. Right mouse click on it and select properties.Make sure that the correct computer hosting RSLinx Enterprise is listed.

3. Double Click on Communication Setup

4. Make sure that there is a shortcut configured and that has the correct name

5. Click on the shortcut and make sure that it’s pointing to the expected device within theRSWho tree.

6. Right mouse click on the network that you are using and select Start Browsing.

If the device disappears then RSLinx Enterprise is no longer finding the device on thenetwork. Continue tracing the network or device.

B. If RSLinx Enterprise is configured correctly and the device is present then we should be able tobrowse the namespace and collect some data with the Rockwell Software Data Client that shipswith the FactoryTalk Administration Console.

1. Open the Rockwell Software Data Client. From the Start menu, select Programs >Rockwell Software > FactoryTalk Tools >Rockwell Software Data Client.

2. Select FactoryTalk on the top of the dialog and then select the type of FactoryTalkdirectory that you are using. (Network or Local)


3. Navigate to the application containing the RSLinx Enterprise that you are trying to use. Browseand put some data scan. If you can’t browse for the tags then RSLinx Enteprise is not configuredcorrectly or the devices that RSLinx Enterprise is pointing to are not configured or connected.

C. Check the RSOPC Gateway configuration

1. Open the RSOPC Gateway Configuration. Check to see if the server is running or stopped.If it is then stopped the server and click on configure. Make sure that the proper applicationincluding scope (network or local) is selected.

2. View that you have the correct activation for the application that you are trying to run.(Distributed vs. Station, maximum tag count) Verify this with the FactoryTalk Diagnostics logto see the project that you are trying to load is demands a different activation then you have.


Appendix

Counters that can be used for ControlLogix family of processors

Name of predefined item Description OPC Datatype

General information and status

@DevicePath Returns the path to the target device(e.g., Ethernet.192.168.100.101,SerialDF1.1, DH+.055.

VT_BSTR

@ProcessorName Returns the ControlLogix processor'sproject name. Use to determine ifcommunications can be establishedwith the processor and determine whatproject the processor is presentlyrunning.

STRING

@IsPresent Returns whether the processor ispresent and has a valid program. Useto determine whether communicationscan be established with the processor.Value is 0 if the processor is offline ordoes not have a valid program. Valueis 1 if it does.

VT_UI4

@Mode Returns the current operating mode ofthe processor. (Run, Program,Remote Run, Remote Program). Thiscan be used to determine why dataisn't changing.

STRING

@Status Returns the current status of theprocessor (OK or Faulted.)

STRING

@Revision Returns the processor's firmwarerevision.

STRING

@RedundancyMode Returns the redundancy mode of theprocessor. Presently this is supportedonly in ControlLogix 5555. Primaryreturns 1; anything else returns 0.

VT_UI2

@DPVersion Returns the version of the ControlLogixData Provider. Use to determine the

STRING


actual version string of theControlLogix Data Provider file. Thiswould be useful in determining patchrelease versions.

Packet status

@PacketsSent Returns the total number of packetssent to the ControlLogix processor.

VT_UI4

@PacketsReceived Returns the total number of packetsreceived from the ControlLogixprocessor.

VT_UI4

@PacketsCancelled Returns the total number of packetscancelled for the ControlLogixprocessor. This could be due to itemsbeing removed, etc.

VT_UI4

@AveragePacketResponse Returns the average packet responsetime from the ControlLogix processor.Use to determine the average amountof time it takes the processor torespond to the packets. This time alsoincludes the time it waits in aconnection queue to be handled.

VT_UI4

@PacketsPerSecond Returns the average number ofreceived packets per second. Use todetermine the rate at which packetscan be read.

VT_R8

@CLXPacketsReinitialized Returns the number of packets thatwere re-initialized due a connectiondrop or other problem.

VT_UI4

@CLXWritePackets Returns the packets written to theprocessor.

VT_UI4

@NumberOfOptimizedPackets Returns the total number of optimizedpackets to the ControlLogix processor.Use to determine the number of pre-optimized items on scan.

VT_UI4

@NumberOfCLXOptimizedPackets Returns the total number of optimizedpackets to the ControlLogix processor.Use to determine the number ofpackets that are required to read thedata. (This includes both ControlLogixdata items and predefined items.)

VT_UI4

Connection status

@ConnectionsActive Returns the number of active CIP VT_UI4


connections.

@ConnectionsDropped Returns the number of dropped CIPconnections.

VT_UI4

@ConnectionsAttempted Returns the number of CIPconnections attempted.

VT_UI4

@ConnectionOpensFailed Returns the number of CIP connectionopen attempts that failed. Use to test anew connection after an item is firstadded to the network or after adisconnect requires a new connection.

VT_UI4

@ConnectionOpensRejected Returns the number of CIP connectionopen attempts that were rejected. Useto determine network errors whenattempting to open connection. This isnormally done when items are firstadded or when a disconnect requires anew connection.

VT_UI4

@ConnectionsClosed Returns the number of CIPconnections that were closed. Use todetermine if connections were closedafter items have been removed.

VT_UI4

@ConnectionClosesFailed Returns the number of CIP connectionclose attempts that failed. This ischecked when all clients haveremoved their items or no furtherwrites are being done and an attemptis made to close the connection. Useto determine network errors whenattempting to close connections.

VT_UI4

@ConnectionClosesRejected Returns the number of CIP connectionclose attempts the were rejected. Thisis checked when all clients haveremoved their items or no furtherwrites are being done and an attemptis made to close the connection. Useto determine network errors whenattempting to close connections.

VT_UI4

@LastConnectionDropTime Returns the last time a CIP connectionwas dropped. Use to determine whenthe last connection occurred in relationto the present time.

STRING

@FirstConnectionDropTime Returns the first time a CIP connectionwas dropped. Use to determine thefirst time a connection dropped alongwith the last connection drop time todetermine when the actual network

STRING


errors began occurring.

Items status

@NumberOfItems Returns the total number of items thatare presently added. The number ofitems includes the data items and thepredefined items for that device.

VT_UI4

@NumberOfPredefinedItems Returns the number of predefineditems on scan.

VT_UI4

@NumberOfDataItems Returns the number of data itemsadded;

that is, the actual number of uniquetags the ControlLogix device isproviding. UDTs and arrayed items arecounted separately. However, if youdefine an arrayed item as "item,L10" itis considered one item.

VT_UI4

@WriteItems Returns the items written to theprocessor.

VT_UI4

@WriteItemsSuccess Returns the number of writes in whichthe item's data could be correctlyconverted to the processor type.

VT_UI4

@WriteItemsFailure Returns the number of writes in whichthe item's data could not be correctlyconverted to the processor type.

VT_UI4

@AddItems Returns the number of Added Items.Returns the number of items that havebeen added for the processor withwhich you are communicating.

VT_UI4

@AddItemsIgnored Returns the number of Added Itemsthat were ignored because the sameitem was already on scan. Use todetermine if there are duplicate items;for example, if there are any items thatare on the same screen or a macro,etc.

VT_UI4

@RemoveItems The number of Remove Item calls. Useto determine how many items havebeen removed versus the added count.

VT_UI4

@RemoveItemsDuplicate Returns the number of Remove Itemcalls that resulted in a item referencecount decrement instead of removalbecause it is a duplicate item.

VT_UI4


Scan status

@CLXMaxScanTime Returns the maximum scan time of theControlLogix processor. Use todetermine processor execution time.

VT_UI4

@CLXPresentScanTime Returns the present scan time of theControlLogix processor. Use todetermine processor scan executiontime.

VT_UI4

Memory status

@FreeMem Returns the total amount of freememory in the processor.

VT_UI4

@FreeMemIO Returns the total amount of freememory in the I/O section of theprocessor.

VT_UI4

@FreeMemDT Returns the total amount of freememory in the Data Table section ofthe processor.

VT_UI4

@FreeMemGM Returns the total amount of freememory in the General Memorysection of the processor.

VT_UI4

@FreeMemSC Returns the total amount of freesecurity memory is available in theprocessor.

VT_UI4

@TotalMem Returns the total amount of memory inthe processor.

VT_UI4

@TotalMemDT Returns the total amount of Data Tablememory contained in the processor.

VT_UI4

@TotalMemGM Returns the total amount of GeneralMemory in contained in the processor.

VT_UI4

@TotalMemIO Returns the total amount of I/Omemory contained in the processor.

VT_UI4

@TotalMemSC Returns the total amount of securitymemory contained in the processor.

VT_UI4

Poll requests

@PollBlocks Returns the number of poll requestsfrom the FactoryTalk Toolkit. Use todetermine whether items are still beingpolled.


Notes

op09_rsopcgateway

Documents

factorytalk application

rslinx enterprise server

rsview se data

rslinx enterprise diagnostics

rsview se server

opc connection

opc clients access

rsopc gateway connection