tn_rf_13 - opc configuration

8/2/2019 TN_RF_13 - OPC Configuration

1/26

Ref : TN_RF_13 V1.0

BeanairFRANCE

ww.beanair.com

TECHNICAL NOTE OPC Configuration


2/26

Rethinking sensing technologyDocument version : 1.0

OPC ConfigurationDocument type : Technical Note

Ref: TN_RF_011 Publication date : 20/02/2012 model B_SES_120 Page : 1 / 26

DOCUMENT

Document number Version V1.0

External Reference TN_RF_011 Publication date 20/02/2012

Author Christophe DONTEGREUIL

Internal Reference Project Code N.A.

Document Name OPC ConfigurationVALIDATION

Function RecipientsForValidation

Forinformation

Reader Maneli PARSY X

Author X

MAILING LIST

Function Recipients For action For Info

Staffer 1 Loic PENELON XStaffer 2 Christophe DONTEGREUIL X

UpdatesVersion Date Author Evolution & Status

V1.0 20/02/2012 Maneli PARSY First version of the document


3/26




1. TECHNICAL SUPPORT .................................................................................................................................... 4

2. VISUAL SYMBOLS DEFINITION ...................................................................................................................... 5

3. ACRONYMS AND ABBREVIATIONS ............................................................................................................... 6

4. RELATED DOCUMENTS .................................................................................................................................. 7

4.1 Applications Notes ..................................................................................................................................... 7

4.2 Technical Notes ......................................................................................................................................... 8

5. AIM OF THE DOCUMENT ................................................................................................................................ 9

6. SOME DEFINTIONS ....................................................................................................................................... 11

6.1 What is the OPC ? ................................................................................................................................... 11

6.2 DCOM (Distributed Component Object Model) ....................................................................................... 12

6.3 OPC and DCOM ...................................................................................................................................... 12

7. INSTALLING THE OPC CORE COMPONENTS ............................................................................................ 13

8. CONFIGURING COM AND DECOM WHEN USING A CLIENT ON A SEPARATE COMPUTER ................. 14

9. CONFIGURING THE OPC ON WINDOWS 7 ................................................................................................. 24

Contents


4/26




Disclaimer

The information contained in this document is the proprietary information of BeanAir.

The contents are confidential and any disclosure to persons other than the officers, employees, agents orsubcontractors of the owner or licensee of this document, without the prior written consent of BeanAir Ltd, isstrictly prohibited.

BeanAir makes every effort to ensure the quality of the information it makes available. Notwithstanding theforegoing, BeanAir does not make any warranty as to the information contained herein, and does not acceptany liability for any injury, loss or damage of any kind incurred by use of or reliance upon the information.

BeanAir disclaims any and all responsibility for the application of the devices characterized in this document,

and notes that the application of the device must comply with the safety standards of the applicable country,and where applicable, with the relevant wiring rules.

BeanAir reserves the right to make modifications, additions and deletions to this document due totypographical errors, inaccurate information, or improvements to programs and/or equipment at any time andwithout notice.

Such changes will, nevertheless be incorporated into new editions of this document.Copyright: Transmittal, reproduction, dissemination and/or editing of this document as well as utilization of itscontents and communication thereof to others without express authorization are prohibited. Offenders will beheld liable for payment of damages. All rights are reserved.

Copyright BeanAir Ltd. 2012.


5/26




1. TECHNICAL SUPPORT

For general contact, technical support, to report documentation errors and to order manuals, contact

BeanAir Technical Support Center(BTSC) at:

[email protected]

For detailed information about where you can buy the BeanAir equipment/software or for

recommendations on accessories and components visit:

www.beanair.com

To register for product news and announcements or for product questions contact BeanAirs Technical

Support Center (BTSC).

Our aim is to make this user manual as helpful as possible. Please keep us informed of your comments and

suggestions for improvements. BeanAir appreciates feedback from the users.
mailto:[email protected]:[email protected]://www.beanair.com/http://www.beanair.com/http://www.beanair.com/mailto:[email protected]


