"Kim Jensen" <kim@comcasystems.com> wrote in message
news:47a39fc8$1@newsgroups.borland.com...
> Here is the HEX data.
Your log shows '?' and ':' by themselves before you send the ID command. Is
the controller sending those in response to anything you sent beforehand
that is not in the log? Or is it sending those when you initially connect?
Are you the one sending the CRLF in between them, or is the controller? It
would have been more helpful if you had provided a binary log file instead
of a textual hex dump of the payload. There is no information from the TCP
headers to indicate who sent what. I don't know if SmartSniff can save such
a log file, but other sniffers like Wireshark/Ethereal can.
As for the commands that are in the log, each response line from the
controller does indeed appear to terminate with a CRLF, and then the ':' at
the end of each response does not have a CRLF. So that falls into the "more
tricky" scenerio I described in my last reply. you'll have to trace more
commands/responses to see how consistant that is. Are there any commands
you can send the controller for testing that do not have any response
payload other than the ending ':'?
Gambit
