104 replies to this topic

[anudanan]

They have problems with the DNS entries for vuplus-support.org. 

 

 

You can reach the forum with vuplus-forum.org

 

When you go to the vti forum with the new link you can find a thread about the problems and solutions for some problems like the vti feed. For connecting to the feed you can temporary edit the /etc/host file. 

[Dimitrij]

coom

Original image same problem?

http://code.vuplus.c...model=vuuno4kse

[Abu Baniaz]

Using a Duo 4K. I will test later on a Gigablue, if required.

 

Managed to change reception equipment. Both devices use identical SCRs.

 

19.2 = LNB (manually edited boot time) 

<product name="IDLU-32UL40-UNBOO-OPP" positions="4" bootuptime="2500" format="jess" scrs="1210,1420,1680,2040,984,1020,1056,1092,1128,1164,1256,1292,1328,1364,1458,1494,1530,1566,1602,1638,1716,1752,1788,1824,1860,1896,1932,1968,2004,2076,2112,2148"/>

 

28.2 = switch

<product name="IDLU-UST110-CUO1O-32P" format="jess" bootuptime="2500" scrs="1210,1420,1680,2040,984,1020,1056,1092,1128,1164,1256,1292,1328,1364,1458,1494,1530,1566,1602,1638,1716,1752,1788,1824,1860,1896,1932,1968,2004,2076,2112,2148"/>

 

 

Can you remind me of the test again please?

 I have so far only set 1 SCR on both Tuners A and B. I have set a recording 5 minute recording on 28.2 and also one on 19.2 at the same time. Both played back fine while they were recording.

Edited by Abu Baniaz, 10 February 2022 - 19:57.

[Dimitrij]

<product name="IDLU-32UL40-UNBOO-OPP" positions="4" bootuptime="2500" format="jess"

 

not  positions="4"

 

<product name="IDLU-UST110-CUO1O-32P" format="jess" bootuptime="2500"

 

set SCR 1210

[Abu Baniaz]

Bother, error about device on previous post, models number slightly different. Both 19.2 and 28.2 are using 1210 frequency. 

 

 

config.audio.volume=70

config.av.videomode.DVI=1080p

config.av.videorate.1080p=auto

config.misc.do_overscanwizard=false

config.misc.enableGeolocation=false

config.misc.firstrun=false

config.misc.initialchannelselection=false

config.misc.languageselected=false

config.misc.rcused=0

config.misc.startCounter=6

config.misc.videowizardenabled=false

config.Nims.0.advanced.lnb.1.lof=unicable

config.Nims.0.advanced.lnb.1.scrList=1

config.Nims.0.advanced.lnb.1.unicable=unicable_matrix

config.Nims.0.advanced.lnb.1.unicableManufacturer=Inverto

config.Nims.0.advanced.lnb.1.unicableProduct=IDLU-UST110-CUO1O-32P

config.Nims.0.advanced.sat.282.lnb=1

config.Nims.0.advanced.sats=282

config.Nims.0.configMode=advanced

config.Nims.1.advanced.lnb.1.lof=unicable

config.Nims.1.advanced.lnb.1.scrList=1

config.Nims.1.advanced.lnb.1.unicable=unicable_lnb

config.Nims.1.advanced.lnb.1.unicableManufacturer=Inverto

config.Nims.1.advanced.lnb.1.unicableProduct=IDLU-32UL40-UNBOO-OPP

config.Nims.1.advanced.sat.192.lnb=1

config.Nims.1.configMode=advanced

config.Nims.8.configMode=nothing

config.Nims.9.configMode=nothing

config.timezone.val=London

config.unicable.unicableManufacturer=Inverto

config.unicable.unicableProduct=IDLU-32UL40-UNBOO-OPP

config.usage.setup_level=expert

 

[Dimitrij]

<product name="IDLU-UST110-CUO1O-32P" format="jess" bootuptime="2500" scrs="1210,1420,1680,2040,984,1020,1056,1092,1128,1164,1256,1292,1328,1364,1458,1494,1530,1566,1602,1638,1716,1752,1788,1824,1860,1896,1932,1968,2004,2076,2112,2148"/>

 

 

<product name="IDLU-32UL40-UNBOO-OPP" positions="4" bootuptime="800" format="jess" scrs="1210,1420,1680,2040,984,1020,1056,1092,1128,1164,1256,1292,1328,1364,1458,1494,1530,1566,1602,1638,1716,1752,1788,1824,1860,1896,1932,1968,2004,2076,2112,2148"/>

[Abu Baniaz]

Can you please rephrase what you are trying to convey.

[Dimitrij]

Can you please rephrase what you are trying to convey.

