Device Network SDK (Queue Management)

Device Network SDK (Queue Management)
Developer Guide
Device Network SDK (Queue Management) 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
Contents
Chapter 1 Overview .................................................................................................................... 1
1.1 Introduction ........................................................................................................................... 1
1.2 Update History ....................................................................................................................... 2
Chapter 2 Typical Applications .................................................................................................... 4
2.1 Alarm and Event Receiving ..................................................................................................... 4
2.1.1 Configure Queue Management Alarm .......................................................................... 4
2.1.2 Receive Alarm/Event in Arming Mode .......................................................................... 8
2.1.3 Receive Alarm/Event in Listening Mode ..................................................................... 11
2.2 Search Queue Management Report or Data ........................................................................ 14
Chapter 3 API Reference ........................................................................................................... 20
3.1 NET_DVR_Cleanup ............................................................................................................... 20
3.2 NET_DVR_GetErrorMsg ....................................................................................................... 20
3.3 NET_DVR_GetLastError ........................................................................................................ 21
3.4 NET_DVR_Init ....................................................................................................................... 21
3.5 NET_DVR_Login_V40 ........................................................................................................... 21
3.5.1 fLoginResultCallBack ................................................................................................... 22
3.6 NET_DVR_Logout ................................................................................................................. 23
3.7 NET_DVR_SetSDKInitCfg ...................................................................................................... 23
3.8 NET_DVR_GetSTDAbility ...................................................................................................... 25
3.9 NET_DVR_GetSTDConfig ...................................................................................................... 25
3.10 NET_DVR_MIME_UNIT ...................................................................................................... 26
3.11 NET_DVR_SetSTDConfig .................................................................................................... 27
3.12 NET_DVR_STDXMLConfig ................................................................................................... 28
3.13 NET_DVR_CloseAlarmChan_V30 ....................................................................................... 29
3.14 NET_DVR_GetDVRConfig ................................................................................................... 29
3.15 NET_DVR_SetDVRConfig .................................................................................................... 31
ii
3.16 NET_DVR_SetDVRMessageCallBack_V50 .......................................................................... 32

3.16.1 MSGCallBack ............................................................................................................. 39
3.17 NET_DVR_SetupAlarmChan_V50 ....................................................................................... 40
3.18 NET_DVR_StartListen_V30 ................................................................................................. 40
3.19 NET_DVR_StopListen_V30 ................................................................................................. 41
Appendix A. Data Structure ...................................................................................................... 83
A.1 DATE_TIME .......................................................................................................................... 83
A.2 NET_DVR_DEVICEINFO_V30 ................................................................................................ 83
A.3 NET_DVR_DEVICEINFO_V40 ................................................................................................ 87
A.4 NET_DVR_INIT_CFG_ABILITY ............................................................................................... 90
A.5 NET_DVR_LOCAL_SDK_PATH ............................................................................................... 91
A.6 NET_DVR_USER_LOGIN_INFO ............................................................................................. 91
A.7 NET_SDK_CALLBACK_STATUS_NORMAL .............................................................................. 92
A.8 NET_VCA_RECT .................................................................................................................... 93
A.9 NET_DVR_CRUISECHAN_INFO ............................................................................................. 93
A.10 NET_DVR_EVENT_SCHEDULE ............................................................................................ 94
A.11 NET_DVR_EVENT_TRIGGER ............................................................................................... 94
A.12 NET_DVR_HANDLEEXCEPTION_V41 .................................................................................. 95
A.13 NET_DVR_MIME_UNIT ...................................................................................................... 96
A.14 NET_DVR_PRESETCHAN_INFO ........................................................................................... 96
A.15 NET_DVR_PTZTRACKCHAN_INFO ...................................................................................... 97
A.16 NET_DVR_SCHEDTIME ....................................................................................................... 97
A.17 NET_DVR_STD_ABILITY ...................................................................................................... 97
A.18 NET_DVR_STD_CONFIG ..................................................................................................... 98
A.19 NET_DVR_XML_CONFIG_INPUT ........................................................................................ 99
A.20 NET_DVR_XML_CONFIG_OUTPUT .................................................................................. 100
A.21 NET_ALARM_CVR_SUBINFO_UNION .............................................................................. 101
A.22 NET_ALARM_RECORD_EXCEPTION ................................................................................. 101
iii
A.23 NET_ALARM_RECORDFILE_LOSS ..................................................................................... 102

A.24 NET_ALARM_RESOURCE_USAGE .................................................................................... 103
A.25 NET_ALARM_STREAM_EXCEPTION ................................................................................. 103
A.26 NET_DVR_ALARMER ........................................................................................................ 103
A.27 NET_DVR_ALARMINFO_DEV ........................................................................................... 104
A.28 NET_DVR_ALARMINFO_DEV_V40 ................................................................................... 105
A.29 NET_DVR_ALARMINFO_V30 ............................................................................................ 106
A.30 NET_DVR_ALARMINFO_V40 ............................................................................................ 107
A.31 NET_DVR_ALRAM_FIXED_HEADER ................................................................................. 108
A.32 NET_DVR_ALARM_ISAPI_INFO ........................................................................................ 112
A.33 NET_DVR_ALARM_ISAPI_PICDATA .................................................................................. 113
A.34 NET_DVR_ETHERNET_V30 ............................................................................................... 113
A.35 NET_DVR_IPADDR_UNION .............................................................................................. 114
A.36 NET_DVR_NETCFG_V50 ................................................................................................... 114
A.37 NET_DVR_PPPOECFG ....................................................................................................... 115
A.38 NET_DVR_SETUPALARM_PARAM_V50 ............................................................................ 116
A.39 NET_DVR_TIME ............................................................................................................... 119
A.40 NET_DVR_TIME_EX ......................................................................................................... 119
Chapter 4 Request URL ............................................................................................................. 43
4.1 /ISAPI/Intelligent/channels/<ID>/capabilities ...................................................................... 43
4.2 /ISAPI/Intelligent/channels/<ID>/personQueueDetection/capabilities?format=json ......... 43
4.3 /ISAPI/Intelligent/channels/<ID>/personQueueDetection/queueCountingFile?format=json
.................................................................................................................................................... 44
4.4 /ISAPI/Intelligent/channels/<ID>/personQueueDetection/queueCountingResult?
format=json ............................................................................................................................... 44
4.5 /ISAPI/Intelligent/channels/<ID>/personQueueDetection/queueTimeFile?format=json ... 45
4.6 /ISAPI/Intelligent/channels/<ID>/personQueueDetection/queueTimeResult?format=json
.................................................................................................................................................... 46
4.7 /ISAPI/Intelligent/channels/<ID>/personQueueDetection/rawDataFile?format=json ........ 46
iv
4.8 /ISAPI/Intelligent/channels/<ID>/personQueueDetection?format=json ............................. 47

Chapter 5 Request and Response Message ............................................................................... 48
5.1 JSON_EventNotificationAlert_Alarm/EventInfo ................................................................... 48
5.2 JSON_EventNotificationAlert_PeopleQueuingUpAlarmMsg ............................................... 48
5.3 JSON_EventNotificationAlert_RealTimeQueueManagementDataMsg ................................ 51
5.4 JSON_EventNotificationAlert_WaitingTimeDetectionAlarmMsg ......................................... 52
5.5 JSON_PersonQueueCountingDescription ............................................................................ 55
5.6 JSON_PersonQueueCountingFileResult ............................................................................... 56
5.7 JSON_PersonQueueCountingResult ..................................................................................... 57
5.8 JSON_PersonQueueDetectionInfo ....................................................................................... 58
5.9 JSON_PersonQueueDetectionInfoCap ................................................................................. 61
5.10 JSON_PersonQueueRawDataFileDescription ..................................................................... 65
5.11 JSON_PersonQueueRawDataFileResult ............................................................................. 66
5.12 JSON_PersonQueueTimeDescription ................................................................................. 67
5.13 JSON_PersonQueueTimeFileResult .................................................................................... 68
5.14 JSON_PersonQueueTimeResult ......................................................................................... 68
5.15 JSON_ResponseStatus ........................................................................................................ 71
5.16 XML_Cap_Schedule ........................................................................................................... 72
5.17 XML_EventNotificationAlert_AlarmEventInfo ................................................................... 73
5.18 XML_EventTriggersCap ...................................................................................................... 73
5.19 XML_EventTriggerCapType ................................................................................................ 76
5.20 XML_IntelliCap ................................................................................................................... 77
5.21 XML_ResponseStatus ......................................................................................................... 81
Appendix B. Appendixes ......................................................................................................... 121
B.1 Device Network SDK Errors ................................................................................................ 121
B.2 Response Codes of Text Protocol ....................................................................................... 164
v
Chapter 1 Overview
This manual provides the integration methods and flows based on HCNetSDK for queue
management applications.
1.1 Introduction
Queue management is applicable to analyze the queuing status of public places (e.g., market,
ticket office), it provides the functions of people queuing-up detection and waiting time detection.
You can configure these two kinds of alarms for receiving the alarm information in the third-party
platform or system, and search for the detection reports or data.
Figure 1-1 Queue Management Overall Flow

People Queuing-Up
The people queuing-up is to detect the queuing-up people amount in multiple rule regions. When
the queuing-up people amount is larger than the configured amount threshold, the alarm is
triggered and uploaded by the device. For example, if the configured queuing-up people amount
threshold is 6 in the Region 1 of the following figure, when the number of persons is larger than
or equal to 6, the alarm will be triggered and uploaded according to the configured uploading
time interval.
Figure 1-2 People Queuing-Up
Waiting Time Detection

The waiting time detection is to detect the waiting time duration of a target queuing-up person in
multiple rule regions. When the waiting time of a target person is longer than the configured time
duration threshold, the alarm will be triggered and uploaded by device. For example, if the
configured queuing-up duration threshold is 30 minutes in the Region 2 of the following figure,
1
when the queuing-up duration of target person A is longer than or equal to 30 minutes, the alarm
will be triggered and uploaded according to the configured uploading time interval.
Figure 1-3 Waiting Time Detection
1.2 Update History
Summary of Changes in Version 6.0.2.36_May, 2019

1. Extended queue management configuration capability message
JSON_PersonQueueDetectionInfoCap (related API: NET_DVR_STDXMLConfig ; related URL: /
ISAPI/Intelligent/channels/<ID>/personQueueDetection/capabilities?format=json ):
added a node "isSupportAlgParam" (whether supports configuring advanced parameters for
algorithm library);
added three sub nodes, i.e., "countTriggerType" (triggering type of people queuing-up alarm),
"maxAlarmCount" (maximum number of queuing-up persons to trigger alarm), and
"durationTime" (queuing-up status (number of queuing-up persons) keeping duration), to the
node "PersonQueueCounting" (people queuing-up parameters);
added a sub node "timeTriggerType" (triggering type of waiting time detection alarm) to the
node "PersonQueueTime" (waiting time detection parameters);
added a sub node "isSupportAverageTime" (whether supports calculating average waiting time
duration in people queuing-up statistics) to the node "WaitTimeListCap" (waiting time
information).
2. Extended configuration parameter message JSON_PersonQueueDetectionInfo of queue
management (related API: NET_DVR_STDXMLConfig ; related URL: /ISAPI/Intelligent/channels/
<ID>/personQueueDetection?format=json ):
added three sub nodes, i.e., "countTriggerType" (triggering type of people queuing-up alarm),
"maxAlarmCount" (maximum number of queuing-up persons to trigger alarm), and
"durationTime" (queuing-up status (number of queuing-up persons) keeping duration), to the
node "PersonQueueCounting" (people queuing-up parameters);
node "PersonQueueTime" (waiting time detection parameters).
3. Extended waiting time detection alarm message with binary picture data or picture URL ( ):
node "rule" (rule properties).
4. Extened people queuing-up alarm message with binary picture data or picture URL ( ):
2
added two sub nodes "countTriggerType" (triggering type of people queuing-up alarm) and
"durationTime" (queuing-up status (number of queuing-up persons) keeping duration) to the
node "rule" (rule properties).
Summary of Changes in Version 6.0.2.X_Mar., 2019

New document.
3
Chapter 2 Typical Applications
2.1 Alarm and Event Receiving

The alarm/event information from the device can be received in third-party platform or system
when the alarms are triggered or event occurred. Two modes are available for receiving alarms,
including arming mode and listening mode.
Arming Mode
The third-party platform connects to device automatically, when the alarm is triggered, the
platform sends alarm uploading command to the device, and then the device will upload the
alarm to the platform.
Listening Mode
When alarm is triggered, the device automatically uploads the alarm, and then the third-party
platform receives the uploaded alarm via the configured listening host (listening address and port
should be configured). This mode is applicable for multiple devices uploading alarm/event
information to one third-party platform without logging in to devices, and the restart of devices
will not affect the alarm/event uploading. But a device can only support the configuration of one
or two listening addresses and ports.
2.1.1 Configure Queue Management Alarm

Queue management alarm includes people queuing-up alarm, waiting time detection alarm, and
real-time queue management alarm. You can set the alarm parameters to trigger the people
queuing-up alarm when the queuing-up people amount in a region is larger than the configured
threshold, trigger the waiting time detection alarm when the waiting time of a queue stays a
certain length is longer than the configured threshold, and trigger real-time queue management
alarm when queuing-up people amount changed or waiting time duration is longer than threshold.
Before You Start
● Make sure you have called NET_DVR_Init to initialize the development environment.
● Make sure you have called NET_DVR_Login_V40 to log in to device.
4
Steps
Figure 2-1 Programming Flow of Configuring Queue Management Alarm
5
Note
The queue management parameters, alarm linkage actions, and arming schedules can be directly
configured by logging in to device via web browser.
1. Call NET_DVR_STDXMLConfig to pass through the request URL: GET /ISAPI/Intelligent/
channels/<ID>/capabilities for getting intelligent channel capability to check if the device
supports queue management.
The intelligent channel capability is returned in the message XML_IntelliCap by output pointer
(lpOutputParam).
If the node <isSupportPersonQueueDetection> is returned in the capability message, it
indicates that queue management function is supported and you can perform the following
steps.
Otherwise, this function is not supported, please end this task.
2. Optional: Call NET_DVR_STDXMLConfig to pass through the request URL: GET /ISAPI/
Intelligent/channels/<ID>/personQueueDetection/capabilities?format=json for getting the
queue management capability to check the supported configuration parameters.
The queue management capability is returned in the message
JSON_PersonQueueDetectionInfoCap by output pointer (lpOutputParam).
3. Optional: Call NET_DVR_STDXMLConfig to pass through the request URL: GET /ISAPI/
Intelligent/channels/<ID>/personQueueDetection?format=json for getting default or
configured queue management parameters for reference.
The queue management parameters are returned in the message
JSON_PersonQueueDetectionInfo by the output pointer (lpOutputParam).
4. Call NET_DVR_STDXMLConfig to pass through the request URL: PUT /ISAPI/Intelligent/
channels/<ID>/personQueueDetection?format=json and set the input pointer (lpInputParam)
to the message JSON_PersonQueueDetectionInfo for setting queue management parameters.
5. Configure linkage action for queue management alarm.
1) Call NET_DVR_GetSTDAbility with
NET_DVR_GET_EVENT_TRIGGERS_CAPABILITIES
(command No.: 3501) to get alarm linkage capability of device.
The alarm linkage capability is returned in the message XML_EventTriggersCap by the output
buffer (lpOutBuffer) in structure NET_DVR_STD_ABILITY .
2) Optional: Call NET_DVR_GetSTDConfig with
NET_DVR_GET_PERSONQUEUE_TRIGGER
(command No.: 4406) to get the default or configured linkage actions of queue management
alarm for reference.
The linkage actions are returned in the structure NET_DVR_EVENT_TRIGGER by the output
buffer (lpOutBuffer) in structure NET_DVR_STD_CONFIG .
3) Call NET_DVR_SetSTDConfig with
NET_DVR_SET_PERSONQUEUE_TRIGGER
6
(command No.: 4407), and then set condition buffer (lpCondBuffer) and input buffer
(lpInBuffer) in structure NET_DVR_STD_CONFIG to 4-byte channel No. and
NET_DVR_EVENT_TRIGGER , respectively, for setting the linkage actions of queue
management alarm.
Note
To receive alarms in arming mode via platform, the linkage action must be set to "center"
(upload to alarm center).
6. Configure arming schedule of queue management alarm.
1) Call NET_DVR_GetSTDAbility with
NET_DVR_GET_PERSONQUEUE_SCHEDULE_CAPABILITIES
(command No.: 4408) to get the arming schedule capability of queue management device.
The arming schedule capability is returned in the message XML_Cap_Schedule by the output
buffer (lpOutBuffer) of structure NET_DVR_STD_ABILITY .
2) Optional: Call NET_DVR_GetSTDConfig with
NET_DVR_GET_PERSONQUEUE_SCHEDULE
(command No.: 4409) and set condition buffer (lpCondBuffer) in structure
NET_DVR_STD_CONFIG to 4-byte channel No. for getting the default or configured arming
schedule of queue management for reference.
The arming schedule parameters are returned in the structure NET_DVR_EVENT_SCHEDULE
by the output buffer (lpOutBuffer) in structure NET_DVR_STD_CONFIG .
3) Call NET_DVR_SetSTDConfig with
NET_DVR_SET_PERSONQUEUE_SCHEDULE
(command No.: 4410), and then set condition buffer (lpCondBuffer) and input buffer
(lpInBuffer) in structure NET_DVR_STD_CONFIG to 4-byte channel No. and
NET_DVR_EVENT_SCHEDULE , respectively, for setting arming schedule of queue
management.
7. Optional: Set the uploading message type (lCommand) in alarm callback function to
"COMM_VCA_ALARM" (macro definition value: 0x4993) for receiving queue management
alarms, i.e., people queuing-up alarm, waiting time detection alarm, and real-time queue
management alarm, in arming mode (refer to Receive Alarm/Event in Arming Mode ) or
listening mode (refer to Receive Alarm/Event in Listening Mode ).
The people queuing-up alarm is uploaded in the message
JSON_EventNotificationAlert_PeopleQueuingUpAlarmMsg ; the waiting time detection alarm is
uploaded in the message JSON_EventNotificationAlert_WaitingTimeDetectionAlarmMsg ; and
the real-time queue management alarm is uploaded in the message
JSON_EventNotificationAlert_RealTimeQueueManagementDataMsg .
What to do next
Call NET_DVR_Logout and NET_DVR_Cleanup to log out from device and release the resources.
7
2.1.2 Receive Alarm/Event in Arming Mode

When the alarm is triggered or the event occurred, the secondarily developed third-party platform
can automatically connect and send alarm/event uploading command to the device, and then the
device uploads the alarm/event information to the platform for receiving.
Before You Start
● Make sure you have called NET_DVR_Login_V40 to log in to the device.
● Make sure you have configured the alarm/event parameters, refer to the typical alarm/event
configurations for details.

Steps
Figure 2-2 Programming Flow of Receiving Alarm/Event in Arming Mode

1. Call NET_DVR_SetDVRMessageCallBack_V50 to set callback function for returning alarm/event
information.
8
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
#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;
}
9
//Set alarm callback function

NET_DVR_SetDVRMessageCallBack_V50(0, MessageCallbackNo1, NULL);
//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;
char szSubscribe[1024] = {0};

//The following code is for alarm subscription (subscribe all)
memcpy(szSubscribe, "<SubscribeEvent version=\"2.0\" xmlns=\"http://www.isapi.org/ver20/XMLSchema\">\r
\n<eventMode>all</eventMode>\r\n", 1024);
LONG lHandle = -1;
if (0 == strlen(szSubscribe))
{
//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_Cleanup();
return;
}
//Log out
//Release resources
NET_DVR_Cleanup();
10
return;
}
What to do next
Call NET_DVR_Logout and NET_DVR_Cleanup to log out and release resources.
2.1.3 Receive Alarm/Event in Listening Mode

When alarm is triggered or event occurred, the device uploads the alarm/event information
automatically, so you can configure the listening address and port for listening and receiving the
alarm/event in the secondarily developed third-part platform.
Before You Start
● Make sure you have configured the alarm/event parameters, refer to the typical alarm/event
configurations for details.
11
Steps
Figure 2-3 Programming Flow of Receiving Alarm/Event in Listening Mode

1. Optional: Call NET_DVR_Login_V40 to log in to device.
2. Optional: Call NET_DVR_GetDVRConfig with "NET_DVR_GET_NETCFG_V50" (command No.:
1015) to get the existing listening configurations (i.e., listening address and port) for reference.
The listening parameters are retruned in the structure NET_DVR_NETCFG_V50 by the output
parameter pointer lpOutBuffer.
3. Call NET_DVR_SetDVRConfig with "NET_DVR_SET_NETCFG_V50" (command No.: 1016) and
specify the input parameter pointer lpInBuffer to the structure NET_DVR_NETCFG_V50 for
setting the listening address and port.
4. Call NET_DVR_StartListen_V30 to set callback function for returning alarm/event information
and start the listening.
12
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>
void main() {
//---------------------------------------
// Initialize
NET_DVR_Init();
//Set connection time and reconnection time
//---------------------------------------
// 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_Cleanup();
return;
}
Sleep(5000);
13
//Disable listening
if (!NET_DVR_StopListen_V30(lHandle))
{
printf("NET_DVR_StopListen_V30 error, %d\n", NET_DVR_GetLastError());
NET_DVR_Cleanup();
return;
}
//Log out
//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.
2.2 Search Queue Management Report or Data

When the queue management alarm is triggered and uploaded to third-party platform/system, you
can search for the reports of people queuing-up and waiting time detection, and get the reports in
different formats (i.e., report details and report URL). You can also directly get the file URL of
unprocessed data (raw data).
Search People Queuing-Up Report

Get Report Details
Call NET_DVR_STDXMLConfig to pass through the request URL: POST /ISAPI/Intelligent/
channels/<ID>/personQueueDetection/queueCountingResult?format=json .
The report details is returned in the message JSON_PersonQueueCountingResult by output
pointer (lpOutputParam).
Get Report URL
Call NET_DVR_STDXMLConfig to pass through the request URL: POST /ISAPI/Intelligent/
channels/<ID>/personQueueDetection/queueCountingFile?format=json and set the input
pointer (lpInputParam) to the message JSON_PersonQueueCountingDescription .
The report URL is returned in the message JSON_PersonQueueCountingFileResult by output
pointer (lpOutputParam). You can download the report from the URL.
Search Waiting Time Detection Report

Get Report Details
Call NET_DVR_STDXMLConfig to pass through the request URL: POST .
14
The report details is returned in the message JSON_PersonQueueTimeResult by output pointer

(lpOutputParam).
Get Report URL
Call NET_DVR_STDXMLConfig to pass through the request URL: POST and set the input pointer
(lpInputParam) to the message JSON_PersonQueueTimeDescription .
The report URL is returned in the message JSON_PersonQueueTimeFileResult by output pointer
(lpOutputParam). You can download the report from the URL.
Search Queue Management Raw Data
Figure 2-4 Interaction Process of Raw Data Search

As the raw data is paged, if you want to get all raw data, you should set search time period and
repeatedly call NET_DVR_STDXMLConfig to pass through the request URL: POST and set the input
pointer (lpInputParam) to the message JSON_PersonQueueRawDataFileDescription .
The searched raw data is returned in the message JSON_PersonQueueRawDataFileResult by
output pointer (lpOutputParam).
15
Note
● When setting search time period, the previous search end time returned by device should be
specified as the start time of next search.
● The raw data will be paged and returned by file URL, and the records are sorted from earliest to
latest in the file.
● Up to 4000 records can be returned after searching for once.
Example
Figure 2-5 Compare Queuing-Up People Amount for Different Regions
16
Figure 2-6 Compare Queuing-Up People Amount for Different Waiting Times
17
Figure 2-7 Compare Queuing-Up Duration for Different Regions
18
Figure 2-8 Compare Queuing-Up Duration for Different Queue Lengths
19
Chapter 3 API Reference
3.1 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.
3.2 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.
Remarks
You can call NET_DVR_GetLastError to get the error codes.
20
3.3 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.
3.4 NET_DVR_Init
Initialize the programming environment before calling other APIs.
API Definition
BOOL NET_DVR_Init(
);
Return Values
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
3.5 NET_DVR_Login_V40
Log in to the device (supports asynchronous login).
21
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
3.5.1 fLoginResultCallBack
22
Login Status Callback Function
Member Data Type Description

lUserID LONG User ID, which is returned by
NET_DVR_Login_V40 .
dwResult DWORD Login status: 0-asynchronously logging in failed,
1-asynchronously logged in.
lpDeviceInfo NET_DVR_DEVICEINFO Device information, such as serial No., channel,
_V40 capability, and so on.
pUser void* User data.
3.6 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
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 .
3.7 NET_DVR_SetSDKInitCfg
Set initialization parameters.
API Parameters
BOOL NET_DVR_SetSDKInitCfg(
NET_SDK_INIT_CFG_TYPE enumType,
23
void* const lpInBuff

);
Parameters
enumType
[IN] Initialization parameter type. Different type values correspond to different parameters, see
details in the table below.
Table 3-1 NET_SDK_INIT_CFG_TYPE

enumType Value Description lpInBuff
NET_SDK_INIT_CFG_ 1 Capability supported by NET_DVR_INIT_CFG_A
ABILITY SDK. BILITY
NET_SDK_INIT_CFG_ 2 Set loading path for NET_DVR_LOCAL_SDK
SDK_PATH component libraries _PATH
(supported by both
Linux and Windows
system).
NET_SDK_INIT_CFG_ 3 Set path (including Path in string format,
LIBEAY_PATH library name) for e.g., C:\\libeay32.dll.
libeay32.dll (Windows),
libcrypto.so (Linux),
and libcrypto.dylib
(Mac) of OpenSSL in
version 1.1.1 and 1.0.2.
NET_SDK_INIT_CFG_ 4 Set path (including Path in string format,
SSLEAY_PATH library name) for e.g., C:\\ssleay32.dll.
ssleay32.dll (Windows),
libssl.so (Linux),
libssl.dylib (Mac) of
OpenSSL in version
1.1.1 and 1.0.2.
lpInBuff
[IN] Input parameter. Different parameter types correspond to different structures, see details in
the table above.
Return Values
24
Remarks
This API should be called before calling NET_DVR_Init to initialize and check the dependent
libraries or capabilities.
3.8 NET_DVR_GetSTDAbility
Get the device capabilities.
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.
3.9 NET_DVR_GetSTDConfig
Get the device configuration information.
API Definition
BOOL NET_DVR_GetSTDConfig(
LONG lUserID,
DWORD dwCommand,
NET_DVR_STD_CONFIG lpConfigParam
);
25
Parameters
lUserID
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 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
See Also
NET_DVR_SetSTDConfig
3.10 NET_DVR_MIME_UNIT
Input Content Details Structure of Message Transmission API

(NET_DVR_STDXMLConfig)

szContentType Array of char Content type (corresponds to Content-Type
field in the message), e.g., text/json. text/xml,
and so on. The content format must be
supported by HTTP.
szName Array of char Content name (corresponds to name field in the
message), e.g., name="upload".
szFilename Array of char Content file name (corresponds to filename
field in the message), e.g., filename="C:\Users
\test\Desktop\11.txt".
26

dwContentLen DWORD Content size
pContent char* Data point
bySelfRead BYTE 0-External file, 1-Internal data, whose address is
specified by szFilename.
byRes Array of BYTE Reserved. Set to 0. Maximum: 15 bytes.
See Also
NET_DVR_XML_CONFIG_INPUT
3.11 NET_DVR_SetSTDConfig
Set the device parameters.
API Definition
BOOL NET_DVR_SetSTDConfig(
LONG lUserID,
DWORD dwCommand,
NET_DVR_STD_CONFIG lpConfigParam
);
Parameters
lUserID
dwCommand
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".
27
Return Values
See Also
NET_DVR_GetSTDConfig
3.12 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
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.
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:
28
Parameter of NET_DVR_STDXMLConfig Component of Text Protocol

lpInputParam lpRequestUrl (see in structure Method+URL
NET_DVR_XML_CONFIG_INPU E.g., GET /ISAPI/System/
T) capabilities
lpInBuffer (see in structure Request Message
NET_DVR_XML_CONFIG_INPU
T)
lpOutputParam lpOutBuffer (see in structure Response Message
NET_DVR_XML_CONFIG_OUTP
UT )
lpStatusBuffer (see in structure Response Message
NET_DVR_XML_CONFIG_OUTP
UT )
3.13 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.
The available error codes of this API are 0, 3, 6, 12, 17, 41, and 47. See details in the Device
Network SDK Errors .
3.14 NET_DVR_GetDVRConfig
Get the device configuration information.
29
API Definition
BOOL NET_DVR_GetDVRConfig(
LONG lUserID,
DWORD dwCommand,
LONG lRuleID,
LONG lChannel,
LPVOID lpOutBuffer,
DWORD dwOutBufferSize,
LPDWORD lpBytesReturned
);
Parameters
lUserID
dwCommand
[IN] Device getting commands, which are different according to different getting functions.
lRuleID
[IN] Rule ID.
lChannel
[IN] Channel No. (NIC No.), which varies with different commands. 0xffffffff-invalid or all
channels, 1-main NIC, 2-extended NIC.
lpOutBuffer
[OUT] Pointer of buffer to receive data. For different getting functions, the structures of this
parameter are different.
dwOutBufferSize
[IN] Size of buffer to receive data (unit: byte). It cannot be 0.
lpBytesReturned
[OUT] Pointer of actually received data size. It cannot be NULL.
Return Values
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
30
3.15 NET_DVR_SetDVRConfig
Set the device parameters.
API Definition
BOOL NET_DVR_SetDVRConfig(
LONG lUserID,
DWORD dwCommand,
LONG lChannel,
LPVOID lpInBuffer,
DWORD dwInBufferSize
);
Parameters
lUserID
dwCommand
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
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
31
3.16 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.
fMessageCallBack
[IN] Callback function, see details in MSGCallBack .
pUser
[IN] User data.
Return Values
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>
int iNum=0;
void CALLBACK MessageCallbackNo1(LONG lCommand, NET_DVR_ALARMER *pAlarmer, char *pAlarmInfo, DWORD
dwBufLen, void* pUser)
{
32
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
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
switch(struPlateResult.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:
33
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
{
break;
break;
break;
break;
default:
break;
}
//Save scene picture
if ((struITSPlateResult.struPicInfo[i].dwDataLen != 0)&&(struITSPlateResult.struPicInfo[i].byType== 1)||
(struITSPlateResult.struPicInfo[i].byType == 2))
{
34
sprintf(filename,"testITSpic%d_%d.jpg",iNum,i);
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);
fwrite(struITSPlateResult.struPicInfo[i].pBuffer, struITSPlateResult.struPicInfo[i].dwDataLen, 1, \
fSnapPicPlate);
iNum++;
}
}
break;
}
default:
break;
}
}
void CALLBACK MessageCallbackNo2(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
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);
}
35
}
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
switch(struPlateResult.struPlateInfo.byColor)//License plate color

{
break;
break;
printf("Vehicle color: White\n");
break;
break;
default:
break;
}
//Scene picture
if (struPlateResult.dwPicLen != 0 && struPlateResult.byResultType == 1 )
{
sprintf(filename,"testpic_%d.jpg",iNum);
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);
fwrite(struPlateResult.pBuffer1,struPlateResult.dwPicLen,1,fSnapPicPlate);
iNum++;
}
break;
}
case COMM_ITS_PLATE_RESULT:
36
{
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
{
break;
break;
break;
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);
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);
fwrite(struITSPlateResult.struPicInfo[i].pBuffer, struITSPlateResult.struPicInfo[i].dwDataLen, 1, \
fSnapPicPlate);
iNum++;
}
}
break;
}
default:
break;
}
}
37
void main() {
//---------------------------------------
//Initialize
NET_DVR_Init();
//Set the connection time and reconnection time
//---------------------------------------
//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;
}
//Set alarm callback function

//Enable arming
NET_DVR_SETUPALARM_PARAM struSetupParam={0};
struSetupParam.dwSize=sizeof(NET_DVR_SETUPALARM_PARAM);
//Alarm information type to upload: 0-History Alarm (NET_DVR_PLATE_RESULT), 1-Real-Time Alarm

(NET_ITS_PLATE_RESULT)
struSetupParam.byAlarmInfoType=1;
//Arming Level: Level-2 arming (for traffic device)
struSetupParam.byLevel=1;
LONG lHandle = NET_DVR_SetupAlarmChan_V41(lUserID,&struSetupParam);

if (lHandle < 0)
{
printf("NET_DVR_SetupAlarmChan_V41 error, %d\n", NET_DVR_GetLastError());
NET_DVR_Cleanup();
return;
}
Sleep(20000);
//Disarm uploading channel
if (!NET_DVR_CloseAlarmChan_V30(lHandle))
{
printf("NET_DVR_CloseAlarmChan_V30 error, %d\n", NET_DVR_GetLastError());
NET_DVR_Cleanup();
38
return;
}
//User logout
//Release SDK resource
NET_DVR_Cleanup();
return;
}
See Also
NET_DVR_SetupAlarmChan_V50
3.16.1 MSGCallBack
Alarm/event information callback function.
Callback Function Definition

typedef void(CALLBACK *MSGCallBack)(
LONG lCommand,
NET_DVR_ALARMER *pAlarmer,
char *pAlarmInfo,
DWORD dwBufLen,
void *pUser
);
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.
39
3.17 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,
);
Parameters
lUserID
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.
3.18 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,
40
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.
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).
3.19 NET_DVR_StopListen_V30
Stop listening (supports multiple threads).
API Definition
BOOL NET_DVR_StopListen_V30(
LONG lListenHandle
);
41
Parameters
lListenHandle
Listening handle, which is returned by NET_DVR_StartListen_V30 .
Return Values
The available error codes of this API are 0, 3, 12, and 17. See details in the Device Network SDK
Errors .
42
Chapter 4 Request URL