6/26




2. VISUAL SYMBOLS DEFINITION

Visual Definition

Caution or Warning Alerts the user with important informationabout BeanAir wireless sensor networks (WSN), if this information isnot followed, the equipment /software may fail or malfunction.

Danger This information MUST be followed if not you may damagethe equipment permanently or bodily injury may occur.

Tip or Information Provides advice and suggestions that may beuseful when installing BeanAir Wireless Sensor Networks.


7/26




3. ACRONYMS AND ABBREVIATIONS

AES Advanced Encryption Standard

CCA Clear Channel Assessment

CSMA/CA Carrier Sense Multiple Access/Collision Avoidance

DA Direct Access

GTS Guaranteed Time-Slot

kSps Kilo samples per second

LLC Logical Link Control

LQI Link quality indicator

LDCDA Low duty cycle data acquisition

MAC Media Access Control

PAN Personal Area Network

PER Packet error rate

OPC Ole for Process Control

RF Radio Frequency

SD Secure Digital

WSN Wireless sensor Network


8/26




4. RELATED DOCUMENTS

In addition to this User manual, please consult the application notes & technical notes:

4.1 APPLICATIONS NOTES

Nom du document Produits concerns Description

AN_RF_007 : Beanair_WSN_Deployment All BeanAir products Wireless sensor networks

deployment guidelines

AN_RF_006 How to extend your wireless

range

All BeanAir products A guideline very useful for extending

your wireless range

AN_RF_005 Ver 1.0- BeanGateway & Data

Terminal Equipment Interface

BeanGateway DTE interface Architecture on the

BeanGateway

AN_RF_004 V1.0-1. Coexistence And

[email protected]

All BeanAir products Coexistence & interferences of

different RF technologies in the 2.4

GHz frequencies band.

AN_RF_003 V1.1 IEEE 802.15.4 2.4 GHz Vs

868 MHz (English)

All BeanAir products Comparison between 868 MHz

frequency band and a 2.4 GHzfrequency band.


9/26




4.2 TECHNICAL NOTES

Document name Concerned products Description

TN_RF_011 OPC Configuration OPC & BeanScape The aim of this document is to helpdeploying the OPC DA and all associatedservices.

TN_RF_010 BeanDevice Power

Management

All the BeanDevice This technical note describes the sleep &

active power mode on the BeanDevice.

TN_RF_009 BeanGateway management

on LAN infrastructure

BeanGateway BeanGateway integration on a LAN

infrastructure

TN_RF_008 Data acquisition modes

available on the BeanDevice

All the BeanDevice Data acquisition modes available on the

BeanDevice

TN_RF_007BeanDevice DataLogger User

Guide

All the BeanDevice This document presents the DataLogger

feature on the BeanDevice

TN_RF_006 BeanDevice wireless

network association

All the BeanDevice Description of the BeanDevice network

association

TN_RF_005 Pulse counter & binary data

acquisition on the BeanDevice SUN-BN

BeanDevice SUN-BN This document presents Pulse counter (ex:

energy metering application) and binary

data acquisition features on the

BeanDevice SUN-BN.

TN_RF_004 - Ambient Light sensor technicalspecifications

BeanDevice SUN-XX(Ecosensor)

Technical description of the Ambient light

sensor available on the BeanDevice SUN-

XX products

RF_TN_003 V1.0- Wireless Network capacity All the products Network capacity characterization of

Beanair Wireless Sensor Networks

RF_TN_002 V1.0 - Current consumption in

active & sleep mode

BeanDevice Current consumption estimation of the

BeanDevice in active and sleeping mode

RF_TN_001 V1.0- Wireless range

benchmarking

BeanDevice Wireless range benchmarking of theBeanDevice


10/26




5. AIM OF THE DOCUMENT

The aim of this document is to help deploying the OPC DA and all associated services.


11/26





12/26




6. SOME DEFINTIONS

6.1 WHAT IS THE OPC ?

