FPGA upgrade + 1.78 = DVB-T issues

Resurrecting this old thread in case it is of any use to anyone else.

I swapped Tuner A (DVB-S) with Tuner C (DVB-T).

The DVB-S tuner in slot C is now glitching intermittently, and the DVB-T tuner in slot A is working perfectly.
So, the problem appears to be with the slot rather than the tuner.....
 
Wiggy9 said:
Resurrecting this old thread in case it is of any use to anyone else.

I swapped Tuner A (DVB-S) with Tuner C (DVB-T).

The DVB-S tuner in slot C is now glitching intermittently, and the DVB-T tuner in slot A is working perfectly.
So, the problem appears to be with the slot rather than the tuner.....
Click to expand...

I suppose you have all three slots with a tuner because the use of A and C without B it's not supported.
If it's your situation please write to VuPlus (www.vuplus.com) about this issue
 
I decided to try a dual tuner in the Ultimo, hoping that I could perhaps avoid using slot C.

I put the DVB-T in slot A and the borrowed dual S2 in slot B. I left slot C empty.

The machine booted, but only detected the DVB-T in slot A.

I swapped the dual into A and put the DVB-T in B.
The image would not boot, it stayed stuck on the Starting GUI screen (BH 2.0.5).
Anyone else have grief with a dual tuner in an Ultimo?
 
Matrix10 said:
Why BH 2.0.5 ?
You have test with BH 2.0.8 upgrade to 2.0.8.1
Click to expand...

I didn't think that updating to 2.0.8.x would make any difference to my issue.

Found out since that on the Ultimo, the dual tuner is supported only in slot C.
So it was never going to be a solution for my problem.

To recap, my problem is that slot C exhibits breakup and glitching of the TV picture.
This problem arose after upgrading the FPGA.
It happens regardless of whether the tuner is DVB-S2 or DVB-T.
There is nothing wrong with either tuner.
I don't know what can be done about the problem.
I don't get any response when I mail vu+ support.
I deeply regret purchasing this piece of sh1t.
 
I have not tested it , because I have not the possibility
But I know that there have been various changes in drivers
so maybe is not bad to test.
 
I agree that nothing should be ruled out.

However, the issue first arose with an upgrade to 1.78 and an FPGA update.
Rolling back from 1.78 did not fix it.
There is no way to roll back the FPGA.
No subsequent upgrade fixed it.
The problem is not with the tuners, rather, it is with the socket, i.e. the motherboard.

Therefore, I don't believe an image update will fix this....
 
Wiggy9 said:
I agree that nothing should be ruled out.

However, the issue first arose with an upgrade to 1.78 and an FPGA update.
Rolling back from 1.78 did not fix it.
There is no way to roll back the FPGA.
No subsequent upgrade fixed it.
The problem is not with the tuners, rather, it is with the socket, i.e. the motherboard.

Therefore, I don't believe an image update will fix this....
Click to expand...

I do not know
I know that there have been many changes in the drivers lately.
If you do not test you doe not know if fix was made.
But more than that I can not advise.
 
You must log in or register to reply here.
Back
Top