59 replies to this topic

[amila4341]

hello friend

 

I have vu+ duo2

Satellite ST 2@ 88.0 , Videocon D2H

 

now its 4 tp my receiver not scanning channels all tps have 80 s% snr

TP (04) signals are strong but unable to scan any of the services

 

11483 H SR 44995 FEC 2/3 DVB-S2 8PSK

11546 V SR 44995 FEC 2/3 DVB-S2 8PSKAll 

11546 H SR 44995 FEC 2/3 DVB-S2 8PSK

11672 H SR 44995 FEC 2/3 DVB-S2 8PSK

 

 

i have installed dvb snoop can it be used to find cause of this issue

and all other tps scanning perfectly.

and other tps also 44000 plus samble rate..

Tuner is AVL 6222.

 

 

[mimisiku]

That's a satellite we cannot receive in Europe.. Most tuners end at 45.000 Msym so you are really on the edge... Since others with same Msym rate CAN be locked you might want to check out your LNB and possibly the settings. LOF set OK?

Are you sure the 2 middle entries are correct? I have never seen a satellite using the same frequency for both H and V polarisation...

Edited by mimisiku, 4 October 2016 - 04:36.

[amila4341]

That's a satellite we cannot receive in Europe.. Most tuners end at 45.000 Msym so you are really on the edge... Since others with same Msym rate CAN be locked you might want to check out your LNB and possibly the settings. LOF set OK?

Are you sure the 2 middle entries are correct? I have never seen a satellite using the same frequency for both H and V polarisation...

yes both horizontal and vertical transponders used same frequency

[amila4341]

 

That's a satellite we cannot receive in Europe.. Most tuners end at 45.000 Msym so you are really on the edge... Since others with same Msym rate CAN be locked you might want to check out your LNB and possibly the settings. LOF set OK?

Are you sure the 2 middle entries are correct? I have never seen a satellite using the same frequency for both H and V polarisation...

yes both horizontal and vertical transponders used same frequency

 

LOF = Universal LNB

[amila4341]

hello
i did some experiment with lamedb.i got lamedb file from my friends vu+ zero which scan all transponders and store all channels and merge with my lamedb.now when i switch to those channels my duo2 couldn't scan ,there is signal but after some little while no data on transponder timeout reading pat appear could you suggest remady

Edited by amila4341, 4 October 2016 - 06:21.

[amila4341]

no data on transponder timeout reading pat

 

why this message?

[Pr2]

This is typically the message that you get when you cannot receive properly a given TP (transponder).

 

If your provider use both V and H on the same frequency I guess the conter polarization of your LNB is really important and needs to be very good (the rotation of the LNB inside its support).

 

http://www.trackdish...l-rate-details/

 

But if you google with "VU+ problem with high symbol rate"  you will see that it is a well-known issue with VU+ product...

 

Exemple:

 

http://www.world-of-...hp/t-50769.html

 

So OpenPLi is not to blame, report the issue to VU+ and tell us if you get any answer from them, if so you should purchase a "Lotery ticket" because you will be in a very good day.  

 

Pr2

[amila4341]

This is typically the message that you get when you cannot receive properly a given TP (transponder).

 

If your provider use both V and H on the same frequency I guess the conter polarization of your LNB is really important and needs to be very good (the rotation of the LNB inside its support).

 

http://www.trackdish...l-rate-details/

 

But if you google with "VU+ problem with high symbol rate"  you will see that it is a well-known issue with VU+ product...

 

Exemple:

 

http://www.world-of-...hp/t-50769.html

 

So OpenPLi is not to blame, report the issue to VU+ and tell us if you get any answer from them, if so you should purchase a "Lotery ticket" because you will be in a very good day.  

 

Pr2

problem is only some transponders is not scanned .but some with high symbol rates is scanned and channels are stored. 

i did report it to vu+ several times. but they have not responded to any of the emails 

Edited by amila4341, 5 October 2016 - 12:26.

[Rob van der Does]

I did report it to vu+ several times. but they have not responded to any of the emails

They never do; even a 'thank you' is asked too much for their (not existing) customer care....

[amila4341]

Is there any way to find out what is going wrong.vu+ don't seems to be giving answer.
any tools like dvb snoop?

[Pr2]

Tuner/driver issue for those high value symbol rate, I don't think that you can debug this by yourself.

[amila4341]

So you mean we have no way out of this problem. It's very sad that vu + doing nothing about it. Could anyone help me to contact vu with regard to this issue.
Thank you.

[Erik Slagter]

It can even be a hardware issue.

[amila4341]

It can even be a hardware issue.

You may be correct. I think that is why vu + is not responding.

[Rob van der Does]

No. VU never responds to any question/remark/bug-report.

[Huevos]

@Amila4341, looks like you missed the most important comment in this thread. Your LNB skew is wrong. Everything else is just noise. Vu+ boxes have no problem whatsoever scanning these symbol rates.

[Erik Slagter]

I can't confirm that, I can only receive transponders with up to 30 Ms/s (from this location). Otherwise suggestions welcome

Edited by Erik Slagter, 9 October 2016 - 09:29.

[dax]

I can't confirm that, I can only receive transponders with up to 30 Ms/s (from this location). Otherwise suggestions welcome

Me too. I'm in Europe, if somebody tell to me where find a sat with high symbol rate i can test also. First with a field strenght signal meter and after with a solo2.

[amila4341]

@Amila4341, looks like you missed the most important comment in this thread. Your LNB skew is wrong. Everything else is just noise. Vu+ boxes have no problem whatsoever scanning these symbol rates.

How could it be lnb skew.its not only me facing this issue most of vu + duo2 holders who tried to get st 2 is facing same issue . could you explain please.

Edited by amila4341, 9 October 2016 - 12:54.

[amila4341]

Does "vu + development team" stopped driver development for vu + duo2.