Upgraded LNB now get Tune Failed message

[White Monk]

I have a VU+ Ultimo 4K bought from WoS a while ago and am happy with it. I recently upgraded the f/w to 6.3.002.

I had a Technisat 4+4 LNB installed pointing at 28.2E. The SCR output was feeding Tuner I with Tuners K, L and M all set up and working. The legacy outputs were feeding my recently purchased (from WoS) Octagon box, a Freesat TV and a Freesat 4K Box. All perform okay.

Next, I uninstalled Tuner M and using a splitter connected the Octagon to the SCR using the now available Userband 4. No problems.

I then bought a GT-SAT GT-S3dCSS24 and swapped out the Technisat LNB. The three legacy outputs are now feeding the Freesat TV and a Freesat 4K Box. All work okay.

The cabling indoors remained unchanged.

I set up the Octagon to Userband 1 (975 MHz) and tried Userband 2 (1025MHz) as well. No problems. So far, so good.

Next came the task of reconfiguring the VU+'s tuners, which should have been straightforward. I randomly chose Userband 11 (1475 MHz) for Tuner I and followed on with Tuners K, L and M. Initially, I chose 'User defined' for 'SCR type', with 'SCR JESS' for 'Format', but later on in another post found that 'dLNB dHello' was the correct 'Model' and 'Manufacturer' 'GT-SAT' which chose the correct frequency for the Userband.

Then I got the Tune Failed message.

I rechecked my typing then hit the forums for help. I downloaded 'satelliteequipmentcontrol' plugin and followed the relevant post by starting at 0800 and moving upwards then stopped at 2500.

Not sure what to do next. I attach a couple of relevant screenshots.

6474864749

[twol]

I have a VU+ Ultimo 4K bought from WoS a while ago and am happy with it. I recently upgraded the f/w to 6.3.002.

I had a Technisat 4+4 LNB installed pointing at 28.2E. The SCR output was feeding Tuner I with Tuners K, L and M all set up and working. The legacy outputs were feeding my recently purchased (from WoS) Octagon box, a Freesat TV and a Freesat 4K Box. All perform okay.

Next, I uninstalled Tuner M and using a splitter connected the Octagon to the SCR using the now available Userband 4. No problems.

I then bought a GT-SAT GT-S3dCSS24 and swapped out the Technisat LNB. The three legacy outputs are now feeding the Freesat TV and a Freesat 4K Box. All work okay.

The cabling indoors remained unchanged.

I set up the Octagon to Userband 1 (975 MHz) and tried Userband 2 (1025MHz) as well. No problems. So far, so good.

Next came the task of reconfiguring the VU+'s tuners, which should have been straightforward. I randomly chose Userband 11 (1475 MHz) for Tuner I and followed on with Tuners K, L and M. Initially, I chose 'User defined' for 'SCR type', with 'SCR JESS' for 'Format', but later on in another post found that 'dLNB dHello' was the correct 'Model' and 'Manufacturer' 'GT-SAT' which chose the correct frequency for the Userband.

Then I got the Tune Failed message.

I rechecked my typing then hit the forums for help. I downloaded 'satelliteequipmentcontrol' plugin and followed the relevant post by starting at 0800 and moving upwards then stopped at 2500.

Not sure what to do next. I attach a couple of relevant screenshots.

6474864749

Not sure if it will help, but there is a plugin forcefbclnbpower

[Huevos]

Socket on Vu fbc is powered full time.

[White Monk]

Thanks for your fast responses.

@twol - I looked in the plugin list but couldn't see it - setup/plugins/system.

@huevos - not sure if this a setting somewhere or refers to @twol's post.

This morning, I've removed the 'satelliteequipmentcontrol' plugin and performed a factory reset. The only user plugin I have is for the USB T2 Turbo V2 tuner (Tuner S).

I removed the splitter from the SCR feed and connected it direct to the Octagon. The Unicable tuner only accepts Userbands 1 thru 8, all of which work. It does seem a bit sluggish changing channels though.

I disconnected all other LNB cables from the VU+ box and reconnected the SCR feed direct to Tuner A set it up for Userband 11 as before and did a scan on 10714H.

Nothing found.

[twol]

Thanks for your fast responses.

@twol - I looked in the plugin list but couldn't see it - setup/plugins/system.

@huevos - not sure if this a setting somewhere or refers to @twol's post.

