自动驾驶系列报告一---综合篇
自动驾驶产业格局、自动驾驶解决方案、自动驾驶芯片、传感器、车联网国金证券SINOLINKSECURITIES行业深度研究图表年加州报告披露路测成绩图表:与克莱斯勒合作车辆及其硬件系统图表发展历程图表:百度平台技术框架图表:百度计划成员单位图表:百度划成员单位图表:百度十划成员单位(按产业链分部分)图表:特斯拉功能图表:奧迪自动驾驶传感器系统图表:特斯拉奥迪图表:自动驾驶芯片主要产品性能图表:未来专用计算平台将成为主流图表系列图表计算平台图表:地平线“征程”自动驾驶芯片图表:各类传感器特点图表:激光雷达原理图表:激光雷达效果图表:激光雷达优缺点图表产品信息图表:新128线激光雷达图表激光雷达芯片图表激光雷达生产线图表:国内主要激光雷达产品信息图表调制亳米波雷达原理图表:毫米波需达类别图表:毫米波雷达优缺点图表:行易道毫米波雷达参数图表:承泰科技毫米波雷达应用图表:苏州豪米波产品基本信息图表:纳雷科技产品基本信息图表:摄像头优缺点图表:车载摄像头产业链图表年全球市场占比图表:舜宇光学车载镜头出货量图表:舜宇光学车载镜头出货量增长率图表:舜宇光学年出货量图表:欧菲科技智能汽车业务收入图表:车联网的应用敬请参阅最后一页特别声明国金证券SINOLINKSECURITIES行业深度研究图表:车联网供应链架构图表:车联网发展趋势图表:我国车联网市场规模(亿美元)图表:三旗通信车联网产品图表:三旗通信合作伙伴图表:英卡科技服务结构图图表系列无线数据记录仪图表卫星定位汽车行驶记录仪图表系统图表系统图表:四维图新“趣驾”系统图表在车联网构架上是核心环节图表:奔驰年新一代车载信息终端系统图表系统的盈利模式图表系统总附加值拆解图表:全球从事系统主要企业图表:国外主要汽车企业所用的系统图表:国内从事系统主要企业图表:国内主要汽车企业所用的系统图表前装和后装市场规模测算(亿元)图表:公司系统分类及主营产品图表:驾驶员控制系统图表:智能车联电子系统图表:华阳集团产品图表:车载信息娱乐系统图表:显示模组与系统图表:高精地图与普通导航电子地图的区别图表:高精地图与普通导航电子地图的区别图表:高精地图头部厂商情况敬请参阅最后一页特别声明国金证券SINOLINKSECURITIES行业深度研究、总论:自动驾驶与电动化、共享化改变汽车产业格局和出行方式意义:与汽车电动化、共享化的趋势结合自动驾驶与汽车电动化、共享化的趋势结合。相比与传统的汽车行业,电动车在系统控制与执行层面更适合自动驾驶,而自动驾驶与车联网的结合、汽车共享化的趋势,能够有效的预防交通事故、同时减少拥堵、提高道路的通行效率,使其容纳不断上升的通流量。未来的出行方式以及汽车本身都将会有很大的变化,由此带来巨大的新兴市场。美国年轻人首次申领驾照人数比例持续下降,自年起,美国肯年群体(岁)驾照持有人数几乎以每年递减;岁各年龄层的驾照持有率均出现了下降,以岁为例,年持有驾照的人数比例下降近;反怏出了即使是美囯这样车轮子上的国家,年轻人不再那么迫切的去考鸳照,共享出行已经可以满足出行需求。图表:美国年轻人首次中领驾照人数比例持续下摩岁有驾照人数来源:匡金证券研究所年美国市场售出万辆二手车(历史最大值),其中即近万人将成为“无车一族”,不再选择买新车而是选择使用以及公共交通解决通勤,也反映出美国市场对于共享出行方式的认可。图表:美国二手车卖家卖车后的选择选择UberLyftt等叫车软件9%其他或不确定,14%买了另辆车或还有一辆车77%来源:路透社,囯金证券研究所敬请参阅最后一页特别声明国金证券SINOLINKSECURITIES行业深度研究我国市场接受度更高。我国市场对于汽车电动化、共享化以及自动化的接受度更高,产业投入更大,预计年自动驾驶的汽车会占据整体出行里程的以上,由此带来的千亿美元规模的新兴市场有待开发。图表:我因出行方式里程比100%90%80%70%60%50%40%30%20%10%0%20172018201920202021202220232024202520262027202820292030自驾私家车自动私家车自驾共享车辆自动共享车辆来源:因会证券研究所分级:人类驾驶逐级步入车辆自动驾驶自动驾驶定义ε即让汽车自己拥有环境感知、路径规划并自主实现车辆控制的技术,也就是用电子技术控制汽车进行的仿人驾驶或是自动驾驶。根据人与车辆控制的程度不同,美国汽车工程师协会界定了五级自动驾驶方業,目前在基础上,到级刑的自动驾驶将迳渐成为新车型的标配产生大量新增需求,这是目前主要的投资机会到的完全自动驾驶也在逐渐成熟中,一旦商业化将影响产业的未来。敬请参阅最后一页特别声明国金证券SINOLINKSECURITIES行业深度研究图表;美国汽车工程师加会自动驾分级Execution ofFallbackManitoringSystemSAElevelNameNarrative DefinitionAcceleration/ of Driving, of Dynamic(DrivingDecelerationEnvironment Driving Task Modes)Human driver monitors the driving environmentNothe full-time per formance by the human driver of allAutomation aspects of the dynamic driving task, even when enhanced Human driver Human driver Human driverthe driving mode-specific execution by a driver assistancestem of either steering or acceleration/deceleration using Human drver Human driver Human driver some drivingAssistance information about the driving environment and with theand systemmodesaspects of the dynamic ariving taskthe driving mode-specific execution by one or more driverassistance systems of both steering and acceleration/Partial decelerat on using information about the drivingAutomation environment and with the expectation that the humanSystem Human driver Human driverSome drivingmodesdriver perform all remaining aspects of the dynamic arivingtaskAutomated driving system("system")monitors the driving environmentthe driving mode-specific performance by an automated3Conditional driving system of all aspects of the dynamic driving tasksystemHuman driver Some drivingAutomation with the expectation that the human driver will respondmodesappropr iately to a request to intervenethe driving mode-specific performance by an automa: edHigh driving system of all aspects of the dynamic driving task,SystemSystemSystemSome drivingAutomation even if a human driver does not respond appropriately to amodesequest to intervenethe full-time performance by an automated driving system5Fullof all aspects of the dynamic driving task under all roadwaySystemAll drivingAutomation and environmental conditions that can be managed by amodeshuman drver国金证券研究所代表没有自动驾驶介入的传统人类驾驶。级能够对方向盘和加减速中的单项操作给与支持。比如已经广泛应用的自适应巡航()功能,即能够通过雷达探测与前车的实时距离自动控制加减速,从而保持与前车的安全距离。级能够同时对方向盘和加减速中的多项操作给与支持。如果汽车除了具备上面级描述中的自造应巡航外,同时还具备车道保持()功能,或者自动变道功能,那则属于级自动驾驶级之前环境的观察者都是人,进入则意味着道路环境的观察和驾驶操作都由系统来完成,人只需要对所有的系统请求进行应答。系统已经完全能够识別出直线、弯道、红绿灯、限速路牌,路上行走奔跑的人猫狗等等各种环境变量。环境观察和驾駛操作都由系统来完成,人只需要对所有的系统请求进行应答。比如突然下雨了,检测到地面湿滑是否需要减速;比如裣测到前方车辆行驶过慢是否需要超车;检测到前方有人在车道较近处走动是否需要呜笛提醒等等,这些请求系统会反馈给驾驶员,由人来做决定。级驾驶操作和环境观察仍然都由系统完成,人只需要在某些复杂情况进行应答。比如只需要在某些复杂地形或者天气恶劣的情况时,才需要人对系统请求做出决策,而其他情况下系统能独自应付自动驾驶。级就是完全的自动驾驶状态,车上没有方向盘,没有刹车,没有油门,完全不需要人的介入。敬请参阅最后一页特别声明国金证券SINOLINKSECURITIES行业深度研究图表;人类驾欤逐级步入车辆自动驾驶HumanMachineLEVEL OLEVELTLEVEL 2VEL4LEVEL 5No driverAwarenessInterventionLongitudinal orTrafficfor Take OverNo ActiveTransverseControlAssistanceulaeNo DriverNo Take OverystemLongitudinalTake OverRequestLongitudinal orRequestTransverseand TransverseGuideGuideHands onHands onHands Temp offHands offHands offHands offEyes onEyes Onyes Temp ofEyes offMind offDriver C仟fIiWAutobahn(SA)City(Ride Sharing)来源国金诬券研究所实现:通过决策层、感知层、执行层■自动驾驶系统通常可分为决策层、感知层、执行层,以及高精地图和车联网的支持图表:自动驾狄实现层级自动车联网驾驶云端地图中控制器车端C|D感知层执行层摄像头转向制动动力雷达芯片模块来源:国金证桊研究所感知层:环境信息和车内信息的采集与处理。这方面涉及到道路边界检测、车辆检测、行人检测等技术,即传感器技术,所用到的传感器一般都会有敬请参阅最后一页特别声明国金证券SINOLINKSECURITIES行业深度研究激光雷达、摄像头、毫米波雷达、超声波雪达、速度和加速庋传感器等等由于各个传感器在设计的时候有各自的局限性,总个传感器满足不了各种工况下的精确感知,想要车辆在各砷环境下平稳运行,就需要运用到多传感器融合技术,该技术也是环境感知这一大类技术的关键技术所在,目前国内这方面和国外的主要差距也集中在多传感器融合方面。决策层:依据获取的信息来进行决策判断,确定适当工作模型制定相应控制策略,替代人类做出驾驶决策。这部分的功能类似于给车辆下达相应的任务,例如在车道保持、车道偏高预警、车距保持,障碍物警告等系统中需要预测本车与其他车辆、车道、行人等在未来一段时间内的状态,先进的决策理论包括模糊推理、强化学习、神经网络和贝叶斯网络技术等。由于人类驾驶过程中所面临的路况与场景多种多样,且不同人对不同情况所做出的驾驶策略应对乜有所不同。因此驾驶决策算法的优化需要非常完善高效的人工智能模型以及大量的有效数据。这些数据需要尽可能的覆盖到各种罕见的路况,而这也是驾驶决策发展的最大瓶颈所在执行层:指系统在做出决策后,替代人类对车辆进行控制,反馈到底层模块执行任务。车辆的各个操控系统都需要能够通过总线与决策系统相链接并能够按照决策系统发岀的总线指令精确地控制加速程度,制动程度以及转向幅度等驾驶动作。高精地图以及车联网的支持,系统能够确定位置并规划一条可通行的路径实现智能车辆的自主导航;更进一步,车联网的应用一方面能够是出行更加方便智能,另一方面又能够护展汽车交通工具的属性,成为未来个人的移动平台。相关公司图表:自动驾驶相关公司公司名称代码收盘价业务索菱股份自动驾驶系统兴民智通、自动驾驶系统德赛西威、人机交互均胜电子人机交互系统华阳集团数字仪表东软集闭自动驾驶系统路畅科技自动驾驶系统巨星科技激光雷达中海达激光雷达华域汽车毫米波雷达舜宇光学车载摄像头欧菲科技车载摄像头四维图新高精度地图亚太股份自动驾驶制动系统耐世特自动驾驶转向系统金龙汽车整车来源:国佥证券研究所敬请参阅最后一页特别声明国金证券SINOLINKSECURITIES行业深度研究二、自动驾驶解决方案:整车厂和科技巨头蓄势待发厂商:投入巨大、成果显著传统整车厂如奧迪、特斯拉、通用、丰田、福特等公司均有自己的自动驾驶研发团队,在自动驾驶领域投入巨大,成果显著,如奧迪级自动驾駛系统已经量产上市。图表:厂商进展情况系统路径进展测试车队奥迪和并行级量产上市禾取摄像头毫米波雷达方案,目前年型具备能力,有万辆特斯拉白至能够传回驾驶数据,有大量驾驶里栏。马斯克最近宣布,覆盖各类驾驶场景的完全自动驾驶将在年年末到来通用和并行将生产数千辆自动驾驶汽车,用于出租车服务:亿美辆雪佛兰元收购亿美元入股直接年首先将自动驾驶车投入招车服务,亿美金收购辆沃尔沃丰田和并行己实现,车型正在测试,年实现完全无人驾驶能力亿关金收购,战略投资,拥有庞大福特直接自动驾驶测试车队,年自动驾驶汽年上路,用于共享出行,年辆年销售私人客户来源:公开資料、国金证桊研究所系统厂商:小联盟百度大联盟能够提供自动驾驶解决方案的系统厂商,目前以谷歌的和百度的为代表,图表:系统厂商进展情况系统路径进展测试车队年即起步,年组建年与克菜斯勒合作的放(谷歌直接无人驾驶车上市,预计年投入运营。已积累英里,每英里需人工干预次,遥遥领先竞争对手克菜斯勒,辆年成立自动驾驶事业部,年自动驾驶事业群组,李彦宏(百度)为主,支持宣布年小规模生产自动驾驶小巴车年大规模量产自动驾欤汽车测试年月进行深圳实地路测;此前进行了硅谷雨夜的路测。结果显示均较好。来源:公开资料、国金证券研究所■谷歌母公司旗下独立的专注自动驾驶系统开发的子公司。谷歌自年起启动自动驾驶项日,年成立独立实体图表发展历程时间开发进展年启动自动驾驶汽车项日,成立自动驾驶汽车团队,大范围采集街景数据,构建地图数据库年经由《纽约时报》,正式对外公布正在研发全自动驾驶汽车及以上年获得加州机动车管理局〈)颁布的自动驾驶汽车路测许可年正弌开始复杂情况下的城市道路实测年。设计(萤火虫)原型车并进行系列改装年公司重组为,开始和汽车制造商合作,不再亲自制造汽车本身年成立专注研究并商业化自动骂驶技术的独立实体公司年拿到美国高速公路安全管逗局(〕的认定文件,开启真人乘车试验年在亚利桑那州拿到美国首个商业自动驾驶打车服务执照来源:公司官网,国金证券研究所敬请参阅最后一页特别声明
- 2020-11-30下载
- 积分：1
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
|
联系客服（QQ：3324461878）
