Multituner: First commits - but they need a lot of improvements
Re: Multituner: First commits - but they need a lot of improvements #301
Re: Multituner: First commits - but they need a lot of improvements #302
Posted 13 April 2019 - 23:52
I have been having tuning fatal error message when zapping on ViX but pressing OK twice zaps.
Ive just flashed to PLI 7.0 using openmultiboot plugin but now 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
Using Suntek DVB-S tuner on my VU+ Uno4K box
Edited by dsayers2016, 13 April 2019 - 23:53.
Re: Multituner: First commits - but they need a lot of improvements #303
Posted 14 April 2019 - 01:43
Ok after switching back to Vix then PLI I have managed to get the tuner showing. Automatic scan doesn't work it finds no channels ABM scan finds them but I dont have the zapping issues maybe 2 seconds to zap. How do I enable debug logs in PLI? I looked in sytem but I cant find it.
For ViX I managed to get Automatic scan working by replacing NimManager.pyo and Satconfig.pyo from Vix 5.2.034 and 5.2.030 on 5.2.038 and it only finds 12 channels.
Re: Multituner: First commits - but they need a lot of improvements #304
Posted 14 April 2019 - 12:02
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
OpenATV_Information.jpg 78.29KB
1 downloads
Driver date on install of sundtek tuner
Drivers_Date.jpg 42.56KB
1 downloads
Automatic scan works with no zapping issues
Automatic_scan.jpg 55.29KB
1 downloads
Updated drivers
Drivers_2019.jpg 62.26KB
1 downloads
Automatic scan again no zapping issues
Automatic_scan_2019.jpg 58.15KB
1 downloads
The only difference I noticed is Automatic scan picked up more channels after driver update.
Re: Multituner: First commits - but they need a lot of improvements #305
Posted 14 April 2019 - 12:12
How does the about screen looks? How does the tuner setup look. Does it report as combined or multi tuner? Maybe it reports as combined/hotswitchable tuner which it cannot do? (Then we need an exception for sundtek)
Edited by littlesat, 14 April 2019 - 12:16.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Multituner: First commits - but they need a lot of improvements #306
Posted 14 April 2019 - 12:36
I tried openpli-7.0-release-vuuno4k-20190408_usb
On OpenATV before I updated Sundtek driver I went to tuner config and it gave both as DVB-C and DVB-S/S2, after I updated Sundtek drivers it just shows as DVB-S/S2 but Sundtek did say essential core parts of the driver were updated for multi-tuner support
Ill boot back to PLI and grab a screen shot of the tuner info.
Edited by dsayers2016, 14 April 2019 - 12:38.
Re: Multituner: First commits - but they need a lot of improvements #307
Re: Multituner: First commits - but they need a lot of improvements #308
Posted 14 April 2019 - 12:48
About screen
Information.jpg 83.48KB 1 downloads
Sundtek Plugin
Sundtek_Plugin.jpg 64.08KB 1 downloads
Tuner config
Tuner+Info.jpg 44.24KB 1 downloads
Tuner_Config.jpg 98.69KB 1 downloads
What I have noticed when going into tuner config on other images background picture is normally blank.
Re: Multituner: First commits - but they need a lot of improvements #309
Posted 14 April 2019 - 12:59
No idea? What does dmesg indicate as soon you plugin the usb tuner?
Sundtek usually use not the kernel method for tuners which means somehow with these tuners you have some kind of work-a-round. I do not own such tuner so for my side I cannot troubleshoot.
But it sees the tuner so it should scan... and it should find channels... maybe difference in satellites.xml?
Edited by littlesat, 14 April 2019 - 13:01.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Multituner: First commits - but they need a lot of improvements #310
Posted 14 April 2019 - 13:14
With 7.0 or haven't you added the new satconfig/Nimmanger code to 7.0?
I see it registered as virtual tuner and you configured single lnb on 23.5 east. Is this really a single lnb???
Its configured to 28.2 and only one LNB USB sat tuner my other tuner is an FBC Tuner using DVB-C
What does dmesg indicate as soon you plugin the usb tuner?
Im not sure what you mean by dmesg
Re: Multituner: First commits - but they need a lot of improvements #311
Posted 14 April 2019 - 14:14
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Multituner: First commits - but they need a lot of improvements #312
Posted 14 April 2019 - 14:24
In release 7.0 we still have the older Nimmanager stuff dmesg is what you can do via the console to verify if the drivers etc are correctly connected... but it scans and find channels/services?
So none of your releases have the new code? I thought it thats why I switched to PLI with the new code on ViX I cant find any channels on Automatic scan but ABM scans fine but I get tune failed when zapping channels till I press OK twice to bring up second infobar.
Last night it didn't find any channels when doing Automatic but ive just tried again 12 channels found scan but ABM scan finds all and I dont have the zapping issues on PLI 7.0
Edited by dsayers2016, 14 April 2019 - 14:28.
Re: Multituner: First commits - but they need a lot of improvements #313
Re: Multituner: First commits - but they need a lot of improvements #314
Posted 14 April 2019 - 14:33
So only the scan is an issue?
Im not sure it seems to be different issues for ViX and PLI
So after doing Auto scan this is how my bouquets look
Entertainment.jpg 72.01KB 6 downloads
Re scan ABM and channels are fine.
Re: Multituner: First commits - but they need a lot of improvements #315
Re: Multituner: First commits - but they need a lot of improvements #316
Re: Multituner: First commits - but they need a lot of improvements #317
Posted 14 April 2019 - 16:03
Release images are stable images, they never get intermediate updates, only fixes for serious bugs. We don't release develop images anymore.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Multituner: First commits - but they need a lot of improvements #318
Posted 14 April 2019 - 17:33
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Re: Multituner: First commits - but they need a lot of improvements #319
Posted 14 April 2019 - 17:47
So only the scan is an issue?
Im not sure it seems to be different issues for ViX and PLI
So after doing Auto scan this is how my bouquets look
Re scan ABM and channels are fine.
OpenViX is the new code.
21 user(s) are reading this topic
0 members, 21 guests, 0 anonymous users