Jump to content


Photo

Timer & motorised dish - logic


  • Please log in to reply
19 replies to this topic

#1 Robinson

  • Senior Member
  • 2,614 posts

+30
Good

Posted 13 January 2018 - 17:41

As athoik noticed in another thread, when using a motorised dish, timer recording may start before the dish has reached its position. This causes the beginning of the recording to be truncated or, in certain cases, the recording fails if there is still no lock when the recording starts.

I have done some tests and the dish always starts to move approx. 20 seconds before the time the recording is supposed to start, no matter how far away from the destination satellite the dish is at the moment.

The 20 seconds is not enough if the satellite is approx. 25 degrees away or more.

Does anyone know where the 20 seconds is located in Enigma2 code?

Could it be extended to 60 seconds? That would very much cover the whole arc, I think.

Thank you.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Timer & motorised dish - logic #2 Robinson

  • Senior Member
  • 2,614 posts

+30
Good

Posted 25 January 2018 - 23:03

Pity noone is able to locate the value inside Enigma2 code. It is probably something like 20000 [milliseconds]


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Timer & motorised dish - logic #3 WanWizard

  • PLi® Core member
  • 68,311 posts

+1,719
Excellent

Posted 26 January 2018 - 18:35

I don't think it works that way.

 

I think it is more likely the dish starts moving when the recording process allocates the tuner, which afaik is when the timer changes to "about to start".


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (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: Timer & motorised dish - logic #4 Robinson

  • Senior Member
  • 2,614 posts

+30
Good

Posted 26 January 2018 - 19:09

I see.

So a potential change of the time when the timer changes to "about to start" (it seems to be 20 seconds) would affect everybody, not just owners of the motorised dish?

Pity. Therefore for motorized systems recordings will usually be truncated at the beginning if the dish has to travel more than 20-30 seconds.

No chance to make this setting configurable for rotor owners?


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Timer & motorised dish - logic #5 Dimitrij

  • PLi® Core member
  • 9,969 posts

+335
Excellent

Posted 26 January 2018 - 19:23

For this there is a special setting "Margin before recording (minutes)"

or

edit timer start time manual

 

 

No need to invent anything.


GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Timer & motorised dish - logic #6 WanWizard

  • PLi® Core member
  • 68,311 posts

+1,719
Excellent

Posted 26 January 2018 - 19:40

No, I don't think so.
 
My default margin is 5 minutes, but the status of a timer in the timer list doesn't change to "about to start" until 30 seconds or so before the actual recording starts. Which sometimes is tight for me as well, as my NAS disks take quite a bit of time to spin up. Enigma will then mark the NAS as offline, and record on the internal disk instead (which is one of the reasons my box still has one).
 
I think this is it: https://github.com/O...op/timer.py#L14 which is used here: https://github.com/O...rdTimer.py#L636 to determine when to start preparing (so 20 sec was a very good guess ;)).

 

So it would perhaps not be a bad idea to have this value configurable?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (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: Timer & motorised dish - logic #7 Pr2

  • PLi® Contributor
  • 6,046 posts

+256
Excellent

Posted 26 January 2018 - 20:18

 

...

So it would perhaps not be a bad idea to have this value configurable?

 

Hi,

 

Cannot we compute the maximum time a motor will take to go from one extremity to the other one and add a few more seconds for security, this is worst case and the longer time a motor can be in movement.  So define this value instead of the 20 seconds?

 

Pr2


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 


Re: Timer & motorised dish - logic #8 WanWizard

  • PLi® Core member
  • 68,311 posts

+1,719
Excellent

Posted 26 January 2018 - 22:05

It is not (only) related to a motor perse.

 

In my case, the timing is dependent on the wakeup and activation time of my RAID array in my NAS. Which can't be measured very easily. And on the other hand, you want this as short as possible, to avoid unneeded allocation of a tuner.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (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: Timer & motorised dish - logic #9 ColinB

  • Senior Member
  • 743 posts

+28
Good

Posted 26 January 2018 - 22:35

Sorry if this sounds really dumb.

 

If a tuner had via a switch "A/B" ,  a motor (A) & another LNB (B)

 

Could Enigma send a quick GoTo to the motor(A) and return to the service on (B) ?

 

I'm thinking No, unless the motor/rotor had its own power.


Xtrend et8000 7.1-Release

2 x 8/1 DiSEqC  30w 13e 19e 23e 28e   

Astrometa USB Tuner Working DVB-T2 now on Kernel 4.10+  ;)

WD10EARX 1TB

Sandisk 32GB USB for AFB, EPG, Picons & Timeshift

 

ZGemma Star S 7.0-Release

4/1 DiSEqC  30w 13e 19e 28e

Sandisk 8GB USB for AFB, EPG, Picons & Timeshift

 

LG 49UH610V UHD-HDR

UHF/Cable/Sat

 

E-Channelizer

 

 

 


Re: Timer & motorised dish - logic #10 Robinson

  • Senior Member
  • 2,614 posts

+30
Good

Posted 26 January 2018 - 22:41

So it would perhaps not be a bad idea to have this value configurable?

 

I would really appreciate it. I assume this setting should only be visible in the EXPERT mode.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Timer & motorised dish - logic #11 Robinson

  • Senior Member
  • 2,614 posts

+30
Good

Posted 26 January 2018 - 22:44

Cannot we compute the maximum time a motor will take to go from one extremity to the other one and add a few more seconds for security, this is worst case and the longer time a motor can be in movement.  So define this value instead of the 20 seconds?

 

Worst case scenario for a motor should not be longer than 90-100 seconds but because WanWizard has found a completely different reason to have this configurable I would kindly ask for a configuration option.

Thank you.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Timer & motorised dish - logic #12 ColinB

  • Senior Member
  • 743 posts

+28
Good

Posted 26 January 2018 - 22:48

AFIK the motor speed is dependent on the polarity of the channel you are tuning to. H or V, something to do with the voltages if I remember


Xtrend et8000 7.1-Release

2 x 8/1 DiSEqC  30w 13e 19e 23e 28e   

Astrometa USB Tuner Working DVB-T2 now on Kernel 4.10+  ;)

