Daktronics

Show Control System: How do I create buttons that trigger look changes for my 6000 Processor?

Topic

  • Buttons to control the VP-6000 looks using PuTTy/ System Control Scripting
  • Show Control's Display Studio script buttons for layout or look changes
 

Environment

  • Product: VP-6000 Series Processor version 9 or later
  • Component: Display Studio 2.5 or later
  • Control System: Show Control Suite
DisplayStudio-Logo_Blue.png
This article details the original process of triggering looks on a VP-6000. It is considered a legacy workflow. Please see this article for the current process of triggering looks: How do I create display studio scripts to trigger the VP-6000 looks? (VP-6000 version 9 or later and Show Control 2.5 or later) 

Steps

To best manage VP-6000 scripts, it is advised to create a series of admin button scripts that can be used as include scripts for look control. These include scripts will permit the user to later embed the admin scripts in a new scripting button in Display Studio.  This will minimize the duplication of admin commands that need to be created.

The VP-6000 look package is configured in the config.js file.   

To verify which looks you have for an specific site connect to the VP-6000 with putty using How to log into DI-6000 or VP-6000 using PuTTY

Type the following command:  cat /etc/kadoka/config/vpctld/0/js/config.js
Some potential triggers (names may be different/custom for your config):

Single Looks Package

  • Fullscreen
  • LBar_Left
  • LBar_Right
  • UBar_Bottom
  • UBar_Top
  • Pillars
  • Letterbox
  • LBar_TopLeft
  • LBar_TopRight
  • UBar_Left
  • UBar_Right

Dual Looks Package

  • FullscreenA
  • FullscreenB
  • LBar_LeftA
  • LBar_LeftB
  • LBar_RightA
  • LBar_RightB
  • UBar_BottomA
  • UBar_BottomB
  • UBar_TopA
  • UBar_TopB
  • Pillars_A
  • Pillars_B
  • LetterboxA
  • LetterboxB
  • LBar_TopLeftA
  • LBar_TopLeftB
  • LBar_TopRightA
  • LBar_TopRightB
  • UBar_LeftA
  • UBar_LeftB
  • UBar_RightA
  • UBar_RightB
Note: Looks with A will be on top of B if their area_A and area_B rectangles overlap.

The Sources for Single looks package are as follows:

  • PIP_DMP (DisplayPort Input)
  • PIP_Video_A (HD-SDI input 1)
  • PIP_Video_B (HD-SDI input 2)
  • PIP_Video_C (HD-SDI input 3)
  • PIP_Video_D (HD-SDI input 4)

The Sources for Dual looks package are as follows:

  • PIPA_DMP_ (DisplayPort Input)
  • PIPA_Video_A (HD-SDI input 1)
  • PIPA_Video_B (HD-SDI input 2)
  • PIPA_Video_C (HD-SDI input 3)
  • PIPA_Video_D (HD-SDI input 4)
  • PIPB_DMP_ (DisplayPort Input)
  • PIPB_Video_A (HD-SDI input 1)
  • PIPB_Video_B (HD-SDI input 2)
  • PIPB_Video_C (HD-SDI input 3)
  • PIPB_Video_D (HD-SDI input 4)

Button Creation

      Note: Advanced Scripting must be enabled in Display Studio, See Advanced Option Under System Control is Missing from Display Studio

 

  1. Create a Script button in Display Studio.
  2. Right click, select New button.
  3. Add Line
    1. System Control
    2. Advanced
    3. Play
    4. Choose the following:
  • Protocol: UDP/IP
  • Address: (ip address of VP6000 to control)
  • Port: 1337
  • Sign Number: 0
  • Drive Letter: J
  • Library: leave this blank
  • File: name of source in config.js

    5. Continuous

    4.  Repeat to script the backup VP-6000 if available. Name the button "display name-name of trigger in config.js (above)"

      • Example Main- LBar_Left

     Look PIP_DMP.png

     

           

     

     

     

     

     

     

     

     

            5.   Add line in script button to call out a look for the selected source. Use the same address, port sign number and Driver letter in previously configured line.

            6.   Sources should be scripted before looks

            7.  PIP_DMP only needs to be called out for Fullscreen DMP 

    • This will also need to be scripted for the backup VP-6000

     

     step 4 script example.png

     

    See example below of what a primary/backup scripting button should look like when finished.

    Look Scripting Lines2.png    		 

     

    		 

     

     

    KB ID: DD3444478

    DISCLAIMER: Use of this content may void the equipment warranty, please read the disclaimer prior to performing any service of the equipment.

    DAKTRONICS DOES NOT PROMISE THAT THE CONTENT PROVIDED HEREIN IS ERROR-FREE OR THAT ANY DEFECTS WILL BE CORRECTED, OR THAT YOUR USE OF THE CONTENT WILL PROVIDE SPECIFIC RESULTS. THE CONTENT IS DELIVERED ON AN "AS-IS" AND "AS-AVAILABLE" BASIS. ALL INFORMATION PROVIDED IN THIS ARTICLE IS SUBJECT TO CHANGE WITHOUT NOTICE. DAKTRONICS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY WARRANTIES OF ACCURACY, NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. DAKTRONICS DISCLAIMS ANY AND ALL LIABILITY FOR THE ACTS, OMISSIONS AND CONDUCT OF YOU OR ANY THIRD PARTIES IN CONNECTION WITH OR RELATED TO YOUR USE OF THE CONTENT. ADJUSTMENT, REPAIR, OR SERVICE OF THE EQUIPMENT BY ANYONE OTHER THAN DAKTRONICS OR ITS AUTHORIZED REPAIR AGENTS MAY VOID THE EQUIPMENT WARRANTY. YOU ASSUME TOTAL RESPONSIBILITY FOR YOUR USE OF THE CONTENT AND ANY LINKED CONTENT. YOUR SOLE REMEDY AGAINST DAKTRONICS FOR DISSATISFACTION WITH THE CONTENT IS TO STOP USING THE CONTENT. THIS LIMITATION OF RELIEF IS A PART OF THE BARGAIN BETWEEN THE PARTIES.

    The above disclaimer applies to any property damage, equipment failure, liability, infringement, or personal injury claim arising out of or in any way related to your use or application of the content, whether such claim is for breach of contract, tort, negligence or any other cause of action.