Go to documentation repository
Page History
...
The message parameters are described in the table below.
Parameter | Description |
Object type | Object type (GRABBER, CAM, or MONITOR) |
Object ID | The object ID set during creation of the object in Axxon PSIM |
Action | Action (command) |
Parameter <Value> | Parameter name. The value is enclosed by angle brackets |
To check the network, you can use the <trash:N> parameter, where N is the length of the parameter in bytes. As a result, a text string of a given length will be generated in the message, containing numbers and Latin letters. The parameter name can be anything. For example, if you add the following parameter to the message
| Code Block |
|---|
param1<trash:128> |
the following text string will be generated in response
| Code Block |
|---|
param1<88n9ESCAFyBfHyXzIoPpOF1GirSmlMJ1Ahh9oYZDIQou2RgWY0jXlaL2HhaX9ZY2oKfkQYLuPLg8bGNQK6OumvQjVp1G7BEt1wFsw6FApzIZ3NbBUJNCKnP335OlgEwN> |
Example 1. Setting camera 1 to recording mode.
...
SendMsg(id,msg);
| Info | ||
|---|---|---|
| ||
| The SET_DRIVES command includes the ID of any of the video capture cards created in the system. |
| Info | ||
|---|---|---|
| ||
| The SET_DRIVES command does not change the video archiving settings set in the system. |
...
Overview
Content Tools