I took a quick look at that document. The framing is TCP with CRNL "line" endings, but there's no guarantee that the
binary data (like the length fields) won't accidentally look like a CRNL when reading a response, which may be a problem.
The short form instructions to get started:
Set up a
TCP Out device to port 60128 of the receiver. Use CRNL line endings and check the auto-connect box. It should show as
connected immediately; if it doesn't, you're having networking (or receiver
) problems.
Next set up an
unrecognized event and tell it to write the whole input into an Indigo variable.
Create an action that sends the QSTN command (query mute state). Run the action, and you should see
one event for the response (I think). Examine the variable and see if it's the
whole response (framing and all - it'll be wrapped with binary length fields and all that gunk).
To watch packets on the network (so you can learn what the heck is going on there
):
1. Open Terminal
2. Run
- Code: Select all
sudo tcpdump -i enx -X port 60128
where the
enx is the name of your interface - usually either en0 (Ethernet) or en1 (Wifi), though this can vary for some kinds of Macs. Leave it running.
3. Exercise your script. You'll see all the messages to and from port 60128 in the Terminal output.
4. Grab that output and try to make sense of it.
Good luck!
-- perry