The request URLs for implementing the functions in this manual are listed here for reference. You
can search for the URLs and view their definitions.
4.1 /ISAPI/Intelligent/channels/<ID>/capabilities
Get the intelligent capability of device.
Request URI Definition
Table 4-1 GET /ISAPI/Intelligent/channels/<ID>/capabilities

Method GET
Description Get the intelligent capability of device.
Query None
Request None.
Response Succeeded: XML_IntelliCap
Failed: XML_ResponseStatus
Remarks
The <ID> in the URI refers to the intelligent channel ID.
4.2 /ISAPI/Intelligent/channels/<ID>/personQueueDetection/
capabilities?format=json
Get the configuration capability of queue management by channel.
Table 4-2 GET /ISAPI/Intelligent/channels/<ID>/personQueueDetection/capabilities?format=json

Method GET
Description Get the configuration capability of queue management by channel.
Query format: determine the format of request or response message.
43
Request None
Response Succeeded: JSON_PersonQueueDetectionInfoCap
Failed: JSON_ResponseStatus
Remarks
The <ID> in the URI refers to the channel ID.
queueCountingFile?format=json
Search for and get the people queuing-up detection report file.
Table 4-3 POST /ISAPI/Intelligent/channels/<ID>/personQueueDetection/queueCountingFile?

format=json
Method POST
Description Search for and get the people queuing-up detection report file.
Request JSON_PersonQueueCountingDescription
Response Succeeded: JSON_PersonQueueCountingFileResult
Remarks
queueCountingResult?format=json
Search for and get the people queuing-up detection report details.
44
Table 4-4 POST /ISAPI/Intelligent/channels/<ID>/personQueueDetection/queueCountingResult?

format=json
Method POST
Description Search for and get the people queuing-up detection report details.
Request JSON_PersonQueueCountingDescription
Response Succeeded: JSON_PersonQueueCountingResult
Remarks
queueTimeFile?format=json
Search for and get the waiting time detection report file.
Table 4-5 POST /ISAPI/Intelligent/channels/<ID>/personQueueDetection/queueTimeFile?

format=json
Method POST
Description Search for and get the waiting time detection report file.
Request JSON_PersonQueueTimeDescription
Response Succeeded: JSON_PersonQueueTimeFileResult
Remarks
45
queueTimeResult?format=json
Search for and get the waiting time detection report details.
Table 4-6 POST /ISAPI/Intelligent/channels/<ID>/personQueueDetection/queueTimeResult?

format=json
Method POST
Description Search for and get the waiting time detection report details.
Request None
Response Succeeded: JSON_PersonQueueTimeResult
Remarks
rawDataFile?format=json
Search for and get the queue management raw data in file format.
Table 4-7 POST /ISAPI/Intelligent/channels/<ID>/personQueueDetection/rawDataFile?

format=json
Method POST
Description Search for and get the queue management raw data in file format.
Request JSON_PersonQueueRawDataFileDescription
Response Succeeded: JSON_PersonQueueRawDataFileResult
46
Remarks
4.8 /ISAPI/Intelligent/channels/<ID>/personQueueDetection?
format=json
Get or set parameters of queue management alarm by channel.
Table 4-8 GET /ISAPI/Intelligent/channels/<ID>/personQueueDetection?format=json

Method GET
Description Get parameters of queue management alarm by channel.
Request None
Response Succeeded: JSON_PersonQueueDetectionInfo
Table 4-9 PUT /ISAPI/Intelligent/channels/<ID>/personQueueDetection?format=json

Method PUT
Description Set parameters of queue management alarm by channel.
Request JSON_PersonQueueDetectionInfo
Response JSON_ResponseStatus
Remarks
47
Chapter 5 Request and Response Message

The request and response messages in XML or JSON format of each request URL are listed here for
reference. You can search for the parameters by the message name.
5.1 JSON_EventNotificationAlert_Alarm/EventInfo
EventNotificationAlert message with alarm or event information in JSON format.
{
"ipAddress": "",
/*required, device IPv4 address , string, the maximum size is 32 bytes*/
"ipv6Address": "",
/*optional, device IPv6 address, string, the maximum size is 128 bytes*/
"portNo": ,
/*optional, device port No., integer32*/
"protocol": "",
/*optional, protocol type, "HTTP, HTTPS", string, the maximum size is 32 bytes*/
"macAddress": "",
/*optional, MAC address, string, the maximum size is 32 bytes, e.g., 01:17:24:45:D9:F4*/
"channelID": "",
/*optional, device channel No., integer32*/
"dateTime": "",
/*optional, string, alarm/event triggered or occurred time based on ISO8601, the maximum size is 32 bytes, e.g.,
2009-11-14T15:27Z*/
"activePostCount": "",
/*required, alarm/event frequency, integer32*/
"eventType": "",
/*required, alarm/event type, "captureResult, faceCapture,...", string, the maximum size is 128 bytes*/
"eventState": "",
/*required, string, the maximum size is 32 bytes, durative alarm/event status: "active"-valid, "inactive"-invalid*/
"eventDescription": "",
/*required, event description, string, the maximum size is 128 bytes*/
"deviceID":"",
/*string type, device ID*/
"uuid":"",
/*string type, event UUID, which is used to uniquely identify an event, the standard UUID format is xxxxxxxx-xxxx-xxxx-
xxxx-xxxxxxxxxxxx*/
...
/*optional, for different alarm/event types, the nodes are different, see the message examples in different
applications*/
}
5.2 JSON_EventNotificationAlert_PeopleQueuingUpAlarmMsg
JSON message about regional people queuing-up alarm details
48
Regional People Queuing-Up Alarm with Binary Picture Data

Content-Type: multipart/form-data; boundary=MIME_boundary
--MIME_boundary
Content-Type: application/json
Content-Length: 480
{
"ipAddress": "",
"ipv6Address": "",
"portNo": ,
"protocol": "",
"macAddress": "",
"channelID": "",
"releatedChannelList": [1,2,3],
/*optional, array of integers, list of alarm related channels, which are of the same camera with channelID; this
parameter is used for live view or playback on the platform*/
"dateTime": "",
"activePostCount": ,
"eventType": "",
/*required, string, occurred event type, here it should be set to "personQueueCounting", and the maximum value size
is 128 bytes*/
"eventState": "",
"deviceID": "",
"RegionCapture"{
/*captured region information*/
"humanCounting":{
/*people amount*/
"count":
/*required, integer, actual people amount, it is ranging from 0 to 60*/
}
"rule":{
/*rule properties*/
"ruleID": ,
/*required, integer, rule ID, which corresponds to the target person region ID*/
"alarmCount": ,
/*required, integer, configured threshold of queuing-up people amount, it is ranging from 0 to 60*/
"regionColor": "",
/*required, string, rule region color, "blue", "red", and "yellow" are available*/
"Region": [{
/*required, rule region coordinates, it is polygonal (3 to 10 edges)*/
"x": ,
/*required, float, x-coordinate, it is ranging from 0.000 to 1*/
"y":
/*required, float, y-coordinate, it is ranging from 0.000 to 1*/
}]
"countTriggerType": "",
/*optional, string type, triggering type of people queuing-up alarm: "greater", "less", "equal", "unequal"-the alarm is
triggered when the number of queuing-up persons is larger than, smaller than, equal to, or not equal to the value of
alarmCount; "range"-the alarm is triggered when the number of queuing-up person is in the range between
maxAlarmCount and alarmCount*/
49
"durationTime":
/*optional, integer type, queuing-up status (number of queuing-up persons) keeping duration, which is between 0 and
3600, the default duration is 300, unit: second; the people queuing-up alarm is triggered if the number of queuing-up
persons keeps for the configured duration*/
}
}
"contentID": ""
/*background picture*/
}
--MIME_boundary
Content-Type: image/jpeg
Content-Length: 42569
Content-ID: human_image
fefefwageegfqaeg…
--MIME_boundary--
Regional People Queuing-Up Alarm with Picture URL

{
"ipAddress": "",
"ipv6Address": "",
"portNo": ,
"protocol": "",
"macAddress": "",
"channelID": "",
"dateTime": "",
"eventType": "",
/*required, string, occurred event type, here it should be set to "personQueueCounting", and the maximum value size
is 128 bytes*/
"eventState": "",
"deviceID": "",
"RegionCapture"{
/*captured region information*/
"humanCounting":{
/*people amount*/
"count":
/*required, integer, actual people amount, it is ranging from 0 to 60*/
}
"rule":{
/*rule properties*/
"ruleID": ,
"alarmCount": ,
/*required, integer, configured threshold of queuing-up people amount, it is ranging from 0 to 60*/
"regionColor": "",
50
"Region": [{
"x": ,
"y":
}]
"durationTime":
}
}
"backgroundImageURL": ""
/*background picture URL*/
}
5.3 JSON_EventNotificationAlert_RealTimeQueueManagementDataMsg
JSON message about details of real-time regional people queuing-up alarm
{
"ipAddress": "",
/*required, string, IPv4 address of alarm device, the maximum value size is 32 bytes, e.g., 172.6.64.7*/
"ipv6Address": "",
/*required, string, IPv6 address of alarm device, the maximum value size is 128 bytes*/
"portNo": ,
/*optional, integer32, port No. of alarm device*/
"protocol": "",
/*optional, string, protocol type: "HTTP"-for device network SDK, "HTTPS", "EHome"-for ISUP SDK; the maximum
value size is 32 bytes*/
"macAddress": "",
/*optional, string, MAC address, the maximum value size is 32 bytes, e.g., 01:17:24:45:D9:F4*/
"channelID": ,
/*optional, integer32, No. of alarm triggered channel*/
"dateTime": "",
/*required, string, alarm triggered time (ISO 8601 format), the maximum value size is 32 bytes, e.g.,
2004-05-03T17:30:08+08:00*/
/*required, integer32, uploaded times of one alarm*/
"eventType": "",
51
/*required, string, occurred event type, here it should be set to "personQueueRealTime", and the maximum value size
is 128 bits*/
"eventState": "",
/*see the description of above nodes in JSON_EventNotificationAlert_Alarm/EventInfo*/
"deviceID": "",
/*optional, device ID (PUID), which is returned in the alarm based on ISUP (Intelligent Security Uplink Protocol)*/
"PersonQueueRealTimeData": {
/*real-time information of queue management*/
"targetID": ,
/*required, integer type, target ID*/
"ruleID": ,
/*required, integer type, rule ID*/
"personState": "",
/*required, string type, people status: "enter"-region entrance, "leave"-region exiting*/
"waitTime": ,
/*dependent, integer32 type, actual waiting time, this node is valid only when personState is "leave", whose value is
between 0 and 3600s*/
"peopleNum": ,
/*required, integer type, total number of people in this region*/
"enterTime": ""
/*dependent, target entered time, which is in ISO8601 time format, this node is valid only when personState is
"leave"*/
}
}
5.4 JSON_EventNotificationAlert_WaitingTimeDetectionAlarmMsg
JSON message about details of waiting time detection alarm
Waiting Time Detection Alarm with Binary Picture Data

Content-Type: multipart/form-data; boundary=MIME_boundary
--MIME_boundary
Content-Type: application/json
Content-Length: 480
{
"ipAddress": "",
/*required, string, IPv4 address of alarm device, the maximum value size is 32 bytes, e.g., 172.6.64.7*/
"ipv6Address": "",
/*required, string, IPv6 address of alarm device, the maximum value size is 128 bytes*/
"portNo": ,
/*optional, integer32, port No. of alarm device*/
"protocol": "",
/*optional, string, protocol type: "HTTP"-for device network SDK, "HTTPS", "EHome"-for ISUP SDK; the maximum
value size is 32 bytes*/
"macAddress": "",
/*optional, string, MAC address, the maximum value size is 32 bytes, e.g., 01:17:24:45:D9:F4*/
"channelID": ,
/*optional, integer32, No. of alarm triggered channel*/
52
"dateTime": "",
/*required, string, alarm triggered time (ISO 8601 format), the maximum value size is 32 bytes, e.g.,
2004-05-03T17:30:08+08:00*/
/*required, integer32, uploaded times of one alarm*/
"eventType": "",
/*required, string, occurred event type, here it should be set to "personQueueTime", and the maximum value size is
128 bytes*/
"eventState": "",
"deviceID": "",
"humanCapture": {
/*captured human information*/
"human":{
/*human attributes*/
"targetID": ,
/*required, integer, person target ID, whose waiting time is longer than the configured alarm threshold. The ID is
generated by DSP, and corresponds to the person position*/
"waitTime": ,
/*required, integer, actual waiting time, it is ranging from 0 to 3600s*/
"Region": [{
/*required, target person region coordinates, it is quadrilateral*/
"x": ,
"y":
}]
contentID": ""
/*captured human thumbnail*/
},
"rule":{
/*rule properties*/
"ruleID": ,
"alarmTime": ,
/*required, integer, configured waiting time alarm threshold, it is ranging from 0 to 3600s*/
"regionColor": "",
"Region": [{
"x": ,
"y":
}]
"timeTriggerType": ""
/*optional, string type, triggering type of waiting time detection alarm: "greater", "less", "equal", "unequal"-the alarm
is triggered when waiting time is larger than, smaller than, equal to, or not equal to the value of alarmTime*/
}
53
},
"contentID": ""
/*background picture*/
}
--MIME_boundary
Content-ID: human_image
fefefwageegfqaeg…
--MIME_boundary
Content-ID: background_image
fefefwageegfqaeg…
--MIME_boundary--
Waiting Time Detection Alarm with Picture URL

{
"ipAddress": "",
"ipv6Address": "",
"portNo": ,
"protocol": "",
"macAddress": "",
"channelID": "",
"dateTime": "",
"eventType": "",
/*required, string, occurred event type, here it should be set to "personQueueTime", and the maximum value size is
128 bytes*/
"eventState": "",
"deviceID": "",
"humanCapture": {
/*captured human information*/
"human":{
/*human attributes*/
"targetID": ,
/*required, integer, person target ID, whose waiting time is longer than the configured alarm threshold. The ID is
generated by DSP, and corresponds to the person position*/
"waitTime": ,
/*required, integer, actual waiting time, it is ranging from 0 to 3600s*/
"Region": [{
/*required, target person region coordinates, it is quadrilateral*/
"x": ,
"y":
54

}],
"humanImageURL": ""
/*captured human thumbnail URL*/
},
"rule":{
/*rule properties*/
"ruleID": ,
"alarmTime": ,
/*required, integer, configured waiting time alarm threshold, it is ranging from 0 to 3600s*/
"regionColor": "",
"Region": [{
"x": ,
"y":
}]
}
},
"backgroundImageURL": ""
/*background picture URL*/
}
5.5 JSON_PersonQueueCountingDescription
JSON message about conditions of searching for people queuing-up reports
{
"PersonQueueCountingDescription": {
/*required, search condition of people queuing-up report*/
"fileType": "",
/*optional, string, file type, opt="excel, txt"*/
"reportType": "",
/*required, string, report type, opt="daily, weekly, monthly, custom"*/
"startTime": "",
/*required, IOS8601 time, search start time, e.g., "2004-05-03T00:00:00+08:00" or "2004-05-03T00:00:00.000Z"*/
"RuleList": [{
/*required, rule information, up to 3 rules can be supported*/
"ruleID": ,
/*required, integer, rule ID, which corresponds to the region ID when configuring rule*/
}],
"CountRangeList" : [{
/*required, array, people queuing-up data of all regions under a rule, up to 3 regions are supported*/
"minCount": ,
55
/*optional, integer, minimum number of queuing-up people, range: from 0 to 60*/

"maxCount": ,
/*optional, integer, maximum number of queuing-up people, range: from 0 to 60*/
}]
"endTime": "",
/*dep, IOS8601t type, end time of report search, e.g., 2004-05-03T00:00:00+08:00, it is valid only when the
reportType is "custom"*/
"customReportAccuracy": "day"
/*dep, cuatom report accuracy, currently, it only corrects to day, and it is valid only when the reportType is "custom"*/
}
}
Note
At least one of the minCount and maxCount fields is required, if only minCount is configured, it
indicates no upper-limit, e.g., minCount = 10, maxCount is reserved, the statistics data more than
10 people will be searched; if only maxCount is configured, it indicates no lower-limit, e.g.,
maxCount = 10, minCount is reserved, the statistics data less than 10 persons will be searched.
Example
Message Example
{
"PersonQueueTimeDescription":{
"fileType":"excel",
"reportType":"daily",
"startTime":"2017-1-14T00:00:00Z",
"searchType":"rule",
"RuleList":[{
"ruleID":1
}],
"CountList":[{
"minCount":0,
"maxCount":20
},
{
"minCount":20,
"maxCount":40
}]
}
}
5.6 JSON_PersonQueueCountingFileResult
JSON message about results of searching for people queuing-up report files
{
"PersonQueueCountingFileResult":
/*required, search result of people queuing-up report*/
{
56
"fileURL": ""
/*file URL of people queuing-up report*/
}
}
Example
Message Example
{
"PersonQueueCountingFileResult": {
"fileURL": "http://10.10.36.163/ISAPI/Intelligent/DownloadFile?filePath=/home/
Day_CountFile_2017-01-14T00:00:00.xls&"
}
}
5.7 JSON_PersonQueueCountingResult
JSON message about results of searching for people queuing-up report details
{
"PersonQueueCountingResult": {
/*required, search result of people queuing-up detection report*/
"RuleList" : [{
/*required, array, people queuing-up detection reports of all regions under multiple rules, up to 3 rules are
supported*/
"ruleID": ,
/*required, integer, rule ID, which corresponds to the region ID when configuring rules*/
"CountRangeList" : [{
/*required, array, people queuing-up data of all regions under a single rule, up to 3 regions are supported*/
"minCount": ,
/*optional, integer, minimum number of queuing-up people, range: from 0 to 60*/
"maxCount": ,
/*optional, integer, maximum number of queuing-up people, range: from 0 to 60*/
"CountingInfoList": [{
/*required, people queuing-up report details*/
"startTime": "",
/*required, IOS8601 time, start time of the time period, e.g., 2004-05-03T00:00:00+08:00 or
2004-05-03T00:00:00.000Z*/
"endTime": "",
/*required, IOS8601 time, end time of the time period, e.g., 2004-05-03T00:00:00+08:00 or
2004-05-03T00:00:00.000Z*/
"count":
/*required, integer, number of queuing-up persons: between 0 to 60*/
}]
}]
}]
}
}
57
Note
● At least one of the minCount and maxCount fields is required, if only minCount is configured, it
indicates no upper-limit, e.g., minCount = 10, maxCount is reserved, the statistics data more
than 10 persons will be searched; if only maxCount is configured, it indicates no lower-limit, e.g.,
maxCount = 10, minCount is reserved, the statistics data less than 10 persons will be searched.
● For daily report, one result will be returned at each hour, total 24 results; for weekly report, one
result will be returned at each day, total 7 results; for monthly report, one result will be returned
at each day, total 30 results.
Example
Message Example
{
"PersonQueueCountingDescription":{
"reportType":"daily",
"startTime":"2017-12-21T00:00:00Z",
"RuleList":[{
"ruleID":1
}],
"WaitTimeList":[{
"minWaitTime":600,
"maxWaitTime":1000
}]
}
}
5.8 JSON_PersonQueueDetectionInfo
JSON message about people queuing-up parameters
{
"PersonQueueDetectionInfo": {
/*required, queue management configuration information*/
"countingEnabled": ,
/*required, boolean, enable people queuing-up detection*/
"queueTimeEnabled": ,
/*required, boolean, enable waiting time detection*/
"RuleInfo": [{
/*required, queue management rule information, the number of rules is ranging from 1 to 3*/
"ruleID": ,
/*required, integer, rule ID*/
"ruleName": "",
/*required, string, rule name, string size: between 0 and 32*/
"OSDOverlayEnabled": ,
/*required, boolean, enable OSD*/
"alarmIntervalTime": ,
/*required, integer, alarm time interval, range: between 0 to 3600s, default: 300s*/
58
"PersonQueueCounting":{
/*required, people queuing-up parameters*/
"alarmCount": ,
/*required, integer, number threshold of persons for triggering alarm, range: between 0 and 60 persons, default: 10*/
"maxAlarmCount": ,
/*dep, integer type, maximum number of queuing-up persons to trigger alarm, it is valid when countTriggerType is
"range"*/
"durationTime":
},
"PersonQueueTime":{
/*required, waiting time detection parameters*/
"alarmTime": ,
/*required, integer, waiting time threshold for triggering alarm, range: between 0 and 3600s, default: 600s*/
},
"regionColor": "",
/*required, string, color of region that configured with rule, "blue, red, yellow"*/
"Region": [{
/*required, coordinates of region (polygon, 3 to 10 sides) that configured with rule*/
"x": ,
/*required, float, x-coordinate, range: between 0.000 and 1*/
"y":
/*required, float, y-coordinate, range: between 0.000 and 1*/
}]
}]
"alarmPicEnabled": ,
/*optional, boolean, whether to upload pictures (i.e., background picture and human body thumbnail) when alarm is
triggered, if this node is not supported by device, the alarm pictures will be uploaded by default*/
"realTimeEnabled":
/*optional, boolean, whether to upload real-time data of queue management, the corresponding event type is
"personQueueRealTime"*/
}
}
Example
Message Example
{
"PersonQueueDetectionInfo": {
"countingEnabled": false,
"queuetimeEnabled": true,
"RuleInfo": [{
59
"ruleID": 1,
"ruleName": "East Window",
"OSDOverlayEnabled": true,
"alarmIntervalTime": 300,
"alarmCount": 5,
"countTriggerType": "range",
"maxAlarmCount": 5,
"durationTime": 300
},
"PersonQueueTime": {
"alarmTime": 300,
"timeTriggerType": "greater"
},
"regionColor": "yellow",
"Region": [{
"x": 0.411000,
"y": 0.325000
},
{
"x": 0.250000,
"y": 0.643000
},
{
"x": 0.435000,
"y": 0.751000
},
{
"x": 0.576000,
"y": 0.675000
},
{
"x": 0.647000,
"y": 0.501000
}]
},
{
"ruleID": 2,
"ruleName": "Area2",
"OSDOverlayEnabled": true,
"alarmIntervalTime": 300,
"alarmCount": 5
},
"PersonQueueTime":{
"alarmTime": 300
},
"regionColor": "yellow",
"Region":[{
"x":0.106000,
"y":0.218000
},
60
{
"x": 0.078000,
"y": 0.383000
},
{
"x": 0.282000,
"y": 0.429000
},
{
"x": 0.369000,
"y": 0.204000
},
{
"x": 0.188000,
"y": 0.019000
}]
}]
"alarmPicEnabled": true,
"realTimeEnabled": true
}
}
5.9 JSON_PersonQueueDetectionInfoCap
JSON message about configuration capability of people queuing-up
{
"PersonQueueDetectionInfoCap": {
/*required, queue management capability*/
"countingEnabled": "true,false",
/*required, boolean, whether to enable people queuing-up*/
"queueTimeEnabled": "true,false",
/*required, boolean, whether to enable waiting time detection*/
"RuleInfoCap": {
/*required, queue management rule information, the number of rules is ranging from 1 to 3*/
"maxSize": 3,
/*required, integer, capability of maximum number of supported queue management rules*/
"ruleID": {
"@min": 1,
"@max": 3
},
"ruleName": {
/*required, string, rule name, the string size is ranging from 0 to 32*/
"@min": 0,
"@max": 32
},
"OSDOverlayEnabled": "true,false", /*required, boolean, enable OSD*/
"alarmIntervalTime": {
/*required, integer, alarm time interval, range: between 0 and 3600s, default: 300s*/
61
"@min": 0,
"@max": 3600,
"#text": 300
},
/*required, people queuing-up parameters*/
"alarmCount": {
/*required, integer, number threshold of persons for triggering alarm, range: between 0 and 60 persons, default: 10*/
"@min": 0,
"@max": 60,
"#text": 10
}
"countTriggerType": {
"@opt": "greater,less,equal,unequal,range",
"@def": "greater"
},
"maxAlarmCount": {
/*dep, integer type, maximum number of queuing-up persons to trigger alarm, it is valid when countTriggerType is
"range"*/
"@min": 0,
"@max": 60,
"#text": 5
},
"durationTime": {
"@min": 0,
"@max": 3600,
"#text": 300
}
},
"PersonQueueTime":{
/*required, waiting time detection parameters*/
"alarmTime": {
/*required, integer, waiting time threshold for triggering alarm, range: between 0 and 3600s, default: 600s*/
"@min": 0,
"@max": 3600,
"#text": 600
}
"timeTriggerType": {
"@opt": "greater,less,equal,unequal",
"@def": "greater"
},
},
"regionColor": {
62
/*required, string, color of region that configured with rule, "blue, red, yellow"*/
"@opt": "blue,red,yellow",
"#text": "yellow"
},
"RegionCap": {
/*required, coordinates of region (polygon, 3 to 10 sides) that configured with rule*/
"minSize": 3,
/*required, integer, capability of minimum region sides*/
"maxSize": 10,
/*required, integer, capability of maximum region sides*/
"x": {
/*required, float, x-coordinate, range: between 0.000 and 1*/
"@min": 0.000,
"@max": 1.000,
"#text": 0.120
},
"y": {
/*required, float, y-coordinate, range: between 0.000 and 1*/
"@min": 0.000,
"@max": 1.000,
"#text": 0.120
}
}
"alarmPicEnabled":{
/*optional, boolean, whether to upload pictures (i.e., background picture and human body thumbnail) when alarm is
triggered, if this node is not supported by device, the alarm pictures will be uploaded by default*/
"@opt": "true,false",
/*"true"-upload alarm picture (default), "false"-not upload alarm pictures*/
"@def": "true"
},
"realTimeEnabled":{
/*optional, boolean, whether to upload real-time data of queue management, the corresponding event type is
"personQueueRealTime"*/
"@opt": "true,false", /*"true"-upload real-time data (default), "false"-not upload*/
"@def": "true"
}
}
},
"PersonQueueCountingCap": {
/*optional, capability of getting people queuing-up result and report*/
"fileType": {
/*optional, string, file type, "excel, txt"*/
"@opt": "excel,txt",
"#text": "excel"
},
"reportType": {
/*required, string, report type, "daily, weekly, monthly, custom"*/
"@opt": "daily,weekly,monthly,custom",
"#text": "daily"
},
"isSupportStartTime": "true,false",
/*required, bool, whether supports setting start time of searching reports*/
63
"RuleListCap": {
"maxSize": 3,
/*required, integer, capability of capability of maximum number of supported queue management rules*/
"ruleID": {
"@min": 1,
"@max": 3
}
},
"WaitTimeListCap": {
/*required, waiting time information, up to 3 time durations are supported*/
"maxSize": 3,
/*required, integer, supported maximum number of time durations*/
"minWaitTime": {
/*required, integer, minimum waiting time, it ranges from 0s to 3600s*/
"@min": 0,
"@max": 3600
},
"maxWaitTime": {
/*required, integer, maximum waiting time, it ranges from 0s to 3600s*/
"@min": 0,
"@max": 3600
}
},
"isSupportEndTime": "true,false",
/*dep, boolean, whether support the end time of report search, and it is valid only when reportType is custom*/
"customReportAccuracy": {
/*dep, custom report accuracy, currently, it corrects to day. And it is valid only when reportType is custom*/
"@opt": "day",
"@def": "day"
}
"isSupportAverageTime": "true,false"
/*optional, boolean type, whether supports calculating average waiting time duration in people queuing-up statistics*/
},
"PersonQueueTimeCap": {
/*optional, capability of getting waiting time detection result and report*/
"fileType": {
/*optional, string, file type, "excel, txt"*/
"@opt": "excel,txt",
"#text": "excel"
},
"reportType": {
/*required, string, report types, "daily, weekly, monthly, custom"*/
"@opt": "daily,weekly,monthly, custom",
"#text": "daily"
},
"isSupportStartTime": "true,false",
/*required, bool, whether supports setting start time of searching reports*/
"RuleListCap": {
"maxSize": 3,
64
/*required, integer, capability of capability of maximum number of supported queue management rules*/
"ruleID": {
"@min": 1,
"@max": 3
}
},
"CountListCap": {
/*required, queuing-up people amount information, up to 3 queues are supported*/
"maxSize": 3,
/*required, integer, supported maximum number of queues*/
"minCount": {
/*required, integer, minimum number of queuing-up people, it ranges from 0 to 60*/
"@min": 0,
"@max": 60
},
"maxCount": {
/*required, integer, maximum number of queuing-up people, it ranges from 0 to 60*/
"@min": 0,
"@max": 60
}
},
"isSupportEndTime": "true,false",
/*dep, boolean, whether support the end time of report search, and it is valid only when reportType is custom*/
"customReportAccuracy": {
/*dep, custom report accuracy, currently, it corrects to day. And it is valid only when reportType is custom*/
"@opt": "day",
"@def": "day"
}
}
"isSupportRawDataFile": "true,false"
/*required, boolean, whether supports getting queue management raw data*/
"isSupportAlgParam": "true,false"
/*optional, boolean type, whether supports configuring advanced parameters for algorithm library*/
}
5.10 JSON_PersonQueueRawDataFileDescription
JSON message about conditions of searching for queue management raw data
{
"PersonQueueRawDataFileDescription": { /*required, search condition of queue management raw data files*/
"searchID": , /*required, integer, search ID, which is used to save the search history for fast search at next time*/
"searchResultPosition": , /*required, integer, start position of in the search result list*/
"maxResults": , /*required, integer, number of matched records, up to 4000 records can be searched for once*/
"startTime": "", /*required, ios_8601 time, start time of search, e.g., 2004-05-03T00:00:00+08:00 or
2004-05-03T00:00:00.000Z*/
"endTime": "" /*required, ios_8601 time, end time of search, e.g., 2004-05-03T00:00:00+08:00 or
2004-05-03T00:00:00.000Z*/
}
65
}
}
Example
Message Example
{
"PersonQueueRawDataFileDescription":{
"searchID":1,
"searchResultPosition":1,
"maxResults":4000,
"startTime":"2017-01-14T00:00:00.000Z",
"endTime":"2017-01-15T00:00:00.000Z"
}
}
5.11 JSON_PersonQueueRawDataFileResult
JSON message about results of searching for queue management raw data
{
"PersonQueueRawDataFileResult": /*required, search result of queue management raw file*/
{
"searchID": , /*required, integer, search ID, which is used to save the search history for fast search at next
time*/
"responseStatus": "", /*required, string, search status, "OK"-receiving completed, "NO MATCHES"-no data found,
"MORE"-more data to be received at next time*/
"numOfMatches": , /*required, integer, number of returned records*/
"totalMatches": , /*required, integer, total number of matched records*/
"endTime": "", /*required, ios_8601 time, time of returning the last data record, e.g., 2004-05-03T00:00:00+08:00
or 2004-05-03T00:00:00.000Z*/
"fileURL": "" /*required, string, file URL*/
}
}
Example
Message Example
{
"PersonQueueRawDataFileResult": {
"searchID": 1,
"responseStatus": "NO MATCHES",
"numOfMatches": 0,
"totalMatches": 0,
"endTime": "1970-01-01T00:00:00",
RawFile_2017-01-14T00:00:00_1970-01-01T00:00:00.xls&"
}
}
66
5.12 JSON_PersonQueueTimeDescription
JSON message about conditions of searching for waiting time detection reports
{
"PersonQueueTimeDescription": { /*required, search condition of waiting time detection report*/
"fileType": "", /*optional, string, file type, "excel, txt"*/
"reportType": "", /*required, string, report type, "daily, weekly, monthly, custom"*/
"startTime": "", /*required, IOS8601 time, start time of searching report, e.g., 2004-05-03T00:00:00+08:00 or
2004-05-03T00:00:00.000Z*/
"RuleList": [{ /*required, rule information, up to 3 rules can be supported*/
"ruleID": , /*required, integer, rule ID, which corresponds to the region ID when configuring rule*/
}],
"WaitTimeRangeList" : [{ /*required, array, waiting time of all time periods under a single rule, up to 3 time periods
are supported*/
"minWaitTime": , /*Optional, integer, minimum waiting time, range: from 0 to 3600s*/
"maxWaitTime": , /*Optional, integer, maximum waiting time, range: from 0 to 3600s*/
}]
"endTime": "", /*dep, IOS8601t type, end time of report search, e.g., 2004-05-03T00:00:00+08:00, it is valid only
when the reportType is "custom"*/
"customReportAccuracy": "day" /*dep, cuatom report accuracy, currently, it only corrects to day, and it is valid only
when the reportType is "custom"*/
}
}
Note
At least one of minWaitTime and maxWaitTime fields is required, if only minWaitTime is
configured, it indicates no upper-limit, e.g., minWaitTime=600, maxWaitTime is reserved, the
waiting time which is longer than 600s will be searched; if only maxWaitTime is configured, it
indicates no lower-limit, e.g., maxWaitTime=600, minWaitTime is reserved, the waiting time which
is shorter than 600s will be searched.
Example
Message Example
{
"PersonQueueTimeDescription":{
"reportType":"daily","startTime":"2017-1-14T00:00:00Z",
"RuleList":[{
"ruleID":1
}],
"CountList":[{
"minCount":0,
"maxCount":20
}]
}
}
67
5.13 JSON_PersonQueueTimeFileResult
JSON message about results of searching for waiting time detection report files
{
"PersonQueueTimeFileResult": /*required, search result of waiting time detection report*/
{
"fileURL": "" //file URL of waiting time detection report
}
}
Example
Message Example
{
"PersonQueueTimeFileResult": {
Day_TimeFile_2017-01-14T00:00:00.xls&"
}
}
5.14 JSON_PersonQueueTimeResult
JSON message about results of searching for waiting time detection report details
{
"PersonQueueTimeResult": { /*required, search results of waiting time detection report*/
"RuleList" : [{ /*required, array, waiting time of all time periods under multiple rules, up to 3 rules are
supported*/
"ruleID": , /*required, integer, rule ID, which corresponds to the time period ID when configuring rules*/
"WaitTimeRangeList" : [{ /*required, array, waiting time of all time periods under a single rule, up to 3 time
periods are supported*/
"minWaitTime": , /*Optional, integer, minimum waiting time, range: from 0 to 3600s*/
"maxWaitTime": 600, /*Optional, integer, maximum waiting time, range: from 0 to 3600s*/
"TimeInfoList": [{ /*required, waiting time detection report details*/
"startTime": "", /*required, IOS8601 time, start time of the time period, e.g., 2004-05-03T00:00:00+08:00 or
2004-05-03T00:00:00.000Z*/
"endTime": "", /*required, IOS8601 time, end time of the time period, e.g., 2004-05-03T00:00:00+08:00 or
2004-05-03T00:00:00.000Z*/
"time": 60 /*required, integer, waiting time: from 0 to 3600s*/
}]
}]
}]
}
}
68
Note
● At least one of minWaitTime and maxWaitTime fields is required, if only minWaitTime is
configured, it indicates no upper-limit, e.g., minWaitTime=600, maxWaitTime is reserved, the
waiting time which is longer than 600s will be searched; if only maxWaitTime is configured, it
indicates no lower-limit, e.g., maxWaitTime=600, minWaitTime is reserved, the waiting time
which is shorter than 600s will be searched.
● For daily report, one result will be returned at each hour, total 24 results; for weekly report, one
result will be returned at each day, total 7 results; for monthly report, one result will be returned
at each day, total 30 results.
Example
Message Example
{
"PersonQueueTimeResult": {
"RuleList": [{
"ruleID": 1,
"CountRangeList": [{
"minCount": 0,
"maxCount": 20,
"TimeInfoList": [{
"time": 0,
"startTime": "2017-01-14T00:00:00",
"endTime": "2017-01-14T00:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T01:00:00",
"endTime": "2017-01-14T01:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T02:00:00",
"endTime": "2017-01-14T02:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T03:00:00",
"endTime": "2017-01-14T03:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T04:00:00",
"endTime": "2017-01-14T04:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T05:00:00",
"endTime": "2017-01-14T05:59:59"
69
},
{
"time": 0,
"startTime": "2017-01-14T06:00:00",
"endTime": "2017-01-14T06:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T07:00:00",
"endTime": "2017-01-14T07:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T08:00:00",
"endTime": "2017-01-14T08:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T09:00:00",
"endTime": "2017-01-14T09:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T10:00:00",
"endTime": "2017-01-14T10:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T11:00:00",
"endTime": "2017-01-14T11:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T12:00:00",
"endTime": "2017-01-14T12:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T13:00:00",
"endTime": "2017-01-14T13:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T14:00:00",
"endTime": "2017-01-14T14:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T15:00:00",
"endTime": "2017-01-14T15:59:59"
},
{
70
"time": 0,
"startTime": "2017-01-14T16:00:00",
"endTime": "2017-01-14T16:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T17:00:00",
"endTime": "2017-01-14T17:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T18:00:00",
"endTime": "2017-01-14T18:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T19:00:00",
"endTime": "2017-01-14T19:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T20:00:00",
"endTime": "2017-01-14T20:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T21:00:00",
"endTime": "2017-01-14T21:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T22:00:00",
"endTime": "2017-01-14T22:59:59"
},
{
"time": 0,
"startTime": "2017-01-14T23:00:00",
"endTime": "2017-01-14T23:59:59"
}]
}]
}]
}
}
5.15 JSON_ResponseStatus
JSON message about response status
{
"requestURL":"",
71
/*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*/
}
5.16 XML_Cap_Schedule
Schedule capability message in XML format
<Schedule version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<id></id>
<eventType
opt="IO,VMD,videoloss,PIR,linedetection,fielddetection,audioexception,facedetection,regionEntrance,regionExiting,loi
tering,group,rapidMove,parking,unattendedBaggage,attendedBaggage,storageDetection,shipsDetection,HUMANATTRI
BUTE,humanAttribute,faceContrast,faceSnap, mixedTargetDetection">

