PDA

View Full Version : VU+ Duo4k FBC and recording issues.



Toja60
03-03-19, 16:51
Hi.
I have two S2X-FBC in the box, both have two "lnb in" (of cource you know that : ), but I have only one cable attached to each tuner.

I have noticed that when a channel is recorded I can't switch to that channel from another channel without problem, "Tuning failed" and "Timeshift is impossible" is flashing. Especially if I record two or three channels simultaneously.

I tried with only one tuner in the box and used 2 cables into the lonely tuner, but same problem...

I have to admit that I do not have full control over how it works with 2 FBC installed, but I think I have configured them correctly.
I use 2 standard cables straight from the head.

I have debugging activated if someone want to se it.

I have same but only 1 S2X in my Ultimo 4k, and I don't have this problem with that box.

Tuner settings...

58491
58492
58493

Any ideas?

Thanks!

abu baniaz
03-03-19, 17:34
You have not shown the tuner configuration properly. Have a read of the thread on how to setup the tuner again. Probably forgotten the "connected"

goRt
04-03-19, 07:54
Examples here

https://r.tapatalk.com/shareLink?url=https%3A%2F%2Fwww%2Eworld-of-satellite%2Ecom%2Fshowthread%2Ephp%3Ft%3D60640&share_tid=60640&share_fid=12108&share_type=t

Sent from my ONEPLUS A6003 using Tapatalk

abu baniaz
04-03-19, 14:02
Probably forgotten the "connected"

Ignore above, as that would apply if you have a unicable LNB.



I presume you have a universal LNB. You said you only have one signal wire attached to each tuner card, i.e, total of two wires.

You have set Tuner A as 0.8.

You have set Tuner B as 0.8.

You have set Tuner I as 0.8.

You have set Tuner J as 0.8.



You have told the receiver it has 4 wires attached, when it only has two, this is the problem. You have to disable the tuners without the wires attached. This is simplest option.

Trial
04-03-19, 14:46
Hi,
I only have 1 FBC tuner card in my box. Tuner B must be connected to A and C to H FBC automatic I think.

ciao

abu baniaz
04-03-19, 15:05
"Connected" only applies to Unicable.

Trial
04-03-19, 16:05
Hi,
I think it is also valid here to tell the box that all tuner are only for A. B is the second input on the card. The connected you mean is in the unicable configuration I mean connected directly for tuner B.

ciao

abu baniaz
04-03-19, 17:00
If a tuner does not have a wire from universal LNB attached, simplest thing is to leave it disabled. Telling the receiver a tuner has a signal wire attached when it doesn't is wrong.

We can discuss the loop through options later. Better still add a unicable LNB.

Toja60
08-03-19, 17:15
Hello again!

I have now bought and mounted a Unicable LNB for 4 receivers.
Disgusted by me as I thought it would work with all "virtual" fbc tuners ...

If I understand everything correctly, is it that a U-LNB for four receivers can only handle 4 channels?

And if I split to two receivers, I get a maximum of 2 channels / receivers (or 1+3)?

I have ordered another Unicable II LNB with 32 channels now, to test and experiment with.
And it seems that the splitters are the same for U-LNB and U2-LNB.

I will post some additional questions in the future, have seen some shady things with the virtual tuners.

Anyway, thanx for your help for so long.

