Ok - some more debug info...output in Hercules format which helps transcribe...
When I connect to my Onkyo, it always responds thus:
ISCP#NUL#NUL#NUL#DLE#NUL#NUL#NUL#VT#SOH#NUL#NUL#NUL!1NLSC-P#SUB#CR#LF
I can then send a command...
In HEX, with TCP/IP command protocol, I send this:
0x4953435000000010000000090100000021314d564c5153544e0D0A
This translates as :
ISCP#NUL#NUL#NUL#DLE#NUL#NUL#NUL#HT#SOH#NUL#NUL#NUL!1MVLQSTN#CR#LF
This works, however I now want to read the response...
So using a TCP connection tool, I run the above and get this response back:
ISCP#NUL#NUL#NUL#DLE#NUL#NUL#NUL#LF#SOH#NUL#NUL#NUL!1MVL1A#SUB#CR#LF
It's the 1A I'm interested in, Hex for 20.
However, what I'm getting back in the TCP/IP log (after I enabled it) is this:
As you can see, OpenRemote is parsing the CR/LF (and some other stuff, apparently) - but it's not getting the last line...
If I use Hercules in text mode, watching as OR connects in, I see this conversation:
ISCP!1NLSC-P
ISCP
!1MVL1E
The above shows the ISCP!1NLSC-P as OR connects - we don't see the command issued, as we're a "watcher" in this case, but we do see the response...which is the MVL1E line.
Clues? Can I extend the TCP buffer easily?
Annoying it WAS briefly working, but seems to have knocked itself out on a restart...
Cheers!