The entire risk of the use or the result of the use of this Hardware and Software and documentation remains
with the User. Information in this document is subject to change without notice. No part of this document
may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in
any form or by any means, electronic or mechanical, including photocopying without express written
permission of Jupiter Systems. See also “Statement of Limited Warranty” on page v.
Notice of Regulatory Compliance
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant
to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial environment. This equipment generates,
uses, and can radiate radio frequency (RF) energy and, if not installed and used in accordance with the
instructions, may cause harmful interference to radio communications. Operation of this equipment in a
residential area is likely to cause harmful interference in which case the user will be required to correct the
interference. The user is cautioned that changes or modifications not approved by Jupiter Systems can void
the user’s authority to operate this equipment.
Jupiter, Jupiter logo, and PixelNet are registered trademarks of Jupiter Systems. PDC and TeamMate are
trademarks of Jupiter Systems.
Acknowledgements
All non-Jupiter brands and names are the property of their respective owners.
Jupiter Systems
31015 Huntwood Avenue
Hayward, CA 94544-7007
510-675-1000 (v)
510-675-1001 (f)
info@jupiter.com
support@jupiter.com
510-675-1007 (v)
PixelNet Domain Control User Manualiii
Warranty
Statement of Limited Warranty
PixelNet Hardware
Jupiter Systems warrants that the PixelNet Hardware sold by Jupiter are free from defects in material and
workmanship and will perform in accordance with the product specification for a period of 24 months from
the date of shipment from Jupiter Systems. This warranty is in effect whether the product was purchased
directly from Jupiter or through an authorized Jupiter distributor. Any product becoming defective within
the time period specified will be repaired or replaced, at Jupiter’s option and at Jupiter’ s factory or
authorized repair center. The defective product must be returned to Jupiter or to the Jupiter authorized
repair center at the expense of the customer. Expense for the return shipment of the product to the customer
within the U.S. will be borne by Jupiter.
Products returned to Jupiter must have a Return Merchandise Authorization (RMA) number. To obtain an
RMA number contact the Jupiter repair service center at the phone number listed on the Copyright page.
PRODUCTS SHIPPED TO JUPITER WITHOUT A RETURN AUTHORIZATION NUMBER
WILL NOT BE ACCEPTED.
JUPITER’S TOTAL LIABILITY UNDER THIS WARRANTY SHALL BE LIMITED TO THE
REPA IR OR REPLACEMENT OF THE DEFECTIVE PRODUCT OR, AT JUPITER’S OPTION,
RETURN OF THE PRODUCT TO JUPITER FOR A REFUND OF THE FULL PURCHASE
PRICE. THE ABOVE WARRANTY IS THE ONLY WARRANTY APPLICABLE TO JUPITER’S
PRODUCTS AND IS THE CUSTOMER’S SOLE AND EXCLUSIVE REMEDY FOR ANY
DEFECT IN THE PRODUCTS.
Jupiter does not warrant the product for fitness for any particular purpose or application. Jupiter has no
liability for statements of functionality, performance, or configurability beyond the written product
specification for the specific Jupiter product. Jupiter shall not be held liable for incidental, indirect,
consequential, general or special damages resulting from the use or the inability to use or the failure of a
Jupiter product used in any application. No warranty, including this warranty, shall apply to any Jupiter
products that have been modified in any way, by any organization other than the Jupiter factory. The
warranty is void for products that have been subjected to misuse, improper maintenance, negligence, and/
or damage by excessive current, temperature, or accident.
Jupiter neither assumes nor authorizes any representative or other person to assume for Jupiter any other
warranty or liability in connection with the sale or shipment of Jupiter products. Jupiter reserves the right
to make changes or improvements in its products without incurring any obligation to similarly alter
products previously purchased.
PixelNet Domain Control User Manualv
Warranty
Software Warranty and Special Provisions
Limited Warranty
Jupiter Systems warrants that the SOFTWARE will perform substantially in accordance with the
accompanying written materials for a period of ninety (90) days from the date of sale. Any implied
warranties on the SOFTWARE are limited to ninety (90) days.
Customer Remedies
Jupiter Systems’ entire liability and your exclusive remedy shall be, at Jupiter Systems’ option, either (a)
return of the price paid, or (b) repair or replacement of the SOFTWARE that does not meet this Limited
Warranty and which is returned to Jupiter Systems with a copy of your receipt or purchase order number.
This Limited Warranty is void if failure of the SOFTWARE has resulted from accident, abuse, or
misapplication. Any replacement SOFTWARE will be warranted for the remainder of the original
warranty period or thirty (30) days, whichever is longer.
No Other Warranties
To the maximum extent permitted by applicable law , Jupiter Systems disclaims all other warranties, either
expressed or implied, including but not limited to implied warranties of merchantability and fitness for a
particular purpose, with regard to the SOFTWARE and the accompanying written materials.
No Liability for Consequential Damages
To the maximum extent permitted by applicable law, in no event shall Jupiter Systems or its suppliers be
liable for any damages whatsoever (including without limitation, special, incidental, consequential, or
indirect damages for personal injury, loss of business, profits, business interruption, loss of business
information, or any other pecuniary loss) arising out of the use of or inability to use this product, even if
Jupiter Systems has been advised of the possibility of such damages. In any case, Jupiter Systems’ entire
liability under any provision of this agreement shall be limited to the amount actually paid by you for the
SOFTWARE.
viPixelNet Domain Control User Manual
Using this Manual
Using this Manual
Introduction
Chapter titles are at the top of every page to assist you in finding sections.
The Table of Contents is a section, chapter, and heading outline of the
manual; whereas, the comprehensive index at the end of the manual
guides you through a search of subjects, figures, and tables.
Note and Caution
This manual uses two special entries to get your attention:
• Note
• Caution
These entries are listed in their ascending order of importance. The
examples shown are found throughout this manual.
NoteNotes are entries that bring your attention to specific items
that you must see, read, and understand before continuing.
Caution Cautions are entries that alert you to items that may cause
the operating system to not operate properly. For instance,
tasks that were either done out of sequence or not
supposed to be done at all may cause the system to
malfunction. Cautions also alert you about physical
connections that can cause the system to not operate
properly.
PixelNet offers a new and revolutionary way to capture, distribute, display,
and control digital and analog video streams. PixelNet input nodes capture
a wide variety of source signals and output nodes display them
simultaneously on a single display or display wall.
PixelNet Domain Control User Manual1
1—Introduction to PixelNet
The PixelNet distributed node system is one of the chief advantages of
using individual input and output nodes. This distributed node system
allows installation of nodes at the signal source and/or display device.
This distributed network system allows for simple Cat 6 cabling
between sources, displays, and the PixelNet Switch rather than
expensive analog or digital cables.
Based on a switched, proprietary network, PixelNet consists of input nodes
and output nodes that connect through a PixelNet Switch to a display wall
via standard Cat 6 network cabling. PixelNet makes creating complex
topologies of inputs, outputs, and display walls simple, inexpensive, and
future proof.
PixelNet
has the ability to capture the wide variety of source signals found
within a control room, and display them simultaneously on a display wall,
ancillary displays, even across multiple rooms. Based on standard Cat 6
cabling, PixelNet input and output nodes can be placed as far as 100m
from a PixelNet Switch. A PixelNet network automatically configures in the
field, every input node is visible to each output node.
All of this power and flexibility is managed by Jupiter’s PixelNet Domain
Control (PDC) software, providing an intuitive, object-oriented, drag-anddrop interface to control and manage multiple inputs, outputs and display
walls.
Key Terms
Node - An active electronic device that is attached to a network, and is
capable of sending, receiving, or forwarding information over, to, or from
that network.
PixelNet Domain – An interconnected set of switches and PixelNet nodes
creating a non-blocking set of gigabit ports to which the PixelNet nodes are
connected. Organized and managed via PixelNet Domain Control software.
Non-Blocking – The non-blocking PixelNet switch provides for switching
such that multiple paths through the switch do not affect each other nor
any other path in the switch. Full bandwidth is always realized through the
switch.
2PixelNet Domain Control User Manual
Outstanding Visual Quality
1.1 Outstanding Visual Quality
PixelNet captures video signals at full resolution, frame rate, and color
depth assuring exceptional visual performance.
Format conversion, de-interlacing, scaling, noise-reduction and colorspace conversion are all performed automatically for the user within
PixelNet – resulting in perfect representation regardless of input signal or
display device.
PixelNet’s output node, TeamMate, can display a single or multiple sources
in freely scalable windows, or multiple TeamMate nodes can be combined
together to create a display wall of virtually any size with source windows
being able to span one or all displays. All TeamMate nodes connected to
PixelNet have access to all connected inputs.
1.2 The PixelNet Difference
The PixelNet Network is a high-bandwidth, non-blocking switched network.
Data transmission from one PixelNet node to another is completely
independent of other communicating nodes. Networks are automatically
self-organizing, and PixelNet nodes exchange visual data in a common,
digital format. Nodes have very long Mean Time Between Failure (MTBF). A
failed node can easily be replaced.
All connections between nodes and switches are made using common
Cat 6 cables up to 100 meters in length. PixelNet is completely digital in
nature, and with digital input sources such as a DVI computer source or
SDI video, the network can be digital end-to-end, resulting in the best
possible visual performance. Video signals are enhanced through the use
of superior video processing technology for de-interlacing and antialiasing. The result is a broadcast-quality display. Any application will
benefit from the simple installation and superb visual performance of a
PixelNet network.
1.3 Multiple Wall Support
With PixelNet, it is now possible to manage multiple displays in widely
separated locations, and to control them independently. This new feature
expands the boundaries of any given PixelNet domain and can include
many display walls. Content is no longer confined to a single display wall;
it can now be presented in more than one place on a variety of display
types.
PixelNet Domain Control User Manual3
1—Introduction to PixelNet
1.4 Window Borders and Titles
PixelNet now offers options to apply colored borders to any window on the
display wall and add titles to the borders using a text editor. Window
layouts can be saved and instantly recalled on the wall, including the
borders and titles.
1.5 Nodes
1.5.1 DVI-I Input Node
Jupiter Systems designed the DVI-I Input Node to capture analog (RGB)
and digital progressive scan (DVI) signals from graphical outputs of other
computers. Resolutions up to 2048 x 1200 and a pixel clock up to 165 MHz
are supported.
The DVI-I input node supports analog and digital loop-through from the
source to a display or another input node. The DVI-I input node
automatically detects incoming signal formats for plug-and-play simplicity .
Each input node contains two gigabit PixelNet ports.
1.5.2 HD Component Input Node
The HD Component Input Node is designed to capture incoming SDTV
(NTSC/PAL/SECAM) and HDTV (ATSC) signals, and accepts analog
component inputs (YPrPb). This is an audio-capable input node that
supports stereo and 5.1 encoding formats: 48KHz, 44.1KHz, 24bit.
The HD Component input node automatically detects incoming signal
formats for plug-and-play simplicity. Each input node contains two gigabit
PixelNet Ports.
1.5.3 3G-SDI Input Node
The 3G-SDI Input Node is designed to support 3G-, HD-, and SD-SDI
signals—3G (1080 p), HD (720 p, 1080i), and SD (480 i/p, 576 i/p)—at 50
or 60 fps. This is an audio-capable input node that supports stereo and 5.1
encoding formats: 48KHz, 44.1KHz, 24bit.
The 3G-SDI input node provides SDI signal loop-through and 10-bit color
processing. Similar to the other input nodes, the 3G-SDI input node
automatically detects incoming signal formats for plug-and-play simplicity .
Each input node contains two gigabit PixelNet Ports.
4PixelNet Domain Control User Manual
PixelNet Switches
1.5.4 Quad CVBS-Y/C Input Node
The Quad Composite Video Broadcast Standard and S-Video (CVBS-Y/C)
Input Node is designed to support SD signals—SD (480 i, 576 i)—at 25 or
30 fps. This input node handles NTSC/PAL/SECAM composite and S-Video
signals. This node allows for four channels to be processed simultaneously.
1.5.5 TeamMate Output Node
Jupiter Systems designed the TeamMate Output Node to provide DVI and
analog display signals to graphical display devices (such as flat-panels,
projectors, cubes, etc.) Resolutions up to 2048 x 1200 and a pixel clock up
to 165 MHz are supported.
The T eamMate output node provides for an optional FrameLock, wherein all
output nodes are connected to a single SYNC signal. In a display wall
environment, there will be one master SYNC output node supplying the
SYNC signal to all other output nodes. Each output node contains two
gigabit PixelNet Ports.
1.5.6 Audio Output Node
The PixelNet Audio output node routes audio associated with video data
captured at audio-capable PixelNet input nodes (the 3G-SDI and HD
Component input nodes). Audio configurations are saved as part of
PixelNet Domain Control layouts and are automatically recalled when the
associated layout is selected. Unlike other solutions, PixelNet users will be
able to both see and hear a source, managing the two capabilities through
a drag-and-drop interface.
Digital audio can be transferred optically over fiber optic TOSLINK (Toshiba
LINK) F05 connectors or Bayonet Neill-Concelman (BNC) 75 Ohm coax
cables can be used. Also, the AES-3id standard is supported.
1.6 PixelNet Switches
Each PixelNet Network requires the use of at least one 48-port PixelNet
Switch. PixelNet switches are based on a proprietary switching network
and can not be used within a standard Ethernet network.
PixelNet Domain Control User Manual5
1—Introduction to PixelNet
1.7 PixelNet Domain
A PixelNet Domain is a network configuration that consists of a
combination of input nodes, output nodes, one or more PixelNet switches,
and a PixelNet Domain Server running PixelNet Control Software.
1.8 PixelNet Domain Server
In order to run the PixelNet Domain Control Software, the PixelNet Domain
Server requires a dedicated gigabit Ethernet port with jumbo packet
support. Furthermore, all of the items shown in the Connection Properties list must be disabled (unchecked), before using the Server.
6PixelNet Domain Control User Manual
Chapter 2—PixelNet Hardware
2. PixelNet Hardware
2.1 Hardware Overview
This chapter describes the hardware characteristics of the PixelNet DVI-I
input node (“Figure 1”), the PixelNet HD Component input node
(“Figure 2”), PixelNet 3G-SDI input node (“Figure 3” on page 8),
Quad CVBS-Y/C input node (“Figure 4” on page 8), PixelNet output
node (“Figure 5” on page 8), and the 48-port PixelNet Switch (“Figure
15” on page 19).
Figure 1 - PixelNet DVI-I Input Node Front Panel
PixelNet Domain Control User Manual7
2—PixelNet Hardware
Figure 2 - PixelNet HD Component Input Node Front Panel
Figure 3 - PixelNet 3G-SDI Input Node Front Panel
Figure 4 - PixelNet Quad SD Input Node Front Panel
Figure 5 - PixelNet Output Node Front Panel
8PixelNet Domain Control User Manual
Hardware Overview
Figure 6 - PixelNet Audio Output Node Front Panel
2.1.1 LED Behavior
The PixelNet nodes contain four LEDs—Active, Input, Output, and Fault.
The Active, Input, and Output LEDs must be interpreted in conjunction
with the Fault LED color.
2.1.1.1 Fault LED
The Fault LED colors (red, yellow, and green) indicate the node’s functional
status through its Power-up, Operational, and Fault modes.
Power-up Mode
As the node powers-up, the Fault LED remains yellow. If the Fault LED
turns red, the node is experiencing internal or power problems. During
startup the active, input, and output LEDs will flash through different
colors.
Operational Mode
Once the power-up is complete, the node is in operating mode. The Fault
LED turns green.
Fault Mode
When the Fault LED is red, the node is not functioning and is in a fault
mode. Attempt a power-cycle of the node; if Fault LED is still red, contact
Jupiter Technical Support for assistance.
2.1.1.2 Active, Input, and Output LEDs
When the Fault LED is Red:
The Active, Input, and Output LEDs will show a specific static display of
red, yellow, green, and off. You should make a note of this LED display
sequence and call Jupiter Technical Support so that we can decipher the
Fault code and resolve the issue.
PixelNet Domain Control User Manual9
2—PixelNet Hardware
When the Fault LED is Yellow:
The Active, Input, and Output LEDs will show a combination of LED
displays while the node is in the process of powering up.
NoteSo far, the LED behavior has been the same for both the
Input and Output nodes. However, when the Fault LED is
green the LED behavior changes depending on whether it is
an Input or Output node.
When the Fault LED is Green:
In an input node:
• The Input LED is green when it has a valid signal, or yellow if the
source is not detected.
• The Active LED is green when actively processing data or yellow
when idle.
• The Output LED is green when it is sending packets (a data
stream) or yellow when idle.
In an output node:
• The Output LED is green when it is connected to a display device
• The Active LED is green when actively processing data or yellow
when idle.
• The Input LED is green when it is receiving packets (a data
stream) or yellow when idle.
2.2 HD Component Input Node
• Supports SDTV (NTSC/PAL/SECAM) and HDTV (NTSC)
• Provides analog component inputs (YPrPb)
• Provides automatic format detection for plug-and-play simplicity
• Provides two gigabit PixelNet ports
10PixelNet Domain Control User Manual
DVI Input Node
Y
Input
Pb
Input
Pr
Input
Figure 7 - HD Input Node Rear View
2.3 DVI Input Node
• Captures signals up to 2048 x 1200 resolution and up to 165 MHz
pixel rate
• Captures analog or digital progressive scan signals
• Supports analog-to-analog and digital-to-digital loop-through
• Provides choice of external (loop-through) or internal EDID
• Provides automatic format detection for plug-and-play simplicity
• Provides two gigabit PixelNet ports
“Figure 8” on page 12 shows the rear panel of the DVI input node.
Cable connections are also indicated in the figure. Note that the USB port
is reserved for future capabilities. The node is also capable of providing a
duplicate of the input signal. The signal type presented at the SIGNAL IN
connector DVI-I (DVI-D or analog RGB) will be duplicated at the SIGNAL
OUT connector, i.e. analog-to-analog or digital-to-digital. This allows a
monitor connected to the SIGNAL OUT connector to receive the same
signals present at the SIGNAL IN.
Left, Right, and Coaxial
audio connections
PixelNet
Port 1
PixelNet
Port 2
Power
PixelNet Domain Control User Manual11
2—PixelNet Hardware
DVI-I
Input
E D I D
Switch
Figure 8 - DVI Input Node View
DVI-I
Input
USB not currently
supported
PixelNet
Port 1
PixelNet
Port 2
Power
2.3.1 EDID Switch
Display Data Channel (DDC) is a communication standard used by graphics
channels of PCs to talk to monitors. The DDC uses the Extended Display
Identification Data (EDID) to find out information about what the system
supports regarding preferred resolution and color depth.
The EDID Switch allows two settings, left and right, the operation of the
DVI-I input node depends on the following criteria:
• When a monitor is connected to Signal Out (with the switch to
the left towards the monitor icon), the PC connected to the
Signal In connector requests the monitor for the EDID table and
verifies the information so that an acceptable resolution value is
used by the PC. This resolution will also be used by the DVI-I
input node.
• With the switch to the right towards the crossed-out monitor
icon, the PC connects to an internal chip in the node with a builtin EDID table to get information about the maximum resolution
that the node will support.
12PixelNet Domain Control User Manual
3G-SDI Input Node
2.4 3G-SDI Input Node
• Supports 3G-, HD-, and SD-SDI signals:
• 3G (1080 p), HD (720 p, 1080 i), and SD (480 i/p, 576 i/p)—at
50 or 60 fps
• Supports automatic format detection for plug-and-play simplicity
• Provides SDI signal loop-through
• Provides 10 bit color processing
• Provides two gigabit PixelNet ports
Signal InSignal OutPixelNet
Figure 9 - PixelNet 3G-SDI Input Node Rear View
Port 1
PixelNet
Port 2
Power
“Figure 9” on page 13 shows the rear panel of the 3G-SDI input node.
Cable connections are also indicated in the figure. The 3G-SDI input node
also provides loop through output. The signal type presented at the
SIGNAL IN connector will be duplicated at the SIGNAL OUT connector.
PixelNet Domain Control User Manual13
2—PixelNet Hardware
2.5 Quad CVBS-Y/C Input Node
• Supports SD signals:
• SD (480 i, 576 i)—at 25 or 30 fps
• Handles NTSC/PAL/SECAM components, and S-Video signals
• Supports automatic format detection for plug-and-play simplicity
• Provides 8-bit 4:2:2 color processing
• Provides two gigabit PixelNet ports
C1
Chromi-
nance
S-VideoS-Video
Figure 10 - Quad CVBS-Y/C Input Node Rear View
Y1
Luminance
C2
Chromi-
nance
Y2
Lumi-
nance
PixelNet
Port 1
PixelNet
Port 2
Power
“Figure 10” on page 14 shows the rear panel of the Quad-CVBS-Y/C
input node. This node allows for four channels (combination of composite
or S-Video signals) to be processed simultaneously. Cable connections are
indicated in the figure; either up to two S-Video (YC1 and YC2) or up to
four composite (1, 2, 3, and 4). When an S-Video signal is connected, the
corresponding composite capability is removed, for instance, using Y1 and
C1 disables composite 1 and 2.
14PixelNet Domain Control User Manual
TeamMate Output Node
2.6 TeamMate Output Node
• Supports DVI or Analog display outputs
• Supports output resolutions up to 2048 x 1200 or 165 MHz pixel
clock
• Provides two gigabit PixelNet ports
• Provides optional FrameLock, connecting all output nodes to a
single SYNC signal
SYNCDVI-I Output USB not currently
supported
Figure 11 - PixelNet Output Node Rear View
PixelNet
Port 1
PixelNet
Port 2
2.6.1 SYNC Port
The output node sync port provides for synchronizing all output node
signals to the displays. Use this if you want all the output nodes in your
configuration to be tied to a single sync signal. Synchronization allows for
full motion video with no tearing of image at display boundaries.
The first output node of a display wall will be configured as a master; by
default, all the other nodes will be configured as slaves. The master output
node is configured with the PixelNet Domain Control software.
2.6.1.1 Distribution Amplifier (DA)
Up to ten output nodes can be used in a simple configuration—one master,
nine slaves. More complex systems with more than ten output nodes are
possible with a high-bandwidth Distribution Amplifier (DA). Each DA port
can support up to ten output nodes. Also, more than one DA can be daisychained from the first DA. The DA is available as a PixelNet option.
Power
PixelNet Domain Control User Manual15
2—PixelNet Hardware
The following figure shows the basic daisy-chain connections for the Sync
Port. Every node requires a T-Connector. Every branch of the T-Connector
will be connected. Each end of the daisy-chain has a 75 Ohm terminator
attached.
Figure 12 - Output Node Basic Sync Connections
16PixelNet Domain Control User Manual
Loading...
+ 221 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.