OPC is all about Open Productivity & Connectivity in industrial automation and the enterprisesystems that support industry. Interoperability is assured through the creation and maintenance of openstandards specifications. There are currently seven standards specifications completed or in development.

Based on fundamental standards and technology of the general computing market, the OPC Foundationadapts and creates specifications that fill industry-specific needs. OPC will continue to create new standardsas needs arise and to adapt existing standards to utilize new technology.

OPC is a series of standards specifications.The first standard (originally called simply the OPCSpecification and now called the Data Access Specification) resulted from the collaboration of a number ofleading worldwide automation suppliers working in cooperation with Microsoft. Originally based onMicrosoft's OLE COM (component object model) and DCOM (distributed component object model)technologies, the specification defined a standard set of objects, interfaces and methods for use in processcontrol and manufacturing automation applications to facilitate interoperability. The COM/DCOMtechnologies provided the framework for software products to be developed. There are now hundreds ofOPC Data Access servers and clients.

Everyone's favorite analogy for needing the original Data Access Specification is printer drivers in DOS andthen in Windows. Under DOS the developer of each application had to also write a printer driver for everyprinter. So AutoCAD wrote the AutoCAD application and the printer drivers. And WordPerfect wrote theWordPerfect application and the printer drivers. They had to write a separate printer driver for every printer

they wanted to support: one for an Epson FX-80 and one for the H-P LaserJet, and on and on. In theindustrial automation world, Intellution wrote their Human Machine Interface (HMI) software and a proprietarydriver to each industrial device (including every PLC brand). Rockwell wrote their HMI and a proprietarydriver to each industrial device (including every PLC brand, not just their own).

Windows solved the printer driver problem by incorporating printer support into the operating system. Nowone printer driver served all the applications! And these were printer drivers that the printer manufacturerwrote (not the application developer). Windows provided the infrastructure to allow the industrial devicedriver's solution as well. Adding the OPC specification to Microsoft's OLE technology in Windows allowedstandardization. Now the industrial devices' manufacturers could write the OPC DA Servers and the software(like HMIs) could become OPC Clients.

The resulting selfish benefit to the software suppliers was the ability to reduce their expenditures forconnectivity and focus them on the core features of the software. For the users, the benefit was flexibility.

They could now choose software suppliers based on features instead of "Do they have the driver to myunique device?" They don't have to create a custom interface that they must bear the full cost of creating andupgrading through operating system or device vendor changes. Users were also assured of better qualityconnectivity as the OPC DA Specification codified the connection mechanism and compliance testing. OPCinterface products are built once and reused many times; hence, they undergo continuous quality control andimprovement. The user's project cycle is shorter using standardized software components. And their cost islower. These benefits are real and tangible. Because the OPC standards are based in turn upon computerindustry standards, technical reliability is assured.

The original specification standardized the acquisition of process data. It was quickly realized thatcommunicating other types of data could benefit from standardization. Standards for Alarms & Events,Historical Data, and Batch data were launched.


13/26




6.2 DCOM (DISTRIBUTED COMPONENT OBJECT MODEL)

DCOM (Distributed Component Object Model) is a set of Microsoft concepts and program interfaces inwhich client program object s can request services from server program objects on other computers in anetwork. DCOM is based on the Component Object Model (COM), which provides a set of interfacesallowing clients and servers to communicate within the same computer (that is running Windows 95 or a laterversion).

For example, you can create a page for a Web site that contains a script or program that can be processed(before being sent to a requesting user) not on the Web site server but on another, more specialized serverin the network. Using DCOM interfaces, the Web server site program (now acting as a clientobject ) canforward a Remote Procedure Call ( RPC ) to the specialized server object, which provides the necessaryprocessing and returns the result to the Web server site. It passes the result on to the Web page viewer.

DCOM can also work on a network within an enterprise or on other networks besides the public Internet. It

uses TCP/IP andHypertext Transfer Protocol . DCOM comes as part of the Windows operating systems.DCOM is or soon will be available on all major UNIX platforms and on IBM's large server products. DCOMreplaces OLE Remote Automation.

