Output strings on same TCP connection of controlling application??

[ConnerLawson]

Hi.
I'm writing a C# application that will interact with WatchOut.

I will send commands and receive notifications. To do that should I open two connections, one as a client to issue commands to WatchOut and another as a server to receive notifications from WatchOut Outputs?  essay writer Is there a way to get Outputs in the same connection I use to send commands - and to receive errors?

Thank you for reading.

[RBeddig]

If you control a display cluster, the cluster usually sends back information on the same ip port. Try the getStatus command or the ping command to see what comes back.

You can also use IDs with each command and then the ackn will also include the ID to distinguish the answers.

If you want to send commands from a string output of WATCHOUT, this would need a separate port and a TCP/IP server on the control side.

There also used to be an undocumented feature, which would send strings to the control port instead. The trick was to use control cues and type something like    :message   into the name field. The colon is important here! I haven't tried it for quite some time but I guess it should stilll work.

Hope this helps.

[Fredrik Svahnberg]

Yes, this undocumented feature was called "The Norwegian Feature" from the project where it was originally used. I can confirm it works, at least up to WO v6.2 (see log below), as I was using it in a Musuem installation with Medialon a while back. Medialon was eventually replaced by PIXILAB Blocks

MacBook-Pro: telnet 169.254.12.130 3039
Trying 169.254.12.130...
Connected to 169.254.12.130.
Escape character is '^]'.
authenticate 1
Ready "6.2" "WATCHPOINT" "Windows" true
load "Norwegian test62"
Busy "Cluster Established" "" 0
Ready "6.2" "WATCHPOINT" "Windows" true
run
Information ":Test1"
Information ":Test2"
Information ":Loop"
Information ":Test1"
Information ":Test2"
halt

 

[jfk]

1 hour ago, Fredrik Svahnberg said:

Yes, this undocumented feature was called "The Norwegian Feature" from the project where it was originally used. I can confirm it works, at least up to WO v6.2 (see log below), as I was using it in a Musuem installation with Medialon a while back. Medialon was eventually replaced by PIXILAB Blocks

MacBook-Pro: telnet 169.254.12.130 3039
Trying 169.254.12.130...
Connected to 169.254.12.130.
Escape character is '^]'.
authenticate 1
Ready "6.2" "WATCHPOINT" "Windows" true
load "Norwegian test62"
Busy "Cluster Established" "" 0
Ready "6.2" "WATCHPOINT" "Windows" true
run
Information ":Test1"
Information ":Test2"
Information ":Loop"
Information ":Test1"
Information ":Test2"
halt

 

FYI The Norwegian feature goes back to version 2 and is retained as a form of backward compatibility. As such, it only works on the main timeline, as auxiliary timelines did not appear until a later major version. I recently tested it with v6.5 and it still works as indicated above.