Brick-HD Videowall Control Software

 


Setup

Program Options

Video Input Settings

DVI Input EDID Table

Video Output Settings

Monitor Alignment

Sequence Buttons

Serial Communications Protocol

Sequence File Format

Sequence File Commands

Message Functions

Editor

Remote Directory

Sequence Keypad

Binary Sequence Decoder

Reset

Version Information

Firmware Update

Quick Start Guide

Specification

Further Information

 

Command Shell

Web Server


 Brick-HD Control Software

 

A guide to getting started with the Brick-HD processor itself is available here. The capabilities of the processor are described in the specification summary.

 

The Brick-HD can also be controlled using a terminal emulation program via the Command Shell.

 

The Video Wall Control application will present the main window below initially.

 

Context sensitive help is provided by indexing automatically into this file. If the F1 key is pressed a help page will pop up relevant to the current dialog box. Alternatively, if the help option from the main menu (show below) is selected, this file will be presented. This is the same as pressing the F1 key from the main window.

 

To set-up the software to control are remote Brick-HD processor, click on File then Setup from this point. To further configure the Brick-HD base configuration click on File then Configure once communication has been established.

 

Once the connection to the processor (or processors) is established it is possible to configure the processor, in particular,

Once set-up, it's possible to start configuring sequences. These are files of timed statements which cause messages to be sent to the processor to change the configuration, such as magnification factors and colour washes. A number of example sequence files are provided to demonstrate how to create these in addition to this documentation.

 

Sequence files can executed from the main window by filename. They can also be executed by clicking on a button defined in the sequence buttons page.

 

Other features are available to assist in the management of the processor. The processor can be reset, which is useful to return to a known start point if you've set the processor in state you didn't realise when developing sequences. It's also necessary to do this after downloading an updated version of firmware, or to apply changes to the IP configuration.

 


 Setup

 

In order to control the Brick-HD processor using this software some parameters need to be configured, via the setup dialog (shown below).

 

 

 

The processor (or processors) need to be connected to the controlling PC using either a serial cable or via an IP connection using the Brick-HD's Ethernet port. 

 

Serial Connection

 

Many PCs no longer have built in serial port, in which case a USB serial adapter can be used. In this case the USB adapter should be plugged into the PC prior to running the Brick-HD Control software - otherwise the port will not appear in the pull-down list of COM ports.

 

Select the COM port to use from the pull down menu in the serial link box. Once the COM port is set, configure the number of installed units. If there is more than one unit connected, each will need a different unit ID. If the units were purchased at the same time as a package, they will have been supplied configured with unique IDs. Single units will always have a Unit ID of 0 preset.

 

The settings can be saved and applied automatically next time the software is run using the Save settings button. This will update the file "BrickHD.ini" located in ....\My Documents\BrickHDProjects.

 

 

Unit ID

 

If you only have one BrickHD it's ID should be set to 0 and it will have been supplied set-up this way, so you can probably ignore the rest of this section.

 

The easiest way to set the devices's ID is to use the Vacuum Florescent Display (VFD) menu on each device.

 

It is also possible to change a device's unit ID via the  Brick-HD Control software. This can be done connecting one unit at a time to the PC using the serial cable and selecting the required unit ID from the Primary Unit ID set  and then clicking on the "Set Unit ID" button.

 

When all of the units have had their ID set, connect them in the usual "daisy chain". Unit 0 should be the one connected to the PC via the Host port. Unit 1 Host Port should be connected to Unit 0 Loop port and so on. 

 

Alternatively, the units can be connected together as above (daisy chained) and their IDs can be set in one go. The device to become unit ID 0 has it's host port connected to the PC. The Primary Unit ID should be set to 0, and the Set Unit ID button clicked. This will set each successive device in the chain the the ID of the previous device +1.

 

Click on Auto for the software to scan each unit and set the installed flag to confirm the correct configuration of the chain.

 

In addition, to check communication with all the processors, read back the version information using the File/Hardware Info menu option.

 

The Unit ID can also be set using the Remote Configuration dialog from the "File/Config" menu option. Changing the unit ID here only changes the save configuration. To apply the configuration the  Brick-HD unit will have to be reset. This also only works if communication is possible with the unit in the first place - which requires the current unit ID to be known.

 

 

Ethernet Port

 

The Ethernet port is permanently enabled. It will auto configure for 10/100BaseT and auto-sense the Tx/Rx connections, so that it is not necessary to use a cross-over cable to connect the Ethernet port directly to an Ethernet port on a PC. The state of the Ethernet connection can be viewed from the front panel VFD display or from the display virtually by selecting "Display" from the top level menu.

 

If the display is blank, press the front panel button or click Enter in the Display panel dialog. Rotate the Select front panel knob or click the Down button in the Display panel dialog to select the Ethernet status display, shown below. This will display the MAC address and the Ethernet status. In the examples below, the first shows the Ethernet cable unplugged, the second with the Ethernet cable connected to a 100BaseT Hub. The display will be updated in real time.

 

 

 

IP Configuration

 

To use TCP/IP, the Brick-HD processor IP parameters associated with the Ethernet port must be configured. If a serial port is available temporarily, the process above can be used to establish communication between the PC and processor using the serial port first and then the IP parameters set via the serial channel.

 

If multiple Brick-HDs are used, unit ID 0 should be connected to the other units by daisy chaining the host and loop ports. This allows unit 0 to act as a master and send messages to the other units.  

 

If a serial connection exists  the IP parameters can be set using the "File/Config" menu option dialog shown below. If not, then the IP parameters must be configured using the VFD display from the front panel.

 

 

 

The MAC address must be unique. The lower bytes of this will usually be set to the device serial number to ensure this is the case, however if the configuration is ever completely wiped a default will be assigned. This default will need to be changed if more than one Brick-HD is present on the same LAN. To create a valid unique MAC address derived from the device serial number, click on the "set MAC from serial number" button and enter the decimal serial number.  The saved configuration will be updated with the MAC address when the "Apply" button is pressed, however to use the address in practice will require a reset.

 

The Host Address, Netmask, Default Gateway and DNS Server can be configured automatically using DHCP if the Enable DCHP box is checked. In this case the values configured will only be used if DCHP fails. However it is recommended that DHCP is not used and a static IP address is assgned, unless the DCHP server is configured to permanently assign a specific address to the device. This is because in many ways the Brick-HD acts as a server and it's IP address needs to be known by controlling applications

 

The SNTP and DNS server  addresses are not essential and can be configured later if required. SNTP is used to set the Real Time clock at start-up.  The RTC time will be offset by the Time Zone Offset. The can be +/- 12Hrs with a half hour resolution. The value can be determined from the PC's time zone by clicking the PC Zone button.

 

The DNS server is only used with certain commands from the Brick-HD shell, accessed via a terminal emulator.

 

In order to connect the Brick-HD Control software via TCP/IP the Brick-HD needs to run the MTCP (Media Technologies Control Protocol). This is a simple protocol which encapsulates the messages used with the serial port in TCP/IP. To transfer files between the controlling PC and the Brick-HD the TFTP service is necessary.  The two boxes labelled TFTP and MTCP respectively should be checked to enable this.

 

Telnet, which  allows a console session to be established via TCP/IP is optional. This is not used by the Brick-HD Control software supplied, but can be used with other 3rd party applications.

 

HTTP support is limited in the current firmware. If this box is checked, the Brick-HD will run a web server listening on port 80.

 

The FPGA file and System code file fields will be filed in with the currently configured files, unless the configuration has been wiped. These should match the files held in the Bootflash: volume. See the section on firmware upgrades for further details.

 

The unit ID will correspond to the unit ID originally configured when communication via the serial protocol was established - or configured using the VFD menu. When only a single device is used this should be set to zero.

 

The TCP/IP connection to the Brick-HD can be unauthenticated or authenticated using a shared secret. In both cases the configuration must match at ether end of the connection. When the configuration is applied, you will be prompted to copy the parameters sent to the remote Brick-HD into the Brick-HD Control software's IP configuration to ensure both sides of the connection match. If the IP address has been set by DHCP, the DHCP IP address will be used not the statically configured fallback IP address.

 

Once the form is configured, click Apply or OK to update the configuration. In the case of Apply the configuration will be read back and re-displayed. In order to make the Brick-HD use all of the configured parameters it is necessary to reset the device.

 

Once the Brick-HD has re-started, go the the Setup Menu and click the Remote (TCP/IP) button. This will attempt to make an MTCP connection to the device. If this is successful the connection type shown in the bottom left corner of the window in the status bar will be shown as TCP/IP instead of the COM port originally selected.

 

If the settings are saved at this point, next time the Brick-HD Control software is invoked it will automatically connect using TCP/IP. Settings are saved per user - so a different user on the same PC can have different settings saved.

 

 

The lower part of this dialog box are concerned with firmware boot parameters described in the firmware update section.

 


Front Panel VFD Menu

 

Th Brick HD includes a simple mechanism for configuring and monitoring the processor using a 2x20 line VFD and shaft encoder mounted on the front panel. A virtual representation of this display is provided by the Brick-HD Control Software by selecting the main menu Display option. This will present a dialog box as show below.

 

 

 

 

The VFD provides a number of status summary pages, a control menu for downloaded sequences and a configuration menu. To scroll through these pages from the default page rotate the shaft encoder knopb clockwise or click on the down button using the dialog box from the Brick-HD Control software. 

 

The display will go blank after a configurable period if not used to prevent burning in certain characters from the default display. If the display is blank, press the control knob to wake it up (or enter in the case of the virtual display above). If the knob is pressed when the default display is selected it will blank the display.

 

The top level pages available are,

  • Real time clock and status display

  • Video input status

  • IP configuration display

  • Ethernet status

  • Environmental status

  • Software version

  • Sequence control

  • Configuration

The sequence control and configuration pages contain further menu levels, the other pages are just status displays.

 

 

