Upgraded LNB now get Tune Failed message

[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

Tuners 1.jpg
Tuners 2.jpg
Tuner A.jpg
Tuner B.jpg
Tuner C.jpg
Tuner S.jpg

[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

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.

1_0_19_CD6E_844_2_11A0000_0_0_0_20230218152742.jpg

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!

Multiboot.jpg

Tuner A.jpg

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.

Tuner A on its own.jpg

Attempted both full and single tp scans.

Scan Results.jpg

Confirmed by Signal Finder

Signal Finder.jpg

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.