wo 5.5.1 and TCP commands

[Luca]

I'm using an aux timeline to switch on/off 8 barco projectors using TCP command string.

I created 8 TCP output each one configured with its projector IP and port and then put the 8 cues on a timeline with the power on/off string.

 

Now it happens that when it runs only the first 3 projectors switch on/off.

I thought a it was due to network issue but the strange thing is that if I put the power on output command of the PJs 4,5,6 before PJs 1,2,3 watchout switch on the 4,5,6 PJs and not the 1,2,3,7,8 and so on.

 

So it seems that the output works only for the first 3 connections... do you have any experience on that?

[Claudio]

Did you put all the cues at the very same time in the timeline?

Have you tried to put some delay between each cue, let say 200ms?

 

If you are in Italy you can contact me off forum...

[Jonas Dannert]

I agree with Claudio, you'll need to separate your String Cue:s slightly, then it will work.

 

/jonas

[Luca]

there are 2 seconds between every command

[Jonas Dannert]

That should work then.

 

Each Cue have 8 String commands at the same point in time on the timeline, or?

 

If so, the String commands needs to be separated, slightly in time.

 

/jonas

[Luca]

here is my output window (each ip is a barco projector) and aux timeline called "PJ ON" which should turn on all the projectors:

[Luxav Daniel]

Hi

My cue times are often 0.1s and it will work.

 

But not on every Destination: other Watchout Production PC, VLC, the Vista System Spyder, the Extron DVS 605 and Powerpoint is working well with this times.

 

i have the same "Error" by sending IP Commands to a Picturall Octo Mediaserver to control the Layers (synced to Watchout): Sometimes the Command is working sometimes not.

 

Do you have the Chance to see the "Log" of the Projectors? Christie is written everything into a log that i could see in my Windows Browser (Power up, Cooing Time, Input, Commands on TCPIP Port, RS232, GPIO and so on), perhaps ist possible that the Barcos have a similar "tool"

 

My next step will be: Read the Network traffic with a "Sniffing Tool" and try to compare the Commands with the Commands from the "original Software Tool" which is controlling the Server. On that way i get the Commands for Watchout to control the Vista Spyder ;-)

Perhaps it will work in your Case.

 

Greetings from Germany

Daniel

[Luca]

i'll try to sniff the tcp packets as soon as this event is over. thanks

[Andrew]

If you passible, change protocol type. e.a) TCP/IP -> UDP

 

and use the test with TCP/IP and UDP. e.a) 1,2,3 PROJ -> TCP, 4,5,6 -> UDP