Brick-HD Videowall Processor - Web Server
If enabled the Brick-HD provides a simple web server. The web pages are contained in the flash file directory /wwwroot. Images used by the webpage (.gif and .jpg) are stored in the directory /images.
The default index.html file is shown below. This provides a link to a help file and a sequence buttons page.
The Sequence Buttons page is a dynamically created page, an example of which is shown below. It makes use of some simple AJAX technology, so requires the browser to support javascript.
The buttons shown correspond to the binary sequence files saved in the Brick-HD /sequence directory. The contents of this directory in this case are:
#dir -l /sequence
08-Jul-10 11:46:04 48 BlackWash.SFB
08-Jul-10 11:46:01 47 BlueWash.SFB
08-Jul-10 11:45:58 48 GreenWash.SFB
08-Jul-10 11:45:55 46 RedWash.SFB
08-Jul-10 11:45:49 28 DispVideo.SFB
08-Jul-10 11:45:42 34 Y1in.SFB
08-Jul-10 11:45:34 30 DVIin.SFB
08-Jul-10 11:45:10 23 Split5.SFB
08-Jul-10 11:45:07 23 Split4.SFB
08-Jul-10 11:45:04 23 Split3.SFB
08-Jul-10 11:45:01 23 Split2.SFB
08-Jul-10 11:44:57 23 Split1.SFB
396 bytes in 12 files
These files are installed in this directory using the "Buttons" dialog described here.
Clicking on one of the buttons on the web page will run the associated sequence file.
In the current version of firmware the order of the buttons follows the random order that the files are listed in the directory.
The web pages make use of CGI type URLs to make requests to the Brick-HD web server to activate the sequence files associated with each button. The CGI URL commands are formatted as follows:
http://host/cgi-bin/buttons?(transaction)command[id]=argument
The (transaction) part is a random transaction number. This can be used to prevent certain browsers caching the request even though the HTTP header includes command to prevent local content caching.
The ID part is used to relate the acknowledgement with the request and is used in the sever response. The = delimiter is necessary but the argument is not used with all commands. Note the square brackets are used in practice, they do not indicate that the id is optional in this case.
For example, to run the sequence BlackWash.SFB
http://192.168.11.7/cgi-bin/buttons?(34023281)run[100]=BlackWash.SFB
The sever will respond with [100]Running:BlackWash.SFB
http://192.168.11.7/cgi-bin/buttons?run=BlackWash.SFB
In this case there is no id, so the response is [000]Running:BlackWash.SFB
To stop a currently running sequence
http://192.168.11.7/cgi-bin/buttons?(34023282)stop[200]=
The response will be [200]Stopped:None or [200]Stopped:BlackWash.SFB if BlackWash.SFB was running
http://192.168.11.7/cgi-bin/buttons?stop=
This is the same as the previous example, except the id will be 000 since none was provided in the request
To skip a pending wait command in a running sequence
http://192.168.11.7/cgi-bin/buttons?(34023283)skip[201]=
http://192.168.11.7/cgi-bin/buttons?skip=
The response format is the same as the stop case, except the skip command word is used.
Web pages can be created as the Brick-HD itself does dynamically using javascript and the XMLHttpRequest object to embed these transactions in the web page - or used in other programming environments such as a perl scripts.
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.
Web Server Help file version 1.0 [19-Dec-10] © Media Technologies Ltd.