First, thanks for the tests.

Second, one of the LNB uses positions="4",and that's a big difference.

Can you remove positions="4" from unicable.xml and check?

[coom]

coom

Original image same problem?

http://code.vuplus.c...model=vuuno4kse

 

sorry, can't tell, haven't tested it. not sure i find the time (honestly I am quite happy with what we have achieved ;-) )

[Abu Baniaz]

 

Can you please rephrase what you are trying to convey.

First, thanks for the tests.

Second, one of the LNB uses positions="4",and that's a big difference.

Can you remove positions="4" from unicable.xml and check?

 

 

I have removed the position entries. Still working fine. I installed history zap selector and can zap between 28.2 and 19.2 without an issue

 

I should add, the Unicable LNB is powered by the STB. The unicable switch has a power inserter connected to it. Not enough space to add two LNBs for 19.2 and 28.2 on teh same dish as the invertos are wide. I will have to add another dish to test two LNBs. Hopefully sometime next week.

[Dimitrij]

I think it's time to close the topic.

A workaround has been found, but no one will fix the driver.

I think the VU+ office is no longer working, the era of satellite giants is over.

 

Thanks everyone.

[WanWizard]

I see the OP complain that you can't have two tuners connected to different LNB's using the same SCR band, and I see Abu Baniaz respond it works fine for him.

 

I don't see any technical difference between a Unicable LNB and a Unicable switch, that is transparent for the tuner, it just tunes into the frequency defined.

 

So what exactly is the problem, and what is the workaround?

 

If something has to be passed on the VU+, we need exact information.

 

p.s. I think VU+ is struggling finding a way forward at the moment, since it's a "Broadcom shop", and Broadcom doesn't supply SoC's for the OEM market anymore.

[Abu Baniaz]

The problem for the OP i using two identical Unicable LNBs pointing at two different satellites, and the identical SCR and LNB number being used results in the recording issues. The workaround is to use different LNB numbers.

 

You (Wanwizard) and I have both tested without a problem. We are however using a different receiver and you used switches whereas I used a switch and an LNB. I also only configured one tuner for each satellite. So, it is not an exact controlled test.

[anudanan]

@Anbu Baniaz:

 

I think you can make a test which is similar to the issue from @coom. Because your switch and LNB use the same SCR/frequencies you can configure all tuners with the LNB and not with the switch. Maybe you can reproduce the issue.

[Abu Baniaz]

I tested (I think I did it properly) and cannot reproduce the issue.

 

There is no need to test one device used on all 8 demodulators. The forums would be awash with reports if there was an issue.

[anudanan]

So you have used the LNB and not the switch type for tuner A and for tuner B?

 

I´ve seen only your config in post #85 with the switch model for tuner A and LNB modell for tuner B. Are you sure you´ve tested tuner A und B with the same LNB modell?

Edited by anudanan, 12 February 2022 - 19:58.

[WanWizard]

You (Wanwizard) and I have both tested without a problem. We are however using a different receiver and you used switches whereas I used a switch and an LNB. I also only configured one tuner for each satellite. So, it is not an exact controlled test.

 

I didn't have two Unicable systems available with the same userband freqencies, so my test turned out to be not relevant.

 

So you have used the LNB and not the switch type for tuner A and for tuner B?

 

Whether it is an LNB or a Switch is completely transparent for both Enigma and the tuner, it is only information for the user, its sole purpose is determining the number of positions, the number of user bands, and the user band frequencies.

 

So I don't see why an LNB and a switch would be different from two LNB's.

[anudanan]

Yes, that is also my feeling, but why does it work on the VU of @coom

Edited by anudanan, 12 February 2022 - 20:23.

[WanWizard]

I don't know.

 

The other variable in the equation is LNB number, which is info passed on in the JESS command (which a switch uses to select the correct LNB in a multi-LNB setup, and is otherwise ignored I think).

 

But that was tested by @Abu Baniaz in post #85.

 

It might still be specific to the Uno 4K SE.

[Abu Baniaz]

So you have used the LNB and not the switch type for tuner A and for tuner B?

 

I´ve seen only your config in post #85 with the switch model for tuner A and LNB modell for tuner B. Are you sure you´ve tested tuner A und B with the same LNB modell?

No, I have not. I used a switch for one tuner and an LNB for another. That is the dish in my garden, you cannot fit two inverto LNBs next to each other as they are wide.

 

The dish on my neighbours roof has a Unicable LNB, but the bands don't match. So it is not testing the problem.

 

The system only saves one of these even if you have more than one device.

config.unicable.unicableManufacturer=

config.unicable.unicableProduct=

Edited by Abu Baniaz, 12 February 2022 - 20:55.