LeonardhoFstader Posted July 24, 2020 Report Share Posted July 24, 2020 I would like to set input variables using TCP. This works as expected when controlling the entire show from the TCP session (load and run). If the show is started using WatchNet, the TCP session doesn't seem to get authenticated correctly. omegle xender Sending "authenticate 1" results in "Ready "6.4" "WATCHPOINT" "Windows" true" but any command after that returns "Not authorized for:<command>" Is there any other authentication level that should be used for setting Inputs when the show is controlled by WatchNet? 0 Quote Link to comment Share on other sites More sharing options...
Dataton Partner Jim Testa Posted July 24, 2020 Dataton Partner Report Share Posted July 24, 2020 You do not need to explicitly send the 'authenticate 1' from WATCHNET. However, you do have to load the show before you begin issuing any other show-related commands. 0 Quote Link to comment Share on other sites More sharing options...
Moderator jfk Posted July 25, 2020 Moderator Report Share Posted July 25, 2020 WATCHNET works much the same way as WATCHOUT Production - when it is communicating with the WATCHOUT Displays, all other IP control methods are locked out. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.