output Watchout 6.7 version error when use string output to control device

[SawLae]

 

I'm having trouble with my WATCHOUT software. Sometimes, when I try to use string output to control the Projector Shutter, it gives me errors. It works fine sometimes, but other times, it doesn't work at all.

 

[Eddy Yanto]

Hi SawLae,

• Make sure there's only NIC in either WATCHOUT Production or Display machine so that the command is routed to the correct network
• Make sure the firewall is always off on both systems
• When you switch from running the show using WATCHOUT Production/Master to WATCHOUT Display controlled by third party control system, please issue a LOAD command to the Display machine first
• Try to put some delay (eg: 50 ms) between commands (as shown in the attached video)
• Try to add Line Feed or $0A in the command eg:
  •     $25$31$41$56$4D$54$20$33$30$0A$0D
  •     $25$31$41$56$4D$54$20$33$31$0A$0D  

     

[Mike Fahl]

If I recall correctly, that error means that WATCHOUT was unable to connect to the TCP port on the targetIP address.

Verify connecting to that IP and port by other means (e.g., using a telnet client) to determine if connection fails there too. If so, check the devices that are supposed to receive the data to make sure that accept the connection OK as well as the network path to get there.

I doubt that "multiple NICs" can cause this error. That typically only affect broadcast and possibly multicast messages, which this one isn't.

Mike

 

[Eddy Yanto]

Yes, agree with Mike that the error means WATCHOUT failed to connect and to deliver the AV mute/unmute commands to the TCP device for some reasons. It could be many things hence the suggestions. Some of the common issues that I've seen in the past were due to having multiple active networks (wired and wireless network being active at the same time and were connected to different networks), firewall being disabled temporarily but enabled upon computer reboot thus blocking the message and in some cases the commands were simply too fast for the target device hence the need for delay between commands.

For SawLae's case, Epson Thailand has also reached out to us yesterday. We talked and confirmed that the TCP port 4352 on all projectors were in fact had always been open. They tested it using third party TCP sender software to confirm this. In fact, we also tested with Epson projectors in our showroom, and it worked without issue (see attached test video).

The only difference between our test is the ASCII command that I used (which I don't think make matter):

• %1AVMT 30$0D
• %1AVMT 31$0D

 

 

[SawLae]

I switched from the Shutter command to the AV Mute command, but it still displays the same error message. The system functions properly when we only use string cues in the timeline. However, when we include a string cue in the timelines that contains video files, Dxm control, and other elements, it displays an error message.

[RBeddig]

21 hours ago, SawLae said:

when we include a string that contains video files

What is a "string that contains video files"?

If I understand your problem correctly, sometimes one projector reacts to the command and sometimes the same does not? And all this happens when the projector is fully powered up and working?

You're trying to use PJlink and have turned the password protection off?

You're sure that you don't have any IP address or network range conflicts?

Are you using the wired network port on the projector and have the wifi turned off (if possible)?

Have you tried to send the command from some other software to see whether the projector answers something?

Apart from PuTTY, my tool of choice is usually PacketSender as it can store commands and you can also see the feedback.

Another valuable tool is wireshark. It's a bit advanced but you can install it on the computer sending the strings and run it while you send the data. If you are using the production computer to run the show, install it there. It will probably collect a huge list but you can filter the results to see only the communication send out from your computer or received from the IP of your projector.

I don't know which Epson model you are using, but the manual for the EB-PU2213/2216/2113/2116 models states that the projector info can show some event ID codes which can give you hints on network problems inside the projector. Page 116 of the current user guide.

And on page 135 of the Epson manual, I noticed a remark about mute settings.

Some of the large Epson projectors also allow to be controlled over Art-Net. Have you tried this?

[SawLae]

I apologize for my mistake in the previous message. Here is the corrected version: 

"When we include a string cue in the timeline containing video files, Dxm control, and other elements."

For the password projection, I have already turned it off. Regarding the signal range conflicts, I don't think they are related, as the range I'm using is within the specification of the LAN cable. Lastly, the model of the projector we are using is Epson PU1008B.

[QuinLoft]

This has been a problem for a decade now. It's a PJ Link issue, and it's related to the ports opening and closing I think, but I've never been able to figure out all the exact quirks because the rules don't always apply. However, the general thing I've found is it's open for 30 seconds then will close. Sometimes it'll reopen just fine, sometimes it'll fail, but it's always repeat the pattern if you run it in order.

The solution I've found is to just build an alternate timeline, send a empty %0D Carriage Return every 25 seconds or so to keep the port open, then loop that for eternity. As long as you don't rapid fire the commands, you should be good.

[Diego Marchente]

Hi,

In some cases I had to double the command (enter the same command twice) so that the first one opened the TCP connection port and the second one activated the command... it seems stupid but it works.

Best regards

Diego