Difference between revisions of "Command:33"
From Awesome Baozam
| (7 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
if file_size=0 it means that device should delete the file | if file_size=0 it means that device should delete the file | ||
| − | + | ---- | |
| − | on error device should send cmd: | + | on error device should send [[cmd:38]] (server - [[cmd:39]]) with corresponding [[report codes#file processing messages|code]] |
| − | + | ||
| − | + | ||
| − | == | + | if ok ping-pong by [[cmd:34]]<==>[[cmd:35]] commands starts |
| − | + | ||
| + | when uploading finished device should send [[cmd:38]] with [[report codes#file processing messages|code 600]] | ||
| + | |||
| + | <noinclude> | ||
{{cmd:34}} | {{cmd:34}} | ||
{{cmd:35}} | {{cmd:35}} | ||
Latest revision as of 11:42, 16 September 2016
PUT file to device
1 cmd type 2 cmd id // set by server 1 files count // max 256
file infos[*]
wl filename length c* filename wl file size if file_size=0 it means that device should delete the file
on error device should send cmd:38 (server - cmd:39) with corresponding code
if ok ping-pong by cmd:34<==>cmd:35 commands starts
when uploading finished device should send cmd:38 with code 600
GET file part from server
1 cmd type 2 cmd id // set by server 1 parts count // always 1 wl filename length c* filename wl part start wl part length
response to GET file part from server
1 cmd type 2 cmd id // set by server 1 parts count // always 1 wl filename length c* filename wl part start wl part length b* bytes
