Sorry if I am not clear my wife constantly reminds me that my communication skills suck . So which part is throwing you off?
Basically I throw one of the ptz commands into a function which has that header building, it goes where I the "cShortURI", at theach end send off the entire cHeader command to the device.
Note that the newer AW-HE series cameras have changed the way they react to HTTP calls within the last year or so. Before, they would still respond and work to malformed URLs (I know because I've got older AW-HE60 cameras working with incomplete/malformed URL calls); now, the URL must fully conform to standards (I've got cameras working with updated, correctly formed URL's as well).
DeviceID, thisCommand, and thisIPAddress are variables fed into the function from elsewhere in the code. Note that, in my "old" code, I've got the pound sign getting sent twice: "...cmd=##T50..." ...because of a bug in my code, and it just works, and they also work without any proper HTTP GET 'connection close' and two consecutive CR,LF character sets in termination code. Newer versions of cameras will not work with the two pound signs in the URL, and also won't work without the fully, correctly formed URL with the two sets of CR,LF being sent at the end. However I'm not sure if the CR *and* LF are really required (I think they are), or whether just the LF is required (code sample above). I would try that one change first.
It took me awhile to realize newer versions of the cameras are a lot more strict about the format of the GET call than my older cameras.
With mine i recall having a doc that said just a LF, so I didnt question it. I loaded it, it worked so I walked away. I guess I could have tried different combinations to see how it would have reacted.
Comments
1 = Left || Up || In
2 = Right || Down || Out
3 = Stop
Make sense?
Sorry but can't understand
Basically I throw one of the ptz commands into a function which has that header building, it goes where I the "cShortURI", at theach end send off the entire cHeader command to the device.
DeviceID, thisCommand, and thisIPAddress are variables fed into the function from elsewhere in the code. Note that, in my "old" code, I've got the pound sign getting sent twice: "...cmd=##T50..." ...because of a bug in my code, and it just works, and they also work without any proper HTTP GET 'connection close' and two consecutive CR,LF character sets in termination code. Newer versions of cameras will not work with the two pound signs in the URL, and also won't work without the fully, correctly formed URL with the two sets of CR,LF being sent at the end. However I'm not sure if the CR *and* LF are really required (I think they are), or whether just the LF is required (code sample above). I would try that one change first.
It took me awhile to realize newer versions of the cameras are a lot more strict about the format of the GET call than my older cameras.