This morning, I've removed the 'satelliteequipmentcontrol' plugin and performed a factory reset. The only user plugin I have is for the USB T2 Turbo V2 tuner (Tuner S).

I removed the splitter from the SCR feed and connected it direct to the Octagon. The Unicable tuner only accepts Userbands 1 thru 8, all of which work. It does seem a bit sluggish changing channels though.

I disconnected all other LNB cables from the VU+ box and reconnected the SCR feed direct to Tuner A set it up for Userband 11 as before and did a scan on 10714H.

Nothing found.
.. probbaly I missed it but if you use Userbands 1 _> 8 on the Vu+??

[White Monk]

.. probbaly I missed it but if you use Userbands 1 _> 8 on the Vu+??

Sadly not. I guess I ought to have mentioned it in my first post. I tried random Userbands.

In the meantime, I've fed Tuner R from our IRS temporarily and disabled Tuner A so I can use ABM to create a Freesat bouquet.

I hope WoS will give me a refund on this LNB if we can't resolve this problem. Still got the box!

[abu baniaz]

You really ought to send a screenshot of all the tuner settings, not just the main one.


There may be a bug in code where a change in Unicable bands is not saved. There is a change in the developer image that addresses this. Can you try following:
issue following command using Putty/terminal:
init 4
Using FTP, navigate to /etc/enigma2
Edit the file called settings with following changes: delete all the lines that start/have nim
Save, ensure ftp transfer back completes
Restart with following command:
init 3


Or flash a new image, do not restore anything and start from scratch

[Huevos]

The Unicable tuner only accepts Userbands 1 thru 8, all of which work.What does that mean? What does "Unicable tuner" mean? And then you say "only accepts Userbands 1 thru 8" and you config "11"?

[Huevos]

Also are you sure you are selecting the correct LNB? Do yo have the spec sheet that came with it?

[abu baniaz]

Do yo have the spec sheet that came with it?
If it is the LNB that he mentioned, those frequencies were added by Sicilian and are correct. All the GT-sat Hello range use the same 24 frequency bands.

[White Monk]

What does that mean? What does "Unicable tuner" mean? And then you say "only accepts Userbands 1 thru 8" and you config "11"?

I apologise for not being clear. I have two devices which are now connected to a single Unicable feed:

1] Vu+ Ultimo 4K bought from WoS with a variety of tuners and inputs, one of which is a FBC Tuner originally connected to a Technisat 4+4 LNB's SCR output. The Unicable/JESS allows lots of userbands. When I upgraded the LNB, I just chose 11 randomly and it didn't work.

2] Octagon SFX6018 recently supplied by WoS. I set it up originally on a feed from a universal LNB but wanted to transfer it to the Unicable feed so I nicked userband 4 from the Vu+. The tuner's setup dialogue only accepts userbands 1 to 8. It is currently set at userband 1 and works.

[White Monk]

Also are you sure you are selecting the correct LNB? Do yo have the spec sheet that came with it?

By this, do you mean chose the correct LNB for my upgrade? I chose the GT-SAT GT-S3dCSS24 as it was available from WoS. There was no spec sheet supplied with it, only a small piece of paper with the userband's frequency list. The manufacturer's webpage for this LNB contains a few errors.

[White Monk]

You really ought to send a screenshot of all the tuner settings, not just the main one.


There may be a bug in code where a change in Unicable bands is not saved. There is a change in the developer image that addresses this. Can you try following:
issue following command using Putty/terminal:
init 4
Using FTP, navigate to /etc/enigma2
Edit the file called settings with following changes: delete all the lines that start/have nim
Save, ensure ftp transfer back completes
Restart with following command:
init 3


Or flash a new image, do not restore anything and start from scratch

Thanks for this.

It's been a while since I used Putty so I'll have to install it and re-educate myself!

Regarding the latter comment, do you mean re-flash with the current VIX image from a USB plugged into the front socket and not taking the option to restore a backup? I have used this method several times already. Would it be worth trying a different image?

[abu baniaz]

If you did not restore settings after flashing the image, there would be no old entries to delete using Putty.

Your original post is full of extraneous text. Let us just deal with the Vu+.
Can you describe again the wiring from LNB to Vu +.
Post screenshots of all the tuner settings for the Vu+. (This is the second time of asking. It will cut through the mud and get to a solution very quickly. Please attach all of them.)

[Willo3092]

I'm using an SF8008 on the same LNB as the OP.

My settings file nims section is like this:

config.Nims.0.advanced.lnb.1.bootuptime=2500
config.Nims.0.advanced.lnb.1.lof=unicable
config.Nims.0.advanced.lnb.1.powerinserter=False
config.Nims.0.advanced.lnb.1.scrList=9
config.Nims.0.advanced.lnb.1.unicableManufacturer= GT-SAT
config.Nims.0.advanced.lnb.1.unicableProduct=GT-S3DCSS24
config.Nims.0.advanced.sat.282.lnb=1
config.Nims.0.advanced.sats=282
config.Nims.0.configMode=advanced
config.Nims.0.diseqcA=282
config.Nims.0.diseqcB=3601
config.Nims.0.diseqcC=3601
config.Nims.0.diseqcD=3601
config.Nims.1.advanced.lnb.1.bootuptime=2500
config.Nims.1.advanced.lnb.1.lof=unicable
config.Nims.1.advanced.lnb.1.powerinserter=False
config.Nims.1.advanced.lnb.1.scrList=10
config.Nims.1.advanced.lnb.1.unicableManufacturer= GT-SAT
config.Nims.1.advanced.lnb.1.unicableProduct=GT-S3DCSS24
config.Nims.1.advanced.sat.282.lnb=1
config.Nims.1.advanced.sats=282
config.Nims.1.configMode=advanced
config.Nims.1.configModeDVBT=True
config.Nims.1.diseqcA=282
config.Nims.1.diseqcB=3601
config.Nims.1.diseqcC=3601
config.Nims.1.diseqcD=3601
config.Nims.1.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)

[White Monk]

If you did not restore settings after flashing the image, there would be no old entries to delete using Putty.

Your original post is full of extraneous text. Let us just deal with the Vu+.
Can you describe again the wiring from LNB to Vu +.
Post screenshots of all the tuner settings for the Vu+. (This is the second time of asking. It will cut through the mud and get to a solution very quickly. Please attach all of them.)

LNB Cabling. Single cable from SCR outlet to Tuner A. One join where the splitter was.

Reflashed. Added driver plugin for USB Turbo2 Vtuner. Added satelliteequipmentsetup plugin ready for action.

Setup Tuners A, B, C and S. Single TP scan for Tuner - Okay. Full scan for Tuner S - Okay

Problem doing single TP scan for Tuner A - got Tune Failed.

One comment. After reboot, got Tune Failed. Disabled Tuner A, displayed last channel by Tuner B. Re-enabled Tuner A

64768
64769
64770
64771
64772
64773

[White Monk]

Sorry - left out 'B' for the first tuner scan

[twol]

Sorry - left out 'B' for the first tuner scan

I have probably missed it, but whats on B? Attached to what?

[White Monk]

I'm using an SF8008 on the same LNB as the OP.

My settings file nims section is like this:

config.Nims.0.advanced.lnb.1.bootuptime=2500
config.Nims.0.advanced.lnb.1.lof=unicable
config.Nims.0.advanced.lnb.1.powerinserter=False
config.Nims.0.advanced.lnb.1.scrList=9
config.Nims.0.advanced.lnb.1.unicableManufacturer= GT-SAT
config.Nims.0.advanced.lnb.1.unicableProduct=GT-S3DCSS24
config.Nims.0.advanced.sat.282.lnb=1
config.Nims.0.advanced.sats=282
config.Nims.0.configMode=advanced
config.Nims.0.diseqcA=282
config.Nims.0.diseqcB=3601
config.Nims.0.diseqcC=3601
config.Nims.0.diseqcD=3601
config.Nims.1.advanced.lnb.1.bootuptime=2500
config.Nims.1.advanced.lnb.1.lof=unicable
config.Nims.1.advanced.lnb.1.powerinserter=False
config.Nims.1.advanced.lnb.1.scrList=10
config.Nims.1.advanced.lnb.1.unicableManufacturer= GT-SAT
config.Nims.1.advanced.lnb.1.unicableProduct=GT-S3DCSS24
config.Nims.1.advanced.sat.282.lnb=1
config.Nims.1.advanced.sats=282
config.Nims.1.configMode=advanced
config.Nims.1.configModeDVBT=True
config.Nims.1.diseqcA=282
config.Nims.1.diseqcB=3601
config.Nims.1.diseqcC=3601
config.Nims.1.diseqcD=3601
config.Nims.1.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)