</eventType>
<inputIOPortID></inputIOPortID>
<outputIOPortID></inputIOPortID>
<videoInputChannelID></videoInputChannelID>
<TimeBlockList size="8">
<TimeBlock>
<dayOfWeek opt="1,2,3,4,5,6,7">

</dayOfWeek>
<TimeRange>
<beginTime></beginTime>
<endTime></endTime>
</TimeRange>
</TimeBlock>
</TimeBlockList>
<HolidayBlockList>
<TimeBlock>
<TimeRange>
<beginTime></beginTime>
72
<endTime></endTime>

</TimeRange>
</TimeBlock>
</HolidayBlockList>
</Schedule>
5.17 XML_EventNotificationAlert_AlarmEventInfo
EventNotificationAlert message with alarm/event information in XML format.
<EventNotificationAlert version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<ipAddress></ipAddress>
<ipv6Address></ipv6Address>
<portNo></portNo>
<protocol></protocol>
<macAddress></macAddress>
<channelID></channelID>
<dateTime></dateTime>
<activePostCount></activePostCount>
<eventType></eventType>
<eventState>

</eventState>
<eventDescription></eventDescription>
<...></...>
</EventNotificationAlert>
5.18 XML_EventTriggersCap
XML message about linkage capabilities of different alarm categories
<EventTriggersCap version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<DiskfullTriggerCap></DiskfullTriggerCap>
<DiskerrorTriggerCap></DiskerrorTriggerCap>
<NicbrokenTriggerCap></NicbrokenTriggerCap>
<IpconflictTriggerCap></IpconflictTriggerCap>
<IllaccesTriggerCap></IllaccesTriggerCap>
<BadvideoTriggerCap></BadvideoTriggerCap>
<VideomismatchTriggerCap></VideomismatchTriggerCap>
<IOTriggerCap></IOTriggerCap>
<LineDetectTriggerCap></LineDetectTriggerCap>
<RegionEntranceTriggerCap></RegionEntranceTriggerCap>
<RegionExitingTriggerCap></RegionExitingTriggerCap>
<LoiteringTriggerCap></LoiteringTriggerCap>
<GroupDetectionTriggerCap></GroupDetectionTriggerCap>
<RapidMoveTriggerCap></RapidMoveTriggerCap>
73
<ParkingTriggerCap></ParkingTriggerCap>

<UnattendedBaggageTriggerCap></UnattendedBaggageTriggerCap>
<AttendedBaggageTriggerCap></AttendedBaggageTriggerCap>
<FireDetectionTriggerCap></FireDetectionTriggerCap>
<FireDetectionCap></FireDetectionCap>
<StorageDetectionTriggerCap></StorageDetectionTriggerCap>
<ShipsDetectionTriggerCap></ShipsDetectionTriggerCap>
<ThermometryCap></ThermometryCap>
<VandalProofTriggerCap></VandalProofTriggerCap>
<BlackListTriggerCap></
BlackListTriggerCap>
<WhiteListTriggerCap></
WhiteListTriggerCap>
<AllVehicleListTriggerCap></OtherVehicleListTriggerCap>
<PeopleDetectionTriggerCap></PeopleDetectionTriggerCap>
<PIRAlarmCap></PIRAlarmCap>
<TamperDetectionTriggerCap></TamperDetectionTriggerCap>
<DefocusDetectionTriggerCap></DefocusDetectionTriggerCap>
<FaceDetectionTriggerCap></FaceDetectionTriggerCap>
<SceneChangeDetectionTriggerCap></SceneChangeDetectionTriggerCap>
<VandalProofAlarmCap></VandalProofAlarmCap>
<JudgmentTriggerCap></JudgmentTriggerCap>
<FightingTriggerCap></FightingTriggerCap>
<RisingTriggerCap></RisingTriggerCap>
<DozingTriggerCap></DozingTriggerCap>
<CountingTriggerCap></CountingTriggerCap>
<VideoLossTriggerCap></VideoLossTriggerCap>
<HideTriggerCap></HideTriggerCap>
<AlarmInTriggerCap></AlarmInTriggerCap>
<VehicleDetectionTriggerCap></VehicleDetectionTriggerCap>
<AudioExceptionCap></AudioExceptionCap>
<FiledDetectTriggerCap></FiledDetectTriggerCap>
<MotionDetectionTriggerCap></MotionDetectionTriggerCap>
<TemperatureCap></TemperatureCap>
<IntelligentTriggerCap></IntelligentTriggerCap>
<FaceContrastTriggerCap></
FaceContrastTriggerCap>
<PersonDensityDetectionTriggerCap></PersonDensityDetectionTriggerCap>
<PersonQueueDetectionTriggerCap></
PersonQueueDetectionTriggerCap>
<HumanRecognitionTriggerCap></HumanRecognitionTriggerCap>
<FaceSnapTriggerCap></FaceSnapTriggerCap>
<isSupportWhiteLightAction>

</isSupportWhiteLightAction>
<isSupportAudioAction>

</isSupportAudioAction>
<HFPDTriggerCap></HFPDTriggerCap>
<MixedTargetDetectionCap></MixedTargetDetectionCap>
74
<HVTVehicleDetectionTriggerCap></HVTVehicleDetectionTriggerCap>

<VCATriggerCap></VCATriggerCap>
<PIRCap></PIRCap>
<IllegalParkingTriggerCap></
IllegalParkingTriggerCap>
<PedestrianTriggerCap></
PedestrianTriggerCap>
<TrafficAccidentTriggerCap></
TrafficAccidentTriggerCap>
<ConstructionTriggerCap></
ConstructionTriggerCap>
<RoadBlockTriggerCap></
RoadBlockTriggerCap>
<AbandonedObjectTriggerCap></AbandonedObjectTriggerCap>
<ParallelParkingTriggerCap></
ParallelParkingTriggerCap>
<ParkingStateTriggerCap></ParkingStateTriggerCap>
<CongestionTriggerCap></
CongestionTriggerCap>
<IntersectionAnalysisCap></
IntersectionAnalysisCap>
<ShipsFlowDetectionTriggerCap></
ShipsFlowDetectionTriggerCap>
<dredgerDetectionTriggerCap></
dredgerDetectionTriggerCap>
<voltageInstableTriggerCap></
voltageInstableTriggerCap>
<HighHDTemperatureTriggerCap></
HighHDTemperatureTriggerCap>
<LowHDTemperatureTriggerCap></
LowHDTemperatureTriggerCap>
<HDImpactTriggerCap></HDImpactTriggerCap>
<HDBadBlockTriggerCap></
HDBadBlockTriggerCap>
<SevereHDFailureTriggerCap></
SevereHDFailureTriggerCap>
<HUMANATTRIBUTECap></HUMANATTRIBUTECap>
<HumanAttributeTriggerCap></
HumanAttributeTriggerCap>
<BlackListFaceContrastTriggerCap></BlackListFaceContrastTriggerCap>
<FaceLibTriggerCap></FaceLibTriggerCap>
<SafetyHelmetDetectionTriggerCap></SafetyHelmetDetectionTriggerCap>
<VibrationDetectionTriggerCap></RadarLineDetectionTriggerCap>
<RadarFieldDetectionTriggerCap></RadarFieldDetectionTriggerCap>
75
<HBDLibTriggerCap></

HBDLibTriggerCap>
<FaceThermometryCap></FaceThermometryCap>
<NoMaskDetectionTriggerCap></NoMaskDetectionTriggerCap>
<TMPATriggerCap></TMPATriggerCap>
<FireEscapeDetectionTriggerCap></FireEscapeDetectionTriggerCap>
<TakingElevatorDetectionTriggerCap></TakingElevatorDetectionTriggerCap>
<RuleTriggerCap>
<isSupportCityManagement>

</isSupportCityManagement>
</RuleTriggerCap>
<ThermalCalibrationFileExceptionCap></ThermalCalibrationFileExceptionCap>
</EventTriggersCap>
See Also
XML_EventTriggerCapType
5.19 XML_EventTriggerCapType
XML message about capability of alarm linkage action types
<EventTriggerCapType version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<isSupportCenter></isSupportCenter>
<isSupportRecord></isSupportRecord>
<isSupportMonitorAlarm></isSupportMonitorAlarm>
<isSupportBeep></isSupportBeep>
<isSupportIO></isSupportIO>
<isSupportFTP></isSupportFTP>
<isSupportEmail></isSupEmail>
<isSupportLightAudioAlarm></isSupportLightAudioAlarm>
<isSupportFocus></isSupportFocus>
<isSupportPTZ></isSupportPTZ>
<maxPresetActionNum>

</maxPresetActionNum>
<maxPatrolActionNum>
</maxPatrolActionNum>
<maxPatternActionNum>
</maxPatternActionNum>
<isSupportTrack></isSupportTrack>
<isSupportWhiteLight>
76


</isSupportWhiteLight>
<isSupportCloud></isSupportCloud>
<targetNotificationInterval max="1000" min="0" default="30"></targetNotificationInterval>
<direction opt="both,forward,reverse"></direction>
<presetDurationTime min="" max=""></presetDurationTime>
<isSupportSMS></isSupportSMS>
<maxCellphoneNum></maxCellphoneNum>
<isSupportOSD></isSupportOSD>
<isSupportAudio></isSupportAudio>
<AudioAction>
<audioTypeList>
<audioType>
<audioID></audioID>
<audioDescription></alarmTimes>
</AudioAction>
<isSupportSMS></isSupportSMS>
<maxCellphoneNum></maxCellphoneNum>
<isNotSupportCenterModify></
isNotSupportCenterModify>
<isSupportMessageConfig>

</isSupportMessageConfig>
<isSupportAnalogOutput></
isSupportAnalogOutput>
<isSupportIOOutputUnify></
isSupportIOOutputUnify>
<isSupportFaceContrast></
isSupportFaceContrast>
<isSupportSiren></isSupportSiren>
<isSupportOutput></isSupportOutput>
</EventTriggerCapType>
5.20 XML_IntelliCap
XML message about intelligent capability
77
<IntelliCap version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">

<isFaceSupport></isFaceSupport>
<isBehaviorSupport></isBehaviorSupport>
<isLineDetectionSupport></
isLineDetectionSupport>
<isFieldDetectionSupport></
isFieldDetectionSupport>
<isRegionEntranceSupport></
isRegionEntranceSupport>
<isRegionExitingSupport></
isRegionExitingSupport>
<isLoiteringSupport></isLoiteringSupport>
<isGroupSupport></isGroupSupport>
<isRapidMoveSupport></
isRapidMoveSupport>
<isParkingSupport></isParkingSupport>
<isUnattendedBaggageSupport></
isUnattendedBaggageSupport>
<isAttendedBaggageSupport></
isAttendedBaggageSupport>
<isTeacherSupport></
isTeacherSupport>
<isStudentSupport></
isStudentSupport>
<isCombinedSupport></isCombinedSupport>
<isTrafficSupport></isTrafficSupport>
<RestoreLib>
<libName opt="studentsStoodUp,peopleCounting,shipDetection"></libName>
</RestoreLib>
<RestoreDefParamForbid>

</RestoreDefParamForbid>
<RestoreAlgLibParam>

<libName opt="faceSnap,HMS,behaviorAnalysis"></libName>
</RestoreAlgLibParam>
<isFaceCaptureStatisticsSupport></isFaceCaptureStatisticsSupport>
<isSupportPersonQueueDetection></
isSupportPersonQueueDetection>
<isSupportIntersectionAnalysis>

</isSupportIntersectionAnalysis>
<isSupportCityManagement></isSupportCityManagement>
<mixedTargetDetectionWithoutAttribute></mixedTargetDetectionWithoutAttribute>
<isSupportUploadFacePictureByForm></isSupportUploadHumanPictureByForm>
<isSupportMisinfoFilterStatisticalMode></isSupportMisinfoFilterStatisticalMode>
<isSupportFaceScore></
isSupportFaceScore>
<HumanRecognitionModeSearchCap>
<searchTargetsNumMax></searchTargetsNumMax>
<HumanMode>
<searchCond opt="age_group,gender,jacet_color,glass,bag,ride,unlimit"/>
<similarity min="0.0" max="100.0"/>
</HumanMode>
<HumanInfo>
<age_group opt="child,infant,kid,middle,middleAged,old,prime,teenager,unknown,young">

</age_group>
<gender opt="female,male,unknown"></gender>
<jacet_color
opt="black,black,blue,brown,cyan,deepBlue,deepGray,gray,green,mixture,orange,pink,purple,red,silver,unknown,whit
e,yellow">

</jacet_color>
<glass opt="yes,no,unknown,sunglasses"></glass>
<bag opt="yes,no,unknown"></bag>
<ride opt="yes,no,unknown"></ride>
</HumanInfo>
<positive opt="true,false"/>
<eventType opt="unlimit,humanRecognition">

</eventType>
<isSupportMultiChannelSearch>

</isSupportMultiChannelSearch>
<isSupportTotalSearchResult>
</searchTargetsNumMax>
<eventType opt="unlimit,vehicleBlackList,vehicleWhiteList"/>
<VehicleMode>
<searchCond opt="licensePlate,vehicleLogo,vehicleSubLogoRecog,vehicleType,vehicleColor,unlimit"/>
<similarity min="0.0" max="100.0"/>
</VehicleMode>
<isSupportMultiChannelSearch>

</isSupportMultiChannelSearch>
79
<isSupportTotalSearchResult>

<isSupportTrigger opt="false,true"></isSupportTrigger>
<SearchCondition>
<startTime></startTime>
<endTime></endTime>
</SearchCondition>
</FaceContrastAnalyzeCap>
<FramesPeopleCountingCap>
<Statistics>
<SearchCondition>
<startTime></startTime>
<endTime></endTime>
</SearchCondition>
</Statistics>
<MaskRegion>
<maxRegionNum></maxRegionNum>
<Region>
<vertexNum min="3" max="10"></vertexNum>
</Region>
</MaskRegion>
</FramesPeopleCountingCap>
<FaceContrastPersonInfoExtend>
<personInfoCap>
<maxPersonInfo min="0" max="4">

</maxPersonInfo>
</personInfoCap>
<personInfoFDlibCap>
<maxPersonInfo min="0" max="4">

</maxPersonInfo>
</personInfoFDlibCap>
</FaceContrastPersonInfoExtend>
<isSupportSafetyHelmetDetection>

</isSupportSafetyHelmetDetection>
<isSupportDistanceRecognition></
isSupportDistanceRecognition>
<isSupportATM></isSupportATM>
<isSupportFaceTemperature></isSupportFaceTemperature>
<isSupportFireEscapeDetectionSearch>

</isSupportFireEscapeDetectionSearch>
<isSupportTakingElevatorDetectionSearch>
80

</isSupportTakingElevatorDetectionSearch>
<isSupportCityManagementSearch>

</isSupportCityManagementSearch>
<isSupportSafetyHelmetDetectionSearch>

</isSupportSafetyHelmetDetectionSearch>
<isSupportFramesPeopleCountingSearch>
true
</isSupportFramesPeopleCountingSearch>
<isSupportChannelPollingSchedules>

</isSupportChannelPollingSchedules>
<AnalysisImageFaceCap>

<modeling opt="false"></
modeling>
</AnalysisImageFaceCap>
</IntelliCap>
5.21 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>

</requestURL>
<statusCode>

</statusCode>
<statusString>

</statusString>
<subStatusCode>

</subStatusCode>
<MErrCode>

</MErrCode>
<MErrDevSelfEx>

</MErrDevSelfEx>
</ResponseStatus>
82
Appendix A. Data Structure
A.1 DATE_TIME
Date and Time Structure

year short Year.
month short Month.
dayOfWeek short Days of the week: 0-Sunday, 1-
Monday, 2-Tuesday, 3-
Wednesday, 4-Thursday, 5-
Friday, 6-Saturday.
day short Day.
hour short Hour.
minute short Minute.
second short Second.
milliSecond short Millisecond.
A.2 NET_DVR_DEVICEINFO_V30
Device parameter structure (V30).
Device Parameter Structure (V30)

sSerialNumber BYTE Device serial No.
byAlarmInPortNum BYTE Number of analog alarm inputs
byAlarmOutPortNum BYTE Number of analog alarm outputs
byDiskNum BYTE Number of HDDs
byDVRType BYTE Device type
byChanNum BYTE Number of analog channels
83

byStartChan BYTE Start No. of analog channel, which starts from
1.
byAudioChanNum BYTE Number of two-way audio channels
byIPChanNum BYTE Number of digital channels, low 8-bit.
byZeroChanNum BYTE Number of channel-zero
byMainProto BYTE Transmission protocol type of main stream: 0-
private protocol (default), 1-RTSP, 2-private
protocol+RTSP
bySubProto BYTE Transmission protocol type of sub-stream: 0-
private protocol (default), 1-RTSP, 2-private
protocol+RTSP
bySupport BYTE 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.
● bySupport&0x1: whether supports VCA
search.
● bySupport&0x2: whether supports backup.
● bySupport&0x4: whether supports getting
encoding parameters.
● bySupport&0x8: whether supports dual-NIC.
● bySupport&0x10: whether supports remote
SADP.
● bySupport&0x20: whether supports RAID
card.
● bySupport&0x40: whether supports
searching in IPSAN directory.

● bySupport&0x80: whether supports RTP over
RTSP.
bySupport1 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.
● bySupport1&0x1: whether supports SNMP
with version 30.

● bySupport1&0x2: whether supports playback
and downloading video files.
84

● bySupport1&0x4: whether supports setting
the arming priority.
● bySupport1&0x8: whether supports
extending the arming time period.
multiple HDDs (more than 33).
● bySupport1&0x20: whether supports RTP
over RTSP.
● bySupport1&0x80: whether supports license
plate recognition alarm.
● bySupport2&0x1: whether supports getting
stream via URL.

● bySupport2&0x2: whether supports FTP with
version 40.
● bySupport2&0x4: whether supports ANR.
device status.
encrypting stream.
wDevType WORD Device model
supported, while, if the result is 1, it indicates
that the capability is supported.
● bySupport3&0x1: whether supports multi-
stream.
configuring by group (e.g., image, alarm

input, alarm output, user, device status, JPEG
picture capture, continuous and scheduled
capture, .HDD group management, and so
on).
stream via DDNS.
85

byMultiStreamProto BYTE Whether supports multi-stream, if the result of
bitwise operation is 0, it refers to not support, if
the result is 1, it refers to support.
● byMultiStreamProto&0x1: whether supports
third-stream.
● byMultiStreamProto&0x2: whether supports
fourth-stream.
● byMultiStreamProto&0x40: whether
supports main stream.

● byMultiStreamProto&0x80: 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&0x01: whether all stream types
support RTSP and private protocol.

● bySupport4&0x02: whether the device
supports transmitting form format data via

API (NET_DVR_STDXMLConfig).
● bySupport4&0x10: whether supports loading
network disk by domain name.

byLanguageType BYTE Supported language types, if the result of
bitwise operation is 0, it refers to not support, if
the result is 1, it refers to support.
● byLanguageType ==0: this field is not
supported by device.
● byLanguageType&0x1: whether supports
Chinese.
● byLanguageType&0x2: whether supports
English.
byVoiceInChanNum BYTE Number of audio input channels
86

byStartVoiceInChanNo BYTE Start No. of audio input channel, 0-invalid.
byRes3 Array of BYTE Reserved, set to 0.
byMirrorChanNum BYTE Number of mirror channels
wStartMirrorChanNo WORD Start No. of mirror channel
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
A.3 NET_DVR_DEVICEINFO_V40
Device Parameter Structure (V40)

struDeviceV30 NET_DVR_DEVICEINFO Device parameters
_V30
bySupportLock BYTE Whether supports locking function: 1-support.
byRetryLoginTime BYTE Remaining login attempts, it is valid when the
user name or password is incorrect and the
bySupportLock is 1.
byPasswordLevel BYTE Password strength: 0-invalid, 1-default
password, 2-valid password, 3-risky password.
For default password or risky password, the
users are reminded to change password.
byProxyType BYTE Proxy type: 0-no proxy, 1-standard proxy, 2-
EHome proxy.
87

dwSurplusLockTime DWORD Remaining locking time, unit: second. It is valid
only when bySupportLock is 1. During the
locing time, if the user try to log in to again, the
remaining locking time will resume to 30
minutes.
byCharEncodeType BYTE Character encodings. 0-no decoding
information, 1-GB2312 (Simplified Chinese), 2-
GBK, 3-BIG5 (Traditional Chinese), 4-Shift_JIS
(Japanese), 5-EUC-KR (Korean), 6-UTF-8, 7-
ISO8859-1, 8-ISO8859-2, 9-ISO8859-3, …, 21-
ISO8859-15 (Western European)
bySupportDev5 BYTE Whether to support getting the parameters of
devices that support HCNetSDK version 5.0 or
above, the size of device name and type name
are extended to 64 bytes.
bySupport BYTE Whether it supports uploading changes, it
depends on the result of bitwise AND (&)
operation: 0-not support, 1-support. The result
of bySupport&0x1 indicates that this member is
reserved; the result of bySupport&0x2 indicates
that whether it supports uploading changes: 0-
not support, 1-support. This member is the
capability set extension.
byLoginMode BYTE Login mode: 0-login via private protocol, 1-login
via text protocol. For private protocol, the
default login port number is 8000, and for text
protocol, the default login port number is 80 or
443.
dwOEMCode DWORD OEM code.
iResidualValidity int Remaining valid days of the user's password,
unit: day. If the negative number is returned, it
indicates that the password being used has
expired. For example, if -3 is returned, it
indicates that the password being used has
expired for three days.
byResidualValidity BYTE Whether the member iResidualValidity is valid:
0-invalid, 1-valid.
88

bySingleStartDTalkCha BYTE Start channel No. for connecting independent
n audio tracks to the device. The value 0 is
reserved and invalid. The channel No. of audio
tracks cannot start from 0.
bySingleDTalkChanNu BYTE Total number of channels of the device
ms connected with independent tracks, 0-not
support.
byPassWordResetLevel BYTE Whether to prompt the non-admin user to
change the password: 0 (invalid), 1 (If the
administrator creates a non-admin user account
with an initial password, the non-admin user
will be prompted "Please change the initial
password" each time he/she logs in to the
device until he/she changes the initial
password), 2(If the non-admin user's password
has been changed by the administrator, the
non-admin user will be prompted "Please set a
new password" each time he/she logs in to the
device until he/she changes the password).
bySupportStreamEncry BYTE Whether it supports stream encryption, it
pt depends on the result of bitwise AND (&)
operation: 0-no, 1-yes. The result of
bySupportStreamEncrypt&0x1 indicates
whether to support RTP/TLS streaming, the
result of bySupportStreamEncrypt&0x2
indicates whether to support SRTP/UDP
streaming, and the result of
bySupportStreamEncrypt&0x4 indicates
whether to support SRTP/MULTICAST
streaming.
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:
89
○ 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
contains three kinds of the character types.

● For login via text protocol, the following parameters are not supported: bySupportLock,
byRetryLoginTime, byPasswordLevel, byProxyType, dwSurplusLockTime, byCharEncodeType,
and bySupportDev5.
A.4 NET_DVR_INIT_CFG_ABILITY
Initialization Capability Structure

enumMaxLoginUsersN INIT_CFG_MAX_NUM Maximum number of users can log in, see
um details below:
enum _INIT_CFG_MAX_NUM_{
INIT_CFG_NUM_2048 = 2048,
INIT_CFG_NUM_10240 = 10240,
INIT_CFG_NUM_15360 = 15360,
INIT_CFG_NUM_20480 = 20480
}INIT_CFG_MAX_NUM
enumMaxAlarmNum INIT_CFG_MAX_NUM Maximum number of alarm channels, see

details below:
enum _INIT_CFG_MAX_NUM_{
INIT_CFG_NUM_10240 = 10240,
INIT_CFG_NUM_15360 = 15360,
INIT_CFG_NUM_20480 = 20480
}INIT_CFG_MAX_NUM
byRes Array of BYTE Reserved, set to 0.
90
Remarks
By default, up to 2048 channels are supported. More channels require higher computer
performance and network bandwidth.
See Also
NET_DVR_SetSDKInitCfg
A.5 NET_DVR_LOCAL_SDK_PATH
Path Information Structure for Loading Component Libraries

sPath Array of char Component libraries' addresses
byRes Array of BYTE Reserved.
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.
A.6 NET_DVR_USER_LOGIN_INFO
Structure About Login Parameters

sDeviceAddress char Device IP address, or domain name.
byUseTransport BYTE Enable capability transmission or not: 0-no
(default), 1-yes.
wPort WORD Device port number, e.g., 8000 (when login by
private protocol), 80 (when login by text
protocol).
sUserName char User name for logging in to device.
sPassword char Login password.
cbLoginResult fLoginResultCallBack Callback function used to return login status, it
is valid only when bUseAsynLogin is "1".
91

pUser void* User data.
bUseAsynLogin BOOL Whether to enable asynchronous login: 0-no, 1-
yes.
byProxyType BYTE Proxy server type: 0-no proxy, 1-standard proxy,
2-EHome proxy.
byUseUTCTime BYTE 0-not convert (default), 1-input or output UTC
time, 2-input or output local time.
byLoginMode BYTE Login mode: 0-login by private protocol, 1-login
by text protocol, 2-self-adaptive (it is available
when the protocol type supported by device is
unknown, and this mode does not support
asynchronous login).
byHttps BYTE Whether to enable TLS for login (by private
protocol or by text protocol): 0-no, 1-yes, 2-self-
adaptive (which is usually used when the
protocol type supported by device is unknown.
Both HTTP and HTTPS requests will be sent).
iProxyID LONG Proxy server No.
byVerifyMode BYTE Whether to enable verification mode: 0-no, 1-
bidirectional verification (currently not
available), 2-unidirectional verification (it is
valid when byLoginMode is 0 and byHttps is 1);
when byVerifyMode is 0, CA certificate is not
required, when byVerifyMode is 2, you should
call NET_DVR_SetSDKLocalCfg to load CA
certificate, and the enumeration value is "NET_
SDK_LOCAL_CFG_CERTIFICATION".
byRes3 BYTE[] Reserved, the maximum length is 119 bytes.
A.7 NET_SDK_CALLBACK_STATUS_NORMAL
92
Enumeration About Persistent Connection Status
Enumeration Type Marco Definition Description

Value
NET_SDK_CALLBACK_STATUS_ 1000 Succeeded.
SUCCESS
NET_SDK_CALLBACK_STATUS_ 1001 Connecting. The lpBuffer is 4-byte
PROCESSING status.
NET_SDK_CALLBACK_STATUS_ 1002 Failed. The lpBuffer is the value of
FAILED 4-byte status and 4-byte error
code.
A.8 NET_VCA_RECT
Structure About Rectangle Region Coordinate Parameters

fX float X-coordinate of frame's upper-left corner, it
ranges from 0.000 to 1.
fY float Y-coordinate of frame' upper-left corner, it
ranges from 0.000 to 1.
fWidth float Frame width, it ranges from 0.000 to 1.
fHeight float Frame height, it ranges from 0.000 to 1.
A.9 NET_DVR_CRUISECHAN_INFO
Structure about The Information of Channel That Called Patrol

dwEnableCruiseChan DWORD Channel that called patrol.
dwCruiseNo DWORD Patrol No., 0xfffffff-invalid.
93
A.10 NET_DVR_EVENT_SCHEDULE
Arming Schedule Parameter Structure

dwSize DWORD Structure size
struAlarmTime Array of Arming schedule, 7 days per week, 8 time
NET_DVR_SCHEDTIME periods per day
struHolidayAlarmTime Array of Holiday arming schedule, see details in the
NET_DVR_SCHEDTIME structure .
byRes BYTE Reserved.
A.11 NET_DVR_EVENT_TRIGGER
Structure About Event Linkage Configuration

dwSize DWORD Structure size.
struHandleException Array of Exception handling mode
NET_DVR_HANDLEEXC
EPTION_V41
dwRelRecordChan Array of DWORD Actually triggered video channel, represented
by value, read starts from 0, and it is invalid
after the value of 0xffffffff being read.
struPresetChanInfo Array of Information of channel that called preset
NET_DVR_PRESETCHA
N_INFO
struCruiseChanInfo Array of Information of channel that called patrol
NET_DVR_CRUISECHA
N_INFO
struPtzTrackInfo Array of Information of channel that called pattern
NET_DVR_PTZTRACKC
HAN_INFO
94

byDirection Array of BYTE Triggering direction: 0-reserved, 1-all, 2-
forward, 3-backward
szFDID Char Face picture library ID
byRes2 Array of BYTE Reserved
A.12 NET_DVR_HANDLEEXCEPTION_V41
Exception Information Structure

dwHandleType DWORD Handling types, see details below:
● 0x00: no response
● 0x01: display alarm on monitor screen
● 0x02: audio warning
● 0x04: upload to center
● 0x08: trigger alarm output
● 0x10: send picture with JPEG format by e-
mail
● 0x20: trigger wireless sound and light alarm
● 0x40: trigger e-map (supported by PCNVR
only)
● 0x200: capture picture and upload to FTP
● 0x400: focus mode linkage (for defocus
detection)
● 0x800: PTZ linkage (speed dome tracks the
target)
● 0x1000: capture picture and upload to cloud
storage.
● 0x10000: message alarm
E.g., if dwHandleType is 0x01|0x04, it indicates

that the alarm information will be displayed on
monitor screen and uploaded to alarm center
when the alarm is triggered.
dwMaxAlarmOutChan DWORD Manixmum number of alarm outputs (read
nelNum only) supported by the device.
95

dwRelAlarmOut Array of DWORD Alarm output No. triggered by alarm, which
starts from 0, 0xffffffff-invalid. E.g.
byRelAlarmOut[i]==3 indicates that the alarm
output No.4 is triggered.
A.13 NET_DVR_MIME_UNIT
Input Content Details Structure of Message Transmission API