Configuration Menu

 

To select the configuration menu rotate the control knob clockwise until the message "Push to configure..." is displayed. Press the control knob. The top line displays the position in the configuration menu, the bottom line the selected item in the menu. Rotate the knob to select a particular option and press to select. Each menu level ends with the Exit option. If selected this will drop back to the previous menu level.

 

The control knob can be pressed and then rotated clockwise or anti-clockwise before being released providing two menu navigation short cuts. Releasing the knob after pressing and rotating anti-clockwise moves back to either the previous menu, or in the case of a multi-field value to the previous field. Pressing and releasing the knob after rotating clockwise moves forward in the menu system. When a menu option is shown this is the same as just pressing and releasing the knob. If a menu option has been selected and and associated value is available to edit it will be abandoned and the menu option re-displayed.

 

Each menu option when selected either selects a further menu layer or ends with a value that can be modified. Values can be either a single field or mulitple fields (e.g. an IP address consists of 4 byte fields). The selected field will flash. Pressing the knob will save the displayed value and step to the next field. To cancel any changes press and rotate the knob anti-clockwise and release to go backwards to the menu or previous field. Press and rotate clockwise then release to go forwards. This will skip over all other fields back to the menu and cancel any changes to preceding fields in that value (if any).

 

The configuration menu levels/options available are shown below.

 

Config

    Video

        I/P

            Chnl          {DVI|YPrPb} 

            Std           {X, Y, Scan, Rfsh }

            Auto-mode     {On|Off}

            Save

            Restore

            Exit

        O/P

            Type          {DVI|YPrPb|RGB}

            Enable        {Channel, YES|NO}

            Map           {Channel, Row, Column}

            Filter        {YES|NO}

            Save

            Restore

            Exit

        Exit

    Align

        Split            {X, Y}

        Row              {Row, Offset} 

        Column           {Row, Offset}

        Pan            

            Rows         {Offset}

            Cols         {Offset}

            Exit

        Zoom

            Rows         {Offset}

            Cols         {Offset}

            Exit

        Save

        Restore

        Exit

    Options              {Bit7 .. 0} 

    Boot                 {Filename|<none>}

    FPGA                 {Filename|<none>}

    Clock

        Date             {Day, Month, Year}

        Time             {Hours, Min, Secs}

        Exit

    Display

        Timeout          {Seconds} 

        Brightness       {0..3}

        Exit

    IP

        DHCP             {On|Off}

        Address          {A,B,C,D}

        Mask             {A,B,C,D}

        Gateway          {A,B,C,D}

        DNS              {A,B,C,D}

        SNTP             {A,B,C,D}

        MAC Address      {A,B,C,D,E,F} 

        Exit

    Unit ID              {0..255}

    EDID

        Get              {DVI Channel 1..16}

        Set              {Filename|<none>}

        Delete           {Filename|<none>}

        Exit

    Reset                {Yes|No}

    Keypad               {Yes|No}

    Baudrate

        Host             {Default|1k2|4K8|9K6|19K2|48k|56k}

        Loop             {Default|1k2|4K8|9K6|19K2|48k|56k}

        Exit

    Service

        Telnet           {Yes|No}

        HTTP             {Yes|No}

        MTCP             {Yes|No}

        TFTP             {Yes|No}

        Exit

    Clear

        Config

            Video-in     {Yes|No}

            Video-out    {Yes|No}

            Align        {Yes|No}

            All          {Yes|No} 

            Exit

        Base

        Debug            {Yes|No}

        Secret           {Yes|No}

        Exit

    Exit

  

Changing some values such as IP addresses, baud rates and boot filenames will only take effect following a reset.

 

Sequence Control Menu

 

The sequence control menu allows sequences that have been installed via the Buttons dialog box to be executed locally. When selected the Sequence Control page displays the name of any executing sequence file or <none> if there isn't a sequence running. Press the control knob to enter the menu, which has the following options

Stop
Run       
{Filename|<none>}
Run Num    {0..9}

Startup    {Filename|<none>}

Delete     {Filename|<none>}

Exit

Stop will stop any sequence that is running.

 

Run will present a sub-menu allowing the list of files in the Brick-HD /sequence directory with the file extension .sfb or .SFB to be selected. If selected the sequence will execute.

 

Run Num will run sequences mapped to the ASCII characters 0..9.

 

Startup will copy the selected file to a file called "/sequence/startup.sfb" If this file is present following a reset or power on it will be executed.

 

Delete will delete the selected file.

 

 


 

 Program Options

 

Program options are selected from the File/Options menu.

 

 

 

Three options are available

 

  • Skip the standard include file.

This can be useful sometimes when testing sequence files. If the option is checked the file STD.INC will not be included before a sequence file is interpreted.

  • Don't perform a link status check.

    Normally when a menu option is selected requiring communication with a remote unit, a link status check is first performed. A message dialog will be presented if this check fails and the normal dialog box will not be presented. To stop this behaviour check this box.

    Skipping the link status check can be useful if there is a problem with one of a number of linked Brick-HD units - for example if two units have the same ID, both will respond to the status check message which will then be corrupted.
     

  • Enable logging

To record messages sent to and from the processor in a log file check the logging enabled tick box. Once a log has been created it can be viewed from this menu using the View Log button. To clear the log click Clear Log. This feature should be used with caution since large log files could be generated.

 

The selected options are not saved, so the default options will always apply when the program starts.

 


 Video Input Settings

 

Video input settings are set using the Video Input Dialog box selected from the main menu Video In option.

 

 

The software can be used to control up to four processors directly via the GUI. Select the processor to be configured using the buttons in the "configure unit" box. To configure all units the same, using unit 0 as the master use the "*" select all button.

 

If a valid signal is present on the selected input, the lock box will be shown green, if not locked it will be red. The Brick-HD can be set to automatically determine the video standard on the selected input by checking the "Auto standard detect" box. Alternatively the video input signal parameters can be configured manually if the box is unchecked. To set the Brick-HD to the manually configured parameters click update.

 

If the video standard is known there may be some advantage to using the manual configuration since a valid signal will be available downstream faster since it will not be necessary for the Brick-HD to take some time to measure the input signal before it is used. It is possible to select the automatic option to configure the input initially and revert to the manual mode once it has locked.

 

The Standard Definition configuration buttons will be greyed out if the firmware does not support any SD video formats via the Composite/S-Video inputs.

 

The selected input and video standard can be saved to be re-applied on power-up/reset using the save button. The settings can be copied into the editor cut/paste buffer using the copy button and used in a sequence.

 

The Details button can be used to show some detailed diagnostic information which can be useful to determine the cause of a sync. lock failure. The detailed information is similar to  that available from the shell command "show video input".

 

To exit click on the "OK" button.

 

 


 DVI EDID Table

 

 

The DVI specification provides a mechanism for a device to read the display characteristics of a monitor (Extended Display Identification Data) via the DVI interface. This is usually a small serial ROM (Read Only Memory) with the information in a compressed data format. In the case of the Brick-HD this is programmable to allow the device connected to the Brick-HD's DVI input to see information that relates to the monitors connected to the outputs.

 

By default the Brick-HD provides an EDID table that includes the common display modes likely to be used. This can be replaced by the EDID table captured from a monitor connected to one of the DVI outputs of the Brick-HD, or a file generated externally.

 

To replace the default EDID table on start-up a file called dvi.edid must be placed in the flash filing system directory /etc.

 

To manage the edid files, select the menu option /Files/Edid. This will show a dialog box with a list of installed edid files. If there are none a warning dialog box will be displayed prior to this, indicating a failure to download the initial list.

 

 

 

 

To create an EDID file by capturing the EDID information from a connected monitor click the Capture button. The Brick-HD's output mode must be set to DVI for this to work. Each output available to capture information from will be shown in the capture dialog.

 

 

Click on the appropriate channel number. A file named "ChannelNN.edid" will be saved in /etc and listed in the Set EDID dialog list. To make this the initial EDID file on start-up select the filename and click on Make Default. The file dvi.edid will be created if it did not exist or overwritten with the new data if it did.

 

EDID files for HDMI interfaces contain an HDMI vendor specific data block. If this block is not preset the connected HDMI device should treat the interface as a DVI interface. The Brick-HD uses a DVI interface, not DVI. So to remove the HDMI Vendor Specific Data block, if present in a captured EDID, check the Suppress HDMI Vendor Specific Data Block check box.

 

The contents of an EDID file can be decoded by selecting it and clicking on the View button.

 

 

 

The video output settings are set using the video output dialog below selected using the main menu Video Out option.

 

There are three possible output modes, DVI or Component (YPrPb or RGB). All are via the same DVI connector.

 

If supported by the installed firmware each output has a 2 dimensional interpolation filter. This can be enabled or disabled in both directions independently. If the installed firmware version does not support the interpolation filter, these options will also be greyed out.

 

Once configured the settings can be saved in a file in flash memory on the processor. These settings will be re-applied after a software reset or on power-up. The settings can also be copied to the editor cut/paste buffer, using the copy button. The configuration can then be pasted into a text file as part of a sequence.

 

The software can be used to control up to four processors. Select the processor to be configured using the buttons in the "configure unit" box. To configure all units the same, using unit 0 as the master use the "*" select all button.

 

To exit click on the "OK" button.

 


 Monitor Alignment

 

The monitor alignment feature allows various monitor layouts to be configured. The gaps between the monitors (mullions) can be compensated for. It is also possible to move rows and columns of monitors by a large enough margin to account for monitors with a different aspect ratio to the input signal.

 

The alignment dialog box is show below.

The Brick-HD needs to be aligned for each split (magnification factor) that is going to be used for each image resolution used.

 

The alignment capability provided by the processor is no substitute for alignment on the monitors themselves. These should be all be aligned the same to start with.

 

