驾驶证识别接口说明书
DS-TCG2PK-AIR 智能车牌识别摄像头说明书
Specification
Image Sensor
1/2.8" Progressive Scan CMOS
Min. Illumination
Color: 0.002Lux@(F1.2, AGC ON) B/W: 0.002Lux@(F1.2, AGC ON)
Shutter Speed
1/30 s to 1/100,000 s
Lens
3.1 mm to 9 mm
IR Cut Filter
Support
Video Compression
H.265, H.264
Vieo Bit Rate
32 Kbps to 16 Mbps
Image Format
JPEG
Max. Resolution
1920 × 1200
Frame Rate
DS-TCG2PK-AIR(12V/PoE) ANPR Camera
Entrance & Exit Product
2MP
CMOS
ANPR
IR
VF
Relays
All-in-one
PowerZoom
DS-TCG2PK-AIR(12V/PoE) camera, based on deep learning, consists of protective cover, lens, camera, LED and power supply, offers high-definition Progressive Scan CMOS, and integrates intelligent recognition algorithms for specific applications such as entrance management, road safety enforcement, in-vehicle monitoring, parking lot control, etc.
驾驶证识别的方法教程
驾驶证识别的方法教程
大家在生活中有遇到过驾驶证识别的问题吗，你是如何去解决的？好的方法不仅可以节约时间还可以提高工作效率，今天就给大家出一个驾驶证识别的方法教程，有需要的人可以学习一下。
解决方法：通过捷速OCR文字识别软件去操作。
软件介绍：可以识别出银行卡，身份证，行驶证多种票据，也是支持多种文件格式的图片的，如果你有遇到不会去识别驾驶证的时候，下载捷速OCR文字识别软件/就可以帮你快速解决这个问题了。
操作步骤：
1、第一步打开电脑在浏览器上搜索下载一个捷速OCR文字识别
软件并安装到自己的电脑当中去。
2、第二步运行软件点击“票证识别”然后点击添加你要识别的驾驶
证图片或者你把图片拖进去都是可以的。
3、第三步图片添加进去之后票证类型选择为“驾驶证”。
4、第四步票证类型选择完之后点击右边区域的“开始识别”。
5、第五步识别完成之后点击“打开文件”。
6、第六步打开文件后会出来几种文件保存形式，选择一个你想要
保存的文件形式就可以了，这样你的驾驶证图片就被识别保存出来了。
今天就给大家分享到这里了，大家都学会了吗？。
2024版OBD使用说明
OBD使用说明•OBD基本概念与原理•OBD设备选择与安装目录•数据读取与解析方法•故障诊断与排除流程•软件更新与升级策略•总结回顾与展望未来01OBD基本概念与原理OBD 能够对车辆的各种运行状态进行监测，及时发现潜在的故障并提醒驾驶员。
OBD系统还可以对车辆的排放进行监控，确保其符合环保法规要求。
OBD是英文On-Board Diagnostics的缩写，意思是指车载自动诊断系统。
OBD定义及作用OBD系统通过各种传感器和控制单元来监测车辆的运行状态。
当发现异常或故障时，OBD系统会通过故障代码（DTC）来指示具体问题。
驾驶员或维修人员可以通过专门的诊断工具来读取故障代码，并进行相应的维修。
工作原理简述在车辆年检时，检测人员会通过OBD 系统来检查车辆是否存在故障或排放超标等问题。
车辆年检故障排查二手车评估当车辆出现故障时，维修人员可以通过OBD 系统来快速定位并解决问题。
在购买二手车时，可以通过OBD 系统来检查车辆的历史故障记录和维修情况，为购买决策提供参考。
030201常见应用场景相关法规与标准各国针对OBD系统都制定了相应的法规和标准，以确保其能够有效地监控车辆的运行状态和排放情况。
在我国，环保部门也制定了严格的OBD法规和标准，要求所有新生产的轻型汽车和重型柴油车都必须配备OBD系统。
随着环保要求的不断提高，未来OBD系统将会更加普及和重要。
02OBD设备选择与安装03多功能集成式OBD 设备除了基本的OBD 功能外，还集成了GPS 定位、行车记录仪、胎压监测等多种功能。
01独立式OBD 设备可独立工作，无需连接手机或电脑，具有实时故障诊断、数据存储等功能。
02蓝牙/WIFI 连接式OBD 设备通过蓝牙或WIFI 与手机或电脑连接，实现远程监控、数据传输、实时故障诊断等功能。
设备类型及功能对比选购注意事项与建议选择与您的车型及OBD 接口兼容的设备。
选择知名品牌、质量可靠的产品，避免购买劣质设备。
车辆识别验证手册说明书
Authorised Inspector Vehicle Identity Validation ManualContents1. Introduction (4)2. Where to get advice (4)3. Vehicle Identity Validation (Compliance Inspection) (5)What is a Compliance Check? (5)Who may perform Compliance Checks? (5)When are Compliance Checks required? (5)4. Vehicle identifiers (5)5. Vehicle Identification Number (VIN) /Chassis Number (5)6. Structure of VINs (6)7. Vehicle Identification Number location and attachment (6)8. Identification plates (pre 1 July 2021) (7)9. Secure Vehicle Identification (SVI) label (from 1 July 2021) (9)10. Approved plate or label location and attachment (9)11. Engine numbers (10)12. Secondary identifiers and other markings (10)13. Date coding and other markings (10)14. Data Dot security system (only used by some manufacturers) (10)15. Compliance Check procedure (11)Reason for rejection (11)16. Inspect the engine number (11)Reason for rejection (11)1.IntroductionThe purpose of this reference guideline is to assist Authorised Inspectors with a method of inspecting a vehicle’s identifiers. Its aim is to ensure that the vehicle identifiers are not missing or altered in any way, and to also ensure that the vehicle corresponds with the registration application details and/or information contained on a registration authorit y’s data base.2.Where to get adviceFrom time to time, Authorised Inspectors may encounter situations that are not covered by the inspection guidelines or relevant manuals. In such cases, the problem should not be put aside or solved by guess-work. Instead, advice should be sought from the Vehicle Standards and Compliance team.The Vehicle Standards and Compliance team is a group of Technical Officers and Transport Inspectors who are available to provide advice in relation to a vehicle standards or compliance issue that an Authorised Inspectors may encounter. General enquiries should be directed to the Vehicle Standards and Compliance Group at the following contacts.3.Vehicle Identity Validation (Compliance Inspection)What is a Compliance Check?A compliance check is an inspection of a vehicles identifiers by an approved person. Its aim is to ensure that the vehicle identifiers are not missing or altered in any way, and to also ensure that the vehicle corresponds with the registration application details and/or information contained on a registration authorities data base.Who may perform Compliance Checks?Transport Inspectors, Police Officers and approved Authorised Inspectors, may carry out compliance checks. Approved Authorised Inspectors may carry out compliance checks on factory new Motor Vehicles including used interstate vehicles that are owned by a Northern Territory Licensed Motor Vehicle Dealer.When are Compliance Checks required?Compliance checks are required on all vehicles:•That are applying for first registration in the Northern Territory, previously NT registered vehicles returning from a period of interstate registration do not require a compliance check.•When confirmation of vehicle identification or vehicle description is required, not including update of an engine / number change (same for same) where recorded by an Authorised Inspector on their inspection report.4.Vehicle identifiersVehicles are identified by a number of markings that are unique to the particular vehicle these being: •Vehicle Identification Number (VIN) or chassis number•Vehicle Identification Plate•Secure Vehicle Identification Label (SVI)•Engine number•Data Dot markings where applied.Australian Design Rules (ADRs) require the above identifiers excluding Data Dots to be placed on vehicles by vehicle manufacturers. The VIN is considered to be the primary vehicle identifier. The other identifiers are used to support and confirm the vehicle identity. Vehicles may also have a number of secondary forms of identification such as a manufacturers build plate.5.Vehicle Identification Number (VIN) /Chassis NumberChassis numbers were used on all vehicles prior to the introduction of VINs. They have no mandatory structure, however manufacturers did have set styles of stamping and number types.VINs were introduced from 1 July 1988 and became mandatory on all vehicles certified for road use manufactured from 1 January 1989, with the exception of ‘L Group’ M oped 3 Wheels and Motor Tricycle where VIN’s became mandatory from 1 March 1991.VINs are a unique form of vehicle identification and are an international standard used by vehicle manufacturers worldwide. No two vehicles in the world should have the same VIN.6.Structure of VINsThe first three characters comprise the World Manufacturer Identifier (WMI), which is a code assigned to the manufacturer and also shows the country where the manufacturing plant is located.The next six characters comprise the Vehicle Description Section (VDS). This section may be used by the manufacturer to provide information describing the vehicle. A manufacturer may for example, use this section to identify the vehicle construction type and/or to show the vehicle level of luxury, mass etc. Alternatively some manufacturers may not wish to use this section and elect to fill the six spaces with a single set of characters of their own choice.The last eight characters are the Vehicle Indicator Section (VIS). This section distinguishes one particular vehicle from another. It is a requirement that the last four characters be numeric. It is normal practice for numbers in this section to be sequential e.g., the first VIN in a model run may end in 0001, the second 0002 etc.Note 1:The minimum height (A) of the letters or numerals is:•7mm if stamped on the body, frame or chassis and•4mm if stamped on a separate plate except for trailer plates fitted to trailers less than4.5 tonnes (ATM).•The minimum height for a VIN on such a trailer plate is 2.5mm.Note 2: Only Roman Letters and Arabic Numerals may be used. The letters “I”, “O” and “Q” must not be used.7.Vehicle Identification Number location and attachmentThe VIN number may be located on either side of the vehicle, preferably on the front half and located on a permanent structure of the vehicle, or alternatively on a separate plate which has been permanently affixed to the vehicle.A typical location for a VIN could be on a permanent structure of a vehicle, which cannot be easily substituted, or is not likely to be removed or replaced. Such as the fire wall of a motor vehicle or the chassis rail on a semi-trailer or the drawbar on a box trailer.The VIN number may be either impressed, embossed, etched or fabricated on to the vehicle or plate. If a plate is used, it must be made of metal and be affixed so that it cannot be easily removed, replaced or altered without detection. Acceptable methods of attachment include welding, tamper proof rivets and hammer drive screws.Manufacturers who do not have equipment that will easily allow affixing of a 17 character VIN number may choose to use the VIN plate alternative which could be pre-stamped with the non-variable parts of the VIN number.Trailers less than 4.5 tonnes Aggregate Trailer Mass (ATM) are only required to display the VIN on the trailer plate. However, in addition to this requirement the VIN may also be stamped on the chassis or drawbar of the trailer.8.Identification plates (pre 1 July 2021)Identification plates are currently a mandatory requirement under Australian Design Rules (ADRs), they are required on all new passenger cars and goods vehicles manufactured after 1 January 1974, all motor cycles manufactured after 10 October 1976 and all trailers manufactured after 1 August 1989, their primary purpose is to indicate compliance to all relevant ADRs at the time of manufacture. They are required to carry some specific information including the vehicles VIN or chassis number.Identification plates were not intended to be a significant vehicle identifier as they can be easily transferred between vehicles. However, used in conjunction with other identifiers they are seen as a valuable tool in identifying a vehicle.The Motor Vehicle Standards Act 1989 (the Act) defines identification plates as plates declaring the status of new road vehicles in relation to the national standards, and approved to be placed on new vehicles of that type or description under procedures and arrangements provided for in subsection 10(1) of the Act.Note 1: In practical terms, identification plates placed on new vehicles indicate that the (Commonwealth) Administrator of Vehicle Standards (the Administrator) has issued an Identification PlateApproval (IPA) for new vehicles of that type under Section 10A of the Act.Note 2: Identification plates were formerly known as compliance plates.Note 3: Refer to examples of identification plates – see next page.Identification plates, regardless of type, are distinguishable from other plates that may be fitted to vehicles such as manufacturers build plates, as they will always have a reference to the Australian Motor Vehicle Certification Board, or Motor Vehicle Standards Act 1989.For further Information refer to the Federal Government Circular 0-3-2 via the below linkhttps://.au/vehicles/vehicle_regulation/files/0-3-2.pdfExample of full volume motor vehicle compliance plate.Example of full volume two and three wheeled motor vehicles (motor cycles and trikes) compliance plate.Example of standard new trailers compliance plate.9.Secure Vehicle Identification (SVI) label (from 1 July 2021)The Commonwealth Department of Infrastructure, Transport, Regional Development and Communications (DITRDC) replaced the Motor Vehicle Standards Act 1989 (Cth) (MVSA) with the Road Vehicle Standards Act 2018 (RVSA) and Road Vehicle Standards Rules 2019 (Cth) (the Rules).The RVSA, the Rules and other related legislation are collectively referred to as the RVS legislation. A 12 month transitional period began on 1 July 2021, where some MVSA approvals will continue to remain in force to ensure a smooth transition to the new regulatory framework.A key change under the RVS legislation is the introduction of the Register of Approved Vehicles (RAV), which is a publicly searchable database of vehicles that have met the requirements of the RVS legislation and been approved to be provided to the Australian market. The RAV replaces the need for the physical compliance (ID) plates to be fitted to new vehicles.The information previously obtained from the compliance (ID) plate, will now be accessible by searching the vehicle’s VIN on the RAV. The VIN will still be physically located on the vehicle through a Secure Vehicle Identification (SVI) label. Of note, during the transitional period, some vehicles can continue to be provided to the Australian market under existing MVSA approvals (i.e. vehicles may still have compliance plates fitted and may not be on the RAV or a combination of both for 12 months from 1 July 2021). Under the RVS legislation, all road vehicles (cars, trucks, trailers and caravans etc.) must be entered onto the RAV before they can be provided to the market for the first time in Australia.Access to the RAV can be found via the following web link:.au/vehicles/rav/index.aspxExample of RAV10.Approved plate or label location and attachmentThe approved plate, adhesive label or SVI should be placed on the body part of the vehicle in a position where it is not exposed to accident damage or disfigurement and can be readily examined. The body part to which the plate or label is placed should not usually be subject to replacement in the event of an accident. Commonly used locations for placing the approved plate or adhesive label include the following: ∙Passenger cars and bonneted trucks - on the panel separating the front compartment from thepassenger compartment, on a front suspension tower or on an engine compartment side deck.More recently, the labels are located on front door sill panels or pillars.∙Cab over engine trucks - in the passenger compartment on the inner panel rearward of the driver’s or passenger’s door.∙Forward control passenger vehicles and vans - within the passenger compartment in the front passenger’s footwell a rea.∙Motorcycles and mopeds - on the steering head.∙Trailers - on the front vertical face of the trailer (adjacent to the trailer brake line couplings if appropriate) or on an inward facing vertical face of an A-frame draw bar where fitted.Approved metal plates must be placed on the vehicle by either welding or riveting or otherwise permanently attached in a readily visible position. Identification plates are required to be located in a conspicuous position on the vehicle, and are usually under the bonnet on the firewall, other locations may be door pillars or in the boot.The Road Vehicle Certification System may provide useful information (in the form of a grid location) in locating vehicle identifiers via a Vehicle Search, refer to the below web link.au/If one is available, the grid location can be referenced in the Grid Location Charts found via the below web link.au/vehicle%20identification%20and%20engine%20number%20location.pdf 11.Engine numbersLike chassis numbers there is no formal structure to engine numbers and manufacturers use a wide range of in house systems and stamping techniques. ADRs require the number to be placed on a main component of an engine at the time of manufacture. The numbers are usually stamped into the engine block on a machined surface.12.Secondary identifiers and other markingsSecondary identifiers are such things as vehicle build plates and date coding on vehicle components etc. These are not usually checked as part of a compliance check, but can be used for further investigation on a suspect vehicle. They are useful in the aid of confirming identity and can often give a good indication to the date of manufacture of the vehicle.13.Date coding and other markingsA number of vehicle components are marked with date coding indicating the date of manufacture of the component. Components such as seatbelts and glass are generally marked and easily checked, other components such as transmissions, steering racks and plastic components may also have date coding labels or markings. The dates on these components should all be prior to the claimed build date of the vehicle unless the parts have been replaced. However, if all dated parts have dates later than the claimed build date this would be suspicious and may warrant further Police investigation.14.Data Dot security system (only used by some manufacturers)The Data Dot vehicle security system involves spraying many thousands of tiny Data Dots (each about1mm in diameter and a few microns thick) which carry the vehicles VIN. The dots are carried in a special clear adhesive that contains an ultra-violet trace and are sprayed onto vehicle surfaces such as, vehicle under body, inside box sections, onto drive line and suspension components.To confirm the vehicles identity the dots are located with an ultra-violet light and some removed and checked under a magnifying glass or microscope.Authorised Inspector Vehicle Identity Validation Manual pliance Check procedureInspect the VIN / chassis number stamped on the vehicle chassis/body.Reason for rejectionThe VIN:∙is incomplete;∙missing;∙shows any signs of being tampered with or altered;∙stamping is not the correct type as used by the manufacturer;∙does not match the VIN/chassis number on the identification plate;∙is not stamped in the correct location for the make model of vehicle;∙SVI label shows any signs of being tampered with or altered (subject to RVS);∙VIN is not on the RAV (subject to RVS).16.Inspect the engine numberReason for rejectionThe engine number:∙is unable to be located or missing;∙shows signs of being tampered with or altered;∙is not located in the correct location for the make model of vehicle.Note:The above may not necessarily be an immediate reason for rejection, refer to Senior Transport Inspector.Department of Infrastructure, Planning and Logistics4 August 2021 | Version 3Page 11 of 11。
证件识别SDK开发手册(文通)
一般说来，使用 SDK 的大致流程如下：
安装扫描仪\拍照设备
加载 SDK 库
循环进行采集图像、识别
卸载 SDK 库
地址：北京市海淀区北四环西路 9 号银谷大厦 16 层 1609 室 电话：（010）62800286/62800250 网址：
5
1.5 SDK 文件清单
Demo_setup 文件夹：演示程序； OCX 控件及文档：OCX 控件及说明文档； DLL&LIB 文件夹：识别核心文件； HelpDoc 文件夹：识别核心的开发手册； Samples 文件夹： SDK 的调用例程，包括 VB、VC、C#、VB6.0 的； 图像校准工具： 校准图像。 注意：如果要正常使用本 SDK 需要配合使用 1.6 里面提到的授权文件。
地址：北京市海淀区北四环西路 9 号银谷大厦 16 层 1609 室 电话：（010）62800286/62800250 网址：
4
第一章 SDK 简介
1.1 SDK 版权说明
身份证扫描识别 SDK 版权归属北京文通科技有限公司所有，未经北京文通科 技有限公司授权，不得擅自进行使用。
1.4 调用约束
在调用身份证件识别 SDK 前，请确认选用的身份证件专用扫描仪或拍照设备 已正确安装完毕，并正常连接。
提示：本身份证件识别 SDK 只有在挂接身份证件专用扫描仪或拍照设备后才 能正常调用，否则将加载失败无法调用。
地址：北京市海淀区北四环西路 9 号银谷大厦 16 层 1609 室 电话：（010）62800286/62800250 网址：
2
目录
第一章 SDK 简介.........................................................................................................4 1.1 SDK 版权说明..........................................................................................4 1.2 SDK 运行环境..........................................................................................4 1.3 SDK 主要功能描述..................................................................................4 1.4 调用约束...................................................................................................4 1.5 SDK 文件清单..........................................................................................5 1.6 SDK 授权文件说明..................................................................................5 1.7 SDK 使用流程简述..................................................................................5
车牌识别简易说明书
车牌识别简易说明书一：安全岛施工图
二:拓扑图
三:脱机车牌识别控制板接线图
四：电脑IP设置
注意：如果电脑IP不在零网段，请务必为电脑在添加个零网段的IP，例如上图添加完以后电脑一般有两个IP地址
五:相机IP地址设置
六:触发线及焦距设置
IE浏览器地址栏直接输入相机IP地址回车
注：正确设置
注:错误的设置
七:串口推送设置
注意：这里的串口1和串口2的波特率请设置为115200后点确认
注意：串口推送配置的每个选项的排序不能乱必须跟图片一样
八:停车场软件设置
第一步:添加出入口控制机号
注：添加”控制类型”必须填写正确
第二步: 设置通讯方式
第三步：设置车道及车牌识别选项
第四步:设置户外屏参数
第五步：加载时间，收费标准
八:车辆授权
九:进入在线监控
十:微信支付设置
注意：如果场内有停车自助缴费终端机的话，这请务必添加终端机。
驾驶证识别在电脑上怎样操作
目前有驾驶证的人越来越多，那么大家知不知道驾驶证是怎样被识别信息的呢？今天小编就分享给大家一下驾驶证识别的具体操作。
有兴趣的可以试试哈！
第一步：打开我们电脑上迅捷OCR文字识别软件。
我们需要的驾驶证识别是在票证识别的页面内，所以我们应点击“票证识别”。
第二步：进入到票证识别的页面，在票证识别的页面内显示有多种票证识别功能。
第三步：我们需要选取并点击票证识别功能的驾驶证识别，即进入到驾驶证识别的界面内了。
第四步：在驾驶证识别的界面内可点击“添加文件”或是“添加文件夹”，还可以点击界面中间的加号。
第五步：把相关的驾驶证图片添加进去之后，我们还需要考虑好识别驾驶证之后的TXT保存文件，这个可以在设置保存路径内调整。
第六步：最后就是对“一键识别”键进行点击了。
大家看懂了驾驶证识别的操作过程了吗？喜欢的小伙伴们可以分享给我们的朋友们哈！。
驾驶员身份识别器产品手册
道路运输车辆卫星定位系统车载终端
项目编号
SZSW-XD
文档编号
SZW-XD-0003
文档版本
V3.0
交通部 IC 卡道路运输证 驾驶员身份识别器 产品手册 （V0.3）
深圳市雄帝科技股份有限公司
驾驶员身份识别器产品手册
文件修订记录
版本号 V0.1 V0.2 V0.3 生成日期 2012-08-01 2012-09-01 2013-04-01 作者 石张文 石张文 石张文 修订内容 初始版本 初始版本 正式版本
95 长 x70 宽 x22.5 高 mm
4、产品接口
4.1、外置驾驶员身份识别器与终端设备连接，接头各厂家根据自己产品自配；
注：连接终端设备的线长 1.5m；
深圳市雄帝科技股份有限公司
4
驾驶员身份识别器产品手册
4.2、接线头定义:
Ø 电源：粉（红） Ø TX：棕 （橙） Ø RX:蓝 （绿） Ø GND：黑（黑）
目
录
文件修订记录.......................................................................................................................................................2 目 录.................................................................................................................................................................2 1、型号名称：EMP5700 驾驶员身份识别器............................................................................................3 2、产品概述.................................................................................................................................................3 2、产品示意图.............................................................................................................................................3 3、技术参数.................................................................................................................................................4 4、产品接口.................................................................................................................................................4 4.2、接线头定义:.........................................................................................................................................5 5、识别器安装方式.....................................................................................................................................5 二、内置式驾驶员身份识别器 ...........................................................................................................................6 1、型号名称：EMP5701 驾驶员身份识别器............................................................................................6 2、产品示意图.............................................................................................................................................6 3、接口.........................................................................................................................................................7 4、技术参数.................................................................................................................................................7 5、安装方式.................................................................................................................................................8 一、外置式驾驶员身份识别器 ...........................................................................................................................3
车牌识别系统HVActiveX控件接口说明
车牌识别系统HV ActiveX2控件接口说明目录1注册控件 (4)2控件属性 (4)⏹LONG RecvSnapImageFlag (4)⏹LONG RecvPlateImageFlag (4)⏹LONG RecvPlateBinImageFlag (4)⏹LONG RecvVideoFlag (4)⏹BOOL AutoSaveFlag (4)⏹BSTR ShowPlateImage (5)⏹BSTR ShowFirstImage (5)⏹BSTR ShowSecondImage (5)⏹BSTR ShowPlateResult (5)⏹BSTR ShowCaptureVideo (5)⏹BSTR ShowMainVideo (5)⏹BSTR Station (5)⏹BSTR Direction (5)3属性页 (5)⏹附加输出信息 (5)4控制接口函数 (6)⏹void ConnectTo(BSTR strAddr) (6)⏹LONG GetStatus(void) (6)⏹void Disconnect(void) (6)⏹Void ForceSend(void) (6)⏹LONG ForceSendEx(LONG iVideoID); (6)⏹LONG SetConfig(void) (6)⏹LONG SetDevIP(void) (7)⏹LONG SetDevBasic(void) (7)⏹LONG SetDevMode(void) (7)⏹LONG SetResultParam(void) (7)⏹LONG SetDataProcessing(void) (7)5获取信息和保存结果接口函数 (7)⏹LONG GetCarID(void) (7)⏹BSTR GetPlate(void) (7)⏹BSTR GetPlateColor(void) (7)⏹BSTR GetPlateInfo（void） (7)⏹LONG GetVideoID(void) (8)⏹LONG SaveSnapImage(BSTR strFileName) (8)⏹LONG SaveSnapImage2(BSTR strFileName) (8)⏹LONG SavePlateImage(BSTR strFileName) (8)⏹LONG SavePlateBinImage(BSTR strFileName) (8)⏹LONG SaveSizedSnapImage(LPCTSTR strFileName, LONG iWidth, LONG iHeight) .8⏹LONG SaveSizedSnapImage2(LPCTSTR strFileName, LONG iWidth, LONG iHeight)8⏹LONG SaveComplexImage(BSTR strFileName) (8)⏹LONG SavePlateBin2BMP(BSTR strFileName) (9)⏹LONG GetVideoFrame(BYTE* pFrame, LONG* plSize) (9)⏹BSTR GetVideoFrameSM(LONG lVideoID, LONG* plSize) (9)⏹LONGLONG GetImageTime(LONG ImageIndex) (10)⏹BSTR GetImageTimeString (LONG ImageIndex) (10)⏹BSTR GetImageShareMemName (LONG ImageIndex, LONG iType, LONG*pImageSize) (10)6事件函数 (11)⏹void OnReceivePlate() (11)⏹void OnReceiveVideo(void) (11)7HV ActiveX流程图 (12)1注册控件◆HV ActiveX2控件必须依赖于HVDLL.dll和GrfCfg.dll。
驾驶证机动车查询验证WebSerivce调用编程接口说明及示例代码
驾驶证机动车查询验证WebSerivce调⽤编程接⼝说明及⽰例代码 编写⽬的为全国机动车驾驶证验证查询（物流公司、银⾏保险、⼤型⽹站）提供统⼀的WebService访问⼊⼝。
接⼝的访问需要遵循相关的格式规定，为了使其他业务系统能很好地调⽤提供的WebService特编写该⼿册。
1.2 接⼝功能说明⼀、查询接⼝（提供规范）（1）驾驶者查询(验证），如果驾驶⼈姓名为空，则为驾驶证查询，否则为验证，只获取基本信息。
（提交必要条件：发证机关、证件类型、证件号码，可选条件驾驶⼈姓名）（queryDriveInfoValidate）。
（2）机动车信息验证提交必要条件：发证机关、车辆类型、车辆号码、验证类型（0 查询 1发动机号校验 2 所有⼈校验 3 车架号校验 4 车⾝颜⾊校验）；可选条件：验证关键词（queryMotorInfoValidate）。
⼆、接⼝访问地址考虑到WebService接⼝提供给全国各个公司的验证查询权限及安全机制的不同，分别提供不同的WebService访问接⼝。
对其他业务系统的接⼝访问地址为：2、调⽤接⼝说明2.1其他业务系统的接⼝定义说明⼀、驾驶证信息查询验证接⼝（1）对外公布⽅法名：public XmlDocument queryDriveInfoValidate(string Pin, string Fzjg, string Zjlx, string Zjhm, string Syr)序号参数参数名称注释1调⽤序列号Pin2发证机关Fzjg必须3证件类型Zjlx必须4证件号码Zjhm必须5驾驶⼈姓名Syr可选（2）返回结果封装格式：<?xml version="1.0" encoding="utf-8" ?><DriveInfo><Code>00</Code><Message>查询成功</Message><Date><Yxq>2003年03⽉31⽇⾄2009年03⽉31⽇</Yxq><Jsnx>旧期限</Jsnx><Zjcx>A2E</Zjcx><Ljjf>0</Ljjf><Cfrq>未填写</Cfrq><Yxqz>2009年03⽉31⽇</Yxqz><Hzrq>2010年03⽉31⽇</Hzrq><Zt>正常</Zt><Zxtjbrq>2008年04⽉29⽇</Zxtjbrq><Hzjl>3</Hzjl><Syjl>4</Syjl><Hz0><HZRQ>2003年01⽉20⽇</HZRQ><Bhzyy>⾃愿降级</Bhzyy><Yjsqx>旧证</Yjsqx><Yyxqz>未填写</Yyxqz></Hz0><Hz1><HZRQ>2003年12⽉24⽇</HZRQ><Bhzyy>期满</Bhzyy><Yjsqx>旧证</Yjsqx><Yyxqz>未填写</Yyxqz></Hz1><Hz2><HZRQ>2009年04⽉07⽇</HZRQ><Bhzyy>遗失</Bhzyy><Yjsqx>旧证</Yjsqx><Yyxqz>未填写</Yyxqz></Hz2><Sy0><Syrq>2005年12⽉31⽇</Syrq><Ysynd>2005年12⽉24⽇</Ysynd></Sy0><Sy1><Syrq>2006年12⽉30⽇</Syrq><Ysynd>2006年12⽉24⽇</Ysynd></Sy1><Sy2><Syrq>2008年04⽉29⽇</Syrq><Ysynd>2007年12⽉24⽇</Ysynd></Sy2><Sy3><Syrq>2009年02⽉18⽇</Syrq><Ysynd>2008年12⽉24⽇</Ysynd></Sy3></Date></DriveInfo>（3）备注：code：返回结果信息，00表⽰正常，其他值表⽰调⽤出现出错Message：返回结果中⽂解析Date:当Code为00时，返回详细结果，否则这个节点不存在。
车牌识别说明书
1停车场软件的安装1.1安装停车场软件1)打开光盘，运行Set_Up.EXE，如图示1图示12)安装完成弹出如下对话框，如图示2图示23)首先创建本地数据库，执行选择弹出数据库管理工具，如图示3图示3输入服务器名称，然后连接数据库再创建数据库，创建成功后直接退出4)创建数据库成功后就需要连接数据库，执行“连接到其他电脑”5)弹出连接数据库工具，输入数据库名称然后测试连接（多台电脑连接同一个数据库也是在此工具下设置），连接成功后点击确定保存信息2停车场软件操作2.1软件的登陆1)运行软件的安装包，安装好软件。
2)创建好数据库后，点击图标打开软件如图示13)出现智能停车场管理系统登录窗口，如图示2，输入用户编号101后，直接点击“确定”按钮进入软件操作图示22.2出入口设置1)打开系统设置中的出入口设置如图示1。
图示1注：在设定出入口设置之前，先提前在系统基础参数设置里面选择好摄像机类型。
如下图选择好相机类型后进入下位机设置界面如图示2。
网络摄像机IP提取和设置按钮图示22)一体机IP提取和设置A、ZS相机的设定□1点击右上角的“网络摄像机IP提取和设置”按钮，调取出一体机配置工具界面，如图示3。
图示3□2点击登录设备下的开始按钮，此时会扫描出局域网内摄像机IP。
选择扫描出的摄像机IP，点击网络参数设置按钮，进入一体机IP设置界面图示10选择设备IP，点击登录设备下的打开按钮如图示11，图示11连接成功后，打开会显示一体机画面，如图示12图示12点击设备操作下的“线圈设置”，可设定虚拟线圈识别区域，设定好后保存。
点击聚焦、变倍的“+”“—”按钮可调节一体机摄像机的焦距和清晰度。
车辆通过方向为方向识别图示14点击白名单：可以查询摄像机里面的的白名单资料更多配置里面的关于：可以查询摄像机的版本车牌记录：可以查询识别的历史记录生成日志、加密配置、视频配置、导出配置：功能暂时不用。
点击LED亮度：可调节补光灯的亮暗度。
车辆合格证识别产品使用手册说明书
悦保科技视觉AI识别产品使用手册（车辆合格证识别）一、接口名字：车辆合格证识别二、请求地址：https:///api/ocr/vehicleCertificate三、请求方法：POST四、请求体格式：multipart/form-data五、请求参数：1.Query六、返回值说明：1、返回结果2、data七、返回示例：成功请求返回值示例{"code":0,"status":200,"message":"success","serialNo":"411340469696462848","data":{"certificateNo":"WAC282002051711","releaseDate":"2019年09月30日","companyName":"东风汽车有限公司","vehicleBrand":"东风日产牌","vehicleName":"轿车","vehicleModel":"DFL7161VANH2","vin":"LGBH72E07KY835139","vehicleColor":"珠光白","chassisModels":"","engineType":"HR16","engineNo":"501217H","fuelType":"汽油","displacement":"1598","power":"93","emissionStandard":"GB18352.6-2016国V","fuelConsumption":"","outsideSize":"","internalSize":"","leafSpring":"","tireNumber":"4","tireSpecifications":"","wheelBaseBefore":"","wheelBaseAfter":"","wheelbase":"2700","axleWeight":"","shaftNumber":"2","toForm":"方向盘","totalQuality":"1670","weight":"1239","ratedLoadWeight":"","loadUtilization":"","tractionTotal":"","semiSaddleMaxTotal":"","cab":"","ratedPassenger":"","topSpeed":"190","vehicleManufacturingDate":"2019年09月29日"}}失败请求返回值示例{"code":3000,"status":400,"message":"识别失败", "serialNo":"411337047136010240"}八、通用的ERROR_MESSAGE九、服务支持若有疑问或更多产品需求（离线SDK、私有化部署等），可以通过技术文档、微信、热线电话等方式获得帮助，我们竭诚为您服务。
AXIS P1445-LE-3 车牌识别验证器套件说明书
DatasheetAXIS P1445-LE-3License Plate Verifier KitEasy,cost-effective kit for vehicle accessAXIS P1445-LE-3License Plate Verifier Kit consists of AXIS P1445-LE Network Camera and pre-installed AXIS License Plate Verifier analytics,making it an easy,cost-effective kit for automated vehicle entry and exit management.With edge storage and I/O ports,AXIS P1445-LE-3uses allow and block lists to accurately verify access to controlled areas such as parking lots.Furthermore,built-in support for AXIS A1001Network Door Controller makes it possible to expand the system and an open API allows for integration with third-party software.AXIS P1445-LE-3features OptimizedIR, impact resistance and a wide temperature range for installation in any environment.>Cost-effective standalone system>Single lane detection up to30km/h(19mph)>Allow and block lists for license plate verification>Day and night with OptimizedIR>Built-in support for Axis door controller and Axis I/O relay modulesAXIS License Plate VerifierApplicationComputeplatformEdgeLicenses AXIS License Plate Verifier license included.Configuration Web configuration includedSettings Define area of interest in scene.Allow-and blocklist logic.Barrier mode:Open to all,open to allowlisted,open to all butblocklisted.Minimum width:130pixels for one-row license plates;70pixelsfor two-row license plates.FIFO event log entries including thumbnail image of license plate.Up to1000entries on camera storage.Up to100000entriesonAXIS Surveillance Cards.Configurable retention time of stored eventsDetection range 2.0to7.0m(6.6to23ft)Vehicle speed Up to30km/h(19mph)Detection time Less than1second.ScenariosTypical applications Vehicle access controlIn Access control,the application monitors entrances and exits of gated areas such as parking areas.The application verifies detected license plates against an allowlist or a blocklist for granting or denying access to an area.Maximum 10,000license plates in each list.For a scenario where greater functionality and flexibilityare required,use AXIS A1001Network Door Controller.AXIS A1001with AXIS Entry Manager software supports access rules including schedules and a more detailed event log.Multiple partner software that support a great number of credentials and features are available.License plate recognition in slow speed trafficIn Freeflow,the application can detect and read license plates in slow speed traffic on larger access roads,city centers and enclosed areas like campuses,ports or airports.This allows for LPR-forensic search and LPR triggered events in a VMS such as ACS.System integrationApplicationProgrammingInterfaceOpen API for software integration.Event streaming Integrates with camera event management system to enableevent streaming to management software and camera actionssuch as I/O control,notification,and edge storage.Supported devices Direct integration with AXIS A1001Network Door Controller and AXIS A91Network I/O Relay Modules.GeneralSupported countries For a complete list of supported countries,go to the product page at Languages EnglishAXIS P1445-LE CameraImage sensor1/2.8”progressive scan RGB CMOSLens 2.8-8.5mm,F1.2Horizontal field of view:110˚-38˚Vertical field of view:62˚-21˚Varifocal,Remote focus and zoom,P-Iris control,IR correctedDay and night Automatically removable infrared-cut filterMinimum illumination HDTV1080p25/30fps with Forensic WDR and Lightfinder: Color:0.07lux,at50IRE F1.2;B/W:0.01lux,at50IRE F1.2 HDTV1080p50/60fps with Lightfinder:Color:0.14lux,at50IRE F1.2;B/W:0.03lux,at50IRE F1.2 0lux with IR illumination onSystem on chip(SoC)Model ARTPEC-6Memory1024MB RAM,512MB FlashVideoVideocompressionH.264(MPEG-4Part10/AVC)Baseline,Main and High ProfilesMotion JPEGResolution1920x1080to160x90Frame rate HDTV1080p(1920x1080)with WDR:Up to25/30FPS(50/60 HZ)in all resolutionsHDTV1080p(1920x1080)without WDR:Up to50/60FPS(50/60HZ)in all resolutionsVideo streaming Multiple,individually configurable streams in H.264and Motion JPEGAxis Zipstream technology in H.264Controllable frame rate and bandwidthVBR/ABR/MBR H.264Image settings Saturation,contrast,brightness,sharpness,Forensic WDR:Up to 120dB depending on scene,white balance,day/night threshold,exposure mode,exposure zones,compression,orientation:auto,0°,90°,180°,270°including Corridor Format,mirroring ofimages,dynamic text and image overlay,privacy masksPan/Tilt/Zoom Digital PTZAudioAudio streaming Audio in,simplexAudio encoding24bit LPCM,AAC-LC8/16/32/48kHz,G.711PCM8kHz,G.726ADPCM8kHz,Opus8/16/48kHzConfigurable bit rateAudio input/output External microphone input or line input Automatic gain controlNetworkSecurity Password protection,IP address filtering,HTTPS a encryption, IEEE802.1X(EAP-TLS)a network access control,digestauthentication,user access log,centralized certificatemanagement,brute force delay protection,signed firmwareSupported protocols IPv4,IPv6USGv6,ICMPv4/ICMPv6,HTTP,HTTPS a,HTTP/2,SSL/TLS a,QoS Layer3DiffServ,FTP,SFTP,CIFS/SMB,SMTP,mDNS (Bonjour),UPnP®,SNMP v1/v2c/v3(MIB-II),DNS/DNSv6,DDNS, NTP,RTSP,RTP,SRTP,TCP,UDP,IGMPv1/v2/v3,RTCP,ICMP, DHCPv4/v6,ARP,SOCKS,SSH,LLDP,CDP,MQTT v3.1.1,Syslog, Link-Local address(ZeroConf)System integrationApplication Programming Interface Open API for software integration,including VAPIX®and AXIS Camera Application Platform;specifications at One-click cloud connectionONVIF®Profile G,ONVIF®Profile S and ONVIF®Profile T,specifi-cation at Event conditions AnalyticsDetectors:live stream accessed,video motion detection,audiodetection,day/night mode,shock detection,tamperingHardware:network,temperatureInput Signal:digital input port,manual trigger,virtual inputsMQTT subscribeStorage:disruption,recordingSystem:system readyTime:recurrence,use scheduleEvent actions Record video:SD card and network shareUpload of images or video clips:FTP,SFTP,HTTP,HTTPS,networkshare and emailPre-and post-alarm video or image buffering for recording oruploadNotification:email,HTTP,HTTPS,TCP and SNMP trapPTZ:PTZ preset,start/stop guard tourOverlay text,external output activation,day/night modeMQTT publishData streaming Event dataBuilt-in installation aids Pixel counter,remote zoom(3x optical),remote focus,auto rotationAnalyticsApplications IncludedAXIS Motion Guard,AXIS Fence Guard,AXIS Loitering GuardAXIS License Plate VerifierGeneralCasing IP66/IP67-,NEMA4X-,and IK10-rated casingPolycarbonate blend and aluminiumColor:white NCS S1002-BSustainability PVC freePower Power over Ethernet IEEE802.3af/802.3at Type1Class3Typical:5.6W,max12.95WConnectors Shielded RJ4510BASE-T/100BASE-TX PoE3.5mm mic/line inI/O:4-pin terminal block for1alarm input and1outputIR illumination OptimizedIR with power-efficient,long-life850nm IR LEDs Storage Support for microSD/microSDHC/microSDXC cardSupport for SD card encryption(AES-XTS-Plain64256bit)Recording to network-attached storage(NAS)For SD card and NAS recommendations see Operatingconditions-40°C to60°C(-40°F to140°F)Maximum temperature according to NEMA TS2(2.2.7):74°C(165°F)Humidity10–100%RH(condensing)Storageconditions-40°C to65°C(-40°F to149°F)Humidity5-95%RH(non-condensing)Approvals EMCEN55032Class A,EN50121-4,IEC62236-4,EN55024,EN61000-6-1,EN61000-6-2,FCC Part15Subpart B Class A,ICES-003Class A,VCCI Class A,RCM AS/NZS CISPR32Class A,KCC KN32Class A,KN35SafetyIEC/EN/UL62368-1,IEC/EN/UL60950-22,IEC62471EnvironmentIEC60068-2-1,IEC60068-2-2,IEC60068-2-6,IEC60068-2-14,IEC60068-2-27,IEC60068-2-78,IEC/EN60529IP66/IP67,IEC/EN62262IK10,NEMA250Type4X,NEMA TS2(2.2.7-2.2.9)NetworkNIST SP500-267Weight With weather shield:1kg(2.2lb)DimensionsØ132x260mm(Ø53/16x101/4in)IncludedaccessoriesInstallation guide,Windows®decoder1-user license,drill holetemplate,connector kit,mounting bracketAXIS Weather Shield LOptionalaccessoriesAXIS T94F01M J-Box/Gang Box Plate,AXIS T91A47Pole Mount,AXIS T94P01B Corner Bracket,AXIS T94F01P Conduit Back Box,AXIS Weather Shield K,Axis PoE MidspansFor more accessories,see VideomanagementsoftwareAXIS Companion,AXIS Camera Station,video managementsoftware from Axis’Application Development Partners availableat /vmsLanguages English,German,French,Spanish,Italian,Russian,SimplifiedChinese,Japanese,Korean,Portuguese,Traditional Chinese Warranty5-year warranty,see /warrantya.This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit.(),and cryptographic software written by Eric Young (*****************).Environmental responsibility:/environmental-responsibility©2018-2021Axis Communications AB.AXIS COMMUNICATIONS,AXIS,ARTPEC and VAPIX are registered trademarks ofAxis AB in various jurisdictions.All other trademarks are the property of their respective owners.We reserve the right tointroduce modifications without notice.T10126239/EN/M21.2/2110。
车牌自动识别器DLL接口说明
车牌自动识别器DLL接口说明车牌识别系统DLL软件开发对外接口使用说明书目录第一章HVDLL.dll接口概述 (2)第二章对外接口函数详细说明 (3)1. 单个设备连接接口函数 (3)1.1. OpenHv (3)1.2. CloseHv (3)1.3. CloseIP (4)1.4. HvIsConnected (4)1.5. SetHvCallBack (4)1.6. CARINFO_BEGIN_CALLBACK (5)1.7. CARINFO_ END _CALLBACK (5)1.8. PLATE_NO_CALLBACK (6)1.9. BIG_IMAGE_CALLBACK (6)1.10. SMALL_IMAGE_CALLBACK (7)1.11. BINARY _IMAGE_CALLBACK (7)1.12. VIDEO _CALLBACK (8)1.13. VIDEO _ HISTORY_CALLBACK (9)1.14. STREAM_CALLBACK (9)1.15. DEBUG_STR_CALLBACK (10)1.16. SearchHVDeviceCount (10)1.17. GetHVDeviceAddr (11)1.18. SetHvIPFromMac (11)1.19. Yuv2Rgb (11)1.20. Yuv2BMP (12)1.21. Yuv2Jpg (12)1.22. HV_ForceSend (13)1.23. HV_ForceSendEx (13)1.24. HV_ GetPlateInfo (13)1.25. HV_ ProcessUserData (14)1.26. HV_ GetHistoryVideo (14)1.27. HV_CombineTwoImagesToOneImage (15)1.28. HV_AntiTamper_Embed (15)1.29. HV_AntiTamper_Examine (16)1.30. SendTriggerOut (16)1.31. SetHvTime (17)1.32. GetHvTime (17)2. 视频检测器接口函数 (17)2.1. TRIGGERINFO_CALLBACK (17)2.2. HV_GetStatInfo (18)3. 主动连接接口函数 (19)3.1. OpenHvServer (19)3.2. CloseHvServer (19)3.3. CONNECT_EVENT (19)3.4. DISCONNECT_EVENT (20)3.5. SetHvServerEvent (20)第三章应用系统开发说明 (20)第四章HVDLL编程指南 (24)1 编写回调函数 (24)2 创建句柄 (24)3 设置回调 (24)4 Timer事件 (25)5 取消回调 (25)6 关闭句柄 (26)HVDLL.dll接口概述HVDLL.dll是我公司车牌识别系统的核心接口，负责从识别器接收识别结果和视频信息，是各种接收应用程序的底层接口。
行驶证识别接口说明书
行驶证识别接口说明书文件更改摘要目录1.目的 02.适用范围 03.参考文档 04.术语 05.接口及数据定义 05.1.接口清单 05.2.行驶证识别接口 05.2.1.接口地址 05.2.2.请求方式 05.2.3.请求示例 05.2.4.请求参数说明 (1)5.2.5.返回参数说明 (1)5.2.6.data字段说明 (1)字段说明 (1)5.2.8.返回示例 (2)5.2.9.返回码描述 (2)1.目的编写本文档目的在于，说明程序系统的接口设计，为开发编码奠定基础。
2.适用范围本文档读者对象为项目经理、技术经理、开发人员。
3.参考文档无4.术语5.接口及数据定义5.1.接口清单5.2.行驶证识别接口5.2.1.接口地址https://5.2.2.请求方式post5.2.3.请求示例{"baseFile":""}5.2.4.请求参数说明5.2.5.返回参数说明5.2.6.data字段说明字段说明5.2.8.返回示例成功：{"status": "OK","data": {"name": "李昭烨","cardno": "闽D6N320","address": "福建厦门市湖里区钟宅村钟宅社8000号","issueDate": "20121231","vehicleType": "小型轿车","useCharacte": "非营运","model": "风神牌DFM7161G1B","vin": "LGJE1FE09CM132893","enginePN": "209334W","registerDate": "20121228"}}失败：{"status": "-101","info": "未找到上传的文件"}5.2.9.返回码描述。
车牌识别DLL接口说明
车牌识别仪DLL接口说明主要文件:TKLPNSVR.dll从属文件:JPGLIB.DLL,IJL15.DLL.这些文件必须与执行文件在同一目录,或者在系统目录下.主要接口说明//初始化1.void (WINAPI StartServer)(void);开始数据监听服务2. void(WINAPI ShowDlg)(void);显示系统配置对话框,该函数在调用StartServer函数后才能生效//释放3. void (WINAPI ExitServer)(void);退出数据监听服务//回调4. void (WINAPI SetCallback)(long caller,long userdata);设置回调,回调函数将接收终端传过来的数据和消息回调函数的参数为Void CALLBACK eipcalback(int cmdtype,char *ip,char *rectime,char *lpn,char *imgfile,BYTE*imgdata,int imgsize,RECT *lpnpos,long userdata);Cmdtype,调用的类型,0表示一般的提示信息,1表示图片和车牌信息接收Ip,当cmdtype=1时表示,发送的终端的IP地址,否则表示一般的提示信息内容Cmdtype=2时表示,在配置对话框中修改了保存图片的路径,ip为路径的名称.Cmdtype=3时表示,表示自动搜索终端设备,IP不为空时表示找到了地址为ip的设备.lpn表示搜索的进度如’80’表示进度的80%.当cmdtype=1 时Rectime,时间串,格式为yyyy-mm-dd hh:mm:ssLpn,表示车牌号码Imgfile表示存储的文件名称(JPG格式),如果不自动保存图片,则该值为空Imgdata,JPG格式的图片内存地址Imgsize,图片的内存尺寸大小Lpnpos,车牌的坐标区域Userdata,用户自定义数据;//播放指定IP地址的终端实时视频5.void (WINAPI PlayRealVideo)(char *ip,long hdc, RECT where);ip:指定要播放的终端IP地址hdc:指定要播放的句柄where:指定在什么位置播放struct RECT{Int .eft,top,bottom,right;}6. int RequestVideoStream(char *ip ,int mode );设置终端是否发送实时视频给接收端,Ip:指定是何终端Mode:0,表示不播放,1 表示播放返回1表示设置成功7. int TriggerCapture(char *ip);在接收端手动触发终端进行图片的抓拍与识别Ip:指定是何终端返回1表示发送命令成功;典型的设备连接图附ActiveX接口说明文件名Tkeip.ocx,与前篇DLL文件置于同一目录下.1.StartEIPServer()开始数据监听,在调用以下函数前,必须先调用函数2.ExitEIPServer()退出监听3.PlayEIPVideo(LPCTSTR ip, long wheretoshow,long x1,long y1,long x2,long y2 )在上位机上播放视频流,Ip为终端的地址,Whereshow为一个HDC句柄,申请后记得自行释放X1,y1,x2,y2,在什么位置播放.分别表示左上角坐标,和右下角坐标.4.HandCapture (LPCTSTR ip);手动抓拍指定IP地址的终端5.ForceDSPVideo(LPCTSTR ip, long mode);指定终端是否发送实时视频Mode=0表示停止,=1表示发送Ip为终端地址6.ShowEIPDlg()显示终端配管理对话框,这个函数需在StartEIPServer执行后才能生效.Send232(LPCTSTR ip,long data,long datalen)发送rs232 指令到LED显示屏ip,终端地址data,要发送的数据（byte 数组）起始地址datalen,数据长度Send485(LPCTSTR ip,long data,long datalen).发送Rs485指令到LED显示屏ip,终端地址data,要发送的数据（byte 数组）起始地址datalen,数据长度PlaySound(LPCTSTR ip,short cmdtype,short flag,LPCTSTR data)播放语音ip,终端地址cmdtype,播放的类型，0:表示一般提示性语音，具体是什么，看flag的值1:表示播放车牌2.表示播放费用;flag ,播放的内容标记，对于提示性的语音具体的播放内容将参考该值；0,欢迎光临-1,此卡已过期2.此卡将过期3.此卡余额不足4.此卡已入场5.此卡被禁用6.此卡无效7.此卡未入场12.请交费28.祝您一路顺风事件Private Sub Tkeip1_ImageReceive(rectime As String, ip As String, lpn As String, filename As String, ByVal imgdata As Long, ByVal imgsize As Long)Rectime接收的时间Ip 终端IP地址Lpn 车牌号Filename,文件名Imgdata jpg图片内存地址Imgsize jpg图片大小原始的SOCKET 协议1.数据结果(采用TCP/IP),端口10086(delphi型声明)type TReceiveData = recordiP: array[0..24] of char;datetime: array[0..6] of byte; //年月日时分秒lpn: array[0..24] of char;lpnpos: TRect; // array[0..48] of char; //车牌坐标;jpgsize: integer; //大小;state: integer; //报警状态;end;紧跟着是jpgsize大小的jpeg图像(C型声明)Struct CReceiveData{Char ip[25];BYTE datetime[7];Char lpn[25];RECT lpnpos;Int jpgsize;Int state;};注意,lpn是一个utf8编码的字符串,要转成ansi才能正常显示.紧跟着是jpgsize大小的jpeg图像2.实时JPEG图像流(采用UDP协议传输),服务端口10089(delphi型声明)type TudpFrame = recordframeno: integer;segno: integer;jpgsize: integer;segcount: integer;segsize: integer;jobsize: integer;jpgstream: array[0..511] of byte;end;(C型声明)Struct CudpFrame{ int frameno;Int segno;Int jpgsize;Int segcount;Int segsize;Int jobsize;BYTE jpgstream[512] ;};Segsize表示当前udp帧的大小只有当jpgsize=所有接收的segsize之后,而且segno=segcount表示完整的一帧JPEG图像接收完成!。
驾照识别技术
驾照识别技术五一小长假即将到来，预备自驾出行的人比比皆是。
但是一到旅游旺季黄金路段就将迎来车流高峰期和事故高发期，这一状况让不少人对自驾游表示担忧。
所以各地交警部门都使出浑身解数，只为了保障旅游线路的畅通，让游客有个美好的出行体验。
其中就有些地方的交警利用驾驶证识别SDK等技术促进智能交通管理，来提高交警的办公效率，以便让游客在出行过程更轻松、惬意。
那么传说中的驾驶证识别是怎样为人民服务的呢？那么接下来笔者就以云脉驾驶证识别SDK为例，为大家详细介绍一下吧。
什么是驾照识别软件驾照识别是一款基于android和PC平台的驾照识别软件，通过手机端的相机进行驾照拍摄，利用OCR技术自动识别驾照上的内容信息，将识别后的内容分组归类，存入手机端或同步服务器，避免繁琐的手工录入，提高信息录入的工作效率，同时也可对证件图像进行头像照片切割处理。
如此方便快捷的功能如此强大的驾照识别软件，那么驾照识别具体有什么优点呢？让我们以目前市场上人气比较高的云脉驾照识别软件为例：驾照识别产品介绍：1. 当有大量驾照的时候，支持全局搜索，独有的排序模式，帮助您全面掌控行驶证资源2. 自定义管理群组，针对不同重要行驶证信息详细分类3. 精确识别驾照上的信息内容，可随意进行修改或增加驾照内容4. 驾照图片数据清晰存储，可备注重要信息5. 驾照识别SDK支持IOS、安卓、WINDOWS及服务端平台驾照识别特点：1. 支持多平台：安卓、PC及服务器版本2. 快速高效，采集识读一张证件2-3秒钟3. 识别精度高，驾驶证识别栏目识别率可达80%以上，字符识别率可达92%以上4. 识别引擎小(仅为5MB)，可提供成熟的驾照识别OCR SDK，集成简单易用。
KuaiLai司机接口说明书
KuaiLai 司机接口说明书版本1.0修改人汪熙日期2017-04-24说明创建目1录序言 ................................................................................................................................................................3 1.1 1.2 1.3 概述 ................................................................................................................................................3 适用读者 ........................................................................................................................................3 参考文档 ........................................................................................................................................32接口说明 ........................................................................................................................................................4 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 司机登录 ........................................................................................................................................4 忘记密码 ........................................................................................................................................5 验证码验证 ....................................................................................................................................5 获取物流分配单 ............................................................................................................................6 获取物流分配单详情.....................................................................................................................6 获取订单详情信息.........................................................................................................................7 执行物流分配单发货.....................................................................................................................8 查询物流分配单…….....................................................................................................................8 订单完成操作……...……………………………………………………………………………..9 分配单取货……...…...……………………………………………………………...……………91 序言概述 1. 2. 3. 该接口主要用户送货司机 APP 操作 接口是平台重要的组成部分。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
5.2.6.data字段说明3
字段说明3
5.2.8.返回示例3
5.2.9.返回码描述4
1.
编写本文档目的在于，说明程序系统的接口设计，为开发编码奠定基础。
ห้องสมุดไป่ตู้2.
本文档读者对象为项目经理、技术经理、开发人员。
3.
无
4.
名词
定 义
JSON
专门为浏览器中的网页上运行的JavaScript代码而设计的一种数据格式
string
是
正确返回数据
info
string
否
错误返回说明
5.2.6.
名称
类型
说明
name
string
姓名
cardno
string
证号
sex
string
性别
birthday
string
出生日期
address
string
领地
issueDate
string
初始领证日期
nation
string
国籍
drivingType
5.
5.1.
序号
名称
说明
责任人
修改人
备注
1
驾驶证识别接口
提供驾驶证识别
5.2.
5.2.1.
5.2.2.
post
5.2.3.
{
"baseFile":""
}
5.2.4.
名称
类型
必填
说明
baseFile
String
是
Base64位图片字符串
5.2.5.
名称
类型
必填
说明
status
string
是
返回码
data
}
}
失败：
{
"status": "-101",
"info": "未找到上传的文件"
}
5.2.9.
名称
返回码
说明
status
OK
成功
status
-101
未找到上传的文件
status
-102
上传图片过大（文件超过5M）
status
-110
识别失败：1.识别引擎出现异常，2.图片模糊或曝光等原因造成引擎无法识别出图片的内容
string
准驾车型
registerDate
String
有效起始日期
validPeriod
string
有效期限
5.2.7.
名称
类型
说明
info
string
返回错误对应的信息
5.2.8.
成功：
{
"status": "OK",
"data": {
"name": "高海涛",
"cardno": "",
"sex": "男",
驾驶证识别接口说明书
文件更改摘要
日期
版本号
修订说明
修订人
审核人
批准人
2018.12.14
V1.1
新增
1.目的1
2.适用范围1
3.参考文档1
4.术语1
5.接口及数据定义1
5.1.接口清单1
5.2.驾驶证识别接口2
5.2.1.接口地址2
5.2.2.请求方式2
5.2.3.请求示例2
5.2.4.请求参数说明2
"birthday": "1974年09月18日",
"address": "河南省孟津县城关镇文化路体委家属院",
"issueDate": "2004-06-14",
"nation": "中国",
"drivingType": "B1E",
"registerDate": "2010-06-14",
"validPeriod": "10年"