Device Network SDK (ANPR) - Developer Guide - V6.1.0.X - 20230330
Device Network SDK (ANPR) - Developer Guide - V6.1.0.X - 20230330
Developer Guide
Device Network SDK (ANPR) Developer Guide
Legal Information
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE DOCUMENT IS PROVIDED "AS IS"
AND "WITH ALL FAULTS AND ERRORS". OUR COMPANY MAKES NO REPRESENTATIONS OR
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. IN NO EVENT
WILL OUR COMPANY BE LIABLE FOR ANY SPECIAL, CONSEQUENTIAL, INCIDENTAL, OR INDIRECT
DAMAGES, INCLUDING, AMONG OTHERS, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS
INTERRUPTION OR LOSS OF DATA, CORRUPTION OF SYSTEMS, OR LOSS OF DOCUMENTATION,
WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, IN
CONNECTION WITH THE USE OF THE DOCUMENT, EVEN IF OUR COMPANY HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES OR LOSS.
i
Device Network SDK (ANPR) Developer Guide
Contents
Chapter 1 Overview .................................................................................................................... 1
1.1 Introduction ........................................................................................................................... 1
1.2 Update History ....................................................................................................................... 1
Chapter 2 Configure ANPR Alarm ................................................................................................ 2
Chapter 3 Configure Blocklist and Allowlist ANPR Alarm ............................................................. 6
Chapter 4 Control Barrier Gate Status ....................................................................................... 11
Chapter 5 Alarm/Event Receiving ............................................................................................. 13
5.1 Receive Alarm/Event in Arming Mode ................................................................................. 13
5.2 Receive Alarm/Event in Listening Mode .............................................................................. 16
Chapter 6 API Reference ........................................................................................................... 20
6.1 NET_DVR_GetDeviceAbility ................................................................................................. 20
6.2 NET_DVR_GetDeviceConfig ................................................................................................. 21
6.3 NET_DVR_GetDownloadState .............................................................................................. 22
6.4 NET_DVR_GetSTDAbility ...................................................................................................... 22
6.5 NET_DVR_GetSTDConfig ...................................................................................................... 23
6.6 NET_DVR_GetUploadState .................................................................................................. 24
6.7 NET_DVR_RemoteControl ................................................................................................... 26
6.8 NET_DVR_SetDeviceConfig .................................................................................................. 27
6.9 NET_DVR_SetSTDConfig ...................................................................................................... 28
6.10 NET_DVR_STDXMLConfig ................................................................................................... 29
6.11 NET_DVR_StartDownload .................................................................................................. 30
6.12 NET_DVR_StopDownload .................................................................................................. 31
6.13 NET_DVR_UploadClose ...................................................................................................... 31
6.14 NET_DVR_UploadFile_V40 ................................................................................................ 32
6.15 NET_DVR_Cleanup ............................................................................................................. 33
6.16 NET_DVR_GetErrorMsg ..................................................................................................... 33
ii
Device Network SDK (ANPR) Developer Guide
iii
Device Network SDK (ANPR) Developer Guide
iv
Device Network SDK (ANPR) Developer Guide
v
Device Network SDK (ANPR) Developer Guide
vi
Device Network SDK (ANPR) Developer Guide
vii
Device Network SDK (ANPR) Developer Guide
viii
Device Network SDK (ANPR) Developer Guide
ix
Device Network SDK (ANPR) Developer Guide
Chapter 1 Overview
This manual provides the integration methods and processes based on HCNetSDK for ANPR
(Automatic Number Plate Recognition) applications.
1.1 Introduction
The ANPR (Automatic Number Plate Recognition) applications integrated by private protocol help
to analyze and recognize the vehicle license plate, and support importing the blocklist or allowlist
to trigger license plate recognition alarms. In addition, for some entrance and exit devices, you can
also control the barrier gate remotely by calling APIs.
1
Device Network SDK (ANPR) Developer Guide
2
Device Network SDK (ANPR) Developer Guide
Steps
3
Device Network SDK (ANPR) Developer Guide
Note
You can also configure the triggering mode and arming schedule for ANPR alarm by logging in to
device via web browser.
6. Optional: Configure parameters to display license plate information on alarm picture.
1) Optional: Call NET_DVR_GetDeviceConfig with "NET_ITS_GET_OVERLAP_CFG_V50"
(command No.: 5055) and set the input buffer (lpInBuffer) to the structure
NET_ITS_OVERLAPCFG_COND for getting the configured or existing overlay parameters for
reference.
The overlay parameters are returned by the output buffer (lpOutBuffer) in the structure of
NET_ITS_OVERLAP_CFG_V50 .
2) Call NET_DVR_SetDeviceConfig with "NET_ITS_SET_OVERLAP_CFG_V50" (command No.:
5056), set the input buffer (lpInBuffer) to the structure NET_ITS_OVERLAPCFG_COND , and
set the input parameter (lpInParamBuffer) to the structure NET_ITS_OVERLAP_CFG_V50 for
setting the parameters to display license plate information on alarm picture.
4
Device Network SDK (ANPR) Developer Guide
Note
To check whether the device supports filtering duplicated license plates, you can call
NET_DVR_STDXMLConfig to transmit /ISAPI/Traffic/channels/<ID>/capabilities by GET
method. The capability will be returned in the message JSON_Filtration by lpOutputParam. If it
supports, the node <isSupportFiltration> will be in the capability message and its value is "true".
8. Optional: Receive ANPR alarm in arming mode (see Receive Alarm/Event in Arming Mode ) or
listening mode (see Receive Alarm/Event in Listening Mode ) when alarm is triggered.
Note
The command (lCommand) to receive ANPR alarms should be set to
"COMM_ITS_PLATE_RESULT" (command No.: 0x3050) or "COMM_UPLOAD_PLATE_RESULT"
(command No.: 0x2800) in the alarm callback function MSGCallBack .
For alarm details, refer to XML_EventNotificationAlert_ANPR returned in the field pXmlBuf of
NET_DVR_PLATE_INFO in the structure NET_ITS_PLATE_RESULT or NET_DVR_PLATE_RESULT .
What to do next
Call NET_DVR_Logout and NET_DVR_Cleanup to log out from device and release resources.
5
Device Network SDK (ANPR) Developer Guide
6
Device Network SDK (ANPR) Developer Guide
Steps
Figure 3-1 Programming Flow of Configuring Blocklist and Allowlist ANPR Alarm
7
Device Network SDK (ANPR) Developer Guide
1. Optional: Get intelligent traffic capability to check if the following functions are supported.
- Call NET_DVR_GetDeviceAbility , set the capability type (dwAbilityType) to
"DEVICE_ABILITY_INFO" (0x011), and set the input parameter pointer (pInbuf) to the message
XML_Desc_ITDeviceAbility .
The intelligent traffic capability is returned in the message of XML_ITDeviceAbility , and the
related node is <ITCAbility>.
- Call NET_DVR_STDXMLConfig to pass through the request URL: GET /ISAPI/ITC/capability .
The intelligent traffic capability is returned in the message XML_ITCCap by lpOutBuffer of
lpOutputParam.
2. Optional: Call NET_DVR_GetDeviceConfig with "NET_DVR_GET_TRIGGEREX_CFG" (command
No.: 5074) and set the input buffer (lpInBuffer) to the structure NET_DVR_TRIGGER_COND for
getting the configured or existing triggering mode of blocklist and allowlist ANPR alarm for
reference.
The triggering mode parameters are returned by the output buffer (lpOutBuffer) in the structure
of NET_ITC_TRIGGERCFG .
3. Call NET_DVR_SetDeviceConfig with "NET_DVR_SET_TRIGGEREX_CFG" (command No.: 5075),
set the input buffer (lpInBuffer) to the structure NET_DVR_TRIGGER_COND , and set the input
parameter (lpInParamBuffer) to the structure NET_ITC_TRIGGERCFG for setting the triggering
mode.
4. Optional: Configure parameters to display license plate information on alarm picture.
1) Optional: Call NET_DVR_GetDeviceConfig with "NET_ITS_GET_OVERLAP_CFG_V50"
(command No.: 5055) and set the input buffer (lpInBuffer) to the structure
NET_ITS_OVERLAPCFG_COND for getting the configured or existing overlay parameters for
reference.
The overlay parameters are returned by the output buffer (lpOutBuffer) in the structure of
NET_ITS_OVERLAP_CFG_V50 .
2) Call NET_DVR_SetDeviceConfig with "NET_ITS_SET_OVERLAP_CFG_V50" (command No.:
5056), set the input buffer (lpInBuffer) to the structure NET_ITS_OVERLAPCFG_COND , and
set the input parameter (lpInParamBuffer) to the structure NET_ITS_OVERLAP_CFG_V50 for
setting the parameters to display license plate information on alarm picture.
5. Call NET_DVR_StartDownload with "NET_SDK_DOWNLOAD_VEHICLE_BLOCKALLOWLIST_FILE"
(command No.: 7) to download the blocklist and allowlist template.
6. Call NET_DVR_UploadFile_V40 with "UPLOAD_VEHICLE_BLOCKALLOWLIST_FILE" (command
No.: 13) to import the blocklist and allowlist information filled in the template.
7. Optional: Call NET_DVR_STDXMLConfig to pass through the request URL: POST /ISAPI/Traffic/
channels/<ID>/searchLPListAudit and set lpInBuffer of lpInputParam to the message
XML_LPListAuditSearchDescription to search for the configured or existing blocklist or allowlist.
8. Configure arming schedule for blocklist ANPR alarm or allowlist ANPR alarm.
- Configure arming schedule for blocklist ANPR alarm
a. Call NET_DVR_GetSTDConfig with "NET_DVR_GET_VEHICLE_BLOCKLIST_SCHEDULE"
(command No: 6622) to get the configured or existing arming schedule of blocklist ANPR
alarm for reference.
8
Device Network SDK (ANPR) Developer Guide
Note
The arming schedule parameters ( NET_DVR_EVENT_SCHEDULE ) are returned by the
output buffer (lpOutBuffer) of structure NET_DVR_STD_CONFIG .
b. Call NET_DVR_SetSTDConfig with "NET_DVR_SET_VEHICLE_BLOCKLIST_SCHEDULE"
(command No.: 6623) and set the input buffer (lpInBuffer) of structure
NET_DVR_STD_CONFIG to NET_DVR_EVENT_SCHEDULE for setting arming schedule.
- Configure arming schedule for allowlist ANPR alarm
a. Call NET_DVR_GetSTDConfig with "NET_DVR_GET_VEHICLE_ALLOWLIST_SCHEDULE"
(command No: 6624) to get the configured or existing arming schedule of allowlist ANPR
alarm for reference.
Note
The arming schedule parameters ( NET_DVR_EVENT_SCHEDULE ) are returned by the
output buffer (lpOutBuffer) of structure NET_DVR_STD_CONFIG .
b. Call NET_DVR_SetSTDConfig with "NET_DVR_SET_VEHICLE_ALLOWLIST_SCHEDULE"
(command No.: 6625) and set the input buffer (lpInBuffer) of structure
NET_DVR_STD_CONFIG to NET_DVR_EVENT_SCHEDULE for setting arming schedule.
9. Optional: Call NET_DVR_GetSTDAbility , set the dwAbilityType to
"NET_DVR_GET_EVENT_TRIGGERS_CAPABILITIES" (value: 3501), and set condition parameter
lpCondBuffer in the structure of NET_DVR_STD_ABILITY to "NULL" for getting the configuration
capability of blocklist and allowlist ANPR alarm linkage.
The configuration capability is returned in the message XML_EventTriggersCap by the output
parameter lpOutBuffer in the structure of NET_DVR_STD_ABILITY .
10. Configure linkage action for blocklist ANPR alarm or allowlist ANPR alarm.
- Configure linkage action for blocklist ANPR alarm
a. Call NET_DVR_GetSTDConfig with "NET_DVR_GET_VEHICLE_BLOCKLIST_EVENT_TRIGGER"
(command No.: 6626) to get the configured or existing linkage action of blocklist ANPR
alarm for reference.
Note
The linkage action parameters ( NET_DVR_EVENT_TRIGGER ) are returned by the output
buffer (lpOutBuffer) of structure NET_DVR_STD_CONFIG .
b. Call NET_DVR_SetSTDConfig with "NET_DVR_SET_VEHICLE_BLOCKLIST_EVENT_TRIGGER"
(command No.: 6627) and set the input buffer (lpInBuffer) of structure
NET_DVR_STD_CONFIG to NET_DVR_EVENT_TRIGGER for setting linkage action.
- Configure linkage action for allowlist ANPR alarm
a. Call NET_DVR_GetSTDConfig with "NET_DVR_GET_VEHICLE_ALLOWLIST_EVENT_TRIGGER"
(command No.: 6628) to get the configured or existing linkage action of allowlist ANPR
alarm for reference.
9
Device Network SDK (ANPR) Developer Guide
Note
The linkage action parameters ( NET_DVR_EVENT_TRIGGER ) are returned by the output
buffer (lpOutBuffer) of structure NET_DVR_STD_CONFIG .
b. Call NET_DVR_SetSTDConfig with "NET_DVR_SET_VEHICLE_ALLOWLIST_EVENT_TRIGGER"
(command No.: 6629) and set the input buffer (lpInBuffer) of structure
NET_DVR_STD_CONFIG to NET_DVR_EVENT_TRIGGER for setting linkage action.
11. Optional: Receive blocklist and allowlist ANPR alarm in arming mode (see Receive Alarm/Event
in Arming Mode ) or listening mode (see Receive Alarm/Event in Listening Mode ) when alarm
is triggered.
Note
● The commands (lCommand) to receive blocklist and allowlist ANPR alarms should be set to
"COMM_VEHICLE_CONTROL_ALARM" (command No.: 0x3059) in
NET_DVR_SetDVRMessageCallBack_V50 and NET_DVR_StartListen_V30 .
● For alarm details, refer to the structure of NET_DVR_VEHICLE_CONTROL_ALARM .
What to do next
Call NET_DVR_Logout and NET_DVR_Cleanup to log out from device and release resources.
10
Device Network SDK (ANPR) Developer Guide
Steps
11
Device Network SDK (ANPR) Developer Guide
What to do next
Call NET_DVR_Logout and NET_DVR_Cleanup to log out from device and release resources.
12
Device Network SDK (ANPR) Developer Guide
● Make sure you have configured the alarm/event parameters, refer to the typical alarm/event
13
Device Network SDK (ANPR) Developer Guide
Steps
Note
● If the configured alarm is triggered or event occurred, the alarm/event information will be
uploaded by device and returned in the callback function. You can view the alarm/event and
do some processing operations.
● For the integration via device network SDK (HCNetSDK), to receive different types of alarm/
event information, the parameter lCommand (data type to be uploaded) in the configured
callback function should be different (refer to the typical alarm/event configurations). For the
integration via text protocol, the lCommand should be set to "COMM_ISAPI_ALARM"
(command No.: 0x6009) and the input parameter pAlarmInfo in the callback function
MSGCallBack should be set to NET_DVR_ALARM_ISAPI_INFO .
2. Call NET_DVR_SetupAlarmChan_V50 to set up uploading channel.
3. Call NET_DVR_CloseAlarmChan_V30 to close uploading channel and stop receiving alarm or
event information.
Example
Sample Code of Receiving Alarm or Event in Arming Mode
14
Device Network SDK (ANPR) Developer Guide
#include <stdio.h>
#include <iostream>
#include "Windows.h"
#include "HCNetSDK.h"
using namespace std;
void main() {
//---------------------------------------
// Initialize
NET_DVR_Init();
//Set connection time and reconnection time
NET_DVR_SetConnectTime(2000, 1);
NET_DVR_SetReconnect(10000, true);
//---------------------------------------
// Log in to device
LONG lUserID;
//Login parameters, including device IP address, user name, password, and so on.
NET_DVR_USER_LOGIN_INFO struLoginInfo = {0};
struLoginInfo.bUseAsynLogin = 0; //Synchronous login mode
strcpy(struLoginInfo.sDeviceAddress, "192.0.0.64"); //Device IP address
struLoginInfo.wPort = 8000; //Service port No.
strcpy(struLoginInfo.sUserName, "admin"); //User name
strcpy(struLoginInfo.sPassword, "abcd1234"); //Password
//Device information, output parameter
NET_DVR_DEVICEINFO_V40 struDeviceInfoV40 = {0};
lUserID = NET_DVR_Login_V40(&struLoginInfo, &struDeviceInfoV40);
if (lUserID < 0)
{
printf("Login failed, error code: %d\n", NET_DVR_GetLastError());
NET_DVR_Cleanup();
return;
}
//Enable arming
NET_DVR_SETUPALARM_PARAM_V50 struSetupParamV50={0};
struSetupParamV50.dwSize=sizeof(NET_DVR_SETUPALARM_PARAM_V50);
//Alarm category to be uploaded
struSetupParamV50.byAlarmInfoType=1;
//Arming level
struSetupParamV50.byLevel=1;
15
Device Network SDK (ANPR) Developer Guide
//Arm
lHandle = NET_DVR_SetupAlarmChan_V50(lUserID, &struSetupParamV50, NULL, strlen(szSubscribe));
}
else
{
//Subscribe
LlHandle = NET_DVR_SetupAlarmChan_V50(lUserID, &struSetupParamV50, szSubscribe, strlen(szSubscribe));
}
if (lHandle < 0)
{
printf("NET_DVR_SetupAlarmChan_V50 error, %d\n", NET_DVR_GetLastError());
NET_DVR_Logout(lUserID);
NET_DVR_Cleanup();
return;
}
Sleep(20000);
//Disarm the uploading channel
if (!NET_DVR_CloseAlarmChan_V30(lHandle))
{
printf("NET_DVR_CloseAlarmChan_V30 error, %d\n", NET_DVR_GetLastError());
NET_DVR_Logout(lUserID);
NET_DVR_Cleanup();
return;
}
//Log out
NET_DVR_Logout(lUserID);
//Release resources
NET_DVR_Cleanup();
return;
}
What to do next
Call NET_DVR_Logout and NET_DVR_Cleanup to log out and release resources.
● Make sure you have configured the alarm/event parameters, refer to the typical alarm/event
16
Device Network SDK (ANPR) Developer Guide
Steps
17
Device Network SDK (ANPR) Developer Guide
Note
For the integration via device network SDK (HCNetSDK), to receive different types of alarm/
event information, the parameter lCommand (data type to be uploaded) in the configured
callback function should be different (refer to the typical alarm/event configurations). For the
integration via text protocol, the lCommand should be set to "COMM_ISAPI_ALARM" and the
input parameter pAlarmInfo in the callback function MSGCallBack should be set to
NET_DVR_ALARM_ISAPI_INFO .
The alarm/event information is automatically uploaded by the device when the configured
alarm is triggered or event occurred, and the third-party platform or system gets the alarm/
event information from the configured callback function.
5. Call NET_DVR_StopListen_V30 to stop listening and receiving alarm or event information.
Example
Sample Code of Receiving Alarm/Event in Listening Mode
#include <stdio.h>
#include <iostream>
#include "Windows.h"
#include "HCNetSDK.h"
using namespace std;
void main() {
//---------------------------------------
// Initialize
NET_DVR_Init();
//Set connection time and reconnection time
NET_DVR_SetConnectTime(2000, 1);
NET_DVR_SetReconnect(10000, true);
//---------------------------------------
// Log in to device
LONG lUserID;
NET_DVR_DEVICEINFO_V30 struDeviceInfo;
lUserID = NET_DVR_Login_V30("172.0.0.100", 8000, "admin", "12345", &struDeviceInfo);
if (lUserID < 0)
{
printf("Login error, %d\n", NET_DVR_GetLastError());
NET_DVR_Cleanup();
return;
}
//Enable listening
LONG lHandle;
lHandle = NET_DVR_StartListen_V30(NULL,7200, MessageCallback, NULL);
if (lHandle < 0)
{
printf("NET_DVR_StartListen_V30 error, %d\n", NET_DVR_GetLastError());
NET_DVR_Logout(lUserID);
NET_DVR_Cleanup();
return;
}
Sleep(5000);
18
Device Network SDK (ANPR) Developer Guide
//Disable listening
if (!NET_DVR_StopListen_V30(lHandle))
{
printf("NET_DVR_StopListen_V30 error, %d\n", NET_DVR_GetLastError());
NET_DVR_Logout(lUserID);
NET_DVR_Cleanup();
return;
}
//Log out
NET_DVR_Logout(lUserID);
//Release SDK resource
NET_DVR_Cleanup();
return;
}
What to do next
Call NET_DVR_Logout (if logged in) and NET_DVR_Cleanup to log out and release resources.
19
Device Network SDK (ANPR) Developer Guide
6.1 NET_DVR_GetDeviceAbility
Get the device capabilities.
API Definition
BOOL NET_DVR_GetDeviceAbility(
LONG lUserID,
DWORD dwAbilityType,
char *pInBuf,
DWORD dwInLength,
char *pOutBuf,
DWORD dwOutLength
);
Parameters
lUserID
[IN] Value returned by NET_DVR_Login_V40 .
dwAbilityType
[IN] Capability types, which are different according to different devices and functions.
pInBuf
[IN] Input parameter buffer pointer, which are different according to different devices and
functions, and they are returned in the structure or messages.
dwInLength
[IN] Size of input buffer.
pOutBuf
[OUT] Output parameter buffer pointer, which are different according to different devices and
functions, and they are returned in the structure or messages.
dwOutLength
[OUT] Size of buffer for receiving data.
Return Values
Returns TRUE for success, and returns FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
20
Device Network SDK (ANPR) Developer Guide
6.2 NET_DVR_GetDeviceConfig
Get device configuration information in batch (with sending data).
API Definition
BOOL NET_DVR_GetDeviceConfig(
LONG lUserID,
DWORD dwCommand,
DWORD dwCount,
LPVOID lpInBuffer,
DWORD dwInBufferSize,
LPVOID lpStatusList,
LPVOID lpOutBuffer,
DWORD dwOutBufferSize
);
Parameters
lUserID
[IN] Value returned by NET_DVR_Login_V40 .
dwCommand
[IN] Device getting commands. The commands are different for different getting functions.
dwCount
[IN] Number of configurations (cameras) to get at a time. 0, 1-one camera, 2-two cameras, 3-
three cameras, and so on. Up to 64 cameras' configuration information can be obtained at a
time.
lpInBuffer
[IN] Pointer of configuration condition buffer, which specifies the number (dwCount) of
configurations to get, and relates to the getting commands.
dwInBufferSize
[IN] Size of configuration condition buffer, which saves the obtained configuration information
(the number is dwCount).
lpStatusList
[OUT] Error information list, and its memory is allocated by user, each error information
contains 4 bytes (a unsigned 32-bit integer).
There is a one-to-one correspondence between the errors in the list and the cameras need to
search, e.g., lpStatusList[2] corresponds to lpInBuffer[2].
If the parameter value is 0 or 1, it refers to getting succeeded, otherwise, this parameter value is
the error code.
lpOutBuffer
21
Device Network SDK (ANPR) Developer Guide
[OUT] Parameters returned by device, which relates to the getting commands. And there is a
one-to-one correspondence between the parameters and the cameras need to search.
If the lpStatusList of one camera is larger than 1, the corresponding lpOutBuffer is invalid.
dwOutBufferSize
[IN] Total size of returned results (the number is dwCount).
Return Values
Returns TRUE for success, and returns FALSE for failure. If returns TRUE, it does not mean that all
configurations are obtained, you can check the value of lpStatusList[n] to judge which one is
succeeded.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
See Also
NET_DVR_SetDeviceConfig
6.3 NET_DVR_GetDownloadState
Get the file downloading progress and status.
API Definition
LONG NET_DVR_GetDownloadState(
LONG lDownloadHandle,
DWORD *pProgress
);
Parameters
lDownloadHandle
[IN] Handle for downloading files, which is returned by NET_DVR_StartDownload .
pProgress
[OUT] Returned progress value, which is ranging from 1 to 100.
Return Values
Returns -1 for calling failed, and returns other values as the downloading status codes: 1-
Downloaded, 2-Downloading, 3-Downloading Failed, 4-Network Disconnected, Unknown Status.
If returning failed, you can call NET_DVR_GetLastError to get the error code.
6.4 NET_DVR_GetSTDAbility
Get the device capabilities.
22
Device Network SDK (ANPR) Developer Guide
API Definition
BOOL NET_DVR_GetSTDAbility(
LONG lUserID,
DWORD dwAbilityType,
NET_DVR_STD_ABILITY lpAbilityParam
);
Parameters
lUserID
[IN] Value returned by NET_DVR_Login_V40 .
dwAbilityType
[IN] Capability types, which are different according to different functions.
lpAbilityParam
[IN/OUT] Capability details, including condition parameter, input parameter, output parameter,
and so on (see details in the structure NET_DVR_STD_ABILITY ), which are different according
to different capability types.
Return Values
Returns TRUE for success, and returns FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
6.5 NET_DVR_GetSTDConfig
Get the device configuration information.
API Definition
BOOL NET_DVR_GetSTDConfig(
LONG lUserID,
DWORD dwCommand,
NET_DVR_STD_CONFIG lpConfigParam
);
Parameters
lUserID
[IN] Value returned by NET_DVR_Login_V40 .
dwCommand
[IN] Device configuration commands, which are different according to different configuration
functions.
lpConfigParam
23
Device Network SDK (ANPR) Developer Guide
[IN][OUT] Set input and output parameters, which are different according to different
configuration functions. For different configuration functions, the lpCondBuffer and lpOutBuffer
in the IpConfigParam are also different. See the structure NET_DVR_STD_CONFIG for details.
Note
When getting configuration parameters, the lpInBuffer in the lpConfigParam is invalid, you can
set it to NULL.
Return Values
Returns TRUE for success, and returns FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
See Also
NET_DVR_SetSTDConfig
6.6 NET_DVR_GetUploadState
Get the file uploading progress and status.
API Definition
LONG NET_DVR_GetUploadState(
LONG lUploadHandle,
DWORD *pProgress
);
Parameters
lUploadHandle
[IN] Handling for uploading files, which is returned by NET_DVR_UploadFile_V40 .
pProgress
[OUT] Returned progress value.
Return Values
Return -1 for failure, and return other values as the uploading status codes, see details in the
following table.
24
Device Network SDK (ANPR) Developer Guide
25
Device Network SDK (ANPR) Developer Guide
6.7 NET_DVR_RemoteControl
Implement remote control.
API Definition
BOOL NET_DVR_RemoteControl(
LONG lUserID,
DWORD dwCommand,
LPVOID lpInBuffer,
DWORD dwInBufferSize
);
Parameters
lUserID
[IN] Value returned by NET_DVR_Login_V40 .
dwCommand
[IN] Control commands. To realize different functions, the commands are different.
lpInBuffer
[IN] Input parameters, which vary with different control commands.
dwInBufferSize
[IN] Size of input parameters.
Return Values
Returns TRUE for success, and returns FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
26
Device Network SDK (ANPR) Developer Guide
6.8 NET_DVR_SetDeviceConfig
Set device parameters in batch (sending data is supported).
API Definition
BOOL NET_DVR_SetDeviceConfig(
LONG lUserID,
DWORD dwCommand,
DWORD dwCount,
LPVOID lpInBuffer,
DWORD dwInBufferSize,
LPVOID lpStatusList,
LPVOID lpInParamBuffer,
DWORD dwInParamBufferSize
);
Parameters
lUserID
[IN] Value returned by NET_DVR_Login_V40 .
dwCommand
[IN] Device configuration commands, which are different according to different configurations.
dwCount
[IN] Number of cameras to be set at a time. 0,1-one camera, 2-two cameras, 3-three cameras,
and so on. Up to 256 cameras can be configured at a time.
lpInBuffer
[IN] Pointer of configuration condition buffer, e.g., stream ID, which specifies the number
(dwCount) of cameras to set, and relates to the configuration commands.
dwInBufferSize
[IN] Size of configuration condition buffer, which saves the configured information of cameras
with the number of dwCount.
lpStatusList
[OUT] Error information list, and its memory is allocated by user, each error information
contains 4 bytes (a unsigned 32-bit integer).
There is a one-to-one correspondence between the errors in the list and the cameras that need
to be searched, e.g., lpStatusList[2] corresponds to lpInBuffer[2].
If the parameter value is 0, it refers to setting succeeded, otherwise, this parameter value is the
error code.
lpInParamBuffer
27
Device Network SDK (ANPR) Developer Guide
[IN] Device parameters to set, which relates to the configuration commands. And there is a one-
to-one correspondence between the parameters and the cameras that need to be searched.
dwInParamBufferSize
[IN] Set the size of content buffer.
Return Values
Returns TRUE for success, and returns FALSE for all failed. If returns TRUE, it does not indicate that
all settings are succeeded, you can get the value of lpStatusList[n] to check which one is
succeeded.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
See Also
NET_DVR_GetDeviceConfig
6.9 NET_DVR_SetSTDConfig
Set the device parameters.
API Definition
BOOL NET_DVR_SetSTDConfig(
LONG lUserID,
DWORD dwCommand,
NET_DVR_STD_CONFIG lpConfigParam
);
Parameters
lUserID
[IN] Value returned by NET_DVR_Login_V40 .
dwCommand
[IN] Device configuration commands, which are different according to different configuration
functions.
lpConfigParam
[IN][OUT] Set input and output parameters, which are different according to different
configuration functions. For different configuration functions, the lpCondBuffer and lpInBuffer
in the IpConfigParam are also different. See the structure NET_DVR_STD_CONFIG for details.
Note
When getting configuration parameters, the lpOutBuffer in the lpConfigParam is invalid, you
can set it to "NULL".
28
Device Network SDK (ANPR) Developer Guide
Return Values
Returns TRUE for success, and returns FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
See Also
NET_DVR_GetSTDConfig
6.10 NET_DVR_STDXMLConfig
Transmit request URL with XML or JSON format to implement some typical functions.
API Definition
BOOL NET_DVR_STDXMLConfig(
LONG lUserID,
const NET_DVR_XML_CONFIG_INPUT *lpInputParam,
NET_DVR_XML_CONFIG_OUTPUT *lpOutputParam
);
Parameters
lUserID
[IN] Value returned by NET_DVR_Login_V40 .
lpInputParam
[IN] Input parameters, refer to the structure NET_DVR_XML_CONFIG_INPUT for details.
lpOutputParam
[IN][OUT] Output parameters, refer to the structure NET_DVR_XML_CONFIG_OUTPUT for
details.
Return Values
Return TRUE for success, and return FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
Remarks
The input parameter lpInputParam and output parameter lpOutputParam are different when
transmitting text protocol for implementing different functions, and each parameter corresponds
to a component of text protocol, see the relations below:
29
Device Network SDK (ANPR) Developer Guide
6.11 NET_DVR_StartDownload
Start downloading files
API Definition
LONG NET_DVR_StartDownload(
LONG lUserID,
DWORD dwDownloadType,
LPVOID lpInBuffer,
DWORD dwInBufferSize,
char const *sFileName
);
Parameters
lUserID
[IN] Value returned by NET_DVR_Login_V40 .
dwDownloadType
[IN] Downloading commands which specify the file type to download, see details in the
enumeration NET_SDK_DOWNLOAD_TYPE .
lpInBuffer
[IN] Input parameters, which are different according to different downloading commands.
dwInBufferSize
[IN] Input buffer size.
30
Device Network SDK (ANPR) Developer Guide
sFileName
[IN] Path for saving downloaded files (absolute path, includes file name).
Return Values
Returns -1 for failure, and returns other values as the parameters of NET_DVR_StopDownload and
NET_DVR_GetDownloadState .
If returning failed, you can call NET_DVR_GetLastError to get the error code.
6.12 NET_DVR_StopDownload
Stop downloading files.
API Definition
BOOL NET_DVR_StopDownload(
LONG lHandle
);
Parameters
lHandle
[IN] Handle for downloading files, which is returned by NET_DVR_StartDownload .
Return Values
Returns TRUE for success, and returns FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
6.13 NET_DVR_UploadClose
Stop uploading files.
API Definition
BOOL NET_DVR_UploadClose(
LONG lUploadHandle
);
Parameters
lUploadHandle
[IN] Handle for uploading files, which is returned by NET_DVR_UploadFile_V40 .
31
Device Network SDK (ANPR) Developer Guide
Return Values
Return TRUE for success, and return FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
6.14 NET_DVR_UploadFile_V40
Upload file.
API Definition
LONG NET_DVR_UploadFile_V40(
LONG lUserID,
DWORD dwUploadType,
LPVOID lpInBuffer,
DWORD dwInBufferSize,
char *sFileName,
LPVOID lpOutBuffer,
DWORD dwOutBufferSize
);
Parameters
lUserID
[IN] Value returned by NET_DVR_Login_V40 .
dwUploadType
[IN] Uploading commands, which specify the file type to upload, see details in the enumeration
NET_SDK_UPLOAD_TYPE .
lpInBuffer
[IN] Input parameters, which are different according to different uploading commands.
dwInBufferSize
[IN] Input buffer size.
sFileName
[IN] Name of the file to be uploaded. For the complete file path (including the file name), the
maximum size is 128 bytes, and the maximum size of the file name is 32 bytes.
lpOutBuffer
[OUT] Output parameters, which are different according to different uploading commands.
dwOutBufferSize
[OUT] Output buffer size.
32
Device Network SDK (ANPR) Developer Guide
Return Values
Return -1 for failure, and return other values as the parameter of NET_DVR_UploadClose and
NET_DVR_GetUploadState .
If -1 is returned, you can call NET_DVR_GetLastError to get the error code.
6.15 NET_DVR_Cleanup
Release the resources after the program is ended.
API Definition
BOOL NET_DVR_Cleanup(
);
Return Values
Returns TURE for success, and returns FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
The available error codes may be returned by this API are 0 and 3. See details in Device Network
SDK Errors .
Remarks
● When calling this API, you cannot call other APIs at the same time.
● NET_DVR_Init and this API should be called by pair. That is, once the NET_DVR_Init is called, you
should call NET_DVR_Cleanup to release the resources when exiting the program.
6.16 NET_DVR_GetErrorMsg
Return the error information of the last operation.
API Definition
char *NET_DVR_GetErrorMsg(
LONG *pErrorNo
);
Parameters
pErrorNo
[OUT] Error code pointer.
Return Values
The return values are the pointers of error information, see Device Network SDK Errors for details.
33
Device Network SDK (ANPR) Developer Guide
Remarks
You can call NET_DVR_GetLastError to get the error codes.
6.17 NET_DVR_GetLastError
Return the error code of the last operation.
API Definition
DWORD NET_DVR_GetLastError(
);
Return Values
The return values are error codes, see Device Network SDK Errors for details.
Remarks
You can also call NET_DVR_GetErrorMsg to directly get the error information.
6.18 NET_DVR_Init
Initialize the programming environment before calling other APIs.
API Definition
BOOL NET_DVR_Init(
);
Return Values
Returns TURE for success, and returns FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
The available error codes of this API are 0, 41, and 53. See details in Device Network SDK Errors .
Remarks
Before initializing, you can call NET_DVR_SetSDKInitCfg to set the initialization parameters, such as
supported capabilities, loading path of component libraries (only supported by Linux system), and
so on.
See Also
NET_DVR_Cleanup
34
Device Network SDK (ANPR) Developer Guide
6.19 NET_DVR_Login_V40
Log in to the device (supports asynchronous login).
API Definition
LONG NET_DVR_Login_V40(
NET_DVR_USER_LOGIN_INFO pLoginInfo,
NET_DVR_DEVICEINFO_V40 lpDeviceInfo
);
Parameters
pLoginInfo
[IN] Login parameters, including device address, user name, password, and so on. See details in
the structure NET_DVR_USER_LOGIN_INFO .
lpDeviceInfo
[OUT] Device information. See details in the structure NET_DVR_DEVICEINFO_V40 .
Return Values
● For asynchronous login, the callback function ( fLoginResultCallBack ) configured in the
structure ( NET_DVR_USER_LOGIN_INFO ) returns the asynchronous login status, user ID and
device information.
● For synchronous login, this API returns -1 for logging failed, and returns other values for the
returned user IDs. The user ID is unique, and it helps to realize the further device operations.
● If -1 is returned, you can call NET_DVR_GetLastError to get the error code.
Remarks
● When bUseAsynLogin in pLoginInfo is 0, it indicates that login is in synchronous mode; when
bUseAsynLogin in pLoginInfo is 1, it indicates that login is in asynchronous mode.
● Up to 2048 users are allowed to log in to HCNetSDK at same time, and the values of returned
UserID are ranging from 0 to 2047.
See Also
NET_DVR_Logout
6.19.1 fLoginResultCallBack
35
Device Network SDK (ANPR) Developer Guide
6.20 NET_DVR_Logout
Log out from devices.
API Definitions
BOOL NET_DVR_Logout(
LONG lUserID
);
Parameters
lUserID
[IN] User ID, which is returned by NET_DVR_Login_V40 .
Return Values
Returns TURE for success, and returns FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
The available error codes may be returned by this API are 0, 3, 7, 8, 9, 10, 14, 17, 41, 44, 47, 72,
and 73. See details in Device Network SDK Errors .
6.21 NET_DVR_SetSDKInitCfg
Set initialization parameters.
API Parameters
BOOL NET_DVR_SetSDKInitCfg(
NET_SDK_INIT_CFG_TYPE enumType,
36
Device Network SDK (ANPR) Developer Guide
Parameters
enumType
[IN] Initialization parameter type. Different type values correspond to different parameters, see
details in the table below.
Return Values
Returns TURE for success, and returns FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
37
Device Network SDK (ANPR) Developer Guide
Remarks
This API should be called before calling NET_DVR_Init to initialize and check the dependent
libraries or capabilities.
6.22 NET_DVR_CloseAlarmChan_V30
Close alarm uploading channel.
API Definition
BOOL NET_DVR_CloseAlarmChan_V30(
LONG lAlarmHandle
);
Parameters
lAlarmHandle
Value returned by NET_DVR_SetupAlarmChan_V50 .
Return Values
Return TURE for success, and return FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
The available error codes of this API are 0, 3, 6, 12, 17, 41, and 47. See details in the Device
Network SDK Errors .
6.23 NET_DVR_GetDVRConfig
Get the device configuration information.
API Definition
BOOL NET_DVR_GetDVRConfig(
LONG lUserID,
DWORD dwCommand,
LONG lRuleID,
LONG lChannel,
LPVOID lpOutBuffer,
DWORD dwOutBufferSize,
LPDWORD lpBytesReturned
);
Parameters
lUserID
38
Device Network SDK (ANPR) Developer Guide
Return Values
Returns TRUE for success, and returns FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
The following error codes may be returned by this API: 0, 3, 6, 7, 8, 9, 10, 12, 17, 41, 43, 44, 47, 72,
73, and 76. See the corresponding error types and descriptions in the Device Network SDK Errors .
See Also
NET_DVR_SetDVRConfig
6.24 NET_DVR_SetDVRConfig
Set the device parameters.
API Definition
BOOL NET_DVR_SetDVRConfig(
LONG lUserID,
DWORD dwCommand,
LONG lChannel,
LPVOID lpInBuffer,
DWORD dwInBufferSize
);
39
Device Network SDK (ANPR) Developer Guide
Parameters
lUserID
[IN] Value returned by NET_DVR_Login_V40 .
dwCommand
[IN] Device configuration commands, which are different according to different configuration
functions.
lChannel
[IN] Channel No. (NIC No.), which varies with different commands. 0xFFFFFFFF-invalid, 1-main
NIC, 2-extended NIC.
lpInBuffer
[IN] Pointer of input data buffer. For different configuration functions, the structures of this
parameter are different.
dwInBufferSize
[IN] Size of input data buffer (unit: byte).
Return Values
Returns TRUE for success, and returns FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
The following error codes may be returned by this API: 0, 3, 6, 7, 8, 9, 10, 12, 17, 41, 43, 44, 47, 72,
73, and 76. See the corresponding error types and descriptions in the Device Network SDK Errors .
See Also
NET_DVR_GetDVRConfig
6.25 NET_DVR_SetDVRMessageCallBack_V50
Set callback functions for getting the video data.
API Definition
BOOL NET_DVR_SetDVRMessageCallBack_V50(
int iIndex,
MSGCallBack fMessageCallBack,
void *pUser
);
Parameters
iIndex
[IN] Callback function index No., which ranges from 0 to 15.
40
Device Network SDK (ANPR) Developer Guide
fMessageCallBack
[IN] Callback function, see details in MSGCallBack .
pUser
[IN] User data.
Return Values
Return TRUE for success, and return FALSE for failure.
If FALSE returned, call NET_DVR_GetLastError to get the error code.
Remarks
● This API supports setting multiple callback functions for different channels (up to 16 channels are
supported) at same time, and the configured callback functions are distinguished by the index
No.
● All alarm/event information will be returned in each configured callback function, and you can
distinguish the devices via the pAlarmInfo in the callback function ( MSGCallBack ).
Example
Sample Code of Setting Multiple Callback Functions to Receive Different Alarms/Events in Arming
Mode
#include <stdio.h>
#include <iostream>
#include "Windows.h"
#include "HCNetSDK.h"
using namespace std;
int iNum=0;
void CALLBACK MessageCallbackNo1(LONG lCommand, NET_DVR_ALARMER *pAlarmer, char *pAlarmInfo, DWORD
dwBufLen, void* pUser)
{
int i=0;
char filename[100];
FILE *fSnapPic=NULL;
FILE *fSnapPicPlate=NULL;
//This sample code is for reference only. Actually, it is not recommended to process the data and save file in the
callback function directly.
//You'd better process the data in the message response funcion via message mode (PostMessage).
switch(lCommand)
{
case COMM_ALARM:
{
NET_DVR_ALARMINFO struAlarmInfo;
memcpy(&struAlarmInfo, pAlarmInfo, sizeof(NET_DVR_ALARMINFO));
switch (struAlarmInfo.dwAlarmType)
{
case 3: //Motion detection alarm
41
Device Network SDK (ANPR) Developer Guide
for (i=0; i<16; i++) //#define MAX_CHANNUM 16 //The maximum number of channels
{
if (struAlarmInfo.dwChannel[i] == 1)
{
printf("Channel Number with Motion Detection Alarm %d\n", i+1);
}
}
break;
default:
break;
}
break;
}
case COMM_UPLOAD_PLATE_RESULT:
{
NET_DVR_PLATE_RESULT struPlateResult={0};
memcpy(&struPlateResult, pAlarmInfo, sizeof(struPlateResult));
printf("License Plate Number: %s\n", struPlateResult.struPlateInfo.sLicense);//License plate number
42
Device Network SDK (ANPR) Developer Guide
fclose(fSnapPicPlate);
}
//Processing other data...
break;
}
case COMM_ITS_PLATE_RESULT:
{
NET_ITS_PLATE_RESULT struITSPlateResult={0};
memcpy(&struITSPlateResult, pAlarmInfo, sizeof(struITSPlateResult));
for (i=0;i<struITSPlateResult.dwPicNum;i++)
{
printf("License Plate Number: %s\n", struITSPlateResult.struPlateInfo.sLicense);//License plate number
switch(struITSPlateResult.struPlateInfo.byColor)//License plate color
{
case VCA_BLUE_PLATE:
printf("Vehicle Color: Blue\n");
break;
case VCA_YELLOW_PLATE:
printf("Vehicle Color: Yellow\n");
break;
case VCA_WHITE_PLATE:
printf("Vehicle Color: White\n");
break;
case VCA_BLACK_PLATE:
printf("Vehicle Color: Black\n");
break;
default:
break;
}
//Save scene picture
if ((struITSPlateResult.struPicInfo[i].dwDataLen != 0)&&(struITSPlateResult.struPicInfo[i].byType== 1)||
(struITSPlateResult.struPicInfo[i].byType == 2))
{
sprintf(filename,"testITSpic%d_%d.jpg",iNum,i);
fSnapPic=fopen(filename,"wb");
fwrite(struITSPlateResult.struPicInfo[i].pBuffer, struITSPlateResult.struPicInfo[i].dwDataLen,1,fSnapPic);
iNum++;
fclose(fSnapPic);
}
//License plate thumbnails
if ((struITSPlateResult.struPicInfo[i].dwDataLen != 0)&&(struITSPlateResult.struPicInfo[i].byType == 0))
{
sprintf(filename,"testPicPlate%d_%d.jpg",iNum,i);
fSnapPicPlate=fopen(filename,"wb");
fwrite(struITSPlateResult.struPicInfo[i].pBuffer, struITSPlateResult.struPicInfo[i].dwDataLen, 1, \
fSnapPicPlate);
iNum++;
fclose(fSnapPicPlate);
}
//Processing other data...
}
43
Device Network SDK (ANPR) Developer Guide
break;
}
default:
break;
}
}
//This sample code is for reference only. Actually, it is not recommended to process the data and save file in the
callback function directly.
//You'd better process the data in the message response funcion via message mode (PostMessage).
switch(lCommand)
{
case COMM_ALARM:
{
NET_DVR_ALARMINFO struAlarmInfo;
memcpy(&struAlarmInfo, pAlarmInfo, sizeof(NET_DVR_ALARMINFO));
switch (struAlarmInfo.dwAlarmType)
{
case 3: //Motion detection alarm
for (i=0; i<16; i++) //#define MAX_CHANNUM 16 //The maximum number of channel
{
if (struAlarmInfo.dwChannel[i] == 1)
{
printf("Channel No. with Motion Detection Alarm %d\n", i+1);
}
}
break;
default:
break;
}
break;
}
case COMM_UPLOAD_PLATE_RESULT:
{
NET_DVR_PLATE_RESULT struPlateResult={0};
memcpy(&struPlateResult, pAlarmInfo, sizeof(struPlateResult));
printf("License Plate Number: %s\n", struPlateResult.struPlateInfo.sLicense);//License plate number
44
Device Network SDK (ANPR) Developer Guide
case VCA_YELLOW_PLATE:
printf("Vehicle Color: Yellow\n");
break;
case VCA_WHITE_PLATE:
printf("Vehicle color: White\n");
break;
case VCA_BLACK_PLATE:
printf("Vehicle Color: Black\n");
break;
default:
break;
}
//Scene picture
if (struPlateResult.dwPicLen != 0 && struPlateResult.byResultType == 1 )
{
sprintf(filename,"testpic_%d.jpg",iNum);
fSnapPic=fopen(filename,"wb");
fwrite(struPlateResult.pBuffer1,struPlateResult.dwPicLen,1,fSnapPic);
iNum++;
fclose(fSnapPic);
}
//License plate picture
if (struPlateResult.dwPicPlateLen != 0 && struPlateResult.byResultType == 1)
{
sprintf(filename,"testPicPlate_%d.jpg",iNum);
fSnapPicPlate=fopen(filename,"wb");
fwrite(struPlateResult.pBuffer1,struPlateResult.dwPicLen,1,fSnapPicPlate);
iNum++;
fclose(fSnapPicPlate);
}
//Processing other data...
break;
}
case COMM_ITS_PLATE_RESULT:
{
NET_ITS_PLATE_RESULT struITSPlateResult={0};
memcpy(&struITSPlateResult, pAlarmInfo, sizeof(struITSPlateResult));
for (i=0;i<struITSPlateResult.dwPicNum;i++)
{
printf("License Plate Number: %s\n", struITSPlateResult.struPlateInfo.sLicense);//License plate number
switch(struITSPlateResult.struPlateInfo.byColor)//License plate color
{
case VCA_BLUE_PLATE:
printf("Vehicle Color: Blue\n");
break;
case VCA_YELLOW_PLATE:
printf("Vehicle Color: Yellow\n");
break;
case VCA_WHITE_PLATE:
printf("Vehicle Color: White\n");
break;
45
Device Network SDK (ANPR) Developer Guide
case VCA_BLACK_PLATE:
printf("Vehicle Color: Black\n");
break;
default:
break;
}
//Save scene picture
if ((struITSPlateResult.struPicInfo[i].dwDataLen != 0)&&(struITSPlateResult.struPicInfo[i].byType== 1)||
(struITSPlateResult.struPicInfo[i].byType == 2))
{
sprintf(filename,"testITSpic%d_%d.jpg",iNum,i);
fSnapPic=fopen(filename,"wb");
fwrite(struITSPlateResult.struPicInfo[i].pBuffer, struITSPlateResult.struPicInfo[i].dwDataLen,1,fSnapPic);
iNum++;
fclose(fSnapPic);
}
//License plate thumbnails
if ((struITSPlateResult.struPicInfo[i].dwDataLen != 0)&&(struITSPlateResult.struPicInfo[i].byType == 0))
{
sprintf(filename,"testPicPlate%d_%d.jpg",iNum,i);
fSnapPicPlate=fopen(filename,"wb");
fwrite(struITSPlateResult.struPicInfo[i].pBuffer, struITSPlateResult.struPicInfo[i].dwDataLen, 1, \
fSnapPicPlate);
iNum++;
fclose(fSnapPicPlate);
}
//Processing other data...
}
break;
}
default:
break;
}
}
void main() {
//---------------------------------------
//Initialize
NET_DVR_Init();
//Set the connection time and reconnection time
NET_DVR_SetConnectTime(2000, 1);
NET_DVR_SetReconnect(10000, true);
//---------------------------------------
//Log in to device
LONG lUserID;
NET_DVR_DEVICEINFO_V30 struDeviceInfo;
lUserID = NET_DVR_Login_V30("172.0.0.100", 8000, "admin", "12345", &struDeviceInfo);
if (lUserID < 0)
{
printf("Login error, %d\n", NET_DVR_GetLastError());
46
Device Network SDK (ANPR) Developer Guide
NET_DVR_Cleanup();
return;
}
//Enable arming
NET_DVR_SETUPALARM_PARAM struSetupParam={0};
struSetupParam.dwSize=sizeof(NET_DVR_SETUPALARM_PARAM);
Sleep(20000);
//Disarm uploading channel
if (!NET_DVR_CloseAlarmChan_V30(lHandle))
{
printf("NET_DVR_CloseAlarmChan_V30 error, %d\n", NET_DVR_GetLastError());
NET_DVR_Logout(lUserID);
NET_DVR_Cleanup();
return;
}
//User logout
NET_DVR_Logout(lUserID);
//Release SDK resource
NET_DVR_Cleanup();
return;
}
See Also
NET_DVR_SetupAlarmChan_V50
47
Device Network SDK (ANPR) Developer Guide
6.25.1 MSGCallBack
Alarm/event information callback function.
Parameters
lCommand
[OUT] Uploaded message type. You can distinguish the alarm/event information via the type.
pAlarmer
[OUT] Alarm device information, including serial No., IP address, login handle, and so on, see
details in NET_DVR_ALARMER .
pAlarmInfo
[OUT] Alarm/event information, the details are returned in different structures according to
lCommand.
dwBufLen
[OUT] Size of alarm/event information buffer.
pUser
[OUT] User data.
6.26 NET_DVR_SetupAlarmChan_V50
Set up persistent connection to receive alarm/event information (supports alarm/event
subscription).
API Definition
LONG NET_DVR_SetupAlarmChan_V50(
LONG lUserID,
NET_DVR_SETUPALARM_PARAM_V50 lpSetupParam,
char *pData,
DWORD dwDataLen,
);
48
Device Network SDK (ANPR) Developer Guide
Parameters
lUserID
[IN] Value returned by NET_DVR_Login_V40 .
lpSetupParam
[IN] Arming parameters, refer to the structure NET_DVR_SETUPALARM_PARAM_V50 for
details.
pData
[IN] Alarm/event subscription conditions.
dwDataLen
[IN] Length of alarm/event subscription conditions.
Return Values
Return -1 for failure, and return other values as the handles of NET_DVR_CloseAlarmChan_V30 .
If -1 is returned, you can call NET_DVR_GetLastError to get the error code.
Remarks
This API supports alarm/event subscription, you can specify the types of alarm or event to be
uploaded by device by setting pData and dwDataLen.
6.27 NET_DVR_StartListen_V30
Register callback function for receiving alarm/event information and start listening (supports
multiple threads).
API Definition
LONG NET_DVR_StartListen_V30(
char *sLocalIP,
WORD wLocalPort,
MSGCallBack DataCallback,
void *pUserData
);
Parameters
sLocalIP
[IN] IP address of local PC. It can be set to null.
wLocalPort
[IN] Listening port No. of local PC. It is configured by user, and it should be the same with that of
device.
49
Device Network SDK (ANPR) Developer Guide
DataCallback
[IN] Alarm/event information callback function, see details in MSGCallBack .
pUserData
[IN] User data.
Return Values
Return -1 for failure, and return other values for the handle parameters of
NET_DVR_StopListen_V30 .
If -1 is returned, you can call NET_DVR_GetLastError to get the error code.
The available error codes of this API are 0, 3, 6, 12, 17, 41, 44, 47, 72, and 75. See details in the
Device Network SDK Errors .
Remarks
● To receive the alarm/event information sent by device, you should set the management host
server address or listening host server address of device to the IP address of PC (which is same
with the sLocalIP), or set the management host server port or listening host server port to the
listening port No. of PC (which is same with the wLocalPort).
● The callback function in this API is prior to other callback functions, that is, if the callback
function is configured in this API, other callback functions will not receive the alarm information.
All the device alarm information is returned in same callback function, and you can distinguish
the devices via the alarm device information (pAlarmInfo).
6.28 NET_DVR_StopListen_V30
Stop listening (supports multiple threads).
API Definition
BOOL NET_DVR_StopListen_V30(
LONG lListenHandle
);
Parameters
lListenHandle
Listening handle, which is returned by NET_DVR_StartListen_V30 .
Return Values
Return TRUE for success, and return FALSE for failure.
If FALSE is returned, you can call NET_DVR_GetLastError to get the error code.
The available error codes of this API are 0, 3, 12, and 17. See details in the Device Network SDK
Errors .
50
Device Network SDK (ANPR) Developer Guide
7.1.1 ITC_LANE_DIRECTION_TYPE
Enumerate the lane direction type.
Enumeration Definition
enum{
ITC_LANE_DIRECTION_UNKNOW = 0,
ITC_LANE_LEFT = 1,
ITC_LANE_STRAIGHT = 2,
ITC_LANE_LEFT_STRAIGHT = 3,
ITC_LANE_RIGHT = 4,
ITC_LANE_LEFT_RIGHT = 5,
ITC_LANE_RIGHT_STRAIGHT = 6,
ITC_LANE_LEFT_RIGHT_STRAIGHT = 7,
ITC_LANE_LEFT_WAIT = 9,
ITC_LANE_STRAIGHT_WAIT = 10,
ITC_LANE_FORWARD = 11,
ITC_LANE_BACKWARD = 12,
ITC_LANE_BOTHWAY = 13,
ITC_LANE_STRAIGHT_WAIT_RIGHT = 14
}ITC_LANE_DIRECTION_TYPE
Member
ITC_LANE_DIRECTION_UNKNOW
Unknown.
ITC_LANE_LEFT
Turn left.
ITC_LANE_STRAIGHT
Go straight.
ITC_LANE_LEFT_STRAIGHT
Turn left and go straight.
ITC_LANE_RIGHT
Turn right.
ITC_LANE_LEFT_RIGHT
Turn left and turn right.
51
Device Network SDK (ANPR) Developer Guide
ITC_LANE_RIGHT_STRAIGHT
Turn right and go straight.
ITC_LANE_LEFT_RIGHT_STRAIGHT
Turn left, turn right and go straight.
ITC_LANE_LEFT_WAIT
Turn left and wait.
ITC_LANE_STRAIGHT_WAIT
Go straight and wait.
ITC_LANE_FORWARD
Drive forward.
ITC_LANE_BACKWARD
Drive backward.
ITC_LANE_BOTHWAY
Drive bidirectionally.
ITC_LANE_STRAIGHT_WAIT_RIGHT
Go straight and wait, and turn right.
7.1.2 ITC_LANE_USEAGE_TYPE
Enumerate the lane usage type.
Enumeration Definition
enum {
ITC_LANE_USEAGE_UNKNOW = 0,
ITC_LANE_CARRIAGEWAY = 1,
ITC_LANE_BUS = 2,
ITC_LANE_FAST = 3,
ITC_LANE_SLOW = 4,
ITC_LANE_MOTOR = 5,
ITC_LANE_NONMOTOR = 6,
ITC_LANE_REVERSE_LANE = 7,
ITC_LANE_BAN_TRUCKS = 8,
ITC_LANE_MIX = 9,
ITC_LANE_EMERGENCY = 10,
ITC_LANE_BAN_LEFT = 11,
ITC_LANE_BAN_RIGHT = 12
}ITC_LANE_USEAGE_TYPE
Member
ITC_LANE_USEAGE_UNKNOW
52
Device Network SDK (ANPR) Developer Guide
Unknown.
ITC_LANE_CARRIAGEWAY
Normal lane.
ITC_LANE_BUS
Bus lane.
ITC_LANE_FAST
Fast lane.
ITC_LANE_SLOW
Slow lane.
ITC_LANE_MOTOR
Motor vehicle lane.
ITC_LANE_NONMOTOR
Non-motor vehicle lane.
ITC_LANE_REVERSE_LANE
Opposite lane.
ITC_LANE_BAN_TRUCKS
Non-truck lane.
ITC_LANE_MIX
All-purpose lane.
ITC_LANE_EMERGENCY
Emergency lane.
ITC_LANE_BAN_LEFT
Lane banning turning left.
ITC_LANE_BAN_RIGHT
Lane banning turning right.
7.1.3 ITS_OVERLAP_ITEM_TYPE
Enumerate character overlay type.
Enumeration Definition
enum{
OVERLAP_ITEM_NULL = 0,
OVERLAP_ITEM_SITE = 1,
OVERLAP_ITEM_ROADNUM, = 2,
OVERLAP_ITEM_INSTRUMENTNUM, = 3,
OVERLAP_ITEM_DIRECTION, = 4,
53
Device Network SDK (ANPR) Developer Guide
OVERLAP_ITEM_DIRECTIONDESC, = 5,
OVERLAP_ITEM_DIRECTIONDESC, = 6,
OVERLAP_ITEM_LANEDES, = 7,
OVERLAP_ITEM_CAPTIME, = 8,
OVERLAP_ITEM_CAPTIME_MILLSECOND, = 9,
OVERLAP_ITEM_PLATENUM, = 10,
OVERLAP_ITEM_CARCOLOR, = 11,
OVERLAP_ITEM_CARTYPE, = 12,
OVERLAP_ITEM_CARBRAND, = 13,
OVERLAP_ITEM_CARSPEED, = 14,
OVERLAP_ITEM_SPEEDLIMIT, = 15,
OVERLAP_ITEM_CARLENGTH, = 16,
OVERLAP_ITEM_ILLEGALNUM, = 17,
OVERLAP_ITEM_MONITOR_INFO, = 18,
OVERLAP_ITEM_ILLEGALDES, = 19,
OVERLAP_ITEM_OVERSPEED_PERCENT, = 20,
OVERLAP_ITEM_RED_STARTTIME, = 21,
OVERLAP_ITEM_RED_STOPTIME, = 22,
OVERLAP_ITEM_RED_DURATION, = 23,
OVERLAP_ITEM_SECUNITY_CODE, = 24,
OVERLAP_ITEM_CAP_CODE, = 25,
OVERLAP_ITEM_SEATBELT, = 26,
OVERLAP_ITEM_MONITOR_ID, = 27,
OVERLAP_ITEM_SUN_VISOR, = 28,
OVERLAP_ITEM_LANE_DIRECTION, = 29,
OVERLAP_ITEM_LICENSE_PLATE_COLOR, = 30,
OVERLAP_ITEM_SCENE_NUMBER, = 31,
OVERLAP_ITEM_SCENE_NAME, = 32,
OVERLAP_ITEM_YELLOW_SIGN_CAR, = 33,
OVERLAP_ITEM_DANGEROUS_CAR, = 34,
OVERLAP_ITEM_CAR_SUBBRAND, = 35,
OVERLAP_ITEM_CAR_DIRECTION, = 36,
OVERLAP_ITEM_PENDANT, = 37,
OVERLAP_ITEM_CALL, = 38,
OVERLAP_ITEM_CAR_VALIDITY = 39
}ITS_OVERLAP_ITEM_TYPE
Member
OVERLAP_ITEM_NULL
Unknown.
OVERLAP_ITEM_SITE
Location.
OVERLAP_ITEM_ROADNUM
Intersection No.
OVERLAP_ITEM_INSTRUMENTNUM
Device No.
OVERLAP_ITEM_DIRECTION
54
Device Network SDK (ANPR) Developer Guide
Direction No.
OVERLAP_ITEM_DIRECTIONDESC
Direction.
OVERLAP_ITEM_LANENUM
Lane No.
OVERLAP_ITEM_LANEDES
Lane.
OVERLAP_ITEM_CAPTIME
Capture time (without milliseconds).
OVERLAP_ITEM_CAPTIME_MILLSECOND
Capture time (milliseconds).
OVERLAP_ITEM_PLATENUM
License plate No.
OVERLAP_ITEM_CARCOLOR
Vehicle color.
OVERLAP_ITEM_CARTYPE
Vehicle type.
OVERLAP_ITEM_CARBRAND
Vehicle brand.
OVERLAP_ITEM_CARSPEED
Vehicle speed.
OVERLAP_ITEM_SPEEDLIMIT
Speed limit sign.
OVERLAP_ITEM_CARLENGTH
Vehicle length, ranges from 1 to 99, unit: m.
OVERLAP_ITEM_ILLEGALNUM
Violation code, actually overlay illegal action information, such as low speed, overspeed, driving
in the opposite direction, running the red light, occupying the road, driving over the yellow line,
etc.
OVERLAP_ITEM_MONITOR_INFO
Camera information.
OVERLAP_ITEM_ILLEGALDES
Illegal action.
OVERLAP_ITEM_OVERSPEED_PERCENT
Overspeed percentage.
55
Device Network SDK (ANPR) Developer Guide
OVERLAP_ITEM_RED_STARTTIME
Red light start time.
OVERLAP_ITEM_RED_STOPTIME
Red light end time.
OVERLAP_ITEM_RED_DURATION
Duration of right light on.
OVERLAP_ITEM_SECUNITY_CODE
Security code.
OVERLAP_ITEM_CAP_CODE
Capture No.
OVERLAP_ITEM_SEATBELT
Whether to fasten the seat belt.
OVERLAP_ITEM_MONITOR_ID
Camera No.
OVERLAP_ITEM_SUN_VISOR
Sun visor.
OVERLAP_ITEM_LANE_DIRECTION
Driving direction of the lane.
OVERLAP_ITEM_LICENSE_PLATE_COLOR
License plate color.
OVERLAP_ITEM_SCENE_NUMBER
Scene No.
OVERLAP_ITEM_SCENE_NAME
Scene name.
OVERLAP_ITEM_YELLOW_SIGN_CAR
Yellow label vehicle.
OVERLAP_ITEM_DANGEROUS_CAR
Hazardous material truck.
OVERLAP_ITEM_CAR_SUBBRAND
Vehicle sub-brand.
OVERLAP_ITEM_CAR_DIRECTION
Driving direction of the vehicle.
OVERLAP_ITEM_PENDANT
Pendant on the window.
56
Device Network SDK (ANPR) Developer Guide
OVERLAP_ITEM_CALL
Talking on the phone.
OVERLAP_ITEM_CAR_VALIDITY
Confidence level.
See Also
NET_ITS_OVERLAP_SINGLE_ITEM_PARAM_V50
7.1.4 ITC_RELA_LANE_DIRECTION_TYPE
Enumerate the lane directions.
Enumeration Definition
enum{
ITC_RELA_LANE_DIRECTION_UNKNOW = 0,
ITC_RELA_LANE_EAST_WEST = 1,
ITC_RELA_LANE_WEST_EAST = 2,
ITC_RELA_LANE_SOUTH_NORTH = 3,
ITC_RELA_LANE_NORTH_SOUTH = 4,
ITC_RELA_LANE_EASTSOUTH_WESTNORTH = 5,
ITC_RELA_LANE_WESTNORTH_EASTSOUTH = 6,
ITC_RELA_LANE_EASTNORTH_WESTSOUTH = 7,
ITC_RELA_LANE_WESTSOUTH_EASTNORTH = 8
}ITC_RELA_LANE_DIRECTION_TYPE
Member
ITC_RELA_LANE_DIRECTION_UNKNOW
Other
ITC_RELA_LANE_EAST_WEST
From east to west.
ITC_RELA_LANE_WEST_EAST
From weat to east.
ITC_RELA_LANE_SOUTH_NORTH
From south to north.
ITC_RELA_LANE_NORTH_SOUTH
From north to south.
ITC_RELA_LANE_EASTSOUTH_WESTNORTH
From southeast to northwest.
ITC_RELA_LANE_WESTNORTH_EASTSOUTH
57
Device Network SDK (ANPR) Developer Guide
7.1.5 ITC_TRIGGERMODE_TYPE
Enumerate the trigger modes.
Enumeration Definition
enum{
ITC_POST_IOSPEED_TYPE = 0x1,
ITC_POST_SINGLEIO_TYPE = 0x2,
ITC_POST_RS485_TYPE = 0x4,
ITC_POST_RS485_RADAR_TYPE = 0x8,
ITC_POST_VIRTUALCOIL_TYPE = 0x10,
ITC_POST_HVT_TYPE_V50 = 0x20,
ITC_POST_MPR_TYPE = 0x40,
ITC_POST_PRS_TYPE = 0x80,
ITC_EPOLICE_IO_TRAFFICLIGHTS_TYPE = 0x100,
ITC_EPOLICE_RS485_TYPE = 0x200,
ITC_PE_RS485_TYPE = 0x10000,
ITC_VIDEO_EPOLICE_TYPE = 0x20000,
ITC_VIA_VIRTUALCOIL_TYPE = 0x40000,
ITC_POST_IMT_TYPE = 0x80000,
IPC_POST_HVT_TYPE = 0x100000,
ITC_POST_MOBILE_TYPE = 0x200000,
ITC_REDLIGHT_PEDESTRIAN_TYPE = 0x400000,
ITC_NOCOMITY_PEDESTRIAN_TYPE = 0x800000
}ITC_TRIGGERMODE_TYPE
Member
ITC_POST_IOSPEED_TYPE
Triggered by I/O speed detection (checkpoint)
ITC_POST_SINGLEIO_TYPE
Triggered by single I/O (checkpoint)
ITC_POST_RS485_TYPE
Triggered by RS-485 vehicle detector (checkpoint)
ITC_POST_RS485_RADAR_TYPE
Triggered by RS-485 radar (checkpoint)
ITC_POST_VIRTUALCOIL_TYPE
58
Device Network SDK (ANPR) Developer Guide
7.1.6 ITC_VIOLATION_DETECT_TYPE
Enumerate violation detection types.
Structure Definition
enum {
ITC_VIOLATION_POST = 0x01,
ITC_VIOLATION_DRIVELINE = 0x02,
59
Device Network SDK (ANPR) Developer Guide
ITC_VIOLATION_REVERSE = 0x04,
ITC_VIOLATION_REDLIGHT = 0x08,
ITC_VIOLATION_DIRECTION = 0x10,
ITC_VIOLATION_INTERSECTION_CONGEST = 0x20,
ITC_VIOLATION_NONDRIVEWAY = 0x40,
ITC_VIOLATION_CHANGELANE = 0x80,
ITC_VIOLATION_BAN = 0x100,
ITC_VIOLATION_INTERSECTION_PARK = 0x200,
ITC_VIOLATION_GREEN_PARK = 0x400,
ITC_VIOLATION_BAN_DRIVE = 0x800,
ITC_VIOLATION_ACROSS_YELLOWLINE = 0x1000,
ITC_VIOLATION_HIGH_SPEED = 0x2000,
ITC_VIOLATION_LOW_SPEED = 0x4000,
ITC_VIOLATION_TURN_AROUND = 0x8000,
ITC_VIOLATION_CONGESTION = 0x10000
}ITC_VIOLATION_DETECT_TYPE
Member
ITC_VIOLATION_POST
Checkpoint capture.
ITC_VIOLATION_DRIVELINE
Driving on the lane line capture.
ITC_VIOLATION_REVERSE
Wrong-way driving capture.
ITC_VIOLATION_REDLIGHT
Red light running capture.
ITC_VIOLATION_DIRECTION
Driving against direction guidance capture.
ITC_VIOLATION_INTERSECTION_CONGEST
Overstaying at intersection capture.
ITC_VIOLATION_NONDRIVEWAY
Motor vehicle on non-motor vehicle lane capture.
ITC_VIOLATION_CHANGELANE
Illegal lane change.
ITC_VIOLATION_BAN
Prohibition violation.
ITC_VIOLATION_INTERSECTION_PARK
Stop vehicle over the stop line when the red light is on.
ITC_VIOLATION_GREEN_PARK
Stop vehicle when the green light is on.
60
Device Network SDK (ANPR) Developer Guide
ITC_VIOLATION_BAN_DRIVE
Prohibition.
ITC_VIOLATION_ACROSS_YELLOWLINE
Cross the yellow line.
ITC_VIOLATION_HIGH_SPEED
Overspeed (only for checkpoint).
ITC_VIOLATION_LOW_SPEED
Low speed (only for checkpoint).
ITC_VIOLATION_TURN_AROUND
Illegal U-turning.
ITC_VIOLATION_CONGESTION
Congestion.
Remarks
● Crossing the yellow line means capturing lane change or U-turning of vehicles by cameras
installed by the roadside, and the concept of illegal lane change is the same as that in the
intersection violation system.
● Prohibition requires capturing all license plates of a specific area, and prohibition violation only
captures a specific type of license plates in the lane.
7.1.7 NET_DVR_BARRIERGATE_CFG
Barrier control parameter structure
Structure Definition
struct{
DWORD dwSize;
DWORD dwChannel;
BYTE byLaneNo;
BYTE byBarrierGateCtrl;
BYTE byEntranceNo;
BYTE byRes[13];
}NET_DVR_BARRIERGATE_CFG,*LPNET_DVR_BARRIERGATE_CFG;
Members
dwSize
Structure size.
dwChannel
Channel No.
61
Device Network SDK (ANPR) Developer Guide
byLaneNo
Barrier No.: 0-invalid, 1-barrier No.1
byBarrierGateCtrl
Control parameters: 0-close barrier, 1-open barrier, 2-stop control, 3-lock barrier
byEntranceNo
Entrance/Exit No., which is between 1 and 8
byRes
Reserved, set to 0.
7.1.8 NET_DVR_CRUISECHAN_INFO
7.1.9 NET_DVR_EVENT_SCHEDULE
7.1.10 NET_DVR_EVENT_TRIGGER
62
Device Network SDK (ANPR) Developer Guide
7.1.11 NET_DVR_GEOGLOCATION
Address and location information structure.
Structure Definition
struct{
int iRes[2];
DWORD dwCity;
}NET_DVR_GEOGLOCATION, *LPNET_DVR_GEOGLOCATION;
Members
iRes
63
Device Network SDK (ANPR) Developer Guide
Reserved, set to 0.
dwCity
Province and city.
7.1.12 NET_DVR_GUARD_CFG
Structure about the configuration parameters of ANPR arming schedule.
Structure Definition
struct{
DWORD dwSize;
NET_DVR_TIME_DETECTION struAlarmSched[MAX_DAYS/*7*/][MAX_TIMESEGMENT_V30/*8*/];
NET_DVR_HANDLEEXCEPTION_V41 struHandleException;
DWORD dwMaxRelRecordChanNum;
DWORD dwRelRecordChanNum;
DWORD dwRelRecordChan[MAX_CHANNUM_V30/*64*/];
NET_DVR_TIME_DETECTION struHolidayTime[MAX_TIMESEGMENT_V30/*8*/];
BYTE byDirection;
BYTE byRes[87];
}NET_DVR_GUARD_CFG,*LPNET_DVR_GUARD_CFG;
Members
dwSize
Structure size
struAlarmSched
Arming schedule, 7 days for a week, maximum 8 time periods for a day, see details in the
structure NET_DVR_TIME_DETECTION .
struHandleException
Alarm linkage action, supports "center"-upload to center, see details in the structure
NET_DVR_HANDLEEXCEPTION_V41 .
dwMaxRelRecordChanNum
Maximum number of triggered video channels (read only) that can be supported.
dwRelRecordChanNum
Actual number of triggered video channels that can be supported, that is, the number of
channels in the current group.
dwRelRecordChan
Alarm triggered video channel No., E.g., if the value of dwRecordChanNum is 5, the values of
dwRelRecordChan is between 0 and 4.
struHolidayTime
64
Device Network SDK (ANPR) Developer Guide
Remarks
● When the value of dwMaxRelRecordChanNum is larger than 64, the channels should be
grouped, and maximum 64 channels can be in a group.
● The video channel No. is linked with the group No., e.g., if the group No. is 0, the channel No. is
between 1 and 64; if the group No. is 1, the channel No. is between 65 and 128; if 0xffffffff
appears, it indicates that the following channel No. is invalid.
7.1.13 NET_DVR_GUARD_COND
Structure about the configuration conditions of ANPR arming schedule.
Structure Definition
struct{
DWORD dwSize;
DWORD dwChannel;
BYTE byRelateType;
BYTE byGroupNo;
BYTE byRes[62];
}NET_DVR_GUARD_COND,*LPNET_DVR_GUARD_COND;
Members
dwSize
Structure size
dwChannel
Channel No.
byRelateType
Capture linkage mode: 0-invalid, 1-MPR mode (video triggered capture, for network camera
only), 2-HVT mode
byGroupNo
Group No.
byRes
Reserved, set to 0.
65
Device Network SDK (ANPR) Developer Guide
7.1.14 NET_DVR_HANDLEEXCEPTION_V41
mail
● 0x20: trigger wireless sound and light alarm
only)
● 0x200: capture picture and upload to FTP
detection)
● 0x800: PTZ linkage (speed dome tracks the
target)
● 0x1000: capture picture and upload to cloud
storage.
● 0x10000: message alarm
7.1.15 NET_DVR_INIT_CFG_ABILITY
66
Device Network SDK (ANPR) Developer Guide
Remarks
By default, up to 2048 channels are supported. More channels require higher computer
performance and network bandwidth.
See Also
NET_DVR_SetSDKInitCfg
7.1.16 NET_DVR_LLI_PARAM
67
Device Network SDK (ANPR) Developer Guide
7.1.17 NET_DVR_LLPOS_PARAM
7.1.18 NET_DVR_MIME_UNIT
68
Device Network SDK (ANPR) Developer Guide
See Also
NET_DVR_XML_CONFIG_INPUT
7.1.19 NET_DVR_PLATE_INFO
Note
The value "COUNTRY_ALL" (0xff, it indicates all
countries) is not supported.
69
Device Network SDK (ANPR) Developer Guide
enum EMI_AREA{
EMI_AREA_UNKNOWN = 0, //Unknown Area (the
area recognition is not supported)
EMI_AREA_AD, //Abu Dhabi
EMI_AREA_FJR, //Fujairah
EMI_AREA_DB, //Dubai
EMI_AREA_RAK, //Ras Al Khaimah
EMI_AREA_AM, //Ajman
EMI_AREA_SJ, //Sharjah
EMI_AREA_UMW, //Umm Al Quwain
EMI_AREA_OTHER = 0xff, //Unrecognized (the
device supports this algorithm, but the area cannot be
recognized due to environment and so on)
}EMI_AREA;
Note
The size of this member is 8 bytes for 64-bit
Windows Linux operation systems. For other
operating systems, its size is 4 bytes.
Note
This member is valid for operation systems
except 64-bit Windows and Linux.
70
Device Network SDK (ANPR) Developer Guide
Note
This member is valid when lCommand in the
callback function MSGCallBack of
NET_DVR_SetDVRMessageCallBack_V50 is
"COMM_ITS_PLATE_RESULT" (0x3050).
7.1.20 NET_DVR_PLATE_RESULT
ANPR result structure
Structure Definition
struct{
DWORD dwSize;
BYTE byResultType;
BYTE byChanIndex;
WORD wAlarmRecordID;
DWORD dwRelativeTime;
BYTE byAbsTime[32];
DWORD dwPicLen;
DWORD dwPicPlateLen;
DWORD dwVideoLen;
BYTE byTrafficLight;
BYTE byPicNum;
BYTE byDriveChan;
BYTE byVehicleType;
DWORD dwBinPicLen;
DWORD dwCarPicLen;
71
Device Network SDK (ANPR) Developer Guide
DWORD dwFarCarPicLen;
BYTE *pBuffer3;
BYTE *pBuffer4;
BYTE *pBuffer5;
BYTE byRelaLaneDirectionType;
BYTE byRes3[7];
NET_DVR_PLATE_INFO struPlateInfo;
NET_DVR_VEHICLE_INFO struVehicleInfo;
BYTE *pBuffer1;
BYTE *pBuffer2;
}NET_DVR_PLATE_RESULT, *LPNET_DVR_PLATE_RESULT;
Members
dwSize
Structure size
byResultType
Recognition type: 0-recognize via video, 1- recognize via picture, 2-continuous recorded video
(support search)
byChanIndex
Lane No.
wAlarmRecordID
Alarm video ID (for video search only), and this parameter is valid only when byResultType is
"2".
dwRelativeTime
Time of UTC ± 00:00. (reserved)
byAbsTime
Local time, accurate to millisecond, format: yyyymmddhhmmssxxx, e.g. 20090810235959999.
dwPicLen
Picture length (close-up picture).
dwPicPlateLen
Length of license plate thumbnail (colorful picture).
dwVideoLen
Video size.
byTrafficLight
0-capture without red or green light, 1-capture with green light, 2-capture with red light.
byPicNum
No. of continuously captured picture.
byDriveChan
Triggered lane No.
72
Device Network SDK (ANPR) Developer Guide
byVehicleType
Vehicle type, see details in VTR_RESULT .
dwBinPicLen
Size of binary picture (for iDS-65 series only).
dwCarPicLen
Size of original vehicle picture (for iDS-65 series only).
dwFarCarPicLen
Size of long-shot picture (for iDS-65 series only).
pBuffer3
Binary picture of license plate (for iDS-65 series only).
pBuffer4
Original vehicle picture (for iDS-65 series only).
pBuffer5
Long-shot picture (for iDS-65 series only).
byRelaLaneDirectionType
Direction of linked lane, see details in ITC_RELA_LANE_DIRECTION_TYPE .
byRes3
Reserved.
struPlateInfo
License plate information.
struVehicleInfo
Vehicle information
pBuffer1
For close-up picture information, the size of this buffer equals to the value of dwPicLen; for
video information, the size of this buffer equals to the value of dwVideoLen.
pBuffer2
For license plate thumbnail information, the size of this buffer equals to the value of
dwPicPlateLen.
Remarks
The uploaded picture or video information can be distinguished according to the information
length (if the length is 0). The picture data includes scene picture and license plate thumbnail. If
the video size is 0xffffffff, it indicates that the video is exception and only the alarm information
(without video) will be uploaded, and the video pointer is NULL.
For iDS-65 series devices, the manually captured picture can only be uploaded to pBuffer1 and
pBuffer2.
73
Device Network SDK (ANPR) Developer Guide
If the byResultType is 2, the wAlarmRecordID can be set as the search conditions for alarm video
search.
7.1.21 NET_DVR_PRESETCHAN_INFO
7.1.22 NET_DVR_PTZTRACKCHAN_INFO
7.1.23 NET_DVR_SCHEDTIME
7.1.24 NET_DVR_STD_ABILITY
74
Device Network SDK (ANPR) Developer Guide
Remarks
For different capability types (which depend on the parameter dwAbilityType in the API
NET_DVR_GetSTDAbility ), the condition parameter lpCondBuffer and output parameter
lpOutBuffer are different. For details, refer to the typical applications.
7.1.25 NET_DVR_STD_CONFIG
75
Device Network SDK (ANPR) Developer Guide
7.1.26 NET_DVR_TIME_V30
76
Device Network SDK (ANPR) Developer Guide
7.1.27 NET_DVR_TIME_V50
Time parameters structure.
Structure Definition
struct{
WORD wYear;
BYTE byMonth;
BYTE byDay;
BYTE byHour;
BYTE byMinute;
BYTE bySecond;
BYTE byISO8601;
WORD wMilliSec;
signed char cTimeDifferenceH;
signed char cTimeDifferenceM;
}NET_DVR_TIME_V50, *LPNET_DVR_TIME_V50;
Members
wYear
Year
byMonth
Month
byDay
Day
byHour
77
Device Network SDK (ANPR) Developer Guide
Hour
byMinute
Minute
bySecond
Second
byISO8601
ISO8601 format, whether time differences are valid, 0-no, it is local time, 1-yes
wMillisecond
Millisecond, it is 0 by default
cTimeDifferenceH
Time offset (hours) from UTC, e.g., -12 ... +14, positive offset indicates eastern time zone
cTimeDifferenceM
Time offset (minutes) from UTC, e.g., -30, 0, 30, 45, positive offset indicates eastern time zone
7.1.28 NET_DVR_TIME_DETECTION
ANPR arming schedule structure
Structure Definition
struct{
NET_DVR_SCHEDTIME struSchedTime;
BYTE byDetSceneID;
BYTE byRes[15];
}NET_DVR_TIME_DETECTION,*LPNET_DVR_TIME_DETECTION;
Members
struSchedTime
Arming schedule, start time and end time parameters, see details in the structure .
byDetSceneID
Detection scene No., 0-invalid, other values: [1,4]. For network camera, the default value of this
parameter is 0.
byRes
Reserved, set to 0.
See Also
78
Device Network SDK (ANPR) Developer Guide
7.1.29 NET_DVR_TRIGGER_COND
Structure about the configuration conditions of triggering mode.
Structure Definition
struct{
DWORD dwSize;
DWORD dwChannel;
DWORD dwtriggerMode;
BYTE byDetSceneID;
BYTE byRes[63];
}NET_DVR_TRIGGER_COND,*LPNET_DVR_TRIGGER_COND;
Members
dwSize
Structure size
dwChannel
Channel No.
dwTriggerMode
Triggering mode, see details in ITC_TRIGGERMODE_TYPE
byDetSceneID
Detection scene No.: 0-invalid, other values: [1,4].
byRes
Reserved, set to 0.
7.1.30 NET_DVR_VEHICLE_ADDINFO
79
Device Network SDK (ANPR) Developer Guide
7.1.31 NET_DVR_VEHICLE_CONTROL_ALARM
Structure about the information of blocklist and allowlist ANPR alarm.
Structure Definition
struct{
DWORD dwSize;
BYTE byListType;
BYTE byPlateType;
BYTE byPlateColor;
BYTE byRes1;
char sLicense[MAX_LICENSE_LEN/*16*/];
char sCardNo[MAX_CARDNO_LEN/*48*/];
NET_DVR_TIME_V30 struAlarmTime;
DWORD dwChannel;
DWORD dwPicDataLen;
BYTE byPicType;
BYTE byPicTransType
BYTE byRes3[2];
char *pPicData;
BYTE byRes2[48];
}NET_DVR_VEHICLE_CONTROL_ALARM,*LPNET_DVR_VEHICLE_CONTROL_ALARM;
Members
dwSize
Structure size.
byListType
List type: 0-allowlist, 1-blocklist, 2-temporary list.
byPlateType
License plate type, seed details in VCA_PLATE_TYPE .
80
Device Network SDK (ANPR) Developer Guide
byPlateColor
License plate color, see details in VCA_PLATE_COLOR .
byRes1
Reserved, set to 0.
sLicense
License plate number
sCardNo
Card No.
struAlarmTime
Alarm time, see details in the structure NET_DVR_TIME_V30 .
dwChannel
Device channel No.
dwPicDataLen
Picture data size, 0-no picture, non-0-with picture data.
byPicType
Picture format: 0-JPEG, 1-BMP, 2-PNG
byPicTransType
Picture transmission method: 0-binary, 1-url
byRes3
Reserved, set to 0.
pPicData
Buffer of picture data in JPEG format.
byRes2
Reserved, set to 0.
7.1.32 NET_DVR_VEHICLE_INFO
Vehicle information structure
Structure Definition
struct{
DWORD dwIndex;
BYTE byVehicleType;
BYTE byColorDepth;
BYTE byColor;
BYTE byRaderState;
WORD wSpeed;
WORD wLength;
81
Device Network SDK (ANPR) Developer Guide
BYTE byIllegalType;
BYTE byVehicleLogoRecog;
BYTE byVehicleSubLogoRecog;
BYTE byVehicleModel;
BYTE byCustomInfo[16];
WORD wVehicleLogoRecog;
BYTE byIsParking;
BYTE byRes;
DWORD dwParkingTime;
BYTE byBelieve;
BYTE byRes3[7];
}NET_DVR_VEHICLE_INFO, *LPNET_DVR_VEHICLE_INFO;
Members
dwIndex
Vehicle No.
byVehicleType
Vehicle type: 0-others, 1-small-sized vehicle, 2-oversized vehicle, 3-pedestrian, 4-two-wheel
vehicle, 5-three-wheel vehicle, 6-motor vehicle
byColorDepth
Vehicle color depth: 0-dark color, 1-light color
byColor
Vehicle color: 0-other, 1-white, 2-silver, 3-gray, 4-black, 5-red, 6-deep blue, 7-blue, 8-yellow, 9-
green, 10-brown, 11-pink, 12-purple, 13-dark gray, 14-cyan, 0xff-unkonwn
byRaderState
Radar status: 0-normal, 1-fault, 2-keeps sending same speed, 3-no data sent, 4-the sent radar
data is too large or too small.
wSpeed
Vehicle speed, unit: km/h
wLength
Vehicle length
byIllegalType
0-Normal, 1-Low Speed, 2-Overspeed, 3-Wrong-Way Driving, 4-Rad Light Running, 5-Driving on
Lane Line, 6-Driving in Wrong Lane at Intersection, 7-Intersection Stranded, 8-Motor Vehicle
Occupied Non-Motor Lane, 9-Illegal Lane Change, 10-Special Lane Occupancy, 11-Yellow Vehicle
Restriction, 12-Intersection Parking, 13-Green Light Parking, 14-Out of Comity to Pedestrian, 15-
Illegal Parking, 16-Illegal U-Turn, 17-Emergency Lane Occupancy, 18-No Right-Turn, 19-No Left-
Turn, 20-Driving on Yellow Line, 21-Seatbelt Unfastened, 22-Pedestrian Red Light Running, 23-
Vehicle Queue Jumping, 24-Illegal High Beam, 25-Driving with Making Call, 26-Left Turn not
Yield to Straight, 27-Right Turn not Yield to Left Turn, 28-U-Turn not Yield to Straight, 29-Small
82
Device Network SDK (ANPR) Developer Guide
Turn at Big Bend, 30-Running Green Light in Congestion, 31-Without Helmet, 32-Manned Non-
Motor Vehicle, 33-Motor Vehicle on Non-Motor Vehicle Lane, 34-Non-Motor Vehicle Umbrella
Tent, 35-Vehicle Discharging Black Smoke, 36-Honk, 37-Parking Over the Lane Line, 38-
Occupying Two Parking Spaces, 39-Parking Over the Lane Line and Occupying Two Parking
Spaces, 40-Not Yield to Vehicle from Right,41-Not Yield to Vehicles in the Roundabout, 42-on
Ramp Not Yield to Main Road, 43-Large-Sized Vehicle on the Lane, 44-Roadster Step on the Gas,
45-Smoke.
byVehicleLogoRecog
Vehicle main brand. For details, refer to the enumeration VLR_VEHICLE_CLASS .
byVehicleSubLogoRecog
Vehicle sub brand.
byVehicleModel
Vehicle model of sub brand
byCustomInfo
Custom information
wVehicleLogoRecog
Vehicle main brands (it is compatible with byVehicleLogoRecog). For details, refer to the
enumeration VLR_VEHICLE_CLASS .
byIsParking
Whether the vehicle is parking: 0-invalid, 1-parking, 2-not parking.
byRes
Reserved.
dwParkingTime
Parking time, unit: second.
byBelieve
Confidence of byIllegalType.
byRes
Reserved.
Remarks
For the vehicle main and sub brands, refer to the list provided by device.
7.1.33 NET_DVR_VIA_LANE_PARAM
Structure about the lane parameters for VIA video detection mode
83
Device Network SDK (ANPR) Developer Guide
Structure Definition
struct{
BYTE byLaneNO;
BYTE byRes[63];
NET_ITC_LANE_LOGIC_PARAM struLogicParam;
NET_ITC_LINE struLaneLine;
NET_ITC_POLYGON struPlateRecog;
BYTE byRes1[300];
}NET_DVR_VIA_LANE_PARAM, *LPNET_DVR_VIA_LANE_PARAM;
Members
byLaneNO
Linked lane No.
byRes
Reserved.
struLogicParam
Lane attribute parameter, see details in the structure NET_ITC_LANE_LOGIC_PARAM .
struLaneLine
Lane line, see details in the structure NET_ITC_LINE .
struLaneLine
License plate recognition area parameter, see details in the structure NET_ITC_POLYGON .
byRes1
Reserved.
See Also
NET_DVR_VIA_VTCOIL_PARAM
7.1.34 NET_DVR_VIA_VTCOIL_PARAM
VIA video detection parameter structure.
Structure Definition
struct{
BYTE byEnable;
BYTE byLaneNum;
BYTE byRes[62];
NET_ITC_LINE struLaneBoundaryLine;
NET_DVR_VIA_LANE_PARAM struLaneParam[MAX_ITC_LANE_NUM/*6*/];
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
84
Device Network SDK (ANPR) Developer Guide
BYTE byRes1[624];
}NET_DVR_VIA_VTCOIL_PARAM, *LPNET_DVR_VIA_VTCOIL_PARAM;
Members
byEnable
Enable or not: 0-no, 1-yes.
byLaneNum
Number of recognized lanes.
byRes
Reserved.
struLaneBoundaryLine
Lane boundary line, which is the left boundary line of the leftmost lane, see details in the
structure NET_ITC_LINE .
struLaneParam
Lane parameter for VIA video detection, see details in the structure
NET_DVR_VIA_LANE_PARAM .
struPlateRecog
License plate recognition parameter, see details in the structure
NET_ITC_PLATE_RECOG_PARAM .
byRes1
Reserved.
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.35 NET_DVR_XML_CONFIG_INPUT
85
Device Network SDK (ANPR) Developer Guide
Related API
NET_DVR_STDXMLConfig
7.1.36 NET_DVR_XML_CONFIG_OUTPUT
86
Device Network SDK (ANPR) Developer Guide
Related API
NET_DVR_STDXMLConfig
7.1.37 NET_IPC_LANE_HVT_PARAM
Mixed checkpoint lane parameter structure of network camera.
Structure Definition
struct{
BYTE byLaneNO;
BYTE byCarDriveDirect;
BYTE byRes[62];
NET_ITC_LINE struLaneLine;
NET_ITC_POLYGON struPlateRecog;
BYTE byRes1[256];
}NET_IPC_LANE_HVT_PARAM, *LPNET_IPC_LANE_HVT_PARAM;
Members
byLaneNO
Lane No.
byCarDriveDirect
Vehicle driving direction, which is enumerated below:
enum _ITC_LANE_CAR_DRIVE_DIRECT_{
ITC_LANE_DRIVE_UNKNOW = 0,
ITC_LANE_DRIVE_UP_TO_DOWN = 1,
ITC_LANE_DRIVE_DOWN_TO_UP = 2
}ITC_LANE_CAR_DRIVE_DIRECT
ITC_LANE_DRIVE_UNKNOW
87
Device Network SDK (ANPR) Developer Guide
Unknown
ITC_LANE_DRIVE_UP_TO_DOWN
Drive from up to bottom on image.
ITC_LANE_DRIVE_DOWN_TO_UP
Drive from bottom to up on image.
byRes
Reserved, set to 0.
struLaneLine
Lane line, refer to the structure NET_ITC_LINE for details.
struPlateRecog
ANPR region parameters, refer to the structure NET_ITC_POLYGON for details.
byRes1
Reserved, set to 0.
See Also
NET_IPC_POST_HVT_PARAM
7.1.38 NET_IPC_POST_HVT_PARAM
Structure of mixed checkpoint trigger parameters of network camera.
Structure Definition
struct{
BYTE byEnable;
BYTE byLaneNum;
BYTE byRes[62];
NET_ITC_LINE struLaneBoundaryLine;
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
NET_IPC_LANE_HVT_PARAM struLaneParam[MAX_ITC_LANE_NUM/*6*/];
char szSceneName[NAME_LEN/*32*/];
NET_VCA_LINE struSnapLine;
BYTE byRes1[392];
}NET_IPC_POST_HVT_PARAM,*LPNET_IPC_POST_HVT_PARAM;
Members
byEnable
Whether to enable mixed checkpoint trigger mode of network camera: 0-no, 1-yes.
byLaneNum
Number of lanes to be recognized.
88
Device Network SDK (ANPR) Developer Guide
byRes
Reserved.
struLaneBoundaryLine
Left boundary line of left lane, refer to the structure NET_ITC_LINE for details.
struPlateRecog
ANPR parameters, refer to the structure NET_ITC_LANE_MPR_PARAM for details.
struLaneParam
Lane parameters, refer to the structure NET_IPC_LANE_HVT_PARAM for details.
szSceneName
Scene name.
struSnapLine
Capture line, it is valid only when the camera is mounted at road side, refer to the structure
NET_VCA_LINE for details.
byRes1
Reserved.
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.39 NET_ITC_EPOLICE_IOTL_PARAM
Structure about IO traffic light parameters for the intersection violation system.
Structure Definition
struct{
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
NET_ITC_SINGLE_IOTL_PARAM struSingleIOTL[MAX_IOSPEED_GROUP_NUM/*4*/];
BYTE byRes[32];
}NET_ITC_EPOLICE_IOTL_PARAM, *LPNET_ITC_EPOLICE_IOTL_PARAM;
Members
struPlateRecog
License plate recognition parameter, see details in the structure
NET_ITC_PLATE_RECOG_PARAM .
struSingleIOTL
IO traffic light parameter of a single group, see details in the structure
NET_ITC_SINGLE_IOTL_PARAM .
byRes
89
Device Network SDK (ANPR) Developer Guide
Reserved.
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.40 NET_ITC_EPOLICE_LANE_PARAM
Structure about lane parameters of RS-485 vehicle detector trigger mode for the intersection
violation system.
Structure Definition
struct{
BYTE byEnable;
BYTE byRelatedDriveWay;
WORD wDistance;
BYTE byRecordEnable;
BYTE byRecordType;
BYTE byPreRecordTime;
BYTE byRecordDelayTime;
BYTE byRecordTimeOut;
BYTE bySignSpeed;
BYTE bySpeedLimit;
BYTE byOverlayDriveWay;
NET_ITC_SERIAL_INFO struSerialInfo;
BYTE byRelatedIOOut[MAX_IOOUT_NUM/*4*/];
BYTE byFlashMode;
BYTE bySerialType;
BYTE byRelatedIOOutEx;
BYTE bySnapPicPreRecord;
NET_ITC_PLATE_RECOG_REGION_PARAM struPlateRecog[MAX_LANEAREA_NUM/*2*/];
BYTE byBigCarSignSpeed;
BYTE byBigCarSpeedLimit;
BYTE byRedTrafficLightChan;
BYTE byYellowTrafficLightChan;
BYTE byRelaLaneDirectionType;
BYTE byRes3[11];
}NET_ITC_EPOLICE_LANE_PARAM, *LPNET_ITC_EPOLICE_LANE_PARAM;
Members
byEnable
Whether to enable: 0-no, 1-yes.
byRelatedDriveWay
Linked lane No.
wDistance
90
Device Network SDK (ANPR) Developer Guide
91
Device Network SDK (ANPR) Developer Guide
Remarks
The linked lane No. configured by byRelatedDriveWay corresponds to the lane in the vehicle
detector for capturing. The lane No. configured by byOverlayDriveWay is the overlay lane No.
which is the actual lane No.
See Also
NET_ITC_EPOLICE_RS485_PARAM
7.1.41 NET_ITC_EPOLICE_RS485_PARAM
Structure about triggering parameters of RS-485 vehicle detector for intersection violation system
and checkpoint intersection violation system.
Structure Definition
struct{
BYTE byRelatedLaneNum;
BYTE byTrafficLightSignalSrc;
BYTE byRes1[2];
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
NET_ITC_EPOLICE_LANE_PARAM struLane[MAX_ITC_LANE_NUM/*6*/];
BYTE byRes[32];
}NET_ITC_EPOLICE_RS485_PARAM, *LPNET_ITC_EPOLICE_RS485_PARAM;
Members
byRelatedLaneNum
92
Device Network SDK (ANPR) Developer Guide
Remarks
The parameters byRedTrafficLightChan and byYellowTrafficLightChan in the structure
NET_ITC_EPOLICE_LANE_PARAM are valid only when byTrafficLightSignalSrc is set to 1.
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.42 NET_ITC_INTERVAL_PARAM
Structure about capture interval parameters.
Structure Definition
struct{
BYTE byIntervalType;
BYTE byRes1[3];
WORD wInterval[MAX_INTERVAL_NUM/*4*/];
BYTE byRes[8];
}NET_ITC_INTERVAL_PARAM, *LPNET_ITC_INTERVAL_PARAM;
Members
byIntervalType
Interval type: 0-time (default), 1-distance.
byRes1
Reserved.
wInterval
93
Device Network SDK (ANPR) Developer Guide
Burst interval (unit: millisecond) or burst distance (unit: decimeter). The burst interval type is
determined by byIntervalType.
byRes
Reserved.
7.1.43 NET_ITC_IO_LIGHT_PARAM
Structure about IO access traffic light parameters.
Structure Definition
struct{
NET_ITC_SINGLE_IO_LIGHT_PARAM struIOLight[MAX_LIGHT_NUM/*6*/];
BYTE byRes[8];
}NET_ITC_IO_LIGHT_PARAM, *LPNET_ITC_IO_LIGHT_PARAM;
Members
struIOLight
Single IO access traffic light parameters, see details in the structure
NET_ITC_SINGLE_IO_LIGHT_PARAM .
byRes
Reserved.
See Also
NET_ITC_LIGHT_ACCESSPARAM_UNION
7.1.44 NET_ITC_LANE_HVT_PARAM_V50
Structure about the extended lane parameters of the mixed-traffic checkpoint.
Structure Definition
struct{
BYTE byLaneNO;
BYTE byFlashMode;
BYTE bySignSpeed;
BYTE bySpeedLimit;
BYTE bySignLowSpeed;
BYTE byLowSpeedLimit;
BYTE byBigCarSignSpeed;
BYTE byBigCarSpeedLimit;
BYTE byBigCarSignLowSpeed;
BYTE byBigCarLowSpeedLimit;
BYTE bySnapTimes;
94
Device Network SDK (ANPR) Developer Guide
BYTE byDriveLineSnapTime;
BYTE byHighSpeedSnapTime;
BYTE byLowSpeedSnapTime;
BYTE byBanSnapTime;
BYTE byReverseSnapTime;
BYTE byRelatedDriveWay;
BYTE byLaneType;
BYTE byRelaLaneDirectionType;
BYTE byRes1[29];
DWORD dwVioDetectType;
DWORD dwRelatedIOOut;
NET_ITC_LINE struTrigLine;
NET_ITC_LINE struLineLeft;
NET_ITC_POLYGON struPlateRecog;
NET_ITC_LANE_LOGIC_PARAM struLane;
NET_ITC_INTERVAL_PARAM struInterval;
BYTE byRes2[280];
}NET_ITC_LANE_HVT_PARAM_V50, *LPNET_ITC_LANE_HVT_PARAM_V50;
Members
byLaneNO
Linked lane No. used for overlaying and uploading, ranging from 1 to 255.
byFlashMode
Flashing mode of the flash light: 0-simultaneous, 1-sequential.
bySignSpeed
Maximum marked speed limit for small-sized vehicle, unit: km/h.
bySpeedLimit
Maximum speed limit for small-sized vehicle, unit: km/h.
bySignLowSpeed
Minimum marked speed limit for small-sized vehicle, unit: km/h.
byLowSpeedLimit
Minimum speed limit for small-sized vehicle, unit: km/h.
byBigCarSignSpeed
Maximum marked speed limit for large-sized vehicle, unit: km/h.
byBigCarSpeedLimit
Maximum speed limit for large-sized vehicle, unit: km/h.
byBigCarSignLowSpeed
Minimum marked speed limit for large-sized vehicle, unit: km/h.
byBigCarLowSpeedLimit
Minimum speed limit for large-sized vehicle, unit: km/h.
bySnapTimes
95
Device Network SDK (ANPR) Developer Guide
96
Device Network SDK (ANPR) Developer Guide
See Also
NET_ITC_POST_HVT_PARAM_V50
7.1.45 NET_ITC_LANE_IMT_PARAM
Structure about lane parameters for smart monitoring.
Structure Definition
struct{
BYTE byLaneNO;
BYTE byRelaLaneDirectionType;
BYTE byRes[146];
NET_ITC_LINE struLaneLine;
BYTE byRes1[256];
}NET_ITC_LANE_IMT_PARAM, *LPNET_ITC_LANE_IMT_PARAM;
Members
byLaneNO
Overlay lane No.
byRelaLaneDirectionType
Linked lane direction type, see details in the structure ITC_RELA_LANE_DIRECTION_TYPE . It
corresponds to the linked lane No. to ensure that the lane is unique.
byRes
Reserved, set to 0.
struLaneLine
Lane line, see details in the structure NET_ITC_LINE .
byRes1
Reserved, set to 0.
See Also
NET_ITC_POST_IMT_PARAM
97
Device Network SDK (ANPR) Developer Guide
7.1.46 NET_ITC_LANE_LOGIC_PARAM
Structure about lane attribute parameters
Structure Definition
struct{
BYTE byUseageType;
BYTE byDirectionType;
BYTE byCarDriveDirect;
BYTE byRes[33];
}NET_ITC_LANE_LOGIC_PARAM, *LPNET_ITC_LANE_LOGIC_PARAM;
Members
byUseageType
Lane usage type, see details in the structure ITC_LANE_USEAGE_TYPE .
byDirectionType
Lane direction type, see details in the structure ITC_LANE_DIRECTION_TYPE .
byCarDriveDirect
Vehicle driving direction, see details below:
enum{
ITC_LANE_DRIVE_UNKNOW = 0,
ITC_LANE_DRIVE_UP_TO_DOWN = 1,
ITC_LANE_DRIVE_DOWN_TO_UP = 2
}ITC_LANE_CAR_DRIVE_DIRECT
ITC_LANE_DRIVE_UNKNOW
Unknown.
ITC_LANE_DRIVE_UP_TO_DOWN
Driving from top to bottom on image (down direction).
ITC_LANE_DRIVE_DOWN_TO_UP
Driving from bottom to top on image (up direction).
byRes
Reserved, set to 0.
See Also
NET_ITC_LANE_HVT_PARAM_V50
NET_ITC_LANE_VIDEO_EPOLICE_PARAM
98
Device Network SDK (ANPR) Developer Guide
7.1.47 NET_ITC_LANE_MPR_PARAM
Structure about the lane parameters in video recognition mode.
Structure Definition
struct{
BYTE byLaneNO;
union{
BYTE uLen[4];
struct{
BYTE byIONo;
BYTE byTriggerType;
BYTE byRes1[2];
}struIO;
struct{
BYTE byRelateChan;
BYTE byRes2[3];
}struRS485;
}uTssParamInfo;
BYTE byCarDriveDirect;
BYTE byRes[58];
NET_ITC_LINE struLaneLine;
NET_ITC_POLYGON struPlateRecog;
BYTE byRes1[256];
}NET_ITC_LANE_MPR_PARAM,*LPNET_ITC_LANE_MPR_PARAM;
Members
byLaneNO
Vehicle lane No.
uTssParamInfo
Triggering parameter union, see details below.
uLen
Union size, which is 4 bytes.
struIO
Structure about the parameters of alarm input triggering mode, see details below.
byIONo
Linked alarm input No., which starts from 1.
byTriggerType
Triggering mode, 0-falling edge,1-rising edge
byRes1
Reserved, set as 0.
99
Device Network SDK (ANPR) Developer Guide
struRS485
Structure about the parameters of RS-485 triggering mode, see details below.
byRelateChan
Linked vehicle detector No., which is between 1 and 16.
byRes2
Reserved, set as 0.
byCarDriveDirect
Vehicle driving direction, see details below:
enum{
ITC_LANE_DRIVE_UNKNOW = 0,
ITC_LANE_DRIVE_UP_TO_DOWN = 1,
ITC_LANE_DRIVE_DOWN_TO_UP = 2
}ITC_LANE_CAR_DRIVE_DIRECT
ITC_LANE_DRIVE_UNKNOW
Unknown.
ITC_LANE_DRIVE_UP_TO_DOWN
Drive from top to bottom on image.
ITC_LANE_DRIVE_DOWN_TO_UP
Drive from bottom to top on image.
byRes
Reserved
struLaneLine
Lane line, see details in the structure NET_ITC_LINE .
struPlateRecog
License plate region information, see details in the structure NET_ITC_POLYGON .
byRes1
Reserved
Remarks
The structure struIO in the union uTssParamInfo is valid when the value of parameter
bySourceType (in structure NET_ITC_POST_MPR_PARAM ) equal to1; the structure struRS485 in
the union uTssParamInfo is valid when the value of parameter bySourceType (in structure
NET_ITC_POST_MPR_PARAM ) equal to 2.
7.1.48 NET_ITC_LANE_NOCOMITY_PEDESTRIAN_PARAM
Structure about lane parameters of triggering mode of not yielding to pedestrian.
100
Device Network SDK (ANPR) Developer Guide
Structure Definition
struct{
BYTE byRelatedDriveWay;
BYTE byRelaLaneDirectionType;
BYTE byPedestriansNum;
BYTE byVehicleSpeed;
DWORD dwVehicleInterval;
BYTE byPedesDetRule;
BYTE byRes[3];
NET_ITC_LINE struLaneLine;
NET_ITC_LINE struStopLine;
NET_ITC_POLYGON struPlateRecog;
BYTE byRes1[280];
}NET_ITC_LANE_NOCOMITY_PEDESTRIAN_PARAM, *LPNET_ITC_LANE_NOCOMITY_PEDESTRIAN_PARAM;
Members
byRelatedDriveWay
Linked lane No.
byRelaLaneDirectionType
Linked lane direction type.
byPedestriansNum
Number of pedestrian threshold, ranging from 1 to 100, the default value is 1.
byVehicleSpeed
Vehicle speed threshold, ranging from 1 to 100, the default value is 0.
dwVehicleInterval
Vehicle following detection threshold, ranging from 0 to 65536, the default value is 0.
byPedesDetRule
Pedestrian detection rule, which indicates the walking direction of the pedestrian in the
detection area: 0-from right to left, 1-from left to right.
byRes
Reserved, set to 0.
struLaneLine
Lane line, see details in the structure NET_ITC_LINE .
struStopLine
Stop line, see details in the structure NET_ITC_LINE .
struPlateRecog
License plate recognition area, see details in the structure NET_ITC_POLYGON .
byRes1
101
Device Network SDK (ANPR) Developer Guide
Reserved, set to 0.
See Also
NET_ITC_NOCOMITY_PEDESTRIAN_PARAM
7.1.49 NET_ITC_LANE_PARAM
Lane parameter structure
Structure Definition
struct{
BYTE byEnable;
BYTE byRelatedDriveWay;
WORD wDistance;
WORD wTrigDelayTime;
BYTE byTrigDelayDistance;
BYTE bySpeedCapEn;
BYTE bySignSpeed;
BYTE bySpeedLimit;
BYTE bySnapTimes;
BYTE byOverlayDriveWay;
NET_ITC_INTERVAL_PARAM struInterval;
BYTE byRelatedIOOut[MAX_IOOUT_NUM];
BYTE byFlashMode;
BYTE byCartSignSpeed;
BYTE byCartSpeedLimit;
BYTE byRelatedIOOutEx;
NET_ITC_PLATE_RECOG_REGION_PARAM struPlateRecog[MAX_LANEAREA_NUM];
BYTE byLaneType;
BYTE byUseageType;
BYTE byRelaLaneDirectionType;
BYTE byLowSpeedLimit;
BYTE byBigCarLowSpeedLimit;
BYTE byLowSpeedCapEn;
BYTE byEmergencyCapEn;
BYTE byRes[9];
}NET_ITC_LANE_PARAM,*LPNET_ITC_LANE_PARAM;
Members
byEnable
Whether to enable this lane: 0-no, 1-yes.
byRelatedDriveWay
Linked lane No., which matches with the lane of vehicle detector, and it is used for capture.
wDistance
102
Device Network SDK (ANPR) Developer Guide
103
Device Network SDK (ANPR) Developer Guide
byUseageType
Lane usage, which is enumerated in ITC_LANE_USEAGE_TYPE .
byRelaLaneDirectionType
Linked lane direction, which is enumerated in ITC_RELA_LANE_DIRECTION_TYPE .
byLowSpeedLimit
Low speed limit of small-sized vehicle, unit: km/h.
byBigCarLowSpeedLimit
Low speed limit of large-sized vehicle, unit: km/h.
byLowSpeedCapEn
Whether to trigger capture when low speed is detected: 0-no, 1-yes.
byEmergencyCapEn
Whether to trigger capture when emergency lane occupation is detected.
byRes
Reserved.
Remarks
7.1.50 NET_ITC_LANE_PRS_PARAM
Structure about lane parameters of video detection triggering mode.
Structure Definition
struct{
BYTE byLaneNO;
union{
BYTE uLen[4];
struct{
BYTE byIONo;
BYTE byTriggerType;
BYTE byRes1[2];
}struIO;
struct{
BYTE byRelateChan;
BYTE byRes2[3];
}struRS485;
}uTssParamInfo;
BYTE byRes[59];
NET_ITC_LINE struLaneLine;
NET_ITC_POLYGON struPlateRecog;
BYTE byRelaLaneDirectionType;
BYTE byRes2[3];
NET_ITC_LINE struTrigLine;
104
Device Network SDK (ANPR) Developer Guide
BYTE byRes1[228];
}NET_ITC_LANE_PRS_PARAM, *LPNET_ITC_LANE_PRS_PARAM;
Members
byLaneNO
Lane No.
uTssParamInfo
Triggering parameters information union, see its members below:
uLen
Union size (4 bytes).
struIO
Structure about triggering mode parameters, see its members below:
byIONo
Linked IO No., starting from 1.
byTriggerType
Triggering mode: 0-falling edge, 1-rising edge.
byRes1
Reserved, set to 0.
struRS485
Structure about RS-485 triggering mode parameters, see its members below:
byRelateChan
Linked vehicle detector channel No., ranging from 1 to 16.
byRes2
Reserved, set to 0.
byRes
Reserved.
struLaneLine
Lane line, see details in the structure NET_ITC_LINE .
struPlateRecog
License plate recognition area, see details in the structure NET_ITC_POLYGON .
byRelaLaneDirectionType
Linked lane direction type, see details in the structure ITC_RELA_LANE_DIRECTION_TYPE .
byRes2
Reserved.
struTrigLine
105
Device Network SDK (ANPR) Developer Guide
See Also
NET_ITC_POST_PRS_PARAM
7.1.51 NET_ITC_LANE_VIDEO_EPOLICE_PARAM
Structure about the lane parameters of video intersection violation system triggering mode.
Structure Definition
struct{
BYTE byLaneNO;
BYTE bySensitivity;
BYTE byEnableRadar;
BYTE byRelaLaneDirectionType;
NET_ITC_LANE_LOGIC_PARAM struLane;
NET_ITC_VIOLATION_DETECT_PARAM struVioDetect;
NET_ITC_VIOLATION_DETECT_LINE struLine;
NET_ITC_POLYGON struPlateRecog;
BYTE byRecordEnable;
BYTE byRecordType;
BYTE byPreRecordTime;
BYTE byRecordDelayTime;
BYTE byRecordTimeOut;
BYTE byCarSpeedLimit;
BYTE byCarSignSpeed;
BYTE bySnapPicPreRecord;
NET_ITC_INTERVAL_PARAM struInterval;
BYTE byRes[36];
}NET_ITC_LANE_VIDEO_EPOLICE_PARAM, *LPNET_ITC_LANE_VIDEO_EPOLICE_PARAM;
Members
byLaneNO
Linked lane No.
bySensitivity
Coil sensitivity, ranging from 1 to 100.
byEnableRadar
Whether to enable radar detection: 0-no, 1-yes.
byRelaLaneDirectionType
106
Device Network SDK (ANPR) Developer Guide
107
Device Network SDK (ANPR) Developer Guide
7.1.52 NET_ITC_LIGHT_ACCESSPARAM_UNION
Traffic light connection parameters union.
Structure Definition
union {
DWORD uLen[122];
NET_ITC_IO_LIGHT_PARAM struIOLight;
NET_ITC_RS485_LIGHT_PARAM struRS485Light;
NET_ITC_VIDEO_DETECT_LIGHT_PARAM struVideoDelectLight;
}NET_ITC_LIGHT_ACCESSPARAM_UNION, *LPNET_ITC_LIGHT_ACCESSPARAM_UNION;
Members
uLen
Union size.
struIOLight
IO access traffic light parameters, see details in the structure NET_ITC_IO_LIGHT_PARAM .
struRS485Light
RS-485 access traffic light parameters, see details in the structure
NET_ITC_RS485_LIGHT_PARAM .
struVideoDelectLight
Traffic light parameters detected in the video, see details in the structure
NET_ITC_VIDEO_DETECT_LIGHT_PARAM .
See Also
NET_ITC_TRAFFIC_LIGHT_PARAM
7.1.53 NET_ITC_LINE
Traffic line information structure
Structure Definition
struct{
struLine;
BYTE byLineType;
BYTE byRes[7];
}NET_ITC_LINE, *LPNET_ITC_LINE;
108
Device Network SDK (ANPR) Developer Guide
Members
struLine
Traffic line parameters.
byLineType
Traffic line type, see details below.
enum{
ITC_LINT_UNKNOW = 0,
ITC_LINE_WHITE = 1,
ITC_LINE_STOP = 2,
ITC_LINE_SINGLE_YELLOW = 3,
ITC_LINE_DOUBLE_YELLOW = 4,
ITC_LINE_GUARD_RAIL = 5,
ITC_LINE_NO_CROSS = 6
}ITC_LINE_TYPE
ITC_LINT_UNKNOW
Unknown
ITC_LINE_WHITE
Solid white line between lanes
ITC_LINE_STOP
Stop line
ITC_LINE_SINGLE_YELLOW
Single yellow line
ITC_LINE_DOUBLE_YELLOW
Double yellow line
ITC_LINE_GUARD_RAIL
Guardrail on the lane
ITC_LINE_NO_CROSS
No-Crossing line
byRes1
Reserved, set to 0.
7.1.54 NET_ITC_NOCOMITY_PEDESTRIAN_PARAM
Structure about triggering parameters of not yielding to pedestrian.
109
Device Network SDK (ANPR) Developer Guide
Structure Definition
struct{
BYTE byEnable;
BYTE byLaneNum;
BYTE byRes[74];
NET_ITC_LINE struLaneBoundaryLine;
NET_ITC_LINE struTriggerLine;
NET_ITC_POLYGON struPedesDetRecog;
NET_ITC_LANE_NOCOMITY_PEDESTRIAN_PARAM struLaneParam[MAX_ITC_LANE_NUM/*6*/];
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
BYTE byRes1[400];
}NET_ITC_NOCOMITY_PEDESTRIAN_PARAM, *LPNET_ITC_NOCOMITY_PEDESTRIAN_PARAM;
Members
byEnable
Whether to enable: 0-no, 1-yes.
byLaneNum
Number of recognized lanes, ranging from 1 to 3.
byRes
Reserved, set to 0.
struLaneBoundaryLine
Border line of the lane, which is the border line of the rightmost lane, see details in the
structure NET_ITC_LINE .
struTriggerLine
Triggering line of not yielding to pedestrian, see details in the structure NET_ITC_LINE .
struPedesDetRecog
Pedestrian detection area, see details in the structure NET_ITC_POLYGON .
struLaneParam
Lane parameters, each array represents a lane, see details in the structure
NET_ITC_LANE_NOCOMITY_PEDESTRIAN_PARAM .
struPlateRecog
License plate recognition parameters, see details in the structure
NET_ITC_PLATE_RECOG_PARAM .
byRes1
Reserved, set to 0.
See Also
NET_ITC_TRIGGER_PARAM_UNION
110
Device Network SDK (ANPR) Developer Guide
7.1.55 NET_ITC_PLATE_RECOG_PARAM
ANPR parameter structure.
Structure Definition
struct{
BYTE byDefaultCHN[MAX_CHJC_NUM/*3*/];
BYTE byEnable;
DWORD dwRecogMode;
BYTE byVehicleLogoRecog;
BYTE byProvince;
BYTE byRegion;
BYTE byRes1;
WORD wPlatePixelWidthMin;
WORD wPlatePixelWidthMax;
BYTE byRes[24];
}NET_ITC_PLATE_RECOG_PARAM,*LPNET_ITC_PLATE_RECOG_PARAM;
Members
byDefaultCHN
Province
byEnable
Whether to enable ANPR for this region: 0-no, 1-yes.
dwRecogMode
Recognition type:
● bit0-Recognition direction: 0-from front, 1-from back (back plate recognition);
111
Device Network SDK (ANPR) Developer Guide
7.1.56 NET_ITC_PLATE_RECOG_REGION_PARAM
Structure about license plate recognition area parameters.
Structure Definition
struct{
BYTE byMode;
BYTE byRes1[3];
union{
NET_VCA_RECT struRect;
NET_ITC_POLYGON struPolygon;
}uRegion;
BYTE byRes[16];
}NET_ITC_PLATE_RECOG_REGION_PARAM, *LPNET_ITC_PLATE_RECOG_REGION_PARAM;
Members
byMode
Area type: 0-rectangle area, 1-polygon area.
byRes1
Reserved.
struRect
112
Device Network SDK (ANPR) Developer Guide
7.1.57 NET_ITC_POLYGON
Polygon information structure.
Structure Definition
struct{
DWORD dwPointNum;
NET_VCA_POINT struPos[ITC_MAX_POLYGON_POINT_NUM/*20*/];
}NET_ITC_POLYGON,*LPNET_ITC_POLYGON;
Members
dwPointNum
Number of valid points, which should be larger than and equal to 3, if three points are on a
straight line, or the lines crossed, it indicates the invalid region.
struPo
Polygon boundary points, the maximum number is 20, refer to the structure NET_VCA_POINT
for details.
7.1.58 NET_ITC_POST_HVT_PARAM_V50
Structure about the extended parameters of the mixed-traffic checkpoint.
Structure Definition
struct{
BYTE byLaneNum;
BYTE byCapType;
BYTE byCapMode;
BYTE bySceneMode;
BYTE bySpeedMode;
BYTE byLineRuleEffect;
BYTE byRes1[78];
NET_ITC_LINE struLeftTrigLine;
NET_ITC_LINE struRigtTrigLine;
NET_ITC_LINE struLaneBoundaryLine;
NET_ITC_POLYGON struDetectArea;
NET_DVR_GEOGLOCATION struGeogLocation;
113
Device Network SDK (ANPR) Developer Guide
NET_ITC_LANE_HVT_PARAM_V50 struLaneParam[MAX_ITC_LANE_NUM/*6*/];
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
BYTE byRes2[260];
}NET_ITC_POST_HVT_PARAM_V50, *LPNET_ITC_POST_HVT_PARAM_V50;
Members
byLaneNum
Number of recognized lanes, ranging from 1 to 6.
byCapType
Capture type: 0-motor vehicle, non-motor vehicle and pedestrian (default), 1-motor vehicle.
byCapMode
Capture mode: 0-video frame extracting, 1-interrupt and capture, 2-mixed mode.
bySceneMode
Scene type: 0-city roads (default), 1-community entrance and exit, 2-highway.
bySpeedMode
Speed detection mode: 0-no speed detection, 1-radar speed detection, 2-video speed
detection.
byLineRuleEffect
Validity of triggering rule line, each bit represents a triggering rule line, bit0-left triggering rule
line, bit1-right triggering rule line, bit2-video detection area.
byRes1
Reserved, set to 0.
struLeftTrigLine
Left triggering line, which is a vertical line.
struRigtTrigLine
Right triggering line, which is a vertical line.
struLaneBoundaryLine
Border line of the lane, which is the right border line of the rightmost lane.
struDetectArea
Video detection area, see details in the structure NET_ITC_POLYGON .
struGeogLocation
Address and location, see details in the structure NET_DVR_GEOGLOCATION .
struLaneParam
Properties of a single lane, each array indicates a kind of lane information, see details in the
structure NET_ITC_LANE_HVT_PARAM_V50 .
struPlateRecog
114
Device Network SDK (ANPR) Developer Guide
7.1.59 NET_ITC_POST_IMT_PARAM
Structure about configuration parameters for smart monitoring.
Structure Definition
struct{
BYTE byEnable;
BYTE byLaneNum;
BYTE bySnapMode;
BYTE byRes[61];
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
NET_ITC_LINE struLaneBoundaryLine;
NET_ITC_LANE_IMT_PARAM struLaneParam[MAX_ITC_LANE_NUM/*6*/];
BYTE byRes1[1584];
}NET_ITC_POST_IMT_PARAM, *LPNET_ITC_POST_IMT_PARAM;
Members
byEnable
Whether to enable smart monitoring mode: 0-disable, 1-enable.
byLaneNum
Number of recognized lanes, ranging from 1 to 6.
bySnapMode
Capture type: 0-motor vehicle, 1-motor vehicle, non-motor vehicle, and pedestrian.
byRes
Reserved, set to 0.
struPlateRecog
License plate recognition parameters, see details in the structure
NET_ITC_PLATE_RECOG_PARAM .
struLaneBoundaryLine
Lane boundary line, which is the left boundary line of the leftmost lane, see details in the
structure NET_ITC_LINE .
struLaneParam
Properties of a single lane, see details in the structure NET_ITC_LANE_IMT_PARAM .
byRes1
115
Device Network SDK (ANPR) Developer Guide
Reserved, set to 0.
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.60 NET_ITC_POST_IOSPEED_PARAM
Structure about checkpoint IO speed detection parameters.
Structure Definition
struct{
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
NET_ITC_SINGLE_IOSPEED_PARAM struSingleIOSpeed[MAX_IOSPEED_GROUP_NUM/*4*/];
BYTE byRes[32];
}NET_ITC_POST_IOSPEED_PARAM, *LPNET_ITC_POST_IOSPEED_PARAM;
Members
struPlateRecog
License plate recognition parameters, see details in the structure
NET_ITC_PLATE_RECOG_PARAM .
struSingleIOSpeed
Parameters of a single IO speed detection group, see details in the structure
NET_ITC_SINGLE_IOSPEED_PARAM .
byRes
Reserved.
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.61 NET_ITC_POST_MOBILE_PARAM
Structure about mobile traffic triggering parameters.
Structure Definition
struct{
BYTE byEnable;
BYTE bySceneMode;
WORD wExpressWayCapType;
WORD wUrbanRoadCapType;
BYTE byCapNum;
BYTE byRecordEnable;
116
Device Network SDK (ANPR) Developer Guide
DWORD dwPreRecordTime;
DWORD dwOverRecordTime;
BYTE byRes[256];
}NET_ITC_POST_MOBILE_PARAM, *LPNET_ITC_POST_MOBILE_PARAM;
Members
byEnable
Whether to enable: 0-no, 1-yes.
bySceneMode
Scene mode: 0-highway, 1-city road.
wExpressWayCapType
Highway capture type, represented by bit: bit0-checkpoint, bit1-large-sized vehicle occupying
lane, bit2-driving on hard shoulder.
wUrbanRoadCapType
City road capture type, represented by bit: bit0-checkpoint, bit1-motor vehicle on non-motor
vehicle lane, bit2-occupying dedicated lane.
byCapNum
Number of captured pictures, ranging from 2 to 3.
byRecordEnable
Whether to enable violation recording: 0-no, 1-yes.
dwPreRecordTime
Pre-record time, unit: second.
dwOverRecordTime
Recording timeout, unit: second.
byRes
Reserved, set to 0.
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.62 NET_ITC_POST_MPR_PARAM
Structure about the trigger parameters of multi-frame detection.
Structure Definition
struct{
BYTE byEnable;
BYTE byLaneNum;
BYTE bySourceType;
117
Device Network SDK (ANPR) Developer Guide
BYTE byPicUploadType;
BYTE byRoadType;
BYTE byRes2;
WORD wCustomDelayTime;
BYTE byRes[56];
NET_ITC_LINE struLaneBoundaryLine;
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
NET_ITC_LANE_MPR_PARAM struLaneParam[MAX_ITC_LANE_NUM/*6*/];
char szSceneName[NAME_LEN/*32*/];
NET_VCA_LINE struSnapLine;
BYTE byRes1[392];
}NET_ITC_POST_MPR_PARAM,*LPNET_ITC_POST_MPR_PARAM;
Members
byEnable
Whether to enable: 0-no, 1-yes
byLaneNum
Number of recognized lanes
bySourceType
Signal source type, 0-triggered by MPR (triggered by video), 1-troggered by alarm input
(inductive loop), 2-triggered by RS-485.
byPicUploadType
Picture uploading type: 0-upload all, 1-forward uploading, 2-backward uploading
byRoadType
Road Mode: 0-entrance/exit, 1-city road, 2-custom, 3-alarm input
byRes2
Reserved
wCustomDelayTime
Custom capture delay time (it is valid when byRoadType is "2"), value range: [0,15000], unit: ms
byRes
Reserved.
struLaneBoundaryLine
Left boundary of left lane, see details in the structure NET_ITC_LINE .
struPlateRecog
ANPR parameters, see details in NET_ITC_PLATE_RECOG_PARAM .
struLaneParam
Lane multi-frame detection parameters, see details in NET_ITC_LANE_MPR_PARAM .
szSceneName
Scene name
118
Device Network SDK (ANPR) Developer Guide
struSnapLine
Capture line, it valid when camera is mounted at road side, see details in NET_VCA_LINE .
byRes1
Reserved.
7.1.63 NET_ITC_POST_PRS_PARAM
Structure about parameters triggering video detection (PRS).
Structure Definition
struct{
BYTE byEnable;
BYTE byLaneNum;
BYTE bySourceType;
BYTE bySnapMode;
BYTE byCapMode;
BYTE byNoPlatCarCap;
BYTE bySceneMode;
BYTE byRes[57];
NET_ITC_LINE struLaneBoundaryLine;
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
NET_ITC_LANE_PRS_PARAM struLaneParam[MAX_ITC_LANE_NUM/*6*/];
BYTE byRes1[440];
}NET_ITC_POST_PRS_PARAM, *LPNET_ITC_POST_PRS_PARAM;
Members
byEnable
Whether to enable: 0-no, 1-yes.
byLaneNum
Number of recognized lanes.
bySourceType
Signal source type: 0-video detection, 1-linked IO trigger (inductive loops), 2-linked RS-485
triggering signal.
bySnapMode
Capture mode: 0-panorama image, 1-panorama image+feature view.
byCapMode
0-strobe light mode, 1-flash light mode. It is valid when bySourceType is set to 0.
byNoPlatCarCap
Whether to capture vehicle without license plate: 0-no, 1-yes.
bySceneMode
119
Device Network SDK (ANPR) Developer Guide
Scene mode: 0-normal entrance and exit, 1-toll station (vehicles will stay for longer time), 2-
underground parking lot (there will be dark day and night).
byRes
Reserved, set to 0.
struLaneBoundaryLine
Lane boundary line, which is the left boundary line of the leftmost lane, see details in the
structure NET_ITC_LINE .
struPlateRecog
License plate recognition parameters, see details in the structure
NET_ITC_PLATE_RECOG_PARAM .
struLaneParam
Lane parameters, see details in the structure NET_ITC_LANE_PRS_PARAM .
byRes1
Reserved, set to 0.
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.64 NET_ITC_POST_RS485_PARAM
Trigger parameter structure of RS-485 vehicle detector in the checkpoint.
Structure Definition
struct{
BYTE byRelatedLaneNum;
BYTE byTriggerSpareMode;
BYTE byFaultToleranceTime;
BYTE byRes1;
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
NET_ITC_LANE_PARAM struLane[MAX_ITC_LANE_NUM/*6*/];
BYTE byRes[32];
}NET_ITC_POST_RS485_PARAM,*LPNET_ITC_POST_RS485_PARAM;
Members
byRelatedLaneNum
Number of linked lanes.
byTriggerSpareMode
Trigger mode for spare (when the coil trigger is in fault): 0-none, 1-wireless virtual coil mode, 2-
mixed checkpoint mode.
120
Device Network SDK (ANPR) Developer Guide
byFaultToleranceTime
Error tolerance time, unit: minute, which is used to check if the vehicle detector has normally
worked for maximum time period.
byRes1
Reserved.
struPlateRecog
ANPR parameters, refer to the structure NET_ITC_PLATE_RECOG_PARAM for details.
struLane
Linked lane parameters, refer to the structure NET_ITC_LANE_PARAM for details.
byRes
Reserved.
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.65 NET_ITC_POST_RS485_RADAR_PARAM
Structure about checkpoint RS-485 radar triggering parameters.
Structure Definition
struct{
BYTE byRelatedLaneNum;
BYTE byRes1[3];
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
NET_ITC_LANE_PARAM struLane[MAX_ITC_LANE_NUM/*6*/];
NET_ITC_RADAR_PARAM struRadar;
BYTE byRes[32];
}NET_ITC_POST_RS485_RADAR_PARAM, *LPNET_ITC_POST_RS485_RADAR_PARAM;
Members
byRelatedLaneNum
Number of linked lanes.
byRes1
Reserved.
struPlateRecog
License plate recognition parameters, see details in the structure
NET_ITC_PLATE_RECOG_PARAM .
struLane
Linked lane parameters, see details in the structure NET_ITC_LANE_PARAM .
121
Device Network SDK (ANPR) Developer Guide
struRadar
Radar parameters, see details in the structure NET_ITC_RADAR_PARAM .
byRes
Reserved.
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.66 NET_ITC_POST_SINGLEIO_PARAM
Structure about single IO triggering parameters.
Structure Definition
struct{
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
NET_ITC_SINGLEIO_PARAM struSingleIO[MAX_IOIN_NUMEX/*10*/];
}NET_ITC_POST_SINGLEIO_PARAM, *LPNET_ITC_POST_SINGLEIO_PARAM;
Members
struPlateRecog
License plate recognition parameters, see details in the structure
NET_ITC_PLATE_RECOG_PARAM .
struSingleIO
Single IO triggering parameters, the array 0 refers to IO 1, the array 1 refers to IO 2, and so on,
see details in the structure NET_ITC_SINGLEIO_PARAM .
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.67 NET_ITC_POST_VTCOIL_PARAM
Structure of MPR trigger parameters in checkpoint.
Structure Definition
struct{
BYTE byEnable;
BYTE byLaneNum;
BYTE bySourceType;
BYTE byPicUploadType;
BYTE byRoadType;
BYTE byRes2;
122
Device Network SDK (ANPR) Developer Guide
WORD wCustomDelayTime;
BYTE byRes[56];
NET_ITC_LINE struLaneBoundaryLine;
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
NET_ITC_LANE_MPR_PARAM struLaneParam[MAX_ITC_LANE_NUM/*6*/];
char szSceneName[NAME_LEN/*32*/];
NET_VCA_LINE struSnapLine;
BYTE byRes1[392];
}NET_ITC_POST_MPR_PARAM,*LPNET_ITC_POST_MPR_PARAM;
Members
byEnable
Whether to enable checkpoint MPR trigger mode: 0-no, 1-yes.
byLaneNum
Number of lanes to be recognized.
bySourceType
Signal source type: 0-MPR triggered (video), 1-linked IO triggered (ground coil), 2-linked RS-485
triggered.
byPicUploadType
Picture type to be uploaded: 0-upload all, 1-, 2-
byRoadType
Lane type: 0-entrance and exit, 1-urban road, 2-custom, 3-alarm input.
byRes2
Reserved.
wCustomDelayTime
Custom capture delay time, it is valid when byRoadType is "2", unit: ms, value range: [0,15000].
byRes
Reserved.
struLaneBoundaryLine
Left boundary line of left lane, refer to the structure NET_ITC_LINE for details.
truPlateRecog
ANPR parameters, refer to the structure NET_ITC_LANE_MPR_PARAM for details.
struLaneParam
MPR lane parameters, refer to the structure NET_ITC_PLATE_RECOG_PARAM for details.
szSceneName
Scene name.
struSnapLine
123
Device Network SDK (ANPR) Developer Guide
Capture line, it is valid only when the camera is mounted at road side, refer to the structure
NET_VCA_LINE for details.
byRes1
Reserved.
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.68 NET_ITC_POST_MPR_PARAM
Structure about the trigger parameters of multi-frame detection.
Structure Definition
struct{
BYTE byEnable;
BYTE byLaneNum;
BYTE bySourceType;
BYTE byPicUploadType;
BYTE byRoadType;
BYTE byRes2;
WORD wCustomDelayTime;
BYTE byRes[56];
NET_ITC_LINE struLaneBoundaryLine;
NET_ITC_PLATE_RECOG_PARAM struPlateRecog;
NET_ITC_LANE_MPR_PARAM struLaneParam[MAX_ITC_LANE_NUM/*6*/];
char szSceneName[NAME_LEN/*32*/];
NET_VCA_LINE struSnapLine;
BYTE byRes1[392];
}NET_ITC_POST_MPR_PARAM,*LPNET_ITC_POST_MPR_PARAM;
Members
byEnable
Whether to enable: 0-no, 1-yes
byLaneNum
Number of recognized lanes
bySourceType
Signal source type, 0-triggered by MPR (triggered by video), 1-troggered by alarm input
(inductive loop), 2-triggered by RS-485.
byPicUploadType
Picture uploading type: 0-upload all, 1-forward uploading, 2-backward uploading
byRoadType
124
Device Network SDK (ANPR) Developer Guide
7.1.69 NET_ITC_RADAR_PARAM
Radar parameter structure.
Structure Definition
struct{
BYTE byRadarType;
BYTE byLevelAngle;
WORD wRadarSensitivity;
WORD wRadarSpeedValidTime;
BYTE byRes1[2];
float fLineCorrectParam;
int iConstCorrectParam;
BYTE byRes2[8];
}NET_ITC_RADAR_PARAM, *LPNET_ITC_RADAR_PARAM;
Members
byRadarType
125
Device Network SDK (ANPR) Developer Guide
Radar type: 0-no radar, 1-Andoray radar, 2-Olvia, 3-TransMicrowave, 4-radar connecting I/O
expansion box (this parameter is only used in checkpoint virtual coil interface and is not used
for checkpoint RS-485 radar), 5-Andoray (without radar controller), 0xff-custom type.
byLevelAngle
Angle between the radar and the horizontal line, ranging from 0 degree to 90 degree, the
default value is 25 degree.
wRadarSensitivity
Radar sensitivity.
wRadarSpeedValidTime
Radar speed valid time, ranging from 0 to 2000, 0 means it is not supported.
byRes1
Reserved.
fLineCorrectParam
Linear correction parameter (for multiplying operation), ranging from 0.0 to 2.0.
iConstCorrectParam
Constant correction parameter (for adding and subtracting operation), ranging from -100 to
100.
byRes2
Reserved.
Remarks
In the checkpoint RS-485 radar triggering mode, the radar detection vehicle will be detected as
soon as the vehicle passes by, which means that the speed and the capture signal are received
almost simultaneously. Therefore, wRadarSpeedValidTime is invalid in this mode.
7.1.70 NET_ITC_REDLIGHT_PEDESTRIAN_PARAM
Structure about the parameters triggered by pedestrian running the red light.
Structure Definition
struct{
BYTE byEnable;
BYTE bySnapNumTimes;
BYTE byPedesDir;
BYTE byDelayTime;
BYTE byStackTargetEnble;
BYTE byCalibRecogCtrl;
BYTE byRes1[2];
NET_ITC_TRAFFIC_LIGHT_PARAM struTrafficLight;
NET_ITC_LINE struStopLine;
126
Device Network SDK (ANPR) Developer Guide
NET_ITC_POLYGON struCalibRecog[MAX_CALIB_RECOG_NUM/*2*/];
BYTE byRes[440];
}NET_ITC_REDLIGHT_PEDESTRIAN_PARAM, *LPNET_ITC_REDLIGHT_PEDESTRIAN_PARAM;
Members
byEnable
Whether to enable: 0-disable, 1-enable.
bySnapNumTimes
Number of captured pictures, ranging from 1 to 3, the default value is 3.
byPedesDir
Pedestrian direction: 0-forward, 1-backward, 2-bidirectional.
byDelayTime
Delay time, ranging from 1 to 5, unit: second.
byStackTargetEnble
Whether to overlay the target frame on the captured picture, which means that the pedestrian
running the red light on the first captured picture will be marked with a rectangle frame: 0-no,
1-yes.
byCalibRecogCtrl
Manage calibration areas: 0-delete the calibration area, 1-add a calibration area.
byRes1
Reserved, set to 0.
struTrafficLight
Traffic light parameters, see details in the structure NET_ITC_TRAFFIC_LIGHT_PARAM .
struStopLine
Stop line, see details in the structure NET_ITC_LINE .
struCalibRecog
Calibration area, see details in the structure NET_ITC_POLYGON .
byRes
Reserved, set to 0.
See Also
NET_ITC_TRIGGER_PARAM_UNION
7.1.71 NET_ITC_RS485_LIGHT_PARAM
Structure about RS-485 access traffic light parameters.
127
Device Network SDK (ANPR) Developer Guide
Structure Definition
struct{
NET_ITC_SINGLE_RS485_LIGHT_PARAM struRS485Light[MAX_LIGHT_NUM/*6*/];
BYTE byRes[8];
}NET_ITC_RS485_LIGHT_PARAM, *LPNET_ITC_RS485_LIGHT_PARAM;
Members
struRS485Light
Single RS-485 access traffic light parameters, see details in the structure
NET_ITC_SINGLE_RS485_LIGHT_PARAM .
byRes
Reserved, set to 0.
See Also
NET_ITC_LIGHT_ACCESSPARAM_UNION
7.1.72 NET_ITC_SINGLE_IO_LIGHT_PARAM
Structure about single IO access traffic light parameters.
Structure Definition
struct{
BYTE byLightType;
BYTE byRelatedIO;
BYTE byRedLightState;
BYTE byRes[17];
}NET_ITC_SINGLE_IO_LIGHT_PARAM, *LPNET_ITC_SINGLE_IO_LIGHT_PARAM;
Members
byLightType
Guiding direction type of the traffic light: 0-left turn signal, 1-straight signal, 2-right turn signal.
byRelatedIO
Linked IO port No., ranging from 1 to 6.
byRedLightState
Red light level status: 0-low-level red light, 1-high-level red light.
byRes
Reserved.
128
Device Network SDK (ANPR) Developer Guide
See Also
NET_ITC_IO_LIGHT_PARAM
7.1.73 NET_ITC_SINGLE_IOSPEED_PARAM
Structure about a single group of IO speed detection parameters.
Structure Definition
struct{
BYTE byEnable;
BYTE byTrigCoil1;
BYTE byCoil1IOStatus;
BYTE byTrigCoil2;
BYTE byCoil2IOStatus;
BYTE byRelatedDriveWay;
BYTE byTimeOut;
BYTE byRelatedIOOutEx;
DWORD dwDistance;
BYTE byCapSpeed;
BYTE bySpeedLimit;
BYTE bySpeedCapEn;
BYTE bySnapTimes1;
BYTE bySnapTimes2;
BYTE byBigCarSpeedLimit;
BYTE byBigCarSignSpeed;
BYTE byIntervalType;
WORD wInterval1[MAX_INTERVAL_NUM/*4*/];
WORD wInterval2[MAX_INTERVAL_NUM/*4*/];
BYTE byRelatedIOOut[MAX_IOOUT_NUM/*4*/];
BYTE byFlashMode;
BYTE byLaneType;
BYTE byCarSignSpeed;
BYTE byUseageType;
NET_ITC_PLATE_RECOG_REGION_PARAM struPlateRecog[MAX_LANEAREA_NUM/*2*/];
BYTE byRelaLaneDirectionType;
BYTE byLowSpeedLimit;
BYTE byBigCarLowSpeedLimit;
BYTE byLowSpeedCapEn;
BYTE byEmergencyCapEn;
BYTE byRes[27];
}NET_ITC_SINGLE_IOSPEED_PARAM, *LPNET_ITC_SINGLE_IOSPEED_PARAM;
Members
byEnable
Whether to enable: 0-no, 1-yes.
byTrigCoil1
129
Device Network SDK (ANPR) Developer Guide
130
Device Network SDK (ANPR) Developer Guide
byIntervalType
Interval type: 0-time (default), 1-distance.
wInterval1
Coil 1 burst interval (unit: millisecond) or burst distance (unit: decimeter). The burst interval
type is determined by byIntervalType.
wInterval2
Coil 2 burst interval (unit: millisecond) or burst distance (unit: decimeter). The burst interval
type is determined by byIntervalType.
byRelatedIOOut
Linked IO output port. Multiple ports can be linked simultaneously. The array 0 refers to IO
output port 1, the array 1 refers to IO output port 2, and so on. 0 means that the output port is
not linked, and 1 means that the output port is linked.
byFlashMode
Flashing mode of the flash light: 0-simultaneous, 1-sequential.
byLaneType
Lane type: 0-unconfigured, 1-highway, 2-city express way, 0xff-other way.
byCarSignSpeed
Marked speed limit for small-sized vehicle, unit: km/h.
byUseageType
Lane usage type, see details in the structure ITC_LANE_USEAGE_TYPE .
struPlateRecog
License plate recognition parameters, see details in the structure
NET_ITC_PLATE_RECOG_REGION_PARAM . One license plate recognition area is available, and
the other one is reserved.
byRelaLaneDirectionType
Linked lane direction type, see details in the structure ITC_RELA_LANE_DIRECTION_TYPE .
byLowSpeedLimit
Minimum speed limit for small-sized vehicle, unit: km/s.
byBigCarLowSpeedLimit
Minimum speed limit for large-sized vehicle, unit: km/s.
byLowSpeedCapEn
Whether to enable low speed capture: 0-no, 1-yes.
byEmergencyCapEn
Whether to enable occupying emergency lane capture: 0-no, 1-yes.
byRes
131
Device Network SDK (ANPR) Developer Guide
Reserved.
See Also
NET_ITC_POST_IOSPEED_PARAM
7.1.74 NET_ITC_SINGLE_IOTL_PARAM
Structure about a single group of IO traffic light parameters for the intersection violation system.
Structure Definition
struct{
BYTE byEnable;
BYTE byLightIO;
BYTE byTrafficLight;
BYTE byTrigIO;
BYTE byTrigIOStatus;
BYTE byRelatedDriveWay;
BYTE byRecordEnable;
BYTE byRecordType;
BYTE byPreRecordTime;
BYTE byRecordDelayTime;
BYTE byRecordTimeOut;
BYTE byRedSnapTimes;
BYTE byGreenSnapTimes;
BYTE byRelatedIOOutEx;
BYTE byRes1;
BYTE byIntervalType;
WORD wRedInterval[MAX_INTERVAL_NUM/*4*/];
WORD wGreenInterval[MAX_INTERVAL_NUM/*4*/];
BYTE byRelatedIOOut[MAX_IOOUT_NUM/*4*/];
BYTE byFlashMode;
BYTE byRes2[3];
NET_ITC_PLATE_RECOG_REGION_PARAM struPlateRecog[MAX_LANEAREA_NUM/*2*/];
BYTE byRes[32];
}NET_ITC_SINGLE_IOTL_PARAM, *LPNET_ITC_SINGLE_IOTL_PARAM;
Members
byEnable
Whether to enable: 0-no, 1-yes.
byLightIO
Traffic light IO: 0-IO1, 1-IO2, 2-IO3, 3-IO4, 4-IO5, 5-IO6.
byTrafficLight
Valid status of the traffic light: 0-high-level red light and low-level green light, 1-high-level green
light and low-level red light.
132
Device Network SDK (ANPR) Developer Guide
byTrigIO
Triggered IO port No.: 0-IO1, 1-IO2, 2-IO3, 3-IO4, 4-IO5, 5-IO6.
byTrigIOStatus
Triggered IO port status: 0-falling edge (default), 1-rising edge, 2-rising edge and falling edge, 3-
high level, 4-low level.
byRelatedDriveWay
Linked lane No.
byRecordEnable
Whether to record by cycle for running red light event: 0-no, 1-yes.
byRecordType
Recording type for running red light event: 0-pre-record, 1-post-record.
byPreRecordTime
Pre-record time for running red light event, the default value is 0, unit: second.
byRecordDelayTime
Post-record time for running red light event, the default value is 0, unit: second.
byRecordTimeOut
Cycle recording timeout for running red light event, unit: second.
byRedSnapTimes
Red light capture times: 0-not capture, other value-number of pictures per burst capture (the
maximum value is 5).
byGreenSnapTimes
Green light capture times: 0-not capture, other value-number of pictures per burst capture (the
maximum value is 5).
byRelatedIOOutEx
Linked IO output port. The output port No. is represented by bit, e.g., bit 0 refers to IO output
port 1, bit 1 refers to IO output port 2, and so on. For each bit, 0 means that the output port is
not linked, and 1 means that the output port is linked. Up to 8 IO output ports can be linked.
This member is compatible with byRelatedIOOut.
byRes1
Reserved.
byIntervalType
Interval type: 0-time (default), 1-distance.
wRedInterval
Burst time (unit: millisecond) or burst distance (unit: decimeter) of the red light. The burst
interval type is determined by byIntervalType.
wGreenInterval
133
Device Network SDK (ANPR) Developer Guide
Burst time (unit: millisecond) or burst distance (unit: decimeter) of the green light. The burst
interval type is determined by byIntervalType.
byRelatedIOOut
Linked IO output port. Multiple ports can be linked simultaneously.
byFlashMode
Flashing mode of the flash light: 0-simultaneous, 1-sequential.
byRes2
Reserved.
struPlateRecog
License plate recognition area parameters, see details in the structure
NET_ITC_PLATE_RECOG_REGION_PARAM .
byRes
Reserved.
See Also
NET_ITC_EPOLICE_IOTL_PARAM
7.1.75 NET_ITC_SINGLE_RS485_LIGHT_PARAM
Structure about single RS-485 access traffic light parameters.
Structure Definition
struct{
BYTE byLightType;
BYTE byRelatedLightChan;
BYTE byInputLight;
BYTE byRelatedYLightChan;
BYTE byRes[16];
}NET_ITC_SINGLE_RS485_LIGHT_PARAM, *LPNET_ITC_SINGLE_RS485_LIGHT_PARAM;
Members
byLightType
Guiding direction type of the traffic light: 0-left turn signal, 1-straight signal, 2-right turn signal.
byRelatedLightChan
No. of the traffic light detector channel linked to the red light, ranging from 0 to 16, 0 indicates
no red light.
byInputLight
Accessed traffic light type: 0-access red light, 1-access green light. It is not supported by ITS
cameras.
134
Device Network SDK (ANPR) Developer Guide
byRelatedYLightChan
No. of the traffic light detector channel linked to the yellow light, ranging from 0 to 16, 0
indicates no yellow light.
byRes
Reserved, set to 0.
Remarks
For example, if the traffic light types in the intersection includes left turn+straight and right turn,
you need to configure three arrays. The first array is for left turn signal and linked to detector
channel 1, the second array is for straight signal and linked to detector channel 1, and the third
array is for right turn signal and linked to detector channel 2.
See Also
NET_ITC_RS485_LIGHT_PARAM
7.1.76 NET_ITC_SINGLE_TRIGGERCFG
A single triggering parameter structure
Structure Definition
struct{
BYTE byEnable;
BYTE byRes1[3];
DWORD dwTriggerType;
NET_ITC_TRIGGER_PARAM_UNION uTriggerParam;
BYTE byRes[64];
}NET_ITC_SINGLE_TRIGGERCFG,*LPNET_ITC_SINGLE_TRIGGERCFG;
Member
byEnable
Whether to enable: 0-disable, 1-enable
byRes1
Reserved, set to 0
dwTriggerType
Trigger mode, see details in ITC_TRIGGERMODE_TYPE .
uTriggerParam
Trigger parameters, see details in the structure NET_ITC_TRIGGER_PARAM_UNION .
See Also
NET_ITC_TRIGGERCFG
135
Device Network SDK (ANPR) Developer Guide
7.1.77 NET_ITC_SINGLE_VIDEO_DETECT_LIGHT_PARAM
Structure about the traffic light parameters detected in a single video.
Structure Definition
struct{
BYTE byLightNum;
BYTE byStraightLight;
BYTE byLeftLight;
BYTE byRightLight;
BYTE byRedLight;
BYTE byGreenLight;
BYTE byYellowLight;
BYTE byYellowLightTime;
NET_POS_PARAM struLightRect;
BYTE byRes[24];
}NET_ITC_SINGLE_VIDEO_DETECT_LIGHT_PARAM, *LPNET_ITC_SINGLE_VIDEO_DETECT_LIGHT_PARAM;
Members
byLightNum
Number of traffic lights.
byStraightLight
Whether the straight signal is on: 0-no, 1-yes.
byLeftLight
Whether the left turn signal is on: 0-no, 1-yes.
byRightLight
Whether the right turn signal is on: 0-no, 1-yes.
byRedLight
Whether the red light is on: 0-no, 1-yes.
byGreenLight
Whether the green light is on: 0-no, 1-yes.
byYellowLight
Whether the yellow light is on: 0-no, 1-yes.
byYellowLightTime
Yellow light duration used to correct recognition deviation of red light and green light.
struLightRect
Traffic light area, see details in the structure NET_POS_PARAM .
byRes
136
Device Network SDK (ANPR) Developer Guide
Reserved, set to 0.
See Also
NET_ITC_VIDEO_DETECT_LIGHT_PARAM
7.1.78 NET_ITC_SINGLEIO_PARAM
Structure about single IO parameters.
Structure Definition
struct{
BYTE byDefaultStatus;
BYTE byRelatedDriveWay;
BYTE bySnapTimes;
BYTE byRelatedIOOutEx;
NET_ITC_INTERVAL_PARAM struInterval;
BYTE byRelatedIOOut[MAX_IOOUT_NUM/*4*/];
BYTE byFlashMode;
BYTE byEnable;
BYTE byUseageType;
BYTE byEmergencyCapEn;
NET_ITC_PLATE_RECOG_REGION_PARAM struPlateRecog[MAX_LANEAREA_NUM/*2*/];
BYTE byRes[32];
}NET_ITC_SINGLEIO_PARAM, *LPNET_ITC_SINGLEIO_PARAM;
Members
byDefaultStatus
Default IO triggering status: 0-low level, 1-high level.
byRelatedDriveWay
Linked lane No.
bySnapTimes
Capture times (the default value is 1): 0-not capture, other value-number of pictures per burst
capture (the maximum value is 5).
byRelatedIOOutEx
Linked IO output port. The output port No. is represented by bit, e.g., bit 0 refers to IO output
port 1, bit 1 refers to IO output port 2, and so on. For each bit, 0 means that the output port is
not linked, and 1 means that the output port is linked. Up to 8 IO output ports can be linked.
This member is compatible with byRelatedIOOut.
struInterval
Capture interval parameters, see details in the structure NET_ITC_INTERVAL_PARAM .
byRelatedIOOut
137
Device Network SDK (ANPR) Developer Guide
See Also
NET_ITC_POST_SINGLEIO_PARAM
7.1.79 NET_ITC_TRAFFIC_LIGHT_PARAM
Traffic light parameter structure.
Structure Definition
struct{
BYTE bySource;
BYTE byRes1[3];
NET_ITC_LIGHT_ACCESSPARAM_UNION struLightAccess;
BYTE byRes[32];
}NET_ITC_TRAFFIC_LIGHT_PARAM, *LPNET_ITC_TRAFFIC_LIGHT_PARAM;
Members
bySource
Traffic light accessing source: 0-IO access, 1-RS-485 access, 2-video detection.
byRes1
Reserved, set to 0.
struLightAccess
Traffic light accessing parameters, see details in the structure
NET_ITC_LIGHT_ACCESSPARAM_UNION .
138
Device Network SDK (ANPR) Developer Guide
byRes
Reserved, set to 0.
7.1.80 NET_ITC_TRIGGER_PARAM_UNION
Trigger parameter union
Structure Definition
union{
DWORD uLen[1070];
NET_ITC_POST_IOSPEED_PARAM struIOSpeed;
NET_ITC_POST_SINGLEIO_PARAM struSingleIO;
NET_ITC_POST_RS485_PARAM struPostRs485;
NET_ITC_POST_RS485_RADAR_PARAM struPostRadar;
NET_ITC_POST_VTCOIL_PARAM struVtCoil;
NET_ITC_POST_HVT_PARAM_V50 struHvtV50;
NET_ITC_POST_MPR_PARAM struPostMpr;
NET_ITC_POST_PRS_PARAM struPostPrs;
NET_ITC_EPOLICE_IOTL_PARAM struIOTL;
NET_ITC_EPOLICE_RS485_PARAM struEpoliceRs485;
NET_ITC_EPOLICE_RS485_PARAM struPERs485;
NET_DVR_VIA_VTCOIL_PARAM struViaVtCoil;
NET_ITC_POST_IMT_PARAM struPostImt;
NET_IPC_POST_HVT_PARAM struIpcHvt;
NET_ITC_POST_MOBILE_PARAM struPostMobile;
NET_ITC_REDLIGHT_PEDESTRIAN_PARAM struRedLightPed;
NET_ITC_NOCOMITY_PEDESTRIAN_PARAM struNoComityPed;
}NET_ITC_TRIGGER_PARAM_UNION,*LPNET_ITC_TRIGGER_PARAM_UNION;
Members
uLen
Union size, total 4280 bytes (1070*4).
struIOSpeed
(Checkpoint) I/O speed detection parameters, see details in the structure
NET_ITC_POST_IOSPEED_PARAM .
struSingleIO
(Checkpoint) Single I/O parameters, see details in the structure
NET_ITC_POST_SINGLEIO_PARAM .
struPostRs485
(Checkpoint) RS-485 vehicle detector parameters, see details in the structure
NET_ITC_POST_RS485_PARAM .
struPostRadar
139
Device Network SDK (ANPR) Developer Guide
140
Device Network SDK (ANPR) Developer Guide
See Also
NET_ITC_SINGLE_TRIGGERCFG
7.1.81 NET_ITC_TRIGGERCFG
Trigger parameter structure.
Structure Definition
struct{
DWORD dwSize;
NET_ITC_SINGLE_TRIGGERCFG struTriggerParam;
BYTE byRes[32];
}NET_ITC_TRIGGERCFG,*LPNET_ITC_TRIGGERCFG;
Members
dwSize
Structure size
struTriggerParam
Single trigger parameter, see details in the structure NET_ITC_SINGLE_TRIGGERCFG .
byRes
Reserved, set to 0.
7.1.82 NET_ITC_VIDEO_DETECT_LIGHT_PARAM
Structure about the traffic light parameters detected in the video.
Structure Definition
struct{
NET_ITC_SINGLE_VIDEO_DETECT_LIGHT_PARAM struTrafficLight[MAX_VIDEO_DETECT_LIGHT_NUM/*12*/];
BYTE byRes[8];
}NET_ITC_VIDEO_DETECT_LIGHT_PARAM, *LPNET_ITC_VIDEO_DETECT_LIGHT_PARAM;
Members
struTrafficLight
Traffic light parameters detected in a single video, see details in the structure
NET_ITC_SINGLE_VIDEO_DETECT_LIGHT_PARAM .
141
Device Network SDK (ANPR) Developer Guide
byRes
Reserved, set to 0.
See Also
NET_ITC_LIGHT_ACCESSPARAM_UNION
7.1.83 NET_ITC_VIOLATION_DETECT_LINE
Structure about violation detection line parameters.
Structure Definition
struct{
NET_ITC_LINE struLaneLine;
NET_ITC_LINE struStopLine;
NET_ITC_LINE struRedLightLine;
NET_ITC_LINE struCancelLine;
NET_ITC_LINE struWaitLine;
NET_ITC_LINE struRes[8];
}NET_ITC_VIOLATION_DETECT_LINE, *LPNET_ITC_VIOLATION_DETECT_LINE;
Members
struLaneLine
Lane line parameters, see details in the structure NET_ITC_LINE .
struStopLine
Stop line parameters, see details in the structure NET_ITC_LINE .
struRedLightLine
Triggering line parameters of red light running, see details in the structure NET_ITC_LINE .
struCancelLine
Canceling line parameters of triggering location of going straight, see details in the structure
NET_ITC_LINE .
struWaitLine
Stop line parameters of waiting area, see details in the structure NET_ITC_LINE .
struRes
Reserved, set to 0.
142
Device Network SDK (ANPR) Developer Guide
Remarks
● If the vehicle runs over the triggering line of red light running when the red light is on, the
vehicle will be judged to be red light running violation. Generally, the triggering line of red light
running is below the triggering line of going straight.
● If the vehicle runs over the canceling line of triggering location of going straight, the vehicle will
be judged to go straight instead of turning left or right. It is used to judge violation of not driving
according to the lane guidance.
See Also
NET_ITC_LANE_VIDEO_EPOLICE_PARAM
7.1.84 NET_ITC_VIOLATION_DETECT_PARAM
Violation detection parameter structure.
Structure Definition
struct{
DWORD dwVioDetectType;
BYTE byDriveLineSnapTimes;
BYTE byReverseSnapTimes;
WORD wStayTime;
BYTE byNonDriveSnapTimes;
BYTE byChangeLaneTimes;
BYTE bybanTimes;
BYTE byDriveLineSnapSen;
WORD wSnapPosFixPixel;
BYTE bySpeedTimes;
BYTE byTurnAroundEnable;
BYTE byThirdPlateRecogTime;
BYTE byPostSnapTimes;
BYTE byRes1[18];
WORD wStopLineDis;
BYTE byRes[14];
}NET_ITC_VIOLATION_DETECT_PARAM, *LPNET_ITC_VIOLATION_DETECT_PARAM;
Members
dwVioDetectType
Violation detection type represented by bit. For each bit, 0 refers to disabling, 1 refers to
enabling, see details in the structure ITC_VIOLATION_DETECT_TYPE .
byDriveLineSnapTimes
Number of captured pictures of driving on the lane line, ranging from 2 to 3.
byReverseSnapTimes
143
Device Network SDK (ANPR) Developer Guide
See Also
NET_ITC_LANE_VIDEO_EPOLICE_PARAM
144
Device Network SDK (ANPR) Developer Guide
7.1.85 NET_ITS_ILLEGAL_INFO
Traffic violation code structure.
Structure Definition
struct{
BYTE byIllegalInfo[MAX_ILLEGAL_LEN/*64*/];
BYTE byRes[256];
}NET_ITS_ILLEGAL_INFO,*LPNET_ITS_ILLEGAL_INFO;
Members
byIllegalInfo
Traffic violation code (in character string format)
byRes
Reserved, set to 0.
See Also
NET_ITS_PLATE_RESULT
7.1.86 NET_ITS_OVERLAP_CFG_V50
Extended text overlay parameter structure (V50)
Structure Definition
struct{
DWORD dwSize;
BYTE byEnable;
BYTE byRes1[3];
NET_ITS_OVERLAP_ITEM_PARAM_V50 struOverLapItemV50;
NET_ITS_OVERLAP_INFO_PARAM struOverLapInfo;
BYTE byRes[120];
}NET_ITS_OVERLAP_CFG_V50,*LPNET_ITS_OVERLAP_CFG_V50;
Members
dwSize
Structure size.
byEnable
Whether to enable: 0-no, 1-yes
byRes1
Reserved.
145
Device Network SDK (ANPR) Developer Guide
struOverLapItemV50
Character string parameter, refer to the structure NET_ITS_OVERLAP_ITEM_PARAM_V50 for
details.
struOverLapInfo
Character string details, refer to the structure NET_ITS_OVERLAP_INFO_PARAM for details.
byRes
Reserved.
7.1.87 NET_ITS_OVERLAP_INFO_PARAM
Structure about the character string to be displayed.
Structure Definition
struct{
BYTE bySite[128];
BYTE byRoadNum[32];
BYTE byInstrumentNum[32];
BYTE byDirection[32];
BYTE byDirectionDesc[32];
BYTE byLaneDes[32];
BYTE byRes1[32];
BYTE byMonitoringSite1[44];
BYTE byMonitoringSite2[32];
BYTE byRes[64];
}NET_ITS_OVERLAP_INFO_PARAM,*LPNET_ITS_OVERLAP_INFO_PARAM;
Members
bySite
Location description.
byRoadNum
Intersection No.
byInstrumentNum
Device No.
byDirection
Direction No.
byDirectionDesc
Direction description.
byLaneDes
Lane description
146
Device Network SDK (ANPR) Developer Guide
byRes1
Reserved, set to 0.
byMonitoringSite1
Information of camera No.1
byMonitoringSite2
Information of camera No.2
byRes
Reserved, set to 0.
See Also
NET_ITS_OVERLAP_CFG_V50
7.1.88 NET_ITS_OVERLAP_ITEM_PARAM_V50
Structure about configuration parameters for overlaying characters
Structure Definition
struct{
NET_ITS_OVERLAP_SINGLE_ITEM_PARAM_V50 struSingleItem[MAX_OVERLAP_ITEM_NUM/*50*/];
DWORD dwLinePercent;
DWORD dwItemsStlye;
WORD wStartPosTop;
WORD wStartPosLeft;
WORD wCharStyle;
WORD wCharSize;
WORD wCharInterval;
BYTE byRes1[2];
DWORD dwForeClorRGB;
DWORD dwBackClorRGB;
BYTE byColorAdapt;
BYTE byParamFillZeroEnble;
BYTE byPlateLeftCornerEnable;
BYTE byRes2;
WORD wStartSPicPosTop;
WORD wStartSPicPosLeft;
BYTE byOsdLocate;
BYTE byRes[63];
}NET_ITS_OVERLAP_ITEM_PARAM_V50, *LPNET_ITS_OVERLAP_ITEM_PARAM_V50;
Members
struSingleItem
Single character parameter.
147
Device Network SDK (ANPR) Developer Guide
dwLinePercent
Percentage of overlayed lines, ranges from 0 to 100, the default value is 100.
dwItemsStlye
Overlaying type: 0-horizontal (default), 1-vertical.
wStartPosTop
The coordinate of top starting point, it is only valid for overlaying within the picture, ranges
from 0 to 2,448, the default value is 0.
wStartPosLeft
The coordinate of left starting point, it is only valid for overlaying within the picture, ranges from
0 to 2,448, the default value is 0.
wCharStyle
Font type: 0-SimSun, 1-STXinwei (default).
wCharSize
Character size: 0-16*16, 1-32*32, 2-48*48, 3-64*64 (default), 4-128*128.
wCharInterval
Space distance between two characters, ranges from 0 to 16, available unit: pixel (default).
byRes1
Reserved, set to 0.
dwForeClorRGB
RGB value of foreground color:
See Also
7.1.89 NET_ITS_OVERLAP_SINGLE_ITEM_PARAM_V50
Structure about overlaying single character information.
Structure Definition
struct{
BYTE byRes1[2];
BYTE byItemType;
BYTE byChangeLineNum;
BYTE bySpaceNum;
BYTE byRes2[2];
BYTE byEnablePos;
WORD wStartPosTop;
WORD wStartPosLeft;
BYTE byItemTypeCustom[32];
148
Device Network SDK (ANPR) Developer Guide
BYTE byRes[8];
}NET_ITS_OVERLAP_SINGLE_ITEM_PARAM_V50, *LPNET_ITS_OVERLAP_SINGLE_ITEM_PARAM_V50;
Members
byRes1
Reserved.
byItemType
Type, see details in the structure ITS_OVERLAP_ITEM_TYPE .
byChangeLineNum
Number of line feeds after overlaying items, ranges from 0 to 10, the default value is 0.
bySpaceNum
Number of spaces after overlaying items, ranges from 0 to 255, the default value is 0.
byRes2
Reserved.
byEnablePos
Whether to enable displaying coordinates: 0-no, 1-yes.
wStartPosTop
The coordinate of top starting point, it is only valid for overlaying within the picture, ranges
from 0 to 2,448, the default value is 0.
wStartPosLeft
The coordinate of left starting point, it is only valid for overlaying within the picture, ranges from
0 to 2,448, the default value is 0.
byItemTypeCustom
Custom type, corresponds to the parameter byItemType, customize type name for byItemType
parameter. If byItemTypeCustom is "NULL", the type name of byItemType parameter will be
used by default.
byRes
Reserved.
See Also
NET_ITS_OVERLAP_ITEM_PARAM_V50
7.1.90 NET_ITS_OVERLAPCFG_COND
Structure about the OSD configuration conditions.
149
Device Network SDK (ANPR) Developer Guide
Structure Definition
struct{
DWORD dwSize;
DWORD dwChannel;
DWORD dwConfigMode;
BYTE byPicModeType;
BYTE byRes[15];
}NET_ITS_OVERLAPCFG_COND,*LPNET_ITS_OVERLAPCFG_COND;
Members
dwSize
Structure size
dwChannel
Channel No.
dwConfigMode
Configuration mode: 0-via client software, 1-access device via web browser to configure
byPicModeType
Picture mode: 0-thumbnail, 1-large picture (composite picture)
byRes
Reserved, set to 0
7.1.91 NET_ITS_PLATE_RESULT
ANPR result structure
Structure Definition
struct{
DWORD dwSize;
DWORD dwMatchNo;
BYTE byGroupNum;
BYTE byPicNo;
BYTE bySecondCam;
BYTE byFeaturePicNo;
BYTE byDriveChan;
BYTE byVehicleType;
BYTE byDetSceneID;
BYTE byVehicleAttribute;
WORD wIllegalType;
BYTE byIllegalSubType[8];
BYTE byPostPicNo;
BYTE byChanIndex;
WORD wSpeedLimit;
150
Device Network SDK (ANPR) Developer Guide
BYTE byChanIndexEx;
BYTE byRes2;
NET_DVR_PLATE_INFO struPlateInfo;
NET_DVR_VEHICLE_INFO struVehicleInfo;
BYTE byMonitoringSiteID[48];
BYTE byDeviceID[48];
BYTE byDir;
BYTE byDetectType;
BYTE byRelaLaneDirectionType;
BYTE byCarDirectionType;
DWORD dwCustomIllegalType;
BYTE *pIllegalInfoBuf;
BYTE byIllegalFromatType;
BYTE byPendant;
BYTE byDataAnalysis;
BYTE byYellowLabelCar;
BYTE byDangerousVehicles;
BYTE byPilotSafebelt;
BYTE byCopilotSafebelt;
BYTE byPilotSunVisor;
BYTE byCopilotSunVisor;
BYTE byPilotCall;
BYTE byBarrierGateCtrlType;
BYTE byAlarmDataType;
NET_DVR_TIME_V50 struSnapFirstPicTime;
DWORD dwIllegalTime;
DWORD dwPicNum;
NET_ITS_PICTURE_INFO struPicInfo[6];
}NET_ITS_PLATE_RESULT, *LPNET_ITS_PLATE_RESULT;
Members
dwSize
Structure Size
dwMatchNo
Match ID, which consists of vehicle No., data type, and lane No.
byGroupNum
Number of picture groups (total number of one vehicle picture groups captured by multiple
cameras), the default value is 1.
byPicNo
No. of continuously captured picture (if byPicNo is byGroupNum, it indicates that the last
picture is received).
bySecondCam
Whether the picture is captured by the second camera.
byFeaturePicNo
151
Device Network SDK (ANPR) Developer Guide
Intersection violation system for red light running, the No. of picture to be set as close-up
picture, 0xff-not set.
byDriveChan
Triggered lane No.
byVehicleType
Vehicle type: 0-unknown, 1-bus, 2-truck, 3-car, 4-mini bus, 5-van, 6-pedestrian, 7-two-wheel
vehicle, 8-three-wheel vehicle, 9-SUV/MPV, 10-medium bus, 11-motor vehicle, 12-non-motor
vehicle, 13-mini car, 14-micro car, 15-pickup truck. Generally, the vehicle type is determined by
this member. If this member is set to 0, the vehicle type is determined by the member
byVehicleType in the structure NET_DVR_VEHICLE_INFO .
byDetSceneID
Detection scene No., 0-invalid, other values: [1,4], for network camera, its value is 0 (not
support)
byVehicleAttribute
Vehicle properties, 0-no additional properties, other values: bit1-yellow label vehicle, bit2-
danguous goods vehicle, bit value: 0-no, 1-yes.
wIllegalType
Traffic violation type. When the value of this parameter is 0, see the traffic violation type in
dwCustomIllegalType.
byIllegalSubType
Sub type of traffic violation.
byPostPicNo
The No. of picture to be set as the checkpoint picture, 0xff-not set.
byChanIndex
Channel No.
wSpeedLimit
Upper limit of speed (it is valid only when overspeed).
byChanIndexEx
byChanIndexEx*256+byChanIndex is the actual channel No.
byRes2
Reserved
struPlateInfo
License plate information, see details in the structure NET_DVR_PLATE_INFO .
struVehicleInfo
Vehicle information , see details in the structure NET_DVR_VEHICLE_INFO .
byMonitoringSiteID
152
Device Network SDK (ANPR) Developer Guide
Monitoring point ID
byDeviceID
Device ID
byDir
Detection direction: 1-backward, 2-forward, 3-bidirection, 4-from east to west, 5from south to
north, 6-from west to east, 7from north to south, 8-other
byDetectType
Detection type: 0-vehicle detection, 1-triggered by inductive loop, 2- triggered by video
detection, 3-multi-frame recognition, 4- triggered by radar, 5-mixed-traffic detection.
byRelaLaneDirectionType
Linked lane direction, see details in ITC_RELA_LANE_DIRECTION_TYPE , which corresponds to
the linked lane No.
byCarDirectionType
Vehicle driving direction: 0-from top to bottom in image, 1- from bottom to top in image.
dwCustomIllegalType
Traffic violation type (custom), this parameter is valid only when wIllegalType is 0.
pIllegalInfoBuf
Violation code, it is valid when byIllegalFromatType is 1. The code pointer points to the
structure NET_ITS_ILLEGAL_INFO .
byIllegalFromatType
Traffic violation information format: 0-digital format, 1-character format
byPendant
Objects hanging on window?: 0-unknown, 1-yes, 2-no
byDataAnalysis
Data analyzed?: 0-no, 1-yes
byYellowLabelCar
Yellow label vehicle? 0-unknown, 1-yes, 2-no
byDangerousVehicles
Dangerous goods vehicle? 0-unknown, 1-yes, 2-no
byPilotSafebelt
Driver wearing safety belt? 0-unknown, 1-yes, 2-no
byCopilotSafebelt
Co-driver wearing safety belt?: 0-unknown, 1-yes, 2-no
byPilotSunVisor
Sun shield of co-driver room opened?: 0-unknown, 1-yes, 2-no
153
Device Network SDK (ANPR) Developer Guide
byCopilotSunVisor
Sun shield of co-driver room opened?: 0-unknown, 1-yes, 2-no
byPilotCall
Driver making call? 0-unknown, 1-yes, 2-no
byBarrierGateCtrlType
Barrier control type: 0-open, 1-close.
byAlarmDataType
Alarm data type: 0-real-time data, 1-history data.
struSnapFirstPicTime
Time of first captured picture, unit: ms, see details in the structure NET_DVR_TIME_V50 .
dwIllegalTime
Violation duration (unit: ms)=time of last captured picture-time of first captured picture
dwPicNum
Number of pictures.
struPicInfo
Picture information, call back one by one, and up to 6 pictures are allowed, see details in the
structure NET_ITS_PICTURE_INFO .
Remarks
Generally, refer to the parameter byVehicleType of this structure for the vehicle type. If
byVehicleType is 0, refer to the parameter byVehicleType of structure NET_DVR_VEHICLE_INFO .
7.1.92 NET_ITS_PICTURE_INFO
Captured picture information structure.
Structure Definition
struct{
DWORD dwDataLen;
BYTE byType;
BYTE byDataType;
BYTE byCloseUpType;
BYTE byPicRecogMode;
DWORD dwRedLightTime;
BYTE byAbsTime[32];
NET_VCA_RECT struPlateRect;
NET_VCA_RECT struPlateRecgRect;
BYTE *pBuffer;
DWORD dwUTCTime;
BYTE byCompatibleAblity;
BYTE byTimeDiffFlag;
154
Device Network SDK (ANPR) Developer Guide
Members
dwDataLen
Size of media data.
byType
Data type: 0-license plate picture, 1-scene picture, 2-composite picture, 3-close-up picture, 4-
binary picture, 5-stream, 6-driver's face thumbnail, 7-co-driver's face thumbnail, 8-non-motor
vehicle, 9-pedestrian, 10-raw data, 11-target picture, 12-driver room picture, 13-co-driver room
picture, 14-face thumbnail
byDataType
Data uploading type: 0-directly upload, 1-upload URL of cloud storage server
byCloseUpType
Close-up picture type: 0-reserved, 1-non-motor vehicle, 2-pedestrian
byPicRecogMode
Recognition mode: 0-recognize in forward direction, 1-recognize in backward direction
dwRedLightTime
Red light duration, unit: s
byAbsTime
Absolute time: yyyymmddhhmmssxxx, e.g.20090810235959999, the last three bits are
milliseconds.
struPlateRect
When byType is "1", this parameter indicates the position of license plate on the scene picture,
when byType is "8" or "9", this parameter indicates the person coordinates. See details in the
structure NET_VCA_RECT .
struPlateRecgRect
ANPR region coordinates, when byType is "12" or "13", this parameter indicates the coordinates
of driver. See details in the structure NET_VCA_RECT .
pBuffer
Buffer for saving data.
dwUTCTime
UTC time
byCompatibleAblity
Compatible with capability filed, and it is represented by bit, value: 0-invalid, 1-valid. bit0-
whether the parameter dwUTCTime is valid.
155
Device Network SDK (ANPR) Developer Guide
byTimeDiffFlag
Whether the time difference parameter is valid: 0-invalid, 1-valid.
cTimeDifferenceH
Time difference between time and UTC time, unit: hour, the value is between -12 and +14 ("+"
indicates the east time zone), it is valid when byTimeDiffFlag is "1".
cTimeDifferenceM
Time difference between time and UTC time, unit: minute, the value is -30, +30, or +45 ("+"
indicates the east time zone), it is valid when byTimeDiffFlag is "1".
byRes2
Reserved
Remarks
● If only the scene picture is uploaded, you can capture the close-up view from scene picture
according to the parameter struPlateRecgRect, and you can also adjust the width and height as
required.
● Picture URL format: http://CVMIP:Port/pic?
did=DevID&bid=BlkID&pid=PictureID&ptime=PicTime. E.g., http://10.192.65.140:8009/pic?
did=35b9cbd0-8ffa-1031-87e6-0025903c6a50&bid=387&pid=2952790009&ptime=1378106185
CVMIP
IP address of CVM (Cloud Video Management) server.
Port
Port number (default: 8009) of HTTP service provided by CVM (Cloud Video Management)
server.
DevID
Device ID of CVS (Cloud Video Server).
BlkID
Device block ID of CVS (Cloud Video Server)
PictureID
Picture ID generated by CVS (Cloud Video Server)
PicTime
Picture timestamp.
7.1.93 NET_POS_PARAM
Region parameter structure.
156
Device Network SDK (ANPR) Developer Guide
Structure Definition
struct{
WORD wLeft;
WORD wTop;
WORD wRight;
WORD wBottom;
}NET_POS_PARAM, *LPNET_POS_PARAM;
Members
wLeft
X-coordinate of the upper-left corner of the boundary frame, value range: [1, 1000].
wTop
Y-coordinate of the upper-left corner of the boundary frame, value range: [1, 1000].
wRight
X-coordinate of the lower-right corner of the boundary frame, value range: [1, 1000].
wBottom
Y-coordinate of the lower-right corner of the boundary frame, value range: [1, 1000].
See Also
NET_ITC_SINGLE_VIDEO_DETECT_LIGHT_PARAM
7.1.94 NET_VCA_LINE
Structure about line parameters.
Structure Definition
struct{
NET_VCA_POINT struStart;
NET_VCA_POINT struEnd;
}NET_VCA_LINE,*LPNET_VCA_LINE;
Members
struStart
Start point, see details in the structure NET_VCA_POINT
struEnd
End point, see details in the structure NET_VCA_POINT .
7.1.95 NET_VCA_POINT
157
Device Network SDK (ANPR) Developer Guide
7.1.96 NET_VCA_RECT
7.1.97 VCA_PLATE_COLOR
Enumerate the license plate colors.
Enumeration Definition
enum{
VCA_BLUE_PLATE =0,
VCA_YELLOW_PLATE =1,
VCA_WHITE_PLATE =2,
VCA_BLACK_PLATE =3,
VCA_GREEN_PLATE =4,
VCA_BKAIR_PLATE =5,
VCA_RED_PLATE,
VCA_ORANGE_PLATE,
158
Device Network SDK (ANPR) Developer Guide
VCA_OTHER =0xff
}VCA_PLATE_COLOR
Member
VCA_BLUE_PLATE
Blue
VCA_YELLOW_PLATE
Yellow
VCA_WHITE_PLATE
White
VCA_BLACK_PLATE
Black
VCA_GREEN_PLATE
Green
VCA_BKAIR_PLATE
Black (for special use)
VCA_RED_PLATE
Red
VCA_ORANGE_PLATE
Orange
VCA_OTHER
Other
7.1.98 VCA_PLATE_TYPE
Enumerate the license plate types.
Enumeration Definition
enum{
VCA_STANDARD92_PLATE =0,
VCA_STANDARD02_PLATE =1,
VCA_WJPOLICE_PLATE =2,
VCA_JINGCHE_PLATE =3,
STANDARD92_BACK_PLATE =4,
VCA_SHIGUAN_PLATE =5,
VCA_NONGYONG_PLATE =6,
VCA_MOTO_PLATE =7,
NEW_ENERGY_PLATE =8,
VCA_CONSULATE_PLATE =9,
VCA_EMERGENCY_PLATE = 10
159
Device Network SDK (ANPR) Developer Guide
TRANSPORT_PLATE = 0x20,
COMMERCIAL_PLATE,
PRIVATE_PLATE,
LEARNING_PLATE,
CD_PLATE,
CC_PLATE,
SPECIAL_PLATE,
PROTOCOL_PLATE,
GOVERNMENT_PLATE,
EXPORT_PLATE,
TAXI_PLATE,
TESTING_PLATE,
TRANSFER_PLATE,
TRUCK_PLATE,
BUS_PLATE,
PUBLIC_PLATE,
PUB_TRANS_PLATE,
PRI_TRANS_PLATE,
UNKNOWN_PLATE = 0xff
}VCA_PLATE_TYPE
Member
VCA_STANDARD92_PLATE
License plate of civil and military vehicle.
VCA_STANDARD02_PLATE
License plate of civil vehicle
VCA_WJPOLICE_PLATE
License plate of armed police vehicle.
VCA_JINGCHE_PLATE
License plate of police vehicle.
STANDARD92_BACK_PLATE
Tail board of civil vehicle.
VCA_SHIGUAN_PLATE
License plate of embassy vehicle.
VCA_NONGYONG_PLATE
License plate of farm vehicle.
VCA_MOTO_PLATE
License plate of motor vehicle.
NEW_ENERGY_PLATE
License plate of new energy vehicle.
VCA_CONSULATE_PLATE
160
Device Network SDK (ANPR) Developer Guide
161
Device Network SDK (ANPR) Developer Guide
7.1.99 DATE_TIME
7.1.100 NET_DVR_DEVICEINFO_V30
Device parameter structure (V30).
162
Device Network SDK (ANPR) Developer Guide
search.
● bySupport&0x2: whether supports backup.
encoding parameters.
● bySupport&0x8: whether supports dual-NIC.
SADP.
● bySupport&0x20: whether supports RAID
card.
● bySupport&0x40: whether supports
RTSP.
bySupport1 BYTE Extended capabilities, if the result of bitwise
operation is 0, it refers that the capability is not
163
Device Network SDK (ANPR) Developer Guide
over RTSP.
● bySupport1&0x80: whether supports license
version 40.
● bySupport2&0x4: whether supports ANR.
device status.
● bySupport2&0x40: whether supports
encrypting stream.
wDevType WORD Device model
bySupport3 BYTE Extended capabilities, if the result of bitwise
operation is 0, it refers that the capability is not
supported, while, if the result is 1, it indicates
that the capability is supported.
● bySupport3&0x1: whether supports multi-
stream.
● bySupport3&0x4: whether supports
164
Device Network SDK (ANPR) Developer Guide
third-stream.
● byMultiStreamProto&0x2: whether supports
fourth-stream.
● byMultiStreamProto&0x40: whether
supports sub-stream.
byStartDChan BYTE Start No. of digital channel, 0-no digital channel
(e.g., DVR, network camera).
byStartDTalkChan BYTE Start No. of two-way audio channel, 0-no two-
way audio channel.
byHighDChanNum BYTE Number of digital channels, high 8-bit.
bySupport4 BYTE Extended capabilities, if the result of bitwise
operation is 0, it refers that the capability is not
supported, if the result is 1, it indicates that the
capability is supported.
● bySupport4&0x01: whether all stream types
165
Device Network SDK (ANPR) Developer Guide
Remarks
● The maximum number of digital channels equal to byIPChanNum+byHighDChanNum*256.
● For login via text protocol, the following parameters are not supported: byMainProto,
bySubProto, bySupport, bySupport1, bySupport2, bySupport3, bySupport4, bySupport5,
bySupport6, bySupport7, byMultiStreamProto, byStartDTalkChan, byVoiceInChanNum,
byStartVoiceInChanNo, byMirrorChanNum, and wStartMirrorChanNo.
See Also
NET_DVR_DEVICEINFO_V40
7.1.101 NET_DVR_DEVICEINFO_V40
166
Device Network SDK (ANPR) Developer Guide
167
Device Network SDK (ANPR) Developer Guide
168
Device Network SDK (ANPR) Developer Guide
Remarks
● Four character types are allowed in the password, including digits, lowercase letters, uppercase
letters and symbols. The maximum password length is 16 bits, and there are four password
strength levels, see details below:
○ Level 0 (Risky Password): The password length is less than 8 bits, or only contains one kind of
the character types. Or the password is the same with the user name, or is the mirror writing
of the user name.
○ Level 1 (Weak Password): The password length is more than or equal to 8 bits, and contains
two kinds of the character types. Meanwhile, the combination should be (digits + lowercase
letters) or (digits + uppercase letters).
○ Level 2 (Medium Password): The password length is more than or equal to 8 bits, and contains
two kinds of the character types. Meanwhile, the combination cannot be (digits + lowercase
letters) and (digits + uppercase letters).
○ Level 3 (Strong Password): The password length is more than or equal to 8 bits, and at least
7.1.102 NET_DVR_INIT_CFG_ABILITY
169
Device Network SDK (ANPR) Developer Guide
Remarks
By default, up to 2048 channels are supported. More channels require higher computer
performance and network bandwidth.
See Also
NET_DVR_SetSDKInitCfg
7.1.103 NET_DVR_LOCAL_SDK_PATH
Remarks
If the path of HCNetSDKCom folder and HCNetSDK libraries are same, but the path of executable
programs are different, you can call NET_DVR_SetSDKInitCfg to specify the path of HCNetSDKCom
folder to make sure the component libraries are loaded normally.
7.1.104 NET_DVR_USER_LOGIN_INFO
170
Device Network SDK (ANPR) Developer Guide
171
Device Network SDK (ANPR) Developer Guide
7.1.105 NET_SDK_CALLBACK_STATUS_NORMAL
7.1.106 NET_VCA_RECT
172
Device Network SDK (ANPR) Developer Guide
7.1.107 NET_ALARM_CVR_SUBINFO_UNION
7.1.108 NET_ALARM_RECORD_EXCEPTION
173
Device Network SDK (ANPR) Developer Guide
7.1.109 NET_ALARM_RECORDFILE_LOSS
7.1.110 NET_ALARM_RESOURCE_USAGE
7.1.111 NET_ALARM_STREAM_EXCEPTION
174
Device Network SDK (ANPR) Developer Guide
7.1.112 NET_DVR_ALARMER
175
Device Network SDK (ANPR) Developer Guide
7.1.113 NET_DVR_ALARMINFO_DEV
Remarks
For pNO: if dwAlarmType is 0, 3, 6, or 7, it may be channel No.; if dwAlarmType is 5, it may be disk
No.
176
Device Network SDK (ANPR) Developer Guide
7.1.114 NET_DVR_ALARMINFO_DEV_V40
Remarks
For pNO: if dwAlarmType is 0, 3, 6, or 7, it may be channel No.; if dwAlarmType is 5, it may be disk
No.
7.1.115 NET_DVR_ALARMINFO_V30
177
Device Network SDK (ANPR) Developer Guide
Remarks
The time interval to upload the alarm of face picture library changed is 1 hour; for other alarm
type, the alarm information is uploaded in real-time, and the time interval is 1s. Currently, editing
the time interval is not supported.
7.1.116 NET_DVR_ALARMINFO_V40
178
Device Network SDK (ANPR) Developer Guide
Remarks
● The time interval to upload the alarm of face picture library changed is 1 hour; for other alarm
type, the alarm information is uploaded in real-time, and the time interval is 1s. Currently,
editing the time interval is not supported.
● The content of pAlarmData varies with the value of dwAlarmType in the structure
NET_DVR_ALRAM_FIXED_HEADER , see details in the table below:
179
Device Network SDK (ANPR) Developer Guide
7.1.117 NET_DVR_ALRAM_FIXED_HEADER
180
Device Network SDK (ANPR) Developer Guide
181
Device Network SDK (ANPR) Developer Guide
Table 7-6 Structure about Alarm Parameters of Education Sharing System (struRecordingHost)
Member Data Type Description
bySubAlarmType BYTE Alarm minor type: 1-one-touch post-record
byRes1 Array of BYTE Reserved, set to 0. The maximum size is 3 bytes.
struRecordEndTime NET_DVR_TIME_EX Recording end time.
Table 7-7 Structure about Alarm Parameters of Supply Voltage Exception (struVoltageInstable)
Member Data Type Description
fVoltageValue float Supply voltage, unit: V, corrects to one decimal
place.
byVoltageAlarmType BYTE Supply voltage exception type: 0-high supply
voltage, 1-low supply voltage
byRes1 Array of BYTE Reserved, set to 0. The maximum size is 3 bytes.
182
Device Network SDK (ANPR) Developer Guide
Remarks
dwAlarmType==0, 23 corresponds to the structure struIOAlarm; dwAlarmType==
2/3/6/9/10/11/13/15/16/28 corresponds to the structure struAlarmChannel; dwAlarmType==
1/4/5 corresponds to the structure struAlarmHardDisk; dwAlarmType== 17 corresponds to the
structure struRecordingHost; dwAlarmType== 31 corresponds to the structure struVoltageInstable;
for other value, the union is not available.
7.1.118 NET_DVR_ALARM_ISAPI_INFO
183
Device Network SDK (ANPR) Developer Guide
Remarks
When enabling the listening mode, you should call the network configuration API based on text
protocol to set the IP address for the listening service.
7.1.119 NET_DVR_ALARM_ISAPI_PICDATA
7.1.120 NET_DVR_ETHERNET_V30
184
Device Network SDK (ANPR) Developer Guide
7.1.121 NET_DVR_IPADDR_UNION
IP Address Union
7.1.122 NET_DVR_NETCFG_V50
185
Device Network SDK (ANPR) Developer Guide
186
Device Network SDK (ANPR) Developer Guide
Remarks
● For device only supports the private protocol with version 3.0 or lower, when the parameter
byUseDhcp="0xff", you should set the device IP address to null, and then the device will
automatically get the DHCP information.
● When the parameter byIPv6Mode is set to 0 or 2, setting IPv6 address in the parameter
struEtherNet is not required, it will be obtained automatically by the device; when byIPv6Mode
is set to 1, you should set IPv6 address. As there are multiple IPv6 addresses, the IPv6 address of
current logged-in device may be different with that in struEtherNet.
7.1.123 NET_DVR_PPPOECFG
7.1.124 NET_DVR_SETUPALARM_PARAM_V50
187
Device Network SDK (ANPR) Developer Guide
188
Device Network SDK (ANPR) Developer Guide
1-yes.
● bit1-whether to enable ANR for people
no, 1-yes.
● bit3-whether to enable ANR for face capture:
0-no, 1-yes.
● bit4-whether to enable ANR for face picture
189
Device Network SDK (ANPR) Developer Guide
data, 1-URL
● bit1-type of picture uploaded in message: 0-
binary, 1-URL
● bit2-type of picture uploaded for face picture
Remarks
● The parameters byLevel and byAlarmInfoType are available for traffic cameras. Up to 1 cameras
can be armed in the priority of level 0, up to 3 cameras can be armed in the priority of level 1,
and up to 5 cameras can be armed in the priority of level 3, the alarm/event information from
the camera in highest priority will be uploaded first.
● For arming via client software, only supports arming one channel, and supports uploading the
alarm/event when device is offline; for real-time arming, up to four channels can be armed at
same time, but uploading alarm/event when device is offline is not supported.
● The parameter wTaskNo is used to distinguish different arming connections. If the value of this
parameter in different arming connections is same, error will be returned.
7.1.125 NET_DVR_TIME
190
Device Network SDK (ANPR) Developer Guide
7.1.126 NET_DVR_TIME_EX
7.2 Enumeration
7.2.1 COUNTRY_INDEX
Enumerate country names.
Enumeration Definition
enum{
COUNTRY_NONSUPPORT = 0,
191
Device Network SDK (ANPR) Developer Guide
COUNTRY_CZE = 1,
COUNTRY_FRA = 2,
COUNTRY_DEU = 3,
COUNTRY_ESP = 4,
COUNTRY_ITA = 5,
COUNTRY_NLD = 6,
COUNTRY_POL = 7,
COUNTRY_SVK = 8,
COUNTRY_BLR = 9,
COUNTRY_MDA = 10,
COUNTRY_RUS = 11,
COUNTRY_UKR = 12,
COUNTRY_BEL = 13,
COUNTRY_BGR = 14,
COUNTRY_DNK = 15,
COUNTRY_FIN = 16,
COUNTRY_GBR = 17,
COUNTRY_GRC = 18,
COUNTRY_HRV = 19,
COUNTRY_HUN = 20,
COUNTRY_ISR = 21,
COUNTRY_LUX = 22,
COUNTRY_MKD = 23,
COUNTRY_NOR = 24,
COUNTRY_PRT = 25,
COUNTRY_ROU = 26,
COUNTRY_SRB = 27,
COUNTRY_AZE = 28,
COUNTRY_GEO = 29,
COUNTRY_KAZ = 30,
COUNTRY_LTU = 31,
COUNTRY_TKM = 32,
COUNTRY_UZB = 33,
COUNTRY_LVA = 34,
COUNTRY_EST = 35,
COUNTRY_ALB = 36,
COUNTRY_AUT = 37,
COUNTRY_BIH = 38,
COUNTRY_IRL = 39,
COUNTRY_ISL = 40,
COUNTRY_VAT = 41,
COUNTRY_MLT = 42,
COUNTRY_SWE = 43,
COUNTRY_CHE = 44,
COUNTRY_CYP = 45,
COUNTRY_TUR = 46,
COUNTRY_SVN = 47,
COUNTRY_MTG = 48,
COUNTRY_KOV = 49,
COUNTRY_ADR = 50,
COUNTRY_ARM = 51,
COUNTRY_MON = 52,
192
Device Network SDK (ANPR) Developer Guide
COUNTRY_LIE = 53,
COUNTRY_SMO = 54,
COUNTRY_RES1 = 55,
COUNTRY_RES2 = 56,
COUNTRY_RES3 = 57,
COUNTRY_RES4 = 58,
COUNTRY_CHI = 59,
COUNTRY_IBN = 60,
COUNTRY_SKR = 61,
COUNTRY_LEB = 62,
COUNTRY_NEP = 63,
COUNTRY_THA = 64,
COUNTRY_PAK = 65,
COUNTRY_EMI = 66,
COUNTRY_BHU = 67,
COUNTRY_OMA = 68,
COUNTRY_KOR = 69,
COUNTRY_PHI = 70,
COUNTRY_CAM = 71,
COUNTRY_QAT = 72,
COUNTRY_KYR = 73,
COUNTRY_MAL = 74,
COUNTRY_MLY = 75,
COUNTRY_MOG = 76,
COUNTRY_ARA = 77,
COUNTRY_BRU = 78,
COUNTRY_LAO = 79,
COUNTRY_JAP = 80,
COUNTRY_RES19 = 81,
COUNTRY_PAS = 82,
COUNTRY_TAJ = 83,
COUNTRY_KUW = 84,
COUNTRY_SYR = 85,
COUNTRY_IND = 86,
COUNTRY_ISA = 87,
COUNTRY_AFG = 88,
COUNTRY_LAN = 89,
COUNTRY_IRQ = 90,
COUNTRY_VIE = 91,
COUNTRY_IRA = 92,
COUNTRY_YEM = 93,
COUNTRY_JOR = 94,
COUNTRY_BUR = 95,
COUNTRY_SIK = 96,
COUNTRY_BAN = 97,
COUNTRY_SGA = 98,
COUNTRY_EAT = 99,
COUNTRY_RES5 = 100,
COUNTRY_RES6 = 101,
COUNTRY_RES7 = 102,
COUNTRY_RES8 = 103,
COUNTRY_EGT = 104,
193
Device Network SDK (ANPR) Developer Guide
COUNTRY_LIY = 105,
COUNTRY_SUA = 106,
COUNTRY_TUN = 107,
COUNTRY_ALG = 108,
COUNTRY_MCC = 109,
COUNTRY_ETH = 110,
COUNTRY_ERI = 111,
COUNTRY_SDE = 112,
COUNTRY_DJI = 113,
COUNTRY_KEN = 114,
COUNTRY_TAI = 115,
COUNTRY_UGA = 116,
COUNTRY_RWA = 117,
COUNTRY_BUD = 118,
COUNTRY_SEY = 119,
COUNTRY_CHA = 120,
COUNTRY_CEA = 121,
COUNTRY_CON = 122,
COUNTRY_EQG = 123,
COUNTRY_GAB = 124,
COUNTRY_TCO = 125,
COUNTRY_DRC = 126,
COUNTRY_STP = 127,
COUNTRY_MAN = 128,
COUNTRY_WSA = 129,
COUNTRY_SEL = 130,
COUNTRY_TGA = 131,
COUNTRY_MAI = 132,
COUNTRY_BUF = 133,
COUNTRY_GUI = 134,
COUNTRY_GUB = 135,
COUNTRY_CAV = 136,
COUNTRY_SLE = 137,
COUNTRY_LIR = 138,
COUNTRY_IVC = 139,
COUNTRY_GHA = 140,
COUNTRY_TGO = 141,
COUNTRY_BEN = 142,
COUNTRY_NIG = 143,
COUNTRY_ZAB = 144,
COUNTRY_ANG = 145,
COUNTRY_ZBE = 146,
COUNTRY_MAW = 147,
COUNTRY_MOQ = 148,
COUNTRY_BOT = 149,
COUNTRY_NAM = 150,
COUNTRY_SAF = 151,
COUNTRY_SWD = 152,
COUNTRY_LES = 153,
COUNTRY_MAG = 154,
COUNTRY_UOC = 155,
COUNTRY_MAT = 156,
194
Device Network SDK (ANPR) Developer Guide
COUNTRY_NGE = 157,
COUNTRY_SSD = 158,
COUNTRY_SAH = 159,
COUNTRY_MYT = 160,
COUNTRY_REN = 161,
COUNTRY_CAI = 162,
COUNTRY_AZO = 163,
COUNTRY_MAD = 164,
COUNTRY_RES9 = 165,
COUNTRY_RES10 = 166,
COUNTRY_RES11 = 167,
COUNTRY_RES12 = 168,
COUNTRY_CAD = 169,
COUNTRY_GRE = 170,
COUNTRY_PIE = 171,
COUNTRY_USA = 172,
COUNTRY_BER = 173,
COUNTRY_MEX = 174,
COUNTRY_GUA = 175,
COUNTRY_BLI = 176,
COUNTRY_SAR = 177,
COUNTRY_HOR = 178,
COUNTRY_NIC = 179,
COUNTRY_COR = 180,
COUNTRY_PAN = 181,
COUNTRY_TBM = 182,
COUNTRY_TCI = 183,
COUNTRY_CUB = 184,
COUNTRY_JAM = 185,
COUNTRY_CAY = 186,
COUNTRY_HAT = 187,
COUNTRY_TDO = 188,
COUNTRY_PUR = 189,
COUNTRY_VIL = 190,
COUNTRY_BVI = 191,
COUNTRY_ATV = 192,
COUNTRY_ANB = 193,
COUNTRY_CSM = 194,
COUNTRY_ACY = 195,
COUNTRY_SBY = 196,
COUNTRY_SKN = 197,
COUNTRY_MOT = 198,
COUNTRY_GLP = 199,
COUNTRY_DOM = 200,
COUNTRY_MTE = 201,
COUNTRY_LUC = 202,
COUNTRY_SVG = 203,
COUNTRY_GRD = 204,
COUNTRY_BAR = 205,
COUNTRY_TRT = 206,
COUNTRY_CUR = 207,
COUNTRY_ARB = 208,
195
Device Network SDK (ANPR) Developer Guide
COUNTRY_NEA = 209,
COUNTRY_COL = 210,
COUNTRY_VEN = 211,
COUNTRY_GUY = 212,
COUNTRY_SUR = 213,
COUNTRY_FRN = 214,
COUNTRY_ECU = 215,
COUNTRY_PER = 216,
COUNTRY_BOL = 217,
COUNTRY_PAR = 218,
COUNTRY_CLE = 219,
COUNTRY_BRA = 220,
COUNTRY_UGY = 221,
COUNTRY_ARG = 222,
COUNTRY_RES13 = 223,
COUNTRY_RES14 = 224,
COUNTRY_RES15 = 225,
COUNTRY_RES16 = 226,
COUNTRY_ATN = 227,
COUNTRY_NED = 228,
COUNTRY_PNG = 229,
COUNTRY_SAN = 230,
COUNTRY_VAU = 231,
COUNTRY_NCN = 232,
COUNTRY_PAU = 233,
COUNTRY_FSM = 234,
COUNTRY_MRI = 235,
COUNTRY_CNM = 236,
COUNTRY_TEG = 237,
COUNTRY_NUR = 238,
COUNTRY_KIB = 239,
COUNTRY_FID = 240,
COUNTRY_TNG = 241,
COUNTRY_TUV = 242,
COUNTRY_WEF = 243,
COUNTRY_TIS = 244,
COUNTRY_EAS = 245,
COUNTRY_TOE = 246,
COUNTRY_NUE = 247,
COUNTRY_TCD = 248,
COUNTRY_PFP = 249,
COUNTRY_PID = 250,
COUNTRY_HAW = 251,
COUNTRY_RES17 = 252,
COUNTRY_RES18 = 253,
COUNTRY_UNRECOGNIZED = 0xfe,
COUNTRY_ALL = 0xff,
COUNTRY_INVALID = 0xfd
}COUNTRY_INDEX
196
Device Network SDK (ANPR) Developer Guide
Members
COUNTRY_NONSUPPORT
Not support
COUNTRY_CZE
Czech Republic
COUNTRY_DEU
Germany
COUNTRY_ESP
Spain
COUNTRY_ITA
Italy
COUNTRY_NLD
Netherlands
COUNTRY_POL
Poland
COUNTRY_SVK
Slovakia
COUNTRY_BLR
Belorussia
COUNTRY_MDA
Moldova
COUNTRY_RUS
Russia
COUNTRY_UKR
Ukraine
COUNTRY_BEL
Belgium
COUNTRY_BGR
Bulgaria
COUNTRY_DNK
Denmark
COUNTRY_FIN
Finland
COUNTRY_GBR
197
Device Network SDK (ANPR) Developer Guide
United Kingdom
COUNTRY_GRC
Greece
COUNTRY_HRV
Croatia
COUNTRY_HUN
Hungary
COUNTRY_ISR
Israel
COUNTRY_LUX
Luxembourg
COUNTRY_MKD
Macedonia
COUNTRY_NOR
Norway
COUNTRY_PRT
Portugal
COUNTRY_ROU
Romania
COUNTRY_SRB
Serbia
COUNTRY_AZE
Azerbaijan
COUNTRY_GEO
Georgia
COUNTRY_KAZ
Kazakhstan
COUNTRY_LTU
Lithuania
COUNTRY_TKM
Turkmenistan
COUNTRY_UZB
Uzbekistan
COUNTRY_LVA
198
Device Network SDK (ANPR) Developer Guide
Latvia
COUNTRY_EST
Estonia
COUNTRY_ALB
Albania
COUNTRY_AUT
Austria
COUNTRY_BIH
Bosnia and Herzegovina
COUNTRY_IRL
Ireland
COUNTRY_ISL
Iceland
COUNTRY_VAT
Vatican
COUNTRY_MLT
Malta
COUNTRY_SWE
Sweden
COUNTRY_CHE
Switzerland
COUNTRY_CYP
Cyprus
COUNTRY_TUR
Turkey
COUNTRY_SVN
Slovenia
COUNTRY_MTG
Montenegro
COUNTRY_KOV
Kosovo
COUNTRY_ADR
Andorra
COUNTRY_ARM
199
Device Network SDK (ANPR) Developer Guide
Armenia
COUNTRY_MON
Monaco
COUNTRY_LIE
Liechtenstein
COUNTRY_SMO
San Marino
COUNTRY_RES1
Reserved
COUNTRY_RES2
Reserved
COUNTRY_RES3
Reserved
COUNTRY_RES4
Reserved /* Asia, 48 countries, in which Cyprus is located on the border of Europe and Asia*/
COUNTRY_CHI
China
COUNTRY_IBN
In bahrain
COUNTRY_SKR
South Korea
COUNTRY_LEB
Lebanon
COUNTRY_NEP
Nepal
COUNTRY_THA
Thailand
COUNTRY_PAK
Pakistan
COUNTRY_EMI
The united Arab emirates
COUNTRY_BHU
Bhutan
COUNTRY_OMA
200
Device Network SDK (ANPR) Developer Guide
Oman
COUNTRY_KOR
North Korea
COUNTRY_PHI
The Philippines
COUNTRY_CAM
Cambodia
COUNTRY_QAT
Qatar
COUNTRY_KYR
Kyrgyzstan
COUNTRY_MAL
The maldives
COUNTRY_MLY
Malaysia
COUNTRY_MOG
Mongolia
COUNTRY_ARA
Saudi Arabia
COUNTRY_BRU
brunei
COUNTRY_LAO
Laos
COUNTRY_JAP
Japan
COUNTRY_RES19
Reserved
COUNTRY_PAS
Palestinian state
COUNTRY_TAJ
Tajikistan
COUNTRY_KUW
Kuwait
COUNTRY_SYR
201
Device Network SDK (ANPR) Developer Guide
Syria
COUNTRY_IND
India
COUNTRY_ISA
Indonesia
COUNTRY_AFG
Afghanistan
COUNTRY_LAN
Sri Lanka
COUNTRY_IRQ
Iraq
COUNTRY_VIE
Vietnam
COUNTRY_IRA
Iran
COUNTRY_YEM
yemen
COUNTRY_JOR
Jordan
COUNTRY_BUR
Burma
COUNTRY_SIK
Sikkim
COUNTRY_BAN
Bangladesh
COUNTRY_SGA
Singapore
COUNTRY_EAT
East Timor
COUNTRY_RES5
Reserved
COUNTRY_RES6
Reserved
COUNTRY_RES7
202
Device Network SDK (ANPR) Developer Guide
Reserved
COUNTRY_RES8
Reserved /*Africa, 60 countries and regions*/
COUNTRY_EGT
Egypt
COUNTRY_LIY
Libya
COUNTRY_SUA
Sudan
COUNTRY_TUN
Tunisia
COUNTRY_ALG
Algeria
COUNTRY_MCC
Morocco
COUNTRY_ETH
Ethiopia
COUNTRY_ERI
Eritrea
COUNTRY_SDE
Somalia Democratic
COUNTRY_DJI
Djibouti
COUNTRY_KEN
Kenya
COUNTRY_TAI
Tanzania
COUNTRY_UGA
Uganda
COUNTRY_RWA
Rwanda
COUNTRY_BUD
Burundi
COUNTRY_SEY
203
Device Network SDK (ANPR) Developer Guide
Seychelles
COUNTRY_CHA
Chad
COUNTRY_CEA
Central African
COUNTRY_CON
Cameroon
COUNTRY_EQG
Equatorial Guinea
COUNTRY_GAB
Gabon
COUNTRY_TCO
the Congo
COUNTRY_DRC
Democratic Republic of the Congo
COUNTRY_STP
Sao Tome and Principe
COUNTRY_MAN
Mauritania
COUNTRY_WSA
Western Sahara
COUNTRY_SEL
Senega
COUNTRY_TGA
the Gambia
COUNTRY_MAI
Mali
COUNTRY_BUF
Burkina Faso
COUNTRY_GUI
Guinea
COUNTRY_GUB
Guinea-Bissau
COUNTRY_CAV
204
Device Network SDK (ANPR) Developer Guide
Cape Verde
COUNTRY_SLE
Sierra Leone
COUNTRY_LIR
Liberia
COUNTRY_IVC
Ivory Coast
COUNTRY_GHA
Ghana
COUNTRY_TGO
Togo
COUNTRY_BEN
Benin
COUNTRY_NIG
Niger
COUNTRY_ZAB
Zambia
COUNTRY_ANG
Angola
COUNTRY_ZBE
Zimbabwe
COUNTRY_MAW
Malawi
COUNTRY_MOQ
Mozambique
COUNTRY_BOT
Botswana
COUNTRY_NAM
Namibia
COUNTRY_SAF
South Africa
COUNTRY_SWD
Swaziland
COUNTRY_LES
205
Device Network SDK (ANPR) Developer Guide
Lesotho
COUNTRY_MAG
Madagasca
COUNTRY_UOC
Union of Comoros
COUNTRY_MAT
Mauritius
COUNTRY_NGE
Nigeria
COUNTRY_SSD
South Sudan
COUNTRY_SAH
Saint Helena
COUNTRY_MYT
Mayotte
COUNTRY_REN
Reunion
COUNTRY_CAI
Canary Islands
COUNTRY_AZO
AZORES
COUNTRY_MAD
Madeira
COUNTRY_RES9
Reserved
COUNTRY_RES10
Reserved
COUNTRY_RES11
Reserved
COUNTRY_RES12
Reserved /*America, 55 countries and regions*/
COUNTRY_CAD
Canada
COUNTRY_GRE
206
Device Network SDK (ANPR) Developer Guide
Greenland Nuuk
COUNTRY_PIE
/Pierre and Miquelon
COUNTRY_USA
United States
COUNTRY_BER
Bermuda
COUNTRY_MEX
Mexico
COUNTRY_GUA
Guatemala
COUNTRY_BLI
Belize
COUNTRY_SAR
El Salvador
COUNTRY_HOR
Honduras
COUNTRY_NIC
Nicaragua
COUNTRY_COR
Costa Rica
COUNTRY_PAN
Panama
COUNTRY_TBM
The Bahamas
COUNTRY_TCI
The Turks and Caicos Islands
COUNTRY_CUB
Cuba
COUNTRY_JAM
Jamaica
COUNTRY_CAY
Cayman Islands
COUNTRY_HAT
207
Device Network SDK (ANPR) Developer Guide
Haiti
COUNTRY_TDO
The Dominican
COUNTRY_PUR
Puerto Rico
COUNTRY_VIL
The United States Virgin Islands
COUNTRY_BVI
The British Virgin Islands
COUNTRY_ATV
Anguilla The Valley
COUNTRY_ANB
Antigua and Barbuda
COUNTRY_CSM
Collectivite de Saint-Martin
COUNTRY_ACY
Autonomous country
COUNTRY_SBY
Saint-Barthelemy
COUNTRY_SKN
Saint Kitts and Nevis
COUNTRY_MOT
Montserrat
COUNTRY_GLP
Guadeloupe
COUNTRY_DOM
Dominica
COUNTRY_MTE
Martinique
COUNTRY_LUC
St. Lucia
COUNTRY_SVG
Saint Vincent and the Grenadines
COUNTRY_GRD
208
Device Network SDK (ANPR) Developer Guide
Grenada
COUNTRY_BAR
Barbados
COUNTRY_TRT
Trinidad and Tobago
COUNTRY_CUR
Curaao
COUNTRY_ARB
Aruba
COUNTRY_NEA
Netherlands Antilles
COUNTRY_COL
Colombia
COUNTRY_VEN
Venezuela
COUNTRY_GUY
Guyana
COUNTRY_SUR
Suriname
COUNTRY_FRN
Guyane Francaise
COUNTRY_ECU
Ecuador
COUNTRY_PER
Peru
COUNTRY_BOL
Bolivia
COUNTRY_PAR
Paraguay
COUNTRY_CLE
Chile
COUNTRY_BRA
Brazil
COUNTRY_UGY
209
Device Network SDK (ANPR) Developer Guide
Uruguay
COUNTRY_ARG
Argentina
COUNTRY_RES13
Reserved
COUNTRY_RES14
Reserved
COUNTRY_RES15
Reserved
COUNTRY_RES16
Reserved /*Oceania, 25 countries and regions*/
COUNTRY_ATN
Australien
COUNTRY_NED
Neuseeland
COUNTRY_PNG
Papua New Guinea
COUNTRY_SAN
Salomonen
COUNTRY_VAU
Vanuatu
COUNTRY_NCN
New Caledonia
COUNTRY_PAU
Palau
COUNTRY_FSM
Federated States of Micronesia
COUNTRY_MRI
Marshall Island
COUNTRY_CNM
Commonwealth of the Northern Mariana Islands
COUNTRY_TEG
The Territory of Guahan
COUNTRY_NUR
210
Device Network SDK (ANPR) Developer Guide
Nauru
COUNTRY_KIB
Kiribati
COUNTRY_FID
Fidschi
COUNTRY_TNG
Tonga
COUNTRY_TUV
Tuvalu
COUNTRY_WEF
Wallis et Futuna
COUNTRY_TIS
The Independent State of Samoa
COUNTRY_EAS
Eastern Samoa
COUNTRY_TOE
Tokelau
COUNTRY_NUE
Niue
COUNTRY_TCD
The Cook Islands
COUNTRY_PFP
Polynesie franaise French Polynesia
COUNTRY_PID
Pitcairn Islands
COUNTRY_HAW
Hawaii State
COUNTRY_RES17
Reserved
COUNTRY_RES18
Reserved
COUNTRY_UNRECOGNIZED
Unrecognized
COUNTRY_ALL
211
Device Network SDK (ANPR) Developer Guide
ALL
COUNTRY_INVALID
byCountry is invalid and you should use CRIndex, see CR_INDEX for details.
7.2.2 CR_INDEX
Enumeration about country or region index.
Enumeration Definition
enum{
CR_NONSUPPORT = 0,
CR_CZE = 1,
CR_FRA = 2,
CR_DEU = 3,
CR_ESP = 4,
CR_ITA = 5,
CR_NLD = 6,
CR_POL = 7,
CR_SVK = 8,
CR_BLR = 9,
CR_MDA = 10,
CR_RUS = 11,
CR_UKR = 12,
CR_BEL = 13,
CR_BGR = 14,
CR_DNK = 15,
CR_FIN = 16,
CR_GBR = 17,
CR_GRC = 18,
CR_HRV = 19,
CR_HUN = 20,
CR_ISR = 21,
CR_LUX = 22,
CR_MKD = 23,
CR_NOR = 24,
CR_PRT = 25,
CR_ROU = 26,
CR_SRB = 27,
CR_AZE = 28,
CR_GEO = 29,
CR_KAZ = 30,
CR_LTU = 31,
CR_TKM = 32,
CR_UZB = 33,
CR_LVA = 34,
CR_EST = 35,
CR_ALB = 36,
CR_AUT = 37,
212
Device Network SDK (ANPR) Developer Guide
CR_BIH = 38,
CR_IRL = 39,
CR_ISL = 40,
CR_VAT = 41,
CR_MLT = 42,
CR_SWE = 43,
CR_CHE = 44,
CR_CYP = 45,
CR_TUR = 46,
CR_SVN = 47,
CR_MTG = 48,
CR_KOV = 49,
CR_ADR = 50,
CR_ARM = 51,
CR_MON = 52,
CR_LIE = 53,
CR_SMO = 54,
CR_RES1 = 55,
CR_RES2 = 56,
CR_RES3 = 57,
CR_RES4 = 58,
CR_CHI = 59,
CR_IBN = 60,
CR_SKR = 61,
CR_LEB = 62,
CR_NEP = 63,
CR_THA = 64,
CR_PAK = 65,
CR_EMI = 66,
CR_BHU = 67,
CR_OMA = 68,
CR_KOR = 69,
CR_PHI = 70,
CR_CAM = 71,
CR_QAT = 72,
CR_KYR = 73,
CR_MAL = 74,
CR_MLY = 75,
CR_MOG = 76,
CR_ARA = 77,
CR_BRU = 78,
CR_LAO = 79,
CR_JAP = 80,
CR_RES19 = 81,
CR_PAS = 82,
CR_TAJ = 83,
CR_KUW = 84,
CR_SYR = 85,
CR_IND = 86,
CR_ISA = 87,
CR_AFG = 88,
CR_LAN = 89,
213
Device Network SDK (ANPR) Developer Guide
CR_IRQ = 90,
CR_VIE = 91,
CR_IRA = 92,
CR_YEM = 93,
CR_JOR = 94,
CR_BUR = 95,
CR_SIK = 96,
CR_BAN = 97,
CR_SGA = 98,
CR_EAT = 99,
CR_RES5 = 100,
CR_RES6 = 101,
CR_RES7 = 102,
CR_RES8 = 103,
CR_EGT = 104,
CR_LIY = 105,
CR_SUA = 106,
CR_TUN = 107,
CR_ALG = 108,
CR_MCC = 109,
CR_ETH = 110,
CR_ERI = 111,
CR_SDE = 112,
CR_DJI = 113,
CR_KEN = 114,
CR_TAI = 115,
CR_UGA = 116,
CR_RWA = 117,
CR_BUD = 118,
CR_SEY = 119,
CR_CHA = 120,
CR_CEA = 121,
CR_CON = 122,
CR_EQG = 123,
CR_GAB = 124,
CR_TCO = 125,
CR_DRC = 126,
CR_STP = 127,
CR_MAN = 128,
CR_WSA = 129,
CR_SEL = 130,
CR_TGA = 131,
CR_MAI = 132,
CR_BUF = 133,
CR_GUI = 134,
CR_GUB = 135,
CR_CAV = 136,
CR_SLE = 137,
CR_LIR = 138,
CR_IVC = 139,
CR_GHA = 140,
CR_TGO = 141,
214
Device Network SDK (ANPR) Developer Guide
CR_BEN = 142,
CR_NIG = 143,
CR_ZAB = 144,
CR_ANG = 145,
CR_ZBE = 146,
CR_MAW = 147,
CR_MOQ = 148,
CR_BOT = 149,
CR_NAM = 150,
CR_SAF = 151,
CR_SWD = 152,
CR_LES = 153,
CR_MAG = 154,
CR_UOC = 155,
CR_MAT = 156,
CR_NGE = 157,
CR_SSD = 158,
CR_SAH = 159,
CR_MYT = 160,
CR_REN = 161,
CR_CAI = 162,
CR_AZO = 163,
CR_MAD = 164,
CR_RES9 = 165,
CR_RES10 = 166,
CR_RES11 = 167,
CR_RES12 = 168,
CR_CAD = 169,
CR_GRE = 170,
CR_PIE = 171,
CR_USA = 172,
CR_BER = 173,
CR_MEX = 174,
CR_GUA = 175,
CR_BLI = 176,
CR_SAR = 177,
CR_HOR = 178,
CR_NIC = 179,
CR_COR = 180,
CR_PAN = 181,
CR_TBM = 182,
CR_TCI = 183,
CR_CUB = 184,
CR_JAM = 185,
CR_CAY = 186,
CR_HAT = 187,
CR_TDO = 188,
CR_PUR = 189,
CR_VIL = 190,
CR_BVI = 191,
CR_ATV = 192,
CR_ANB = 193,
215
Device Network SDK (ANPR) Developer Guide
CR_CSM = 194,
CR_ACY = 195,
CR_SBY = 196,
CR_SKN = 197,
CR_MOT = 198,
CR_GLP = 199,
CR_DOM = 200,
CR_MTE = 201,
CR_LUC = 202,
CR_SVG = 203,
CR_GRD = 204,
CR_BAR = 205,
CR_TRT = 206,
CR_CUR = 207,
CR_ARB = 208,
CR_NEA = 209,
CR_COL = 210,
CR_VEN = 211,
CR_GUY = 212,
CR_SUR = 213,
CR_FRN = 214,
CR_ECU = 215,
CR_PER = 216,
CR_BOL = 217,
CR_PAR = 218,
CR_CLE = 219,
CR_BRA = 220,
CR_UGY = 221,
CR_ARG = 222,
CR_RES13 = 223,
CR_RES14 = 224,
CR_RES15 = 225,
CR_RES16 = 226,
CR_ATN = 227,
CR_NED = 228,
CR_PNG = 229,
CR_SAN = 230,
CR_VAU = 231,
CR_NCN = 232,
CR_PAU = 233,
CR_FSM = 234,
CR_MRI = 235,
CR_CNM = 236,
CR_TEG = 237,
CR_NUR = 238,
CR_KIB = 239,
CR_FID = 240,
CR_TNG = 241,
CR_TUV = 242,
CR_WEF = 243,
CR_TIS = 244,
CR_EAS = 245,
216
Device Network SDK (ANPR) Developer Guide
CR_TOE = 246,
CR_NUE = 247,
CR_TCD = 248,
CR_PFP = 249,
CR_PID = 250,
CR_HAW = 251,
CR_RES17 = 252,
CR_RES18 = 253,
CR_UNRECOGNIZED = 0xfe,
CR_ALL = 0xff,
CR_TAIWAN = 256
}CR_INDEX
Members
CR_NONSUPPORT
Not support
CR_CZE
Czech Republic
CR_DEU
Germany
CR_ESP
Spain
CR_ITA
Italy
CR_NLD
Netherlands
CR_POL
Poland
CR_SVK
Slovakia
CR_BLR
Belorussia
CR_MDA
Moldova
CR_RUS
Russia
CR_UKR
Ukraine
CR_BEL
217
Device Network SDK (ANPR) Developer Guide
Belgium
CR_BGR
Bulgaria
CR_DNK
Denmark
CR_FIN
Finland
CR_GBR
United Kingdom
CR_GRC
Greece
CR_HRV
Croatia
CR_HUN
Hungary
CR_ISR
Israel
CR_LUX
Luxembourg
CR_MKD
Macedonia
CR_NOR
Norway
CR_PRT
Portugal
CR_ROU
Romania
CR_SRB
Serbia
CR_AZE
Azerbaijan
CR_GEO
Georgia
CR_KAZ
218
Device Network SDK (ANPR) Developer Guide
Kazakhstan
CR_LTU
Lithuania
CR_TKM
Turkmenistan
CR_UZB
Uzbekistan
CR_LVA
Latvia
CR_EST
Estonia
CR_ALB
Albania
CR_AUT
Austria
CR_BIH
Bosnia and Herzegovina
CR_IRL
Ireland
CR_ISL
Iceland
CR_VAT
Vatican
CR_MLT
Malta
CR_SWE
Sweden
CR_CHE
Switzerland
CR_CYP
Cyprus
CR_TUR
Turkey
CR_SVN
219
Device Network SDK (ANPR) Developer Guide
Slovenia
CR_MTG
Montenegro
CR_KOV
Kosovo
CR_ADR
Andorra
CR_ARM
Armenia
CR_MON
Monaco
CR_LIE
Liechtenstein
CR_SMO
San Marino
CR_RES1
Reserved
CR_RES2
Reserved
CR_RES3
Reserved
CR_RES4
Reserved /* Asia, 48 countries, in which Cyprus is located on the border of Europe and Asia*/
CR_CHI
China
CR_IBN
In bahrain
CR_SKR
South Korea
CR_LEB
Lebanon
CR_NEP
Nepal
CR_THA
220
Device Network SDK (ANPR) Developer Guide
Thailand
CR_PAK
Pakistan
CR_EMI
The united Arab emirates
CR_BHU
Bhutan
CR_OMA
Oman
CR_KOR
North Korea
CR_PHI
The Philippines
CR_CAM
Cambodia
CR_QAT
Qatar
CR_KYR
Kyrgyzstan
CR_MAL
The maldives
CR_MLY
Malaysia
CR_MOG
Mongolia
CR_ARA
Saudi Arabia
CR_BRU
brunei
CR_LAO
Laos
CR_JAP
Japan
CR_RES19
221
Device Network SDK (ANPR) Developer Guide
Reserved
CR_PAS
Palestinian state
CR_TAJ
Tajikistan
CR_KUW
Kuwait
CR_SYR
Syria
CR_IND
India
CR_ISA
Indonesia
CR_AFG
Afghanistan
CR_LAN
Sri Lanka
CR_IRQ
Iraq
CR_VIE
Vietnam
CR_IRA
Iran
CR_YEM
yemen
CR_JOR
Jordan
CR_BUR
Burma
CR_SIK
Sikkim
CR_BAN
Bangladesh
CR_SGA
222
Device Network SDK (ANPR) Developer Guide
Singapore
CR_EAT
East Timor
CR_RES5
Reserved
CR_RES6
Reserved
CR_RES7
Reserved
CR_RES8
Reserved /*Africa, 60 countries and regions*/
CR_EGT
Egypt
CR_LIY
Libya
CR_SUA
Sudan
CR_TUN
Tunisia
CR_ALG
Algeria
CR_MCC
Morocco
CR_ETH
Ethiopia
CR_ERI
Eritrea
CR_SDE
Somalia Democratic
CR_DJI
Djibouti
CR_KEN
Kenya
CR_TAI
223
Device Network SDK (ANPR) Developer Guide
Tanzania
CR_UGA
Uganda
CR_RWA
Rwanda
CR_BUD
Burundi
CR_SEY
Seychelles
CR_CHA
Chad
CR_CEA
Central African
CR_CON
Cameroon
CR_EQG
Equatorial Guinea
CR_GAB
Gabon
CR_TCO
the Congo
CR_DRC
Democratic Republic of the Congo
CR_STP
Sao Tome and Principe
CR_MAN
Mauritania
CR_WSA
Western Sahara
CR_SEL
Senega
CR_TGA
the Gambia
CR_MAI
224
Device Network SDK (ANPR) Developer Guide
Mali
CR_BUF
Burkina Faso
CR_GUI
Guinea
CR_GUB
Guinea-Bissau
CR_CAV
Cape Verde
CR_SLE
Sierra Leone
CR_LIR
Liberia
CR_IVC
Ivory Coast
CR_GHA
Ghana
CR_TGO
Togo
CR_BEN
Benin
CR_NIG
Niger
CR_ZAB
Zambia
CR_ANG
Angola
CR_ZBE
Zimbabwe
CR_MAW
Malawi
CR_MOQ
Mozambique
CR_BOT
225
Device Network SDK (ANPR) Developer Guide
Botswana
CR_NAM
Namibia
CR_SAF
South Africa
CR_SWD
Swaziland
CR_LES
Lesotho
CR_MAG
Madagasca
CR_UOC
Union of Comoros
CR_MAT
Mauritius
CR_NGE
Nigeria
CR_SSD
South Sudan
CR_SAH
Saint Helena
CR_MYT
Mayotte
CR_REN
Reunion
CR_CAI
Canary Islands
CR_AZO
AZORES
CR_MAD
Madeira
CR_RES9
Reserved
CR_RES10
226
Device Network SDK (ANPR) Developer Guide
Reserved
CR_RES11
Reserved
CR_RES12
Reserved /*America, 55 countries and regions*/
CR_CAD
Canada
CR_GRE
Greenland Nuuk
CR_PIE
/Pierre and Miquelon
CR_USA
United States
CR_BER
Bermuda
CR_MEX
Mexico
CR_GUA
Guatemala
CR_BLI
Belize
CR_SAR
El Salvador
CR_HOR
Honduras
CR_NIC
Nicaragua
CR_COR
Costa Rica
CR_PAN
Panama
CR_TBM
The Bahamas
CR_TCI
227
Device Network SDK (ANPR) Developer Guide
228
Device Network SDK (ANPR) Developer Guide
Dominica
CR_MTE
Martinique
CR_LUC
St. Lucia
CR_SVG
Saint Vincent and the Grenadines
CR_GRD
Grenada
CR_BAR
Barbados
CR_TRT
Trinidad and Tobago
CR_CUR
Curaao
CR_ARB
Aruba
CR_NEA
Netherlands Antilles
CR_COL
Colombia
CR_VEN
Venezuela
CR_GUY
Guyana
CR_SUR
Suriname
CR_FRN
Guyane Francaise
CR_ECU
Ecuador
CR_PER
Peru
CR_BOL
229
Device Network SDK (ANPR) Developer Guide
Bolivia
CR_PAR
Paraguay
CR_CLE
Chile
CR_BRA
Brazil
CR_UGY
Uruguay
CR_ARG
Argentina
CR_RES13
Reserved
CR_RES14
Reserved
CR_RES15
Reserved
CR_RES16
Reserved /*Oceania, 25 countries and regions*/
CR_ATN
Australien
CR_NED
Neuseeland
CR_PNG
Papua New Guinea
CR_SAN
Salomonen
CR_VAU
Vanuatu
CR_NCN
New Caledonia
CR_PAU
Palau
CR_FSM
230
Device Network SDK (ANPR) Developer Guide
231
Device Network SDK (ANPR) Developer Guide
Hawaii State
CR_RES17
Reserved
CR_RES18
Reserved
CR_UNRECOGNIZED
Unrecognized
CR_ALL
ALL
CR_TAIWAN
Taiwan (China)
7.2.3 NET_SDK_DOWNLOAD_TYPE
Enumerate file types to be downloaded.
Enumeration Definition
typedef enum {
NET_SDK_DOWNLOAD_CERT = 0,
NET_SDK_DOWNLOAD_IPC_CFG_FILE = 1,
NET_SDK_DOWNLOAD_BASELINE_SCENE_PIC = 2,
NET_SDK_DOWNLOAD_VQD_ALARM_PIC = 3,
NET_SDK_DOWNLOAD_CONFIGURATION_FILE = 4,
NET_SDK_DOWNLOAD_SCENE_CONFIGURATION_FILE = 5,
NET_SDK_DOWNLOAD_FILE_FORM_DB = 6,
NET_SDK_DOWNLOAD_TME_FILE = 7,
NET_SDK_DOWNLOAD_VEHICLE_BLOCKALLOWLIST_FILE = 8,
NET_SDK_DOWNLOAD_GUID_FILE = 9,
NET_SDK_DOWNLOAD_FILE_FORM_CLOUD = 10,
NET_SDK_DOWNLOAD_PICTURE = 11,
NET_SDK_DOWNLOAD_VIDEO = 12,
NET_DVR_DOWNLOAD_SCREEN_FILE = 13,
NET_SDK_DOWNLOAD_PUBLISH_MATERIAL = 14,
NET_SDK_DOWNLOAD_THERMOMETRIC_FILE = 15,
NET_SDK_DOWNLOAD_LED_CHECK_FILE = 16,
NET_SDK_DOWNLOAD_VEHICLE_INFORMATION = 17,
NET_SDK_DOWNLOAD_CERTIFICATE_BLOCKLIST_TEMPLET = 18,
NET_SDK_DOWNLOAD_LOG_FILE = 19,
NET_SDK_DOWNLOAD_FILEVOLUME_DATA = 20,
NET_SDK_DOWNLOAD_FD_DATA = 21,
NET_SDK_DOWNLOAD_SECURITY_CFG_FILE = 22,
NET_SDK_DOWNLOAD_PUBLISH_SCHEDULE = 23,
NET_SDK_DOWNLOAD_RIGHT_CONTROLLER_AUDIO = 24,
NET_SDK_DOWNLOAD_MODBUS_CFG_FILE = 25,
232
Device Network SDK (ANPR) Developer Guide
NET_SDK_DOWNLOAD_RS485_PROTOCOL_DLL_FILE = 26,
NET_SDK_DOWNLOAD_CLUSTER_MAINTENANCE_LOG = 27,
NET_SDK_DOWNLOAD_SQL_ARCHIVE_FILE = 28,
NET_SDK_DOWNLOAD_SUBWIND_STREAM = 29,
NET_SDK_DOWNLOAD_DEVTYPE_CALIBFILE = 30,
NET_SDK_DOWNLOAD_HD_CAMERA_CORRECT_TABLE = 31,
NET_SDK_DOWNLOAD_CLIENT_CALIBFILE = 32,
NET_SDK_DOWNLOAD_FOUE_CAMERAS_PICTURES = 33,
NET_SDK_DOWNLOAD_DOOR_CONTENT = 34,
NET_SDK_DOWNLOAD_PUBLISH_MATERIAL_THUMBNAIL = 35,
NET_SDK_DOWNLOAD_PUBLISH_PROGRAM_THUMBNAIL = 36,
NET_SDK_DOWNLOAD_PUBLISH_TEMPLATE_THUMBNAIL = 37,
NET_SDK_DOWNLOAD_DARK_FIGHTER_X_CORRECT_TABLE_MAIN = 38,
NET_SDK_DOWNLOAD_DARK_FIGHTER_X_CORRECT_TABLE_BACKUP = 39,
NET_SDK_DOWNLOAD_OFFLINE_CAPTURE_INFO_TEMPLATE = 40,
NET_SDK_DOWNLOAD_CAPTURE_DATA = 41,
NET_SDK_DOWNLOAD_HD_CAMERA_CORRECT_TABLE_FILE = 42,
NET_SDK_DOWNLOAD_CLIENT_CALIBFILE_FILE = 43,
NET_SDK_DOWNLOAD_FOUR_CAMERAS_PICTURES_FILE = 44,
NET_SDK_DOWNLOAD_SCENE_FILE = 45,
NET_SDK_DOWNLOAD_OPEN_SOURCE_CERT = 46,
NET_SDK_DOWNLOAD_RATIOSTITCHING_FILE = 47,
NET_SDK_DOWNLOAD_LENS_PARAM_FILE = 48,
NET_SDK_DOWNLOAD_SELECT_DEVTYPE_CALIBFILE = 49
} NET_SDK_DOWNLOAD_TYPE;
Enumeration Type
NET_SDK_DOWNLOAD_CERT
Certificate.
NET_SDK_DOWNLOAD_IPC_CFG_FILE
Network camera configuration file.
NET_SDK_DOWNLOAD_BASELINE_SCENE_PIC
Base scene picture.
NET_SDK_DOWNLOAD_VQD_ALARM_PIC
VQD (video quality diagnosis) alarm picture.
NET_SDK_DOWNLOAD_CONFIGURATION_FILE
Configuration file.
NET_SDK_DOWNLOAD_SCENE_CONFIGURATION_FILE
Scene configuration file.
NET_SDK_DOWNLOAD_FILE_FORM_DB
File in the image and video library.
NET_SDK_DOWNLOAD_TME_FILE
Entrance and exit management file.
233
Device Network SDK (ANPR) Developer Guide
NET_SDK_DOWNLOAD_VEHICLE_BLOCKALLOWLIST_FILE
Blocklist and allowlist configuration file.
NET_SDK_DOWNLOAD_GUID_FILE
GUID file.
NET_SDK_DOWNLOAD_FILE_FORM_CLOUD
Picture in the cloud storage.
NET_SDK_DOWNLOAD_PICTURE
Picture.
NET_SDK_DOWNLOAD_VIDEO
Video.
NET_DVR_DOWNLOAD_SCREEN_FILE
Screen server file.
NET_SDK_DOWNLOAD_PUBLISH_MATERIAL
Local material file of information release.
NET_SDK_DOWNLOAD_THERMOMETRIC_FILE
Thermometry calibration file.
NET_SDK_DOWNLOAD_LED_CHECK_FILE
LED correction file.
NET_SDK_DOWNLOAD_VEHICLE_INFORMATION
Vehicle information to be exported.
NET_SDK_DOWNLOAD_CERTIFICATE_BLOCKLIST_TEMPLET
ID card blocklist template.
NET_SDK_DOWNLOAD_LOG_FILE
Log to be exported.
NET_SDK_DOWNLOAD_FILEVOLUME_DATA
File volume data file, currently it is only supported by CVR (central video recorder) devices.
NET_SDK_DOWNLOAD_FD_DATA
Data in a specific face picture library to be exported.
NET_SDK_DOWNLOAD_SECURITY_CFG_FILE
Configuration file to be securely exported.
NET_SDK_DOWNLOAD_PUBLISH_SCHEDULE
Schedule to be exported.
NET_SDK_DOWNLOAD_RIGHT_CONTROLLER_AUDIO
Audio file of the main controller.
234
Device Network SDK (ANPR) Developer Guide
NET_SDK_DOWNLOAD_MODBUS_CFG_FILE
Configuration file of Modbus protocol.
NET_SDK_DOWNLOAD_RS485_PROTOCOL_DLL_FILE
Dynamic library file of RS-485 protocol.
NET_SDK_DOWNLOAD_CLUSTER_MAINTENANCE_LOG
Cluster maintenance log to be exported.
NET_SDK_DOWNLOAD_SQL_ARCHIVE_FILE
Archived record in the database to be exported.
NET_SDK_DOWNLOAD_SUBWIND_STREAM
Sub-window stream to be exported.
NET_SDK_DOWNLOAD_DEVTYPE_CALIBFILE
Model calibration file to be exported (*.cal).
NET_SDK_DOWNLOAD_HD_CAMERA_CORRECT_TABLE
24 MP/32 MP correction list to be exported (*.cal).
NET_SDK_DOWNLOAD_CLIENT_CALIBFILE
Client calibration file to be exported (*.pto).
NET_SDK_DOWNLOAD_FOUE_CAMERAS_PICTURES
Four-channel picture package to be exported (.tar).
NET_SDK_DOWNLOAD_DOOR_CONTENT
Door contact information.
NET_SDK_DOWNLOAD_PUBLISH_MATERIAL_THUMBNAIL
Thumbnail of local information release material.
NET_SDK_DOWNLOAD_PUBLISH_PROGRAM_THUMBNAIL
Thumbnail of information release program.
NET_SDK_DOWNLOAD_PUBLISH_TEMPLATE_THUMBNAIL
Thumbnail of information release template.
NET_SDK_DOWNLOAD_DARK_FIGHTER_X_CORRECT_TABLE_MAIN
DarkfighterX correction list file (main partition).
NET_SDK_DOWNLOAD_DARK_FIGHTER_X_CORRECT_TABLE_BACKUP
DarkfighterX correction list file (backup partition).
NET_SDK_DOWNLOAD_OFFLINE_CAPTURE_INFO_TEMPLATE
User list template of collection.
NET_SDK_DOWNLOAD_CAPTURE_DATA
Offline collected data.
235
Device Network SDK (ANPR) Developer Guide
NET_SDK_DOWNLOAD_HD_CAMERA_CORRECT_TABLE_FILE
HD camera correction sheet (CAL format).
NET_SDK_DOWNLOAD_CLIENT_CALIBFILE_FILE
User calibration file (PTO format).
NET_SDK_DOWNLOAD_FOUR_CAMERAS_PICTURES_FILE
Channel pictures package (TAR format).
NET_SDK_DOWNLOAD_SCENE_FILE
Scene file.
NET_SDK_DOWNLOAD_OPEN_SOURCE_CERT
Open source license compliance.
NET_SDK_DOWNLOAD_RATIOSTITCHING_FILE
Ratio stitching file.
NET_SDK_DOWNLOAD_LENS_PARAM_FILE
Lens parameters file.
NET_SDK_DOWNLOAD_SELECT_DEVTYPE_CALIBFILE
Calibration file in CAL format.
7.2.4 NET_SDK_UPLOAD_TYPE
236
Device Network SDK (ANPR) Developer Guide
237
Device Network SDK (ANPR) Developer Guide
238
Device Network SDK (ANPR) Developer Guide
7.2.5 VLR_VEHICLE_CLASS
Enumerate the vehicle parent brands.
Enumeration Definition
typedef enum _VLR_VEHICLE_CLASS{
VLR_OTHER = 0, //Other
VLR_VOLKSWAGEN = 1, //Volkswagen
VLR_BUICK = 2, //Buick
VLR_BMW = 3, //BMW
VLR_HONDA = 4, //Honda
VLR_PEUGEOT = 5, //Peugeot
VLR_TOYOTA = 6, //Toyota
VLR_FORD = 7, //Ford
VLR_NISSAN = 8, //Nissan
VLR_AUDI = 9, //Audi
VLR_MAZDA = 10, //Mazda
VLR_CHEVROLET = 11, //Chevrolet
VLR_CITROEN = 12, //Citroen
VLR_HYUNDAI = 13, //Hyundai
VLR_CHERY = 14, //Chery
VLR_KIA = 15, //Kia
VLR_ROEWE = 16, //Roewe
VLR_MITSUBISHI = 17, //Mitsubishi
VLR_SKODA = 18, //Skoda
VLR_GEELY = 19, //Geely
VLR_ZHONGHUA = 20, //Zhonghua
239
Device Network SDK (ANPR) Developer Guide
240
Device Network SDK (ANPR) Developer Guide
241
Device Network SDK (ANPR) Developer Guide
242
Device Network SDK (ANPR) Developer Guide
243
Device Network SDK (ANPR) Developer Guide
7.2.6 VTR_RESULT
Enumerate the vehicle type recognition results.
Enumeration Definition
typedef enum _VTR_RESULT{
VTR_RESULT_OTHER = 0,
VTR_RESULT_BUS = 1,
VTR_RESULT_TRUCK = 2,
VTR_RESULT_CAR = 3,
VTR_RESULT_MINIBUS = 4,
VTR_RESULT_SMALLTRUCK = 5,
VTR_RESULT_HUMAN = 6,
VTR_RESULT_TUMBREL = 7,
VTR_RESULT_TRIKE = 8,
VTR_RESULT_SUV_MPV = 9,
VTR_RESULT_MEDIUM_BUS = 10,
VTR_RESULT_MOTOR_VEHICLE = 11,
VTR_RESULT_NON_MOTOR_VEHICLE = 12,
VTR_RESULT_SMALLCAR = 13,
VTR_RESULT_MICROCAR = 14,
VTR_RESULT_PICKUP = 15,
VTR_RESULT_CONTAINER_TRUCK = 16,
VTR_RESULT_MINI_TRUCK = 17,
VTR_RESULT_SLAG_CAR = 18,
VTR_RESULT_CRANE = 19,
VTR_RESULT_OIL_TANK_TRUCK = 20,
VTR_RESULT_CONCRETE_MIXER = 21,
VTR_RESULT_PLATFORM_TRAILER = 22,
VTR_RESULT_HATCHBACK = 23,
VTR_RESULT_SALOON = 24,
VTR_RESULT_SPORT_SEDAN = 25
}VTR_RESULT;
Members
VTR_RESULT_OTHER
244
Device Network SDK (ANPR) Developer Guide
Unknown.
VTR_RESULT_BUS
Bus.
VTR_RESULT_TRUCK
Truck.
VTR_RESULT_CAR
Car.
VTR_RESULT_MINIBUS
Minivan.
VTR_RESULT_SMALLTRUCK
Light truck.
VTR_RESULT_HUMAN
Pedestrian.
VTR_RESULT_TUMBREL
Two wheeler.
VTR_RESULT_TRIKE
Tricycle.
VTR_RESULT_SUV_MPV
SUV/MPV.
VTR_RESULT_MEDIUM_BUS
Middle-sized bus.
VTR_RESULT_MOTOR_VEHICLE
Motor vehicle.
VTR_RESULT_NON_MOTOR_VEHICLE
Non-motor vehicle.
VTR_RESULT_SMALLCAR
Small sedan.
VTR_RESULT_MICROCAR
Mini sedan.
VTR_RESULT_PICKUP
Pick-up truck.
VTR_RESULT_CONTAINER_TRUCK
Container truck.
VTR_RESULT_MINI_TRUCK
245
Device Network SDK (ANPR) Developer Guide
246
Device Network SDK (ANPR) Developer Guide
247
Device Network SDK (ANPR) Developer Guide
248
Device Network SDK (ANPR) Developer Guide
A.1 /ISAPI/ITC/capability
Get intelligent traffic capability.
A.2 /ISAPI/Traffic/channels/<ID>/capabilities
Get traffic channel capability.
249
Device Network SDK (ANPR) Developer Guide
Query None
Request None
Response Succeeded: XML_TrafficChannelCap
Failed: XML_ResponseStatus
Remarks
The <ID> in the request URI refers to the traffic channel ID.
A.3 /ISAPI/Traffic/channels/<ID>/licensePlate/filtration?format=json
Get or set the parameters of filtering duplicated license plate.
Remarks
The <ID> in the request URI refers to channel ID.
250
Device Network SDK (ANPR) Developer Guide
A.4 /ISAPI/Traffic/channels/<ID>/searchLPListAudit
Search for license plate list by channel.
Remarks
The <ID> in the request URI refers to the channel ID.
251
Device Network SDK (ANPR) Developer Guide
B.1 JSON_Filtration
Message about license plate filtration in JSON format
{
"Filtration": {
"enabled":
/*optional, boolean, whether to enable filtering duplicated license plate, by default, it is "false"*/
}
}
B.2 JSON_ResponseStatus
JSON message about response status
{
"requestURL":"",
/*optional, string, request URL*/
"statusCode": ,
/*optional, int, status code*/
"statusString":"",
/*optional, string, status description*/
"subStatusCode":"",
/*optional, string, sub status code*/
"errorCode": ,
/*required, int, error code, which corresponds to subStatusCode, this field is required when statusCode is not 1. The
returned value is the transformed decimal number*/
"errorMsg":"",
/*required, string, error details, this field is required when statusCode is not 1*/
"MErrCode": "0xFFFFFFFF",
/*optional, string, error code categorized by functional modules*/
"MErrDevSelfEx": "0xFFFFFFFF"
/*optional, string, extension of MErrCode. It is used to define the custom error code, which is categorized by
functional modules*/
}
B.3 XML_Desc_ITDeviceAbility
Input description message for getting intelligent traffic capability.
<?xml version="1.0" encoding="utf-8"?>
<!--req, description of input parameter pInBuf for getting intelligent traffic capability-->
<ITDeviceAbility version="2.0">
<channelNO><!--req, xs:integer, channel No.--></channelNO>
252
Device Network SDK (ANPR) Developer Guide
Remarks
Refer to the message XML_ITDeviceAbility of for the intelligent traffic capability details.
B.4 XML_EventNotificationAlert_ANPR
XML message about ANPR results
<EventNotificationAlert version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema"><!--required, xs:object, ANPR
result-->
<ipAddress><!--required, xs:string, IPv4 address of the device that triggers the alarm--></ipAddress>
<ipv6Address><!--optional, xs:string, IPv6 address of the device that triggers the alarm--></ipv6Address>
<portNo><!--optional, xs:integer, port No. of the device that triggers the alarm--></portNo>
<protocol><!--required, xs:string, transmission communication protocol type: HTTP, HTTPS, EHome. The value should
be HTTP when ISAPI protocol is transmitted via EZVIZ protocol. The value should be EHome when ISAPI protocol is
transmitted via ISUP--></protocol>
<macAddress><!--optional, xs:string, MAC address--></macAddress>
<dynChannelID><!--optional, xs:string, digital channel No.--></dynChannelID>
<channelID><!--optional, xs:string, channel (video channel) number of the device that triggers the alarm--></
channelID>
<releatedChannelList><!--optional, xs:string, list of channels linked with the alarm (the same alarm source). These
channels, which are used to display live view or playback when the platform receives alarms, and that whose number
is the value of <channelID> are in the same camera. Multiple channel No. should be separated by commas--></
releatedChannelList>
<dateTime>
<!--required, xs:datetime, alarm triggering time, e.g., 2017-04-22T15:39:01+08:00-->
</dateTime>
<activePostCount><!--required, xs:integer, times that the same alarm has been uploaded--></activePostCount>
<eventType><!--required, xs:string, event types, here it should be "ANPR"--></eventType>
<eventState><!--required, xs:string, continuous event's status: active (valid event), inactive (invalid event)--></
eventState>
<eventDescription><!--required, xs:string, event description--></eventDescription>
<channelName><!--optional, xs:string, channel name--></channelName>
<deviceID><!--optional, xs:string, device ID, which should be returned when the alarm is uploaded via ISUP--></
deviceID>
<ANPR><!--optional, xs:object, ANPR alarm information. This node is valid only when the value of <eventType> is
ANPR-->
<region><!--optional, xs:string, region. For details, refer to Region Code--></region>
<country><!--optional, xs:string, country/region. For details, refer to Country/Region Code--></country>
<area><!--optional, xs:string, regions in United Arab Emirates: FJR (Al Fujayrah), AD (Abu Dhabi,), unknown, UMW
(Umm Al Qaiwain), other, AM (Ajman), RAK (Ras Al Khaimah), DB (Dubai), SJ (Sharjah)--></area>
<licensePlate><!--required, xs:string, license plate number: "noPlate" (vehicle without license plate), "unknown" (no
license plate recognized), "XXXXXX" (recognized license plate number). The maximum string size is 32 bytes--></
licensePlate>
<line><!--required, xs:integer, recognized lane number--></line>
<direction><!--optional, xs:string, license plate recognition direction: "reverse", "forward", "unknown"--></
direction>
<confidenceLevel><!--required, xs:integer, confidence level, which ranges from 0 to 100--></confidenceLevel>
253
Device Network SDK (ANPR) Developer Guide
<plateType><!--optional, xs:string, license plate type: "unknown", "92TypeCivil"-92 civil vehicle, "92FarmVehicle"-
civil vehicle two-line license plate, "arm"-police vehicle, "upDownMilitay"-military vehicle (up/down format),
"92TypeArm"-92 armed police vehicle, "leftRightMilitay"-military vehicle (left/right format), "02TypePersonalized"-02
personalized vehicle, "yellowTwoLine"-yellow two-line license plate, "04NewMilitay"-04 new military vehicle,
"embassy"-embassy car, "oneLineArm"-new armed police vehicle with one-line structure, "twoLineArm"-new armed
police vehicle with two-line structure, "yellow1225FarmVehicle"-yellow agricultural vehicle with 1225 structure,
"green1325FarmVehicle"-green agricultural vehicle with 1325 structure, "yellow1325FarmVehicle"-yellow agricultural
vehicle with 1325 structure, "motorola"-motorcycle, "newEnergy"-new energy vehicle license plate, "civilAviation"-
civil aviation license plate, "coach"-driver-training car, "tempTravl"-temporary license plate car, "trailer", "consulate"-
consulate car, "hongKongMacao"-vehicle entering and exiting Hong Kong and Macao, "tempEntry"-temporary entry
car, "emergency"-emergency license plate, "oneLineArmHeadquarters"-armed police headquarter license plate (one-
line), "twoLineArmHeadquarters"-armed police headquarter license plate (two-line)--></plateType>
<plateColor>
<!--optional, xs:string, license plate color: "black", "blue", "golden", "orange", "red", "yellow", "white", "unknow",
"other", "newEnergyYellowGreen" (new energy green and yellow), "civilAviationBlack" (civil aviation black),
"civilAviationGreen" (civil aviation green), "green", "mixedColor" (mixed color), "newEnergyGreen" (new energy
green)-->
</plateColor>
<licenseBright>
<!--optional, xs:integer, license plate brightness, which ranges from 0 to 255-->
</licenseBright>
<Rect><!--optional, coordinates of the license plate thumbnail in the matched picture. The origin is the upper-left
corner of the screen-->
<height><!--required, xs:float, height, value range: [0.000,1.000]--></height>
<width><!--required, xs:float, width, value range: [0.000,1.000]--></width>
<x><!--required, xs:float, X-coordinate of the upper-left point, value range: [0.000,1.000]--></x>
<y><!--required, xs:float, Y-coordinate of the upper-left point, value range: [0.000,1.000]--></y>
</Rect>
<pilotsafebelt>
<!--optional, xs:string, whether the driver is wearing safety belt: "unknown, yes, no"-->
</pilotsafebelt>
<vicepilotsafebelt>
<!--optional, xs:string, whether the co-driver is wearing safety belt: "unknown, yes, no"-->
</vicepilotsafebelt>
<pilotsunvisor>
<!--optional, xs:string, whether the driver room's sun visor is open: "unknown, yes, no"-->
</pilotsunvisor>
<vicepilotsunvisor>
<!--required, xs:string, whether the co-driver room's sun visor is open: "unknown, yes, no"-->
</vicepilotsunvisor>
<envprosign><!--optional, xs:string, whether it is a yellow-label vehicle: "unknown,yes,no"--></envprosign>
<dangmark>
<!--optional, xs:string, whether it is dangerous goods vehicle: "unknown, yes, no"-->
</dangmark>
<uphone>
<!--optional, xs:string, whether the driver is making call: "unknown, yes, no"-->
</uphone>
<pendant>
<!--optional, xs:string, whether there is window hangings detected: "unknown, yes, no"-->
</pendant>
<tissueBox>
<!--optional, xs:string, whether there is tissue box detected: "unknown, yes, no"-->
254
Device Network SDK (ANPR) Developer Guide
</tissueBox>
<frontChild>
<!--optional, xs:string, whether the co-driver is with baby in arm: "unknown, yes, no"-->
</frontChild>
<label>
<!--optional, xs:string, whether there is label detected: "unknown, yes, no"-->
</label>
<decoration>
<!--optional, xs:string, whether there is decoration detected: "unknown, yes, no"-->
</decoration>
<smoking>
<!--optional, xs:string, whether there is smoking detected: "unknown, yes, no"-->
</smoking>
<perfumeBox>
<!--optional, xs:string, whether there is perfume box detected: "unknown, yes, no"-->
</perfumeBox>
<pdvs>
<!--optional, xs:string, whether there is a person sticking out of sunroof: "unknown, yes, no"-->
</pdvs>
<helmet>
<!--optional, xs:string, whether there is helmet detected: "unknown, yes, no"-->
</helmet>
<twoWheelVehicle>
<!--optional, xs:string, whether there is two-wheel detected: "unknown, yes, no"-->
</twoWheelVehicle>
<threeWheelVehicle>
<!--optional, xs:string, whether there is three-wheel detected: "unknown, yes, no"-->
</threeWheelVehicle>
<blackness>
<!--optional, xs:integer, Ringelmann emittance, which is used for smoke detection-->
</blackness>
<plateCharBelieve>
<!--optional, xs:string, confidence of the license plate's character, value range: [0,100.00]. The value is accurate to
two decimal places. For example, if the confidence of characters in the license plate "ZA12345" is 20, 30, 40, 50, 60,
and 70, it indicates that the possibility that the first character recognized is "Z" is 20%, the possibility that the second
character recognized is "A" is 30%, and so forth-->
</plateCharBelieve>
<speedLimit>
<!--optional, xs:integer, maximum speed limit, this node is valid only when overspeeding occurred-->
</speedLimit>
<illegalInfo>
<!--optional, traffic violation information of the vehicle-->
<illegalCode>
<!--required, xs:string, violation code-->
</illegalCode>
<illegalName>
<!--required, xs:string, violation name-->
</illegalName>
<illegalDescription>
<!--optional, xs:string, violation description-->
</illegalDescription>
</illegalInfo>
255
Device Network SDK (ANPR) Developer Guide
<vehicleType>
<!--optional, xs:string, vehicle type: "SUVMPV" (SUV/MPV), "buggy" (small-sized truck), "bus", "concreteMixer"
(concrete mixer), "containerTruck" (container truck), "coupe", "crane", "hatchback", "largeBus" (large-sized bus),
"lightTruck" (light truck), "mediumBus" (middle-sized bus), "mediumHeavyTruck" (medium and heavy truck),
"miniCar" (mini sedan (transformed to "vehicle")), "minibus", "minitruck", "motorVehicle" (motor vehicle
(transformed to "vehicle")), "nonmotorVehicle" (non-motor vehicle (transformed to "threeWheelVehicle")),
"oilTankTruck" (oil tank truck), "pedestrian", "pickupTruck" (pickup truck (transformed to "buggy")), "platformTrailer"
(platform trailer), "saloon", "slagTruck" (dump truck), "smallCar" (small sedan (transformed to "vehicle")),
"threeWheelVehicle" (tricycle), "truck", "twoWheelVehicle" (two wheeler), "unknown", "van", "vehicle" (sedan)-->
</vehicleType>
<postPicFileName>
<!--optional, xs:string, name of the picture selected as the checkpoint picture when illegal action occurs, "none"
refers to not selecting any picture-->
</postPicFileName>
<featurePicFileName>
<!--optional, xs:string, name of the picture selected as the close-up picture when running the red light in the
intersection violation system is detected, "none" refers to not selecting any picture-->
</featurePicFileName>
<detectDir>
<!--optional, xs:integer, detection direction: 1-upward, 2-downward, 3-bidirectional, 4-westward, 5-northward, 6-
eastward, 7-southward, 8-other-->
</detectDir>
<detectType>
<!--optional, xs:integer, detection type: 1-inductive loop trigger, 2-video trigger, 3-multiple-frame recognition, 4-
radar trigger-->
</detectType>
<barrierGateCtrlType>
<!--optional, xs:integer, whether the barrier gate is opened: 0-opened, 1-not opened-->
</barrierGateCtrlType>
<alarmDataType>
<!--optional, xs:integer, 0-real-time data, 1-history data-->
</alarmDataType>
<dwIllegalTime>
<!--optional, xs:integer, violation duration, which is the time difference between the capture time of the last
picture and that of the first picture, unit: millisecond-->
</dwIllegalTime>
<vehicleInfo><!--optional, xs:object, vehicle information-->
<index>
<!--required, xs:integer, vehicle No.-->
</index>
<vehicleType>
<!--optional, xs:integer, vehicle type: 0-other vehicle, 1-small-sized vehicle, 2-large-sized vehicle, 3-pedestrian
trigger, 4-two wheeler trigger, 5-tricycle trigger, 6-motor vehicle trigger-->
</vehicleType>
<colorDepth>
<!--required, xs:integer, shade of the vehicle color: 0-deep color, 1-light color-->
</colorDepth>
<color>
<!--required, xs:string, vehicle color: "unknown", "white", "silver"-silvery, "gray", "blacks"-black, "red",
"deepBlue"-dark blue, "blue", "yellow", "green", "brown", "pink", "purple", "deepGray"-dark gray, "cyan", "orange"-->
</color>
<speed>
256
Device Network SDK (ANPR) Developer Guide
257
Device Network SDK (ANPR) Developer Guide
<cardNo>
<!--optional, xs:string, card No.-->
</cardNo>
<parkType>
<!--optional, xs:string, parking type: "permanent", "temporary"-->
</parkType>
</EntranceInfo>
<pictureInfoList><!--required, xs:object, picture list. Up to 8 pictures can be supported-->
<pictureInfo><!--required, xs:object, picture information-->
<fileName>
<!--required, xs:string, picture name, which must correspond to the picture name transmitted with the alarm
message-->
</fileName>
<type>
<!--required, xs:string, picture type: "detectionPicture, licensePlatePicture, pilotPicture, copilotPicture,
compositePicture, plateBinaryPicture, nonMotorPicture, pedestrianDetectionPicture, pedestrianPicture"-->
</type>
<dataType>
<!--required, xs:integer, data type: 0-upload data, 1-upload URL-->
</dataType>
<picRecogMode>
<!--optional, xs:integer, 0-front license plate recognition, 1-rear license plate recognition-->
</picRecogMode>
<redLightTime>
<!--optional, xs:integer, red light time elapsed, unit: second-->
</redLightTime>
<vehicleHead>
<!--optional, xs:integer, "unknown", "forward"-front license plate recognition, "back"-rear license plate
recognition-->
</vehicleHead>
<absTime>
<!--optional, xs:time, absolute time, format: yyyyMMddHHmmssxxx, e.g.: 20090810235959999, the last three
number is time in millisecond-->
</absTime>
<plateRect>
<!--dependent, the normalized value is the current image size in percentage multiplying 1000 and it is accurate
to three decimal places. This node is valid only when <type> is "detectionPicture"-->
<X>
<!--required, xs:integer, X-coordinate of the upper-left corner of the boundary frame-->
</X>
<Y>
<!--required, xs:integer, Y-coordinate of the upper-left corner of the boundary frame-->
</Y>
<width>
<!--required, xs:integer, width of the boundary frame-->
</width>
<height>
<!--required, xs:integer, height of the boundary frame-->
</height>
</plateRect>
<vehicelRect>
<!--dependent, the normalized value is the current image size in percentage multiplying 1000. This node is valid
258
Device Network SDK (ANPR) Developer Guide
259
Device Network SDK (ANPR) Developer Guide
alarm of ANPR and intelligent arming of vehicle will be uploaded; if this node is not returned, it is normal vehicle
detection--></vehiclePositionControl>
<vehicleMonitorTaskID><!--optional, xs:string, task ID of intelligent arming of vehicle, the maximum size is 64 bytes,
this node is returned when the value of vehiclePositionControl is "vehicleMonitor"--></vehicleMonitorTaskID>
<vehicleListName><!--optional, xs:string, name of the list that the vehicle belongs to, the maximum size is 128
bytes--></vehicleListName>
<vehicleThermometryEnabled><!--optional, xs:boolean, whether to enable vehicle temperature measurement--
>true</vehicleThermometryEnabled>
<currTemperature><!--optional, xs:float, temperature-->36.5</currTemperature>
<thermometryUnit><!--optional, xs:string, temperature unit: celsius, fahrenheit, kelvin-->celsius</
thermometryUnit>
<plateCategory><!--optional, xs:string, additional license plate information, the maximum string size is 8 bytes. This
node is only used for license plates of the Middle East-->test</plateCategory>
<plateSize><!--optional, xs:int, license plate size: 0 (unknown), 1 (long), 2 (short, which is used for license plates of
the Middle East)-->1</plateSize>
</ANPR>
<UUID>
<!--optional, xs:string, common ID, which is used to link the same capture across multiple servers-->
</UUID>
<picNum>
<!--optional, xs:integer, number of pictures-->
</picNum>
<monitoringSiteID>
<!--optional, xs:string, camera No.-->
</monitoringSiteID>
<ePlateUUID>
<!--optional, xs:string, electronic license plate ID. If this node is configured with a value, it indicates that an
electronic license plate is linked-->
</ePlateUUID>
<isDataRetransmission><!--optional, xs:boolean, data retransmission mark--></isDataRetransmission>
<SceneInfo><!--optional, scene information-->
<scenesID><!--optional, xs:string, scene ID, value range: [1,16]--></scenesID>
<sceneName><!--optional, xs:string, scene name, the maximum size is 32 bytes--></sceneName>
<PTZPos><!--optional, PTZ information-->
<elevation><!--optional, xs:integer, value range: [-900,2700]--></elevation>
<azimuth><!--optional, xs:integer, value range: [0,3600]--></azimuth>
<absoluteZoom><!--optional, xs:integer, value range: [0,1000]--></absoluteZoom>
</PTZPos>
</SceneInfo>
<monitorDescription><!--optional, xs:string, camera information--></monitorDescription>
<DeviceGPSInfo>
<!--optional, xs:object, GPS location information of the device-->
<longitudeType>
<!--required, xs:string, longitude type: E, W-->E
</longitudeType>
<latitudeType>
<!--required, xs:string, latitude type: S, N-->S
</latitudeType>
<Longitude>
<!--required, object, longitude-->
<degree>
<!--required, int, degree-->60
260
Device Network SDK (ANPR) Developer Guide
</degree>
<minute>
<!--required, int, minute, value range: [0,59]-->59
</minute>
<sec>
<!--required, float, second, value range: [0,59.999999]-->59.000000
</sec>
</Longitude>
<Latitude>
<!--required, object, latitude-->
<degree>
<!--required, int, degree-->60
</degree>
<minute>
<!--required, int, minute, value range: [0,59]-->59
</minute>
<sec>
<!--required, float, second, value range: [0,59.999999], the value is accurate to six decimal places-->59.000000
</sec>
</Latitude>
</DeviceGPSInfo>
<pilotStandardSafebelt>
<!--optional, enum, whether the driver is buckled well: unknown, yes, no-->yes
</pilotStandardSafebelt>
<vicepilotStandardSafebelt>
<!--optional, enum, whether the front passenger is buckled well: unknown, yes, no-->yes
</vicepilotStandardSafebelt>
<trafficLightSnap>
<!--optional, enum, whether the picture is captured at the traffic light: yes, no-->yes
</trafficLightSnap>
<sequence>
<!--optional, int, vehicle capture number by the burst triggered by the network, value range: [1,4294967295]. The
burst control command will be applied after triggered by the network. Related URI: /ISAPI/Traffic/startRecognition.
Related API of Device Network SDK: NET_DVR_ContinuousShoot-->0
</sequence>
<relaLaneDirectionType>
<!--optional, int, linked lane direction: 0 (other), 1 (from east to west), 2 (from west to east), 3 (from south to north),
4 (from north to south) ,5 (from southeast to northwest), 6 (from northwest to southeast), 7 (from northeast to
southwest), 8 (from southwest to northeast)-->1
</relaLaneDirectionType>
<carDirectionType>
<!--optional, int, vehicle moving direction on the lane: 0 (downward), 1 (upward)-->1
</carDirectionType>
<targetID>
<!--optional, string, vehicle target ID, value range:[1,64]. The device should ensure that it is unique. It corresponds
to dwMatchNo in the Device Network SDK-->test
</targetID>
<isSecondCamera>
<!--optional, bool, whether the picture is captured by the second camera-->false
</isSecondCamera>
<dataAnalysisType>
<!--optional, int, data analysis type: 0 (data not analyzed), 1 (data already analyzed)-->1
261
Device Network SDK (ANPR) Developer Guide
</dataAnalysisType>
<RecordInfo>
<!--optional, object, vehicle video information-->
<fileName>
<!--required, string, video file name: record.mp4 (vehicle video). When the video is transmitted in binary format,
the value of this node must be the same as that of Content-ID-->record.mp4
</fileName>
<dataType>
<!--required, int, data type: 0 (binary data), 1 (URL)-->0
</dataType>
<URL>
<!--optional, string, URL. This node is valid when the value of <dataType> is URL-->null
</URL>
</RecordInfo>
<VehicleWeightInfo>
<!--optional, object, vehicle weight information-->
<isOverWeight>
<!--optional, bool, whether the vehicle is overweight-->false
</isOverWeight>
<axleNum>
<!--optional, int, number of axles, value range:[1,10]-->4
</axleNum>
<overWeight>
<!--optional, float, weight over the limit, value range: [0.000,100.000], unit: ton. The value is accurate to three
decimal places-->4.502
</overWeight>
<weight>
<!--optional, float, vehicle weight, value range: [0.000,100.000], unit: ton. The value is accurate to three decimal
places-->4.502
</weight>
<limitWeight>
<!--optional, float, weight limit, value range: [0.000,100.000], unit: ton. The value is accurate to three decimal
places-->4.502
</limitWeight>
<axleLen>
<!--optional, float, wheelbase, value range:[0.00,100.00], unit: ton. The value is accurate to two decimal places--
>4.502
</axleLen>
<devDescInfo>
<!--optional, string, device description, the maximum string size is 64 bytes-->null
</devDescInfo>
<AxleInfoList>
<!--optional, object, list of the axle information. The number of elements in the list is the same as the value of
<axleNum>-->
<AxleInfo>
<!--optional, object, information of an axle-->
<axleWeight>
<!--optional, float, axle weight, value range:[0.00,10000.00], unit: kg-->100.00
</axleWeight>
<axleDistance>
<!--optional, int, axle distance, value range:[0,100000], unit: mm. It is the distance between the current axle and
the next axle-->30000
262
Device Network SDK (ANPR) Developer Guide
</axleDistance>
</AxleInfo>
</AxleInfoList>
<length>
<!--optional, int, vehicle length, value range:[1,1000000], unit: cm-->4000
</length>
<width>
<!--optional, int, vehicle width, value range:[1,1000000], unit: cm-->4000
</width>
<height>
<!--optional, int, vehicle height, value range:[1,1000000], unit: cm-->4000
</height>
<tiresNum>
<!--optional, int, number of tires, value range:[1,20]-->4
</tiresNum>
<approvedPassengers>
<!--optional, int, maximum number of passengers allowed, value range:[1,100]-->7
</approvedPassengers>
</VehicleWeightInfo>
<isNotSlowZebraCrossing>
<!--optional, bool, whether the vehicle did not slow down at zebra crossing-->false
</isNotSlowZebraCrossing>
<isTurnRightStop>
<!--optional, bool, whether the vehicle did not stop before turning right-->false
</isTurnRightStop>
<PlateInfoList>
<!--optional, object, license plate information (only used for Hong Kong/Macau license plates)-->
<PlateInfo>
<!--optional, object, information of a license plate-->
<plateRect>
<!--optional, object, coordinate of the license plate area. This node is valid when the value of <type> is
detectionPicture. The value is normalized and equal to the size in percentage of the current image multiplying 1000.
The origin is the upper-left corner of the screen-->
<X>
<!--required, int, X-coordinate of the upper-left corner of the boundary frame, value range: [0,1000]-->1000
</X>
<Y>
<!--required, int, Y-coordinate of the upper-left corner of the boundary frame, value range: [0,1000]-->1000
</Y>
<width>
<!--required, int, width of the boundary frame, value range:[0,1000]-->1000
</width>
<height>
<!--required, int, height of the boundary frame, value range:[0,1000]-->1000
</height>
</plateRect>
<plateColor>
<!--required, enum, license plate color: black, blue, golden, orange, red, yellow, white, unknow, other,
newEnergyYellowGreen (new energy green and yellow), civilAviationBlack (civil aviation black), civilAviationGreen (civil
aviation green), green, mixedColor (mixed color), newEnergyGreen (new energy green)-->black
</plateColor>
<licensePlate>
263
Device Network SDK (ANPR) Developer Guide
<!--required, string, license plate number: noPlate (vehicle without license plate), unknown (no license plate
recognized), XXXXXX (recognized license plate number)-->A283KY77
</licensePlate>
<confidenceLevel>
<!--required, int, confidence level, value range:[0,100]-->50
</confidenceLevel>
</PlateInfo>
</PlateInfoList>
<deviceUUID>
<!--optional, string, device number, the maximum string size is 32 bytes. It is the device's serial number by default
and can be edited by the node <deviceID> in the message of /ISAPI/System/deviceInfo-->12345
</deviceUUID>
</EventNotificationAlert>
See Also
Region Code
Country/Region Code
B.5 XML_EventTriggerCapType
XML message about capability of alarm linkage action types
<EventTriggerCapType version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<isSupportCenter><!--optional, xs:boolean--></isSupportCenter>
<isSupportRecord><!--optional, xs:boolean--></isSupportRecord>
<isSupportMonitorAlarm><!--optional, xs:boolean--></isSupportMonitorAlarm>
<isSupportBeep><!--optional, xs: boolean, whether it supports audible warning--></isSupportBeep>
<isSupportIO><!--optional, xs:boolean--></isSupportIO>
<isSupportFTP><!--optional, xs:boolean--></isSupportFTP>
<isSupportEmail><!--optional, xs:boolean--></isSupEmail>
<isSupportLightAudioAlarm><!--optional, xs:boolean--></isSupportLightAudioAlarm>
<isSupportFocus><!--optional, xs:boolean--></isSupportFocus>
<isSupportPTZ><!--optional, xs:boolean--></isSupportPTZ>
<maxPresetActionNum>
<!--dependent, xs:integer, it is valid only when <isSupportPTZ> is "true"-->
</maxPresetActionNum>
<maxPatrolActionNum>
<!--dependent, xs:integer, it is valid only when <isSupportPTZ> is "true"-->
</maxPatrolActionNum>
<maxPatternActionNum>
<!--dependent, xs:integer, it is valid only when <isSupportPTZ> is "true"-->
</maxPatternActionNum>
<isSupportTrack><!--optional, xs:boolean, whether it supports PTZ linked tracking--></isSupportTrack>
<isSupportWhiteLight>
<!--optional, xs: boolean, whether it supports supplement light alarm linkage-->
</isSupportWhiteLight>
<isSupportCloud><!--optional, xs:boolean, whether it supports upload to the cloud--></isSupportCloud>
<targetNotificationInterval max="1000" min="0" default="30"><!--xs:integer, range: [0, 1000], the default value is 30,
unit: seconds, this node is valid for <MotionDetectionTriggerCap> and <TamperDetectionTriggerCap> and this node is
valid when <isSupportPTZ> is "true"--></targetNotificationInterval>
264
Device Network SDK (ANPR) Developer Guide
<direction opt="both,forward,reverse"><!--xs:string, triggering direction, this node is valid for the node
<BlackListTriggerCap>, <WhiteListTriggerCap>, and <VehicleDetectionTriggerCap>--></direction>
<presetDurationTime min="" max=""><!--dependent, xs:integer--></presetDurationTime>
<isSupportSMS><!--optional, xs:boolean, whether to support SMS (Short Message Service)--></isSupportSMS>
<maxCellphoneNum><!--dependent, xs:integer, the maximum number of cellphones, which is node is valid only
when <isSupportSMS> is "true"--></maxCellphoneNum>
<isSupportOSD><!--optional, xs:boolean--></isSupportOSD>
<isSupportAudio><!--optional, xs:boolean, whether it supports setting audio alarm independently. If this node is set
to "true", audio alarm and buzzer alarm can be linked separately, and the linage method is audio--></isSupportAudio>
<AudioAction><!--dependent, this node is valid when <isSupportBeep> is "true" or <isSupportAudio> is "true"-->
<audioTypeList>
<audioType><!--list-->
<audioID><!--required, xs:integer, alarm sound type--></audioID>
<audioDescription><!--required, xs:string, alarm sound description, it should correspond to the alarm sound type--
></audioDescription>
</audioType>
</audioTypeList>
<alarmTimes opt="0,1,2,3,4,5,6,7,8,9,255"><!--required, xs:integer, alarm times, it is between 0 and 9, 255-
continuous alarm, unit: time--></alarmTimes>
</AudioAction>
<isSupportSMS><!--optional, xs:boolean --></isSupportSMS>
<maxCellphoneNum><!--dependent, if <isSupportSMS> is true, xs:integer--></maxCellphoneNum>
<isNotSupportCenterModify><!--optional, xs:boolean, whether editing configuration parameters of the monitoring
center is not supported: "true"-yes (configuration parameters of the monitoring center cannot be edited), "false" or
this node is not returned-no (configuration parameters of the monitoring center can be edited)--></
isNotSupportCenterModify>
<isSupportMessageConfig>
<!--optional, xs:boolean, whether it supports SMS configuration, if supports, set cellphoneNumber to null-->
</isSupportMessageConfig>
<isSupportAnalogOutput><!--optional, xs:boolean, whether it supports IO output of linkage analog channel--></
isSupportAnalogOutput>
<isSupportIOOutputUnify><!--optional, xs:boolean, whether it supports configuration of IO output--></
isSupportIOOutputUnify>
<isSupportFaceContrast><!--optional, xs:boolean, whether it supports face picture comparison linkage--></
isSupportFaceContrast>
<isSupportSiren><!--optional, xs:boolean, whether it supports siren linkage--></isSupportSiren>
<isSupportOutput><!--optional, xs:boolean, whether it supports relay linkage--></isSupportOutput>
</EventTriggerCapType>
B.6 XML_EventTriggersCap
XML message about linkage capabilities of different alarm categories
<EventTriggersCap version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<DiskfullTriggerCap><!--optional, xs: EventTriggerCapType--></DiskfullTriggerCap>
<DiskerrorTriggerCap><!--optional, xs: EventTriggerCapType--></DiskerrorTriggerCap>
<NicbrokenTriggerCap><!--optional, xs: EventTriggerCapType--></NicbrokenTriggerCap>
<IpconflictTriggerCap><!--optional, xs: EventTriggerCapType--></IpconflictTriggerCap>
<IllaccesTriggerCap><!--optional, xs: EventTriggerCapType--></IllaccesTriggerCap>
<BadvideoTriggerCap><!--optional, xs: EventTriggerCapType--></BadvideoTriggerCap>
265
Device Network SDK (ANPR) Developer Guide
266
Device Network SDK (ANPR) Developer Guide
<isSupportWhiteLightAction>
<!--dependent, xs: boolean, see details in EventTriggerCapType, it is valid when isSupportWhiteLight is "true"-->
</isSupportWhiteLightAction>
<isSupportAudioAction>
<!--dependent, xs: boolean, see details in EventTriggerCapType, it is valid when isSupportBeep is "true"-->
</isSupportAudioAction>
<HFPDTriggerCap><!--optional, xs: EventTriggerCapType--></HFPDTriggerCap>
<MixedTargetDetectionCap><!--optional, xs: EventTriggerCapType--></MixedTargetDetectionCap>
<HVTVehicleDetectionTriggerCap><!--optional, xs: EventTriggerCapType--></HVTVehicleDetectionTriggerCap>
<VCATriggerCap><!--optional, xs: EventTriggerCapType--></VCATriggerCap>
<PIRCap><!--optional, xs: EventTriggerCapType--></PIRCap>
<IllegalParkingTriggerCap><!--optional, xs: EventTriggerCapType, whether it supports illegal parking detection--></
IllegalParkingTriggerCap>
<PedestrianTriggerCap><!--optional, xs: EventTriggerCapType, whether it supports pedestrian detection--></
PedestrianTriggerCap>
<TrafficAccidentTriggerCap><!--optional, xs: EventTriggerCapType, whether it supports traffic accident detection--></
TrafficAccidentTriggerCap>
<ConstructionTriggerCap><!--optional, xs: EventTriggerCapType, whether it supports construction detection--></
ConstructionTriggerCap>
<RoadBlockTriggerCap><!--optional, xs: EventTriggerCapType, whether it supports roadblock detection--></
RoadBlockTriggerCap>
<AbandonedObjectTriggerCap><!--optional, xs: EventTriggerCapType, whether it supports objects dropped down
detection--></AbandonedObjectTriggerCap>
<ParallelParkingTriggerCap><!--optional, xs: EventTriggerCapType, whether it supports parallel parking detection--></
ParallelParkingTriggerCap>
<ParkingStateTriggerCap><!--optional, xs: EventTriggerCapType, whether it supports parking space status detection,
currently this node is not supported--></ParkingStateTriggerCap>
<CongestionTriggerCap><!--optional, xs: EventTriggerCapType, whether it supports congestion detection--></
CongestionTriggerCap>
<IntersectionAnalysisCap><!--optional, xs: EventTriggerCapType, whether it supports intersection analysis--></
IntersectionAnalysisCap>
<ShipsFlowDetectionTriggerCap><!--optional,xs:EventTriggerCapType, ship flow detection--></
ShipsFlowDetectionTriggerCap>
<dredgerDetectionTriggerCap><!--optional,xs:EventTriggerCapType, dredger detection--></
dredgerDetectionTriggerCap>
<voltageInstableTriggerCap><!--optional,xs:EventTriggerCapType, supply voltage exception--></
voltageInstableTriggerCap>
<HighHDTemperatureTriggerCap><!--optional, xs:EventTriggerCapType, HDD high temperature detection--></
HighHDTemperatureTriggerCap>
<LowHDTemperatureTriggerCap><!--optional, xs:EventTriggerCapType, HDD low temperature detection--></
LowHDTemperatureTriggerCap>
<HDImpactTriggerCap><!--optional, xs:EventTriggerCapType, HDD impact detection--></HDImpactTriggerCap>
<HDBadBlockTriggerCap><!--optional, xs:EventTriggerCapType, HDD bad sector detection--></
HDBadBlockTriggerCap>
<SevereHDFailureTriggerCap><!--optional, xs:EventTriggerCapType, HDD severe fault detection--></
SevereHDFailureTriggerCap>
<HUMANATTRIBUTECap><!--optional, xs:EventTriggerCapType--></HUMANATTRIBUTECap>
<HumanAttributeTriggerCap><!--optional, xs:EventTriggerCapType, human body attribute--></
HumanAttributeTriggerCap>
<BlackListFaceContrastTriggerCap><!--opt, xs:EventTriggerCapType, alarm linkage capability of blocklist face
comparison--></BlackListFaceContrastTriggerCap>
<FaceLibTriggerCap><!--optional, xs:EventTriggerCapType--></FaceLibTriggerCap>
267
Device Network SDK (ANPR) Developer Guide
See Also
XML_EventTriggerCapType
B.7 XML_ITCCap
XML message about intelligent traffic capability
<ITCCap version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<isSupportITC><!—dependent, xs:boolean--></isSupportITC>
<isSupportITCStatus>
<!--req, xs:boolean, whether it supports device status-->
</isSupportITCStatus>
<isSupportIllegalDictionary>
<!--req, xs:boolean, whether it supports traffic violation dictionary-->
</isSupportIllegalDictionary>
<isSupportVehicleDetection>
<!--dep, xs: boolean, whether it supports vehicle detection-->
</isSupportVehicleDetection>
<isSupportHVTVehicleDetection><!--dependent, xs:boolean--></isSupportHVTVehicleDetection>
<isSupportlicencePlateAuditData><!--optional, xs:boolean--></isSupportlicencePlateAuditData>
<isSupportSearchLPListAudit><!--optional, xs:boolean--></isSupportSearchLPListAudit>
268
Device Network SDK (ANPR) Developer Guide
<isSupportEvidenceDictionary>
<!--req, xs: boolean, whether it supports traffic law enforcement dictionary-->
</isSupportEvidenceDictionary>
<isSupportITCSetUp>
<!--req, xs:boolean, whether it supports installation parameters-->
</isSupportITCSetUp>
<isSupportTrafficParam>
<!--req, xs:boolean, whether it supports vehicle counting statistics-->
</isSupportTrafficParam>
<isSupportManualCap>
<!--req, xs:boolean, whether it supports manual capture-->
</isSupportManualCap>
<isSupportIllegalUploadPic>
<!--req, xs:boolean, whether it supports uploading pictures-->
</isSupportIllegalUploadPic>
<isSupportContinueCap>
<!--req, xs:boolean, whether it supports continuous capture-->
</isSupportContinueCap>
<isSupportWiper>
<!--req, xs:boolean, whether it supports wiper-->
</isSupportWiper>
<isSupportEntranceCap>
<!--optional, xs:boolean, whether it supports entrance and exit functions-->
</isSupportEntranceCap>
<isSupportPlateRecognitionParam>
<!--req, xs:boolean, whether it supports license plate recognition parameters-->
</isSupportPlateRecognitionParam>
<isSupportSyncSignalOutput>
<!--req, xs:boolean,whether it supports output parameters-->
</isSupportSyncSignalOutput>
<isSupportSyncPower>
<!--req, xs:boolean, whether it supports signal light synchronization-->
</isSupportSyncPower>
<isSupportImageMerge>
<!--req, xs:boolean, whether it supports picture composition-->
</isSupportImageMerge>
<isSupportCabinetParam>
<!--req, xs:boolean, whether it supports device cabinet alarm-->
</isSupportCabinetParam>
<isSupportCarFeatureParam>
<!--req, xs:boolean, whether it supports vehicle features-->
</isSupportCarFeatureParam>
<isSupportLightCorrect>
<!--req, xs:boolean, whether it supports exporting illegal action codes-->
</isSupportLightCorrect>
<isSupportSnapshot>
<!--req, xs:boolean, whether it supports image capture resolution-->
</isSupportSnapshot>
<isSupportIllegalCodeData>
<!--req, xs:boolean, whether it supports signal light correction-->
</isSupportIllegalCodeData>
<isSupportNetStorage>
269
Device Network SDK (ANPR) Developer Guide
B.8 XML_ITDeviceAbility
ITDeviceAbility message in XML format.
<ITDeviceAbility version="2.0"><!--capabilities of traffic camera and traffic terminal server-->
<channelNO><!--req, xs:integer, channel No.--></channelNO>
<ITCAbility><!--req, traffic camera capability-->
<IOInNo min="" max=""/>
<!--req, xs:integer, max and min number of IO input ports-->
<IOOutNo min="" max=""/>
<!--req, xs:integer, max and min number of IO output ports-->
<singleIOTriggerNum>4</singleIOTriggerNum>
<!--req, xs:integer, group number of single IO trigger-->
<lightArrayNum>8</lightArrayNum>
<!--req, xs:integer, group number of traffic lights-->
<measureArrayNum>4</measureArrayNum>
<!--req, xs:integer, group number of velocimetry modes-->
<lensMode opt="CCD,CMOS"/>
<!-- Lens mode-->
<PreTrigger>
<enabled></enabled>
<!--req, whether it is the original trigger mode, no this node if not support-->
</PreTrigger>
<triggerMode
opt="postIOSpeed,postSingleIO,postRS485,postRS485Radar,postVirtualcoil,epoliceIoTrafficLights,epoliceRS485,peRS48
5,postNoComityPed, postRedLightPed, videoEpolice"/>
<!--req, trigger mode, the cameras of the version smaller than V3.1 are not support it-->
<support opt="imageOverlayString,calibrateTime,multiNIC,NICBonding,voiceIntercom,IOEnableCfg,FTPExpand"/>
<!--req, bySupport??
bySupport&0x1??indicates whether support characters overlay configuration extension
bySupport&0x2??indicates whether support extend time correction cofiguration
270
Device Network SDK (ANPR) Developer Guide
<ImageCombine>
<enabled>true</enabled>
<!--req, it supports the picture mergence, no this node if not support-->
</ImageCombine>
<TrafficDataUpload>
<UploadType1>
<enabled>
true</enabled>
<!--req, it supports the uploading mode no.1 (that is, the type supported by intelligent traffic camera,
COMM_UPLOAD_PLATE_RESULT of arming mode), no this node if not support-->
</UploadType1>
<UploadType2>
<enabled>
true</enabled>
<!--req, it supports the uploading mode no.2 (that is, the type supported by ITS,
COMM_ITS_PLATE_RESULT of listening mode), no this node if not support-->
</UploadType2>
<UploadType3>
<enabled>
true</enabled>
<!--req, it supports the uploading mode no.2 (that is, the type supported by intelligent traffic camera,
COMM_ITS_PLATE_RESULT of arming mode), no this node if not support-->
</UploadType3>
</TrafficDataUpload>
<VideoLocalRecord>
<enabled>true</enabled>
<!--req, whether it supports local recording, no this node if not support-->
</VideoLocalRecord>
271
Device Network SDK (ANPR) Developer Guide
<PicLocalStore>
<enabled>true</enabled>
<!--req, whether it supports local storage of pictures, no this node if not support-->
</PicLocalStore>
<PlateRecognise>
<enabled>true</enabled>
<!--req, whether it supports license plate recognition, no this node if not support-->
<regionType opt="rect,polygon"/>
<!--the supported types of license plate recognition area-->
<plateTypeopt opt="standard92,standard02,armedPolice,police,standard92Back,embassy,agricultural,moto"/>
<plateColor opt="blue,yellow,white,black,green"/>
<vehicleType opt="small,big"/>
<bodyworkColor opt="white,silver,gray,black,red,darkblue,blue,yellow,green,brown,pink,violet"/>
</PlateRecognise>
<imageOverlayString>
<mode1>
<!--opt, the character overlay on the picture of original intelligent traffic camera, no this node if not support-->
<overlayStringType
opt="monitor,time,speed,speedRatio,speedLimit,plate,carColor,carLength,carType,laneNum,milliSecond,illegalInfo,red
OnTime"/>
<!--opt, monitoring site, time, speed, overspeed ratio, speed limit sign, license plate, color of vehicle, length of
vehicle,
vehicle type, traffic lane ID, millisecond, violation information, the time that the red light has been lighted-->
</mode1>
<mode2>
<!--opt, the character overlay on the picture of ITS or camera of ITS, no this node if not support-->
<overlapType
opt="monitor,site,roadNum,instrumentNum,directionNum,directionDes,laneNum,laneDes,capTime,capTimeMilli,plate
,carColor,carLength,carType,carBrand,speed,speedRatio,speedLimit,illegalDes,redStart,redStop,redOnTime,securityCod
e,capCode"/>
<!--opt, monitoring site, location, intersection ID, device ID, direction ID, direction description, lane ID, lane
description,
the time of capturing, the time of capturing(millisecond), license plate number, color of vehicle, length of vehicle,
vehicle type,
vehicle brands, speed, overspeed ratio, speed limit sign, violation information, the starting time of red light, the
ending time of
red light, the time that the red light has been lighted, security code, capturing ID-->
<itemLength min="0" max=""/>
<!--opt, length of character overlay-->
<changeLineNum min="0" max="10"/>
<!--opt, the number of line breaks-->
<spaceNum min="0" max="255"/>
<!--opt, the number of spaces-->
<linePercent min="0" max="100"/>
<!--opt, percentage of overlay line-->
<itemsStlye opt="horizontal,vertical"/>
<!--opt, overlay style: horizontal, vertical -->
<startPosTop min="0" max="2448"/>
<!--opt, the upper coordinate of starting point-->
<startPosLeft min="0" max="2448"/>
<!--opt, the left coordinate of starting point-->
<charStyle opt="SongTi,WeiTi"/>
272
Device Network SDK (ANPR) Developer Guide
273
Device Network SDK (ANPR) Developer Guide
</supportMilliCheckTime>
<SnapStatusDetectCFG>
<!--req, enabled parameter capability of status detection, the corresponding stucture is
(NET_DVR_STATUS_DETECTCFG), the node does not display when there is no support-->
<triggerIODectect opt="true,false"/><!--req,IO status detection triggered by ITC, true-enable??false-disable-->
<flashOutDetect opt="true,false"/><!--req,ITC sync-output status detection, true-enable??false-disable-->
<RS485Detect opt="true,false"/><!--req,ITC RS485 receive status detection, true-enable??false-disable-->
<trafficLightDetect opt="true,false"/><!--req,ITC traffic light detection, true-enable??false-disable-->
</SnapStatusDetectCFG>
<SnapRadarParam>
<!--req, radar configuration parameter capability, the corresponding stucture is (NET_ITC_RADAR_PARAM),the
node does not display when there is no support-->
<radarType opt="noRadar,Andaolei,Olivia,microwave,IOExpanBox,other"/><!--req,radar type, 0-noRadar,1-
Andaolei,2-Olivia,3-microwave, 4-IOExpanBox,0xff-other -->
<levelAngle min="0" max="90"/><!--req,the angle with horizontal line, 0~90 -->
<radarSensitivity min="0" max="65535"/><!--req, radar sensitivity, 0~65535 -->
<radarSpeedValidTime min="0" max="2000"/><!--req, valid time of radar speed [0~2000] -->
<lineCorrectParam min="0.0" max="2.0"/>
<!--req,linear correction parameters -->
<constCorrectParam min="-100" max="100"/>
<!--req,constant correction parameters -->
</SnapRadarParam>
<SnapEnableCfg>
<!--req,the corresponding stucture is (NET_DVR_SNAPENABLECFG) -->
<plateEnable opt="true,false"/>
<!--req, whether support plate recognition??0-false??1-true -->
<jpegPICSize min="64" max="8196"/>
<!--req Jpeg size[64-8196]-->
<frameFlip opt="noturn,turn"/>
<!--req 0-noturn(no flip) 1-turn(flip)-->
<flipAngle opt="0,90,180,270"/>
<!--req angle of image: 0,90,180,270-->
<lightPhase min="0" max="360"/>
<!--req phase, data range[0, 360]-->
<lightSyncPower opt="noSynchronized,Synchronized"/>
<!--req whether the signal lamp is synchronized with power supply??0-noSynchronized??1-Synchronized-->
<frequency min="0" max="255"/>
<!--req signal frequency-->
<uploadSDEnable opt="false,true"/>
<!--req whether auto upload SD picture: 0-false, 1-true-->
<plateMode opt="videoTrigger,externalTrigger"/>
<!--req recognition mode parameter: 0-videoTrigger, 1-externalTrigger-->
<uploadInfoFTP opt="false,true"/>
<!--req whether upload the additional info of capture to FTP: 0-false, 1-true-->
<autoFormatSD opt="false,true"/>
<!--req whether auto format SD card: 0-false, 1-true-->
</SnapEnableCfg>
<ITCIOoutParam>
274
Device Network SDK (ANPR) Developer Guide
<defaultStatus opt="lowlevel,highlevel"/>
<!--req IO default status: 0 - lowlevel??1 - highlevel-->
<IOoutStatus opt="lowlevel,highlevel,impulse"/>
<!--req IO valid status: 0 - lowlevel,1 - highlevel,2 - impulse-->
<flashMode opt="video,post,illegal"/>
<!--req flash work mode,described by bit: 0-work??1-not work, bit0 - video, bit1 - post,bit2 - illegal-->
<timeDelay min="" max=""/>
<!--req IO valid contious time, unit: us-->
<aheadTime min="" max=""/>
<!--req output IO ahead time,unit: us-->
<dutyRate min="0" max="40"/>
<!--req rate??[0,40%]-->
<detectBrightness opt="false,true"/>
<!--req auto detect the brightness of enabled flash: 0-false, 1-true-->
<brightnessThreld min="0" max="100"/>
<!--req brightness threld of flash, range:[0,100], flash when higher than threld-->
<flashLightEnable opt="false,true"/><!--req set flash time enable: 0-false, 1-true-->
<autoPlateBrightness opt="false,true"/>
<ioWorkMode opt="flashlight,polarizer"/>
<!--IO output port working mode: 0-Flash light, 1- Polarizer-->
</ITCIOoutParam>
<CameraSetUpCfg>
<setupHeight min="0" max="65535"/><!--req setup height/-->
<lensType opt="unKnown,8mm,12mm,16mm,25mm,35mm,50mm"/><!--req lens type/-->
<setupHeightUnit opt="M,CM"/>
<!--req 0~M,1~CM-->
<sceneDis min="0" max="65535"/><!--req the horizontal distance between the bottom of image and camera, unit:
cm-->
<videoDetCoefficient min="" max=""/><!--req video test coefficient[0,300]-->
<erectMethod opt="normalinstallation,sideinstallation"/><!--req, erect mode: 0- normal ??1- side -->
<horFieldAngle min="" max=""/>
<!-- The horizontal filed angle range [0??~360??]-->
<verFieldAngle min="" max=""/>
<!-- The vertical filed angle range [0??~360??]-->
</CameraSetUpCfg>
<PlcCfg>
<PLCEnable opt="false,true"/>
<!--req plate brightness compensation??default to enable????0-close??1-enable-->
<plateExpectBright min="0" max="100"/>
<!--req expectation brightness of plate,?? default to 50??, data range: [0, 100]-->
<brightChangeEnable opt="false,true"/>
<!--req illumination variation??default to enable????0-close??1-enable -->
<brightChangeThreld min="0" max="100"/>
<!--req brightness change threld ?? default to 50????data range: [0, 100]-->
<tradeOffFlash opt="false,true"/>
<!--req whether consider influence of flash: 0 - no; 1 - yes(default), when use the flash compensation, 1- weaken
the enhancement effect of flash brightness, 0 - no -->
<correctFactor min="0" max="100"/>
<!--req correction factor, data range: [0,100], default it to 50 (restore the default value when swicth
tradeoff_flash?? -->
275
Device Network SDK (ANPR) Developer Guide
<loopStatsEn opt="false,true"/>
<!--req brightness of coil, described by bit: 0- No statistical??1- statistical-->
<PLCBrightOffSet min="0" max="100"/>
<!--req sensitivity of plate brightness compensation(vitual coil mode valid only)??data range: 1- 100-->
</PlcCfg>
<CabinetAlarmParamCfg>
<supportCabinetNum min="0" max="8"/>
<cabinetNameLen min="0" max="32"/>
<associateIO opt="1,2,3,4,0xff"/>
<!--req 1-4??0xff?? 1-4: IO channel, 0xff- disable-->
<cabinetState opt="lowlevel,hightlevel"/>
<!--req 0- lowlevel, 1- highlevel-->
<alarmIntervalTime min="1" max="60"/>
<!--req data range: 1-60??uint: s -->
</CabinetAlarmParamCfg>
<ExceptionAlarmITC>
<exceptionType opt="diskError,nicBroken,ipConflict,sensors,signalDetector"/>
<alarmHandleType opt="monitor,audio,center,alarmout,picture,wirelesslight,uploadftp"/><!--req,
handle ,picture: capture and send mail-->
</ExceptionAlarmITC>
<ICRCFG>
<autoCtrlTime>4</autoCtrlTime>
<ICRPreset>2</ICRPreset>
<switchType opt="no,auto,manual,time,algorithmAuto"/>
<!--0 ~ Not switch, 1- Auto switch, 2~Manually switch,3~Scheduling switch??4~Auto-arithmetic-->
<AlgorithmAutoSwitch>
<detThreshold min="" max="" def=""/><!--Check the threshold, range[0~100], default:58-->
<unBrightnessThreshold min="" max="" def=""/><!--Abnormal brightness, range[0~255],default:12 -->
</AlgorithmAutoSwitch>
</ICRCFG>
<ITCFTP>
<ItcFtpTypeCond>
<workMode opt="ftp1,ftp2"/><!--req 0-FTP1(main FTP)??1-FTP2( backupFTP)-->
</ItcFtpTypeCond>
<ItcFtpCfg>
<enableFtp opt="true,false"/><!--req 0-false,1-true-->
<addressType opt="ipaddress,domainname"/><!--req 0- actual ipv4 ipv6 address, 1-domain-->
<ftpPort min="" max=""/><!--req ftp port range-->
<domainLen min="" max=""/><!--req domain length-->
<userNameLen min="" max=""/><!--req user name length-->
<passwordLen min="" max=""/><!--req password length-->
<dirLevel opt="rootdirectory,parentdirectory,childdirectory,threedirectory,fourdirectory"/>
<!--req 0 = don't use directory??save in the root directory,1 = use level 1 directory, 2= use level 2 directory, 3 =
use level 3 directory, 4=use level 4 directory-->
<uploadDataType opt="all,post,illegal"/><!--req 0-all,1- post,2-illegal(default to select all when use single FTP,
select post when use double FTP)-->
<itemOrder
opt="devname,devno,devip,channelname,channelno,time,cardno,plateno,paltecolor,laneno,carspeed,picnumber,
carnumber,speedlimit,illegalcode,crossnumber,directionnumber"/>
276
Device Network SDK (ANPR) Developer Guide
</ITCFTP>
<GPSDATACFG>
<gpsDataMode opt="auto,manual"/>
<!--Getting GPS data, 0-Auto??1-Manual-->
<longitudeType opt="east,west"/><!--Longitude: 0- East longitude??1-West longitude-->
<latitudeType opt="north,south"/><!--latitude: 0-South latitude??1-North latitude-->
<Longitude>
<degree min="0" max="180"/>
<minute min="0" max="60"/>
<sec min="0" max="60"/>
</Longitude>
<Latitude>
<degree min="0" max="180"/>
<minute min="0" max="60"/>
<sec min="0" max="60"/>
</Latitude>
</GPSDATACFG>
</ITCAbility>
<ITSAbility>
<cameraAmount>
<!--req, xs:integer, the maximum number of supported cameras-->
</cameraAmount>
<storeAmount>
<!--req, xs:integer, the maximum amount of supported data storage-->
</storeAmount>
<ImageCombine>
<enabled>true</enabled>
277
Device Network SDK (ANPR) Developer Guide
278
Device Network SDK (ANPR) Developer Guide
</mode1>
<mode2>
<!--opt, the character overlay on the picture of ITS or camera of ITS, no this node if not support-->
<overlapType
opt="monitor,site,roadNum,instrumentNum,directionNum,directionDes,laneNum,laneDes,capTime,capTimeMilli,plate
,carColor,carLength,carType,carBrand,speed,speedRatio,speedLimit,illegalDes,redStart,redStop,redOnTime,securityCod
e,capCode"/>
<!--opt, monitoring site, location, intersection ID, device ID, direction ID, direction description, lane ID, lane
description,
the time of capturing, the time of capturing(millisecond), license plate number, color of vehicle, length of vehicle,
vehicle type,
vehicle brands, speed, overspeed ratio, speed limit sign, violation information, the starting time of red light, the
ending time of
red light, the time that the red light has been lighted, security code, capturing ID-->
<itemLength min="0" max=""/>
<!--opt, length of character overlay-->
<changeLineNum min="0" max="10"/>
<!--opt, the number of line breaks-->
<spaceNum min="0" max="255"/>
<!--opt, the number of spaces-->
<linePercent min="0" max="100"/>
<!--opt, percentage of overlay line-->
<itemsStlye opt="horizontal,vertical"/>
<!--opt, overlay style: horizontal, vertical-->
<startPosTop min="0" max="2448"/>
<!--opt, the upper coordinate of starting point-->
<startPosLeft min="0" max="2448"/>
<!--opt, the left coordinate of starting point-->
<charStyle opt="SongTi,WeiTi"/>
<!--opt, font type: standard typeface of Chinese, typeface of Wei-->
<charSize opt="16*16,32*32,48*48,64*64"/>
<!--req, font size: 0-32*32(Chinese)/16*32(English), 1-64*64(Chinese)/32*64(English), 2-48*48 -->
<charInterval min="0" max="16"/>
<!--opt, character spacing-->
<ForeClorRGB>
<enabled>
true</enabled>
<!--opt, whether it supports to adjust RGB value of foreground color, no this node if not support-->
</ForeClorRGB>
<BackClorRGB>
<enabled>
true</enabled>
<!--opt, whether it supports to adjust RGB value of background color, no this node if not support-->
</BackClorRGB>
<ColorSelfAdapt>
<enabled>
true</enabled>
<!--opt, whether the color is adaptive, no this node if not support-->
</ColorSelfAdapt>
</mode2>
</imageOverlayString>
<TPSAlarm>
279
Device Network SDK (ANPR) Developer Guide
<!--req, whether it supports uploading information of traffic counting, no this node if not support-->
<UploadType1>
<enabled>
true</enabled>
<!--req, it supports the uploading mode no.2 (it supports the uploading mode no.2(that is, the type supported
by ITS, COMM_ITS_TRAFFIC_COLLECT of listening mode), no this node if not support-->
</UploadType1>
<UploadType2>
<enabled>
true</enabled>
<!--req, it supports the uploading mode no.2 (that is, the type supported by intelligent traffic camera,
COMM_ITS_TRAFFIC_COLLECT of arming mode,no this node if not support-->
</UploadType2>
</TPSAlarm>
<CameraSetup>
<!--req, it supports camera mounting configuration, no this node if not support-->
<enabled>
true</enabled>
</CameraSetup>
<!--req,park project -->
<LampCtrlInfo>
<lampCtrlMode opt="inlayLamp,externalLamp"/>
<!--req, lamp control mode??1-internal lamp??2-external lamp-->
<ctrlChannelIndex min="" max=""/>
<!--req alternate control channel number-->
<inlayLampCtrlMode>
<!--req internal lamp control mode -->
<lampStateCtrlNum min="" max=""/>
<!--req range of park space supported-->
<parkInlayInfo>
<enable opt="false,true"/>
<!--req,whether enable, true-enable, false-disable-->
<flicker opt="false,true"/>
<!--req,whether flash, true-flash??false- no flash-->
<lampColor opt="close,red,green,yellow,blue,magenta,cyan,white"/>
<!--req 0- none 1-red 2-green 3-yellow 4-blue 5-pink 6-cyan 7-white-->
</parkInlayInfo>
</inlayLampCtrlMode>
<externalLampCtrlMode>
<!--req external lamp control mode -->
<maxParkNum min="" max=""/>
<!--req park space number-->
<parkInfoType opt="normalParkIOstate,normalNoParkIOstate,specialParkIOstate,noSpecialParkIOstate"/>
<parkExternalSubinfo>
<enable opt="false,true"/>
<!--req,whether enable, true-enable??false-disable-->
<flicker opt="false,true"/>
<!--req,whether flash, true-flash??false-no flash-->
<IOstate opt="lowLevel,hightLevel"/>
<!--req,level, 0-low level??1-high level(valid external lamp)-->
</parkExternalSubinfo>
</externalLampCtrlMode>
280
Device Network SDK (ANPR) Developer Guide
</LampCtrlInfo>
<parkSpaceAttributeParam>
<maxParkNum min="" max=""/>
<!--req park number-->
<parkSpaceInfo>
<parkSpaceAttribute opt="normalPack,specialPack"/>
<!-- 0~normal pack 1~special pack-->
</parkSpaceInfo>
</parkSpaceAttributeParam>
<lampExternalCfg>
<enable opt="false,true"/>
<!--req,whethe enable, true-enable??false-disable-->
<lampState>
<flicker opt="false,true"/>
<!--req,whether flash, true-flash??false-no flash-->
<IONo opt="IO1,IO2,IO3"/>
<!--req 1~IO1,2~IO2,4~IO3 -->
</lampState>
</lampExternalCfg>
<compelCaptureCfg>
<parkIndex opt="parkPlace1,parkPlace2,parkPlace3,parkPlace4"/>
<!-- park number from left to right 1,2,3,4-->
</compelCaptureCfg>
<externalControlAlarm>
<lampState>
<flicker opt="false,true"/>
<!--req,whether flash, true-flash??false- no flash-->
<IONo opt="IO1,IO2,IO3"/>
<!--req 1~IO1,2~IO2,4~IO3 -->
</lampState>
<externalBeginTime>true</externalBeginTime>
<!--req whether support external begin time uploading -->
</externalControlAlarm>
<ManualSnap>
<!-- req, 3.7 added-->
<osdEnable>true</osdEnable>
<!-- req, capture OSD supports force closing-->
<laneNo min="1" man="6" />
<!-- req, vehicle lane No.-->
</ManualSnap>
</ITSAbility>
</ITDeviceAbility>
Example
Enter an example to illustrate your reference here (optional).
281
Device Network SDK (ANPR) Developer Guide
B.9 XML_LPListAuditSearchDescription
LPListAuditSearchDescription message in XML format
<LPListAuditSearchDescription version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<searchID><!--req, xs: string, search ID, which is used to check whether the current search requester is the same as
the previous one. If they are the same, the search record will be stored in the device to speed up the next search--></
searchID>
<searchResultPosition><!--req, xs: integer, the end position of search result in result list--></searchResultPosition>
<maxResults><!--req, xs: integer, the maximum number of results obtained by this search. Up to 2000 results can be
obtained by each search--></maxResults>
<type><!--optional, xs:string, license plate type: "blackList" (license plate in blocklist), "whitelist" (license plate in
allowlist), "allVehicleList" (license plate in all lists), "otherVehicleList" (license plate in other lists)--></type>
<LicensePlate><!--optional, xs:string, license plate number, fuzzy search is supported--></LicensePlate>
<cardNo><!--optional, xs:string, card No.--></cardNo>
<cardID><!--optional, xs:sring, card ID (Wiegand protocol), the maximum string size is 9 bytes--></cardID>
</LPListAuditSearchDescription>
B.10 XML_LPListAuditSearchResult
LPListAuditSearchResult message in XML format
<LPListAuditSearchResult version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<searchID><!--req, xs: string--></searchID>
<responseStatus></responseStatus>
<responseStatusStrg></responseStatusStrg>
<numOfMatches><!--req, xs: integer--></numOfMatches>
<totalMatches><!--req, xs: integer--></totalMatches>
<LicensePlateInfoList>
<LicensePlateInfo>
<id><!--req, xs: string --></id>
<LicensePlate><!--opt, xs: string--></LicensePlate>
<type><!--opt, xs: string, "blackList,whitelist,allVehicleList,otherVehicleList"--></type>
<createTime><!--opt, xs: string, time in ISO8601 format--></createTime>
<direction><!--opt, xs: string, "forward,reverse,unknown"--></direction>
<laneNo><!--opt, xs: integer, lane No.--></laneNo>
<plateCategory><!--optional, xs:string, license plate type--></plateCategory>
<country><!--optional, xs:string, country/region--></country>
<area><!--optional, xs:integer, area--></area>
<effectiveTime><!--optional, xs:date, effective date of the blocklist and allowlist--></effectiveTime>
<countryIndex><!--optional, xs:integer, country/region index--></countryIndex>
<cardID><!--optional, xs:string, card ID (Wiegand protocol), the maximum string size is 9 bytes--></cardID>
<effectiveDateTime><!--optional, xs:datetime, effective date and time of the blocklist and allowlist--></
effectiveDateTime>
<effectiveStartDate><!--optional, xs:string, start date of the effective period--></effectiveStartDate>
</LicensePlateInfo>
</LicensePlateInfoList>
</LPListAuditSearchResult>
282
Device Network SDK (ANPR) Developer Guide
B.11 XML_ResponseStatus
XML message about response status
<?xml version="1.0" encoding="utf-8"?>
<ResponseStatus version="2.0" xmlns="http://www.std-cgi.org/ver20/XMLSchema">
<requestURL>
<!--required, read-only, xs:string, request URL-->
</requestURL>
<statusCode>
<!--required, read-only, xs:integer, status code: 0,1-OK, 2-Device Busy, 3-Device Error, 4-Invalid Operation, 5-Invalid
XML Format, 6-Invalid XML Content, 7-Reboot Required, 9-Additional Error-->
</statusCode>
<statusString>
<!--required, read-only, xs:string, status description: OK, Device Busy, Device Error, Invalid Operation, Invalid XML
Format, Invalid XML Content, Reboot, Additional Error-->
</statusString>
<subStatusCode>
<!--required, read-only, xs:string, describe the error reason in detail-->
</subStatusCode>
<MErrCode>
<!--optional, xs:string, error code categorized by functional modules, e.g., 0x12345678-->
</MErrCode>
<MErrDevSelfEx>
<!--optional, xs:string, extension field of MErrCode. It is used to define the custom error code, which is categorized
by functional modules-->
</MErrDevSelfEx>
</ResponseStatus>
B.12 XML_SubscribeEvent
SubscribeEvent message in XML format
<SubscribeEvent version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema" >
<heartbeat>
<!--optional, xs:integer, heartbeat interval, unit: second, the default value is 30s-->
</heartbeat>
<eventMode>
<!--required, xs:string, "all"-upload all alarms/events, "list"-upload specified alarm/event-->
</eventMode>
<EventList>
<Event><!--uploading mode of specified alarm/event, this node exists only when eventMode is "list"-->
<type>
<!--required, xs:string, alarm/event types, which are obtained from the capability, refer to Alarm/Event Types for
Subscription for its values-->
</type>
<minorAlarm>
<!--opt, xs:string, minor alarm type: "0x400,0x401,0x402,0x403", see details in Access Control Event Type. This
node is required when type is "AccessControllerEvent"-->
283
Device Network SDK (ANPR) Developer Guide
</minorAlarm>
<minorException>
<!--opt, xs:string, minor exception type: "0x400,0x401,0x402,0x403", see details in Access Control Event Type.
This node is required when type is "AccessControllerEvent"-->
</minorException>
<minorOperation>
<!--opt, xs:string, minor operation type: "0x400,0x401,0x402,0x403", see details in Access Control Event Type.
This node is required when type is "AccessControllerEvent"-->
</minorOperation>
<minorEvent>
<!--opt, xs:string, minor event type: "0x01,0x02,0x03,0x04", see details in Access Control Event Type. This node is
required when type is "AccessControllerEvent"-->
</minorEvent>
<pictureURLType>
<!--opt, xs:string, alarm picture format: "binary"-binary, "localURL"-device local URL, "cloudStorageURL"-cloud
storage URL-->
</pictureURLType>
</Event>
</EventList>
<channels>
<!--optional, xs:string, event linked channel information, and multiple channels can be linked, each channel is
separated by comma, e.g., "1,2,3,4…"-->
</channels>
<channels>
<!--optional, xs:string, specify channels (each channel is separated by comma, e.g., "1,2,3,4…") to be armed, this
node does not exist if you want to arm all channels, and if this node exists, the sub node <channels> in the node
<Event> is invalid-->
</channels>
<identityKey max="64"/>
<!--opt, xs: string, interaction command of subscription, supports subscribing comparison results of face picture
library (importing with this command), the maximum length is 64-->
</SubscribeEvent>
B.13 XML_TrafficChannelCap
Traffic channel capability message in XML format
<TrafficChannelCap version="1.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<deviceTypeSupport>
<!--optional, xs: integer, device type: 0-video monitoring, 1-loop detection, 2-video analysis, 3-reserved, 4-video
analysis (event + traffic enforcement + traffic data collection), 5-video analysis + capture (event + traffic enforcement +
traffic data collection), 6-video structurization, 7-speed dome for dynamic tracking and capture, 8-speed dome for non-
dynamic tracking and capture-->
</deviceTypeSupport>
<isPTZSupport><!--optional, xs:boolean, whether it supports configuring PTZ type, PTZ address, PTZ control speed,
and zooming speed--><isPTZSupport>
<isEvidenceGettingSupport>
<!--optional, xs: boolean, whether it supports violation enforcement, setting scenes, and scene auto-switch-->
</isEvidenceGettingSupport>
<isBasicSupport>
284
Device Network SDK (ANPR) Developer Guide
285
Device Network SDK (ANPR) Developer Guide
</videoEvidenceTypeSupport>
<isRecordParamSupport>
<!--optional, xs: boolean, whether it supports setting recording parameters-->
</isRecordParamSupport>
<AIDEventSupport opt="abandonedObject, pedestrian, congestion, roadBlock, construction, trafficAccident,
fogDetection, wrongDirection, illegalParking, SSharpDriving, lowSpeed, dragRacing">
<!--optional, xs: string, supported traffic incident type: "abandonedObject"-objects dropped down, "pedestrian"-
pedestrian, "congestion"-congestion, "roadBlock"-roadblock, "construction"-construction, "trafficAccident"-traffic
accident, "fogDetection"-fog, "wrongDirection"-wrong-way driving, "illegalParking"-illegal parking, "SSharpDriving"-
slalom driving, "lowSpeed"-driving in low speed, "dragRacing"-street racing-->
</AIDEventSupport>
<TFSEventSupport opt="illegalParking, wrongDirection, crossLane, laneChange, vehicleExist, turnRound,
parallelParking, notKeepDistance, notSlowZebraCrossing, overtakeRightSide, lowSpeed, dragRacing,
changeLaneContinuously, SSharpDriving, largeVehicleOccupyLine, jamCrossLine">
<!--optional, xs: string, supported enforcement event type: "illegalParking"-illegal parking, "wrongDirection"-wrong-
way driving, "crossLane"-driving on the lane line, "laneChange"-illegal lane change, "vehicleExist"-motor vehicle on
non-motor vehicle lane, "turnRound"-illegal U-turn, "parallelParking"-parallel parking, "notKeepDistance"-not keeping
vehicle distance, "notSlowZebraCrossing"-not slowing down at zebra corssing, "overtakeRightSide"-overtaking on the
right, "lowSpeed"-driving in low speed, "dragRacing"-street racing, "changeLaneContinuously"-continuous lane
change, "SSharpDriving"-slalom driving, "largeVehicleOccupyLine"-lane occupation by large-sized vehicle,
"jamCrossLine"-queue jumping-->
</TFSEventSupport>
<isVehicleStatisticsSupport>
<!--optional, xs: boolean, whether it supports setting parameters for traffic data collection-->
</isVehicleStatisticsSupport>
<isLaneRuleSupport>
<!--optional, xs: boolean, whether it supports setting lane rules-->
</isLaneRuleSupport>
<isSupportPlateListEvidence>
<!--optional, xs: boolean, whether it supports setting parameters for blocklist and allowlist ANPR enforcement-->
</isSupportPlateListEvidence>
<isSupportMixedTargetDetection>
<!--optional, xs: boolean, whether it supports multi-target-type detection-->
</isSupportMixedTargetDetection>
<isSupportVideoOverlays>
<!--optional, xs: boolean, whether it supports overlaying information on video-->
</isSupportVideoOverlays>
<isSupportAddrInfo>
<!--optional, xs:boolean, whether it supports overlaying address information-->
</isSupportAddrInfo>
<VehiclePositionControl><!--optional, whether it supports vehicle direction control-->
<license min="0" max="16"><!--required, xs:string, license plate number--></license>
<intervalTime min="0" max="65535" def="1"><!--required, xs:integer, upload interval, unit: s, by default it is 1--></
intervalTime>
</VehiclePositionControl>
<isSupportLicensePlateExposure><!--optional, xs:boolean, whether it supports license plate exposure, return "true" if
it supports, and this node will not be returned if the device does not supports this function--></
isSupportLicensePlateExposure>
<isSupportFiltration><!--optional, xs:boolean, whether it supports filtering duplicated license plate, return "true" if it
supports, and this node will not be returned if the device does not support the function--></isSupportFiltration>
</TrafficChannelCap>
286
Device Network SDK (ANPR) Developer Guide
Example
TrafficChannelCap Message Example
<TrafficChannelCap version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<isEvidenceGettingSupport>false</isEvidenceGettingSupport>
<isBasicSupport>true</isBasicSupport>
<isImageMergeSupport>true</isImageMergeSupport>
<isOverlapSupport>true</isOverlapSupport>
<isEdfAlgSupport>true</isEdfAlgSupport>
<isEdfManualItsCapSupport>false</isEdfManualItsCapSupport>
<isEDFRemoteHostSupport>true</isEDFRemoteHostSupport>
<isANRSupport>true</isANRSupport>
<isvoiceTriggerSupport>false</isvoiceTriggerSupport>
<uploadDataTypesSupport></uploadDataTypesSupport>
<aidTypeSupport>wrongDirection,turnRound,vehicleexist,congestion,crossLane,laneChange,pedestrian,roadBlock,aba
ndonedObject,construction,trafficAccident,fogDetection</aidTypeSupport>
<isIntellMonitorSupport>false</isIntellMonitorSupport>
<isVCRSupport>false</isVCRSupport>
<isEdfManualTrackSupport>false</isEdfManualTrackSupport>
<videoEvidenceTypeSupport></videoEvidenceTypeSupport>
<TFSEventSupport>wrongDirection,turnRound,vehicleexist,crossLane,laneChange</TFSEventSupport>
<AIDEventSupport>congestion,pedestrian,roadBlock,abandonedObject,construction,trafficAccident,fogDetection</
AIDEventSupport>
<isVehicleStatisticsSupport>true</isVehicleStatisticsSupport>
<isLaneRuleSupport>true</isLaneRuleSupport>
<isSupportPlateListEvidence>true</isSupportPlateListEvidence>
</TrafficChannelCap>
287
Device Network SDK (ANPR) Developer Guide
Appendix C. Appendixes
General Errors
288
Device Network SDK (ANPR) Developer Guide
289
Device Network SDK (ANPR) Developer Guide
290
Device Network SDK (ANPR) Developer Guide
291
Device Network SDK (ANPR) Developer Guide
292
Device Network SDK (ANPR) Developer Guide
293
Device Network SDK (ANPR) Developer Guide
294
Device Network SDK (ANPR) Developer Guide
295
Device Network SDK (ANPR) Developer Guide
296
Device Network SDK (ANPR) Developer Guide
297
Device Network SDK (ANPR) Developer Guide
298
Device Network SDK (ANPR) Developer Guide
299
Device Network SDK (ANPR) Developer Guide
300
Device Network SDK (ANPR) Developer Guide
301
Device Network SDK (ANPR) Developer Guide
302
Device Network SDK (ANPR) Developer Guide
303
Device Network SDK (ANPR) Developer Guide
304
Device Network SDK (ANPR) Developer Guide
305
Device Network SDK (ANPR) Developer Guide
306
Device Network SDK (ANPR) Developer Guide
307
Device Network SDK (ANPR) Developer Guide
308
Device Network SDK (ANPR) Developer Guide
309
Device Network SDK (ANPR) Developer Guide
310
Device Network SDK (ANPR) Developer Guide
311
Device Network SDK (ANPR) Developer Guide
312
Device Network SDK (ANPR) Developer Guide
313
Device Network SDK (ANPR) Developer Guide
314
Device Network SDK (ANPR) Developer Guide
315
Device Network SDK (ANPR) Developer Guide
316
Device Network SDK (ANPR) Developer Guide
317
Device Network SDK (ANPR) Developer Guide
318
Device Network SDK (ANPR) Developer Guide
319
Device Network SDK (ANPR) Developer Guide
320
Device Network SDK (ANPR) Developer Guide
321
Device Network SDK (ANPR) Developer Guide
322
Device Network SDK (ANPR) Developer Guide
323
Device Network SDK (ANPR) Developer Guide
324
Device Network SDK (ANPR) Developer Guide
325
Device Network SDK (ANPR) Developer Guide
326
Device Network SDK (ANPR) Developer Guide
327
Device Network SDK (ANPR) Developer Guide
328
Device Network SDK (ANPR) Developer Guide
329
Device Network SDK (ANPR) Developer Guide
330
Device Network SDK (ANPR) Developer Guide
StatusCode=1
331
Device Network SDK (ANPR) Developer Guide
StatusCode=2
StatusCode=3
332
Device Network SDK (ANPR) Developer Guide
333
Device Network SDK (ANPR) Developer Guide
334
Device Network SDK (ANPR) Developer Guide
335
Device Network SDK (ANPR) Developer Guide
StatusCode=4
336
Device Network SDK (ANPR) Developer Guide
337
Device Network SDK (ANPR) Developer Guide
338
Device Network SDK (ANPR) Developer Guide
339
Device Network SDK (ANPR) Developer Guide
340
Device Network SDK (ANPR) Developer Guide
341
Device Network SDK (ANPR) Developer Guide
342
Device Network SDK (ANPR) Developer Guide
343
Device Network SDK (ANPR) Developer Guide
344
Device Network SDK (ANPR) Developer Guide
345
Device Network SDK (ANPR) Developer Guide
346
Device Network SDK (ANPR) Developer Guide
347
Device Network SDK (ANPR) Developer Guide
348
Device Network SDK (ANPR) Developer Guide
349
Device Network SDK (ANPR) Developer Guide
350
Device Network SDK (ANPR) Developer Guide
351
Device Network SDK (ANPR) Developer Guide
352
Device Network SDK (ANPR) Developer Guide
353
Device Network SDK (ANPR) Developer Guide
354
Device Network SDK (ANPR) Developer Guide
355
Device Network SDK (ANPR) Developer Guide
356
Device Network SDK (ANPR) Developer Guide
357
Device Network SDK (ANPR) Developer Guide
358
Device Network SDK (ANPR) Developer Guide
359
Device Network SDK (ANPR) Developer Guide
360
Device Network SDK (ANPR) Developer Guide
361
Device Network SDK (ANPR) Developer Guide
StatusCode=5
StatusCode=6
362
Device Network SDK (ANPR) Developer Guide
363
Device Network SDK (ANPR) Developer Guide
364
Device Network SDK (ANPR) Developer Guide
365
Device Network SDK (ANPR) Developer Guide
366
Device Network SDK (ANPR) Developer Guide
367
Device Network SDK (ANPR) Developer Guide
368
Device Network SDK (ANPR) Developer Guide
StatusCode=7
369
Device Network SDK (ANPR) Developer Guide
370
Device Network SDK (ANPR) Developer Guide
is not allowed.
● Editing your own level or
371
Device Network SDK (ANPR) Developer Guide
372
Device Network SDK (ANPR) Developer Guide
373
Device Network SDK (ANPR) Developer Guide
374
Device Network SDK (ANPR) Developer Guide
375
Device Network SDK (ANPR) Developer Guide
376
Device Network SDK (ANPR) Developer Guide
377
Device Network SDK (ANPR) Developer Guide
378
Device Network SDK (ANPR) Developer Guide
379
Device Network SDK (ANPR) Developer Guide
380
Device Network SDK (ANPR) Developer Guide
381
Device Network SDK (ANPR) Developer Guide
382
Device Network SDK (ANPR) Developer Guide
383
Device Network SDK (ANPR) Developer Guide
configured.
● Node value exceeds the
configured.
● Node value exceeds the
384
Device Network SDK (ANPR) Developer Guide
385
Device Network SDK (ANPR) Developer Guide
386
Device Network SDK (ANPR) Developer Guide
387
Device Network SDK (ANPR) Developer Guide
388
Device Network SDK (ANPR) Developer Guide
389
Device Network SDK (ANPR) Developer Guide
390
Device Network SDK (ANPR) Developer Guide
391
Device Network SDK (ANPR) Developer Guide
392
Device Network SDK (ANPR) Developer Guide
393
Device Network SDK (ANPR) Developer Guide
394
Device Network SDK (ANPR) Developer Guide
395
Device Network SDK (ANPR) Developer Guide
396