fdoeve Posted April 24, 2018 Report Share Posted April 24, 2018 Hey guys! i thought i would try and use watchnet to control my production software, but as soon as i enable the UDP control in Watchout Production i get an error message over and over saying [Error 7 0 "Unrecognized Command: Discover"] and there is no info or control in Watchnet.. i know that, because i am using watchout 5.5.2 with watchnet 1.4, production computers won't show up in the network inside Watchnet, but controlling them should still be possible, right? Anyone have any idea as to what i'm doing wrong? there's no firewall in the production Computer, so nothing's blocked there... Thanks! Frank 0 Quote Link to comment Share on other sites More sharing options...
fdoeve Posted April 24, 2018 Author Report Share Posted April 24, 2018 i tried 2 different computers with the production software, both have the same issue.. as soon as i turn on the UDP it starts giving me errors every 40 seconds one windows 8 machine and one windows 7 machine 0 Quote Link to comment Share on other sites More sharing options...
Dataton Partner RBeddig Posted April 24, 2018 Dataton Partner Report Share Posted April 24, 2018 I've not tried to control the production software of WATCHOUT 5. The discovery function for the production software works with WATCHOUT 6.2 and later. You might still try to enter the IP address manually in WATCHNET. The error you report just says that WATCHNET sends data into the network and the production software tries to listen but does not understand the new commands. 0 Quote Link to comment Share on other sites More sharing options...
fdoeve Posted April 24, 2018 Author Report Share Posted April 24, 2018 It look like the production software doesn't under stand it's own listen command. Manually entering the IP address works, but watchnet isn't able to connect to the production pc. Another issue is that after trying a while, the watchnet server locks up and is unreachable. 0 Quote Link to comment Share on other sites More sharing options...
joakim Posted April 25, 2018 Report Share Posted April 25, 2018 Hi, The [Error 7 0 "Unrecognized Command: Discover"] is reported by the production computer because WATCHNET broadcasts a discover message on the UDP port that the production computer listens on. The reason that the error is logged is as Rainer pointed out the WATCHOUT 6.2 or later is required for the network discovery to work, earlier versions will log this error instead. The error in itself will not cause any problems for WATCHNET or for the production computer, the only effect is that the production computer will not be discoverable by WATCHNET. When it comes to controlling a production computer that cannot be discovered on the network, the IP address of the production computer must be manually entered as you did but you must also enable TCP connections for the current show. This is done in preferences right next to where UDP control is enabled and is required because WATCHNET uses UDP for discovery mechanisms but TCP for the actual show control. Since you're using an older version of WATCHOUT production I would suggest enabling TCP control and disabling UDP control for the current show. This will allow you to control the production interface and should stop the unrecognised command errors from appearing as the production computer will not be listening on that port any more. Best, Joakim 0 Quote Link to comment Share on other sites More sharing options...
fdoeve Posted April 25, 2018 Author Report Share Posted April 25, 2018 (edited) That sounds like it should work... adding the production computer by ip address works and the Watchnet sees it as online, but there's still no control. Also, the Production software now gives me the error [Unrecognized command: getStatus]..... EDIT: My Watchnet Server is also giving me all sorts of error messages (tried to upload image, didnt work), but i get a lot of IllegalState Cluster not ready messages... Edited April 25, 2018 by fdoeve Additional info 0 Quote Link to comment Share on other sites More sharing options...
joakim Posted April 26, 2018 Report Share Posted April 26, 2018 Hi, I think the culprit here is line 5 of the WATCHNET log: "Cluster error". Could you please send an email to support tagged with WATCHNET and attach the log files from WATCHOUT production and WATCHNET and we will dig deeper into this issue. Best, Joakim 0 Quote Link to comment Share on other sites More sharing options...
fdoeve Posted April 26, 2018 Author Report Share Posted April 26, 2018 7 minutes ago, joakim said: Hi, I think the culprit here is line 5 of the WATCHNET log: "Cluster error". Could you please send an email to support tagged with WATCHNET and attach the log files from WATCHOUT production and WATCHNET and we will dig deeper into this issue. Best, Joakim I'll get on it! thanks! 0 Quote Link to comment Share on other sites More sharing options...
fdoeve Posted May 1, 2018 Author Report Share Posted May 1, 2018 On 4/26/2018 at 12:58 PM, fdoeve said: I'll get on it! thanks! Email was sent! 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.