szContentType Array of char Content type (corresponds to Content-Type
field in the message), e.g., text/json. text/xml,
and so on. The content format must be
supported by HTTP.
szName Array of char Content name (corresponds to name field in the
message), e.g., name="upload".
szFilename Array of char Content file name (corresponds to filename
field in the message), e.g., filename="C:\Users
\test\Desktop\11.txt".
dwContentLen DWORD Content size
pContent char* Data point
bySelfRead BYTE 0-External file, 1-Internal data, whose address is
specified by szFilename.
byRes Array of BYTE Reserved. Set to 0. Maximum: 15 bytes.
See Also
NET_DVR_XML_CONFIG_INPUT
A.14 NET_DVR_PRESETCHAN_INFO
96
Preset Information Structure

dwEnablePresetChan DWORD Channel that called preset.
dwPresetPointNo DWORD Called preset No., 0xfffffff-not call preset.
A.15 NET_DVR_PTZTRACKCHAN_INFO
Pattern Information Structure

dwEnablePtzTrackChan DWORD Channel that called the pattern.
dwPtzTrackNo DWORD Called pattern No., 0xfffffff-invalid.
A.16 NET_DVR_SCHEDTIME
Structure About Start and End Time Parameters

byStartHour BYTE Start time: hour.
byStartMin BYTE Start time: minute.
byStopHour BYTE End time: hour.
byStopMin BYTE End time: minute.
A.17 NET_DVR_STD_ABILITY
97
Input and Output Parameter Structure for Getting Capabilities

lpCondBuffer LPVOID Condition parameters (ASCII character format),
e.g., the channel No., it can be set to "null".
dwCondSize DWORD Buffer size of condition parameters.
lpOutBuffer LPVOID Output parameters buffer (the parameter is
returned in the message with XML format), it
cannot be set to "null.
dwOutSize DWORD Output buffer size.
lpStatusBuffer LPVOID Get the returned status parameters
( XML_ResponseStatus ) when getting
capabilities failed. It can be set to null.
dwStatusSize DWORD Status buffer size.
dwRetSize DWORD Obtained data size (if the capability is obtained,
the value refers to the size of lpOutBuffer; if
getting failed, the value refers to the size of
lpStatusBuffer).
byRes Array [BYTE] Reserved. The maximum size is 32 bytes.
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.
A.18 NET_DVR_STD_CONFIG
Structure About Configuring Input and Output Parameters

lpCondBuffer LPVOID Condition parameters, e.g., channel No., it can
be set to "NULL".
dwCondSize DWORD Size of buffer for storing condition parameters
lpInBuffer LPVOID Input parameters (a structure)
98

dwInSize DWORD Size of buffer for storing input parameters
lpOutBuffer LPVOID Output parameters (a structure)
dwOutSize DWORD Size of buffer for storing output parameters
lpStatusBuffer LPVOID Returned status parameters in XML format, it
can be set to NULL.
dwStatusSize DWORD Size of buffer for storing status parameters
lpXmlBuffer LPVOID Request or response message in XML format, it
is valid when byDataType is 1.
dwXmlSize DWORD Size of memory pointed by lpXmlBuffer.
byDataType BYTE Input or output parameter type: 0-valid when
the input or output parameters is a structure; 1-
valid when the input or output parameters is a
XML message.
byRes Array [BYTE] Reserved, set to 0. The maximum size is 32
bytes.
A.19 NET_DVR_XML_CONFIG_INPUT
Input Parameter Structure of Message Transmission API (NET_DVR_STDXMLConfig)

lpRequestUrl void* Request URL (command) for implement
different functions, and it is in string format.
dwRequestUrlLen DWORD Request URL size.
lpInBuffer void* Buffer for storing input parameters (request
messages), see the input content details
structure in NET_DVR_MIME_UNIT .
dwInBufferSize DWORD Input buffer size.
dwRecvTimeOut DWORD Receiving timeout, unit: ms, 0-5000ms (default).
99

byForceEncrpt BYTE Whether to enable force encryption (the
messages will be encrypted by AES algorithm
for transmission): 0-no, 1-yes.
byNumOfMultiPart BYTE Number of message segments: 0-invalid; other
values-number of message segments, which is
transmitted by the parameter lpInBuffer in the
structure NET_DVR_MIME_UNIT .
Related API
NET_DVR_STDXMLConfig
A.20 NET_DVR_XML_CONFIG_OUTPUT
Output Parameter Structure of Message Transmission API


lpOutBuffer void* Buffer for storing output parameters (response
messages), which is allocated when passing
through URL by GET method.
dwOutBufferSize DWORD Output buffer size.
dwReturnedXMLSize DWORD Actual size of response message.
lpStatusBuffer void* Response status (ResponseStatus message).
This parameter will not be assigned if
performing GET operation succeeded, and you
can also set it to "NULL" if not required.
dwStatusSize DWORD Size of response status buffer.
lpDataBuffer HPR_VOIDPTR Buffer for transmitted data. This parameter is
valid when the value of byNumOfMultiPart is
larger than 0.
100

byNumOfMultiPart HPR_UINT8 Number of parts that the message is divided
into.
byRes BYTE Reserved, set to 0.
[23]
Related API
NET_DVR_STDXMLConfig
A.21 NET_ALARM_CVR_SUBINFO_UNION
Union about CVR Alarm Information

byLen BYTE[] Union size, the maximum array length is 492
bytes.
struRecordLost NET_ALARM_RECORD Video loss alarm information, the value of
FILE_LOSS dwAlarmType in
NET_DVR_ALARMINFO_DEV_V40 is 8.
struStreamException NET_ALARM_STREAM Streaming exception alarm information, the
_EXCEPTION value of dwAlarmType in
struResourceUsage NET_ALARM_RESOUR Resource usage alarm information, the value of
CE_USAGE dwAlarmType in
struRecordException NET_ALARM_RECORD Recording exception alarm information, the
_EXCEPTION value of dwAlarmType in
A.22 NET_ALARM_RECORD_EXCEPTION
101
Structure about Recording Exception Alarm Information

byReason BYTE Exception reason: 0-video volume full, 1-video
volume exception, 2-no available video volume.
byRes1 BYTE[] Reserved, set to 0. The maximum array length is
3 bytes.
sVolumeName BYTE[] Video volume name, the maximum array length
is "MAX_VOLUMENAME_LEN" (32 bytes).
dwVolumeID DWORD Video volume ID, or HDD No.
byRes BYTE[] Reserved, set to 0. The maximum array length is
452 bytes.
A.23 NET_ALARM_RECORDFILE_LOSS
Structure about Video Loss Alarm Information

struInspectStart NET_DVR_TIME_EX Start time of video loss check.
struInspectEnd NET_DVR_TIME_EX End time of video loss check.
struIP NET_DVR_IPADDR_UN IP address of video loss channel.
ION
dwChanNo DWORD Channel No.
dwIDIndex DWORD Encoder ID.
sName BYTE[] Encoder name, the maximum array length is
"STREAM_ID_LEN" (32 bytes).
struLossStartTime NET_DVR_TIME_EX Start time of video loss.
struLossEndTime NET_DVR_TIME_EX End time of video loss.
dwLostNum DWORD Number of lost video files, 0xffffffff-all video
files are lost.
240 bytes.
102
A.24 NET_ALARM_RESOURCE_USAGE
Structure about Resource Usage Alarm Information

byLevel BYTE Usage alarm level: 0-normal, 1-alarm level 1, 2-
alarm level 2, 3-alarm level 3.
491 bytes.
A.25 NET_ALARM_STREAM_EXCEPTION
Structure about Video Exception Alarm Information

struIP NET_DVR_IPADDR_UN IP address of video exception channel.
ION
dwChanNo DWORD Channel No.
dwIDIndex DWORD Encoder ID.
sName BYTE[] Encoder name, the maximum array length is
"STREAM_ID_LEN" (32 bytes).
byExceptionCase BYTE Exception reason: 0-data writing exception, 1-
network exception.
307 bytes.
A.26 NET_DVR_ALARMER
103
Alarm Device Information Structure

byUserIDValid BYTE Whether the user ID is valid: 0-no, 1-yes
bySerialValid BYTE Whether the serial No. is valid: 0-no, 1-yes
byVersionValid BYTE Whether the version No. is valid: 0-no, 1-yes
byDeviceNameValid BYTE Whether the device name is valid: 0-no, 1-yes
byMacAddrValid BYTE Whether the MAC address is valid: 0-no, 1-yes
byLinkPortValid BYTE Whether the login port No. is valid: 0-no, 1-yes
byDeviceIPValid BYTE Whether the device IP address is valid: 0-no, 1-
yes
bySocketIPValid BYTE Whether the Socket IP address is valid: 0-no, 1-
yes
lUserID LONG Value returned by NET_DVR_Login_V40 , it is
valid when arming.
sSerialNumber Array of BYTE Serial No.
dwDeviceVersion DWORD Version information
sDeviceName Array of char Device name
byMacAddr Array of BYTE MAC address
wLinkPort WORD Device communication port No.
sDeviceIP Array of char Device IP address
sSocketIP Array of char Socket IP address when actively uploading
alarm.
byIpProtocol BYTE Network protocol: 0-IPv4, 1-IPv6
A.27 NET_DVR_ALARMINFO_DEV
104
Device Alarm Information Structure
Memeber Data Type Description

dwAlarmType DWORD Alarm types: 0-alarm input alarm of encoder, 1-
second private volume damaged, 2-NVR
disconnected, 3-encoder exception, 4-system
clock exception, 5-the remaining capacity of the
recording volume is too low, 6-motion detection
alarm of encoder or encoding channel, 7-video
tampering alarm of encoder or encoding
channel.
struTime Alarm time
dwNumber DWORD Number of alarm triggered channels.
pNO WORD* Channel No. or disk No., which ranges from 0 to
65535.
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.
A.28 NET_DVR_ALARMINFO_DEV_V40
Structure about CVR Alarm Information

dwAlarmType DWORD Alarm categories: 0-alarm input alarm of
encoder, 1-second private volume damaged, 2-
NVR disconnected, 3-encoder exception, 4-
system clock exception, 5-the remaining
capacity of the recording volume is too low, 6-
motion detection alarm of encoder or encoding
channel, 7-video tampering alarm of encoder or
encoding channel, 8-video loss alarm, 9-real-
time health monitoring alarm, 10-usage alarm,
105

11-CVR exception recovered, 12-recording
exception.
struTime NET_DVR_TIME Alarm time
uSubAlarmInfo NET_ALARM_CVR_SU CVR alarm information structure, and it is valid
BINFO_UNION when the alarm type is 8, 9, 10, and 12.
byRes Array of BYTE Reserved, set to 0. The maximum size is 256
bytes.
dwNumber DWORD Number of alarm triggered channels.
pNO WORD* Channel No. or disk No., which ranges from 0 to
65535.
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.
A.29 NET_DVR_ALARMINFO_V30
Structure About Uploaded Alarm Information

dwAlarmType DWORD Alarm types: 0-alarm input alarm of encoder, 1-
second private volume damaged, 2-NVR
disconnected, 3-encoder exception, 4-system
clock exception, 5-the remaining capacity of the
recording volume is too low, 6-motion detection
alarm of encoder or encoding channel, 7-video
tampering alarm of encoder or encoding
channel, 8-video loss alarm, 9-real-time health
monitoring alarm, 10-usage alarm, 11-CVR
exception recovered, 12-recording exception.
dwAlarmInputNumber DWORD Alarm input No., it is valid when alarm type is 0
or 23
byAlarmOutputNumbe Array of BYTE The triggered alarm output No. E.g.
r dwAlarmOutputNumber[0]==1 indicates that
106

alarm output No.1 is triggered;
dwAlarmOutputNumber[1]==1 indicates that
alarm output No.2 is triggered.
byAlarmRelateChannel Array of BYTE The triggered recording channel No.: 0-not
triggered, 1-triggered. E.g.
dwAlarmRelateChannel[0]==1 indicates that the
channel No.1 is triggered to record.
byChannel Array of BYTE Alarm channel, it is valid when alarm type is 2,
3, 6, 9, 10 or 11. E.g. dwChannel[0]==1 indicates
that the channel No. is in alarm.
byDiskNumber Array of BYTE Alarm HDD, it is valid when alarm type is 1, 4, or
5. E.g. dwDiskNumber [0]==1 indicates that the
HDD No.1 is abnormal.
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.
A.30 NET_DVR_ALARMINFO_V40
Structure About Uploaded Alarm Information

struAlarmFixedHeader NET_DVR_ALRAM_FIX Constant content in alarm information, see
ED_HEADER details in the structure .
pAlarmData DWORD* Variable content in alarm information
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:
107
Table A-1 Relations Between pAlarmData and dwAlarmType

dwAlarmType Description pAlarmData
0, 23 Alarm input alarm, pulse alarm dwTrigerAlarmOutNum*(DWOR
D) Alarm output No.,
+dwTrigerRecordChanNum*(DW
ORD) Channel No.
2, 3, 6, 9, 10, 11, 13, 15, Video loss, motion detection, dwAlarmChanNum*(DWORD)
16, 19 video tampering alarm, video channel No.
exception, recording exception,
scene change, resolution
mismatched, VCA detection, PoE
power supply exception, audio
loss
1, 4, 5 HDD full, HDD uninitialized, dwAlarmHardDiskNum*(DWOR
writing to HDD failed D) HDD No.
7, 8, 12, 17, 18, 24, 25, 26 Standard mismatches, invalid None
login, array exception, education
sharing system alarm, two-way
audio request alarm, face library
HDD exception, face library
changed, picture changed in face
picture library
A.31 NET_DVR_ALRAM_FIXED_HEADER
Structure About Constant Alarm Information

dwAlarmType DWORD Alarm information type: 0-alarm input alarm, 1-
HDD full, 2-video loss, 3-motion detection, 4-
HDD unformatted, 5-writing to HDD failed, 6-
video tampering alarm, 7-standard mismatched,
8-invalid login, 9-video exception, 10-recording
exception, 11-scene change, 12-RAID exception,
13-resolution mismatched, 15-VCA detection,
16- PoE power supply exception, 17-education
sharing system alarm, 18-two-way audio
request alarm, 23-pulse alarm, 24-face picture
108

library HDD exception, 25-face picture library
changed, 26-picture of face picture library
changed, 27-POC exception, 28-camera FOV
exception, 30-no SD card, 31-supply voltage
exception, 32-PTZ locked
struAlarmTime NET_DVR_TIME_EX Alarm time
uStruAlarm Union ( Table 4-2 ) Alarm information union
pRes DWORD* Reserved.
byTimeDiffFlag BYTE Whether the time difference parameter is valid:
0-invalid, 1-valid.
cTimeDifferenceH char 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 byISO8601 is "1".
cTimeDifferenceM char 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
byISO8601 is "1".
byRes Array of BYTE Reserved, set to 0. The maximum size is 5 bytes.
Table A-2 Union about Alarm Information Structures (uStruAlarm)

