Facility Control

Hi all,

Has anyone had any success controlling Crossfire from a DashBoard panel using VDCP?

My connection is good and I can send commands over Ethernet however they don't work as intended. If I hit play, pause, cue, etc it either pauses or ejects the clip in the channel, none of them (even pause) work as expected.

My commands are the normal ones such as vdcp.pause('IP Address', port, channel);
vdcp.cueClip('IP Address', port, channel, 'clip name');

Are there any other variables in all this that may be vendor specific?


Thanks,

Taylor

Sorry for the delayed response.
Yes, we have controlled Crossfire from DashBoard panels.

A few notes:
You must use vdcp.continuePlay([host], [port], [channel]) instead of vdcp.play
Cue Clip also has a version with an eject command:
vdcp.cueClip([host], [port], [channel], [clip id], [eject = true/false]);

If it doesn't work, I would suggest double-checking the VDCP settings on the Crossfire - they should be the same settings you would use when talking to an Acuity or Vision switcher.
#DashBoard

What about Daktronics Venus VDCP through Dashboard?

#DashBoard

Sorry, we have not done any testing with the Daktronics Venus.
It may work but I couldn't say for sure. If you try it and have success, we'd love to know about it.
#DashBoard

I'm going to drag up this thread instead of starting a new one, since I'm trying to do the exact same thing.

I'm trying to cue a clip in my Crossfire, I can play, pause, stop, etc as expected. But as I try to cue any clip, the logs in my Crossfire are saying :
[ unit 1, port 1 ] - 12:04:39.709 - Tx: 05 00
REQUEST = PLAYCUE_VARIABLE
[ unit 1, port 1 ] - 12:04:39.709 - *** Could not find clip with ID "TEST_Wipe"

Now this clip ID is exactly what I see in the Choose ID field on my Vision switcher, which is able to cue the clip fine. Is there some other ID I should be looking for?


Also, I will be looking to do some VDCP control of our Dak Venus servers as well, I can report back how that goes. I do know that you can only do it with 7000 servers, the feature has been removed for the 8000s for some reason.
#DashBoard

I figured it out, so now I'm going to answer my own question, in case anyone else needs this info.

I sent the cue command from my vision switcher, then found the hex bits in the Crossfire log and converted to ASCII. I found the Clip ID I need is actually "TEST_Wipe (11 Spaces) 02865‡"
Since the dynamic clip id length is set to 25, this string has to be 25 characters long, hence all the spaces. The number at the end appears to be arbitrarily assigned, but I can pull that off of the Assign Clips screen on my Vision.
#DashBoard

It's also worth noting that the Crossfire expects you to use CONTINUE PLAY instead of VARIABLE PLAY (or what DashBoard calls "play").
#DashBoard

After doing a lot of testing and asking questions, it seems the the VDCP Protocol that Dashboard uses is slightly different the a Vision Switcher. Since I have an all 8000 system, you have to go into V7000 and create sequences to send out a command to play a file on that RTD Sign. I configured all of that, I could load the clip list, however it would only trigger what I had as the default file set as in V7Display.

I am not trying to create a custom RTD (similar to a fire alarm trigger) within the Venus 7000 and can associate a command to play a sequence. The only thing I am not sure how to do is create the ASCII string in dashboard to fire that sequence over udp. I am going to number everything 1-25 just to keep things simple. If anyone can help with a script for that, it would be greatly appreciated.
#DashBoard