To align the monitor array first make sure the monitors are cabled as expected. Selecting an individual monitor in the array will cause the corresponding channel to display a blue colour wash. If the channel does not appear in the correct position in the array instead of moving the cables it's possible to achieve the same effect in software. See the channel mapping section below.

 

Next select a split to align the wall with using the spit button, e.g. 4x4 in the case of standard 16 channel installation. Click on a row (button A,B,C etc) to select a row to adjust, Use the slider on the left to move that row up or down relative to the rest. The same action is possible on columns (1,2,3 etc).

 

To clear a selection click on the X button in the top left hand side of the monitor array.

 

If the split is less than the maximum it will repeat. So for example, in the case of a split of 2 on a 4x4 wall, columns 2 and 4 will have the same video image and alignment as columns 1 and 3.

 

To completely erase the settings for all splits for the current image resolution, use the Default button. To clear the current selected row or column and set it back the default use the Clear button.

 

When complete, the alignment can be saved in a file on the processor using the Save button. The saved configuration will be applied on power-up/reset. The split selected will also be re-applied at the same time.

 

If you are using monitors with no overscan it is possible to set the alignment using the bezel button.

 

 

Enter the outside dimensions of one of the LCD monitors in the Bezel width and Bezel height fields. Enter the size of the image on one of the monitors in picture width and picture height. The units are arbitrary since the final calculation uses a ratio of the inner and outer dimensions. When you click on OK or Apply the alignment offsets will be set with the image aligned so that the top left hand side of the image is aligned to the top left hand side monitor. In the case of a 4x4 array with a split of 4 this will for example this will leave a black boarder on the right hand side and bottom edges. To avoid this set the split to 5 and apply the bezel dimensions. Use the Pan button in conjunction with the two slider controls to centre the image.

 

When using the bezel button it is essential that there is an image being displayed, since the calculation requires the source image dimensions (in pixels) to be known.

 

The bezel adjustment, like all of the alignment settings has to be performed for each split (magnification) and each image dimension that is likely to be used.

 

 

Channel mapping

 

The mapping of output channels to a position in the video wall array can be changed using the Channel Mapping feature.

 

To map a channel either click on the monitor you want to move then click on Swap, (or simply right click on the monitor). The selected monitor will be highlighted in yellow. Then left click on the monitor position you want it to occupy. The monitor positions will be swapped. The effect will be immediately visible on the videowall itself if a video image is being displayed.

 

To re-dimension the wall from it's normal default mapping wall use the Dimension button. This will automatically allocate the channels in rows and columns from a starting point. Click on a monitor to select this prior to clicking the Dimension button. For example the apparently odd mapping for a 5x5 wall can easily be changed to linear row/column count using this feature. When the Dimension button is pressed a further dialog box will appear allowing the row/column and split details to be entered.

 

The monitor mapping configuration can be saved using the Save button in the channel mapping box. The mapping can also be copied to the editor cut/paste scratch pad, using the copy button. The mapping configuration can then be pasted into a text file as part of a sequence.

 

Channels can also be mapped dynamically as part of a timed sequence to create visual effects.

 

 

This dialog is used to set the Split (magnification). Click on a value in the X column to set the X and Y split. If an asymmetric split is desired select the Y split factor. X will remain unchanged

 

This dialog is available from the Monitor Alignment dialog.

 


 Array Dimension

 

The Array Dimension dialog allows the output channels to be mapped in bulk in regular arrays. The Dialog is selected by clicking on the Map button from the Monitor Alignment Dialog available from the main menu.

 

Before selecting the dialog box, select the monitor you want the new mapped array to start at e.g the top left hand monitor. This sets the array mapping origin. Alternatively the origin can be set using the Start Row and Start Column pull down menus.

 

The size of the mapped array can be set with the Width and Height pull-down menu.

 

The units to be used to supply the channels can be selected by checking the appropriate check box in the units group. Channels can be allocated in rows or columns by selecting the desired option in the Algorithm group. If more than one unit is selected and the "use complete rows/columns" option is checked, the channels will be mapped so that all the channels of the "allocate in" type are taken from the same unit.

 

Once set click OK. The mapping will take place on return to the Monitor Alignment dialog.

 


 Sequence Buttons

 

The Sequence Buttons Dialog box is available from the main menu "Buttons" or by right clicking in the main window client area.

 

The dialog box provides 10 tabbed pages of buttons which comprises a project. Each button is associated with a sequence file. The highlighted button in the action group determines what will happen if one of the buttons on the tabbed section is left clicked, using the mouse. If the button is right clicked a menu will appear presenting a set of actions, which is a shortcut way of performing an action on the sequence file associated with the button, if that action isn't selected. Right clicking on the space where a button could be placed presents a different menu to create a new button or paste a previously cut button.

 

The default action is to execute the Sequence file (Run).

 

To create a new project - or select an existing project click on the Project button in the Action group. This will present a file open dialog box. Use this to either move to a suitable directory and enter the name of a new project, or navigate to a directory and click on an existing project then Open. Project files have the extension .EFX

 

See below on how to add buttons to the project

 

To execute a sequence, select the Run action and left click on the button.

 

To move a button, select the Cut action and click on the button. Left click on a spare button to place it. It is possible to change pages in this state. The Cut button will be remembered and can be pasted more then once. This only duplicates the button - there is still only one underlying sequence file.

 

To permanently delete a button select the Delete action and click on the desired button. This will only delete the button, not the associated sequence file.

 

To edit the sequence associated with the button click on Edit in the action group, then the desired button. If the sequence file exists it will be opened in the editor. If not a dialog box asking to create the file will be presented. A sequence file is a plain text file containing a number of sequence commands. The format of a sequence file in general is described here.

 

See below to rename the button, or associated file.

 

To exit from the dialog box click Done. If changes to the project have been made you will be prompted to save these changes. If this request is cancelled the button dialog will remain, If the answer is No, changes since the last save are lost.

 

 

Adding a Sequence Buttons

 

To add buttons to the project click on New in the Action group. This will disable all existing buttons on the tab and show all the spare button positions. A different page can be selected in this state. Click on a spare button. A dialog box will appear allowing the name of the button and path to a sequence file to be entered. An open file dialog box can be used to locate the sequence file if Browse is selected. The sequence file does not have to exist at this point - the name of a new file can be entered. By convention the file should have the extension .SEQ

 

You can achieve the same by right clicking in the button tabbed area at a spare button location. A menu will pop up, select new to add a new button or paste to paste in a previously cut button.

 

Alternatively, if a sequence file exists that you want to map to a button - from another project for example, open a Windows Explorer window (My Computer) and browse to the directory the file is located in. Left click and hold the mouse button down and drag the file to the tabbed area and release the mouse button. This will "Drag and Drop" the file to the project.

 

If the point at which the mouse cursor is located when the mouse button is released is where a sequence button would be located a button will be created and the add sequence dialog will appear with the legend and filename fields populated. These can be edited at this point.

 

 

 

If the mouse button is released at another location within the dialog box, the spare button positions will be highlighted. Clicking on one of these will pop up the "Add Sequence Button" dialog as before.

 

 

Renaming a Sequence Button

 

Renaming a button is much the same as adding one. Select Rename from the Action group and left click on the button to rename it. The dialog box shown below will appear, with the appropriate legend and filename values populated. These can be edited. When OK is pressed the new values will be saved.

Installing Sequences on the Processor

 

It is possible to download a sequence to the processor Flash memory and have it execute on the processor itself. Execution can be triggered using the VFD menu on the front panel  - or by any other control device capable of sending ASCII characters at the correct speed and format (The default is 19200 bit/s, 8 Data bits, 1 Stop bit and no Parity).

 

The Brick-HD must be have the TFTP service enabled and have IP connectivity with the PC running the control software to allow file transfer with the controlling PC.

 

To download a sequence click on the install action then the button associated with the sequence. This will invoke the sequence compiler. If successful, the compiled sequence, now in a binary format, is downloaded to the Flash memory of the processor. The filename used is derived by the software from the PC filename - but this can be changed prior to downloading if required. The extension ".SFB" must be used for files to be executed by the processor. Files downloaded to the Flash memory can be managed using the Flash utility available from the main menu Flash option.

 

In a multi-processor installation, sequence files are generally only installed on processor 0. Messages in the sequence for other processors in the daisy chain are sent by unit 0 to the addressed processor. The slave processors behave in the same way as if they were being controlled by a remote PC.

 

It is possible to install sequences on processors other than unit 0 by selecting the processor selecting the Unit as the primary unit from the setup dialog. Changing the Unit ID from the "Unit ID" group of buttons changes the unit ID in compiled sequences but does not set the primary unit.

 

Executing a Sequence

 

When a sequence is run the software reads the lines of text from the file into memory and begins interpreting them. If an error is detected a dialog pops up indicating the error. At this point it is possible to select an option to open the file and go directly to the line causing the error.

 

The line number currently being executed is displayed. The time-code, relative to the time the sequence stared is also displayed. Since lines execute quickly it's only lines with a "wait" command the will be displayed in the line number box for a sustained period. At this point the Skip button will be enabled. To skip over the wait, click the skip button. Execution will continue until then next wait statement. To pause indefinitely click the Pause button. The name of the Pause button will change to Run. Click this Run button to resume execution.

 

To exit the sequence at any point click Stop.

 

If the Done button is clicked when a sequence is running it will be abandoned and the dialog box closed.

 

If the sequence contains a REM statement, the Tabbed page of buttons is replaced by a text window while the sequence is running. REM statement text is displayed in this window. If REM statement does not cause the text window to appear and a button from the tabbed page of buttons is clicked, the current sequence is aborted and the new sequence selected runs.

 

Set Unit ID

 

A special macro value "_UNIT" is set to the value of the current unit ID (indicated by the IDx pane in the status line of the main window) at the start of a sequence. This value can be changed by selecting the unit ID from one of the file buttons in the "Unit ID" set. 

 

A specific unit ID button will only be active if that unit has been enabled in the Setup dialog.

 