DCOM is generally equivalent to the Common Object Request Broker Architecture ( CORBA ) in terms ofproviding a set of distributed services. DCOM is Microsoft's approach to a network-wide environment forprogram and data objects. CORBA is sponsored by the rest of the information technology industry under theauspices of the Object Management Group ( OMG ).

6.3 OPC AND DCOM

The OPC specifications Data Access, Alarms & Events and Historical Data Access are based on theDistributed Component Object Model, which is part of all Windows operating systems. The nearly"ubiquitous" Microsoft platform, even in industrial environments, is certainly one reason for the rapiddistribution of OPC. However, DCOM restricts the use of OPC technology to Windows operating systems.For years now, industry has been calling on the OPC Foundation to provide an OPC standard that can beutilized on different operating systems (manufacturers of ERP systems on Unix platforms and manufacturersof embedded systems with real-time operating systems such as VxWorks, QNX, etc).OPC XML-DA andOPC UA are no longer based on DCOM but on a service oriented architecture (SOA).
http://searchenterprisedesktop.techtarget.com/definition/clienthttp://searchsoa.techtarget.com/definition/objecthttp://whatis.techtarget.com/definition/0,,sid9_gci212964,00.htmlhttp://searchwinit.techtarget.com/definition/Component-Object-Modelhttp://searchsoa.techtarget.com/definition/objecthttp://searchsoa.techtarget.com/definition/Remote-Procedure-Callhttp://searchnetworking.techtarget.com/definition/TCP-IPhttp://searchwindevelopment.techtarget.com/definition/HTTPhttp://searchsqlserver.techtarget.com/definition/CORBAhttp://searchsoa.techtarget.com/definition/Object-Management-Grouphttp://searchsoa.techtarget.com/definition/Object-Management-Grouphttp://searchsqlserver.techtarget.com/definition/CORBAhttp://searchwindevelopment.techtarget.com/definition/HTTPhttp://searchnetworking.techtarget.com/definition/TCP-IPhttp://searchsoa.techtarget.com/definition/Remote-Procedure-Callhttp://searchsoa.techtarget.com/definition/objecthttp://searchwinit.techtarget.com/definition/Component-Object-Modelhttp://whatis.techtarget.com/definition/0,,sid9_gci212964,00.htmlhttp://searchsoa.techtarget.com/definition/objecthttp://searchenterprisedesktop.techtarget.com/definition/client


14/26




7. INSTALLING THE OPC CORE COMPONENTS

Note: Before you begin this task, you must have a Windows administrator account.

Log onto Windows using an administrator account.

Insert the distribution CD.

The OPC Products Installer window opens.

If the disk does not start (Windows settings can causethis), locate and select the file named autorun.exe.

Click to install the OPC Core ComponentsRedistributable.

The OPC Core Components Redistributable Setup Wizardstarts.

Click Next.

At the Select Installation Folder step, do the following:Document: 553701 Issue 1.2: March 2011 2-3

Accept the default folder for the installation.

Select the radio button for Everyone.

Click Next.

Review and accept the Licence Agreement, click Next.

At Confirm Installation, click Next to start theinstallation.

When Installation Complete appears, click Close.

You have now installed the OPC Core ComponentsRedistributable.

OPC corecompnentinstallation


15/26




8. CONFIGURING COM AND DECOM WHEN USING A CLIENT ON A

SEPARATE COMPUTER

You can use the OPC DA Server in a system with the clients and the server on separate computers. To dothis, you need to set up the Distributed COM (DCOM) protocol on each computer. This will enable theremote clients to communicate with the OPC Portal Server.

Note: You must use the same user name and password for the Windows accounts on each

computer.

Note: Before you begin this task, you must have a Windows administrator account.

To configure DCOM, do the following:

On windows 7

On Windows XP

Log onto Windows using an administrator account.

Open the Windows Control Panel and navigate to Administrative

Tools. Select Component Services.The Component Services applet starts.

Within the Component Services applet, navigate to ComponentServices Computers My Computer.

Step 1: Accessing

