View Full Version : Tune failed when zapping Sundtek DVB-S/S2 vix 5.2.036
I did a software update from vix 5.2.035 to 5.2.036 yesterday and noticed some strange zapping issues, if I zap from 103 to 104 I get tuned failed message until I press ok twice.
I haven't had chance to run a debug log yet but there is something wrong. I went to bed this morning after work and got up this afternoon the box was on tune failed as the family use the box as soon as I pressed ok twice so second infobar shows it played the channel.
I'm just trying to work out if it's just me or a general bug but I won't be able to run debug logs till tomorrow.
abu baniaz
09-04-19, 19:44
Double check your tuner configuration is still correct.
Double check your tuner configuration is still correct.
Yes tuner config is correct, that's the first thing that I checked. I can zap no problem once I press ok twice to bring up the second infobar. I'll try and get debug logs tomorrow.
Edit just to add zapping to my fbc dvb-c tuners are fine.
Attached is a debug log. Box booted on 103 ITV 1 HD with tune failed I pressed ok twice and the channel played then I used CH+ to zap to 104 Channel 4 HD again tuned failed message till I pressed OK twice to brig up second infobar.
Same problem with Sundtek DVB/T2 usb-tuner after upgrading to OpenViX 5.2.037 (2019-04-09) .VU+ Solo2
ALso when trying automatic scan the system does not find any channels.
There's a new Sundtek driver release, dated 2/4/2019, the first since last year. Which driver are you using??
I have the 2019-04-02 version.
I had no problems with the previous 5.2.034 version.
The Sundtek Control Centre allows you to set driver updates to install automatically. Do you use this setting? I always do updates manually.
I can't make it go wrong. Configured with just a single Sundtek DVB-T2 tuner.
I tried on 5.2.035 with the old and new Sundtek drivers, and then flashed 5.2.037, again it worked ok with the old and new drivers.
One thing I did notice, the settings restore remembered it was a DVB-T2 tuner, it's always in the past reverted to a DVB-C.
Haven't there been some commits recently in this area, to automatically switch between C and T2??
I flashed back to 5.2.034 and noticed that even with this image there is the same problem but it doesn't happen so often.
When shifting from channel to another it just sometimes gives the error tune failed and just pressing ok again it works.
But when trying to scan the channels it still doesn't find any. I'm not sure which vesion I had when I last time searched the channels.
Does it work ok if you disable all your other tuners?
Watch out for timer conflicts if you do try it!!
I tried with the internal tuners disabled but no change.
Is it possible to get the older Sundtek drivers somewhere and test with them?
They can be found here. Can't advice how best to install them, I'm afraid.
http://sundtek.de/media/
Does uninstalling sundtek plugin remove current drivers? I guess we can download the sh file and put it in usr/script then install with script runner. I'm just not sure on removing current drivers.
If you can find out the name of the driver(s), then removing them is the easiest way.
The name will be in the script somewhere, I've had a look but nothing obvious.
Maybe removing the control centre gets rid of the drivers as well, reboot, reinstall and see if it thinks you have any drivers already installed.
A fresh flash with no settings/plugins restore would do it, but more work to get going, and then there's still the shell script to run.
abu baniaz
12-04-19, 02:50
There's a new Sundtek driver release, dated 2/4/2019, the first since last year. Which driver are you using??
Where are you guys getting the updated drivers from? I have been trying to get in touch with Sundtek since January.
English driver board is 404
https://support.sundtek.com/index.php/board,9.0.html
Username on forum is still waiting approval
No response on ticket
No response to Skype
Where are you guys getting the updated drivers from? I have been trying to get in touch with Sundtek since January.
English driver board is 404
https://support.sundtek.com/index.php/board,9.0.html
Username on forum is still waiting approval
No response on ticket
No response to Skype
The drivers are just downloaded from the sundtek plugin. Post 16 has a link to driver installs. I think this is latest http://www.sundtek.de/media/sundtek_installer_190402.110615.sh
Ok, now it works. I downloaded the latest and the previous versions.
I uninstalled the latest version: ./sundtek_installer_190402.110615.sh -u
reboot
installed previous version:
./sundtek_installer_181220.135032.sh
reboot
Scanning the tuner finds all channels and zapping from channel to another works everytime.
Ok, now it works. I downloaded the latest and the previous versions.
I uninstalled the latest version: ./sundtek_installer_190402.110615.sh -u
reboot
installed previous version:
./sundtek_installer_181220.135032.sh
reboot
Scanning the tuner finds all channels and zapping from channel to another works everytime.
How did you issue ./sundtek_installer_190402.110615.sh -u? I tried and received
login as: root@vuuno4k:~# ./sundtek_installer_190402.110615.sh -u
-sh: ./sundtek_installer_190402.110615.sh: No such file or directory
root@vuuno4k:~#
Did you download both sh files to root then issue the commands?
abu baniaz
12-04-19, 12:31
If anyone gets in touch with Sundtek, the installer script needs updating. It only detects Arm receivers by Vu+ and treats rest as mipsel.
It'll depend where the .sh file has been downloaded to. You need to cd into that directory before issuing the command.
Maybe /tmp is the place to start???
If anyone gets in touch with Sundtek, the installer script needs updating. It only detects Arm receivers by Vu+ and treats rest as mipsel.
Support chat is here
https://support.sundtek.de/chat.php But I haven't had much luck getting in touch.
I downloaded the scripts to /tmp and then cd /tmp and issued the commands there.
And of course if the scripts are not executable you have to do: chmod +x sund* before executing them.
abu baniaz
12-04-19, 12:47
Can someone check Sundtek Satellite tuners with OpenATV? Maybe the switchable tuner code in PLiVix needs some tweaking.
Sundtek replied to chat and said they'll take a look at this thread when they have time to investigate
I downloaded the scripts to /tmp and then cd /tmp and issued the commands there.
Installing older drivers didn't work for me. I'll wait for sundtek to reply
Can someone check Sundtek Satellite tuners with OpenATV? Maybe the switchable tuner code in PLiVix needs some tweaking.
I'll try openatv tonight.
Can someone check Sundtek Satellite tuners with OpenATV? Maybe the switchable tuner code in PLiVix needs some tweaking.
Ok swapped to an old openatv 6.3 image using openmultiboot no problems zapping then updated drivers using sundtek plugin and zapping fine. I then did a software update and zaps fine again.
ABM scans fine aswel. Although I don't have issues with scanning.
I'm happy to test any files
Someone of you guys please join the chat on Sunday or Monday again, I will have some time for checking the software then.
There are just too many things going on on our side at the moment with several new products...
Unless someone can join the support chat within the next 15 minutes (then I can have a look right now) (18:30-19:00 (forum time))
https://support.sundtek.de/chat.php
ok no one in the chat. so I'll be back on Sunday.
As what I read here it's good that there's no driver bug (essential core parts of the driver were updated for multi-tuner support), just the installer needs to be updated for the Settopbox Detection.
Aside of that, we have rewritten large portions of the Installer already since architecture and settopbox checks just polluted the installer scripts too much after many years. It's not officially updated yet.
abu baniaz
13-04-19, 15:36
I am not experiencing issues with the tuner in Terrestrial mode on a solo 4K. I don't have a satellite Sundtek tuner.
ABM scans fine aswel. Although I don't have issues with scanning.
I'm happy to test any files
Edit Automatic scan on the tuner doesn't find any channels.
Log attached
What settings do I use for Config mode Advanced? I just want to test if changing from simple to Advanced makes any difference.
58743
abu baniaz
13-04-19, 18:44
Your tuner is not configured, because the LNB is not assigned.
Simple, single, 28.2
Your tuner is not configured, because the LNB is not assigned.
Simple, single, 28.2
I already have it to simple, single, 28.2 I was just seeing if other modes give the same results Ill leave it at simple.
A bit of testing I tried NimManager.pyo and Satconfig.pyo from Vix 5.2.034 and 5.2.030 on 5.2.038 and automatic scan works but I still get tune failed when zapping. Maybe both tuner python changes and sundtek drivers are causing issues.
abu baniaz
13-04-19, 21:53
I am pretty sure only the installer has changed to say they are 10years old, but drivers are still the same. Hopefully the remote assistance will identify the issue.
abu baniaz
13-04-19, 21:59
Just for reference purposes, the installer script has been adapted for other 4k receivers. Needs a bit more testing.
I have posted in the PLI thread asking people to test with Sundtek satellite tuners. We know that there is no issue with openatv
I am pretty sure only the installer has changed to say they are 10years old, but drivers are still the same. Hopefully the remote assistance will identify the issue.
I've just compared the last 2 and they appear to be very different.
abu baniaz
13-04-19, 22:02
I stand corrected then.
Ok im getting confused now I said Automatic scan works with NimManager.pyo and Satconfig.pyo from Vix 5.2.034 and 5.2.030 on 5.2.038 I didnt let it complete scan and it only finds 12 channels.
Now it shows a load of the ABM channels NA but for the channels that are there Zap with no issues, rescan ABM all channels scan but I get the tune failed when zapping until I press OK twice.
I think im going to leave it at that as im causing myself an headache lol till I speak with Sundtek hopefully they can work out what is happening.
I have posted in the PLI thread asking people to test with Sundtek satellite tuners. We know that there is no issue with openatv
Does openmultiboot plugin work with PLI? I can Boot to PLI to test if tuner works.
Does openmultiboot plugin work with PLI? I can Boot to PLI to test if tuner works.
Ok flashed PLI using multiboot Sundtek plugin showed no stick found so I went to update drivers and it showed current drivers date N/A so I updated drivers and rebooted box, once rebooted the plugin still shows no stick found but driver date 2019-04-02
I am not experiencing issues with the tuner in Terrestrial mode on a solo 4K. I don't have a satellite Sundtek tuner.
Have you tried with default images with no restore?
Installed PLI to multiboot no driver installed stick not detected so I updated drivers and rebooted still no stick detected.
Installed fresh ATV 6.2 after installing sundtek plugin and going into it it said drivers not installed do you want to install I chose yes then rebooted box no stick detected.
Boot back to vix (Flash) and stick is fine but tune fatal message till pressing OK twice.
I deleted the older ATV openmultiboot images so I cant test them so im not sure whats happening.
abu baniaz
14-04-19, 06:19
How do you check what drivers are in use for the Sundtek?
How do you check what drivers are in use for the Sundtek?Run the control centre, press menu, and the first option is to install drivers. Select, and it will tell you which driver you're currently using.
Ok I have managed to get sundtek running on an openatv-6.3-vuuno4k-20190308_usb.zip Image as I wanted to test older and new drivers. For testing I haven't ran ABM
58753
Driver date on install of sundtek tuner
58754
Automatic scan works with no zapping issues
58755
Updated drivers
58756
Automatic scan again no zapping issues
58757
Edit the only difference I noticed is Automatic scan picked up more channels after driver update.
Both of our installers will pick the latest drivers from http://sundtek.de/media
The task of the installer script is to identify the architecture and if the system is a settopbox.
The new installer script is just more orderly than the old one, and also easier to extend and/or debug, however it's not as well tested as the old one which got extended quite a lot over the years.
I have a similar issue, but I'm not sure which OpenVIX version caused the problem. One of the updates in the last few weeks warned that I would lose my settings for the Sundtek tuner after upgrading and the problem started after that. Before rescan, getting Tuner Failed error until pressing OK twice on remote. Tried rescan, and no channels found. At which point I attached my Turbo DVB-C tuner and scanned - which worked. But I still have the intermittent problem of the Tuner Failed error on the Sundtek tuner until pressing OK twice. Recording timers will also intermittently fail to start on the Sundtek tuner producing a 0 size recording.
I'm using the DVB-C Sundtek tuner by the way, and current version of VIX is 5.2.037 and Sundtek control centre has a date of 20180605-2.
I'm not sure where the issues are.
Openvix 5.2.037 and 038:
Tune failed when zapping
Automatic scan finds no channels abm scans fine.
Automatic scan works with NimManager.pyo and Satconfig.pyo from Vix 5.2.034 and 5.2.030 on 5.2.038 Automatic scan only finds 12 channels.
Now it shows a load of the ABM channels NA but for the channels that are there Zap with no issues, rescan ABM all channels scan but I get the tune failed when zapping until I press OK twice.
Openpli 7.0:
Automatic scan only finds 12 channels but ABM scan finds all and no zapping issues.
Openatv 6.3:
Both Automatic scan and abm scans with no zapping issues.
Maybe a mismatch of driver issues and multi tuner updates
There's a new Sundtek driver released today.
abu baniaz
17-04-19, 16:27
There's a new Sundtek driver released today.
Link to drivers please. Not installer.
Link to drivers please. Not installer.
http://www.sundtek.de/media/sundtek_installer_190417.094831.sh
http://sundtek.de/media/
abu baniaz
17-04-19, 16:49
That is installer. Not the same thing as drivers.
There's a new Sundtek driver released today.
Thanks but still the same tune failed and only 12 channels found with the older tuner files. I'm on holiday Friday so I don't think I'll have time to look into it more.
That is installer. Not the same thing as drivers.
From Sundtek…..
Both of our installers will pick the latest drivers from http://sundtek.de/media
abu baniaz
17-04-19, 16:59
You stated "There's a new Sundtek driver released today"
There are no new drivers on that website/I can't find them/I'm looking in wrong place. The plugin on my solo 4k does not find them. I can find the newer installer script, which was adapted a few days ago to deal with 4K receivers made by non-Vu manufacturers and presumably tidied up/improved.
Am I doing something wrong? Or by "drivers", you meant "installer"
Run the control centre, press menu, and the first option is to install drivers. Select, and it will tell you which driver you're currently using.
I can see that the latest "sundtek driver version" is 2019-04-17 09:48:31", I can't do any more than that.
abu baniaz
17-04-19, 20:48
As per Sundtek, update is:
drivers & script but unrelated to settopboxes
I just found out with my Uno 4K SE and Duo2 that combination ViX latest images and Sundtek T2 tuners are useless. Timer recording when box is in standby-mode gives result 0 MB (recording starts as soon as you turn box on) and manual servicescan does not function.
I can see that the latest "sundtek driver version" is 2019-04-17 09:48:31", I can't do any more than that.
Updated again this evening, showing 2019-04-18 17:00:44 via the Sundtek Control Centre.
There was a driver update today, it should fix the problems.
Updates were needed for upcoming multituners unfortunately. Simulating the depreciated FE_GET_EVENT event (threadless) without interfering with other driver parts was a bit challenging.
abu baniaz
19-04-19, 00:45
Scanning on TM Nano se M2 now working fine.
There was a driver update today, it should fix the problems.
Updates were needed for upcoming multituners unfortunately. Simulating the depreciated FE_GET_EVENT event (threadless) without interfering with other driver parts was a bit challenging.
This update has fixed my 'Tuner Failed!' error, good work. :)
There was a driver update today, it should fix the problems.
Updates were needed for upcoming multituners unfortunately. Simulating the depreciated FE_GET_EVENT event (threadless) without interfering with other driver parts was a bit challenging.
For the fututure Markus, please make sure your existing customers see their Sundteks are working.
I've only just got round to trying the latest update and all seems fine. Thanks
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.