Facility Control

Hi All,

I am trying to declare a parameter inside a TCP string and think I must be doing something wrong.

<task tasktype="ogscript">rosstalk.sendMessage("params.getValue('IP1', 0)", 9993, "record: name: “params.getValue('CLIPNAME1', 0)[0]”", null);</task>
         </button>
         <button buttontype="push" colspan="1" fill="both" id="STOP1" name="STOP" rowspan="1" weightx="1.0" weighty="1.0">
            <task tasktype="ogscript">rosstalk.sendMessage("param_DESTIP1 (IP1)[0]", 9993, "stop", null);</task>
         </button>

When I use visual logic it creates it as

   <task tasktype="ogscript">rosstalk.sendMessage("param_DESTIP1 (IP1)[0]", 9993, "stop", null);</task>

However I thought it should be more like

<task tasktype="ogscript">rosstalk.sendMessage("params.getValue('IP1', 0)", 9993, "record: name: “params.getValue('CLIPNAME1', 0)[0]”", null);</task>

Thanks,
Kai

I think you need to escape your quotes and then concatenate your variables.

Maybe something like this?

<task tasktype="ogscript">
rosstalk.sendMessage(params.getValue('IP1', 0), 9993, "record: name: \"" + params.getValue('ClipName1', 0)[0] + "\"", null);
</task>

Note how the IP parameter is not in quotes, and then the quotes for the clip name are escaped, which would produce a string like this:

record: name: "myClip.mov"

Does that help?

Hi there @KaiB, I am currently working on a remote sollution for the BMD HyperDeck (both pro and mini) as well.
So far I have no issues getting the hyperdeck to respond to the TCP commands, however I'm having small luck in getting a response from it.

Maybe you got a few tips @jamespeltzer?

Currently I have the following:

function callback(string1, string2, string3, string4, string5) {
   ogscript.debug("String 1: "+string1);
   ogscript.debug("String 2: "+string2);
   ogscript.debug("String 3: "+string3);
   ogscript.debug("String 4: "+string4);
   ogscript.debug("String 5: "+string5);
}

rosstalk.sendMessage("10.2.51.194", 9993, params.getValue('text', 0), callback);

This gets me back the following:

13:05:10:603: String 1: true

13:05:10:619: String 2: help

13:05:10:620: String 3: null

13:05:10:620: String 4: null

13:05:10:621: String 5: undefined

I pretty much guess the string 1 is just an indicator to wether or not the command was accepted, and string 2 is basically just what command string I sent through (just "help" in this case).
However, string 2 and 3 returns as "null", and string 5 is undefined (guess it has no 5th return value).
However, reading the document from BMD about their API and the reponse it says:

[QUOTE]Simple responses from the server consist of a three digit response code and descriptive text terminated by a new line:
{Reponse Code} {Reponse text}

If a response carries parameters, the response text is terminated with a colon, and a parameter name and value apirs follow on subsequent lines until a blank line is returned.

{Reponse Code} {Response Text}
{Parameter}: {Value}
{Parameter}: {Value}
{Parameter}: {Value}
...


Never tried handling responses from a TCP connection before, so new to this one.
Any tips? Or anyone have any experience with BMD HyperDeck and TCP responses?

HypderDeck manual with Developer Information and syntax here:
http://documents.blackmagicdesign.com/HyperDeck/20170711-bdb5d3/HyperDeck_Manual.pdf

You're using rosstalk.sendMessage.
What you'll want to use if you care about waiting around for the server to respond is:
rosstalk.sendMessageWithResponse

function callback(success, sentData, resultString, exception)
{
    
}
rosstalk.sendMessageWithResponse('[host]', [port], '[message]', '[end of message indicator]', callback);

You're using rosstalk.sendMessage.
What you'll want to use if you care about waiting around for the server to respond is:
rosstalk.sendMessageWithResponse

function callback(success, sentData, resultString, exception)
{

}
rosstalk.sendMessageWithResponse('[host]', [port], '[message]', '[end of message indicator]', callback);

If you have to deal with asynchronous messages at any time, then @josephadams is on the right track. A listener will probably be necessary.

Here's an example that creates a listener and exposes it so you can send messages through it elsewhere in your code:

<abs contexttype="opengear" style="">
   <meta>
      <listener autostart="true" connecthost="localhost" connectport="8765" delimitertype="newline" id="client">
         <task tasktype="ogscript">if (event.isConnectEvent())
{
   ogscript.putObject("listener-connection", this);
}
else if (event.isMessageEvent())
{
   ogscript.debug("CLIENT GOT BACK: " + event.getBytesAsString());
}
else if (event.isDisconnectEvent())
{
   var lObj = ogscript.getObject("listener-connection");
   if (lObj == this)
   {
      ogscript.putObject("listener-connection", null);      
   }
}
</task>
      </listener>
      <listener autostart="true" delimitertype="newline" id="server" listenport="8765">
         <task tasktype="ogscript">/* A silly server that just reverses any string it was given and sends it back */
if (event.isMessageEvent())
{
   var myMessage = event.getBytesAsString().trim() + "";
   var response = "";
   for (var i = myMessage.length - 1; i &gt;= 0; i--)
   {
      response += myMessage.charAt(i);
   }
   this.writeString(response + "\n", false);
}

</task>
      </listener>
   </meta>
   <button buttontype="push" height="199" left="37" name="Send &quot;Hello&quot; Through Listener" top="38" width="317">
      <task tasktype="ogscript">var listener = ogscript.getObject("listener-connection");
if (listener != null)
{
   listener.writeString("HELLO\n", false);
}</task>
   </button>
</abs>

So... I'm taking a look at this one again...
And there is just one thing here I cant wrap my head around...

Setting up a listener as below:

<listener autostart="false" buttontype="toggle" colspan="1" connecthost="158.36.157.225" connectport="9993" delimitertype="newline" fill="both" height="100" id="commandSender" left="0" name="Comms" pheight="168" pwidth="150" style="style:ToggleButtons;" top="0" width="150">
   <task tasktype="ogscript">if (event.isConnectEvent()) {
   var cmd = 'stop';
   if (cmd != '') {
      ogscript.debug('Command: ' + cmd);
      this.writeString(commandToSend + '\n', false);
   } else {
      ogscript.debug ('No command');
   }
} else if (event.isMessageEvent()) {
   var message = event.getBytesAsString().trim();
   ogscript.debug(message);
} else if (event.isDisconnectEvent()) {
   ogscript.debug('connection closed');
} else {
   ogscript.debug('no event info');
}</task>
</listener>

Ok, so this will set up a client connection between DashBoard and the BMD HyperDeck Mini (for that specified IP anyhow).
And it works. I get the first command, wich is "stop" in this case to send, and I get all the replies I could want. But only when I start the listener. As in toogle the button ON.
However, this also takes that connection, and wont let go! Meaning I cannot send any further commands to the device until I disconnect from it as a client...

So, my question... How do I send more commands through the client connection?
Cause if I've not connected to it through a client, just sending a TCP with a callback function will give me the info for that command.
But if I request a bigger response, like say the device info, this is not included in the regular callback info, but is sent as extra information if I have a listener/client connection open.

• record: name: test
• record: name: 'test'
• record: name: "test"
• record: name: \'test\'
• record: name: "test"
• record: name: {test}