byUnionLen Array of BYTE Union size, which is 116 bytes.
struIOAlarm Struct ( Table 4-3 ) Structure about alarm input parameters
struAlarmChannel Struct ( Table 4-4 ) Structure about alarm channel parameters
struAlarmHardDisk Struct ( Table 4-5 ) Structure about HDD alarm parameters
struRecordingHost Struct ( Table 4-6 ) Structure about alarm parameters of education
sharing system
struVoltageInstable Struct ( Table 4-7 ) Structure about alarm parameters of supply
voltage exception
struPTLocking Struct ( Table 4-8 Structure about parameters of PTZ locked alarm
109
Table A-3 Structure about Alarm Input Parameters (struIOAlarm)

dwAlarmInputNo DWORD Alarm input No.
dwTrigerAlarmOutNum DWORD The number of triggered alarm outputs. It is
used for calculating the number of all triggered
alarm outputs by pAlarmData in
NET_DVR_ALARMINFO_V40 , each alarm
output is represented by 4 bytes.
dwTrigerRecordChanN DWORD The number of triggered recording channels. It
um is used for calculating the number of all
triggered recording channels by pAlarmData of
NET_DVR_ALARMINFO_V40 , each channel is
represented by 4 bytes.
Table A-4 Structure about Alarm Channel Parameters (struAlarmChannel)

dwAlarmChanNum DWORD The number of alarm channels. It is used for
calculating the number of all alarm channels by
pAlarmData of NET_DVR_ALARMINFO_V40 ,
each alarm channel is represented by 4 bytes.
dwPicLen DWORD Size of JPEG picture.
byPicURL BYTE Picture data format: 0-binary data, 1-URL.
byTarget BYTE Detection target type: 0-not supported, 1-
person, 2-vehicle.
byRes1 Array of BYTE Reserved, the maximum size is 2 bytes.
pDataBuff char* Alarm picture data or URL. The pointer size is 8
bytes.
byRes3 Array of BYTE Reserved, the maximum size is 4 bytes. This
member is only available for 64-bit Window
operating system and 64-bit Linux operating
system.
110
Table A-5 Structure about HDD Alarm Parameters (struAlarmHardDisk)

dwAlarmHardDiskNum DWORD The number of alarm HDD. It is used for
calculating the number of all alarm HDDs by
pAlarmData of NET_DVR_ALARMINFO_V40 ,
each alarm HDD is represented by 4 bytes.
Table A-6 Structure about Alarm Parameters of Education Sharing System (struRecordingHost)
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 A-7 Structure about Alarm Parameters of Supply Voltage Exception (struVoltageInstable)
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.
Table A-8 Structure about Parameters of PTZ Locked Alarm (struPTLocking)

fTemperature float Sensor temperature, which is accurate to one
decimal place.
dwCustomInfoLength DWORD Custom information length.
pCustomInfo BYTE* Custom information.
byType BYTE PTZ locked direction: 1-panning is locked, 2-
tilting is locked.
byDeicingEnabled BYTE Whether to enable heat for PTZ: 0-no, 1-yes.
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==
111
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.
A.32 NET_DVR_ALARM_ISAPI_INFO
Structure about Alarm Information Transmitted Based on Text Protocol

pAlarmData char* Alarm information based on
text protocol (XML or JSON
message without binary data).
dwAlarmDataLen DWORD Alarm data length.
byDataType BYTE Alarm data type: 0-invalid, 1-
XML, 2-JSON.
byPicturesNumber BYTE The number of pictures
(number of pPicPackData
returned). When this member
is 1, only one structure of
NET_DVR_ALARM_ISAPI_PICD
ATA will be returned by
pPicPackData. When this
member is larger than 1,
multiple structures of
ATA will be returned by
pPicPackData.
byRes Array of BYTE Reserved, set to 0. The
maximum size is 2 bytes.
pPicPackData void* Alarm picture structure, see
ATA for details.
byRes Array of BYTE Reserved. The maximum size is
32 bytes.
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.
112
A.33 NET_DVR_ALARM_ISAPI_PICDATA
Structure about Alarm Picture Data Transmitted Based on Text Protocol

dwPicLen DWORD Alarm picture data length.
byRes Array of BYTE Reserved, set to 0. The
szFilename Array of char Picture file saving path,
including file name. The
pPicData BYTE* Pointer that pointing to the
uploaded image data.
A.34 NET_DVR_ETHERNET_V30
Ethernet Configuration Structure

struDVRIP NET_DVR_IPADDR_UN Device IP address
ION
struDVRIPMask NET_DVR_IPADDR_UN Mask of device IP address
ION
dwNetInterface DWORD Network interface type: 1-10MBase-T;
2-10MBase-T (full duplex); 3-100MBase-TX;
4-100M (full duplex); 5-10M/100M/1000M
(self-adaptive); 6-1000M (full duplex)
wDVRPort WORD Device port No.
wMTU WORD MTU settings, the default is 1500.
byMACAddr Array of BYTE Device physical address.
byEthernetPortNo BYTE Network interface No.: 0-invalid, 1-interface 0,
2-interface 1, and so on. This parameter is read-
only.
byRes Array of BYTE Reserved.
113
A.35 NET_DVR_IPADDR_UNION
IP Address Union

szIPv4 char[] IPv4 address. The maximum length is 16 bytes.
szIPv6 char[] IPv6 address. The maximum length is 256 bytes.
A.36 NET_DVR_NETCFG_V50
Network Configuration Structure

struEtherNet Array of Ethernet interface
NET_DVR_ETHERNET_
V30
struRes1 Array of Reserved, set to 0.
struAlarmHostIpAddr NET_DVR_IPADDR_UN Listening service IP address
ION
byRes2 Array of BYTE Reserved, set as 0
wAlarmHostIpPort WORD Listening service port No.
byUseDhcp BYTE Whether to enable DHCP: 0xff- invalid; 0-
disable, 1-enable
byIPv6Mode BYTE Allocation mode of IPv6 address: 0-by router
advertisement, 1-by manual setting, 2-by
enabling DHCP allocation.
struDnsServer1IpAddr NET_DVR_IPADDR_UN IP address of domain name server 1
ION
struDnsServer2IpAddr NET_DVR_IPADDR_UN IP address of domain name server 2
ION
114

byIpResolver Array of BYTE IP resolver domain name or IP address (if the
port No. of device is 8000, the domain name is
not supported).
wIpResolverPort WORD IP resolver port No.
wHttpPortNo WORD HTTP port No.
struMulticastIpAddr NET_DVR_IPADDR_UN Multicast group address
ION
struGatewayIpAddr NET_DVR_IPADDR_UN Gateway address
ION
struPPPoE NET_DVR_PPPOECFG PPPoE parameters
byEnablePrivateMultic BYTE Private multicast search (SADP): 0-default, 1-
astDiscovery enable, 2-disable
byEnableOnvifMulticas BYTE Onvif multicast search (SADP): 0-default, 1-
tDiscovery enable, 2-disable
wAlarmHost2IpPort WORD Port No. of listening host 2.
struAlarmHost2IpAddr NET_DVR_IPADDR_UN IP address of listening host 2
ION
byEnableDNS BYTE DNS address setting mode: 0-automatically get,
1-manually set.
byRes Array of BYTE Reserved, set to 0
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.
A.37 NET_DVR_PPPOECFG
115
PPPoE Configuration Structure

dwPPPOE DWORD Whether to enable PPPoE: 0-no, 1-yes.
sPPPoEUser Array of BYTE PPPoE user name.
sPPPoEPassword Array of char PPPoE password.
struPPPoEIP NET_DVR_IPADDR_UN PPPoE IP address
ION
A.38 NET_DVR_SETUPALARM_PARAM_V50
Arming Parameter Structure

byLevel BYTE Arming priority: 0-high, 1-medium, 2-low.
byAlarmInfoType BYTE Intelligent traffic alarm information type: 0-old
(NET_DVR_PLATE_RESULT),1-new (NET_ITS_
PLATE_RESULT).
byRetAlarmTypeV40 BYTE 0-the motion detection, video loss, video
tampering, and alarm input alarm information
is uploaded in normal mode (alarm type:
COMM_ALARM_V30, alarm information
structure: NET_DVR_ALARMINFO_V30 ); 1-
alarm information is uploaded in variable size
(alarm type: COMM_ALARM_V40, alarm
information structure:
NET_DVR_ALARMINFO_V40 ).
byRetDevInfoVersion BYTE Alarm types of CVR: 0-COMM_ALARM_DEVICE
(alarm information structure:
NET_DVR_ALARMINFO_DEV ), 1-COMM_
ALARM_DEVICE_V40 (alarm information
structure: NET_DVR_ALARMINFO_DEV_V40 ).
byRetVQDAlarmType BYTE VQD alarm types: 0-COMM_ALARM_VQD
(alarm information structure: NET_DVR_VQD_
116

DIAGNOSE_INFO), 1-COMM_ALARM_VQD_EX
(alarm information structure: NET_DVR_VQD_
ALARM, including camera information and
captured pictures)
byFaceAlarmDetection BYTE Face detection alarm types: 1-face detection
alarm (alarm type: COMM_ALARM_FACE_
DETECTION, alarm information structure: NET_
DVR_FACE_DETECTION), 0-face capture alarm
(alarm type: COMM_UPLOAD_FACESNAP_
RESULT, alarm information structure: NET_VCA_
FACESNAP_RESULT).
bySupport BYTE Capabilities, which is represented by bit:
● bit0-whether to upload picture: 0-yes, 1-no
● bit1-whether to enable ANR: 0-no, 1-yes
● bit4-whether to upload abnormal event
detection events of all detection targets: 0-

no, 1-yes. It is used to enable the NVR to get
events of all targets detected by network
cameras.
● bit5-whether to enable all-day event or alarm
uploading: 0-no, 1-yes. It is used to enable

the NVR to receive all alarms from network
cameras.
byBrokenNetHttp BYTE ANR type, which is represented by bit and
should be supported by device:
● bit0-whether to enable ANR for ANPR: 0-no,
1-yes.
● bit1-whether to enable ANR for people
counting: 0-no, 1-yes.

● bit2-whetehr to enable ANR for heat map: 0-
no, 1-yes.
● bit3-whether to enable ANR for face capture:
0-no, 1-yes.
● bit4-whether to enable ANR for face picture
comparison: 0-no, 1-yes.

● bit5-whether to enable ANR for JSON
message transmission: 0-no, 1-yes.
117

● bit6: whether to enable ANR for uploading
heat map data by dwell time duration and by
people quantity: 0-no, 1-yes.
● bit7: whether to enable ANR for uploading
intersection analysis result: 0-no, 1-yes.
wTaskNo BYTE Task No.
byDeployType BYTE Arming type: 0-arm via client software, 1-real-
time arming.
bySubScription BYTE Subscription parameters, which is represent by
bit.
Bit7-whether to upload picture after subscribing
motion detection alarm by person or vehicle: 0-
no, 1-yes.
byRes1 Array [BYTE] Reserved, set to 0. The maximum size is 2 bytes.
byAlarmTypeURL BYTE Alarm picture data type, which is represented
by bit, if the device supports uploading alarm
pictures in binary format and URL format, you
can specify the data type to be uploading via
this parameter, if the device only supports URL
format, this parameter is invalid. If the URL
format is selected, you should set the device
and enable the cloud storage, otherwise, the
picture will still be transmitted in binary format.
● bit0-type of captured face pictures: 0-binary
data, 1-URL
● bit1-type of picture uploaded in message: 0-
binary, 1-URL
● bit2-type of picture uploaded for face picture
comparison: 0-binary, 1-URL

byCustomCtrl BYTE Custom control type, which is represented by
bit, bit0-whether to upload the face thumbnail
of the front passenger: 0-no, 1-yes
byRes4 Array [BYTE] Reserved, set to 0. The maximum size is 128
bytes.
118
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.
A.39 NET_DVR_TIME
Time Parameter Structure

dwYear DWORD Year
dwMonth DWORD Month
dwDay DWORD Day
dwHour DWORD Hour
dwMinute DWORD Minute
dwSecond DWORD Second
A.40 NET_DVR_TIME_EX
Extended Time Parameter Structure

wYear WORD Year
byMonth BYTE Month
byDay BYTE Day
byHour BYTE Hour
byMinute BYTE Minute
119

bySecond BYTE Second
byRes BYTE Reserved.
120
Appendix B. Appendixes
B.1 Device Network SDK Errors

The errors that may occur during the device network SDK integration are listed here for reference.
You can search for the error descriptions according to the error codes or names returned by a
specific API (NET_DVR_GetLastError or NET_DVR_GetErrorMsg).
General Errors
Error Name Error Code Error Description

NET_DVR_NOERROR 0 No error.
NET_DVR_PASSWORD_ERROR 1 Incorrect user name or password.
NET_DVR_NOENOUGHPRI 2 No permission.
NET_DVR_NOINIT 3 Uninitialized.
NET_DVR_CHANNEL_ERROR 4 Incorrect channel No.
NET_DVR_OVER_MAXLINK 5 No more device can be connected.
NET_DVR_VERSIONNOMATCH 6 Version mismatches.
NET_DVR_NETWORK_FAIL_CONNECT 7 Connecting to device failed. The
device is offline or network
connection timed out.
NET_DVR_NETWORK_SEND_ERROR 8 Sending data to device failed.
NET_DVR_NETWORK_RECV_ERROR 9 Receiving data from device failed.
NET_DVR_NETWORK_RECV_TIMEOUT 10 Receiving data from device timed out.
NET_DVR_NETWORK_ERRORDATA 11 The data sent to the device is illegal,
or the data received from the device
error. E.g. The input data is not
supported by the device for remote
configuration.
NET_DVR_ORDER_ERROR 12 API calling order error.
NET_DVR_OPERNOPERMIT 13 No permission for this operation.
NET_DVR_COMMANDTIMEOUT 14 Executing device command timed out.
NET_DVR_ERRORSERIALPORT 15 Incorrect serial port No. The specified
serial port does not exist.
121

NET_DVR_ERRORALARMPORT 16 Alarm port No. error. The alarm input
or output port of the specified device
does not exist.
NET_DVR_PARAMETER_ERROR 17 Incorrect parameter. The input or
output parameters of the SDK API is
empty, or the parameter value or
format is invalid.
NET_DVR_CHAN_EXCEPTION 18 Device channel is in exception status.
NET_DVR_NODISK 19 No HDD in the device.
NET_DVR_ERRORDISKNUM 20 Incorrect HDD No.
NET_DVR_DISK_FULL 21 HDD full.
NET_DVR_DISK_ERROR 22 HDD error.
NET_DVR_NOSUPPORT 23 Device does not support this function.
NET_DVR_BUSY 24 Device is busy.
NET_DVR_MODIFY_FAIL 25 Failed to edit device parameters.
NET_DVR_PASSWORD_FORMAT_ 26 Invalid password format.
ERROR
NET_DVR_DISK_FORMATING 27 HDD is formatting. Failed to startup.
NET_DVR_DVRNORESOURCE 28 Insufficient device resources.
NET_DVR_DVROPRATEFAILED 29 Device operation failed.
NET_DVR_OPENHOSTSOUND_FAIL 30 Failed to collect local audio data or
open audio output during two-way
audio and broadcast.
NET_DVR_DVRVOICEOPENED 31 Two-way audio channel is occupied.
NET_DVR_TIMEINPUTERROR 32 Incorrect time input.
NET_DVR_NOSPECFILE 33 No video file for playback.
NET_DVR_CREATEFILE_ERROR 34 Failed to create a file during local
recording, saving picture, getting
configuration file or downloading
video file remotely.
NET_DVR_FILEOPENFAIL 35 Failed to open a file. The file does not
exist or directory error.
122

NET_DVR_OPERNOTFINISH 36 Operation conflicted.
NET_DVR_GETPLAYTIMEFAIL 37 Failed to get the current played time.
NET_DVR_PLAYFAIL 38 Failed to play.
NET_DVR_FILEFORMAT_ERROR 39 Invalid file format.
NET_DVR_DIR_ERROR 40 File directory error.
NET_DVR_ALLOC_RESOURCE_ERROR 41 Allocating resources failed.
NET_DVR_AUDIO_MODE_ERROR 42 Invalid sound card mode error. The
opened sound play mode and
configured mode mismatched.
NET_DVR_NOENOUGH_BUF 43 Insufficient buffer for receiving data
or saving picture.
NET_DVR_CREATESOCKET_ERROR 44 Failed to create SOCKET.
NET_DVR_SETSOCKET_ERROR 45 Failed to set SOCKET.
NET_DVR_MAX_NUM 46 No more registrations and live views
can be connected.
NET_DVR_USERNOTEXIST 47 The user doest not exist. The user ID
is logged out or unavailable.
NET_DVR_WRITEFLASHERROR 48 Writing FLASH error during device
upgrade.
NET_DVR_UPGRADEFAIL 49 Failed to upgrade device. Network
problem or language mismatches.
NET_DVR_CARDHAVEINIT 50 The decoding card is already
initialized.
NET_DVR_PLAYERFAILED 51 Failed to call the function of player
SDK.
NET_DVR_MAX_USERNUM 52 No more users can log in to.
NET_DVR_GETLOCALIPANDMACFAIL 53 Failed to get the IP address or physical
address of local PC.
NET_DVR_NOENCODEING 54 The decoding function of this channel
is not enabled.
NET_DVR_IPMISMATCH 55 IP address mismatches.
123

NET_DVR_MACMISMATCH 56 MAC address mismatches.
NET_DVR_UPGRADELANGMISMATCH 57 The language of upgrade file
mismatches.
NET_DVR_MAX_PLAYERPORT 58 No more channels can be started to
play.
NET_DVR_NOSPACEBACKUP 59 Insufficient space to back up file.
NET_DVR_NODEVICEBACKUP 60 No backup device found.
NET_DVR_PICTURE_BITS_ERROR 61 Picture pixel bit mismatches. Only 24
bits are allowed.
NET_DVR_PICTURE_DIMENSION_ 62 Too large picture. The height*width
ERROR should be less than 128x256.
NET_DVR_PICTURE_SIZ_ERROR 63 Too large picture. The picture size
should be smaller than 100K.
NET_DVR_LOADPLAYERSDKFAILED 64 Failed to load the player(PlayCtrl.dll,
SuperRender.dll, AudioRender.dll) to
the current directory.
NET_DVR_LOADPLAYERSDKPROC_ 65 Failed to find the function in player
ERROR SDK.
NET_DVR_LOADDSSDKFAILED 66 Failed to load the DS SDK to the
current directory.
NET_DVR_LOADDSSDKPROC_ERROR 67 Failed to find the function in the DS
SDK.
NET_DVR_DSSDK_ERROR 68 Failed to call the API in the hardware
decoding library.
NET_DVR_VOICEMONOPOLIZE 69 The sound card is exclusive.
NET_DVR_JOINMULTICASTFAILED 70 Failed to join to multicast group.
NET_DVR_CREATEDIR_ERROR 71 Failed to create log file directory.
NET_DVR_BINDSOCKET_ERROR 72 Failed to bind socket.
NET_DVR_SOCKETCLOSE_ERROR 73 Socket disconnected. Network
disconnected or the destination is
unreachable.
124

NET_DVR_USERID_ISUSING 74 Operation is executing. Failed to log
out.
NET_DVR_SOCKETLISTEN_ERROR 75 Failed to listen.
NET_DVR_PROGRAM_EXCEPTION 76 Program exception.
NET_DVR_WRITEFILE_FAILED 77 Failed to write file during local
recording, downloading file remotely
or saving picture.
NET_DVR_FORMAT_READONLY 78 The HDD is read-only. Formatting is
forbidden.
NET_DVR_WITHSAMEUSERNAME 79 The user name already exists.
NET_DVR_DEVICETYPE_ERROR 80 Device model mismatches when
importing parameters.
NET_DVR_LANGUAGE_ERROR 81 Language mismatches when
NET_DVR_PARAVERSION_ERROR 82 Software version mismatches when
NET_DVR_IPCHAN_NOTALIVE 83 The external IP channel is offline live
view.
NET_DVR_RTSP_SDK_ERROR 84 Failed to load StreamTransClient.dll.
NET_DVR_CONVERT_SDK_ERROR 85 Failed to load SystemTransform.dll.
NET_DVR_IPC_COUNT_OVERFLOW 86 No more IP channels can access to.
NET_DVR_MAX_ADD_NUM 87 No more video tags can be added.
NET_DVR_PARAMMODE_ERROR 88 Invalid parameter mode of image
enhancement.
NET_DVR_CODESPITTER_OFFLINE 89 Code distributer is offline.
NET_DVR_BACKUP_COPYING 90 Device is backing up.
NET_DVR_CHAN_NOTSUPPORT 91 This operation is not supported by the
channel.
NET_DVR_CALLINEINVALID 92 The height line is too concentrated, or
the length line is not inclined enough.
125

NET_DVR_CALCANCELCONFLICT 93 Cancel calibration conflict, if the rule
and global actual size filter are
configured.
NET_DVR_CALPOINTOUTRANGE 94 The calibration point is out of
limitation.
NET_DVR_FILTERRECTINVALID 95 The size filter does not meet the
requirement.
NET_DVR_DDNS_DEVOFFLINE 96 Device has not registered to DDNS.
NET_DVR_DDNS_INTER_ERROR 97 DDNS internal error.
NET_DVR_FUNCTION_NOT_ 98 This function is not supported by this
SUPPORT_OS Operating system.
NET_DVR_DEC_CHAN_REBIND 99 Decoding channel binding display
output is limited.
NET_DVR_INTERCOM_SDK_ERROR 100 Failed to load the two-way audio SDK
of the current directory.
NET_DVR_NO_CURRENT_UPDATEFILE 101 No correct upgrade packet.
NET_DVR_USER_NOT_SUCC_LOGIN 102 Login failed.
NET_DVR_USE_LOG_SWITCH_FILE 103 The log switch file is under using.
NET_DVR_POOL_PORT_EXHAUST 104 No port can be bound in the port
pool.
NET_DVR_PACKET_TYPE_NOT_ 105 Incorrect stream packaging format.
SUPPORT
NET_DVR_IPPARA_IPID_ERROR 106 Incorrect IPID for IP access
configuration.
NET_DVR_LOAD_HCPREVIEW_SDK_ 107 Failed to load the live view
ERROR component.
NET_DVR_LOAD_HCVOICETALK_SDK_ 108 Failed to load the audio component.
ERROR
NET_DVR_LOAD_HCALARM_SDK_ 109 Failed to load the alarm component.
ERROR
NET_DVR_LOAD_HCPLAYBACK_SDK_ 110 Failed to load the playback
ERROR component.
126

NET_DVR_LOAD_HCDISPLAY_SDK_ 111 Failed to load the display component.
ERROR
NET_DVR_LOAD_HCINDUSTRY_SDK_ 112 Failed to load application component.
ERROR
NET_DVR_LOAD_ 113 Failed to load the general
HCGENERALCFGMGR_SDK_ERROR configuration management
component.
NET_DVR_CORE_VER_MISMATCH 121 Component version and core version
mismatched when loading the
component singly.
NET_DVR_CORE_VER_MISMATCH_ 122 Live view component version and core
HCPREVIEW version mismatched.
NET_DVR_CORE_VER_MISMATCH_ 123 Audio component version and the
HCVOICETALK core version mismatched.
NET_DVR_CORE_VER_MISMATCH_ 124 Alarm component version and the
HCALARM core version mismatched.
NET_DVR_CORE_VER_MISMATCH_ 125 Playback component version and the
HCPLAYBACK core version mismatched.
NET_DVR_CORE_VER_MISMATCH_ 126 Display component version and the
HCDISPLAY core version mismatched.
NET_DVR_CORE_VER_MISMATCH_ 127 Application component version and
HCINDUSTRY the core version mismatched.
NET_DVR_CORE_VER_MISMATCH_ 128 General configuration management
HCGENERALCFGMGR component version and the core
version mismatched.
NET_DVR_COM_VER_MISMATCH_ 136 Live view component version and SDK
HCPREVIEW version mismatched.
NET_DVR_COM_VER_MISMATCH_ 137 Audio component version and SDK
HCVOICETALKy version mismatched.
NET_DVR_COM_VER_MISMATCH_ 138 Alarm component version and SDK
HCALARM version mismatched.
NET_DVR_COM_VER_MISMATCH_ 139 Playback component version and SDK
HCPLAYBACK version mismatched.
127

NET_DVR_COM_VER_MISMATCH_ 140 Display component version and SDK
HCDISPLAY version mismatched.
NET_DVR_COM_VER_MISMATCH_ 141 Application component version and
HCINDUSTRY SDK version mismatched.
NET_DVR_COM_VER_MISMATCH_ 142 General configuration management
HCGENERALCFGMGR component version and SDK version
mismatched.
NET_DVR_ALIAS_DUPLICATE 150 Duplicated alias(for HiDDNS
configuration).
NET_DVR_USERNAME_NOT_EXIST 152 User name does not exist (error code
of network camera and network
speed dome with version from 5.1.7
to 5.3.1).
NET_ERR_USERNAME_LOCKED 153 The user name is locked.
NET_DVR_INVALID_USERID 154 Invalid user ID.
NET_DVR_LOW_LOGIN_VERSION 155 The version is too low.
NET_DVR_LOAD_LIBEAY32_DLL_ 156 Failed to load libeay32.dl.l
ERROR
NET_DVR_LOAD_SSLEAY32_DLL_ 157 Failed to load ssleay32.dll.
ERROR
NET_ERR_LOAD_LIBICONV 158 Failed to load libiconv.dll.
NET_ERR_SSL_CONNECT_FAILED 159 Connecting to SSL failed.
NET_DVR_TEST_SERVER_FAIL_ 165 Failed to connect to test server.
CONNECT
NET_DVR_NAS_SERVER_INVALID_DIR 166 Failed to load NAS server to the
directory, Invalid directory, or
incorrect user name and password.
NET_DVR_NAS_SERVER_ 167 Failed to load NAS server th the
NOENOUGH_PRI directory. No permission.
NET_DVR_EMAIL_SERVER_NOT_ 168 The server uses domain name
CONFIG_DNS without configuring DNS, the domain
name may be invalid.
128

NET_DVR_EMAIL_SERVER_NOT_ 169 No gateway configured. Sending email
CONFIG_GATEWAY may be failed.
NET_DVR_TEST_SERVER_PASSWORD_ 170 Incorrect user name or password of
ERROR test server.
NET_DVR_EMAIL_SERVER_CONNECT_ 171 Interaction exception between device
EXCEPTION_WITH_SMTP and SMTP server.
NET_DVR_FTP_SERVER_FAIL_ 172 FTP server creating directory failed.
CREATE_DIR
NET_DVR_FTP_SERVER_NO_WRITE_ 173 FTP server has no wirting permission.
PIR
NET_DVR_IP_CONFLICT 174 IP conflicted.
NET_DVR_INSUFFICIENT_ 175 Storage pool space is full.
STORAGEPOOL_SPACE
NET_DVR_STORAGEPOOL_INVALID 176 Invalid cloud storage pool. No storage
pool configured or incorrect storage
pool ID.
NET_DVR_EFFECTIVENESS_REBOOT 177 Restart to take effect.
NET_ERR_ANR_ARMING_EXIST 178 The ANR arming connection already
exists( the error will be returned
when arming with ANR function if the
private SDK protocol arming
connection is established).
NET_ERR_UPLOADLINK_EXIST 179 The ANR uploading connection
already exists( the error will be
returned when EHome protocol and
private SDK protocol do not support
ANR at the same time).
NET_ERR_INCORRECT_FILE_FORMAT 180 The imported file format is incorrect.
NET_ERR_INCORRECT_FILE_CONTENT 181 The imported file content is incorrect.
NET_ERR_MAX_HRUDP_LINK 182 No more HRUDP can be connected to
device.
NET_ERR_MAX_PORT_MULTIPLEX 183 Maximum number of multiplexed
ports reaches.
NET_ERR_CREATE_PORT_MULTIPLEX 184 Creating port multiplier failed.
129

NET_DVR_NONBLOCKING_CAPTURE_ 185 Non-blocking picture capture is not
NOTSUPPORT supported.
NET_SDK_ERR_FUNCTION_INVALID 186 Invalid function. The asynchronous
mode is enabled.
NET_SDK_ERR_MAX_PORT_ 187 Maximum number of multiplex ports
MULTIPLEX reached.
NET_DVR_INVALID_LINK 188 Link has not been created or the link
is invalid.
NET_DVR_NAME_NOT_ONLY 200 This name already exists.
NET_DVR_OVER_MAX_ARRAY 201 The number of RAID reaches the
upper-limit.
NET_DVR_OVER_MAX_VD 202 The number of virtual disk reaches
the upper-limit.
NET_DVR_VD_SLOT_EXCEED 203 The virtual disk slots are full.
NET_DVR_PD_STATUS_INVALID 204 The physical disk for rebuilding RAID
is error.
NET_DVR_PD_BE_DEDICATE_SPARE 205 The physical disk for rebuilding RAID
is specified as hot spare.
NET_DVR_PD_NOT_FREE 206 The physical disk for rebuilding RAID
is busy.
NET_DVR_CANNOT_MIG2NEWMODE 207 Failed to migrate the current RAID
type to the new type.
NET_DVR_MIG_PAUSE 208 Migration is paused.
NET_DVR_MIG_ABOUTED 209 Migration is cancelled.
NET_DVR_EXIST_VD 210 Failed to delete RAID. Virtual disk
exists in the RAID.
NET_DVR_TARGET_IN_LD_ 211 Target physical disk is a part of the
FUNCTIONAL virtual disk and it is working normally.
NET_DVR_HD_IS_ASSIGNED_ 212 The specified physical disk is allocated
ALREADY as virtual disk.
NET_DVR_INVALID_HD_COUNT 213 The number of physical disks and
specified RAID level mismatched.
130

NET_DVR_LD_IS_FUNCTIONAL 214 The RAID is normal. Failed to rebuild.
NET_DVR_BGA_RUNNING 215 Background task is executing.
NET_DVR_LD_NO_ATAPI 216 Failed to create virtual disk by ATAPI
disk.
NET_DVR_MIGRATION_NOT_NEED 217 There is no need to migrate the RAID.
NET_DVR_HD_TYPE_MISMATCH 218 The physical disk type is not allowed.
NET_DVR_NO_LD_IN_DG 219 No virtual disk. Operation failed.
NET_DVR_NO_ROOM_FOR_SPARE 220 Insufficient disk space. Failed to
allocate the disk as hot spare.
NET_DVR_SPARE_IS_IN_MULTI_DG 221 The disk is already allocated as the
hot spare of one RAID.
NET_DVR_DG_HAS_MISSING_PD 222 No disk in the RAID.
NET_DVR_NAME_EMPTY 223 The name is empty.
NET_DVR_INPUT_PARAM 224 Incorrect input parameters.
NET_DVR_PD_NOT_AVAILABLE 225 The physical disk is not available.
NET_DVR_ARRAY_NOT_AVAILABLE 226 The RAID is not available.
NET_DVR_PD_COUNT 227 Incorrect number of physical disks.
NET_DVR_VD_SMALL 228 Insufficient virtual disk space.
NET_DVR_NO_EXIST 229 Not exist.
NET_DVR_NOT_SUPPORT 230 This operation is not supported.
NET_DVR_NOT_FUNCTIONAL 231 The RAID status is exception.
NET_DVR_DEV_NODE_NOT_FOUND 232 The device node of virtual disk does
not exist.
NET_DVR_SLOT_EXCEED 233 No more slots are allowed.
NET_DVR_NO_VD_IN_ARRAY 234 No virtual disk exists in the RAID.
NET_DVR_VD_SLOT_INVALID 235 Invalid virtual disk slot.
NET_DVR_PD_NO_ENOUGH_SPACE 236 Insufficient physical disk space.
NET_DVR_ARRAY_NONFUNCTION 237 Only the RAID in normal status
supports to be migrated.
131

NET_DVR_ARRAY_NO_ENOUGH_ 238 Insufficient RAID space.
SPACE
NET_DVR_STOPPING_SCANNING_ 239 Pulling disk out safely or rescanning.
ARRAY
NET_DVR_NOT_SUPPORT_16T 240 Creating RAID with size larger than
16T is not supported.
NET_DVR_ERROR_DEVICE_NOT_ 250 The device is not activated (login
ACTIVATED failed.)
NET_DVR_ERROR_RISK_PASSWORD 251 Risky password.
NET_DVR_ERROR_DEVICE_HAS_ 252 The device is already activated.
ACTIVATED
NET_DVR_ID_ERROR 300 The configured ID is invalid.
NET_DVR_POLYGON_ERROR 301 Invalid polygon shape.
NET_DVR_RULE_PARAM_ERROR 302 Invalid rule parameters.
NET_DVR_RULE_CFG_CONFLICT 303 Configured information conflicted.
NET_DVR_CALIBRATE_NOT_READY 304 No calibration information.
NET_DVR_CAMERA_DATA_ERROR 305 Invalid camera parameters.
NET_DVR_CALIBRATE_DATA_UNFIT 306 Invalid inclination angle for
calibration.
NET_DVR_CALIBRATE_DATA_ 307 Calibration error.
CONFILICT
NET_DVR_CALIBRATE_CALC_FAIL 308 Failed to calculate calibration
parameter values of camera.
NET_DVR_CALIBRATE_LINE_OUT_ 309 The inputted calibration line exceeds
RECT the external sample rectangle.
NET_DVR_ENTER_RULE_NOT_READY 310 No region entrance is configured.
NET_DVR_AID_RULE_NO_INCLUDE_ 311 No lane configured in the traffic event
LANE rull(especially for traffic jam or driving
against the traffic).
NET_DVR_LANE_NOT_READY 312 Lane not configured.
NET_DVR_RULE_INCLUDE_TWO_WAY 313 Two different directions are contained
in event rule.
132

NET_DVR_LANE_TPS_RULE_CONFLICT 314 Lane and data rule conflicted.
NET_DVR_NOT_SUPPORT_EVENT_ 315 This event type is not supported.
TYPE
NET_DVR_LANE_NO_WAY 316 The lane has no direction.
NET_DVR_SIZE_FILTER_ERROR 317 Invalid size of filter frame.
NET_DVR_LIB_FFL_NO_FACE 318 No face picture exists in the image
inputted when positioning feature
point.
NET_DVR_LIB_FFL_IMG_TOO_SMALL 319 The inputted image is too small when
positioning feature point.
NET_DVR_LIB_FD_IMG_NO_FACE 320 No face picture exists in the image
inputted when detecting single face
picture.
NET_DVR_LIB_FACE_TOO_SMALL 321 Face picture is too small when
building model.
NET_DVR_LIB_FACE_QUALITY_TOO_ 322 The face picture quality is too poor
BAD when building model.
NET_DVR_KEY_PARAM_ERR 323 The configured advanced parameter
is incorrect.
NET_DVR_CALIBRATE_DATA_ERR 324 Calibration sample number error, or
data value error, or the sample points
are beyond the horizontal line.
NET_DVR_CALIBRATE_DISABLE_FAIL 325 Canceling calibration is not allowed
for configured rules.
NET_DVR_VCA_LIB_FD_SCALE_ 326 The minimum width and height of
OUTRANGE maximum filter frame are twice or
more larger than the maximum width
and height of minimum filter frame.
NET_DVR_LIB_FD_REGION_TOO_ 327 Too large detection region. The
LARGE maximum region should be 2/3 of the
image.
NET_DVR_TRIAL_OVERDUE 328 Trial period is ended.
NET_DVR_CONFIG_FILE_CONFLICT 329 Device type and configuration file
conflicted.
133

NET_DVR_FR_FPL_FAIL 330 Failed to positioning face feature
points.
NET_DVR_FR_IQA_FAIL 331 Failed to test face picture quality.
NET_DVR_FR_FEM_FAIL 332 Failed to extract the face feature
points.
NET_DVR_FPL_DT_CONF_TOO_LOW 333 The face detection validity is too low
when positioning face feature points.
NET_DVR_FPL_CONF_TOO_LOW 334 The validity of feature points
positionong is too low.
NET_DVR_E_DATA_SIZE 335 Data size mismatches.
NET_DVR_FR_MODEL_VERSION_ERR 336 Incorrect model version in face model
library.
NET_DVR_FR_FD_FAIL 337 Failed to detect face in the face
recognition library.
NET_DVR_FA_NORMALIZE_ERR 338 Failed to normalize face attribute.
NET_DVR_DOG_PUSTREAM_NOT_ 339 Dongle type and camera type
MATCH mismatched.
NET_DVR_DEV_PUSTREAM_NOT_ 340 Camera version mismatches.
MATCH
NET_DVR_PUSTREAM_ALREADY_ 341 This camera is already added to other
EXISTS channels of devices.
NET_DVR_SEARCH_CONNECT_FAILED 342 Failed to connect to face retrieval
server.
NET_DVR_INSUFFICIENT_DISK_SPACE 343 Insufficient storage space.
NET_DVR_DATABASE_CONNECTION_ 344 Failed to connect to database.
FAILED
NET_DVR_DATABASE_ADM_PW_ 345 Incorrect database user name and
ERROR password.
NET_DVR_DECODE_YUV 346 Decoding failed.
NET_DVR_IMAGE_RESOLUTION_ 347 Invalid picture resolution
ERROR
134

NET_DVR_CHAN_WORKMODE_ 348 Invalid channel working mode.
ERROR
NET_ERROR_TRUNK_LINE 711 Sub system is configured as the trunk
line.
NET_ERROR_MIXED_JOINT 712 Mixed joint is not supported.
NET_ERROR_DISPLAY_SWITCH 713 Switch of display channel is not
supported.
NET_ERROR_USED_BY_BIG_SCREEN 714 Decoded resource is occupied by the
big screen.
NET_ERROR_USE_OTHER_DEC_ 715 Using resources of other sub system is
RESOURCE not allowed.
NET_ERROR_SCENE_USING 717 The scene is being used.
NET_ERR_NO_ENOUGH_DEC_ 718 Insufficient resources for decoding.
RESOURCE
NET_ERR_NO_ENOUGH_FREE_ 719 Insufficient resources for display.
SHOW_RESOURCE
NET_ERR_NO_ENOUGH_VIDEO_ 720 Insufficient video storage resources.
MEMORY
NET_ERR_MAX _VIDEO_NUM 721 Insufficient resources for multiple
channels.
NET_ERR_WINDOW_COVER_FREE_ 722 Windows cover free display output
SHOW_AND_NORMAL channel and normal output channel.
NET_ERR_FREE_SHOW_WINDOW_ 723 Window division is not supported for
SPLIT free display windows.
NET_ERR_INAPPROPRIATE_ 724 For the windows whose number is not
WINDOW_FREE_SHOW integral multiple of the number of
output channels, free display is not
supported.
NET_DVR_TRANSPARENT_WINDOW_ 725 For windows whose transparency
NOT_SUPPORT_SPLIT configuration is enabled, window
division is not supported.
NET_DVR_SPLIT_WINDOW_NOT_ 726 For windows whose window division
SUPPORT_TRANSPARENT is enabled, transparency configuration
is not supported.
135

NET_ERR_TERMINAL_BUSY 780 The terminal busy.
NET_DVR_FUNCTION_RESOURCE_ 791 Failed to enable this function. The
USAGE_ERROR resources is occupied by other
functions.
NET_DVR_DEV_NET_OVERFLOW 800 Network traffic is out of the
limitation.
NET_DVR_STATUS_RECORDFILE_ 801 Failed to lock. The video file is
WRITING_NOT_LOCK recording.
NET_DVR_STATUS_CANT_FORMAT_ 802 Failed to format HDD. The HDD space
LITTLE_DISK is too small.
NET_SDK_ERR_REMOTE_DISCONNEC 803 Failed to connect to the remote
terminal.
NET_SDK_ERR_RD_ADD_RD 804 Spare server cannot be added to
spare server.
NET_SDK_ERR_BACKUP_DISK_EXCEPT 805 Backup disk exception.
NET_SDK_ERR_RD_LIMIT 806 No more spare server can be added.
NET_SDK_ERR_ADDED_RD_IS_WD 807 The added spare server is a working
server.
NET_SDK_ERR_ADD_ORDER_WRONG 808 Adding flow error.
NET_SDK_ERR_WD_ADD_WD 809 Working server cannot be added to
working server.
NET_SDK_ERR_WD_SERVICE_EXCETP 810 CVR service exception (For N+1 mode,
it refers to CVR working server
exception).
NET_SDK_ERR_RD_SERVICE_EXCETP 811 Spare CVR server exception.
NET_SDK_ERR_ADDED_WD_IS_RD 812 The added working server is spare
server.
NET_SDK_ERR_PERFORMANCE_LIMIT 813 The performance reaches the upper-
limit.
NET_SDK_ERR_ADDED_DEVICE_EXIST 814 This device already exists.
NET_SDK_ERR_INQUEST_RESUMING 815 Inquest resuming.
NET_SDK_ERR_RECORD_BACKUPING 816 Inquest video backing up.
136

NET_SDK_ERR_DISK_PLAYING 817 Playing.
NET_SDK_ERR_INQUEST_STARTED 818 Inquest started.
NET_SDK_ERR_LOCAL_OPERATING 819 Locally operating.
NET_SDK_ERR_INQUEST_NOT_START 820 Inquest is not started.
NET_SDK_ERR_CHAN_AUDIO_BIND 821 The channel is not bound or binding
two-way audio failed.
NET_DVR_N_PLUS_ONE_MODE 822 Ddevice is in N+1 mode. Cloud
storage is not supported.
NET_DVR_CLOUD_STORAGE_OPENED 823 Cloud storage mode is enbaled.
NET_DVR_ERR_OPER_NOT_ALLOWED 824 Operation failed. The device is in N+0
taken over status.
NET_DVR_ERR_NEED_RELOCATE 825 The device is in N+0 taken over status.
Get re-positioning information and try
again.
NET_SDK_ERR_IR_PORT_ERROR 830 IR output error.
NET_SDK_ERR_IR_CMD_ERROR 831 IR output port command number
error
NET_SDK_ERR_NOT_INQUESTING 832 Device is not in inquest status.
NET_SDK_ERR_INQUEST_NOT_ 833 Device is not in paused status.
PAUSED
NET_DVR_CHECK_PASSWORD_ 834 Incorrect verification code.
MISTAKE_ERROR
NET_DVR_CHECK_PASSWORD_NULL_ 835 Verification code is required.
ERROR
NET_DVR_UNABLE_CALIB_ERROR 836 Failed to calibrate.
NET_DVR_PLEASE_CALIB_ERROR 837 Calibration first.
NET_DVR_ERR_PANORAMIC_CAL_ 838 Panoramic calibration is empty in
EMPTY Flash.
NET_DVR_ERR_CALIB_FAIL_ 839 Calibration failed, please try again.
PLEASEAGAIN
137

NET_DVR_ERR_DETECTION_LINE 840 Rule line configuration error. Please
try again and make sure the line is
within the red region.
NET_DVR_EXCEED_FACE_IMAGES_ 843 No more face pictures can be added.
ERROR
NET_DVR_ANALYSIS_FACE_IMAGES_ 844 Picture recognition failed.
ERROR
NET_ERR_ALARM_INPUT_OCCUPIED 845 A<-1 alarm number is used for
triggering vehicle capture.
NET_DVR_FACELIB_DATABASE_ERROR 846 Database version in face picture
library mismatched.
NET_DVR_FACELIB_DATA_ERROR 847 Face picture library data error.
NET_DVR_FACE_DATA_ID_ERROR 848 Invalid face data PID.
NET_DVR_FACELIB_ID_ERROR 849 Invalid face picture library ID.
NET_DVR_EXCEED_FACE_LIBARY_ 850 No more face picture libraries can be
ERROR established..
NET_DVR_PIC_ANALYSIS_NO_ 851 No target recognized in the picture.
TARGET_ERROR
NET_DVR_SUBPIC_ANALYSIS_ 852 Sub picture modeling failed.
MODELING_ERROR
NET_DVR_PIC_ANALYSIS_NO_ 853 No VCA engine supports picture
RESOURCE_ERROR secondary recognition.
NET_DVR_ANALYSIS_ENGINES_NO_ 854 No VCA engine.
RESOURCE_ERROR
NET_DVR_ANALYSIS_ENGINES_ 855 Overload. The engine CPU reached
USAGE_EXCEED_ERROR 100%.
NET_DVR_EXCEED_HUMANMISINFO_ 856 No more false alarm channel can be
FILTER_ENABLED_ERROR enabled.
NET_DVR_NAME_ERROR 857 Name error.
NET_DVR_NAME_EXIST_ERROR 858 The name already exists.
NET_DVR_FACELIB_PIC_IMPORTING_ 859 The pictures is importing to face
ERROR picture library.
138

NET_DVR_PIC_FORMAT_ERROR 864 Invalid picture format.
NET_DVR_PIC_RESOLUTION_ 865 Invalid picture resolution.
INVALID_ERROR
NET_DVR_PIC_SIZE_EXCEED_ERROR 866 The picture size is too large.
NET_DVR_PIC_ANALYSIS_TARGRT_ 867 Too many targets in the picture.
NUM_EXCEED_ERROR
NET_DVR_ANALYSIS_ENGINES_ 868 Initializing analysis engine.
LOADING_ERROR
NET_DVR_ANALYSIS_ENGINES_ 869 Analysis engine exception.
ABNORMA_ERROR
NET_DVR_ANALYSIS_ENGINES_ 870 Analysis engine is importing pictures
FACELIB_IMPORTING to face picture library.
NET_DVR_NO_DATA_FOR_ 871 No data for modeling.
MODELING_ERROR
NET_DVR_FACE_DATA_MODELING_ 872 Device is modeling picture.
ERROR Concurrent processing is not
supported.
NET_ERR_FACELIBDATA_OVERLIMIT 873 No more face picture can be added to
the device (the data of imported face
picture library)
NET_DVR_ANALYSIS_ENGINES_ 874 Channel is linked to the analysis
ASSOCIATED_CHANNEL engine.
NET_DVR_ERR_CUSTOMID_LEN 875 The minimum length of upper layer
custom ID is 32 bytes.
NET_DVR_ERR_CUSTOMFACELIBID_ 876 The applied custom face picture
REPEAT library ID is duplicated
NET_DVR_ERR_CUSTOMHUMANID_ 877 The applied custom person ID is
REPEAT duplicated.
NET_DVR_ERR_URL_DOWNLOAD_ 878 URL download failed.
FAIL
NET_DVR_ERR_URL_DOWNLOAD_ 879 URL download has not started.
NOTSTART
139

NET_DVR_CFG_FILE_SECRETKEY_ 880 The security verification key of
ERROR configuration file is error.
NET_DVR_THERMOMETRY_REGION_ 883 Invalid thermometry region
OVERSTEP_ERROR
NET_DVR_ERR_TOO_SHORT_ 894 Too short time for calibration.
CALIBRATING_TIME
NET_DVR_ERR_AUTO_CALIBRATE_ 895 Auto calibration failed.
FAILED
NET_DVR_ERR_VERIFICATION_FAILED 896 Verification failed.
NET_DVR_NO_TEMP_SENSOR_ERROR 897 No temperature sensor.
NET_DVR_PUPIL_DISTANCE_ 898 The pupil distance is too large.
OVERSIZE_ERROR
NET_ERR_WINCHAN_IDX 901 Window channel index error.
NET_ERR_WIN_LAYER 902 Window layer number error(the
count of window layers on a single
screen exceeds the max number).
NET_ERR_WIN_BLK_NUM 903 Window block number error(the
count of screens that single window
overlays exceeds the max number).
NET_ERR_OUTPUT_RESOLUTION 904 The output resolution error.
NET_ERR_LAYOUT 905 Layout index error.
NET_ERR_INPUT_RESOLUTION 906 The input resolution is not supported.
NET_ERR_SUBDEVICE_OFFLINE 907 The sub-device is off-line.
NET_ERR_NO_DECODE_CHAN 908 There is no free decoding channel.
NET_ERR_MAX_WINDOW_ABILITY 909 The upper limit of window number.
NET_ERR_ORDER_ERROR 910 Calling order error.
NET_ERR_PLAYING_PLAN 911 Be playing plan.
NET_ERR_DECODER_USED 912 Decoder board is being used.
NET_ERR_OUTPUT_BOARD_DATA_ 913 Output board data overflow
OVERFLOW
NET_ERR_SAME_USER_NAME 914 Duplicate user name
140

NET_ERR_INVALID_USER_NAME 915 Invalid user name
NET_ERR_MATRIX_USING 916 Input matrix is in use.
NET_ERR_DIFFERENT_CHAN_TYPE 917 Different channel type (the type of
matrix output channel mismatches
that of the controller input channel)
NET_ERR_INPUT_CHAN_BINDED 918 Input channel has been bound by
other matrix
NET_ERR_BINDED_OUTPUT_CHAN_ 919 The matrix output channels in use
OVERFLOW exceeded the number bound by
matrix and controller
NET_ERR_MAX_SIGNAL_NUM 920 Number of input signals reached
upper limit
NET_ERR_INPUT_CHAN_USING 921 Input channel is in use
NET_ERR_MANAGER_LOGON 922 Administrator has logged in,
operation failed
NET_ERR_USERALREADY_LOGON 923 The user has logged in, operation
failed
NET_ERR_LAYOUT_INIT 924 Scene is initializing, operation failed
NET_ERR_BASEMAP_SIZE_NOT_ 925 Base image size does not match
MATCH
NET_ERR_WINDOW_OPERATING 926 Window is in other operation,
operation failed
NET_ERR_SIGNAL_UPLIMIT 927 Number of signal source window
reached upper limit
NET_ERR_WINDOW_SIZE_OVERLIMIT 943 The window size exceeds the limit.
NET_ERR_MAX_WIN_OVERLAP 951 The number of windows overlap has
reached the maximum limit.
NET_ERR_STREAMID_CHAN_BOTH_ 952 stream ID and channel number are
VALID both valid.
NET_ERR_NO_ZERO_CHAN 953 The device has no zero channel.
NEED_RECONNECT 955 Need redirection (for transcoding
system)
141

NET_ERR_NO_STREAM_ID 956 The stream ID does not exist.
NET_DVR_TRANS_NOT_START 957 The transcoding has not been started.
NET_ERR_MAXNUM_STREAM_ID 958 The number of stream ID has reached
the maximum limit.
NET_ERR_WORKMODE_MISMATCH 959 The work mode does not match with
the requirement.
NET_ERR_MODE_IS_USING 960 It Has been working in current mode.
NET_ERR_DEV_PROGRESSING 961 The device is in processing
NET_ERR_PASSIVE_TRANSCODING 962 It is in transcoding.
NET_DVR_ERR_WINDOW_SIZE_ 975 Wrong window position.
PLACE
NET_DVR_ERR_RGIONAL_ 976 Screen distance exceeds the limit.
RESTRICTIONS
NET_DVR_ERR_CLOSE_WINDOWS 984 Operation failed. Close the window
first.
NET_DVR_ERR_MATRIX_LOOP_ 985 Beyond the cycle decoding capacity.
ABILITY
NET_DVR_ERR_MATRIX_LOOP_TIME 986 Invalid cycle decoding time.
NET_DVR_ERR_LINKED_OUT_ABILITY 987 No more linked camera can be added.
NET_ERR_RESOLUTION_NOT_ 990 The resolution is not supported (odd
SUPPORT_ODD_VOUT No.).
NET_ERR_RESOLUTION_NOT_ 991 The resolution is not supported (even
SUPPORT_EVEN_VOUT No.).
NET_ERR_UnitConfig_Failed 998 Unit configuration failed.
XML_ABILITY_NOTSUPPORT 1000 Getting capability node is not
supported
XML_ANALYZE_NOENOUGH_BUF 1001 Not enough output memory
XML_ANALYZE_FIND_LOCALXML_ 1002 Failed to find related local xml
ERROR
XML_ANALYZE_LOAD_LOCALXML_ 1003 Loading local xml error
ERROR
142

XML_NANLYZE_DVR_DATA_FORMAT_ 1004 Device capability data format error
ERROR
XML_ANALYZE_TYPE_ERROR 1005 Capability set type error
XML_ANALYZE_XML_NODE_ERROR 1006 XML capability node format error
XML_INPUT_PARAM_ERROR 1007 Input capability XML node value error
XML_VERSION_MISMATCH 1008 XML version does not match
NET_ERR_TRANS_CHAN_START 1101 Transparent channel has been open,
operation failed
NET_ERR_DEV_UPGRADING 1102 Device is upgrading
NET_ERR_MISMATCH_UPGRADE_ 1103 Upgrade pack type does not match
PACK_TYPE
NET_ERR_DEV_FORMATTING 1104 Device is formatting
NET_ERR_MISMATCH_UPGRADE_ 1105 Upgrade pack version does not match
PACK_VERSION
NET_ERR_PT_LOCKED 1106 PT is locked.
NET_DVR_ERR_ILLEGAL_ 1111 Illegal verification code. Change the
VERIFICATION_CODE verification code.
NET_DVR_ERR_LACK_VERIFICATION_ 1112 No verification code. Enter the
CODE verification code.
NET_DVR_ERR_FORBIDDEN_IP 1113 The IP address cannot be configured.
NET_DVR_ERR_HTTP_BKN_EXCEED_ 1125 Up to one channel's ANR function can
ONE be enabled.
NET_DVR_ERR_FORMATTING_FAILED 1131 Formatting HDD failed.
NET_DVR_ERR_ENCRYPTED_ 1132 Formatting encrypted HDD failed.
FORMATTING_FAILED
NET_DVR_ERR_WRONG_PASSWORD 1133 Verifying password of SD card failed.
Incorrect password.
NET_ERR_SEARCHING_MODULE 1201 Searching peripherals.
NET_ERR_REGISTERING_MODULE 1202 Registering external module
NET_ERR_GETTING_ZONES 1203 Getting arming region parameter
NET_ERR_GETTING_TRIGGERS 1204 Getting trigger
143

NET_ERR_ARMED_STATUS 1205 System is in arming status
NET_ERR_PROGRAM_MODE_STATUS 1206 System is in programming mode
NET_ERR_WALK_TEST_MODE_STATUS 1207 System is in pacing measuring mode
NET_ERR_BYPASS_STATUS 1208 Bypass status
NET_ERR_DISABLED_MODULE_ 1209 Function not enabled
STATUS
NET_ERR_NOT_SUPPORT_OPERATE_ 1210 Operation is not supported by arming
ZONE region
NET_ERR_NOT_SUPPORT_MOD_ 1211 Module address cannot be modified
MODULE_ADDR
NET_ERR_UNREGISTERED_MODULE 1212 Module is not registered
NET_ERR_PUBLIC_SUBSYSTEM_ 1213 Public sub system associate with its
ASSOCIATE_SELF self
NET_ERR_EXCEEDS_ASSOCIATE_ 1214 Number of associated public sub
SUBSYSTEM_NUM system reached upper limit
NET_ERR_BE_ASSOCIATED_BY_ 1215 Sub system is associated by other
PUBLIC_SUBSYSTEM public sub system
NET_ERR_ZONE_FAULT_STATUS 1216 Arming region is in failure status
NET_ERR_SAME_EVENT_TYPE 1217 Same event type exists in enable
event trigger alarm output and
disable event trigger alarm output
NET_ERR_ZONE_ALARM_STATUS 1218 Arming region is in alarm status
NET_ERR_EXPANSION_BUS_SHORT_ 1219 Extension bus short-circuit
CIRCUIT
NET_ERR_PWD_CONFLICT 1220 Password conflict, e.g., lock password
is identical with duress password
NET_ERR_DETECTOR_GISTERED_BY_ 1221 Detector has been registered by other
OTHER_ZONE arming regions
NET_ERR_DETECTOR_GISTERED_BY_ 1222 Detector has been registered by other
OTHER_PU hosts
NET_ERR_DETECTOR_DISCONNECT 1223 Detector offline
NET_ERR_CALL_BUSY 1224 Device in call
144

NET_ERR_FILE_NAME 1357 File name error, empty or invalid
NET_ERR_BROADCAST_BUSY 1358 Device in broadcast
NET_DVR_ERR_LANENUM_EXCEED 1400 Over the number of lanes.
NET_DVR_ERR_PRAREA_EXCEED 1401 Recognition area is too large.
NET_DVR_ERR_LIGHT_PARAM 1402 Signal lamp access parameters error.
NET_DVR_ERR_LANE_LINE_INVALID 1403 Lane configuration error.
NET_DVR_ERR_STOP_LINE_INVALID 1404 Stop line configuration error.
NET_DVR_ERR_LEFTORRIGHT_LINE_ 1405 Turn left / right boundary
INVALID configuration error.
NET_DVR_ERR_LANE_NO_REPEAT 1406 Overlay lane number repetition.
NET_DVR_ERR_PRAREA_INVALID 1407 The polygon does not meet the
requirements.
NET_DVR_ERR_LIGHT_NUM_EXCEED 1408 Video detection of traffic light signal
exceeds the maximum number of.
NET_DVR_ERR_SUBLIGHT_NUM_ 1409 Video detection of traffic signal lamp
INVALID lights are not legitimate
NET_DVR_ERR_LIGHT_AREASIZE_ 1410 The size of the video detection of
INVALID traffic light input signal lamp is not
valid.
NET_DVR_ERR_LIGHT_COLOR_ 1411 The color of the video detection of
INVALID traffic light input signal lamp color is
not legitimate.
NET_DVR_ERR_LIGHT_DIRECTION_ 1412 The direction property of the video
INVALID detection of traffic light input light is
not valid.
NET_DVR_ERR_LACK_IOABLITY 1413 Lack of IO ablity.
NET_DVR_ERR_FTP_PORT 1414 FTP port error.
NET_DVR_ERR_FTP_CATALOGUE 1415 FTP catalogue error.
NET_DVR_ERR_FTP_UPLOAD_TYPE 1416 FTP upload type error.
NET_DVR_ERR_FLASH_PARAM_ 1417 Setting param flash write error.
WRITE
145

NET_DVR_ERR_FLASH_PARAM_READ 1418 Getting param flash read error.
NET_DVR_ERR_PICNAME_DELIMITER 1419 Pic name delimiter error.
NET_DVR_ERR_PICNAME_ITEM 1420 Pic name item error.
NET_DVR_ERR_PLATE_RECOGNIZE_ 1421 Plate recognize type error.
TYPE
NET_DVR_ERR_CAPTURE_TIMES 1422 Capture times error.
NET_DVR_ERR_LOOP_DISTANCE 1423 Loop distance error.
NET_DVR_ERR_LOOP_INPUT_STATUS 1424 Loop input status error.
NET_DVR_ERR_RELATE_IO_CONFLICT 1425 Related IO conflict.
NET_DVR_ERR_INTERVAL_TIME 1426 Interval time error.
NET_DVR_ERR_SIGN_SPEED 1427 Sign speed error.
NET_DVR_ERR_PIC_FLIP 1428 Flip is used.
NET_DVR_ERR_RELATE_LANE_ 1429 Related lane number error.
NUMBER
NET_DVR_ERR_TRIGGER_MODE 1430 Trigger mode error.
NET_DVR_ERR_DELAY_TIME 1431 Delay time error.
NET_DVR_ERR_EXCEED_RS485_ 1432 Exceed RS485 count.
COUNT
NET_DVR_ERR_RADAR_TYPE 1433 Radar type error.
NET_DVR_ERR_RADAR_ANGLE 1434 Radar angle error.
NET_DVR_ERR_RADAR_SPEED_ 1435 Radar speed valid time error.
VALID_TIME
NET_DVR_ERR_RADAR_LINE_ 1436 Radar line correct error.
CORRECT
NET_DVR_ERR_RADAR_CONST_ 1437 Radar const correct error.
CORRECT
NET_DVR_ERR_RECORD_PARAM 1438 Record param error.
NET_DVR_ERR_LIGHT_WITHOUT_ 1439 Light number and other param error.
COLOR_AND_DIRECTION
146

NET_DVR_ERR_LIGHT_WITHOUT_ 1440 Light number and detection region
DETECTION_REGION error.
NET_DVR_ERR_RECOGNIZE_ 1441 Plate recognize Province param error.
PROVINCE_PARAM
NET_DVR_ERR_SPEED_TIMEOUT 1442 IO Speed TimeOut Param error.
NET_DVR_ERR_NTP_TIMEZONE 1443 NTP TimeZone Param error.
NET_DVR_ERR_NTP_INTERVAL_TIME 1444 NTP Interval Time error.
NET_DVR_ERR_NETWORK_CARD_ 1445 Network Card Num error.
NUM
NET_DVR_ERR_DEFAULT_ROUTE 1446 Default Route error.
NET_DVR_ERR_BONDING_WORK_ 1447 Banding Work Mode error.
MODE
NET_DVR_ERR_SLAVE_CARD 1448 Sub-Card error.
NET_DVR_ERR_PRIMARY_CARD 1449 Primary Card error.
NET_DVR_ERR_DHCP_PPOE_WORK 1450 DHCP and PPOE not Meanwhile start.
NET_DVR_ERR_NET_INTERFACE 1451 Net Interface invalid.
NET_DVR_ERR_MTU 1452 Invalid MTU parameters.
NET_DVR_ERR_NETMASK 1453 Netmask address invalid.
NET_DVR_ERR_IP_INVALID 1454 IP address invalid.
NET_DVR_ERR_MULTICAST_IP_ 1455 Multicast IP address invalid.
INVALID
NET_DVR_ERR_GATEWAY_INVALID 1456 Gateway address invalid.
NET_DVR_ERR_DNS_INVALID 1457 DNS Param invalid.
NET_DVR_ERR_ALARMHOST_IP_ 1458 AlarmHost IP invalid.
INVALID
NET_DVR_ERR_IP_CONFLICT 1459 IP address Conflict.
NET_DVR_ERR_NETWORK_SEGMENT 1460 IP not support Multi Network
segment.
NET_DVR_ERR_NETPORT 1461 NetPort error.
NET_DVR_ERR_PPPOE_NOSUPPORT 1462 PPPoE is not supported.
147

NET_DVR_ERR_DOMAINNAME_ 1463 Not Support Domain Name.
NOSUPPORT
NET_DVR_ERR_NO_SPEED 1464 Speed Not Enabled.
NET_DVR_ERR_IOSTATUS_INVALID 1465 IO Status invalid.
NET_DVR_ERR_BURST_INTERVAL_ 1466 Burst Interval invalid.
INVALID
NET_DVR_ERR_RESERVE_MODE 1467 Reserve Mode invalid.
NET_DVR_ERR_LANE_NO 1468 Lane No error.
NET_DVR_ERR_COIL_AREA_TYPE 1469 Coil Area Type error.
NET_DVR_ERR_TRIGGER_AREA_ 1470 Trigger Area Param error.
PARAM
NET_DVR_ERR_SPEED_LIMIT_PARAM 1471 Speed Limit Param error.
NET_DVR_ERR_LANE_PROTOCOL_ 1472 Lane Protocol Type error.
TYPE
NET_DVR_ERR_INTERVAL_TYPE 1473 Capture Interval Type error.
NET_DVR_ERR_INTERVAL_DISTANCE 1474 Capture Interval Distance error.
NET_DVR_ERR_RS485_ASSOCIATE_ 1475 Rs485 Associate DevType error.
DEVTYPE
NET_DVR_ERR_RS485_ASSOCIATE_ 1476 Rs485 Associate LaneNo error.
LANENO
NET_DVR_ERR_LANENO_ASSOCIATE_ 1477 LaneNo Associate MulitRs485 error.
MULTIRS485
NET_DVR_ERR_LIGHT_DETECTION_ 1478 Light Detection Region error.
REGION
NET_DVR_ERR_DN2D_NOSUPPORT 1479 UnSupport Capture Frame 2D Noise
Reduction.
NET_DVR_ERR_IRISMODE_ 1480 UnSupport scene Mode.
NOSUPPORT
NET_DVR_ERR_WB_NOSUPPORT 1481 UnSupport White Balance Mode.
NET_DVR_ERR_IO_EFFECTIVENESS 1482 IO Effectiveness invalid.
148

NET_DVR_ERR_LIGHTNO_MAX 1483 Access Detector Lights Red / Yellow
Overrun.
NET_DVR_ERR_LIGHTNO_CONFLICT 1484 Access Detector Lights Red / Yellow
Conflict.
NET_DVR_ERR_CANCEL_LINE 1485 Trigger straight line error.
NET_DVR_ERR_STOP_LINE 1486 Subject line area stop line error.
NET_DVR_ERR_RUSH_REDLIGHT_LINE 1487 Red light trigger lines error.
NET_DVR_ERR_IOOUTNO_MAX 1488 IO out port error.
NET_DVR_ERR_IOOUTNO_ 1489 IO out ahead time error.
AHEADTIME_MAX
NET_DVR_ERR_IOOUTNO_ 1490 IO out inwork time error.
IOWORKTIME
NET_DVR_ERR_IOOUTNO_ 1491 IO out frequency multiplication error.
FREQMULTI
NET_DVR_ERR_IOOUTNO_DUTYRATE 1492 IO out duty rate error.
NET_DVR_ERR_VIDEO_WITH_ 1493 IO out work mode error.
EXPOSURE
NET_DVR_ERR_PLATE_BRIGHTNESS_ 1494 Plate enable in plate compensate
WITHOUT_FLASHDET mode on.
NET_DVR_ERR_RECOGNIZE_TYPE_ 1495 Recognize Type error.
PARAM
NET_DVR_ERR_PALTE_RECOGNIZE_ 1496 Plate Recognize Area Param error.
AREA_PARAM
NET_DVR_ERR_PORT_CONFLICT 1497 Port Conflict.
NET_DVR_ERR_LOOP_IP 1498 IP cannot be the loopback address.
NET_DVR_ERR_DRIVELINE_SENSITIVE 1499 Driveline sensitivity error.
NET_ERR_VQD_TIME_CONFLICT 1500 The time period conflict.
NET_ERR_VQD_PLAN_NO_EXIST 1501 The diagnostic plan of VQD dese not
exist.
NET_ERR_VQD_CHAN_NO_EXIST 1502 The channel dese not exist.
149

NET_ERR_VQD_CHAN_MAX 1503 The total number of VQD plans
exceeds the max limit.
NET_ERR_VQD_TASK_MAX 1504 The total number of VQD tasks
exceeds the max limit.
NET_DVR_ERR_EXCEED_MAX_ 1600 Capture times exceed 2 in flash mode.
CAPTURE_TIMES
NET_DVR_ERR_REDAR_TYPE_ 1601 Radar type conflict.
CONFLICT
NET_DVR_ERR_LICENSE_PLATE_NULL 1602 The license plate is null.
NET_DVR_ERR_WRITE_DATABASE 1603 Failed to write data into the database.
NET_DVR_ERR_LICENSE_EFFECTIVE_ 1604 The effective time of license plate
TIME error.
NET_DVR_ERR_PRERECORDED_ 1605 The pre recorded start time is greater
STARTTIME_LONG than the number of illegal capture.
NET_DVR_ERR_TRIGGER_RULE_LINE 1606 Trigger rule line error.
NET_DVR_ERR_LEFTRIGHT_ 1607 Left and right trigger line is not
TRIGGERLINE_NOTVERTICAL vertical.
NET_DVR_ERR_FLASH_LAMP_MODE 1608 Flash lamp mode error.
NET_DVR_ERR_ILLEGAL_SNAPSHOT_ 1609 Illegal capture number error.
NUM
NET_DVR_ERR_ILLEGAL_DETECTION_ 1610 Illegal detection type error.
TYPE
NET_DVR_ERR_POSITIVEBACK_ 1611 Positive back to trigger line height
TRIGGERLINE_HIGH error.
NET_DVR_ERR_MIXEDMODE_ 1612 Mixed mode only supports capture
CAPTYPE_ALLTARGETS type all targets.
NET_DVR_ERR_CARSIGNSPEED_ 1613 Car sign speed greater than speed
GREATERTHAN_LIMITSPEED limit value.
NET_DVR_ERR_BIGCARSIGNSPEED_ 1614 Big car sign speed limit greater than
GREATERTHAN_LIMITSPEED speed limit value.
NET_DVR_ERR_BIGCARSIGNSPEED_ 1615 Big car sign speed limit is greater than
GREATERTHAN_CARSIGNSPEED the car sign speed limit value.
150

NET_DVR_ERR_BIGCARLIMITSPEED_ 1616 Big car speed limit value is greater
GREATERTHAN_CARLIMITSPEED than the car speed limit value.
NET_DVR_ERR_ 1617 Big car low speed limit value is greater
BIGCARLOWSPEEDLIMIT_ than the car low speed limit value.
GREATERTHAN_CARLOWSPEEDLIMIT
NET_DVR_ERR_CARLIMITSPEED_ 1618 Car speed limit greater than exception
GREATERTHAN_EXCEPHIGHSPEED high speed value.
NET_DVR_ERR_BIGCARLIMITSPEED_ 1619 Big car speed limit greater than
GREATERTHAN_EXCEPHIGHSPEED exception high speed value.
NET_DVR_ERR_STOPLINE_ 1620 Stopping more than straight lines
MORETHAN_TRIGGERLINE trigger lines.
NET_ERR_TIME_OVERLAP 1900 Time periods overlap
NET_ERR_HOLIDAY_PLAN_OVERLAP 1901 Holiday plan overlap
NET_ERR_CARDNO_NOT_SORT 1902 Card number is not sorted
NET_ERR_CARDNO_NOT_EXIST 1903 Card number does not exist
NET_ERR_ILLEGAL_CARDNO 1904 Card number error
NET_ERR_ZONE_ALARM 1905 Arming region is in arming status
(parameter cannot be modified)
NET_ERR_ZONE_OPERATION_NOT_ 1906 Arming region does not support the
SUPPORT operation
NET_ERR_INTERLOCK_ANTI_ 1907 Interlock and anti-passback
CONFLICT configuration conflict
NET_ERR_DEVICE_CARD_FULL 1908 Card full (return after card reached
10,000)
NET_ERR_HOLIDAY_GROUP_ 1909 Failed to download holiday group
DOWNLOAD
NET_ERR_LOCAL_CONTROL_OFF 1910 Distributed access controller offline
NET_ERR_LOCAL_CONTROL_DISADD 1911 Distributed access controller is not
added
NET_ERR_LOCAL_CONTROL_HASADD 1912 Distributed access controller is added
NET_ERR_LOCAL_CONTROL_ 1913 Conflict with added distributed access
DOORNO_CONFLICT controller
151

NET_ERR_LOCAL_CONTROL_ 1914 Distributed access controller
COMMUNICATION_FAIL communication failed
NET_ERR_OPERAND_INEXISTENCE 1915 Operation object does not exist
(operation to door, alarm output,
alarm input, return when the object is
not added)
NET_ERR_LOCAL_CONTROL_OVER_ 1916 Distributed access controller
LIMIT exceeded device capability upper limit
NET_ERR_DOOR_OVER_LIMIT 1917 Door exceeded device capability
upper limit
NET_ERR_ALARM_OVER_LIMIT 1918 Alarm input and output exceeded
device capability upper limit
NET_ERR_LOCAL_CONTROL_ 1919 Distributed access controller address
ADDRESS_INCONFORMITY_TYPE does not match with type
NET_ERR_NOT_SUPPORT_ONE_ 1920 not support one person multi-card
MORE_CARD
NET_ERR_DELETE_NO_EXISTENCE_ 1921 The face picture does not exist.
FACE
NET_ERR_DOOR_SPECIAL_ 1922 Repeated door door duress code, the
PASSWORD_REPEAT super password, or the dismiss code.
NET_ERR_AUTH_CODE_REPEAT 1923 Repeated device authentication code
NET_ERR_DEPLOY_EXCEED_MAX 1924 No more devices can be armed.
NET_ERR_NOT_SUPPORT_DEL_FP_ 1925 The fingerprint module does not
BY_ID support deleting fingerprint by finger
ID.
NET_ERR_TIME_RANGE 1926 Invalid range of the effective period.
NET_ERR_CAPTURE_TIMEOUT 1927 Collection timed out.
NET_ERR_LOW_SCORE 1928 Low quality of collected data.
NET_ERR_OFFLINE_CAPTURING 1929 The device is collecting data offline
and cannot respond.
NET_DVR_ERR_OUTDOOR_ 1950 Communication exception with
COMMUNICATION outdoor terminal
152

NET_DVR_ERR_ROOMNO_ 1951 Room number is not set
UNDEFINED
NET_DVR_ERR_NO_CALLING 1952 No call
NET_DVR_ERR_RINGING 1953 Ringing
NET_DVR_ERR_IS_CALLING_NOW 1954 Call in progress
NET_DVR_ERR_LOCK_PASSWORD_ 1955 Incorrect smart lock password
WRONG
NET_DVR_ERR_CONTROL_LOCK_ 1956 Lock control failure
FAILURE
NET_DVR_ERR_CONTROL_LOCK_ 1957 Lock control timed out
OVERTIME
NET_DVR_ERR_LOCK_DEVICE_BUSY 1958 Smart lock device busy
NET_DVR_ERR_UNOPEN_REMOTE_ 1959 Remote lock control not enabled
LOCK_FUNCTION
NET_DVR_ERR_FILE_NOT_COMPLETE 2100 Downloaded file is incomplete
NET_DVR_ERR_IPC_EXIST 2101 The camera already exists
NET_DVR_ERR_ADD_IPC 2102 Camera has been added to the
channel
NET_DVR_ERR_OUT_OF_RES 2103 Not enough network bandwidth
NET_DVR_ERR_CONFLICT_TO_ 2104 IP address of camera conflicts with
LOCALIP that of DVR
NET_DVR_ERR_IP_SET 2105 Invalid IP address
NET_DVR_ERR_PORT_SET 2106 Invalid port number
NET_ERR_WAN_NOTSUPPORT 2107 Not in the same LAN, cannot set
security question or export GUID file
NET_ERR_MUTEX_FUNCTION 2108 Mutually exclusive function
NET_ERR_QUESTION_CONFIGNUM 2109 Error in number of security question
configurations
NET_ERR_FACECHAN_NORESOURCE 2110 All the face VCA channels are
occupied.
NET_ERR_DATA_CALLBACK 2111 Data is calling back.
153

NET_ERR_ATM_VCA_CHAN_IS_ 2112 The VCA channel is already linked.
RELATED
NET_ERR_ATM_VCA_CHAN_IS_ 2113 The VCA channel is already overlayed.
OVERLAPED
NET_ERR _FACE_CHAN_UNOVERLAP_ 2114 The face channels cannot be
EACH_OTHER overlayed.
NET_DVR_SMD_ENCODING_ 2116 Insufficient SMD encoding resource
NORESOURSE
NET_DVR_SMD_DECODING_ 2117 Insufficient SMD decoding resource
NORESOURSE
NET_DVR_FACELIB_DATA_ 2118 Face picture library data is in
PROCESSING processing
NET_DVR_ERR_LARGE_TIME_ 2119 There is a great time difference
DIFFRENCE between device and server.
NET_DVR_NO_SUPPORT_WITH_ 2120 It is not supported. Playback is
PLAYBACK enabled.
NET_DVR_CHANNEL_NO_SUPPORT_ 2121 It is not supported. SMD of channel is
WITH_SMD enabled.
NET_DVR_CHANNEL_NO_SUPPORT_ 2122 It is not supported. Face capture of
WITH_FD channel is enabled.
NET_DVR_ILLEGAL_PHONE_NUMBER 2123 Invalid telephone number
NET_DVR_ILLEGAL_CERITIFICATE_ 2124 Invalid ID No.
NUMBER
NET_DVR_ERR_CHANNEL_ 2125 The channel resolution is not
RESOLUTION_NO_SUPPORT supported
NET_DVR_ERR_CHANNEL_ 2126 The channel encoding format is not
COMPRESSION_NO_SUPPORT supported
NET_DVR_ERR_CLUSTER_DEVICE_ 2127 Deleting is not allowed. The number
TOO_LESS of devices is not enough
NET_DVR_ERR_CLUSTER_DEL_ 2128 Deleting is not allowed. The device is
DEVICE_CM_PLAYLOAD cluster host.
NET_DVR_ERR_CLUSTER_DEVNUM_ 2129 No more devices can be added.
OVER_UPPER_LIMIT
154

NET_DVR_ERR_CLUSTER_DEVICE_ 2130 Device type mismatched.
TYPE_INCONFORMITY
NET_DVR_ERR_CLUSTER_DEVICE_ 2131 Device version mismatched.
VERSION_INCONFORMITY
NET_DVR_ERR_CLUSTER_IP_ 2132 Cluster system IP address conflict:
CONFLICT ipv4 address conflict, invalid ipv6.
NET_DVR_ERR_CLUSTER_IP_INVALID 2133 Invalid cluster system IP address:
invalid ipv4, invalid ipv6.
NET_DVR_ERR_CLUSTER_PORT_ 2134 Cluster system port conflict
CONFLICT
NET_DVR_ERR_CLUSTER_PORT_ 2135 Invalid cluster system port
INVALID
NET_DVR_ERR_CLUSTER_ 2136 Invalid user name or password
USERNAEM_OR_PASSWORD_INVALID
NET_DVR_ERR_CLUSTER_DEVICE_ 2137 The device already exists.
ALREADY_EXIST
NET_DVR_ERR_CLUSTER_DEVICE_ 2138 The device does not exist.
NOT_EXIST
NET_DVR_ERR_CLUSTER_NON_ 2139 The device working mode is not the
CLUSTER_MODE cluster mode .
NET_DVR_ERR_CLUSTER_IP_NOT_ 2140 IP addresses are in different LAN.
SAME_LAN Building cluster or extending capacity
for NVRs in different LAN is not
allowed.
NET_DVR_ERR_IDENTITY_KEY 2147 Incorrect interaction password
NET_DVR_MISSING_IDENTITY_KEY 2148 Interaction password is missing
NET_DVR_ERR_CAPTURE_PACKAGE_ 2141 Capturing packets failed.
FAILED
NET_DVR_ERR_CAPTURE_PACKAGE_ 2142 Capturing packet.
PROCESSING
NET_DVR_ERR_SAFETY_HELMET_NO_ 2143 No enough hard hat detection
RESOURCE resource.
155

NET_DVR_NO_SUPPORT_WITH_ 2144 This function is not supported. Video
ABSTRACT synopsis is already enabled.
NET_DVR_INSUFFICIENT_DEEP_ 2146 No more deep learning resources can
LEARNING_RESOURCES be added.
NET_DVR_NO_SUPPORT_WITH_ 2149 People gathering density is enabled, it
PERSON_DENSITY_DETECT is not supported
NET_DVR_IPC_RESOLUTION_ 2150 The network camera resolution is too
OVERFLOW large
NET_DVR_IPC_BITRATE_OVERFLOW 2151 The network camera bitrate is too
large
NET_DVR_ERR_INVALID_TASKID 2152 Invalid taskID
NET_DVR_PANEL_MODE_NOT_ 2153 The ATM panel mode is not
CONFIG configured.
NET_DVR_NO_HUMAN_ENGINES_ 2154 No enough engine resource
RESOURCE
NET_DVR_ERR_TASK_NUMBER_ 2155 No more task data is allowed
OVERFLOW
NET_DVR_ERR_COLLISION_TIME_ 2156 Collision time is over the limit
OVERFLOW
NET_DVR_ERR_EVENT_NOTSUPPORT 2159 Subscribing alarm/event is not
supported.
NET_DVR_IPC_NUM_REACHES_LIMIT 2184 The max. number of network camera
channels reached.
NET_DVR_IOT_NUM_REACHES_LIMIT 2185 The max. number of IoT channels
reached
NET_DVR_IOT_CHANNEL_DEVICE_ 2186 Device of the IoT channel already
EXIST exists.
NET_DVR_IOT_CHANNEL_DEVICE_ 2187 Device of the IoT channel does not
NOT_EXIST exist.
NET_DVR_INVALID_IOT_PROTOCOL_ 2188 Invalid IoT protocol type
TYPE
NET_DVR_INVALID_EZVIZ_SECRET_ 2189 Invalid verification code
KEY
156

NET_DVR_DUPLICATE_IOT_DEVICE 2190 Duplicated IoT device
NET_DVR_ERROR_NEED_DOUBLE_ 2206 Double verification is required
VERIFICATION
NET_DVR_NO_DOUBLE_ 2207 No double verification user
VERIFICATION_USER
NET_DVR_TIMESPAN_NUM_OVER_ 2209 Max. number of time buckets reached
LIMIT
NET_DVR_CHANNEL_NUM_OVER_ 2210 Max. number of channels reached
LIMIT
NET_DVR_NO_SEARCH_ID_ 2211 Insufficient searchID resources
RESOURCE
NET_DVR_SWITCH_TIMEDIFF_LESS_ 2249 Time difference between power on
LIMIT and off should be less than 10
minutes.
NET_DVR_NO_SUPPORT_DELETE_ 2262 Deleting stranger library is not
STRANGER_LIB supported
NET_DVR_NO_SUPPORT_CREATE_ 2263 Creating stranger library is not
STRANGER_LIB supported
NET_DVR_SSD_FILE_SYSTEM_ERROR 2266 SSD file system error
NET_DVR_INSUFFICIENT_SSD__FOR_ 2267 Insufficient SSD space for person
FPD frequency detection
NET_DVR_SMRDISK_NOT_SUPPORT_ 2269 SMR disk does not support RAID.
RAID
NET_DVR_ERR_NOTSUPPORT_ 3001 Device does not support deicing
DEICING function under current status.(Deicing
function is only supported under the
power status of POE+, AC24V, and
DC12V).
NET_DVR_ERR_THERMENABLE_ 3002 Temperature measurement function
CLOSE is not enabled. (The enable function
in NET_DVR_THERMOMETRY_
BASICPARAM is not turned on)
NET_DVR_ERR_PANORAMIC_LIMIT_ 3004 Panoramic map and limit cannot be
OPERATED operated at same time
157

NET_DVR_ERR_SMARTH264_ROI_ 3005 SmartH264 and ROI cannot be
OPERATED enabled at the same time.
NET_DVR_ERR_RULENUM_LIMIT 3006 No more rules can be added.
NET_DVR_ERR_LASER_DEICING_ 3007 Laser and deicing function cannot be
OPERATED enabled at the same time.
NET_DVR_ERR_OFFDIGITALZOOM_ 3008 Please disable the digital zoom
OR_MINZOOMLIMIT function or set the zoom limit to the
minimum value. Otherwise, when
enabling smoke and fire detection,
abnormal event detection, ship
detection, defective point correction,
temperature measurement, smoke
and fire shielding function, this error
code will be prompted.
NET_DVR_SYNCHRONIZEFOV_ERROR 3010 Field of view synchronization failed.
NET_DVR_RULE_SHIELDMASK_ 3013 The rule region conflicts with the
CONFLICT_ERROR shielded area.
NET_DVR_ERR_NO_SAFETY_HELMET_ 3501 The hard hat detection area is not
REGION configured.
NET_DVR_ERR_UNCLOSED_SAFETY_ 3502 The hard hat detection is enabled.
HELMET
NET_DVR_UPLOAD_HBDLIBID_ERROR 3504 Incorrect ID of human body picture
library (incorrect HBDID or
customHBDID)
RTSP Communication Library Related Errors

NET_DVR_RTSP_ERROR_ 401 Authentication failed: if server
NOENOUGHPRI returns 401, it will change to this
error code
NET_DVR_RTSP_ERROR_ALLOC_ 402 Failed to allocate the resource
RESOURCE
NET_DVR_RTSP_ERROR_PARAMETER 403 Parameter error
158

NET_DVR_RTSP_ERROR_NO_URL 404 The assigned URL does not exist:
when the server returns 404, SDK
turns to this error code. E.g. the
channel is not available, or the
channel does not support sub
stream
NET_DVR_RTSP_ERROR_FORCE_STOP 406 The user forces to exit midway
NET_DVR_RTSP_GETPORTFAILED 407 RTSP port getting error.
NET_DVR_RTSP_DESCRIBERROR 410 RTSP DECRIBE communicate error
NET_DVR_RTSP_ 411 Sending "RTSP DECRIBE" is timeout.
DESCRIBESENDTIMEOUT
NET_DVR_RTSP_DESCRIBESENDERROR 412 Failed to send "RTSP DECRIBE".
NET_DVR_RTSP_ 413 Receiving "RTSP DECRIBE" is
DESCRIBERECVTIMEOUT timeout.
NET_DVR_RTSP_ 414 Receiving data of "RTSP DECRIBE"
DESCRIBERECVDATALOST error.
NET_DVR_RTSP_DESCRIBERECVERROR 415 Failed to receive "RTSP DECRIBE".
NET_DVR_RTSP_DESCRIBESERVERERR 416 "RTSP DECRIBE, the device returns
the error code: 501 (failed to
allocate the resource in the device)
NET_DVR_RTSP_SETUPERROR 420 (or 419), RTSP SETUP interaction
error. Generally, it is that the
address(URL) returned by the
device is not accessible, or it is
rejected by the server
NET_DVR_RTSP_SETUPSENDTIMEOUT 421 Sending "RTSP SETUP" is timeout.
NET_DVR_RTSP_SETUPSENDERROR 422 Sending "RTSP SETUP" error.
NET_DVR_RTSP_SETUPRECVTIMEOUT 423 Receiving "RTSP SETUP" is timeout.
NET_DVR_RTSP_SETUPRECVDATALOST 424 Receiving data of "RTSP SETUP"
error.
NET_DVR_RTSP_SETUPRECVERROR 425 Failed to receive "RTSP SETUP".
NET_DVR_RTSP_OVER_MAX_CHAN 426 "RTSP SETUP" device returns the
error that values 401 or 501. It
159

exceeds the max connection
number.
NET_DVR_RTSP_PLAYERROR 430 RTSP PLAY interaction error.
NET_DVR_RTSP_PLAYSENDTIMEOUT 431 Sending "RTSP PLAY" is timeout.
NET_DVR_RTSP_PLAYSENDERROR 432 Sending "RTSP PLAY" error.
NET_DVR_RTSP_PLAYRECVTIMEOUT 433 Receiving "RTSP PLAY" is timeout.
NET_DVR_RTSP_PLAYRECVDATALOST 434 Receiving data of "RTSP PLAY" error.
NET_DVR_RTSP_PLAYRECVERROR 435 Failed to receive "RTSP PLAY".
NET_DVR_RTSP_PLAYSERVERERR 436 "RTSP PLAY" device returns the
error that values 401 or 501.
NET_DVR_RTSP_TEARDOWNERROR 440 RTSP TEARDOWN interaction error.
NET_DVR_RTSP_ 441 Sending "RTSP TEARDOWN" is
TEARDOWNSENDTIMEOUT timeout.
NET_DVR_RTSP_ 442 Sending "RTSP TEARDOWN" error.
TEARDOWNSENDERROR
NET_DVR_RTSP_ 443 Receiving "RTSP TEARDOWN" is
TEARDOWNRECVTIMEOUT timeout.
NET_DVR_RTSP_ 444 Receiving data of "RTSP
TEARDOWNRECVDATALOST TEARDOWN" error.
NET_DVR_RTSP_ 445 Failed to receive "RTSP
TEARDOWNRECVERROR TEARDOWN".
NET_DVR_RTSP_ 446 "RTSP TEARDOWN" device returns
TEARDOWNSERVERERR the error that values 401 or 501.
Software Decoding Library Related Errors

NET_PLAYM4_NOERROR 500 No error.
NET_PLAYM4_PARA_OVER 501 Input parameter is invalid.
NET_PLAYM4_ORDER_ERROR 502 API calling order error.
NET_PLAYM4_TIMER_ERROR 503 Failed to create multimedia clock.
160

NET_PLAYM4_DEC_VIDEO_ERROR 504 Failed to decode video data.
NET_PLAYM4_DEC_AUDIO_ERROR 505 Failed to decode audio data.
NET_PLAYM4_ALLOC_MEMORY_ 506 Failed to allocate memory.
ERROR
NET_PLAYM4_OPEN_FILE_ERROR 507 Failed to open the file.
NET_PLAYM4_CREATE_OBJ_ERROR 508 Failed to create thread event.
NET_PLAYM4_CREATE_DDRAW_ 509 Failed to create DirectDraw object.
ERROR
NET_PLAYM4_CREATE_OFFSCREEN_ 510 Failed to create backstage cache for
ERROR OFFSCREEN mode.
NET_PLAYM4_BUF_OVER 511 Buffer overflow, failed to input stream.
NET_PLAYM4_CREATE_SOUND_ 512 Failed to create audio equipment.
ERROR
NET_PLAYM4_SET_VOLUME_ 513 Failed to set the volume.
ERROR
NET_PLAYM4_SUPPORT_FILE_ONLY 514 This API can be called only for file
playback mode.
NET_PLAYM4_SUPPORT_STREAM_ 515 This API can be called only when playing
ONLY stream.
NET_PLAYM4_SYS_NOT_SUPPORT 516 Not support by the system. Decoder can
only work on the system above Pentium
3.
NET_PLAYM4_FILEHEADER_ 517 There is no file header.
UNKNOWN
NET_PLAYM4_VERSION_ 518 The version mismatch between decoder
INCORRECT and encoder.
NET_PLAYM4_INIT_DECODER_ 519 Failed to initialize the decoder.
ERROR
NET_PLAYM4_CHECK_FILE_ERROR 520 The file is too short, or the stream data
is unknown.
NET_PLAYM4_INIT_TIMER_ERROR 521 Failed to initialize multimedia clock.
NET_PLAYM4_BLT_ERROR 522 BLT failure.
161

NET_PLAYM4_UPDATE_ERROR 523 Failed to update overlay surface
NET_PLAYM4_OPEN_FILE_ERROR_ 524 Failed to open video & audio stream
MULTI file.
NET_PLAYM4_OPEN_FILE_ERROR_ 525 Failed to open video stream file.
VIDEO
NET_PLAYM4_JPEG_COMPRESS_ 526 JPEG compression error.
ERROR
NET_PLAYM4_EXTRACT_NOT_ 527 Don't support the version of this file.
SUPPORT
NET_PLAYM4_EXTRACT_DATA_ 528 Extract video data failed.
ERROR
Container Format Conversion Library Related Errors

NET_CONVERT_ERROR_NOT_ 581 This container format is not supported.
SUPPORT
Two Way Audio Library Related Errors

NET_AUDIOINTERCOM_OK 600 No error.
NET_AUDIOINTECOM_ERR_NOTSUPORT 601 Not support.
NET_AUDIOINTECOM_ERR_ALLOC_MEMERY 602 Memory allocation error.
NET_AUDIOINTECOM_ERR_PARAMETER 603 Parameter error.
NET_AUDIOINTECOM_ERR_CALL_ORDER 604 API calling order error.
NET_AUDIOINTECOM_ERR_FIND_DEVICE 605 No audio device
NET_AUDIOINTECOM_ERR_OPEN_DEVICE 606 Failed to open the audio device
NET_AUDIOINTECOM_ERR_NO_CONTEXT 607 Context error.
NET_AUDIOINTECOM_ERR_NO_WAVFILE 608 WAV file error.
NET_AUDIOINTECOM_ERR_INVALID_TYPE 609 The type of WAV parameter is
invalid
162

NET_AUDIOINTECOM_ERR_ENCODE_FAIL 610 Failed to encode data
NET_AUDIOINTECOM_ERR_DECODE_FAIL 611 Failed to decode data
NET_AUDIOINTECOM_ERR_NO_PLAYBACK 612 Failed to play audio
NET_AUDIOINTECOM_ERR_DENOISE_FAIL 613 Failed to denoise
NET_AUDIOINTECOM_ERR_UNKOWN 619 Unknown
QoS Stream Control Library Related Errors

NET_QOS_ERR_SCHEDPARAMS_BAD_ 678 Incorrect predefined minimum
MINIMUM_INTERVAL interval.
NET_QOS_ERR_SCHEDPARAMS_BAD_ 679 Incorrect predefined score.
FRACTION
NET_QOS_ERR_SCHEDPARAMS_INVALID_ 680 Invalid predefined bandwidth.
BANDWIDTH
NET_QOS_ERR_PACKET_TOO_BIG 687 The packet size is too large.
NET_QOS_ERR_PACKET_LENGTH 688 Invalid packet size.
NET_QOS_ERR_PACKET_VERSION 689 Incorrect packet versio
information.
NET_QOS_ERR_PACKET_UNKNOW 690 Unknown packet.
NET_QOS_ERR_OUTOFMEM 695 Out of memory.
NET_QOS_ERR_LIB_NOT_INITIALIZED 696 The library is not initialized.
NET_QOS_ERR_SESSION_NOT_FOUND 697 No session found.
NET_QOS_ERR_INVALID_ARGUMENTS 698 Invalid parameters.
NET_QOS_ERROR 699 QoS Stream Control Library
error.
NET_QOS_OK 700 No error.
163
NPQ (Network Protocol Quality) Related Error

NET_ERR_NPQ_PARAM 8001 NPQ library: Incorrect parameter.
NET_ERR_NPQ_SYSTEM 8002 NPQ library: Operating system error.
NET_ERR_NPQ_GENRAL 8003 NPQ library: Internal error.
NET_ERR_NPQ_PRECONDITION 8004 NPQ library: Calling sequence error.
NET_ERR_NPQ_NOTSUPPORT 8005 NPQ library: This function is not
supported.
NET_ERR_NPQ_NOTCALLBACK 8100 No data is called back.
NET_ERR_NPQ_LOADLIB 8101 Loading NPQ library failed.
NET_ERR_NPQ_STEAM_CLOSE 8104 The NPQ function of this stream is not
enabled.
NET_ERR_NPQ_MAX_LINK 8110 No more streaming channel's NPQ
function can be enabled.
NET_ERR_NPQ_STREAM_CFG_ 8111 The configured encoding parameters
CONFLICT conflicted.
B.2 Response Codes of Text Protocol

The response codes returned during the text protocol integration is based on the status codes of
HTTP. 7 kinds of status codes are predefined, including 1 (OK), 2 (Device Busy), 3 (Device Error), 4
(Invalid Operation), 5 (Invalid Message Format), 6 (Invalid Message Content), and 7 (Reboot
Required). Each kind of status code contains multiple sub status codes, and the response codes are
in a one-to-one correspondence with the sub status codes.
StatusCode=1
SubStatusCode Error Code Description

ok 0x1 Operation completed.
riskPassword 0x10000002 Risky password.
armProcess 0x10000005 Arming process.
164
StatusCode=2
Sub Status Code Error Code Description

noMemory 0x20000001 Insufficient memory.
serviceUnavailable 0x20000002 The service is not available.
upgrading 0x20000003 Upgrading.
deviceBusy 0x20000004 The device is busy or no
response.
reConnectIpc 0x20000005 The video server is
reconnected.
transferUpgradePackageFailed 0x20000006 Transmitting device upgrade
data failed.
startUpgradeFailed 0x20000007 Starting upgrading device
failed.
getUpgradeProcessfailed. 0x20000008 Getting upgrade status failed.
certificateExist 0x2000000B The Authentication certificate
already exists.
StatusCode=3

deviceError 0x30000001 Hardware error.
badFlash 0x30000002 Flash operation error.
28181Uninitialized 0x30000003 The 28181 configuration is not
initialized.
socketConnectError 0x30000005 Connecting to socket failed.
receiveError 0x30000007 Receive response message
failed.
deletePictureError 0x3000000A Deleting picture failed.
pictureSizeExceedLimit 0x3000000C Too large picture size.
clearCacheError 0x3000000D Clearing cache failed.
updateDatabasError 0x3000000F Updating database failed.
165

searchDatabaseError 0x30000010 Searching in the database
failed.
writeDatabaseError 0x30000011 Writing to database failed.
deleteDatabaseError 0x30000012 Deleting database element
failed.
searchDatabaseElementError 0x30000013 Getting number of database
elements failed.
cloudAutoUpgradeException 0x30000016 Downloading upgrade packet
from cloud and upgrading
failed.
HBPException 0x30001000 HBP exception.
UDEPException 0x30001001 UDEP exception
elasticSearchException 0x30001002 Elastic exception.
kafkaException 0x30001003 Kafka exception.
HBaseException 0x30001004 Hbase exception.
sparkException 0x30001005 Spark exception.
yarnException 0x30001006 Yarn exception.
cacheException 0x30001007 Cache exception.
trafficException 0x30001008 Monitoring point big data
server exception.
faceException 0x30001009 Human face big data server
exception.
SSDFileSystemIsError 0x30001013 SSD file system error (Error
occurs when it is non-Ext4 file
system)
insufficientSSDCapacityForFPD 0x30001014 Insufficient SSD space for
person frequency detection.
wifiException 0x3000100A Wi-Fi big data server exception
structException 0x3000100D Video parameters structure
server exception.
noLinkageResource 0x30001015 Insufficient linkage resources.
166

engineAbnormal 0x30002015 Engine exception.
engineInitialization 0x30002016 Initializing the engine.
algorithmLoadingFailed 0x30002017 Loading the model failed.
algorithmDownloadFailed 0x30002018 Downloading the model failed.
algorithmDecryptionFailed 0x30002019 Decrypting the model failed.
unboundChannel 0x30002020 Delete the linked channel to
load the new model.
unsupportedResolution 0x30002021 Invalid resolution.
unsupportedSteamType 0x30002022 Invalid stream type.
insufficientDecRes 0x30002023 Insufficient decoding resources.
insufficientEnginePerformance 0x30002024 Insufficient engine
performance (The number of
channels to be analyzed
exceeds the engine's
capability).
improperResolution 0x30002025 Improper resolution (The
maximum resolution allowed is
4096×4096).
improperPicSize 0x30002026 Improper picture size (The
maximum size allowed is 5MB).
URLDownloadFailed 0x30002027 Downloading the picture via
the URI failed.
unsupportedImageFormat 0x30002028 Invalid picture format (Only JPG
is supported currently).
unsupportedPollingIntervalTim 0x30002029 Invalid polling interval (The
e interval should be more than
10s).
exceedImagesNumber 0x30002030 The number of pictures
exceeds the limit (The platform
can apply 1 to 100 picture URIs
per time, the maximum
number allowed is 100).
167

unsupportedMPID 0x30002031 The applied MPID does not
exist in the device, so updating
this MPID is not supported.
modelPackageNotMatchLabel 0x30002032 The model and the description
file mismatch.
modelPackageNotMatchTask 0x30002033 The task and the model type
mismatch.
insufficientSpace 0x30002034 Insufficient space (When the
number of model packages
does not reach the maximum
number allowed but their size
together exceeds the free
space, the model packages
cannot be added).
engineUnLoadingModelPackag 0x30002035 Applying the task failed. This
e engine is not linked to a model
package (Canceling the linkage
failed, this engine is not linked
to a model package).
engineWithModelPackage 0x30002036 Linking the engine to this
model package failed. The
engine has been linked to
another model package. Please
cancel their linkage first.
modelPackageDelete 0x30002037 Linking the model package
failed. The model package has
been deleted.
deleteTaskFailed 0x30002038 Deleting the task failed (It is
returned when the user fails to
end a task).
modelPackageNumberslimited 0x30002039 Adding the model package
failed. The number of model
package has reached the
maximum number allowed.
modelPackageDeleteFailed 0x30002040 Deleting the model package
failed.
168

noArmingResource 0x30001016 Insufficient arming resources.
calibrationTimeout 0x30002051 Calibration timed out.
captureTimeout 0x30006000 Data collection timed out.
lowScore 0x30006001 Low quality of collected data.
uploadingFailed 0x30007004 Uploading failed.
StatusCode=4

notSupport 0x40000001 Not supported.
lowPrivilege 0x40000002 No permission.
badAuthorization 0x40000003 Authentication failed.
methodNotAllowed 0x40000004 Invalid HTTP method.
notSetHdiskRedund 0x40000005 Setting spare HDD failed.
invalidOperation 0x40000006 Invalid operation.
notActivated 0x40000007 Inactivated.
hasActivated 0x40000008 Activated.
certificateAlreadyExist 0x40000009 The certificate already exists.
operateFailed 0x4000000F Operation failed.
USBNotExist 0x40000010 USB device is not connected.
upgradePackageMoret 0x40001000 Up to 2GB upgrade package is allowed to be
han2GB uploaded.
IDNotexist 0x40001001 The ID does not exist.
interfaceOperationErro 0x40001002 API operation failed.
r
synchronizationError 0x40001003 Synchronization failed.
synchronizing 0x40001004 Synchronizing.
importError 0x40001005 Importing failed.
importing 0x40001006 Importing.
169

fileAlreadyExists 0x40001007 The file already exists.
invalidID 0x40001008 Invalid ID.
backupnodeNotAllowe 0x40001009 Accessing to backup node is not allowed.
Log
exportingError 0x4000100A Exporting failed.
exporting 0x4000100B Exporting.
exportEnded 0x4000100C Exporting stopped.
exported 0x4000100D Exported.
IPOccupied 0x4000100E The IP address is already occupied.
IDAlreadyExists 0x4000100F The ID already exists.
exportItemsExceedLimi 0x40001010 No more items can be exported.
t
noFiles 0x40001011 The file does not exist.
beingExportedByAnoth 0x40001012 Being exported by others.
erUser
needReAuthentication 0x40001013 Authentication is needed after upgrade.
unitAddNotOnline 0x40001015 The added data analysis server is offline.
unitControl 0x40001016 The data analysis server is already added.
analysis unitFull 0x40001017 No more data analysis server can be added.
unitIDError 0x40001018 The data analysis server ID does not exist.
unitExit 0x40001019 The data analysis server already exists in the
list.
unitSearch 0x4000101A Searching data analysis server in the list failed.
unitNotOnline 0x4000101B The data analysis server is offline.
unitInfoEror 0x4000101C Getting data analysis server information failed.
unitGetNodeInfoError 0x4000101D Getting node information failed.
unitGetNetworkInfoErr 0x4000101E Getting the network information of data
or analysis server failed
unitSetNetworkInfoErr 0x4000101F Setting the network information of data analysis
or server failed
170

setSmartNodeInfoError 0x40001020 Setting node information failed.
setUnitNetworkInfoErr 0x40001021 Setting data analysis server network
or information failed.
unitRestartCloseError 0x40001022 Rebooting or shutting down data analysis server
failed.
virtualIPnotAllowed 0x40001023 Adding virtual IP address is not allowed.
unitInstalled 0x40001024 The data analysis server is already installed.
badSubnetMask 0x40001025 Invalid subnet mask.
uintVersionMismatche 0x40001026 Data analysis server version mismatches.
d
deviceMOdelMismatch 0x40001027 Adding failed. Device model mismatches.
ed
unitAddNotSelf 0x40001028 Adding peripherals is not allowed.
noValidUnit 0x40001029 No valid data analysis server.
unitNameDuplicate 0x4000102A Duplicated data analysis server name.
deleteUnitFirst 0x4000102B Delete the added data analysis server of the
node first.
getLocalInfoFailed 0x4000102C Getting the server information failed.
getClientAddedNodeFa 0x4000102D Getting the added node information of data
iled analysis server failed.
taskExit 0x4000102E The task already exists.
taskInitError 0x4000102F Initializing task failed.
taskSubmitError 0x40001030 Submiting task failed.
taskDelError 0x40001031 Deleting task failed.
taskPauseError 0x40001032 Pausing task failed.
taskContinueError 0x40001033 Starting task failed.
taskSeverNoCfg 0x40001035 Full-text search server is not configured.
taskPicSeverNoCfg 0x40001036 The picture server is not configured.
taskStreamError 0x40001037 Streaming information exception.
taskRecSDK 0x40001038 History recording is not supported.
171

taskCasaError 0x4000103A Cascading is not supported.
taskVCARuleError 0x4000103B Invalid VCA rule.
taskNoRun 0x4000103C The task is not executed.
unitLinksNoStorageNo 0x4000103D No node is linked with the data analysis server.
de Configure the node first.
searchFailed 0x4000103E Searching video files failed.
searchNull 0x4000103F No video clip.
userScheOffline 0x40001040 The task scheduler service is offline.
updateTypeUnmatche 0x40001041 The upgrade package type mismatches.
d
userExist 0x40001043 The user already exists.
userCannotDelAdmin 0x40001044 The administrator cannot be deleted.
userInexistence 0x40001045 The user name does not exist.
userCannotCreatAdmi 0x40001046 The administrator cannot be created.
n
monitorCamExceed 0x40001048 Up to 3000 cameras can be added.
monitorCunitOverLimit 0x40001049 Adding failed. Up to 5 lower-levels are
supported by the control center.
monitorReginOverLimit 0x4000104A Adding failed. Up to 5 lower-levels are
supported by the area.
monitorArming 0x4000104B The camera is already armed. Disarm the
camera and try again.
monitorSyncCfgNotSet 0x4000104C The system parameters are not configured.
monitorFdSyncing 0x4000104E Synchronizing. Try again after completing the
synchronization.
monitorParseFailed 0x4000104F Parsing camera information failed.
monitorCreatRootFaile 0x40001050 Creating resource node failed.
d
deleteArmingInfo 0x40001051 The camera is already . Disarm the camera and
try again.
cannotModify 0x40001052 Editing is not allowed. Select again.
172

cannotDel 0x40001053 Deletion is not allowed. Select again.
deviceExist 0x40001054 The device already exists.
IPErrorConnectFailed 0x40001056 Connection failed. Check the network port.
cannotAdd 0x40001057 Only the capture cameras can be added.
serverExist 0x40001058 The server already exists.
fullTextParamError 0x40001059 Incorrect full-text search parameters.
storParamError 0x4000105A Incorrect storage server parameters.
picServerFull 0x4000105B The storage space of picture storage server is
full.
NTPUnconnect 0x4000105C Connecting to NTP server failed. Check the
parameters.
storSerConnectFailed 0x4000105D Connecting to storage server failed. Check the
network port.
storSerLoginFailed 0x4000105E Logging in to storage server failed. Check the
user name and password.
searchSerConnectFaile 0x4000105F Connecting to full-text search server failed.
d Check the network port.
searchSerLoginFailed 0x40001060 Logging in to full-text search server failed.
Check the user name and password.
kafkaConnectFailed 0x40001061 Connecting to Kafka failed. Check the network
port.
mgmtConnectFailed 0x40001062 Connecting to system failed. Check the network
port.
mgmtLoginFailed 0x40001063 Logging in to system failed. Check the user
name and password.
TDAConnectFailed 0x40001064 Connecting to traffic data access server failed.
Checking the server status.
86sdkConnectFailed 0x40001065 Connecting to listening port of iVMS-8600
System failed. Check the parameters.
nameExist 0x40001066 Duplicated server name.
batchProcessFailed 0x40001067 Processing in batch failed.
173

IDNotExist 0x40001068 The server ID does not exist.
serviceNumberReache 0x40001069 No more service can be added.
sLimit
invalidServiceType. 0x4000106A Invalid service type.
clusterGetInfo 0x4000106B Getting cluster group information failed.
clusterDelNode 0x4000106C Deletion node failed.
clusterAddNode 0x4000106D Adding node failed.
clusterInstalling 0x4000106E Creating cluster…Do not operate.
clusterUninstall 0x4000106F Reseting cluster…Do not operate.
clusterInstall 0x40001070 Creating cluster failed.
clusterIpError 0x40001071 Invalid IP address of task scheduler server.
clusterNotSameSeg 0x40001072 The main node and sub node must be in the
same network segment.
clusterVirIpError 0x40001073 Automatically getting virtual IP address failed.
Enter manually.
clusterNodeUnadd 0x40001074 The specified main (sub) node is not added.
clusterNodeOffline 0x40001075 The task scheduler server is offline.
nodeNotCurrentIP 0x40001076 The analysis node of the current IP address is
required when adding main and sub nodes.
addNodeNetFailed 0x40001077 Adding node failed. The network disconnected.
needTwoMgmtNode 0x40001078 Two management nodes are required when
adding main and sub nodes.
ipConflict 0x40001079 The virtual IP address and data analysis server's
IP address conflicted.
ipUsed 0x4000107A The virtual IP address has been occupied.
cloudAlalyseOnline 0x4000107B The cloud analytic server is online.
virIP&mainIPnotSame 0x4000107C The virtual IP address is not in the same
NetSegment network segment with the IP address of main/
sub node.
getNodeDispatchInfoFa 0x4000107D Getting node scheduler information failed.
iled
174

unableModifyManage 0x4000107E Editing management network interface failed.
mentNetworkIP The analysis board is in the cluster.
notSpecifyVirtualIP 0x4000107F Virtual IP address should be specified for main
and sub cluster.
armingFull 0x40001080 No more device can be armed.
armingNoFind 0x40001081 The arming information does not exist.
disArming 0x40001082 Disarming failed.
getArmingError 0x40001084 Getting arming information failed.
refreshArmingError 0x40001085 Refreshing arming information failed.
ArmingPlateSame 0x40001086 The license plate number is repeatedly armed.
ArmingParseXLSError 0x40001087 Parsing arming information file failed.
ArmingTimeError 0x40001088 Invalid arming time period.
ArmingSearchTimeErro 0x40001089 Invalid search time period.
r
armingRelationshipRea 0x4000108A No more relation can be created.
chesLimit
duplicateAarmingNam 0x4000108B The relation name already exists.
e
noMoreArmingListAdd 0x4000108C No more blocklist library can be armed.
ed
noMoreCamerasAdded 0x4000108D No more camera can be armed.
noMoreArmingListAdd 0x4000108E No more library can be linked to the camera.
edWithCamera
noMoreArmingPeriodA 0x4000108F No more time period can be added to the
dded arming schedule.
armingPeriodsOverlap 0x40001090 The time periods in the arming schedule are
ped overlapped.
noArmingAlarmInfo 0x40001091 The alarm information does not exist.
armingAlarmUnRead 0x40001092 Getting number of unread alarms failed.
getArmingAlarmError 0x40001093 Getting alarm information failed.
175

searchByPictureTimed 0x40001094 Searching picture by picture timeout. Search
Out again.
comparisonTimeRange 0x40001095 Comparison time period error.
Error
selectMonitorNumber 0x40001096 No more monitoring point ID can be filtered.
UpperLimit
noMoreComparisonTas 0x40001097 No more comparison task can be executed at
ksAdded the same time.
GetComparisonResultF 0x40001098 Getting comparison result failed.
ailed
comparisonTypeError 0x40001099 Comparison type error.
comparisonUnfinished 0x4000109A The comparison is not completed.
facePictureModelInvali 0x4000109B Invalid face model.
d
duplicateLibraryName. 0x4000109C The library name already exists.
noRecord 0x4000109D No record found.
countingRecordsFailed. 0x4000109E Calculate the number of records failed.
getHumanFaceFrameF 0x4000109F Getting face thumbnail from the picture failed.
ailed
modelingFailed. 0x400010A0 Modeling face according to picture URL failed.
1V1FacePictureCompar 0x400010A1 Comparison 1 VS 1 face picture failed.
isonFailed
libraryArmed 0x400010A2 The blocklist library is armed.
licenseExeedLimit 0x400010A3 Dongle limited.
licenseExpired 0x400010A4 Dongle expired.
licenseDisabled 0x400010A5 Unavailable dongle.
licenseNotExist 0x400010A6 The dongle does not exist.
SessionExpired 0x400010A7 Session expired .
beyondConcurrentLimi 0x400010A8 Out of concurrent limit.
t
stopSync 0x400010A9 Synchronization stopped.
176

getProgressFaild 0x400010AA Getting progress failed.
uploadExtraCaps 0x400010AB No more files can be uploaded.
timeRangeError 0x400010AC Time period error.
dataPortNotConnected 0x400010AD The data port is not connected.
addClusterNodeFailed 0x400010AE Adding to the cluster failed. The device is
already added to other cluster.
taskNotExist 0x400010AF The task does not exist.
taskQueryFailed 0x400010B0 Searching task failed.
modifyTimeRuleFailed 0x400010B2 The task already exists. Editing time rule is not
allowed.
modifySmartRuleFailed 0x400010B3 The task already exists. Editing VAC rule is not
allowed.
queryHistoryVideoFaile 0x400010B4 Searching history video failed.
d
addDeviceFailed 0x400010B5 Adding device failed.
addVideoFailed 0x400010B6 Adding video files failed.
deleteAllVideoFailed 0x400010B7 Deleting all video files failed.
createVideoIndexFailed 0x400010B8 Indexing video files failed.
videoCheckTypeFailed 0x400010B9 Verifying video files types failed.
configStructuredAddre 0x400010BA Configuring IP address of structured server
ssFailed failed.
configPictureServerAd 0x400010BB Configuring IP address of picture storaged
dressFailed server failed.
storageServiceIPNotExi 0x400010BD The storage server IP address does not exist.
st
syncBackupDatabaseFa 0x400010BE Synchronizing sub database failed. Try again.
iled
syncBackupNTPTimeFa 0x400010BF Synchronizing NTP time of sub server failed.
iled
clusterNotSelectLoopb 0x400010C0 Loopbacl address is not supported by the main
ackAddress or sub cluster.
177

addFaceRecordFailed 0x400010C1 Adding face record failed.
deleteFaceRecordFaile 0x400010C2 Deleting face record failed.
d
modifyFaceRecordFaile 0x400010C3 Editing face record failed.
d
queryFaceRecordFailed 0x400010C4 Searching face record failed.
faceDetectFailed 0x400010C5 Detecting face failed.
libraryNotExist 0x400010C6 The library does not exist.
blackListQueryExportin 0x400010C7 Exporting matched blocklists.
g
blackListQueryExporte 0x400010C8 The matched blocklists are exported.
d
blackListQueryStopExp 0x400010C9 Exporting matched blocklists is stopped.
orting
blackListAlarmQueryEx 0x400010CA Exporting matched blocklist alarms.
porting
blackListAlarmQueryEx 0x400010CB The matched blocklists alarms are exported.
ported
blackListAlarmQuerySt 0x400010CC Exporting matched blocklist alarms is stopped.
opExporting
getBigDataCloudAnalys 0x400010CD Getting big data cloud analytic information
isFailed failed.
setBigDataCloudAnalys 0x400010CE Configuring big data cloud analytic failed.
isFailed
submitMapSearchFaile 0x400010CF Submitting search by picture task failed.
d
controlRelationshipNot 0x400010D0 The relation does not exist.
Exist
getHistoryAlarmInfoFai 0x400010D1 Getting history alarm information failed.
led
getFlowReportFailed 0x400010D2 Getting people counting report failed.
addGuardFailed 0x400010D3 Adding arming configuration failed.
178

deleteGuardFailed 0x400010D4 Deleting arming configuration failed.
modifyGuardFailed 0x400010D5 Editing arming configuration failed.
queryGuardFailed 0x400010D6 Searching arming configurations failed.
uploadUserSuperCaps 0x400010D7 No more user information can be uploaded.
bigDataServerConnect 0x400010D8 Connecting to big data server failed.
Failed
microVideoCloudRequ 0x400010D9 Adding response information of micro video
estInfoBuildFailed cloud failed.
microVideoCloudRespo 0x400010DA Parsing response information of micro video
nseInfoBuildFailed cloud failed.
transcodingServerRequ 0x400010DB Adding response information of transcoding
estInfoBuildFailed server failed.
transcodingServerResp 0x400010DC Parsing response information of transcoding
onseInfoParseFailed server failed.
transcodingServerOffli 0x400010DD Transcoding server is offline.
ne
microVideoCloudOfflin 0x400010DE Micro video cloud is offline.
e
UPSServerOffline 0x400010DF UPS monitor server is offline.
statisticReportRequestI 0x400010E0 Adding response information of statistics report
nfoBuildFailed failed.
statisticReportRespons 0x400010E1 Parsing response information of statistics report
eInfoParseFailed failed.
DisplayConfigInfoBuild 0x400010E2 Adding display configuration information failed.
Failed
DisplayConfigInfoParse 0x400010E3 Parsing display configuration information failed.
Failed
DisplayConfigInfoSaveF 0x400010E4 Saving display configuration information failed.
ailed
notSupportDisplayConf 0x400010E5 The display configuration type is not supported.
igType
passError 0x400010E7 Incorrect password.
179

upgradePackageLarge 0x400010EB Too large upgrade package.
sesssionUserReachesLi 0x400010EC No more user can log in via session.
mit
ISO 0x400010ED Invalid ISO8601 time format.
8601TimeFormatError
clusterDissolutionFaile 0x400010EE Deleting cluster failed.
d
getServiceNodeInfoFail 0x400010EF Getting service node information failed.
ed
getUPSInfoFailed 0x400010F0 Getting UPS configuration information failed.
getDataStatisticsRepor 0x400010F1 Getting data statistic report failed.
tFailed
getDisplayConfigInfoFai 0x400010F2 Getting display configuration failed.
led
namingAnalysisBoardN 0x400010F3 Renaming analysis board is not allowed.
otAllowed
onlyDrawRegionsOfCo 0x400010F4 Only drawing convex polygon area is supported.
nvexPolygon
bigDataServerRespons 0x400010F5 Parsing response message of big data service
eInfoParseFailed failed.
bigDataServerReturnFa 0x400010F6 No response is returned by big data service.
iled
microVideoReturnFaile 0x400010F7 No response is returned by micro video cloud
d service.
transcodingServerRetu 0x400010F8 No response is returned by transcoding service.
rnFailed
UPSServerReturnFailed 0x400010F9 No response is returned by UPS monitoring
service.
forwardingServer 0x400010FA No response is returned by forwarding service.
ReturnFailed
storageServer 0x400010FB No response is returned by storage service.
ReturnFailed
180

cloudAnalysisServerRet 0x400010FC No response is returned by cloud analytic
urnFailed service.
modelEmpty 0x400010FD No model is obtained.
mainAndBackupNodeC 0x400010FE Editing the management interface IP address of
annotModifyManagem main node and backup node is not allowed.
entNetworkInterfaceIP
IDTooLong 0x400010FF The ID is too long.
pictureCheckFailed 0x40001100 Detecting picture failed.
pictureModelingFailed 0x40001101 Modeling picture failed.
setCloudAnalsisDefault 0x40001102 Setting default province of cloud analytic
ProvinceFailed service failed.
InspectionAreasNumbe 0x40001103 No more detection regions can be added.
rExceedLimit
picturePixelsTooLarge 0x40001105 The picture resolution is too high.
picturePixelsTooSmall 0x40001106 The picture resolution is too low.
storageServiceIPEmpty 0x40001107 The storage server IP address is required.
bigDataServerRequestI 0x40001108 Creating request message of big data service
nfoBuildFail failed.
analysiTimedOut 0x40001109 Analysis time out.
high- 0x4000110A Please enable high-performance mode.
performanceModeDisa
bled.
configuringUPSMonito 0x4000110B Configurating the UPS monitoring server time
ringServerTimedOut out. Check IP address.
cloudAnalysisRequestI 0x4000110C Creating request message of cloud analytic
nformationBuildFailed service failed.
cloudAnalysisResponse 0x4000110D Parsing response message of cloud analytic
InformationParseFailed service failed.
allCloudAnalysisInterfa 0x4000110E Calling API for cloud analytic service failed.
ceFailed
cloudAnalysisModelCo 0x4000110F Model comparison of cloud analytic service
mpareFailed failed.
181

cloudAnalysisFacePictu 0x40001110 Getting face quality grading of cloud analytic
reQualityRatingFailed service failed.
cloudAnalysisExtractFe 0x40001111 Extracting feature of cloud analytic service
aturePointsFailed failed.
cloudAnalysisExtractPr 0x40001112 Extracting property of cloud analytic service
opertyFailed failed.
getAddedNodeInformat 0x40001113 Getting the added nodes information of data
ionFailed analysis server failed.
noMoreAnalysisUnitsA 0x40001114 No more data analysis servers can be added.
dded
detectionAreaInvalid 0x40001115 Invalid detection region.
shieldAreaInvalid 0x40001116 Invalid shield region.
noMoreShieldAreasAd 0x40001117 No more shield region can be drawn.
ded
onlyAreaOfRectangleS 0x40001118 Only drawing rectangle is allowed in detection
hapeAllowed area.
numberReachedLlimit 0x40001119 Number reached the limit.
wait1~3MinutesGetIPAf 0x4000111A Wait 1 to 3 minutes to get IP address after
terSetupDHCP configuring DHCP.
plannedTimeMustbeH 0x4000111B Schedule must be half an hour.
alfAnHour
oneDeviceCannotBuild 0x4000111C Creating main and backup cluster requires at
Cluster least two devices.
updatePackageFileNot 0x4000111E Upgrade package is not uploaded.
Uploaded
highPerformanceTasks 0x4000111F Drawing detection area is not allowed under
NotSupportDrawingDe high-performance mode.
tectionRegions
controlCenterIDDoesN 0x40001120 The control center ID does not exist.
otExist
regionIDDoesNotExist 0x40001121 The area ID does not exist.
licensePlateFormatErro 0x40001122 Invalid license plate format.
r
182

managementNodeDoe 0x40001123 The operation is not supported.
sNotSupportThisOperat
ion
searchByPictureResour 0x40001124 The conditions for searching picture by picture
ceNotConfiged are not configured.
videoFileEncapsulation 0x40001125 The video container format is not supported.
FormatNotSupported
videoPackageFailure 0x40001126 Converting video container format failed.
videoCodingFormatNot 0x40001127 Video coding format is not supported.
Supported
monitorOfDeviceArmin 0x40001129 The camera is armed. Disarm it and try again.
gdeleteArmingInfo
getVideoSourceTypeFai 0x4000112A Getting video source type failed.
led
smartRulesBuildFailed 0x4000112B Creating VAC rule failed.
smartRulesParseFailed 0x4000112C Parsing VAC rule failed.
timeRulesBuildFailed 0x4000112D Creating time rule failed.
timeRulesParseFailed 0x4000112E Parsing time rule failed.
monitoInfoInvalid 0x4000112F Invalid camera information.
addingFailedVersionMi 0x40001130 Adding failed. The device version mismatches.
smatches
theInformationReturne 0x40001131 No response is returned by the cloud analytic
dAfterCloudAnalysisIsE service.
mpty
selectingIpAddressOfH 0x40001132 Setting IP address for main node and backup
ostAndSpareNodeFaile node failed. Check the node status.
dCheckTheStatus
theSearchIdDoesNotEx 0x40001133 The search ID does not exist.
ist
theSynchronizationIdD 0x40001134 The synchronization ID does not exist.
oesNotExist
theUserIdDoesNotExist 0x40001136 The user ID does not exist.
183

theIndexCodeDoesNot 0x40001138 The index code does not exist.
Exist
theControlCenterIdDoe 0x40001139 The control center ID does not exist.
sNotExist
theAreaIdDoesNotExist 0x4000113A The area ID does not exist.
theArmingLinkageIdDo 0x4000113C The arming relationship ID does not exist.
esNotExist
theListLibraryIdDoesNo 0x4000113D The list library ID does not exist.
tExist
invalidCityCode 0x4000113E Invalid city code.
synchronizingThePass 0x4000113F Synchronizing backup system password failed.
wordOfSpareServerFail
ed
editingStreamingTypeIs 0x40001140 Editing streaming type is not supported.
NotSupported
switchingScheduledTas 0x40001141 Switching scheduled task to temporary task is
kToTemporaryTaskIsNo not supported.
tSupported
switchingTemporaryTas 0x40001142 Switching temporary task to scheduled task is
kToScheduledTaskIsNot not supported.
Supported
theTaskIsNotDispatche 0x40001143 The task is not dispatched or is updating.
dOrItIsUpdating
thisTaskDoesNotExist 0x40001144 This task does not exist in the cloud analytic
serice.
duplicatedSchedule 0x40001145 Schedule period cannot be overlapped.
continuousScheduleWi 0x40001146 The continuous schedule periods with same
thSameAlgorithmType algorithm type should be merged.
ShouldBeMerged
invalidStreamingTimeR 0x40001147 Invalid streaming time period.
ange
invalidListLibraryType 0x40001148 Invalid list library type.
184

theNumberOfMatched 0x40001149 The number of search results should be larger
ResultsShouldBeLarger than 0.
Than0
invalidValueRangeOfSi 0x4000114A Invalid similarity range.
milarity
invalidSortingType 0x4000114B Invalid sorting type.
noMoreListLibraryCanB 0x4000114C No more lists can be added to one device.
eLinkedToTheDevice
InvalidRecipientAddres 0x4000114D Invalid address format of result receiver.
sFormat
creatingClusterFailedT 0x4000114E Insert the dongle before creating cluster.
heDongleIsNotPlugged
In
theURLIsTooLong 0x4000114F No schedule configured for the task.
noScheduleIsConfigure 0x40001150 No schedule configured for the task.
dForTheTask
theDongleIsExpiried 0x40001151 Dongle has expired.
dongleException 0x40001152 Dongle exception.
invalidKey 0x40001153 Invalid authorization service key.
decryptionFailed 0x40001154 Decrypting authorization service failed.
encryptionFailed 0x40001155 Encrypting authorization service failed.
AuthorizeServiceRespo 0x40001156 Authorization service response exception.
nseError
incorrectParameter 0x40001157 Authorization service parameters error.
operationFailed 0x40001158 Operating authorization service error.
noAnalysisResourceOr 0x40001159 No cloud analytic resources or no data in the list
NoDataInTheListLibrary library.
calculationException 0x4000115A Calculation exception.
allocatingList 0x4000115B Allocating list.
thisOperationIsNotSup 0x4000115C This operation is not supported by the cloud
portedByTheCloudAnal analytic serice.
ytics
185

theCloudAnalyticsIsInt 0x4000115D The operation of cloud analytic serice is
errupted interrupted.
theServiceIsNotReady 0x4000115E The service is not ready.
searchingForExternalA 0x4000115F Searching external interfaces failed.
piFailed
noOnlineNode 0x40001160 No node is online.
noNodeAllocated 0x40001161 No allocated node.
noMatchedList 0x40001162 No matched list.
allocatingFailedTooMa 0x40001163 Allocation failed. Too many lists of big data
nyFacePictureLists service.
searchIsNotCompleted 0x40001164 Current searching is not completed. Search
SearchAgain again.
allocatingListIsNotCom 0x40001165 Allocating list is not completed.
pleted
searchingForCloudAnal 0x40001166 Searching cloud analytic serice overtime.
yticsResultsFailed
noDataOfTheCurrentLi 0x40001167 No data in the current library. Make sure there
braryFound is data in the Hbase.
noFacePictureLibraryIs 0x40001168 No face picture library is armed for big data
Armed service.
noAvailableDataSlicing 0x40001169 Invalid standard version information.
VersionInformationAr
mFirstAndSliceTheData
duplicatedOperationDa 0x4000116A Slicing failed. Duplicated operation.
taSlicingIsExecuting
slicinDataFailedNoArm 0x4000116B Slicing failed. No arming information in the face
edFacePictureLibrary big data.
GenerateBenchmarkFil 0x4000116C Generating sliced file failed. Slice again.
eFailedSlicingAgain
NonprimaryNodeIsPro 0x4000116D Slicing is not allowed by the backup node.
hibitedFromSlcingData
NoReadyNodeToCluste 0x4000116E Creating the cluster failed. No ready node.
rServers
186

NodeManagementServ 0x4000116F The node management server is offline.
iceIsOffline
theCamera(s)OfTheCo 0x40001170 Some cameras in control center are already
ntrolCenterAreAlready armed. Disarm them and try again.
Armed.DisarmThemFir
st
theCamera(s)OfTheAre 0x40001171 Some cameras in this area are already armed.
aAreAlreadyArmed.Dis Disarm them and try again.
armThemFirst
configuringHigh- 0x40001172 Configuring high frequency people detection
frequencyPeopleDetect failed.
ionFailed
searchingForHigh- 0x40001173 Searching detection event logs of high-
frequencyPeopleDetect frequency people detection failed.
ionLogsFailed.
gettingDetailsOfSearch 0x40001174 Getting the search result details of frequently
edHigh- appeared person alarms failed.
frequencyPeopleDetect
ionLogsFailed.
theArmedCamerasAlre 0x40001175 Some cameras in control center are already
adyExistInTheControlC armed.
enter
disarmingFailedTheCa 0x40001177 Disarming failed. The camera is not armed.
meraIsNotArmed
noDataReturned 0x40001178 No response is returned by the big data service.
preallocFailure 0x40001179 Pre-allocating algorithm resource failed.
overDogLimit 0x4000117A Configuration failed. No more resources can be
pre-allocated.
analysisServicesDoNot 0x4000117B Not supported.
Support
commandAndDispatch 0x4000117C Scheduling service of cloud analytic serice error.
ServiceError
engineModuleError 0x4000117D Engine module of cloud analytic serice error.
187

streamingServiceError 0x4000117E Streaming component of cloud analytic serice
error.
faceAnalysisModuleErr 0x4000117F Face analysis module of cloud analytic serice
or error.
vehicleAnalysisModule 0x40001180 Vehicle pictures analytic module of cloud
Error analytic serice error.
videoStructuralAnalysis 0x40001181 Video structuring module of cloud analytic
ModuleError serice error.
postprocessingModule 0x40001182 Post-processing module of cloud analytic serice
Error error.
frequentlyAppearedPe 0x40001183 Frequently appeared person alarm is already
rsonAlarmIsAlreadyCo armed for blocklist library.
nfiguredForListLibrary
creatingListLibraryFaile 0x40001184 Creating list library failed.
d
invalidIdentiryKeyOfLis 0x40001185 Invalid identity key of list library.
tLibrary
noMoreDevicesCanBe 0x40001186 No more camera can be added.
Armed
settingAlgorithmTypeF 0x40001187 Allocating task resource failed.
orDeviceFailed
gettingHighFrequencyP 0x40001188 Setting frequently appeared person alarm
ersonDetectionAlarmIn failed.
formationFailed
invalidSearchConfition 0x40001189 Invalid result.
theTaskIsNotComplete 0x4000118B The task is not completed.
d
resourceOverRemainLi 0x4000118C No more resource can be pre-allocated.
mit
frequentlyAppearedPe 0x4000118D The frequently appeared person alarm of this
rsonAlarmIs camera is configured. Delete the arming
AlreadyConfiguredForT information and try again.
heCameraDisarmFirstA
ndTryAgain
188

switchtimedifflesslimit 0x4000123b Time difference between power on and off
should be less than 10 minutes.
associatedFaceLibNum 0x40001279 Maximum number of linked face picture
OverLimit libraries reached.
noMorePeopleNumCh 0x4000128A Maximum number of people number changing
angeRulesAdded rules reached.
noMoreViolentMotion 0x4000128D Maximum number of violent motion rules
RulesAdded reached.
noMoreLeavePositionR 0x4000128E Maximum number of leaving position rules
ulesAdded reached.
SMRDiskNotSupportRa 0x40001291 SMR disk does not support RAID.
id
OnlySupportHikAndCus 0x400012A3 IPv6 camera can only be added via Device
tomProtocol Network SDK or custom protocols.
vehicleEnginesNoReso 0x400012A6 Insufficient vehicle engine resources.
urce
noMoreRunningRulesA 0x400012A9 Maximum number of running rules reached.
dded
noMoreGroupRulesAd 0x400012AA Maximum number of people gathering rules
ded reached.
noMoreFailDownRules 0x400012AB Maximum number of people falling down rules
Added reached.
noMorePlayCellphone 0x400012AC Maximum number of playing cellphone rules
RulesAdded reached.
ruleEventTypeDuplicat 0x400012C8 Event type duplicated.
e
noMoreRetentionRules 0x400015AD Maximum number of people retention rules
Added reached.
noMoreSleepOnDutyR 0x400015AE Maximum number of sleeping on duty rules
ulesAdded reached.
polygonNotAllowCrossi 0x400015C2 Polygons are not allowed to cross.
ng
189

configureRuleBeforeAd 0x400015F8 Advanced parameters fail to be configured as
vanceParam no rule is configured, please configure rule
information first.
behaviorCanNotPackTo 0x40001603 The behavior model cannot be packaged as a
Pic picture algorithm.
noCluster 0x40001608 No cluster created.
NotAssociatedWithOw 0x400019C1 Current channel is not linked.
nChannel
AITargetBPCaptureFail 0x400019C5 Capturing reference picture for AI target
comparison failed.
AITargetBPToDSPFail 0x400019C6 Sending reference picture to DSP for AI target
comparison failed.
AITargetBPDuplicateNa 0x400019C7 Duplicated name of reference picture for AI
me target comparison.
audioFileNameWrong 0x400019D0 Incorrect audio file name.
audioFileImportFail 0x400019D1 Importing audio file failed.
NonOperationalStandb 0x400019F0 Non-operational hot spare.
yMachine
MaximumNumberOfD 0x400019F1 The maximum number of devices reached.
evices
StandbyMmachineCan 0x400019F2 The hot spare cannot be deleted.
notBeDeleted
alreadyRunning 0x40002026 The application program is running.
notRunning 0x40002027 The application program is stopped.
packNotFound 0x40002028 The software packet does not exist.
alreadyExist 0x40002029 The application program already exists.
noMemory 0x4000202A Insufficient memory.
invalLicense 0x4000202B Invalid License.
noClientCertificate 0x40002036 The client certificate is not installed.
noCACertificate 0x40002037 The CA certificate is not installed.
190

authenticationFailed 0x40002038 Authenticating certificate failed. Check the
certificate.
clientCertificateExpired 0x40002039 The client certificate is expired.
clientCertificateRevocat 0x4000203A The client certificate is revoked.
ion
CACertificateExpired 0x4000203B The CA certificate is expired.
CACertificateRevocatio 0x4000203C The CA certificate is revoked.
n
connectFail 0x4000203D Connection failed.
loginNumExceedLimit 0x4000203F No more user can log in.
HDMIResolutionIllegal 0x40002040 The HDMI video resolution cannot be larger
than that of main and sub stream.
hdFormatFail 0x40002049 Formatting HDD failed.
formattingFailed 0x40002056 Formatting HDD failed.
encryptedFormattingFa 0x40002057 Formatting encrypted HDD failed.
iled
wrongPassword 0x40002058 Verifying password of SD card failed. Incorrect
password.
audioIsPlayingPleaseW 0x40002067 Audio is playing. Please wait.
ait
twoWayAudioInProgre 0x40002068 Two-way audio in progress. Please wait.
ssPleaseWait
calibrationPointNumFu 0x40002069 The maximum number of calibration points
ll reached.
completeTheLevelCalib 0x4000206A The level calibration is not set.
rationFirst
completeTheRadarCam 0x4000206B The radar-camera calibration is not set.
eraCalibrationFirst
pointsOnStraightLine 0x4000209C Calibrating failed. The calibration points cannot
be one the same line.
TValueLessThanOrEqua 0x4000209D Calibration failed. The T value of the calibration
lZero points should be larger than 0.
191

HBDLibNumOverLimit 0x40002092 The number of human body picture libraries
reaches the upper limit
theShieldRegionError 0x40002093 Saving failed. The shielded area should be the
ground area where the shielded object is
located.
theDetectionAreaError 0x40002094 Saving failed. The detection area should only
cover the ground area.
invalidLaneLine 0x40002096 Saving failed. Invalid lane line.
enableITSFunctionOfTh 0x400020A2 Enable ITS function of this channel first.
isChannelFirst
noCloudStorageServer 0x400020C5 No cloud storage server
NotSupportWithVideo 0x400020F3 This function is not supported.
Task
noDetectionArea 0x400050df No detection area
armingFailed 0x40008000 Arming failed.
disarmingFailed 0x40008001 Disarming failed.
clearAlarmFailed 0x40008002 Clearing alarm failed.
bypassFailed 0x40008003 Bypass failed.
bypassRecoverFailed 0x40008004 Bypass recovery failed.
outputsOpenFailed 0x40008005 Opening relay failed.
outputsCloseFailed 0x40008006 Closing relay failed.
registerTimeOut 0x40008007 Registering timed out.
registerFailed 0x40008008 Registering failed.
addedByOtherHost 0x40008009 The peripheral is already added by other
security control panel.
alreadyAdded 0x4000800A The peripheral is already added.
armedStatus 0x4000800B The partition is armed.
bypassStatus 0x4000800C Bypassed.
zoneNotSupport 0x4000800D This operation is not supported by the zone.
zoneFault 0x4000800E The zone is in fault status.
192

pwdConflict 0x4000800F Password conflicted.
audioTestEntryFailed 0x40008010 Enabling audio test mode failed.
audioTestRecoveryFaile 0x40008011 Disabling audio test mode failed.
d
addCardMode 0x40008012 Adding card mode.
searchMode 0x40008013 Search mode.
addRemoterMode 0x40008014 Adding keyfob mode.
registerMode 0x40008015 Registration mode.
exDevNotExist 0x40008016 The peripheral does not exist.
theNumberOfExDevLi 0x40008017 No peripheral can be added.
mited
sirenConfigFailed 0x40008018 Setting siren failed.
chanCannotRepeatedB 0x40008019 This channel is already linked by the zone.
inded
inProgramMode 0x4000801B The keypad is in programming mode.
inPaceTest 0x4000801C In pacing mode.
arming 0x4000801D Arming.
masterSlaveIsEnable 0x4000802c The main-sub relationship has taken effect, the
sub radar does not support this operation.
forceTrackNotEnabled 0x4000802d Mandatory tracking is disabled.
isNotSupportZoneConfi 0x4000802e This area does not support the zone type.
gByLocalArea
alarmLineCross 0x4000802f Trigger lines are overlapped.
zoneDrawingOutOfRan 0x40008030 The drawn zone is out of detection range.
ge
alarmLineDrawingOut 0x40008031 The drawn alarm trigger line is out of detection
OfRange range.
hasTargetInWarningAr 0x40008032 The warning zone already contains targets.
ea Whether to enable mandatory arming?
radarMoudleConnectF 0x40008033 Radar module communication failed.
ail
193

importCfgFilePassword 0x40008034 Incorrect password for importing configuration
Err files.
overAudioFileNumLimi 0x40008038 The number of audio files exceeds the limit.
t
audioFileNameIsLong 0x40008039 The audio file name is too long.
audioFormatIsWrong 0x4000803a The audio file format is invalid.
audioFileIsLarge 0x4000803b The size of the audio file exceeds the limit.
pircamCapTimeOut 0x4000803c Capturing of pircam timed out.
pircamCapFail 0x4000803d Capturing of pircam failed.
pircamIsCaping 0x4000803e The pircam is capturing.
audioFileHasExisted 0x4000803f The audio file already exists.
subscribeTypeErr 0x4000a016 This metadata type is not supported to be
subscribed.
EISError 0x4000A01C Electronic image stabilization failed. The smart
event function is enabled.
jpegPicWithAppendDat 0x4000A01D Capturing the thermal graphic failed. Check if
aError the temperature measurement parameters
(emissivity, distance, reflective temperature) are
configured correctly.
startAppFail / Starting running application program failed.
yuvconflict / The raw video stream conflicted.
overMaxAppNum / No more application program can be uploaded.
noFlash / Insufficient flash.
platMismatch / The platform mismatches.
emptyEventName 0x400015E0 Event name is empty.
sameEventName 0x400015E1 A same event name already exists.
emptyEventType 0x400015E2 Event type is required.
sameEventType 0x400015E3 A same event type already exists.
maxEventNameReache 0x400015E4 Maximum of events reached.
d
194

hotSpareNotAllowedEx 0x400015FC External storage is not allowed when hot spare
ternalStorage is enabled.
sameCustomProtocolN 0x400015FD A same protocol name already exists.
ame
maxPTZTriggerChannel 0x400015FE Maximum of channels linked with PTZ reached.
Reached
POSCanotAddHolidayPl 0x400015FF No POS events during holidays.
an
eventTypeIsTooLong 0x40001600 Event type is too long.
eventNameIsTooLong 0x40001601 Event name is too long.
PerimeterEnginesNoRe 0x40001602 No more perimeter engines.
source
invalidProvinceCode 0x40001607 Invalid province code.
StatusCode=5

badXmlFormat 0x50000001 Invalid XML format.
StatusCode=6

badParameters 0x60000001 Invalid parameter.
badHostAddress 0x60000002 Invalid host IP address.
badXmlContent 0x60000003 Invalid XML content.
badIPv4Address 0x60000004 Invalid IPv4 address.
badIPv6Address 0x60000005 Invalid IPv6 address.
conflictIPv4Address 0x60000006 IPv4 address conflicted.
conflictIPv6Address 0x60000007 IPv6 address conflicted.
badDomainName 0x60000008 Invalid domain name.
connectSreverFail 0x60000009 Connecting to server failed.
195

conflictDomainName 0x6000000A Domain name conflicted.
badPort 0x6000000B Port number conflicted.
portError 0x6000000C Port error.
exportErrorData 0x6000000D Importing data failed.
badNetMask 0x6000000E Invalid sub-net mask.
badVersion 0x6000000F Version mismatches.
badDevType 0x60000010 Device type mismatches.
badLanguage 0x60000011 Language mismatches.
incorrentUserNameOrPasswor 0x600000012 Incorrect user name or
d password.
invalidStoragePoolOfCloudServ 0x600000013 Invalid storage pool. The
er storage pool is not configured
or incorrect ID.
noFreeSpaceOfStoragePool 0x600000014 Storage pool is full.
riskPassword 0x600000015 Risky password.
UnSupportCapture 0x600000016 Capturing in 4096*2160 or
3072*2048 resolution is not
supported when H.264+ is
enabled.
userPwdLenUnder8 0x60000023 At least two kinds of
characters, including digits,
letters, and symbols, should be
contained in the password.
userPwdNameSame 0x60000025 Duplicated password.
userPwdNameMirror 0x60000026 The password cannot be the
reverse order of user name.
beyondARGSRangeLimit 0x60000027 The parameter value is out of
limit.
DetectionLineOutofDetectionR 0x60000085 The rule line is out of region.
egion
196

DetectionRegionError 0x60000086 Rule region error. Make sure
the rule region is convex
polygon.
DetectionRegionOutOfCountin 0x60000087 The rule region must be
gRegion marked as red frame.
PedalAreaError 0x60000088 The pedal area must be in the
rule region.
DetectionAreaABError 0x60000089 The detection region A and B
must be in the a rule frame.
ABRegionCannotIntersect 0x6000008a Region A and B cannot be
overlapped.
customHBPIDError 0x6000008b Incorrect ID of custom human
body picture library
customHBPIDRepeat 0x6000008c Duplicated ID of custom human
body picture library
dataVersionsInHBDLibMismatc 0x6000008d Database versions mismatches
hes of human body picture library
invalidHBPID 0x6000008e Invalid human body picture PID
invalidHBDID 0x6000008f Invalid ID of human body
picture library
humanLibraryError 0x60000090 Error of human body picture
library
humanLibraryNumError 0x60000091 No more human body picture
library can be added
humanImagesNumError 0x60000092 No more human body picture
can be added
noHumanInThePicture 0x60000093 Modeling failed, no human
body in the picture
analysisEnginesNoResourceErr 0x60001000 No analysis engine.
or
analysisEnginesUsageExcced 0x60001001 The engine usage is
overloaded.
197

PicAnalysisNoResourceError 0x60001002 No analysis engine provided for
picture secondary recognition.
analysisEnginesLoadingError 0x60001003 Initializing analysis engine.
analysisEnginesAbnormaError 0x60001004 Analysis engine exception.
analysisEnginesFacelibImportin 0x60001005 Importing pictures to face
g picture library. Failed to edit
analysis engine parameters.
analysisEnginesAssociatedChan 0x60001006 The analysis engine is linked to
nel channel.
smdEncodingNoResource 0x60001007 Insufficient motion detection
encoding resources.
smdDecodingNoResource 0x60001008 Insufficient motion detection
decoding resources.
diskError 0x60001009 HDD error.
diskFull 0x6000100a HDD full.
facelibDataProcessing 0x6000100b Handling face picture library
data.
capturePackageFailed 0x6000100c Capturing packet failed.
capturePackageProcessing 0x6000100d Capturing packet.
noSupportWithPlaybackAbstra 0x6000100e This function is not supported.
ct Playback by video synopsis is
enabled.
insufficientNetworkBandwidth 0x6000100f Insufficient network
bandwidth.
tapeLibNeedStopArchive 0x60001010 Stop the filing operation of
tape library first.
identityKeyError 0x60001011 Incorrect interaction command.
identityKeyMissing 0x60001012 The interaction command is
lost.
noSupportWithPersonDensityD 0x60001013 This function is not supported.
etect The people density detection is
enabled.
198

ipcResolutionOverflow 0x60001014 The configured resolution of
network camera is invalid.
ipcBitrateOverflow 0x60001015 The configured bit rate of
network camera is invalid.
tooGreatTimeDifference 0x60001016 Too large time difference
between device and server.
noSupportWithPlayback 0x60001017 This function is not supported.
Playback is enabled.
channelNoSupportWithSMD 0x60001018 This function is not supported.
Motion detection is enabled.
channelNoSupportWithFD 0x60001019 This function is not supported.
Face capture is enabled.
illegalPhoneNumber 0x6000101a Invalid phone number.
illegalCertificateNumber 0x6000101b Invalid certificate No.
linkedCameraOutLimit 0x6000101c Connecting camera timed out.
achieveMaxChannelLimit 0x6000101e No more channels are allowed.
humanMisInfoFilterEnabledCha 0x6000101f No more channels are allowed
nNumError to enable preventing false
alarm.
humanEnginesNoResource 0x60001020 Insufficient human body
analysis engine resources.
taskNumberOverflow 0x60001021 No more tasks can be added.
collisionTimeOverflow 0x60001022 No more comparison duration
can be configured.
invalidTaskID 0x60001023 Invalid task ID.
eventNotSupport 0x60001024 Event subscription is not
supported.
invalidEZVIZSecretKey 0x60001034 Invalid verification code for Hik-
Connect.
needDoubleVerification 0x60001042 Double verification required
noDoubleVerificationUser 0x60001043 No double verification user
199

timeSpanNumOverLimit 0x60001044 Max. number of time buckets
reached
channelNumOverLimit 0x60001045 Max. number of channels
reached
noSearchIDResource 0x60001046 Insufficient searchID resources
noSupportDeleteStrangerLib 0x60001051 Deleting stranger library is not
supported
noSupportCreateStrangerLib 0x60001052 Creating stranger library is not
supported
behaviorAnalysisRuleInfoError 0x60001053 Abnormal event detection rule
parameters error.
safetyHelmetParamError 0x60001054 Hard hat parameters error.
OneChannelOnlyCanBindOneE 0x60001077 No more engines can be
ngine bound.
engineTypeMismatch 0x60001079 Engine type mismatched.
badUpgradePackage 0x6000107A Invalid upgrade package.
AudioFileNameDuplicate 0x60001135 Duplicated audio file name.
CurrentAudioFileAIRuleInUseAl 0x60001136 The AI rule linkage related to
readyDelete current audio file has been
deleted.
TransitionUseEmmc 0x60002000 Starting device failed. The
EMMC is overused.
AdaptiveStreamNotEnabled 0x60002001 The stream self-adaptive
function is not enabled.
AdaptiveStreamAndVariableBit 0x60002002 Stream self-adptive and
rateEnabled variable bitrate function cannot
be enabled at the same time.
noSafetyHelmetRegion 0x60002023 The hard hat detection area is
not configured (if users save
their settings without
configuring the arming area,
they should be prompted to
configure one).
200

unclosedSafetyHelmet 0x60002024 The hard hat detection is
enabled (If users save their
settings after deleting the
arming area, they should be
prompted to disable hard hat
detection first and then delete
the arming area).
width/ 0x6000202C The width/height ratio of the
heightRatioOfPictureError uploaded picture should be in
the range from 1:2 to 2:1.
PTZNotInitialized 0x6000202E PTZ is not initialized.
PTZSelfChecking 0x6000202F PTZ is self-checking.
PTZLocked 0x60002030 PTZ is locked.
advancedParametersError 0x60002031 Auto-switch interval in
advanced parameters cannot
be shorter than parking
tolerance for illegal parking
detection in speed dome rule
settings.
resolutionError 0x60005003 Invalid resolution
deployExceedMax 0x60006018 The arming connections exceed
the maximum number.
detectorTypeMismatch 0x60008000 The detector type mismatched.
nameExist 0x60008001 The name already exists.
uploadImageSizeError 0x60008016 The size of the uploaded
picture is larger than 5 MB.
laneAndRegionOverlap / The lanes are overlapped.
unitConfigurationNotInEffect / Invalid unit parameter.
ruleAndShieldingMaskConflict / The line-rule region overlaps
with the shielded area.
wholeRuleInShieldingMask / There are complete
temperature measurement
rules in the shielded area.
201

LogDiskNotSetReadOnlyInGrou 0x60001100 The log HDD in the HDD group
pMode cannot be set to read-only.
LogDiskNotSetReDundancyInGr 0x60001101 The log HDD in the HDD group
oupMode cannot be set to redundancy.
holidayNameContainChineseOr 0x60001080 No Chinese and special
SpecialChar characters allowed in holiday
name.
genderValueError 0x60001081 Invalid gender.
certificateTypeValueError 0x60001082 Invalid identification type.
personInfoExtendValueIsTooLo 0x60001083 The length of customized tags
ng exceeds limit.
personInfoExtendValueContain 0x60001084 Invalid characters are not
sInvalidChar allowed in customized tags of
the face picture library.
excelHeaderError 0x60001085 Excel header error.
intelligentTrafficMutexWithHig 0x60008014 Please disable all functions of
hFrames traffic incident detection,
violation enforcement, and
traffic data collection, or adjust
the video frame rate to that
lower than 50 fps.
intelligentTrafficMutexWithHig 0x60008018 Please disable all functions of
hFramesEx traffic incident detection,
violation enforcement, traffic
data collection, and vehicle
detection, or adjust the video
frame rate to that lower than
50 fps.
StatusCode=7
SubStatusCode Error Code Description

rebootRequired 0x70000001 Reboot to take effect.
202

Device Network SDK (Queue Management) - Developer Guide - V6.0.2.X - 20230330

Uploaded by

Copyright:

Available Formats

Device Network SDK (Queue Management) - Developer Guide - V6.0.2.X - 20230330

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Device Network SDK (Queue Management) - Developer Guide - V6.0.2.X - 20230330

Uploaded by

Copyright:

Available Formats

3.16 NET_DVR_SetDVRMessageCallBack_V50 .......................................................................... 32

A.23 NET_ALARM_RECORDFILE_LOSS ..................................................................................... 102

4.8 /ISAPI/Intelligent/channels/<ID>/personQueueDetection?format=json ............................. 47

Figure 1-1 Queue Management Overall Flow

Figure 1-2 People Queuing-Up

Waiting Time Detection

Figure 1-3 Waiting Time Detection

1.2 Update History

Summary of Changes in Version 6.0.2.36_May, 2019

Summary of Changes in Version 6.0.2.X_Mar., 2019

Chapter 2 Typical Applications

2.1 Alarm and Event Receiving

2.1.1 Configure Queue Management Alarm

● Make sure you have called NET_DVR_Login_V40 to log in to device.

Figure 2-1 Programming Flow of Configuring Queue Management Alarm

2.1.2 Receive Alarm/Event in Arming Mode

● Make sure you have called NET_DVR_Login_V40 to log in to the device.

configurations for details.

Figure 2-2 Programming Flow of Receiving Alarm/Event in Arming Mode

//Set alarm callback function

char szSubscribe[1024] = {0};

2.1.3 Receive Alarm/Event in Listening Mode

configurations for details.

Figure 2-3 Programming Flow of Receiving Alarm/Event in Listening Mode

2.2 Search Queue Management Report or Data

Search People Queuing-Up Report

Search Waiting Time Detection Report

The report details is returned in the message JSON_PersonQueueTimeResult by output pointer

Search Queue Management Raw Data

Figure 2-4 Interaction Process of Raw Data Search

Figure 2-5 Compare Queuing-Up People Amount for Different Regions

Figure 2-7 Compare Queuing-Up Duration for Different Regions

Figure 2-8 Compare Queuing-Up Duration for Different Queue Lengths

Chapter 3 API Reference

Login Status Callback Function

Member Data Type Description

void* const lpInBuff

Table 3-1 NET_SDK_INIT_CFG_TYPE

Input Content Details Structure of Message Transmission API

Member Data Type Description

Member Data Type Description

Parameter of NET_​DVR_​STDXMLConfig Component of Text Protocol

switch(struPlateResult.struPlateInfo.byColor)//License plate color

void CALLBACK MessageCallbackNo2(LONG lCommand, NET_DVR_ALARMER *pAlarmer, char *pAlarmInfo, DWORD

switch(struPlateResult.struPlateInfo.byColor)//License plate color

//Set alarm callback function

//Alarm information type to upload: 0-History Alarm (NET_DVR_PLATE_RESULT), 1-Real-Time Alarm

LONG lHandle = NET_DVR_SetupAlarmChan_V41(lUserID,&struSetupParam);

Callback Function Definition

Chapter 4 Request URL

Request URI Definition

Table 4-1 GET /ISAPI/Intelligent/channels/<ID>/capabilities

Request URI Definition

Table 4-2 GET /ISAPI/Intelligent/channels/<ID>/personQueueDetection/capabilities?format=json

Request URI Definition

Table 4-3 POST /ISAPI/Intelligent/channels/<ID>/personQueueDetection/queueCountingFile?

Request URI Definition

Table 4-4 POST /ISAPI/Intelligent/channels/<ID>/personQueueDetection/queueCountingResult?

Parameter of NET_DVR_STDXMLConfig Component of Text Protocol

void CALLBACK MessageCallbackNo2(LONG lCommand, NET_DVR_ALARMER pAlarmer, char pAlarmInfo, DWORD

/required, float, y-coordinate, it is ranging from 0.000 to 1/

/optional, integer, minimum number of queuing-up people, range: from 0 to 60/

/optional, string, request URL/