Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Results 1 to 11 of 11

Thread: ABM incorrect channel duplicate UK 28.2 - VU+ Solo 4K & Dur-Line UK 124 Unicable LNB

  1. #1

    Title
    Junior Member
    Join Date
    Jun 2011
    Posts
    16
    Thanks
    4
    Thanked 2 Times in 2 Posts

    ABM incorrect channel duplicate UK 28.2 - VU+ Solo 4K & Dur-Line UK 124 Unicable LNB

    After running automatic channel scan I'm ending up with some duplicate channels with different service reference's.

    I'm not sure if it's something to do with the DUR-line UK 124 Unicable LNB, but it was working fine on OpenVIX 3.2, so not sure what's gone wrong.

    After running ABM it's using the duplicated channels that do not work.

    An example of duplicate would be Discovery Channel. I'm getting 2 showing up in last scanned bouquet. I have checked them out in Dreamboxedit and get the following service references for Discovery channel:

    1_0_1_1842_7D9_2_11A0000_0_0_0 <- this one works

    1_0_1_1839_7D9_2_11A0000_0_0_0 <- doesn't work

    ABM is using (1_0_1_1839_7D9_2_11A0000_0_0_0) which does not clear.

    I have attached abm.log file.

    Would really appreciate any help with resolving this
    Attached Files Attached Files
    Last edited by td75; 05-01-17 at 23:29. Reason: add settings file

  2. #2
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,339
    Thanks
    6,422
    Thanked 9,146 Times in 6,224 Posts
    which bouquet are you checking please?

  3. #3

    Title
    Junior Member
    Join Date
    Jun 2011
    Posts
    16
    Thanks
    4
    Thanked 2 Times in 2 Posts
    For this example the Documentaries bouquet. Discovery will not work but Discovery +1 will work.

  4. #4

    Title
    Junior Member
    Join Date
    Jun 2011
    Posts
    16
    Thanks
    4
    Thanked 2 Times in 2 Posts
    Have attached settings file as well if that helps..

  5. #5
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,339
    Thanks
    6,422
    Thanked 9,146 Times in 6,224 Posts
    Quote Originally Posted by td75 View Post
    After running automatic channel scan I'm ending up with some duplicate channels with different service reference's.

    I'm not sure if it's something to do with the DUR-line UK 124 Unicable LNB, but it was working fine on OpenVIX 3.2, so not sure what's gone wrong.

    After running ABM it's using the duplicated channels that do not work.

    An example of duplicate would be Discovery Channel. I'm getting 2 showing up in last scanned bouquet. I have checked them out in Dreamboxedit and get the following service references for Discovery channel:

    1_0_1_1842_7D9_2_11A0000_0_0_0 <- this one works

    1_0_1_1839_7D9_2_11A0000_0_0_0 <- doesn't work

    ABM is using (1_0_1_1839_7D9_2_11A0000_0_0_0) which does not clear.

    I have attached abm.log file.

    Would really appreciate any help with resolving this
    1_0_1_1839_7D9_2_11A0000_0_0_0 works for me. I presume it is a reception issue on your part although I may be wrong.

    If you perform a conventional satellite scan (i.e not use ABM), how many channels do you get?

  6. #6

    Title
    Junior Member
    Join Date
    Jun 2011
    Posts
    16
    Thanks
    4
    Thanked 2 Times in 2 Posts
    That's interesting, does 1_0_1_1842_7D9_2_11A0000_0_0_0 work for you as well?

    Any idea why I get duplicates with difference references when I scan - is that normal? Think reception is good as it's working on other reference.

    I'm getting 982 channels with convention scan.

    screenshot.jpg

  7. The Following User Says Thank You to td75 For This Useful Post:

    abu baniaz (06-01-17)

  8. #7
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,339
    Thanks
    6,422
    Thanked 9,146 Times in 6,224 Posts
    There are "duplicated" channels with different references. It's normal. If you don't want them, disable not-indexed in ABM.

    If you want to rule out ABM, delete all channel data (see linux command in thread in my signature) and just scan the affected transponders.

    Both work fine for me.

  9. The Following 2 Users Say Thank You to abu baniaz For This Useful Post:

    stebourne (06-01-17),td75 (06-01-17)

  10. #8

    Title
    Junior Member
    Join Date
    Jun 2011
    Posts
    16
    Thanks
    4
    Thanked 2 Times in 2 Posts
    Thanks for your help with this. So if both of these should be clearing then I guess it must be a reception issue as you suggested.

  11. #9
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,755
    Thanks
    472
    Thanked 607 Times in 433 Posts
    Quote Originally Posted by abu baniaz View Post
    There are "duplicated" channels with different references. It's normal. If you don't want them, disable not-indexed in ABM.

    If you want to rule out ABM, delete all channel data (see linux command in thread in my signature) and just scan the affected transponders.

    Both work fine for me.
    Abu baniaz with the command to remove channel data will that include m3u bouquets and could it be used in script runner?

  12. #10
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,339
    Thanks
    6,422
    Thanked 9,146 Times in 6,224 Posts
    You can run any script in script runner. It is destructive, so not a good idea leaving it on the box. I was planning to add it (a version exists already), the picon removal script and the more thorough EPG removal (which checks all mounts) to the "system tools" plugin. This has prompts so better to have it in there. Unfortunately, politics and and my lack of coding skill prevent this.

    However, there is code to remove bouquets in images, so that would be better. It is in CPP, not many people well versed in it.


    Code:
    #!/bin/sh
    # Script to remove bouquets and channels then restart
    
    echo "Enigma2 will be stopped and then all channels will be removed. The receiver will restart automatically"
    
    init 4
    sleep 10
    rm -rf /etc/defaultsat.tar.gz
    rm -rf /etc/enigma2/lamedb*
    rm -rf /etc/enigma2/*.tv
    rm -rf /etc/enigma2/*.radio
    rm -rf /etc/enigma2/*.del
    init 3

    I don't have any m3u bouquets, but if they end in ".tv" they will be deleted.

    "/etc/defaultsat.tar.gz"
    OpenATV image has this and reloads it at start with no user choice. That is why I added it to removal process.

    "/etc/enigma2/*.del"
    Deleted bouquets get given the .del extension

  13. The Following User Says Thank You to abu baniaz For This Useful Post:

    dsayers (06-01-17)

  14. #11
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,755
    Thanks
    472
    Thanked 607 Times in 433 Posts
    I did look at adding a delete option for lamedb in service searching the code looks correct ive created a py file in python calling the message box then added the delete to menu.xml I can see it in the menu but when choosing it nothing happens like the if os exist isnt finding lamedb.


    DeleteChannelData.py

    Code:
    from enigma import eTimer
    
    import Components.Task
    from Screens.MessageBox import MessageBox
    from Components.config import config
    
    
    class ChannelDeleteMsg(MessageBox):
    	def __init__(self, session):
    		MessageBox.__init__(self, session, _("Are you sure you want to delete the Channel data from:etc/enigma2/lamedb") , MessageBox.TYPE_YESNO, default=False)
    		self.skinName = "MessageBox"
    code within menu.xml

    Code:
     
    <item weight="15" level="0" text="Delete Channel Data" >
    <code>
    from Components.DeleteChannelData import ChannelDeleteMsg
    def msgClosed(ret):
    	if ret:
    		import os
    		if os.path.exists("etc/enigma2/lamedb"):
    			os.remove("etc/enigma2/lamedb")
    		self.session.openWithCallback(msgClosed, ChannelDeleteMsg)
    </code></item>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.