I'm not too clued up on what this means, but I saw in one of the stickies that these complex LNBs need a bit of extra time to do things hence me loading up the satelliteequipmentsetup plugin ready for Abu, just in case it's needed :confused:

I've got 6.3.002 loaded on slot 2 of my SFX6018 which I believe uses the same image as yours but that's a topic for another day.

[White Monk]

Sorry - left out 'B' for the first tuner scan

line 3 of my previous post. Tuner B was the first tuner I set up. It's on one of the legacy ports of this LNB.

Apologies for leaving this out of my reply to Abu.

[Huevos]

Right now we are concerned with tuner A only.
Disable all other tuners.
Use user band 1.
Plug the aerial cable direct in tuner A.
Do not use any splitter or other device, must be direct.
Send an image of the back of the box showing the one cable and where it is inserted.
Go in signal finder and see if it is showing signal.

[Willo3092]

This is the settings for Tuner A on my SF8008. Tuner B is the same apart from SCR10.
I think the delay of 2500 is automatically set after choosing the LNB in settings.
It is set in /usr/share/enigma2/unicable.xml.

64774

I notice that the delay is slightly longer on DLNB dHello.


<manufacturer name="GT-SAT">
<product name="GT-S1-2-3SCR4" scrs="1210,1420,1680,2040"/>
<product name="dLNB dHello" format="jess" bootuptime="2700" scrs="0975,1025,1075,1125,1175,1225,1275,1325,1375,1425, 1475,1525,1575,1625,1675,1725,1775,1825,1875,1925, 1975,2025,2075,2125"/>
<product name="GT-dLNB1-T" format="jess" bootuptime="2700" scrs="0975,1025,1075,1125,1175,1225,1275,1325,1375,1425, 1475,1525,1575,1625,1675,1725,1775,1825,1875,1925, 1975,2025,2075,2125"/>
<product name="GT-dLNB1-DY" format="jess" bootuptime="2700" scrs="0975,1025,1075,1125,1175,1225,1275,1325,1375,1425, 1475,1525,1575,1625,1675,1725,1775,1825,1875,1925, 1975,2025,2075,2125"/>
<product name="GT-S1dCSS24" format="jess" bootuptime="2500" scrs="0975,1025,1075,1125,1175,1225,1275,1325,1375,1425, 1475,1525,1575,1625,1675,1725,1775,1825,1875,1925, 1975,2025,2075,2125"/>
<product name="GT-S2dCSS24" format="jess" bootuptime="2500" scrs="0975,1025,1075,1125,1175,1225,1275,1325,1375,1425, 1475,1525,1575,1625,1675,1725,1775,1825,1875,1925, 1975,2025,2075,2125"/>
<product name="GT-S3DCSS24" format="jess" bootuptime="2500" scrs="0975,1025,1075,1125,1175,1225,1275,1325,1375,1425, 1475,1525,1575,1625,1675,1725,1775,1825,1875,1925, 1975,2025,2075,2125"/>

[Huevos]

On a Vu the delay is academic because the socket is permanently powered.

[abu baniaz]

I am slightly confused about your hardware/wiring physical setup. You keep mentioning configuring tuner before describing wiring. For tuner config to be correct, it must match the hardware. To me, best to describe hardware first, then tuner config. From what I can make out from your descriptions, you do not have any wires hooked up to tuner A ( top slot of first card/matrix). So no wonder it is not working. The "connected to" ( what I describe as "through another tuner") only works on the same tuner module/matrix. When you say "Tuner B" I think you are saying the module B (i.e tuners I-P)

Please also post a screenshot of Menu > Information > Devices

May I suggest the following:
Disconnect the USBT tuner (just for now)
Please flash image again. Do not restore settings/plugins after flashing (i.e you are starting from scratch).

For now (in line with exiting train of thought/testing):
Hardware:
Hook up signal wire from Unicable port to top hole of the first tuner/matrix. I.e tuner A.
Configure tuner A to unicable. Remember it has it's own signal wire, so you are not going through another tuner, so "connected to" must be no.
Disable all other tuners.
Scan/Test it is working.

Stage 2.
Do not touch wiring/do not install USB tuner.
Configure tuner B-H as unicable. You are going through tuner A, so connected must be yes.
Check signal on all tuners.

Stage 3:
Re-add splitter
One wire to go to top slot of first module (tuner A)
One wire to go to top slot of second module (tuner I)
Leave tuners I-P as not configured
Test tuners A-H

