Unable to watch/record more than two channels again

[mitchelln]

Hi.

I updated the software on my Duo4k SE and I'm now once again getting the problem where I can only watch/record two channels at a time. Before I could record at least 8 channels simultaneously if required.
This is a recurring problem that keeps happening after software updates. Unfortunately I cannot find the thread when this problem happened last time to look to see how it was fixed.

I have 10 tuners. A-H are DVB-S NIM(45308X FBC) and I and J are DVT-T NIM(BCM3466). I upgraded to 6.5.003 from 6.4.008 and the problem started again.

Any ideas please? Thanks.

The settings file contains:
config.audio.volume=95
config.autobouquets.area=4099#67#4103
config.autobouquets.ordering=True
config.autobouquetsmaker.addprefix=True
config.autobouquetsmaker.FTA_only=terrestrial_uk_f reeview|sat_282_sky_uk
config.autobouquetsmaker.hidesections=terrestrial_ uk_freeview:670|sat_282_sky_uk:490|sat_282_sky_uk: 560|sat_282_sky_uk:701|sat_282_sky_uk:900|sat_282_ sky_uk:993|sat_282_sky_uk:1000|sat_282_sky_uk:1020 |sat_282_sky_uk:1030|sat_282_sky_uk:580
config.autobouquetsmaker.nextscheduletime=16296768 00
config.autobouquetsmaker.providers=terrestrial_uk_ freeview:rowridge___________:45:|sat_282_sky_uk:hd _west_dorset:76:
config.av.autores_delay=500
config.av.autovolume=hdmi
config.av.btaudiodelay=0
config.av.downmix_aac=passthrough
config.av.downmix_ac3=passthrough
config.av.generalAC3delay=0
config.av.generalPCMdelay=0
config.av.hdmicolordepth=12bit
config.av.surround_3d=hdmi
config.av.videomode.HDMI=1080p
config.av.videorate.1080p=60Hz
config.av.videorate.2160p=60Hz
config.backupmanager.backupdirs=['/etc/enigma2/', '/etc/fstab', '/etc/hostname', '/etc/network/interfaces', '/etc/passwd', '/etc/shadow', '/etc/etc/shadow', '/etc/resolv.conf', '/etc/ushare.conf', '/etc/inadyn.conf', '/etc/tuxbox/config/', '/etc/wpa_supplicant.conf', '/usr/softcams/', '/etc/auto.network', '/usr/crossepg/crossepg.config', '/usr/crossepg/providers', '/usr/keys', '/etc/samba/smb-user.conf', '/etc/samba/private']
config.crash.daysloglimit=8
config.crash.debugloglimit=4
config.crash.enabledebug=True
config.crash.logtimeformat=1
config.crash.sizeloglimit=10
config.epg.freesat=True
config.epg.histminutes=30
config.epg.netmed=False
config.epg.viasat=False
config.epgselection.grid.btn_blue=openEPGSearch
config.epgselection.grid.btn_channeldown=nextPage
config.epgselection.grid.btn_channelup=prevPage
config.epgselection.grid.btn_reclong=addEditAutoTi mer
config.epgselection.grid.btn_red=forward24Hours
config.epgselection.grid.btn_yellow=addEditAutoTim er
config.epgselection.grid.eventfs=0
config.epgselection.grid.infowidth=50
config.epgselection.grid.number_buttons_mode=servi ce
config.epgselection.grid.piconwidth=100
config.epgselection.grid.primetime=19:0
config.epgselection.grid.servfs=0
config.epgselection.grid.servicetitle_mode=picon+s ervicenumber+servicename
config.epgselection.grid.servicewidth=250
config.epgselection.grid.timelinefs=0
config.epgselection.multi.btn_blue=openEPGSearch
config.epgselection.multi.btn_yellow=addEditAutoTi mer
config.epgselection.multi.eventfs=0
config.epgselection.multi.servicewidth=7
config.hdmicec.control_receiver_standby=True
config.hdmicec.debug=1
config.hdmicec.enabled=True
config.hdmicec.force_volume_forwarding=True
config.hdmicec.minimum_send_interval=10
config.hdmicec.tv_wakeup_detection=wakeup
config.hdmicec.volume_forwarding=True
config.keyboard.keymap=eng.kmap
config.lcd.bright=3
config.lcd.dimbright=0
config.misc.ButtonSetup.displayHelp=Infobar/openEventView
config.misc.ButtonSetup.power_long=Module/Screens.Standby/TryQuitMainloop/1
config.misc.ButtonSetup.text=Infobar/showPiP,Infobar/openEventView
config.misc.epgcachepath=/media/hdd/
config.misc.firstrun=False
config.misc.initialchannelselection=False
config.misc.languageselected=False
config.misc.pluginbrowser.plugin_order=Plugins/Extensions/AutoBouquets,Plugins/SystemPlugins/CrossEPG,Plugins/Extensions/EPGImport,Plugins/Extensions/IMDb,Plugins/Extensions/MediaScanner,Plugins/Extensions/MovieOrganisor,Plugins/Extensions/OpenWebif,Plugins/Extensions/PicturePlayer,Plugins/SystemPlugins/TransCodingSetup,Plugins/Extensions/WitAiSpeechToText
config.misc.pluginlist.extension_order=Turn on HDMI-IN PiP mode,AutoBouquets Downloader,CrossEPG Downloader,EPG-Importer,Turn on HDMI-IN full screen mode,Softcam manager,ViX Image Management,Activate Picture in Picture
config.misc.pluginWakeupName=EPG-Importer
config.misc.restorewizardrun=True
config.misc.startCounter=121
config.misc.videowizardenabled=False
config.misc.zapkey_delay=5
config.movielist.enable_collections=1
config.movielist.fontsize=0
config.Nims.0.advanced.lnb.1.diseqcMode=1_0
config.Nims.0.advanced.sat.192.lnb=1
config.Nims.0.diseqcA=282
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.2.diseqcMode=1_0
config.Nims.1.advanced.sat.192.lnb=2
config.Nims.1.diseqcA=282
config.Nims.1.diseqcB=3601
config.Nims.1.diseqcC=3601
config.Nims.1.diseqcD=3601
config.Nims.1.powerMeasurement=False
config.Nims.2.advanced.lnb.1.lof=unicable
config.Nims.2.advanced.lnb.1.scrfrequency=1210
config.Nims.2.advanced.lnb.1.scrList=1
config.Nims.2.advanced.lnb.1.unicableManufacturer= Dura-Sat(DUR-line)
config.Nims.2.advanced.lnb.1.unicableProduct=UK101
config.Nims.2.advanced.sat.192.lnb=1
config.Nims.2.advanced.sat.282.lnb=1
config.Nims.2.advanced.sats=282
config.Nims.3.advanced.sats=192
config.Nims.8.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.9.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.OpenWebif.responsive_enabled=True
config.osd.language=en_GB
config.pic.lastDir=/media/hdd/
config.pluginbrowser.src=True
config.plugins.autotimer.show_help=False
config.plugins.bluetoothsetup.enable=True
config.plugins.bluetoothsetup.lastAudioConn=cc:98: 8b:93:a6:37
config.plugins.epgimport.deepstandby=wakeup
config.plugins.epgimport.enabled=True
config.plugins.epgimport.longDescDays=5
root@vuduo4kse:/etc/enigma2#
root@vuduo4kse:/etc/enigma2#
root@vuduo4kse:/etc/enigma2#
root@vuduo4kse:/etc/enigma2#
root@vuduo4kse:/etc/enigma2#
root@vuduo4kse:/etc/enigma2#
root@vuduo4kse:/etc/enigma2#
root@vuduo4kse:/etc/enigma2# more settings
config.audio.volume=95
config.autobouquets.area=4099#67#4103
config.autobouquets.ordering=True
config.autobouquetsmaker.addprefix=True
config.autobouquetsmaker.FTA_only=terrestrial_uk_f reeview|sat_282_sky_uk
config.autobouquetsmaker.hidesections=terrestrial_ uk_freeview:670|sat_282_sky_uk:490|sat_282_sky_uk: 560|sat_282_sky_uk:701|sat_282_sky_uk:900|sat_282_ sky_uk:993|sat_282_sky_uk:1000|sat_282_sky_uk:1020 |sat_282_sky_uk:1030|sat_282_sky_uk:580
config.autobouquetsmaker.nextscheduletime=16296768 00
config.autobouquetsmaker.providers=terrestrial_uk_ freeview:rowridge___________:45:|sat_282_sky_uk:hd _west_dorset:76:
config.av.autores_delay=500
config.av.autovolume=hdmi
config.av.btaudiodelay=0
config.av.downmix_aac=passthrough
config.av.downmix_ac3=passthrough
config.av.generalAC3delay=0
config.av.generalPCMdelay=0
config.av.hdmicolordepth=12bit
config.av.surround_3d=hdmi
config.av.videomode.HDMI=1080p
config.av.videorate.1080p=60Hz
config.av.videorate.2160p=60Hz
config.backupmanager.backupdirs=['/etc/enigma2/', '/etc/fstab', '/etc/hostname', '/etc/network/interfaces', '/etc/passwd', '/etc/shadow', '/etc/etc/shadow', '/etc/resolv.conf', '/etc/ushare.conf', '/etc/inadyn.conf', '/etc/tuxbox/config/', '/etc/wpa_supplicant.conf', '/usr/softcams/', '/etc/auto.network', '/usr/crossepg/crossepg.config', '/usr/crossepg/providers', '/usr/keys', '/etc/samba/smb-user.conf', '/etc/samba/private']
config.crash.daysloglimit=8
config.crash.debugloglimit=4
config.crash.enabledebug=True

