Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem in vertical frequencies... #154

Closed
rubenqs12 opened this issue Sep 23, 2019 · 3 comments
Closed

Problem in vertical frequencies... #154

rubenqs12 opened this issue Sep 23, 2019 · 3 comments
Labels

Comments

@rubenqs12
Copy link

I´m using the latest perexg/satip-axe firmware (satip-axe-201810211549-15 - Sun Oct 21 2018) for the Digibit R1.
The problem is that the channels in vertical frequencies (example Movistar +) do not receive a signal, but if I first reproduce a channel of a horizontal frequency and change to a vertical frequency, if it is played.
If I only play the vertical channel, I only receive 0% SNR on tvheadend.

An example:
Play "Canal sur" in tvheadend = Not work.
Play in this order... "Travel 4K" and then "Canal sur" = It works perfectly and stable and even the other tunners work.

I have a monoblock LNB for Astra and Hotbird respectively, and only under one cable to input 0 ...

In minisat I have configured the next boot.
-7 0:1,0:2,0:3 '/ minisatip8

But I have the problem commented ... could someone help me to make it work properly, please? Thank you

@perexg perexg added the question label Oct 8, 2019
@perexg
Copy link
Owner

perexg commented Oct 8, 2019

You may try the recent build - #155 - or try to play with the diseqc timing (-q or --diseqc-timing option).

@rubenqs12
Copy link
Author

Amazing...
I had been with this problem for weeks ... now it works from the beginning.

Thank you!

This work with monoblock
/sbin/minisatip8 -f --diseqc-timing *:155-54-15-15-15-0 -7 0:1,0:2,0:3

@perexg perexg closed this as completed Oct 16, 2019
@m4tt075
Copy link

m4tt075 commented Oct 24, 2019

@rubenqs12: Bloody h***! I've been chasing the same issue for weeks, too. Didn't expect to find the solution here. Thank You!

@perexg: Just for information, in case you'll see similar reports elsewhere: The firmware upgrade alone was not sufficient to fix it. Changing the diseqc timing as above did. I'm running Digibit R1s.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants