35 replies to this topic

[masterw]

ок

 

Two options:

1)First, check on another image VTI or ATV

or

2)Report an error personally Sundtek http://support.sundtek.com

 

I tested VTI 9.0.x image including latest updates yesterday and same issue occured.

Only difference is that I had to install the drivers with the Windows SundtekSettopboxInstaller. Installing the drivers manually like with OpenPLI didn't work.

Anyway I will go back to OpenPLI 4.0 because personally I don't like the VTI image.

 

I will get in touch with Sundtek for further troubleshooting. As mentioned in one of the previous posts they suspect a wrong buffer setting.

[zeros]

You may try old Vu+ zero drivers. I posted them here (post #32):

 

http://forums.openpl...b-stick/page-2?

 

Perhaps it help?? I would suggest it just in case, because it helped me here with DVB-T/DVB-T2.

[Stefan]

Sorry Erik mijn reactie was wat te heftig hierbij hoop ik het goed te kunnen maken.
Het werk wat jullie (jij) doen word zeker gewaardeerd,ik had iets anders moeten reageren,ikwas misschien iets wat onduidelijk!

[Tech]

Ach, iedereen heeft wel eens een slechte dag en reageert wel eens zoals het niet bedoeld is, dat is het nadeel van geschreven tekst, soms interpreteert men iets anders dan dat het de bedoeling is.
Ook lees je makkelijk over tekst heen en mis je de essentie van een reactie, in dit geval de slechte ondersteuning van usb tuners in het algemeen.

[sundtek]

Normally external Tuners have a good support, however Vu+ / Marusys has done some updates recently which are not mature yet.

We've been told those have been done for WebTV streams.

In order to improve that support we need to be able to reproduce any issue and also tell Vu+ / Marusys what's wrong in detail.

[masterw]

You may try old Vu+ zero drivers. I posted them here (post #32):

 

http://forums.openpl...b-stick/page-2?

 

Perhaps it help?? I would suggest it just in case, because it helped me here with DVB-T/DVB-T2.

 

Many thanks zeros for this suggestion.

I installed the old Vu+ drivers as you suggested and the box is now tuned on the same HD channel for 2h45 an no issue so far.

Image used is still latest VTI 9.0.x

 

Tomorrow I will perform longer tests to confirm if it's 100% fixed.

If OK I will re-flash the box with latest OpenPLI 4.0 image and apply the same old Vu+ drivers.

[masterw]

Normally external Tuners have a good support, however Vu+ / Marusys has done some updates recently which are not mature yet.

We've been told those have been done for WebTV streams.

In order to improve that support we need to be able to reproduce any issue and also tell Vu+ / Marusys what's wrong in detail.

 

OK whenever I have some time I will contact you to reproduce the problem.

Perhaps some logs can be collected showing what's wrong in detail.

Edited by masterw, 16 December 2015 - 23:35.

[Erik Slagter]

I can understand Sundtek won't be spontaneously saying it, but pluggable (internal) tuners are always a better choice than USB tuners.

[sundtek]

It depends on the use case. Who knows where those settopboxes will be in 2020, if you have a look at cutting edge tablet PC SoCs those broadcom chipsets are not competitive. USB will always be there it's a fixed standard.

Our units from 2008 still work fine, and we even extended the use case.

 

We're now integrating the tuners in Android systems, the USB Tuners are way more flexible than internal tuners.

While internal tuners of course have their own advantage (eg. they can be used with CA-Modules of those particular settopboxes (since the hardware path goes through that), and they are much cheaper to manufacture since they are usually 1-2 chip only solutions).

Technically seen from the zapping speed I don't see a reason why internal tuners should be quicker than external ones either  (the only delay that can be caused here is by the interface which allows external tuners).

 

For longer term USB Tuners are definitely a good choice.

Edited by sundtek, 17 December 2015 - 13:02.

[masterw]

I can confirm that the issue is definitely solved using the the old Vu+ drivers as suggested by zeros.

Left the box on an HD channel the whole night and this morning it was still ok.

I will test the old Vu+ drivers on OpenPli 4.0 image this evening.

Edited by masterw, 17 December 2015 - 14:57.

[Stefan]

Toch ben en blijf ik van mening dat interne tuners beter zijn ,ook begrijp ik niet dat als je een box koopt en kabel belangrijk voor je is je voor een Zero kiest.
Gelukkig is het probleem opgelost dat is het belangrijkste.

[Erik Slagter]

Ja diverse partijen, diverse belangen, laten we het daar op houden

[satjunk]

Ik heb de VU+ Turbo
Met PLI constant bij zappen dat radertje en dan BOX handmatig booten..
Onder VTI draait als een zonnetje..ervaar geen verschil met interne tuner..
Dus USB kan afhankelijk zijn van welke image je draait..

[Stefan]

Niks boven een interne tuner,je geeft het zelf al aan onder PLI niet echt stabiel en kan afhankelijk zijn welke image je draait, daar heb je met interne tuners geen last van.
Flashen en gaan met die banaan,zowel PLI als VTI.

Edited by Stefan, 17 December 2015 - 19:59.

[sundtek]

Let's get back to the topic, in order to file a detailed bug report for marusys / vu+ we need logfiles of what is going on on your side with their latest drivers.

masterw, just let us know via skype (since we already have you in the contact list now) when you have some time for this.

Edited by sundtek, 17 December 2015 - 22:34.

[masterw]

I re-installed OpenPli 4.0 yesterday, installed sundtek_installer_151212.134440.sh driver and the old vuzero drivers provided by zeros (vuplus-dvb-modules-vuzero-3.13.5-20150511.tar). After 10-15 minutes the picture starts freezing intensely and finally blocks. At that moment the tuner is not decoding any channel anymore.

 

Then I re-installed the sundtek drivers using the SundtekSettopboxInstaller-Windows-20150719 and until now it's working fine.