[twol]

I am not of your setup, but you seem to have both 19.2 & 28.2E setup on your fbc tuners

[mitchelln]

Thanks for the reply. I don't know how that's got in there. So do I simply remove the 19.2 entries?

[bmitie]

Why did you upgrade when all was working fine?? And did you do a clean install?

[mitchelln]

Why should I not upgrade from 6.4 to 6.5? Why would I do a clean install for a simple software update? None of my other devices require such a drastic step. This is being sold as a consumer device and should behave as such.

I suspect the upgrade was not actually the cause. I bet something else broke the tuner config somehow over the last months of use and the reboot after the upgrade picked the change.

[mitchelln]

Thanks for the reply. I don't know how that's got in there. So do I simply remove the 19.2 entries?


I am not of your setup, but you seem to have both 19.2 & 28.2E setup on your fbc tuners
I removed the 19.2 entries in the settings file and rebooted, but it just inserted them again. Do you know where it might be picking up this dud setting from please?
There's no mention of 19.2 in my tuner setup screen, so I'm mystified where it's getting it from.

[bmitie]

I have the duo4kse as well but reading your problems it all sounds very complicated. What you have is corrupted software and the only way to resolve it would be a clean install. Are you aware the box has a multiboot function? Also the box may be faulty from the outset. When a new image is released avoid it like the plague until it has been thoroughly tested and above all if you have a box that’s working perfect never update. I am still on 6.3. remember if it ain’t broke don’t fix it.