To use this value within a sequence, command macros must use the _UNIT value in place of the unit ID value in send commands, for example,

 

send 7 _UNIT 0

 

The value of _UNIT can also be set within a sequence, for example,

 

set _UNIT = 1

 


 

FRAME STRUCTURE

 

The Serial RS-232 communications frame structure is common to both directions of transmission. Messages are delimited by start and end of message flags. The body of the frame comprises the control and address bytes the message (which is optional) and a single byte checksum.

 

SOM

Control

Address

[Channel]

[Source]

[ <Message data...> ]

Checksum

EOM

Frames not containing any message data bytes are referred to as 'null' frames.

 

Characters received between EOM and SOM characters (i.e. un-framed) are ignored - unless the single character sequence file feature is invoked.

 

The start and end of messages are special character values that must not occur in the data bytes between them to ensure correct message framing. To achieve this a third value, the byte stuff character, (BSF) is used. This is also a unique character value that also must not appear as a data byte, so is also preceded by a BSF character.

 

The byte values of these three special characters are:

SOM 

0x7E

EOM

0x7D

BSF

0x7C

Byte transparency is achieved by replacing any of the three special characters that occur as data bytes with a two byte sequence headed by the BSF character. The second character is the character X-ORed with the 'smudge' character, 0x20, which prevents recognition by the receiver as a special byte. e.g. a data byte 0x7E is replaced with the byte pair: 0x7C,0x5E.

 

The channel and source bytes are only present in extended frames. An extended frame is indicated by bit 5 in the control byte set to 1. Extended frames are only required between devices in a multi-device chain. Extended frames are not required for communication between the host PC and a Brick-HD and are not used by the PC control Software supplied.

 

 

CONTROL BYTE

 

The control byte comprises two fields. The upper 4 bits are mode bits controlling the use of the addressing information. The lower 4 bits are the Device Address. In the receive direction (Processor to PC) the mode bits are not used. (Unused bits are marked in the table below with an dash) As a convention, unused bits should be set to zero, but receiving software should not reject messages if they are not.

Transmit Bits

7

6

5

4

3

2

1

0

M1

M0

EXTN

0

A3

A2

A1

A0

 

 

Receive Bits

7

6

5

4

3

2

1

0

-

-

EXTN

1

A3

A2

A1

A0

Device Address [ A3 to A0 ] Device Type

 

Device Address

 Device Type

0 - 6  Reserved

 Brick Processor

The two mode bits M1 and M0 allow for 4 addressing modes:

 

M1 M0  Addressing Mode
00Normal Address
01Response (Poll)
10Global of type (A3 to A0)
11

Global all units.

The EXTN bit indicates an extended frame is used. If an extended frame is used two bytes are added to the frame header, channel and source. The channel relates to the TCP/IP socket on the Brick-HD from which the message originated and the source byte is the Unit ID of the originating Brick-HD. Channels number from 0.

 

 

 

ADDRESS BYTE

 

The address byte allows 256 devices of the type selected in the Control byte Device Address field to be individually addressed.

 

NORMAL ADDRESS MODE

 

In this mode, the address byte is used to select a specific device (one of 256), of the type set by the device address field in the control byte. Only one unique device will therefore act on the message.

 

RESPONSE (POLL) MODE

 

The message will be received by the addressed device in the same manner as the Normal Address mode, however the addressed device will respond with a return frame. If there is no message pending in the addressed device the response will be a null frame. Note this will be the reply from a previous message. If the device receives a POLL it will send the next message in the outgoing queue before processing the message. A null frame can be used to read the next message from the send queue without executing a command.

 

GLOBAL TYPE ADDRESS MODE

 

All devices of the type defined in the control bytes unit field will act upon this message. It is not possible to globally poll devices since more than one would respond and the messages collide. In this mode the address byte is redundant, but it is still sent to maintain a simple frame structure. By convention the address byte should be zero in this case.

 

GLOBAL ADDRESS MODE

 

This is similar to the previous case except that all devices of any type will act on the message.  The usefulness of this mode is really restricted to generic commands such as 'RESET' and 'BAUDRATE'

 

CHECKSUM

 

The checksum is calculated by summing modulo-256, all of the bytes between the start and end of message characters, prior to the byte stuffing process, and subtracting this figure from zero.  The receiver checks the received data by summing all the bytes following the start of message (after expanding the 'stuffed' bytes). When the end of message character is received the sum should be zero.

 

MESSAGE CONTENTS

 

The length of the message is not limited by the protocol. As described above, it can be of zero length for use in polling and null responses, where there is otherwise no data to transfer. The message format is the same for both directions of transmission, comprising a function code in the range 0 to 255 followed by an optional parameter list. The convention for parameters greater then 255 is least significant byte first.

 

Function codes are device specific and detailed in separate manuals for each device. The function codes from 0 to 15 are reserved for generic operations, such as returning software version numbers, which all devices support. In addition there are generic function codes to support extended addressing techniques for selecting multiple devices.

 

PROTOCOL VIOLATIONS

 

Any protocol violations should cause the current message to be abandoned. The receiver will revert to a mode waiting for the start of message character. If the violation was an out of sequence start of message character, a new message will be assumed. Message frames with checksum errors are ignored.

 

Although the BSF character would normally only precede a 'smudged' version of one of the 3 special byte codes, (SOM, EOM, BSF) the presence of any other character is not considered a violation. The 'un-smudging' process should be applied regardless of the 'smudged' character code provided it is not either SOM, EOM or BSF.

 


 

The Brick-HD Software control program includes a simple real-time sequence control language. Video effects are invoked using timed sequences of commands to the hardware. The language commands are held in standard ASCII text files. The sequence files may be created with the integrated editor or an external text editor/word processor.

 

Control commands are decoded and sent as messages to the hardware via the PC serial ports. Sequences can be compiled and downloaded to the processor itself and executed there.

 

The control language uses a basic command and parameter list format. A line based macro processor is included.

 

The description of the commands uses the following common language notation. Optional parameters are contained in square brackets. A parameter which must be one of a set is indicated by the set enclosed in curly brackets, each parameter separated by a vertical bar. Variable parameters are contained in angle brackets. Parameters are separated by commas.

 

Each line of the command file consists of either a blank line, a comment, or a command. Only one command may be invoked per line. Most commands are followed by a variable length list of parameters dependent on the command type.

 

Numeric parameters can be in either decimal, hex, or binary. Hex numbers may be represented in either the 'C' format as 0xnn or the 'assembler' format using a leading decimal digit and trailing 'H' Binary numbers are designated by a trailing 'B'.  Any number may have leading zeros. Unlike 'C' this does not designate base 8. Hex numbers may use upper or lower case letters.

 

For example

 

Decimal                 

255

16-bit Decimal

&16430

8-Bit Binary 

 11111111B

8-bit Hexadecimal   

 0xFF, 0x0ff  or 0FFH

16-bit Hexadecimal  

&0x800F

 

All commands and parameters should be delimited by a space, comma, or tab character. The default base may be changed using the RADIX command to any base from 2 to 16. Macros may be defined to substitute text strings with key words. Command words can be in either upper or lower case. Macros are case sensitive.

 

Examples are provided on the distribution disk which should be consulted to gain a further insight into the application of these commands.

 

Function codes are used in messages, sent to the processor with an optional set of arguments that vary for each function code. They are are preceded by the address of the device to which they are directed. i.e

 

SEND 7 0 FN_CODE p1 .. pn

 

SEND               

Builds and sends a message to the selected device.

7

The device type for the Brick-HD processor - the MACRO BRICKHD defined in std.inc can be used instead

0

The sub-address of the device type. To use the current unit id the _UNIT macro can be used

FN_CODE

Command code, 0 to 255 binary

p1 .. pn 

Optional parameters

 

 

For example, to set the global split to 4x4 either of the two command lines could be used.

 

SEND BRICKHD _UNIT FN_SPLIT 4

send 7 0 40 4

 

The first line will be expanded by the macro pre-processor to the 2nd form (assuming _UNIT = 0) before being executed.

 

Some functions require 16 bit parameters. These can be created by preceding them with the '&' character. For example, to position the graphics cursor:..

 

SEND 7 0 85 &100 &100

 

String parameters are required by some functions.

 

SEND 7 0 FN_CODE "string"

 

The macro pre-processor can be used to make these message statements more human readable by defining names for strings of constants using the DEFINE and PROC commands, described below.

 

A number of pre-defined macro definitions are included in the file STD.INC. This must be located in the same directory as vwctrl.exe program. It is possible (but not recommended) to edit "STD.INC" to customise the names for function commands, for example to substitute words in another language.

 

Command messages have one of two attributes, either immediate or queued. Commands with the immediate attribute are executed when they are received. Commands that do not have this attribute are queued and execute when the currently executing command completes.

 

It is possible to change the immediate behaviour using the IMMEDIATE message. A command sent after the IMMEDIATE command will act immediately regardless of its immediate attribute.

 

Commands with the queued attribute will execute in downloaded sequence files. Commands without this attribute are commands that would normally be used with an external control program and could have a detrimental effect if executed locally within a downloaded sequence, e.g. RESET.

 


 Sequence File Commands

 

The following commands are implemented.

 

 

INCLUDE

 

 

The include command 'includes' text from another file in the current file. The command syntax is:-

 

INCLUDE { <filename.typ> | ["][d:][\path\]filename[.typ]["] }

 

The INCLUDE command has one parameter, either a filename in angle brackets or a conventional Windows filename. Quotes are optional on the conventional filename if it doesn't use spaces. Included filenames in angle brackets are expected to be in the same directory as the program.

 

Conventional filenames without the angle brackets can optionally have drive letters, path descriptions and file types.

 

Includes can be nested to a depth of 10. The nesting depth is the only method by which recursive includes are trapped. Files may be 'included' at any point in a command file.

 

