FDT技術(shù)介紹-美名軟件內(nèi)部培訓(xùn)資料課件

FDTBasicsFrankSchmid

M&MSoftwareGmbH

+49(0)77249415-29

Frank.Schmid@FDTTechnologyOverview

MotivationVariousStandaloneToolsHARTEngineering/ProgrammingToolEngineering-SystemFDTTechnologyOverview

BasicIdeaDTM(DeviceTypeManager)isa

softwaredriver

deliveredwiththe

device

Standardizedsoftware

interface

Similarideaasa

printdriverFDTTechnologyOverview

ConceptFDTTechnologyOverview

FDT-Plug&WorkHARTFrameApplication(DeviceTypeManagerDTM)HARTFDTTechnologyOverview

DTM-DeviceTypeManagerDeviceDriverForaparticularDeviceorDeviceFamilyCreatedandshippedbyDevicevendorSpec.Features(e.g.FirmwareUpdate)SoftwareProxyforrealDeviceInfoonParameterEditParameter(Online/Offline)Diagonstics,DocumentationIncludingGUIActiveXControlsCorporateDesign(Look&Feel)IntegrateswitheveryFDTContainerDeviceType

ManagerDTMSymbolsORFDTTechnologyOverview

FDTContainerWindowsApplicationDeviceConfigurationToolIntegratedinEngineering-SystemorProcessControlSystemResponsibleforManageDTMCatalog(installedDTMs)EngineeringofTopologyManageDTMlifecycleHostsDTMUserInterfaceDataPersistency(DTM,Topology,...)PrintDocumentationUserManagmentAuditTrailFDTTechnologyOverview

TheSimplestCase:

StandaloneTools(1)CalibrationParameterizationDiagnosisMaintenanceFieldDeviceStandaloneToolFDTTechnologyOverview

TheSimplestCase:

StandaloneTools(2)TypicalUseCases:WorkshopsorsmallinstallationsOnlineconnectiontothedeviceOperationmainlyviatheDTM’sGUIUserhasaccesstoallDTMfunctionality,e.g.byswitchingbetweendifferenttabcardsCurrentconfigurationandparametersarereadfromthedeviceParametersmaybewrittentothedevicee.g.fortestpurposesFDTTechnologyOverview

TheComplexCase:

ControlSystems(2)TypicalUseCases:Different‘Frame

Applications’mayuseaDTMindifferentcontextsAvailabilityofDTMfunctionsiscontrolledaccordingtotheapplicationcontextAllsettingsloadedtothedevicearestoredinasystemdatabaseOnlineconnectiontothedeviceisnotalwaysavailable

DTMworksondatabaseonlyDTMfunctionsarefrequentlyusedinthebackgroundw/ostartingauserdialogDeviceDTMFrameApplicationCommunication

DTMStartDownloadRead/Write

Request

(protocolspecificFDTXML)Read/Write

(comm.hardwarespecific)Read/Write

(fieldbusprotocol

specific)

Handover

Communication

InterfaceRead/WriteResponse

(protocolspecific

FDTXML)FDTTechnologyOverview

CommunicationProfibusDPV1ReadRequest<?xmlversion="1.0"?><FDTxmlns="x-schema:FDTProfibusDPV1CommunicationSchema.xml">

<ReadRequestslot="1"index="16"communicationReference="xyz"/></FDT>

ProfibusDPV1ReadResponse<?xmlversion="1.0"?><FDTxmlns="x-schema:FDTProfibusDPV1CommunicationSchema.xml"> <ReadResponseslot="1"index="16"communicationReference="xyz"

errorCode="0">

<fdt:CommunicationDatabyteArray="68656C6C6F20776F7AB23"/>

</ReadResponse></</FDT>FDTTechnologyOverview

ProfibusXMLExamplesFDTTechnologyOverview

CommunicationusesTunnelingHARTGateway

DTMDevice

DTMDevice

DTMGateway

DTMDPHART-FrameDPHART-FrameIFdtCommunicationIFdtCommunicationIFdtCommunicationCommunication

DTMFrameApplicationCommunication

ChannelCommunicationtounderlyingfieldbussystemisprovidedbyaCommunicationDTMorFrameApplicationChannelSysDPHART-FrameDPSysEthernetTCP/IPFDTTechnologyOverview

CommunicationEachcomponentwrapsthecommunicationframefromthecomponentbelow,WITHOUTknowingthecontentsRoutingthroughsystemtopologyDTMbelowdoesnothaveanyknowledgeaboutthenetworktopologyDTMmustonlysupportitsowncommunicationprotocolCommunication/routingthroughANYnetworktopology,nolimitationsCommunication/routingispossibleeveniftheunderlyingprotocolisunknownbytheengineeringorstandalonetoolFDTTechnologyOverview

ScopeofFDTCore

SpecificationFDTTechnologyOverview

FDT1.2.1ReleasedsinceAugust2005FDT1.2.1=FDT1.2+Addendum+EnhancementsRevisedDocumentStructureDevelopmentHintsmovedtobestpracticedocumentsSeparatedocuments(protocolspecificannex)KeyIssuesVersioningandInteroperability HandlingofDTMspecificFiles DTMandFDTFrameApplicationbehaviorinspecificcasesEnhancedbusscanfunctionalityCommunicationEnhancementsDeviceinitiateddatatransferBlockTypeManager(BTM)HighPerformanceDataAccessDTM/BTMupdateandreplacementFDTTechnologyOverview

DTMStyleGuideGoalsUniformuserguidanceUniformbehaviorofaDTMClearidentificationofdeviceandDTMAllchangesoftheconfigurationaremarkedCleardisplaywhetherdatasetordeviceareaffectedPlausibilitychecksoftheconfigurationonalexical,syntacticalandsemanticalbasisUniforminstallation/de-installation3userinterfacecategoriesStandarduserinterfaceIdentificationareaMenubar(optional)Toolbar(optional)ApplicationareaActionareaStatusbarAdvanceduserinterfaceStandard+navigationareaCompositionuserinterfaceAdvanced+navigationareashowsallapplicationsFDTTechnologyOverview

DTMStyleGuideElementsofstatusbarFDTTechnologyOverview

DTMStyleGuideIconsforstatusinformationandDTMfunctionsFDTTechnologyOverview

DTMStyleGuideGSDDescribesconfiguration(cyclicdata)DD(e.g.EDDL)DescribesallparametersanddependenciesofdeviceLimitedinGUI(usuallytabularviews)Plattform-independent(usesinterpreter)DTMSoftwareProxyofrealdevice(binary)IndividualLook&FeelpossibleIndividualPresentationspossibleIndividualFeaturespossibleFDTTechnologyOverview

DTMvs.DDsDTMsmaysupportofflineconfiguration(engineering)visualizemeasuringvaluesgraphicallysendhealthinfoondevicetovendorinformenduseraboutnewsfromvendor(Internet)updatefirmwaremonitorsignificantdeviceparametertoprovidesuggestionsformaintenanceschedulingplaytrainingvideostosupportmaintenance....(nolimits)FDTTechnologyOverview

DTMisflexibleFDTTechnologyOverview

WaystoaDTMsUniversalDTMHARTCommonPractice/UniversalCommandsPROFIBUSProfilesLimitedinGUIandfeaturesGenerationbasedonDDLimitedinfeaturesQuickresultsIndividualDevelopmentOptimizationforyourspecificneedsE.g.CooporateDesignSemi-automaticGenerationCompanySpecificSolution