This chapter provides information on software administration and troubleshooting options available with Onyx2 DPLEX. The examples given do not reflect what may be installed at any specific customer site.
The basic combiner screen has been modified to show a DPLEX option. Figure 3-1 shows the combiner interface main screen with the DPLEX option selected.
To display the Combiner's graphical user interface, type:
/usr/gfx/ircombine -gui
To specify a different display from the current workstation, such as a different pipe of a rackmount system, a remote workstation, or a specific pipe of a remote rackmount system as the target on which to display the combination, use a command similar to:
/usr/gfx/ircombine -gui -target dplexsystemname:0.0 -display remotename:0.0
When the first pipe in the DPLEX cascade must genlock internally:
Create a combination with channel 0 on pipe 0 set to 1280x1024_60. Then set channel 1 to 1280x1024_60 and the DPLEX channel to 1280x1024_60. If the genlock signal is coming from an outside source, (house sync) the format on channel 1 does not need to be loaded. See Figure 3-1.
Click Edit globals.
In the Combination Attributes window, set the Sync Source to Loopback Ch1 unless the genlock signal is coming from an outside source (house sync), in which case set it to External.
Save this combination as dplexpipe0.cmb or something similar.
Click the Download combination button and the settings are loaded.
Quit ircombine and then restart it with the target option specifying the next pipe in the DPLEX cascade.
Note: Presuming the physical cabling is correct, the additional pipes in the cascade genlock to the pipe 0 channel 1 genlock loop, see Chapter 2 for information on physical cabling. Create a combination with channel 0 at 1280x1024_60 on the next DPLEX pipe. Set the DPLEX output to 1280x1024_60.
Click Edit globals.
In the Combination Attributes window, set the Sync Source to External and Sync Format to 1280x1024_60. Whenever the sync comes from another pipe, it is also External.
Save the combination as dplexpipe1.cmb or something similar.
Click the Download combination button to save the settings.
Note: dplexpipe1.cmb can be reused for additional pipes if no changes to the DG channels are needed. All DPLEX boards must run the same video format. Repeat steps 6 through 11 for any additional pipes in the DPLEX cascade.
Deleting a pipe from an existing DPLEX cascade requires halting the system and recabling the pipes in the DPLEX cascade to connect the new configuration. This section provides an example of converting a four-pipe DPLEX cascade to a three-pipe cascade. Use the following steps to delete one of the pipes from the cascade:
Shut down the system and use the information in Chapter 2 to convert the cabling of the DPLEX to a three-pipe cascade.
Restart the system.
Use the setmon command or the Combiner interface to change the definition of the pipe that is no longer part of the DPLEX cascade. If you use ircombine, use the -target option to set the disconnected pipe. (For more information, see the setmon (1G) man page or the InfiniteReality Video Format Combiner User's Guide).
Create a combination that uses the DG channels as appropriate to the new configuration. Set the sync source to Internal (see Figure 3-2). Note that if the sync comes from another pipe, the source should be set to external.
Save the combination and close the ircombine interface.
Adding a pipe to an existing DPLEX cascade requires halting the system and recabling the pipes in the DPLEX cascade to connect the new configuration. This section provides an example of converting a two-pipe DPLEX cascade to a three-pipe cascade. The same steps should be used for converting a three-pipe to a four-pipe and so on. Follow these steps to add a pipe to the cascade:
Shut down the system and use the information in Chapter 2 to convert the cabling of the DPLEX from a two-pipe to a three-pipe cascade.
Restart the system.
Use the setmon command or the Combiner interface to change the definition of the new pipe that is now part of the DPLEX cascade. If you use ircombine, use the -target option to set the new pipe. (For more information, see the setmon (1G) man page or the InfiniteReality Video Format Combiner User's Guide).
Set the DPLEX output to 1280x1024_60. (Use the Managed Area fields if you are using the Combiner interface).
Note: DPLEX supports formats with pixel clocks between 31 and 110 MHz. Set the sync source to External. Note that whenever the sync comes from another pipe, it is External.
Set the sync format to be the same video format as that sent from the genlock master. This is shown as pipe 0 channel 1 in the cabling examples when an outside (house sync) source is not used. (Use the Sync Format field when using the Combiner interface).
Save the new combination and close the ircombine interface.
All the DPLEX pipes in a cascaded set must be connected, genlocked, and properly wired for swap ready signals to function. If you have followed all the cabling instructions (see Chapter 2) the physical cabling should be complete. The following sections provide information on checking the cabling configurations using software function tests.
You can also use the /usr/gfx/setmon command option to properly set genlock. The -g argument to /usr/gfx/setmon enables external genlocking (video clocking). See the setmon(1G) man page for details on all the /usr/gfx/setmon options.
The irsaudit provides only a limited check on individual DPLEX boards. Note that the window manager should not be running, as irsaudit needs to take direct control of the graphics hardware. You can stop the window system using /usr/gfx/stopgfx from root.
Note that you cannot run irsaudit from the DPLEX output monitor.
The operator must have root privilege to run irsaudit. See the irsaudit(1) man page for details.
Entering irsaudit with no arguments following the command runs a standard set of tests that stops upon encountering a first failure. This may be useful for testing the general state of a new or upgraded system.
The command /usr/gfx/gfxinfo provides a batch of functional information for each pipe. Note that for all pipes other than the first, gfxinfo should report source as external and the genlock as true. If you use the -v command option to /usr/gfx/gfxinfo you receive a detailed description of each pipe's components and functional status. See the following example of status for two DPLEX pipes. Note that the bold type is shown for emphasis because of the large amount of information presented.
% /usr/gfx/gfxinfo -v Graphics board 0 is “KONAL” graphics. Managed (“:0.0”) 1280x1024 Display has 2 channels 4 GEs (of 4), occmask = 0x0f 4MB external BEF ram, 32bit path 1 RM7 board (of 1) 1/0/0/0 Texture Memory: 64MB/-/-/- Medium pixel depth 32K cmap DPLEX option detected brd: 20160a06 3020c02/-/-/- f9211002 ge: 0 14832057 14731057 14231057 rm0: 15032057 15431057 4631057 1/1/1/1 4d31057 2/2/2/2/2/2/2/2 4938057 4/4/4/4/4/4/4/4/4/4/4/4/4/4/4/4/4/4/4/4 dg: 05532057 5838057 1/1/1/1 5631057 1/1 GE: NIC #: 0000.0009.9854 (family: 0b) Serial #: CJK150 Part #: 030-1129-001 KT: No NIC serial number available. RM0: NIC #: 0000.000a.986e (family: 0b) Serial #: DBT079 Part #: 030-1054-001 TM0: NIC #: 0000.000e.62a5 (family: 0b) Serial #: DBT121 Part #: 030-1053-001 RM1: No NIC serial number available. TM1: No NIC serial number available. RM2: No NIC serial number available. TM2: No NIC serial number available. RM3: No NIC serial number available. TM3: No NIC serial number available. BP: No NIC serial number available. DG: NIC #: 0000.002f.e630 (family: 0b) Serial #: HPG092 Part #: 030-1242-001 DGOPT:NIC #: 0000.002c.e13c (family: 0b) Serial #: HSD973 Part #: 030-1409-001 Input Sync: Voltage - Video Level; Source - Internal; Genlocke d - True Channel 0: Origin = (0,0) Video Output: 1280 pixels, 1024 lines, 60.00Hz (1280x1024_60. vfo) Video Format Flags: (none) Sync Output(s): Composite sync on Green Composite TTL sync on Aux 0 Using Gamma Map 0 Channel 1: Channel's Source Size: 96 pixels, 92 lines; Origin = (0,0) Video Output: 1280 pixels, 1024 lines, 60.00Hz (1280x1024_60. vfo) Video Format Flags: (none) Sync Output(s): Composite sync on Green Composite TTL sync on Aux 0 Using Gamma Map 0 Channel 2 (physical port 222): Origin = (0,0) Video Output: 1280 pixels, 1024 lines, 60.00Hz (1280x1024_60. vfo) Video Format Flags: (none) Sync Disabled Using Gamma Map 0 Graphics board 1 is “KONAL” graphics. Managed (“:0.1”) 1280x1024 Display has 2 channels 4 GEs (of 4), occmask = 0x0f 4MB external BEF ram, 32bit path 1 RM7 board (of 1) 1/0/0/0 Texture Memory: 64MB/-/-/- Medium pixel depth 32K cmap DPLEX option detected brd: 20160a06 3020c02/-/-/- f9211002 ge: 0 14832057 14731057 14231057 rm0: 15032057 15431057 4631057 1/1/1/1 4d31057 2/2/2/2/2/2/2/2 4938057 4/4/4/4/4/4/4/4/4/4/4/4/4/4/4/4/4/4/4/4 dg: 05532057 5838057 1/1/1/1 5631057 1/1 GE: NIC #: 0000.0009.9858 (family: 0b) Serial #: CKW000 Part #: 030-1129-001 KT: No NIC serial number available. RM0: NIC #: 0000.000a.48e8 (family: 0b) Serial #: DBS160 Part #: 030-1054-001 TM0: NIC #: 0000.000a.4ce5 (family: 0b) Serial #: DBS176 Part #: 030-1053-001 RM1: No NIC serial number available. TM1: No NIC serial number available. RM2: No NIC serial number available. TM2: No NIC serial number available. RM3: No NIC serial number available. TM3: No NIC serial number available. BP: No NIC serial number available. DG: NIC #: 0000.001e.3105 (family: 0b) Serial #: HPG076 Part #: 030-1242-001 DGOPT:NIC #: 0000.001e.3109 (family: 0b) Serial #: HSD984 Part #: 030-1409-001 Input Sync: Voltage - Video Level; Source - External; Genlocke d - True Channel 0: Origin = (0,0) Video Output: 1280 pixels, 1024 lines, 60.00Hz (1280x1024_60. vfo) Video Format Flags: (none) Sync Output(s): Composite sync on Green Composite TTL sync on Aux 0 Using Gamma Map 0 Channel 2 (physical port 222): Origin = (0,0) Video Output: 1280 pixels, 1024 lines, 60.00Hz (1280x1024_60. vfo) Video Format Flags: (none) Sync Disabled Using Gamma Map 0 Another way to query the Onyx2 system about the operational status of a DPLEX cascade is to use the command: /usr/gfx/hyperpipeinfo Note that this command does not accept any arguments. To run the command from another workstation you should rlogin and use a command such as: setenv DISPLAY :0.0 |
The following example shows an Onyx2 system with six pipes installed. In this example pipe 5 either does not have a DPLEX option or it's LVDS cable is disconnected. This is indicated by the -1 following the network id.
% /usr/gfx/hyperpipeinfo opening default display :0.0 pipe :0.0 network id 0 pipe :0.1 network id 0 pipe :0.2 network id 0 pipe :0.3 network id 0 pipe :0.4 network id 0 pipe :0.5 network id -1 |
The following listed man pages offer additional operational information on DPLEX:
GLX_SGIX_hyperpipe
glXQueryHyperpipeNetworkSGIX (3G)
glXQueryHyperpipeConfigSGIX (3G)
glXDestroyHyperpipeConfigSGIX (3G)
glXBindHyperpipeSGIX (3G)
glXHyperpipeConfigSGIX (3G)
DPLEX users can also obtain additional information by looking at the example program /usr/diags/IR/bin/hyper. This example program configures the existing DPLEX network and runs a simple clock application on all the pipes.
The output of all these pipes is multiplexed at the output pipe. See the command line options for /usr/diags/IR/bin/hyper for further details. The source for this program may be found in /usr/share/src/hyperpipe/hyper. Note that the file gl_dev.sw.gldev must be installed in order to gain access to this example program. The program is intended only as a basic example.