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
#1
Posted 26 December 2024 - 16:01
Re: AutoDiseqc issues #2
Posted 26 December 2024 - 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
Re: AutoDiseqc issues #4
Posted 26 December 2024 - 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, 26 December 2024 - 17:01.
GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K
Re: AutoDiseqc issues #5
Re: AutoDiseqc issues #6
Re: AutoDiseqc issues #7
Re: AutoDiseqc issues #8
Re: AutoDiseqc issues #9
Posted Yesterday, 16:22
Nevertheless, it should reliably detect the connected satellites in common configurations. And it doesn't.
Another annoying thing is, that it changes the selected configuration. When chosen A/B/C/D it should keep this mode after scanning, no matter what the result is.
before_scan.jpg 78.45KB 0 downloads after_scan.jpg 59.87KB 0 downloads
Re: AutoDiseqc issues #10
Posted Yesterday, 16:33
Problem this
if mode == "diseqc_a_b_c_d": list.append((self.indent % _("Port C"), nim.diseqcC, _("Select the satellite which is connected to Port-C of your switch. If you are unsure select 'automatic' and the receiver will attempt to determine this for you. If nothing is connected to this port, select 'nothing connected'."))) list.append((self.indent % _("Port D"), nim.diseqcD, _("Select the satellite which is connected to Port-D of your switch. If you are unsure select 'automatic' and the receiver will attempt to determine this for you. If nothing is connected to this port, select 'nothing connected'."))) if (nim.diseqcC.value == '3600') or (nim.diseqcD.value == '3600'): self.autodiseqc_ports = 4
Maybe
if mode == "diseqc_a_b_c_d": if self.autodiseqc_ports: self.autodiseqc_ports = 4
GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K
Re: AutoDiseqc issues #11
Re: AutoDiseqc issues #12
Re: AutoDiseqc issues #13
Posted Yesterday, 23:31
Connected on the one where nothing was found. I never discovered when you set abcd that it changes to ab and visa versa.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: AutoDiseqc issues #14
Posted Yesterday, 23:35
There must be a recent code change, that modifies the selected configuration depending on the scan results.
You can repoduce it. Set the config like in the attached screenshot and then select AutoDiseqc.
before_scan_2sats.jpg 60.26KB 0 downloads
Edited by Stan, Yesterday, 23:42.
Re: AutoDiseqc issues #15
Posted Today, 08:25
I actually never liked that you could set auto individually and predefine some positions. Maybe it was always better to have just one option auto…. And when off you can set it individually. And when (afterwards) we have some positions show for where nothing was found nothing connected.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: AutoDiseqc issues #16
Posted Today, 09:53
Ok, so once again the screenshots:
before_scan_2sats.jpg 60.26KB 0 downloads -> AutoScan -> after_scan_2become1.jpg 36.35KB 0 downloads
It's actually a good thing, that you can repeat scanning for only certain sat positions that may have not been detected at first scan. But it should work right!
The semi-automatic logic that kicks in after the scan and changes the selected mode should be removed.
Re: AutoDiseqc issues #17
Posted Today, 09:54
Sounds it limits to location where it find something only and not keep the ones you set manually before (it was never made for this).
Needs investigation.
Is at my todo list. First fix simplechannellist
Edited by littlesat, Today, 09:57.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: AutoDiseqc issues #18
Posted Today, 10:58
OK. If you have time for it, there's a second issue: If only some of the Ports are set to automatic, AutoScan will assign wrong satellites to them.
For example, my actual satellite setup is this: 4sats_correct.jpg 63.41KB 0 downloads I should always get this result after AutoDiseqc. (if it works right)
Instead, when scanning Ports C and D only, I get this:
before_scan_4sats.jpg 70.53KB 0 downloads -> AutoDiseqc -> scan_2from4.jpg 49.75KB 0 downloads -> Result -> after_scan_4sats_2wrong.jpg 65.08KB 0 downloads
Re: AutoDiseqc issues #19
Posted Today, 11:05
Yes…. You do something it was never made for…. And due to you can set it up like this, what you experience happens… you find the ‘edges’ on something that is in there for >10 years or so and also in more images what nobody discovered…
Edited by littlesat, Today, 11:06.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: AutoDiseqc issues #20
Posted Today, 11:20
Why am I always getting this attitude?
[..] You do something it was never made for…. [...]
I am doing exactly what is was made for.
https://github.com/O...c808f8f79086e5b
Edited by Stan, Today, 11:24.
3 user(s) are reading this topic
0 members, 3 guests, 0 anonymous users