in vdr-1.7.28 without patches
while browsing the log I found
Jun 9 05:28:08 server vdr: [13569] frontend 1/0 timed out while tuning to channel 1877, tp 212713 Jun 9 05:28:40 server vdr: [13569] frontend 1/0 regained lock on channel 14, tp 110743
so frontend 1 regained a lock it never had. That seems like a consequence of the fact that LostLock is only a local variable in cDvbTuner::Action, so it cannot be reset when the channel changes
also, I wonder about this code sequence in dvbdevice.c:
switch (tunerStatus) { ... case tsLocked: if (Status & FE_REINIT) { ... else if (tunerStatus == tsLocked) {
at the "else if", how could tunerStatus not be tsLocked?
On 09.06.2012 11:24, Reinhard Nissl wrote:
I guess that's a matter of philosophy. In normal operation the frontend doesn't report any such messages,so everything is fine. When the frontend loses the lock for any reason, I think it make sense to have it report back whenever it has regained the lock. If, in the meantime, the channel has been changed, well, then regaining the lock just so happens on a different channel.
Resetting LostLock in case tsSet could lead to logs where a frontend reports that it has lost the lock, but never reports when it has regained it.
Klaus
Am Samstag, 9. Juni 2012, 12:02:37 schrieb Klaus Schmidinger:
fine with me - I was just wondering.
I was looking at those things because I had some trouble with my 3 USB TT S2-3600 receivers. They very often lost lock. Putting them in a cooler place helped a bit. Better cabling helped a bit. Updating the receiver firmware (bought in 2012, update from 2008 was not applied!) helped a bit. Optimizing my Quad Monoblock for Astra helped a bit. At that stage, often all 3 receivers lost lock at the same time. And all that only with DVB-S2 channels. And mostly in early evening (which still puzzles me)
At the end it seems the LNB had a problem. I now have another one and no lost locks since 12 hours.
-
Klaus Schmidinger -
Reinhard Nissl -
Wolfgang Rohdewald