33
1.877.877.2269
BLACKBOX.COM
NEED HELP?
LEAVE THE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
PROBLEM: THE MOUSE POINTER OF THE AGILITY RECEIVER IS SLOW OR SLUGGISH WHEN MOVED ACROSS THE
SCREEN.
This issue is often related to either using dithering on the video output of one or more transmitting computers or using video
converters.
Dithering is used to improve the perceived quality and color depth of images by diffusing or altering the color of pixels between
video frames. This practice is commonly used on Apple Mac computers using ATI or Nvidia graphics cards. VGA converters
unwittingly produce a similar issue by creating high levels of pixel background noise.
Agility units attempt to considerably reduce network traffic by transmitting only the pixels that change between successive
video frames. When dithering is enabled and/or VGA converters are used, this can have the effect of changing almost every pixel
between each frame, thus forcing the Agility transmitter to send the whole of every frame: resulting in greatly increased network
traffic and what’s perceived as sluggish performance.
REMEDIES:
• Linux PCs
Check the video settings on the PC. If the Dither video box option is enabled, disable it.
• Apple Mac with ATI graphics
Enable the Magic Eye dither removal feature.
• Windows PCs
If you suspect these issues with PC’s, contact technical support for assistance.
• Replace old VGA adapters on host computers with DisplayPort or HDMI video cards.
PROBLEM: THE AUDIO OUTPUT OF THE AGILITY RECEIVER SOUNDS LIKE A SCRATCHED RECORD.
This issue is called Audio crackle and is a symptom of the same problem that produces blinding (see previous page). The issue is
related to missing data packets.
REMEDIES:
As per blinding discussed previously.
PROBLEM: IPATH CANNOT LOCATE WORKING AGILITY UNITS.
There are a few possible causes:
• The Agility units must be reset back to their zero config IP addresses for IPATH discovery. If you have a working network of
Agility’s without IPATH and then add IPATH to the network IPATH will not discover the Agility units until they are reset to the
zero config IP addresses.
• This could be caused by Layer 2 Cisco switches that have
enabled but do not also have
portfast
enabled on the ports to which Agility units are connected. Without portfast enabled, Agility units will all be assigned the same
zero config IP address at reboot and IPATH will only acquire them one at a time on a random basis.
You can easily tell whether portfast is enabled on a switch that is running STP: When you plug the link cable from a working
Agility unit into the switch port, check how long it takes for the port indicator to change from orange to green. If it takes roughly
one second, portfast is on; if it takes roughly thirty seconds then portfast is disabled.
REMEDIES:
• Ensure that the Agility units and the IPATH Agility Controller are located within the same subnet because iPATH cannot cross
subnet boundaries.
•
the Agility units to their zero config IP addresses.
• Enable portfast on all switch ports that have Agility units attached to them or try temporarily disabling STP on the switches
while IPATH is attempting to locate Agility units.