When you installing and configuring a headend (both TDX and TDH800), there are some "rules" or "guidelines" you must follow. This is what we call 'Best Practice'. By following these guidelines, you will ensure a more homogeneous and evenly performing headend.
The risk that you will experience congestion on the internal databuses, or errors on modules or CAM will be minimized.
Therefore will we always encourage you to follow these rules/guidelines and we will refer to them if you later need support.
Through the installation of a headend, we will ask you to observe the following points. They will help to ensure the best conditions for signal reception and the environment around the main station.
Location and Ground Connection
Properly ground the TDX chassis (and make sure external equipment connected to the headend, have the same grounding)
- The headend can handle temperatures from -10 ° C to + 50 ° C and humidity up to 80%.
- Ensure that min. 10cm ventilation space is available on both sides and the front of the headend. If you install several headends, Min. 20cm ventilation space must be available between headends.
Connectors / Cables / Dishes
Use only high quality press fit water proof F-connectors.
- Make sure F-connectors are properly fitted, tightened an free of corrosion.
- Use 4G/LTE shielded cables.
- Make sure dish mount is stable, and the dish has an unobstructed line of sight to the satellite.
- Verify signal level (better than -35 dBm) and SNR (better than 12 dBm.
Planning / Configuration
When you are to plan and configure the your headend, we recommend you to follow these rules. They will help you to achieve the best possible mux usage and ensure a higher quality image.
If you wish to have remote access to the headend, please read this article: TDX remote access (Through router/firewall)
TRIAX will never recommend, that you connect any type of equipment directly to the internet (access without a router). Connecting a host directly to the internet will always be considered as 'Bad Practise'. Connecting a switch to you modem/uplink and then the headend to the switch, is also considered as a direct connection.
Connecting a host directly to the internet, exposes the the host and renders it vulnerable to malicious intrusions and attacks. For security reasons, you will always be advised to protect your hosts. You do this, by 'hiding' them behind a router/firewall.
The TDX (or any equipment from Triax) is categorized as host, like your PC, laptop, printer or other networking equipment.
From input modules to output modules
The headend is divided into two internal 'bus'. A right and a left.
Services received on the input modules on the left side and Link0, should preferably be sent out on the output modules on the left side.
- Services received on the input modules on the right side and Link1, should preferably be sent out on the output modules on the right side.
- Avoid mixing services from multiple input modules on an output module. There is a greater likelihood that the various services peaks at the same time. Try to use all services from one input module, on one output module.
- In general, a MUX should not exceed more than ~75% in paylod, as there can be large differences in the data pr. channel, in and outside 'prime time'. Some HD channels can even vary from ~ 8 to ~ 15Mbit/s or more.
From Main Unit to Sub Unit
Services received on a input module should be used on an output module, on the same headend. This applies if you have an installation with multiple units (Main unit with Sub units).
- Descramble services on the unit, where they are to be used.
- Use CA modules of a good quality, with high speed capacity. This will give you more capacity on the modules.
- Descramble services on the same output modules, where they are to be used.
- Preferably descramble services received on one input module, on the same CA module. Not from several input modules.
Under Network, please set the EIT to Full Actual - P/F Other for both DBV-C and DVB-T.
This will reduce EIT data bursts internally in the TDX. These burst may, in worst case, result in pixelisation and glitches.
- Use the prioritization ( prio.1 / prio.2 / prio.3 / prio.4) where services in prio.4 has the lowest priority and will be affected if bandwidth limit is reached.
- Configure network switch port to UDE (UniDirectional Ethernet) to avoid data from the network disturbing the IP-output module. See this article
To sum up the worst errors, here's a list.
- Avoid mixing services from multiple input modules on an output module.
- In general, a MUX should not exceed more than ~75% in payload.
- Do not use the services across units. Use the services 'local'.
- Do not use Full Actual - Full Other under the Network/EIT settings.
- Nerver connect the headend directly to the internet. Use a router with a VPN connection or Port forwarding.