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

Unicable does not work, how can I detect broken hardware? #104

Closed
HellGL opened this issue Jan 20, 2018 · 1 comment
Closed

Unicable does not work, how can I detect broken hardware? #104

HellGL opened this issue Jan 20, 2018 · 1 comment

Comments

@HellGL
Copy link

HellGL commented Jan 20, 2018

Hi,
my unicable setup (gss.Box, satip-axe V14, various clients on linux and iOS) stopped working. I did not change anything, it just stopped on all clients. Connecting my gss.Box directly to the matrix and changing to quad lnb input setting I get a picture but as I only have one cable, of course only on one tuner. I suspected the Unicable switch (DUR-line SCR 514K) and got another switch on ebay (Preisner/Televes MSU 518NG, used but factory refurbished) which shows the same behaviour. Is there a way to check if the switch is really broken or if something else is going wrong? On the status website I get STR readings for the clients but no picture. Any ideas?

Regards,
HellG

@HellGL HellGL changed the title Unicable does not work, how can I detect broken hardware Unicable does not work, how can I detect broken hardware? Jan 20, 2018
@perexg
Copy link
Owner

perexg commented Jan 25, 2018

Have you tried to play with the diseqc timing? issue #79

@perexg perexg closed this as completed Sep 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants