UDS诊断程序，整车网络测试应用程序（PCAN-UDS API – User Manual.pdf）
UDS_PCAN_APIA应用程序，整车网络诊断应用程序，超值！（PEAK CAN UDS Application Programming InterfaceUser Manual.pdf）PCAN-UDS APi- User ManualContents1 PCAN-UDS API Documentation2 Introduction2.1 Understanding PCAN-UDS2.2 Using PCAN-UDS2.3 Features7888992.4 System Requi rements2.5 Scope of supply3 DLL API Reference3.1 Namespaces103.1.1 Peak Can uds3.2 Units3.21 PuDs Unit3.3 Classes3.3.1 UDSApi3.3.2 TUDSApi3. 4 structures1022334553.4.1 TPUDSMsg3.4.2 TPUDSSessionInfo3.43 TPUDSNetAddrinfo3.5 Types213.5.1 TPUDSCANHand]e223.5.2 TPUDSstatus233.5.3 TPUDSBaudrate253.5.4 TPUDSHWType283.5.5 TPUDSResult303.5.6 TPUDSParameter313.5.7 TPUDSService393.5.8 TPUDSAddress423.5.9 TPUDSCanId443.5.10 TPUDSProtoco l463.5.11 TPUDSAddressingType483.5.12 TPUDSMessageType493.5.13 TPUDSSVCParamDSC503.5.14 TPUDSSVCParamER513.5.15 TPUDSSVCParamcc533.5.16 TPUDSSVCParamTP543.5.17 TPUDSSVCParamcdTCS543.5.18 TPUDSSvCParamROE553.5.19 TPUDSSvCParamROERe commendedserviceID573.5.20 TPUDSSVCParamLC583.5.21 TPUDSSvcParamLCBaudrateidentifier593.5.22 TPUDSSVCParamDI603.5.23 TPUDSSVCParamRDBPI643.5.24 TPUDSSVCParamDDDI653,525 TPUDSSyCParamRDTCI66PCAN-UDS APi- User Manual3.5.26 TPUDSSVCParamRDTCI DTCSVM6935.27 TPUDSSYCParamIOCBI703.5.28 TPUDSSvCParamRC3.5.29 TPUDSSVCParaMRC RID723.6 Methods733.6.1 Initialize753.6.2 Initialize(TpudsCanhandle, tpudsbaudrate)3.6.3 Initialize(TPUdsCANhandle, TPUdSBaudrate, TPudSHWType, UInt32,UInt16)83.6.4 Uninitialize813.6.5 Setvalue843.6.6 Setvalue (TPUdsCanhandle, tpudsparameter, UInt32, uint32)843.6Setvalue (TPUdSCaNHandle, TPUDSParameter, stringBufferUint32)873.6.8 Setvalue (TPUDSANHandle, TPUDSParameter, Byte[], Uint32)883.6.9 Setvalue(Tpudscanhand le, tpudsparameter, IntPtr, UInt32)3.6.10 Getvalue933.6.11 Getvalue (TPUDSCANHandle, TPUDSParameter, StringBufferUint32)933.6. 12 Getvalue (TPUDSCANHandle, tpudsparameter, uint32, Uint32)963.6.13 Getvalue (TPUDsCaNHandle, TPUDSParameter, Byte l], UInt32)993.6. 14 Getvalue (TPUdSCAnhandle, tpudSParameter, Intptr, UInt32)1013.6.15 Getstatus1043.6.16Read1073.6.17 Write3.6.18 Reset1143.6.19 WaitForsing lemessage1163. 6.20 WaitFormultiplemessage1203.6.21 Waitforseryice1263.6.22 WaitForservicefunctional1303.6.23 ProcessResponse1333.6. 24 SvCDiagnosticsessioncontro l1383.6.25 SVCECUReset1413.6.26 SvcSecuri tyAccess1453.6.27 SvCCommunicationControl1483.6.28 SvcTesterpresent1523.6.29 SvcsecuredDataTransmission1553.6.30 SvcControlDTCSetting1583.6.31 SvcResponseonEvent1623.6.32 SVCLinkcontrol1663.6.33 SVCReaddatabyidentifier1703.6. 34 SvcReadMemory ByAddress1733.6.35 SvcReadscal ingdatabyidentifier1773.6. 36 SvcReadDataByperiodicIdentifier1803.6.37 SvcDynamicallydefinedataIdentifierDBID1843.6.38 SvcDynamicall ydefineDataIdentifierDBMA1883.6. 39 SvcDynamical lyDefineDataIdentifierCDDDI1933.6.40 SvcWri teDataByidentifier1973.6. 41 Svcwri teMemory byaddress2003.6.42 SvcClearDi agnosticInformation2053. 6. 43 SVCReadDTCInformation2083.6.44 SvCReadDTCInformationRDTCSSBDTC2113. 6. 45 SvCReaddTCInformationRDTCSSBRN215PCAN-UDS APi- User Manual3. 6.46 SVcReadDTCInformationReportExtended2183.6. 47 SvcReadDTCInformationReportseverity2213,648 SvcReaddTCInformationrsIodtc2253. 6.49 SvCReadDTCInformationNoParam2283.6.50 SvcInputout put contro byidentifier2323. 6.51 SyCRoutineControl2363.6.52 SvCReques tOwn load2393.6.53 SvcRequestUp load2433. 6.54 SVCTransferData2483.6.55 SvCRequestTransferExit2513.7 Functions2563.7.1 UDS Initialize2583.7.2 UDs Uninitialize2593.7.3 UDs Setvalue2603.7.4 UDs Getvalue2613.7.5 UDS Getstatus2623.7.6 UDS Read2643.7.7 UDs Write2653.7.8 UDs Reset2663.7.9 UDS_WaitForsinglemessage2673.7.10 UDS_waitForMultipleMessage2693.7.11 UDs Wai ce2723.7.12 UDS WaitForserviceFunctional2733.7.13 UDS_ Processresponse2753.7.14 UDS_SvcDiagnosticSessionControl2773.7.15 UDS SVCECUReset2783.7.16 DS_SVCSecuri tyAccess2803.7.17 UDS SVCCommunicationcontrol2813.7.18 UDs SvCTesterpresent2833719 UDS SvCSecuredDatatransmission2843.7.20 UDS_SvCControlDTCSetting2863.7.21 UDS_SVCResponseonEvent2873,7.22 UDs SVCLinkcontrol2893.7.23 UDS_SvcReaddatabyidentifier2913.7.24 UDS_SvcReadMemory byAddress2923.7.25 uDs_ SvcReadscalingdatabyidentifier2943.7.26 UDS_SvCReadDataBy Periodi iDentifier2953.7. 27 UDS_SVcDynamical l yDefineDataIdentifierDBID2973.7.28 UDS_SvcDynami call ydefinedataIdentifierDBMa2993.7.29 UDS_SvcDynami cal l yDefineDataIdentifierCDDDI3013. 7.30 UDS_SvcWriteDataByIdentifier3023,7.31 UDs SvcWri teMemorybyaddress3033.7. UDS_SvcClearDiagnosticInformation3053.7.33 UDS SVCReadDTCInformation3073.7. UDs SyCReadDTCInformationRdtCSSBDTC3093.7.35 uDs SvCReadDTCInformationRdtcssbrn3103.7.36 UDS_ SvCReadDTCInformationReportExtended3113.7.37 UDS_SvcReadDTCInformationReportseverity3133.7.38 UDS SVCReadDTCInformationRSIODTC3153,739 UDS SVCReadDTCInformationNoParam3163. 7.40 UDS_SvcInputoutput contro l byIdentifier3,7. 41 UDs SyCRoutinecontrol319PCAN-UDS APi- User Manual3.7.42 UDS_SvcRequestDown load3213.7.43 UDS_ SVCRequestupload32337.44 UDS SyCTransferData3253.7.45 UDS_SVCRequestTransferExit3263.8 Definitions3293.8.1 PCAN-UDS Handle Definitions3293.8.2 Parameter value defintions3313.8.3 TPUDSMsg Member value Definitions3323.8.4 PCAN-UDs Service parameter Definitions3334 Additional Information3354.1 PCAn Fundamentals33542 PCAN-Basic3364.3 UDS and ISO-TP Network Addressing Information3384.3.1 ISO-TP network addressing format3384.4 USing Events3405 License Information3426PCAN-UDS APi- User Manual1 PCAn-UDS APi DocumentationWelcome to the documentation of PCan-UD APl, a PEAK CAN API that implements ISo 15765-3, UDS in CANan international standard that allows a diagnostic tester(client) to control diagnostic functions in an on-vehicleElectronic Control Unit(ECU or serveIn the following chapters you will find all the information needed to take advantage of this aPlIntroduction on page 8DLL API Reference on page 10Additional Information on page 335PCAN-UDS APi- User Manual2 IntroductionPCAN-UDS is a simple programming interface intended to support windows automotive applications that usePEAK-Hardware to communicate with Electronic Control Units(ECU) connected to the bus systems of a car, formaintenance purpose2.1 Understanding PCAN-UDSUDS stands for Unified Diagnostic Services and is a communication protocol of the automotive industry. thisprotocol is described in the norm iSo 14229-1The UDS protocol is the result of 3 other standardized diagnostic communication protocolsIS0 14230-3, as known as Keyword 2000 Protocol(KWP2000L IS0 15765-3, as known as diagnostic on CANISo 15765-2, as known as ISo-TPThe idea of this protocol is to contact all electronic data units installed andCAN OBDninterconnected in a car, in order to provide maintenance, as checking for errors,actualizing of firmware, etcUDS is a Client/Server oriented protocol. In a UDS session(diagnostic session ),aprogram application on a computer constitutes the client(within UDS, it is calledPCAN-UDSTester), the server is the ecu being tested and the diagnostic requests from client toserver are called services. The client always starts with a request and this ends with apositive or negative response from the server(ECuSince the transport protocol of UDS is done using ISo-TP, an international standardPCAN ISOTPfor sending data packets over a CAN Bus, the maximum data length that can betransmitted in a single data-block is 4095 bytes.PCAN-UDS API is an implementation of the Uds on CAN standard the physicalcommunication is carried out by PCAN-Hardware (PCAN-USB, PCAN-PCI etc )throughPCAN-Basithe pCAN-ISo-TP and PCAN-Basic API (free CAN APls from PEAK-System). Because ofthis it is necessary to have also the pCAN-1S0-tP and PCAN-Basic APls(PCAN-ISO-TP. dll and PCAN Basic. dll) present on the working computer where UdS is intended tobe used. PCAN-UDS, PCAN-ISO-TP and PCan-Basic apis are free and available for allFigure 1: Relationship of thepeople that acquire a pCAn-hardware2.2 Using PCAN-UDSSince PCAN-UDS API is built on top of the PCAN-1So-TP API and PCAN-Basic APls, it shares similar functions. Itoffers the possibility to use several PCAn-UDS (PUds) channels within the same application in an easy way. Thecommunication process is divided in 3 phases: initialization interaction and finalization of a puds-channelInitialization In order to do UDS on CAN communication using a channel, it is necessary to initialize it first. Thisis done by making a call to the function UDS_ Initialize (class- method: InitializePCAN-UDS APi- User ManualInteraction: After a successful initialization a channel is ready to communicate with the connected can bus.Further configuration is not needed the 24 functions starting with UDS Svc(class-methods: starting with Svccan be used to transmit UdS requests and the utility functions starting with Uds WaitFor(class- methodsstarting with WaitFor) are used to retrieve the results of a previous request. the Uds read and UDS Write(class-methods: Read and Write are lower level functions to read and write UDs messages from scratch. Ifdesired, extra configuration can be made to improve a communication session, like service request timeouts orISo-TP parametersFinalization: When the communication is finished, the function UDS_ Uninitialize(class-method: Uninitializeshould be called in order to release the puds-channel and the resources allocated for it. In this way thechannel is marked as free"and can be used from other applications23 FeaturesI mplementation of the UDS protocol(iSo 14229-1)for the communication with control unitsWindows DLLs for the development of 32-bit and 64-bit applicationsPhysical communication via Can using a Can interface of the pcan seriesUses the pcan-Basic programming interface to access the can hardware in the computerUses the pCAn-ISo-TP programming interface(iso 15765-2)for the transfer of data packages up to 4095bytes via the can bus2.4 System Requi rementsL- Windows 10, 8.1, 7(32/64-bitAt least 512 Mb ram and 1 GHz CPUPC CAN interface from peak-SystemPCAN-Basic APlL PCAN-SO-TP API2.5 Scope of supplyInterface DLL, examples, and header files for all common programming languagesDocumentation in pdf formatDocumentation in HTML Help formatPCAN-UDS APi- User Manual3 DLL API ReferenceThis section contains information about the data types (classes, structures, types, defines enumerations)andAPI functions which are contained in the pcan-uds api3.1 NamespacesPEAK offers the implementation of some specific programming interfaces as namespaces for the. NEtFramework programming environment. The following namespaces are available:NamespacesNameDescription}PeakContains all namespaces that are part of the managed programming environment fromPEAK-SystemPeak CanContains types and classes for using the PCan aPi from PEAK-SystemPeak Can. LightContains types and classes for using the PCAn-Light API from PEAK-SystemPeak Can basicContains types and classes for using the pcan-Basic APl from PEAK-SystemPeak Can CcpContains types and classes for using the CCP API implementation from PEAK-SystemPeak Can XcpContains types and classes for using the XcP aPi implementation from PEAK-SystemPeak Can. Iso TpContains types and classes for using the pCAN-IS0-TP aPl implementation from PEAKSystelPeak Can, UdsContains types and classes for using the PCan-UDS API implementation from PEAK-SystemPeakCan.Obdll Contains types and classes for using the PCAN-OBDIll API implementation from PEAKSystemt}Peak. LinContains types and classes used to handle with lin devices from PEAK-Systemt}Peak. RP1210AContains types and classes used to handle with can devices from PEak-System through theTMC Recommended Practices 1210, version A, as known as RP1210(A3.1.1 Peak Can UdsThe peak Can. Uds namespace contains types and classes to use the pcan-UdS aPi within the. NET Frameworkprogramming environment and handle pcan devices from peak-SystemRemarks: Under the delphi environment, these elements are enclosed in the puds-Unit. the functionality of allelements included here is just the same. the difference between this namespace and the delphi unit consists inthe fact that delphi accesses the Windows api directly it is not managed code)AliasesAliasDescriptionTPUDSCANHandle Represents a pCAn-UDS channel handleClassesClassDescription像曰UDSApiDefines a class which represents the PCAN-UDS API10
- 2020-06-27下载
- 积分：1
CANOpen应用层和通讯协议（CiA301）
CANOpen应用层和通讯协议，基于CiA301的中文翻译，整理好了书签，学习CANopen必备资料。CANopen应用层和通信协议目录1适用范围2参考资料2.规范性引用2.2信息参考3缩写和定义·非·垂8888831缩写3.2定义…标准帧扩展帧.999CAN-工DCOB-ID·········实体FSA,,,设备域9逻辑设备,++Node-ID+++++,.,+·+···对象9虚拟设备建模…104.1设备域模型104.2通信参考模型.4.2.1简述14.2.2 CANopen应用层………….114.2.2.1概述··::············::··114.2.22服务原语1142.2.3应用层服务124.3 CANopen设备模型43.1简述..124.4通信协议分类··;·······∴134.4.1简述4.4.2主/从协议6··134.4.3客户端/服务器协议1444.4生产者/消费者协议-推/拉模式144.45对象字典网络系统模型1545.1设备协议154.5.2应用协议155物理层5.1OS参考模型.∴…16介质相关接口53物理介质连接.54物理信令…166数据链路层186.1简述…∴186.2AN帧类型·4···:·;··4·44···.···:·4·4·4··4··+∴187应用层.197.1数据类型和编码规则..197.1.1数据类型和编码规则简述.19⊙CA2011-保留所有权利CANopen应用层和通信协议7.1.2数据类型定X位序207.1.3位序列7.1.3.1位序列定义7.1.3.2位序列的传输语法……207.1.4基本数据类型217.1.4.1简述217.1.4.27.1,4.3 Boolean.……7.1.4.4Void.7.1. 4.5 Unsigned interge222222111127.1.4.6 Signed Integer....7.1.4.7浮点数.··+·“·4·“··+:···;4······+······7.1.5复合数据类型237.1.6扩展数据类型7.1.6.1简述7.1.6.2八进制字符…27.1.6.3可显示字符串7.1.6.4 Unicode字符串7.1.6.5时间2223444247.1.6.6时间差.47.1.6.7域247.2通信对象247.2.1简述247.2.2过程数据对象(PDO).257.2.2.1简述257.2.2.2传输模式267.2.2.3触发模式.….267.2.2.4PD0服务7.2.2.5PD0协议287.2.3寻址PD0MPD0)7.2.3.1简述.287.2.3.2MPD0寻址模式297.2.3.3PD0服务297.2.3.4MD0协议307.2.4服务数据对象(SD)7.2.4.1简述317.2.4.2SD0服务7.2.4.3S00协议…43服务器49服务器49客户端服务器.…537.25同步对象(SYNC)597.2.5.1简述597.2.5.2SYNC服务597.2.5.3同步协议…7.2.6时间戳对象(TIME)7.2.6.1简述607.2.6.2TIME服务607.2.6.3TIME协议和“……………617.2.7应急对象(EMCY617.2.7.1应急对象的使用617.2.7.2应急的对象服务…ccⅰA2011-保留所有权利CANopen应用层和通信协议7.2.7.3应急对象协议…1547.28网络管理···.·:4·········7.2.8.1简述7.2.8.2NM服务7.2.8.3NMT协议6973网络初始化和系统 boot-up∴747.3.1简化的MMT启动∴747.3.2NT状态机.757.3.2.1概述7.3.2.2MMT状态767.3.2.3MT状态转换7.3.3通用预定义连接集7.3.4特定预定义连接集…787.3.5受限CAN-IDs7974对象字典7.4.1常规结构·++·“+“797.42索引和子索引的使用.807.4.3对象代码的使用7.4.4数据类型的使用.817.4.5访问权限的使用∴817.4.6类别和条目类别的使用.7.4.7数据类型条目的使用827.4.7.1简述7.4.7.2对象字典条目的组织结构7.4.8预定义复合数据类型规范7.4.8.1PD0通讯参数记录规格847.4.8.2PD0映射参数记录规格7.4.8.3SD0参数记录规格857.4.8.4身份记录规格857.4.8.50S调试记录规格.857.4.8.60S命令记录规格通信协议规范867.51对象及其条目说明规范∴867.5.2通信协议对象的详细规范877.5.2.1对象1000:设备类型1877.5.2.2对象1001h:错误寄存器7.5.2.3对象10021:制造商状态寄存器7.5.24对象1003:预定义错误域897.5.2.5对象1005:COB-ID同步消息∴917.5.2.6对象1006:通信循环周期.927.5.27对象1007:同步窗长度.927.5.28对象1008:制造商设备名称7.5.2.9对象1009:制造商的硬件版本937.5.2.10对象100A1:制造商软件版本947.5.2.11对象1000:监护周期947.5.2.12对象100D:生存周期因子7.5.2.13对象1010:保存参数957.5.2.14对象1011:恢复缺省参数977.5.2.15对象10121:时间戳对象COB-ID1007.5.2.16对象1013:高分辨率时间戳1017.5.2.17对象1014: EMCY COB-ID1017.5.2.18对象1015:EMCY抑制时间.1027.5.2.19对象1016:消费者心跳超时.103⊙CA2011-保留所有权利CANopen应用层和通信协议7.52.20对象1017:生产者心跳超时………1047.5.221对象1018:对象身份1057.5.2.22对象1019:同步计数器溢出值7.5.2.23对象1020:验证配置1077.5.2.24对象1021:存储EDS1087.5.2.25对象1022:存储格式1097.5.2.26对象1023:0S命令7.5.2.27对象1024:0s命令模式…·;·中1117.5.2.28对象10251:0s调试接口.1127.5.2.29对象1026:0S提示符命令接口.1137.5.2.30对象1027:模块列表1147.5.231对象1028:应急消费对象7.5.2.32对象1029:错误行为对象.1177.5.2.33对象1200127F:SD0服务器参数1187.5.234对象128012F:SD0客户端参数.1217.5.235对象1400~15FF1:RPD0通信参数1237.5.2.36对象160017FF:RPD0映射参数.1267.5.2.37对象180019FB:TPD0通信参数1297.5.238对象1A00"1BF:TPD0映射参数1347.5.2.39对象1FA011FCF:对像扫描仪列表1367.5.2.40对象1FD0^1FFR:对象分配列表…138附件A(更多信息)140注译版木记录142CA2011-保留所有权利CANopen应用层和通信协议1适用范围本规范定义了 CANopen应用层。包括数据类型、编码规则、对象字典以及 CANopen通信服务协议。此外,本规范也定义了 CANopen网络管理服务协议本规范规定了 CANopen通信协议,例如物理层、通信对象标识符预定义连接集、应急对象( Emergency)、时间戳和同步通笮对象⊙CA2011-保留所有权利CANopen应用层和通信协议2参考资料2.1规范性引用/EN61131-3EN61131-3,可编程控制器一一第3部分:编程语言/IS07498-1/IS07498-1,信息技术-开放系统互连-基本参考模型:基本模型/IS08859/IS08859,信息技术——8位单字节编码图形字符集ISol!898-1/Is011898-1,道路车辆—控制器区域网络(CAN)——第1部分:数据链路层和物理信令/IS0ll898-2/IS0118982,道路车辆——控制器区域网络(CAN)—一第2部分:高速介质访问单元/IS01l8983ⅠS0118983,道路车辆——控制器区域网络CAN——第3部分:低速度、容错的介质相关接口。/IS010646/IS010646,信息技术通用多八位编码字符集(LCS)2.2信息参考/IEEE754/TEEE754,标准的二进制的浮点运算/IEC62390IEC TR62390,常规的白动化设备一协议的准则3缩写和定义3.1缩写ARQ自动重复请求CAN控制局域网CAN IDCAN标识符COB通信对象COB-IDCOB标识符CRC循环冗余校验CSDOClicnt-SDODAM目的地址模式FSA有限状态机LLO逻辑链路控尙LSB最低位/字节MAC介质访问控制MDI介质相关接口MPDO多路复用PD0MSB最高位/字节网络管理NODE-ID节点标识符OSI开放系统互连PDO过程数据对象PLS物理层的信令ccⅰA2011-保留所有权利CANopen应用层和通信协议PMA物理介质连接RPDO接收PDORTR远程传输请求SAM源地址模式SDO服务数据对象SSDOServer-SDoSYNC同步对象TPDO发送PDO3.2定义标准帧/IS01898-1/屮定义的最多可包含8个字节数据和11位标识符的消息扩展帧/IS011898-1/中定义最多可包含8个字节数据和29位标识符的消息CAN-ID/IS011898-1/中定义的CAN数据和远程帧标识符COB-ID包含CAN-1D和附加控制位的标识符实体特指事物如人、地点、过程、概念、组织或事件FSA若干计算行为组成的模式作为一个状态,一个启动状态,输入一个字母,映射输入符号和当前状态到下一状态的转换功能:以一个宁符串输入作为启动状态的计算起始;依赖传递函数变换到新状态(译者注:无法按字面翻译,译者定义为表示有限个状态以及在这些状态之间的转移和动作等行为的数学模型,即有限状态机)。设备域1.自动化系统中独立联网的物理实体,在特定的上下文和分隔符中使用自身接口执行指定的功能2.在自动化系统中向其他实体扶行控制、操纵和/或传感功能和相关接口的实体。逻辑设备根据改备域模型所组织的一系列对象和行为,描述了该设备的数据和行为使网络所理解Node-ID网络范围内每个 CANopen设备的独特标识对象封装了状态和行为有明确界限和身份的实体虚拟设备能够像域设备一样完成所属功能事件的软件实体,⊙CA2011-保留所有权利9CANopen应用层和通信协议4建模4.1设备域模型如图1所示,设备域至少包含一个 CANopen设备。其中每个 CANopen设备至少带有一个包含数据链路层(见本章第6节)和物理层(见本章第5节)的网络接凵、一个node-1D、至少一种通信状态机(FSA)。通信状态机不仅带有NMT从状态机(见7.3.2),还包括应急状态机(见7.27)等共他附加状态机。这些附加状态机定义于所谓的框架协议内,不属于本协议范围。一个 CANopen设备至少包含一个多至8个逻辑设备,且不可分割于多个设备域。每个逻辑设备可包含一个逻辑设备状态机(可选)和多个虚拟设备。逻辑设备不可分割于多个 CANopen设备。逻辑设备定义于所谓的设备协议中(见4.5.1),不在本协议的范围内。每个虚拟设备包含一个虚拟设备状态机且不可分割于多个逻辑设备。虚拟改备定义于所请的应用协议(请参阅子句452),不在本协议范围内。设备域的最小化结构如图2所示。Field deviceCANopen device (Node-ID)CANopen device (Node-ID)CommunicationCommunicationCommunicationCommunicationFSA●●FSAFSAFSA1st logical device1st logical deviceLogical deviceLogical deviceLogical deviceLogical device●自FSAFSAFSAFSAVirtual deviceVirtual deviceVirtual deviceVirtual deviceDevice●●DeviceDevice●●●DeviceFSAFSAFSAFSA8th logical device8th logical deviceLogical device●●Logical devicLogical device@●●Logical deviceFSAFSAFSAFSAVirtual deviceVirtual deviceVirtual deviceVirtual deviceDevice鲁●●DeviceDeviceDeviceFSAFSAFSAFSA图1:设备域模型ccⅰA2011-保留所有权利
- 2020-12-04下载
- 积分：1
