Difference between revisions of "Command:13"
From Awesome Baozam
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==SET Monitor== | ==SET Monitor== | ||
| − | + | * is an alias of [[CMD:12|response to GET Monitor]] | |
| + | * used for set monitor | ||
| + | |||
{{CMD:12}} | {{CMD:12}} | ||
<noinclude> | <noinclude> | ||
As response to this command should be send | As response to this command should be send | ||
| − | + | * [[cmd:14]] response to Monitor SET | |
| − | + | and can be send | |
| + | * [[CMD:16|Monitor packets]] | ||
{{CMD:14}} | {{CMD:14}} | ||
{{CMD:16}} | {{CMD:16}} | ||
Latest revision as of 16:04, 18 November 2015
SET Monitor
- is an alias of response to GET Monitor
- used for set monitor
Response to GET Monitor
1 cmd type 2 cmd id // set by server 1 monitors count // max 256
monitors*
4 addr 1 on/off
As response to this command should be send
- cmd:14 response to Monitor SET
and can be send
response to SET Monitor
- is an alias of response to GET Monitor
- used in answer to SET Monitor
Response to GET Monitor
1 cmd type 2 cmd id // set by server 1 monitors count // max 256
monitors*
4 addr 1 on/off
Monitor packet
- is an alias of response to GET
- used for sending monitoring data. Sending ON/OFF regulated by SET Monitor
response to GET
1 cmd type 2 cmd id // set by server 1 monitors count // max 256
monitor*
4 address 1 parameter type [wl] values count; if this > 1 then pt < 0 and this byte presents in the packet v* value; see details into parameter type