Stage 4
Hardware still as in stage 3
Configure tuner I as unicable. It has a wire from splitter, so connected = no
Configure tuner J-P as unicable. They do not have thir own wire and you are going through the wire in tuner I, so connected = yes
Test all the tuners.

Stage 5.
Re-add the USB tuner. Install drivers
Repeat the signal tests

[abu baniaz]

I suppose this is the issue when people refer to letters on casing instead of the actual tuner letters. I hope this picture helps.

[White Monk]

On a Vu the delay is academic because the socket is permanently powered.

So no point installing the satelliteequipmentsetup plugin?

[White Monk]

I am slightly confused about your hardware/wiring physical setup. You keep mentioning configuring tuner before describing wiring. For tuner config to be correct, it must match the hardware. To me, best to describe hardware first, then tuner config. From what I can make out from your descriptions, you do not have any wires hooked up to tuner A ( top slot of first card/matrix). So no wonder it is not working. The "connected to" ( what I describe as "through another tuner") only works on the same tuner module/matrix. When you say "Tuner B" I think you are saying the module B (i.e tuners I-P)

Please also post a screenshot of Menu > Information > Devices

May I suggest the following:
Disconnect the USBT tuner (just for now)
Please flash image again. Do not restore settings/plugins after flashing (i.e you are starting from scratch).

For now (in line with exiting train of thought/testing):
Hardware:
Hook up signal wire from Unicable port to top hole of the first tuner/matrix. I.e tuner A.
Configure tuner A to unicable. Remember it has it's own signal wire, so you are not going through another tuner, so "connected to" must be no.
Disable all other tuners.
Scan/Test it is working.

Stage 2.
Do not touch wiring/do not install USB tuner.
Configure tuner B-H as unicable. You are going through tuner A, so connected must be yes.
Check signal on all tuners.

Stage 3:
Re-add splitter
One wire to go to top slot of first module (tuner A)
One wire to go to top slot of second module (tuner I)
Leave tuners I-P as not configured
Test tuners A-H

Stage 4
Hardware still as in stage 3
Configure tuner I as unicable. It has a wire from splitter, so connected = no
Configure tuner J-P as unicable. They do not have thir own wire and you are going through the wire in tuner I, so connected = yes
Test all the tuners.

Stage 5.
Re-add the USB tuner. Install drivers
Repeat the signal tests

Thanks for this. I've printed your post off. I'll follow your instructions and report back.

[White Monk]

Before starting Abu's suggestion, I've confirmed that the cable from the SCR output is ok by connecting it to my SFX6018. This also will confirm that a signal is present!

64776

64777

I'll now transfer the cable to Tuner A of the Vu+

[White Monk]

Cable transferred to Tuner A, USB stick installed, USBT tuner confirmed disconnected. Reflashed. No restore, no plugins.

Configured Tuner A, others disabled.

64778

Attempted both full and single tp scans.

64779

Confirmed by Signal Finder

64780

Shall I continue with Stage 2? I have confirmed that a signal is being received by the LNB via one of the legacy feeds.

[Huevos]

1) No point adding the plugin for this parameter on the Vu.
2) Send a photo of the back of your receiver with the one cable inserted.
3) Send a screenshot of the tuner config of the Octagon tuner that you say is working.

[White Monk]

1) No point adding the plugin for this parameter on the Vu.
2) Send a photo of the back of your receiver with the one cable inserted.
3) Send a screenshot of the tuner config of the Octagon tuner that you say is working.

2)

64781

3) Already have - see post #28

[Huevos]

So set it identical to that. If doesnt work retest in the octagon, pluging the exact same cable in the octagon.

[White Monk]

So set it identical to that. If doesnt work retest in the octagon, pluging the exact same cable in the octagon.

But I've already done that today. The tuner setups in both boxes are the same apart from the passband. The passband chosen doesn't affect the outcome. I had the Octagon sitting on top of the Vu+ and swapped the RJ45, HDMI and LNB cable between the two.

[abu baniaz]

Sorry, I am out of ideas. The last thing I could suggest is to try ATV, they have different FBC code. Select reliable tune. I have a duo 4k and also the gt-sat. Last time I had vix on the receiver it worked with that LNB.

May I take the opportunity to emphasise putting receiver in deep standby before removing the HDMI cable. I also use to think this was non-sense until swapping HDMI burned the chip on my GB UE 4K.