The file STD.INC is a special case. If a file of this name is found in the current directory it will be included before the sequence file is executed.

 

 

SEND

 

The SEND command sends a single command to the processor. The send command expects at least 3 parameters. (See the hardware interface description for details of commands.) Command syntax is as follows:-

 

SEND <p1>,<p2>,<p3> [,<p4> .. <pN>]

 

The parameters p1 to pN are numbers in the range 0 - 255. A parameter from p4 onwards may be preceded by the '&' character to force it to occupy two bytes, LSB first.

 

The first 3 parameters common to all SEND commands are as follows.

 

p1 = Module type.  

p2 = Module address. 

p3 = Message function code.

 

 

Module type is a number with the following allocation, 

 

0 - 6  : RESERVED 

7      : BRICK PROCESSOR

 

The module address is a number from 0 to 255. A macro “_UNIT” may be used instead, which substitutes the currently selected unit address from the UNIT ID menu.

 

The message function code is decoded by the addressed module which executes the function using any parameters which follow.

 

The Brick-HD series processors have no separate internal modules so requires only one sub-address. By default this is zero. If additional processors are used, e.g to provide full frame splits greater than 4x4, each processor needs to be allocated a unique address. If the processors are ordered with this intention, they will be supplied pre-configured.

 

Parameters p4 to pN are placed in the data bytes section of a message. An ASCII text string can be used in the parameter list.

 

Each character of the string will be converted to a number in the range 32..127 and used in the same way as numeric parameters.

 

 

GET

 

The GET command combines SEND with a poll for the reply. The command syntax is the same as SEND.

 

 

OUTPUT

 

The OUTPUT command is a lower level version of the SEND command. It will send any number of parameters supplied as bytes to the hardware (limited by the maximum line length) without formatting the data into a structured message.

 

Command syntax is...

 

OUTPUT <p1> [<p2> .. <pN>] 

 

A parameter may be preceded by the '&' character to force it to occupy two bytes, LSB first. ASCII strings may be sent by enclosing them in double quotes, For example:

 

OUTPUT "PLAY",0x0D

 

 

RATE

 

This sets the assumed refresh/field rate. This may be used in WAIT commands where fractions of a second are expressed as N fields. (See the WAIT command syntax below.) It is also used when sequences are compiled and downloaded to the Brick-HD itself. The sequence compiler will convert a WAIT command to a number of fields using this parameter.

 

The default value is 60.

 

WAIT

 

This is the primary time dependent command word. Parameters supplied determine whether the control program will wait for a set period, until the elapsed time since the start of the file, the absolute time or on reaching a time code for the selected video source.

 

Command syntax is as follows.

 

WAIT [FOR|ELAPSED] <time>

WAIT EVENT {DVI-SYNC | YPBPR-SYNC | DVI-LOS | YPBPR-SYNC}

 

 

The time parameter consists of hh:mm:ss:ff or hh:mm:ss.dd

Value

Units

hh

Hours

mm

Minutes

ss

Seconds

dd

1/100 fractions of a second

ff

Fields

The time is defined in the 24 hour clock format, hours, minutes, seconds and optionally hundredths of a second if a dot is used to separate the seconds or fields if a colon is used.

 

The field rate is determined using the RATE command (above).

 

The default if no sub-command is supplied is the same as FOR.

 

The WAIT FOR subcommand will wait for the selected time on decoding the command. The wait condition can be terminated in advance by clicking on the "skip" button.

 

The WAIT ELAPSED subcommand will wait until the elapsed time from the start of the command file is greater than the time defined.

 

The WAIT EVENT subcommand can be used to pause the sequence waiting for an external event. The sequence will halt indefinitely until the event condition is met. Four conditions are currently provided.

Event

Description

DVI-SYNC

DVI input becomes active

DVI-LOS

DVI input loss of signal

YPRB-SYNC

YPrPb Input out locked (to line sync)

YPRPB-LOS

YPrPb Input loss of input signal

 

DEFINE

 

Macros can be defined, using the DEFINE command, which will be expanded on a line by line basis when encountered.

 

Command syntax is…

 

DEFINE NAME [=] text....

 

The macro NAME can have up to 16 characters. There is no restriction on the characters of the macro name apart from delimiters equals, space,  tab and comma. Macros are expanded as they are encountered in the input file by the command processor except if they are parameters to a macro definition.

 

Macros must be defined before they can be used.

 

The macro text can comprise delimited parameters. A parameter substitution mechanism is provided. This allows up to 9 parameters in the text portion of the macro definition to be undefined. These are designated by a question mark followed by a decimal digit in the range 1 to 9.

 

Parameters following the macro name on expansion will be substituted in the order defined by the number following the question mark.

 

For example the macro defined like this…

 

DEFINE SWAP = ?2,?1

 

On expansion, will reverse the parameters supplied, so that for example…

 

OUTPUT SWAP 200,100

 

Expands to…

 

OUTPUT 100 200

 

Macros can be nested to any depth, but on expansion the line length must not exceed 132 characters.

 

 

FORGET

 

Macros and procedures can be deleted from the symbol table at any point in the file using the FORGET command. If previously defined macros depend on the macro that has been deleted they will cause errors on expansion later.

 

Command syntax is…

 

FORGET name

 

 

PROCEDURES

 

Procedures are similar to macros in many ways except that they span more than one line and may contain a number of commands. Up to 9 parameters can be passed to each procedure. The procedure is defined starting with the PROC keyword and terminates with the ENDPROC keyword. Both keywords must be on a separate line.

 

Command syntax is…

 

PROC name [p1 .. pn]

  .

  Commands

  .

ENDPROC

 

Procedures can have up to 9 parameters. These can be used to substitute parameters to commands within the body of the procedure, or passed as further parameters to procedures calls within the procedure body, for example:-

 

PROC EFFECT start,middle,finish ; Procedure EFFECT with 3 parameters

  SEND 7 0 1,2,start            ; Use each parameter in turn for the

  SEND 7 0 1,2,middle           ; same basic command

  SEND 7 0 1,2,finish

ENDPROC                         ; End of procedure

 

EFFECT 1,2,3                    ; Execute procedure

EFFECT 4,5,6                    ; Again with different arguments

 

The dummy arguments: 'start, middle, finish' define the number of parameters the procedure will accept. When the procedure is used the number of parameter arguments supplied is checked. If the wrong number of parameters is supplied an error message is displayed and execution stops.

 

Note:    Procedures with parameters are not supported in compiled sequences downloaded (installed) to the Brick-HD.

 

 

REMARKS

 

The REM command allows remarks to be displayed on screen as the commands are sent to the processor. All the text following the REM statement is displayed on the screen. As soon as the macro expander recognises the REM command, macro expansion ceases.

 

In addition a number of escape codes are provided as follows.

 

@t Current system time. 

@d Current system date. 

@s File start time. 

@e Elapsed time.

@f The current sequence file name. 

@b Bell character.

 

Two further escape codes may be used in REM commands to show the two innermost loop counts generated by the REPEAT command.

 

@i Inner loop count 

@j Second level loop count

 

REM commands are not compiled into download sequences.

 

 

REPEAT

 

Command syntax is.

 

REPEAT [FOREVER | <n>]

 

The REPEAT command marks the beginning of a program loop. REPEAT commands must be matched by a corresponding AGAIN or UNTIL command.

 

An optional loop count can be supplied. If a loop count is not supplied, FOREVER is assumed.

 

A loop can be terminated using a parameter to the UNTIL command even if it is started with a REPEAT FOREVER command, for example:-

 

REPEAT 20

 .

 Commands on any number of lines

 .

AGAIN

 

Or...

 

REPEAT FOREVER

  . 

  Commands in loop 

  . 

UNTIL 00:20:00

 

REPEAT commands can be nested, for example:-

 

REPEAT            ; Start of outer loop 

  REPEAT 20       ; Repeat a sequence 20 times

  .

  Commands        ; Commands comprising the sequence 

  .

  AGAIN           ; Loop back to nearest REPEAT 

UNTIL 0:0:10      ; Keep going until time is passed

 

Two special macros are provided which are converted to the current loop index when used. These special macros are @i and @j.

 

The following shows the format.

 

REPEAT 3 

  REPEAT 3 

    REM Loop = @j,@i 

  AGAIN 

AGAIN

 

This double loop will display in a window the following messages…

 

Loop = 1,1 

Loop = 1,2 

Loop = 1,3 

Loop = 2,1 

(etc... until) 

Loop = 3,3

 

These special macros can be used as parameters to macros and procedures.

 

 

AGAIN

 

This command marks the end of a looping program block. There are no parameters. See above REPEAT command.

 

 

UNTIL

 

The UNTIL command marks the end of a sequence loop. The loop is repeated conditionally with one of two conditions: ELAPSED, or LOOP. Command syntax is.

 

UNTIL [ ELAPSED [ TIME[ = ] ] hh:mm:ss[ {.dd|:ff} ] ] 

UNTIL [ LOOP [TIME[ = ] ] hh:mm:ss[ {.dd|:ff} ] ]

 

ELAPSED TIME is followed by time parameters.

 

The loop will continue until the elapsed time since the start of execution of the file is greater than the time parameter.

 

UNTIL LOOP TIME is also followed by time parameters. This will loop until the elapsed time since the start of the

loop is greater than the supplied time parameter.

 

 

POLL

 

Command syntax is.

 

POLL <card>,<address>

 

This command requests information from hardware in the output buffer. A higher level command "GET" will send a command and automatically poll for a response.

 

If the POLLed device has any data ready for transmission it will be returned on receipt of this command.

 

Devices will only have data if they have been sent a command previously requesting it.

 

If no data is ready a 'NULL POLL' message will be returned. There will be no displayed information in response to 'NULL POLL'

 

If the device addressed does not exist then after a short time-out period a message will be displayed showing that the POLL command failed.

 

Returned messages are defined in the device-specific documentation.

 

 

RADIX

 

