16 replies to this topic

[Clown]

STB: Gigablue UE UHD 4K

 

Image: OpenPLI 7.3

 

Tuner: NIM TT2L10 DVB-C/T combi tuner

 

 

I just got this STB yesterday, the SAT channels are working fine.

 

I cannot get the cable channels to scan/find any channels.  I have tried cable scan, auto scan, and manual scan with known valid channel settings/info from my area and It will not find/tune any cable channels.  I've tried Brute force, network ID and every available option in the DVB-C scanning menu.

 

I have tried every image available for this STB, with the same results; the DVB-C/T tuner is not finding any channels.  I know this is not an OpenPLI problem, I'm just asking for some advice.  I think it is probably a rookie/stupid mistake I'm making.

 

Please note: My Xtrend ET-10000 tunes all cable channels with no problems( I reconnected the Xtrend 3 times to verify this...no problems), so the cabling and/or connectors are ruled out.

 

Are there specific settings I should use to get the DVB-C/T tuner to scan/tune cable channels?

 

Thanks.

[WanWizard]

Did you configure the tuner for cable, as it is a combi tuner?

[Clown]

Yes, I did, thanks.

[Pr2]

Hi,

 

If you already have a channel list (the one from your XTrend 1000) you can perhaps try to restore it on your Gigablue.

If your tuner is properly set on DVB-C you should be able to zap DVB-C channel and see what happens.

 

Now the tuner sensitivity can be different, so for your Gigablue may be your signal is too strong and saturate the tuner and an attenuator is needed, or too weak for it and then it is an amplifier which is needed.

 

Pr2

[Clown]

Thanks to everyone for your replies,

 

I transferred my old/saved channel list using DBEdit to my new Gigablue, and the cable channels are not tuning.

 

The tuner is configured for cable. 

 

I have tried every available image for this receiver with the same results.

 

I think maybe the tuner is AFU.

 

I'll contact the seller(HM-Sat.de) tomorrow.

 

Once again, thanks for your replies.

[Pr2]

Thanks for your feedback, indeed sounds like a hardware issue.

One last thing that you can try if it is pluggable tuner, try to remove and reinsert it. It has perhaps moved in the slot during transport.

Edited by Pr2, 19 August 2020 - 07:45.

[Dimitrij]

Please telnet answer:

cat /proc/bus/nim_sockets 

 

[Clown]

Thanks for your help Dimitrij.

 

Here is the telnet output:

 

NIM Socket 0:
        Type: DVB-S2X
        Name: DVB-S2X NIM(45308X FBC)
        Frontend_Device: 0
        I2C_Device: 3
NIM Socket 1:
        Type: DVB-S2X
        Name: DVB-S2X NIM(45308X FBC)
        Frontend_Device: 1
        I2C_Device: 3
NIM Socket 2:
        Type: DVB-S2X
        Name: DVB-S2X NIM(45308X FBC)
        Frontend_Device: 2
        I2C_Device: 3
NIM Socket 3:
        Type: DVB-S2X
        Name: DVB-S2X NIM(45308X FBC)
        Frontend_Device: 3
        I2C_Device: 3
NIM Socket 4:
        Type: DVB-S2X
        Name: DVB-S2X NIM(45308X FBC)
        Frontend_Device: 4
        I2C_Device: 3
NIM Socket 5:
        Type: DVB-S2X
        Name: DVB-S2X NIM(45308X FBC)
        Frontend_Device: 5
        I2C_Device: 3
NIM Socket 6:
        Type: DVB-S2X
        Name: DVB-S2X NIM(45308X FBC)
        Frontend_Device: 6
        I2C_Device: 3
NIM Socket 7:
        Type: DVB-S2X
        Name: DVB-S2X NIM(45308X FBC)
        Frontend_Device: 7
        I2C_Device: 3
NIM Socket 8:
        Type: DVB-C
        Name: GIGA DVB-T2/C NIM (TT2L10)
        Has_Outputs: yes
        Frontend_Device: 8
        Mode 0:DVB-C
        Mode 1:DVB-T2
        I2C_Device: 4

[Abu Baniaz]

It might be a driver bug. USB tuners behave in the same way.

 

