Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tech [2026/03/24 06:15] – nedstech [2026/03/24 06:39] (current) – neds
Line 7: Line 7:
 ==== Ethernet ==== ==== Ethernet ====
 <WRAP indent> <WRAP indent>
 +
 Connect the Ethernet port(s) to a network switch. On models with multiple ports, all ports must be connected in order for all tuners to be accessible. A single port can be directly connected to the network interface on a PC to access that specific device. All ports are auto-crossover so a standard Ethernet cable can be used. Connect the Ethernet port(s) to a network switch. On models with multiple ports, all ports must be connected in order for all tuners to be accessible. A single port can be directly connected to the network interface on a PC to access that specific device. All ports are auto-crossover so a standard Ethernet cable can be used.
  
 </WRAP> </WRAP>
 +
 </WRAP> </WRAP>
 ===== Additional Tools and Software ===== ===== Additional Tools and Software =====
Line 39: Line 41:
 Copy hdhomerun_config to /usr/local/bin Copy hdhomerun_config to /usr/local/bin
  
-</WRAP> 
 </WRAP> </WRAP>
  
 +</WRAP>
 ===== Command Line Utility (hdhomerun_config) ===== ===== Command Line Utility (hdhomerun_config) =====
 <WRAP indent> <WRAP indent>
Line 187: Line 189:
  
 </WRAP> </WRAP>
-==== Tuning a virtual channel (TECH3-6CC only) ====+==== Tuning a virtual channel (TECH3-CC only) ====
 <WRAP indent> <WRAP indent>
  
Line 315: Line 317:
  
 It may take several seconds after setting the channel for the stream information to be fully populated (depending on how long the channel takes to lock and how often the stream information is sent by the broadcaster/cable provider). It may take several seconds after setting the channel for the stream information to be fully populated (depending on how long the channel takes to lock and how often the stream information is sent by the broadcaster/cable provider).
 +
 </WRAP> </WRAP>
 ==== Filtering by program (sub-channel) ==== ==== Filtering by program (sub-channel) ====
Line 414: Line 417:
 </WRAP> </WRAP>
  
-The target machine must be listening on the given UDP port. The TECH3 will automatically clear the +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.
-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 496: Line 497:
 </WRAP> </WRAP>
  
 +</WRAP>
 </WRAP> </WRAP>
  
 +===== HTTP Streaming (TECH3-CC only) =====
 +<WRAP indent>
 +TECH3-CC models can be used to stream via HTTP (unicast only) to VLC or other clients.
  
 +<WRAP indent>
 +<code>
 +Format: http://<ip address of device>:5004/auto/v<vchannel number>
 +Example: http://10.10.10.2:5004/auto/v721
 +</code>
 +</WRAP>
 +
 +</WRAP>
 +
 +===== Lineup file (TECH3-CC only) =====
 +<WRAP indent>
 +TECH3-CC units support virtual channel lineup information transmitted by the cable provider and received via the CableCARD. This is available in XML and JSON format.
 +
 +<WRAP indent>
 +<code>
 +http://<ip address of device>/lineup.xml
 +http://<ip address of device>/lineup.json
 +</code>
 +</WRAP>
 +
 +</WRAP>
 +
 +===== Datacast operation =====
 +<WRAP indent>
 +
 +TECH3 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>
 +<code>
 +hdhomerun_config discover
 +</code>
 +</WRAP>
 +
 +Set the physical channel:
 +
 +<WRAP indent>
 +<code>
 +hdhomerun_config FFFFFFFF set /tuner0/channel auto:651000000
 +</code>
 +</WRAP>
 +
 +Set the datacast PID:
 +
 +<WRAP indent>
 +<code>
 +hdhomerun_config FFFFFFFF set /tuner0/filter 0x0A00
 +</code>
 +</WRAP>
 +
 +Set the target:
 +
 +<WRAP indent>
 +<code>
 +hdhomerun_config FFFFFFFF set /tuner0/target datacast
 +</code>
 +</WRAP>
 +
 +</WRAP>
 +
 +===== Using /sys/boot =====
 +<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>
 +<code>
 +<variable1> <value of variable1>
 +<variable2> <value of variable2>
 +...
 +<variableN> <value of variableN>
 +</code>
 +</WRAP>
 +
 +Example (save as boot.txt):
 +
 +<WRAP indent>
 +<code>
 +/tuner0/channelmap us-cable
 +/tuner0/channel 103
 +/tuner0/program 4
 +</code>
 +</WRAP>
 +
 +To store the configuration to the device:
 +
 +<WRAP indent>
 +<code>
 +Format: hdhomerun_config <id> set /sys/boot - < filename
 +Example: hdhomerun_config FFFFFFFF set /sys/boot - < boot.txt
 +</code>
 +</WRAP>
 +
 +Changes will be applied the next boot; to execute the new /sys/boot immediately:
 +
 +<WRAP indent>
 +<code>
 +Format: hdhomerun_config <id> execute
 +Example: hdhomerun_config FFFFFFFF execute
 +</code>
 +</WRAP>
 +
 +==== Static IP assignment ====
 +<WRAP indent>
 +
 +A static IP address can be configured using the following command (the quotes are required as shown):
 +
 +<WRAP indent>
 +<code>
 +Format: hdhomerun_config <old ip> set /sys/ipaddr "<new ip> <subnet> <gateway>"
 +Example: hdhomerun_config 169.254.34.98 set /sys/ipaddr "10.10.20.43 255.255.255.0 10.10.20.1"
 +</code>
 +</WRAP>
 +
 +Note: The TECH requires a gateway when used to stream multicast, even if on the same subnet.
 +
 +</WRAP>
 +==== Reverting to DHCP ====
 +<WRAP indent>
 +
 +The TECH can be configured for DHCP operation (default) using the following command:
 +
 +<WRAP indent>
 +<code>
 +Format: hdhomerun_config <old ip> set /sys/ipaddr dhcp
 +Example: hdhomerun_config 169.254.34.98 set /sys/ipaddr dhcp
 +</code>
 +</WRAP>
 +
 +</WRAP>
 +
 +</WRAP>
 +
 +===== 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>
 +<code>
 +Format: hdhomerun_config <ip|id> set /tuner<n>/channelmap <channelmap>
 +Example: hdhomerun_config 10001000 set /tuner0/channelmap us-cable
 +Example: hdhomerun_config 10001000 set /tuner1/channelmap us-cable
 +</code>
 +</WRAP>
 +
 +Channel maps supported by HDHR-TECH-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 |
 +</WRAP>
 +
 +Channel maps supported by HDHR-TECH-EU 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 |
 </WRAP> </WRAP>
  • Last modified: 2026/03/24 06:15