-
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
-
ORACLE高可用性(RAC)技术应用解决方案基于成熟的生产环境
ORACLE高可用性(RAC)技术是如何应用于基于成熟的生产环境的一个解决方案美河学习在线基础知识介绍1.RAC是什么,全称,译为“实时应用集群”,是新版数据库中采用的一项新技术,是高可用性的一种,也是数据库支持网格计算环境的核心技术。2.RAC的优缺点优点:主要支持版本,可以支持有效的数据库应用系统,在低成木服务器上构建高可用性数据库系统,并且自由部署应用,无需修改代码。在环境下,集成提供了集群软件和存储管理软件,为用户降低了应用成本。当应用规模需要扩允时,用户可以按需扩展系统,以保证系统的性能。多节点负载均衡提供高可用:故障容错和无缝切换功能,将硬件和软件错误造成的影响最小化通过并行执行技术提高事务响应时间通常用于数据分析系统通过橫冋扩展提髙每秒交易数和连接数通常对于联机事务系统节约硬件成本,可以用多个廉价服务器代替昂贵的小型机或大型机,同时节约相应维护成本可扩展性好,可以方便添加删除节点,扩展硬件资源。缺点相对单机,管理更复杂,要求更高可能会增加软件成本如果使用高配置的服务器,般按照个数收费美河学习在线3. Oracle rac原理在一个应用环境当中,所有的服务器使用和管理同一个数据库,目的是为了分散每一台服务器的工作量,硬件上至少需要两台以上的服务器,而且还需要个共享存储设备。同时所有服务器上的都应该是同一类根据负载均衡的配置策略,当一个客户端发送请求到某一台服务的后,这台服务器根据我们的负载均衡策略,公把请求发送给本机的组件处理也可能公发送给另外一台服务器的组件处理,处理完请求后,会通过集群软件来访问共享存储设备逻辑结构上看:每一个参加集群的节点有一个独立的访问同一个数据库。每一个节点的都有自己的每一个节点的都有自己的每个节点的都有自己的每一个节点的都有白己的表空间。所有节点都共享一份和三类虚拟地址集群注册文件记录每个节点的相关信息仲裁机制用于仲裁多个节点向共享节点同时写的行为,这样做是为了避免发生冲突。美河学习在线存储技术介绍独立冗余磁盘阵列(是一种把多块独立的硬盘(物理硬盘)按不同的方式组合起来形成一个硬盘组(逻辑硬盘),从而提供比单个硬盘更高的存储性能与数据备份能力的技术。特色是玦硬盘冋时读取速度加快及提供容错性可以将分为不同级別,级別并不代表技术高低,选择哪一种产品纯视用户的操作环境及应用而定,与级别高低没有必然关系。:无差错控制的带区组RAID OBDFGHMNO etc要实现必须要有两个以上硬盘驱动器,数据并不是保存在一个硬盘上,而是分成数据块保存在不同驱动器上。因为将数据分布在不冋驱动器上,所以数据吞吐率大大提高,驱动器的负载也比较平衡。它的缺点是它没有数据差错控制,如果一个驱动器中的数据发生错误,即使其它盘上的数据正确也无济于事了。不应该将它用于对数据稳定性要求高的场合。在所有的级别中,的速度是最快的。但是没冇冗余功能的,如果…个磁盘(物理)损坏,则所有的数据都无法使用美河学习在线:镜象结构RAID 1B-BGG0DDHH对于使用这种结构的设备来说控制器必须能够同时对两个盘进行读操作和对两个镜象盘进行写操作。镜象结构是在一组盘岀现问题时,可以使用镜象磁盘,提高系统的容错能力。每读一次盘只能读岀一块数据,也就是说数据块传送速率与单独的盘的读取速率相同。当您的系统需要极高的可靠性时,如进行数据统计,那么使用比较合适。而且技术支持“热替换”,即不断电的情况下对故障磁盘进行更换,更换完毕只要从镜像盘上恢复数据即可。当主硬盘损坏时,镜像硬盘就可以代替主硬盘工作。镜像硬盘相当于一个备份盘,这种硬盘模式的安全性是非常高的,的数据安全性在所有的级别上来说是最好的。但是其磁盐的利用率却只有是所有级别中最低的。:分布式奇偶校验的独立磁盘结构RAID 5A Blocks B Blocks C Blocks D Blocks E BlocksA0 Co D0 parityParitGenerationA1B1(A2 B2arity D2 E2A3 3 parity C3 E34p(B4(40(E4将数据分散存放于多个硬盘上面,同时使用一定的编码技术产生奇偶校验码来提供错误检査及恢复能力,数据段的校验位交互存放于各个硬盘上。因为奇偶校验码在不同的磁盘上,所以提高∫可靠性,允许单个磁盘出错。任何一个硬盘损坏,都可以根据其它硬盘上的校验美河学习在线位来重建损坏的数据。硬盘的利用率为。优点是提供了冗余性(支持一块盘掉线后仍然正常运行),磁盘空间利用率较高(),读写速度较快(倍)。是级别中最常见的一个类型:高可靠性与高效磁盘结构RAID 10BBBDFHmIrroringstriping这种结构是一个带区结构加一个镜象结构,因为两种结构各有优缺点,因此可以相互补允,达到既高效又高速还可以互为镜像的目的。大家可以结合两种结构的优点和缺点来理解这种新结构。这种新结构的价格高,可扩充性不好。主要用于容量不大,但要求速度和差错控制的数据库中。RAID10是先镜射再分区数据。是将所有硬盘分为两组,然后将这两组各自视为RAID1运作。RAID10有着不错的读取速度,而且拥有比RAID0更高的数据保护性。美河学习在线系统结构设计1.RAC系统拓扑结构基本如下图所示:核心交换机SUNT44数据库raNT4/4数据库rac2面出HSUNSANRAC心跳RAC心跳EMC VNX 5300美河学习在线2.主机操作系统系统数据库服务器系统规划用户组规划说明0 racle清单和软件所有者Oracle自动存储管理组ASM数据库管理员组ASM操作员组数据库管理员用户规划说明默认口令用户数据管理员主机文件系统规划物理硬盘数文件系统AD方式「挂载点文件系统大小/homeufs70GB8水300GB(文件系统用300Gswapswap30GBuf200GB美河学习在线3.存储规划存储一般采用存储方式。硬盘总物理大RAID方逻辑大小(可用 Hotspare数式空间大小)15TB存储组件/BokASMIib NameSizeComments系统路径Device/dev/sda OCR VOL1100G OCR and Voting /dev/oraclOCR/dev/sdb OCR VOL2100GDiskseasm/ORCdev oracl数据文件|/dev/ sdb DATA VOLL3T ASM Data Diskgroup easm/DATAVOIASM/dev/orac l文件备份/dev/ sdaBACK VOL11.8T RecoveryBackup easm/BACKDiskgrou备注存储暂用4.数据库RAC环境数据库规划环境信息节点名称实例名称处理器内存操作系统数据库版本软件组件软件组件名称用户主组辅组用户目录基目录
- 2020-12-03下载
- 积分：1
-
房屋租赁合同(常用版)，租房合同 模板
房屋租赁合同，房屋租赁合同(常用版)，租房合同 模板
- 2021-05-06下载
- 积分：1
-
gps，电子罗盘串口通讯
gps和电子罗盘窗口串口通讯，数据接收和处理
- 2020-12-08下载
- 积分：1
-
图像下采样算法
实现图像、影像下采样，采样方法有最邻近采样法、二次插值法、双三次卷积法。matlab实现。
- 2020-11-29下载
- 积分：1
-
3种模板匹配法实现的手写数字识别示例
3种模板匹配法实现的手写数字识别示例3种模板匹配法实现的手写数字识别示例3种模板匹配法实现的手写数字识别示例
- 2020-12-02下载
- 积分：1
-
新闻发布系统
新闻发布系统，能够进行新闻的发布功能，实现简单页面的布局，对新闻能够进行增加，删除，更改和查询
- 2020-12-06下载
- 积分：1
-
.Net WebAPi JWT身份验证
.NetFrameWork 4.6.2 WebAPI 实现JWT身份验证，简单的Demo程序
- 2021-05-06下载
- 积分：1
-
Invest介绍
了解模型的每一个模块，掌握每一个模型所需要的数据，很好的使用invest 模型
- 2020-12-05下载
- 积分：1
-
MCP3421电压采集
MCP3421使用STM32实现电压采集，可以选择多种模式。
- 2020-12-10下载
- 积分：1