Just for reference, same receiver with the TT3L10 tuner

 

root@gbue4k:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-S2
        Name: DVB-S2 NIM(45308 FBC)
        Frontend_Device: 0
        I2C_Device: 3
NIM Socket 1:
        Type: DVB-S2
        Name: DVB-S2 NIM(45308 FBC)
        Frontend_Device: 1
        I2C_Device: 3
NIM Socket 2:
        Type: DVB-S2
        Name: DVB-S2 NIM(45308 FBC)
        Frontend_Device: 2
        I2C_Device: 3
NIM Socket 3:
        Type: DVB-S2
        Name: DVB-S2 NIM(45308 FBC)
        Frontend_Device: 3
        I2C_Device: 3
NIM Socket 4:
        Type: DVB-S2
        Name: DVB-S2 NIM(45308 FBC)
        Frontend_Device: 4
        I2C_Device: 3
NIM Socket 5:
        Type: DVB-S2
        Name: DVB-S2 NIM(45308 FBC)
        Frontend_Device: 5
        I2C_Device: 3
NIM Socket 6:
        Type: DVB-S2
        Name: DVB-S2 NIM(45308 FBC)
        Frontend_Device: 6
        I2C_Device: 3
NIM Socket 7:
        Type: DVB-S2
        Name: DVB-S2 NIM(45308 FBC)
        Frontend_Device: 7
        I2C_Device: 3
NIM Socket 8:
        Type: DVB-C
        Name: GIGA DVB-T2/C NIM (TT3L10)
        Has_Outputs: yes
        Frontend_Device: 8
        Mode 0:DVB-C
        Mode 1:DVB-T2
        I2C_Device: 4
NIM Socket 9:
        Type: DVB-C
        Name: GIGA DVB-T2/C NIM (TT3L10)
        Has_Outputs: yes
        Frontend_Device: 9
        Mode 0:DVB-C
        Mode 1:DVB-T2
        I2C_Device: 4

Edited by Abu Baniaz, 19 August 2020 - 13:56.

[Pr2]

Yes but is it an internal or external USB tuner?

[Abu Baniaz]

Clown's one is pluggable tuner, same as my 310.

Sent from my Moto G (5S) using Forum Fiend v1.3.3.

[Clown]

Hi Abu,

 

your  "cat /proc/bus/nim_sockets" is exactly the same as mine...correct?

 

This means the STB is correctly recognizing the tuner, correct?

 

Thanks for your help.

 

[Abu Baniaz]

Not exactly. I have 10 tuners, you have 9, they start at 0. Our 9th tuners are identical apart from name. I am guessing the TT3L10 is twin hybrid tuner and TT2L10 is single hybrid tuner. Is that correct?

 

The TT3L10 pluggable tuner is working fine on my box.

 

Sorry to add confusion by mentioning USB tuners, but the report you have given is exactly the same as how a USB tuner works on the Gigablue. Almost instant finish of scan and does not pick up any channels.

[Dimitrij]

DVB-C tuner unable to find/scan cable channels

[twol]

As I have pointed out, but everybody ignores - this tuner is not specified as working on the Giga 4K‘s(by Impex / GigaBlue) its the old tuner, so unless no cable tuner works on the Giga you are wasting your breath posting Gigablue

Edited by twol, 20 August 2020 - 18:20.

[Clown]

Hi Twol

 

Thanks for your help.

 

I contacted HM-Sat today, I advised them of the info you gave me from the Impex/Gigablue website, and I'm returning the tuner.

 

I'm not quite sure which tuner they are going to send, but I sent them a link from Impex/Gigablue website about which tuners are supported by Gigablue UHD UE 4K.  We'll see what happens.

 

Thanks for everyone's help.

[Clown]

I received the new tuner today (the same model: TT2L10) and it tunes fine. HM-Sat said they verified the original tuner was faulty.

Like Twol said...I think I shoulda got the updated tuner, but I'm not bothered as I'm finished with cable in about a year. I would never order from HM-Sat again. I ordered a STB, splitter and Unicable LNB; splitter was wrong brand, tuner was faulty and looked used (corrosion on board and mounting holes). I haven't connected the LNB yet??

Thanks for everyone's help on here.