CLICKHERETO DOWNLOAD
TheBrowseNameisofDataTypeQualifiedName,containingaNamespaceIndexandaStringTheOpenPlatformCommunicationsUnitedArchitecture(OPC UA)isadataexchangestandardusedinindustrialautomationandcommunication.OPCUAprovidesaframeworkforinteroperabilitytobeusedIntheData ManagerGroupsscreensection(lowerlefthandsideofthescreen),right-clickyourmouseandselectAddGroupfromthedisplayedmenuOPCUAisan independentstandardwithnorelationtoaspecificsystemormanufacturerPartpresentstheconceptsandoverviewoftheOPCUnifiedArchitecture(OPCUA) ReadingthisdocumentishelpfultounderstandtheremainingPartsofthismulti-partdocumentsetIntheGroupNamefield,typegroup1andclickOKOptimized, robustandfault-tolerantprotocolwithintegratedsecuritymechanismsDescriptionofwhatOPCUAisandwhatitcanaccomplishItcommunicatesbyPC-tomachinecommunicationormachine-to-machinecommunicationOPCUnifiedArchitecture(OPCUA)isthenewstandardspecificationforinterconnectivityin state-of-the-artindustrialautomationtechnology,enablingrichinformationmodelingcapabilities,replacingexistingOPCspecifications.TheAddDataManager Groupwindow(Figure)appears.ExplainshowtomigratefromOPCtoOPCUA.ForIT-architects,developers,projectmanagers,OPCissimplycalledOpen ConnectivityviaOpenStandardstodayOPCUAdefinestwoattributescontainingnaminginformationaboutanOPCUANode,theBrowseNameandthe DisplayNameIncludessupplementarymaterial:AccessesExplainshowtomigratefromOPCtoOPCUAForIT-architects,developers,projectmanagers, engineers,andsystemadministratorsOPCleveragedMicrosoft’sCOMtechnologyforquitesometimeInformationcanbedescribedusingobject-oriented means1ScopeSinceOPCUAOPCUnifiedArchitecture(OPCUA)isthenewstandardspecificationforinterconnectivityinstate-of-the-artindustrial automationtechnology,enablingrichinformationmodeling1ScopeFigureAddDataManagerGroupWindowItreadsdataandcommands,andwritesdataback toMicrosoftExcelTheTherearethreetypesofevents:simple,tracking,andcondition.RecommendationsforDisplayNamewillbegiveninalaterversionofthis documentOldOPCUAServerswilljustnotprovidethose,andnewOPCUAClientswillnotexpectthemtobeavailableinallOPCUAServers,sincetheyare optionalItwasthebasisforAlarm&EventsMatrikonOPC–IntroductiontoOPCTutorialMatrikonOPCExploreractsasthedatasinkEachoftheotherparts isbrieflyexplainedalongwithasuggestedreadingorderAuthors:MatthiasDamm,Stefan-HelmutLeitner,WolfgangMahnkePartpresentstheconceptsand overviewoftheOPCUnifiedArchitecture(OPCUA)ReadingthisdocumentishelpfultounderstandtheremainingPartsofthismulti-partOPCUAisplatformindependentandcanusedifferentprotocolsasacommunicationmediumThethreetypesofeventsasdefinedbytheOPCAlarmsandEventsspecificationare showninFigureTheconditionThispaperfirstintroducesthemainideabehindOPC,showswhyOPCisdifferentfromconventional(oftenproprietary) communicationprotocols,andexplainshowOPChelpsovercomethelimitationsofsuchnativeprotocolsNamingConventionsforNodes.Thisfunctionality simplifiesaccessanddataexchangeofproductsfromanotherWolfgangMahnkeDescriptionofwhatOPCUAisandwhatitcanaccomplishAlltheOPC informationisintegratedinanamespace,forexampledataandalarms