new: The corresponding chapters are new or completely revised.
corr.: Passages of the corresponding chapter were corrected; see modification bars.
add.: Passages of the corresponding chapter were added; see modification bars.
This manual refers to following hardware and software configurations of A
Release X ServerR3.48
RGUS X Terminal:
Document history
Modifications, which result in a new version, are indicated by a vertical bar.
Brand and product names mentioned in this manual may be trademarks, registered trademarks or copyrights of
their respective holders. All brand and product names mentioned in this manual serve as comments or examples
and are not to be understood as advertising for the products or their manufacturers.
Die Weitergabe sowie die Vervielfältigung aller Unterlagen, die von uns überlassen werden, deren Verwertung
und Mitteilung ihres Inhaltes an Dritte ist nicht gestattet, soweit dies nicht ausdrücklich zugestanden ist.
Urheberrechte, insbesondere auch solche an Software, werden nur insoweit übertragen, als es für die Erreichung
des speziellen Vertragszwecks erforderlich ist. Zuwiderhandlungen können zu Schadensersatz verpflichten. Alle
Rechte aus der Erteilung eines Patents oder der Eintragung eines Gebrauchsmusters verbleiben bei uns.
All rights reserved. No part of this document may be copied, reproduced or translated. It shall not otherwise be
recorded, transmitted or stored in a retrieval system without the prior written consent of Barco.
Guarantee and compensation
Barco provides a guarantee relating to perfect manufacturing as part of the legally stipulated terms of guarantee.
On receipt, the purchaser must immediately inspect all delivered goods for damage incurred during transport, as
well as for material and manufacturing faults. Barco must be informed immediately in writing of any complaints.
The period of guarantee begins on the date of transfer of risks, in the case of special systems and software on
the date of commissioning, at the latest 30 days after the transfer of risks. In the event of justified notice of
complaint, Barco can repair the fault or provide a replacement at its own discretion within an appropriate period.
If this measure proves to be impossible or unsuccessful, the purchaser can demand a reduction in the purchase
price or cancellation of the contract (redhibition). All other claims, in particular those relating to compensation for
direct or indirect damage, and also damage attributed to the operation of software as well as to other services
provided by Barco, being a component of the system or independent services, will be deemed invalid provided
the damage is not proven to be attributed to the absence of properties guaranteed in writing or due to the intent
or gross negligence on the part of Barco.
If the purchaser or a third party carries out modifications or repairs on good delivered by Barco, or if the goods
are handled incorrectly, in particular if the systems are commissioned or operated incorrectly or if, after the
transfer of risks, the goods are subject to influences not agreed upon in the contract, all guarantee claims of the
purchaser will be rendered invalid. Not included in the guarantee coverage are system failures which are attributed to programs or special electronic circuitry provided by the purchaser, e. g. interfaces. Normal wear as well
as normal maintenance are not subject to the guarantee provided by Barco either.
The environmental conditions as well as the servicing and maintenance regulations specified in this manual must
be complied with by the customer.
1.1 How this manual is organized .....................................................................................................................1-2
1.2 Styles and symbols.......................................................................................................................................1-3
1.3.2 Unpacking of devices...........................................................................................................................1-6
3.1.2 Argus OmniBus ....................................................................................................................................3-6
3.2.1 Power supply .......................................................................................................................................3-9
3.2.13 CPU board.........................................................................................................................................3-25
3.2.14 Argus OmniBus ................................................................................................................................3-27
3.2.15 Arrangement of expansion cards....................................................................................................3-29
3.3 Starting up ..................................................................................................................................................3-35
3.3.2 Switching on ......................................................................................................................................3-36
3.4.1 System configuration.........................................................................................................................3-38
4.2 Color management.......................................................................................................................................4-3
4.2.2 Color capabilities of Argus...................................................................................................................4-5
4.3 X Display manager .......................................................................................................................................4-7
4.4 X Server extensions......................................................................................................................................4-8
4.6 Displaying video and RGB signals..............................................................................................................4-12
4.6.1 The input cards ..................................................................................................................................4-13
4.6.2 The video channels............................................................................................................................4-16
4.6.3 The Xvideo client ...............................................................................................................................4-17
4.6.4 Displaying video and RGB signals.....................................................................................................4-19
4.6.5 The options ........................................................................................................................................4-28
4.6.6 The resource files...............................................................................................................................4-33
4.7 Remote-Control for OverView display walls .............................................................................................4-39
4.7.1 The Remote-Control daemon............................................................................................................4-40
4.7.2 The Remote-Control clients (command line based) ........................................................................4-41
4.7.3 The GUI Remote-Control client..........................................................................................................4-47
4.8.1 Show wallinfo utility..........................................................................................................................4-52
6.1.5 X server parameters ............................................................................................................................6-8
6.1.8 Nearby color allocation......................................................................................................................6-17
6.1.9 BIOS settings for Wake On LAN.........................................................................................................6-18
7.3 Order codes.................................................................................................................................................7-16
8.1 Argus not booting.........................................................................................................................................8-2
8.2 Argus does not boot from CD.......................................................................................................................8-3
8.3 Hot line .........................................................................................................................................................8-4
This chapter explains the structure of the manual itself and the used typographic styles and symbols. Safety information is provided concerning the operation of computer systems from Barco.
This manual describes design and startup of ARGUS from Barco. It is divided into nine chapters:
•Introduction
explains the structure of the manual itself and the used typographic styles and symbols. Safety information is
provided concerning the operation of computer systems from Barco.
•Summary
gives an overview about the features of A
• Getting Started
describes the set up of A
RGUS and provides you with a guide through the software configuration. If your ARGUS
is already configured within your working place you can skip this chapter and continue with chapter 4
Operating.
• Operating
shows the capabilities which A
RGUS offers displaying graphics and video. You are introduced into operating
the X video client for displaying video and RGB signals and the R
VIEW display wall.
• Maintenance
describes the maintenance of A
RGUS.
RGUS.
EMOTE-CONTROL client for controlling an OVER-
•Advanced Configuration
may provide useful information for reconfiguring the software of your A
RGUS.
•Technical Appendix
gives tabular overviews about the technical details of A
RGUS, its components and of their interfaces.
•Troubleshooting
gives advice, if your A
RGUS does not operate properly.
• Index
lists the keywords of the manual.
Chapters, pages, figures and tables are numbered separately. Chapters are indicated by a »point syntax«, e. g.
4.2.3, pages by a »dash syntax«, e. g. 2-1, as figures and tables are, e. g. figure 5-4.
This section describes safety precautions, which must be observed when installing and operating a product from
Barco.
1.3.1 Precautions
For your own protection, observe the following safety precautions when installing,
operating and servicing your device:
• Before operating the units please read this manual thoroughly and retain it for future reference!
• Observe all warnings and instructions printed on the devices!
• Servicing not explicitly mentioned in this manual should never be carried out by unauthorized personnel!
Never open the case of the unit without first disconnecting the power supply cord!
• To prevent fire or electrical shock hazard, do not expose this unit to rain or moisture!
• This product should be operated from an AC power source!
• Check that the voltage and frequency of your power supply match those printed on the device label with the
rated electrical values!
• If you are not sure of the type of AC power available, consult your dealer or local power company!
• This product is equipped with a 3-wire grounding plug, a plug having a third (grounding) pin. This plug will
only fit into a grounding-type power outlet. This is a safety feature. If you are unable to insert the plug into
the outlet, contact your electrician to replace your obsolete outlet. Do not defeat the purpose of the grounding-type plug!
• This equipment must be grounded (earthen) via the supplied 3 conductor AC power cable. (If the supplied
power cable is not the correct on, consult your dealer.)
Mains lead (AC power cord) with CEE 7 plug:
The wires of the mains lead are colored in accordance with the following code:
yellow + green Earth (Ground)
blue Neutral
brown Line (Life)
The wires of the power cord are colored in accordance with the following code.
1. Introduction
yellow + green Earth (Ground)
white Neutral
black Line ( Life)
Figure 1-2
ANSI 73.11 plug
• Do not allow anything to rest on the power cord. Do not locate this product where people will walk on the
cord. To disconnect the cord, pull it out by the plug. Never pull the cord itself.
• If an extension cord is used with this product, make sure that the total of the ampere ratings on the products
plugged into the extension cord does not exceed the extension cord ampere rating.
• Never push objects of any kind into this product through cabinet slots as they may touch dangerous voltage
points or short out parts that could result in a risk of fire or electrical shock.
• Never spill liquid of any kind on the product. Should any liquid or solid object fall into the cabinet, unplug the
set and have it checked by qualified service personnel before resuming operations.
• Lightning - For extra protection for this video product during a lightning storm or when it is lift unattended
and unused for a long period of time, unplug it from the wall outlet. This will prevent damage to the unit
due to lightning and AC power-line surges.
Due to high touch current, the Argus OmniBus is intended to be used in a location having
equipotential bonding:
• The building installation shall provide a means for connection to protective earth.
• The equipment is to be connected to that means.
• A service person shall check whether or not the socket outlet from which the equipment is to be powered
provides a connection to the building protective earth. If not, the service person shall arrange for the installation of a protective earthing conductor from the separate protective earthing terminal to the protective earth
wire in the building.
• Do not place this unit on an unstable cart, stand, or table. The unit may fall, causing serious damage to it.
• Do not use this unit near water.
• Use only the power cord supplied with your unit. While appearing to be similar, other power cords have not
been safety tested at the factory and may not be used to power the unit. For a replacement power cord,
contact your dealer.
• Slots and openings in the cabinet and the sides are provided for ventilation; to ensure reliable operation of
the unit and to protect it from overheating, these openings must not be blocked or covered. The openings
should never be blocked by placing the product on a bed, sofa, rug, or other similar surface. This product
should never be placed near or over a radiator or heat register. This unit should not be placed in a built-in installation or enclosure unless proper ventilation is provided.
• The maximum recommended ambient temperature for this equipment is 40° C.
• When using the unit in a multi-unit rack assembly or closed assembly the ambient temperature inside the
assembly may not succeed the maximum rated ambient temperature.
• When installed in a rack, the installation should be such that the amount of air flow required for safe opera-
tion of the equipment is not compromised. The mounting of the equipment should be such that no hazardous
condition is achieved due to uneven mechanical loading.
1.3.4 Servicing
Mechanical or electrical modifications others than described in this manual must not be made to the devices.
Barco is not liable for damages resulting from modified devices.
Only authorized personnel should carry out other maintenance work not explicitly
mentioned in this installation manual!
Never open the case of Argus
Measurements and tests with the opened device may be carried out only in the factory or
by specially trained personnel, due to the dangers of electrical shock.
without first disconnecting all power supply cords!
1.3.5 Cleaning
Unplug this product from the wall outlet before cleaning. Do not use liquid cleaners or aerosol cleaners. See section 5.1 Cleaning for a cleaning instruction!
1.3.6 Re-packing
Keep the original shipping carton and packing material; they will come in handy if you ever have to ship your
unit. For maximum protection, repack your set as it was originally packed at the factory.
On the documentation CD OVT-2686-7 this manual DOC-3265-2 can also be found in electronic form. Insert the
CD in the CD ROM drive to view the manual. If autorun is enabled on the computer the start page of the CD
comes up automatically.
On a Linux computer you might first need to mount the CD by using the following command
mount /dev/cdrom /mnt/cdrom
and then to open the start page index.html of the CD manually.
On this start page you will find a link to the user's manual of Argus X Terminal.
Acrobat Reader can be used to view the file. Adobe® Acrobat® Reader is free and freely distributable software
that lets you view and print Adobe Portable Document Format (PDF) files.
If Acrobat Reader is already installed, the manual can be viewed just by a click on the respective link. Else the
Acrobat Reader must be installed first. The required installation files can also be found on the CD.
ARGUS was designed to control large, modular OVERVIEW display walls. Its multi-screen capability allows you to
control displays of virtually unlimited size. The display area is one logically connected display. Digital imaging
devices based on modern technologies such as Single LCD, DLP and Poly-Silicon LCD with the highest display
quality are controlled digitally. Digital data transfer is immune to electromagnetic interference and therefore
ensures the display wall picture to be displayed in absolutely distortion free image quality.
™
CRT monitors and analog projectors can also be controlled by A
RGUS,using the analog output mode of the graphic
cards. Thus, multi-monitor operator stations can be ergonomically designed and easily implemented.
(DLP is a trademark of Texas Instruments Incorporated)
The hardware and software of A
RGUS is based on world-wide accepted standards. ARGUS offers the following ex-
ceptional capabilities:
• High performance graphics output using the most modern processor and chip technologies
• Supports current LAN and WAN interfaces
• Graphic and video outputs in high color quality
• Video in a window, up and down scaleable up to full-screen
• Overlapping and freely moveable video and graphics windows of unlimited size
• Up to 64 videos on one to four projection modules.
The A
RGUS system provides a flexible and scalable architecture, which is suitable to support all sizes of display
walls. Just one A
RGUS PROCESSOR and one to five ARGUS OMNIBUS devices can be used to set up a monolithic system.
Or for more complex configurations a distributed system can be used consisting of a central processor and multiple rendering engines to control a display wall of any size and number of input sources.
Independent of the usage of a monolithic system or a distributed system, both the user and the application software ‘see’ one single display. Installation, operation and service do not differ from that of a standard X terminal.
A
RGUS offers the possibility to operate it in normal boot mode or in eXtended safety boot mode. Normal boot
mode offers full write access to the hard disk and enables the operation of the wall management software O
SIRIS.
eXtended safety boot mode offers in addition to normal boot mode a backup partition for improved system
safety. With eXtended safety boot mode the system files are stored safely, and faultless startup is guaranteed
even after unpredictable events, e.g. power failure.
RGUS is the perfect solution for the integration of video and RGB sources into desktop graphic data into digitally
A
controlled display walls. However graphics only systems support also analog display connection.
The case of the ARGUS PROCESSOR is available in two models: The standard case and the case for redundant power
supply and RAID (Redundant Array of Independent Disks).
The front
RGUS PROCESSOR standard:
A
3
RESET
KB/LK
H.D.D.
POWER
74
9
10a
1
18
12
RGUS PROCESSOR with redundancy options:
A
1
12
35411
13
1 air supply
3 restart button
4 lock keyboard switch
5 buzzer reset button: power module failed
6 LED: power module failed
7 LED: hard disk access
8 LED: power on
9 floppy disk drive
10a/b hard disk drive / RAID subsystem
11 CD ROM drive
12 (reserved)
13 power button
On the left side there are the air supply openings [1]. In the center of the standard case there are three buttons.
The upper one is the restart button [3], the one in the middle is the lock keyboard switch [4], that serves to
enable or disable keyboard input and the lower one is the power button [13]. The two LEDs next to the switches
indicate hard disk drive operating [7] respectively power on [8].
The case for redundant operation additionally has a buzzer reset button for power module failure [5], which is
located on the top leftmost position. The restart button [3] is located between the lock keyboard switch [4]
and the power button [13] instead. On the front there is also an additional LED, indicating power module failure [6].
On the right hand side there is the floppy disk drive [9], followed by the CD ROM drive [11] and below it the hard
disk drive [10a] or [10b].
The RAID hard disk drive system [10b] is available for RAID 1 (as shown in Figure 3-1 front view of Argus Processor) or
for RAID 5, please see the figure below.
RAID 5 hard disk drivers
Figure 3-2
Each RAID 5 hard disk provides three LED’s at the front of the removable frame. If the red LED lightens, this indicates that this particular hard disk has failed and should be replaced.
Please note for RAID 5 systems:
Never remove more than one hard disk while the system is running. Otherwise the system
will crash and not be able to restore!
A hard disk is already switched off by turning the frame lock key!
Never change the sequential order of the hard disks. Otherwise the complete data on the
drives will get corrupt and not be able to restore!
The rendering processors of the distributed system are assembled accordingly. They are
delivered without CD-ROM drive and hard disk drive.
14 air supply
15 genlock loop through in (optional)
16 remote power on/off connector / genlock loop through out
17 external genlock in (optional)
18 (reserved)
19-24 network cards, link interface card and other PCI cards
25 mains connection
26 PS/2 mouse (green jack)
27 PS/2 keyboard (purple jack)
28 USB3, USB4 (if position 33 is not available USB1, USB2)
29 COM1
30 LPT1
31 onboard VGA adapter (models AGS-3328-2/3) or
COM2 (models AGS-3328-0/1 and AGS-3270-0)
32 onboard LAN adapter
from model AGS-3328-2 on with the following LED signals:
left LED lightens green a connection exists
blinking green activity
right LED off 10 Mbps connection
lightens green 100 Mbps connection
lightens yellow 1000 Mbps connection
35 power switch of individual power module
36 LED: individual power module operating
rear view of A
Figure3-3
RGUS PROCESSOR
On the left hand side is the mains connection [25]. At the case of the ARGUS PROCESSOR for redundant operation
there is for both of the two power modules a mains connection [25] and additionally a power switch [35] and
an LED [36], indicating operation of the power module, if lightened. In the middle of the power modules there is
the air supply [14].
The remote power on/off connector [16] is for connection to A
RGUS OMNIBUS devices.With the optional connec-
tors external genlock in [17] and external genlock loop through in [15] an external genlock signal can be
connected to multiple P
ROCESSORS and OMNIBUS devices. PS/2 mouse [26] is for plugging in a PS/2 mouse and
PS/2 keyboard [27] is for plugging in a PS/2 keyboard. If available with network adapter [32] the network
connection can be established.
On the right hand side there are different cards [19-24] inserted depending on the actual hardware configuration
of your A
RGUS PROCESSOR.
To protect A
RGUS PROCESSOR from overheating, the air supply openings in the case shall be
kept free of obstructions!
To disconnect A
RGUS PROCESSOR from the power supply all power cords have to be pulled of
the mains connection [25]. Therefore the back panel has to be easily accessible!
The expansion slots
The A
RGUS PROCESSOR provides six PCI expansion slots for insertion of link interface cards, network cards, VGA
graphic card and Multiport I/O Cards. Depending on the model of the P
ROCESSOR, the numbering varies. In the
models AGS-3328-2 and AGS-3328-3 they are numbered in the following way:
PCI 1PCI 2PCI 3PCI 4PCI 5PCI 6
numbering of PCI slots on the back panel of A
RGUS PROCESSOR AGS-3328-2/3
In the models AGS-3270-0, AGS-3328-0 and AGS-3328-1 they are numbered in the following way:
numbering of PCI slots on the back panel of A
RGUS PROCESSOR AGS-3270, AGS-3328-0/1
In the following sections reference is taken to the numbering of the slots.
Each ARGUS OMNIBUS provides eighteen PCI expansion slots. They can be used for Barco's UGX or AGX GRAPHIC CARDS,
MNISCALERS,QUAD ANALOG VIDEO CARDS, STREAMING VIDEO CARDS and DUAL RGBINPUT CARDS.
O
Although the backplane of the Argus OmniBus is based on standard 64bit/66MHz PCI bus it
is highly recommended to not insert other cards than those mentioned above.
Other cards will not work due to the missing driver support and there is also a risk to
damage the OmniBus or the inserted cards.
The front view of OMNIBUS:
423
2 Ventilation flap with air supply
3 LED: operating status off power switch [26] on the back switched off
red power switch [26] switched on, system in stand-by
green
power switch [26] switched on, OMNIBUS is started, ei-
ther by the On/Off push button [4] or via the remote
power cable by the ARGUS PROCESSOR.All power modules
that are currently in the OMNIBUS are working well.
red blinking One of the redundant, hot-plug power modules failed.
4 Push button On/Off
Front of the A
Figure 3-6
RGUS OMNIBUS
On the front of the ARGUS OMNIBUS at the bottom to the right there is the On/Off push button [4]. Next to it
there is an LED [3], showing the operating status of the O
MNIBUS.
In an OmniBus with redundant power supply the LED [3] is also lightened green, if one of
the two power modules is removed but the remaining power module is working well.
It is not an indicator that redundancy is available!
5 CPU board
6 link interface card
7-13 graphic cards
14-20 OMNISCALER
21-24 input cards
25 air supply
26a, 26b power switch (a standard power module, b optional redundant power module)
27a, 27b mains connection (a standard power module, b optional redundant power module)
28 connection for equipotential bonding conductor
back of A
27a
Figure 3-7
RGUS OMNIBUS
On the upper part of the back of the OMNIBUS there are different cards. On the left there is the CPU board [5] and
the link interface board [6], followed by graphic cards, O
configuration of A
RGUS.
MNISCALERS and input cards [7-24] depending on the
On the right of the lower part is the standard mains connection [27a] and the power switch [26a]. On the left
side there might be another mains connection [27b] and the power switch [26b] for a second power module
for redundant operation, depending on the configuration of the A
RGUS. To the left of the standard mains connec-
tion there might be a connection for the equipotential bondig conductor [28].
To protect the O
MNIBUS from overheating, the air supply openings in the case shall be kept
free of obstructions!
To disconnect the O
MNIBUS from the power supply all power cords have to be pulled of the
mains connection [27a] and [27b]. Therefore the back panel has to be easily accessible!
Check the power rating on your outlet before connecting A
power strip. Contact your facilities manager or a qualified electrician if you are not sure
what type of power is supplied to your building.
A
RGUS is designed to operate with single-phase power systems having a grounded neutral
conductor. To reduce the risk of electrical shock, do not plug into any other type of power
system.
To connect PROCESSOR and the OMNIBUS devices to the power supply, follow these steps:
• If using an OMNIBUS with redundant power supply first connect an equipotential bondig conductor to the
connector [28].
• Plug the female end of the power cords into the mains connections of each PROCESSOR [25] and OMNIBUS [27]
respectively.
RGUS to the wall outlet or to a
Mains connection of A
Figure 3-9
RGUS
• Plug the male end of each power cord into a power outlet.
3.2.2 Mouse
The standard mouse is a PS/2 mechanical mouse. Plug it into the PS/2 mouse jack [26].
Figure 3-10
PS/2 mouse jack
3.2.3 Keyboard
The standard keyboard is a MF-II type keyboard with a PS/2 connector. Plug it into the PS/2 keyboard jack [27].
The keyboard extension allows a distant positioning of keyboard and mouse. The figure below shows schematically the parts and the cabling of the keyboard extension.
The keyboard extension is made up of two extension boxes (remote extension box REX [3], local extension box LEX [5]) and two connection cables (connection cable 20m [4], PC cable [6]). Keyboard and mouse are
plugged into the remote extension box instead of being plugged directly into the Pextension box is connected to the local extension box with the connection cable 20m.
The local extension box is connected to the PS/2 keyboard and PS/2 mouse port of the PROCESSOR with the PC cable, which has on the one end a single plug, but on the other end two plugs.
The two interface boxes are prepared for grounding. On each side labeled EXT there is a thread for fixing a ring
connector size 3.
The DDC capable UGX and AGXGRAPHIC CARDS provide the facility for connecting CRT monitors or projectors (analog
mode) or for connecting Barco projection modules (digital mode) to an A
board they can easily be switched between analog and digital mode.
For ARGUS systems with digital output and video or RGB insertions the output of the graphic cards is led over to
MNISCALERS and then connected to the display device. Please refer to section 3.2.6 OmniScaler.
O
UGX Graphic Card
RGUS. By means of a rotary switch on the
The UGX
GRAPHIC CARD provides two Dual-DVI connectors to connect four display devices. For digital output, resolu-
tions up to UXGA can be processed.
AGX Graphic Card
The AGX
GRAPHIC CARD provides one Dual-DVI connector to connect two display devices. For digital output, resolu-
Depending on the configuration the card is delivered with different adapter cables:
• Dual-DVI to 2xDVI-D adapter cable:
Digital output for display on projection modules with digital input.
• Dual-DVI to 2xCRT adapter cable:
Analog output for display on projection modules with analog input.
3. Getting started
Figure 3-15
Dual-DVI to 2xDVI-D adapter cable
The DDC capable display devices must be connected to the graphic cards before Argus is
switched on. If they are connected afterwards Argus will not be able to detect them!
The first graphic card in respect to PCI slot numbering identifies itself as primary graphic adapter by lighting the
green LED of the respective graphic channel when ARGUS is switched on. The primary graphic adapter is the channel, where the system emits diagnostic and status messages during system startup.
For the explicit order of the graphic cards, please refer to the sections 3.2.14 Argus OmniBus and 3.2.15 Arrangement
of expansion cards.
AGX and UGX
GRAPHIC CARDS may not be mixed within the same system!
Each UGX
GRAPHIC CARD provides four ports for connecting projection cubes, monitors or projectors. The upper con-
nector contains port 0 and 1, the lower one contains port 2 and 3. Thus the default sequence of the graphic
channels is:
board 1 2 3
port 0
1
2
3
0
1
2
3
0
1
2
3
channel 1 2 3 4 5 6 7 8 9 10 11 12
Figure 3-17
Each AGXGRAPHIC CARD provides two ports, the upper one is port 0, the lower one port 1. Thus the default sequence of the graphic channels is:
board 1 2 3 4 5
port 0
1
0
1
0
1
0
1
0
1
channel 1 2 3 4 5 6 7 8 9 10
Figure 3-18
For non default sequence see section 6.1.6 Advanced Argus configuration.
The BAROC projection modules are assigned from left to right (view from in front of the screens) or if arranged in
a square numbered in rows starting at the top left:
1
234
5678
Numbering of projection channels
Figure 3-19
This numbering is carried on for distributed systems. For each rendering machine the
modules are numbered as described.
Specifications
For detailed technical specifications of the graphic cards please refer to section 7.1 Technical data.
For configuring a distributed system, the graphical output of the central device must be
displayed somewhere. Therefore a VGA monitor can be connected either to the VGA-Card of
the central processor or if available to the onboard VGA adapter of the central processor,
please refer to section 3.1.1 Argus Processor.
In addition to graphic cards, also OMNISCALERS are a substantial part of ARGUS to connect to projection modules. The
MNISCALERS provide the ability to integrate video and RGB data into the graphical data from the graphic cards.
O
Therefore the out connector of the graphic card needs to be connected to the in connector of the O
Only graphic cards in digital mode can be connected. DDC information from the projection device is looped
through to the graphic card for further processing.
The O
MNISCALER exists in two versions. OMNISCALERAGX-3313 is a replacement for the OMNISCALERAGX-3002.
Within one system both types of O
MNISCALERS can be used, provided that the requirements given in the table
AGX-3002 SXGA R 3.0 and higher
AGX-3313 UXGA R 3.3 and higher
Compatibility matrix of O
Connectors
The O
MNISCALER provides one Dual-DVI connector for data insertion from the graphic card and one Dual-DVI con-
nector for digital output for two projection modules.
MNISCALER.
Table 3-1
MNISCALER versions
ports of the O
Figure 3-21
MNISCALER
In every OMNISCALER card package a Dual-DVI to Dual-DVI cable is included. It serves to connect port 0/1 in of the
MNISCALER with port 0/1 or port 2/3 of the graphic card:
O
Dual-DVI to Dual-DVI adapter cable
Figure 3-22
For the connection to the projection modules the Dual-DVI to 2×DVI-D adapter cable that was provided with the
graphic card is used. It must be plugged into port 0/1 out of the O
The QUAD ANALOG VIDEO CARD, provides the capability of displaying video signals like VCR, TV, CCTV etc. The analog
video signals are digitized for further processing in the O
ously.
Standard
The video standards S-Video (S-VHS, Y/C) and Composite Video (VHS, FBAS, CVBS, CVS, Y) are supported.
Connectors
UAD ANALOG VIDEO CARD provides one LFH-160 pin connector for video insertion. In every QUAD ANALOG VIDEO
The Q
CARD package a video breakout cable is included. The breakout cable itself provides eight BNC connectors that can
be used to connect four S-Video or composite signals. The eight cables are marked with CVBS/Y 1 to 4 or with
C 1 to 4 respectively, please refer to section 7.2 Interfaces for appropriate signal connection.
MNIBUS. Four video signals can be processed simultane-
connector of the QUAD ANALOG VIDEO CARD (left) and video breakout cable (right)
Order
Within a single Q
UAD ANALOG VIDEO CARD the numbering of the video channels is as shown in the figure above. The
order in that the input cards are inserted into one or more O
and 3.2.15 Arrangement of expansion cards.
Specifications
For detailed technical specifications of the Q
UAD ANALOG VIDEO CARD please refer to section 7.1 Technical data.
Figure 3-23
MNIBUS devices is given in section 3.2.14 Argus OmniBus
The STREAMING VIDEO CARD provides the capability of displaying compressed encoded digital video streams. The
digital signal is decoded for further processing in the O
taneously. The S
TREAMING VIDEO CARD allows a redundant connection to the Ethernet.
Standard
TREAMING VIDEO CARD supports MPEG-2 streams over Ethernet. Please refer also to section 7.1 Technical data.
The S
Connectors
The S
TREAMING VIDEO CARD provides two RJ45 connectors to establish the connection to the network. For a redun-
dant connection a network cable should be plugged into each of the plugs [1] and [2]. These network cables
should connect on the other side to a redundant network. In case of a failure of one connection the other connection will take over the complete network traffic. If a redundant connection is not required either plug [1] or
plug [2] can be used for the connection. Both plugs use the same IP and MAC address, so no configuration in
regard of the used plug is required.
MNIBUS. Up to four video streams can be processed simul-
3
1
5
4
2
6
7
8
9
10
1 RJ45 Network connector 1
2 RJ45 Network connector 2
3 green LED: connector 1 connected to the Ethernet
4 green LED: connector 2 connected to the Ethernet
5 green LED: ON connector 1 connected with 100 Mbps
OFF connector 1 connected with 10 Mbps
6 green LED: ON connector 2 connected with 100 Mbps
OFF connector 2 connected with 10 Mbps
7 stream 1 is active
8 stream 2 is active
9 stream 3 is active
10 stream 4 is active
Order
The order in that the input cards are inserted into one or more O
OmniBus and 3.2.15 Arrangement of expansion cards.
Specifications
For detailed technical specifications of the S
TREAMING VIDEO CARD please refer to section 7.1 Technical data.
The DUAL RGBINPUT CARD provides the capability of displaying RGB monitor signals. Either two analog signals up to
1280×1024@75Hz or one analog signal up to UXGA resolution or higher are digitized for further processing in
RGUS.
A
Standard
The synchronization modes Hsync+Vsync, Csync and Sync-on-Green are supported.
Connectors
The D
UAL RGBINPUT CARD has two VGA compatible 15-pin SubMinD connectors. Each is for connecting one RGB
signal to the O
able.
MNIBUS. If an UXGA signal is inserted it must be connected to RGB In 1, while RGB In 2 is not avail-
RGB In 1
RGB In 2
Order
Within a single D
UAL RGBINPUT CARD the numbering of the video channels is as shown in the figure above. The
order in that the input cards are inserted into one or more O
and 3.2.15 Arrangement of expansion cards.
Specifications
For detailed technical specifications of the D
UAL RGBINPUT CARD please refer to section 7.1 Technical data.
connector of D
MNIBUS devices is given in section 3.2.14 Argus OmniBus
The Multiport I/O Card extends the system with additional serial connectors. They might be helpful for controlling
multiple devices through the control room management software O
Connectors
The Multiport I/O Card has two serial sockets.
SIRIS.
1 1st serial port
2 2nd serial port
Order
The Multiport I/O Card is inserted in an PCI slot of the A
used in an A
RGUS PROCESSOR.
Inserting a Multiport I/O Card in an Argus OmniBus is not supported!
Multiport
I/O Card
PCI 1PCI 2PCI 3PCI 4PCI 5PCI 6
Figure 3-26
Multiport I/O Card
RGUS PROCESSOR. Up to three Multiport I/O Cards can be
With ARGUS the following network adapters are available: The onboard LAN adapter on the mainboard, the
Ethernet Card 100 Mbps as well as the Ethernet Card 1000 Mbps. These adapters are used to connect the ARGUS
PROCESSOR to the LAN (local area network) and to connect central device and rendering machines to the sub-net.
The onboard LAN adapter and the Ethernet Card 1000 Mbps have the ability to establish a 10 Mbps, 100 Mbps or
1000 Mbps connection. The Ethernet Card 100 Mbps has the ability to establish a 10 Mbps or 100 Mbps connection.
The sub-net connection is established via a Gigabit Ethernet Switch, see section 3.2.12 Distributed system.
Redundant network connection
For a redundant connection to the LAN the Ethernet Card 100 Mbps as well as the Ethernet Card 1000 Mbps are
also available as server adapters, allowing to configure them in teaming mode, sharing one single IP-address. On
the label on the card is indicated whether a network card is of server or desktop type. Please refer also to section
6.1.7 Redundant network adapter for more information.
Models
For the different applications the network cards are delivered in different models.
In a distributed system the rendering machines are booted via the sub-net by means of packets
sent by the central device. Therefore the network adapter in the rendering machines must be capable to boot via a network. For the A
this. It depends on the hardware that is used in your A
ods is used.
Former systems used special rendering Ethernet cards that carry Etherboot code which requests the
needed boot packets as soon as the central device is booted. With A
from X server release 3.48 on no special rendering Ethernet cards are needed any longer (anyhow
the usage of these cards remains supported). Instead PXE (the Pre-eXecution Environment) is used.
For reliable function of this mechanism it is necessary that wake on LAN (WOL) is configured in the
server configuration (see section 3.4.3 Configuring a distributed system) and that WOL is also enabled in
the BIOS of the mainboard of the respective rendering machines (see section 6.1.9 BIOS settings for
Wake On LAN)
•To connect an Argus Processor machine to the sub-net
Ethernet Card 100 Mbps
Ethernet Card 1000 Mbps
• To connect an Argus rendering machine to the sub-net using PXE
The onboard LAN adapter, the 100 Mbps and the 1000 Mbps network card offer each a Twisted Pair connection:
DATA
ACT/LNK
10=OFF
100=GRN
1000=YLW
DATA
ACT/LNK
100 TX
Figure 3-28
Connecting to Twisted Pair (RJ-45)
100 Mbps onboard LAN adapter (left), 100 Mbps Ethernet Card (middle) and 1000 Mbps Ethernet Card (right)
Order
The network cards are inserted in sequence into the PCI slots of the A
RGUS PROCESSOR with the highest numbers. If
more than one network card is built-in, they are numbered in ascending order for descending PCI slot numbers.
The Ethernet addresses are labeled on the network cards.
LAN
LA
Eth 2
Eth 1
If using different types of network cards, this type determines the order as well. The system
detects first the onboard LAN adapter, then 100 Mbps network cards in the order of the PCI
slots and finally the 1000 Mbps network cards. Therefore to get a straight numbering of the
cards the 1000 Mbps network cards should be inserted in the PCI slots with the higher
numbers than the 100 Mbps network cards.
Inserting a network card in an Argus OmniBus is not supported!
With the distributed system multiple rendering machines are used, each one consisting of a rendering processor
and one or two O
RGUS sub-net.
A
With the distributed system, each rendering machine operates a rectangular array of projection modules within a
display wall. The actual subdivision into arrays depends on the requirements of each display wall (e. g. displaying
video). The following figure shows an example for a 10×5 arrangement:
MNIBUS devices. Each rendering processor is connected to the central processor by means of the
A
RGUS
A
RGUS
A
RGUS
A
RGUS
A
RGUS
A
RGUS
Example for the assignment of rendering machines and O
MNIBUS devices to projection modules
Figure 3-30
Additional information about the assignment of rendering machines and OmniBus devices to
projection modules can be found in section 6.1.6 Advanced Argus configuration.
The rendering machines are connected to the central processor within a separate sub-net (see also section 3.2.11
Network). Therefore the central processor is equipped with an additional network card. If also for the LAN connec-
tion an extra network card is used and not the onboard LAN adapter, then the network card with the lower
Ethernet address, respectively the higher PCI slot number connects to the LAN, the card with the higher Ethernet
address, respectively the lower PCI slot number connects to the sub-net.
Sub-net
PCI 1 PCI 2 PCI 3 PCI 4 PCI 5 PCI 6
PCI 1 PCI 2 PCI 3 PCI 4 PCI 5 PCI 6
Example for network cards in the central processor: LAN connection via onboard LAN adapter (left) and via a network card (right)
LANSub-net
Figure 3-31
To connect the rendering processors to the sub-net either the onboard LAN adapters are used or the rendering
processors are equipped with one network card each:
The Sub-net is established via a Gigabit Ethernet Switch. The Gigabit Ethernet Switch connects the rendering
processors and the central processor. Up to 7 rendering processors and the central processor can be connected
with one Gigabit Ethernet Switch.
The CPU board controls amongst other the remote power on/off mechanism between the OMNIBUS devices and
its host and the transmission of a genlock signal.
Connectors
On the CPU board there are two RJ-45 connectors for connecting the remote power on/off cables.
Do not remove the sheet metal plate. The connector behind is reserved for diagnostic
purposes.
connectors of CPU board
Figure 3-33
Connecting order remote power on/off
Each A
RGUS OMNIBUS should be connected to its host for the remote power on/off mechanism. Therefore the
remote power on/off connector [16] on the back of the host (A
connected with the remote power on/off in connector of the CPU board of the O
RGUS PROCESSOR or rendering processor) must be
MNIBUS. Multiple OMNIBUS de-
vices are connected in a daisy chain to their host by connecting the remote power on/off out connector of the
MNIBUS to the remote power on/off in connector of the next OMNIBUS and so on. The remote power
first O
on/off out connector of the last O
MNIBUS remains unconnected.
cabling for remote power on/off
Figure 3-34
Do not mix up the connetors for remote power on/off with the mechanically identical
connectors of the network adapters!
Mixing the connectores will cause damage to the system.
MNIBUS devices that are locked to the same source must be connected to each other by means of
the remote power on/off cabling.
Therefore in a distributed system an additional connection is necessary; the remote power on/off connector
[16] on the back of the central processor must be connected with external genlock loop through in connector
[15] on the back of the first rendering processor.
The remote power on/off out connector of the last OMNIBUS
must be connected to the external genlock loop through in connector [15] on the back of the next rendering
processor.
If multiple A
last O
central processor of the next A
RGUS systems shall be locked to the same source, the remote power on/off out connector of the
MNIBUS must be connected to the external genlock loop through in connector [15] on the back of the
RGUS system.
If an external source is used for genlocking it must be connected to the external genlock in connector [17] on
the back of the ARGUS PROCESSOR.
An example of cabling for an external genlock source is given in the figure below:
external
genlock
Rendering 1
Rendering 2
A
RGUS
Central Processor
System 1
A
RGUS
Central Processor
System 2
Rendering 1
Rendering 2
cabling for remote power on/off and external genlock
ROCESSOR and OMNIBUS is established with a link interface cable. It connects the
respective link interface card in the host [19-24] with the link interface card in the O
cable or a flat ribbon cable is used:
round cable (left) or flat ribbon cable (right) for connection of host and O
The cable between host and O
MNIBUS is fragile. It may not last under tension, or being bent
or twisted.
MNIBUS [6]. Either a round
Figure 3-36
MNIBUS
Connecting several OmniBus devices
In the A
vices can be connected to one A
RGUS PROCESSOR there are five PCI slots for link interface cards available. Therefore five ARGUS OMNIBUS de-
RGUS PROCESSOR. Each OMNIBUS is connected in the manner explained above.
Order
The link interface cards are inserted in the PCI slots of the A
slots with the lower numbers. If more than one A
RGUS OMNIBUS is connected, they are numbered in the sequence
of the PCI slots.
Link
Inter-
face
1
PCI 1 PCI 2
Link
Link
Inter-
Inter-
face
face
3
2
PCI 3PCI 4PCI 5PCI 6
Link interface cards in host to connect to multiple O
The Processor expects the primary graphic adapter in the first Argus OmniBus. Therefore the
OmniBus that is connected to the link interface 1 must be equipped with graphic cards.
The graphic cards are numbered consecutively with ascending PCI slots. Each O
to the graphic card it is connected to. The Q
are numbered commonly with ascending PCI slots. The O
ascending order of their respective PCI slots in the P
UAD ANALOG VIDEO CARDS,STREAMING VIDEO CARDS and DUAL RGBINPUT CARDS
MNIBUS devices themselves are taken into account in
ROCESSOR or in a distributed system in the order of the render-
There are various ways how Barco’s expansion cards can be arranged in the PCI slots of the ARGUS OMNIBUS devices. The most important rules are listed below:
• A graphic card with digital output transmits the data to an OMNISCALER for additional video and RGB integra-
tion, or if no video or RGB sources are displayed it transmits data directly to the display wall. A graphic card
with analog output displays data always without O
MNISCALER by means of the external Dual-DVI to Dual-DVI cable.
an O
• Data fed to the system through QUAD ANALOG VIDEO CARD, STREAMING VIDEO CARD and DUAL RGBINPUT CARD can only
be displayed on the projection modules that are connected to the O
inserted.
• Cards of the same type are inserted in consecutive order, but not all cards of one type must be in the same
MNIBUS.
O
• The order of the different types of expansion cards in the PCI slots of one OMNIBUS is first graphic cards then
MNISCALERS and finally input cards.
O
• If not all slots are used for plugging in expansion cards, then these empty slots should be located between
graphic cards and O
MNISCALERS.
• Graphic cards can be placed in different OMNIBUS devices than OMNISCALERS and the input cards belonging to
them.
MNISCALER. Data is transmitted between a graphic card and
MNIBUS devices, in which these cards are
• If no graphic cards are used in an OMNIBUS, then the OMNISCALERS are inserted in the PCI slots with the lowest
numbers at the very left.
• In a distributed system, it is necessary that the display wall is built of rectangular arrays. That means the
output to the wall of each O
MNIBUS that provides data for the display wall must feed a rectangular array.
• In the rendering machine of a distributed system either one or two OMNIBUS devices can be connected to the
rendering processor. If using one O
vices one is for graphic cards, the other for O
MNIBUS all kind of boards may be inserted into it. If using two OMNIBUS de-
MNISCALER and input cards.
• Also other restrictions may apply. If in doubt contact your authorized service personnel.
Examples of some significant configurations
The examples below cover different kind of configurations to point up the rules given above. The following abbreviations are used:
• G: graphic card
• O: OMNISCALER
• I: input card, i.e. QUAD ANALOG VIDEO CARD, STREAMING VIDEO CARD or DUAL RGBINPUT CARD
The schematic drawings of the O
arranged, only the 18 free available PCI slots of an O
MNIBUS devices show always the view on the back of a device. To keep it clearly
MNIBUS are plotted. The display wall is shown from the front!
Below a sketch of a four-channel system with digital output and 4/2 free movable and scalable video/RGB windows using one OMNIBUS in a monolithic system:
video1
I16/0
video2
I16/1
GOIIO
PCI
P
ROCESSOR
video3
I16/2
video4
I16/3
video5
I17/0
video6
I17/1
13121711161015914876543210
O
MNIBUS
1
Figure 3-39
small system configuration
In our example a monolithic system is used, i.e. an OMNIBUS is directly connected to the ARGUS PROCESSOR. In the
MNIBUS the empty slots are arranged between graphic cards and OMNISCALERS. Input cards follow the OMNISCALERS,
The following system has 54 channels, digital output and 60 video windows that are movable and scalable
within their respective display area. To get video windows that are free movable on the whole display wall a
distributed system would be required instead.
One PROCESSOR that connects to four OMNIBUS devices controls the wall. OMNIBUS 1 is solely filled with graphic cards
and does therefore not directly provide data for the wall. O
MNIBUS 2, 3 and 4 contain the OMNISCALERS and input
cards (and some further graphic cards) and provide the final display data for the projection modules. The video
output of each O
MNIBUS can be displayed on its respective display area but can not be moved into another display
The following system has 72 channels, digital output and a configuration that enables either 20 free movable
video windows or 60 video windows that are movable and scalable within their respective display area. Here
four free movable windows and 48 windows that are limited to their display area are shown.
Three rendering machines are used each consisting out of two OMNIBUS devices (one for graphic cards and one for
MNISCALER and input cards) and one rendering processor that connects to the subnet. On the wall there are three
O
logical display areas, each belongs to one rendering machine.
There are different possibilities to display the video windows. On the one hand a video can be displayed using
multiple input channels one from each rendering machine to form one logical video channel. Such a video window can be displayed freely movable and scalable on the whole wall regardless of the different display areas. In
our example 20 such video channels could be built.
On the other hand, 60 videos could be displayed, each 20 restricted to one display area but within these boundaries freely movable and scalable.
Also combinations between these both ways to display video are possible. In the example above each rendering
machine provides 16 videos that are restricted to their display area (input card 12, 13, 14 and 15) and together
they are able to display 4 further videos movable over the whole display wall (input card 16). Please refer also
to section 4.6.2 The video channels.
To build larger display walls, simply connect further rendering machines to the sub-net. By this virtually unlimited display walls can be set up, all being configured in the way explained in the example above.
Below is an example of a system with 36 channels and digital output. Only a limited number of projection modules need to display video.
dispaly area
OOOOOO
GGGGGGGGG
MNIBUS
2dispaly area
OI I IOI
13121711161015914876543210
13121711161015914876543210
MNIBUS
1
O
MNIBUS
2
MNIBUS
1
O
PCI
P
ROCESSOR
system configuration with digital output and partial usage of O
Figure 3-43
MNISCALERs
Therefore two OMNIBUS devices in a monolithic system are used. OMNIBUS 1 is used for graphic cards. The output
of the graphic cards 4-8 is directly displayed on the projection modules on the right side of the display wall (display area O
video integration. The output of the O
O
MNIBUS 2). On this area 16 video windows can be displayed and freely scaled and moved. If a video window is
moved to the display of O
MNIBUS 1). The output of the graphic cards 0-3 is provided to the OMNISCALERS in the OMNIBUS 2 for
MNISCALERS is displayed on the left part of the display wall (display area
MNIBUS 1, the video can no longer be displayed. Instead the window background ap-
First of all you have to provide the appropriate power supply. Plug in the power cables on the back panel of the
RGUS devices. Please, refer to section 3.2.1 Power supply!
A
Mouse and keyboard must be connected to the respective sockets on the rear of the P
ROCESSOR respectively the
central processor. Please, refer to sections 3.2.2 Mouse and 3.2.3 Keyboard!
Connect the link interface and remote power on/off cables to the ARGUS devices. If an external genlock signal is
used connect it also to the A
Connect the graphic cards to the O
cards or O
MNISCALERS. At least one display must be connected for administrating ARGUS. Please, refer to 3.2.5
Graphic cards and 3.2.6 OmniScaler. Connect the video and RGB sources to the video-input cards of A
RGUS. Please refer to 3.2.13 CPU board and 3.2.14 Argus OmniBus!
MNISCALERS, if OMNISCALERS are used. Connect the display devices to the graphic
RGUS. Please,
refer to section 3.2.7 Quad Analog Video Card, 3.2.8 Streaming Video Card and 3.2.9 Dual RGB Input Card!
Connect the ARGUS PROCESSORto the local area network by connecting the network to the network card or the
network onboard adapter! Please, refer to section 3.2.11 Network!
For configuring a distributed system, the central device must be connected to a monitor.
Refer to section 3.2.5 Graphic cards, please! Connect the rendering machines with the central
processor and the O
Distributed system, please!
MNIBUS devices with the rendering processors. Refer to section 3.2.12
First make sure that the power switches [26] of all connected OMNIBUS devices are on. The LED operating status
[3] on each O
RGUS PROCESSOR and rendering processors are switched on. Then switch on the ARGUS PROCESSOR and the ren-
the A
dering processors by pressing the power button [13] on the front of each device! By means of the remote
power on/off mechanism each O
status of each O
MNIBUS should show a red light. Check also that the power switches [35] (if available) on the rear of
MNIBUS is switched on and initialized in the necessary order. The LED operating
MNIBUS should show a green light.
If the remote power on/off mechanism is not used, each O
MNIBUS must be switched on first by means of the
push button on/off [4] on the front. If the LED of each of it turns green, the respective host can be switched on
as well.
The order in which the central processor and the rendering processors are switched on is of
no importance.
There are two possible boot modes for ARGUS.Normal boot mode and eXtended safety boot mode. See section
6.1.1 Boot modes. The operation of A
RGUS differs a little, depending on this mode.
Normal boot mode
The displays show their respective bus and slot no., e. g.:
PCI Bus: 2, PORT: 1
After a few minutes the graphical user interface X.11 appears.
eXtended safety boot mode
The displays show their respective bus and slot no., e. g.:
PCI Bus: 2, PORT: 1
The ARGUS startup screen comes up. Select linux to boot from the working partition.
If you select backup, the restore procedure is started and the working partition becomes
overwritten with the backup system, which might lead to a loss of current data, depending
on the state of the backup, please see section 4.8.5 Backup and restore procedures (eosxs Utility)!
Argus startup screen
Figure 3-44
After a few minutes the graphical user interface X.11 appears.
Configuration
If software configuration has already been carried out you can go on with chapter 4 Operating. Otherwise proceed
configuring A
To switch off ARGUS save your work, remove any disk or CD from the drives and exit from any application. Terminate the X-Server, log on as root and enter
rebooting.
eos:/root # shutdown –h now
When ARGUS has shut down it switches off automatically.
shutdown –h now for shutting down or shutdown –r now for
To avoid any complications, it is recommended to switch off A
above!
The order in which you switch off central processor and rendering machines is insignificant.
RGUS is switched off as explained above, not all parts are disconnected from the power
If A
supply. To disconnect the whole device the power plug has to be pulled out after switching
off.
ARGUS comes to you with installed and pre-configured software. Nevertheless before you put ARGUS into opera-
tion, you have to run through a system configuration to insert the properties of your network like the IP address
and the keyboard type. Furthermore an X.11 configuration is needed to adjust A
3.4.1 System configuration
The following section describes how to change or insert the network configuration, keyboard properties, user
properties or passwords.
To change the configuration log in as root and start the configuration utility. The factory set password for root is
barco:
eos login: root
Password: barco
Enter linuxconf.
eos:/root #linuxconf
Navigate within the configuration window by using the Tab key and the arrow keys. A + in front of a folder significates the folder is open, a – significates the folder is closed. Select the folder by putting the focus on it (Arrow up key and Arrow down key) and confirming with the Enter key to change it’s state An arrow after a word sig-
nalizes that there is a list hidden. Open the list by putting the focus on the word and pressing
the focus on a list item to select it and confirm.
RGUS to your local conditions.
<Ctrl> X. Put
There are also help files available. Each window contains a Help button. The Help button of the main window
offers general help. The Help buttons of the sub windows offer help, concerning the content of the sub window.
Select Config : Networking : Client Tasks : Host name and IP network devices.
3. Getting started
Figure 3-45
Up to four network cards are automatically detected during the system installation. This means the settings for
net device and kernel module are correct if the cards have been present during installation. If a card is inserted
afterwards also these settings have to be adopted. The drivers (Setting: Kernel module) for the different network cards are:
driver network card redundancy
eepro100 Ethernetcard 100 Mbps, PCI no
e100 Ethernetcard 100 Mbps, PCI possible
e1000 Ethernetcard 1000 Mbps, PCI possible
e1000 onboard LAN adapter (AGS-3328-2 and higher) no
bcm4400 onboard LAN adapter (AGS-3328-1 and lower) no
The section Adaptor 1 treats the network options of the LAN connection of ARGUS.You can change them by selecting and editing them. If you are putting A
RGUS into operation you have to change the pre-adjusted IP address
to your own.
Figure 3-46
Take care to insert the same sub net IP address within the configuration for a distributed
system as explained in section 3.4.3 Configuring a distributed system.
The section Adaptor 2 treats the network options of the subnet, used with the distributed
system.
For the sub-net network card of the central unit, IP addresses must be specified.
Use the IP addresses
192.168.60.254 for the central processor.This enables the numbering of the rendering machines
Select
consequently with
the field Primary name + domain insert
192.168.60.xxx as long as it will not collide with any other subnet within the Internet.
1, 2, 3, etc. Clarify the corresponding Netmask addresses with your network administrator. In
eos-core.
Figure 3-47
Confirm your changes with Accept or leave with Cancel.
Select Control : Features. The Features tab opens. Here is the keyboard map that provides the different keyboard
types. You have also the possibility to choose the language in which the dialogs are held. Hit Accept when finished.
Time (optional)
RGUS is just used as X-terminal, it does no date & time related processing.
If A
Select Control : Date&Time. Adjust A
RGUS to your time and confirm with Accept.
User accounts (optional)
As A
RGUS comes preconfigured with user <mmt> and password <mmt> usually defining an additional user account
is not required.
Select Config : Users accounts : Normal : User accounts. This will open the Users accounts tab.
If you have more than 15 accounts on the system, Linuxconf will provide you with a filter screen. You can use
this to select a smaller range of accounts than the full list. To get the full list, select Accept without changing any
of the parameters.
Select Add. This will open the User account creation tab.
The User account creation tab is where you enter all the information on the new account. It has a number of
fields; only the login name is required, though filling in the Full name field is strongly recommended. Once you
have entered the login name and any other desired information select the Accept button. If you decide against
creating a new user, hit Cancel instead.
Upon hitting Accept the configuration program will prompt you to enter the password. There is also a field called
Confirmation where you will need to type the password again. Passwords must be at least 6 characters in
length. They may contain numbers as well as a mix of lowercase and uppercase letters. Hit Accept when finished.
Changing a user’s password (optional)
Select Config : Users accounts – Normal – User accounts. This will open the Users accounts window. Select the
account whose password you wish to change. This will open the User information window. Select Passwd from
the options at the bottom of the screen.
The configuration software will then prompt you to enter the new password. There is also a field called
Confirmation where you will need to type the password again. This is to prevent you from mistyping the password. Passwords must be at least 6 characters in length. They may contain numbers as well as a mix of lowercase and uppercase letters. If you decide against changing the password, just hit Cancel. Once you have entered
the new password select Accept.
You have to reboot A
If you operate A
partition after successful configuration, see section 4.8.5 Backup and restore procedures (eosxs
Utility).
RGUS to make changes become effective.
RGUS in eXtended safety boot mode, please take care to update the backup
For the X.11 configuration of ARGUS the script call must be entered in line mode. Therefore leave X.11 for configuration purposes with the following keys pressed simultaneously:
<Ctrl> <Alt> <Backspace>
Now, back in line mode log in as root! The factory set password for root is barco:
eos login: root
Password: barco
Configuration can be carried out by means of the configuration script EOSconfig. To start this script change the
directory first:
eos:/root # cd /opt/MMT2686/config/
then execute the script:
eos:/opt/MMT2686/config # ./EOSconfig
EOSconfig will guide you through the configuration. You can exit configuration without saving the modifications
at any time by pressing simultaneously:
<Ctrl> C
Thus all parameters entered up to now were deleted again. It is more convenient however to check all data necessary for configuration first and then start the script. Therefore you are recommended to read through the following pages of this section before starting the configuration.
Below you can read through a typical course of the configuration script expanded with comments giving more
details.
*********************************************************
* *
* Eos X Server Configuration *
* Release 3.4.x *
* (c)2005 BARCO *
* *
* email : support.bcd@barco.com *
* Tel : 0049-721-6201-0 *
* Fax : 0049-721-6201-298 *
* *
*********************************************************
1 Config Eos Multi-Screen X Server
2 Config Eos Distributed X Server
3 Config Visu Plus Standalone X Server
4 Config Eos Multiple Logical Screens X Server
5 Exit
Enter your X Server Configuration [1]: 1
Customized Configuration (yes/no)? [no]: no
The value indicated in square brackets will be taken by simply pressing <Return>. This can be the default value
if the configuration script is running the first time or the value entered during the last configuration.
The first question allows you to choose between the configuration of a monolithic ARGUS [1], a distributed system
2], an X server for VISU
[
logical screens[
4]. Entering [5] exits the script.
PLUS
standalone [3] (this is not part of this manual) or an ARGUS configuration with multiple
Configuring a distributed system is largely similar to configuring a monolithic A
section configuration of a monolithic A
RGUS is demonstrated, but this part is identical for
RGUS. In this
both kind of configuration. See section 3.4.3 Configuring a distributed system for the additional
parts.
The second question allows you to choose between a complete and a custom configuration, see section 6.1.4
Custom configuration.
Mouse device
You can connect different types of mice. Please enter the type of mouse you want to use and specify its properties! If you have a PS/2 mouse you must select:
• 8. PS/2 MicrosoftIntelliMouse and compatible Wheel Mice or
• 12. No Mouse with OSIRIS where ARGUS is operated without local mouse.
Configuring the Monolithical X Server
=====================================
Settings for the Input Devices
==============================
Please enter the required settings for
- Mouse
- Cursor size
Configuring the Mouse Device
–-------------------------First specify a mouse protocol type. Choose one from the following list:
1. Microsoft Mouse and compatible 2-buttons Mice
2. Mouse Systems 3-buttons Mice
3. MM Series
4. Logitech Mouse (old type, Logitech protocol)
5. Logitech MouseMan (Microsoft compatible)
6. MM HitTablet
7. PS/2 Microsoft Mouse and compatible Mice
8. PS/2 Microsoft IntelliMouse and compatible Wheel Mice
Do you want to use the USB device (yes/no)? [no]: no
X11 big mouse cursor
In particular for big display walls, it can be useful to enlarge the mouse pointer. Indicate the desired magnification factor:
Configuring the Big Mouse Cursor
-------------------------------When using the X Server with high resolution
the standard cursors are hard to track for some people.
Therefore you can define magnified mouse cursors.
Following magnification factors are available:
factor 1 : standard cursors
factor 2..8 : magnified cursors
Enter the magnification factor [1]: 2
These are your Input Device settings
====================================
- Cursor size: Factor 2
- Mouse Protocol: "ImPS/2 "
- Mouse device: PS/2: "/dev/psaux"
Everything correct? (yes/no)? [yes]: y
Settings for the Output Devices
===============================
Please enter the required settings for
- Graphic Card Types (AGX-3000 or AGX-3281)
- Output Signal (analog or digital)
- Monitor Resolution (only for analog devices)
- Refresh Rate
- Screen Type (Multi Head or Multi Screen; only monolithic Server)
If you have analog output the monitor resolution and the refresh rate has to be specified. In case of analog and
digital mixed output just the refresh rate for the analog outputs is to be specified.
X Server General Settings
=========================
Please enter the required settings for
- Visual Depth
- Visual Class
- X Server's background RGB values
- XDM
- Font Server
Depth resolution
Specifying the depth resolution tells X.11 how many colors you want to use.
Configuring the Depth resolution (Bit Per Pixel)
(N,B: 4 and 5 are Usable only for resolution up to 1400x1050)
1 - for 8 bpp (256 colors)
2 - for 16 bpp (64K colors)
3 - for 32 bpp (16M colors)
4 - for 8 and 16 bpp (MultiDepth/MultiColor: Default visual = PseudoColor
5 - for 16 and 8 bpp (MultiDepth/MultiColor: Default visual = TrueColor)
Enter the depth resolution [2]: 4
Dependent on the configuration and the requirements for video the depth resolution must be selected. An extensive overview about correlation between settings of X.11 and the display of video as well as an explanation
of multi-color-depth is given in section 4.2.2 Color capabilities of Argus. An overview about bandwidth requirements
of video and RGB in dependence of color depth is given in section 4.6.1 The input cards.
Visual class
Specifying a visual class tells X.11 how to handle colors. This is only asked if you selected above the numbers
4. Refer also to section 4.2 Color management for a more detailed description, please!
The background of the X server can be set. Specify, if you want to set your individual background color and how.
In RGB values red is 255 0 0, green is 0 255 0 and blue is 0 0 255. You can choose any combination of these
colors within the range of 0 to 255.
Configuring the X Server's background
-----------------------------------Do you want set the X-Server's background color (yes/no)? [yes]: yes
Enter the RGB values [range 0..255] [0 0 0]: 40 40 200
X display manager
The X display manager,
xdm, is a system process which manages a user session from the login to the logout.
xdm provides a flexible and configurable method for logging in with an X server. Refer to section 4.3 X Display
manager for a more detailed description, please!
Entering
y allows you to specify the query type, entering n causes X.11 to start without xdm.
• query will connect you directly to the specified XDM;
• indirect will cause a chooser box to be opened, where you can select your XDM;
• broadcast will connect you to the XDM that replies first to your request.
Configuring X Display Manager (XDM)
----------------------------------The local X Display Manager can be used to login on the Eos X Terminal.
Do you want start the X Server with XDMCP (yes/no)? [yes]: y
Set the XDMCP Query Types
1 - query (direct)
2 - indirect
3 - broadcast
Enter query type [2]: 2
Enter the ip address of your XDM [150.158.181.149]: 199.123.222.17
Font server
Please specify, if you want to use a font server. If necessary clarify the IP address as well as the respective port
number with your network administrator!
Configuring the Font Server
--------------------------If you want a Font Server which supplies fonts for the X Server,
please answer the following question with either 'y' or 'n'
Do you want to use a Font Server (yes/no)? [yes]: y
Enter the ip address of your Font Server [150.158.181.149]: 199.123.222.17
Enter the Font Server's port number [7100]: 7100
The script lists your settings. Examine the values and confirm them by entering y or enter n for repeating the
previous configuration steps.
These are your X Server General Settings
========================================
For some installations it is useful to change the order of the projection channels. This can be assigned in the
Channel Reordering section. If you want to reorder the projection channels enter y. By entering n this section will
be skipped.
X Server's Channel Reordering
=============================
This is the reordering configuration part of the X Server.
It offers the possibility to define the reordering channels section.
The channels section defines the assignment of graphic channels
to projection channels.
Please read the section "X Server Configuration" in the
User's Manual "Eos X Terminal"
Do you want to proceed (yes/no)? [no]: y
The correlation between graphic channels and projection channels is explained in section 6.1.6 Advanced Argus
configuration (channels). Please have a look there to have a further explanation.
Channel Reordering
==================
Assign to a default graphic channel
a new position in the Display Wall
Channel Reordering:
-----------------1: redefine reordering
2: take default (no reordering)
Enter selection [1]: 1
Enter the list of the default channels [1 2]: 1 2 3 4 5 6 7 8
Enter the list of the new channels [2 1]: 1 3 5 7 2 4 6 8
These are the Reordering Settings for the Monolithic X Server:
=============================================================
1 2 3 4 5 6 7 8 --> 1 3 5 7 2 4 6 8
None of these ports and daemons is disabled. Changes in the configuration
of these ports and daemons by the user, will not be changed by the X.11
configuration.
Setting the Eos FireWall Policies
=================================
If you want to configure the Eos as secure
X Terminal, choose the policy "high"
then only X11-Connection are permitted
You have chosen the FireWall Policy "Medium"
Is this correct? (yes/no)? [yes]:y
Finishing the configuration
3. Getting started
If you do install a single A
ing a distributed system
RGUS, configuration is done and the script is finished with the next step. When configur-
you have to specify the data for the central device and the rendering machines. See
section 3.4.3 Configuring a distributed system.
***********************************************************************
* *
* The EOS-X configuration is finished now, please enter your choice *
* *
***********************************************************************
1 Exit configuration (all your current entries will be lost)
2 Finish configuration
Enter your X Server Configuration [2]:2
The EOS-X System will be configured now. Please wait ...
Configuring a distributed system is largely similar to configuring a monolithic system. See
section 3.4.2 X.11 configuration for the basic course of the installation script. This section
describes the additional part for configuring a distributed system.
On the one hand, the additional sections in the configuration of a distributed system contain the specification of
the sub-net and on the other hand, the successive parameterization of every individual rendering machine.
Sub-net
Indicate the transmission rate of the sub-net network card and the desired interface type!
The IP address of the sub-net network card of the central device must be specified identical to the IP address
specified with linuxconf. See section 3.4.1 System configuration.
Configuring Distributed X-Server's Subnet
==========================================
You want to install the Distributed Server therefore
additional configuring values are needed:
You have to insert the sub-net specification according to the specifications explained in
section 3.4.1 System configuration. Changes have to be made in a consistent way in both places.
Enter IP Address for the subnet NIC card[192.168.149.254]: 192.168.60.0
Enter Sub Netmask of graphic engines [255.255.255.0]: 255.255.255.0
Rendering machines
The parameterization of the rendering machines is carried out successively for every device. For every rendering
machine, the arrangement of the Barcoprojection modules is indicated in the following form:
<w>x<h>
Here <w> and <h> give the number of columns and rows. For example:
4x2
4 monitors next to each other, 2 monitors on top of each other.
For every rendering machine, the position of the projection modules, that is the position of the upper left module
is indicated, in the following form:
<x>,<y>
Here <x> and <y> give the horizontal and vertical position within the display wall starting with the upper left
module as
0,0.
0,04,0
4×24×2
Figure3-48
For each rendering machine a unique IP address within the specified sub-net must be provided. In addition the
Ethernet addresses of the rendering machines’ network cards must be entered. The Ethernet address is printed
on a label on the network card. For example:
EA=00.60.97.78.29.0a
As well the Ethernet address can be read from the output during the boot process.
Enter number of graphic engines [2]: 2
IP address for engine 1 [192.168.149.1]: 192.168.60.1
Ethernet address for engine 1 [00.00.00.00.00.00]: 00.60.08.a6.a9.58
Screen arrangement for engine 1 (Width x Height) [2x4]: 4x2
Position for engine 1 (X,Y) [0,0]: 0,0
IP address for engine 2 [192.168.149.2]: 192.168.60.2
Ethernet address for engine 2 [00.00.00.00.00.00]: 00.60.08.a6.a9.73
Screen arrangement for engine 2 (Width x Height) [2x4]: 4x2
Position for engine 2 (X,Y) [0,0]: 4,0
Next there is the choice to enable Wake On LAN for the network adapters of the rendering machines. From Release 3.48 of the X server on PXE can be used to boot the rendering machines. In this case Wake On LAN must be
activated, to enable the rendering machines to boot and reboot reliable. If still the Etherboot mechanism is used
Wake On LAN can also be activated but there is no need to do so.
Please refer to section 3.2.11 Network for a short explanation of Etherboot and PXE boot mechanism and in case
you activate WOL check also for the appropriate BIOS settings, see section 6.1.9 BIOS settings for Wake On LAN.
Engine's boot mode Configuration
-------------------------------The Engines can be switched on by the Core Machine
by using the WOL (Wake On LAN) facility.
(NB: When using WOL you have to enable WOL
also in the motherboard BIOS)
Do you want to use WOL (yes/no)? [no]: yes
The script lists your settings. Examine the values and confirm them by entering y, or enter n for repeating the
previous installation steps.
These are your Distributed Server settings
==========================================
- Core machine's second IP: 192.168.149.254
- Engines Netmask Address: 255.255.255.0
- NIC card: 100 Mbit
- Number engines : 2
- Values for engine 1: IP = 192.168.149.1 Ether = 00.60.08.a6.a9.58
arrangement = 4x2 position = 0,0
- Values for engine 2: IP = 192.168.149.2 Ether = 00.60.08.a6.a9.73
arrangement = 4x2 position = 0,0
- WakeOnLAN : Yes
Everything correct? (yes/no)? [yes]: y
Channel reordering
For some installations it is useful to change the order of the projection channels. This can be assigned in the
Channel Reordering section. If you want to reorder the projection channels enter y. By entering n this section will
be skipped.
X Server's Channel Reordering
=============================
This is the reordering configuration part of the X Server.
It offers the possibility to define the reordering channels section.
The channels section defines the assignment of graphic channels
to projection channels.
Please read the section "X Server Configuration" in the
User's Manual "Eos X Terminal"
Do you want to proceed (yes/no)? [no]: y
The order can be changed only within the rendering machines (graphic engines). First the engine has to be indicated then the graphic channels (default) and the projection channels (new) can be entered. The correlation
between graphic channels and projection channels is explained in section 6.1.6 Advanced Argus configuration
(channels). Please have a look there to have a further explanation.
Channel Reordering for the Distributed X Server
===============================================
Assign to a default graphic channel within a
graphic engine a new position in the
Display Wall
Enter graphic engine's number for reordering[1]: 1
Channel Reordering:
-----------------1: redefine reordering
2: take default (no reordering)
Enter selection [1]: 1
Enter the list of the default channels [1 2]: 1 2 3 4
Enter the list of the new channels [2 1]: 1 2 4 3
Reordering of a new engine? (yes/no)? [no]: y
Enter graphic engine's number for reordering[2]: 2
Channel Reordering:
-----------------1: redefine reordering
2: take default (no reordering)
Enter selection [1]: 1
Enter the list of the default channels [1 2]: 1 2 3 4
Enter the list of the new channels [2 1]: 4 3 2 1
Reordering of a new engine? (yes/no)? [no]: n
These are the Reordering Settings for the Distributed X Server:
===============================================================
engine_1 :1 2 3 4 --> 1 2 4 3
engine_2 :1 2 3 4 --> 4 3 2 1
Everything correct? (yes/no)? [yes]: y
3. Getting started
Logic video channels
The assignment of the adapters of Q
UAD ANALOG VIDEO CARDS or STREAMING VIDEO CARDS to »logic« video channels can
be defined. This assignment is explained in detail in section 6.1.6 Advanced Argus configuration (video). The numbers
of the assigned channels result like described there and have to be inserted into the lines of the respective rendering machines (
Logical Video Channels
======================
This is the configuration part for the assignment of Phisical Video Adapters
to Logical Video Channels.
This assignment specifies which video is displayed on which part of
the Display wall.
Please read the section "X Server Configuration" in the
User's Manual "Eos X Terminal"
Do you want to proceed (yes/no)? [no]: y
Logical Video Channels:
--------------------------1: define Video settings
2: take default Video settings
Enter selection [1]: 1
Enter for each video channel the video adapters for engine-1 [1]: 1 2 0
Enter for each video channel the video adapters for engine-2 [1]: 0 1 2
These are the Logical Video settings for the Distributed X Server:
==================================================================
engine_1 : 1 2 0
engine_2 : 0 1 2
3.4.4 Configuring a distributed system with multiple logical screens
Configuring a distributed system with multiple logical screens is largely similar to
configuring a distributed system without multiple logical screens. See section 3.4.2 X.11
configuration for the basic course of the installation script. This section describes the
additional part for configuring multiple logical screens.
More information concerning multiple logical screens can be found in the sections 4.1 Multi-screen capability and
6.1.6 Advanced Argus configuration. The configuration runs mostly along the X.11 configuration and the configuration
of a distributed system.
Mode of multiple logical screens
Select the multiple logical screens mode. If you select separate mode you are also prompted to indicate whether
you want cursor wrap or not (Please see the keyword
configuration).
Configuring the Multiple Logical Screen X Server
================================================
There are two modes of MLS operation
1 - Contiguous mode
2 - Separate mode
Please enter the MLS mode [1]:
Switching on the cursor wrap around feature (yes/no)? [no]: no
NoCursorWrap in section 6.1.6 Advanced Argus
Subnet and rendering machines
Next the Sub-net and the rendering machines are configured. Please see section 3.4.3 Configuring a distributed
system. The number of rendering machines (graphic engines) is asked. For each rendering machine the IP address
and the arrangement must be specified. The position of the machine is only asked, if you configure continuous
mode. Furthermore the type of the graphic card must be indicated and the depth resolution must be assigned.
Subnet Configuration
-------------------Enter IP Address for the subnet NIC card[192.168.1.254]:
Enter Sub Netmask of graphic engines [255.255.255.0]:
Graphic Engines' Configuration
-----------------------------Enter number of graphic engines [2]:
IP address for engine 1 [192.168.1.1]:
Ethernet address for engine 1 [00.00.00.00.00.00]: 00.a0.c0.83.76.98
Screen arrangement for engine 1 (Width x Height) [2x4]: 2x2
Position for engine 1 (X,Y) [0,0]:
Graphic card type for engine 1
1 - "AGX-3000"
2 – "AGX-3281"
Enter the graphic card type [1]: 2
Configuring the Depth Resolution (Bit Per Pixel)
–--------------------------------------------- 1 - for 8 bpp (256 colors)
2 - for 16 bpp (64K colors)
3 - for 8 and 16 bpp (MultiDepth/MultiColor feature)
Usable only for resolution up to 1400x1050
4 - for 32 bpp (16M colors)
Enter the Depth Resolution [3]: 2
Configuring the Visual Class
–-------------------------A visual class describes the characteristics of a virtual colormap,
that has been or can be created for use a particular screen
IP address for engine 2 [192.168.1.2]:
Ethernet address for engine 2 [00.00.00.00.00.00]: 00.a0.c0.83.54.77
Screen arrangement for engine 2 (Width x Height) [2x4]: 2x2
Position for engine 2 (X,Y) [0,0]: 2,0
Graphic card type for engine 2
1 - "AGX-3000"
2 – "AGX-3281"
Enter the graphic card type [1]: 2
Configuring the Depth Resolution (Bit Per Pixel)
–--------------------------------------------- 1 - for 8 bpp (256 colors)
2 - for 16 bpp (64K colors)
3 - for 8 and 16 bpp (MultiDepth/MultiColor feature)
Usable only for resolution up to 1400x1050
4 - for 32 bpp (16M colors)
Enter the Depth Resolution [3]: 2
Configuring the Visual Class
–-------------------------A visual class describes the characteristics of a virtual colormap,
that has been or can be created for use a particular screen
The following visual class are supported.
1 - TrueColor (read only visual)
2 - DirectColor (read/write visual)
Enter the Visual Class [1]: 2
These are your MLS Server settings
==================================
- Core machine's second IP: 192.168.1.254
- Engines Netmask Address: 255.255.255.0
- Operational mode : Contiguous
- Number engines : 2
- Values for engine 1: IP = 192.168.1.1 Ether = 00.a0.c0.83.76.98
arrangement = 2x2 position = 0,0
AGX-3281: Bpp = 16 Visual = TrueColor
- Values for engine 2: IP = 192.168.1.2 Ether = 00.a0.c0.83.54.77
arrangement = 2x2 position = 2,0
AGX-3281: Bpp = 16 Visual = DirectColor
Everything correct? (yes/no)? [yes]:
3. Getting started
Finishing the configuration
After specifying the parameters for multiple logical screens the values explained in section 3.4.2 X.11 configuration
and section 3.4.3 Configuring a distributed system must be indicated.
When configuration is completed, you can enter service mmtserv to start the X server:
eos:/opt/MMT2686/config # service mmtserv
If you operate Argus in eXtended safety boot mode, please take care to update the backup
partition after successful configuration, see section 4.8.5 Backup and restore procedures (eosxs
This chapter shows the capabilities that ARGUS offers displaying graphics and video. The multi-screen capability of
RGUS, the extensions of the X server and the X window system’s strategies for color management are explained.
A
You are introduced into operating the video client for displaying video and RGB signals and the remote control
client for controlling a Barco display wall.
An essential feature of ARGUS is the multi-screen capability, which differs in some points from the multi-head
mode of a conventional X server.
The X server of ARGUS allows a root window that extends over all connected projection modules. In this case,
X clients use the whole display area, without even knowing this (transparent multi-screen).
For an exact description of the differences between multi-screen and multi-head mode, the terms display and
screen of X.11 terminology are important:
Display
A display contains all input and output devices, which are assigned to an X server. Two or more displays may be
installed on a single computer. In this case several X servers are running each of which has its own keyboard
(mouse, tablet etc.) and its own screen; however, both servers operate logically independent from each other so
that two separate workplaces are available.
Screen
A screen is a logic output device of an X server which is represented generally by a physical output device. An
X server can quite operate several screens. However, such a construction has only one keyboard and one mouse.
It is a workplace for a single person.
The difference between a conventional X server in multi-head mode with several monitors and the multi screencapable A
RGUS controlling a display wall is described below.
Multi head
Every screen is represented in the multi-head mode by a corresponding monitor and has its own root window.
An X client, which is connected to this server can open windows on both screens. However, an individual window
is always completely attached to a screen. Moreover, the client must be specifically programmed for the use of
several screens, what is hardly the case among standard X.11 applications. In addition, when starting such clients
the output screen must be indicated immediately. Finally there are only few window managers, which allow
consistent management over several screens.
Multi screen
In multi-screen mode A
RGUS offers – in the sense of X.11 – only a single root window, which extends over the
whole display wall with an unlimited number of projection modules. Every window manager allows to position
the windows of any client somewhere on the display wall, to displace them to another projection module or
even to expand them over several or all projection modules simultaneously.
Multiple logical screens
With the multiple-logical-screens mode A
RGUS combines in a way the multi-head mode and the multi-screen
mode. It allows one X server to display multiple screens each on an individual rectangular array of m×n graphic
channels. Each screen can be configured with its own color depth and visual class. Multiple-logical-screens can
only be used with a distributed system. Each rendering machine displays one screen.
The configuration of multiple-logical-screens is explained in section 6.1.6 Advanced Argus configuration (geometry).
Note that multiple logical screens can not be used simultaneously together with the
X MultiCursor extension (XMC), see section 4.4 X Server extensions.
The translation between RGB values specified in applications and the color displayed on-screen is controlled by
pixel values serving as indices to a color map. The application obtains the pixel values from the X window system.
RGB values
RGB values are the red, green and blue intensity values that are used to define a color. According to the X.11
protocol these values are represented as 16-bit, unsigned numbers, with 0 the minimum intensity and 65535 the
maximum intensity. Most hardware however represents each value as a number in the range from 0 to 255.
Color map
A color map consists of a set of numbered entries – so called color cells – defining pixel values. Each color cell
contains a single RGB triple – a combination of RGB values. The color map will be filled at runtime.
X.11 supports two ways for handling color maps:
•shared color cell
Colors that can be used by different X clients are called shared colors. A color that was once allocated can not
be changed. When an X client is requesting for a shared color the X server searches the color map for exactly
the requested color (exact match). If the color is not found a new color will be allocated in the color map.
•private color cell
A color that can only be used by one client is considered to be a private color. Only the client that allocated it
can use a private color. A client is able to change the contents of a private cell. As long as entries are available in the color map, private colors can be allocated.
Color depth
On a black-and-white screen, each pixel is represented with a single binary digit, i. e. a color depth of 1. Many
color workstations have a color depth of 8bit, each pixel on such a screen is represented by eight bits, allowing
8
= 256 on-screen colors. A color depth of 24 bits corresponds to 224 = 16.7 million (16M) colors and is said to
2
cover all shades of colors the human eye can distinguish.
Due to the different display capabilities of workstations reaching from a color depth of 1 bit up to 24 bits different strategies for translating pixel values into on-screen colors have been developed in the X window system.
These strategies are called visual classes.
The X window system defines six visual classes, three of them are dynamic (PseudoColor, GrayScale,
DirectColor) and three are static (StaticColor, StaticGray, TrueColor):
•PseudoColor
is a class having a color map in which a pixel value indexes the color map entry to produce an independent
RGB value; that is, the color map is viewed as an array of triples (RGB values). Shared and private color cells
can be allocated.
•StaticColor
can be viewed as a case of PseudoColor in which the RGB values are predefined and readonly; no private color cells are available.
• GrayScale
can be viewed as a case of PseudoColor, in which the red, green, and blue values in any given color map entry are equal and thus, produce shades of gray Shared and private color cells can be allocated.
• StaticGray
can be viewed as a case of GrayScale in which the gray values are predefined and read-only;
no private color cells are available.
•DirectColor
is a class of color map in which a pixel value is decomposed into three separate subfields for indexing. The
first subfield indexes an array to produce red intensity values. The second subfield indexes a second array to
produce blue intensity values. The third subfield indexes a third array to produce green intensity values.
Shared and private color cells can be allocated.
•TrueColor
can be viewed as a case of DirectColor in which the subfields in the pixel value directly encode the corresponding RGB values. That is, the color map has predefined read-only RGB
values.
Further documentation
The color management of the X window system is explained in more detail in:
• The Definitive Guide to the X Window System – Volume 1
RGUS you can use the following combinations of visual class and color depth, depending on
which kind of application is to be displayed:
• DirectColor, 16bit (R: 5bit, G: 6bit, B: 5bit) for displaying video
16
= 64K colors can be displayed. Shared and private color cells are available.
2
• DirectColor, 32bit (R: 8bit, G: 8bit, B: 8bit) for displaying video
24
= 16M colors can be displayed. Shared and private color cells are available.
2
• TrueColor, 16bit (R: 5bit, G: 6bit, B: 5bit) for displaying video
16
= 64K colors can be displayed. The possible RGB values in the color map are predefined in equidistant
2
steps. Thus it is guaranteed that the whole spectrum of colors is covered.
• TrueColor, 32bit (R: 8bit, G: 8bit, B: 8bit) for displaying video
24
= 16M colors can be displayed. The possible RGB values in the color map are predefined in equidistant
2
steps. Thus it is guaranteed that the whole spectrum of colors is covered.
• PseudoColor, 8bit with NearBy Color Allocation for displaying pure 8 bit applications
8
= 256 colors out of 2563 = 16M can be displayed. Shared and private color cells are available. The maxi-
2
mum number of shared and private color cells together is 256.
NearBy color allocation
X clients may exit on an allocation of a shared or private color cell, if the color map is already full and the requested color cell is not included in the color map, yet. However, the NearBy Color Allocation guarantees, that
each request for a shared color cell returns a color cell, whether or not the color map is already full or an entry in
the color map matches the request. Please, refer to section 6.1.8 Nearby color allocation for more details.
Multi-color-depth
With the multi-color-depth option of the X server two color modes, 8 bit PseudoColor and 16 bit TrueColor, are
available for X clients in parallel. The root window runs in one color mode whereas X clients may also display
windows in the other color mode. Multi-color-depth can be configured in the following way:
• 8 bit PseudoColor for the root window and 8 bit PseudoColor or 16 bit TrueColor as Option for X clients
• 16 bit TrueColor for the root window and 8 bit PseudoColor or 16 bit TrueColor as Option for X clients.
By default most X clients start in the same color mode that the X server uses for the root window. Some X clients
have the ability to use alternatively another color mode. There are two types of such X clients that can make use
of this feature:
• X clients that need to be started with an option identifying the wanted color mode
• X clients that have the ability to automatically start in the color mode most suitable to display their content
This feature is available with UGXGRAPHIC CARDS and for resolutions up to 1400×1050.
OmniScaler
The O
MNISCALER enables to display video and RGB sources no matter in what color mode and color depth the
X server operates. Thus optimal integration of 8 bit PseudoColor applications with high quality video and RGB
display is possible. If the X server operates in 8 bit PseudoColor mode, the video / RGB window is displayed in
YUV4:2:2 / 16 bit TrueColor mode. Complete correlation between color mode of the X Server and the video/RGB
window is listed in the table below.
With Module Video the video or RGB signals of the Q
UAD ANALOG VIDEO CARD, STREAMING VIDEO CARD or DUAL RGBINPUT
CARD are displayed without borders and fitted to complete projection modules (1 to n×n, depending on configuration). The same color capabilities apply as with movable and scalable video and RGB windows. Please, refer also
to section 4.6.3 The Xvideo client for more details.
Dual RGB Input Card
The D
UAL RGBINPUT CARD offers the possibility to provide RGB data either in 16 bpp (RGB 5:6:5) or in 24 bpp
(RGB 8:8:8). Switching between these two modes requires a restart of the X server with the respective option
set, please refer to section 6.1.5 X server parameters.
Overview of color capabilities
The following table lists color depth and format of the video and of the X clients in dependence of color depth
and visual class of the X server. The video and RGB color format applies with module video as well as with video
in a window.
QUAD ANALOG VIDEO CARD /
STREAMING VIDEO CARD
PseudoColor 8 bit
Video in YUV4:2:2
DUAL RGBINPUT CARDapplication windows of
X clients
RGB format with 16 bpp or
color mode of X server
RGB format with 24 bpp 2)
multi-color-depth
PseudoColor 8 bit and
TrueColor 16 bit overlay 1)
DirectColor 16 bit
Video in YUV4:2:2
Video in YUV4:2:2
RGB format with 16 bpp or
RGB format with 24 bpp 2)
RGB format with 16 bpp or
color mode of X server or
16 bit TrueColor
color mode of X server
RGB format with 24 bpp 2)
TrueColor 16 bit
Video in YUV4:2:2
RGB format with 16 bpp or
color mode of X server
RGB format with 24 bpp 2)
multi-color-depth
TrueColor 16 bit and
PseudoColor 8 bit overlay 1)
DirectColor 32 bit
Video in YUV4:2:2
Video in YUV4:2:2
RGB format with 16 bpp or
RGB format with 24 bpp 2)
RGB format with 16 bpp or
color mode of X server or
8 bit PseudoColor
color mode of X server
RGB format with 24 bpp 2)
TrueColor 32 bit
Video in YUV4:2:2
RGB format with 16 bpp or
color mode of X server
RGB format with 24 bpp 2)
color capabilities for X server and video of ARGUS
Besides some standard X server extensions ARGUS offers a set of additional specialized X server extensions. These
extensions are mentioned here briefly. Full documents for software development are available on request.
X MultiCursor (XMC)
The X MultiCursor extension allows the simultaneous use of several mouse pointers, which can be moved independently from each other over the root window. The XMC extension behaves like the standard X.11 input extension of the X Consortiums and can be handled exactly the same way.
Note that the X MultiCursor can not be used simultaneously together with multiple logical
screens, see section 4.1 Multi-screen capability.
X Blink
With the X Blink extension, a blinking property can be put on shared color cells. A blinking color has two color
information. These two colors are changed with an optional frequency. DIN blinking frequencies are provided.
X Video
The X Video extension for connecting a Barco video input card is dealt with in detail in the following chapter.
X UCL
This extension is required for O
SIRIS. The functionality includes authorization mechanisms for X Clients and support
of constraint areas for windows.
X MVGS
This extension is required for O
SIRIS. It offers layout configuration management and remote pointer.
Multiple logical screens can be used together with Osiris and the X MVGS, X UCL extension
only in the contiguous mode.
X Genlock
The X Genlock extension enables to synchronize the graphic output to the frame rate of an internal or external
video source or to the clock of one UGX or AGXGRAPHIC CARD. The usage of X Genlock is explained in the following
sections.
The window manager, which is pre-configured on ARGUS offers a convenient and fast way to choose certain
commands. By clicking on the root window background depending on left click or right click a menu opens.
Left click and right click on the root window background
Work menu
Xterm Start X terminal window
Xvideo Start Xvideo client for displaying video and RGB
Rctrl Start REMOTE-CONTROL client
Xgenlock Select QAVC (Quad Analog
Select the first channel of the first QUAD ANALOG VIDEO CARD for genlocking
Video Card)
Select SVC (Streaming
Select the first channel of the first STREAMING VIDEO CARD for genlocking
Video Card)
Select Intern Select the first UGX or AGXGRAPHIC CARD for genlocking Select Extern Select the external genlock signal for genlocking OFF Switch genlocking off
ON Switch genlocking on Read Config File Read and apply the last saved genlock settings Save Config File Save the current genlock settings and apply them automatically after
system restart
When using genlock make sure, that the cabling for genlock has been established as
explained in section 3.2.13 CPU board.
Figure 4-1
If an external signal is connected only external may be selected. If selecting internal or a
video signal it will be disturbed by the external signal. Therefore the external signal should
be unplugged before switching to an other type of genlock!
Configuration Screensaver
Default Set screensaver to default settings
Immediately Set screensaver to immediate screensaving
Blank Set screensaver to blank display
Pattern after 5 min off Set screensaver to switch off pattern after 5 minutes
Off Switch screensaver off
Mouse
Fast Set speed of mouse to fast
Normal Set speed of mouse to normal
Slow Set speed of mouse to slow
Left handed mouse Configure mouse for left handed operation
Right handed mouse Configure mouse for right handed operation
System beep Loud and long Set system beep to loud and long
Loud Set system beep to loud
Normal Set system beep to normal
off Switch off system beep
Root Background BARCO logo Select Barco logo as background for root window
Standard black Select black as background for root window
Standard white Select white as background for root window
Standard gray Select gray as background for root window
Standard navy blue Select navy blue as background for root window
Grid 640x480 Display adjustment grid (maintenance)
Grid 800x600 Display adjustment grid (maintenance)
Grid 1024x768 Display adjustment grid (maintenance)
Grid 640x480 bold Display adjustment grid (maintenance)
Grid 800x600 bold Display adjustment grid (maintenance)
Grid 1024x768 bold Display adjustment grid (maintenance)
Restart Eos X Server default mode Restart X server in default color mode
pseudo 8 Bit color mode Restart X server in PseudoColor mode, 8bpp
true 16 Bit color mode Restart X server in TrueColor mode, 16 bpp
direct 16 Bit color mode Restart X server in DirectColor mode, 16 bpp
true 32 Bit color mode Restart X server in TrueColor mode, 32 bpp
direct 32 Bit color mode Restart X server in DirectColor mode, 32 bpp
Alternatively the X server can by restarted by means of the restart X server utility, please refer to section 4.8.4
Restart X server utility (service mmtserv).
It is not possible to restart the X server in multi-color-depth, if an other color mode has
been configured in the X.11 configuration.
But if the X server has been configured in multi-color-depth it can be restarted with the
other color depths mentioned above. To revert to multi-color-depth the X server must be
restarted in the default mode.
Please keep in mind that a higher color depth requires also a higher bandwidth for graphic
data.
In addition, changing the color mode of the X server might change the color mode of video
or RGB and lead therefore also to an increase in required bandwidth for video, please refer
to section 4.2.2 Color capabilities of Argus to see which video color mode applies for which X
server color mode and to section 4.6.1 The input cards to see the required bandwidth for video
and RGB.
Both effects might lead to a loss of performance!
Window Menu
Move Move window Resize Resize window
Iconify Iconify window Maximize/Normal Maximize window, respective return to normal
(Un)Stick Stick window to its position on a virtual desktop
Refresh Refresh window
Raise Raise window
Lower Lower window
Next Next window
Previous Previous window
Window list Display window list
Close Close window
Kill Kill window
Fvwm2
Restart Fvwm2 Restart window manager
Modules
Audio (Please, refer to the fvwm2 man pages!)
AutoRaise on (Please, refer to the fvwm2 man pages!)
AutoRaise off (Please, refer to the fvwm2 man pages!)
Banner (Please, refer to the fvwm2 man pages!)
Buttons (Please, refer to the fvwm2 man pages!)
Debug (Please, refer to the fvwm2 man pages!)
Icon Box (Please, refer to the fvwm2 man pages!)
Icon Man (Please, refer to the fvwm2 man pages!)
Ident (Please, refer to the fvwm2 man pages!)
Pager (Please, refer to the fvwm2 man pages!)
Save (Please, refer to the fvwm2 man pages!)
SaveDesk (Please, refer to the fvwm2 man pages!)
Scroll (Please, refer to the fvwm2 man pages!)
Talk (Please, refer to the fvwm2 man pages!)
WinList (Please, refer to the fvwm2 man pages!)
4. Operating
System tools
EOSinfo Display release integrity status, please refer also to section 4.8.6 Release
integrity utility (eosinfo).
Event Test Start event monitor
Vi Start vi text editor
Telnet Start telnet client
Clocks
Analog Display analog clock
Digital Display digital clock
Shells
Bash
Bash Start bash shell
Big bash Start big bash shell
Login bash Start login bash shell
Tcsh
Tcsh Start tcsh shell
Big tcsh Start big tcsh shell
Login tcsh Start login tcsh shell
Video and RGB signals can be displayed on an Barcodisplay wall with the optional input cards QUAD ANALOG VIDEO
CARD, STREAMING VIDEO CARD and DUAL RGBINPUT CARD. Based on an extension library of the X server the Barco video
client
xvideo allows the convenient handling of analog video, streaming video and RGB signals.
Simultaneous operation
Multiple input cards can be operated simultaneously. In this case, the corresponding video windows may freely
overlap. For larger display walls a system with multiple OmniBus devices may be required. Large systems with
freely movable video and RGB windows require the usage of a distributed system.
OmniScaler
Due to the dual color mode capability of the O
MNISCALER, ARGUS can display video and RGB signals in their native
color mode e.g. YUV4:2:2 and 16 bit RGB TrueColor while the X Server operates in 8 bit PseudoColor mode with
256 colors. Please, refer to section 4.2 Color management for more details.
MNISCALER provides the capability to process up to 128 video and RGB inputs simultaneously. Video and RGB
One O
data is triple buffered. Therefore only entire frames are displayed in sync with the graphical data to avoid frame
tearing.
Backend scaling
MNISCALER is able to do backend scaling. Scaling the video data at the backend of data transfer chain (Input
The O
card -> PCI-Bus -> O
MNISCALER provides up-scaling capabilities until full-screen resolution and far beyond.
O
MNISCALER) has its big advantage in a reduced need of PCI Bus bandwidth. Furthermore the
The backend scaling uses linear interpolation for calculating new pixels.
In standard configuration the X server, depending on the size of the video window and the type of the input card
automatically controls the usage of backend scaling.
Dependant on the scaling factor either the O
video or RGB window is larger than 1:1 the O
MNISCALER or the input card scales data. As soon as the size of the
MNISCALER scales data up to the displayed size. If the video is dis-
played in a lower resolution than 1:1, then the input card itself performs a downscaling, to reduce the need of
bandwidth for the data transfer.
Module video
UAD ANALOG VIDEO CARD, STREAMING VIDEO CARD and the DUAL RGBINPUT CARD also display videos and RGB signals
The Q
respectively without borders and fitted to complete projection modules (1 to n×n, depending on configuration).
The display is always »on top«, other applications are »behind« and can not be manipulated by accident. If the
display is removed from the desktop (quit or iconified) all covered applications show up again immediately.
In a distributed system the display wall is controlled by multiple rendering machines. If a
video shall be displayed on the display areas of multiple rendering machines, all concerned
OmniBus devices must be supplied with the video signal.
Genlock
The A
RGUS system provides the ability for genlocking. Either a video of the QUAD ANALOG VIDEO CARD or of a
TREAMING VIDEO CARD, the clock of an UGX or AGX GRAPHIC CARD or an external studio signal can be used as refer-
S
ence signal. Basic functionality of genlock is accessible via the window manager, please refer to section 4.5
Window manager. Access to the complete genlock functionality is explained in section 4.8.8 Genlock utility.
For showing information from external sources like video or RGB data on a Barco display wall a set of input cards
is provided. For integration of video the Q
RGB data the D
UAL RGBINPUT CARD can be used. Multiple input cards can be inserted into an ARGUS OMNIBUS.
An X video application allows to display the sources connected to the input cards in individual windows on the
display wall, that can be freely scaled and moved within the projection cubes connected to theOMNIBUS. The
display options can be set in a dialog box.
Quad Analog Video Card
UAD ANALOG VIDEO CARD and the STREAMING VIDEO CARD is available and for
Four different video sources (VHS or S-VHS) can be connected to a Q
UAD ANALOG VIDEO CARD and displayed simulta-
neously.
Streaming Video Card
Up to four MPEG-2 D-1 or CIF video streams per S
ously by one S
TREAMING VIDEO CARD.
TREAMING VIDEO CARD can be decoded and displayed simultane-
Dual RGB Input Card
The D
UAL RGBINPUT CARD digitizes one or two analog monitor signals. In dual input mode it supports two monitor
signals with a pixel frequency between 10 MHz and 135 MHz, in single input mode it supports one signal with a
pixel frequency up to 270 MHz. The most common VESA timings are stored as presets. In addition, user defined
timings can be saved. The timing and aspect ratio of the connected RGB signal are detected automatically.
UAL RGBINPUT CARD has an automated static frame rate reduction depending on number and type of the
The D
signals it processes, please see the table below.
static frame rate reduction* used socket
dual input mode (two signals, both ≤ 1280×1024@75Hz) 1/3 RGB in 1 AND RGB in 2
single input mode (one signal ≤ 1280×1024@75Hz) 1 RGB in 1 OR RGB in 2
single input mode (one signal > 1280×1024@75Hz) ½ RGB in 1
(* values are valid from release of the X server 3.4 on and Control ware 6 of the D
static frame rate reduction for RGB sources
UAL RGBINPUT CARD)
Table 4-2
To take advantage of the higher frame rate for signals ≤ 1280×1024@75Hz in single input mode, the other
socket may be connected to a second signal but that signal may not be displayed on the display wall.
The X video application allows selecting additionally a dynamic frame rate reduction of the source, which must
be multiplied to the static frame rate reduction to obtain the overall frame rate reduction, please refer also to
section 4.6.4 Displaying video and RGB signals.
The number of video and RGB data that can be processed in one A
able on the O
MNIBUS. These are 400 MBps. The following table gives an overview about the bandwidth required
RGUS OMNIBUS underlies the bandwidth avail-
for some standard window sizes. In the last column there is in addition the value of maximal windows of that
type. This value is valid if only windows with the specified properties are displayed.
type number of
pixels
Sources of Quad Analog Video Card and Streaming Video Card
size of video/RGB data and number of displayable video windows in case that only this type of video window is displayed by that O
Table 4-3
To calculate the bandwidth for windows of different sizes or frame rates the following formula can be used:
B = res
* res
xxxx
* fr * cd
yyyy
The abbreviations have the following meaning:
• res
, resy – resolution of the source in x- and y-direction in pixels
x
It is important to consider the final scaling used to display the window. Up-scaling of the input sources is performed in the O
MNISCALER therefore data is transferred 1:1 and the original resolution must be inserted into
the formula. If the source is displayed smaller than 1:1 the source is downscaled directly in the input card.
The original size of the different video types can be read from the table above.
• fr – frame rate
For video a frame rate of 25fps (PAL/SECAM) and 30fps (NTSC) is standard. For dynamic RGB input a frame
rate of 20 fps in normal cases gives an acceptable performance. If the RGB-source is mostly static even lower
frame rates can be selected.
For all video windows the color mode YUV 4:2:2 is used, which means the factor is
cd = 2
For RGB windows two different color modes may be useful, please refer to section 4.2.2 Color capabilities of
Argus:
Color mode = RGB 16 bppcd = 2C o l o r m o d e = RGB 24 bppcd = 3
4. Operating
With the effective bandwidth of the O
MNIBUS of 400 MBps the sum of the bandwidth of the individual windows
may not be bigger than 400 MBps to provide optimal performance:
400 MBps = B
+ B2 + … + B
1
n
Bandwidth optimization for video and RGB windows:
All optimization settings are made by means of the X video client, please refer to the section 4.6.4
Displaying video and RGB signals.
Frame rate
For video sources there are two settings with different frame rate reduction factors selectable to
optimize the bandwidth usage. For RGB sources the static reduction of the frame rate depends on
the input mode and the dynamic frame rate reduction is selectable. (Use the Fps setting for video
data and Reduction for RGB data respectively and refer to the subsection Dual RGB Input Card
above)
Color depth
RGB sources can be digitized with 16 bpp or with 24 bpp (depending on the visual class of the X
server).
For digitalization of the analog or streaming video data and of RGB sources, a hardware module (adapter) is
necessary. Each video and RGB adapter offers one input (port). Accordingly, the Q
TREAMING VIDEO CARD has 4 adapters with one port each and the DUAL RGBINPUT CARD has two adapters with
the S
one port each.
The ARGUS system automatically creates video channels according to the available input adapters by simply assigning one channel per adapter in the order in which the input cards are inserted into the PCI slots of the A
O
MNIBUS.
In a distributed system in addition the order of the rendering machines is considered when
creating the numbers of the video channels.
In a monolithic system where input cards are located in multiple OMNIBUS devices, the video display is restricted
to the display area of the respective O
MNIBUS where the input card is plugged in.
In a distributed system video adapters of multiple rendering machines (one from each rendering machine) can
be integrated to a »logic« video channel. A logic video channel can be displayed on the display area of all appendant rendering machines.
UAD ANALOG VIDEO CARD as well as
RGUS
Channel 1
The configration of logical video channels is done by means of the configuration script
EOSconfig, please refer to section 3.4.3 Configuring a distributed system. Additional background
information about the configuration of logical video channels can be found in section 6.1.6
Advanced Argus configuration.
1
A
RGUS
Channel 2
2
A
RGUS
Channel 1
A
RGUS
1
A
RGUS
Figure 4-2
video input cards in different rendering machines
left: operated separately, right: as one logical channel
For displaying videos and RGB signals on the display wall an X client is available. The client is called xvideo and
handles all inputs from Q
The video client
xvideo can be started as follows:
# xvideo [-<option>]
After xvideo is started two windows show up: the control panel and the canvas panel. The control panel of-
fers controls for customizing the display, whereas the canvas panel displays the video or RGB data. The video
client detects automatically what kind of signal is connected to channel 1.
UAD ANALOG VIDEO CARD, STREAMING VIDEO CARD and DUAL RGBINPUT CARD.
Xvideo client control and canvas panel
Figure 4-3
The video client offers up to three tabs for QUAD ANALOG VIDEO CARD, STREAMING VIDEO CARD and DUAL RGBINPUT CARD
depending on the actual hardware configuration of your A
The options for starting the video client
xvideo are listed in section 4.6.5 The options. An important option is
RGUS.
described below: Module Video and Module RGB.
Module video and module RGB
All input cards allow to start the video client
xvideo with an option for displaying the input signal without bor-
ders and fitted to complete projection modules (1 to n×n, depending on configuration).
The command
# xvideo –mv 1 –mg 1x1+1+0
lets the video client start as Module Video (-mv 1) on the second projection module from the left in the upper
-mg 1x1+1+0).
row (
The displayed video or RGB signal is always »on top«, other applications are »beyond« and can not be manipulated by accident.
File Read Config File … Read configuration file
Save Config File … Save configuration file
Save Config File As … Save configuration file to another path and file name
Read Preset File … Read preset file
Save Preset File … Save preset file
Save Preset File As … Save preset file to another path and file name
Exit Quit video client
Pref Save After Exit Save/not save configuration on quitting the video client
Canvas Pref … Define position and size of Canvas Panel
RGB Pref … Set Remote Display Opens a dialag to enter IP address and screen number of the screen that
is connected to the current RGB channel
On/Off Remote Pointer Switches the remote pointer ability of the above set screen on or off;
i.e. the pointer of the ARGUS can be used to operate the screen, displayed by the RGB channel
Map/Unmap Remote
Keyboard
Maps or unmaps the remote keyboard; i.e. the keyboard of the ARGUS
can be used to operate the screen, displayed by the RGB channel
(it is also switched to the country scheme of the keyboard)
SVC Pref … Stream Settings Define settings of video streams
Board Settings Define settings of a STREAMING VIDEO CARD
View Close Canvas Panel Close canvas panel
Iconify Canvas Panel Iconify canvas panel
Raise Canvas Panel Raise canvas panel
Close Control Panel Close control panel
Help Display help in canvas panel
Table 4-4
A left mouse click in the canvas panel raises the control panel, another click dismisses it.
If no signal is connected to a video channel, the corresponding video window appears in
background color. If a signal is connected later, the Channel, Port or Live button must be
pressed.
C Set contrast of video display
B Set brightness of video display
S Set saturation of video display
Live Start video display
Still Freeze video display
QAVC 1 Select video card (the cards can be renamed)
Channel 1 Select video channel of the QUAD ANALOG VIDEO CARD (max. 4 channels; the channels can be
renamed)
Encoding Shows the detected video standard (PAL, NTSC, SECAM)
Signal Select recording standard (VHS, S-VHS)
Fps Select the frame rate (FULL, HALF - default)
Table 4-5
Configuration of the video display
In the Control Panel you can adjust the video display regarding hue, saturation and brightness etc.
The video client can store these settings as well as the selected video channel in a configuration file. From the
File menu you can choose to save the current configuration or read in other.
A certain configuration file can also be invoked as an option on the command line when starting the video client.
Please, refer to section 4.6.5 The options.
C Set contrast of video display
B Set brightness of video display
S Set saturation of video display
Live Start video display
Still Freeze video display
SVC 1 Select video card (the cards can be renamed)
Channel 1 Select video channel of the STREAMING VIDEO CARD (max. 4 channels; the channels can be
renamed)
Stream Assign a video stream to the selected Channel, please refer also to section Configuring
Streaming Video Card and Configuring video streams below
Encoding Shows the detected video standard (PAL, NTSC)
Fps Select the frame rate (FULL, HALF - default)
TREAMING VIDEO CARD once the configuration parameters must be entered into the SVC Settings dialog,
therefore select SVC Pref … -> Board Settings from the File menu; please refer to section 4.6.3 The Xvideo client.
SVC Settings dialog of the S
Figure 4-6
TREAMING VIDEO CARD
IP Configuration
Address IP address of the STREAMING VIDEO CARD.
Each STREAMING VIDEO CARD needs its own, fixed IP address
Netmask Netmask of the STREAMING VIDEO CARD, must be the same value for all cards
Gateway Gateway, must be the same value for all cards. Even if the network does not require
an indication of the Gateway, a value must be filled in.
Decoder Configuration
Algorithm All video streams processed by one STREAMING VIDEO CARD must have the same com-
pression algorithem. Currently mpeg2 and visiowave is supported
The parameters of a video stream must be defined in the SVC Stream Params Editor, before the S
TREAMING VIDEO
CARD can display it. Once defined it is available for every STREAMING VIDEO CARD in the system. To open the SVC Stream Params Editor select SVC Pref … -> Stream Settings from the File menu, please refer to section 4.6.3
The Xvideo client.
Pressing the Add button adds a new stream with the entered name into the Streams list. The parameters that
are displayed at that time are saved together with it. If there exists already an entry with the same name then
its parameters are not changed. Pressing the Apply button applies the displayed parameters to the hardware. In
that way changes can be controlled directly. Pressing the OK button applies the parameters to the hardware and
to the system. Pressing the Cancel button closes the window, anyhow changes that are already confirmed with
the Add or Delete button can not be revoked.
Stream A list of all video streams in alphabetic order
Decoder Control
IP Address select the type of stream (unicast, broadcast or multicast)
when multicast is selected also the multicast IP address must be specified
Port Encoder port, appendant to the IP address.
IP Portocol Selection of the used IP protocol.
(firmware < 2.0 of the STREAMING VIDEO CARD only supports UDP)
Stream Protocol auto Auto-detection of the stream protocol elementary Elementary stream program Program stream transport Transport stream
PID Should be entered for transport streams when the PAT (program allocation tables) or
PMT (program map tables) are not sent.
0 is a predefined value. It causes an auto-search for the video PID. If no valid PID is found
no video will be shown.
Skip bytes at …
Start
End
Encoder dependant value of the number of bytes that must be skipped at the beginning
/ end of each packet, please see table below.
Encoder Control This section contains data that is used, if initial communication with the encoder is
needed to prompt the encoder to send a stream. All fields must be filled in!
IP Address IP address of the encoder; may only be filled in if TCP has been selected for IP Protocol
Port Port where the encoder listens to TCP start commands; may only be filled in if TCP has
been selected for IP Protocol
IP Protocol Should remain udp, as indicated in the section Decoder control above. Only if a commu-
nication with the encoder is required, tcp should be selected.
Startstring String that is sent to the specified encoder
Parameters on the SVC Stream Params Editor
Figure 4-7
As unicast streams are only sent to one single IP address, only one Streaming Video Card at
a time is able to display one particular unicast stream.
The following table lists the encoder specific values that must be entered into the SVC Stream Params Editor.
Encoder IP Protocol Skip bytes
at Start …
Skip bytes
at End …
Stream type TCP PID
VCS VideoJet 1000
firmware < 2.0
Display stamping (including Time, Stamping, Time Stamping, … ) is used
UDP 16 0 auto Off 0
firmware ≥ 2.0 RTP 4 0 auto Off 0
Display stamping (including Time, Stamping, Time Stamping, … ) may not be used
Vbrick 4000UDP 0 0 auto Off 0
The encoder setting Low Latency should not be used; if there are big changes in the video image
a green flash will appear at the bottom side of the video.
IMPath I-Volution
UDP 0 0 auto Off 0
4000
NKFC-20
firmware < 2.0UDP 28 0 auto Off 256
firmware ≥ 2.0 RTP 0 0 auto Off 256
Visiowave
firmware ≥ 2.0 UDP 0 0 auto ON 0
Use »visiowave« as startstring and specify also the other entries in the section Encoder Control!
Control
R Intensity of red component G Intensity of green component
B Intensity of blue component Lock RGB Change red, green and blue component together
Bright Brightness of display
Live Start the RGB display.
Still Freeze the RGB display. DRGB 1 Select one DUAL RGBINPUT CARD (the cards can be renamed) Channel 1 Select video channel of the DUAL RGBINPUT CARD (max. 2 channels; the channels can
be renamed)
Presets Select a timing (current timing is indicated in the button)
Auto Activate auto-detect of source settings
Reduction Set the dynamic reduction factor of the frame rate; range (0, 1, 2, ... , 15)
The static frame rate reduction, determined by the input mode (please refer to section 4.6.1 The input cards (Dual RGB Input Card) can additionally be reduced by this factor
0: sets dynamic part of frame rate reduction to 1, best quality;
4: sets dynamic part of frame rate reduction to 1/2;
6: sets dynamic part of frame rate reduction to 1/3;
15: sets dynamic part of frame rate reduction to 1/15, best performance
Input Settings
Auto Auto adjustment of source Sync Level Determine the sync level of the signal
HV: tuning the horizontal/vertical sync level
SoG: tuning the Sync on Green level
Position Position display area of visible RGB signal in the Canvas Panel
H: horizontal position of first active pixel (in steps of two)
V: vertical position of first active line
SizeDetermine size of visible RGB signal
H: number of active pixels per line (in steps of four)
V: number of active lines
Phase Tune phase shift of ADC PLL Devider Determine pixel frequency of RGB input
Info Information about input signal
V_Tot: number of lines
V_Freq: frame rate
Sync: mode of synchronization
Registry Clear Name Clear text box, which displays name of current preset
Append Current setting is added to the list of presets
Insert Current setting is inserted in the list of presets (before the highlighted preset)
Replace Replace highlighted preset by current setting
Delete Delete highlighted preset
Clear all Delete all listed presets
Save Save all listed presets in preset file
Reload Reload preset file and discard changes
Import Add Add all highlighted presets to list of presets
Clear Select Clear selection
Dismiss Dismiss dialog box
If the applied signal changes while
adjusting the settings, then a warning
message apears, please see below. You
can change to the contol tab and select an
appropriate timing for the new signal
(click YES).
It is also possible, that the system detects a new timing, if the settings have been displaced
too much. In this case click NO and readjust the settings again.
UAL RGBINPUT CARD digitizes monitor signals with a pixel frequency up to 270 MHz. The video client is pre-
configured for displaying most common VESA-timings.
Since most monitor signals differ slightly from the VESA-timings, the user can adjust the pre-configured modes to
the provided monitor signals. Also additional timings can be entered and stored as new presets.
For configuring the D
UAL RGBINPUT CARD it is useful to have a suitable test pattern, basically thin black and white
vertical lines:
Windows 95/98/NT,
Macintosh,
Switch desktop pattern to alternating, one pixel wide, black and white vertical
lines
PowerMacintosh
Sun Workstation In console window (cmdtool) enter xsetroot -mod 4 4,
(enter xsetroot -mod 4 4 for removing the pattern again)
Others Display text, which contains many HHHHHHH.
Adjusting the preset
• Set up a suitable test pattern on the connected computer.
• Start the video client xvideo.
• Select the input channel in the Control tab (Channel 1 or Channel 2).
Table 4-10
Configuring RGB input
Figure 4-10
•Switch to the Input Settings tab and press Auto. This will automatically detect the source and set the right
preset.
•If necessary switch to the Input Settings tab and tune PLL Devider (approx. 1.3 × horizontal size) until the
test pattern is displayed correctly.
• Align the display within the window with Position.
• If necessary tune Phase until the test pattern is displayed without flicker.
As already mentioned a set of presets is pre-configured in the video client. These presets are stored in a preset
file. The current preset file can be modified in the Registry tab, i. e. you can replace an existing timing by your
own settings or add these to the list of timings.
The video client can handle more than one preset file. From the File menu you can choose to save the current
preset file or read in another.
A certain preset file can also be invoked as an option on the command line when starting the video client.
Please, refer to section 4.6.5 The options.
Configuration of the RGB display
Back in the Control tab you can adjust the RGB display regarding hue, saturation and brightness etc.
The video client can store these settings as well as the selected RGB channel and preset in a configuration file.
From the File menu you can choose to save the current configuration or read another.
A certain configuration file can also be invoked as an option on the command line when starting the video client.
Please, refer to section 4.6.5 The options.