At times, the assigned mode may be neither of those two terrestrial modes, and instead one of the non-terrestrial modes of DVB-C, DVB-S, or DVB-S2 is chosen. These non-terrestrial modes mean the tuner is not suitable for broadcast TV reception.
You can see the assigned mode a number of ways -
- GUI - Information>>Devices, or Setup>>Tuners>>Tuner configuration
- OpenWebif - In the 'Tuners' section of the Box Info option which is located under Extras
- File system
For a T2 the USB tuner is detailed in the "NIM Socket 2" entry, and for a T3 it is the "NIM Socket 3" entry. The other sockets are for the internal tuners.
My examples shown here are from a T2, as I don't have a T3.
Code: Select all
root@beyonwizt2:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-T2
Name: DVB-T/T2 NIM
Mode 0: DVB-T2
Mode 2: DVB-C
Frontend_Device: 0
I2C_Device: 0
NIM Socket 1:
Type: DVB-T
Name: DVB-T NIM
Frontend_Device: 1
I2C_Device: 1
NIM Socket 2:
Type: DVB-T
Name: RTL2832U
Frontend_Device: 2
I2C_Device: 843863122
root@beyonwizt2:~#
The correct entry for the USB tuner should be DVB-T (single-type with no "Mode: " entries), represented in /proc/bus/nim_sockets as -
Code: Select all
NIM Socket 2:
Type: DVB-T
Name: RTL2832U
Frontend_Device: 2
I2C_Device: 843863122
Example 1 (multi-type, single-mode, effectively the same as above):
Code: Select all
NIM Socket 2:
Type: DVB-T
Name: RTL2832U
Mode 3: DVB-T
Frontend_Device: 2
I2C_Device: 843863122
Code: Select all
NIM Socket 2:
Type: DVB-T
Name: RTL2832U
Mode 3: DVB-T
Mode 2: DVB-C
Mode 4: DVB-S2
Frontend_Device: 2
I2C_Device: 843863122
Code: Select all
NIM Socket 2:
Type: DVB-T
Name: RTL2832U
Mode 6: DVB-T2
Mode 3: DVB-T
Mode 5: DVB-C2
Mode 2: DVB-C
Mode 4: DVB-S2
Frontend_Device: 2
I2C_Device: 843863122
Here's an example of when the USB tuner was assigned the non-terrestrial mode DVB-C, which meant it couldn't receive a broadcast signal.
Code: Select all
NIM Socket 2:
Type: DVB-T
Name: RTL2832U
Mode 5: DVB-C2
Mode 2: DVB-C
Mode 4: DVB-S2
Frontend_Device: 2
I2C_Device: 843863122
Here's how the above was reported in OWIF for the USB tuner -
Code: Select all
<e2name>Tuner C</e2name>
<e2model>RTL2832U (DVB-C)</e2model>
... and the [NimManager] entries from the debug log -
Code: Select all
{627}< 46.130> [NimManager] slotname = Tuner A, slotdescription = DVB-T/T2 NIM, multitype = True
{627}< 46.131> [NimManager] slotname = Tuner B, slotdescription = DVB-T NIM, multitype = 0
{627}< 48.189> [NimManager][enumerateNIMs] slot: 0 - entry: {'multi_type': {'0': 'DVB-T2', '2': 'DVB-C'}, 'name': 'DVB-T/T2 NIM', 'frontend_device': 0, 'isempty': False, 'i2c': 0, 'type': 'DVB-T2'}
{627}< 48.191> [NimManager][enumerateNIMs] slot: 1 - entry: {'isempty': False, 'frontend_device': 1, 'i2c': 1, 'type': 'DVB-T', 'name': 'DVB-T NIM'}
{627}< 48.192> [NimManager][enumerateNIMs] slot: 2 - entry: {'multi_type': {'2': 'DVB-C', '5': 'DVB-C2', '4': 'DVB-S2'}, 'name': 'RTL2832U', 'frontend_device': 2, 'isempty': False, 'i2c': 843863122, 'type': 'DVB-T'}
{627}< 48.194> [NimManager] slotname = Tuner C, slotdescription = RTL2832U, multitype = True
If you observe a non-terrestrial mode for the USB tuner, then restart the UI. Likely the restart will get a terrestrial mode assigned, if not then rinse, repeat.
If a terrestrial mode has been selected for the USB tuner, and if you keep your T2/T3 in standby rather than shutting it down to deep standby when not in use, then you'll not have this non-terrestrial mode issue appear, until such time as you reboot or restart the UI and then the possibility exists and you must check the mode again.
If you want to keep your T2/T3 in deep standby when not in use, and assuming you're not wanting to risk USB tuner 'mode-itis' (i.e. a non-Terrestrial mode being assigned), then you'll need extra steps in the GUI startup process to monitor the USB tuner mode and take action. That's what I've done with our T2.
I'll post detail of that in the next post.
The U4 is _not_ affected by mode-itis.
