TCP feedback

[Sindre Hovland]

Hi!

Love your products!
I'm currently installing a new Blustream AVoIP system in our church, and I'm trying to implement it with our Kiosc Touch.
Per now I'm able to send TCP tags to the blustream ACM210, which causes the receivers to change sources, like "OUT001FR002\r\n",
What I would like is to create a matrix page for controlling the transmitters/receivers and turing them on and off.
What I can not understand is how to make the Kiosc (on my iPad) and the Kiosc Touch give me visual feedback on the state of the componenets, e.g. on/off/channel1/channel2 etc.
I've tried searching all manuals and youtube videos I can find with no luck.

Can someone point me in the right direction in how this is accomplished?
What I'm not shure about is how the tags should be typed to respond to the feedback from the ACM210, should I use buttons/indicators/checkboxes for this, and if the ACM210 is actually giving a feedback, or if this needs to be done in some other way. We have a KioscTouch1 and a CueCore2. If needed, i guess we could use the CueCore to operate between our acm210 and Kiosc applications, but that seems a bit unnecessary.
The ACM210 API commans can be downloaded here, if that is helpful.
https://www.blustream.co.uk/Attachment/DownloadFile?downloadId=421

Thanks,
Sindre

[Jorge Solano]

Hello Sindre,

Thank you, and glad to hear you're enjoying the products

What you want to do should be possible in principle. Kiosc can use incoming TCP data as feedback for elements such as buttons, indicators and labels. The main question here is what the ACM210 actually sends back.

The API shows commands such as `OUT 001 STATUS` and `STATUS`, but it is not clear what the exact returned message looks like, or whether the ACM210 sends updates automatically when a route changes.

Could you test this with a TCP/Telnet tool such as Packet Sender or PuTTY and send:

`OUT 001 STATUS`

and:

`STATUS`

Please send me the exact response you receive. Also, if possible, leave the connection open and change a route from the ACM210 web interface to see if it sends any feedback automatically.

For testing in Kiosc, I would start with one simple output and use a button for the command and a separate Indicator for the confirmed feedback. This way the GUI shows the actual ACM210 state rather than only what was pressed locally.

If the ACM210 returns a simple predictable message, it may be possible to keep this directly between Kiosc and the ACM210. If it returns a larger status report that needs parsing, then some additional logic may be required. I would not involve the CueCore2 yet until we know the exact ACM210 response.

Could you also let me know the Kiosc version running on the iPad and the software/firmware version of the KioscTouch1? Then we can check the feedback behaviour on both platforms.

Hope this helps!