Unicable and dropped recordings

[Huevos]

Increase that delay to 2500. This is for test purposes.

Here I am using the Vu+ Ultimo 4K for testing and don't see any of your problems regarding tuning failed messages... but the Ultimo keeps the LNB permanently powered.

 

[abu baniaz]

As per bug report and other thread, even 9900 does not solve problem

 

[Arcy]

Increase that delay to 2500. This is for test purposes.

Here I am using the Vu+ Ultimo 4K for testing and don't see any of your problems regarding tuning failed messages... but the Ultimo keeps the LNB permanently powered.

The GigaBlue doesn't, and neither does my Inverto SAT>IP, which is fed via a splitter from the same LNB (it uses different SCRs).

Increasing that setting doesn't seem to make much difference, except possibly to make channel changes slightly slower. Switching between channels or even transponders on the same satellite normally happens almost instantly. But switching from a radio station on 28.2E to a radio station on another satellite takes 2-3 seconds. Switching from another satellite back to 28.2 takes about 7 seconds for radio, a little more for TV, and in either case I always see the 'Tune failed' message before the 28.2E channel appears. The only case I've found where switching to a different satellite produces 'Tune failed' occurs when switching to BFBS radio on 19.2E. This is odd. There may be other examples, of course.

So I'm wondering whether this receiver is just a bit buggy. I made several unsuccessful attempts this morning to reproduce the problem where a timer recording just starting kills a recording already in progress. But when I tried switching between BBC Radio (28.2E) and BFBS (19.2E) while a recording was in progress on BBC Radio 4, the receiver wouldn't play that or any other channel on the BBC transponder. It could nevertheless play radio channels on other 28.2E transponders, but only after a 7-8 second wait. Only the first three minutes of the recording were saved.

In another condition, which I've seen before, the TV picture blinks momentarily at irregular intervals. When this happens, I can no longer select from the channel list and many of the other keys on the remote control do not respond either. I can still change channels with the CH up/down buttons, but the blinking continues. To clear the problem, I reboot the receiver via the web interface.

 

[twol]

Can you just try a simple setup without any plugins and the LNB set to normal mode as per post #14.......

On my Giga‘s I have 3 Sat dishes coming into the FBC tuners plus a plugin DVB-s2x tuner - and I don‘t get any of these issues and certainly no delays between switching - and the FBC tuner on this box is the same as the Vu+ and to the best of my memory (it was a long time ago now) power to the LNB is the same for both Vu+ & Giga (initially there were options in tuner setup to turn on/off power to the LNB)

 

[redrobin]

I've the same delay problem as per thread https://www.world-of-satellite.com/showthread.php?62329-Tune-Failed which occurs when switching from motor to unicable.

 

[Huevos]

"[STRIKE]Delay after enable voltage before switch command[/STRIKE]" -> "Unicable delay after enable voltage before switch command"

 

[twol]

I've the same delay problem as per thread https://www.world-of-satellite.com/showthread.php?62329-Tune-Failed which occurs when switching from motor to unicable.

Which receiver, which LNB, tuner config??

 

[redrobin]

Which receiver, which LNB, tuner config??

Gigablue Ultra UE 4K - GT-Sat GT-dLNB1DY Unicable LNB, not at my receiver at the moment, but off the top of my head A is Unicable, B-H are linked to A, and I is my motor.

 

[twol]

Gigablue Ultra UE 4K - GT-Sat GT-dLNB1DY Unicable LNB, not at my receiver at the moment, but off the top of my head A is Unicable, B-H are linked to A, and I is my motor.

When you have a chance, just for my sanity! Disable B and see what happens

 

[Huevos]

I've the same delay problem as per thread https://www.world-of-satellite.com/showthread.php?62329-Tune-Failed which occurs when switching from motor to unicable.

"[STRIKE]Delay after enable voltage before switch command[/STRIKE]" -> "Unicable delay after enable voltage before switch command"

 

[redrobin]

Disabled tuner B, rebooted, no change.

Huevos - should the value be increased or decreased ?

 

[Arcy]

Disabled tuner B, rebooted, no change.

Huevos - should the value be increased or decreased ?

I've just changed mine from 0200 to 0800, and my initial impression is that it has solved my problem as far as Unicable is concerned. Channel changes from one Unicable service to another now take less than one second. Switching from Unicable to a channel on an ordinary DVB tuner takes a couple of seconds -- but switching back to a Unicable channel takes much longer -- eight or nine seconds -- and the "Tune failed" message pops up briefly just before the picture appears. But at least it gets there. I'm now hoping that this will have solved my problem with dropped recordings.

Much thanks to Huevos!

 

[Huevos]

If you still get the message switching back to the Unicable LNB, add some more delay. You should never get a tune failed message.

 

[Arcy]

I've doubled my 'Unicable delay after enable voltage before switch command' to 1600, and it simply increases the delay before the 'Tune failed!' message appears. So it doesn't seem to have helped. My other Satellite equipment setup parameters are all at the default values.

The delay is not a major nuisance, since the selected channel does appear at the end of it. But I wonder there's some other setting that might have an influence on it.

 

[redrobin]

In my case, switching between Unicable channels hasn't been a problem, its only switching from the motor back to a unicable channel which causes the 'Tuner failed' message before displaying the channel.
Changing the parameter doesn't seem to be having any change.

This has only occured since updating the VIX version (as per my original post).

 

[Arcy]

In my case, switching between Unicable channels hasn't been a problem, its only switching from the motor back to a unicable channel which causes the 'Tuner failed' message before displaying the channel.

That makes two of us, then.

 

[abu baniaz]

Try using 2700 value. When you are using the motor, i.e not using unicable LNB, the Unicable LNB goes to sleep. Needs more time to wake up.

 

[redrobin]

2700 has stopped the tune fail message, takes a while to display channel but it's acceptable.

 

[Arcy]

Looks like I gave up increasing the value a bit too soon. I've now found that with a value of 1700 I still get the long delay and the 'Tune failed!" message. But with 1800, the message no longer appears and the delay on switching back to Unicable is roughly halved So I've set it to 2000 to allow a bit of a margin.

 

[Arcy]

As a postscript to the above, I decided to disconnect everything and start all over again, using an Inverto 32-band Unicable II multiswitch (IDLU-UWT110-CUO10-32P). This now feeds 28.2E to all three receivers (GigaBlue UHD Quad 4K, Vu+ Solo 4K and Inverto Multibox SAT>IP server, connected via a three-way Dur-line splitter with power pass) -- which occupy 20 User Bands in all. And I was thrilled to find that they all worked straight away, with (so far) no tuning problems or other interactions, and no interrupted recordings. I am powering the Unicable switch over the downlead, using the supplied PSU and injector, to avoid uncertainty over relying on the receivers for power.

I don't know what was causing the problems I had earlier, though it can't have been any of the receivers or the Spaun Unicable I switch. Misconfiguration seems the most likely explanation, though I checked my settings no end of times. My thanks to posters in this thread for their advice.