The the SEND program uses decimal numbers by default. This may be changed using the RADIX command to any base from 2 to 16.

 

The base selection parameter is always in decimal regardless of the current radix.

 

Command syntax is.

 

RADIX <n>

 

For example to select HEX as the default base…

 

RADIX 16

 

 

Note: This can cause problems with pre-defined macros if the do not explicitly define the base of a number.

 

 

EXIT IF

 

This command enables ‘include’ files to be 'included' more than once without causing re-definition errors using a conditional EXIT command. The command syntax is:-

 

EXIT IF [ DEFINED ] symbol

 

If the symbol is already defined 'including' is abandoned and control continues from the 'calling' file.

 

For example:-

 

EXIT IF FRED 

DEFINE FRED = 1

 

 

COMMENTS

 

Comments can be included either on a blank line or at the end of a command line by preceding the comment with a semicolon.

 

Commented lines must be less than the line maximum of 132 characters. Blank lines and spaces may be freely spread throughout a command file to improve readability.

 


 Message Functions

 

The full set of supported message functions for a particular version of firmware can be determined using the shell command "show message". The picture below shows the output from a terminal emulator using the the command shell with the output from "show message".

 

The same command with a -d switch will format the output so that it can be cut and pasted directly into an include file (i.e. the default std.inc).

Many of these messages are used to control the processor via the Control Software and are not useful in user created sequence files. Those that are most likely to be useful in a user created sequence are listed below.

RESET

 

Resets the addressed device.

 

All internal parameters are set to their power on reset state. The device configuration is derived from a combination of front panel switches and configurations stored in on-board Flash memory.

 

Byte

Parameter

Comment

0

FN_RESET

Reset addressed processor

 

Example

send 7 0 0        ; Reset Brick-HD device 0

 

SHELL COMMAND

 

Sends a shell command to the addressed device. This is a very powerful function allowing a command from the rich set of shell commands to be used. Shell commands which produce an output cannot be used, since there is no mechanism to read the output text. Using the ? and ?? shell commands from the shell will display the supported list. Those shown with an (M) preceding the command can be used in a message.

 

Byte

Parameter

Comment

0

FN_SHELLCMD

Execute a shell command

1 .. N

string

Shell command string

 

Example

send 7 0 1 "set video input dvi"     ; Select input from the DVI connection

This example achieves the same as the FN_SETIN message with parameter 0 (DVI), i.e.

send 7 0 FN_SETIN 0                  ; Select input from the DVI connection        

The advantage of using explicit messages rather than shell commands is that they are shorter and use less resources in firmware, so execute slightly faster.

 

GO

 

Execute a held command. Used in multi-device applications. A hold command may be broadcast to all devices followed by a command to each device, which is held. Following a broadcast GO command all devices will execute the held command synchronously.

 

Byte

Parameter

Comment

0

FN_GO

 

 

Example

send 7 0 FN_GO

 

HOLD

 

Hold a command, pending a later GO command

 

Byte

Parameter

Comment

0

FN_HOLD

 

 

Example

send 7 0 FN_HOLD

 

IMMEDIATE

 

Force the next command to be executed immediately.

 

Byte

Parameter

Comment

0

FN_IMM

 

 

Example

send 7 0 FN_IMM

 

 

 

SELECT INPUT

 

Select a video input source.

 

Byte

Parameter

Comment

0

FN_SETIN

Set Video input source       

1

Source

0=DVI
1=Composite YPrPb
2=Component (PAL/NTSC)
3=S-Video

2

Task flag

0=Manual
1=Automatic standard selection
3

Lock state

Not used, set to 0
4,5

Image width

2 bytes, LSB first, e.g. &1280

6,7

Image height

2 bytes, LSB first e.g. &720

6

Refresh/Field rate

1 byte e.g. 60

7

Interlace/Scan

0=Progressive
1=Interlaced

 

 

There are three forms of this command depending on the number of parameters supplied

 

1 .   The full set of parameters are supplied explicitly setting the input configuration

2.    The input source is selected and the input standard detection mode is set to manual

3.    The input source is selected, the automatic standard selection process runs by default.

 

Examples

 

send 7 0 FN_SETIN 1 0 0 &1280 &720 60 0        ; Component YPrPb - force 720P/60

send 7 0 FN_SETIN 0 0                          ; DVI use currently configured video standard

send 7 0 FN_SETIN 0                            ; DVI use automaic video standard detection

 

 

Other examples, in this case both have the same effect

 

send 7 0 FN_SETIN 1                            ; Component YPrPb, defaults to automatic standard detection

send 7 0 FN_SETIN 1 1                          ; Component YPrPb, explictly set to automatic standard detection

 

 

To save the settings to be applied on startup.

 

Byte

Parameter

Comment

0

FN_SAVEIN

Save Video Input stettings      

 

 

 

SELECT OUTPUT MODE

 

The Brick-HD can output either DVI or Component Video via the same DVI connectors. All 16 channels have to use the same format. Channels can be selectively enabled/disabled using the channel enable flags. These are optional. If not provided all channels are enabled.

 

 

Byte

Parameter

Comment

0

FN_SETOUT

Set Video output       

1

Output format

0=DVI
1=Component YPrPb
2=Component RGB

3,4

Output enable flags

16 bits, bit0=Channel0, bit15=Channel15
1=Enable O/P, 0=Disable O/P

 

 

e.g.

 

send 7 0 FN_SETOUT 0 &0xEEE0

 

will set the output mode to DVI and enable only the 9 monitors in the top left hand corner of the nominal 4x4 array.

The output enable flags are optional. If not supplied all outputs will be enabled.

 

 

If supported by the firmware the 2D output filters can be set on/off per channel.

 

Byte

Parameter

Comment

0

FN_FILTER

Set Video output filter state      

1

Channel

0 .. 15

2

Filter state

0=Off
1=Horizontal only
2=Vertical only
3=Horizontal and Vertical

 

 

To save the selected settings use the following. There are no parameters required.

 

Byte

Parameter

Comment

0

FN_SAVEOUT

Save Video Output stettings      

 

 

 

EFFECTS COMMANDS

 

These commands are commonly used to assemble sequences of effects.

SET SPLIT

 

Set the split factor. This will magnify the image by the factor.

 

Byte

Parameter

Comment

0

FN_SPLIT

Function code  = 40            

1

Split X

1 to 16               

2

Split Y

1 to 16 Optional

 

Example

 

send 7 0 FN_SPLIT  2            ; Set X,Y magnification to 2 

send 7 0 FN_SPLIT  4 3          ; Set asymmetric split x=4, y=3

 

 

WASH COLOUR

 

Set the colour wash for a given monitor or all monitors simultaneously.

 

The command will have no direct visual effect unless a wash is already selected on a given display monitor. When a monitor display mode is set to WASH the colour set with this command will be applied.

 

If a wash is currently displayed the on-screen colour will be updated.

 

Byte

Parameter

Comment

0

FN_SETWASH

 

1

Monitor (O/P channel)

0 .. 15 or 255 for all monitors

2

Red Intensity 

0 .. 255           

3

Green Intensity

0 .. 255          

4

Blue Intensity 

0 .. 255

 

Examples,

 

Set the wash colour of channel 1 to bright red.

 

send 7 0 FN_SETWASH 0 255 0 0    ; Set monitor 1 (0) to red

 

 

Set the wash colour of all channels to bright mid blue.

 

send 7 0 FN_SETWASH 255 0 0 255  ; Set all monitors to blue

 

 

 

DISPLAY

 

This command sets the display mode for a given monitor.

 

Byte

Parameter

Comment

0

FN_DSPMODE

 

1

Monitor

0 .. 15 or 255 for all monitors

2

Mode

0 = Video

1 = Colour wash

 

Examples, show the preset channel wash colour or video

 

send 7 0 FN_DSPMODE 0 0        ; Show video on monitor 1   

send 7 0 FN_DSPMODE -1 1       ; Show colour washes on all channels

 

Note: -1 translates to 255 for a signed byte

 

 

AUXOUT

The FN_AUXOUT commands sends a string of arbitrary bytes out of the auxillary serial port (Loop). This can only be used with a stand alone Brick-HD or the last Brick-HD in a chain in the case of a multi-Brick-HD installation.

 

Byte

Parameter

Comment

0

FN_AUXOUT

 

1 .. N

List of bytes

 

 

Example, to send the string PLAY followed by cariage return out of the loop port of Brick-HD with the ID of zero,

 

send 7 0 FN_AUXOUT "PLAY" 0x0D

 

If the Brick-HD is used in a multi-Brick-HD mode, the Host and Loop serial ports can be configured in a bussed mode, so that characters received on the Host port are sent directly out of the Loop port. This ensures that all devices in the chain recieve the message at the same time.

To prevent this interferring with the characters sent to the device being controlled by the string commands the last Brick-HD in the chain should be configured with the command FN_RS232 with mode parameter set to 1.

 

Byte

Parameter

Comment

0

FN_RS232

Set Loop serial port mode

1

Mode

0 = Bussed
1 = Independent

 

The Brick-HD will have the RS-232 mode set to independent following a reset.

If set to independent messages will still be sent along the daisy chain of devices but will depend  the unit ID. Messages addressed to devices other than the local device will be forwarded out of the loop port but there will be a delay since the whole message has to be read before the unit id is inspected to route the message.

 

FREEZE

Freeze or Un-Freeze the display.

 

Byte

Parameter

Comment

0

FN_FREEZE

Freeze/Un-Freeze

1

Bus

