FYI
https://github.com/O...0820b7522f33f81
Scanning issue: Dead/out of footprint transponders
Started by Abu Baniaz, 24 Apr 2018 17:18
49 replies to this topic
Re: Scanning issue: Dead/out of footprint transponders #41
-
- PLi® Core member
- 57,154 posts
+698
Excellent
Posted 14 May 2018 - 13:41
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Scanning issue: Dead/out of footprint transponders #42
-
- PLi® Core member
- 70,491 posts
+1,810
Excellent
Posted 14 May 2018 - 13:46
I'll back-port it to 6.2-release, pending the discussion about the timeout time.
Edited by WanWizard, 14 May 2018 - 13:48.
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: Scanning issue: Dead/out of footprint transponders #43
-
- PLi® Contributor
- 2,497 posts
+64
Good
Posted 14 May 2018 - 13:46
Yes, that is what I applied. Sorry, should have been clearer.
https://github.com/O...f530834103dbb07
Re: Scanning issue: Dead/out of footprint transponders #44
-
- PLi® Core member
- 32,766 posts
+245
Excellent
Posted 14 May 2018 - 14:05
I applied this to OpenVix and built an image. It works, thanks.
It waits 5/6 minutes before going to second TP. Can this be reduced to 2 minutes?
the total timeout depends on the turning angle, and the turning speed which is used in the timeout calculation is very conservative (because the motor might be very slow): 2 seconds per degree (plus some constant factor)
This value is not a setting, it cannot be tweaked by users.
Re: Scanning issue: Dead/out of footprint transponders #45
-
- PLi® Contributor
- 4,654 posts
+162
Excellent
Posted 14 May 2018 - 15:54
It waits 5/6 minutes before going to second TP. Can this be reduced to 2 minutes?
Reducing to 2 minutes would break scanning on my positioner.
Re: Scanning issue: Dead/out of footprint transponders #46
-
- PLi® Contributor
- 4,654 posts
+162
Excellent
Posted 14 May 2018 - 15:57
I applied this to OpenVix and built an image. It works, thanks.
It waits 5/6 minutes before going to second TP. Can this be reduced to 2 minutes?
the total timeout depends on the turning angle, and the turning speed which is used in the timeout calculation is very conservative (because the motor might be very slow): 2 seconds per degree (plus some constant factor)
This value is not a setting, it cannot be tweaked by users.
There is no way to know the turning angle, or is there? My receiver has 2 motorised dishes attached. How is enigma supposed to know which dish the stored angle corresponds to?
Edited by Huevos, 14 May 2018 - 15:58.
Re: Scanning issue: Dead/out of footprint transponders #47
-
- PLi® Core member
- 32,766 posts
+245
Excellent
Posted 14 May 2018 - 18:15
Only one dish per tuner I assume?
The angle is known for each tuner, the difference between old/new angle determines the timeout.
The angle is known for each tuner, the difference between old/new angle determines the timeout.
Re: Scanning issue: Dead/out of footprint transponders #48
-
- PLi® Core member
- 70,491 posts
+1,810
Excellent
Posted 14 May 2018 - 21:22
Backported, will be in 6.2-release tomorrow.
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: Scanning issue: Dead/out of footprint transponders #49
-
- PLi® Contributor
- 4,654 posts
+162
Excellent
Posted 14 May 2018 - 22:06
2 dishes. 1 C-band and 1 ku. Used to be on the same tuner but not currently.
Re: Scanning issue: Dead/out of footprint transponders #50
-
- PLi® Contributor
- 2,497 posts
+64
Good
Posted 14 May 2018 - 23:30
The "initial wait" time reduction has already been ruled out.Reducing to 2 minutes would break scanning on my positioner.
4 user(s) are reading this topic
0 members, 4 guests, 0 anonymous users