I have a uno4kse with fbc
for 28 e will do you of pic with tuners tomorrow.

[Willo3092]

MENU > SETUP > TUNERS AND SCANNING > TUNER SETUP

Go into the tuner that has 19.2 set up on it and change the LNB to 'not configured' and press green to save.
Do this for all tuners that have 19.2 showing.
It should ask if you want to remove 19.2 configs.

66356 66357

[mitchelln]

Thanks for the info. I cleared the tuners as described and then set them up again. The GUI then started crashing. Looking at the log file it's because it couldn't find channels.
So I ran a full automatic re-scan which mainly sorted that. It still kept crashing and restarting in some of my custom bouquets. After another half hour of swearing, I managed to patch them up in the Web bouquet editor after running a bouquet update.
The good news is it's now back to being able to record multiple channels and I've taken a full image backup of the working state.

I think this is down to the tuner setup screen appending dud default entries possibly. I'm wondering if just going into the screen is enough to cause incorrect values to be written or there's a bug with the config restore that causes issues.

I do wait until at least the .003 version of a major release before upgrading to ensure any major bugs have been picked up. I now have taken a copy of a working settings file and put it in my ssh /home folder so I can always put back if this happens again.

Thanks for the help with this.

[Willo3092]

It's a good idea to save a copy of all the config.nims settings from /etc/enigma2/settings, on your pc.
Saves a lot of messing about if wanting to setup from scratch.

[mitchelln]

It's a good idea to save a copy of all the config.nims settings from /etc/enigma2/settings, on your pc.
Saves a lot of messing about if wanting to setup from scratch.

Yes, I have done this via ssh. Although it was just putting back the dud 19.2 lines after a reboot until I cleared it all down and did the steps above.

[twol]