WD10EARX 1TB

Sandisk 32GB USB for AFB, EPG, Picons & Timeshift

 

ZGemma Star S 7.0-Release

4/1 DiSEqC  30w 13e 19e 28e

Sandisk 8GB USB for AFB, EPG, Picons & Timeshift

 

LG 49UH610V UHD-HDR

UHF/Cable/Sat

 

E-Channelizer

 

 

 


Re: Timer & motorised dish - logic #13 Robinson

  • Senior Member
  • 2,614 posts

+30
Good

Posted 26 January 2018 - 22:56

Yes, worst-case scenario is vertical polarity but it does not mean that different rotors with different dishes turn at the same speed.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Timer & motorised dish - logic #14 ColinB

  • Senior Member
  • 743 posts

+28
Good

Posted 26 January 2018 - 23:18

So best solution is to make timer record, even if no service is available at the start time ?


Xtrend et8000 7.1-Release

2 x 8/1 DiSEqC  30w 13e 19e 23e 28e   

Astrometa USB Tuner Working DVB-T2 now on Kernel 4.10+  ;)

WD10EARX 1TB

Sandisk 32GB USB for AFB, EPG, Picons & Timeshift

 

ZGemma Star S 7.0-Release

4/1 DiSEqC  30w 13e 19e 28e

Sandisk 8GB USB for AFB, EPG, Picons & Timeshift

 

LG 49UH610V UHD-HDR

UHF/Cable/Sat

 

E-Channelizer

 

 

 


Re: Timer & motorised dish - logic #15 Robinson

  • Senior Member
  • 2,614 posts

+30
Good

Posted 26 January 2018 - 23:38

I'm not sure what you mean.

Best solution is probably to give a user a choice of how long before the actual recording is supposed to start the tuner should be allocated, which means "self.prepare_time" should be configured freely between, let's say, 0 and 300 [seconds].


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Timer & motorised dish - logic #16 Robinson

  • Senior Member
  • 2,614 posts

+30
Good

Posted 22 February 2018 - 08:56

Any chance to implement a configurable setting for tuner allocation time, please?


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Timer & motorised dish - logic #17 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 22 February 2018 - 11:25

Actually there is: in advanced motor settings (turn speed).
That value is neatly used to show the 'moving dish' time, but apparently not for adjusting the time-out for recordings (hence failed recordings).

Re: Timer & motorised dish - logic #18 Robinson

  • Senior Member
  • 2,614 posts

+30
Good

Posted 22 February 2018 - 12:12

The turn speed is not used for tuner allocation for timer recordings.

No matter what turn speed is set, tuner is always allocated 20 seconds before the timed recording is supposed to start.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Timer & motorised dish - logic #19 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 22 February 2018 - 12:45

Yep, that's what I meant.
The values are known to E2, and (only?) used for GUI-presentation, but not for (time-out in) tuner allocation.

Re: Timer & motorised dish - logic #20 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 22 February 2018 - 12:46

I also run into this issue, when the motor is pointing in a very wrong direction. But it seems to be a rather recent issue; I can't remember having this issue in the (far?) past.


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users