My satellite equipment consists of dish with 4 Quattro-LNB's connected to a 17/8 Diseqc 1.0 Multiswitch.
Although this setup is quite common, AutoDiseqc fails to detect the satellites correctly on my Xtrend ET9200.
I wonder if an expert, familiar with the source code, could help?
AutoDiseqc issues
Started by Stan, Yesterday, 16:01
6 replies to this topic
#1
-
- Senior Member
- 481 posts
+5
Neutral
Posted Yesterday, 16:01
Re: AutoDiseqc issues #2
-
- PLi® Core member
- 70,929 posts
+1,835
Excellent
Posted Yesterday, 16:12
That has nothing to do with code.
Whan is needed is a list, with per satellite position a transponder which can be locked that is absolutely unique amongst all sats in the list (to avoid false hits.
You can find the current list here: https://github.com/O...toDiseqc.py#L25
p.s. not common enough, I've got two of those switches here, one new-in-box. Nobody's interested 
.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: AutoDiseqc issues #3
-
- Senior Member
- 481 posts
+5
Neutral
Posted Yesterday, 16:26
You've posted a link to SatFinder. I was talking about AutoDiseqc.
I know that unique frequencies have to be scanned. That is the case, so no problem with that.
Edited by Stan, Yesterday, 16:36.
Re: AutoDiseqc issues #4
-
- PLi® Core member
- 10,381 posts
+354
Excellent
Posted Yesterday, 16:53
Once, about 10 years ago, I noticed on some receivers that they not tune eDVBFrontendParametersSatellite.System_DVB_S2 or some eDVBFrontendParametersSatellite.FEC.
Or problem in 17/8 Diseqc 1.0 Multiswitch.
Edited by Dimitrij, Yesterday, 17:01.
GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K
Re: AutoDiseqc issues #5
-
- Senior Member
- 481 posts
+5
Neutral
Posted Yesterday, 16:59
Could we clarify some basics first? Why is there an option in AutoDiseqc "Set voltage and 22kHz"? It is not needed in a simple Diseqc environment.
Edited by Stan, Yesterday, 17:01.
Re: AutoDiseqc issues #6
-
- PLi® Core member
- 57,467 posts
+708
Excellent
Posted Yesterday, 18:17
Sometimes it is needed in the simple mode… but maybe not when all is in the autodiseqc mode.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: AutoDiseqc issues #7
-
- Senior Member
- 481 posts
+5
Neutral
Posted Yesterday, 18:41
Simple mode is by definition without cascaded switches, right?
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