Bus (currently always set to 0

2

Mode

0 = Un-Freeze

1 = Freeze

 

 

SEQUENCE EXECUTION FUNCTIONS

The following commands are used to initiate sequences which have been downloaded to the processor FLASH memory using the download menu command.

RUN DOWNLOADED SEQUENCE

 

This command executes a sequence which has previously been downloaded to processor and stored in FLASH memory.

 

The file A:/sequence/seqmap.conf in the Brick-HD filing system maps ASCII characters to sequence file names. These single characters can be used via the serial link if it is set to character mode, instead of the default message mode. This mapping can be done using the command shell, or using the Brick-HD Control software via the "Sequence/Remote" menu option.

 

The Brick-HD can be configured to start in character mode by configuring it using the VFD menu from the front panel, or using the shell command "set keypad on". From a shell session via the serial port the exit command will also enter character mode. To return to command mode press return 4 times.

 

Sequence files can also be executed by name using FN_RUNSEQ.

 

Byte

Parameter

Comment

0

FN_SEQIRN

  

1

Code

Character code byte (1..255)

 

Example, run sequence mapped to character A

 

send 7 0 FN_SEQIRN "A"            ; Run sequence A

 

RUN SEQUENCE FILE

 

Executes a sequence file by name.

 

Sequence files are stored in the Brick-HD flash filing system directory A:/sequence/

 

Byte

Parameter

Comment

0

FN_RUNSEQ

 

1 .. N

Filename string

 

 

 

Example, run a sequence called split1.sfb

 

send 7 0 FN_RUNSEQ "split1.sfb"       ; Run sequence

 

READ EXECUTING SEQUENCE FILE NAME

 

Byte

Parameter

Comment

Code

READSEQ

 

 

Returned Data.

 

Byte

Parameter

Comment

Code

FN_READSEQ

 

1 .. N

Character string

 

 

 

Example, to read the current executing sequence if any

 

get 7 0 FN_READEQ         ; Read seqeuence

 

The result will displayed in the Remark window. In order for the result to persist, the get command should be following by a wait statement in a sequence.

 

CANCEL EXECUTING SEQUENCE

 

Byte

Parameter

Comment

Code

FN_STOPSEQ

 

 

Example

 

get 7 0 FN_STOPSEQ         ; Stop any executing seqeuence

 

 

A text editor based around a standard windows edit control is provided as part of the application. This will pop-up when a sequence button is pressed with the text from the sequence file associated with the selected button. It can also be used to open any sequence file not necessarily associated with a button via the main menu "Sequence/Edit" menu option.

 

 

Find

 

To search for text in a file using the editor, enter the text in the Find field.

 

 

Click "Find next" to search from the current cursor location. If the "Match case" check box is ticked the text must have the same upper and lower case. If "Match whole word" is ticked the matched text must be surrounded by white space.

 

Go to Line Number

 

To position the cursor on a specific line, enter the line number and click OK

 

 

The processor includes a Flash memory filing system. Compiled sequence can be downloaded to the filing system - and have a single character mapped to them for character mode sequence file execution. Compilation and downloading is done using the Buttons dialog.

 

Sequence files are held in a directory "/sequence".  The file holding the mapping between single characters and compiled sequence files is seqmap.conf in the same directory.

 

From the main menu option "Sequence/Remote" the dialog box show below can be invoked to manage remote sequence files. A list of files is read from the remote unit when the dialog box is opened. The file seqmap.conf is then read and the character mapped files overlaid leaving a combined list.

Using this dialog it's possible to run and stop binary sequence (.sfb) files previously installed using the Buttons sequence file creation dialog.  To run a sequence file, select the line containing the sequence file and click run. To stop any executing sequence click Stop. There is no need so select a specific sequence file to stop a running sequence.

 

To delete a sequence file, select the line containing it and click delete.

 

To modify a line entry, select the line to modify and click Modify, or just double click the line. This will pop up a further dialog box allowing the associated character code and comment for the file to be amended, as illustrated below.

 

 

 

The Char and Dec fields are essentially the same. The Char field shows the ASCII character mapped. The Dec field shows the decimal equivalent of that character. Changing one field will cause the other to update with the appropriate value. If the decimal number is outside the displayable ASCII character range the Char field will be blank.

 

Files mapped to ASCII characters in the range 0..9 (decimal 48 to 51) can be invoked using the Sequence Keypad dialog or from the front panel VFD menu.

 

 


 

Sequences saved in the flash memory filing system may be mapped to so that they will execute when a single mapped ASCII character is received via the host  port. Characters 0 through 9 when mapped can be tested from the Brick-HD Control software directly using the sequence keypad.

 

To map a sequence to a character, see the Remote Directory section.

 

 

 


 Binary Sequence Decoder

 

Sequences that have been compiled into a binary format and stored on the PC for downloading to the Flash memory in the Brick-HD processor can be decoded using the Decode menu option from Sequences in the main menu.

 

A file open pop-up dialog will appear when this option is selected allowing a binary sequence file to be opened for decoding.  To decode a sequence file already installed in the Flash memory use the "Sequence / Remote" main menu option.

 

The file will be decoded in a read only text window as shown in the example below.

 

 

 


 

To restart the processor select the unit id (or all units) and click OK. The CPU on the Brick-HD processor will execute a software restart. This is necessary after downloading new firmware. It can also be used to restore the processor to a known initial state when developing sequences.

 


To obtain the firmware and FPGA version information for connected units click on File, then Hardware Info. The following dialog will be displayed. The example below shows a typical response for a single unit connected to the PC.

 

 Firmware Update

 

It is possible to update the processor with later versions of firmware as they are made available using the Brick-HD Control software.

 

The firmware comprises two files. One with the extension .xsvf contains the data for the FPGA (Field Programmable Gate Array) chips which are the chips that split and magnify image in real time. A second file contains the system code for the microprocessor with the extension .bin

 

Current versions of both file types are distributed with the Video Control Software and installed in the same directory as the vwctrl.exe program, typically C:\Program Files\BrickHD\

 

Later versions may be available on the Media Technologies Web site. To use one of these, the .bin and or .xsvf  file should be copied to any convenient PC directory prior to installation. There is no need to copy it to the above directory.

 

In a multi-processor installation, each processor has to be updated separately. To select the ID of the processor to update use the Setup dialog to select the Primary Processor ID, which is the ID of the processor that will be updated.

 

To update the firmware on the selected processor, select File / Config from the main window menu. This will pop up the configuration dialog.

 

 

 

Click the Update button next to the file type to be updated and browse to the copy of the relevant file downloaded and saved previously. Select the file from the open file dialog and click OK. The firmware download process will begin, with a confirmation filename dialog box as shown below. A this point the remote (destination) filename and location could be changed, however the default presented will be correct.

 

 

 

On selecting OK from Remote filename dialog the progress dialog will be presented as below.

 

 

 

The filenames for FPGA and System code will be updated when the new file is selected for download. When OK or Apply is clicked the new configuration will be set in the Brick-HD.

 

In order to run the downloaded firmware it is necessary to reset the processor.

 

The Brick-HD flash memory provides two volumes. One is a conventional directory and file based volume. Files are divided into data blocks in a similar manner to conventional disk based filing system. Deleted data blocks are marked as "dirty" when a file is deleted but can be recovered and reused automatically. It also incorporates a wear leveling mechansm to prevent one part of the device being worn out prematurely before the rest of the device. This filing system has to be mounted as part of the system start-up process. If for any reason this volume is not mounted, the list of filing system directories will not be shown.

 

The 2nd volume provided is called "Bootflash:". This is a much simpler filing system where the files are written to the flash device with a single data block. When a file is deleted the space is not immediately recoverable. This does not need to be mounted at start-up. It makes the process of copying data from the flash device to RAM much faster. Files in Bootflash: are rarely updated, usually only as part of a firmware update. There is space in the Bootflash: volume for a number of firmware updates. If Bootflash: eventually runs out of space it may be "squeezed" to recover the space occupied by deleted files. The sequence process will be invoked automatically by the PC software as part of the download process.

 

FPGA and system code to be used as part of the boot process (start-up) must be located in Bootflash:

 

If following a reset, the processor does not work it is possible to drop back to a special version of the code (the ROM Monitor) which allows the code to be re-installed. To force the processor to start the RMON, turn off the power, then power up with the front panel "Select/Push" knob pressed.

 

The RMON does not automatically mount the flash filing system or load the code into the FPGAs.

 

To change the code used from the Front Panel, once the RMON is running, rotate the Select/Push knob clockwise until "Press to configure" is displayed. Press to select the configuration menu. Rotate the  knob clockwise until the FPGA menu option is displayed - press the knob to select. Rotate the knob clockwise/anti-clockwise to view the FPGA file to use from the available list. Press to select a particular version. The configuration will be saved and the FPGA menu option will be re-displayed. Rotate the knob clockwise until Exit is displayed, then press the knob to leave configuration mode.

 

The system code file (.bin)  can be selected in a similar manner. In this case select Boot instead of FPGA and select one of the available .bin files in the list.

 

Once both have been set, reset the processor to use the new configuration.

 

Any file type can be downloaded to Bootflash: (or the conventional flash volume) using the download option from the Brick-HD Control software main menu.

 

Files are transferred to the Brick-HD using TFTP (Trivial File Transfer Protocol), therefore the TFTP server must be enabled. It is possible to transfer files to/from the processor using other TFTP clients, such as that provided with windows XP/Vista/7.

 


 Quick Start

 

 

The Brick-HD can be setup using the Front Panel VFD menu. Alternatively the Brick-HD Control software application supplied can be used with a Windows based PC to achieve same via more user friendly graphical interface. The Brick-HD Control application requires a connection to the Brick-HD. This can be either via a PC COM port or IP using the Brick-HD Ethernet port. A COM port is easier to set up. Also if the Brick-HD is initially connected via a serial port, the IP parameters for the Brick-HD can be set via it, simplifying the IP configuration process.

 

All Video input and control connections to the processor unit are at the front. Video output is via the DVI connectors at the rear.

 

 

Connecting the Brick HD using a PC COM Port

 

Connect the PC to the Brick-HD Host RS232 port using the cross-over cable supplied. If the PC does not have a built in COM port a USB adapter can be used instead. Install this before starting the Brick-HD Control software application.

 

Install the Brick-HD Control software and start the Brick-HD Control software application. From the File main menu, select Setup. Select the desired PC COM port from the pull down menu. Click OK.

 

The  PC should now be in communication with the Brick-HD processor. To configure the IP parameters select the "File/Config" menu option configure the parameters in the dialog box as described in the config section. Reset the processor. When the processor re-starts it will use the configured parameters. To use TCP/IP, from the "File/Setup" dialog, click the Remote TCP/IP button to connect via TCP/IP.

 

The Brick-HD can be controlled using just the serial interface, however an IP connection is required to transfer files to the Brick-HD. This is only necessary if the Brick-HD requires a firmware update, or downloaded sequences are used.

 

With the serial port connected it is also possible to access the Brick-HD shell using a terminal emulation program.

 

 

Connecting the Brick-HD using Ethernet only

 

In order to connect the Brick-HD via TCP/IP over the Ethernet port without first using a serial port requires some initial base IP configuration.

 

By default the Brick-HD will be configured to acquire an IP address using DHCP, so if the Brick-HD is connected to a Switch/Router that supports DHCP the Brick-HD can be connected immediately using a CAT5 cable and powered-up. The IP address assigned can be seen displayed on the VFD as part of the start-up process. Once the Brick-HD has started the IP address can be determined by rotating the front panel knob clockwise to the IP parameters page.

 

Alternatively DHCP can be disabled and an IP address, mask and default gateway set using the Front Panel VFD menu before connecting the Ethernet Cable.

 

If the Brick-HD is connected to a working Ethernet port that does not support DCHP it will take some time trying to acquire an IP address before the rest of the firmware starts up, so if you are not going to use DHCP it is better to disable it using the Front Panel VFD menu before connecting the Ethernet Port.

 

In order for the Brick-HD Control software application to communicate with the Brick-HD, the MTCP (Media Technologies Control Protocol) must be enabled on the Brick-HD. The TFTP service should also be enabled if file transfer to/from the Brick-HD required. The Brick-HD will be supplied with these enabled, however if the configuration is ever completely wiped, these will need to be re-enabled. This can be done using the Front Panel VFD menu.

 

To connect the PC Brick-HD Control software application, select "File/Setup" from the main menu. Click the Configure-IP button.  Fill in the IP address corresponding to the address assigned (via DHCP or by configuration via the VFD). The Port number must be set to 5000. The shared secret should initially be left blank. Click OK and then try and connect via TCP/IP to the Brick-HD by clicking on the Remote (TCP/IP) button. The connection should be established almost immediately. If successful the status bar will show TCP/IP in the botton left hand corner of the application window.  Leave the Set-up dialong and select the "File/Config" menu option. The remaining configuration parameters can now be configured. At this point a shared secret between the PC and Brick-HD can be set, so that next time a connection will be authenticated. 

 

If the connection fails - and an authentication failure message is shown in the Brick-HD Control software application status bar, then the Brick-HD has an old shared secret configured. This can be deleted using the Front Panel VFD. It is not possible to set the shared secret via the VFD, however once the connection is re-established a new shared secret can be set.

 

It is also possible at this stage to re-configure the IP parameters, for example to disable DHCP and use a static IP address. A static IP address is recommended since it is necessary for a client to know the IP address of the Brick-HD to connect. A DHCP server is not likely to always assign the same IP address to a device (unless explicitly configured to do so).

 

Once communication is established, the input and output connection type can be set using the Brick-HD Control software application and the monitor array aligned to correctly display magnified images.

 

 

Video Input Connection

 

There are four video input connections on the front panel. Current firmware supports only those supporting HD signals, i.e.

Either of these can be selected using the Brick-HD Control software supplied or the Front Panel VFD display as the source video signal.

 

The DVI input provides an EDID table. This is not available until the Brick-HD is up and running (unlike a typical monitor that uses a small interface powered serial ROM). The EDID table in the Brick-HD however is programmable and can be set to match the connected monitors. |A default table is provided which is likely to be suitable in most cases.

 

 

Video Output Connections

 

The Brick-HD has 16 output channels. The video output format can be set to either DVI or Component (YPrPb or RGB) using either the Brick-HD Control software supplied, terminal emulation to the Brick-HD shell, or via the Front Panel VFD menu. All channels operate in the same mode - it is not possible to mix output types.

 

The DVI output connectors provide both Analogue and Digital outputs. Analogue outputs can be broken out to RCA connectors using a commonly available passive DVI to RCA converter, or via a suitable cable.

 

The table below shows the default output channel mapping to monitor position in a 4x4 array.

 

Ch 1

 

Ch 2

Ch 3

Ch 4

 

Ch 5

 

Ch 6

Ch 7

Ch 8

 

Ch 9

 

Ch 10

Ch 11

Ch 12

 

Ch 13

 

Ch 14

Ch 15

Ch 16

The channel mapping can be changed in software if required.

 

The initial magnification and array alignment is set using the Alignment menu option from the Brick-HD Control software or from the Front Panel VFD menu. 

 

 

Host RS232 Connection

 

A PC can be connected to the Host RS232 connection to allow control of one or more Brick-HD processors. Multiple processors can be controlled via the same PC COM: port by daisy chaining the Loop port on one processor to the Host port of another.

 

The processor is configured via the PC software provided. Once configured it can be operated with other RS-232 capable control device such as Crestron and AMX systems or operated stand-alone.

 

The 9 Pin D connector pin-out is,

 

Host RS-232 connector (9 Pin D Male)

Pin

Signal

Type

1

None

 

2

RX

Input

3

TX

Output

4

+5V

Via 47R

5

Ground

-

6

Not used.

 

7

+5v

Via 47R

8

None

 

9

+5v

Fused +5v

Loop RS-232 connector (9 Pin D Male)

 

The cable connecting the PC COM port to the processor, and processor to processor is the same, 9 Pin D Female at either end. The cable is a cross over cable wired

Pin

Signal

Type

1

None

 

2

RX

Input

3

TX

Output

4

None

 

5

Ground

-

6 - 9

None

 

 

    2 ----- 3

    3 ----- 2

    5 ----- 5

For PCs without a standard COM port, a USB serial adapter can be used.

 

The RS-232 settings are as follows and for simplicity should not be changed.

Baud Rate19200
Bits per Character8
Parity None
 Stop Bits 

1

For advanced users who want to control the processor at the hardware level, it is necessary to use the frame based command protocol. This protocol is used to convey a set of messages comprising a function code and optional list of arguments. The supplied software provides a macro based sequencing control language to create and time the transmission of these messages.

 

For simpler applications, the processor can also accept single ASCII character commands mapped to complex sequences which can be downloaded to the processor Flash memory using the supplied software.

 

 

 


The following technical details are subject to change without notice.

 

Enclosure

19-inch 2U rack mounting or free standing (detachable brackets).
Size: 455 mm x 275 mm x 88 mm. Weight: 5 kg.

Videowall Array Formats  

Single processor supports up to 16 monitors.
Use multiple processors in parallel for larger video walls to 256 monitors and beyond.
Compatible with consumer LCD and Plasma TV panels, Projectors and PC Monitors.
Compensation for large monitor / bezel gaps.
Future software releases : Feather projector overlaps, Vertical Monitor Formats.

Video Resolution

SD, ED, HD and Graphics resolutions supported at pixel rates up to 80 MHz.
SD : 720 x 480/576 (PAL/NTSC/SECAM).
ED/HDTV : 525i, 625i, 525p, 625p, 720p/50-60, 1080i/50-60, 1080p/24-30
RGB Graphics Digital (DVI) : HDTV Modes, Graphics XGA (1024 × 768 @ 60 Hz).

Video Inputs

Video inputs switched by software, external command, or real-time sequence.
Analog Composite-video input (Phono/RCA Single-Jack).
Analog S-video input (4-pin Mini-DIN).
Analog Component input (RCA Triple-Jack).
Digital DVI-D input (HDCP not supported).

Video Outputs

Up to 16 monitors - use multiple Brick-HD processors to build larger video walls.
16x Analog outputs (via DVI connector):  Component, Composite-video, S-video.
16x DVI-D outputs.

Effects

Square and Anamorphic Magnifications scaling to any video wall array size.
24-bit colour washes different colours on each video wall monitor.

Future software releases: Download and display still images, and many other effects in development
with free software/hardware upgrades via our website.

Effects Control

IP Networking via Ethernet 10/100BaseT interface providing TFTP, TELNET and MTCP (Media Technologies Control Protocol)
RS232 Control / Daisy Chain and Brick-HD can control slave RS232 equipment.
Control software included in price with lifetime updates via our website.

Environmental monitoring and logging.
Manual configuration via 2x20 character display with rotary encoder menu selection.
Download configurations to processor for real time clock / external trigger activation.

Power

Internal 75W AC mains power unit.
IEC C14 Connector, Auto-switching 100VAC to 240VAC, 0.315A, 60/50 Hz.

Environment

Integral low noise fans with user changeable fan filter.
Storage: -40° to +158°F (-40° to +70°C) / 10% to 80%, non-condensing.
Operating: +41 to +95°F (+5 to +35°C) / 10% to 80%, non-condensing.

Warranty

Warranty: 1-years parts and labour.

 


 Further Information

 

For further information on the Brick-HD Videowall processor, online help and the latest software and firmware please visit www.mediat.co.uk or www.mediat.us

 

To report bugs with this software please visit http://www.mediat.co.uk/bugreports.htm

 

 


The information in this document is believed to be accurate in all respects at the time of printing, but is subject to change without notice. Media Technologies Ltd assumes no responsibility for any errors or omissions, and disclaims responsibility for any consequences resulting from the use of the information included herein. Additionally, Media Technologies Ltd assumes no responsibility for the functioning of features or parameters not described.


Help file version 1.5 [20-Feb-11] © Media Technologies Ltd.