Member |
Data Type |
Description |
---|---|---|
dwSize |
DWORD |
Structure size. |
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_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:
|
byBrokenNetHttp |
BYTE |
ANR type, which is represented by bit and should be supported by device:
|
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.
|
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. |
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.