-M-
13-03-19, 01:07
I tried with only one tuner in the box and used 2 cables into the lonely tuner, but same problem...
I assume you have a universal LNB with two or more outputs. Configure Tuner A as 'single' and Tuner B as 'the same as A' (sorry I'm not sure how it is written in user interface, but it is somehing like what I wrote). This should work, I run like this. Of course since it is two inputs and four possible radio bands, some limits. Can only listen to two quadrants at the same time. So it will be some limits of what to do. It is possible to record many tv-channels (>10), but limited to 8 transponders within two quadrants.


If I understand everything correctly, is it that a U-LNB for four receivers can only handle 4 channels?Yes
It can send out data from max 4 transponders in the cable.

PS. Terminology can cause misunderstandings. In your sentence "channel" will be radio channel, i.e. transponder. Every transponder have multiple 'tv channels', which the more correct word for is service.

All 8 demods in a fbc tuner module can listen to any of the 2 tuners (i.e. connector inputs). So with a unicable LNB, the signal is needed only on one of the two inputs.

Toja60
15-03-19, 15:43
Now I use an Unicable II LNB (24 channels) with one cable connected to Tuner A (Sat 0.8W KU-band), and I have 1 new problem and a question.

Problem:

It takes 5-7 sec. to change channel from a SD-channel to a HD-channel on another transponder, or from HD-channel to HD-channel on another transponder, and every time I gets a fail message "Tuning failed", after the fail message the channel work.
Changing from a HD-channel to a non HD-channel on same or another transponder goes quick without any fail messages, changing channel between HD-channels on same transponder goes quicker.

Question:

These pictures shows my tuner settings, and what you can see is in first picture (Tuner setup) is that
Tuner A "Sats: 0.8W" (correct I think because I use only this sat.)
Tuner B "sats 19.2E, 0.8W"
Tuner C "sats 9.2E, 0.9W"
Tuner D "sats 0.9W, 0.8W"
Tuner E to H "Sats: 0.8W" (correct I think)

I use User band 1 to 8 on Tuner A to Tuner H.
I show only the sat overview and the first 4 tuners:

58565

58566
58567
58568
58569

So, what do you think about this?

-M-
15-03-19, 18:43
I have never configure a unicable LNB. So I cannot help with that, however it looks wrong.

I write to tip about another thing, that can effect the tuning fail problem (long zap time). If you have the lcd4linux plugin installed, disable it (the top most settings if you press ok on the lcd4linux-plugin). However, first is my recommendation to cleanup your tuner/lnb settings.

Trial
15-03-19, 20:26
Hi,
if you only use 0.8W why did you configure the other sat? This is WRONG!

ciao

Toja60
15-03-19, 21:40
Hi,

I may didn't explain in a correct way, but I try again in another way (I'm Swedish and are not an expert of English gramma :) )
I use only 1 sat, 0.8W, and as you can see in the 4 last pictures I use "Connected to Tuner A (or B)" which is only connected/configured to use 0.8W.

You can see in the first (top) picture that the tuners B, C and D which is connected to Tuner A also says that they are using (or what it means) "Sats:19.2E" and "Sats:9.2E, 0.9W".

That's make me confused...

Toja60
15-03-19, 21:40
Please remove this post... double post, can't find "delete" :(

