OPC DA 205a SpecificationWord文件下载.docx
《OPC DA 205a SpecificationWord文件下载.docx》由会员分享,可在线阅读,更多相关《OPC DA 205a SpecificationWord文件下载.docx(264页珍藏版)》请在冰点文库上搜索。
![OPC DA 205a SpecificationWord文件下载.docx](https://file1.bingdoc.com/fileroot1/2023-4/28/3599c2c3-86e1-481d-978c-d0526ca356bd/3599c2c3-86e1-481d-978c-d0526ca356bd1.gif)
SpecificationTypeIndustryStandardSpecification
Title:
OPCDataAccessCustom
InterfaceSpecification
Date:
June28,2002
Version:
2.05ASoftMS-Word
Source:
opcda205a_cust
Author:
OpcFoundationStatus:
Released
Synopsis:
ThisspecificationisthespecificationoftheinterfacefordevelopersofOPC
DataAccessclientsandOPCservers..Thespecificationisaresultofan
analysisanddesignprocesstodevelopastandardinterfacetofacilitatethe
developmentofserversandclientsbymultiplevendorsthatshallinter-operate
seamlesslytogether.
Trademarks:
Mostcomputerandsoftwarebrandnameshavetrademarksorregisteredtrademarks.Theindividualtrademarkshavenotbeenlistedhere.
RequiredRuntimeEnvironment:
ThisspecificationrequiresWindows95,WindowsNT4.0orlater
ii
NON-EXCLUSIVELICENSEAGREEMENT
TheOPCFoundation,anon-profitcorporation(the“OPCFoundation”),hasestablishedasetofstandardOLE/COMinterfaceprotocolsintendedtofostergreaterinteroperabilitybetweenautomation/controlapplications,fieldsystems/devices,andbusiness/officeapplicationsintheprocesscontrolindustry.
ThecurrentOPCspecifications,prototypesoftwareexamplesandrelateddocumentation(collectively,the
“OPCMaterials”),formasetofstandardOLE/COMinterfaceprotocolsbaseduponthefunctionalrequirementsofMicrosoft’sOLE/COMtechnology.Suchtechnologydefinesstandardobjects,methods,andpropertiesforserversofreal-timeinformationlikedistributedprocesssystems,programmablelogiccontrollers,smartfielddevicesandanalyzersinordertocommunicatetheinformationthatsuchserverscontaintostandardOLE/COMcomplianttechnologiesenableddevices(e.g.,servers,applications,etc.).
TheOPCFoundationwillgranttoyou(the“User”),whetheranindividualorlegalentity,alicensetouse,andprovideUserwithacopyof,thecurrentversionoftheOPCMaterialssolongasUserabidesbythetermscontainedinthisNon-ExclusiveLicenseAgreement(“Agreement”).IfUserdoesnotagreetothetermsandconditionscontainedinthisAgreement,theOPCMaterialsmaynotbeused,andallcopies(inallformats)ofsuchmaterialsinUser’spossessionmusteitherbedestroyedorreturnedtotheOPCFoundation.ByusingtheOPCMaterials,User(includinganyemployeesandagentsofUser)agreestobeboundbythetermsofthisAgreement.
LICENSEGRANT:
SubjecttothetermsandconditionsofthisAgreement,theOPCFoundationherebygrantstoUseranon-exclusive,royalty-free,limitedlicensetouse,copy,displayanddistributetheOPCMaterialsinordertomake,use,sellorotherwisedistributeanyproductsand/orproductliteraturethatarecompliantwiththestandardsincludedintheOPCMaterials.
AllcopiesoftheOPCMaterialsmadeand/ordistributedbyUsermustincludeallcopyrightandotherproprietaryrightsnoticesincludeonorinthecopyofsuchmaterialsprovidedtoUserbytheOPCFoundation.
TheOPCFoundationshallretainallright,titleandinterest(including,withoutlimitation,thecopyrights)intheOPCMaterials,subjecttothelimitedlicensegrantedtoUserunderthisAgreement.
WARRANTYANDLIABILITYDISCLAIMERS:
UseracknowledgesthattheOPCFoundationhasprovidedtheOPCMaterialsforinformationalpurposesonlyinordertohelpUserunderstandMicrosoft’sOLE/COMtechnology.THEOPCMATERIALSAREPROVIDED“ASIS”WITHOUTWARRANTYOFANYKIND,EXPRESSORIMPLIED,INCLUDING,BUTNOTLIMITEDTO,WARRANTIESOFPERFORMANCE,MERCHANTABILITY,FITNESSFORAPARTICULARPURPOSEORNON-INFRINGEMENT.USERBEARSALLRISKRELATINGTOQUALITY,DESIGN,USEANDPERFORMANCEOFTHEOPCMATERIALS.TheOPCFoundationanditsmembersdonotwarrantthattheOPCMaterials,theirdesignortheirusewillmeetUser’srequirements,operatewithoutinterruptionorbeerrorfree.
INNOEVENTSHALLTHEOPCFOUNDATION,ITSMEMBERS,ORANYTHIRDPARTYBELIABLEFORANYCOSTS,EXPENSES,LOSSES,DAMAGES(INCLUDING,BUTNOTLIMITEDTO,DIRECT,INDIRECT,CONSEQUENTIAL,INCIDENTAL,SPECIALORPUNITIVEDAMAGES)ORINJURIESINCURREDBYUSERORANYTHIRDPARTYASARESULTOFTHISAGREEMENTORANYUSEOFTHEOPCMATERIALS.
iii
GENERALPROVISIONS:
ThisAgreementandUser’slicensetotheOPCMaterialsshallbeterminated(a)byUserceasingalluseoftheOPCMaterials,(b)byUserobtainingasupersedingversionoftheOPCMaterials,or(c)bytheOPCFoundation,atitsoption,ifUsercommitsamaterialbreachhereof.UponanyterminationofthisAgreement,UsershallimmediatelyceasealluseoftheOPCMaterials,destroyallcopiesthereoftheninitspossessionandtakesuchotheractionsastheOPCFoundationmayreasonablyrequesttoensurethatnocopiesoftheOPCMaterialslicensedunderthisAgreementremaininitspossession.
Usershallnotexportorre-exporttheOPCMaterialsoranyproductproduceddirectlybytheusethereoftoanypersonordestinationthatisnotauthorizedtoreceivethemundertheexportcontrollawsandregulationsoftheUnitedStates.
TheSoftwareandDocumentationareprovidedwithRestrictedRights.Use,duplicationordisclosurebytheU.S.governmentissubjecttorestrictionsassetforthin(a)thisAgreementpursuanttoDFARs
227.7202-3(a);
(b)subparagraph(c)
(1)(i)oftheRightsinTechnicalDataandComputerSoftwareclauseat
DFARs252.227-7013;
or(c)theCommercialComputerSoftwareRestrictedRightsclauseatFAR52.227-
19subdivision(c)
(1)and
(2),asapplicable.Contractor/manufactureristheOPCFoundation,P.O.Box
140524,Austin,Texas78714-0524.
ShouldanyprovisionofthisAgreementbeheldtobevoid,invalid,unenforceableorillegalbyacourt,thevalidityandenforceabilityoftheotherprovisionsshallnotbeaffectedthereby.
ThisAgreementshallbegovernedbyandconstruedunderthelawsoftheStateofMinnesota,excludingitschoiceorlawrules.
ThisAgreementembodiestheentireunderstandingbetweenthepartieswithrespectto,andsupersedesanypriorunderstandingoragreement(oralorwritten)relatingto,theOPCMaterials.
iv
Revision2.05AHighlights
Thisrevisionclarifiessection4.2.13Note(5)regardingroundupwhenconvertingfloatsanddoublestointegers.AlsocorrectanerrorinthepropertydefinitionsinAppendixD(200-207wereoffby1).
Revision2.05Highlights
ThisrevisionincludesnumerousclarificationstoSection4.2.13regardingdataconversionbetweenNativeandRequesteddatatypes.
Revision2.04Highlights
ThisrevisionincludesadditionalminorclarificationstocertainambiguitieswhichwerediscoveredduringInteroperabilitysessionsandduringthedevelopmentoftheComplianceTest.Theaffectedsectionsinclude:
TimeBiasandDeadBanddiscussioninGroupObject:
GeneralProperties(4.5.1).LocaleIDforSetState(tomakeitclearthebehaviourisoptional).AdditionorClarificationoferrorreturnsE_INVALIDARGandS_FALSEreturnforGetItemProperties,LookupItemIDs,AddItems,ValidateItems,RemoveItems,SetActiveState,SetClientHandles,SetDataTypes,bothSyncIOandAsyncIOReadandWrite.InparticularforS_FALSE:
change'
waspartiallysuccessful'
to'
completedwithoneormoreerrors'
.Thisnowclearlyimpliesthatthemethodoutputs(specificallytheppErrorsreturns)aredefinedinthiscase.Otheradjustmentstothetextweretomakeerrorreturnsmoreconsistantacrossfunctions.ClarifyGetItemIDbehavior.InRefresh2andIOPCDataCallback:
:
OnDataChangetheTransactionIDparameterisclarified.Specifically:
0isanallowedvalue.SeealsotheintroductiontoOPCAsyncIO(4.5.6).Alsoaddsection4.2.14asageneraldiscussionofClientandServerresponsibilitesregardingLocaleID.
Revision2.03Highlights
ThisrevisionincludesminorclarificationstotheDeadbanddiscussion(4.5.1.6).Italsoclarifiesthebehaviorofemptyenumerators;
ThedescriptionsofIOPCServer:
CreateGroupEnumeratorandIOPCBrowseServerAddressSpace:
BrowseAccessPathshavebeenclarifiedandcorrected.TheyarenowconsistantwiththeexistingdescriptionofIOPCBrowseServerAddressSpace:
BrowseOPCItemIDs.
Revision2.02Highlights
ThisrevisionincludesminorclarificationstotheOPCItemPropertiesInterfacediscussions(4.4.6),GroupStateMgt:
SetState(4.5.3.2)andtheold(1.0)StreamMarshallingDiscussion(4.6.4.6).
Revision2.01Highlights
ThisrevisionincludesclarificationstothedwAccessRightsFilterinIOPCBrowseServerAddressSpaceandalsothediscussionofaccessrightsingeneral(section6.7.6).
Revision2.0Highlights
Thisrevisionincludesenhancementstothe1.0ASpecification.Althoughchangesweremadethroughoutthedocument,thefollowingareasareorparticularimportance:
•ThisisnowreferedtoastheOPCDataAccessSpecificationasthereareotherOPCeffortsunderway.
•TheAutomationInterfacespecificationhasbeenseparatedintoaseparatedocument.
•Allprevious(1.0A)CustomInterfacesremaininplaceandunchangedexceptforminorclarifications.
•AsyncandexceptionbasedconnectionsshouldnowbedoneusingConnectionPointsratherthan
IDataObject.TheexistingIOPCAsyncIO,IDataObjectandClientsideIAdviseSinkinterfacessupport
‘oldstyle’(Version1.0)connections.ThenewIOPCAsyncIO2,IConnectionPointContainerandClientsideIOPCDataCallbackinterfacessupportthe‘newstyle’Version2.0connections.
•ThebehavioroftheexistingIOPCAsyncIO,IDataObjectandClientside