Get in touch to discuss becoming an Authorised Dealer:Contact Us
HDANYWHERE HDMI Extender, 4K to 100M, 1080P to 150M, POE, 2-way IR, RS232 pass-thru
XTND4K100TPC2 (No ARC)
HDANYWHERE, HDMI Extenders, HDMI Extenders
(click to expand)
A long-range super-slim and ultra-lightweight HDMI 2.0 / HDBaseT 2.0 extender set - supports 18Gbps premium UHD/4K 60Hz 4:4:4 data rates, with all current HDR formats inc. Dolby Vision®, HDR10 and HLG up to 100 metres, over one twisted pair Cat cable.
A de-embed stereo audio output port is available on the RX for as a helpful connection option for amplifiers or soundbars etc. Control via two-way IR or RS232 available on the receiver.
Tipping Point Compression w/DSC enables the transmission of 18Gbps content via HDBaseT 2.0 technology, with no human-perceivable difference in video quality. TPC can handle all HDR formats, including Dolby Vision, retaining all original HDR Meta and is compatible with all chroma subsampling and colour space options (4:4:4, 4:2:2, and 4:2:0).
(Product Code: XTND4K100TPC2 SKU: 2.50.887)
Improve your multiroom HD smart home experience with the HDanywhere Control app for phone or tablet.
Watch TV your way
Optimised for all devices
HDanywhere video distribution systems require a single network cable to be run from each HDTV location, back to a central point. Some single wire systems use HDBaseT technology to transmit over 1 x Cat5e/6/7 cable up to a 100 Metre distance.
This article is designed to give you a good overview of the standard of wiring needed for a HDBaseT system.
HDBaseT is a transmission technology widely used for whole-home and commercial distribution of uncompressed HD multimedia content. The cornerstone of HDBaseT technology is 5Play™, a feature set made up of five key things that are sent over a single Cat cable:
Currently you can use Cat5e, Cat6, Cat6e, Cat6a, Cat7 or Cat7a with HDanywhere HDBaseT-based products. The baseline cable standard for HDanywhere systems is Cat5e. Slightly greater distances can be achieved by using Cat6, or slightly better still with the Cat7, which have thicker copper cores for easier signal transfer.
DO NOT USE COPPER CLAD ALUMINIUM (CCA) Cat 5/6/7 CABLE FOR HDBASET PRODUCTS.
Whichever network cable type you choose, ensure that the main wiring architecture is ‘solid core’, not stranded ‘patch’ cabling. Patch cabling can be used for the last few metres of a run (say from a wallplate) but should be avoided over the longer runs as signal transfer over stranded cores is heavily reduced.
The use of pre-made leads is not recommended unless you can be absolutely sure of their construction credentials (i.e. solid core 568B)
Unlike other systems, shielded FTP cable is not a stipulation. If however you preferred this type of cable please ensure compatible shielded accessories are used. Failure to terminate cable screen at all points can induce interference rather than eliminating it.
Best practice advice is to always use a straight piece of cable terminated directly at the matrix and the receiver ends.
If the patch panels are terminated correctly and well, there is minimal loss of distance with HDBaseT.
The use of wallplates and patch panels always has the potential to cause increased resistance on the cable, introducing ‘pinch points’ for signal transmission and could reduce advertised transmission lengths.
TIP – instead of using RJ45 wallplates, use brush plates instead to maintain the neat finish. A search for “brush plates” will yield many results.
HDBaseT is not a signal type that can travel over powerline/homeplug network extension systems.
Terminate the cabling using RJ45 connectors to the 568B wiring standard (shown below).
Check that the Cat cable is not bent, knotted, kinked or distorted in any way that would prevent these high frequency signals from traveling throughout the intended length.
Also, ensure that the cables as far away from potential sources of EMI (Electro-Magnetic Interference) such as electrical cables, transformers, light fixtures, etc.) as possible. Cables should maintain a 300mm separation from power cables.
Try re-terminating the RJ45 connectors again, making absolutely sure that every termination is perfect. Ensure that the RJ45 connectors are fully inserted and click locked into place firmly and securely to ensure perfect connector connection
DO maintain the twists of the pairs as close as possible to the point of termination, or no more than 13mm untwisted.
DO make only gradual bends in the cable where necessary to maintain the minimum bend radius of 4 times the cable diameter or approximately 30mm radius.
DO use low-to-moderate force when pulling cable. The standard calls for a maximum of 34 N-m (newton-metres of force).
DO use cable pulling lubricant for cable runs that may otherwise require great force to install. (You will be amazed at what a difference the cable lubricant will make)
DO keep Category cables as far away from potential sources of EMI (Electro-Magnetic Interference) such as electrical cables, transformers, light fixtures, etc.) as possible. Cables should maintain a 300mm separation from power cables.
DON’T allow the cable to be sharply bent, twisted, or kinked at any time. This can cause permanent damage to the geometry of the cable and cause transmission failures.
DON’T over-tighten cable ties or use plastic ties.
DON’T EVER splice or bridge Category cable at any point.
DON’T use excessive force when pulling cable.
DON’T use oil or any other lubricant not specifically designed for Category network cable pulling as they can infiltrate the cable jacket, causing damage to the insulation.
DON’T tie cables to electrical conduits, or lay cables on electrical fixtures
DON’T install cables taut. A good installation should have the cables loose, but never sagging.
DON’T use staples on Category cable that crimp the cable tightly. The common T-18 and T-25 cable staples are not recommended for Category cable. However, the T-59 insulated staple gun is ideal for fastening both Category and fibre optic cabling, as it does not put any excess pressure on the cable.
DON’T use patch cords (cables) or punch down blocks.