Yes, I have done this via ssh. Although it was just putting back the dud 19.2 lines after a reboot until I cleared it all down and did the steps above.

make sure that when you replace a settings file, you run a telnet session, and init 4 the receiver (stop it), copy the settings file and then init 6 (reboot)

[abu baniaz]

The excerpt you posted had missing tuner numbers. This indicates that they were not configured. Upgrading involved flashing new image and restoring settings/plugins. So it is possible an old faulty configuration was chosen to be restored. If you want your configuration to be double checked, please transfer the current file called "settings" in /etc/enigma2 from receiver to your PC, zip it and upload it here. Please upload the file instead of pasting the contents.

In addition to the post above about replacing files on the receiver, I would add: stop enigma2 before any manual editing. Once edited and file transfer completes, restart.

[bmitie]

Its surprising we never got a pic of the tuners but to help OP this is what it should look like.

2 more sat ones over the page plus the 2 for DTT = 10.

[mitchelln]

Its surprising we never got a pic of the tuners but to help OP this is what it should look like.

2 more sat ones over the page plus the 2 for DTT = 10.

Yes, that's exactly what mine looks like and has always looked like. Not sure where the 19.2 lines in the settings file were coming from.

[mitchelln]

I've attached my settings file. I notice that the 19.2 lines are still there even after completely deleting the tuner config using the steps above. I have never selected the 19.2 satellite, only the 28.2E Astra one in the tuner set up. Perhaps a bug in the tuner setup screen adding some kind of default? Suspect 19.2 is the first in the available list and is being added erroneously?
This doesn't seem to be the cause of my original issue though, as I can now again record multiple channels.

[abu baniaz]