the componentservice


16/26





17/26




On Windows 7

On Windows XP

Right-click on My Computer to display the My Computer Properties,select the Default Properties tab.

Put a tick in the box labeled Enable Distributed COM on this computer.

Set the Default Authentication Level to None.

Set the Default Impersonation Level to Identify.

Step 2: Settingdefault theproperty


18/26




On Windows XP & 7

Select the COM Security tab.

Go to the Access Permissions area, click Edit Default.

The Access Permission dialog box opens.

Add a group named ANONYMOUS LOGON and allowLocal Access and Remote Access.

Similarly add a group named Everyone and allowLocal Access and Remote Access.

Click OK to close the Access Permission dialog box.

Step 3: Creating agroup for remote

access


19/26




On Windows XP & 7

Return to the COM Security tab of the My ComputerProperties dialog box.

Go to the Launch and Activation Permissions area, clickEdit Default.

The Launch Permission dialog box opens.

Add the group ANONYMOUS LOGON you created earlierand allow all permissions Local Launch, RemoteLaunch, Local Activation and Remote Activation.

Similarly add the group Everyone and allow all options.

Click OK.

Step 4: Settingthe persmission

for remotelaunch andactivation


20/26




On Windows XP & 7


Go to the Access Permissions area, click Edit Limits.

The Access Permission window opens.

Set the group ANONYMOUS LOGON to allow LocalAccess and Remote Access.

Similarly set the group Everyone to allow local andremote access.

Click OK.

Step 5: Settingthe persmission

for remote access


21/26




On Windows XP & 7


Go to the Launch and Activation Permissions area,click Edit Limits.

The Launch Permission window opens.

Set all four permissions for both Administrators andEveryone.

Click OK.

Step 6: Settingpersmission forremote launchand activation


22/26




On Windows XP and windows 7

Return to the Component Services applet.

Expand the My Computer item and select DCOMConfig.

Locate the ICSTriplexOPCServer in the list.

Right-click to open the properties for the server,select the General tab.

Set the Authentication Level to None.

Step 7: Settingthe

authentificationlevel


23/26





Go to the Identity tab.

Select the radio button labelled The system account (servicesonly). OPC Portal Server User Guide (AADvance Controller)

Click OK to save the new settings and close the OPC PortalServer Properties.

If you are not configuring a workgroup to use DCOM, reboot thecomputer.

The configuration of DCOM is complete.

Step 8:configuring

DCOM

If you are configuring a workgroup to use DCOM, you must set theOPCEnum properties.

Return to the DCOM Config section of the Component Servicesapplet.

Scroll down to locate OpcEnum.

Right-click to open the properties for OpcEnum, select the Securitytab.

In the Launch and Activation Permissions, select Use Default.

Similarly, in the Access Permissions, select Use Default.

Click OK.

Reboot the computer. The configuration of DCOM is complete.

Step 9:configuring

DCOM(Workgroup

Case)


24/26






25/26




9. CONFIGURING THE OPC ON WINDOWS 7

Sometimes deploying software on windows 7 may result problems. By switching on the windows XPcompatibility mode some of the issues can be solved, however the Beanscape and the OPC DA server arboth windows 7 compliant and operate perfectly without turning on the XP compatibility mode.

Apply the same procedure to your OPC client

Go to Windows program menu

select the beanscape.exe

right click browse through the Drop down menuright click onproperties

The property window appears.

Step 1: Accessingthe propertywindow


26/26



Ref: TN RF 011 Publication date : 20/02/2012 model B_SES_120 Page : 25 / 26

Apply the same procedure to your OPC client

Go to compatibility Tab and Make sure that the windows XP compatibility checkbox is

checked, if not then tick the check box

Make sure that the execute program as administrator

checkbox is checked, if not then tick the check box

Step 2:Compatibility

settings

Click on OK

The property window will close

Your setting will be savedIf necesary, go to the property window and check if your settinghas been saved correctly

Step 3: Save your

setting

tn_rf_13 - opc configuration

Documents