Toja60
16-03-19, 07:54
Due to my problems (post #11 above) I installed latest BH-image just for do a test last evening, no problem with false "Sats:", no fail messages or other problems with changing channels.
And shift channels goes quick.

Due to the false "Sats:" I have noticed that even that I only use 1 sat 0.8W, I can see in settings this:

This is from vix settings:
The Bold and italic is different compared to settings in BH-image.

config.Nims.0.advanced.lnb.1.lof=unicable
config.Nims.0.advanced.lnb.1.powerMeasurement=Fals e
config.Nims.0.advanced.lnb.1.scrList=1
config.Nims.0.advanced.lnb.1.unicableManufacturer= Megasat
config.Nims.0.advanced.lnb.1.unicableProduct=Unica ble II LNB Diavolo
config.Nims.0.advanced.sat.3592.lnb=1
config.Nims.0.advanced.sats=3592
config.Nims.0.configMode=advanced
config.Nims.0.diseqcA=3592
config.Nims.0.diseqcB=3601
config.Nims.0.diseqcC=3601
config.Nims.0.diseqcD=3601
config.Nims.0.powerMeasurement=False
config.Nims.1.advanced.lnb.1.lof=unicable
config.Nims.1.advanced.lnb.1.powerMeasurement=Fals e
config.Nims.1.advanced.lnb.1.scrList=2
config.Nims.1.advanced.lnb.1.unicableManufacturer= Megasat
config.Nims.1.advanced.lnb.1.unicableProduct=Unica ble II LNB Diavolo
config.Nims.1.advanced.sat.192.lnb=1
config.Nims.1.advanced.sat.3592.lnb=1
config.Nims.1.advanced.sats=3592
config.Nims.1.advanced.unicableconnected=True
config.Nims.1.advanced.unicableconnectedTo=0
config.Nims.1.configMode=advanced
config.Nims.1.diseqcA=3592
config.Nims.1.diseqcB=3601
config.Nims.1.diseqcC=3601
config.Nims.1.diseqcD=3601
config.Nims.1.diseqcMode=single
config.Nims.2.advanced.lnb.1.lof=unicable
config.Nims.2.advanced.lnb.1.scrList=3
config.Nims.2.advanced.lnb.1.unicableManufacturer= Megasat
config.Nims.2.advanced.lnb.1.unicableProduct=Unica ble II LNB Diavolo
config.Nims.2.advanced.sat.92.lnb=1
config.Nims.2.advanced.sat.3591.lnb=1
config.Nims.2.advanced.sat.3592.lnb=1
config.Nims.2.advanced.sats=3592
config.Nims.2.advanced.unicableconnected=True
config.Nims.2.advanced.unicableconnectedTo=0
config.Nims.2.configMode=advanced
config.Nims.3.advanced.lnb.1.lof=unicable
config.Nims.3.advanced.lnb.1.scrList=4
config.Nims.3.advanced.lnb.1.unicable=unicable_lnb
config.Nims.3.advanced.lnb.1.unicableManufacturer= Megasat
config.Nims.3.advanced.lnb.1.unicableProduct=Unica ble II LNB Diavolo
config.Nims.3.advanced.sat.3591.lnb=1
config.Nims.3.advanced.sat.3592.lnb=1
config.Nims.3.advanced.sats=3592
config.Nims.3.advanced.unicableconnected=True
config.Nims.3.advanced.unicableconnectedTo=0
config.Nims.3.configMode=advanced


BH settings, there is no "diseq" or false "Sats":

config.Nims.1.configMode=advanced
config.Nims.1.advanced.unicableconnectedTo=0
config.Nims.1.advanced.unicableconnected=true
config.Nims.1.advanced.sat.3592.lnb=1
config.Nims.1.advanced.sats=3592
config.Nims.1.advanced.lnb.1.lof=unicable
config.Nims.1.advanced.lnb.1.unicableLnbManufactur er=Megasat
config.Nims.1.advanced.lnb.1.unicableLnb.Megasat.p roduct=Unicable II LNB Diavolo
config.Nims.1.advanced.lnb.1.unicableLnb.Megasat.v co.Unicable II LNB Diavolo.1=1420
config.Nims.1.advanced.lnb.1.unicableLnb.Megasat.s cr.Unicable II LNB Diavolo=2
config.Nims.0.configMode=advanced
config.Nims.0.advanced.sats=3592
config.Nims.0.advanced.sat.3592.lnb=1
config.Nims.0.advanced.lnb.1.lof=unicable
config.Nims.0.advanced.lnb.1.unicableLnbManufactur er=Megasat
config.Nims.0.advanced.lnb.1.unicableLnb.Megasat.p roduct=Unicable II LNB Diavolo
config.Nims.0.advanced.lnb.1.unicableLnb.Megasat.v co.Unicable II LNB Diavolo.0=1210
config.Nims.3.configMode=advanced
config.Nims.3.advanced.unicableconnectedTo=2
config.Nims.3.advanced.unicableconnected=true
config.Nims.3.advanced.sat.3592.lnb=1
config.Nims.3.advanced.sats=3592
config.Nims.3.advanced.lnb.1.lof=unicable
config.Nims.3.advanced.lnb.1.unicableLnbManufactur er=Megasat
config.Nims.3.advanced.lnb.1.unicableLnb.Megasat.p roduct=Unicable II LNB Diavolo
config.Nims.3.advanced.lnb.1.unicableLnb.Megasat.v co.Unicable II LNB Diavolo.3=2040
config.Nims.3.advanced.lnb.1.unicableLnb.Megasat.s cr.Unicable II LNB Diavolo=4
config.Nims.2.configMode=advanced
config.Nims.2.advanced.unicableconnectedTo=1
config.Nims.2.advanced.unicableconnected=true
config.Nims.2.advanced.sat.3592.lnb=1
config.Nims.2.advanced.sats=3592
config.Nims.2.advanced.lnb.1.lof=unicable
config.Nims.2.advanced.lnb.1.unicableLnbManufactur er=Megasat
config.Nims.2.advanced.lnb.1.unicableLnb.Megasat.p roduct=Unicable II LNB Diavolo
config.Nims.2.advanced.lnb.1.unicableLnb.Megasat.v co.Unicable II LNB Diavolo.2=1680
config.Nims.2.advanced.lnb.1.unicableLnb.Megasat.s cr.Unicable II LNB Diavolo=3

I did a few tries with edit the settings in the backup file, and restore, but cache or another things is
putting in all failed lines again…

These suspicious lines in settings may cause the problem of switching channels as well?

Trial
16-03-19, 09:33
Hi,
did you restore settings when you installed the image? I read a post were restore messed up the sat config. I do not have such problems with my Duo4K and 4 SCR.

ciao

Toja60
16-03-19, 09:39
Thanx Trial,

No, I did only an restore of settings to the installed image.

I will install from scratch now, and see if it works better, there may still some junk from when I used the old standard LNB.

(I installed OpenPLI this morning, and no problems at all.)

Toja60
16-03-19, 10:20
I installed openvix-5.2.032 from scratch, and haven't restored settings, and it works fine now, no fail messages when changing channels, and it change much quicker.

BUT after I did a restore of yesterdays backup, same problem, fail message appear, and shift channels takes longer.

One positive thing is that I haven't any false "Sats" in the tuner overview now after I edited settings in the backup :)

Anyway, it may require new installation of openvix when changing to Unicable LNB...

abu baniaz
16-03-19, 10:49
Your hardware has changed, you have not described how you have setup the wring for your new LNB or confirmed it is the same. People suggesting tuner configuration without a description of your hardware is likely to be incorrect.

Tuner config must match tuner hardware.

Toja60
16-03-19, 11:36
OK, hope I understand what you mean.

From the beginning, I used a standard quad-lnb distributed on 2 boxes, never used diseq or switch, but when there were problems with recordings etc then I first tried a Unicable LNB (four channels), since I wanted to test fbc s2x fully assembled I a Unicable II LNB with 24 channels, I only have 1 cable between Unicable II LNB and the box (tuner A), no switch or diseq mounted.
Now after a clean installation, it works well, no error message when changing channels, there are no false satellites in tuner overview.

I have now tried to record from 8 different channels simultaneously, and that was no problem.

Now is it no false "Sats:"
58574 58575

This is how I configured the tuners, and it works perfect now.

58576 58577 58578 58579

58580 58581 58582 58583

abu baniaz
16-03-19, 11:47
There is a bug with restoring settings that affects tuners at the moment.

You have them like this, which will still work. This used to be a method that was suggested by a Manufacturer owing to a bug in the drivers. These have been fixed, and you are using a different manufacturer. No need to change anything as it is working for you.

B > A
C > B
D > C
E > D
F > E
G > F
H > G

They should have been all connected to A, like below

B > A
C > A
D > A
E > A
F > A
G > A
H > A

Toja60
16-03-19, 12:18
OK, I will do a test with B-H connected to A.

And now the zap-errors occurred again after I installed lcd4linux and enabled it, disabled it (as -M- said in post #12, (sorry for that I missed that post yesterday)) and no zap-errors.