[twol]

But I've already done that today. The tuner setups in both boxes are the same apart from the passband. The passband chosen doesn't affect the outcome. I had the Octagon sitting on top of the Vu+ and swapped the RJ45, HDMI and LNB cable between the two.
So what happens if you disable A/B and connect to teh 2nd FBC tuner I/J

[White Monk]

With the same cabling as before on the Vu+, I swapped the LNB with two others - the original Technisat, an Inverto which I have bought for Tuner I in the future and back to the GT-SAT.

Technisat - success

64783

Inverto - success

64784

GT-SAT - nothing

64785

[White Monk]

Sorry, I am out of ideas. The last thing I could suggest is to try ATV, they have different FBC code. Select reliable tune. I have a duo 4k and also the gt-sat. Last time I had vix on the receiver it worked with that LNB.

May I take the opportunity to emphasise putting receiver in deep standby before removing the HDMI cable. I also use to think this was non-sense until swapping HDMI burned the chip on my GB UE 4K.

Regarding your last comment - a very timely reminder. Thank you!

A couple of days ago Amazon (DE) delivered a DUR-line UK 124-3L dCSS LNB.
This morning (when it got light) I swapped the LNB and decided to bite the bullet.
Connected a splitter for the Octagon and the Vu+. Connected another splitter to feed Tuner A and Tuner I.
Reconnected USBT along with its terrestrial feed.
Connected a lead from a DiSEqC switch (13.0E/19.2E/23.5E/9E) to Tuner Q
Checked all leads. Had breakfast.
Fired up the Octagon and set it to userband 1 Tuned up BBC1 Lon HD no problems. Rebooted to the other image and that worked too. Had a coffee.
Booted up the Vu+ and reflashed it. No restore, set up tuners A (ub9), B (ub10), I (ub17), J (ub18), and Q. Loaded driver for USBT, rebooted and set up tuner S and did a scan - no problems.
Selected tuner Q and did single channel scans on the four satellites. All okay except 23.5E, which has a known problem (to be sorted 'another day')
Set up the remaining leaf tuners with userbands 11-16 and 19-24.
Tested all tuners with Signal Finder. All okay.
Wrote this post.
Going to take an image and settings backup, then have a sandwich.

Part of me wants to get to the bottom of the problem with the GT-SAT LNB and the Vu+. You are probably on the right track that a change of image may fix it.
The other part of me wants to move on with my life now I've got a working system. It would be the icing on the cake if WoS refunded me with the cost of the GT-SAT LNB.

[Willo3092]

I've got GT-SAT GT-S3DCSS24 & GT-dLNB1-DY and both work fine with the FBC tuners on my Vu+ Uno 4K using ViX 6.3.

[White Monk]

I've got GT-SAT GT-S3DCSS24 & GT-dLNB1-DY and both work fine with the FBC tuners on my Vu+ Uno 4K using ViX 6.3.

If that is the case then it looks as I may have been sold a dodgy one :eek:

[Willo3092]

If that is the case then it looks as I may have been sold a dodgy one :eek:

Maybe :confused: the only thing different in my settings apart from the scr is the model number of the lnb.
I think the dLNB dHello is generic and covers all GT-SAT models.

64786

Are you sure you're not connected to one of the legacy ports?
Have you tried changing the settings to Simple > Automatic to see if anything is detected?

.... sorry, I see that you've used other LNB's on the same cable, forget that.

[HeadBanger]

I’m getting the same random ‘tune failed’ messages after upgrading to v6.3. VU+ Uno 4K SE with Gigablue LNB.

I can start a new thread if required but it does seem like the same issue. Did something change with how the Uni cable stuff works with Vix 6.3?

HB

[twol]

I’m getting the same random ‘tune failed’ messages after upgrading to v6.3. VU+ Uno 4K SE with Gigablue LNB.

I can start a new thread if required but it does seem like the same issue. Did something change with how the Uni cable stuff works with Vix 6.3?

HB

Really can think of no changes and I have been playing heavily with a Vu+ Uno SE plus 2 unicable inputs over the last 4 weeks - so pretty sure I would have noticed.
So start a new thread and post configuration and setup.

[White Monk]

I've moved up to 6.3 too. Everything is still OK with my DUR-Line LNB. However, I did choose to start from scratch - flash from USB, without backup restore. I've had a few 'tuner reset' type problems in the past and found that this was the only sure-fire way to fix them.