Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| tech [2026/03/24 06:18] – neds | tech [2026/04/11 01:39] (current) – neds | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== SiliconDust TECH manual ====== | ====== SiliconDust TECH manual ====== | ||
| - | < | + | < |
| ===== Hardware ===== | ===== Hardware ===== | ||
| <WRAP indent> | <WRAP indent> | ||
| + | ==== Current models ==== | ||
| + | <WRAP indent> | ||
| + | |||
| + | ^ Model numbers | ||
| + | ^ TECH5-16US-4X4 | 16 (4 modules of 4 tuners) | ATSC 1.0, QAM64/256 | 1U 19" rack-mount | | ||
| + | | | //Power supply information and other notes:// \\ ||| | ||
| + | ^ TECH5-16DT-4X4 | 16 (4 modules of 4 tuners) | DVB-T1, DVB-T2, DVB-C | 1U 19" rack-mount | | ||
| + | | | //Power supply information and other notes:// \\ ||| | ||
| + | ^ TECH-4K | 4 (1 module of 4 tuners) | **Tuners 0+1:** ATSC 3.0, ATSC 1.0, QAM64/256 \\ **Tuners 2+3:** ATSC 1.0, QAM64/256 | 3.4" | ||
| + | | | //Power supply information and other notes:// \\ < | ||
| + | ^ TECH5-4K8-2X4 | 8 (4 modules of 2 tuners) | ATSC 3.0, ATSC 1.0, QAM64/256 | 1U 19" rack-mount | | ||
| + | | | //Power supply information and other notes:// \\ ||| | ||
| + | |||
| + | </ | ||
| + | ==== Past models (still supported) ==== | ||
| + | <WRAP indent> | ||
| + | |||
| + | <button collapse=" | ||
| + | |||
| + | < | ||
| + | |||
| + | ^ Model numbers | ||
| + | | TECH-US | | ||
| + | | TECH3-US | | ||
| + | | TECH3-8US-2X4 | | ||
| + | | TECH4-2US | | ||
| + | | TECH4-8US-2X4 | | ||
| + | | TECH4-8IS-2X4 | | ||
| + | | TECH3-EU | | ||
| + | | TECH3-8EU-2X4 | | ||
| + | | TECH4-2DT | | ||
| + | | TECH4-8DT-2X4 | | ||
| + | | TECH3-6CC-3X2 | | ||
| + | | TECH3-3CC | | ||
| + | | TECH3-8DC-4X2 | | ||
| + | | TECH5-16DC-4X4 | | ||
| + | </ | ||
| + | |||
| + | </ | ||
| + | ==== LEDs and ports ==== | ||
| + | <WRAP indent> | ||
| + | |||
| + | |||
| + | |||
| + | </ | ||
| + | ==== Power ==== | ||
| + | <WRAP indent> | ||
| + | |||
| + | All devices should be used with the included power supply or power cable. | ||
| + | |||
| + | </ | ||
| ==== Ethernet ==== | ==== Ethernet ==== | ||
| <WRAP indent> | <WRAP indent> | ||
| Line 25: | Line 76: | ||
| <WRAP indent> | <WRAP indent> | ||
| - | Download and install the latest Windows release of the HDHomeRun software: https:// | + | Download and install the latest Windows release of TECH Setup utility: https:// |
| The HDHomeRun Setup wizard is optional. | The HDHomeRun Setup wizard is optional. | ||
| Line 35: | Line 86: | ||
| <WRAP indent> | <WRAP indent> | ||
| - | Download and extract the libhdhomerun archive. | + | Download and extract the libhdhomerun archive: https:// |
| Run " | Run " | ||
| Line 110: | Line 161: | ||
| < | < | ||
| / | / | ||
| - | / | + | / |
| - | / | + | / |
| - | / | + | / |
| / | / | ||
| / | / | ||
| Line 120: | Line 171: | ||
| /sys/ipaddr dhcp|"< | /sys/ipaddr dhcp|"< | ||
| / | / | ||
| - | / | + | / |
| / | / | ||
| / | / | ||
| Line 132: | Line 183: | ||
| / | / | ||
| / | / | ||
| - | / | + | / |
| - | / | + | / |
| + | / | ||
| + | / | ||
| + | / | ||
| </ | </ | ||
| </ | </ | ||
| Line 189: | Line 243: | ||
| </ | </ | ||
| - | ==== Tuning a virtual channel | + | ==== Tuning a virtual channel ==== |
| <WRAP indent> | <WRAP indent> | ||
| + | TECH3-CC, TECH4, and later models support tuning by virtual channel number. | ||
| To set a virtual channel use the set vchannel command: | To set a virtual channel use the set vchannel command: | ||
| Line 322: | Line 377: | ||
| <WRAP indent> | <WRAP indent> | ||
| - | TECH3 and later supports automatic | + | Automatic |
| <WRAP indent> | <WRAP indent> | ||
| Line 417: | Line 472: | ||
| </ | </ | ||
| - | The target machine must be listening on the given UDP port. The TECH3 will automatically clear the target if a ICMP port unreachable message is received when sending to a unicast address. To override this, add no_clear to the target. | + | The target machine must be listening on the given UDP port. The TECH will automatically clear the target if a ICMP port unreachable message is received when sending to a unicast address. To override this, add no_clear to the target. |
| <WRAP indent> | <WRAP indent> | ||
| Line 500: | Line 555: | ||
| </ | </ | ||
| - | ===== HTTP Streaming | + | ===== HTTP Streaming ===== |
| <WRAP indent> | <WRAP indent> | ||
| - | TECH3-6CC-3x2 models can be used to stream via HTTP (unicast only) to VLC or other clients. | + | <btn type=" |
| + | |||
| + | TECH3-CC, TECH4, and later models can be used to stream via HTTP (unicast only) to VLC or other clients. | ||
| <WRAP indent> | <WRAP indent> | ||
| Line 510: | Line 567: | ||
| </ | </ | ||
| </ | </ | ||
| + | |||
| + | </ | ||
| + | |||
| + | ===== Lineup file ===== | ||
| + | <WRAP indent> | ||
| + | TECH3-CC, TECH4, and later models support virtual channel lineup information. This is available in XML and JSON format. | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | http://< | ||
| + | http://< | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | </ | ||
| + | |||
| + | ===== Datacast operation ===== | ||
| + | <WRAP indent> | ||
| + | |||
| + | TECH units support Datacast TCP/IP over OTA broadcast. Datacasting often provides news, weather, traffic, stock market, and other information which may or may not relate to the program[s] it is carried with. An electronic program guide is usually included. Datacast TCP-IP packets are reassembled and then routed to the LAN port. | ||
| + | |||
| + | Example: | ||
| + | |||
| + | Discover the device: | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | hdhomerun_config discover | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Set the physical channel: | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | hdhomerun_config FFFFFFFF set / | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Set the datacast PID: | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | hdhomerun_config FFFFFFFF set / | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Set the target: | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | hdhomerun_config FFFFFFFF set / | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | </ | ||
| + | |||
| + | ===== Boot scripts ===== | ||
| + | <WRAP indent> | ||
| + | |||
| + | The /sys/boot variable allows the TECH unit to automatically set variables at startup, allowing you to preserve settings across power outages or simply set the power on defaults. | ||
| + | |||
| + | The syntax for the /sys/boot consists of multiple lines of text; a variable name followed by a single space and then the value: (there should not be any space before the variable name) | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | ... | ||
| + | < | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Example (save as boot.txt): | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | To place a wait period between commands you can use the " | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | <first command> | ||
| + | |||
| + | sleep 60 | ||
| + | |||
| + | <next command> | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | |||
| + | To store the configuration to the device: | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | Format: hdhomerun_config <id> set /sys/boot - < filename | ||
| + | Example: hdhomerun_config FFFFFFFF set /sys/boot - < boot.txt | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Changes will be applied the next boot; to execute the new /sys/boot immediately: | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | Format: hdhomerun_config <id> execute | ||
| + | Example: hdhomerun_config FFFFFFFF execute | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | </ | ||
| + | ===== Static IP assignment ===== | ||
| + | <WRAP indent> | ||
| + | |||
| + | A static IP address can be configured using the following command (the quotes are required as shown): | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | Format: hdhomerun_config <old ip> set /sys/ipaddr "< | ||
| + | Example: hdhomerun_config 169.254.34.98 set /sys/ipaddr " | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Note: The TECH requires a gateway when used to stream multicast, even if on the same subnet. | ||
| + | |||
| + | ==== Reverting to DHCP ==== | ||
| + | <WRAP indent> | ||
| + | |||
| + | The TECH can be configured for DHCP operation (default) using the following command: | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | Format: hdhomerun_config <old ip> set /sys/ipaddr dhcp | ||
| + | Example: hdhomerun_config 169.254.34.98 set /sys/ipaddr dhcp | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | <WRAP info> | ||
| + | If you cannot access the TECH due to the IP address change, do the following to reset: | ||
| + | |||
| + | Set a static IP on the computer in the 169.254.x.y range (e.g. 169.254.1.9) with a 255.255.0.0 subnet mask. The auto IP address for the TECH device will be randomly chosen within the 169.254.x.y range. Use the [[https:// | ||
| + | </ | ||
| + | |||
| + | </ | ||
| + | |||
| + | </ | ||
| + | |||
| + | ===== Setting the channel map ===== | ||
| + | <WRAP indent> | ||
| + | |||
| + | The channel map is a non-volatile configuration option that is used to set the channel to frequency table, to configure the channel scan table, and to optimize the auto-modulation detection. | ||
| + | |||
| + | GUI: The channel map can be set for each tuner by running HDHomeRun Config (GUI). | ||
| + | |||
| + | Command line: The channel map can be set for each tuner using the following command: | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | Format: hdhomerun_config < | ||
| + | Example: hdhomerun_config 10001000 set / | ||
| + | Example: hdhomerun_config 10001000 set / | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Channel maps supported by US hardware: | ||
| + | |||
| + | <WRAP indent> | ||
| + | ^ Name ^ Description ^ Location ^ | ||
| + | | us-bcast | Digital Antenna (ATSC). | US, Canada | | ||
| + | | us-cable | Digital Cable - Normal frequency layout. | US, Canada | | ||
| + | | us-hrc | Digital Cable - HRC frequency layout. | US, Canada | | ||
| + | | us-irc | Digital Cable - IRC frequency layout. | US, Canada | | ||
| + | </ | ||
| + | |||
| + | Channel maps supported by DVB hardware: | ||
| + | |||
| + | <WRAP indent> | ||
| + | ^ Name ^ Description ^ Location ^ | ||
| + | | au-bcast | Digital Antenna (Australia). | Australia | | ||
| + | | au-cable | Digital Cable (Australia). | Australia | | ||
| + | | eu-bcast | Digital Antenna (Europe). | Europe, New Zealand | | ||
| + | | eu-cable | Digital Cable (Europe). | Europe, New Zealand | | ||
| + | | tw-bcast | Digital Antenna (Taiwan). | Taiwan | | ||
| + | | tw-cable | Digital Cable (Taiwan). | Taiwan | | ||
| + | </ | ||
| + | |||
| + | </ | ||
| + | ===== Multicast ===== | ||
| + | <WRAP indent> | ||
| + | |||
| + | TECH supports multicast streaming within a network. | ||
| + | |||
| + | - Using HDHomeRun Config GUI or hdhomerun_config choose a desired channel and program number for each tuner. In this example we will use channel 19 program 3 on tuner 0 and channel 30 program 1 on tuner 1. | ||
| + | - Choose a multicast IP address for each stream. As a general rule the multicast address should be in the range of 239.255.0.0 to 239.255.255.255. In this example we will use 239.255.1.1 and 239.255.1.2 | ||
| + | - Choose a destination (client) port number. The port should be outside the the well-known ports range (we recommend 50000+) and should be unique for each stream. In this example we will use 59001 and 59002. | ||
| + | - Write the boot script (text file):< | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | |||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | - Write the boot script to the device: < | ||
| + | - Execute the boot script: < | ||
| + | - Check the tuner status and target for each tuner. The packets-per-second “pps” number should be non-zero indicating that the device is sending the stream. < | ||
| + | hdhomerun_config 10010003 get / | ||
| + | hdhomerun_config 10010003 get / | ||
| + | hdhomerun_config 10010003 get / | ||
| + | |||
| + | </ | ||
| + | ===== Example Boot Script Configurations ===== | ||
| + | <WRAP indent> | ||
| + | |||
| + | Tuning 2 ATSC channels and streaming to multicast addresses using RTP: | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Tuning 3 digital cable channels using a CableCARD and streaming to multicast addresses using RTP: | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Tuning 2 DVB-T channels in Australia and streaming to multicast addresses using UDP: | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Tuning 2 DVB-C channels in Europe and streaming to a single PC, ignoring rejection messages from the PC due to a closed port: | ||
| + | |||
| + | <WRAP indent> | ||
| + | < | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | </ | ||
| + | ===== HDHomeRun app ===== | ||
| + | <WRAP indent> | ||
| + | |||
| + | {{ : | ||
| + | When using the TECH3-CC or TECH4 and later, the consumer [[: | ||
| + | |||
| + | - Access the web interface of the TECH unit //(for example, < | ||
| + | - Check the option **" | ||
| + | - All other features of the TECH can still be used in this mode. | ||
| + | |||
| + | <WRAP clear/> | ||
| </ | </ | ||