Thanks. It seems 23.5E has been added to your receiver too :( I was just reading your previous thread, can you please post/upload pictures/details of your LNB again. Your previous thread says you had a universal LNB. In this thread you have a unicable LNB. The model you set only supports 4 frequencies, is this correct? I would like to get this correct for you.

I attach a preliminary version configured for unicable using Durasat uk101.

Using Putty/terminal issue "init 4" command. Ensure that enigma2 has stopped
Using FTP program such as Filezilla, transfer unzipped file to /etc/enigma2
Once File transfer has completed, restart receiver with Putty using following command "init 4".

[mitchelln]

Thanks for your help. Here's a picture of my LNB.
6636166362

[abu baniaz]

Simple post:

I attach a version configured for a Sky quad LNB.

Using Putty/terminal issue "init 4" command. Ensure that enigma2 has stopped
Using FTP program such as Filezilla, transfer unzipped file to /etc/enigma2
Once File transfer has completed, restart receiver with Putty using the following command "init 4".

[mitchelln]

Thank you, I'll give that a go and let you know how it goes.

[abu baniaz]

Explanatory/detailed post:

You have a Sky squad LNB. This is just universal LNBs in one unit. The correct tuner configuration for a tuner with that LNB is: Simple, single 28.2 Press Green to save. It should look like this:

66364


The tuner overview should look like this (this was posted earlier by bmitie)

66365


Once you have to done the transferring, please confirm tuners look as pictured. Please go to Backup manager and create a new settings backup
Blue > Vix > Backup Manager > Green (new backup)


Then delete all the older backups so that in future, you do not inadvertently restore one with wrong details.
Blue > Vix > Backup Manager > Red (Delete)

If you want to do the deletion by FTP, the setting backups are in
/media/hdd/backup


As information only, as you should not be manually editing files, the entries in the settings file for a universal LNB should be:
config.Nims.0.diseqcA=282
config.Nims.1.diseqcA=282

Can I retitle your thread to "Duo 4K SE with Sky quad LNB"?

[mitchelln]

Simple post:

I attach a version configured for a Sky quad LNB.

Using Putty/terminal issue "init 4" command. Ensure that enigma2 has stopped
Using FTP program such as Filezilla, transfer unzipped file to /etc/enigma2
Once File transfer has completed, restart receiver with Putty using the following command "init 4".

I'm afraid this settings file did not work at all. I get no signal. Running an automatic Service scan doesn't return any channels. I reverted to the previous settings files and it works again. The Tuner set up screen does look like the screenshot above.

[bmitie]

As a follow on I just noticed that ABM section for SKY UK and SKY ROI has disappeared since last night and all I did was change the DTT tuners transmitter but a reboot brought it back and this is on openvix 6.4.

Willo has the right idea but never ever done it before. I cant access duo4kse as tv dead.

Updating to a newer version is no longer easy peasy.

Just saw pic of LNB looks very big for an ordinary universal, has it got a unicable output as well and do you know the brand?

[abu baniaz]

@mitchellin,
Forget the file I uploaded and set the tuners yourself properly. Can you confirm that you have signal wires to both tuners? Did you test both tuners individually using signal finder? You have to check several transponders not just one.

[abu baniaz]

Updating to a newer version is no longer easy peasy.


Are you seriously suggesting that flashing a newer image and then restoring the settings file added 19.2 and 23.5 to his settings? The OP had the same issue before the latest image.
You seem to dissuade people from using latest image on other forums. This is unhelpful. You are better off in assisting in getting logs and methods to replicate issue so that issues can be addressed.

Please start your own thread for your ABM issue. ABM will only present the providers for which you have configured tuners.

[mitchelln]

@mitchellin,
Forget the file I uploaded and set the tuners yourself properly. Can you confirm that you have signal wires to both tuners? Did you test both tuners individually using signal finder? You have to check several transponders not just one.
Yes, I had completely deleted the tuner config and set it up from scratch from the Tuner Setup menu two days ago. This got the multiple recording working again, but it does have the erroneous 19.2 lines in the settings. However, this does not seem to stop it working.
I think the Tuner setup screen has some sort of bug which is generating dud config lines.

Also now got this dream EPG issue with the receiver throwing 500 errors (I've created another thread for this) . Pretty fed up now. Just as well I'm Linux savvy, or I'd be seriously stuffed.

[abu baniaz]

I just set up the tuners and there were no 19.2 entries. The default is 19.2 as the original Enigma coders were in Germany. If you confirm on any setting, they will be saved. Doesn't explain how you got 23.5 on there either.

Can you please test both tuners using signal finder.

[mitchelln]

I just set up the tuners and there were no 19.2 entries. The default is 19.2 as the original Enigma coders were in Germany. If you confirm on any setting, they will be saved. Doesn't explain how you got 23.5 on there either.

Can you please test both tuners using signal finder.
I didn't choose 19.2 anywhere. I don't think I even ever seen it presented anywhere in the screens. I have only ever selected 28.2E Astra, which is working. I'm getting a strong signal on 11426 V 29500 8/9

[abu baniaz]

Please check both tuners, not just one. Try a few transponders so you try vertical, horizontal, low, high. Another test is to perform a manual scan, single satellite. You should get over 800 channels if there are no issues. You would have to do that on both tuners too.

I have made the 19.2 mistake myself a few times as it lands on it and you can easily confirm it. You are adamant you didn't do it, so lets leave it that. BTW, if in signal finder or any other scanning applets, you can select other satellites apart from 28.2, your tuners are set incorrectly.

[mitchelln]

Sorry, yes I did the signal finder with both tuners. They both have a good signal for 28.2E. I have the full set of channels available as previously, so all good.

[mitchelln]

Okay, it turns out it's still not able to record multiple channels again. Getting pretty fed up with this now :confused:

[mitchelln]

Hours spent messing about with this :( I guess I still need to remove the erroneous 19.2 entries in settings. Pretty sure something keeps putting them back during a reboot or simply just opening the tuner screen is somehow putting them in again.

[Morini]

There's always the nuclear option of a factory reset and configure the tuners from scratch. Painful, but perhaps quicker and cleaner in the long run?

[Huevos]

I removed the 19.2 entries in the settings file and rebooted, but it just inserted them again. Do you know where it might be picking up this dud setting from please?
There's no mention of 19.2 in my tuner setup screen, so I'm mystified where it's getting it from.
You can't remove them with enigma running. You have to stop enigma, modify the file, then start enigma again.

[twol]

Hours spent messing about with this :( I guess I still need to remove the erroneous 19.2 entries in settings. Pretty sure something keeps putting them back during a reboot or simply just opening the tuner screen is somehow putting them in again.

I have said it, huevos has said it…..you have to STOP the box before replacing the settings file…reboot will not fix it.

[abu baniaz]

Please post a screenshot of your tuner configuration. The individual tuners, not the overview.

Also post the result of this:

cat /etc/enigma2/settings | grep config.Nims > /tmp/mytunerconfig.txt

[mitchelln]

I have said it, huevos has said it…..you have to STOP the box before replacing the settings file…reboot will not fix it.

I AM stopping the box before doing anything. I'm following all provided instructions exactly.

I've attached the mytunerconfig.txt file and screenshots of the tuner screens. The first one shows Tuner A. Tuner B is the same. The 2nd screenshot shows Tuner C and the rest of the satellite ones are the same.

Thanks
66379
66377 66378

[abu baniaz]

You have only shown part of one tuner, we needed to see both tuners. Is there a reason why screenshots are not working?

This is what is in your tuner configuration. A unicable configuration is somehow getting added as well as 19.2 and 23.5 are being added. And a diseqc setup has got added.


config.Nims.0.advanced.lnb.1.diseqcMode=1_0
config.Nims.0.advanced.sat.192.lnb=1
config.Nims.0.advanced.sat.282.lnb=1
config.Nims.0.advanced.sats=282
config.Nims.0.diseqcA=282
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.2.diseqcMode=1_0
config.Nims.1.advanced.sat.192.lnb=2
config.Nims.1.advanced.sat.235.lnb=2
config.Nims.1.advanced.sats=235
config.Nims.1.diseqcA=282
config.Nims.1.diseqcB=3601
config.Nims.1.diseqcC=3601
config.Nims.1.diseqcD=3601
config.Nims.1.powerMeasurement=False
config.Nims.2.advanced.lnb.1.lof=unicable
config.Nims.2.advanced.lnb.1.scrfrequency=1210
config.Nims.2.advanced.lnb.1.scrList=1
config.Nims.2.advanced.lnb.1.unicableManufacturer= Dura-Sat(DUR-line)
config.Nims.2.advanced.lnb.1.unicableProduct=UK101
config.Nims.2.advanced.sat.192.lnb=1
config.Nims.2.advanced.sat.282.lnb=1
config.Nims.2.advanced.sats=282
config.Nims.3.advanced.sats=192
config.Nims.8.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.9.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)

[Huevos]

Ok, so for satellite you have one tuner, a 45308X. With that tuner and your universal LNB you will be able to record from a maximum of 2 satellite transport streams. Updating to a Unicable II LNB will allow you to record from up to 8 satellite transport streams.

[mitchelln]

I have two satellite tuner cards and a DVB-T card as well. Three tuners cards in total. I have been able to record multiple channels in the past. It's software updates that seems to keep breaking it.

I know no one seems to believe me, but I am not adding those extra tuner settings either manually or via the tuner set up screens. I still think there is a bug in either the config backup or restore code, or even the tuner setup screen itself possibly that's adding these entries . I just need a way to get this back to something sensible or a settings file that will work.

Perhaps I should upgrade to a known LNB to help with support. The one I have was fitted to the house when I moved in. The previous owners had a Sky box. This was 11 years ago. So perhaps an upgrade will be best. Any particular recommendations please?

Thanks.

[abu baniaz]

If there was a bug in the code where performing a software update adds 23.5 and 19.2 to tuner configuration as well adding a unicable setup, wouldn't other people have reported it too? I dare you to flash a new image, without restoring anything afterwards and setup your tuners from scratch and video yourself doing it. To my mind you are inadvertently changing something and not realising the mistake you are doing. Alternatively, find someone you trust to remote over and assist you.

Yes, a unicable LNB will allow you to get the most out of your receiver. Provided it is configured correcty. The sponsor sells this LNB among others.
https://www.world-of-satellite.co.uk/gt-sat-gt-s1dcss24-unicable-lnb-1-legacy

I think you have a Mk2 Sky dish, so it should have a 40mm collar. If it isn't you will have to get an adapter for your dish or a newer dish.

[mitchelln]

Thanks for the LNB info. I'll get one. I assume I then just connect it to just one of the inputs on my dual tuner card and there is no point buying a dual cable LNB?

Then I'll probably do a completely clean install by flashing the image. I'll wait until the EPG bug is fixed though.

Thanks for the help with this.

[bmitie]

wow and wow you may have discovered something. I have the duo4kse with 2 x fbc TUNERS ie there is a twin in each slot, its to replace a DUO2 eventually and I have a sony play tv 2ual dtt added. My KURO got the dreaded 8 blinks so could not access the KSE until today as I fixed the KURO y replacing 2 x boards. So while waiting for a delivery I switched on and went to entertainment and proceeded to record channels, bbc bbc2 and then when I clicked on itv4 HD it came up sending the dish to 192 E !! I thought WTF and had about 6 recordings on the go so stopped them and started again and this time when I go to ITV1 I get the message moving from 19E and ITV1 wont open!! When I go to ITV4HD it now opens. Not a clue what is happening. Now my sytem is a bit intricate in that I have a cable going from motorised dish to input on second FBC set as uaals . So I have 3 cables from sky dish and one cable from motorised dish.

I can go on and record other channels and got up to 10 but not itv1. I moved dish to 19e and can view channels on 19 e but not record and tried ITV1 just bit nothing. I can then go to DTT and record all of it, about 12 channels simultaneously= 22 recordings.

But telling dish go to 19e on itv4 first and then showing dish at 19e when I try ITV1 is intriguing. NB I dod have timers set for ITV1 this evening, emmerdale, corrie.

And my tuners my be configured incorrectly here is a pic of slot 2 fbc set up. The reason for the setup in slot 2 is that I wanted input 1 to be for usals and input 2 as a loop out to another box but it wonky so set tuner as is for now.

But ITV4 sending me to 19E is a mystery.

I an using VIX 6.4.010.

I then went to ITV2 ITV3

[abu baniaz]

wow and wow you may have discovered something. I have the duo4kse with 2 x fbc TUNERS ie there is a twin in each slot, its to replace a DUO2 eventually and I have a sony play tv 2ual dtt added. My KURO got the dreaded 8 blinks so could not access the KSE until today as I fixed the KURO y replacing 2 x boards. So while waiting for a delivery I switched on and went to entertainment and proceeded to record channels, bbc bbc2 and then when I clicked on itv4 HD it came up sending the dish to 192 E !! I thought WTF and had about 6 recordings on the go so stopped them and started again and this time when I go to ITV1 I get the message moving from 19E and ITV1 wont open!! When I go to ITV4HD it now opens. Not a clue what is happening. Now my sytem is a bit intricate in that I have a cable going from motorised dish to input on second FBC set as uaals . So I have 3 cables from sky dish and one cable from motorised dish.

I can go on and record other channels and got up to 10 but not itv1. I moved dish to 19e and can view channels on 19 e but not record and tried ITV1 just bit nothing. I can then go to DTT and record all of it, about 12 channels simultaneously= 22 recordings.

But telling dish go to 19e on itv4 first and then showing dish at 19e when I try ITV1 is intriguing. NB I dod have timers set for ITV1 this evening, emmerdale, corrie.

And my tuners my be configured incorrectly here is a pic of slot 2 fbc set up. The reason for the setup in slot 2 is that I wanted input 1 to be for usals and input 2 as a loop out to another box but it wonky so set tuner as is for now.

But ITV4 sending me to 19E is a mystery.

I an using VIX 6.4.010.

I then went to ITV2 ITV3

FBC Tuners do not have a loop out function from their tuners. You cannot loop out to another box.

Your Hardware:
Signal wires from 28.2 fixed dish hooked up tuner A, B and I
Signal wire from motorised dish is hooked up to Tuner J

Going by the overview of your tuners, (you should really access the tuner to obtain a screenshot)
You have told your receiver it has
Tuner I = Motorised dish
Tuner J = It has no physical dish, but should use internal loop-through from Tuner I

If you want us to look at any potential issue, set your tuners to match the hardware connected to them.

What has probably happened is that you have made an error on you tuner configuration and told it it has 19.2 when it does not. It moves what you told it is a motorised dish, but is actually a fixed 28.2 dish until it gets a signal lock. The 28.2 services are now marked as 19.2 too. Have a look at your timers/debug log for the service references.


Correct tuner config = telling receiver what is physically attached to each tuner.

Based on your description, it should be
Tuner A = Simple, Single, 28.2 (Green to save)
Tuner B = Simple, Single, 28.2 (Green to save)
Tuner C-H will be FBC automatic. I.e internal loopthorugh when required.

Tuner I = Simple, Single, 28.2 (Green to save)
Tuner J = Motorised selecting satellites. (Green to save)
Tuner K-P will be FBC automatic. I.e internal loopthrough when required.

[bmitie]

will a look over the weekend. It means pulling out a cabinet and I need to be alone.