Andrew King

Should be amount first, just some doc changes that happened along the way. The speed one is a little more difficult to address. Only a small number of camera support...

First the client requests the HDDInfoList with message ID 0x66 The camera replies with: If no SD Card: ```xml ``` If there is a SD Card ```xml 0 30 1...

Client then requests day records with msg ID: 0x8e and the payload: ```xml 2023 6 1 0 0 0 2023 6 30 23 59 59 0 0 ``` Client replies...

Next the client requests FileInfoList with msg ID 0x0e and the payload: ```xml 0 subStream manual, sched, io, md, people, face, vehicle, dog_cat, visitor 2023 6 9 0 0 0...

The client then requests FileInfoList on message ID 0x0f with the payload: ```xml 0 1 ``` This uses the handle from before The camera replies with: ```xml 0 1 0120230609072812...

The client then sends a FileInfoList on msg ID 0x10 with the payload: ```xml 0 1 ``` The camera just replies with the standard 200 status OK header No idea...

Client then sends ReplaySeek on msgID 0x7b with the payload: ```xml 0 1686278241 2023 6 9 7 28 12 ``` `seq` is the EPOCH time stamp and seek time is...

The client then sends FileInfoList on msg ID 0x0d with payload: ```xml 0 0120230609072812 1 1 subStream ``` This uses the name from the 0x0f FileInfoList Camera replies with ```xml...

Now we get to the actual data. This is done though the FileInfoList command again... with the msg ID 0x05 and the payload: ```xml 0 1 subStream 2023 6 9...

The last message comes from the client as FileInfoList with id 0x07 and the payload ```xml 0 0120230609072812 ``` The camera just replies OK with the standard header This seems...